Lizette:
I will just say it is a tidy thing to do, so it doesn't look like the
sysprog is not doing his duty.
Ed
On Jul 2, 2014, at 8:03 PM, Lizette Koehler wrote:
Willie,
What you did was recatalog a VVDS which probably was not needed.
If you did not accidently delete the VVDS in the CATALOG, you do
not need to
do this in my opinion.
VVDS is a VSAM ESDS data set and can be considered an extension of
the VTOC.
There is one VVDS on every volume that contains VSAM data set or any
SMS-managed data set. The catalog information that requires the most
frequent updates is physically in the VVDS on the same volume as
the data
set, allowing faster access. For VSAM data sets, it contains the
data set
characteristics, extent information, and the volume-related
information.
Every catalog consists of one BCS and one or more VVDSs. A BCS does
not
“own” a VVDS: More than one BCS can have entries for a single VVDS.
Every
VVDS that is connected to a BCS has an entry in the BCS.
A VVDS is created automatically the first time a VSAM data set or a
non-VSAM
SMS-managed data set is allocated in that volume. You do not need to
allocate a VVDS unless you want to define a VVDS with a space
allocation
different from the default. In such a case, you must allocate the VVDS
first.
When DIAGNOSE identifies the problem that might indicate an incomplete
catalog entry, perform these fixes:
If it is an entry in a BCS, delete the catalog record and attempt to
recatalog it:
– DELETE entry_name NOSCRATCH
– DEFINE entry_name RECATALOG
If the truename exists without the associated cluster records:
– DELETE entry_name TRUENAME
If it is an entry in a VVDS, delete the record type:
– DELETE entry_name VVR
– DELETE entry_name NVR
It might be possible to recatalog the data set:
– DEFINE CLUSTER(NAME(cluster_name) … RECATALOG)
This is all talking about data sets that are not the VVDS.
DIAGNOSE
The DIAGNOSE command can be used to scan a basic catalog structure
(BCS) or
a VSAM volume data set (VVDS) to validate the data structures and
detect
structure errors.
So was it necessary to recatalog the VVDS? Probably not. The VSAM
Demystified Redbook is very helpful.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-
m...@listserv.ua.edu] On
Behalf Of willie bunter
Sent: Wednesday, July 02, 2014 10:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IDCAMS QUESTION - RECATALOG
Lizette,
This is what I found in our internal archives regarding the
RECATALOG parm
:
The RECATALOG parameter is required for VSAM and SMS managed
datasets. It
basically tells IDCAMS to read information out of the VVDS to
reconstruct
the
catalog entry correctly
--------------------------------------------
On Wed, 7/2/14, willie bunter <0000001409bd2345-dmarc-
requ...@listserv.ua.edu> wrote:
Subject: Re: IDCAMS QUESTION - RECATALOG
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, July 2, 2014, 7:30 AM
I remember reading it
somewhere. I will dig around and post it.
--------------------------------------------
On Wed, 7/2/14, Lizette Koehler <stars...@mindspring.com>
wrote:
Subject: Re: IDCAMS
QUESTION - RECATALOG
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Wednesday, July 2, 2014, 6:36 AM
So why use the
RECATALOG?
The message
says
Run DIAGNOSE
ICFCATALOG for
the extraneous catalog name. Determine
whether
data sets are missing from the
volume. If no data sets are missing, use the
DELETE command with the NOSCRATCH
option to
remove the VVDS entry from the
extraneous
catalog.
If any data sets
are missing from the volume, recover the data sets in
their
entirety.
Multivolume data sets
require that all
volumes are recovered
together, not just
the affected volume.
Occasionally, a VVDS might
have a record
for a data set which no longer
exists, or
for which there is no corresponding
BCS
entry. The VVDS contains
VVRs for all
VSAM data sets and objects, and on SMS-managed volumes,
NVRs
for non-VSAM
data sets.
Lizette
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
