Hi Peter,
How about this situation ...
I am part of a team of people who plan maintenance upgrades many months
in advance.
There is no possibility of IPL (for many of the maintenance upgrades).
All Batch is held (other than implementation jobs); DFSMShsm, CICS, IMS
and DB2 are down.
TSO is limited to implementers.
SCSQAUTH (an MQ LNKLSTd Dataset) is emptied, its contents replaced and
LLA is REFRESHd.
MQ, CICS, IMS and DB2 are started and tested by implementers and then by
the customer.
After everyone signs off, it's back to "business as usual" and Batch is
restarted.
Do you see any holes in this approach?
Thanks and regards,
David
On 2020-10-19 09:46, Peter Relson wrote:
You delete members (let alone delete all members) from any LNKLST data set
at your own risk. If you're going to do that, you'd better not have LLA
active.
Maybe you get away with it with LLA up and a refresh. That doesn't mean it
worked or didn't leave you undesirably exposed.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
