The system initialization parameter descriptions

Unless otherwise stated, all of the system initialization parameters described here can be defined to CICS® by any of these four ways:

  1. In a DFHSIT macro
  2. In a PARM parameter on the EXEC PGM=DFHSIP statement
  3. In the SYSIN data set of the CICS startup job stream
  4. Through the system console

Default values are underscored; for example, TYPE=CSECT. This notation applies to the SIT macro parameters only.

TYPE={CSECT|DSECT}
specifies the type of SIT to be generated.
CSECT
A regular control section that is normally used.
DSECT
A dummy control section.
ADI={30|number}
specifies the alternate delay interval in seconds for an alternate CICS region when you are running CICS with XRF. The minimum delay that you can specify is 5 seconds. This is the time that must elapse between the (apparent) loss of the surveillance signal in the active CICS region, and any reaction by the alternate CICS region. The corresponding parameter for the active is PDI. ADI and PDI need not have the same value.
Note:
You must give careful consideration to the values you specify for the parameters ADI and JESDI so that they do not conflict with your installation’s policy on PR/SM™ RESETTIME and the XCF INTERVAL and OPNOTIFY intervals. You should ensure that the sum of the interval you specify for ADI plus JESDI exceeds the interval specified by the XCF INTERVAL and the PR/SM policy interval RESETTIME.
AIBRIDGE={AUTO|YES}
specifies whether the autoinstall user replaceable module (URM) is to be called when creating bridge facilities (virtual terminals) used by the 3270 bridge mechanism.
AUTO
This is the default, and specifies that bridge facilities are defined automatically by CICS. The autoinstall URM is not called.
YES
Specifies that the autoinstall URM is to be called for all new bridge facilities.

See the CICS Customization Guide for information about writing an autoinstall user replaceable module.

AICONS={NO|YES|AUTO}
specifies whether you want autoinstall support for consoles. You can also set the state of autoinstall support for consoles dynamically using the CEMT, or EXEC CICS, SET AUTOINSTALL command.
NO
This is the default, and specifies that the CICS regions does not support autoinstall for consoles.
YES
Specifies that console autoinstall is active and CICS is to call the autoinstall control program, as part of the autoinstall process, when an undefined console issues an MVS™ MODIFY command to CICS.
AUTO
Specifies that console autoinstall is active but CICS is not to call the autoinstall control program when an undefined console issues an MVS MODIFY command to CICS. CICS is to autoinstall undefined consoles automatically without any input from the autoinstall control program. The 4-character termid required for the console's TCT entry is generated by CICS, beginning with a ¬ (logical not) symbol.

See the CICS Customization Guide for information about writing an autoinstall control program that supports consoles.

AIEXIT={DFHZATDX|DFHZATDY|name}
specifies the name of the autoinstall user-replaceable program that you want CICS to use when autoinstalling local VTAM® terminals, APPC connections, virtual terminals, and shipped terminals and connections. Autoinstall is the process of installing resource definitions automatically, using VTAM logon or BIND data, model definitions, and an autoinstall program.
Note:
You can specify only one user-replaceable program on the AIEXIT parameter. Which of the CICS-supplied programs (or customized versions thereof) that you choose depends on what combination of resources you need to autoinstall.

For background information about autoinstall, see in the CICS Resource Definition Guide.

DFHZATDX
A CICS-supplied autoinstall user program. This is the default. It installs definitions for:
  • Locally-attached VTAM terminals
  • Virtual terminals used by the CICS Client products
  • Remote shipped terminals
  • Remote shipped connections
DFHZATDY
A CICS-supplied autoinstall user program. It installs definitions for:
  • Locally-attached VTAM terminals
  • Local APPC connections
  • Virtual terminals used by the CICS Client products
  • Remote shipped terminals
  • Remote shipped connections
name
The name of your own customized autoinstall program, which may be based on one of the supplied sample programs. For programming information about writing your own autoinstall program, see the CICS Customization Guide.
AILDELAY={0|hhmmss}
specifies the delay period that elapses after all sessions between CICS and an autoinstalled terminal, APPC device, or APPC system are ended, before the terminal or connection entry is deleted. All sessions are ended when the terminal or system logs off, or when a transaction disconnects it from CICS.
Note:
The AILDELAY parameter does not apply to the following types of autoinstalled APPC connection, which are not deleted:
  • Sync level 2-capable connections (for example, CICS-to-CICS connections)
  • Sync level 1-only, limited resource connections installed on a CICS that is a member of a generic resource group
hhmmss
A 1 to 6-digit number. The default is 0. For non-LU6.2 terminals and LU6.2 single-session connections installed by a CINIT, 0 means that the terminal entry is deleted as soon as the session is ended. For LU6.2 connections installed by a BIND, 0 means that the connection is deleted as soon as all sessions are ended, but is reusable if a new BIND occurs before the deletion starts.

If you leave out the leading zeros, they are supplied (for example, 123 becomes 000123--that is, 1 minute 23 seconds).

AIQMAX={100|number}
specifies the maximum number of VTAM terminals and APPC connections that can be queued concurrently for autoinstall.
number
A number in the range 0 through 999. The default is 100.

A zero value disables the autoinstall function.

Specify a number that is large enough to allow for both APPC connections and terminals.

Note:
This value does not limit the total number of terminals that can be autoinstalled. If you have a large number of terminals autoinstalled, shutdown can fail due to the MXT system initialization parameter being reached or CICS becoming short on storage. For information about preventing this possible cause of shutdown failure, see the CICS Customization Guide.
AIRDELAY={700|hhmmss}
specifies the delay period that elapses after an emergency restart before autoinstalled terminal and APPC connection entries that are not in session are deleted. The AIRDELAY parameter also applies when CEMT SET VTAM OPEN is issued after a VTAM abend and PSTYPE=MNPS is coded. This causes autoinstalled resources to be deleted, if the session was not restored and has not been used since the ACB was opened.
Note:
The AIRDELAY parameter does not apply to the following types of autoinstalled APPC connection, which are always written to the CICS global catalog and recovered during a warm or emergency start:
  • Sync level 2-capable connections (for example, CICS-to-CICS connections)
  • Sync level 1-capable, limited resource connections installed on a CICS that is a member of a generic resource group
hhmmss
A 1-to 6-digit number. If you leave out the leading zeros, they are supplied. The default is 700, meaning a delay of 7 minutes. A value of 0 means that autoinstalled definitions are not written to the global catalog and therefore are not restored at an emergency restart.

For guidance about the performance implications of setting different AIRDELAY values, see the CICS Customization Guide.

Note:
If you are running CICS with XRF, set the same value on the AIRDELAY parameter for both the active and the alternate CICS regions. It is particularly important, if you want autoinstall sessions to be reestablished after a takeover, that you avoid coding a zero on this parameter for either the active or the alternate CICS regions.

For background information, see the CICS/ESA 3.3 XRF Guide.

AKPFREQ={4000|number}
specifies the number of write requests to the CICS system log stream output buffer required before CICS writes an activity keypoint. (For more information about activity keypointing, see the CICS Customization Guide .)
4000
This is the default.
number
number can be 0 (zero) or any value in the range 200 through 65535.(You cannot specify a number in the range 1--199.) You are recommended to allow AKPFREQ to assume its default value, 4000.
Note:
If you specify AKPFREQ=0, no activity keypoints are written, with the following consequences:
  • The CICS system log automatic deletion mechanism will not work so efficiently in this situation. The average system log occupancy would merely increase, maybe quite dramatically for some users. Without efficient automatic deletion, the log stream will spill onto secondary storage, and from there onto tertiary storage (unless you control the size of the log stream yourself).
  • Emergency restarts are not prevented, but the absence of activity keypoints on the system log affects the performance of emergency restarts because CICS has to read backwards through the entire log stream.
  • Backout-while-open (BWO) support is seriously affected, because without activity keypointing, tie-up records are not written to the forward recovery logs and the data set recovery point is not updated. Therefore, for forward recovery to take place, all forward recovery logs must be kept since the data set was first opened for update after the last image copy. For more information about the effect of AKPFREQ=0 on BWO, see Effect of disabling activity keypointing.
APPLID={DBDCCICS|applid}
specifies the VTAM application identifier for this CICS region.
applid
This name, 1 through 8 characters, identifies the CICS region in the VTAM network. It must be unique if running in a sysplex. It must match the name field specified in the APPL statement of the VTAM VBUILD TYPE=APPL definition. For an example, see the CICS Transaction Server for z/OS® Installation Guide.

When you define this CICS region to another CICS region, in a CONNECTION definition you specify the applid as the NETNAME. When sharing a DL/I database with a batch region, the applid is used by the batch region to identify the CICS region.

If the CICS region uses XRF, the form of the APPLID parameter is:

APPLID=(generic_applid,specific_applid)
specifies the generic and specific XRF applids for the CICS region. Both applids must be 1 through 8 characters.
generic_applid
The generic applid for both (active and alternate) the active and the alternate CICS regions. Therefore, you must specify the same name for generic_applid on the APPLID system initialization parameter for both CICS regions. Because IRC uses generic_applid to identify the CICS regions, there can be no IRC connection for an alternate CICS region until takeover has occurred and the alternate CICS region becomes the active CICS region.

When you define this XRF pair to another CICS region, in a CONNECTION definition you specify the generic applid as the NETNAME.

When sharing a DL/I database with a batch region, this name is used by the batch region to identify the CICS region. CICS passes the generic applid to DBRC, because the alternate system does not sign on to DBRC until it has completed takeover.

Do not confuse the term generic applid with generic resource name. Generic applids apply only to CICS regions that use XRF. Generic resource names apply only to VTAM generic resource groups.

specific_applid
specifies the CICS region in the VTAM network. It must match the label specified in the VTAM VBUILD TYPE=APPL definition. You must specify a different specific_applid on the APPLID system initialization parameter for the active and for the alternate CICS region. Also, generic_applid and specific_applid must be different.

The active and alternate CICS regions use the VTAM MODIFY USERVAR command to set a user application name variable, so end users do not need to know which CICS region is active at any instant. For background information about using this command, see the CICS/ESA 3.3 XRF Guide.

AUTCONN={0|hhmmss} (alternate)
specifies that the reconnection of terminals after an XRF takeover is to be delayed, to allow time for manual switching. The delay is hh hours, mm minutes, ss seconds. The default value of zero means that there is no delay in the attempted reconnection.

The interval specified is the delay before the CXRE transaction runs. CXRE tries to reacquire any XRF-capable (class 1) terminal session that failed to get a backup session, or failed the switch for some other reason. CXRE tries to reacquire other terminals that were in session at the time of the takeover.

Note that the same delay interval applies to the connection of terminals with AUTOCONNECT(YES) specified in the TYPETERM definition, at a warm or emergency restart, whether or not you have coded XRF=YES.

AUTODST={NO|YES}
specifies whether CICS is to activate automatic dynamic storage tuning for application programs.
NO
Automatic dynamic storage tuning is not required and CICS does not request this support from Language Environment®.
YES
Automatic dynamic storage tuning is required. This is activated during CICS startup when Language Environment is being initialized. CICS indicates to Language Environment that it is able to support dynamic storage tuning, and if Language Environment responds by indicating that it also supports the facility, CICS and Language Environment are synchronized to provide the required support.

For more information, see the appropriate OS/390® Language Environment manual.

Start of changeAUTORESETTIME={NO|YES]End of change
Start of changespecifies the action CICS should take if, at the next local midnight, the CICS time-of-day differs from the system time-of-day by more than 30 minutes (for example, setting clocks forward or back to adjust for Summer and Winter time).
NO
CICS issues message DFHAP1500 to indicate that a CEMT PERFORM RESET is required to synchronize the CICS time-of-day with the system time-of-day.
YES
CICS issues a PERFORM RESET to synchronize the CICS time-of-day with the system time-of-day
End of change
AUXTR={OFF|ON}
specifies whether the auxiliary trace destination is to be activated at system initialization. This parameter controls whether any of the three types of CICS trace entry are written to the auxiliary trace data set. The three types are: CICS system trace (see the SYSTR parameter), user trace (see the USERTR parameter), and exception trace entries (that are always made and are not controlled by a system initialization parameter).
OFF
Do not activate auxiliary trace.
ON
Activate auxiliary trace.

For details of internal tracing in main storage, see the INTTR parameter in topic INTTR.

AUXTRSW={NO|ALL|NEXT}
specifies whether you want the auxiliary trace autoswitch facility.
NO
Disables the autoswitch facility.
NEXT
Enables the autoswitch facility to switch to the next data set at end of file of the first data set used for auxiliary trace. Coding NEXT permits one switch only, and when the second data set is full, auxiliary trace is switched off.
ALL
Enable the autoswitch facility to switch to the inactive data set at every end of file. Coding ALL permits continuous switching between the two auxiliary trace data sets, DFHAUXT and DFHBUXT, and whenever a data set is full, it is closed and the other data set is opened.
BMS=({MINIMUM|STANDARD|def.FULL }[,COLD][,{def.UNALIGN |ALIGN}] [,{ DDS|NODDS}])
specifies which version of basic mapping support you want to be included. The function included in each version of BMS is shown in Table 19. The parameter BMS can be overridden during CICS initialization.

You need full or standard function BMS, if you are using XRF and have specified MESSAGE for RECOVNOTIFY on any of your TYPETERM definitions.

MINIMUM
The minimum version of BMS is included.
STANDARD
The standard version of BMS is included.
FULL
The full version of BMS is included. This is the default in the SIT.
COLD
CICS deletes delayed messages from temporary storage, and destroys their interval control elements (ICEs). COLD forces the deletion of messages regardless of the value in effect for START. If COLD is not specified, the availability of messages will depend on the values in effect for the START and TS parameters.
UNALIGN
specifies that all BMS maps assembled before CICS/OS/VS Version 1 Release 6 are unaligned. Results are unpredictable if the stated alignment does not match the actual alignment.
ALIGN
All BMS maps assembled before CICS/OS/VS Version 1 Release 6 are aligned.
DDS
BMS is to load suffixed versions of map sets and partition sets. BMS first tries to load a version that has the alternate suffix (if the transaction uses the alternate screen size). If the load fails, BMS tries to load a version that has the default map suffix. If this fails too, BMS tries to load the unsuffixed version. DDS, which stands for "device dependent suffixing", is the default.

You need to use map suffixes only if the same transaction is to be run on terminals with different characteristics (in particular, different screen sizes). If you do not use suffixed versions of map sets and partition sets, CICS need not test for them.

NODDS
BMS is not to load suffixed versions of map sets and partition sets. Specifying NODDS avoids the search for suffixed versions, saving processor time.

Table 19. Versions of BMS
BMS
version
Devices
supported
Function
provided
MINIMUM All 3270 system display units and printers except SNA character string printers, which are defined as DEVICE(SCSPRINT) on the RDO TYPETERM definition or as TRMTYPE=SCSPRT in DFHTCT SEND MAP command, RECEIVE MAP command, SEND CONTROL command.
Default and alternate screens; extended attributes; map set suffixes; screen coordination with null maps; and block data
STANDARD All devices are supported by BMS. These are listed in the CICS Application Programming Guide All function of MINIMUM, plus outboard formats, partitions, controlling a magnetic slot reader, NLEOM mode for 3270 system printers, SEND TEXT command, and Subsystem LDC controls.
FULL All devices supported by BMS. These are listed in the CICS Application Programming Guide Same as STANDARD, plus terminal operator paging, cumulative mapping, page overflow, cumulative text processing, routing, message switching returning BMS-generated data stream to program before output.
BRMAXKEEPTIME={86400|number}
This parameter specifies the maximum time (in seconds) that bridge facilities (virtual terminals used by the 3270 bridge) are kept if they are not used. The client application can specify this timeout value when it sends a request to run a transaction using the Link3270 bridge. If the client specifies a larger value than the BRMAXKEEPTIME value in the AOR, then CICS will change this parameter in the link parameter list.
number
The maximum timeout value that a client can specify (in seconds), before an unused bridge facility is deleted. The value specified must be in the range 0 to 86400. A value of 0 means that bridge facilities are never kept at the end of a transaction, therefore CICS will not be able to run pseudoconversational transactions. This may be useful if the region is only used for inquiry transactions. The default value is 24 hours (86400 seconds).
CDSASZE={0K|number}
specifies the size of the CDSA. The default size is 0, indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
specify number as an amount of storage in the range 0 to 16777215 bytes in multiples of 262144 bytes (256KB). If the size specified is not a multiple of 256KB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Restrictions You can specify the CDSASZE parameter in PARM, SYSIN, or CONSOLE only.

CHKSTRM={CURRENT|NONE}
specifies that terminal storage-violation checking is to be activated or deactivated.
CURRENT
TIOA storage violations are to be checked.
NONE
TIOA storage-violation checking is to be deactivated.

You can also use the CICS-supplied transaction, CSFE, to switch terminal storage-violation checking on and off.

For information about checking for storage violations, see the CICS Transaction Server for z/OS Installation Guide.

Restrictions You can specify the CHKSTRM parameter in PARM, SYSIN, or CONSOLE only.

CHKSTSK={CURRENT|NONE}
specifies that task storage-violation checking at startup is to be activated or deactivated.
CURRENT
All storage areas on the transaction storage chain for the current task only are to be checked.
NONE
Task storage-violation checking is to be deactivated.

You can also use the CICS-supplied transaction, CSFE, to switch task storage-violation checking on and off.

For information about checking for storage violations, see the CICS Transaction Server for z/OS Installation Guide.

Restrictions You can specify the CHKSTSK parameter in PARM, SYSIN, or CONSOLE only.

CICSSVC={216|number}
specifies the number that you have assigned to the CICS type 3 SVC. The default number is 216.

A CICS type 3 SVC with the specified (or default) number must be installed in the LPA. For information about installing the CICS SVC, see CICS Transaction Server for z/OS Installation Guide.

CICS checks if the SVC number supplied corresponds to the correct level of the CICS Type 3 SVC module, DFHCSVC. If the SVC number does not correspond to the correct level of DFHCSVC, the following can happen, depending on the value specified for the PARMERR system initialization parameter:

For details of the PARMERR system initialization parameter, see topic PARMERR.

CILOCK={NO|YES}
specifies whether or not the control interval lock of a non-RLS VSAM file is to be kept after a successful read-for-update request.
NO
is the default and specifies that the control interval is to be freed. This allows other tasks to access other records in the same control interval, without an exclusive control conflict occurring. In these cases throughput should be greater. Note that the record lock on the record for which the read-for-update was first issued, still prevents other tasks from updating this record, even though the control interval lock has been released. When the record is rewritten or deleted, the read-for-update is reissued to VSAM as part of the update processing.

Start of changeIf a WRITE is issued by another task during a READ UDPATE, the WRITE receives a DUPREC condition.End of change

YES
specifies that the control interval is not to be freed. This means that a subsequent rewrite or delete request does not need to reissue the read-for-update request to VSAM. However, if other tasks attempt to access other records in the same control interval, an exclusive control conflict occurs on this control interval, forcing these tasks to wait until the update request completes.
Start of changeCLINTCP={437|codepage} End of change
Start of changespecifies the default client code page to be used by the DFHCNV data conversion table but only if the CLINTCP parameter in the DFHCNV macro is set to SYSDEF. The codepage is a field of up to 8 characters and can take the values supported by the CLINTCP parameter in the DFHCNV macro. See the CICS Family: Communicating from CICS on System/390 for the list of valid code pages. The default is 437.End of change
CLSDSTP={NOTIFY|NONOTIFY}
specifies the notification required for an EXEC CICS ISSUE PASS command. This parameter is applicable to both autoinstalled and non-autoinstalled terminals. You can use the notification in a user-written node error program to reestablish the CICS session when a VTAM CLSDST PASS request resulting from an EXEC CICS ISSUE PASS command fails. For more information about the EXEC CICS ISSUE PASS command, see the CICS Application Programming Reference manual.
NOTIFY
CICS requests notification from VTAM when the EXEC CICS ISSUE PASS command is executed.
NONOTIFY
CICS does not request notification from VTAM.
CLT=xx (alternate)
specifies the suffix for the command list table (CLT), if this SIT is used by an alternate XRF system. The name of the table is DFHCLTxx.

For information about coding the macros for this table, see the CICS Application Programming Reference.

CMDPROT={YES|NO}
specifies that you want to allow, or inhibit, CICS validation of start addresses of storage referenced as output parameters on EXEC CICS commands.
YES
CICS validates the initial byte at the start of any storage that is referenced as an output parameter on EXEC CICS commands to ensure that the application program has write access to the storage. This ensures that CICS does not overwrite storage on behalf of the application program when the program itself cannot do so. If CICS detects that an application program has asked CICS to write into an area to which the application does not have addressability, CICS abends the task with an AEYD abend.

The level of protection against bad addresses depends on the level of storage protection in the CICS environment. The various levels of protection provided when you specify CMDPROT=YES are shown in Table 20.

NO
CICS does not perform any validation of addresses of the storage referenced by EXEC CICS commands. This means that an application program could cause CICS to overwrite storage to which the application program itself does not have write access.
Table 20. Levels of protection provided by CICS validation of application-supplied addresses
  Environment Execution key of affected programs Types of storage referenced by applications that cause AEYD abends
Read-only storage (RENTPGM=PROTECT) CICS-key and user-key CICS key 0 read-only storage (RDSA and ERDSA).
Subsystem storage protection (STGPROT=YES) User-key All CICS-key storage (CDSA and ECDSA)
Transaction isolation (TRANISO=YES) User-key and ISOLATE(YES) Task-lifetime storage of all other transactions
Transaction isolation (TRANISO=YES) User-key and ISOLATE(NO) Task-lifetime storage of all except other user key and ISOLATE(NO) transactions
Base CICS (all storage is CICS key 8 storage) (RENTPGM=NOPROTECT; STGPROT=NO; and TRANISO=NO) CICS-key and user-key MVS storage only
CMDSEC={ASIS|ALWAYS}
specifies whether or not you want CICS to honor the CMDSEC option specified on a transaction’s resource definition.
ASIS
means that CICS honors the CMDSEC option defined in a transaction’s resource definition. CICS calls its command security checking routine only when CMDSEC(YES) is specified in a transaction resource definition.
ALWAYS
CICS overrides the CMDSEC option, and always calls its command security checking routine to issue the appropriate call to the SAF interface.
Notes:
  1. Specify ALWAYS when you want to control the use of the SPI in all your transactions. Be aware that this might incur additional overhead. The additional overhead is caused by CICS issuing the command security calls on every eligible EXEC CICS command, which are all the system programming interface (SPI) commands.
  2. If you specify ALWAYS, command checking applies to CICS-supplied transactions such as CESN and CESF. You must authorize all users of CICS-supplied transactions to use the internal CICS resources for the transactions, otherwise you will get unexpected results in CICS-supplied transactions.

Restrictions You can specify the CMDSEC parameter in the SIT, PARM, or SYSIN only.

CONFDATA={SHOW|HIDETC}
specifies whether CICS is to suppress (hide) user data that might otherwise appear in CICS trace entries or in dumps that contain the VTAM receive any input area (RAIA). This option applies to initial input data received on a VTAM RECEIVE ANY operation, the initial input data received on an MRO link, and FEPI screens and RPLAREAs.

This option also applies to the CICS client use of a Virtual Terminal. Data is traced before and after codepage conversion and is suppressed if HIDETC is used in combination with CONFDATA YES in the transaction.

SHOW
Data suppression is not in effect. User data is traced regardless of the CONFDATA option specified in transaction resource definitions. This option overrides the CONFDATA option in transaction resource definitions.
HIDETC
CICS is to ‘hide’ user data from CICS trace entries. It also indicates that VTAM RAIAs are to be suppressed from CICS dumps. The action actually taken by CICS is subject to the individual CONFDATA attribute on the transaction resource definition (see Table 21).

If you specify CONFDATA=HIDETC, CICS processes VTAM, MRO, and FEPI user data as follows:

  • VTAM: CICS clears the VTAM RAIA containing initial input as soon as it has been processed, and before the target transaction has been identified.

    The normal trace entries (FC90 and FC91) are created on completion of the RECEIVE ANY operation with the text "SUPPRESSED DUE TO CONFDATA=HIDETC IN SIT" replacing all the user data except the first 4 bytes of normal data, or the first 8 bytes of function management headers (FMHs).

    CICS then identifies the target transaction for the data. If the transaction definition specifies CONFDATA(NO), CICS traces the user data that it suppressed from the FC90 trace in the trace entry AP FC92. This trace entry is not created if the transaction is defined with CONFDATA(YES).

  • MRO: CICS does not trace the initial input received on an MRO link.

    The normal trace entries (DD16, DD23, and DD25) are created with the text "SUPPRESSED DUE TO CONFDATA=HIDETC IN SIT" replacing all the user data.

    CICS then identifies the target transaction for the data. If the transaction definition specifies CONFDATA(NO), CICS traces the user data that it suppressed from DD16 in the trace entry AP FC92. This special trace entry is not created if the transaction is defined with CONFDATA(YES).

  • FEPI: FEPI screens and RPL data areas (RPLAREAs) areas are suppressed from all FEPI trace points if CONFDATA(YES) is specified in the transaction resource definition. The user data in the FEPI trace points AP 1243, AP 1244, AP 145E, AP 145F, AP 1460, AP 1461, AP 1595, AP 1596, AP 1597, AP 1598, and AP 1599 is replaced with the message "SUPPRESSED DUE TO CONFDATA=HIDETC IN SIT". If the transaction definition specifies CONFDATA(NO), the FEPI trace entries are created with the user data as normal.

Mirror transactions: The CICS-supplied mirror transaction definitions are specified with CONFDATA(YES). This ensures that, when you specify CONFDATA=HIDETC as a system initialization parameter, CICS regions running mirror transactions suppress user data as described for VTAM and MRO data.

Modified data: By waiting until the transaction has been identified to determine the CONFDATA option, VTAM or MRO data may have been modified (for example, it may have been translated to upper case).

The interaction between the CONFDATA system initialization parameter and the CONFDATA attribute on the transaction resource definition is shown in Table 21.

Table 21. Effect of CONFDATA system initialization and transaction definition parameters
CONFDATA on transaction CONFDATA system initialization parameter
SHOW HIDETC
NO Data not suppressed VTAM RAIAs are cleared.
Initial input of VTAM and MRO data is suppressed from the normal FC90, FC91, DD16, DD23, and DD25 trace entries.
For FC90 and DD16 traces only, suppressed user data is traced separately in an FC92 trace entry.
FEPI screens and RPLAREAs are traced as normal.
YES Data not suppressed VTAM RAIAs are cleared.
All VTAM, MRO, and FEPI user data is suppressed from trace entries.

