Re: VTOC rename

2007-02-19 Thread Walter Marguccio
From: Bruce Black [EMAIL PROTECTED] But I think you are correct about the SERNO field. I have a tool which can modify the field, so I will try to run a test. This is how the VTOCIX was listed using IEHLIST: -DATA SET NAME--- CREATED DATE.EXP FILE TYPE SMS.IND EXT DS.VOL1

Re: VTOC rename

2007-02-18 Thread Bruce Black
I did open a PMR, and they told me that the inconsistent VTOCIX name was the cause of the problem. Later, when I post my considerations to the list and read your update, I started to think that the name inconsistency alone had nothing to do with it. Then I found this SER NO field, and decided

Re: VTOC rename

2007-02-16 Thread Walter Marguccio
From: Bruce Black [EMAIL PROTECTED] Actually, it sounds like a problem which should be reported to IBM. It is either a code error or a doc update. I did open a PMR, and they told me that the inconsistent VTOCIX name was the cause of the problem. Later, when I post my considerations to the

Re: VTOC rename

2007-02-15 Thread Walter Marguccio
From: Bruce Black [EMAIL PROTECTED] So, the question seems to be is the VTOCIX active?, and nothing to do with the VTOCIX name. For the sake of clearness and to close the thread on this topic, I have to admit that Bruce was right about VTOCIX name having nothing to do with the problem I

Re: VTOC rename

2007-02-15 Thread Bruce Black
Instead of simply renaming the VTOCIX, I converted the VTOCIX to OSVTOC with PURGE; then I built a VTOCIX with a consistent name on the affected volume and reran my DR restore. The correct volser shows up now, everything is consistent. Another thing learned. Actually, it sounds like a problem

Re: VTOC rename

2007-02-12 Thread Bruce Black
I also thought the name of the VTOC (well, its 3rd qualifier) didn't have necessarily to match the DASD volser. In case you copy your DASD using the Flashcopy technique with DUMPCOND, and you later DUMP the volume (for DR purposes or whatever other reason) well, it DOES matter. If the VTOC's

Re: VTOC Rename

2005-10-27 Thread Ed Finnell
In a message dated 10/27/2005 8:27:45 A.M. Central Standard Time, [EMAIL PROTECTED] writes: Somebody can help me? Is it corrupt or just mis-cataloged? Usually it's sufficient to convert index to OS format and back to IX.

Re: VTOC Rename

2005-10-27 Thread Ted MacNEIL
Can be rename the the VTOC index Why care? I've run many volumes that have the last qualifier not match the VTOCIX. It's just a convenience when you first create it. -teD In God we Trust! All others bring data! -- W. Edwards Deming

Re: VTOC Rename

2005-10-27 Thread Paul Gilmartin
In a recent note, Bruce Black said: Date: Thu, 27 Oct 2005 15:52:00 -0400 However, there is no need to rename it. Any dataset name beginning with SYS1.VTOCIX. is acceptable, it does not have to match the volser. Hmmm. In a recent thread I learned that IEHLIST does not require