Edit CICS system initialization parameters
- Specify the following CICS® system
initialization (SIT) parameters. For more information on these parameters,
see the CICS Transaction Server
documentation.
- CPSMCONN=LMAS
- Only required if your system uses CICSPlex® SM. Specifies that you want CICS to initialize the region as
a CICSPlex SM locally managed
application system (LMAS) connected to the maintenance point CMAS.
If you are installing CICS Configuration Manager into an existing CICSPlex SM WUI region, then do not alter the existing specification of CPSMCONN=WUI.
- CSDACC=READWRITE
- Required.
- CSDDISP
- Required. You must specify this parameter and the related CSDDSN parameter. Whether you specify CSDDISP=OLD or CSDDISP=SHR depends on your site-specific requirements.
- CSDDSN=name
- You must specify the CSD file via the SIT parameter
CSDDSN, not via the ddname DFHCSD in the CICS region startup JCL.
The CICS Configuration Manager server dynamically modifies the DFHCSD data set name each time it needs to access a CSD file. Specifying the ddname in JCL prevents the server from dynamically allocating the ddname, and causes the CICS Configuration Manager server to report an error.
- CSDLSRNO=value
- The values of CSDLSRNO that you can specify depends on the release
of CICS Transaction Server
that runs the CICS Configuration
Manager server
region:
- V3.2, or earlier: you can specify any value allowed by CSDLSRNO
- From V4.1: you can specify any value allowed by CSDLSRNO, with the following exception: if you specify the SIT parameter TRANISO=YES, then you cannot specify CSDLSRNO=NONE
- CSDRLS=YES or NO
- No restriction on this value. This value has no effect on whether CICS Configuration
Manager uses VSAM record-level
sharing (RLS) mode to access other CSD files.
After completing installation, if you define a CICS configuration that refers to this CSD file (so that you can use CICS Configuration Manager to manage its resource definitions), then, as for any CICS configuration that refers to a CSD file, you must specify an appropriate RLS access option. For details, see Defining CICS configurations that refer to CSD files.
See also the related RLS parameter.
- CSDSTRNO=value
- The CSDSTRNO system initialization parameter specifies the number
of concurrent requests that can be processed against a CSD file. These
requests include requests from CICS Configuration
Manager to update a CSD
file. Each user that processes a CSD file requires two strings. Specify
a value according to the number of concurrent updates that CICS Configuration
Manager might request for
a CSD file at your site. A CSDSTRNO value of 30 (allowing 15 concurrent
requests) should satisfy most installations.
However, if CICS Configuration Manager reports a CSD RDO exception with codes EIBRESP=119 (CSDERR) EIBRESP2=0000005 (insufficient VSAM strings), then increase this value in multiples of 2 (up to a maximum of 254) until the symptoms no longer occur. The MSGUSR output data set of the CICS region might contain messages that further describe the CSDERR.
Note: The CSDSTRNO parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD file are recovered from the global catalog. However, you can redefine the number of strings for the CSD dynamically with an EXEC CICS SET FILE command. For example CECI SET FILE(DFHCSD) STRINGS(value). - ENCRYPTION=STRONG (recommended)
- When saving to a CSD file resource definitions that
contain cipher codes (such as URIMAP and TCPIPSERVICE), CICS restricts the set of cipher-code hex pairs
to the set of values consistent with the CICS region's ENCRYPTION parameter value:
- The CICS Configuration Manager server must use an ENCRYPTION value that is equal to or higher than the highest level of any encryption required by the CICS-CSD or CICSPlex SM systems that the server manages.
- It is recommended that the CICS Configuration Manager server specifies ENCRYPTION=STRONG, so that it can save any of the permissible (valid) cipher values for URIMAP or TCPIPSERVICE.
- GRPLIST=lists
- One of the lists specified by this parameter must be the list to which you added the group CCV530, in Define CICS resources.
- ICVR
- The CICS Configuration Manager server uses CICS file control mass delete (delete with generic key) to purge data from its work files. When processing very large data requests, this delete operation might exceed the CICS region's ICVR (default runaway task time) limit, resulting in a task abend for the CWBA CICS Web support transaction. These errors might appear as an ASP9 abend in the MSGUSR output data set of the CICS region. If these conditions occur, increase the CICS region's ICVR value.
- KEYRING=keyring
- Only required if you want the CICS Configuration Manager server and its client to communicate via a port that uses the secure sockets layer (SSL).
- MXT=value
- Limits the number of concurrent user tasks that the CICS region can process. Each CICS Configuration
Manager API command request
requires 3 concurrent user tasks. In CICS Transaction
Server V4.2 and earlier, the default MXT value is 5, which is inadequate
to handle concurrent CICS Configuration
Manager requests.
From CICS Transaction Server
V5.1, the default MXT value is 500, allowing many concurrent CICS Configuration
Manager requests.
If the MXT value is exceeded when attempting to start a task that is related to CICS Configuration Manager, then CICS might terminate the transaction (CWBA, CCVA, or CCVT) with the abend code AEXY.
When specifying an MXT value, consider the amount of storage allocated to the CICS region.
Note: To set this value while CICS is running, use the EXEC CICS SET SYSTEM MAXTASKS command. For example, CECI SET SYSTEM MAXTASKS(value). - PLTPI=xx
- If you updated the PLTPI: ensure that this parameter refers to the suffix of the PLTPI that you updated or created earlier for the program CCVIINIT, in Optional: Update the PLTPI.
- RLS=YES or NO
- If you specified CSDRLS=YES,
or you want CICS Configuration
Manager to
access CSD files using RLS, then specify RLS=YES.
Even if you specified CSDRLS=NO for this CICS region, if you want CICS Configuration Manager to access the CSD files for other CICS regions using RLS, then specify RLS=YES.
- RRMS=YES
- Required by the CICS Configuration
Manager journal
housekeeping batch program
, and for CICS Transaction Server to run SYNCPOINT ROLLBACK
.
In addition to specifying this parameter, you also need to ensure that the Resource Recovery Services (RRS) are running on the MVS™ system that hosts this CICS region.
For more information on the journal housekeeping batch program, see Unloading and loading journal records.
- SEC=YES or NO
- If you want to authenticate CICS Configuration Manager users, and be able to restrict user access to API commands and resource definitions, then SEC=YES is required. For details, see Authenticating the client user and Restricting access to API commands and resource definitions.
- SSL-related parameters
- If you want the CICS Configuration
Manager server
to listen for clients on an SSL port, then you must specify various
SSL-related parameters.
CICS Configuration Manager has the following specific requirements for SSL-related parameters, depending on the release of CICS Transaction Server that runs the CICS Configuration Manager server region:
- V2.3, or earlier: specify SSLTCBS=2 or greater. (SSLTCBS is obsolete in later releases.)
- V3.1, or later: either do not specify MAXSSLTCBS (to use the default value of 8), or specify MAXSSLTCBS=8 or greater.
For more information on SSL-related parameters, see the CICS documentation.
- TCPIP=YES
- Activates CICS TCP/IP services. These services are required for CICS Web support, which the CICS Configuration Manager server uses to communicate with clients.
- (Optional.) If you want to use the CICS Configuration
Manager agent to perform
actions on active CSD-based CICS regions,
then specify the following CICS system
initialization parameters:
- VTAM=YES
- IRCSTRT=YES
- ISC=YES
These parameters are required for the MRO or ISC links that allow the CICS Configuration Manager server to communicate with agents. Other steps for configuring for the agent are described later, in Optional: Configure the agent for CSD-based CICS regions.