Re: VTOC trashed

2006-10-04 Thread Mike Szyszka

No- problem is still here... have a pressing matter to ask you all.
New message.


On 9/27/06, Shmuel Metz (Seymour J.) [EMAIL PROTECTED] wrote:


In [EMAIL PROTECTED], on 09/22/2006
  at 02:14 PM, Ed Finnell [EMAIL PROTECTED] said:

So all VSAM on the pack is gone? Maybe somebody else can answer, I
don't   know if a REFVTOC will make a new VVDS or not.

It certainly won't fill in the missing catalog information. Do you[1]
have a recent EXPORT?

[1] Mike, not Ed.

--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see http://patriot.net/~shmuel/resume/brief.html
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html





--
Thanks,
Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-27 Thread Shmuel Metz (Seymour J.)
In [EMAIL PROTECTED], on 09/22/2006
   at 02:14 PM, Ed Finnell [EMAIL PROTECTED] said:

So all VSAM on the pack is gone? Maybe somebody else can answer, I
don't   know if a REFVTOC will make a new VVDS or not.

It certainly won't fill in the missing catalog information. Do you[1]
have a recent EXPORT?

[1] Mike, not Ed.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see http://patriot.net/~shmuel/resume/brief.html 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed?

2006-09-26 Thread Hal Merritt
I would agree. Get off that pack ASAP. 

I saw something like that when some ICKDSF function was performed from
one LPAR while being online to another. Varying the unit offline to
*all* LPARs and then back online seemed to fix the problem for us. 

Another possibility is that volume is not protected by GRS or
equivalent. Corruption (to include a VTOC) is to be expected. 

Yet another is a DFDSS volume restore while being online to any LPAR. 

HTH.  

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Szyszka
Sent: Friday, September 22, 2006 9:35 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: VTOC trashed?

Hi all,

ISPF Option 3.4 with just the volser, I receive message in the upper
right
corner of the screen.
Incomplete VTOC list

PF1 shows
Index entry not included because VTOC entry does not exist.

I assume this dasd is trashed and need to be re-inited?
The data sets are still working. I can allocate a new datasets.
One problem is that it is a system pack.

-- 
Thanks,
Mike

 
NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively
for the individual or entity to which it is addressed. The message, together 
with any attachment, may contain confidential and/or privileged
information. Any unauthorized review, use, printing, saving, copying, 
disclosure 
or distribution is strictly prohibited. If you have received this message in 
error, please immediately
advise the sender by reply email and delete all copies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed?

2006-09-25 Thread Chris Mason
Mike

Mention of a trashed VTOC always reminds me of two events from my past:

1)

One volume I - and some colleagues - were working on had accumulated a large
number of temporary data sets. The smart one in the group said I can easily
fix that, here's - after a burst of work on the 029[1] - the utility to do
it. Once the utility had run we had a very *very* clean volume. I - yes, I
was the naively smart one - had too quickly keyed up a

SCRATCH VTOC,VOL=2314=whtevr,SYS

card for my IEHPROGM cards. The too quickly means that the comma before
SYS got missed out. Ever since I made sure always to place the SYS at the
beginning of the parameter list for this function.

Fortunately it was possible to rebuild the volume from tape - slowly.
Unfortunately one of my colleagues was of Scottish origin and it was New
Year's Eve and he had pressing plans to be somewhere other than a machine
room.

2)

A volume I was working with had been restored from tape and, strangely, the
VTOC did not restore. (Maybe other parts also did not restore but - as was
discovered eventually - all that was really needed did.) Fortunately again,
in this case, the guy responsible had brought a VTOC listing. After much 029
work, using techniques I have long forgotten but which at the time I knew
about, I had recreated the VTOC on the volume from the listing - and it
worked.

The unfortunate part here is that the volume had been created under DOS (now
VSE) and the data set names were - how shall I put this? - highly
informative as DOS names traditionally were, restricted only by the 44
character limit. Thus the 029 work was greatly extended.

Chris Mason

