When performing a Group Analysis (G) on ICL from 2 different strategies, at the same time, one ends successfully,
the other receives the following message executing CA RC/Migrator for DB2 for z/OS (RCM):
RMA002E BPID IS CURRENTLY BEING PROCESSED
The analysis ends with a RC=0016
With Copy Group Services, you can create and maintain sets of analysis criteria, known as copy group sets, which are used
in Group Migration analysis and Group ICL-to-DDL analysis.
The message guide has:
BPID IS CURRENTLY BEING PROCESSED.
The data set you specified for the analysis output file is currently being
processed (in analysis or by the Batch Processor).
Enter another DSN for the analysis output file.
What is the cause of this message and how can it be resolved?
Release : 20.0
Component : DB ADMIN SUITE FOR DB2 FOR Z/OS
The important point is this is a Group (G) analysis.
When RCM submits a batch job (analysis or execution) it is done via the Batch Processor (RBP). Each RBP job is assigned a
Batch Processor ID (BPID) which is used to track the execution and allow for restarts.
When a job is running the BPID is generated and a system ENQUEUE is done on the BPID to ensure it is the only instance currently running.
The BPID itself is a string, the type of output determines the value.
For Analysis output to a PDS, the BPID is 'PDS.DATASET.NAME(member)'.
OUTPUT DATASET SPECIFICATIONS:
EDIT DATASET ===> N (Yes, No)
DATASET NAME ===> 'USER.PDS.OUTPUT(ALTEMP3)' <<<
VOLUME SERIAL ===> (If not cataloged)
For Analysis output to Managed output the BPID is comprised of;
In the above examples the BPID should be unique.
For Analysis that is using Copy Group output to a PDS( due to a 'G' group analysis being done), an output member name cannot be specified. This is
because a separate analysis output is generated for each copy group set member. These members names are determined during the analysis processing and is not known when the BPID is established.
Because of this, the design uses the output PDS name as the BPID, with no member. When Job A runs using a BPID of 'PDS.DATASET.NAME' and
while Job B is attempting to use the same BPID, the RMA002E occurs in Job B.
The recommendation is to single thread the execution of Group Analysis jobs if they are using the same BPID (output dataset).