What is a SIPO?
Ward, Garry
System Installation Productivity Option, if I remember correctly.
Basically, instead of separate installation tapes for each component of
VSE, you get a couple of standardized tapes, and a simpler install
process.
Garry E. Ward
Senior Software Specialist
Maritz Research
Automotive Research Group
419-725-4123
-----Original Message-----
From: Steve [mailto:steve.we...@hanesfinishing.com]
Sent: Monday, October 28, 2002 2:09 PM
To: VSE Discussion List
Subject: What is a SIPO?
I am going to be dumb about this and ask "What is SIPO?"
I have gone to the ShopZSeries web site and want to get
a refresh of VSE 2.6.1 and PSP bucket so I can FSU my
existing 2.5.1 system.
Any info is appreciated.
--
Mit freundlichen Gru?en,
Steve Weifenbach -- steve.weifenbach at hanesfinishing dot com
Always do right; this will gratify some people and astonish the rest.
-- Mark Twain
<font size="1">Confidentiality Warning: This e-mail contains information intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail. If you have received this e-mail in error, please immediately notify us by return e-mail. Thank you.
Steve
I have gone to the ShopZSeries web site and want to get
a refresh of VSE 2.6.1 and PSP bucket so I can FSU my
existing 2.5.1 system.
Any info is appreciated.
--
Mit freundlichen Grüßen,
Steve Huggins
-----Original Message-----
From: Steve [mailto:steve.we...@hanesfinishing.com]
Sent: Monday, October 28, 2002 2:09 PM
To: VSE Discussion List
Subject: What is a SIPO?
Mitch Davidson
Did a (fellow) dinosaur create the documentation you are lookin' at?
:)
Steve
knew the official name for the package other than the SP of VSE/SP.
Mitch Davidson
fading... there was IPO (Installation Productivity Option) and IPO/E
(think the E was "Enhanced") and SIPO but wouldn't put down a nickel on
which was first and which was last. (There might have been a SIPO/E,
also.)
The SP in VSE/SP isn't the same as the S and P in SIPO, as far as I
remember.
indust...@dapsco.com
I started my career in 1980 with DOS/VSE (don't ask me release numbers!)
and my first installation was the SIPO/E variety (circa 1982).
System Installation Productivity Option / Enhanced
Note: The 'SP' in VSE/SP was 'System' and either 'Program', 'Product', or
'Package'.
Sincerely,
Dave Clark
dcl...@dapsco.com
DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
(937) 294-5331
Eric Vaughan
IPO debuted in VSE/AF 1.3, I believe, adding a new set of ICCF macros,
(@install, @PTF etc.), essentially, called the Interactive Productivity
Function or IPF. These were a series of macros used to begin the
automation of system tasks, like installations, application of PTFs etc.
Then there was the ever stable and popular 1.3.5 version of VSE/AF, one
that was so stable that many stayed there for years. In VSE/AF 1.4 we
moved to SIPO which now included a "packaged" installation of VSE and
its products, to coincide with the movement to make VSE easier to
install and maintain.
VSE/SP was then introduced in the next release, in what was called
VSE/SP 2.1. Now this IPF type of automated installation and maintenance
had been greatly "enhanced" to something called the Interactive User
Interface (IUI). The IUI was a complete set of panels to do everything,
not just system maintenance, including managing and editing ICCF library
members, submitting jobs, accessing the console (for the first time from
IBM other than the system console), accessing Power Queues and much
more. The IUI was IBM's attempt to add a simpler, menu-driven system to
administer VSE. VSE/SP was also significant because SP (System Package)
was the first official "packaging" of VSE, CICS, ICCF, VSAM and etc.
into a group of products to install. VSE/SP also began to pave the way
for storage constraint relief for the first time in many years,
providing the Virtual Addressabililty Extended, or VAE that still capped
us at 16 mb of virtual storage, but now we could have 3 address spaces
of 16 mb (in theory with the "shared" area). The 3 was an arbitrary
limit that IBM selected, (architecturally it could easily have been 8),
but capped at 3 to make sure VSE did not encroach on the functionality
and usability of MVS. In stepped Pete Clark from Olan Mills, who
published the very famous "patch" that was distributed free to VSE users
around the world, allowing VSE to have 7 address spaces. After IBM's
reluctance, they then officially released VSE/SP 3.2, I believe, that
included 8 address spaces of 16 MB apiece. The release of the patch by
Pete was profound and advanced the cause of VSE in many ways. There was
substantial press coverage of the power of the user community and Pete's
contribution that affected so many. Many recognize Pete as a tireless
worker for VSE customers, but that one single event had a very dramatic
effect on the future of VSE, and Pete has always been remembered for
that. VSE/SP continued until VSE/SP 4.1, which as loosely known as the
"lights-out" release, adding options like AUTOIPL and 1 pack VSE
systems, largely to support one extremely large VSE user with 17,000,
that's right 17,000 VSE systems around North America.
Then finally, we moved to VSE/ESA 1.1 in 1990, that really opened the
door, with support for first more real memory (up to 2 GB) and then more
virtual memory (up to 2 GB). Also added more devices, dynamic partitions
(more than 13 for the first time) and a plethora of other dramatic
changes. All brought about by a determined, and vocal user (and VSE
IBMers) community that demanded changes, specified exactly which ones we
needed and got what they asked for and more. Fast forward 12 years, and
VSE/ESA is now on 2.6 and moving towards 2.7 with steady improvements
and changes in each new release.
We've had an incredible history, and this is the tip of the iceberg as
far as stories to tell. It is also a great reminder of the evolution and
the effect that the very active VSE community has always had, and the
incredible real cooperation we've had with the Boeblingen Lab, and their
support and ingenuity.
We should really think about where next we could guide IBM with the VSE
operating system, because they really have never had the same level of
"demand" and requests ever since VSE/ESA was released.
What a trip down the memory lane! I'm not sure just how precise the
numbers are, but the gist is there!
*-----------------------------------------------------------------------
-*
Eric Vaughan
IntelliWare Systems, Inc. - An IBM Business Partner
Authors of:
z/Web-Host -- Access Your Applications from Anywhere
z/XML-Host -- Extend Your Applications to Anywhere
Visit us at http://www.intelliware.com
Tel: (817) 277-0800 Fax: (817) 277-0899
*-----------------------------------------------------------------------
-*
> -----Original Message-----
> From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf
Of
> Mitch Davidson
> Sent: Monday, October 28, 2002 2:23 PM
> To: VSE Discussion List
Phil Payne
A blast from the past.
"IPO" is "Installation Productivity Option" - a packaging trick IBM tried in the late 1970s to
make life difficult for the customers of plug-compatible vendors while appearing to make it
blissfully easy for those using systems with IBM badges on them.
However - it didn't work.
So the lawyers plugged a couple of glaring gaps in the paperwork, and came up with SIPO -
"System Instllation Productivity Option".
That didn't work either, so ...
--
Phil Payne
http://www.isham-research.com
+44 7785 302 803
+49 173 6242039