Re: Sysprof Exec in z/vm 4.4
Thanks to everyone for their help on Sysprof. I used Mike's suggestion below and it worked like a charm. The new z/vm 4.4 system dust is starting to settle. Anyone game for another question... Yesterday on our new 4.4 system, I was deleting some old users on random packs using Dirmaint while logged onto Maint. Our person who runs Vmbackup was logged on her Vmrmaint account running backups. All the Vmbackup and Vmrmaint mdisks are on the old 230RES pack that we now have attached to the 4.4 system as CP System. The Vmbackup person called me to say that all the mdisks for vmbackup and vmrmaint were empty (she never logged off) and upon checking myself, somehow 230RES was relabeled to SCRTCH. Wow, was that a shocker for me! I immediately restored a backup that I had but am now searching for the reason this happened. Dirmaint? Thanks again for any help. Mary Zervos Binghamton University Mike Walter wrote: 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 AUXRSD1 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! * XEDITSYSPROF $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.
Re: Sysprof Exec in z/vm 4.4
Any chance that a minidisk covering cyl 0 was defined, them deleted? Mary Zervos wrote: Thanks to everyone for their help on Sysprof. I used Mike's suggestion below and it worked like a charm. The new z/vm 4.4 system dust is starting to settle. Anyone game for another question... Yesterday on our new 4.4 system, I was deleting some old users on random packs using Dirmaint while logged onto Maint. Our person who runs Vmbackup was logged on her Vmrmaint account running backups. All the Vmbackup and Vmrmaint mdisks are on the old 230RES pack that we now have attached to the 4.4 system as CP System. The Vmbackup person called me to say that all the mdisks for vmbackup and vmrmaint were empty (she never logged off) and upon checking myself, somehow 230RES was relabeled to SCRTCH. Wow, was that a shocker for me! I immediately restored a backup that I had but am now searching for the reason this happened. Dirmaint? Thanks again for any help. Mary Zervos Binghamton University
Re: Sysprof Exec in z/vm 4.4
Did you bay any chance use DIRMAINT to delete a minidisk that covered cylinder zero of volume 230RES? When DIRMAINT deletes a minidisk, it usua lly has its worker DATAMOVE format the minidisk before deallocating it to prevent the next user from getting data from it. /Tom Kern On Thu, 14 Dec 2006 09:57:06 -0500, Mary Zervos wrote: Anyone game for another question... Yesterday on our new 4.4 system, I was deleting some old users on random packs using Dirmaint while logged onto Maint. Our person who runs Vmbackup was logged on her Vmrmaint account running backups. All the Vmbackup and Vmrmaint mdisks are on the old 230RES pack that we now have attached to the 4.4 system as CP System. The Vmbackup person called me to say that all the mdisks for vmbackup and vmrmaint were empty (she never logged off) and upon checking myself, somehow 230RES was relabeled to SCRTCH. Wow, was that a shocker for me! I immediately restored a backup that I had but am now searching for the reason this happened. Dirmaint?
Re: Sysprof Exec in z/vm 4.4
There is a CYL0_BLK0_CLEANUP setting, and if you set it to YES, it will scratch mdisks that start at cyl 0 too. Or if you have, like we once suffered from, an admin guy who found it more secure to use the option CLEAN on the PURGE or DMDISK commands, overriding the default dirmaint settings, well we lost the same system twice, before we realized that someone else had an userid with fullpack minidisk overlays removed as he was no longer responsible and we were sure we had Dirmaint configured with CYL0_BLK0_CLEANUP=NO .. Ronald van der Laan
Re: Sysprof Exec in z/vm 4.4
You have to reload the INSTSEG DCSS -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mary Zervos Sent: Wednesday, December 13, 2006 11:29 AM To: IBMVM@LISTSERV.UARK.EDU 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: Sysprof Exec in z/vm 4.4
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 AUXRSD1 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! * XEDITSYSPROF $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.
Re: Sysprof Exec in z/vm 4.4
The fact that CMS prefers to use the SYSPROF from the INSTSEG opens opportunities to test your new SYSPROF. Just IPL CMS with: IPL CMS PARM INSTSEG NO Kris, IBM Belgium, VM customer support Mary Zervos [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 2006-12-13 17:28 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
