----- Original Message -----
From: "Edward E. Jaffe" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
Sent: Thursday, July 07, 2005 1:40 PM
Subject: How to Avoid JOBCAT/STEPCAT for DSS VSAM Restore
Restoring a system from DSS logical dump using the following:
RESTORE DS(INCLUDE(**)) INDD(INDD1) OUTDYNAM(xxxxxx) -
BYPASSACS(**) RECATALOG(other.systems.mcat.name) -
NMC NSC IMPORT TOLERATE(ENQFAILURE) REPLACE
The new system's catalog is connected to the driving system's catalog.
RESTORE fails for the VSAM data sets as follows:
ADR485E (ttt)-mmmmm(yy), CATALOG catalog_name IS NOT IN
STEPCAT/JOBCAT/MASTERCAT STRUCTURE. DATA SET dsname WILL NOT BE
PROCESSED
Explanation: The NONSMS cluster named in the message required DFSMSdss to
use IDCAMS or VSAM I/O to perform the COPY or RESTORE. This requires that
both the source and target cluster (allocated by DFSMSdss) be accessible
via the catalog structure.
System Action: Processing continues with the next data set. The return
code is 8.
Operator Response: None.
Application Programmer Response: Add a STEPCAT or JOBCAT JCL statement
specifying the named catalog, or concatenate it to your existing
STEPCAT/JOBCAT JCL statement, and rerun the job. For z/OS V1R5 systems,
the JOBCAT/STEPCAT feature must be enabled with the DFSMS MODIFY CATALOG
command. For additional information about how to enable this feature, see
z/OS Migration.
I need to find an alternative to JOBCAT/STEPCAT for this RESTORE. Any
ideas?
Ed,
Try the MLA workaround we now use for PAGE datasets. Carl did a Bit Bucket
on this a few years ago.
Tom
----------------------------------------------------------------------
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
