Previous Topic: Initiating/Terminating ServicesNext Topic: Command Example

DBEC: Controlling Remote System Resources with Enhanced Commands › Initiating/Terminating Services › Initiating CA Datacom CICS Services

Initiating CA Datacom CICS Services

We recommend that CA Datacom CICS Services be initiated by using CICS PLT startup in each CICS system in which it is used. Use the appropriate DBEC P,STARTup command to initiate CA Datacom CICS Services for a remote system or systems, which can optionally be limited to those active in the CICSplex, if the startup is not automatic (that is to say PLT) or if CA Datacom CICS Services is currently shut down as a result of issuing the SHUTdown command.

When the DBEC command for startup is issued, CA Datacom CICS Services does the following:

  1. Connects all MUFs defined with PLT in the DBCSID macros (or connects the single MUF when there are no DBCSID macros appended to DBCVTPR)
  2. Opens all URTs not defined with AUTO= or DEFER= in DBCVTPR (which then causes connects of any associated MUFs defined with AUTO in the DBCSID macros)
  3. Displays one line of the URT-level panel with the initialization message for the remote system(s) qualified by the SYSID and optional CICSplex options.

You can then enter the command to display the updatable MUF-level or URT-level panel, beginning with the first MUF or URT in the remote system(s), beginning with the local system as qualified by the SYSID option. The display can further be qualified to active CICS regions in a CICSplex or CICSplex system group. When the panel is displayed, you can enter a command from the command line or an action code on any displayed row.

Invoke the following transaction to perform CA Datacom CICS Services startup processing in the specified remote CICS system, a set of CICS systems, or all connected CICS systems including the local system. This command can be issued from the console.

►►─ DBEC ─ PERform,STARTup,SYSid(aaaa) ───────────────────────────────────────►◄
DBEC

(Required) Specify the transaction ID used with Enhanced commands to perform startup or shutdown. Leave a space between the transaction ID and the command.

PERform,

(Required) Command that CA Datacom CICS Services perform the specified action. (PER and P are valid abbreviations.)

STARTup

Action is to initiate CA Datacom CICS Services. (START is a valid abbreviation.)

,SYSID(aaaa)

(Required) For an MRO environment and optionally in a CICSPLEX environment, the value within the parentheses determines whether the inquiry displayed is for a single remote CICS system, a set of CICS systems, or for all CICS systems. Valid values are as follows:

aaaa

Four-character CICS identifier for a single remote CICS system, as defined in the CICS connection table and optionally active in the CICSPLEX.

xxxx

Use a question mark (?) for any position of the four-character value to specify a mask to limit the inquiry display for an update to a set of SYSIDs which can include the local CICS system and any remote systems.

*

All attached CICS systems, beginning with the local system.

(SYS is a valid abbreviation.)

,PLEX(data-value)

Identifies the CICSPLEX context for the function that is issued with this DBEC request. The PLEX value must be the 1- to 8- character name of the CICSPLEX to which this CICS region belongs. If the PLEX option is not specified, the default for the DBEC command is the CICSPLEX specified in the DBCVTPR. The PLEX value must match the CICSPLEX parameter that is specified in the EYUPARM member of the CICS startup. This parameter has no meaning unless the SYSID parameter is also specified in the command. When it is specified in the command with SYSID, it must preceed the SYSID option in the command string.

Note: To use the CICSPLEX-aware feature of DBEC with SYSID, either DBCVTPR should be coded with the CICSPLEX= parameter or the PLEX and SCOPE parameters must be specified in the command. It is important to note that SYSID behaves differently depending on whether DBEC is CICSPLEX-aware. If it is not, then SYSID operates on all MRO connections. If it is, then SYSID operates on only the MRO connections for active CICS regions in the CICSPLEX, that is, for active CICS regions in the CICSPLEX as identified by a CICSRGN CICSPlex SM resource table occurrence. PLEX (a CICSPLEX name) and SCOPE (a CICSPLEX or system group name), can override the DBCVTPR value for the CICSPLEX connections.

,SCOPE(data-value)

Identifies the scope for the function that is issued with this DBEC request. The SCOPE option qualifies the PLEX option or DBCVTPR CICSPLEX parameter. The scope can be:

  • The 1- to -8 character name of the CICSPLEX itself. This is the default as specified in the CICSPLEX parameter of the DBCVTPR.
  • A valid 1- to -8 character name of a CICSPLEX System Group in the CICSPLEX to which this CICS belongs

The SCOPE option should always be used in the command when the PLEX option is used in the command to override the DBCVTPR CICSPLEX parameter or to make the DBEC command CICSPLEX-aware when CICSPLEX is not coded in the DBCVTPR. This parameter has no meaning unless the SYSID parameter is also specified in the command. When it is specified in the command with SYSID, it must preceed the SYSID option in the command string.

Note: SCOPE further qualifies the DBCVTPR CICSPLEX parameter or PLEX option. If either of those two are not specified, SCOPE is ignored in the command.

Important! For previous release compatibility, if neither PLEX or SCOPE are specified in the DBEC command and CICSPLEX= is not specified in the DBCVTPR then the command does not use the CPSM API. DBEC works as before on all MRO connections. The DBCVTPR CICSPLEX parameter could not be specified and still use the DBEC CICSPLEX feature by specifying the PLEX and SCOPE qualifiers in the command.