CA Disk 12.5 : PDS Loadlib Explicit Restore error ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
Article ID: 103526
Updated On:
Products
CA Disk Backup and Restore - MVS
CA DISK BACKUP AND RESTORE- ADD-ON OPTIO
CA DISK BACKUP AND RESTORE
Issue/Introduction
CA Disk RESTORE function restores DA, PO, POE, PS, PSE, and ISAM data sets and OS catalogs without preallocation. You can also restore VSAM clusters and ICF catalogs. Usually, you can restore to a device different from the device the data set was backed up or archived from.
By default, CA Disk will not write over a preallocated data set. This can be changed, however, via sysparms PREALLOC and VSPREDEF. The SCRATCH parameter can also be specified on the RESTORE command, which will cause a preallocated data set to be scratched and then reallocated (providing the DSORG of the target data set matches the DSORG of the data set being restored, otherwise the restore will fail).
It can happen that, running an Explicit Restore of a PDS loadlib, the following errors occur :
...
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO1" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO3" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO4" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO5" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
...
one for each member that cannot be restored and the PDS loadlib is not restored correctly.
Is it possible and how to bypass this problem?
By default, CA Disk will not write over a preallocated data set. This can be changed, however, via sysparms PREALLOC and VSPREDEF. The SCRATCH parameter can also be specified on the RESTORE command, which will cause a preallocated data set to be scratched and then reallocated (providing the DSORG of the target data set matches the DSORG of the data set being restored, otherwise the restore will fail).
It can happen that, running an Explicit Restore of a PDS loadlib, the following errors occur :
...
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO1" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO3" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO4" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
ADSDM119 3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER "ADBINFO5" IN PJ1AD.BIBL.LOADAUTH
ADSDM119 3637 USER TTRN NOT ALLOWED IN PDS/E, MEMBER BYPASSED
...
one for each member that cannot be restored and the PDS loadlib is not restored correctly.
Is it possible and how to bypass this problem?
Environment
Z/OS - CA Disk
Resolution
In the CA Disk Message Guide we provide the following explanation for the error code 3637:
3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER (mmm) IN (nnn) USER TTRN NOT ALLOWED
IN PDSE, MEMBER BYPASSED
Reason:
This message has two print lines. When restoring an archived PDS to a preallocated PDSE, CA Disk found that member (mmm) in the archived PDS (nnn) has user pointers in its directory entry. Processing continues but the bypassed member will not be restored.
It appears that the data set involved is a PDS Loadlib but the Explicit Restore is trying to convert it to a PDSE because of the SMS ACS Routines rules defined or the presence of keyword VOLSER in the RESTORE command issued.
Basically if the file to be restored is a non-loadlib PDS data sets, then module ADSDM119 is called and it will convert it to PDSE format if this is the case of the SMS definition, but this cannot be done for PDS loadlibs.
So, in order to bypass the problem, the PO should be preallocated as PDS before the restore takes place and SYSPARM PREALLOCY should be used during the Explicit Restore to prevent CA Disk from allocating the dataset according to the SMS rules defined.
There are 2 possible choice:
1) Do the preallocation of the loadlib as PDS with a newname 'pds.loadlib.new' and then submit the Explicit Restore in the following way:
//RESTORE EXEC RESTORE
//SYSPRINT DD SYSOUT=*
//SYSPARMS DD *
PREALLOCY
//SYSIN DD *
RESTORE DSN=pds.loadlib,
NEWNAME=pds.loadlib.new
//*
or
2) Perform an uncatalog action of the PDS loadlib involved using :
U or DEL (/) NSCR pds.loadlib , , DMSARC
Then allocate again the same pds.loadlib dsname as PDS and submit the Explicit Restore in the following way:
//RESTORE EXEC RESTORE
//SYSPRINT DD SYSOUT=*
//SYSPARMS DD *
PREALLOCY
//SYSIN DD *
RESTORE DSN=pds.loadlib
If, even after this bypass, the problem still occurs, Please open a Case to CA Support.
3637 USER TTRN FOUND IN DIRECTORY ENTRY OF MEMBER (mmm) IN (nnn) USER TTRN NOT ALLOWED
IN PDSE, MEMBER BYPASSED
Reason:
This message has two print lines. When restoring an archived PDS to a preallocated PDSE, CA Disk found that member (mmm) in the archived PDS (nnn) has user pointers in its directory entry. Processing continues but the bypassed member will not be restored.
It appears that the data set involved is a PDS Loadlib but the Explicit Restore is trying to convert it to a PDSE because of the SMS ACS Routines rules defined or the presence of keyword VOLSER in the RESTORE command issued.
Basically if the file to be restored is a non-loadlib PDS data sets, then module ADSDM119 is called and it will convert it to PDSE format if this is the case of the SMS definition, but this cannot be done for PDS loadlibs.
So, in order to bypass the problem, the PO should be preallocated as PDS before the restore takes place and SYSPARM PREALLOCY should be used during the Explicit Restore to prevent CA Disk from allocating the dataset according to the SMS rules defined.
There are 2 possible choice:
1) Do the preallocation of the loadlib as PDS with a newname 'pds.loadlib.new' and then submit the Explicit Restore in the following way:
//RESTORE EXEC RESTORE
//SYSPRINT DD SYSOUT=*
//SYSPARMS DD *
PREALLOCY
//SYSIN DD *
RESTORE DSN=pds.loadlib,
NEWNAME=pds.loadlib.new
//*
or
2) Perform an uncatalog action of the PDS loadlib involved using :
U or DEL (/) NSCR pds.loadlib , , DMSARC
Then allocate again the same pds.loadlib dsname as PDS and submit the Explicit Restore in the following way:
//RESTORE EXEC RESTORE
//SYSPRINT DD SYSOUT=*
//SYSPARMS DD *
PREALLOCY
//SYSIN DD *
RESTORE DSN=pds.loadlib
If, even after this bypass, the problem still occurs, Please open a Case to CA Support.
Feedback
Yes
No
Powered by
