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
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...
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
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,
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
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
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
