MISMATCHING DSNAME running DLMSCR
Article ID: 74270
Updated On:
Products
CA 1 Flexible Storage
CA 1 Tape Management - Copycat Utility
CA 1 Tape Management - Add-On Options
Issue/Introduction
We are running the DLMSCR utility to synchronize our EMC DLM Library with the CA 1 TMC using the TMECLN01 EARL Report from TMSCLEAN as input.
Sometimes it happens, that volumes are rejected with message:
'VOLUME vvvvvv REQUEST REJECT - MISMATCHING DSNAME'
What is the reason for this and how can this be prevented?
Sometimes it happens, that volumes are rejected with message:
'VOLUME vvvvvv REQUEST REJECT - MISMATCHING DSNAME'
What is the reason for this and how can this be prevented?
Environment
Release:
Component: 1
Component: 1
Resolution
DLMSCR is running without NODSNCHK. In this case DLMSCR compares the DSN from the scratch report with the DSN17 from the tape HDR1 label.
If this does not match then the tape will not be scratched and message 'VOLUME vvvvvv REQUEST REJECT - MISMATCHING DSNAME' is issued.
Note:
For all volumes from a multivolume-multifile chain the 44 character DSN in the TMC volume records is always the data set name from the first file of the chain.
Even if a secondary volume contains secondary files only. The DSN17 field is always correct and matches the HDR1 label.
For example:
We have a multivolume-multifile chain consisting of 2 volumes and 2 files.
TEST.FILE1 is on VOL001 and TEST.FILE2 starts on VOL001 and spans to VOL002.
If we look at the related TMC volume records we have:
VOL001 DSN=TEST.FILE1 DSN17=TEST.FILE1
VOL002 DSN=TEST.FILE1 DSN17=TEST.FILE2 <- the DSN is still from the first file but DSN17 is correct.
In the standard TMECLN01 scratch report we would have TEST.FILE1 for VOL002, which does not match the HDR1 label
resulting in 'VOLUME vvvvvv REQUEST REJECT - MISMATCHING DSNAME' from DLMSCR.
To fix the problem with DLMSCR running with NODSNCHK display the DSN17 field instead of the DSN field in the TMECLN01 report.
Find the following in the TMECLN01 source:
IF P_FILESEQ <= 1
SET SAVE_SCRPOOL = RTN_SCRPOOL
SET SAVE_LABEL = LABEL_TYPE
....
....
and insert SET DSN = DSN17 directly after IF P_FILESEQ <= 1 to replace the DSN with the DSN17 for volume records:
IF P_FILESEQ <= 1
SET DSN = DSN17
SET SAVE_SCRPOOL = RTN_SCRPOOL
SET SAVE_LABEL = LABEL_TYPE
....
....
In case there is a requirement for a TMECLN01 report with the 44 Character DSN for volume records, just add another EARL step using the default version of TMECLN01 to the TMSCLEAN job.
If this does not match then the tape will not be scratched and message 'VOLUME vvvvvv REQUEST REJECT - MISMATCHING DSNAME' is issued.
Note:
For all volumes from a multivolume-multifile chain the 44 character DSN in the TMC volume records is always the data set name from the first file of the chain.
Even if a secondary volume contains secondary files only. The DSN17 field is always correct and matches the HDR1 label.
For example:
We have a multivolume-multifile chain consisting of 2 volumes and 2 files.
TEST.FILE1 is on VOL001 and TEST.FILE2 starts on VOL001 and spans to VOL002.
If we look at the related TMC volume records we have:
VOL001 DSN=TEST.FILE1 DSN17=TEST.FILE1
VOL002 DSN=TEST.FILE1 DSN17=TEST.FILE2 <- the DSN is still from the first file but DSN17 is correct.
In the standard TMECLN01 scratch report we would have TEST.FILE1 for VOL002, which does not match the HDR1 label
resulting in 'VOLUME vvvvvv REQUEST REJECT - MISMATCHING DSNAME' from DLMSCR.
To fix the problem with DLMSCR running with NODSNCHK display the DSN17 field instead of the DSN field in the TMECLN01 report.
Find the following in the TMECLN01 source:
IF P_FILESEQ <= 1
SET SAVE_SCRPOOL = RTN_SCRPOOL
SET SAVE_LABEL = LABEL_TYPE
....
....
and insert SET DSN = DSN17 directly after IF P_FILESEQ <= 1 to replace the DSN with the DSN17 for volume records:
IF P_FILESEQ <= 1
SET DSN = DSN17
SET SAVE_SCRPOOL = RTN_SCRPOOL
SET SAVE_LABEL = LABEL_TYPE
....
....
In case there is a requirement for a TMECLN01 report with the 44 Character DSN for volume records, just add another EARL step using the default version of TMECLN01 to the TMSCLEAN job.
Feedback
Yes
No
Powered by
