CA 7 pre-conversion job AL2DCB10 error 062 - DATA SET DS- DATA SET MBR. MEMBER NAME DOESNT MATCH DIRECTORY MEMBER NAME
search cancel

CA 7 pre-conversion job AL2DCB10 error 062 - DATA SET DS- DATA SET MBR. MEMBER NAME DOESNT MATCH DIRECTORY MEMBER NAME

book

Article ID: 107002

calendar_today

Updated On:

Products

CA 7 Workload Automation

Issue/Introduction

One of the first steps of the CA7 conversion from 11.3 to 12.0 is the execution of job AL2DBC10.

It executes Release 11.3 functions against your Release 11.3 database in preparation for conversion. The first step of this job executes the XREF,TYPE=AL,UPDATE=YES command. The command updates the data set and network using-job references in the database.
The last step of this job executes the Database Verification (DBVR) facility to determine whether any database pointer problems require correction before conversion.

 If the DBVR step does not end with a return code 0, correct the reported errors.
Rerun the step repeatedly until you receive a return code 0.

It can happen that AL2DCB10 ends with a non-zero RC and with the following error message : 

062 - DATA SET DS- DATA SET MBR. MEMBER NAME DOESN'T MATCH DIRECTORY MEMBER NAME - DS-MBR=DS00000000,DS-DIR=DS00nnnnnn

For example 

062 - DATA SET DS- DATA SET MBR. MEMBER NAME DOESNT MATCH DIRECTORY MEMBER NAME - DS-MBR=DS00000000,DS-DIR=DS00300946

How to fix this error and get RC=00 in the DBVR execution?

Environment

Z/OS - CA7 

Resolution

The Database Verification facility is described in the CA Workload Automation SE Release 11.3 Database Maintenance topics.
The DBVR error messages are documented in the CA Workload Automation SE Release 11.3 Messages Guide.
 
In order to fix the error there are some steps to perform. 

1. execute the commands:

DUMP,DSNBR=DS000000 (got the datset name) 
LCTLG,DSN=dataset name (check dsnbr) 
LDSN,DSNBR=DS000000,LIST=ALL 

and get something looking like:

-  18198  115605    LCTLG,DSN=SYSA.TEST.DATASET

 SLID-02 DSN=SYSA.TEST.DATASET                       NOT FOUND.

1LDSN,DSNBR=DS000000,LIST=ALL
 LIST=ALL    DSNBR=DS000000                             DATE 18.198    PAGE 0001

 --------------- DATASET NAME ---------------   DSNBR    PPNBR  POSTTM  DSTYPE
      DSORG   RECFM   LRECL  BLKSZ  DEVTYP  J-USE  J-CRT  £RQ   MDATE/TIME MTYPE

 SYSA.TEST.DATASET ......................  00300946  *NONE*  JTERM PERM
         ,GDG VB      02054  00000  DASD    00000  00000  0000  10041/1456  LOAD

       
2. execute the command:

DUMP,DSNBR=DS00300946 (got the datset name) 
LCTLG,DSN=dataset name (check dsnbr) 
LDSN,DSNBR=DS00300946,LIST=ALL 

and get something looking like:

-  18198  115605    DUMP,DSNBR=DS00300946

 SLIM-02 DSNBR=DS00300946 NOT FOUND.
-  18198  115605    LDSN,DSNBR=DS00300946,LIST=ALL

 SLIB-02 DSNBR=DS00300946 NOT FOUND.

3. execute the following command: 

DMP,DSNBR=00000000,PREFIX=DS,TYPE=DEL 

if the result looks like:

DMP,DSNBR=00000000,PREFIX=DS,TYPE=DEL 
CA-7 DUMP PAGE NO. 001 

00000000 C4E20000 00000000 0000001F 001C892C *DS..............* 
001C876E 001C876D 001C876C 001C876B *................* 

SCO0-00 REQUEST COMPLETED AT 12:35:01 ON 18.198 

but running again the AL2DCB10 job, the DBVR step gets the same 062 error , then there is a final step to do as follows:

4. execute the command :

DMP,PREFIX=DS,DSNBR=0,TYPE=MBR,OFFSET=8 

if the result looks like: 

 -  18198  115605    DMP,PREFIX=DS,DSNBR=0,TYPE=MBR,OFFSET=8
1                              CA-7 DUMP

 0000081C   00049792 00000000 10041F14 56000100    00000806 E5C24040 40000000 00000000   *....................VB..........*

then the error is fixed issuing the following command:

ZAP,PREFIX=DS,DSNBR=0,TYPE=MBR,OFFSET=8,ZDATA=00000000