Or you remove the SYSPROF.XEC from the segement. We used to have a local mod and to avoid problems we had removed it from the segment.
Bruce Roy schreef: > > 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:[email protected]] > *On Behalf Of *Gentry, Stephen > *Sent:* Sunday, July 12, 2009 12:50 AM > *To:* [email protected] > *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 >
