Resource definition attributes

Most resources can be defined using CICS RDO or CICSPlex SM Business Application Services (BAS).

ATOMSERVICE resource definitions
An ATOMSERVICE resource defines an Atom service, a feed, a collection, or a category document, and identifies the resources that are used to supply the data for the feed.
BUNDLE resources
A BUNDLE resource defines a CICS® bundle, a unit of deployment for an application. A bundle is a collection of CICS resources, artifacts, references, and a manifest that you can deploy into a CICS region to represent a whole application or a component of an application.
CONNECTION resources
A CONNECTION defines a remote system with which your CICS system communicates, using intersystem communication (ISC) or multiregion operation (MRO).
DB2CONN resources
A DB2CONN definition defines the attributes of the connection between CICS and Db2®, and of the pool threads and command threads used with the connection.
DB2ENTRY resources
A DB2ENTRY defines the attributes of entry threads used by the CICS Db2 attachment facility.
DB2TRAN resources
A DB2TRAN defines a transaction, or a group of transactions, associated with a DB2ENTRY, that are additional to the transactions specified in the DB2ENTRY itself.
DOCTEMPLATE resources
A DOCTEMPLATE resource defines the attributes of a document template.
ENQMODEL resources
An ENQMODEL defines a named resource for which the EXEC CICS ENQ and EXEC CICS DEQ commands have a sysplex-wide scope.
FEPI resources
Node list definitions, pool definitions, property set definitions, and target list definitions are used for FEPI resources.
FILE resources
A FILE resource defines the physical and operational characteristics of a file.
IPCONN resources
An IPCONN resource defines a Transmission Control Protocol/Internet Protocol (TCP/IP) communication link to a remote system. This communication link is known as an IPIC connection.
JOURNALMODEL resources
A JOURNALMODEL resource defines the connection between a CICS journal name (or identifier) and the associated physical log streams managed by the MVS™ system logger, or between the journal name and the SMF log.
JVMSERVER resources
A JVMSERVER resource defines the runtime environment for a JVM server.
LIBRARY resources
Use the LIBRARY resource to define the physical and operational characteristics of a dynamic program LIBRARY concatenation.
LSRPOOL resources
The LSRPOOL resource defines the size and characteristics of the local shared resources (LSR) pool. The LSR pool is a reserve of data buffers, strings, and Hiperspace buffers that VSAM uses when processing access requests for certain files.
MAPSET resources
A MAPSET resource defines a BMS map sets.
MQCONN resources
An MQCONN resource defines the attributes of the connection between CICS and IBM® MQ. You can install or discard an MQCONN resource only when CICS is not connected to IBM MQ.
MQMONITOR resources
An MQMONITOR resource defines attributes for IBM MQ message consumers, such as the trigger monitor transaction CKTI. Using an MQMONITOR enables the associated transaction that services an MQ queue to restart automatically when the connection to the IBM MQ queue manager is established.
PARTITIONSET resources
A PARTITIONSET resource defines a partition set, that is, is a table that describes to CICS how to partition a display screen.
PARTNER resources
A PARTNER resource enables CICS application programs to communicate, using APPC protocols, with a partner application program running on a remote logical unit.
PIPELINE resources
A PIPELINE resource is used when a CICS application is in the role of a web service provider or requester. It provides information about the message handler programs that act on a service request and on the response. Typically, a single PIPELINE definition defines an infrastructure that can be used by many applications.
PROCESSTYPE resources
A PROCESSTYPE resource defines a BTS process-type. It names the CICS file which relates to the physical VSAM data set (repository) on which details of all processes of this type (and their activity instances) are to be stored.
PROFILE resources
A PROFILE resource specifies options that control the interactions between transactions and terminals or logical units. The PROFILE is a means of standardizing the use of such options as screen size and printer compatibility, and the use of such functions as message journaling and the node error program.
PROGRAM resources
PROGRAM resources control information for a program that is stored in the program library and used to process a transaction, or part of a transaction.
SESSIONS resources
A SESSIONS resource defines the logical link between two CICS systems that communicate using intersystem communication (ISC) or multiregion operation (MRO).
TCPIPSERVICE resources
A TCPIPSERVICE resource defines which TCP/IP services are to use CICS internal sockets support.
TDQUEUE resources
A TDQUEUE definition defines the attributes of a transient data queue.
TERMINAL resources
A TERMINAL resource defines the characteristics of a terminal device which communicates with CICS. Terminal devices include visual display units, printers, operating system consoles, and more specialized devices such as facsimile (FAX) machines.
TRANCLASS resources
A TRANCLASS resource defines the characteristics of a transaction class.
TRANSACTION resources
A TRANSACTION resource defines transaction attributes that relate to functions provided by CICS.
TSMODEL resources
A temporary storage model specifies the properties of a set of TS queues. Individual TS queues are associated with a TSMODEL by the prefix, a character string that matches the leading characters of the queue name.
TYPETERM resources
A TYPETERM resource defines a set of attributes that are common to a group of terminals.
URIMAP resources
URIMAP definitions are resources that match the URIs of HTTP, Atom feed, or web service requests, and provide information on how to process the requests.
WEBSERVICE resources
A WEBSERVICE resource defines aspects of the run time environment for a CICS application program deployed in a web services setting, where the mapping between application data structure and SOAP messages has been generated using the CICS web services assistant. Although CICS provides the usual resource definition mechanisms for WEBSERVICE resources, they are typically installed dynamically, using the output produced by the assistant.

Parent topic: Resources