You cannot modify the CONFDATA option while CICS is running. You must restart CICS to make such a change.

Restrictions You can specify the CONFDATA parameter in the SIT, PARM, and SYSIN only.

CONFTXT={NO|YES}
specifies whether CICS is to prevent VTAM from tracing user data.
NO
CICS does not prevent VTAM from tracing user data.
YES
CICS prevents VTAM from tracing user data.

Restrictions You can specify the CONFTXT parameter in the SIT, PARM, and SYSIN only.

CPSMCONN={NO|CMAS|LMAS|WUI}
specifies whether you want CICS to invoke the specified CICSPlex® SM component to initialize the region as one of the following:
NO
Do not invoke any CICSPlex SM initialization code in this region.
CMAS
Invoke CICSPlex SM code automatically during CICS initialization to initialize the region as a CMAS. The other information CICSPlex SM needs for a CMAS is taken from the CMAS parameters read from the EYUPARM data set, and from resource definitions installed from the CSD from group list EYU310L0.

Specifying CPSMCONN=CMAS is the recommended alternative to specifying the CICSPlex SM CMAS initialization program in a CICS post-initialization program list table (PLTPI).

Note:
If you specify CPSMCONN=CMAS, ensure that your CICS region startup JCL EXEC statement specifies the name of the CICSPlex SM CMAS program, EYU9XECS. For example:
//CMAS    EXEC PGM=EYU9XECS,...,...
LMAS
Invoke CICSPlex SM code automatically during CICS initialization to initialize the region as a local MAS. The other information CICSPlex SM needs for a MAS is taken from the MAS parameters read from the EYUPARM data set, and from resource definitions installed from the CSD from group EYU310G1.

Specifying CPSMCONN=LMAS is the recommended alternative to specifying the CICSPlex SM MAS initialization program in a CICS post-initialization program list table (PLTPI).

WUI
Invoke CICSPlex SM code automatically during CICS initialization to initialize the region as a CICSPlex SM Web User Interface server. The other information CICSPlex SM needs is taken from the MAS and WUI parameters read from the EYUPARM and EYUWUI data sets respectively, and from resource definitions installed from the CSD from groups EYU310G1 and EYU310GW.

Specifying CPSMCONN=WUI is the recommended alternative to specifying the CICSPlex SM MAS and WUI initialization and shutdown programs in initialization and shutdown program list tables (PLTPI and PLTSD).

Note that using the CPSMCONN parameter has the same effect as specifying the relevant CICSPlex SM program in a program list table. This means that MASPLTWAIT and other PLT-related CICSPlex SM parameters are still valid and should be specified as necessary.

For information about starting CICSPlex SM address spaces, see the CICS Transaction Server for z/OS Installation Guide.

Start of changeCRLPROFILE=PROFILENAMEEnd of change
Start of changeSpecifies the 246-character uppercase name of the profile that will be used to authorize CICS to access the certification revocation lists (CRLs) that are stored in an LDAP server. The profile name is specified in the external security manager's LDAPBIND general resource class that contains bind information for an LDAP server.

The profile must contain the name of the LDAP server and the distinguished name and password of a user who is authorized to extract certification revocation lists from it. For more information about setting up the profile, see the CICS RACF Security Guide.

Specifying this parameter means that CICS checks each client certificate during the SSL negotiation for a revoked status using the certificate revocation lists in the LDAP server. If the certificate is revoked, CICS closes the connection immediately.

If the CRLPROFILE parameter is omitted or invalid, or the specified profile contains invalid data, or if the LDAP server identified by the profile is unavailable, CICS does not check the revoked status of certificates during SSL handshakes.

End of change
CSDACC={READWRITE|READONLY}
specifies the type of access to the CSD to be permitted to this CICS region. Note that this parameter is effective only when you start CICS with a START=COLD parameter. If you code START=AUTO, and CICS performs a warm or emergency restart, the file resource definitions for the CSD are recovered from the CICS global catalog. However, you can redefine the type of access permitted to the CSD dynamically with a CEMT SET FILE, or an EXEC CICS SET FILE, command.
READWRITE
Read/write access is allowed, permitting the full range of CEDA, CEDB, and CEDC functions to be used.
READONLY
Read access only is allowed, limiting the CEDA and CEDB transactions to only those functions that do not require write access.
CSDBKUP={STATIC|DYNAMIC}
specifies whether or not the CSD is eligible for BWO. If BWO is wanted, specify CSDBKUP=DYNAMIC.

The CSDBKUP, CSDRECOV, and CSDFRLOG system initialization parameters interact according to how they are specified. For information about their effects when the SIT is assembled and during CICS override processing, see Planning for backup and recovery.

STATIC
All CICS files open for update against the CSD data set must be quiesced before a DFHSM and DFDSS backup of the CSD data set. The files must remain quiesced during the backup.
DYNAMIC
DFHSM and DFDSS are allowed to make a data set back up copy while CICS is updating the CSD.

Note that CSDBKUP=DYNAMIC is valid only if you have also specified CSDRECOV=ALL.

CSDBUFND=number
specifies the number of buffers to be used for CSD data. The minimum you should specify is the number of strings coded on the CSDSTRNO parameter plus 1, up to a maximum of 32768. Note that this parameter is used only if you have also coded CSDLSRNO=NONE; if you have coded CSDLSRNO=number, CSDBUFND is ignored.

If you specify a value for CSDBUFND that is less than the required minimum (the CSDSTRNO value plus 1), VSAM automatically changes the number of buffers to the number of strings plus 1 when CICS issues the OPEN macro for the CSD.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog.

CSDBUFNI=number
specifies the number of buffers to be used for the CSD index. The minimum you should specify is the number of strings coded on the CSDSTRNO parameter, up to a maximum of 32768. This parameter is used only if you have also coded CSDLSRNO=NONE; if you have coded CSDLSRNO=number, CSDBUFNI is ignored.

If you specify a value for CSDBUFNI that is less than the required minimum (the CSDSTRNO value), VSAM automatically changes the number of buffers to the number of strings when CICS issues the OPEN macro for the CSD.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog.

CSDDISP={OLD|SHR}
specifies the disposition of the data set to be allocated to the CSD. If no JCL statement for the CSD exists when it is opened, the open is preceded by a dynamic allocation of the CSD using this disposition. If a DD statement exists in the JCL of the CICS startup job, it takes precedence over this disposition.
OLD
The disposition of the CSD is set to OLD if dynamic allocation is performed.
SHR
The disposition of the CSD is set to SHR if dynamic allocation is performed.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog.

CSDDSN=name
specifies the 1- to 44-character JCL data set name (DSNAME) to be used for the CSD. If no JCL statement exists for the CSD when it is opened, the open is preceded by a dynamic allocation of the CSD using this DSNAME. If a DD statement exists in the JCL of the CICS startup job, it takes precedence over this DSNAME.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog.

CSDFRLOG=number
specifies a number that corresponds to the journal name that CICS uses to identify the forward recovery log stream for the CSD.

This parameter is meaningful only if CSDRECOV=ALL and CSDRLS=NO are specified, otherwise it is ignored. If you specify CSDRLS=NO and CSDRECOV=ALL, but omit CSDFRLOG (or specify CSDFRLOG=NO), the SIT assembly fails. However, if you specify an invalid combination as SIT overrides, CICS initialization will fail.

CSDBKUP, CSDRECOV and CSDFRLOG are ignored if CSDRLS=YES is specified. This is because recovery attributes (that is, the recoverability, the forward recovery LSN, and the BWO eligibility) must be specified in the ICF catalog for data sets that are opened in RLS mode.

The recovery attributes can also be specified (optionally) in the ICF catalog when you specify CSDRLS=NO. If you specify recovery attributes in both the ICF catalog and as system initialization parameters, the ICF catalog values are used (but see the next paragraph).

For a CSD opened in a non-RLS mode (CSDRLS=NO), the CSDBKUP, CSDRECOV, and CSDFRLOG system initialization parameters interact according to how they are specified. For information about their effects when the SIT is assembled and during CICS override processing, see Planning for backup and recovery.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog.

number
The journal number that identifies the user journal that CICS is to use for forward recovery of the CSD. CICS journal names are of the form DFHJnn where nn is a number in the range 1 through 99. CICS maps the resulting journal name (DFHJ01--DFHJ99) to an MVS log stream.
CSDINTEG={UNCOMMITTED|CONSISTENT|REPEATABLE}
specifies the level of read integrity for the CSD if it is accessed in RLS mode. If the CSD is not accessed in RLS mode (CSDRLS=NO), a value for CSDINTEG of CONSISTENT or REPEATABLE will be changed to UNCOMMITTED.
UNCOMMITTED
The CSD is read without read integrity. For each read request, CICS obtains the current value of the record as known to VSAM. No attempt is made to serialize this read request with any concurrent update activity for the same record. The record returned may be a version updated by another RDO task but not yet committed, and this record could change if the update is subsequently backed out.
CONSISTENT
CICS reads the CSD with consistent read integrity. If a record is being modified by another RDO task, the READ request waits until the update is complete, the timing of which depends on whether the CSD is recoverable or non-recoverable:
  • For a recoverable CSD, the READ request completes when the updating transaction completes its next syncpoint or rollback.
  • For a non-recoverable CSD, the READ completes as soon as the VSAM request performing the update completes.
REPEATABLE
CICS reads the CSD with repeatable read integrity. If the record is being modified by another RDO task, the READ request waits until the update is complete, the timing of which depends on whether the CSD is recoverable or non-recoverable:
  • For a recoverable CSD, the READ request completes when the updating transaction completes its next syncpoint or rollback.
  • For a non-recoverable CSD, the READ completes as soon as the VSAM request performing the update completes.

After the CSD read completes, a shared lock remains held until syncpoint. This guarantees that a CSD record read within an RDO task cannot be modified until the end of the task (for example, a CEDA transaction) that is reading the CSD.

CSDJID={NO|number}
specifies the journal identifier of the journal that you want CICS to use for automatic journaling of file requests against the CSD.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog.

NO
You do not want automatic journaling for the CSD. This is the default.
number
A number in the range 1 through 99 to identify the journal that CICS is to use for automatic journaling for the CSD. Mapping to a log stream works in the same way that CSDFRLOG does, that is, nn maps to DFHJnn. 01 no longer maps to the system log.

The automatic journaling options enforced for the CSD when you code CSDJID=number are JNLADD=BEFORE and JNLUPDATE=YES. These options are sufficient to record enough information for a user-written forward recovery utility. No other automatic journaling options are available for the CSD. For information about the options JNLADD=BEFORE and JNLUPDATE=YES, see theCICS Resource Definition Guide.

CSDLSRNO={1|number|NONE|NO}
specifies whether the CSD is to be associated with a local shared resource (LSR) pool.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog. However, you can redefine the LSR pool attribute for the CSD dynamically with an EXEC CICS SET FILE command.

1
The default LSR pool number is 1.
number
The number of the LSR pool the CSD is to be associated with. The number of the pool must be in the range 1 through 8.
NONE|NO
The CSD is not to be associated with a local shared resource pool.
CSDRECOV={NONE|ALL|BACKOUTONLY}
specifies whether the CSD is a recoverable file.

The CSDBKUP, CSDRECOV, and CSDFRLOG system initialization parameters interact according to how they are specified, if CSDRLS=NO is specified. If CSDRLS=YES is specified, these parameters are ignored, because the recovery attributes must be specified in the VSAM catalog (using the BWO, LOG, and LOGSTREAMID parameters on DEFINE CLUSTER or ALTER CLUSTER). If CSDRLS=NO is specified but LOG has been specified in the VSAM catalog, the recovery attributes are taken from the VSAM catalog, and CSDBKUP, CSDRECOV, and CSDFRLOG do not need to be specified. If they are specified, however, the rules given in Planning for backup and recovery must still be followed.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD are recovered from the global catalog.

NONE
The CSD is not recoverable.
ALL
You want both forward recovery and backout for the CSD. If you code ALL, also specify CSDFRLOG with the journal identification of the journal to be used for forward recovery of the CSD.
Note:
If the journal you specify for logstreams associated with CSD recovery (CSDJID, CSDFRLOG, and possibly the log of logs, DFGLGLOG) is a DASD-only log stream, there can be delays when you use the CEDA transaction if the log stream requires a new connection. This delay is because the MVS system logger is formatting the staging dataset. Symptoms of the problem are:
DFHLG0771 07/08/01 03:30:42 IYOT1 A temporary error condition occurred 
during MVS logger operation IXGWRITE for logstream xxxxxx.yyyyyy.zzzzzz.
MVS logger codes: X'00000008', X'00000868'.
If the CSD is the only file using those logstreams, CICS disconnects from the log when you end the CEDA transaction. The next time you run a CEDA transaction, CICS reconnects to the log stream and the MVS system logger allocates and formats a new staging data set.
BACKOUTONLY
CSD recovery is limited to file backout only. If you specify backout for the CSD, CICS uses the system log to record before images for backout purposes.
CSDRLS
specifies whether CICS is to access the CSD in RLS mode.
NO
The CSD is opened in non-RLS mode, as specified on the CSDLSRNO parameter.
YES
The CSD is opened in RLS mode. This enables you to update the CSD concurrently from several CICS regions, provided all the regions specify CSDRLS=YES. If a CICS region opens the CSD in RLS mode, another CICS region cannot open it in non-RLS mode. The first CICS region to open the CSD in a sysplex with SMSVSAM determines the access mode for all regions.

Your CSD must be defined to support RLS access: the IMBED option must not be specified, and recovery attributes must be defined in the VSAM catalog. The CICS Transaction Server for z/OS Installation Guide explains the data set characteristics required to support RLS access. If your CSD does not meet these requirements, it will fail to open.

If you specify both RLS and local shared resource (CSDLSRNO=number), RLS takes precedence.

If you specify CSDRLS=YES, the CSDRECOV, CSDFRLOG, and CSDJID parameters are ignored. You must specify the recovery attributes for an RLS-mode CSD in the ICF catalog entry for the CSD.

Note:
If you define a recoverable CSD for RLS-mode access, you have to quiesce all RLS activity against the CSD before you can update the CSD using the batch utility program, DFHCSDUP. You can use the SET DSNAME QUIESCE command to do this, to ensure that no CEDA, CEDB, or CEDC transactions can run until you unquiesce the data set on completion of the batch job.
CSDSTRNO={6|number}
specifies the number of concurrent requests that can be processed against the CSD. When the number of requests reaches the STRNO value, CICS automatically queues any additional requests until one of the active requests terminates.

CICS requires two strings per CSD user, and you can increase the CSDSTRNO value, in multiples of two, to allow more than one concurrent CEDA user.

See Multiple users of the CSD within a CICS region (non-RLS) before you code this parameter.

This parameter is effective only on a CICS cold or initial start. On a warm or emergency restart, file resource definitions for the CSD 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.

6
The minimum number of concurrent requests for the CSD is 6.
number
This number must be a multiple of 2, in the range 6 through 254.
CWAKEY={USER|CICS}
specifies the storage key for the common work area (CWA) if you are operating CICS with storage protection (STGPROT=YES). (You specify how much storage you want for the CWA on the WRKAREA parameter.) The permitted values are USER (the default), or CICS:
USER
CICS obtains storage for the CWA in user key. This allows a user program executing in any key to modify the CWA.
CICS
CICS obtains storage for the CWA in CICS key. This means that only programs executing in CICS key can modify the CWA, and user-key programs have read-only access.

If CICS is running without storage protection, the CWAKEY parameter is ignored, and the CWA is always allocated from CICS-key storage.

DAE={NO|YES}
specifies the default DAE action when new system dump table entries are created.
NO
New system dump table entries will be created with DAEOPTION(NODAE). This means that the system dump will not be suppressed by the MVS Dump Analysis and Elimination (DAE) component.
YES
New system dump table entries will be created with DAEOPTION(DAE). This means that the system dump is eligible for suppression by the MVS DAE component.
For more information about the DAEOPTION option, see CICS System Programming Reference.
DATFORM={MMDDYY|DDMMYY|YYMMDD}
specifies the external date display standard that you want to use for CICS date displays. An appropriate indicator setting is made in the CSA. It is examined by CICS supplied system service programs that display a Gregorian date. CICS maintains the date in the form 0CYYDDD in the CSA (where C=0 for years 19xx, 1 for years 20xx, and so on; YY=year of century; and DDD=day of year), and converts it to the standard you specify for display.

The DATFORM option selects the order in which the date is to be displayed. It does not select the format of the year. Both YY and YYYY formats are displayed.

MMDDYY
The date is in the form of month-day-year, MMDDYY and MMDDYYYY.
DDMMYY
The date is in the form of day-month-year, DDMMYY and DDMMYYYY.
YYMMDD
The date is in the form of year-month-day, YYMMDD and YYYYMMDD.
DB2CONN={NO|YES}
specifies whether you want CICS to start the DB2® connection automatically during initialization.
NO
Do not automatically invoke DFHD2CM0, the CICS DB2 attach program, during initialization.
YES
Invoke the CICS DB2 attach program, DFHD2CM0, automatically during CICS initialization. The other information CICS needs for starting the attachment is taken from CICS DB2 connection resource definitions installed from the CSD.

Specifying DB2CONN=YES is the recommended alternative to specifying the CICS DB2 attach programs in the CICS post-initialization program list table (PLT).

DBCTLCON={NO|YES}
specifies whether you want CICS to start the DBCTL connection automatically during initialization.
NO
Do not automatically invoke DFHDBCON, the CICS DBCTL attach program, during initialization.
YES
Invoke the CICS DBCTL attach program, DFHDBCON, automatically during CICS initialization. The other information CICS needs for starting the attachment, such as the DRA startup table suffix or the DBCTL subsystem name, is taken from an INITPARM system initialization parameter.

Specifying DBCTLCON=YES means you don't need to define the DBCTL attach program in the CICS post-initialization program list table (PLT).

DEBUGTOOL={NO|YES}
Specifies whether you want to use debugging profiles to select the programs that will run under the control of a debugging tool. The following debugging tools use debugging profiles: Other debugging mechanisms, such as the CICS Execution Diagnostic Facility (CEDF) do not use debugging profiles.
NO
Specifies that you do not want to use CICS debugging profiles to select the programs that will run under the control of a debugger tool.
YES
Specifies that you want to use CICS debugging profiles to select the programs that will run under the control of a debugging tool.
For more information, see the CICS Application Programming Guide.
DFLTUSER={CICSUSER|userid}
specifies the RACF® userid of the default user; that is, the user whose security attributes are used to protect CICS resources in the absence of other, more specific, user identification. For example, except in the case of terminals defined with preset security, the security attibutes of the default user are assigned to terminal users who do not sign on.

The specified userid must be defined to RACF if you are using external security (that is, you have specified the system initialization parameter SEC=YES).

The specified userid is signed on during CICS initialization. If it cannot be signed on, CICS fails to initialize.

Restrictions You can specify the DFLTUSER parameter in the SIT, PARM, or SYSIN only.

DIP={NO|YES}
specifies whether the batch data interchange program, DFHDIP, is to be included. This supports the batch controller functions of the IBM® 3790 Communication System and the IBM 3770 Data Communication System. (Support is provided for the transmit, print, message, user, and dump data sets of the 3790 system.) (For the effect of this parameter, see topic Defining CICS resource table and module keywords.)
DISMACP={YES|NO}
specifies whether CICS is to disable any transaction that terminates abnormally with an ASRD or ASRE abend (caused by a user program invoking a CICS macro, or referencing the CSA, the TCA, or the DB2 RCT).
Note:
DISMACP=YES has no effect if the ASRD or ASRE abend is handled by an active abend exit.
DOCCODEPAGE={037|codepage}
specifies the default host code page to be used by the document domain. The codepage is a field of up to 8 characters. If codepage value is not specified, the default doccodepage is set to 037. See the CICS Family: Communicating from CICS on System/390 for the list of valid code pages.
DSALIM={5M|number}
specifies the upper limit of the total amount of storage within which CICS can allocate the individual dynamic storage areas (DSAs) that reside below the 16MB boundary.
5M
The default DSA limit is 5MB (5 242 880).
number
This is the amount of storage in the range 2MB to 16MB (2 097 152 bytes to 16 777 216 bytes) in multiples of 262 144 bytes (256KB). If the size specified is not a multiple of 256KB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4 194 304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

From the storage size that you specify on the DSALIM parameter, CICS allocates the following dynamic storage areas:

The user DSA (UDSA)
The user-key storage area for all user-key task-lifetime storage below the 16MB boundary.
The read-only DSA (RDSA)
The key-0 storage area for all reentrant programs and tables below the 16MB boundary.
The shared DSA (SDSA)
The user-key storage area for any non-reentrant user-key RMODE(24) programs, and also for any storage obtained by programs issuing EXEC CICS GETMAIN commands for storage below the 16MB boundary with the SHARED option.
The CICS DSA (CDSA)
The CICS-key storage area for all non-reentrant CICS-key RMODE(24) programs, all CICS-key task-lifetime storage below the 16MB boundary, and for CICS control blocks that reside below the 16MB boundary.
Notes:
  1. CICS allocates the UDSA in multiples of 1MB when transaction isolation is active, but in multiples of 256KB in CICS regions without transaction isolation. The other DSAs below 16MB are allocated in multiples of 256KB, with or without transaction isolation. The maximum you can specify depends on a number of factors, such as how you have configured your MVS storage (which governs how much private storage remains below the line) and how much private storage you must leave free to satisfy MVS GETMAIN requests for storage outside the DSAs.
  2. For information about calculating the amount of storage to specify on the DSALIM parameter, see the CICS Performance Guide.
  3. Dynamic changes to the DSA limit are cataloged in the local catalog, and override the DSALIM parameter, if it is specified in the system initialization table, during all forms of restart-initial, cold, and warm. The cataloged value is not used if:
    • You specify startup values as system initialization parameters overrides (for example, in SYSIN).
    • You re-initialize the CICS catalog data sets.
DSHIPIDL={020000|hhmmss}
specifies the minimum time, in hours, minutes, and seconds, that an inactive shipped terminal definition must remain installed in this region. When the timeout delete mechanism is invoked, only those shipped definitions that have been inactive for longer than the specified time are deleted.

You can use this parameter in a transaction routing environment, on the application-owning and intermediate regions, to prevent terminal definitions having to be reshipped because they have been deleted prematurely.

The default minimum idle time is 2 hours.

hhmmss
A 1- to 6-digit number in the range 0-995959. Numbers that have fewer than six digits are padded with leading zeros.
DSHIPINT={120000|0|hhmmss}
specifies the interval between invocations of the timeout delete mechanism. The timeout delete mechanism removes any shipped terminal definitions that have not been used for longer than the time specified by the DSHIPIDL parameter.

You can use this parameter in a transaction routing environment, on the application-owning and intermediate regions, to control:

0
The timeout delete mechanism is not invoked. You might set this value in a terminal-owning region, or if you are not using shipped definitions.
hhmmss
A 1- to 6-digit number in the range 1-995959. Numbers that have fewer than six digits are padded with leading zeros.
DSRTPGM={NONE|DFHDSRP|program-name|EYU9XLOP}
specifies the name of the distributed routing program to be used for dynamically routing:
DFHDSRP
The CICS sample distributed routing program.
EYU9XLOP
The CICSPlex SM routing program.
NONE
For eligible CICS BTS processes and activities, no routing program is invoked. BTS processes and activities cannot be dynamically routed.

For eligible non-terminal-related START requests, the CICS sample distributed routing program, DFHDSRP, is invoked.

program-name
The name of a user-written program.
Note:
See also the DTRPGM parameter, used to name the dynamic routing program.
DTRPGM={DFHDYP|program-name}
specifies the name of the dynamic routing program to be used for dynamically routing:

DFHDYP, the default, is the name of the CICS-supplied program. For information about which transactions started by EXEC CICS START commands, and which program-link requests, are eligible for dynamic routing, see the CICS Intercommunication Guide.

Note:
See also the DSRTPGM parameter, used to name the distributed routing program.
DTRTRAN={CRTX|name|NO}
specifies the name of the transaction definition that you want CICS to use for dynamic transaction routing. This is intended primarily for use in a CICS terminal-owning region, although you can also use it in an application-owning region when you want to daisy-chain transaction routing requests. In a dynamic transaction routing environment, the transaction named on DTRTRAN must be installed in the CICS terminal-owning regions if you want to eliminate the need for resource definitions for individual transactions.
Note:
DTRTRAN does not apply to non-terminal EXEC CICS START requests where the distributed routing program is invoked.

The transaction name is stored in the catalog for recovery during CICS restarts.

CRTX
This is the default dynamic transaction definition. It is the name of the CICS-supplied sample transaction resource definition provided in the CSD group DFHISC.
name
The name of your own dynamic transaction resource definition that you want CICS to use for dynamic transaction routing.
NO
The dynamic transaction routing program is not invoked when a transaction definition cannot be found.

For information about the CICS-supplied sample transaction resource definition, CRTX, and about defining your own dynamic transaction routing definition, see Links and sessions in the CICS Resource Definition Guide.

DUMP={YES|NO} (active and alternate)
specifies whether the CICS dump domain is to take SDUMPs.
YES
SDUMPs are produced, unless suppressed by the options specified in the CICS system dump table or by the MVS system defaults.
NO
SDUMPs are suppressed.
Note:
This does not prevent the CICS kernel from taking SDUMPs.

For more information about SDUMPs, see System dumps.

DUMPDS={AUTO|A|B}
specifies the transaction dump data set that is to be opened during CICS initialization.
AUTO
For all emergency or warm starts, CICS opens the transaction dump data set that was not in use when the previous CICS run terminated. This information is obtained from the CICS local catalog.

If you specify AUTO, or let it default, code DD statements for both of the transaction dump data sets, DFHDMPA and DFHDMPB, in your CICS startup job stream.

A
CICS opens transaction dump data set DFHDMPA.
B
CICS opens transaction dump data set DFHDMPB.
DUMPSW={NO|NEXT}
specifies whether you want CICS to switch automatically to the next dump data set when the first is full.
NO
Disables the CICS autoswitch facility. If the transaction dump data set opened during initialization becomes full, CICS issues a console message to notify the operator. If you want to switch to the alternate data set, you must do so manually using the CEMT or EXEC CICS SET DUMPDS SWITCH command.
NEXT
Enables the autoswitch facility to switch to the next data set at end of file of the data set opened during initialization. Coding NEXT permits one switch only. If you want to switch to the alternate data set again, you must do so manually using CEMT or EXEC CICS SET DUMPDS SWITCH command. If you specify NEXT, code DD statements for both of the transaction dump data sets, DFHDMPA and DFHDMPB, in your CICS startup job stream.

