CICS® ONC RPC provides two RDO groups defining CICS resources used by CICS ONC RPC: DFHRP and DFHRPF.
The following CICS ONC RPC transactions are defined in the locked group DFHRP:
These definitions cannot be changed.
You may want to use other alias transaction names for various reasons:
If you do, you must also define these to CICS, copying the definition from CRPA, and making amendments as necessary. The CRPA definition is as follows:
DEFINE TRANSACTION(CRPA) GROUP(DFHRP)
PROGRAM(DFHRPAS) TWASIZE(0)
PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER)
RUNAWAY(SYSTEM) SHUTDOWN(ENABLED)
PRIORITY(1) TRANCLASS(DFHTCL00)
DTIMOUT(NO) INDOUBT(BACKOUT)
SPURGE(YES) TPURGE(NO)
RESSEC(NO) CMDSEC(NO)
If you want a CICS program to run under an alias with a name other than CRPA, you can enter this in the connection manager when defining the attributes of the 4-tuple associated with the CICS program, as described in Defining the attributes of a 4-tuple. The name of the alias can also be changed by the Decode function, as described in Changing the alias and CICS program.
You might wish to define new alias transactions with CMDSEC(YES) or RESSEC(YES) in order to enforce security checking on the programs run under the alias transaction, including the CICS program that services the client request. The effect of these options is described in Security in CICS and its effect on CICS ONC RPC operations. None of the IBM-supplied programs used by the alias use any of system programmer interface (SPI) commands, so CMDSEC need not be changed. However, if you wish to oversee the use of SPI commands by the CICS program, resource checker, or Encode function of the converter, CMDSEC(YES) is required.
All the CICS ONC RPC programs are defined in the locked group DFHRP.
You need to make definitions for:
User-written XDR routines should be defined with LANGUAGE(C). Converters and CICS programs should be defined with an appropriate LANGUAGE.
Program definitions for CICS programs must include CEDF(YES) if EDF is required for debugging. If you wish to use EDF, you must enter a terminal ID in the connection manager when defining the attributes of the 4-tuple associated with the CICS program, as described in Defining the attributes of a 4-tuple.
CICS operates with storage protection only if the SIT parameter STGPROT is set to YES, and the system has the required hardware and software.
Converters and the resource checker should not be regarded as application programs when defining storage. You are recommended to define them as EXECKEY(CICS). This allows them to modify CICS-key storage.
When the Decode and Encode functions allocate storage to hold the converted data, that storage should be allocated as CICS-key.
User-written XDR routines must be defined as EXECKEY(CICS).
CICS programs should be defined as EXECKEY(USER), unless there is some reason for defining them as CICS-key in your CICS system. Defining programs as EXECKEY(USER) prevents them from overwriting CICS.
If you specify EXECKEY(USER) for the CICS program, ensure that TASKDATAKEY(USER) is specified for the alias. USER is the default TASKDATAKEY setting in the alias definition in the supplied group DFHRP.
If you have CICS programs that need to be specified with EXECKEY(CICS), you are advised to specify TASKDATAKEY(CICS) for the alias that will execute them.
You should specify RELOAD(YES) for any user-written XDR routines to prevent errors in CICS ONC RPC disable processing.
If a CICS program that is to service a remote procedure call runs in a different CICS system from CICS ONC RPC, a program definition is required on both the local system and the remote system. The program resides on the remote system, so its definition there is straightforward. The program definition on the local system:
If the remote transaction ID is specified, you must provide a matching transaction definition in the remote CICS system. This definition must specify the appropriate mirror program for the remote system (DFHMIRS for CICS for MVS/ESA and CICS Transaction Server for OS/390® systems).
If a CICS program is running on a CICS platform other than CICS for MVS/ESA or CICS Transaction Server for OS/390 similar considerations apply, but you should refer to the DPL details for that platform.
Mapset definitions are supplied in the group DFHRP for the connection manager mapsets. The definitions cannot be changed.
You must supply DCT definitions for the CICS ONC RPC message transient data queue. The following sample is supplied with CICS ONC RPC as member DFHRPDCT of the SDFHSAMP target library:
DFHDCT TYPE=SDSCI,
BLKSIZE=137,
RECSIZE=133,
DSCNAME=CRPO,
RECFORM=VARUNB,
BUFNO=1,
TYPEFLE=OUTPUT
DFHDCT TYPE=EXTRA,
DESTID=CRPO,
DSCNAME=CRPO
If you define the destination in the manner of the sample, you must also add a suitable DD statement for the extrapartition queue in the CICS JCL, for instance:
//CRPO DD SYSOUT=A
The destination could also be made intrapartition or indirect.
The XLT system initialization parameter and its associated transaction list should allow the connection manager, CRPC, to be started during normal CICS shutdown. If CICS ONC RPC is delaying shutdown, the connection manager can be used to force an immediate disable of CICS ONC RPC.