Define a request model in the local CICS region.
CREATE REQUESTMODEL >>-CREATE REQUESTMODEL(data-value)--ATTRIBUTES(data-value)------> >--ATTRLEN(data-value)--LOGMESSAGE(cvda)----------------------->< CREATE REQUESTMODEL attribute values: .-TRANSID(CIRP)--. |--+---------------------+--+----------------+------------------> '-DESCRIPTION(char58)-' '-TRANSID(char4)-' .-TYPE(GENERIC)-. >--CORBASERVER(char4)--+---------------+------------------------> +-TYPE(EJB)-----+ '-TYPE(CORBA)---' >--+--------------------------------------------+---------------> '-BEANNAME(char240)--+-INTFACETYPE(BOTH)---+-' +-INTFACETYPE(HOME)---+ '-INTFACETYPE(REMOTE)-' >--+-----------------------------------------+------------------> '-+-----------------+--INTERFACE(char255)-' '-MODULE(char255)-' >--OPERATION(char255)-------------------------------------------|
Conditions: ILLOGIC, INVREQ, LENGERR, NOTAUTH
The CREATE REQUESTMODEL command installs a REQUESTMODEL definition with the attribute specified on the command. It does not use a resource definition stored in the CSD. . If there is already a request model with the name you specify in the local CICS region, the new definition replaces the old one; it not, the new definition is added.
A syncpoint is implicit in CREATE REQUESTMODEL processing, except when an exception condition is detected early in processing the command. Uncommitted changes to recoverable resources made up to that point in the task are committed if the CREATE executes successfully, and rolled back if not. See Creating resource definitions for other general rules governing CREATE commands.