PDT0326/U0806 PDTBATCC CROSS SYSTEM FAILURE

book

Article ID: 5415

calendar_today

Updated On:

Products

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

Issue/Introduction

A Detector Batch job abended with the following message:              

PDT0326 CROSS SYSTEM FAILURE ATTEMPTING TO ACCESS DATASTORE=DSNDB0R ON DB2=DB3R and with USER COMPLETION CODE=0806 in module NAME=PDTBATCC.

What is the root cause of the problem and how to prevent it from reocurrybg?

Environment

Release:
Component: PDT

Resolution

The User 806 abend happens when the cross-system communication fails.  The most probable cause of the failure is that the datastore has been archived. As there is a circumvention to this problem, no processing changes will bemade to address this issue, however, an PDT0326 message will be issued prior to the abend to clarify the circumstances of the abend.                       

 

The abend User 806 is due to the attempt to run PDTBATCH on one LPAR, while the DB2 subsystem for the unload is on another. So, Xmanager from LPAR1 calls the Xmanager on LPAR2 to retrieve the data, but the collection datasets, DTR0001,DTR0002,DTR0003 are archived or LPAR2 take longer than the default value of the TIMEOUT parm which is 20 seconds. The restore process takes too long and the cross-system request fails to meet the XMANAGER's TIMEOUT value. When the cross-system request fails, DT#BAT abends with the User 806 and PDT0326 CROSS SYSTEM FAILURE ATTEMPTING TO ACCESS DATASTORE=DSNDB0R ON DB2=DB3R and with USER COMPLETION CODE=0806 in module NAME=PDTBATCC will be issued prior to the abend to clarify the circumstances of the abend.                       

The recommendation is to add the TIMEOUT(150), or higher to all your Xmanagers JCL or increase it significantly if it exists. The maximum value is 600. 

More information on the TIMEOUT Xmanager parameters can be found in the General Facilities Reference Guide.

Another workaround is to run the batch job on the same system as the DB2 sub-system.