1 - what this mod does (and any pre- or co-reqs). 2- how to apply the mod (command syntax for Xedit, VMSES/E, COPYFILE, etc.) 3- How to test the mod and expected output.
All that is kept in our AUX files on our own local mods disk (not IBM's AUXLCL which can have IBM and ISV local mods on it). Sure makes is easier when upgrading, and should a lightening bolt strike the sysprogs, documents things in a place the next sysprog would have to look anyway. Putting the doc in the AUX files (we use AUXRS for "ouR Stuff") to separate it from IBM and ISV AUXLCL updates) keeps it from obfuscating the actual code, and makes is easy to find and print. Mike Walter Hewitt Associates (Sent from the wee keyboard on a Blackberry.) ----- Original Message ----- From: "Gentry, Stephen" [stephen.gen...@lafayettelife.com] Sent: 07/12/2009 12:45 PM AST To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SYSPROF.EXEC I had to rebuild the INSTSEG to get it to work. Not as easy as the CMS segment. I wrote notes this time and stuck them in multiple places. Thanks. ________________________________ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Bruce Roy Sent: Sunday, July 12, 2009 12:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SYSPROF.EXEC It's been awhile since I've done this. But isn't SYSPROF EXEC in the CMSINST segment also? So you should re-gen that segment when you change any EXEC in it. You should also place the latest SYSPROF EXEC on the 490 disk so you don't lose your mod during a maintenance upgrade. Good luck. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Gentry, Stephen Sent: Sunday, July 12, 2009 12:50 AM To: IBMVM@LISTSERV.UARK.EDU Subject: SYSPROF.EXEC Yes, I know it's preferred that users don't modify this EXEC. Everytime we go to a new release of VM, I have to modify this EXEC. We running vm 5.2 and modifications worked fine on that release. The same mods do not work on 5.4. IIRC I can access the S disk as another fmode, for example E. I use MAINT to make the mods to the exec on E. I log off and back on to MAINT and generate a new CMS NSS. Is there anything else I should have to do? I don't think I've got to regen the CMS nucleus do I? I don't remember doing it in years past when I've made this change. I'm checking the insflags variable for the word 'BATCH" Is any of this documented anywhere? I'd really appreciate some help with this. Thanks in advance. Steve The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
