To install a resource definition dynamically:
- Display an information panel containing the resource you wish to install
and type INS against it. A panel like the one in Figure 25 is
displayed:
Figure 25. Installing a resource in CICS systems
COMMAND ===>
Name C001 Version 0
Type CONNDEF
Target Scope ===>
Related Scope ===>
Usage ===> LOCAL How resource is referenced
Mode ===> N/A Resource use qualifier
Override ===> NONE Scope Attribute overrides applied to
Ref Assign ===> Resource Assignment name
Notify ===> NO Precheck (INACTIVE, RELEASE, FULL, NO)
State Check ===> NO Consistent State (YES, NO)
Force Install ===> NO Unconditional install (YES, NO)
Override string expression: (Type MODIFY to list modifiable columns)
===>
===>
===>
Press ENTER to Install.
Type END or CANCEL to cancel without installing.
- Provide details of the CICS® systems where the resources are to be
installed (see Providing CICS system details).
- Provide any override expressions (see Providing override expressions).
- Press the Enter key to action any pre-installation checks and install
the resource definition in the specified CICS systems.
- Handle any errors (see Handling dynamic installation errors in the EUI).
Provide the following information, as appropriate:
- Target Scope
- Enter the specific or generic name of an existing CICS system or CICS system group into which the specified resource is to be installed. If
you enter a generic value, a list of valid CICS systems and CICS system groups is displayed.
- Related Scope
- If you specify a Usage value of REMOTE, enter
the specific or generic name of an existing CICS system into which the remote resource
is to be installed as LOCAL. If you enter a generic value, a list of valid CICS systems
is displayed.
Note:
For remote transaction definitions (TRANDEFs)
that are defined as dynamic, you can specify a CICS system group for the Related Scope
value. For all other remote resources, you can specify a CICS system group only if it
consists of a single CICS system.
- Usage
- Specify how the resource will be used:
- LOCAL
- The resource is contained within the target CICS system. LOCAL is valid for
all supported resource types.
- REMOTE
- The resource definition refers to a resource installed in a different CICS system. If you
specify REMOTE, you must also specify a Related Scope value to identify the CICS system that
will contain a local instance of the resource. REMOTE is valid only for the
following resource types:
- FILEDEF
- PROGDEF
- TDQDEF
- TRANDEF
Notes:
- When you specify REMOTE, the resources are assigned to all the CICS systems
identified in both the Target Scope and Related Scope fields. Likewise, when
the resources associated with this assignment are installed, remote resources
are installed in both the target and related scopes.
- Although a temporary storage queue may
be created on a remote system, the temporary storage model that controls the
queue's attributes is always a local resource. Therefore, when you install
a temporary storage model definition, the Usage parameter must always specify
LOCAL. See Installing BAS temporary storage model definitions. For a description of the TSMDEF Remote
system attribute, see Temporary storage model definition attributes.
- Mode
- For some resource types, CICSPlex® SM requires additional information to determine
which subset of resource attributes to use in completing the installation.
The Mode value you should specify depends on the resource type being installed:
- Programs (PROGDEF)
- If you specified LOCAL in the Usage field, you can specify AUTO to have
CICS automatically install programs into a system. AUTO means that no explicit
definition of the programs is required in the CICS system. Otherwise, specify N/A.
- Transactions (TRANDEF)
- You can specify whether or not the transaction should be processed by
the dynamic routing program. If the Usage field contains REMOTE, a Mode must
be specified.
Note:
The value you specify here overrides the Dynamic
value in the transaction definitions (TRANDEF).
- DYNAM
- Transactions are processed by the dynamic routing program.
- STAT
- Each transaction should be sent to the remote CICS system identified in the
transaction definition (TRANDEF). This mode may be specified only if the Usage
field contains REMOTE.
- Transient data queues (TDQDEF)
- You can identify the type of transient data queue to be installed:
- EXTRA
- Extrapartition TDQ
- IND
- Indirect TDQ
- INTRA
- Intrapartition TDQ
If you specify N/A, CICSPlex SM uses the Type value in the TDQDEF to
install the transient data queue. If the Type value is REMOTE, CICSPlex SM installs
an indirect TDQ.
For all other resources, specify N/A because
no Mode data is required.
- Override
- If you plan to specify an override expression for the resource, indicate
which scope the override values should be applied to:
- NONE
- Do not apply any override values.
- BOTH
- Apply the override values to both scopes.
- RELATED
- Apply the override values to the Related Scope only.
- TARGET
- Apply the override values to the Target Scope only.
- Ref Assign
- If you are installing connections from the CONNDEF view, identify the
resource assignment that applies to the related session definitions (SESSDEF).
For each connection, CICSPlex SM requires one or more session definitions to properly
construct the actual CICS link.
Note:
The Ref Assign field appears
only when you are installing a connection from the CONNDEF view.
When you install resources into CICS systems dynamically, you can ask CICSPlex SM to
perform certain types of checks before it attempts to install the resources.
- Are the CICS systems running?
- Do the CICS systems support the EXEC CICS CREATE command?
If you request any of these pre-installation checks, CICSPlex SM performs them
for all the resources you specified before any of the resources are actually
installed. You use the Notify field to request opre-installation checks.
- Notify
-
- INACTIVE
- CICSPlex SM checks all of the CICS systems you identified to make sure they are
currently active in the CICSplex. If any of the CICS systems are not active, CICSPlex SM returns
a list of inactive systems.
- RELEASE
- CICSPlex SM checks for CICS systems in the target scope that do not support EXEC
CICS CREATE commands. If any of the CICS systems are running a release of CICS that
does not support EXEC CICS CREATE, CICSPlex SM returns a list of systems where
resources cannot be installed.
- FULL
- CICSPlex SM checks all of the CICS systems you identified to make sure they are
currently active in the CICSplex, and checks that the CICS system is at the appropriate
level for the resource being installed. If any of the CICS systems are not active, CICSPlex SM returns
a list of inactive systems. If any of the CICS systems are running a release of
CICS that does not support EXEC CICS CREATE, CICSPlex SM returns a list of systems
where resources cannot be installed.
- No
- No consistent state checking is performed.
If a resource that you are trying to install already exists in a CICS system, CICSPlex SM can
check whether its current operational state would allow the resource to be
replaced. For example, if a program with the same name and attributes exists
in a CICS system, CICSPlex SM attempts to discard it. However, if that program is currently
in use, CICSPlex SM cannot replace it with a new one. You use the State check field
to request a consistent state check.
- State check
-
- NO
- CICSPlex SM does not provide details on resource that are not installable
because of their status before issuing an EXEC CICS CREATE command.
- YES
- CICSPlex SM provides details on resources that are not installable because
of their status before issuing an EXEC CICS CREATE command.
If you do not request a state check, CICSPlex SM simply passes the EXEC CICS
CREATE request to CICS; if the resource is in a state that prevents it from
being replaced, the request fails.
Before installing a resource, CICSPlex SM checks to see if the same resource
already exists in the CICS system and if CICSPlex SM itself was responsible for installing
it. If so, CICSPlex SM considers the new resource to be a duplicate.
In this situation, CICSPlex SM concludes that the new resource does not need
to be installed because it is a duplicate of one that already exists. However,
you may want to reinstall an existing resource if, for example, you have
changed attributes of the definition, or you are supplying override values
as part of the installation request. To do this, you can use the Force Install
option when you dynamically install resources. The Force Install option is
available when you:
- Install an individual resource
- Install a resource group
- Install a resource description
- Replace a resource description
- Force Install
-
- Yes
- Install the specified resource unconditionally, without checking whether
or not it is a duplicate
- No
- Do not install the duplicate resource.
By default, Force Install is set to No; CICSPlex SM does not normally force
the isntallation of a resource it believes to be a duplicate. However, if
you specify YES for Force Install, you can bypass this duplicate resource
checking. CICSPlex SM will install all of the specified resources unconditioinally.
An override expression identifies attributes of
the specified resource whose values are to be overridden when it is installed
in one or more of the specified scopes. (The value in the Override field determines
which scope the override values are applied to.)
- Override string expression
-
(Optional.) An override expression can be made up of one or more
attribute expressions in the form:

Override Expression
.-,----------.
V |
>>---attr=value-+-.--------------------------------------------><
where:
- attr
- Is the name of a modifiable attribute for the resource.
- value
- Is the value to which you want the attribute set. The following restrictions
apply:
To see a list of resource attributes that can be modified, type MODIFY
in the COMMAND field and press Enter.
[[ Contents Previous Page | Next Page Index ]]