The CEDA INSTALL command

Dynamically make the resource definitions in the named group or group list available to the active CICS® system.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-CEDA--Install--+--------------------+------------------------>
                  +-ALl(name)----------+   
                  +-Connection(name)---+   
                  +-CORbaserver(name)--+   
                  +-DB2Conn(name)------+   
                  +-DB2Entry(name)-----+   
                  +-DB2Tran(name)------+   
                  +-Djar(name)---------+   
                  +-DOctemplate(name)--+   
                  +-Enqmodel(name)-----+   
                  +-File(name)---------+   
                  +-Journalmodel(name)-+   
                  +-Lsrpool(name)------+   
                  +-Mapset(name)-------+   
                  +-PARTItionset(name)-+   
                  +-PARTNer(name)------+   
                  +-PROCesstype(name)--+   
                  +-PROFile(name)------+   
                  +-PROGram(name)------+   
                  +-Requestmodel(name)-+   
                  +-Sessions(name)-----+   
                  +-TCpipservice(name)-+   
                  +-TDqueue(name)------+   
                  +-TErminal(name)-----+   
                  +-TRANClass(name)----+   
                  +-TRANSaction(name)--+   
                  +-TSmodel(name)------+   
                  '-TYpeterm(name)-----'   

>--+-Group(groupname)-+----------------------------------------><
   '-List(listname)---'   

Description

You can use single-resource install to install only the resources you require.

When applied to telecommunication and intercommunication resources, there are restrictions on the single-resource INSTALL command. The restrictions apply to resource definitions that are linked—for example, CONNECTION and SESSIONS definitions.

You can install the following resource types only as part of a group:
  • CONNECTION definitions, except a CONNECTION with ACCESSMETHOD(INDIRECT)
  • SESSIONS definitions
  • TERMINAL definitions for pipeline terminals that share the same POOL.

If you want to use single-resource INSTALL for TERMINAL and related TYPETERM definitions, you must install the TYPETERM that is referred to by a TERMINAL definition before you install the TERMINAL definition.

The same applies when installing groups containing TERMINAL and TYPETERM definitions; install the group containing the TYPETERM definition before you install the group containing the TERMINAL definition. Similarly, if you install a list that contains groups containing TERMINAL and TYPETERM definitions, the group containing the TYPETERM definition must be before the group containing the TERMINAL definition. Also, in a list containing groups of DB2® resource definitions (DB2CONN, DB2ENTRY, and DB2TRAN definitions), the DB2CONN should be defined in the first group in the list.

A CORBASERVER definition must be either in the same group as the DJAR definitions that refer to it, or in a group that is installed before the group containing those DJAR definitions.

If the named resource already exists in the active CICS system, the existing definition is replaced by the new one.

Replacement of an existing definition occurs only if it is not actually in use.

If the installation of one or more of the resources in the group(s) being installed fails because the resource is in use or for any other reason, the following takes place:
  1. The install process continues with the next resource in the group.
  2. When the group install is complete, if the resource that failed was part of an installable set, all the resources in the installable set are backed out. Resources that were committed at the individual resource level are not backed out. For a list of the resource types that are committed as part of an installable set, see What happens when you use the INSTALL command.
  3. A message is displayed to indicate that the group has been only partially installed. A message is also produced on the message panel for each of the resources that failed to install, stating the reason for each failure. No messages are produced for those resources that have been backed out.

In addition, a message is written to the CEMT log, saying that the install completed with errors.

CEDA INSTALL can be performed from a console, using the MVS™ MODIFY command.

Options

Group(groupname)
specifies the group to be installed, or containing the resource to be installed. A generic group name is not accepted.
List(listname)
specifies the list of groups to be installed, or containing the resource to be installed. A generic list name is not accepted.
resource(name)
specifies the resource to be installed.
Note: If you want to use singe-resource install for ENQMODEL, remember that ENQMODELs usually have the default status of ENABLED, so the order of installing ENQMODELs must follow the rules for ENABLING ENQMODELs; that is, ENQMODELs forming nested generic ENQnames must be enabled in order from the most to the least specific. For example, ABCD* then ABC* then AB*.