CPFMTXA is an IBM provided front-end for ICKDSF. There has been a statement posted on this list that support for CPFMTXA will be dropped in the fairly near future. I don't know whether that means that IBM is going to replace ICKDSF or that they just want to get out of the CPFMTXA business.
As for the commands, you could use FORMAT RANGE(0,END) TYPE((0,0,PERM)(1,END,PAGE)) parameters instead of using two format commands. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Bhemidhi, Ashwin > Sent: Monday, June 21, 2010 1:11 PM > To: [email protected] > Subject: Re: IEC606I VTOC INDEX DISABLED > > Hi DJ, > > I have earlier used CMS CPFMTXA utility to format the DASD. I > think CPFMTXA does use ICKDSF for the DASD operations with > CPVOL attribute for the format commands. Going forward I will > start using ICKDSF instead of cpfmtxa: > > So the ICKDSF commands for initializing a DASD volume LEPG2A > @ 5815 as a page volume will be: > > ICKDSF console console > CPVOL FORMAT UNIT(5815) VFY(LEPG2A) RANGE(0,0) CPVOL FORMAT > UNIT(5815) VFY(LEPG2A) RANGE(1,3338) TYPE((PAGE,1, 3338)) > > I have made note of the point that cpowned VM DASD volumes > should be kept offline to MVS. > > But to check if the dummy VTOC was written: > After completing the above format steps, I have detached the > volume @ 5815 from VM. I have asked MVS storage support to > verify that that appeared ok with the dummy VTOC. They said > they got an error trying to read the VTOC. Is this the normal > behavior? > > > Thank you, > Ashwin > Texas Instruments Inc. > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Dave Jones > Sent: Monday, June 21, 2010 11:19 AM > To: [email protected] > Subject: Re: IEC606I VTOC INDEX DISABLED > > Hi, Ashwin. > > When you formatted and allocated the DASD volume from z/OS, > did you specify the CPVOL attribute? That tell ICKDSF to > creaet a "dummy" z/OS style VTOC in cylinder 0 so that to > z/OS, the DASD looks full. > > Also, it's a good idea not to make any of the DASD volumes > that z/VM has marked as 'cpowned' available to the z/OS side. > > DJ > > On 06/21/2010 10:51 AM, Bhemidhi, Ashwin wrote: > > Hello all, > > > > > > I was adding a 2nd page volume LEPG2A (3390-3) to one of our newly > > installed z/VM 6.1 and I accidentally formatted cylinder 0 PERM. We > > are now getting alerts about "IEC606I VTOC INDEX DISABLED ON > > 5815,LEPG2A,142,00000000". The new Page volume is working on z/VM. > > > > q alloc page EXTENT EXTENT TOTAL PAGES HIGH % VOLID RDEV > > START END PAGES IN USE PAGE USED ------ ---- ---------- > > ---------- ------ ------ ------ ---- LEPG1A 5814 1 > > 3338 600840 0 0 0% LEPG2A 5815 1 3338 > > 600840 0 0 0% ------ ------ ---- SUMMARY > > 1174K 0 0% USABLE 1174K > > 0 0% > > > > All our DASD storage is managed from the MVS side and I am guessing > > that it looks for the VTOC and alerts when it cannot find > one. Can I > > use ICKDSF to put a valid VTOC back on the DASD? Are there any > > pointers on this subject that I can use to get more information on? > > Does Device Support facility's user guide all the > information that I > > need to do the above. > > > > Thank you, Ashwin Bhemidhi Texas Instruments Inc. > > > > > > > > -- > Dave Jones > V/Soft > www.vsoft-software.com > Houston, TX > 281.578.7544 >
