You can define CICS® resources using the CICS Explorer®, CICS bundles, CICSPlex® SM Business Application Services, resource definition online (RDO), CICS system programming commands, the DFHCSDUP offline utility, autoinstall, or macro resource definition. Compare the relevant methods of resource definition to choose which way to define each of your CICS resources.
You must use macro instructions to define non-VTAM networks and terminals, non-VSAM files, databases, and resources for monitoring and system recovery. For information about CICS macros, see Macro resource definition.
Which methods you use depends on the resources you want to define. Table 1 suggests some of the things you should consider when deciding which definition method to use. Table 2 shows you the methods you can use for each resource.
Method | Advantages | Disadvantages |
---|---|---|
CICS Explorer |
|
FEPI resources cannot be defined with CICS Explorer. |
Bundles |
|
|
CICSPlex SM BAS |
|
None |
RDO | RDO is used while CICS is running, so allows fast access to resource definitions. | Because CEDA operates on an active CICS system, care should be taken if it is used in a production system. Use some form of auditing as a control mechanism. |
EXEC CICS SPI commands | It enables configuration and installation of CICS resources for large numbers of CICS regions from a single management focal point. It also allows you to write applications for administering the running CICS system. | CREATE commands neither refer to nor record in the CSD file. The resulting definitions are lost on a cold start, and you cannot refer to them in a CEDA transaction. |
EXEC CICS CSD system commands |
|
Requires more work to implement than some other methods. |
DFHCSDUP |
|
|
Autoinstall | If you have large numbers of resources, much time is needed to define them, and if they are not all subsequently used, storage is also wasted for their definitions. Using autoinstall reduces this wasted time and storage. | You must spend some time initially setting up autoinstall in order to benefit from it. |
Macro | Where possible, use the other methods. |
|
Resource | CICS Explorer | CICSPlex SM BAS | RDO, EXEC CICS SPI, and EXEC CICS CSD commands | Bundles | DFHCSDUP | Autoinstall | Macro |
---|---|---|---|---|---|---|---|
Atom documents | Yes | Yes (ATOMDEF) | Yes (ATOMSERVICE) | Yes | Yes | No | No |
Bundles | Yes | Yes (BUNDDEF) | Yes (BUNDLE) | N/A | Yes | No | No |
Connections | Yes | Yes (CONNDEF) | Yes (CONNECTION) | No | Yes | LU 6.2 only | No |
DB2® Connections | Yes | Yes (DB2CDEF) | Yes (DB2CONN) | No | Yes | No | No |
DB2 entries | Yes | Yes (DB2EDEF) | Yes (DB2ENTRY) | No | Yes | No | No |
DB2 transactions | Yes | Yes (DB2TDEF) | Yes (DB2TRAN) | No | Yes | No | No |
Document template | Yes | Yes (DOCDEF) | Yes (DOCTEMPLATE) | No | Yes | No | No |
Enqueue models | Yes | Yes (ENQMDEF) | Yes (ENQMODEL) | No | Yes | No | No |
Event bindings and capture specifications | Yes | No | No | Yes | No | No | No |
Event processing adapter | Yes | No | No | Yes | No | No | No |
Event processing adapter set | Yes | No | No | Yes | No | No | No |
FEPI node lists | No | Yes (FENODDEF) | Yes (NODELIST) | No | No | No | No |
FEPI pool definitions | No | Yes (FEPOODEF) | Yes (POOL) | No | No | No | No |
FEPI property sets | No | Yes (FEPRODEF) | Yes (PROPERTYSET) | No | No | No | No |
FEPI target lists | No | Yes (FETRGDEF) | Yes (TARGETLIST) | No | No | No | No |
Files (BDAM) | No | No | No | No | No | No | Yes (DFHFCT) |
Files (VSAM) | Yes | Yes (FILEDEF) | Yes (FILE) | No | Yes | No | No |
IPIC connections | Yes | Yes (IPCONDEF) | Yes (IPCONN) | No | Yes | Yes | No |
Journals | Yes | Yes (JRNLDEF) | No | No | No | Yes | No |
Journal models | Yes | Yes (JRNMDEF) | Yes (JOURNALMODEL) | No | Yes | No | No |
LIBRARY resources | Yes | Yes (LIBDEF) | Yes (LIBRARY) | Yes | Yes | No | No |
Local shared resource (LSR) pools | Yes | Yes (LSRDEF) | Yes (LSRPOOL) | No | Yes | No | No |
Map sets | Yes | Yes (MAPDEF) | Yes (MAPSET) | No | Yes | Yes | No |
OSGi bundles and services | Yes | No | No | Yes | No | No | No |
Partition sets | Yes | Yes (PRTNDEF) | Yes (PARTITIONSET) | No | Yes | Yes | No |
Partners | Yes | Yes (PARTDEF) | Yes (PARTNER) | No | Yes | No | No |
Pipelines | Yes | Yes (PIPEDEF) | Yes (PIPELINE) | No | Yes | No | No |
Policy | Yes | No | No | Yes | No | No | No |
Process types | Yes | Yes (PROCDEF) | Yes (PROCESSTYPE) | No | Yes | No | No |
Profiles | Yes | Yes (PROFDEF) | Yes (PROFILE) | No | Yes | No | No |
Programs | Yes | Yes (PROGDEF) | Yes (PROGRAM) | Yes | Yes | Yes | No |
Recoverable service elements | No | No | No | No | No | No | Yes (DFHRST) |
Sessions | Yes | Yes (SESSDEF) | Yes (SESSIONS) | No | Yes | No. | No |
TCP/IP services | Yes | Yes (TCPDEF) | Yes (TCPIPSERVICE) | No | Yes | No | No |
Temporary storage (defined by macro) | No | No | No | No | No | No | Yes (DFHTST) |
Temporary storage models (resource definition) | Yes | Yes (TSMDEF) | Yes (TSMODEL) | No | Yes | No | No |
Terminals (non-VTAM) | No | No | No | No | No | No | Yes (DFHTCT) |
Terminals (VTAM) | Yes | Yes (TERMDEF) | Yes (TERMINAL) | No | Yes | Yes | No |
Transactions | Yes | Yes (TRANDEF) | Yes (TRANSACTION) | Yes | Yes | No | No |
Transaction classes | Yes | Yes (TRNCLDEF) | Yes (TRANCLASS) | No | Yes | No | No |
Transient data queues | Yes | Yes (TDQDEF) | Yes (TDQUEUE) | No | Yes | No | No |
Typeterms | Yes | Yes (TYPTMDEF) | Yes (TYPETERM) | No | Yes | No | No |
URI maps | Yes | Yes | Yes (URIMAP) | Yes | Yes | No | No |
Web services | Yes | Yes | Yes (WEBSERVICE) | No | Yes | Yes | No |
WebSphere® MQ connection | Yes | Yes (MQCONDEF) | Yes (MQCONN) | No | Yes | No | No |
XML transforms | Yes | No | No | Yes | No | No | No |