Request model definitions - RQMDEF
The Request model definition (RQMDEF) views display information about the characteristics of request model definitions, which associate inbound IIOP requests with a set of execution characteristics, such as security or priority, and with monitoring and accounting data.
Request model definitions cannot be installed into CICS regions running CICS TS for z/OS, Version 5.1 or higher.
Supplied views
To access from the main menu, click:
| View | Notes |
|---|---|
| Request model definitions EYUSTARTRQMDEF.ADDTOGRP |
Add a RQMDEF to a resource group. |
| Request model definitions EYUSTARTRQMDEF.CREATE |
Create a request model definition and add it to the data repository. |
| Request model definitions EYUSTARTRQMDEF.DETAILED |
Detailed information about a selected request model definition. |
| Request model definitions EYUSTARTRQMDEF.INSTALL |
Install a request model definition in an active system. |
| Request model definitions EYUSTARTRQMDEF.REMOVE |
Remove a request model definition from the data repository. |
| Request model definitions EYUSTARTRQMDEF.TABULAR |
Tabular information about all request model definitions for the current context. |
Actions
| Action | Description |
|---|---|
| ADDTOGRP | Add a RQMDEF to a resource group. |
| CREATE | Create a request model definition and add it to the data repository. |
| CSDCOPY | Copy a CICS CSD resource definition. |
| CSDINSTALL | Install a CICS CSD resource definition into an active system. |
| INSTALL | Install a request model definition in an active system. |
| REMOVE | Remove a request model definition from the data repository. |
| UPDATE | Update a request model definition in the data repository. |
Fields
| Field | Attribute name | Description |
|---|---|---|
| Enterprise bean | BEANNAME | A bean name, of up to 240 characters, matching the name of the enterprise bean in the XML deployment descriptor.
The acceptable characters are A-Z a-z 0-9 . - _ and accented alphabetic characters. If you specify a generic value for BEANNAME, then you must specify INTFACETYPE as BOTH and OPERATION as *. If you specify RTYPE as generic, you must specify BEANNAME as *. For CORBA REQUESTMODELs - that is, if RTYPE is CORBA, this field should be blank. |
| Last modification agent | CHANGEAGENT | The change agent identifier that made the last modification.
|
| Last modification agent release | CHANGEAGREL | The CICS release level of the agent that made the last modification. |
| Last modification time | CHANGETIME | The local date and time when the definition was last changed. |
| Last modification user ID | CHANGEUSRID | The user ID that made the last modification. |
| CorbaServer | CORBASERVER | The name of the destination CORBASERVER for this REQUESTMODEL. The name can be up to 4 characters in length. The acceptable characters are A-Z a-z 0-9. You can also use an asterisk as the last (or only) character to specify a generic name. If a generic CORBASERVER is specified, BEANNAME, the CORBA attributes (MODULE and INTERFACE), and the COMMON attributes (OPERATION) must all be an asterisk (*); INTFACETYPE must be BOTH. For any release prior to CICS TS Version 6 Release 2, if any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) are present in the request model definition, CORBASERVER must be blank, otherwise CORBASERVER is a required attribute. |
| Time created | CREATETIME | The local date and time when the definition was created. |
| CSD group | CSDGROUP | The name of the CSD group for this CICS resource definition. This field is ignored for BAS definitions. |
| Version | DEFVER | The version number of the BAS resource definition, from 1 to 15. This field is ignored for CICS CSD resource definitions. |
| Description code page | DESCCODEPAGE | The code page of the description field. This field is ignored for CICS CSD resource definitions. |
| Description | DESCRIPTION | A description of the request model definition. |
| Interface name | INTERFACE | A name, of up to 255 characters, matching the IDL interface name. The acceptable characters are A-Z a-z 0-9 _
: and accented alphabetic characters. Case is significant and should match the original Java or IDL source. To comply, however, with CORBA, installation of REQUESTMODELS that specify INTERFACE with values differing only in case from previously installed definitions, will be rejected. If a generic INTERFACE is specified, the common attributes (OPERATION) must be an asterisk (*). For EJB REQUESTMODELs - that is, if RTYPE is EJB - this field should be blank. If you specify RTYPE as GENERIC, you must specify INTERFACE(*). If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) are present in the request model definition, INTERFACE must be blank. |
| Java interface type | INTFACETYPE | The Java interface type for this REQUESTMODEL:
|
| Module name | MODULE | A name, of up to 255 characters, matching the IDL module name (which defines the name scope of the interface
and operation). The acceptable characters are A-Z a-z 0-9 _. Characters outside this range may give unpredictable results. You can,
however, use an asterisk as the last (or only) character to specify a generic name. Case is significant and should match the original Java or IDL source. To comply with CORBA, however, installation of REQUESTMODELs that specify MODULE with values differing only in case from previously installed definitions will be rejected. If you specify a generic value for MODULE, then you must specify INTERFACE as * and OPERATION as *. If you specify RTYPE as GENERIC, you must specify MODULE as *. To indicate the default package, leave this field blank and specify a non-blank (but possibly generic) INTERFACE. For EJB REQUESTMODELs - that is, if RTYPE is EJB - this field should be blank. If any of the obsolete attribute values (OMGINTERFACE, OMGMODULE and OMGOPERATION) are present in the request model definition, MODULE must be blank. |
| Name | NAME | The name of the request model definition. |
| Object management group (OMG) interface name | OMGINTERFACE | This attribute is obsolete, but is supported to provide BAS definition support for earlier releases of CICS. If this attribute is present in the request model definition, the following attributes must be blank: BEANNAME, CORBASERVER, INTFACETYPE, INTERFACE, OPERATION and RTYPE. |
| Object management group (OMG) module name | OMGMODULE | This attribute is obsolete, but is supported to provide BAS definition support for earlier releases of CICS. If this attribute is present in the request model definition, the following attributes must be blank: BEANNAME, CORBASERVER, INTFACETYPE, INTERFACE, OPERATION and RTYPE. |
| Object management group (OMG) operation name | OMGOPERATION | This attribute is obsolete, but is supported to provide BAS definition support for earlier releases of CICS. If this attribute is present in the request model definition, the following attributes must be blank: BEANNAME, CORBASERVER, INTFACETYPE, INTERFACE, OPERATION and RTYPE. |
| Operation name | OPERATION | A name, of up to 255 characters, matching the IDL operation or an IDL representation of the bean method signature. The acceptable characters are A-Z a-z 0-9 _ and accented alphabetic characters. |
| Request model type | RTYPE | The type of REQUESTMODEL:
|
| CICS transaction ID | TRANSID | The 4-character name of the CICS transaction to be used when a new request processor transaction instance is required to process a method request matching the specification of the REQUESTMODEL. The transaction definition must have as its initial program a JVM program whose JVMClass is com.ibm.cics.iiop.RequestProcessor. It must be installed in all the AORs of the logical EJB server; it need not be installed in listener regions that are not also AORs. |
| User data area 1 | USERDATA1 | Optional string of up to 8 characters that allows you to provide additional site-specific data related to the BAS resource definition. This field is ignored for CICS CSD resource definitions. |
| User data area 2 | USERDATA2 | Optional string of up to 8 characters that allows you to provide additional site-specific data related to the BAS resource definition. This field is ignored for CICS CSD resource definitions. |
| User data area 3 | USERDATA3 | Optional string of up to 8 characters that allows you to provide additional site-specific data related to the BAS resource definition. This field is ignored for CICS CSD resource definitions. |