Batch Processor : DOES THE RBP BPID NEED TO BE UNIQUE ACROSS A SYSPLEX?

Products

• Database Management for DB2 for z/OS - Administration Suite

Issue/Introduction

The Batch Processor ID, or BPID for short, is used by the sync point and restart system to track the execution status and logging of sync records.

 

Environment

Release: R20
Component: RBP

Resolution

The BPID should be unique across the SYSPLEX. If a job is already running with a particular BPID and a second job then attempts to start with the same BPID (on any LPAR in the SYSPLEX), then that second job will receive the BPA0034E message e.g.:

BPA0034E: THIS BPID IS CURRENTLY BEING USED BY authid

To determine where, in the sysplex, that other job is running, issue the following MVS GRS command:

D GRS,RES=(RBP0200,*)

(Note: See the MVS System Commands manual, pertaining to your particular release of z/OS, for further information on the command).

Issuing the command should result in a display in the MVS System Log similar to the following:

    D GRS,RES=(RBP0200,*)  
   ISG343I 05.38.19 GRS STATUS 552 
    S=SYSTEMS RBP0200 authid.DB2.DDL-SQL T 
    SYSNAME    JOBNAME    ASID   TCBADDR  EXC/SHR   STATUS
     lpar1       authid 03B5   007CBE88 EXCLUSIVE OWN 

Indicating that Jobname authid, is running on system lpar1 in the sysplex and is holding an Exclusive enqueue on the resource with Major Name RBP0200 and Minor Name authid.DB2.DDL-SQL (which is the BPID in this case).

Additional Information

DISPLAY GRS command