Starting the connection manager

Stabilized feature: CICS® support for Open Network Computing Remote Procedure Call (ONC RPC) is stabilized. Consider exposing and orchestrating applications as API services by using z/OS Connect Enterprise Edition or CICS web services, or by writing web applications in Java or Node.js. See also Stabilization notices and discontinued functions.

You can start the connection manager in various ways and the effect of starting the connection manager depends on several factors.

Methods to start the connection manager

You can start the connection manager:
  • From a terminal that supports BMS maps. You can work with the connection manager panels described in this section.
  • From a CICS console.
  • Using an EXEC CICS START command.
  • From a sequential terminal.

Effect of starting the connection manager

The effect of starting the connection manager depends on:
  • Whether CICS ONC RPC is enabled or disabled
  • Whether you start the connection manager from a terminal that permits the use of BMS
  • Whether you enter additional data with the transaction name
  • Whether the Automatic Enable option in the CICS ONC RPC definition record is set to YES
When CICS ONC RPC is disabled, the effect of entering the transaction name (and optional additional data) on a terminal that supports BMS is as follows:
CRPC
  • If Automatic Enable is YES, automatic enable processing occurs.
  • If Automatic Enable is NO, a BMS panel (DFHRP01) is shown.
  • If there is no CICS ONC RPC definition record yet, a BMS panel (DFHRP01) is shown.
CRPC E A(N)
CRPC E A(Y)
  • Automatic enable processing occurs. If there is no CICS ONC RPC definition record, one is created using default values for the options, but no 4-tuples are registered.

If you start the connection manager in a way that does not allow panels to be shown (EXEC CICS START, or non-BMS terminal, for example) and the action is to show a panel, error message DFHRP1505 is produced.

When CICS ONC RPC is enabled, the effect of entering the transaction name (and optional additional data) is as follows:
  • CRPC displays panel DFHRP04, or produces error message DFHRP1505 if panels cannot be shown.
  • CRPC D(N) causes normal disable processing.
  • CRPC D(I) causes immediate disable processing.

The forms CRPC E A(N), CRPC E A(Y), CRPC D(N), and CRPC D(I) are called fast-path commands.

Before you begin

z/OS® Communications Server should be started before you try to enable CICS ONC RPC with the connection manager; otherwise ,you cannot register 4-tuples, and you have to re-enable CICS ONC RPC after starting z/OS Communications Server.

Starting the connection manager when CICS ONC RPC is disabled

If CICS ONC RPC is disabled, panel DFHRP01 is shown.

Figure 1. Panel DFHRP01
CRPC                    CICS ONC RPC for MVS/ESA                       DFHRP01
 
Select one of the following. Then press Enter.
 
_  1. Enable CICS ONC RPC
   2. View or modify the CICS ONC RPC data set
 
 
 
 
 
 
 
 
 
 
 
 
 
Current Status: Disabled
 
 
                                                  SYSID= CI41  APPLID= IYK1ZFL1
PF1=Help   PF3=Exit   PF9=Messages   PF12=Return
Select an option, and then press Enter.
Option
Description
1
Enabling CICS ONC RPC
2
Updating the CICS ONC RPC data set

Starting the connection manager when CICS ONC RPC is enabled

If CICS ONC RPC is enabled, panel DFHRP04 is shown.

Figure 2. Panel DFHRP04
CRPC                    CICS ONC RPC for MVS/ESA                       DFHRP04
 
Select one of the following. Then press Enter.
 
_  1. Disable CICS ONC RPC
   2. View or modify the CICS ONC RPC data set
   3. View or modify CICS ONC RPC status
 
 
 
 
 
 
 
 
 
 
 
 
Current Status: Enabled
 
 
                                                  SYSID= CI41  APPLID= IYK1ZFL1
PF1=Help   PF3=Exit   PF9=Messages
Select an option, and then press Enter.
Option
Description
1
Disabling CICS ONC RPC
2
Updating the CICS ONC RPC data set
3
Updating CICS ONC RPC status