DADS Plus CICS DADBAUIT utility program abends with S0C7.

Products

• DADS Plus

Issue/Introduction

When the client runs the  DADS Plus CICS  DADBAUIT utility audit report they abend with a  S0C7  in program DADBAUIT.

Environment

Z/OS 

CICS

Cause

The DADS Plus CICS audit file FCT DADSAUD  is a VSAM ESDS dataset. The DADSAUD file keeps track of DADS Plus activity in the CICS region. After you define the DADS Plus audit file using IDCAMS a PRIMER record is repro'd into the DADSAUD file to initialize it. The JCL to define and initialize a new DADS Plus audit file is shipped as part of the base install and is located in PDS HLQ.SAMPLIB member DADSAUD. The instream initialization record is corrupt and causing the S0C7 abend.

Resolution

If the DADSAUD initialization record on the DADS Plus audit file is corrupt you can receive a S0C7 abend when executing utility DADBAUIT. Please run an IDCAMS print of the 1st record of the audit file in question. The first record should contain the following 8 bytes of hex data at offset X'14' (X'0000000F0000000F').  

When the DADS  Plus audit  file is created the second step initializes the 1st record in the file. If a user was to CUT and PASTE the initialization record that gets REPRO'd to the file the hex values may not be correct. This will cause an S0C7 abend when running the DADBAUIT utility program to produce the report.

Please correct the initialization record and redefine and Initialization the DADSAUD file.

Below is the JCL to print out the first record in the DADSAUD file so you can check the hex values.

//PRINT EXEC PGM=IDCAMS,REGION=1024K

//SYSPRINT DD SYSOUT=*

//INFILE DD DISP=SHR,DSN=YOUR DADS Audit file

//SYSIN DD *

  PRINT INFILE (INFILE) -

        COUNT (1) -

        HEX

/*

//

This is what the header record should look like.

RBA OF RECORD - 0

F1C3C9C3E2C4C5D4D6E7E7E7E7E7E7E7E7E7E7E70000000F0000000FE7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7E7

E7E7E7E7E700004040404040F0F3F5F4F0F0F0F0

IDC0005I NUMBER OF RECORDS PROCESSED WAS 1

Below is the JCL to define and Initialize the DADS  audit file The JCL is located in HLQ.SAMPLIB member  DADSAUD.

//DADSAUD JOB ** YOUR JOB CARD GOES HERE **

//** JOB : DADSAUD **

//** FUNCTION : SAMPLE JCL TO DEFINE THE DADS AUDIT FILE. **

//** NOTES: **

//** 1) ADD A JOBCARD APPROPRIATE FOR YOUR INSTALLATION **

//** 2) C '*DADSAUD*' 'DADS AUDIT FILE DATASET NAME' **

//** 3) C '*VOLSER*' 'VOLSER OF DISK VOLUME THAT **

//** THE BATCH INTERFACE FILE IS TO **

//** RESIDE ON' **

//** 4) SPACE ALLOCATION MAY BE INCREASED DEPENDING ON **

//** SYSTEM ACTIVITY. **

//** **

//DADSAUD EXEC PGM=IDCAMS,REGION=512K

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

  DEFINE CLUSTER (NAME(*DADSAUD*) -

                  VOLUMES(*VOLSER*) -

                  NONINDEXED -

                  RECSZ(0200 4089) -

                  SHR(2 3)) -

         DATA (NAME(*DADSAUD*.DATA) -

                  CISZ(4096) -

                  CYL(1 0))

/*

//* THIS STEP INITIALIZES THE AUDIT FILE WITH A DUMMY RECORD *

//INITAUDT EXEC PGM=IDCAMS,REGION=512K,COND=(0,LT)

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

     REPRO INFILE(SEQ) OUTFILE(DADSAUD)

//SEQ DD *

1CICSDEMOXXXXXXXXXXX........XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX..

//DADSAUD DD DSN=*DADSAUD*,DISP=SHR

/*

//