After submission of a batch processor job this error is seen.
PTIDB2-CAF: DB2 SYSTEM ID NAME ssid IS INVALID
BPA0010E: CONNECTION TO DB2 SSID ssid HAS FAILED USING PLAN: RBPAPnnn.
RETCODE = 16
DB2 for Z/OS
R20 Release
The job tried to connect to a remote target subsystem while connected to a local subsystem but the remote target subsystem can't be connected.
The job must be run so that the part of the processing that needs to connect to the target subsystem is run on that remote subsystem not on the local subsystem.
When migrating between remote subsystems the UNLOAD MODE Batch Processor Interface screen flag should be used. When processing the unloads it should be set to 'U' (Only the section of input containing Unload statements is to be executed).
Then the user should connect over to the target subsystem and run the rest of the processing by specifying UNLOAD MODE set to 'N' (The section of input containing Unload statements is to be omitted.)
The use of UNLOAD MODE set to 'N' generates a statement like this: .RESTART SYSTEM(SQLDDL,SQLSTATS)
The use of UNLOAD MODE set to 'U' generates a statement like this: .RESTART SYSTEM(UNLOADS)
The .RESTART SYSTEM parm is also generated when a system name is entered into the RESTART ===> field.
If UNLOADS is entered, RESTART ===> UNLOADS, the same .RESTART SYSTEM(UNLOADS) statement is generated.
If SQLDDL is entered, RESTART ===> SQLDDL, the .RESTART SYSTEM(SQLDDL) statement is generated.
For information about the use of the .RESTART SYSTEM , see : Restart a failed BP job which uses .SYSTEM statements, process only a subset of .SYSTEM statements.
One problem with this approach is that the batch processor dataset is stored on disk packs that are not on shared dasd with the remote subsystem. The unload datasets also must be on shared disk packs.
The Following options are valid for UNLOAD MODE:
"A" All Batch Processor input is to be executed.
"N" The section of input containing Unload statements is to be
omitted.
"U" Only the section of input containing Unload statements is to
be executed.
This option is intended for use with Batch Processor Streams which were created via RC/Migrator or RC/Update.