Transaction definitions for additional alias transactions
You may want to use other alias transaction names for various reasons.
- Auditing purposes
- Resource and command checking
- Allocating initiation priorities
- Allocating database plan selection
- Assigning different runaway values for different CICS programs
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.
Changing the CMDSEC and RESSEC values
You might want to define new alias transactions with CMDSEC(YES) or RESSEC(YES) to enforce security checking on the programs run under the alias transaction, including the CICS program that services the client request.
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 want to oversee the use of SPI commands by the CICS program, resource checker, or Encode function of the converter, CMDSEC(YES) is required.