IBM Support

DSNU345I DSNURBXD when running CIUUDBP STEP041 LOAD CIU_CICS_DATA

Question & Answer


Question

Why am I receiving a few hundred thousand DSNU345I messages for CSECT DSNURBXD when running jobstep STEP041 of the CICS Interdependency Analyzer for z/OS (CICS IA) V5.2 supplied CIUUDBP job to load a new set of DB2 records from the dependency files?

This is the complete message I receive:

  DSNU345I    ddd hh:mm:ss:mm DSNURBXD - UNIQUE INDEX KEY DUPLICATES KEY FROM INPUT RECORD
                        'yyy' LOADED AT RID X'000000nnnn',
                             INDEX = schema.XICICS11,
                             TABLE = schema.CIU_CICS_DATA,
                             RECNO = xxx,
                             RID   = X'000000nnnn'

I looked at the XICICS11 index and cannot see why any duplicate keys would get flagged.

Answer

The most common reason for thousands of of DSNU345I messages from CICS IA job CIUUDBP STEP041 at DB2 LOAD of the CIU_CICS_DATA table is due to CICS IA program CIUU040 running in STEP020 which internally translates any unprintable hex characters in the OBJECT column for the RESOURCE name to x'4B' period by default. If dependency collection does not have a CIUPFXTB resource prefix table defined with a mask for CICS temporary storage queue names where the binary CICS taskid is part of the TSQname, then at load time, CIUU040 translates the hex CICS taskid portion of the TSQname resource OBJECT column to x'4B'. At load time DB2 will correctly detect these as duplicate keys on the index as the OBJECT column has been translated to x'4B' for the binary taskid of each input record.

Creating a CIUPFXTB resource prefix table to identify the TSQname mask field and where the binary CICS taskid offset is within the TSQname can eliminate the collection of these as unique records and create a single collection record with "+" plus sign values where the binary CICS taskid would be. When CIUUDPB runs later to load the CIU_CICS_DATA table, it will only need to load one record representing the same TSQ command and program for that TSQ. A similar problem can occur for ENQ resource names that contain unprintable hex characters.

You can run the CIUJCLDL sample job to cleanup the dependency files until the CIUPFXTB resource prefix table can be deployed.

Specify the TSQname prefix as SYSIN to the //PRFGRPS DD * and this CIUDEL utility will delete those records matching the TSQname preifx.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPPUS","label":"CICS Interdependency Analyzer for z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICSIA CICS IA

Document Information

Modified date:
08 October 2015

UID

dwa1231653