RDO |
This method uses the CEDA transaction, which allows you
to define, alter, and install resources in a running CICS system. |
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 CREATE system commands |
This method allows you to add CICS resources to a CICS
region without reference to the CSD file. |
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. |
DFHCSDUP |
DFHCSDUP is an offline utility that allows you to define,
list, and modify resources using a batch job. DFHCSDUP can be invoked as
a batch program or from a user-written program running either in batch mode
or under TSO. Using the second method, you can specify up to five user exit
routines within DFHCSDUP. |
- You can modify or define a large number of resources in one job.
- You can run DFHCSDUP against a non-recoverable CSD file while it is being
shared between CICS regions using RLS access mode.
|
- You cannot install resources into an active CICS system.
- You cannot make updates via DFHCSDUP against a recoverable CSD file that
is being accessed in RLS mode.
|
Autoinstall |
This applies to VTAM terminals, LU6.2 sessions, journals,
programs, mapsets, and partitionsets. You set up “model” definitions using
either RDO or DFHCSDUP. CICS can then create and install new definitions
for these resources dynamically, based on the models. |
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 |
Using this method, you code and assemble macro instructions
to define resources in the form of tables. |
Where possible, use the other methods. |
- You can change the definitions contained in the tables while CICS is running,
but you must stop and restart CICS if you want it to use the changed tables.
- You must do time-consuming assemblies to generate macro tables.
|
CICSPlex SM BAS |
Using BAS, you can create, maintain, and install CICS
resources in a running CICS system. For full information, see CICSPlex System Manager Managing Business
Applications. |
- Centralized resource definition
- Logical scoping
- Distributed resource installation
|
|