Datacom batch job is failing with Datacom RC 68(001) in a SYSPLEX when it was intended that all jobs be restricted to be run on the same lpar as the MUF and the use of XCF was not desired.

book

Article ID: 33321

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

Issue:

A Datacom batch job is failing with Datacom RC 68(001) and the following messages:

DB00121I - UNAVAILABLE - mufname                     
DB00122I - ACCESS TYPE - LOCAL    TASKS=1            
DB00123I - WAITING FOR MUF AVAILABILITY              
DB00124W - REMAINING DELAY68 TIME -    2 MINUTES  
DB00124W - REMAINING DELAY68 TIME -    1 MINUTES                       
DB00501E - OPEN ERROR - RETURN CODE 68 (001) CXX=                    MUFNAME=mufname 
DB10045E - ABNORMAL TERMINATION DUE TO ERROR(S)                        
IEF450I jobname stepname - ABEND=S000 U0004 REASON=00000000  692          

Environment:

z/OS

Cause:

The submitted job was executing on a different lpar in the SYSPLEX than the Datacom Multi-user (MUF) was running and enabled on.

In this installation, it was intended that all jobs be restricted to be run on the same lpar as the MUF and the use of XCF was not desired. 

Resolution:

Add JCL /*JOBPARM statement with SYSAFF= parameter to ensure the conversion and execution of the job will be done on a specific lpar.  

If submitting the job from a remote lpar, supply the specific execution lpar identity:

   /*JOBPARM SYSAFF=lpar-to-execute

When the job is submitted from the same lpar as the MUF, add SYSAFF=* to force execution on the submit lpar:

   /*JOBPARM SYSAFF=*

Additional Information:

Refer to IBM documentation on JCL /*JOBPARM statement and parameters.

Environment

Release:
Component: DB