For more information about transaction dump data sets, see topic The CICS transaction dump data sets.

DURETRY={30|number-of-seconds|0}
specifies, in seconds, the total time that CICS is to continue trying to obtain a system dump using the SDUMP macro. DURETRY allows you to control whether, and for how long, CICS is to reissue the SDUMP macro if another address space in the same MVS system is already taking an SDUMP when CICS issues an SDUMP request.

In the event of an SDUMP failure, CICS responds, depending on the reason for the failure, as follows:

30
30 seconds allows CICS to retry up to 6 times (once every 5 seconds), if the cause of failure is that another region is taking an SDUMP.
number-of-seconds
Code the total number of seconds (up to 32767) during which you want CICS to continue retrying the SDUMP macro if the reason for failure is that another region is taking an SDUMP. CICS retries the SDUMP, once every five seconds, until successful or until retries have been made over a period equal to or greater than the DURETRY value.
0
Code a zero value if you do not want CICS to retry the SDUMP macro.
ECDSASZE={0K|number}
specifies the size of the ECDSA. The default size is 0 indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
Specify number as an amount of storage in the range 0 to 1073741824 bytes in multiples of 1048576 bytes (1MB). If the size specified is not a multiple of 1MB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Note:
Start of change
For the DS domain function CHANGE_MODE, a trace entry will be generated if DS level 2, 3, or ALL tracing is active.
End of change

Restrictions You can specify the ECDSASZE parameter in PARM, SYSIN, or CONSOLE only.

EDSALIM={30M|number}
specifies the upper limit of the total amount of storage within which CICS can allocate the individual extended dynamic storage areas (EDSAs) that reside above the 16MB boundary.
30M
The default EDSA limit is 30MB (31 457 280 bytes).
number
Specify number as a value in the range 10MB to 2047MB, in multiples of 1MB. If the size specified is not a multiple of 1MB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 33 554 432), or as a whole number of kilobytes (for example, 32 768K), or a whole number of megabytes (for example, 32M).

The maximum value allowed depends on a number of factors, such as:

  • The size of the region you have specified on the MVS REGION parameter in the CICS job or procedure
  • How much storage you require for the CICS internal trace table
  • How much private storage you must leave free to satisfy MVS GETMAIN requests for storage above the 16MB boundary outside the DSAs

From the storage value that you specify on the EDSALIM parameter, CICS allocates the following extended dynamic storage areas:

The extended user DSA (EUDSA)
The user-key storage area for all user-key task-lifetime storage above the 16MB boundary.
The extended read-only DSA (ERDSA)
The key-0 storage area for all reentrant programs and tables above the 16MB boundary.
The extended shared DSA (ESDSA)
The user-key storage area for any non-reentrant user-key RMODE(ANY) programs, and also for any storage obtained by programs issuing CICS GETMAIN commands for storage above the 16MB boundary with the SHARED option.
The extended CICS DSA (ECDSA).
The CICS-key storage area for all non-reentrant CICS-key RMODE(ANY) programs, all CICS-key task-lifetime storage above the 16MB boundary, and CICS control blocks that reside above the 16MB boundary.

CICS allocates all the DSAs above the 16MB boundary in multiples of 1MB.

Notes:
  1. For information about calculating the amount of storage to specify on the EDSALIM parameter, see the CICS Performance Guide
  2. Dynamic changes to the EDSA limit are cataloged in the local catalog, and override the DSALIM parameter, if it is specified in the system initialization table, during all forms of restart-initial, cold, and warm. The cataloged value is not used if:

    • You specify startup values as system initialization parameters overrides (for example, in SYSIN).
    • You re-initialize the CICS catalog data sets.
EJBROLEPRFX=ejbrole-prefix
Specifies a prefix that is used to qualify the security role defined in an enterprise bean's deployment descriptor. The prefix is applied to the security role: For more information about how the EJBROLEPRFX parameter is used to qualify security roles for enterprise beans, see Java Applications in CICS.

You can specify a prefix of up to 16 characters. The prefix must not contain a period (.) character. If you specify a prefix that contains lower case characters, blanks, or punctuation characters, you must enclose it in apostrophes. If the prefix contains an apostrophe, code two successive apostrophes to represent it.

Restrictions:
  1. You can specify the EJBROLEPRFX parameter in the SIT, PARM, or SYSIN only.
  2. The EJBROLEPRFX parameter is ignored if security role support is not enabled. To enable security role support you must specify SEC=YES and XEJB=YES.
Start of changeENCRYPTION={ STRONG|WEAK|MEDIUM}End of change
Start of changeSpecifies the cipher suites that CICS uses for secure TCP/IP connections. When a secure connection is established between a pair of processes, the most secure cipher suite supported by both is used.

For compatibility with previous releases, ENCRYPTION=NORMAL is accepted as an equivalent to ENCRYPTION=MEDIUM. For more information about cipher suites, see CICS RACF Security Guide.

CICS can use only the cipher suites that are supported by the underlying z/OS operating system. For an up to date list of the cipher suites that are supported, check the appropriate z/OS documentation.

Possible values for z/OS 1.9 are:

STRONG
Specifies that CICS should use the following cipher suites:
Cipher suite Encryption algorithm Key length MAC algorithm Key exchange
01 No encryption MD5 None
02 No encryption SHA-1 None
03 RC4 40 bits MD5 RSA
04 RC4 128 bits MD5 RSA
05 RC4 128 bits SHA-1 RSA
06 RC2 40 bits MD5 RSA
09 DES 56 bits SHA-1 RSA
0A 3DES 168 bits SHA-1 Fixed Diffie-Hellman key exchange using DSS certificate
0C DES 56 bits SHA-1 Fixed Diffie-Hellman key exchange using DSS certificate
0D 3DES 168 bits SHA-1 Fixed Diffie-Hellman key exchange using DSS certificate
0F DES 56 bits SHA-1 Fixed Diffie-Hellman key exchange using RSA certificate
10 3DES 168 bits SHA-1 Fixed Diffie-Hellman key exchange using RSA certificate
12 DES 56 bits SHA-1 Ephemeral Diffie-Hellman key exchange using DSS certificate
13 3DES 168 bits SHA-1 Ephemeral Diffie-Hellman key exchange using DSS certificate
15 DES 56 bits SHA-1 Ephemeral Diffie-Hellman key exchange using RSA certificate
16 3DES 168 bits SHA-1 Ephemeral Diffie-Hellman key exchange using RSA certificate
2F AES 128 bits SHA-1 Fixed Diffie-Hellman key exchange using DSS certificate
30 AES 128 bits SHA-1 Fixed Diffie-Hellman key exchange using DSS certificate
31 AES 128 bits SHA-1 Fixed Diffie-Hellman key exchange using RSA certificate
32 AES 128 bits SHA-1 Ephemeral Diffie-Hellman key exchange using DSS certificate
33 AES 128 bits SHA-1 Ephemeral Diffie-Hellman key exchange using RSA certificate
35 AES 256 bits SHA-1 RSA
36 AES 256 bits SHA-1 Fixed Diffie-Hellman key exchange using DSS certificate
37 AES 256 bits SHA-1 Fixed Diffie-Hellman key exchange using RSA certificate
38 AES 256 bits SHA-1 Ephemeral Diffie-Hellman key exchange using DSS certificate
39 AES 256 bits SHA-1 Ephemeral Diffie-Hellman key exchange using DSS certificate
The terms used in this table are:
AES
Advanced Encryption Standard
DES
Data Encryption Standard
DSS
Digital Signature Standard
MD5
Message Digest algorithm
RC2, RC4
Rivest encryption
RSA
Rivest-Shamir-Adleman encryption
SHA-1
Secure Hash algorithm
3DES
DES applied three times
WEAK
Specifies that CICS should use the following cipher suites:
Cipher suite Encryption algorithm Key length MAC algorithm
01 No encryption MD5
02 No encryption SHA
03 RC4 40 bits MD5
06 RC2 40 bits MD5
The terms used in this table are:
MD5
Message Digest algorithm
SHA
Secure Hash algorithm
RC2, RC4
Rivest encryption
MEDIUM
Specifies that CICS should use the following cipher suites:
Cipher suite Encryption algorithm Key length MAC algorithm
01 No encryption MD5
02 No encryption SHA
03 RC4 40 bits MD5
06 RC2 40 bits MD5
09 DES 56 bits SHA
The terms used in this table are:
MD5
Message Digest algorithm
SHA
Secure Hash algorithm
RC2, RC4
Rivest encryption
DES
Data Encryption Standard
End of change
EODI={E0|xx}
specifies the end-of-data indicator for input from sequential devices. The characters "xx" represent two hexadecimal digits in the range 01 through FF. The default value is X'E0', which represents the standard EBCDIC backslash symbol (\).
ERDSASZE={0K|number}
specifies the size of the ERDSA. The default size is 0 indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
Specify number as an amount of storage in the range 0 to 1073741824 bytes in multiples of 1048576 bytes (1MB). If the size specified is not a multiple of 1MB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Restrictions You can specify the ERDSAZSE parameter in PARM, SYSIN, or CONSOLE only.

ESDSASZE={0K|number}
specifies the size of the ESDSA. The default size is 0 indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
Specify number as an amount of storage in the range 0 to 1073741824 bytes in multiples of 1048576 bytes (1MB). If the size specified is not a multiple of 1MB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Restrictions You can specify the ESDSAZSE parameter in PARM, SYSIN, or CONSOLE only.

ESMEXITS={NOINSTLN|INSTLN}
specifies whether installation data is to be passed through the RACROUTE interface to the external security manager (ESM) for use in exits written for the ESM.
NOINSTLN
The INSTLN parameter is not used in RACROUTE macros.
INSTLN
CICS-related and installation-supplied data is passed to the ESM using the INSTLN parameter of the RACROUTE macro. For programming information, including the format of the data passed, see the CICS Customization Guide. This data is intended for use in exits written for the ESM.

Restrictions You can specify the ESMEXITS parameter in the SIT only.

EUDSASZE={0K|number}
specifies the size of the EUDSA. The default size is 0 indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
Specify number as an amount of storage in the range 0 to 1073741824 bytes in multiples of 1048576 bytes (1MB). If the size specified is not a multiple of 1MB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Restrictions You can specify the EUDSAZSE parameter in PARM, SYSIN, or CONSOLE only.

FCT={NO|xx|YES}
specifies the suffix of the file control table to be used.

This parameter is effective only on a CICS cold or initial start. CICS does not load an FCT on a warm or emergency restart, and all file resource definitions are recovered from the global catalog.

For information about coding the macros for this table, see the CICS Resource Definition Guide.

You can use a mixture of macro definitions and RDO definitions for files in your CICS region. However, your FCT should contain definitions for only BDAM files to be loaded on a CICS cold start. Other types of files are loaded from their file definitions in RDO groups specified in the GRPLIST system initialization parameter. Any definitions in the FCT other than for BDAM files are ignored.

FEPI={NO|YES}
specifies whether or not you want to use the Front End Programming Interface feature (FEPI).
NO
FEPI support is not required. You should specify NO on this parameter (or allow it to default) if you do not have the feature installed, or if you do not require FEPI support.
YES
You require FEPI support, and CICS is to start the CSZI transaction.

This book does not contain any information about the installation process for the Front End Programming Interface feature. Installation information can be found in the CICS Front End Programming Interface User’s Guide.

