Why PDTBATCC can get RC=12 without any messages?

book

Article ID: 51071

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

Description:

Running PDTBATCC to unload datastores into a sequential flat file, the job gets RC=12 without explanation of what has happened.

adding MSGLEVEL=(1,1), doesn't shows any more info.

XMANAGER log doesn't show any message.

Datastore is accessible through the Detector menus and it's possible to view all kind of data except for dynamic SQL in some intervals.

Solution:

  • The PDTDLOAD and PDTBATCH JCL shipped in highlvl.SRCLIB do not have a REGION specification on the step EXEC card.

    The suggestion is to add REGION=0M in the EXEC card.

  • The job didn't specify dd cards for sort work datasets.

    In this situation, the sort installation defaults are used which controls dynamic allocation of the sort work datasets.

    It appears that in certain intervals that a large amount of Exception data is collected that is exceeding available sort work space based on the sort installation defaults.

    The suggestion is to specify sort work datasets in the JCL, for example:
    //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(100,300))//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(100,300))//SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(100,300))//SORTWK04 DD UNIT=SYSDA,SPACE=(CYL,(100,300))

Environment

Release:
Component: PDT