Defining resources
After you have installed CICS®, you must define and install all the resources that your CICS regions require to run user transactions.
For a list of resources, see CICS resources: listing, syntax, and attributes.
- Resource definition online (RDO) transaction CEDA
Use the CEDA transaction to add, remove, or change resource definitions online. - The resource definition batch utility DFHCSDUP
The CICS system definition utility program, DFHCSDUP, is a component of resource definition online (RDO). You can use the DFHCSDUP offline utility program to read from and write to a CICS system definition (CSD) file, either while CICS is running or while it is inactive. - Autoinstall
Autoinstall is a method of creating and installing CICS resources dynamically as they are required. You can use autoinstall for SNA LUs, MVS™ consoles, APPC connections, IPIC connections, programs, map sets, partition sets, and journals. - Autoinstall models
You must provide at least one model resource definition for each type of resource to be autoinstalled. - Autoinstall control program
You control autoinstall by means of an autoinstall control program, either user-written or supplied by CICS. This program is responsible for, among other things, providing the model name or names to CICS and, providing z/OS® Communications Server information to CICS for autoinstall for terminals, and so on. - Autoinstalling z/OS Communications Server terminals
How to use autoinstall for z/OS Communications Server terminals and connections. - Autoinstalling MVS consoles
Commands issued at an MVS console (or in a job stream) can be directed to a CICS region running as a started task, or job, using the MVS MODIFY command. Before CICS can accept the MVS command, it needs an entry in the terminal control table for the console issuing the command, which CICS terminal control can use to display a response. - Autoinstalling APPC connections
When you decide whether to use autoinstall for connections, there are several factors to consider. - Autoinstalling IPIC connections
Unlike autoinstalling other resources, autoinstalling an IPCONN does not require a model definition (although this is recommended). - Autoinstalling programs, map sets, and partition sets
If autoinstall for programs is active, and an implicit or explicit load request is issued for a previously undefined program, map set, or partition set, CICS dynamically creates a definition, and installs it and catalogs it as appropriate. - Autoinstalling model terminal definitions
If you define a model terminal for autoinstall, you install it just as you would an ordinary resource definition; that is, by installing the group containing it. - Autoinstalling journals
CICS writes journal data to journals or logs on log streams managed by the MVS system logger, or to SMF. - Macro resource definition
Reference information for resource definition macros used to create CICS tables. - Defining CICS bundles
A CICS bundle is a directory that contains artifacts and a manifest that describes the bundle and its dependencies. CICS bundles provide a way of grouping and managing related resources. CICS bundles also provide versioning for the management of resource updates, and can declare dependencies on other resources outside the bundle. Application developers can use CICS bundles for application packaging and deployment, business events, and services. System programmers can use CICS bundles for system events and policies. - Defining terminal resources
You can define terminal resources in two different ways, depending on the type of terminal access method that you want to use. - Resource definition installation
When a resource definition is installed, information about the resources is used to construct the data structures that represent the resource in the CICS address space.
dfha22v.html |
Last updated: Sunday, 4 June 2017