FLDSEP={‘ ’|‘xxxx’
specifies one through four field-separator characters, each of which indicates end of field in the terminal input data. The default is four blanks.

The field separator allows you to use transaction identifications of less than four characters followed by one of the separator characters. When less than four characters are coded, the parameter is padded with blanks, so that the blank is then a field separator. None of the specified field separator characters should be part of a transaction identification; in particular, the use of alphabetic characters as field separators is not recommended.

The character specified in the FLDSEP parameter must not be the same as any character specified in the FLDSTRT parameter. This means that it is invalid to allow both parameters to take the default value. Restrictions

If you specify FLDSEP in the SIT, the characters must be enclosed in single quotation marks.

If you specify FLDSEP as a PARM, SYSIN, or CONSOLE parameter, do not enclose the characters in quotation marks, and the characters you choose must not include an embedded blank, or any of these characters:

(  )  '  =  ,
FLDSTRT={‘ ’|‘x’}
specifies a single character to be the field-name-start character for free-form input for built-in functions. The default is a blank.

The character specified should not be part of a transaction identification; in particular, the use of alphabetic characters is not recommended.

The character specified in the FLDSTRT parameter must not be the same as any character specified in the FLDSEP parameter. This means that it is invalid to allow both parameters to take the default value.

Restrictions

If you specify FLDSTRT in the SIT, the parameter must be enclosed in single quotation marks.

If you specify FLDSTRT as a PARM, SYSIN, or CONSOLE parameter, do not enclose the character in quotation marks, and the character you choose must not be a blank or any of the following characters:

(  )  '  = ,
FORCEQR={NO|YES}
Specifies whether you want CICS to force all Start of change CICSAPI End of changeuser application programs that are specified as threadsafe to run under the CICS QR TCB, as if they were specified as quasi-reentrant programs. This parameter applies to all application programs that are restricted to the current CICS programming interfacesStart of change ( that is, those which specify API(CICSAPI) )End of change, and does not apply to Start of changeany of the following:End of change Start of change none of which can run on the QR TCB.End of change
NO
CICS is to honor the CONCURRENCY(THREADSAFE) attribute on program resource definitions, and allow user application programs to run on an open TCB to avoid unnecessary TCB switching.
YES
CICS is to force all Start of change CICSAPI End of changeuser application programs specified with the CONCURRENCY(THREADSAFE) attribute to run under the CICS QR TCB, as if they were specified as CONCURRENCY(QUASIRENT) programs

FORCEQR=YES will allow you, in a test environment, to run incompletely tested threadsafe application programs that have proved to be non-threadsafe.

FORCEQR will apply to all programs defined as threadsafe that are not invoked as task-related user exits, global user exits, or user-replaceable modules.

FSSTAFF={YES|NO}
specify this parameter in an application-owning region (AOR) to prevent transactions initiated by function-shipped EXEC CICS START requests being started against incorrect terminals.

You may need to code the function-shipped START affinity (FSSTAFF) parameter in an AOR if all of the following are true:

  1. The AOR is connected to two or more terminal-owning regions (TORs) that use the same, or a similar, set of terminal identifiers.
  2. One or more of the TORs issues EXEC CICS START requests for transactions in the AOR.
  3. The START requests are associated with terminals.
  4. You are using shippable terminals, rather than statically defining remote terminals in the AOR.

Consider the following scenario:

Terminal-owning region TOR1 issues an EXEC CICS START request for transaction TRAR, which is owned by region AOR1. It is to be run against terminal T001. Meanwhile, terminal T001 on region TOR2 has been transaction routing to AOR1; a definition of T001 has been shipped to AOR1 from TOR2. When the START request arrives at AOR1, it is shipped to TOR2, rather than TOR1, for transaction routing from terminal T001.

To prevent this situation, code YES on the FSSTAFF parameter in the AOR.

YES
When a START request is received from a terminal-owning region, and a shipped definition for the terminal named on the request is already installed in the AOR, the request is always shipped back to a TOR, for routing, across the link it was received on, irrespective of the TOR referenced in the remote terminal definition.

If the TOR to which the START request is returned is not the one referenced in the installed remote terminal definition, a definition of the terminal is shipped to the AOR, and the autoinstall user program is called. Your autoinstall user program can then allocate an alias termid in the AOR, to avoid a conflict with the previously installed remote definition. For information about writing an autoinstall program to control the installation of shipped definitions, see the CICS Customization Guide.

NO
When a START request is received from a terminal-owning region, and a shipped definition for the named terminal is already installed in the AOR, the request is shipped to the TOR referenced in the definition, for routing.
Notes:
  1. FSSTAFF has no effect:
    • On statically-defined (hard-coded) remote terminal definitions in the AOR. If you use these, START requests are always shipped to the TORs referenced in the definitions.
    • On START requests issued in the local region. It affects only START requests shipped from other regions.
    • When coded on intermediate regions in a transaction-routing path. It is effective only when coded on an application-owning region.
  2. If the AOR contains no remote definition of a terminal named on a shipped START request, the "terminal not known" global user exits, XICTENF and XALTENF, are called. For details of these exits, see the CICS Customization Guide.
FTIMEOUT={30|nn}
specifies a timeout interval for requests made on files that are opened in RLS mode. The interval is in seconds, from 1 through 4080 (sixty eight minutes) and indicates how long VSAM should wait before terminating a request and returning an exception condition.

The default is 30 seconds.

FTIMEOUT applies to transactions that do not have a deadlock timeout interval active. If the DTIMOUT keyword of the TRANSACTION definition is specified, it is used as the file timeout value for that transaction.

GMTEXT={‘DFHZC2312 *** WELCOME TO CICS ***’|‘text’}
specifies whether the default logon message text (WELCOME TO CICS) or your own message text is to be displayed on the screen by the CSGM (good morning) transaction when a terminal is logged on to CICS through VTAM, by the CESN transaction if used to sign on to CICS, or by your own transactions using the EXEC CICS INQUIRE SYSTEM GMMTEXT command.

You can use apostrophes to punctuate your message, in addition to using them as message delimiters. However, you must code two successive apostrophes to represent a single apostrophe in your text. For example,

GMTEXT='User''s logon message text.'

The whole message must still be enclosed by a pair of single delimiting apostrophes.

Your message text can be from 1 through 246 characters (bytes), and can extend over two lines by extending the text to column 80 on the first line, and continuing in column 1 of the second line. For example, the following might be used in the SYSIN data set:

*           CICS Transaction Server for z/OS, Version 3 Release 1 SYSTEM    *
GMTEXT='An Information Development CICS Terminal-Owning Region (TOR) - C
ICSIDC. This message is to show the use of continuation lines when creating a GM
TEXT parameter in the SYSIN data set'  (for first signon
 

The CSGM transaction displays this as follows (with the time appended to the end of message):

 An Information Development CICS Terminal-Owning Region (TOR) - C
 ICSIDC. This message is to show the use of continuation lines when creating a GM
 TEXT parameter in the SYSIN data set 09:56:14

The CESN transaction displays this as follows:

 Signon for CICS Transaction Server for z/OS, Version 3 Release 1 APPLID CICSHTH1
 
An Information Development CICS Terminal-Owning Region (TOR) - CICSIDC.
This message is to show the use of continuation lines when creating a GMTEXT
parameter in the SYSIN data set

For any transaction other than CESN that displays the text specified by this parameter, you must use a TYPETERM with LOGONMSG(YES) for all terminals requiring the logon message. For information about using TYPETERM, see the CICS Resource Definition Guide.

GMTRAN={CSGM|CESN|transaction-id}
specifies the name of the transaction that is:
  1. initiated by ATI when terminals are logged on to CICS by VTAM, and LOGONMSG(YES) is specified in the TYPETERM definition.
  2. set to be the next transaction initiated by the terminal operator following expiry of the terminal user's TIMEOUT period (specified in the External Security Manager) and either:
    • LOGONMSG(YES) and SIGNOFF(YES)
      or
    • LOGONMSG(YES), SIGNOFF(LOGOFF) and DISCREQ(NO)
    is specified in the TYPETERM definition.
§ initiated when terminals are logged on to CICS by VTAM. Do not specify the name of a remote transaction. The transaction must be capable of being automatically initiated (ATI). The default is the transaction CSGM, that displays the text specified in the GMTEXT parameter. Alternatively, you can specify the CICS signon transaction, CESN, which also displays the text specified in the GMTEXT parameter. The GMTRAN parameter can be used with the LGNMSG parameter to retrieve VTAM logon data.
GNTRAN={NO|transaction_id}
specifies the transaction that you want CICS to invoke when a user’s terminal-timeout period expires.
NO
The default value, NO, specifies that no special transaction is to be executed when the timeout period expires. Instead, the user is signed off (subject to the SIGNOFF attribute of the TYPETERM resource definition for the terminal, as described below). After the signoff, if the LOGONMSG(YES) option is specified in the TYPETERM resource definition for the terminal, the transaction specified in the GMTRAN system initialization parameter is executed.
transaction_id
The name of a timeout transaction to signoff the user at the timed-out terminal. You can specify CESF as the timeout transaction. Specifying your own transaction allows you to specify functions in addition to, or instead of, signoff. For example, your own transaction could issue a prompt for the terminal user’s password, and allow the session to continue if the correct password is entered.

The transaction to be used must have been specially written to handle the GNTRAN commarea that is passed to it. Of the CICS-supplied transactions, only CESF has been written to handle the GNTRAN commarea. For more information about writing your own transactions for GNTRAN, see the CICS Customization Guide.

Note:
When either the CICS CESF transaction, or your own transaction, attempts to sign off a terminal, the result is subject to the SIGNOFF attribute of the TYPETERM resource definition for the terminal, as follows:
SIGNOFF
Effect
YES
The terminal is signed off, but not logged off.
NO
The terminal remains signed on and logged on.
LOGOFF
The terminal is both signed off and logged off.
Note:
If GNTRAN fails to attach, and SIGNOFF(LOGOFF) has been specified, the terminal which has reached timeout will be signed off and logged off. GNTRAN will not run and will have no effect.
GRNAME=name
specifies the VTAM generic resource name, as 1 through 8 characters, under which a group of CICS terminal-owning regions in a CICSplex register to VTAM.

There is no default for GRNAME. If you do not specify GRNAME, CICS does not register itself with the VTAM generic resources function. Do not confuse the term generic applid with generic resource name. Generic applids apply only to CICS regions that use XRF. Generic resource names apply only to VTAM generic resource groups.

Notes:
  1. If you are operating a CICSplex that comprises separate terminal-owning regions and application-owning regions, you should ensure that you define a VTAM generic resource name to the CICS terminal-owning regions only.
  2. If you specify the XRF=YES parameter, you should not specify a value for the GRNAME system initialization parameter. Any value specified for GRNAME is set to blanks.
  3. If you specify the XRF=NO parameter, and a value for GRNAME, you should not specify a specific applid (name2) for the APPLID system initialization parameter. Any specific applid (name2) specified for the APPLID parameter is used for the generic applid (name1); that is, the CICS region will be known to VTAM by the value of the specific applid.
  4. Generic resource names must be unique within a single network. A generic resource cannot be identical to:
    • A USERVAR
    • An alias name
    • A real LU name
    Note:
    It is the responsibility of the user to see that these rules are kept.
  5. The first character of the GRNAME cannot be a number.

For example, a CICS region with the system initialization parameters:

APPLID=CICSHTH1
GRNAME=CICSH###

would register to VTAM with the applid CICSHTH1 and the generic resource CICSH###. Other LUs in the same sysplex can communicate with the CICS region either through the generic resource or the applid.

The examples used here are based on a CICS naming convention described in the MVS Sysplex Application Migration manual.

However, care should be taken with LU6 connections initiated from this side (such as AUTOCONNECT(YES)) because the bind will now contain the generic resource name and may fail if the partner only knows this region by the applid. Binds initiated from the partner are examined to identify the name by which the partner knows this region (generic resource or applid), thus allowing the appropriate connection to be built. Recommendations on defining connections can be found in the CICS Intercommunication Guide.

Note:
There are rules that restrict CICS use of the VTAM generic resources function; for more information see the CICS Intercommunication Guide.
GRPLIST={DFHLIST |name|(name[,name2][,name3][,name4])}
specifies the names (each 1 through 8 characters) of up to four lists of resource definition groups on the CICS system definition (CSD) file. The resource definitions in all the groups in the specified lists are loaded during initialization when CICS performs a cold start. If a warm or emergency start is performed, the resource definitions are derived from the global catalog, and the GRPLIST parameter is ignored.

Each name can be either a real group list name or a generic group list name that incorporates global filename characters (+ and *). If you specify more than one group list (either by specifically coding two or more group list names or by coding a group list name with global filename characters), the later group lists are concatenated onto the first group list. Any duplicate resource definitions in later group lists override those in earlier group lists.

Use the CEDA command LOCK to protect the lists of resource groups specified on the GRPLIST parameter.

The default is DFHLIST, the CICS-supplied list that specifies the set of resource definitions needed by CICS. If you create your own group list, either add to it the groups specified in DFHLIST (omitting only those for CICS functions that you know you do not need) or specify the DFHLIST name on the GRPLIST parameter. Do not code GRPLIST=NO unless you have a group list named NO.

Notes:
  1. Group lists specified by a generic group list name are concatenated in alphabetic then numeric order. For example, the generic list name CICSHT* would concatenate the group lists CICSHT#1, CICSHTAP, CICSSD, and CICSHT3V in that order. If the order of concatenation is important (for example, to ensure that a particular resource definition overrides another), you should consider coding real group list names.
  2. If a group list contains resource definitions that are needed by another group list, the group list containing those definitions must be installed first. For example, if list A has TYPETERM definitions needed for TERMINAL definitions in list B, list A must be installed first. This may mean that you have to specifically name the prerequisite group on the GRPLIST parameter.
  3. Take care when using generic group list names, because if a group list on your CSD satisfies the generic name, it will be installed. This means that a group list can be installed more than once; for example, if you specify the real group list name and a generic group list name that it satisfies, or if you specify two generic group list names that the group list name satisfies.
  4. To override one or more of the group lists specified on the GRPLIST system initialization parameter, you must specify all list names (both real and generic) that you want to use, even if you are not changing the names.

For example, if you want to use the four group lists CICSHT#1, CICSHTAP, CICSHT3V, and CICSHTSD, you could specify either of the following system initialization parameters:

GRPLIST=(CICSHT#1,CICSHTAP,CICSHT3V,CICSHTSD)
GRPLIST=(CICSHT*)

In the first example GRPLIST, the group lists are loaded in the order specified, and resource definitions installed from the CICSHTSD group list will override any duplicate definitions installed by the other groups.

In the second example GRPLIST, the group lists are loaded in the order CICSHT#1, CICSHTAP, CICSHTSD, then CICSHT3V, and resource definitions installed from the CICSHT3V group list will override any duplicate definitions installed by the other groups.

If your SIT contains the parameter:

GRPLIST=(CICSHT#1,CICSAP*,CICSHT3V,CICSHTSD)

and you want to replace the list CICSHT3V with the list ANOLST05, you should specify the override:

GRPLIST=(CICSHT#1,CICSAP*,ANOLST05,CICSHTSD)

In general, any required resource definitions should appear in one of the group lists specified on the GRPLIST system initialization parameter.

For information about resource definitions, groups, lists, and the CSD, see the CICS Resource Definition Guide.

GTFTR={OFF|ON}
specifies whether CICS can use the MVS generalized trace facility (GTF) as a destination for trace data.

This parameter controls whether any of the three types of CICS trace entry are written to GTF data sets. The three types are: CICS system trace (see the SYSTR parameter), user trace (see the USERTR parameter), and exception trace entries (which are always made and not controlled by a system initialization parameter).

OFF
CICS does not use GTF as a destination for CICS trace data.
ON
CICS uses GTF as a destination for CICS trace data. To use the GTF data sets for CICS trace data, you must have started GTF with the USR option, in addition to coding GTFTR=ON.

For information about GTF, see the OS/390 MVS Diagnosis: Tools and Service Aids manual, SY28-1985.

HPO={NO|YES}
specifies whether you want to use the VTAM authorized path feature of the high performance option (HPO). If you code YES, the CICS type 6 SVC must be link-edited in your MVS nucleus, and defined to MVS in an SVCPARM statement. If the SVC number is not 215 (the default) you must specify the SVC number on the SRBSVC parameter.

For information about installing the CICS type 6 SVC in your MVS system, and about changing the default number, see the CICS Transaction Server for z/OS Installation Guide.

Restrictions You can specify the HPO parameter in the system initialization table only.

ICP=COLD
specifies that you want to cold start the interval control program. See topic Defining CICS resource table and module keywords for further information. If COLD is not specified, the ICP start type will be determined by the START and TS parameter values.
ICV={1000|number}
specifies the region exit time interval in milliseconds. The ICV system initialization parameter specifies the maximum time in milliseconds that CICS releases control to the operating system when there are no transactions ready to resume processing. This time interval can be any integer in the range 100 through 3600000 milliseconds (specifying an interval up to 60 minutes). A typical range of operation might be 100 through 2000 milliseconds.

A low value interval can enable much of the CICS nucleus to be retained in dynamic storage, and not be paged-out at times of low terminal activity. This reduces the amount of dynamic storage paging necessary for CICS to process terminal transactions (thus representing a potential reduction in response time), sometimes at the expense of concurrent batch region throughput. Large networks with high terminal activity are inclined to run CICS without a need for this value, except to handle the occasional, but unpredictable, period of inactivity. These networks can usually function with a large interval (10000 to 3600000 milliseconds). Once a task has been initiated, its requests for terminal services and the completion of the services are recognized by the system and this maximum delay interval is overridden.

Small systems, or those with low terminal activity, are subject to paging introduced by other jobs running in competition with CICS. By specifying a low value interval, key portions of the CICS nucleus are referenced more frequently, thus reducing the probability of these pages being paged-out. However, the execution of the logic without performing productive work might be considered wasteful. The need to increase the probability of residency by frequent but unproductive referencing must be weighed against the overhead and response time degradation incurred by allowing the paging to occur. By increasing the interval size, less unproductive work is performed at the expense of performance if paging occurs during the periods of CICS activity. For information about the effect of ICV on performance, see the CICS Performance Guide.

Note:
The region exit time interval process contains a mechanism to ensure that CICS does not constantly set and cancel timers (thus degrading performance) while attempting to meet its objectives for a low region exit time interval. This mechanism can cause CICS to release control to the operating system for up to 0.5 seconds when the interval has been set at less than 250; and up to 0.25 seconds more than the region exit time interval when the interval has been set greater than 250.
ICVR={5000|number}
specifies the default runaway task time interval in milliseconds as a decimal number. You can specify zero, or a number in the range 500 through 2 700 000, in multiples of 500. CICS rounds down values that are not multiples of 500. This is the RUNAWAY interval used by transactions defined with RUNAWAY=SYSTEM (see the CICS Resource Definition Guide for further information). CICS may purge a task if it has not given up control after the RUNAWAY interval for the transaction (or ICVR if the transaction definition specified RUNAWAY=SYSTEM). If you code ICVR=0, runaway task control is inoperative for transactions specifying RUNAWAY=SYSTEM in their transaction definition (that is, tasks do not get purged if they appear to be looping). The ICVR value is independent of the ICV value, and can be less than the ICV value. Note that CICS runaway task detection is based upon task time, that is, the interval is decremented only when the task has control of the processor. For information about commands that reinitialize the ICVR value, see the CICS Problem Determination Guide.
ICVTSD={500|number}
specifies the terminal scan delay value. The terminal scan delay facility determines how quickly CICS deals with some terminal I/O requests made by applications. The range is 0 through 5000 milliseconds, with a default of ICVTSD=500.

There is an overhead in dealing with such requests. By specifying a nonzero value, the overhead may be spread over several transactions. A value close to zero (for example 200) would be adequate.

IIOPLISTENER={YES|NO}
specifies whether the CICS region is to function as an IIOP listener region.
YES
The CICS region is an IIOP listener region, or a combined listener and application owning region (AOR).
NO
The CICS region is an IIOP application owning region, and TCPIPSERVICE definitions installed in the region, that specify PROTOCOL(IIOP), cannot be opened.
This parameter has no effect if the region is not an IIOP listener region or an AOR.

For more information about IIOP listener regions and AORs, see Java Applications in CICS

Start of changeINFOCENTER=servername:portnumberEnd of change
Start of changeSpecifies the server name of where the CICS Information Center is installed, and the port number that it uses to run in server mode. The port number is specified in the start up script for the information center. The default value is 29127, but you can change it to a suitable number by editing the script file. CICS-supplied transactions with a Web browser interface use the value of this parameter to construct links to topics in the information center.
Example:
INFOCENTER=http://server_name:29127

If you do not code this parameter, CICS does not construct links to the information center.

End of change
INITPARM=(pgmname_1=‘parmstring_1’[, .... ,pgmname_n=‘parmstring_n’])
specifies that parameters are to be passed to application programs that use the ASSIGN INITPARM command. For example, you can use INITPARM to pass parameters to PLTPI programs to be executed in the final stages of system initialization. The area giving access to the parameters is specified by the ASSIGN INITPARM command. For programming information about the ASSIGN INITPARM command, see the CICS Application Programming Reference.
pgmname
The name of a program. This name must be 1 through 8 alphanumeric or national language characters.
parmstring
The parameter string (up to 60 characters enclosed by single quotes) to be passed to the associated program. Any quotes imbedded in the string must be duplicated. For information on coding INITPARM in the SYSIN data set, see Rules for coding CICS system initialization parameters in the SYSIN data set.

You can specify up to 255 pgmname=‘parmstring’ sets.

Note:
You can specify the INITPARM keyword and its parameters more than once, see Sample startup job stream, note 5.
INTTR={ON|OFF}
specifies whether the internal CICS trace destination is to be activated at system initialization.

This parameter controls whether any of the three types of CICS trace entry are written to the internal trace table. The three types are: CICS system trace (see the SYSTR parameter), user trace (see the USERTR parameter), and exception trace entries (which are always made and not controlled by a system initialization parameter).

ON
Activate main storage trace.
OFF
Do not activate main storage trace.
IRCSTRT={NO|YES}
specifies whether IRC is to be started up at system initialization. If IRCSTRT=YES is not coded, IRC can be initialized by issuing a CEMT or EXEC CICS SET IRC OPEN command.
ISC={NO|YES}
specifies whether the CICS programs required for interregion or intersystem communication are to be included.
JESDI={30|number} (alternate)
specifies, in a SIT for an alternate XRF system, the JES delay interval, in seconds, the minimum being 5 seconds. The alternate CICS region has to ensure that the active CICS region has been canceled before it can take over the resources owned by the active.
Note:
You must give careful consideration to the values you specify for the parameters ADI and JESDI so that they do not conflict with your installation’s policy on PR/SM RESETTIME and the XCF INTERVAL and OPNOTIFY intervals. You should ensure that the sum of the interval you specify for ADI plus JESDI exceeds the interval specified by the XCF INTERVAL and the PR/SM policy interval RESETTIME.
JVMCCPROFILE={DFHJVMCC|profile}
specifies the JVM profile to be used for the master JVM that initializes the shared class cache. The default is the supplied sample JVM profile, DFHJVMCC, which you can modify. The value specified by JVMCCPROFILE is used on an initial or cold start of CICS. You can restart the shared class cache with a different JVM profile while CICS is running. On subsequent restarts, the value from the last CICS execution is used, unless you provide JVMCCPROFILE as a SIT override.

When you specify the JVM profile, use the same combination of upper and lower case characters that is present in the HFS file name of the JVM profile.

JVMCCSIZE={24M|number}
specifies the size of the shared class cache on an initial or cold start of CICS. The size of the shared class cache can be between 1MB and 2047MB. You can specify the number in bytes, or as a whole number of kilobytes followed by the letter K, or as a whole number of megabytes followed by the letter M. The default value is 24MB (specified as 24M). You can use the CEMT PERFORM CLASSCACHE START or RELOAD command (or the equivalent EXEC CICS command) to change the size of the shared class cache while CICS is running. On subsequent restarts, the value from the last CICS execution is used, unless you provide JVMCCSIZE as a SIT override.
JVMCCSTART={AUTO|YES|NO}
determines whether or not the shared class cache is started during CICS initialization, and sets the status of autostart for the shared class cache. When autostart is enabled for the shared class cache, if the shared class cache has been stopped or has not yet been started, it is started as soon as CICS receives a request to run a Java application in a JVM whose profile requires the use of the shared class cache. When autostart is disabled, the shared class cache can only be started by a CEMT PERFORM CLASSCACHE START command (or the equivalent EXEC CICS command). You can change the status of autostart while CICS is running, either by using the AUTOSTARTST option on the CEMT PERFORM CLASSCACHE command, or by using the CEMT SET CLASSCACHE command (or the equivalent EXEC CICS commands). If you do this, subsequent CICS restarts use the changed setting, unless the system is INITIAL or COLD started, or the JVMCCSTART system initialization parameter is specified as an override at startup. In these cases, the setting from the system initialization parameter is used.
AUTO
The shared class cache is not started during CICS initialization. Autostart is enabled, so the shared class cache will start as soon as a JVM needs it.
YES
The shared class cache is started during CICS initialization. Autostart is enabled, so if you stop the shared class cache, it is restarted as soon as a JVM needs it.
NO
The shared class cache is not started during CICS initialization. Autostart is disabled, so the shared class cache will not start unless you issue a CEMT PERFORM CLASSCACHE START command (or the equivalent EXEC CICS command).
JVMxxxxTRACE (JVMLEVEL0TRACE=option, JVMLEVEL1TRACE=option, JVMLEVEL2TRACE=option, JVMUSERTRACE=option)

These system initialization parameters specify the default options for JVM tracing. "Defining tracing for JVMs" in the CICS Problem Determination Guide has information about the JVM trace options that you can set using the JVMLEVEL0TRACE, JVMLEVEL1TRACE, JVMLEVEL2TRACE and JVMUSERTRACE system initialization parameters. There is further information about JVM trace and about problem determination for JVMs in the IBM Developer Kit and Runtime Environment, Java 2 Technology Edition, Version 1.4.2 Diagnostics Guide, SC34-6358, which is available to download from www.ibm.com/developerworks/java/jdk/diagnosis/.

Trace levels 29-32 for the SJ component correspond to JVMLEVEL0TRACE, JVMLEVEL1TRACE, JVMLEVEL2TRACE and JVMUSERTRACE respectively. To activate JVM tracing, specify level numbers 29-32 on the SPCTRSJ or STNTRSJ system initialization parameter, or use the CETR transaction.

Note that JVM trace can produce a large amount of output, so you should normally activate JVM trace for special transactions, rather than turning it on globally for all transactions.

For definitions of the individual JVM tracing parameters, see JVMLEVEL0TRACE, JVMLEVEL1TRACE, JVMLEVEL2TRACE, and JVMUSERTRACE below.

Restrictions: You can specify the JVMxxxxTRACE parameters in PARM, SYSIN, or CONSOLE only.

JVMLEVEL0TRACE={Start of change'ALL(EXCEPTION)'End of change|'user override string'}
Specifies the default option for JVM Level 0 trace, corresponding to trace level 29 of the SJ component. The default setting for this level of tracing maps to trace point level 0 for JVMs, which is reserved for extraordinary events and errors. Unlike CICS exception trace, which cannot be switched off, the JVM Level 0 trace is normally switched off unless JVM tracing is required. JVMxxxxTRACE has more information about these system initialization parameters.
JVMLEVEL1TRACE={Start of change'ALL(ENTRY,EXIT)'End of change|'user override string'}
Specifies the default option for JVM Level 1 trace, corresponding to trace level 30 of the SJ component. The default setting for this level of tracing maps to trace point level 1 for JVMs. JVMxxxxTRACE has more information about these system initialization parameters.
JVMLEVEL2TRACE={Start of change'ALL'End of change|'user override string'}
Specifies the default option for JVM Level 2 trace, corresponding to trace level 31 of the SJ component. The default setting for this level of tracing maps to trace point level 2 for JVMs. Note that the JVM trace point levels go up to level 9. JVMxxxxTRACE has more information about these system initialization parameters.
JVMUSERTRACE={Start of change'NONE'End of change|'user override string'}
Specifies the default option for JVM user trace, corresponding to trace level 32 of the SJ component. Use this option for more complex specifications for JVM tracing.JVMxxxxTRACE has more information about these system initialization parameters.
JVMPROFILEDIR={/usr/lpp/cicsts/cicsts31/JVMProfiles|directory}
specifies the name (up to 240 characters long) of an HFS directory that contains the JVM profiles for CICS. CICS searches this directory for the profiles it needs to configure JVMs. The default value of JVMPROFILEDIR is /usr/lpp/cicsts/cicsts31/JVMProfiles. That is, the supplied setting for JVMPROFILEDIR points to the default directory for the sample JVM profiles. If you chose a different name during CICS installation for the cicsts31 directory beneath which the sample JVM profiles are stored (that is, if you chose a non-default value for the CICS_DIRECTORY variable used by the DFHIJVMJ job), or if you want CICS to load the JVM profiles from a directory other than the samples directory, you need to do one of the following:

Note that the JVM profiles DFHJVMPR and DFHJVMCD, and their associated JVM properties files, must always be available to CICS. DFHJVMPR is used if a Java program is defined as using a JVM but no JVM profile is specified, and it is used for sample programs. DFHJVMCD is used by CICS-defined programs, including the default request processor program and the program that CICS uses to publish and retract deployed JAR files. Both these JVM profiles must therefore either be present in the directory that is specified by JVMPROFILEDIR, or linked to by means of UNIX soft links from that directory.

KEYRING=keyring-name

Specifies the fully qualified name of the key ring, within the external security manager’s database, that contains the keys and X.509 certificates used by CICS support for the secure sockets layer (SSL) and for Web services security.

Be aware that the key ring name is case sensitive.

Notes:
  1. The maximum length of the KEYRING parameter is 47 characters.
  2. For more information on creating a key ring, see the CICS RACF Security Guide
LGDFINT={5|number
Start of changespecifies the log defer interval to be used by CICS log manager when determining how long to delay a forced journal write request before invoking the MVS system logger. The value is specified in milliseconds.
5
This is the default.
Note:
When this parameter was first introduced, the default value was 30 milliseconds, but customer experience has shown that 5 is a more realistic value.
number
number can be any value in the range 0 through 65535. You are recommended to allow LGDFINT to assume its default value, 5.
Note:
You can modify the log defer interval dynamically using the LOGDEFER option of the CEMT SET SYSTEM or EXEC CICS SET SYSTEM commands. However, you are recommended not to modify this value in a production environment without first performing a system evaluation and performance analysis of any changed value.

If you change the log defer interval value dynamically, the new value is not cataloged. The log defer interval value is taken from the LGDFINT system initialization parameter in all types of CICS startup.

Start of changeWhen a CICS system has many tasks issuing forced log write requests, these tasks will not be delayed for periods close to the LGDFINT parameter value. This is because a forced log write request is normally issued while a log deferral is already being performed for another task. The actual interval might also be affected by the need for tasks to wait across a partition exit.End of change

End of change
LGNMSG={NO|YES}
specifies whether VTAM logon data is to be made available to an application program.
NO
VTAM logon data is not available to an application program.
YES
VTAM logon data is available to an application program. The data can be retrieved with an EXEC CICS EXTRACT LOGONMSG command. For programming information about this command, see the CICS Application Programming Reference.

You can use this parameter with the GMTRAN parameter to retrieve the VTAM logon data at the time a terminal is logged on to CICS by VTAM.

LLACOPY={YES|NO|NEWCOPY}
specifies whether CICS is to use the LLACOPY macro or the BLDL macro when locating modules in the DFHRPL concatenation.
YES
CICS always uses the LLACOPY macro when locating modules in the DFHRPL concatenation.
NO
CICS always uses the BLDL macro when locating modules in the DFHRPL concatenation.
NEWCOPY
CICS uses the LLACOPY only when a NEWCOPY or a PHASEIN is being performed. At all other times, CICS uses the BLDL macro when locating modules in the DFHRPL concatenation.
Notes:
  1. If you code LLACOPY=NO or LLACOPY=NEWCOPY you can still benefit from having LLA managed data sets within your DFHRPL concatenation. Modules will continue to be loaded from VLF if appropriate.
  2. If an LLA managed module has been altered, a BLDL macro may not return the new information and a subsequent load will still return the old copy of the module. To load the new module, an LLACOPY must be issued against that module or a MODIFY LLA,REFRESH command must be issued on a system console.
  3. If you set LLACOPY to anything other than NO, ensure that the proper RACF security permissions have been set up first. For more information about this refer to in the CICS RACF Security Guide.
Start of changeLOCALCCSID={037|CCSID} End of change
Start of changeSpecifies the default CCSID for the local region.

The CCSID is a value of up to 8 characters. If CCSID value is not specified, the default LOCALCCSID is set to 037. For lists of valid CCSIDs, see:

037
the default value for LOCALCCSID.
CCSID
represents any other valid CCSID value.
End of change
LPA={NO|YES}
specifies whether any CICS or user modules can be used from the link pack areas.
NO
will not load CICS or user modules from the link pack areas.
YES
CICS or usermodules installed in the LPA or in the ELPA can be used from there, instead of being loaded into the CICS region.

A list of the CICS modules that are read-only, and hence eligible for residence in the link pack areas (LPA or ELPA), are contained in the SMP/E USERMOD supplied on the distribution tape in the CICSTS31.CICS.SDFHSAMP, in a member called DFH$UMOD. For details of the CICS system initialization parameter PRVMOD that you can use to override LPA=YES for selected modules, see topic PRVMOD.

MAXJVMTCBS={5|number}
specifies the maximum number, in the range 1 through 999, of open TCBs CICS can create in the pool of J8 and J9 mode TCBs for use by Java programs that run in a JVM (the JVM pool). Within this limit, there are no constraints on how many of the TCBs in the JVM pool are J9 TCBs, and how many are J8 TCBs.

The default is 5. The minimum permitted value is 1, meaning that CICS is always able to create at least 1 open TCB for use by a JVM, of either J8 or J9 mode.

JM TCBs, used for the master JVM that initializes the shared class cache, do not count towards the MAXJVMTCBS limit.

System initialization parameters for open TCBs has more information about managing open TCBs.

MAXOPENTCBS={Start of change12End of change|number}
Start of changespecifies the maximum number, in the range 1 through Start of change2000 End of change, of open TCBs CICS can create in the pool of L8 Start of change and L9 End of change mode TCBs. Within this limit, there are no constraints on how many of the TCBs in the pool are L8 TCBs, and how many are L9 TCBs. Start of changeEnd of change

The default is Start of change12 End of change. The minimum permitted value is Start of change1 End of change.System initialization parameters for open TCBs has more information about managing open TCBs.

End of change
MAXSOCKETS=number
Specifies the maximum number of IP sockets that can be managed by the CICS sockets domain.

If the CICS region userid (the userid under which CICS is running) has superuser authority, the default value is 65535.

If the CICS region userid does not have superuser authority, the maximum possible value is the value of the MAXFILEPROC parameter in SYS1.PARMLIB member BPXPRMxx. If you specify a value greater than this in the MAXSOCKETS system initialization parameter (or by letting CICS use the default), CICS issues a message indicating the value that CICS has used.

Note that sockets created by Java programs running on threads that are not managed by CICS do not count towards the MAXSOCKETS limit.

Start of changeMAXSSLTCBS={8|number}End of change
Start of changeSpecifies the maximum number of S8 TCBs that can run in the SSL pool. The default is 8, but you can specify up to 1024 TCBs.

Start of changeThis value must not exceed the MAXTHREADS and MAXTHREADTASKS parameter values, that are specified in SYS1.PARMLIB member BPXPRMxx.End of change

End of change
Start of changeMAXXPTCBS={5|number}End of change
Start of changespecifies the maximum number, in the range 1 through 999, of open X8 and X9 TCBs that can exist concurrently in the CICS region. X8 and X9 are the TCBs that are used to provide XPLink support.

System initialization parameters for open TCBs has more information about managing open TCBs.

End of change
MCT={NO|YES|xx}
specifies the monitoring control table suffix. (See topic Defining CICS resource table and module keywords.) If you specify MCT=NO, CICS monitoring builds dynamically a default MCT, ensuring that default monitoring control table entries are always available for use when monitoring is on and a monitoring class (or classes) is active. You can generate an MCT with a single-character suffix only for use by CICS because single-character suffixes cause an error when the MCT is processed by DFHMNDUP. If you use DFHMNDUP, make sure that you create your MCTs with two-charcter suffixes.

For information about coding the macros for this table, see the CICS Operations and Utilities Guide.

MN={OFF|ON}
specifies whether monitoring is to be switched on or off at initialization, and use the individual monitoring class parameters to control which monitoring classes are to be active. (See the MNEVE, MNEXC, and MNPER parameter descriptions.) The default status is that the CICS monitoring facility is off. The monitoring status is recorded in the CICS global catalog for use during warm and emergency restarts.
OFF
Switch off monitoring.
ON
Switch on monitoring. However, unless at least one individual class is active, no monitoring records are written. For details of the effect of monitoring status being on or off, in conjunction with the status of the various monitoring classes, see the following notes:
Notes:
  1. If the monitoring status is ON, CICS accumulates monitoring data continuously and, depending on the status of each of the monitoring classes, processes the accumulated data as follows:
    • For the performance and exception monitoring classes, CICS writes the monitoring data for each class that is active to a system management facilities (SMF) data set.
    • For the SYSEVENT monitoring class, CICS notifies the MVS system resources manager (SRM) of the completion of each transaction. This data can be reported using the resource measurement facility (RMF™), or written to SMF data sets, depending on the RMF options in force.

      For information about the effect of SYSEVENT recording in an MVS workload manager environment, see the CICS Performance Guide.

    If the monitoring status is OFF, CICS does not accumulate or write any monitoring data, even if any of the monitoring classes are active.

  2. You can change the monitoring status and the monitoring class settings at any time, as follows:
    • During a warm restart by coding an MN system initialization parameter in PARM, SYSIN, or through the system console.
    • While CICS is running, by either of:
      • The CEMT SET MONITOR command
      • The EXEC CICS SET MONITOR command

    When you change the status of monitoring, the change takes effect immediately. If you change the monitoring status from OFF to ON, monitoring starts to accumulate data and write monitoring records to SMF for all tasks that start after the status change is made for all active monitoring classes. If the status is changed from ON to OFF, monitoring stops writing records immediately and does not accumulate monitoring data for any tasks that start after the status change is made.

  3. The monitoring status operand can be manipulated independently of the class settings. This means that, even if the monitoring status is OFF, you can change the monitoring class settings and the changes take effect for all tasks that are started after the monitoring status is next set to ON.

For programming information about controlling CICS monitoring, see CICS System Programming Reference.

MNCONV={NO|YES}
specifies whether or not conversational tasks are to have separate performance class records produced for each pair of terminal control I/O requests.

Any clock (including user-defined) that is active at the time such a performance class record is produced is stopped immediately before the record is written. After the record is written, such a clock is reset to zero and restarted. Thus a clock whose activity spans more than one recording interval within the conversational task appears in multiple records, each showing part of the time, and the parts adding up to the total time the clock is active. The high-water-mark fields (which record maximum levels of storage used) are reset to their current values. All other fields are set to X'00', except for the key fields (transid, termid). The monitoring converse status is recorded in the CICS global catalog for use during warm and emergency restarts.

MNEXC={OFF|ON}
specifies whether the monitoring exception class is to be made active during initialization. The monitoring exception class status is recorded in the CICS global catalog for use during warm and emergency restarts.
OFF
Set the exception monitoring class to "not active".
ON
Set the exception monitoring class to "active".

For programming information about exception monitoring records, see the CICS Customization Guide.

MNFREQ={0|hhmmss}
specifies the interval for which CICS automatically produces a transaction performance class record for any long-running transaction. The monitoring frequency value is recorded in the CICS global catalog for use during warm and emergency restarts.
0
No frequency monitoring is active.
hhmmss
The interval for which monitoring produces automatically a transaction performance class record for any long-running transaction. Specify a 1 to 6 digit number in the range 001500-240000. Numbers that are fewer than six digits are padded with leading zeroes.
MNPER={OFF|ON}
specifies whether the monitoring performance class is to be made active during CICS initialization. The monitoring performance class status is recorded in the CICS global catalog for use during warm and emergency restarts.
OFF
Set the performance monitoring class to "not active".
ON
Set the performance monitoring class to "active".

For programming information about performance monitoring records, see the CICS Customization Guide.

MNRES={OFF|ON}
specifies whether transaction resource monitoring is to be made active during CICS initialization. The transaction resource monitoring class status is recorded in the CICS global catalog for use during warm and emergency restarts.
OFF
Set transaction resource monitoring to not active.
ON
Set transaction resource monitoring to active.

Transaction resource monitoring applies to CICS file resources when you specify the FILE=nn option on the DFHMCT TYPE=INTIAL macro.

For programming information about transaction resource monitoring record formats, see the CICS Customization Guide.

MNSUBSYS={null|xxxx}
specifies the 4-character name to be used as the subsystem identification in the monitoring SYSEVENT class records. If you do not specify a name, the subsystem identification defaults to the first four characters of the name1 operand of the APPLID system initialization parameter. The monitoring subsystem id is recorded in the CICS global catalog for use during warm and emergency restarts.

For background information on the SYSEVENT class of monitoring data and the subsystem identification, and about the implications for SYSEVENT recording in a MVS Workload Manager environment, see the CICS Performance Guide.

MNSYNC={NO|YES}
specifies whether you want CICS to produce a transaction performance class record when a transaction takes an implicit or explicit syncpoint (unit-of-work). No action is taken for syncpoint rollbacks. The monitoring syncpoint status is recorded in the CICS global catalog for use during warm and emergency restarts.
MNTIME={GMT|LOCAL}
specifies whether you want the time stamp fields in the performance class monitoring data to be returned to an application using the EXEC CICS COLLECT STATISTICS MONITOR(taskno) command in either GMT or local time. The monitoring time value is recorded in the CICS global catalog for use during warm and emergency restarts.

For programming information on the EXEC CICS COLLECT STATISTICS command, see the CICS System Programming Referencemanual.

MQCONN={NO|YES}
specifies whether you want CICS to start the MQSeries® for OS/390 connection automatically during initialization. Start of changeA single CICS address space can be connected to only one queue manager at a time.End of change
NO
Do not automatically invoke CSQCCODF, the MQSeries attach program, during initialization.
YES
Invoke the MQSeries attach program, CSQCCODF, automatically during CICS initialization. The other information CICS needs for starting the attachment, such as the MQSeries queue manager subsystem name, is taken from the CSQCPARM operand of an INITPARM system initialization parameter.

Specifying MQCONN=YES means you don’t need to define the MQSeries attach program in the CICS post-initialization program list table (PLT).

Note:
The MQCONN parameter works only if you are using the MQSeries-supplied program, CSQCCODF, to start the CICS-MQSeries connection. MQCONN will not work with your own-written attach program if it has a different name.
For more information about starting a connection to an MQSeries queue manager, see MQSeries for MVS/ESA: System Management Guide, SC33-0806.
MROBTCH={1|number}
specifies the number of events that must occur before CICS is posted for dispatch due to the batching mechanism. The number can be in the range 1 through 255, and the default is 1.

Start of changeUse this batching mechanism to spread the overhead of dispatching CICS over several tasks. If the value is greater than 1 and CICS is in a system wait, CICS is not posted for dispatch until the specified number of events has occurred. Events include MRO requests from connected systems or DASD I/O and CHANGE_MODE processing. For these events, CICS is dispatched as soon as one of the following occurs:

Therefore, ensure that the time interval you specify in the ICV parameter is low enough to prevent undue delay to the system.End of change

If CICS is dispatched for another reason, the current batch is dealt with in that dispatch of CICS.

Note:
During periods of low utilization, a value of MROBTCH greater than 1 may result in increased transaction response times. Transactions issuing file I/O requests may be delayed due to increased FCIOWAIT. For further guidance information about the effect of MROBTCH on performance, see the CICS Performance Guide.
MROFSE={NO|YES}
specifies whether you want to extend the lifetime of the long-running mirror to keep it allocated until the end of the task rather than after a user syncpoint for function shipping applications.
NO
The lifetime of the MRO long-running mirror is not extended.
YES
The mirror task remains available to the application until the end of the application's task. This extended long-running mirror saves the overhead of reattaching the mirror task following a user syncpoint.

This parameter is ignored for DPL requests (that is a DPL causes the session to be freed at the next syncpoint even if is has been kept for a previous sequence of syncpoints).

Start of changeIt should be used with caution, especially if DPL requests with SYNCONRETURN or TRANSID are used. For additional information, see the long running mirror sections of the CICS Intercommunication Guide" and the CICS Performance Guide.End of change

Start of changeDo not specify this value in the front-end region when long running tasks might be used to function-ship requests. This because a SEND session is unavailable for allocation to other tasks when unused. Specifying MROFSE=YES could prevent the connection from being released when contact has been lost with the back-end region, until the task terminates or issues a function-shipped request.End of change

MROLRM={NO|YES}
specifies whether you want to establish an MRO long-running mirror task.
NO
The MRO long-running mirror task is not required.
YES
The mirror transaction remains available to the application issuing the remote request. This long-running mirror saves the overhead of re-establishing communication with the mirror transaction if the application makes more function shipping requests in this unit of work.

For information about long-running mirror tasks, see the CICS Intercommunication Guide.

MSGCASE={MIXED|UPPER}
CICS messages handled by the CICS message domain are in mixed case. Specify this parameter to indicate how you want the message domain to display these mixed case messages.
MIXED
This is the default in the SIT; all messages displayed by the CICS message domain remain in mixed case.
UPPER
The message domain displays all mixed case messages in uppercase only.
Note:
Mixed case output is not displayed correctly on Katakana display terminals and printers. Uppercase English characters appear correctly as uppercase English characters, but lowercase appears as Katakana symbols. If you have any Katakana terminals connected to your CICS region, specify MSGCASE=UPPER.
MSGLVL={1|0}
specifies the message level that controls the generation of messages to the console and JES message log.
1
All messages are printed or displayed.
0
Only critical errors or interactive messages are printed or displayed.
MXT={5|number}
specifies the maximum number, in the range 1 through 999, of user tasks CICS allows to exist at any time. CICS queues requests for tasks above this number but does not action (attach) them until the number of tasks attached drops below the MXT limit.

Note that each active IIOP session requires two tasks.

You should review the region size specified on the REGION parameter for CICS address spaces. The increase in CICS use of virtual storage above the 16MB boundary means that you will probably need to increase the REGION parameter.

The introduction of the transaction isolation facility increases the allocation of some virtual storage above the 16MB boundary for CICS regions that are running with transaction isolation active.

If you are running with transaction isolation active, CICS allocates storage for task-lifetime storage in multiples of 1MB for user-key tasks that run above the 16MB boundary. (1MB is the minimum unit of storage allocation above the line for the EUDSA when transaction isolation is active.) However, although storage is allocated in multiples of 1MB above the 16MB boundary, MVS paging activity affects only the storage that is actually used (referenced), and unused parts of the 1MB allocation are not paged.

If you are running without transaction isolation, CICS allocates user-key task-lifetime storage above 16MB in multiples of 64KB.

The subspace group facility uses more real storage, as MVS creates for each subspace a page and segment table from real storage. The CICS requirement for real storage varies according to the transaction load at any one time. As a guideline, each task in the system requires 9KB of real storage, and this should be multiplied by the number of concurrent tasks that can be in the system at any one time (governed by the MXT system initialization parameter).

However, automatic DSA sizing removes the need for accurate storage estimates, with CICS dynamically changing the size of DSAs as demand requires.

Note:
The MXT value does not include CICS system tasks.
NATLANG=(E,x,y,z,...)
specifies the single-character codes for the languages to be supported in this CICS run, selected from the codes in Table 22.
E
English, which is the system default (that is, is provided even if you do not specifically code E).
x,y,z,...
Specify the appropriate letters for the other supported languages that you require.

For the codes that you specify on this parameter, you must ensure that a DFHMET1x module (where x is the language code) is in a library in the STEPLIB DD concatenation of the CICS startup JCL. (For full language support, you must also provide other DFHMEyyx modules.) For information about using the message editing utility to create your own DFHMEyyx modules, see the CICS Operations and Utilities Guide.

English language support is provided, even if you do not specifically code E for English.

The first language code specifies the default language for those elements of CICS enabled to receive National Language Support (NLS) messages, such as some destinations used for CICS messages, and the terminals or users not signed-on with an NLS code. The other language codes are provided to specify the language to be used for messages sent to terminals that are defined with the appropriate language support code. For example, coding NATLANG=(F,G,S) has the same effect as coding NATLANG=(F,G,E,S); that is, in both cases the default NLS language is French (F), and the languages English, German (G), and Spanish (S) are supported. (For such support, you would have to create and install the modules DFHMET1F, DFHMET1G, and DFHMET1S into a library in the STEPLIB DD concatenation of the CICS startup JCL.)

NLS is not available to CICS console messages, which continue to be in English only.

Table 22. Languages and codes supported by CICS
NATLANG code NLS code Language
A ENG Alternative English
Q ARA Arabic
1 BEL Byelorussian
L BGR Bulgarian
B PTB Brazilian Portuguese
T DBCS CHT Traditional Chinese
C DBCS CHS Simplified Chinese
2 CSY Czech
D DAN Danish
E ENU English
G DEU German
O ELL Greek
S ESP Spanish
W FIN Finnish
F FRA French
X HEB Hebrew
3 HRV Croatian
4 HUN Hungarian
J ISL Icelandic
I ITA Italian
K DBCS JPN Japanese
H DBCS KOR Korean
M MKD Macedonian
9 NLD Dutch
N NOR Norwegian
5 PLK Polish
P PTG Portuguese
6 ROM Romanian
R RUS Russian
Y SHC Serbo-Croatian (Cyrillic)
7 SHL Serbo-Croatian (Latin)
V SVE Swedish
Z THA Thai
8 TRK Turkish
U UKR Ukrainian
Note:

DBCS denotes Double-Byte Character Set languages.

The following language module suffixes are not supported by the message editing utility:

  • E - English master data sets.
  • K - Japanese data sets, where translation is performed by IBM.
  • C - Simplified Chinese data sets, where translation is performed by IBM.

The NATLANG code is used as the suffix of the message modules for the associated language.

NCPLDFT={DFHNC001|name}
specifies the name of the default named counter pool to be used by the CICS region on calls it makes to a named counter server. If CICS cannot determine, from the named counter options table, the pool name required by an EXEC CICS named counter command, CICS uses the default name specified on the NCPLDFT parameter.
Note:
This parameter is relevant to references to a named counter server made through the EXEC CICS API only. It not used by the named counter call interface.
DFHNC001
This is the default name that CICS uses as the named counter pool name if you omit the NCPLDFT system initialization parameter.
name
Specifies the 8-character name to be used by CICS as the default pool name in connection with named counter API commands, when the name cannot be resolved by the named counter options table.
NEWSIT={YES|NO}
specifies whether CICS is to load the specified SIT, and enforce the use of all system initialization parameters, modified by any system initialization parameters provided by PARM, SYSIN, or the system console, even in a warm start. Enforcing the use of system initialization parameters in this way overrides any parameters that may have been stored in a warm keypoint at shutdown.

However, there are some exceptions. The following system initialization parameters are always ignored in a warm start, even if they are supplied by PARM, SYSIN, or the console:

In a warm restart, CICS uses the installed resource definitions saved in the CICS global catalog at warm shutdown, and therefore the CSD, FCT, and GRPLIST parameters are ignored. (At CICS startup, you can only modify installed resource definitions, including file control table entries, or change to a new FCT, by performing a cold start of CICS with START=COLD.)

For more information about the use of the NEWSIT parameter, see Controlling start and restart.

Restrictions

You can specify the NEWSIT parameter in PARM, SYSIN, or CONSOLE only.

OFFSITE={NO|YES}
specifies whether CICS is to restart in off-site recovery mode; that is, a restart is taking place at a remote site.
Note:
For a successful off-site restart, the log records of the failed CICS region must be available at the remote site. CICS does not provide a facility for shipping log records to a remote backup site, but you can use a suitable vendor product to perform this function. See the relevant product documentation for other procedures you need to follow for a remote site restart.

See the CICS Recovery and Restart Guide for more information about remote site recovery.

NO
CICS will not perform the special restart processing required for remote site recovery.
YES
CICS will perform an off-site restart at a remote site following a disaster at the primary site. CICS performs this special processing for an off-site restart, because some information (for example, a VSAM lock structure) is not available at the remote site.

CICS performs an emergency restart, even if the global catalog indicates that CICS can do a warm start. OFFSITE=YES is valid with START=AUTO only, and CICS initialization is terminated if you specify START=COLD or INITIAL.

Restrictions

You can specify the OFFSITE parameter in PARM, SYSIN, or CONSOLE only.

OPERTIM={120|number}
specifies the write-to-operator timeout value, in the range 0 through 86400 seconds (24 hours). This is the maximum time (in seconds) that CICS waits for a reply before returning control to this transaction. For information about using the write-to-operator timeout value, see the CICS Application Programming Reference.
OPNDLIM={10|number} (Not required for currently supported releases of VTAM.)
specifies the open destination and close destination request limit. This limit is used to restrict the number of concurrent OPNDSTs and CLSDSTs to prevent VTAM from running out of space in the CICS region. The limit may be any value in the range 0 through 999. When large values are used for OPNDLIM, the value on the EDSALIM system initialization parameter and the value on the MVS REGION parameter may need to be adjusted to ensure that enough operating system storage is available. For information about adjusting these parameters, see the CICS Performance Guide .
PARMERR={INTERACT|IGNORE|ABEND}
specifies what action you want to follow if CICS detects incorrect system initialization parameter overrides during initialization.
Note:
When specified as an override, this parameter affects only subsequent system initialization parameter overrides. Errors in earlier system initialization parameter overrides are dealt with according to the PARMERR system initialization parameter value in the SIT.
INTERACT
Enables the operator to communicate with CICS through the console and correct parameter errors.
Note:
INTERACT is overridden with IGNORE in the following cases:
  • If errors are found in PARM or SYSIN for system initialization parameter overrides that are not allowed to be entered from the console
  • In certain circumstances, in response to invalid data when you have been trying to correct a previous invalid system initialization parameter keyword or value
IGNORE
CICS ignores errors, and tries to complete initialization.
ABEND
CICS abends.
PDI={30|decimal-value}
specifies the XRF primary delay interval, in seconds, in a SIT for an active CICS region. The minimum delay that you can specify is 5 seconds. This is the time that must elapse between the (apparent) loss of the surveillance signal in the alternate CICS region, and any reaction by the active CICS region. The corresponding parameter for the alternate CICS region is ADI. PDI and ADI need not have the same value.
PDIR={NO|yes|xx}
specifies a suffix for the PDIR list. A PDIR is a list of program specification blocks (PSBs) that define, for DL/I, the use of databases by application programs. This is applicable only if DL/I remote support is being used. (See also topic Defining CICS resource table and module keywords.) Specifying a value other than NO implies to CICS that remote DLI support is required.

For information about coding the macros for this table, see the CICS Resource Definition Guide.

PGAICTLG={MODIFY|NONE|ALL}
specifies whether autoinstalled program definitions should be cataloged. While CICS is running, you can set whether autoinstalled programs should be cataloged dynamically, by using either the EXEC CICS SET SYSTEM or CEMT SET SYSTEM command.
MODIFY
Autoinstalled program definitions are cataloged only if the program definition is modified by a SET PROGRAM command subsequent to the autoinstall.
NONE
Autoinstalled program definitions are not cataloged. This gives a faster CICS restart (warm and emergency) compared with the MODIFY or ALL options, because CICS does not reinstall definitions from the global catalog. Definitions are autoinstalled on first reference.
ALL
Autoinstalled program definitions are written to the global catalog at the time of the autoinstall, and following any subsequent modification.
PGAIEXIT={DFHPGADX|name}
specifies the name of the program autoinstall exit program. While CICS is running, you can set the name of the program autoinstall exit program dynamically, by using either the EXEC CICS SET SYSTEM or CEMT SET SYSTEM command.
PGAIPGM={INACTIVE|ACTIVE}
specifies the state of the program autoinstall function at initialization. While CICS is running, you can set the status of program autoinstall dynamically, by using either the EXEC CICS SET SYSTEM or CEMT SET SYSTEM command.
INACTIVE
The program autoinstall function is disabled.
ACTIVE
The program autoinstall function is enabled.
PGCHAIN=character(s)
specifies the character string that is identified by terminal control as a BMS terminal page-chaining command. It can be 1 through 7 characters. For more information about the character string, see the notes in topic 1.
PGCOPY=character(s)
specifies the character string that is identified by terminal control as a BMS command to copy output from one terminal to another. It can be 1 through 7 characters. For more information about the character string, see the notes in topic 1.
PGPURGE=character(s)
specifies the character string that is identified by terminal control as a BMS terminal page-purge command. It can be 1 through 7 characters. For more information about the character string, see the notes in topic 1.
PGRET=character(s)
specifies the character string that is recognized by terminal control as a BMS terminal page-retrieval command. It can be 1 through 7 characters.
Notes:
  1. Each character string is unique with respect to the leading characters of every other transaction identification defined in the CSD. A command requested by a single character precludes the use of all other transaction identifications starting with this character.
  2. In pseudoconversational mode, each character string is unique with respect to the leading characters of any terminal input message.
  3. A field-separator or other suitable delimiter may be specified in each character string to separate this command code from the remainder of the paging command when entered by an operator. For example:
    PGCHAIN = X/
    PGCOPY = C/
    PGPURGE = T/
    PGRET = P/

    This reduces the risk of creating a nonunique command. (See Note 1.)

    Restrictions

    If you specify PGCHAIN, PGCOPY, PGPURGE, or PGRET in the SIT, the characters you choose must not include any of the following: ( ) '

    If you specify PGCHAIN, PGCOPY, PGPURGE, or PGRET as a PARM, SYSIN, or console parameter, do not enclose the characters in quotation marks. The characters you choose must not include an embedded blank or any of the following: ( ) ' =

  4. PGCHAIN, PGCOPY, PGPURGE, and PGRET are required only if full function BMS is being used. For information about the BMS page retrieval transaction CSPG, see CICS Supplied Transactions.
  5. CICS always processes a paging command entered by the operator before initiating a transaction invoked by an EXEC CICS RETURN command with the TRANSID option.
PLTPI={NO|xx|YES}
specifies a program list table, which contains a list of programs to be executed in the final stages of system initialization (see topic Defining CICS resource table and module keywords). You can use the system initialization parameter INITPARM to pass parameters to those programs.

For information about coding the macros for this table, see the CICS Resource Definition Guide.

PLTPISEC={NONE|CMDSEC|RESSEC|ALL}
specifies whether or not you want CICS to perform command security or resource security checking for PLT programs during CICS initialization. The PLT programs run under the authority of the userid specified on PLTPIUSR, which must be authorized to the appropriate resources defined by PLTPISEC.
NONE
You do not want any security checking on PLT initialization programs.
CMDSEC
You want CICS to perform command security checking only.
RESSEC
You want CICS to perform resource security checking only.
ALL
You want CICS to perform both command and resource security checking.

Restrictions You can specify the PLTPISEC parameter in the SIT, PARM, or SYSIN only.

PLTPIUSR=userid
specifies the userid that CICS is to use for security checking for PLT programs that run during CICS initialization. All PLT programs run under the authority of the specified userid, which must be authorized to all the resources referenced by the programs, as defined by the PLTPISEC parameter.

PLT programs are run under the CICS internal transaction, CPLT. Before the CPLT transaction is attached, CICS performs a surrogate user check against the CICS region userid (the userid under which the CICS region is executing). This is to ensure that the CICS region is authorized as a surrogate for the userid specified on the PLTPIUSR parameter. This ensures that you cannot arbitrarily specify any PLT userid in any CICS region--each PLT userid must first be authorized to the appropriate CICS region.

If you do not specify the PLTPIUSR parameter, CICS runs PLTPI programs under the authority of the CICS region userid, in which case CICS does not perform a surrogate user check. However, the CICS region userid must be authorized to all the resources referenced by the PLT programs.

Restrictions You can specify the PLTPIUSR parameter in the SIT, PARM, or SYSIN only.

PLTSD={NO|xx|YES}
specifies a program list table that contains a list of programs to be executed during system termination (see topic Defining CICS resource table and module keywords).
PRGDLAY={0|hhmm}
specifies the BMS purge delay time interval that is added to the specified delivery time to determine when a message is to be considered undeliverable and therefore purged. This time interval is specified in the form "hhmm" (where "hh" represents hours from 00 to 99 and "mm" represents minutes from 00 to 59). If PRGDLAY is not coded, or is given a zero value, a message remains eligible for delivery either until it is purged or until temporary storage is cold started.
Note:
If you specify PRGDLAY as a SIT override, you must still specify a 4-character value (for example 0000).

The PRGDLAY facility requires the use of full function BMS. Note also that you must code a PRGDLAY value if you want the ERRTERM|ERRTERM(name) parameter on EXEC CICS ROUTE commands to be operative. For programming information about notification of undelivered messages, see the CICS Application Programming Reference.

The PRGDLAY value determines the interval between terminal page clean-up operations. A very low value causes the CSPQ transaction to be initiated continuously, and can have a detrimental effect on task-related resources. A zero value stops CSPQ initiating terminal page clean-up. However, this can cause messages to stay in the system forever, resulting in performance problems with long AID queues or lack of temporary storage. The actual purge delay time interval specified is dependent on individual system requirements.

PRINT={NO|YES|PA1|PA2|PA3}
specifies the method of requesting printout of the contents of a 3270 screen.
NO
Screen copying is not required.
YES
Screen copying can be requested by terminal control print requests only.
PA1, PA2, or PA3
Screen copying can be requested by terminal control print request, or by using the PA (program attention) key specified.

The PA key specified by this parameter must not be specified by the TASKREQ option of the RDO TRANSACTION definition or be used for 3270 single keystroke retrieval.

When YES, PA1, PA2, or PA3 is specified, transaction CSPP is initiated which invokes program DFHP3270. The transaction and programs are defined in the CSD group DFHHARDC. In the case of 3270 and LUTYPE2 logical units, the resources defined in CSD group DFHVTAMP are required.

The 3270 print-request facility allows either the application program or the terminal operator to request a printout of data currently displayed on the 3270 display.

If CSPP is invoked to print the screen contents at an associated VTAM printer, the screen size of the printer is chosen according to the screen size defined in the profile for the transaction CSPP. The CICS-supplied definitions use the default screen size. Therefore, if you want DFHP3270 to use the alternate screen size of the printer, you must alter the screen size defined in the profile for the transaction CSPP. For information about defining profiles for transactions, see CICS Supplied Transactions.

For a VTAM 3270 display without the printer-adapter feature, the PRINT request prints the contents of the display on the first available 3270 printer specified by PRINTER and ALTPRINTER options of the RDO TERMINAL definition. For a printer to be considered available, it must be in service and not currently attached to a task. It is not necessary for the printer to be on the same control unit.

In an MRO environment, the printer must be owned by the same system as the VTAM 3270 display.

For the 3275 with the printer-adapter feature, the PRINT request prints the data currently in the 3275 display buffer on the 3284 Model 3 printer attached to the 3275.

The format of the print operation depends on the size of the display buffer. For a 40-character wide display, the print format is a 40-byte line, and for an 80-character wide display the format is an 80-byte line.

For the 3270 compatibility mode logical unit of the 3790 (if the logical unit has the printer-adapter feature specified), the PRINT request prints the contents of the display on the first printer available to the 3790. The allocation of the printer to be used is under the control of the 3790.

For 3274, 3276, and LUTYPE2 logical units with the printer-adapter feature, the PRINT request prints the contents of the display on the first printer available to the 3270 control unit. The printer to be allocated depends on the printer authorization matrix.

For the 3270 compatibility mode logical unit without the printer-adapter feature, see the preceding paragraph on VTAM 3270 displays without the printer-adapter feature.

PRTYAGE={32768|value}
specifies the number of milliseconds to be used in the priority aging algorithm for incrementing the priority of a task. The value can be in the range 0 through 65535, and 32768 is the default.

The priority aging factor is used to increase the effective priority of a task according to the amount of time it is held on a ready queue. The value represents the number of milliseconds that must elapse before the priority of a waiting task can be adjusted upwards by 1. For example, if you code PRTYAGE=3000, a task has its priority raised by 1 for every 3000 milliseconds it is held on the ready queue. Thus a high value for PRTYAGE results in a task being promoted very slowly up the priority increment range, and a low value enables a task to have its priority incremented quickly.

If you specify a value of 0, the priority aging algorithm is not used (task priorities are not modified by age) and tasks on the ready queue are handled according to the user assigned priority.

PRVMOD={name|(name,name...name)}
specifies the names of those modules that are not to be used from the LPA.

The operand is a list of 1-to 8-character module names. This enables you to use a private version of a CICS nucleus module in the CICS address space, and not a version that might be in the LPA. For information about PRVMOD, see the CICS Transaction Server for z/OS Installation Guide.

Restrictions You can specify the PRVMOD parameter in PARM, SYSIN, or CONSOLE only.

PSBCHK={NO|YES}
specifies whether CICS is to perform PSB authorization checks for remote terminal users who use transaction routing to initiate a transaction in this CICS region (to access an attached IMS™ system).
NO
The remote link is checked, but no check is made against the remote terminal. This is the default.
YES
The remote link is checked, and the remote terminal is also checked if RESSEC(YES) is coded in the definition of the transaction in the CSD.

Restrictions You can specify the PSBCHK parameter in the SIT, PARM, or SYSIN only.

Note:
If you require DL/I security checking, you must specify the XPSB system initialization parameter as XPSB=YES or XSPB=name. For further information about the XPSB system initialization parameter, see XPSB .
PSDINT={0|hhmmss}
specifies the persistent session delay interval. This delay interval specifies if, and for how long, VTAM is to hold sessions in a recovery-pending state if CICS fails. The value for hours can be in the range 0 through 23; the minutes and seconds in the range 00 through 59 inclusive.

This value can be overridden during CICS execution (and hence change the action taken by VTAM if CICS fails).

0
If CICS fails, sessions are terminated. This is the default.
hhmmss
A persistent session delay interval from 1 second up to the maximum of 23 hours 59 minutes and 59 seconds. If CICS fails, VTAM holds sessions in recovery pending state for up to the interval specified on the PSDINT system initialization parameter.

Specify a 1-to-6 digit time in hours, minutes and seconds, up to the maximum time. If you specify less than six digits, CICS pads the value with leading zeros. Thus a value of 500 is taken as five minutes exactly.

The interval you specify must cover the time from when CICS fails to when the VTAM ACB is opened by CICS during the subsequent emergency restart.

VTAM holds all sessions in recovery pending state for up to the interval specified (unless they are unbound through path failure or VTAM operator action, or other-system action in the case of intelligent LUs). The PSDINT value used must take account of the types and numbers of sessions involved.

You must exercise care when specifying large PSDINT values because of the problems they may give in some environments, in particular:

Notes:
  1. When specifying a PSDINT value, you must consider the number and, more particularly, the nature of the sessions involved. If LU6.2 sessions to other host systems are retained in recovery pending state, the other host systems may experience excessive queuing delays. This point applies to LU6.1 sessions which are retained until restart (when they are unbound).
  2. The PSDINT parameter is incompatible with the XRF=YES parameter. If XRF=YES is specified, the PSDINT parameter is ignored.
PSTYPE={SNPS|MNPS}
specifies whether CICS is running with VTAM single node persistent sessions (SNPS) or multi node persistent sessions (MNPS). Code this parameter if you are using VTAM MNPS and you wish to recover sessions when the VTAM ACB is opened after a VTAM failure. You should read the VTAM Network Implementation Guide to see how VTAM should be set up to use MNPS and under what conditions sessions persist for MNPS.
PVDELAY={30|number}
specifies the persistent verification delay as a value in the range 0 through 10080 minutes (up to 7 days). PVDELAY defines how long entries can remain in the signed-on-from lists for those connections for which persistent verification is specified in a connection resource definition. If you specify PVDELAY=0, entries are deleted immediately after use.

For information about the use of PVDELAY, see the CICS Performance Guide.

QUIESTIM={240|number}
specifies a timeout value for data set quiesce requests.

In a busy CICSplex, it is possible for the default timeout to expire before the quiesce request has been processed by all the CICS regions, even though there is nothing wrong. If the quiesce operation is not completed when the timeout period expires, SMS VSAM cancels the quiesce. If you find that timeout is occurring too frequently, increase the timeout value.

Specify the timeout value as a number of seconds. The default value is 240 seconds (4 minutes)

The maximum timeout value you can specify is 3600 (1 hour).

RAMAX={256|number}
specifies the size in bytes of the I/O area allocated for each RECEIVE ANY issued by CICS, in the range 0 through 32767 bytes.
Note:
If you are using APPC, do not code a value less than 256; otherwise, the results are unpredictable.

For information about coding this parameter, see the CICS Performance Guide.

RAPOOL={50|value1|(value1,value2,FORCE)}
specifies the size of the CICS receive any pool. value1 is the number of fixed request parameter lists (RPLs), receive any control elements (RACEs), and receive any input areas (RAIAs) that are to be generated whether or not CICS uses the high performance option (HPO). value1, in the range 1 through 999, is also the number that are active in a non-HPO system; value2, in the range 0 through 999, is the number that are active in an HPO system. The default for value1 in the DFHSIT macro is 2. The default for value2 is calculated from value1 as follows:
       If value1 = 1, value2 = 1
       If value1 <= 5, value2 = (value1 minus 1)
       If value1 >= 6 and <= 49, value2 = 5
       If value1 >= 50, value2 is 10 per cent of value1
Note:
You should code value1 equal to or greater than value2; if you code value1 less than value2, CICS forces value2 equal to value1.

If you omit the RAPOOL parameter altogether, RAPOOL=(50,1) is assumed. CICS maintains n VTAM RECEIVE ANYs, where n is either the RAPOOL "number active" value, or the MXT value minus the number of active tasks, whichever is the smaller. For example, in a non-HPO system:

    If RAPOOL=2, MXT=50, active tasks = 45 then RECEIVE ANY = 2
    If RAPOOL=10, MXT=50, active tasks = 45 then RECEIVE ANY = 5
    If RAPOOL=10, MXT=50, active tasks = 35 then RECEIVE ANY = 10

or in an HPO system:

    If RAPOOL=(20,10), MXT=50, active tasks = 45 then RECEIVE ANY = 5

FORCE tells CICS to free up Receive_Any_RPLs if they are stalled. CICS decides that the Receive_Any_RPLs are stalled if all the RA RPLs have been posted but the TCTTE for each one is waiting for a response from a VTAM terminal or session for 10 dispatches of the TCP (CSTP) task.

This typically happens only if a protocol error has occurred, and sessions are waiting for a response; for example, to a BID SHUTD request from CICS.

Each session is unbound, the Receive_Any data is lost and the RA RPL is reissued thus allowing VTAM activity to continue: Message DFHZC4949 is issued for each session affected.

Consider increasing the size of the RAPOOL before resorting to the use of FORCE.

If FORCE is not specified and a Receive_Any stall occurs, DFHZC2118 is written to the console for each session affected.

If FORCE is specified in the SIT, and RAPOOL is supplied as an override, you must again specify FORCE as otherwise it defaults to FORCE not specified.

The number of RECEIVE ANYs needed depends on the expected activity of the system, the average transaction lifetime, and the MAXTASK value specified. For information about coding this parameter, see the CICS Performance Guide.

RDSASZE={0K|number}
specifies the size of the RDSA. The default size is 0, indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
specify number as an amount of storage in the range 0 to 16777215 bytes in multiples of 262144 bytes (256KB). If the size specified is not a multiple of 256KB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Restrictions You can specify the RDSAZSE parameter in PARM, SYSIN, or CONSOLE only.

RENTPGM={PROTECT|NOPROTECT}
specifies whether you want CICS to allocate the read-only DSAs, RDSA and ERDSA, from read-only key-0 protected storage. The permitted values are PROTECT (the default), or NOPROTECT:
PROTECT
CICS obtains the storage for the read-only DSAs from key-0 protected storage.
NOPROTECT
CICS obtains the storage from CICS-key storage, effectively creating two more CICS DSAs (CDSA and ECDSA). This allows programs eligible for the read-only DSAs to be modified by programs that execute in CICS key.

You are recommended to specify RENTPGM=NOPROTECT for development regions only, and to specify RENTPGM=PROTECT for production CICS regions.

RESP={FME|RRN}
specifies the type of request that CICS terminal control receives from logical units.
FME
Function management end is the default.
RRN
Reached recovery node.
RESSEC={ASIS|ALWAYS}
specifies whether you want CICS to honor the RESSEC option specified on a transaction’s resource definition.
ASIS
CICS honors the RESSEC option defined in a transaction’s resource definition. CICS calls its resource security checking routine only when RESSEC(YES) is specified in a transaction resource definition. This is normally a sufficient level of control, because often you will need only to control the ability to execute a transaction.
ALWAYS
CICS overrides the RESSEC option, and always calls its resource security checking routine to issue the appropriate call to the SAF interface.

Use this option only if you need to control or audit all accesses to CICS resources. Using this option can significantly degrade performance.

Restrictions You can specify the RESSEC parameter in the SIT, PARM, or SYSIN only.

RLS={NO|YES}
specifies whether CICS is to support VSAM record-level sharing (RLS).
NO
RLS support is not required in this CICS region. Files whose definitions specify RLSACCESS(YES) will fail to open, with an error indicating that RLS access is not supported. You should not specify RLS=NO if you have files that you want to open in RLS access mode (including the CSD).
YES
RLS support is required in this CICS region. During initialization, CICS automatically registers with an SMSVSAM control ACB to enable RLS access to files opened with RLSACCESS(YES).
RLSTOLSR={NO|YES}
specifies whether CICS is to include files that are to be opened in RLS mode when calculating the number of buffers, strings, and other resources for an LSR pool. CICS performs this calculation only when you have not explicitly defined an LSRPOOL resource definition that corresponds to an LSRPOOLID in a file definition. CICS calculates and builds a default LSR pool only when it is opening the first file in LSR mode that references the default pool.
NO
CICS is not to include files opened in RLS mode, and which also specify an LSRPOOLID, when it is building default LSR pools. Files defined with RLSACCESS(YES) are ignored when CICS is scanning file entries looking for files that specify an LSR pool it is about to build using default values.

If the LSR pools referenced by LSRPOOLIDs in your file resource definitions are defined explicitly by LSRPOOL resource definitions, you should specify RLSTOLSR=NO.

YES
CICS is to include in its calculation, when building default LSR pools, files that specify both RLSACCESS(YES) and an LSRPOOLID.

Note that an LSR pool built including files that are opened in RLS mode is larger than necessary initially. This option is provided to ensure that, if files are subsequently switched to LSR, the LSR pool is adequate for the extra files. You should specify RLSTOLSR=YES only if both of the following conditions are true:

  1. You do not define LSR pools explicitly, relying instead on CICS obtaining a default set of values for you.
  2. You have files that are sometimes accessed in RLS mode and sometimes accessed in non-RLS mode (although this is generally not recommended).

The RLSTOLSR parameter is provided to support files that are normally opened in RLS mode, but which may be closed and then switched to LSR mode.

If LSR pools are not defined explicitly using LSRPOOL resource definitions, CICS calculates the resources needed for an LSR pool using default attributes. CICS performs this calculation when opening the first file that specifies an LSR pool that is not explicitly defined. To calculate a default LSR pool, CICS scans all the file entries to count all the files that specify the same LSRPOOLID. The size of an LSR pool built dynamically in this way remains fixed until all files that reference the LSR pool are closed. After all files have been closed, another request to open a file with the same LSRPOOLID causes CICS to recalculate the size.

If you add files to the system after the LSR calculation has been performed there may be insufficient storage available to enable CICS to open a file that specifies a default pool. This situation could occur if files are opened initially in RLS mode and later closed and reopened in LSR mode. There are two ways to ensure that enough resources are built into the LSR pool to support subsequent switches of files from RLS to LSR:

  1. You can explicitly define LSRPOOL resource definitions that correspond to the LSRPOOLIDs on file definitions, removing the need for CICS to calculate default values.
  2. You can specify RLSTOLSR=YES to force CICS to include RLS files when calculating defaults.
RMTRAN=({CSGM|name1}[,{CSGM |name2}])
specifies the name of the transaction that you want an alternate CICS to initiate when logged-on class 1 terminals, which are defined with the attribute RECOVNOTIFY(TRANSACTION) specified, are switched following a takeover. This parameter is applicable only on an alternate CICS region.

If you do not specify a name here, CICS uses the CSGM transaction, the default CICS good morning transaction.

name1
This is the transaction that CICS initiates at terminals that do not remain signed-on after the takeover (that is, they are still connected to CICS, but are signed off).
name2
This is the transaction that CICS initiates at terminals that remain signed-on after the takeover. If you specify only name1, CICS uses the CSGM transaction as the default for name2.

Start of changeIf you are using VSAM persistent sessions, the name2 transaction is ignored and the name1 transaction is always initiated.End of change

RRMS=NO|YES
specifies whether CICS is to register as a resource manager with recoverable resource management services (RRMS).
NO
You do not require RRMS support.
YES
You require RRMS support to enable DPL requests to be coordinated by resource recovery services (RRS).
Note:
If you specify RRMS=YES, ensure that the DFHRXSVC module is available during CICS initialization. This module, which provides RRMS authorized services, is supplied in the SDFHLINK library. For information about this link list library, see the CICS Transaction Server for z/OS Installation Guide.
RST={NO|xx|YES}
specifies a recoverable service table suffix. (See topic Defining CICS resource table and module keywords.) For information about coding the macros for this table, see the CICS Resource Definition Guide.

If you are running CICS with XRF=YES, and you are using DBCTL, you must specify an RST if you want XRF support for DBCTL. For information about the use of the RST in a CICS-DBCTL environment with XRF=YES, see the CICS IMS Database Control Guide .

RSTSIGNOFF={NOFORCE|FORCE}
specifies whether all users signed-on to the active CICS region are to remain signed-on following a persistent sessions restart or an XRF takeover. Itaplies to the following events:
NOFORCE
Do not sign off users, unless FORCE is specified on either:
  • The RSTSIGNOFF parameter in the TYPETERM definition referenced by the user's terminal definition.
  • The XRFSOFF parameter in the CICS segment of the user's RACF profile.

Thus for a user to remain signed on after a persistent sessions restart or an XRF takeover, NOFORCE must be specified as a system initialization parameter, on the TYPETERM definition, and in the CICS segment.

FORCE
Sign off all users regardless of the options specified on:
  • The RSTSIGNOFF parameter in the TYPETERM definition referenced by the user's terminal definition.
  • The XRFSOFF parameter in the CICS segment of the user's RACF profile.

See the CICS RACF Security Guide for information about user profile options in the CICS segment, and see the CICS Resource Definition Guide for information about the TYPETERM resource definition.

RSTSIGNTIME={5|decimal-value}
Specifies the time-out delay interval for signon retention during a persistent sessions restart or an XRF takeover. You can specify a 1-to-6 digit time in hours, minutes and seconds, up to the maximum time of 23 hours 59 minutes 59 seconds. If you specify less than six digits, CICS pads the value with leading zeros. Thus a value of 500 is taken as five minutes exactly.

RSTSIGNTIME is counted from the time when CICS failed. Note that the time of failure cannot be determined with complete accuracy.

If you specify NOFORCE on all the appropriate parameters to enable a user to remain signed on, but the persistent sessions restart or XRF takeover takes longer than the specified on the RSTSIGNTIME parameter, CICS ensures users do not remain signed on after the delay period expires.

500
Five minutes is the default value.
time
This is the time, in the range 0 through 23 hours 59 minutes 59 seconds, during which CICS permits users to remain signed on during a persistent sessions restart or an XRF takeover. The period is measured as follows:
  • For a persistent sessions restart, the period is the time from the CICS failure and the time when the user starts working on the terminal. If the specified time expires before the user starts working on the terminal, users signed on at the time CICS failed are not signed on again after restart.
  • For an XRF takeover, the period is the time from when the takeover is initiated to the time at which the alternate CICS has completed takeover and is ready to process user transactions. If the takeover takes longer than the specified period, all users signed on at the time the takeover was initiated are signed off.

A value of 0 means there is no time-out delay, and terminals are not signed on after a persistent sessions restart or XRF takeover, which means that RSTSIGNTIME=0 has the same effect as coding RSTSIGNOFF=FORCE.

When XRF is in use with non-XRF-capable terminals, take into account any AUTCONN delay period when setting the value for RSTSIGNTIME. For example, you may need to increase the time specified on RSTSIGNTIME to allow for the delay up to the start of the CXRE transaction imposed by the AUTCONN parameter; otherwise, terminals could be signed off too early.

RUWAPOOL={NO|YES}
specifies the option for allocating a storage pool the first time a program invoked by Language Environment runs in a task.
NO
CICS disables the option and provides no RUWA storage pool. Every EXEC CICS LINK to a program that runs under Language Environment results in a GETMAIN for RUWA storage.
YES
CICS creates a pool of storage the first time a program invoked by Language Environment runs in a task. This provides an available storage pool that reduces the need to GETMAIN and FREEMAIN run-unit work areas (RUWAs) for every EXEC CICS LINK request.
Note:
This applies only to application programs running with the Language Environment run-time option ALL31(ON). RUWAPOOL=YES has no effect on application programs running with the Language Environment run-time option ALL31(OFF).
SDSASZE={0K|number}
specifies the size of the SDSA. The default size is 0, indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
specify number as an amount of storage in the range 0 to 16777215 bytes in multiples of 262144 bytes (256KB). If the size specified is not a multiple of 256KB, CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Restrictions You can specify the SDSAZSE parameter in PARM, SYSIN, or CONSOLE only.

SDTRAN={CESD|name_of_shutdown_tran|NO}
specifies the name of the shutdown transaction to be started at the beginning of normal and immediate shutdown.

The shutdown transaction enables CICS to shut down in a controlled manner, within a reasonable period of time. For example, you can use it to purge and backout long-running tasks, while ensuring that as many tasks as possible commit or backout cleanly. For information about the CICS-supplied program, DFHCESD, started by the default shutdown transaction, CESD, and how to use it as the basis for your own transaction, see the CICS Operations and Utilities Guide.

Notes:
  1. The transaction runs under the userid authority of the issuer of the shutdown command.
  2. If the program named by the shutdown transaction cannot be loaded, CICS waits indefinitely for all user tasks to complete. This happens on an immediate, as well as on a normal, shutdown.
CESD
Starts the CICS-supplied program DFHCESD.
name_of_shutdown_transaction
The 1-to 4-character name of your own shutdown transaction.
NO
No shutdown transaction is to be run. On a normal shutdown, CICS waits indefinitely for all user tasks to complete.
SEC={YES|NO}
specifies what level of external security you want CICS to use.
YES
You want to use full external security. CICS requires the appropriate level of authorization for the access intent: a minimum of READ permission for read intent, and a minimum of UPDATE permission for update intent.
Note:
You must also ensure that the default userid (CICSUSER or another userid specified on the DFLTUSER system initialization parameter) has been defined to RACF.

If command security checking is defined for CICS SP-type commands, then specifying SEC=YES means that the appropriate level of authority is checked for; therefore:

  • A check for READ authority is made for INQUIRE and COLLECT commands.
  • A check for UPDATE authority is made for SET, PERFORM, and DISCARD commands.

    For the results of the interaction between the access intent of the user application, and the permission defined to RACF, see Table 23.

NO
You do not want CICS to use an external security manager. All users have access to all resources, whether determined by attempts to use them or by the QUERY SECURITY command. Users are not allowed to sign on or off.
Note:
With MRO bind-time security, even if you specify SEC=NO, the CICS region userid is still sent to the secondary CICS region, and bind-time checking is still carried out in the secondary CICS region. For information about MRO bind-time security, see the CICS RACF Security Guide.

Define whether to use RACF for resource level checking by using the XDCT, XFCT, XJCT, XPCT, XPPT, XPSB, and XTST system initialization parameters. Define whether to use RACF for transaction-attach security checking by using the XTRAN system initialization parameter. Define whether to use RACF for enterprise bean method authorization checks by using the XEJB system initialization parameter. Define whether RACF session security can be used when establishing APPC sessions by using the XAPPC system initialization parameter.

For information on defining command security checking for CICS SP-type commands, and about CICS security in general, see the CICS RACF Security Guide.

For programming information about the use of external security for CICS system commands, see CICS System Programming Reference.

Table 23. Results of RACF authorization requests (with SEC=YES)
Access Permission defined to RACF for CICS user Access intent in application
READ UPDATE
NONE Refused Refused
READ Permitted Refused
UPDATE Permitted Permitted

Restrictions You can specify the SEC parameter in the SIT, PARM, or SYSIN only.

Note:
If you are using preset terminal security (see CICS RACF Security Guide), and you perform a warm start with SEC=NO and then again with SEC=YES, you must reinstall the terminal definition to preserve the preset user ID that is replaced by the default user ID when security is switched off.
SECPRFX={NO|YES|prefix}
specifies whether CICS is to prefix the resource names in any authorization requests to the external security manager.
NO
CICS does not use prefixes on any resource names.
YES
CICS prefixes all resource names with the CICS region user ID. This is the user ID under which the CICS job runs. It is one of the following:
  • If CICS is a batch job, it is the user ID corresponding to the USER parameter of the CICS JOB statement.
  • If CICS is a started task, it is the user ID associated with the name of the started procedure in the RACF ICHRIN03 table.
  • If CICS is a started job, it is the user ID specified in the user parameter of the STDATA segment of a STARTED general resource class profile.

For more information, see the CICS RACF Security Guide.

prefix
CICS prefixes all resource names with the string you specify. It can be any string of 1 to 8 upper case alphanumeric characters except NO or YES, and must start with an alphabetic character.

Restrictions You can specify the SECPRFX parameter in the SIT, PARM, or SYSIN only.

The SECPRFX parameter is effective only if you specify YES for the SEC system initialization parameter.

SIT=xx
specifies the suffix, if any, of the system initialization table that you want CICS to load at the start of initialization. If you omit this parameter, CICS loads the unsuffixed table, DFHSIT, which is pregenerated with all the default values. This default SIT (shown in The default system initialization table) is in CICSTS31.CICS.SDFHAUTH, and its source, named DFHSIT$$, is in CICSTS31.CICS.SDFHSAMP.

Restrictions You can specify the system initialization parameter anywhere in PARM or SYSIN, or as the first parameter entry at the CONSOLE.

SKRxxxx=‘page-retrieval-command’
specifies that a single-keystroke-retrieval operation is required. ‘xxxx’ specifies a key on the 3270 keyboard which, during a page retrieval session, is to be used to represent a page retrieval command. The valid keys are PA1 through PA3, and PF1 through PF36. Thus up to 39 keys can be specified in this way (each by a separate command).

The ‘page-retrieval-command’ value represents any valid page retrieval command, and must be enclosed in apostrophes. It is concatenated to the character string coded in the PGRET parameter. The combined length must not exceed 16 characters.

Note:
If full function BMS is used, all PA keys and PF keys are interpreted for page retrieval commands, even if some of these keys are not defined.
SNSCOPE={NONE|CICS|MVSIMAGE|SYSPLEX}
specifies whether a userid can be signed on to CICS more than once, within the scope of:

The signon SCOPE is enforced with the MVS ENQ macro where there is a limit on the number of outstanding MVS ENQs per address space. If this limit is exceeded, the MVS ENQ is rejected and CICS is unable to detect if the user is already signed on. When this happens, the signon request is rejected with message DFHCE3587. See the OS/390 MVS Programming: Authorized Assembler Services Guide for guidance on increasing the MVS ENQ limit.

NONE
Each userid can be used to sign on for any number of sessions on any CICS region. This is the compatibility option, providing the same signon scope as in releases of CICS before CICS Transaction Server for z/OS, Version 3 Release 1.
CICS
Each userid can be signed on once only in the same CICS region. A signon request is rejected if the userid is already signed on to the same CICS region. However, the userid can be used to signon to another CICS region in the same, or another, MVS image.
MVSIMAGE
Each userid can be signed on once only, and to only one of the set of CICS regions in the same MVS image that also specify SNSCOPE=MVSIMAGE. A signon request is rejected if the user is already signed on to another CICS region in the same MVS image.
SYSPLEX
Each userid can be signed on once only, and to only one of the set of CICS regions within an MVS sysplex that also specify SNSCOPE=SYSPLEX. A signon is rejected if the user is already signed on to another CICS region in the same MVS sysplex.

The signon scope (if specified) applies to all userids signing on by an explicit signon request (for example, by an EXEC CICS SIGNON command or the CESN transaction). SNSCOPE is restricted to users signing on at local terminals, or signing on after using the CRTE transaction to connect to another system.

Signon scope specified by SNSCOPE does not apply to:

Restrictions You can specify the SNSCOPE parameter in the SIT, PARM, or SYSIN only.

SPCTR={(1,2)|(1[,2][,3])|ALL|OFF}
specifies the level of tracing for all CICS components used by a transaction, terminal, or both, selected for special tracing. If you want to set different tracing levels for an individual component of CICS, use the SPCTRxx system initialization parameter. For a list of all the available trace points and their level numbers, see Start of changeCICS Trace EntriesEnd of change. For information about the differences between special and standard CICS tracing, see the CICS Problem Determination Guide.

It is possible to select up to 32 levels of tracing using the SPCTR system initialization parameter. However, most CICS components only use levels 1, 2 and 3, and some do not have trace points at all these levels. The exceptions are the SM component (storage manager domain), which also has level 4 tracing; and the SJ component (JVM domain), which also has trace levels 29-32, that are reserved to indicate the JVM trace levels 0, 1, and 2, plus a user-definable JVM trace level. You are recommended to use the SPCTRxx system initialization parameter, rather than the SPCTR system initialization parameter, to set special tracing levels above 3 for these components.

number
The level numbers for the level of special tracing you want for all CICS components. The normal options are: 1, (1,2), or (1,2,3). The default, (1,2), specifies special tracing for levels 1 and 2 for all CICS components.
ALL
Enables the special tracing facility for all available levels.
OFF
Disables the special tracing facility.
SPCTRxx={(1,2 )|(1[,2][,3][,4][,29][,30][,31][,32])|ALL|OFF}
specifies the level of tracing for a particular CICS component used by a transaction, terminal, or both, selected for special tracing. You identify the component by coding a value for xx in the keyword. You code one SPCTRxx keyword for each component you want to define selectively. For a CICS component being specially traced that does not have its trace level set by SPCTRxx, the trace level is that set by SPCTR (which, in turn, defaults to (1,2)). The CICS component codes that you can specify for xx on the SPCTRxx keyword are shown in Table 24:
Table 24. CICS component names and abbreviations
Code Component name Code Component name
AP Application domain BA Business application manager
BM Basic mapping support BR 3270 Bridge
CP Common programming interface DC Dump compatibility layer
DD Directory manager DH Document handler domain
DM Domain manager domain DP Debugging profiles domain
DS Dispatcher domain DU Dump domain
EI Exec interface EJ Enterprise Java domain
EM Event manager domain FC File control
GC Global catalog domain IC Interval control
IE ECI over TCP/IP domain II IIOP domain
IS Inter-system communication KC Task control
KE Kernel LC Local catalog domain
LD Loader domain LG Log manager domain
LM Lock manager domain ME Message domain
MN Monitoring domain NQ Enqueue manager
OT Object transaction services domain PA Parameter domain
PC Program control PG Program manager domain
PI Pipeline manager domain PT Partner domain
RI Resource manager interface (RMI) RM Recovery manager
RX RRMS domain RZ Request streams
SC Storage control SH Scheduler services domain
SJ JVM domain SM Storage manager domain
SO Sockets domain ST Statistics domain
SZ Front end programming interface TC Terminal control
TD Transient data TI Timer domain
TR Trace domain TS Temporary storage
UE User exit interface US User domain
WB WEB domain XM Transaction manager
XS Security domain
number
The level numbers for the level of special tracing you want for the CICS component indicated by xx. Level numbers 1, 2, 3, 4, 29, 30, 31 and 32 can be used, depending on the component.

Most CICS components only use levels 1, 2 and 3, and some do not have trace points at all these levels. The exceptions are:

  • The SM component (storage manager domain), which also has level 4 tracing. This level of tracing is intended for IBM field engineering staff.
  • The SJ component (JVM domain), which also has trace levels 29-32, that are reserved to indicate the JVM trace levels 0, 1, and 2, plus a user-definable JVM trace level. You can use the system initialization parameters JVMLEVEL0TRACE, JVMLEVEL1TRACE, JVMLEVEL2TRACE and JVMUSERTRACE to specify options for these JVM trace levels, and then activate them using the SPCTRSJ system initialization parameter.
ALL
You want all the available levels of special CICS tracing switched on for the specified component.
OFF
Switches off all levels of special CICS tracing for the CICS component indicated by xx.

For details of using trace, see the CICS Problem Determination Guide.

Notes:
  1. The component codes BA, BM, CP, DC, DH, EI, FC, IC, IS, KC, PC, SC, SP, TC, TD, and UE are sub-components of the AP domain. As such, the corresponding trace entries are produced with a point ID of AP nnnn.
  2. When you activate JVM trace, using trace levels 29-32 for the SJ component, the JVM trace appears as CICS trace point SJ 4D01.

Restrictions You can specify the SPCTRxx parameter in PARM, SYSIN, or CONSOLE only.

SPOOL={NO|YES}
specifies whether the system spooling interface is required.
NO
The system spooling interface is not required.
YES
The system spooling interface is required.
Start of changeThe CICS spool interface uses the MVS exit, IEFDOIXT, which is provided in the SYS1.LINKLIB library. For further information about the MVS exit IEFDOIXT, see the current z/OS release information on z/OS MVS Installation Exits.End of change
SRBSVC={215|number}
specifies the number that you have assigned to the CICS type 6 SVC. The default number is 215.

For information on changing the SVC number, see "Installing the CICS Type3 SVC" and "Selecting the high-performance option" in the CICS Transaction Server for z/OS Installation Guide. A CICS type 6 SVC with the specified (or default) number must have been link-edited with the system nucleus.

SRT={1$|YES|NO|xx}
specifies the system recovery table suffix (see topic Defining CICS resource table and module keywords.) For information about coding the macros for this table, see the CICS Resource Definition Guide manual.

If SRT=YES is coded, the default DFHSRT1$ table is used.

If SRT=NO is coded, the system recovery program (DFHSRP) does not attempt to recover from a program check or from an operating system abend. However, CICS issues ESPIE macros to intercept program checks to perform clean-up operations before CICS terminates. Therefore, an SRT must be provided if recovery from either program checks or abnormal terminations, or both, is required.

Start of changeSRVERCP={037|codepage} End of change
Start of changeSpecifies the default server code page to be used by the DFHCNV data conversion table but only if the SRVERCP parameter in the DFHCNV macro is set to SYSDEF. The codepage is a field of up to 8 characters and can take the values supported by the SRVERCP parameter in the DFHCNV macro. See the CICS Family: Communicating from CICS on System/390 for the list of valid code pages. The default is 037.End of change
Start of changeSSLCACHE={CICS| SYSPLEX}End of change
Start of changeSpecifies whether SSL is to use the local or sysplex caching of session ids. Sysplex caching is only allowed if multiple CICS socket-owning regions accept SSL connections at the same IP address.End of change
SSLDELAY={600| number}

Specifies the length of time in seconds for which CICS retains session ids for secure socket connections. Session ids are tokens that represent a secure connection between a client and an SSL server.

While the session id is retained by CICS within the SSLDELAY period, CICS can continue to communicate with the client without the significant overhead of an SSL handshake. The value is a number of seconds in the range 0 through 86400.

Start of changeSSLTCBS={8| number]} End of change
Start of changeThis parameter is now obsolete and is only kept for compatibility. If it is specified, it is rejected with a message and MAXSSLTCBS is assumed.End of change
START=({AUTO|INITIAL|COLD|STANDBY}[,ALL])
specifies the type of start for the system initialization program. The value specified for START, or the default of AUTO, becomes the default value for each resource.
AUTO
CICS performs a warm, emergency, cold or initial start, according to the status of two control records on the global catalog:
  • The recovery manager (RM) control record written by the previous execution of CICS
  • The RM autostart override record written by a run of the recovery manager utility program, DFHRMUTL
Note:
If the global catalog does not contain the RM control record:
  • If it contains an RM autostart override record with option AUTOINIT, CICS performs an initial start.
  • If it does not contain an RM autostart override record with option AUTOINIT, CICS does not start.

If you code START=AUTO, you must do one of the following:

  • Provide the global catalog and system log from the previous execution of CICS. For an emergency restart to be successful, you must also have coded an activity keypoint value (see the AKPFREQ parameter in topic AKPFREQ) on the previous execution of CICS.
  • Provide a global catalog against which you have run the DFHRMUTL utility program, specifying SET_AUTO_START=AUTOINIT.

You may choose to leave the START parameter set to AUTO for all types of startup other than XRF standby, and use the DFHRMUTL program to reset the startup mode to COLD or INITIAL when necessary, using SET_AUTO_START=AUTOCOLD or SET_AUTO_START=AUTOINIT, respectively. For information about the DFHRMUTL utility program, see the CICS Operations and Utilities Guide.

INITIAL
The status of CICS resource definitions saved in the global catalog at the previous shutdown is ignored, and all resource definitions are reinstalled, either from the CSD or CICS control tables.

You should rarely need to specify START=INITIAL; if you simply want to reinstall definitions of local resources from the CSD, use START=COLD instead.

Examples of times when an initial start is necessary are:

  • When bringing up a new CICS system for the first time.
  • After a serious software failure, when the system log has been corrupted.
  • If the global catalog is cleared or initialized.
  • When you want to run CICS with a dummy system log. (If the system log is defined as a dummy, it is ignored.)
COLD
The status of CICS resource definitions saved in the global catalog at the previous shutdown is ignored, and all resource definitions (except those for the system log) are reinstalled, either from the CSD or CICS control tables.

Resynchronization information in the global catalog relating to remote systems or to RMI-connected resource managers is preserved. The CICS system log is scanned during startup, and information regarding unit of work obligations to remote systems, or to non-CICS resource managers (such as DB2) connected through the RMI, is preserved. (That is, any decisions about the outcome of local UOWs, needed to allow remote systems or RMI resource managers to resynchronize their resources, are preserved.)

Note that, on a cold start, the following are not preserved:

  • Updates to local resources that were not fully committed or backed out during the previous execution, even if the updates were part of a distributed unit of work.
  • Resynchronization information for remote systems connected by LU6.1 links, or for earlier releases of CICS systems connected by MRO.

If you want to reinstall resource definitions from the CSD, use START=COLD rather than START=INITIAL.

STANDBY
Coding START=STANDBY, but only when you have also specified XRF=YES, defines this CICS as the alternate CICS region in an XRF pair. In other words, you must specify START=STANDBY for the system that starts off as the alternate. (To start an active CICS region, specify AUTO or COLD, as you would without XRF.)
(option,ALL)
The ALL option is a special option you can use on the START parameter when you supply it as a system initialization parameter at CICS startup; you cannot code it in the SIT. If you specify START=(AUTO,ALL), CICS initializes all resources according to the type of startup that it selects (warm, emergency, initial, or cold). The ALL option overrides any individual settings in other system initialization parameters.

However, if you do not use the ALL option, you can individually cold start those resources that have a COLD operand. For details of resources that have a COLD option, see Table 18.

Restrictions You can specify START=(option,ALL) in PARM, SYSIN, or CONSOLE only.

For more information about the types of CICS startup, see Controlling start and restart.

STARTER={NO|YES}
specifies whether the generation of starter system modules (with $ and # suffixes) is permitted, and various MNOTES are to be suppressed. This parameter should only be used when service is being performed on starter system modules.

Restrictions You can specify the STARTER parameter in the SIT only.

STATEOD={0|hhmmss}
specifies the end-of-day time in the format hhmmss. The default is 0, which is midnight.

End-of-day time is expressed in local time and must be in the range 00:00:00-23:59:59. That is, the hh value cannot exceed 23, and the mm and ss values can be specified in the range 00 to 59. If you leave out leading zeros, the DFHSIT macro inserts them (for example, 100 becomes 000100--that is, 1 minute 00 seconds past midnight).

This parameter is the equivalent of the ENDOFDAY option on the CEMT and EXEC CICS SET STATISTICS command, which you can use to modify the value set by STATEOD.

STATINT={030000|hhmmss }
specifies the recording interval for system statistics in the format hhmmss. The default is 3 hours.

The interval must be at least one minute and cannot be more than 24 hours. The minutes and seconds part of the value can be specified in the range 00 to 59. If you leave out leading zeros, the DFHSIT macro inserts them (for example, 3000 becomes 003000--that is, an interval of 30 minutes).

This parameter is the equivalent of the INTERVAL option on the CEMT and EXEC CICS SET STATISTICS command, which you can use to modify the value set by STATINT.

STATRCD={OFF|ON}
specifies the interval statistics recording status at CICS initialization. This status is recorded in the CICS global catalog for use during warm and emergency restarts. Statistics collected are written to the SMF data set.
OFF
Interval statistics are not collected (no action is taken at the end of an interval).

End-of-day statistics are collected at the logical end of day and on shutdown. Unsolicited statistics are written to SMF as resources are discarded or closed.

ON
Interval statistics are collected.

On a cold start of a CICS region, interval statistics are recorded by default at three-hourly intervals. All intervals are timed using the end-of-day time (midnight is the default) as a base starting time (not CICS startup time). This means that the default settings give collections at 00.00, 03.00, 06.00, 09.00, and so on, regardless of the time that you start CICS.

On a warm or emergency restart the statistics recording status is restored from the CICS global catalog.

You can change the statistics recording status at any time as follows:

Whatever the value of the STATRCD system initialization parameter, you can ask for requested statistics and requested reset statistics to be collected. You can get statistics "on demand" for all, or for specified, resource types by using the CEMT or EXEC CICS PERFORM STATISTICS command. The period covered for statistics requested in this way is from the last reset time (that is, from the beginning of the current interval or from when you last issued a CEMT or EXEC CICS statistics command specifying RESETNOW) up to the time that you issue the PERFORM STATISTICS command.

For information about using these CEMT commands, see CICS Supplied Transactions. For programming information about the EXEC CICS PERFORM commands, see the CICS System Programming Reference manual. For information about the statistics utility program DFHSTUP, or recording statistics in the sample program hlq.SAMPLIB, see the CICS Operations and Utilities Guide. For information about the sample programs, see the CICS Operations and Utilities Guide.

STGPROT={NO|YES}
specifies whether you want storage protection in the CICS region. The permitted values are NO (the default), or YES:
NO
If you specify NO, or allow this parameter to default, CICS does not operate any storage protection, and runs in a single storage key as in earlier releases. See Table 31 for a summary of how STGPROT=NO affects the storage allocation for the dynamic storage areas.
YES
If you specify YES, and if you have the required hardware and software, CICS operates with storage protection, and observes the storage keys and execution keys that you specify in various system and resource definitions. See Table 31 for a summary of how STGPROT=YES affects the storage allocation for the dynamic storage areas.

If you do not have the required hardware and software support, CICS issues an information message during initialization, and operates without storage protection.

STGRCVY={NO|YES}
specifies whether CICS should try to recover from a storage violation.
NO
CICS does not try to repair any storage violation that it detects.
YES
CICS tries to repair any storage violation that it detects.

In both cases, CICS continues unless you have specified in the dump table that CICS should terminate.

In normal operation, CICS sets up four task-lifetime storage subpools for each task. Each element in the subpool starts and ends with a ‘check zone’ that includes the subpool name. At each freemain, and at end-of-task, CICS checks the check zones and abends the task if either has been overwritten.

Terminal input-output areas (TIOAs) have similar check zones, which are set up with identical values. At each freemain of a TIOA, CICS checks the check zones and abends the task if they are not identical.

If you specify STGRCVY(YES), CICS resets the check zones correctly and the task continues running.

Start of changeIf you specify STGRCVY(NO), CICS abends the task if it is still running. The storage is not reusable and is not returned to the DSA for the remainder of the CICS cycle. If an error is detected when the task ends, no abend is issued. Any sync point that has taken place could save data that is corrupted.End of change

STNTR={1|(1[,2][,3])|ALL|OFF}
specifies the level of standard tracing required for CICS as a whole.

It is possible to select up to 32 levels of tracing using the STNTR system initialization parameter. However, most CICS components only use levels 1, 2 and 3, and some do not have trace points at all these levels. The exceptions are the SM component (storage manager domain), which also has level 4 tracing; and the SJ component (JVM domain), which also has trace levels 29-32, that are reserved to indicate the JVM trace levels 0, 1, and 2, plus a user-definable JVM trace level. You should use the STNTRxx system initialization parameter, rather than the STNTR system initialization parameter, if you need to set standard tracing levels above 3 for these components.

Note:
Warning! Before globally activating tracing levels 3 and ALL, which will set these tracing levels for the storage manager (SM) component and the JVM domain (SJ) component, read the warnings given in the description for the STNTRxx system initialization parameter.

number
Code the level number(s) for the level of standard tracing you want for all CICS components. The options are: 1, (1,2), or (1,2,3). The default, 1, specifies standard tracing for level 1 for all CICS components.
ALL
Enables standard tracing for all levels.
OFF
Disables standard tracing.

For information about the differences between special and standard CICS tracing, see the CICS Problem Determination Guide.

STNTRxx={1|(1[,2][,3][,4][,29][,30][,31][,32])|ALL|OFF}
specifies the level of standard tracing you require for a particular CICS component. You identify the component by coding a value for xx in the keyword. You code one STNTRxx keyword for each component you want to define selectively. For a CICS component being specially traced that does not have its trace level set by STNTRxx, the trace level is that set by STNTR (which, in turn, defaults to 1). You can select up to three levels of tracing, but some CICS components do not have trace points at all these levels.

The CICS component codes that you can specify for xx on this STNTRxx keyword are shown in Table 24.

ALL
You want all the available levels of standard tracing switched on for the specified component.

Start of changeWarning! Selecting ALL for standard tracing for the storage manager (SM) component, or the temporary storage domain (TS), degrades the performance of your CICS region. This is because ALL switches on trace flags that are used by SM domain for field engineering purposes.End of change

Start of changeWarning! Selecting ALL for standard tracing for the JVM domain (SJ) component is not recommended. JVM trace can produce a large amount of output, so you should normally activate JVM trace for special transactions (using the SPCTRSJ system initialization parameter), rather than turning it on globally for all transactions.End of change

number
The level number(s) for the level of standard tracing you want for the CICS component indicated by xx. Level numbers 1, 2, 3, 4, 29, 30, 31 and 32 can be used, depending on the component.

Most CICS components only use levels 1, 2 and 3, and some do not have trace points at all these levels. The exceptions are:

  • The SM component (storage manager domain), which also has level 4 tracing. This level of tracing is intended for IBM field engineering staff.

    Warning! Selecting tracing levels 3, 4, or ALL for standard tracing for the storage manager (SM) component, or the temporary storage domain (TS), degrades the performance of your CICS region. This is because options 3 and 4 (and ALL) switch on trace flags that are used by SM domain for field engineering purposes.

    SM trace flag 3 deactivates the quickcell mechanism, and SM trace flag 4 forces subpool element chaining on every CICS subpool. Furthermore, once these settings have been activated during system initialization, they cannot be unset, either through a PLTPI program or by using the CETR trace transaction, because they are not used for tracing as such. Thus, a significant performance overhead is incurred if these storage manager trace levels are selected for standard tracing.

    See the CICS Problem Determination Guide for information about the effects of trace levels 3 and 4.

  • The SJ component (JVM domain), which also has trace levels 29-32, that are reserved to indicate the JVM trace levels 0, 1, and 2, plus a user-definable JVM trace level. You can use the system initialization parameters JVMLEVEL0TRACE, JVMLEVEL1TRACE, JVMLEVEL2TRACE and JVMUSERTRACE to specify options for these JVM trace levels, and then activate them using the SPCTRSJ system initialization parameter.

    Warning! Selecting tracing levels 29, 30, 31, 32 or ALL for standard tracing for the JVM domain (SJ) component is not recommended. JVM trace can produce a large amount of output, so you should normally activate JVM trace for special transactions (using the SPCTRSJ system initialization parameter), rather than turning it on globally for all transactions.

OFF
Switches off all levels of standard CICS tracing for the CICS component indicated by xx.

Restrictions You can specify the STNTRxx parameter in PARM, SYSIN, or CONSOLE only.

SUBTSKS={0|1}
specifies the number of task control blocks (TCBs) you want CICS to use for running tasks in concurrent mode. A concurrent mode TCB allows CICS to perform management functions as system subtasks.

CICS always uses at least two TCBs:

  1. The quasi-reentrant mode TCB. CICS runs all user applications under this TCB.
  2. The resource-owning mode TCB. CICS runs tasks that open and close files under this TCB.

If you specify SUBTSKS=0, CICS runs under these two TCBs.

If you specify SUBTSKS=1, CICS uses an additional TCB, a concurrent mode TCB, to perform system subtasking functions.

SUFFIX=xx
specifies the last two characters of the name of this system initialization table.

The first 6 characters of the name of the SIT are fixed as DFHSIT. You can specify the last two characters of the name, using the SUFFIX parameter. Because the SIT does not have a TYPE=INITIAL macro statement like other CICS resource control tables, you specify its SUFFIX on the TYPE=CSECT macro statement.

The suffix allows you to have more than one version of the SIT. Any one or two characters (other than NO and DY) are valid. You select the version of the table to be loaded into the system during system initialization by coding SIT=xx, either in the PARM parameter or the SYSIN data set. (You can, in some circumstances, specify the SIT using the system console, but this is not recommended.)

Restrictions You can specify the SUFFIX parameter in the SIT only.

SYDUMAX={999|number}
specifies the limit on the number of system dumps that can be taken per dump table entry. If this number is exceeded, subsequent system dumps for that particular entry will be suppressed. The SYDUMAX parameter applies for new or added system dump codes. It does not override the limit on the number of system dumps for existing dump table entries.
number
A number in the range 0 through 999. The default, 999, enables an unlimited number of dumps to be taken.
SYSIDNT={CICS|name}
specifies a 1-to 4-character name that is known only to your CICS region. If your CICS region also communicates with other CICS regions, the name you choose for this parameter to identify your local CICS region must not be the same name as an installed CONNECTION resource definition for a remote region.

The value for SYSIDNT, whether specified in the SIT or as an override, can only be updated on a cold start. After a warm start or emergency restart, the value of SYSIDNT is that specified in the last cold start.

For information about the SYSIDNT of a local CICS region, see the CICS Intercommunication Guide.

SYSTR={ON|OFF}
specifies the setting of the master system trace flag.
ON
The master trace flag is set, causing CICS to write trace entries of system activity for the individual CICS components. Trace entries are captured and written only for those components for which the trace level is 1 or greater, as specified on the STNTR or STNTRxx system initialization parameters. Entries are written only to those trace destinations that are active.
OFF
The master trace flag is unset, and no standard trace entries are captured, overriding any trace levels specified by the STNTR or STNTRxx system initialization parameters.
Note:
Setting the master trace flag OFF affects only standard tracing and has no effect on special tracing, which is controlled separately by SPCTR or SPCTRxx trace levels and the CETR transaction.

See the CICS Problem Determination Guide for more information about controlling CICS trace.

TAKEOVR={MANUAL|AUTO|COMMAND} (alternate)
Use this parameter in the SIT for an alternate CICS region. It specifies the action to be taken by the alternate CICS region, following the (apparent) loss of the surveillance signal in the active CICS region. In doing this, it also specifies the level of operator involvement.

If both active and alternate CICS regions are running under different MVS images in the same sysplex, and an MVS failure occurs in the MVS image of the active CICS region, the TAKEOVR option is overridden.

MANUAL
The operator is asked to approve a takeover if the alternate CICS region cannot detect the surveillance signal of the active CICS region.

The alternate CICS region does not ask the operator for approval if the active CICS region signs off abnormally, or if there is an operator or program command for takeover. In these cases, there is no doubt that the alternate CICS region should take over, and manual involvement by the operator would be an unnecessary overhead in the takeover process.

You could use this option, for instance, to ensure manual takeover of a master or coordinator region in MRO.

AUTO
No operator approval, or intervention, is needed for a takeover.
COMMAND
Takeover occurs only when a CEBT PERFORM TAKEOVER command is received by the alternate CICS region. It ensures, for instance, that a dependent alternate CICS region, in MRO, is activated only if it receives the command from the operator, or from a master or coordinator region.
TBEXITS=([name1][,name2][,name3] [,name4][,name5][,name6])
specifies the names of your backout exit programs for use during emergency restart backout processing. For more information about backout exit programs, see the CICS Customization Guide and the CICS Recovery and Restart Guide.

The order in which you code the names is significant. If you do not want to use all the exits, code commas in place of the names you omit. For example:

TBEXITS=(,,EXITF,EXITV)

The program names for name1 through name6 apply to global user exit points as follows:

This exit is invoked (if required) during backout of a unit of work, regardless of whether the backout is taking place at emergency restart, or at any other time.

The XFCBFAIL, XFCLDEL, and XFCBOVER global user exit programs are enabled on all types of CICS start if they are named on the TBEXITS system initialization parameter.

If no backout exit programs are required, you can do one of the following:

Start of changeTCAM={NO|YES} End of change
Start of changeThis parameter is now obsolete and is only kept for compatibility. If it is specified, it is rejected with a message and TCAM=NO is assumed.End of change
TCP={YES|NO}
specifies whether the pregenerated non-VTAM terminal control program, DFHTCP, is to be included.

You must code TCP=YES if you intend using card reader/line printer (sequential) devices.

TCPIP={NO|YES}
specifies whether CICS TCPIP services are to be activated at CICS startup. The default is NO, meaning that these services cannot be enabled. If TCPIP is set to YES, the HTTP, IIOP, and ECI over TCP/IP services can process work.
Note:
The TCPIP system initialization parameter affects only CICS internal TCP/IP Services defined by TCPIPSERVICE resource definitions. It has nothing to do with the TCP/IP Socket Interface for CICS feature of TCP/IP for MVS.
TCSACTN={NONE|UNBIND|FORCE}
specifies the required action that CICS terminal control should take if the terminal control shutdown wait threshold expires. For details of the wait threshold, see the TCSWAIT system initialization parameter. TCSACTN only takes effect when TCSWAIT is coded with a value in the range 1 through 99. This is a global default action. On a terminal-by-terminal basis, you can code a DFHZNEP routine to override this action.
NONE
No action is taken. This can be overridden by DFHZNEP.
  • To report hung terminals and not attempt to force-close them specify the TCSWAIT=mm (with an appropriate time interval) and TCSACTN=NONE system initialization parameters.
  • To attempt to force-close some hung terminals, and only report others, specify the TCSWAIT=mm (with an appropriate time interval) and TCSACTN=NONE system initialization parameters, and code a DFHZNEP routine that selects the required terminals and sets TWAOCN on for them.
UNBIND
CICS terminal control attempts to close the session by issuing a VTAM CLSDST and sending an SNA UNBIND command to the hung terminal. This can be overridden by DFHZNEP.
  • To attempt to force-close all hung terminals specify the TCSWAIT=mm (with an appropriate time interval) and TCSACTN=UNBIND system initialization parameters.
FORCE
CICS terminal control attempts to forceclose the CICS VTAM ACB if there are any hung terminals or parallel connection sessions. All CICS VTAM terminals and sessions are released and CICS normal shutdown continues. This parameter will only take effect if all LU Type 6.2 parallel connections, if any, have successfully completed CNOS close processing.
  • To attempt to force-close the CICS VTAM ACB if there are any hung terminals, specify the TCSWAIT=mm (with an appropriate time interval) and TCSACTN=FORCE system initialization parameters.
TCSWAIT={4|number|NO|NONE|0}
specifies the required CICS terminal control shutdown wait threshold. The wait threshold is the time, during shutdown, that CICS terminal control allows to pass before it considers terminal shutdown to be hung. If all VTAM sessions shutdown and close before the threshold expires then the CICS shutdown process moves on to its next stage, and the terminal control wait threshold then no longer applies. If, however, some of the VTAM sessions do not complete shutdown and close, then CICS takes special action with these sessions. For details of this special action see the description of the TCSACTN system initialization parameter. The wait threshold only applies to VTAM sessions; that is, VTAM terminals and VTAM intersystem connections. The wait time is specified as a number of minutes, in the range 1 through 99. As a special case, TCSWAIT=NO may be specified to indicate that terminal control shutdown is never to be considered hung, no matter how long the shutdown and close process takes. TCSWAIT=NONE and TCSWAIT=0 are alternative synonyms for TCSWAIT=NO, and all three have the same effect (internally they are held as the one value 0 (zero)).

The value that you specify on the TCSWAIT system initialization parameter should be large enough so that under normal circumstances all VTAM terminals and connections shutdown in an orderly fashion. To help choose this value, consider using a value slightly larger than the elapsed time between the following two CICS terminal control shutdown messages:

  DFHZC2305 Termination of VTAM sessions beginning
  DFHZC2316 VTAM ACB is closed
TCT={NO|xx|YES}
specifies which terminal control table, if any, is to be loaded. (See topic Defining CICS resource table and module keywords.) For guidance about coding the macros for this table, see the CICS Resource Definition Guide

If you reassemble the TCT after starting CICS, any changes are applied when you next start CICS, even if it is a warm or emergency startup.

If you have VTAM-connected terminals only, you can specify TCT=NO. If you do this, note that a dummy TCT, called DFHTCTDY, is loaded during system initialization. For more information about DFHTCTDY, see topic The dummy TCT, DFHTCTDY. (If you code TCT=NO, you must specify a CSD group list in the GRPLIST parameter.)

TCTUAKEY={USER|CICS}
specifies the storage key for the terminal control table user areas (TCTUAs) if you are operating CICS with storage protection (STGPROT=YES). The permitted values are USER (the default), or CICS:
USER
CICS obtains the amount of storage for TCTUAs in user key. This allows a user program executing in any key to modify the TCTUA.
CICS
CICS obtains the amount of storage in CICS key. This means that only programs executing in CICS key can modify the TCTUA, and user-key programs have read-only access.

If CICS is running without storage protection, the TCTUAKEY parameter only designates which DSA (User or CICS) the storage comes from. The TCTUAs are accessed in CICS-key whether they are in the UDSA or CDSA.

See The terminal control table user areas for more information about TCTUAs.

TCTUALOC={BELOW|ANY}
specifies where terminal user areas (TCTUA) are to be stored.
BELOW
The TCTUAs are stored below the 16MB line.
ANY
The TCTUAs are stored anywhere in virtual storage. CICS stores TCTUAs above the 16MB line if possible.

For more information about TCTUAs, see Accessing the CSD by the offline utility program, DFHCSDUP.

For details about defining terminals using RDO, see the CICS Resource Definition Guide.

TD=({3|decimal-value-1}[,{ 3|decimal-value-2}])
specifies the number of VSAM buffers and strings to be used for intrapartition transient data (TD).
decimal-value-1
The number of buffers to be allocated for the use of intrapartition transient data. The value must be in the range 1 through 32 767. The default value is 3.

CICS obtains, above the 16MB line, storage for the TD buffers in units of the page size (4KB). Because CICS optimizes the use of the storage obtained, TD may allocate more buffers than you specify, depending on the control interval (CI) size you have defined for the intrapartition data set.

For example, if the CI size is 1536, and you specify 3 buffers (the default number), CICS actually allocates 5 buffers. This is because 2 pages (8192 bytes) are required to obtain sufficient storage for three 1536-byte buffers, a total of only 4608 bytes, which would leave 3584 bytes of spare storage in the second page. In this case, CICS allocates another 2 buffers (3072 bytes) to minimize the amount of unused storage. In this way CICS makes use of storage that would otherwise be unavailable for any other purpose.

decimal-value-2
The number of VSAM strings to be allocated for the use of intrapartition transient data. The value must be in the range 1 through 255, and must not exceed the value specified in decimal-value-1. The default value is 3.

For example, TD=(8,5) specifies 8 buffers and 5 strings.

The operands of the TD parameter are positional. You must code commas to indicate missing operands if others follow. For example, TD=(,2) specifies the number of strings and allows the number of buffers to default.

TDINTRA={NOEMPTY|EMPTY}
specifies whether CICS is to initialize with empty intrapartition TD queues.
NOEMPTY
CICS recovers all the intrapartition TD queues to the state they were in at the previous termination of CICS, as in a normal emergency restart. The TD queue resource definitions are recovered from the CICS global catalog.
EMPTY
CICS initializes with all the intrapartition TD queues empty. This option must be used when CICS is initializing in remote site recovery mode (OFFSITE=YES).

You can optionally use this option to COLD start your intra-partition TD queues to initialize them as empty.

The option is significant only on warm and emergency restarts--cold starts always initialize with empty queues. Note that the EMPTY option may cause data integrity problems because all in-doubt log records associated with logically recoverable TD queues are discarded.

The TD queue resource definitions are recovered from the CICS global catalog.

Start of changeTDSUBTASK={OFF|ON}End of change
Start of changespecifies whether CICS should use the FO TCB to write to an extrapartition transient data queue, where the record format is FIXED and the block format is UNBLOCKED. The default is OFF, so that no TCB switch can occur. This particularly benefits you if you are submitting work to JES using the internal reader (INTRDR).End of change
TRANISO={NO|YES}
specifies, together with the STGPROT system initialization parameter, whether you want transaction isolation in the CICS region. The permitted values are NO (the default), or YES.
NO
This is the default. If you specify NO, or allow this parameter to default, CICS operates without transaction isolation, and all storage in the CICS address space is addressable. If you specify STGPROT=YES and TRANISO=NO, CICS storage protection is active without transaction isolation.
YES
Transaction isolation is required. If you specify TRANISO=YES and STGPROT=YES, and you have the required hardware and software, CICS operates with transaction isolation. This ensures that the user-key task-lifetime storage of transactions defined with the ISOLATE(YES) option is isolated from the user-key programs of other transactions.

If you specify TRANISO=YES, but you do not have the required hardware and software or STGPROT=NO is specified, CICS issues an information message during initialization, and operates without transaction isolation.

STGPROT=NO and TRANISO=YES specified in the system initialization table causes an error during assembly (MNOTE 8).

Note:
VSAM nonshared resources (NSR) are not supported for transactions that use transaction isolation. You should specify ISOLATE(NO) when you define transactions that access VSAM files using NSR.
TRAP={OFF|ON}
specifies whether the FE global trap exit is to be activated at system initialization. This exit is for diagnostic use under the guidance of service personnel. For background information about this exit, see the CICS Problem Determination Guide.
TRDUMAX={999|number}
specifies the limit on the number of transaction dumps that may be taken per Dump Table entry. If this number is exceeded, subsequent transaction dumps for that particular entry will be suppressed.
number
A number in the range 0 through 999. The default, 999, enables an unlimited number of dumps to be taken.
TRTABSZ={16|number-of-kilobytes}
specifies the size in kilobytes of the internal trace table. (1KB = 1024 bytes.) The CICS trace table is allocated in virtual storage above the 16MB line, and it is allocated before the extended CICS-key DSA (ECDSA) and the extended user-key DSA (EUDSA). Ensure that there is sufficient virtual storage for the trace table, the ECDSA, and the EUDSA by specifying a large enough region size on the MVS REGION parameter of your CICS job.

Start of changeUse caution when setting this parameter to a very high value. There must be enough MVS page storage to satisfy both the request as well as the DSA sizes. Use the DISPLAY ASM MVS system command to display current information about the status and utilization of all MVS page data sets.End of change

16
16KB is the default size of the trace table, and also the minimum size.
number
The number of kilobytes of storage to be allocated for the internal trace table, in the range 16KB through 1048576KB. Subpool 1 is used for the trace table storage, which exists for the duration of the CICS execution. The table is page aligned and occupies a whole number of pages. If the value specified is not a multiple of the page size (4KB), it is rounded up to the next multiple of 4KB.

Trace entries are of variable lengths, but the average length is approximately 100 bytes.

Note:
To switch on internal tracing, use the INTTR parameter; for a description of INTTR, see topic INTTR.
TRTRANSZ={16|number-of-kilobytes}
specifies the size in kilobytes of the transaction dump trace table. (1KB = 1024 bytes.)

When a transaction dump is taken, CICS performs an MVS GETMAIN for storage above the 16MB line for the transaction dump trace table.

16
16KB is the default size of the transaction dump trace table.
number
The number of kilobytes of storage to be allocated for the transaction dump trace table, in the range 16KB through 1048576KB.
TRTRANTY={TRAN|ALL}
specifies which trace entries should be copied from the internal trace table to the transaction dump trace table.
TRAN
Only the trace entries associated with the transaction that is abending will be copied to the transaction dump trace table.
ALL
All of the trace entries from the internal trace table will be copied to the transaction dump trace table. If the internal trace table size is larger than the transaction dump trace table size, the transaction dump trace table could wrap. This results in only the most recent trace entries being written to the transaction dump trace table.
TS=([COLD][,{0|3|decimal-value-1 }][,{3|decimal-value-2}])
specifies:
COLD
The type of start for the temporary storage facility. COLD forces a cold start regardless of the value of the START parameter. If COLD is omitted, the TS start type is determined by the value of START.
0
No buffers are required; that is, only MAIN temporary storage is required.
decimal-value-1
The number of buffers to be allocated for the use of auxiliary temporary storage. The value must be in the range 3 through 32 767.
decimal-value-2
The number of VSAM strings to be allocated for the use of auxiliary temporary storage. The value must be in the range 1 through 255, and must not exceed the value specified in decimal-value-1. The default value is 3.

For example, TS=(,8,5) specifies 8 buffers and 5 strings.

The operands of the TS parameter are positional. You must code commas to indicate missing operands if others follow. For example, TS=(,8) specifies the number of buffers and allows the other operands to default.

TST={NO|YES|xx}
specifies the temporary storage table suffix. (See topic Defining CICS resource table and module keywords.)

For information about coding the macros for this table, see the CICS Resource Definition Guide

UDSASZE={0K|number}
specifies the size of the UDSA. The default size is 0, indicating that the DSA size can change dynamically. A non-zero value indicates that the DSA size is fixed.
number
specify number as an amount of storage in the range 0 to 16777215 bytes in multiples of 262144 bytes (256KB). If the size specified is not a multiple of 256KB (or 1MB if transaction isolation is active), CICS rounds the value up to the next multiple.

You can specify number in bytes (for example, 4194304), or as a whole number of kilobytes (for example, 4096K), or a whole number of megabytes (for example, 4M).

Restrictions You can specify the UDSAZSE parameter in PARM, SYSIN, or CONSOLE only.

UOWNETQL=user_defined_value
specifies a qualifier for the NETUOWID for units of work initiated on the local CICS region. UOWNETQL is required only if VTAM=NO is coded. The specified value is used in the following circumstances:

If any of the above conditions apply and UOWNETQL is not specified, a dummy default UOWNETQL of 9UNKNOWN is used. This dummy UOWNETQL is invalid because the first character is a number. UOWNETQL is given this invalid name to avoid a conflict with any real, valid netid.

The value you code can be from 1 to 8 characters long, and must consist of uppercase letters (A through Z), or numbers in the range 0 through 9. The first character must be a letter.

USERTR={ON|OFF}
specifies whether the master user trace flag is to be set on or off. If the user trace flag is off, the user trace facility is disabled, and EXEC CICS ENTER TRACENUM commands receive an INVREQ condition if EXCEPTION is not specified. If the program does not handle this condition the transaction will abend AEIP.

For programming information about the user trace facility using EXEC CICS ENTER TRACENUM commands, see the CICS Application Programming Reference manual.

USRDELAY={30|number}
specifies the maximum time, in the range 0 through 10080 minutes (up to 7 days), that an eligible userid and its associated attributes are to be retained in the user table if the userid is unused. An entry in the user table for a userid that is retained during the delay period can be reused.

The userids eligible for reuse within the USRDELAY period are any that are:

Within the USRDELAY period, a userid in any one of these categories can be reused in one of the other categories, provided the request for reuse is qualified with the same qualifiers. If a userid is qualified by a different group id, APPLID, or terminal id, a retained entry is not reused (except when changing the terminal ID on LU6.2 when the retained entry is used).

If a userid is unused for more than the USRDELAY limit, it is removed from the system, and the message DFHUS0200 is issued. You can suppress this message in an XMEOUT global user exit program. If you specify USRDELAY=0, all eligible userids are deleted immediately after use, and the message DFHUS0200 is not issued. Do not code USRDELAY=0 if this CICS region communicates with other CICS regions and:

You should specify a value that gives the optimum level of performance for your CICS environment.

If you specify USRDELAY=0 in the above scenario, CICS drives a full signon for each incoming request (with I/O to RACF) and a full signoff at the end of each transaction. For function shipping, there may be multiple signons/signoffs driven on a data-owning region for one task on an AOR.

Note:
If a value, other than 0, is specified for USRDELAY, the ability to change the user's attributes or revoke the userid becomes more difficult because the userid and its attributes are retained in the region until the USRDELAY value has expired. For example, if you have specified USRDELAY=30 for a userid, but that userid continues to run transactions every 25 minutes, the USRDELAY value will never expire and any changes made to the userid will never come into effect.

When running a remote transaction, a userid remains signed-on to the remote CICS region (after the conversation associated with the first attach request is complete) until the delay specified by USRDELAY has elapsed since the last transaction associated with the attach request for the userid has completed. When this event occurs, the userid is removed from the remote CICS region.

For more information about the use of USRDELAY, see the CICS Performance Guide .

VTAM={YES|NO}
specifies whether the VTAM access method is to be used. The default is VTAM=YES.
VTPREFIX={\|character}
specifies the first character to be used for the terminal identifiers (termids) of autoinstalled virtual terminals. Virtual terminals are used by the External Presentation Interface (EPI) and terminal emulator functions of the CICS Client products.

Termids generated by CICS for autoinstalled Client terminals consist of a 1-character prefix and a 3-character suffix. The default prefix is ‘\’. The suffix can have the values ‘AAA’ through ‘999’. That is, each character in the suffix can have the value ‘A’ through ‘Z’ or ‘0’ through ‘9’. The first suffix generated by CICS has the value ‘AAA’. This is followed by ‘AAB’, ‘AAC’, ... ‘AAZ’, ‘AA0’, ‘AA1’, and so on, up to ‘999’.

Each time a Client virtual terminal is autoinstalled, CICS generates a 3-character suffix that it has not recorded as being in use.

By specifying a prefix, you can ensure that the termids of Client terminals autoinstalled on this system are unique in your transaction routing network. This prevents the conflicts that could occur if two or more terminal-owning regions (TORs) ship definitions of Client virtual terminals to the same application-owning region (AOR).

If such a naming conflict does occur--that is, if a Client virtual terminal is shipped to an AOR on which a remote terminal of the same name is already installed--the autoinstall user program is invoked in the AOR. Your user program can resolve the conflict by allocating an alias terminal identifier to the shipped definition. (For details of writing an autoinstall user program to install shipped definitions, see the CICS Customization Guide.) However, you can avoid potential naming conflicts by specifying a different prefix, reserved for virtual terminals, on each TOR on which Client virtual terminals are to be installed.

You must not use the characters + - * < > = { } or blank.

Notes:
  1. When specifying a prefix, ensure that termids generated by CICS for Client terminals do not conflict with those generated by your autoinstall user program for user terminals, or with the names of any other terminals or connections.
  2. Client terminal definitions are not recovered after a restart. Immediately after a restart, no Client terminals are in use, so when CICS generates suffixes it begins again with ‘AAA’. This means that CICS does not always generate the same termid for any given Client terminal. This in turn means that server applications should not assume that a particular CICS-generated termid always equates to a particular Client terminal.

    If your server programs do make this assumption, you can use your autoinstall user program to allocate alias termids, by which the virtual terminals will be known to CICS, in a consistent manner.

  3. Clients can override CICS Transaction Server for z/OS-generated termids.

For further information about Client virtual terminals, see the CICS Intercommunication Guide manual.

WEBDELAY=(5|time_out,60|keep_time)
Specifies two Web delay periods:
  1. A time-out period. The maximum time, in minutes, in the range 1-60, that a transaction started through the Web 3270 bridge interface, is allowed to remain in terminal wait state before it is automatically purged by CICS.
  2. The terminal keep time. The time, in minutes, in the range 1-6000, during which state data is kept for a CICS Web 3270 bridge transaction, before CICS performs clean-up.
WRKAREA={512|number}
specifies the number of bytes to be allocated to the common work area (CWA). This area, for use by your installation, is initially set to binary zeros, and is available to all programs. It is not used by CICS. The maximum size for the work area is 3584 bytes.
XAPPC={NO|YES}
specifies whether RACF session security can be used when establishing APPC sessions.
NO
RACF session security cannot be used.
YES
RACF session security can be used.

If you specify BINDSECURITY=YES for a particular APPC connection, a request to RACF is issued to extract the security profile. If the profile exists, it is used to bind the session.

Note:
If you specify XAPPC=YES, the external security manager that you use must support the APPCLU general resource class, otherwise CICS fails to initialize.

Restrictions You can specify the XAPPC parameter in the SIT, PARM, or SYSIN only.

XCMD={YES|name|NO}
specifies whether you want CICS to perform command security checking, and optionally the RACF resource class name in which you have defined the command security profiles. If you specify YES, or a RACF resource class name, CICS calls RACF to verify that the userid associated with a transaction is authorized to use a CICS command for the specified resource. Such checking is performed every time a transaction tries to use a COLLECT, DISABLE, DISCARD, ENABLE, EXTRACT, INQUIRE, PERFORM, RESYNC, or SET command, or any of the FEPI commands, for a resource.
Note:
The checking is performed only if you have specified YES for the SEC system initialization parameter and specified the CMDSEC(YES) option on the transaction resource definition.

For information about preparing for and using security with CICS, see the CICS RACF Security Guide.

YES
CICS calls RACF, using the default class name of CICSCMD prefixed by C or V, to check whether the userid associated with a transaction is authorized to use a CICS command for the specified resource. The resource class name is CCICSCMD and the grouping class name is VCICSCMD.
name
CICS calls RACF, using the specified resource class name prefixed by C or V, to verify that the userid associated with a transaction is authorized to use a CICS command for the specified resource. The resource class name is Cname and the grouping class name is Vname.

The resource class name specified must be 1 through 7 characters.

NO
CICS does not perform any command security checks, allowing any user to use commands that would be subject to those checks.

Restrictions You can specify the XCMD parameter in the SIT, PARM, or SYSIN only.

XDB2={NO|name}
specifies whether you want CICS to perform DB2ENTRY security checking.
NO
CICS does not perform any DB2 resource security checks.
name
CICS calls RACF, using the specified general resource class name, to check whether the userid associated with the CICS DB2 transaction is authorized to access the DB2ENTRY referenced by the transaction.

Unlike the other Xaaa system initialization parameters, this DB2 security parameter does not provide a YES option that implies a default CICS resource class name for DB2ENTRY resources. You have to specify your own DB2 resource class name.

XDCT={YES|name|NO}
specifies whether you want CICS to perform transient data resource security checking. If you specify YES or a RACF resource class name, CICS calls RACF to verify that the userid associated with a transaction is authorized to access the transient data destination. Such checking is performed every time a transaction tries to access a transient data destination.
Note:
The checking is performed only if you have specified YES for the SEC system initialization parameter and specified the RESSEC(YES) option on the transaction resource definition.

For information about preparing for and using security with CICS, see the CICS RACF Security Guide.

YES
CICS calls RACF, with the default CICS resource class name of CICSDCT prefixed by D or E, to verify whether the userid associated with the transaction is authorized to access the specified destination.

The resource class name is DCICSDCT and the grouping class name is ECICSDCT.

name
CICS calls RACF, using the specified resource class name, to check whether the userid associated with the transaction is authorized to access the specified destination. The resource class name is Dname and the grouping class name is Ename.

The resource class name specified must be 1 through 7 characters.

NO
CICS does not perform any transient data security checks, allowing any user to access any transient data destination.

Restrictions You can specify the XDCT parameter in the SIT, PARM, or SYSIN only.

XEJB={YES|NO}
specifies whether support of security roles is enabled.
YES
CICS support for security roles is enabled:
  • When an application invokes a method of an enterprise bean, CICS calls the external security manager to verify that the userid associated with the transaction is defined in at least one of the security roles associated with the method.
  • When an application invokes the isCallerInRole() method, CICS calls the external security manager to determine whether the userid associated with the transaction is defined in the role specified on the method call.
NO
CICS support for security roles is disabled:
  • CICS does not perform enterprise bean method level checks, allowing any userid to invoke any enterprise bean method.
  • The isCallerInRole() method always returns a value of true.
Restrictions:
  1. You can specify the XEJB parameter in the SIT, PARM, or SYSIN only.
  2. To enable security role support, you must also specify SEC=YES.
XFCT={YES|name|NO}
specifies whether you want CICS to perform file resource security checking, and optionally specifies the RACF resource class name in which you have defined the file resource security profiles. If you specify YES, or a RACF resource class name, CICS calls RACF to verify that the userid associated with a transaction is authorized to access File Control-managed files. Such checking is performed every time a transaction tries to access a file managed by CICS File Control.
Note:
The checking is performed only if you have specified YES for the SEC system initialization parameter and specified the RESSEC(YES) option on the resource definitions.

For information about preparing for and using security with CICS, see the CICS RACF Security Guide.

YES
CICS calls RACF, using the default CICS resource class name of CICSFCT prefixed by F or H, to verify that the userid associated with a transaction is authorized to access files reference by the transaction. The resource class name is FCICSFCT and the grouping class name is HCICSFCT.
name
CICS calls RACF, using the specified resource class name, to verify that the userid associated with a transaction is authorized to access files referenced by the transaction. The resource class name is Fname and the grouping class name is Hname.

The resource class name specified must be 1 through 7 characters.

NO
CICS does not perform any file resource security checks, allowing any user to access any file.

Restrictions You can specify the XFCT parameter in the SIT, PARM, or SYSIN only.

XJCT={YES|name|NO}
specifies whether you want CICS to perform journal resource security checking. If you specify YES, or a RACF resource class name, CICS calls RACF to verify that the userid associated with a transaction is authorized to access the referenced journal. Such checking is performed every time a transaction tries to access a CICS journal.
Note:
The checking is performed only if you have specified YES for the SEC system initialization parameter and specified the RESSEC is active for the resource definitions.

For information about preparing for and using security with CICS, see the CICS RACF Security Guide.

YES
CICS calls RACF using the default CICS resource class name of CICSJCT prefixed by a J or K, to check whether the userid associated with a transaction is authorized to access CICS journals referenced by the transaction. The resource class name is JCICSJCT and the grouping class name is KCICSJCT.
name
CICS calls RACF, using the specified resource class name prefixed by J or K, to verify that the userid associated with a transaction is authorized to access CICS journals.

The resource class name specified must be 1 through 7 characters.

NO
CICS does not perform any journal resource security checks, allowing any user to access any CICS journal.

Restrictions You can specify the XJCT parameter in the SIT, PARM, or SYSIN only.

XLT={NO|xx|YES}
specifies a suffix for the transaction list table. ( topic Defining CICS resource table and module keywords.) The table contains a list of transactions that can be attached during the first quiesce stage of system termination.
YES
The default transaction list table, DFHXLT, is used.
xx
The transaction list table DFHXLTxx is used.
NO
A transaction list table is not used.

For guidance information about coding the macros for this table, see the CICS Resource Definition Guide

XPCT={YES|name|NO}
specifies whether you want CICS to perform started transaction resource security checking, and optionally specifies the name of the RACF resource class name in which you have defined the started task security profiles. If you specify YES, or a RACF resource class name, CICS calls RACF to verify that the userid associated with a transaction is authorized to use started transactions and related EXEC CICS commands. Such checking is performed every time a transaction tries to use a started transaction or one of the EXEC CICS commands: COLLECT STATISTICS TRANSACTION, DISCARD TRANSACTION, INQUIRE TRANSACTION, or SET TRANSACTION.
Note:
The checking is performed only if you have specified YES for the SEC system initialization parameter and specified the RESSEC(YES) option on the resource definitions.

For information about preparing for and using security with CICS, see the CICS RACF Security Guide.

YES
CICS calls RACF using the default CICS resource class name CICSPCT prefixed with A or B, to verify that the userid associated with a transaction is authorized to use started transactions or related EXEC CICS commands.

The resource class name is ACICSPCT and the grouping class name is BCICSPCT.

name
CICS calls RACF, using the specified resource class name, to verify that the userid associated with a transaction is authorized to use started transactions or related EXEC CICS commands. The resource class name is ACICSPCT and the grouping class name is BCICSPCT.

The resource class name specified must be 1 through 7 characters.

NO
CICS does not perform any started task resource security checks, allowing any user to use started transactions or related EXEC CICS commands.

Restrictions You can specify the XPCT parameter in the SIT, PARM, or SYSIN only.

XPPT={YES|name|NO}
specifies that CICS is to perform application program resource security checks, and optionally specifies the RACF resource class name in which you have defined the program resource security profiles. Such checking is performed every time a transaction tries to invoke another program by using one of the CICS commands: LINK, LOAD, or XCTL.
Note:
The checking is performed only if you have specified YES for the SEC system initialization parameter and specified the RESSEC(YES) option on the resource definitions.

For information about preparing for and using security with CICS, see the CICS RACF Security Guide.

YES
CICS calls RACF, using the default resource class name prefixed by M or N, to verify that the userid associated with a transaction is authorized to use LINK, LOAD, or XCTL commands to invoke other programs. The resource class name is MCICSPPT and the grouping class name is NCICSPPT.
name
CICS calls RACF, with the specified resource class name prefixed by M or N, to verify that the userid associated with a transaction is authorized to use LINK, LOAD, or XCTL commands to invoke other programs. The resource class name is Mname and the grouping class name is Nname.

The resource class name specified must be 1 through 7 characters.

NO
CICS does not perform any application program authority checks, allowing any user to use LINK, LOAD, or XCTL commands to invoke other programs.

Restrictions You can specify the XPPT parameter in the SIT, PARM, or SYSIN only.

XPSB={YES|name|NO}
specifies whether you want CICS to perform program specification block (PSB) security checking, and optionally specifies the RACF resource class name in which you have defined the PSB security profiles. If you specify YES, or a RACF resource class name, CICS calls RACF to check that the userid associated with a transaction is authorized to access PSBs (which describe databases and logical message destinations used by application programs). Such checking is performed every time a transaction tries to access a PSB.
Notes:
  1. The checking is performed only if you have specified YES for the SEC system initialization parameter and specified the RESSEC(YES) option on the resource definitions.
  2. If you require security checking for PSBs to apply to remote users who access this region by means of transaction routing, the system initialization parameter PSBCHK=YES must be specified. For further information about the PSBCHK system initialization parameter, see topic PSBCHK.

For information about preparing for and using security with CICS, see the CICS RACF Security Guide.

YES
CICS calls RACF, using the default resource class name CICSPSB prefixed by P or Q, to verify that the userid associated with a transaction is authorized to access PSBs. The resource class name is PCICSPSB and the grouping class name is QCICSPSB.
name
CICS calls RACF, using the specified resource class name prefixed by P or Q, to verify that the userid associated with a transaction is authorized to access PSBs. The resource class name is Pname and the grouping class name is Qname.

The resource class name specified must be 1 through 7 characters.

NO
CICS does not perform any PSB resource security checks, allowing any user to access any PSB.

Restrictions You can specify the XPSB parameter in the SIT, PARM, or SYSIN only.

XRF={NO|YES} (active and alternate)
specifies whether XRF support is to be included in the CICS region. If the CICS region is started with the START=STANDBY system initialization parameter specified, the CICS region is the alternate CICS region. If the CICS region is started with the START=AUTO, START=INITIAL or START=COLD system initialization parameter specified, the CICS region is the active CICS region. The active CICS region signs on as such to the CICS availability manager. For background information about XRF, see the CICS/ESA 3.3 XRF Guide .
XRFSOFF={NOFORCE|FORCE}
This parameter is now obsolete and is only kept for compatibility. If it is specified, it is rejected with a message and RSTSIGNOFF is assumed.
XRFSTME={5|decimal-value}
This parameter is now obsolete and is only kept for compatibility. If it is specified, it is rejected with a message and RSTSIGNTIME is assumed.
XTRAN={YES|name|NO}
specifies whether you want CICS to perform transaction-attach security checking, and optionally specifies the RACF resource class name in which you have defined the transaction security profiles. If you specify YES, or a RACF resource class name, CICS calls RACF to verify that the userid associated with the transaction is permitted to run the transaction.
Note:
Start of change
The checking is performed only if you have specified YES for the SEC system initialization parameter.
End of change
YES
CICS calls RACF, using the default CICS resource class name of CICSTRN prefixed by T or G, to verify that the userid associated with the transaction is authorized to run the transaction. The resource class name is TCICSTRN and the grouping class name is GCICSTRN.
name
CICS calls RACF, using the specified resource class name prefixed by T or G, to verify that the userid associated with the transaction is authorized to run the transaction. The resource class name is Tname and the corresponding grouping class name is Gname.

The name specified must be 1 through 7 characters.

NO
CICS does not perform any transaction-attach security checks, allowing any user to run any transaction.

Restrictions: You can specify the XTRAN parameter in the SIT, PARM, or SYSIN only.

XTST={YES|name|NO}
specifies whether you want CICS to perform temporary storage security checking, and optionally specifies the RACF resource class name in which you have defined the temporary storage security profiles. If you specify YES, or a RACF resource class name, CICS calls RACF to verify that the userid associated with a temporary storage request is authorized to access the referenced temporary storage queue.
Note:
The checking is performed only if you have specified YES for the SEC system initialization parameter, specified the RESSEC option on the resource definitions, and specified TYPE=SECURITY in the temporary storage table (TST).
YES
CICS calls RACF, using the default CICS resource class name of CICSTST prefixed by S or U, to verify that the userid associated with the transaction is authorized to access temporary storage queues referenced by the transaction. The resource class name is SCICSTST and the corresponding grouping class name is UCICSTST.
name
CICS calls RACF, using the specified resource class name prefixed by S or U, to verify that the userid associated with a transaction is authorized to access temporary storage queues.

The name specified must be 1 through 7 characters.

NO
CICS does not perform any temporary storage security checks, allowing any user to access any temporary storage queue.

Restrictions You can specify the XTST parameter in the SIT, PARM, or SYSIN only.

XUSER={YES|NO}
specifies whether CICS is to perform surrogate user checks.
YES
CICS is to perform surrogate user checking in all those situations that permit such checks to be made (for example, on EXEC CICS START commands without an associated terminal). Surrogate user security checking is also performed by CICS against userids installing or modifying DB2 resource definitions that specify AUTHID or COMAUTHID.
Note:
The XUSER parameter is also used by CICS to control access to the AUTHTYPE and COMAUTHTYPE parameters on DB2 resource definitions, although not through surrogate user checks. For more information about AUTHTYPE and COMAUTHTYPE parameters, see the CICS Resource Definition Guide.

For information about the various circumstances in which CICS performs surrogate user checks, see the CICS RACF Security Guide.

NO
CICS is not to perform any surrogate user checking.

Restrictions You can specify the XUSER parameter in the SIT, PARM, or SYSIN only.

[[ Contents Previous Page | Next Page Index ]]