To associate the incoming GIOP request with a CICS® transaction ID, you need to provide and install a REQUESTMODEL resource definition. You should supply REQUESTMODEL resources for all possible requests that should run under a non-default transaction ID. At run-time, when CICS receives a GIOP request it compares fields in the request with predefined values in the REQUESTMODELs, to find the REQUESTMODEL that most exactly matches the request. The selected REQUESTMODEL provides the TRANSID name that is used to process the request. If no match is found, a default TRANSID (CIRP) is used. REQUESTMODELs can be used with enterprise beans, stateless CORBA objects, or both. They specify:
DEFINE TRANSACTION(CIRP) GROUP(DFHIIOP)
PROGRAM(DFJIIRP) TWASIZE(0)
PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER)
RUNAWAY(SYSTEM) SHUTDOWN(ENABLED)
PRIORITY(1) TRANCLASS(DFHTCL00)
DTIMOUT(NO) TPURGE(NO)
SPURGE(YES) ISOLATE(YES)
RESSEC(YES) CMDSEC(YES)
RESTART(NO)
DESCRIPTION(Default CICS IIOP Request Processor transaction)
DEFINE PROGRAM(DFJIIRP) GROUP(DFHIIOP)
DESCRIPTION(CICS IIOP Request Processor)
JVM(YES)
JVMCLASS(com.ibm.cics.iiop.RequestProcessor)
JVMPROFILE(DFHJVMCD)
LANGUAGE(LE370) RELOAD(NO) EXECKEY(USER)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(NO) DATALOCATION(ANY)
DYNAMIC(NO)
See Dynamic routing if the request is to be routed to an AOR.