Discussion:
RECATALOG
(too old to reply)
Mark Pace
2014-03-06 18:32:49 UTC
Permalink
I have a copy of a DASD volume that contains some OMVS (ZFS) filesystems.
I realized that I cannot use ISPF 3.4 to catalog the dataset. I get a VSAM
DATA SET error. Looking in at DFSMS AMS I find a RECATALOG option for a
couple of DEFINEs. But the ZFS files are created via ALLOC and not a
DEFINE CLUSTER. The ALLOC does not appear to have a RECATALOG option.

Is there a way to get these OMVS/ZFS files cataloged?
--
The postings on this site are my own and don't necessarily represent
Mainline's positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Paul Peplinski
2014-03-06 18:43:02 UTC
Permalink
Define cluster name(dataset.name) recatalog nixd) ?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Pommier, Rex
2014-03-06 18:44:47 UTC
Permalink
Mark,

You should be able to use the DEF RECATALOG. With the RECATALOG, IDCAMS will look at the dataset on the DASD volume and build the catalog entries for the dataset.

Rex

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Mark Pace
Sent: Thursday, March 06, 2014 12:32 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: RECATALOG

I have a copy of a DASD volume that contains some OMVS (ZFS) filesystems.
I realized that I cannot use ISPF 3.4 to catalog the dataset. I get a VSAM
DATA SET error. Looking in at DFSMS AMS I find a RECATALOG option for a
couple of DEFINEs. But the ZFS files are created via ALLOC and not a
DEFINE CLUSTER. The ALLOC does not appear to have a RECATALOG option.

Is there a way to get these OMVS/ZFS files cataloged?
--
The postings on this site are my own and don't necessarily represent
Mainline's positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Staller, Allan
2014-03-06 18:49:27 UTC
Permalink
If the clusters are not currently defined, no problem. DEFINE CL (NAME(cluster) VOLUME(volser) LINEAR RECATALOG). (All ZFS's are Linear VSAM).

If they are currently defined, there are 2 solutions to this:

1) Move the HLQ (presumably OMVS) to a UCAT and provide uniqueness at qualifier 2 or "lower level" qualifiers. I use the LLQ.
Remember to modify BPXPRM** to include the files/mountpoints.

2) Alter the files to SYS1. This will allow RECATALOG to function. Only datasets with SYS1 or PAGE as the HLQ can be handled w/DEFINE RECATALOG.
Step one may have to be performed as temporary measure to get from here to there.

The SERVERPAC does create the ZFS's w/ALLOC, however this can also be done in JCL. (sample below).

//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=X
//SYSIN DD *
DEFINE CLUSTER (NAME(clustername ) -
LINEAR CYL(xxxxx 0) SHAREOPTIONS(3,3) -
... -
))
//* Format VSAM Linear Data Set as ZFS Multiple File System Aggregate
//TMP EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate clustername -compat -size 900720 -grow xxxxxx')
//*STEPLIB DD DISP=SHR,DSN=hlq.SIOELMOD <--LOADLIB FOR ZFS if not in LNKLST/LPALST
//SYSPRINT DD SYSOUT=X
//STDOUT DD SYSOUT=X


HTH,

<snip>
I have a copy of a DASD volume that contains some OMVS (ZFS) filesystems.
I realized that I cannot use ISPF 3.4 to catalog the dataset. I get a VSAM DATA SET error. Looking in at DFSMS AMS I find a RECATALOG option for a couple of DEFINEs. But the ZFS files are created via ALLOC and not a DEFINE CLUSTER. The ALLOC does not appear to have a RECATALOG option.

Is there a way to get these OMVS/ZFS files cataloged?
</snip>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Mark Pace
2014-03-06 18:58:16 UTC
Permalink
Thank you all for the information.

DEFINE CL (NAME(cluster) VOLUME(volser) LINEAR RECATALOG

Did the trick.
Post by Staller, Allan
If the clusters are not currently defined, no problem. DEFINE CL
(NAME(cluster) VOLUME(volser) LINEAR RECATALOG). (All ZFS's are Linear
VSAM).
1) Move the HLQ (presumably OMVS) to a UCAT and provide uniqueness at
qualifier 2 or "lower level" qualifiers. I use the LLQ.
Remember to modify BPXPRM** to include the files/mountpoints.
2) Alter the files to SYS1. This will allow RECATALOG to function. Only
datasets with SYS1 or PAGE as the HLQ can be handled w/DEFINE RECATALOG.
Step one may have to be performed as temporary measure to get from here to there.
The SERVERPAC does create the ZFS's w/ALLOC, however this can also be done
in JCL. (sample below).
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=X
//SYSIN DD *
DEFINE CLUSTER (NAME(clustername ) -
LINEAR CYL(xxxxx 0) SHAREOPTIONS(3,3) -
... -
))
//* Format VSAM Linear Data Set as ZFS Multiple File System Aggregate
//TMP EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate clustername -compat -size 900720 -grow xxxxxx')
//*STEPLIB DD DISP=SHR,DSN=hlq.SIOELMOD <--LOADLIB FOR ZFS if not in LNKLST/LPALST
//SYSPRINT DD SYSOUT=X
//STDOUT DD SYSOUT=X
HTH,
<snip>
I have a copy of a DASD volume that contains some OMVS (ZFS) filesystems.
I realized that I cannot use ISPF 3.4 to catalog the dataset. I get a
VSAM DATA SET error. Looking in at DFSMS AMS I find a RECATALOG option for
a couple of DEFINEs. But the ZFS files are created via ALLOC and not a
DEFINE CLUSTER. The ALLOC does not appear to have a RECATALOG option.
Is there a way to get these OMVS/ZFS files cataloged?
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
--
The postings on this site are my own and don't necessarily represent
Mainline's positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Continue reading on narkive:
Loading...