CP reads the allocation bit map only when the volume comes online. It's usually VERY difficult to get a CP-Owned volume offline without an IPL - unless the volume was marked CP-Owned but there's no real CP used areas on it. Can you tell us ALL the different allocation types on that volume? And.... what is the use of that VM system (i.e. Just hosting guest systems like z/OS and Linux) or CMS apps?
You can allocate the TDSK cylinders on the disk for use after the next IPL. You can define a new .MDISK on that volume from cyl 0 thru the end, link it R/W, and run CPFMTXA to change the allocation even when it is CP-Owned and online. That gets around having to attach the disk to your ID to format it. Are you running VM:Secure? Until you do all that and IPL, you can still define temporary Virtual Disks In Storage as Marcy described. They are incredibly fast! After trying one you may decide that 100 cylinders of real disk for TDISK is not worth the effort. (We have 2 full 3390-3 for TDISK, but they only get used if there's not enough real storage for a VDISK). Mike Walter Hewitt Associates ----- Original Message ----- From: "Hamilton, Brian" [EMAIL PROTECTED] Sent: 11/04/2007 06:07 PM To: [email protected] Subject: Re: Have no TDSK defined on our system, can I define it and use it without performing an IPL? Thank you, However can I not use an existing CPOWNED volume, one of them is only 25% used and I would like to allocate the last 100 cylinders on that volume for TDSK...and do it without an IPL. I was hoping to do a CPFMTXA and modify the allocation of the above volume? ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Sunday, November 04, 2007 5:56 PM To: [email protected] Subject: Re: Have no TDSK defined on our system, can I define it and use it without performing an IPL? TDISK can be defined as well, IF * you have a RESERVED slot in the CPOWNED list * and you have a free disk Attach the disk to yourself, ALLOCATE part of it as TDSK using ICKDSF, then DEFINE CPOWNED to add the volser to the list of CPOWNED devices in a free slot, at last: ATTACH rdev SYSTEM. If you want to have it after a IPL, update SYSTEM CONFIG. 2007/11/4, Marcy Cortes <[EMAIL PROTECTED]>: Easier to use VDISK (and way faster). "cp define vfb-512 101 120000" (will give you about 100 3390 cyls at address 101) If you don't have it turned on from your system, from a class B id "cp set vdisk syslim inf" "cp set vdisk userlim 800000" (something like that - check the parameters and be sure you set it to what you want it to be ). Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux <http://ehs.homestead.wellsfargo.com/Mainframe/zSS/zSE/zVM-zLinux/Pages/ default.aspx> Enterprise Hosting Services w. (415) 243-6343 c. (415) 517-0895 "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." ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Hamilton, Brian Sent: Sunday, November 04, 2007 2:13 PM To: [email protected] Subject: [IBMVM] Have no TDSK defined on our system, can I define it and use it without performing an IPL? Sorry it's been awhile, our 5.2 system doesn't have any TDSK defined and I would like to define 100 cylinders as TDSK. I have a volume that I use for allocating mini disks, its approx. 75% empty and I want to allocate the last 100 cylinders as TDSK. Can this be done with an IPL? And to do allocate the space do I just invoke CPFMTXA, then ALLOCATE TDSK? Thanks -- Kris Buelens, IBM Belgium, VM customer support 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. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email.
