RG008E RC=-12,0006 DB2 SYSTEM ID NAME DB2 IS INVALID

book

Article ID: 49388

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS 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

Description:

Trying to do a request in RC/Query which accesses a remote system results in the message "DB2 SYSTEM ID NAME DB2 IS INVALID".
The LOCAL subsystem is DSN and the remote subsystem is DB2.

Solution:

The Local and remote subsystems are identified on the main product menu prior to accessing the product.

The default will be the following display which identifies the local subsystem that is active.
In this example, D91A is the active subsystem.

DB2 SSID ==> D91A LOCATION ==> LOCAL

To access the remote subsystem DB2 from the local active subsystem, change the LOCATION to the location name for the remote DB2 subsystem.
This LOCATION for the remote system is defined in the Sysibm.Locations table.

In this example, D91A is the active subsystem and DB2 is the location name associated with the remote subsystem.

DB2 SSID ==> D91A LOCATION ==> DB2

Environment

Release:
Component: RCQ