As noted by another listserv member, it's probably the need to resave INSTSEG.
It can get really tough remembering all the things one needs to do to build, install, test, and move local mods into production. I started using the AUX files as a repository of such local information because that "where I trip over it" when needing to modify something. SYSPROF mods are only one of many, including vendor products. We use AUX files named AUXRS (for "ouR Stuff") so they are easy to find, not being the name of any IBM or ISV AUX files. You may not want to bother with that technique. Here's an example... modify it to meet your needs if you wish: SYSPROF AUXRS D1 F 80 Trunc=80 Size=15 Line=0 Col=1 Alt=0 ====> |...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+ * * * Top of File * * * RS0040DS 501 RS040DS Update SYSPROF with local enhancements. * To create, be sure to copy the proper SYSPROF $EXEC to the A-disk * (EXECUPDT overwrites the SYSPROF EXEC on the same disk as the $EXEC)! * To update SYSPROF EXEC, you should: * COPY SYSPROF $EXEC fm = = A (OLDDATE REPLACE UNPACK <-- See UNPACK! * XEDIT SYSPROF $EXEC * (CTL DMSVM SID RS0040DS, then * EXECUPDT SYSPROF EXEC * (CTL DMSVM HISTory SID * Test the SYSPROF EXEC (esp. for syntax errors!) * COPY SYSPROF EXEC A = EXC040DS E (OLDDate REPLace * so VMFBLD won't complain later on. * COPY SYSPROF EXEC A = EXEC E (OLDDate REPLace ERASE * so we don't get mixed up. * then re-save the INSTSEG NSS, e.g. * CP IPL 190 CLEAR PARM NOSPROF INSTSEG NO MTSEG NO * VMFBLD PPF SEGBLD ESASEGS SEGBLIST INSTSEG ( ALL * * * End of File * * * Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Mary Zervos" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 12/13/2006 10:28 AM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Sysprof Exec in z/vm 4.4 Well, we finally migrated to z/vm 4.4 two days ago from vm/esa 2.3. Most of our little fires are out. But here's a new problem for us......we tailor our Sysprof Exec to run an "account exec" before a users's profile exec. For some reason, Sysprof exec is not being run when we Ipl Cms or Ipl 190. Did something change with Sysprof Exec since vm/esa 2.3? Is it still automatically run as part of the CMS initialization procedure when a user logs on or reIpls CMS? Thanks for any help. We've even traced the original z/vm 4.4 Sysprof Exec and it's not being called? Mary Zervos VM Systems Programmer Binghamton University 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.