[1] Key punch http://www.columbia.edu/acis/history/029.html (for the benefit
of the youngsters) These stories are from the bad old days before TSO.

- Original Message - 
From: Mike Szyszka [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Friday, 22 September, 2006 4:35 PM
Subject: VTOC trashed?


 Hi all,

 ISPF Option 3.4 with just the volser, I receive message in the upper right
 corner of the screen.
 Incomplete VTOC list

 PF1 shows
 Index entry not included because VTOC entry does not exist.

 I assume this dasd is trashed and need to be re-inited?
 The data sets are still working. I can allocate a new datasets.
 One problem is that it is a system pack.

 -- 
 Thanks,
 Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed?

2006-09-25 Thread Arthur T.
On 25 Sep 2006 12:12:39 -0700, in bit.listserv.ibm-main 
(Message-ID:[EMAIL PROTECTED]) 
[EMAIL PROTECTED] (Chris Mason) wrote:



I
was the naively smart one - had too quickly keyed up a

SCRATCH VTOC,VOL=2314=whtevr,SYS

card for my IEHPROGM cards. The too quickly means that 
the comma before
SYS got missed out. Ever since I made sure always to 
place the SYS at the

beginning of the parameter list for this function.


 I always code my SMP input with CHECK as the first 
parm (when doing CHECK).  I don't think I ever had an 
accidental non-CHECK before I started doing it, but putting 
that kind of parm where it can't be ignored due to an 
accidental period just seems like a good idea.



--
I cannot receive mail at the address this was sent from.
To reply directly, send to ar23hur at intergate dot com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed?

2006-09-22 Thread Alan C. Field
Mike,

I'd try disabling and then rebuilding the vtoc index before you go as far 
as re initing. 

Sounds like there is an entry in the index that isn't on the volume.

ICKDSF  BUILDIX ...



Mike Szyszka [EMAIL PROTECTED] 
Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
09/22/2006 09:35
Please respond to
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU


To
IBM-MAIN@BAMA.UA.EDU
cc

Subject
VTOC trashed?






Hi all,

ISPF Option 3.4 with just the volser, I receive message in the upper right
corner of the screen.
Incomplete VTOC list

PF1 shows
Index entry not included because VTOC entry does not exist.

I assume this dasd is trashed and need to be re-inited?
The data sets are still working. I can allocate a new datasets.
One problem is that it is a system pack.

-- 
Thanks,
Mike




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed?

2006-09-22 Thread Daniel A. McLaughlin
I would attempt to migrate as much data off as possible, or backing up, 
before anything else.




Daniel McLaughlin
ZOS Systems Programmer
Crawford  Company
PH: 770 621 3256
[EMAIL PROTECTED]









--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed?

2006-09-22 Thread Cliff McNeill
Mike,

I agree with Alan.  Try to convert the VTOC from indexed to OS, and then 
back again.  Here are the statements I use in ICKDSF:


Convert to OS

BUILDIX- 
 DDNAME(DISK)  - 
 OS   NOPURGE 


Convert back to Indexed

BUILDIX- 
 DDNAME(DISK)  - 
 IX 

Cliff McNeill






Mike,

I'd try disabling and then rebuilding the vtoc index before you go as far 
as re initing. 

Sounds like there is an entry in the index that isn't on the volume.

ICKDSF  BUILDIX ...



Mike Szyszka [EMAIL PROTECTED] 
Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
09/22/2006 09:35
Please respond to
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU


To
IBM-MAIN@BAMA.UA.EDU
cc

Subject
VTOC trashed?

Hi all,

ISPF Option 3.4 with just the volser, I receive message in the upper right
corner of the screen.
Incomplete VTOC list

PF1 shows
Index entry not included because VTOC entry does not exist.

I assume this dasd is trashed and need to be re-inited?
The data sets are still working. I can allocate a new datasets.
One problem is that it is a system pack.

-- 
Thanks,
Mike






--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


VTOC trashed

2006-09-22 Thread Mike Szyszka

I was able to run a List VTOC. It looks normal.

DATE: 2006.265  TIME: 12.03.51

CONTENTS OF VTOC ON VOL SYS501  THIS VOLUME IS NOT SMS MANAGED
THERE IS A  1 LEVEL VTOC
INDEX
DATA SETS ARE LISTED IN ALPHANUMERIC ORDER
.
THERE ARE  2121 EMPTY CYLINDERS PLUS58  EMPTY TRACKS ON THIS VOLUME
THERE ARE3559 BLANK DSCBS IN THE VTOC ON THIS VOLUME
THERE ARE285 UNALLOCATED VIRS IN  THE INDEX

--
Thanks,
Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Bruce Black
Mike, does the VTOCIX (SYS1.VTOCIX.xx) appear in the LISTVTOC?  If 
not, that seems to match your error message.


Or could the message have been refering to the index component of some 
VSAM file?   Can you tell if an index which should be on the volume is 
missing??


An IDCAMS DIAGOSE of the VVDS might find this problem

--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Mike Szyszka

These show up in the list VTOC

SYS1.VTOCIX.SYS501
SYS1.VVDS.VSYS501

This one seems to missing the index
SYSV.ING02.TAKEOVER
SYSV.ING02.TAKEOVER.DATA


On 9/22/06, Bruce Black [EMAIL PROTECTED] wrote:


Mike, does the VTOCIX (SYS1.VTOCIX.xx) appear in the LISTVTOC?  If
not, that seems to match your error message.

Or could the message have been refering to the index component of some
VSAM file?   Can you tell if an index which should be on the volume is
missing??

An IDCAMS DIAGOSE of the VVDS might find this problem




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Bruce Black

This one seems to missing the index
SYSV.ING02.TAKEOVER
SYSV.ING02.TAKEOVER.DATA 
It may be an ESDS or another type that has no index.  Do a LISTCAT on 
the cluster name to see what the component names should be.  The 
DIAGNOSE should also pick this up if it is really missing


--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Ed Finnell
 
In a message dated 9/22/2006 11:12:45 A.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

THERE  ARE  2121 EMPTY CYLINDERS PLUS58  EMPTY TRACKS ON THIS  VOLUME
THERE ARE3559 BLANK DSCBS IN THE VTOC ON THIS  VOLUME
THERE ARE285 UNALLOCATED VIRS IN  THE  INDEX




Maybe the VTOC's OK and the catalog is corrupt. Guess DIGNOSE for suspect  
ALIAS to Volume and UCAT are in order??? 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Mike Szyszka

Listc shows... does not appear to be an error


ASSOCIATIONS

  CLUSTER--SYSV.ING02.TAKEOVER



  ASSOCIATIONS
DATA-SYSV.ING02.TAKEOVER.DATA
DATA --- SYSV.ING02.TAKEOVER.DATA

--

Thanks,
Mike


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Ed Finnell
 
In a message dated 9/22/2006 12:26:31 P.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

Listc  shows... does not appear to be an error




How about the DIAGNOSE? What happens if you just try to print the file? If  
it's too big can just print to DD DUMMY. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Ed Finnell
 
In a message dated 9/22/2006 12:34:40 P.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

How  about the DIAGNOSE? What happens if you just try to print the file? If   
it's too big can just print to DD DUMMY. 




Oh, IEHLIST for the pack. LISTVTOC will show any overlaps. Haven't had to  do 
any of these since we got rid of SLEDs
 
Is this pack SHAREd amongst systems?
 
Guess last thought is Michael Cleary's DAF(data set audit) is good to see  
who's touched the file. _www.cbttape.org_ (http://www.cbttape.org) 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Gabe Torres
..really interested in this thread,.. We have some sysprogs that
maintain their systems that share a disk volume across separate,
nonsysplexed Lpars. Datasets accessed/updated from different systems,..
no GRS protection. 
So I am curious if this is a situation that could clobber a vtoc.
gabe


Maybe the VTOC's OK and the catalog is corrupt. Guess DIGNOSE for
suspect ALIAS to Volume and UCAT are in order??? 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Mike Szyszka

Ran this..
//DIAG EXEC PGM=IDCAMS,COND=(0,NE)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DIAGNOSE VVDS IDS(SYS1.VVDS.VSYS501)
/*

No errors listed.


On 9/22/06, Gabe Torres [EMAIL PROTECTED] wrote:


..really interested in this thread,.. We have some sysprogs that
maintain their systems that share a disk volume across separate,
nonsysplexed Lpars. Datasets accessed/updated from different systems,..
no GRS protection.
So I am curious if this is a situation that could clobber a vtoc.
gabe


Maybe the VTOC's OK and the catalog is corrupt. Guess DIGNOSE for
suspect ALIAS to Volume and UCAT are in order???

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html





--
Thanks,
Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Mike Szyszka

I'd be glad to send anybody the complete problem / resolution when the
problem is fixed.
The list rejected an early email because it had too many replies.

Thanks,Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Bruce Black


..really interested in this thread,.. We have some sysprogs that
maintain their systems that share a disk volume across separate,
nonsysplexed Lpars. Datasets accessed/updated from different systems,..
no GRS protection. 
So I am curious if this is a situation that could clobber a vtoc.
No.  Updates to the VTOC are protected by an ENQ/RESERVE under resource 
SYSVTOC/volser.  Since these systems are not part of a GRSplex, the 
hardware RESERVE is actually issued, and it protects the VTOC from 
concurrent updates that could corrupt it.


The one exposure occurs if they have defined the disk as non-shared 
(SHARED...NO) in HCD/IOCP.   In this case the RESERVE is not done, and 
the exposure for VTOC corruption exists if both systems create, extend 
or delete datasets from the volume.


Having said that, the exposure exists for DATASET corruption, if the 
same dataset, especially a PDS, is updated from multiple systems 
concurrently.  It is up to the updatng application whether it issues a 
RESERVE when updating a PDS to serialize updates. 


--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Mike Szyszka

This command found the problem? No VVDS?

listc ent(/) allDS.VSYS501
SYS501

IDC3012I ENTRY SYS1.VVDS.VSYS501 NOT FOUND+
IDC1566I ** SYS1.VVDS.VSYS501 NOT LISTED
IDC0014I LASTCC=4
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
***



On 9/22/06, Mike Szyszka [EMAIL PROTECTED] wrote:


I'd be glad to send anybody the complete problem / resolution when the
problem is fixed.
The list rejected an early email because it had too many replies.

Thanks,Mike





--
Thanks,
Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Mike Szyszka

It seems DIAGNOSE that was run previous did not find the error?



On 9/22/06, Bruce Black [EMAIL PROTECTED] wrote:



 ..really interested in this thread,.. We have some sysprogs that
 maintain their systems that share a disk volume across separate,
 nonsysplexed Lpars. Datasets accessed/updated from different systems,..
 no GRS protection.
 So I am curious if this is a situation that could clobber a vtoc.
No.  Updates to the VTOC are protected by an ENQ/RESERVE under resource
SYSVTOC/volser.  Since these systems are not part of a GRSplex, the
hardware RESERVE is actually issued, and it protects the VTOC from
concurrent updates that could corrupt it.

The one exposure occurs if they have defined the disk as non-shared
(SHARED...NO) in HCD/IOCP.   In this case the RESERVE is not done, and
the exposure for VTOC corruption exists if both systems create, extend
or delete datasets from the volume.

Having said that, the exposure exists for DATASET corruption, if the
same dataset, especially a PDS, is updated from multiple systems
concurrently.  It is up to the updatng application whether it issues a
RESERVE when updating a PDS to serialize updates.

--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html





--
Thanks,
Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Ed Finnell
 
In a message dated 9/22/2006 1:04:03 P.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

This  command found the problem? No VVDS?




So all VSAM on the pack is gone? Maybe somebody else can answer, I don't  
know if a REFVTOC will make a new VVDS or not. If I had to fix it I'd dump it 
to  
tape reinit it and reload.
 
Oh, the next sample down I think shows how to do a DIGNOSE for VVDS, but if  
it's not there what's gonna happen? Maybe list VSAM that's gone or  
unconnected.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Bruce Black
The VVDS is unique among VSAM files in that it does not have to be 
cataloged, and it can be cataloged in multiple catalogs (every catalog 
that references datasets on the volume).  So the fact that it is not in 
the master catalog (which is where your LISTCAT would look) is not an 
error.  The VVDS is in the LISTVTOC so it is fine.


Does ISPF still show the error?

--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed?

2006-09-22 Thread R.S.

Mike Szyszka wrote:

Hi all,

ISPF Option 3.4 with just the volser, I receive message in the upper
right
corner of the screen.
Incomplete VTOC list

PF1 shows
Index entry not included because VTOC entry does not exist.

I assume this dasd is trashed and need to be re-inited?
The data sets are still working. I can allocate a new datasets.
One problem is that it is a system pack.


My $0.02
Before you start:
1. Make *physical copy* of the volume, it can be DUMP, FLASHCOPY, PPRC, 
whatever.
2. If you want the dataset on this volume to be available (without long 
outage), then copy the datasets *logically* to another volume.

3. Then two possibilities exist:
a) all the datasets are moved to another volume. In fact you can simply 
re-init this (old) volume and forget.
b) at least one of the datasets was not copied - some error occured. In 
this case you have to play with VTOC, VTOCIX, etc.
4. VERY IMPORTANT STEP. After everything is done, try to investigate 
*why* the problem occured. What is the reason. You will be able to avoid 
it in the future.


HTH

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Mike Szyszka

ISPF 3.4 shows this
SYS1.VVDS.VSYS501  SYS501

This command founds an error
listc ent(/) allDS.VSYS501
SYS501

IDC3012I ENTRY SYS1.VVDS.VSYS501 NOT FOUND+
IDC1566I ** SYS1.VVDS.VSYS501 NOT LISTED
IDC0014I LASTCC=4
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
*
//LIST   EXEC  PGM=IEHLIST,REGION=4M
//DD1  DD  VOL=SER=SYS501,UNIT=3390,DISP=SHR
//SYSPRINT DD  SYSOUT=*
//SYSINDD  *

this job shows
SYS1.VTOCIX.SYS501   2002.122   00.000  SEQUENTIAL
SYS1.VVDS.VSYS5012002.126   00.000  VSAM
**
ISPF 3.4 gives this error
Incomplete VTOC list
**
VSAM files are still there.
SYS3.MIMV461.SMPE.CSI
This file works, did a ptf search
**
This is a shared system dasd between 4 LPARS
shares mostly HSM  TWS
**
Looks like a buildix is next?
Which I will not do until the backup is taken tonight
**
Thanks,
Mike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Ted MacNEIL
Datasets accessed/updated from different systems,.. no GRS protection. So I am 
curious if this is a situation that could clobber a vtoc.

Not if you are doing reserve/release processing.
(Though, it is a performance hit).

When in doubt.
PANIC!!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: VTOC trashed

2006-09-22 Thread Ed Finnell
 
In a message dated 9/22/2006 1:35:28 P.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

Looks  like a buildix is next?




Guess I'd try a BR14 on it first.
 
//S1 EXEC PGM=IEFBR14
//DD1 DD  DSN=TEMP,VOL=SER=vv,UNIT=3390,SPACE=(TRK,(10)),
//   DISP=(NEW,PASS)
 
If the IX is broke, then this should fail and it will turn on the DIRF  
bit(DOS) and disable the IX. Then you can try to convert it back to IX and it  
will 
read the pack and rebuild the OS and IX VTOC.
 
Guess I'm still looking for a why? Something failed, a channel, a pack, a  
job that caused this situation. Lacking that, missing an enqueue or reserve  
name across the MIMplex.  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html