IBM Support

PI18311: CIUUPDB JOB IS NOT EXTRACTING ANY DB2 RECORDS WHEN RUN.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are running the CIUUPDB job to extract the DB2 records into
    a database. This job is getting a message stating "No DB2
    Records Extracted". However, when the CIUUPDB2 is run against
    the same input data, it runs ok and gets a message DB2 Records
    Extracted = 3,571
    
    This is due to a file that gets allocated in STEP040 is not
    deleted in STEP041 because this step is not running. In STEP060
    a file with the same name is allocated. So when STEP070 is
    processing the file this file is empty so no DB2 records can be
    extracted.
    
    Additional Symptom(s) Search Keyword(s): KIXREVDAM
    

Local fix

  • To correct this you need to change DD statement of STEP060
    //OUT DD   DSN=&&DATA4,DISP=(,PASS),SPACE=(CYL,(100,20),RLSE),
    to
    //OUT DD   DSN=&&DATA41,DISP=(,PASS),SPACE=(CYL,(100,20),RLSE),
    
    and to change DD statement of STEP070
    
    //INPUT    DD DSN=&&DATA4,DISP=(OLD,DELETE)
    to
    //INPUT    DD DSN=&&DATA41,DISP=(OLD,DELETE)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS IA Version 3.2 users.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Some of CICS IA sample jobs have the    *
    *                      temporary data sets with identical      *
    *                      names in the various steps. It may      *
    *                      result in malfunction of the sample     *
    *                      jobs.                                   *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    This is due to a temporary file (with DISP=(NEW,PASS)) that is
    created in step(STEP01) is not deleted in another step(STEP02)
    that uses file with the same name (with DISP=(OLD,DELETE))
    because this step is not running due to COND parameter of EXEC
    statement. In the next step(STEP03) system creates a file with
    the same name (with DISP=(NEW,PASS)) again but on another
    volume. So when the next step(STEP4) is processing file with the
    same name (with DISP=(OLD,DELETE)), system allocates for this
    step file created in step(STEP01) instead of step(STEP03).
    

Problem conclusion

  • Jobs CIUAFFLD and CIUUPDB have been changed to provide a unique
    name for each temporary file.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI18311

  • Reported component name

    CICS INTER ANAL

  • Reported component ID

    5655U8600

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-20

  • Closed date

    2014-06-30

  • Last modified date

    2014-08-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI19245 PI22159 PI22160

Modules/Macros

  • CIUAFFLD CIUUPDB
    

Fix information

  • Fixed component name

    CICS INTER ANAL

  • Fixed component ID

    5655U8600

Applicable component levels

  • R320 PSY UI19245

       UP14/07/22 P F407

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

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

Document Information

Modified date:
04 August 2014