"Gentry, Stephen" <[email protected]> wrote:
> 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. We have long had the need to provide some additional customisation before some parts of the SYSPROF EXEC complete. The way we do this, to provide minimal maintenance impact, is to insert a number of calls into the SYSPROF on first system build (naturally - we use the VMSES source part update procedure). In our case the calls are all to the same LSYSPROF EXEC with different keypoint parameters. This way the (modified) SYSPROF can be built into the INSTSEG once and never needs to change. Note, however, that if some of your external calls are early in the SYSPROF then your LSYSPROF will have to break another rule and be on the S-190 disk. What I have never understood is why optional external calls were not included in SYSPROF as standard, avoiding this need for local customisation. Colin Allinson Amadeus Data Processing GmbH
