The 19E Y disk can be changed and the files copied without a problem. It
is a little more work than adding a new "public" disk that everyone
accesses. Once the disk is moved, a new "Y-stat not available" error
message starts appearing after IPLing CMS. To resolve that, do the
SAMPNSS CMS from MAINT, then IPL 190 PARM SAVESYS CMS.  


Bob Bates
Enterprise Hosting Services - Enterprise Virtualization - z/VM and
z/Linux 

w. (469)892-6660
c. (214) 907-5071

"This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein.  If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message.  Thank you for your cooperation."



-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Fox Blue
Sent: Monday, May 19, 2008 8:00 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Extension of MAINT 190 (S-DISK)

Kris, 

thank you very much for the info. Focusing now on Y-DISK. Is a simple
cop= y of the files enough after formating the new Y-DISK or are there
onher pit= falls?

Fox 

>Extending the S-disk is seldom done, because not that easy.  Most 
>people would place extra products on the Y-disk (19E), or yet another 
>disks, accessed by SYSPROF.  But, if you insist:
>- FORMAT the new minidisk e.g. as B
>- FORMAT newcuu B nnn (RECOMP
>  makes room for the CMS nucleus, "nnn" is the size of the new minidisk

>minus 7 cylinders
>  (a CMS nuclues is supposed to take at most 7 cylinders nowadays)
>- update DMSNGP, adapt CYLADDR=100 to CYLADDR=nnn
>  regenerate DMSNGP
>- VMFBLD PPF ZVM CMS  CMSLOAD (ALL
>  to build the new nucleus load deck in your reader
>- DET 190 #DEF newcuu 190#IPL 00C CLEAR
>
>As this is not for dummies, I explained briefly.
>
>Kris
>

>
>
>--
>Kris Buelens,
>IBM Belgium, VM customer support
>=========================
==========================
========================

Reply via email to