On Thu, 15 Feb 2018 14:56:31 +0000, Jousma, David wrote: >Yea, I'm not a fan of that either, especially when things are going south, and >a PARMLIB change needs to be made quickly. I do like the idea of automatic >change tracking like Ira mentioned with various software vendors that do that. > When they provide before/after images of the members in the libraries of >interest, it is helpful for change/audit management, but also when someone fat >fingers something by accident... > Even as many installations prefer not to run production systems directly from SMP/E target libraries, there should be a Deploy step for PARMLIB which copies from change-controlled libraries to SYS1.
With suitable auditing of any bypass of Deploy. >-----Original Message----- >From: Allan Staller >Sent: Thursday, February 15, 2018 9:22 AM > >I have heard of some shops that had SYS1.PARMLIB under LIBRARIAN or PANVALET >control. >I (fortunately) have never had to work in any of them. > >-----Original Message----- >From: Sean Gleann >Sent: Thursday, February 15, 2018 7:39 AM > >I'm coming under pressure from 'upstairs' regarding the idea of implementing >change control or versioning on parmlib members and other 'control'-type files >(WLM policy, SMS rules, RACF, etc) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
