We did quite a few redbooks on the subject of 'MVS Software Maintenance'.
Birger Heede
IBM Software Group
SArnett wrote:
I disagree for three two reasons. The first is that the IBM maintenance
documentation stated that it could be done to the live system, the
second is that the IBM maintenance documentation I was provided with was
WRONG in how to apply the maintenance, and the third reason is that
doing the oposite worked.
If you will note, I said I had installed XA express. XA express was
available ONLY to new MVS customers. Those coming from non-IBM systems
or from VSE and VM. In both VM and VSE we applied the maintenance to
the live system(with backups of course). I was new to MVS and had no
MVS experience on which to fall back.
Two months after the incident that I spoke of, my brother showed up in
town on vacation. He was a long time MVS sysprog and showed me how to
set up an emergency system(which saved me when my boss inserted a JCL
error into JES2). It wasn't until about four years later that I learned
how to do indirect catalogue entries and began flip-flopping sysres
volumes/SMPE zones when applying maintenance. I cannot even remember at
what point in time I learned to do that. I went from a shop where I
installed XE express coming from VM/VSE to a shop where I installed XA
express coming from a non-IBM machine and OS to a shop where I upgraded
the system from MVS/SP to MVS/XA using the CBIPO. It was after the
CBIPO that I began the flip-flop maintenance philosophy.
I assure your that there was nothing in the XA express or CBIPO
documentation explaining the "proper" maintenance philosophy of an MVS
system. Nor was anything said in the MVS/XA Structure and Flow class
from IBM or that piece of crap MVS Installation Workshop at IBM for
which my company wasted money by sending me. The philosophy that I
learned I garnered from talking to people like those on this list that
give constructive help and from reading journals.
Shmuel Metz (Seymour J.) wrote:
That sounds like you were using your target system as your driver
system, in which case it was not TSO/E that was at fault.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
