- AKP(data-value)
- specifies, as a fullword binary value, the activity keypoint trigger
value, which is the number of write requests to the CICS system log stream output buffer between the
taking of keypoints. The number must be either zero, which turns off keypointing,
or in the range 200-65535. If CICS was initialized without keypointing
(that is, with the AKPFREQ system initialization parameter set to zero), the
initial value can be overridden and a trigger value can be set.
- DEBUGTOOL(cvda)
- Specifies a CVDA value indicating 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:
- Debug Tool, for compiled language application programs (programs written
in COBOL, PL/I, C, C++ and Assembler)
- Remote debugging tools (for compiled language application programs and
Java programs)
Other debugging mechanisms, such as the CICS Execution Diagnostic Facility
(CEDF) do not use debugging profiles.
The CVDA values are:
- DEBUG
- Specifies that you want to use CICS debugging profiles to select the
programs that will run under the control of a debugging tool.
- NODEBUG
- 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.
For more information about using debugging profiles, see the CICS Application Programming Guide.
- DSALIMIT(data-value)
- specifies, as a fullword binary value, the maximum amount of storage,
in bytes, within which CICS can allocate storage for the four individual dynamic
storage areas (DSAs) that reside below the 16MB boundary. If DSALIMIT specifies
a value lower than the current limit, CICS may not be able to implement the
new limit immediately, but will attempt to do so over time as storage is freed.
The range for DSALIMIT is 2MB-16MB.
- DSRTPROGRAM(data-value)
- specifies the 8-character name of the distributed routing program.
- DTRPROGRAM(data-value)
- specifies the 8-character name of the dynamic routing program.
- DUMPING(cvda)
- specifies a CVDA value indicating whether the taking of CICS system
dumps is to be suppressed. CVDA values are:
- NOSYSDUMP
- System dumps are to be suppressed.
- SYSDUMP
- System dumps are not to be suppressed.
- EDSALIMIT(data-value)
- specifies, as a fullword binary value, the maximum amount of storage,
in bytes, within which CICS can allocate storage for the four individual dynamic
storage areas that reside above the 16MB boundary. If EDSALIMIT specifies
a value lower than the current limit, CICS may not be able to implement the
new limit immediately, but will attempt to do so over time as storage is freed.
The range for EDSALIMIT is 10MB-2GB.
- FORCEQR(cvda)
- specifies whether you want CICS to force all user application programs
specified as CONCURRENCY(THREADSAFE) to run under the CICS QR TCB, as if they
were specified as CONCURRENCY(QUASIRENT) programs.
This allows you, in
a test environment, to run incompletely tested threadsafe application
programs that have proved to be non-threadsafe.
FORCEQR applies to
all programs defined as threadsafe that are not invoked as task-related user exits, global
user exits, or user-replaceable modules.
CVDA values are:
- FORCE
Force all CICSAPI user application programs to run under
the QR TCB, even if they are defined with the CONCURRENY(THREADSAFE) attribute.
Force does not apply to OPENAPI programs or C/C++ programs compiled with
XPLINK.
- NOFORCE
- CICS is to honor the CONCURRENCY(THREADSAFE) attribute defined on program
resource definitions, and invoke them under either the QR TCB or an open
TCB.
The FORCEQR(FORCE|NOFORCE) option allows you to change dynamically
the option specified by the FORCEQR system initialization parameter.
Specifying FORCEQR(FORCE)
is not applied to currently invoked programs, and applies only to programs
invoked for the first time after the change to the FORCEQR status.
- GMMLENGTH(data-value)
- specifies, as a halfword binary value, the length of the "good morning" message text. The range for this value is 1-246.
- GMMTEXT(data-value)
- specifies the "good morning" message text, which can be up to 246
characters long.
- LOGDEFER(data-area)
- specifies, as a halfword binary value, the log deferral interval, which
is the period of time used by CICS Log Manager when determining how long
to delay a forced journal write request before invoking the MVS system logger.
The value can be in the range 0-65535. See the CICS System Definition Guide for
information about the LOGDEFER parameter and associated SIT parameter LGDFINT.
- MAXOPENTCBS(data-value)
- specifies, as a fullword binary value, the maximum number of open TCBs
that can exist concurrently in the CICS region. The value specified can be
in the range 1 to 999.
If you reduce MAXOPENTCBS from its previously defined
value, and the new value is less than the number of open TCBs currently allocated,
CICS detaches TCBs to achieve the new limit only when they are freed by user
tasks. Transactions are not abended to allow TCBs to be detached to achieve
the new limit.
If there are tasks queued waiting for an open TCB, and
you increase MAXOPENTCBS from its previously defined value, they are resumed
when CICS attaches new TCBs up to the new limit.
- MAXTASKS(data-value)
- specifies, as a fullword binary value, the maximum number of tasks that
can be eligible for dispatch at any one time in this CICS system. Both active
and suspended tasks count toward this limit, but tasks that have not reached
the point of initial dispatch do not. System tasks such as terminal and journal
control tasks do not count in CICS Transaction Server for z/OS® either, although they did in earlier
releases. The value can be in the range 1-999.
- MROBATCH(data-value)
- specifies, as a fullword binary value, the number of events that must
occur, from a list of MRO and DASD I/O events on which CICS is waiting, before
CICS is posted explicitly to process them. The value must be in the range
1-255.
- NEWMAXTASKS(data-area)
- returns the new value of MAXTASKS, in fullword binary form.
When
you set MAXTASKS in a SET SYSTEM command, CICS adjusts the value you specify
downward if there is not enough storage for the value you request; NEWMAXTASKS
tells you what the value is after any such adjustment. CICS also raises the
NOSTG condition when it reduces the value, although it continues processing
your command.
- PROGAUTOCTLG(cvda)
- specifies whether and when autoinstalled program definitions are to
be cataloged. Cataloged definitions are restored on a warm or emergency restart.
Those not cataloged are discarded at shutdown and must be installed again
if used in a subsequent execution of CICS.
Decisions to catalog are made
both at initial installation and whenever an autoinstalled definition is modified,
and are based on the PROGAUTOCTLG value at the time. CVDA values are:
- CTLGALL
- Definitions are to be cataloged when installed and when modified.
- CTLGMODIFY
- Definitions are to be cataloged only when modified.
- CTLGNONE
- Definitions are not to be cataloged.
- PROGAUTOEXIT(data-value)
- specifies the 8-character name of the user-provided program to be called
by the CICS program autoinstall code to provide a model definition.
Note:
This program (and any programs it invokes) must be installed before
they can be used in the program autoinstall process, either by explicit PROGRAM
definitions or by autoinstall when some other autoinstall program is in force.
Otherwise, the program autoinstall process fails when next used, and CICS
makes it inactive.
- PROGAUTOINST(cvda)
- specifies whether autoinstall for programs is to be active or inactive.
When a task requests a program, map set, or partition set that is not defined,
CICS attempts to create a definition for it automatically if autoinstall for
programs is active. If not, CICS raises the PGMIDERR exceptional condition.
CVDA values are:
- AUTOACTIVE
- Autoinstall for programs is to be active.
- AUTOINACTIVE
- Autoinstall for programs is to be inactive.
- PRTYAGING(data-value)
- specifies, as a fullword binary value, the rate at which CICS is to
increase the priority of a task waiting for dispatch. CICS increases the task
priority by 1 after each PRTYAGING milliseconds of wait time without a dispatch.
The value must be in the range 0-65535.
- RUNAWAY(data-value)
- specifies, as a fullword binary value, the default for runaway task
time. This value is used for any task executing a transaction with a profile
that does not specify runaway task time (see the RUNAWAY option of the INQUIRE
TRANSACTION command on page INQUIRE TRANSACTION options - RTIMEOUT).
The
value must be either zero, which means that runaway task detection is not
required for tasks using the default value, or in the range 500-2700000.
The value you supply is rounded down to the nearest multiple of 500.
- SCANDELAY(data-value)
- specifies, as a fullword binary value, the maximum number of milliseconds
between a user task making a terminal I/O request and CICS dispatching the
terminal control task to process it. This value is sometimes called the "terminal scan delay", and is set initially by the system initialization
option ICVTSD. The value must be in the range 0-5000.
- TIME(data-value)
- specifies, as a fullword binary value, the maximum interval in milliseconds
for which CICS gives control to the operating system if no tasks are ready
for dispatch. This value is set initially by the ICV system initialization
option and is sometimes called the "region exit time interval". The TIME
value must be in the range 100-3600000 and must not be less than the
SCANDELAY value. You can determine the current SCANDELAY value, if you are
not setting it at the same time, with the INQUIRE SYSTEM SCANDELAY command.