Client Interaction

To allow a client to interact with a CA GTS product, a minimum of one CA GTS address space must be active on the same LPAR as the requestor. In general, no more than one CA GTS system is required, but multiple CA GTS address spaces can be started if situations require it.

Every CA GTS in a CA GTS-Plex (that is, a network of interconnected CA GTS systems) must have a unique identifier. This identifier serves internal purposes, but also allows the routing of requests to uniquely identifiable targets. Take care to provide the correct definition to avoid unintended interactions between multiple CA GTS address spaces on the same system. This includes separating XCF and TCP/IP information as well as the usage of separate CA GTS identifiers.

The ID of a CA GTS server can be specified either on the OS PARM on the EXEC PGM= statement of the JCL using the ID() keyword or the GSINITxx member of the data set allocated under the CAGSPARM DD statement.

If during startup of a CA GTS, it is determined that a CA GTS is trying to join the network that has the name of a CA GTS already active in the network, an error message is produced. The CA GTS in question must be stopped, and the ID changed and restarted (or otherwise the cause of the problem investigated).

The requirement for a 'local' CA GTS exists even if the code to be invoked should execute on a 'remote system' (an LPAR other than the one that the client issues the request).