search cancel

Job AXPOR01 gets RC=16 RC 74 (081) DB01401E - MVS DYNAMIC ALLOCATION ERROR

book

Article ID: 258043

calendar_today

Updated On:

Products

Datacom/AD Datacom CA-11

Issue/Introduction

Upgrading Datacom/AD from 12.0 to 15.1 for CA 11. 

Job AXPOR01 gets a RC=16 with dynamic allocation errors.  

Error message from AXPOR01:  DB00501E - OPEN ERROR - RETURN CODE 74 (081) CXX=AD12CXX  (IXX00002) 

Error message from Datacom MUF:  DB01401E - MVS DYNAMIC ALLOCATION ERROR, DDNAME=IXX002  , , R15=4, ERROR=1708, INFO=0002

 

Environment

Release : 15.1

Cause

The DB01401E MVS DYNAMIC ALLOCATION ERROR ERROR=1708 means the dataset is not catalogued. See article CA Datacom failure RC 74 (081) DB01401E
The job is looking for the old 12.0 dataset not the new 15.0 version.
It will use the dataset name in the 12.0 CXX.
To find what dataset name it is looking for run a DBUTLTY CXX report against your 12.0 MUF, use this JCL:

//REPORT    EXEC PGM=DBUTLTY,REGION=4M
//STEPLIB  DD DISP=SHR,DSN=datacom.R12.CUSLIB
//         DD DISP=SHR,DSN=datacom.R12.CAAXLOAD
//CXX      DD DISP=SHR,DSN=datacom.R12.CXX  
//SYSPRINT DD SYSOUT=*
//SNAPER   DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN  DD  *        
REPORT AREA=CXX,DBID=002
/*

In the report do a find for "IXX002", you will see "DATA SET NAME" on the same line.

Resolution

If only the IXX002 dataset has been deleted you can allocate a new one run an INIT and RETIX using the JCL below then rerun AXPOR01.

//RETIX    EXEC PGM=DBUTLTY,REGION=4M
//STEPLIB  DD DISP=SHR,DSN=datacom.R12.CUSLIB
//         DD DISP=SHR,DSN=datacom.R12.CAAXLOAD
//CXX      DD DISP=SHR,DSN=datacom.R12.CXX  
//SYSPRINT DD SYSOUT=*
//SNAPER   DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//IXX003   DD DSN=datacom.R12.IXX002,
//         UNIT=3390,SPACE=(CYL,(20,2),VOL=SER=nnnnnn,
//         DISP=(NEW,CATLG,DELETE)   
//SYSIN  DD  *                      
 ACCESS  DBID=002,STATUS=OFF,USERS=FAIL 
 COMM    DBID=002,OPTION=CLOSE
 INIT AREA=IXX,DBID=002                      
 RETIX DBID=002,SORT=1000000                 
 ACCESS STATUS=WRITE,DBID=002              
/*

If a lot of the other 12.0 datasets also no longer exist then upgrade job AXPOR01 cannot be run .

There are two options:

  1. Start on the version 15.1 MUF with an empty CA 11 database. To do this run the CA 11 jobs AL7AD1 and AL7AD2 against the new version 15.1 MUF to allocate a new CA 11 database.

  2. If you want to keep the existing CA 11 data on the new 15.1 MUF do the following:
    • Run the CA 11 jobs AL7AD1 and AL7AD2 against your version 15.1 MUF to allocate a new database.
    • Run a BACKUP against your old 12.0 MUF, use CA 11 SAMPJCL member AL7BKUP.
    • Run a LOAD  against the new 15.1 MUF to reload the data, use CA 11 SAMPJCL member AL7LD2.