Startup Options (Sysparms)

#### Search Results

Search

# Startup Options (Sysparms)

The startup options, whether specified as PARM parameters in z/OS or entered as statements read from SYSPARM/SYSIPT, are available as keyword parameters (socalled "sysparms"). These parameters are interpreted and processed by the Com-plete PARM-processor module at Com-plete initialization time. Note that the sysparms must be entered according to established keyword coding conventions.

When read as statements from SYSPARM/SYSIPT, each statement must begin in column one. A maximum of 80 characters per statement is allowed. More than one sysparm is allowed per statement, but successive sysparms must be separated by a comma, and the statement itself must be terminated by a blank. For example:

    KEYWORD1=value1,KEYWORD2=value2...,KEYWORD9=value9

Continuation statements are allowed, by the following rules:

1. A parameter list in parentheses may be wrapped after a comma. For example:

       KEYWORD1=(value1,   comment: continued on the next line
       value2)

2. A parameter value enclosed in apostrophes may be wrapped at the end of the line, continuing in the 1st column of the following line. For example:

       KEYWORD2=’This is a very very very very very very very very very very
       very very very very very very very very very very very very very very
       very very very very long parameter value’

   When coded as shown in the example, trailing blanks on each line are removed all but one when the parameter is parsed.

Multiple statements for the same keyword are permissible. Depending on the keyword, specifying the same keyword again may override a previous specification (example: PATCHAR); or add another member to a list (example: RESIDENTPAGE).

When entered as PARM parameters in z/OS, standard PARM entry conventions apply. Each keyword must be entered in its entirety in any given statement in the format:

    KEYWORD=value

Software AG recommends that you always use the full spelling, to prevent confusion with future new parameters.

In the descriptions that follow, the minimum abbreviations required for each sysparm are indicated by an underscore.

If a keyword option is omitted, the default value takes effect. If column one of any statement contains an asterisk, that statement is treated as a comment.

> ACCESS-FORCE

>   Optional.

>   Value | YES|NO
>   Default | NO

>   Specifies that the sign-on call in initialization will overwrite any existing entry in the Adabas SVC ID table.

> ACCESS-ID

>   Optional.

>   Value | n
>   Default | None

>   Specifies the unique node number that identifies the Com-plete system.

> ACCESS-LOCAL

>   Optional.

>   Value | YES|NO
>   Default | YES

>   Specifies the scope of the ACCESS node (local or global).

> ACCESS-NABS

>   Optional.

>   Value | n
>   Default | ACCESS-NABS=3

>   Specifies the number of attached buffers to be allocated for cross-memory services.

> ACCESS-NCQE

>   Optional.

>   Value | n
>   Default | ACCESS-NCQE=5

>   Specifies the maximum number of concurrent commands for which queue space should be allocated.

> ACCESS-SVC

>   Optional.

>   Value | n
>   Default | None

>   Specifies the number of the Adabas ROUTER SVC.

> ACCESS-TIME

>   Optional.

>   Value | n
>   Default | ACCESS-TIME=30

>   Specifies the number of seconds before the returned response will be timed-out.

> ADABAS-BP

>   Value | ((no,key),(no,key)........(no,key))
>   Default | The number of subpools to allocate will be decided internally. The size of the elements depends on the definitions made to create ADALCO.

>   Where:

>   no. | Is the number of elements to allocated in the buffer subpool for this key. This must be greater than 1 and less or equal than 8,192.
>   key | Is the storage protect key in which the buffer subpool will be allocated. This may be any number between 1 and 15. For z/OS and Hitachi systems, only keys 8 to 15 should be specified here.

>   Default: A subpool is built for keys 8 to 15. 8,192 bytes will be allocated for each subpool and the number of areas that can exist in each subpool will be dependent on the size of the various ADALNK areas required.

>   This keyword is used to define the Adabas buffer pool. This buffer pool is used for Adabas interface work areas which are acquired outside of the thread but in the key of the thread. This parameter enables users to determine what key(s) buffer subpools will be built for and how many buffers will be in each subpool.

>   Notes:

>   1. If an error is encountered in an ADABAS-BP system parameter, the whole line is ignored. Therefore, if there is not a following ADABAS-BP specification in the system parameters, the defaults will be in effect.
>   2. A subsequent specification of the ADABAS-BP system parameter totally overwrites a previous ADABAS-BP specification. Therefore, if the second specification is incorrect, the defaults will again apply even if the first ADABAS-BP specification is correct.

>   #### Example:

>       ADABAS-BP=((20,9),(50,12),(100,8))

>   This will cause an Adabas buffer pool to be built with three subpools. The first subpool will be in key 9 and will have 20 elements, the second subpool will be built in key C(12) and will have 50 elements and the third subpool will be built in key 8 and will have 100 elements.

> ADACALLS

>   Value | n|(dbid,n)
>   Default | ADACALLS=10

>   Specifies the maximum number of Adabas calls that an application can make before the Com-plete/Adabas interface will force the application to be rolled out. This parameter is ignored if ADAROLL=NO is specified.

>   Note that n must be an integer between 1 and 32767.

>   Note also that dbid defines an Adabas data base ID, indicating that the specified ADACALLS parameter only applies to calls directed to the specified Adabas data base.

> ADADBID

>   Value | n|(dbid,n)
>   Default | 177

>   Specifies the default data base ID for Adabas. This value is used if the application program does not supply a specific data base ID in the Adabas control block. Refer to the Adabas Operations documentation for a description of the use of the data base ID.

>   Note that n must be an integer between 1 and 32767.

> ADALIMIT

>   Value | n|(dbid,n)
>   Default | 32768 (=32*1024)

>   The maximum value that can be specified for n is 1,048,576 (=1024*1024).

>   If ADALIMIT=0 is specified, this forces no limit, overriding the default value..

> ADAROLL

>   Value | n|ALWAYS|NO|(dbid,n)|(dbid,ALWAYS)|(dbid,NO)

>   Specifies the amount of time Com-plete will wait on Adabas calls before rolling out the program making the call.

>   Default: Com-plete calculates the optimum value for each database dynamically, based on the statistics for this database. The starting value is ALWAYS, i.e. at the first Adabas call, the program is always eligible for rollout. Then ADAROLL is calculated based on the average response time, using the following rule (here, A is the average response time):

>   A < 0.05 sec ADAROLL=0.1

>   0.05 sec < A < 0.5 sec ADAROLL=2*A

>   A > 0.5 sec ADAROLL=ALWAYS

>   Software AG recommends that you allow this parameter to default.

> ADASVC5

>   Value | n|(dbid,n)
>   Default | ADASVC5=13; the interface to Adabas will be disabled. Programs issuing a call to Adabas will be abnormally terminated with abend code U0004.

>   Specifies the decimal SVC number to be used when communicating with Adabas.

>   Note that n must be an integer from 201 to 255 for z/OS, and from 1 to 110 for z/VSE.

>   Note also that dbid defines an Adabas data base ID, indicating that the specified ADASVC5 parameter only applies to calls directed to the specified Adabas data base.

> APPLICATION-RECOVERY (not supported on z/VSE)

>   Value | YES|NO
>   Default | NO

>   Specifies whether applications which are capable of recovery (such as Natural version 4.2.2 or higher) should make use of this feature.

>   APPLICATION-RECOVERY=YES together with VTAM-PERSIST=YES allows these applications to recover automatically from system or software failures as soon as a Com-plete with the same VTAMAPPL name starts again after such a failure.

>   | Warning: Setting APPLICATION-RECOVERY=YES may significantly increase resource consumption by Com-plete and the applications running in it. Therefore this should be planned carefully.

> APPLYMOD

>   Value | n|(n,n,....n)|(m,NO)
>   Default | None

>   Specifies that the system-wide modifications n is to be included in this session of Com-plete. For a detailed description of each modification, refer to Binary Modifications (APPLYMODS).

>   Note that n must be an integer or string of integers between 1 and 128, separated by commas and enclosed in parentheses.

>   Note also that (m,NO) indicates the removal of the m modification.

> AUTOLOGOFF

>   Value | NO|n
>   Default | AUTOLOGOFF=NO

>   Specifies whether terminal users are to be logged off after a defined period of inactivity.

>   AUTOLOGOFF=NO indicates that users are not to be logged off if inactive.

>   Note that n is the number of minutes that a terminal user is allowed to be inactive before being logged off; n must be an integer between 1 and 600.

>   Specific terminals may be exempted from being logged off for inactivity by specifying "LOGOFF=NO" in the TIB macro.

>   Individual users can be exempted from being logged off for inactivity by specifying "YES" in the EXEMPT FROM AUTOLOGOFF field in the Com-plete user ID maintenance transaction.

> AUTORESIDENT (not supported on z/VSE)

>   Value | YES|NO
>   Default | YES

>   Specifies whether Com-plete is to automatically load reentrant modules into RESIDENTPAGE.

> BATCHLOGON

>   Value | YES|NO
>   Default | NO

>   Specifies whether or not this Com-plete will service batch requests.

> BUFFERPOOL

>   Value | (Esize , Eno , Expno , Loc)

>   These values define the parameters for the building of the General Buffer Pool. For each correctly specified parameter, a subpool is built in the General Buffer Pool from which all non-specific buffer pool requests are satisfied. Please refer to the section Com-plete Resource Usage and Estimates for more details on buffer pools.

>   Default:

>   The default depends on WORKLOAD-AVERAGE or on the number of tib entries. For 80 entries the following bufferpools are allocated:

>       BUFFERPOOL=(64,512,512,ANY)
>       BUFFERPOOL=(64,64)
>       BUFFERPOOL=(128,128,128,ANY)
>       BUFFERPOOL=(128,128)
>       BUFFERPOOL=(256,128,128,ANY)
>       BUFFERPOOL=(256,32,32)
>       BUFFERPOOL=(512,128,128,ANY)
>       BUFFERPOOL=(512,16,16)
>       BUFFERPOOL=(1K,80,80,ANY)
>       BUFFERPOOL=(1K,32,32)
>       BUFFERPOOL=(2K,20,40,ANY)
>       BUFFERPOOL=(2K,4,4)
>       BUFFERPOOL=(4K,20,20,ANY)
>       BUFFERPOOL=(4K,4,8)
>       BUFFERPOOL=(8K,40,40,ANY)
>       BUFFERPOOL=(16K,20,20,ANY)
>       BUFFERPOOL=(32K,20,20,ANY)
>       BUFFERPOOL=(64K,20,20,ANY)

>   Esize | Required This determines the size of each of the individual elements in this buffer subpool. The value will be rounded up to the next multiple of 64.
>   Eno | Required This determines the number of elements of the specified Esize that will initially be built in the buffer subpool to be defined.
>   Expno | Optional This determines the number of elements that the buffer subpool is expanded by the first time the primary Eno is not sufficient. If further expansions are necessary, the number is doubled each time.The Expno value is also affected by the amount of space required for pre-emptive expansion of the subpool. As not all requests can expand a subpool when it is full, Com-plete requires that the general buffer pool expands pre-emptively. The space required for pre-emptive expansion is calculated internally. When the space available in the subpool reaches the specified limit, the subpool is expanded.
>   Loc | Optional Values: BELOW ANY (31 bit capable systems only) Default: BELOW This determines where the buffer subpool elements are to be allocated. BELOW indicates that the storage should be allocated below the 16 meg line and is the default. ANY indicates that the storage can be allocated anywhere within the primary address space and will cause it to be allocated above the 16 meg line under normal circumstances.

> CAPTURE

>   Value | (n,REUSE/NOREUSE)
>   Default | Capture determines how many capture files are specified in the job control; NOREUSE

>   This specifies the number of capture data sets that are available for use.n must be a numeric between 1 and 9 and a CAPTURn DD statement /DLBL should exist for each capture data set specified. The REUSE option indicates that capture processing can reuse full data sets when all other data sets are full. The default, NOREUSE, indicates that the data set must be copied and/or reinitialized using the TUSACAPT utility.

> COM-PASS

>   Value | YES|NO
>   Default | COM-PASS=NO

>   Used to specify whether or not COM-PASS is in operation.

> COMSECDB*

>   Value | n
>   Default | none

>   Specifies the data base ID where the Com-plete Security System data base file exists. n is an integer between 1 and 255.

> COMSECFN*

>   Value | n
>   Default | none

>   Specifies the file number of the Com-plete Security System data base file.n is an integer between 1 and 255.

> COMSECLG*

>   Value | YES/NO
>   Default | NO

>   Specifies that Com-plete Security violations will be logged via message ZSS0031.

>   * Only applicable if the Com-plete Security System is installed.

> COMSTOR-BUFFERPOOL

>   Value | ( Esize , Eno , Expno , Loc )
>   Default | no COMSTOR buffer pool allocated

>   Refer to The COMSTOR Bufferpool in Resource Usage and Estimates for more information on specifications for this parameter.

>   The values have the same meaning as for the BUFFERPOOL parameter, except that the default for Loc is ANY.

> DEBUG-ALLOWUPDATE

>   Value | YES|NO|CTRL
>   Default | NO

>   Specifies whether or not, or if only for users with CONTROL status, the UDEBUG debugging utility shall allow modification of memory contents outside of the application thread being debugged.

> DEBUG-BREAKPTS

>   Value | n
>   Default | 100

>   Determines the initial number of areas allocated for the setting of UDEBUG breakpoints.As these areas are allocated using the Com-plete fixed length buffer mechanism, more areas are made available if required. However, this should be set to reflect the expected usage to avoid expansion and contraction of the DEBUG buffer pool.

> DEBUG-GLOBALSYM

>   Value | n
>   Default | 2000

>   Determines the initial number of areas allocated for global symbols. Please refer to the section on UDEBUG in the Com-plete Utilities documentation for details of what global symbols are and how the number required may be estimated. As these areas are allocated using the Com-plete fixed length buffer mechanism, more areas are made available if required. However, this should be set to reflect the expected usage to avoid expansion and contraction of the DEBUG buffer pool.

>   If an application program exceeds the CPU time specified for the thread in which it is executing, the program is abnormally terminated.

> DEBUG-LOCALSYM

>   Value | n
>   Default | 100

>   Determines the number of symbol table entries a user may define for a UDEBUG session. These are allocated out of the thread in which the UDEBUG session is running and this parameter will have a direct impact on the catalog size for UDEBUG.

> DEBUG-SESSIONS

>   Value | n
>   Default | 20

>   Determines the initial number of areas allocated to handle users running UDEBUG sessions. As these areas are allocated using the Com-plete fixed length buffer mechanism, more areas are made available if required. However, this should be set to reflect the expected usage to avoid expansion and contraction of the DEBUG buffer pool. A UDEBUG session occurs whenever the UDEBUG program is invoked. Therefore, if a user has UDEBUG running on three levels, there are three UDEBUG sessions active and three areas are required.

> DEBUG-SVC

>   Value | Between 200 and 255 (z/VSE: 254)
>   Default | 255

>   Determines the SVC number which will be used by UDEBUG to set breakpoints. When a breakpoint is set, this SVC number replaces the applicable instruction to cause UDEBUG to get control at the appropriate point. It is a logical SVC in that the SVC must not be installed as control is obtained using the SVC screening mechanism.

>   It is recommended that an uninstalled SVC be used where possible, as uninstalled SVC should never normally be issued. If the SVC is issued and it is found that this is not a UDEBUG breakpoint, the SVC will be passed on to the operating system. An existing SVC could conceivably be used and would execute correctly when issued. However, each time the SVC is issued, it would incur the extra overhead of UDEBUG checking to see if it is a breakpoint and then passing on the request EVERY time the SVC is issued. For this reason, we recommend that an unused SVC number be chosen, or an SVC which is not normally issued from the Com-plete address space. The value which can be specified here must be in the user SVC number range of 200 to 255 (z/VSE: 254).

> DUMPDSN

>   This data set name pattern is used for the dump data set when SMARTS writes a dump using the z/OS IEATDUMP service.

>   (z/OS only) Value | Any valid data set name, use of system symbols is permitted. See IBM documentation of the macro IEATDUMP, parameter DSNAD= .
>   Default | None. Com-plete uses SDUMP instead of IEATDUMP.

>   Software AG recommends that you specify this parameter for non-APF authorized installations in order to avoid SNAP dumps.

>   For authorized installations this is not necessary, because SDUMP can be used. SDUMPs are written to SYS1.DUMPxx (or substitute).

>   Note
>   The data set name must be one that the userID in effect for the SMARTS address space is permitted to allocate.

>   Example for fixed dump data set name:

>       DUMPDSN=DUMP.DATASET.NAME

>   Example using symbols:

>       DUMPDSN=DUMP.&jobname..D&YYMMDD..T&HHMMSS.

> DYNALLOC-MSGLEVEL

>   (z/OS only) Value | 0, 4, 8, or 12
>   Default | 12

>   This keyword can be used to select a severity level for messages related to dynamic dataset allocation. Messages with a severity level higher or equal to the value specified will be written to the system console and to the JES log file. Any value higher than 8 will cause Com-plete to request no messages at DYNALLOC invocation. This parameter can also be changed dynamically using UUTIL subfunction TO.

> EOJ-VER

>   Value | character string
>   Default | None

>   Specifies that the indicated character string must be entered as part of the EOJ operator command when Com-plete is terminated.

>   Note that the value specified must be a one- to eight-character string.

> GLOBAL-MAXENQS

>   Value | between 100 and 32767
>   Default | 1024

>   This determines the maximum number of ENQs or LOCKs that can be outstanding from user programs in the Com-plete region or partition.

> HARDCOPYKEY

>   Value | NONE/(interrupt key,OVERRIDE)
>   Default | NONE

>   Specifies which key is to be used to initiate hardcopy requests. Valid values for interrupt key are PA1, PA2, PA3, PF01, PF02 ...... PF24, CLR and TREQ. This is the system default and can be overriden by individual users in their profiles.

>   The OVERRIDE option only has an effect when the selected key is PA2. If this is specified, then the application program can specify that PA2 is returned to the program rather than causing a hardcopy to be taken. If it is NOT specified, the application cannot request the PA2 key as is the case with all other keys. This option is only provided to be compatible with previous releases.

> HELLOMSG

>   Value | YES|NO|dest.code
>   Default | HELLOMSG=NO

>   Specifies whether or not the Com-plete initialization hello message is to be broadcast.

>   HELLOMSG=YES causes the hello message to be sent to all terminals except those defined as ALL=NO in the group argument of the TIB macros.

>   HELLOMSG=NO suppresses transmission of the hello message.

>   If dest.code is specified, the initialization message is sent to all terminals defined in the TIBTAB that have the specified destination code.

> INIT-PGM

>   Value | name|(name1, name2, ..., namen)
>   Default | None

>   Specifies the name(s) of programs to be loaded by Com-plete at the end of initialization. These programs must reside in the COMPLIB. They will be started in the order n which they are specified, will execute in the Com-plete address space in Com-plete's key and will be deleted after execution.
>   Note that these programs must not use the MCALL macro.

> INSTALLATION

>   Value | character string
>   Default | ********

>   Specifies a one- to eight-position character string used as an installation identification name. Note that a comma (,) cannot be part of this identification name.

>   The identification name is used by the CAPTUR function for the initial and trailer labels generated by Com-plete. It is also used in all COM-PASS utility menus.

> IPADDRESS

>   Value | IP address or host name by which this Com-plete shall be found in the network
>   Default | none (Com-plete can only be found using the default IP address of the machine)

>   On a machine with more than one IP address available, real or virtual, this parameter can be used to allocate a specific IP address to Com-plete. This may be useful for the following reasons:

>   - It allows installations to assign the default HTTP, HTTPS, and tn3270 port numbers to Com-plete, if these are not available otherwise.

>   - Using a two-stage DVIPA architecture, HTTP workload balancing can be achieved among multiple Com-pletes.

> IPV6

>   Value | YES|NO
>   Default | YES

>   If IPv6 is enabled on the machine where Com-plete runs, Com-plete will use it by default. No additional configuration is necessary. Specify IPV6=NO if you want Com-plete to run in IPv4-only mode on a machine with a dual v4/v6 stack.

> JUMPCHAR

>   Value | character

>   Specifies a character (usually a special character) as system-wide default to be used to suspend the current session with Com-plete and start the next suspended session. Users must type the character in an input field and press ENTER.

> JUMPKEY

>   Value | key

>   Specifies a PF or PA key as a system-wide default to be used to suspend the current session with Com-plete and start the next suspended session. Possible values: PF1-PF24, PA1 or PA2.

> LANGUAGE

>   Value | n (1..255)
>   Default | LANGUAGE=1 (English)

>   Specifies the default language used to build the user's COM-PASS menu.

> LARGEPAGES

>   Value | YES|NO
>   Default | YES

>   Where applicable, Com-plete allocates the 31-bit thread areas as well as the 64-bit ROLL buffer pool in large (1M) pages. Specify LARGEPAGES=NO if this is not desired.

> LEPIPI-RUNTIME-OPTS

>   Value | string of up to 255 characters
>   Default | TRAP(OFF)

>   Specifies runtime options for IBM Language Environment modules invoked with the Com-plete application programming function LEPIPI.

>   #### Example:

>       LEPIPI-RUNTIME-OPTS='RPTOPTS(ON) RPTSTG(ON)
>       STACK(32K,32K,ANY,KEEP)
>       THREADSTACK(OFF)
>       STORAGE(NONE,NONE,NONE,8K)'

>   See also the information on continuation lines earlier in this section.

> LEPOSIX-RUNTIME-OPTS (z/OS only)

>   Value | string of up to 255 characters
>   Default | POSIX(ON) ABTERMENC(ABEND) TERMTHDACT(UADUMP)

>   Specifies IBM Language Environment runtime options for Com-plete’s HTTP and tn3270 server component. This parameter can be used if the default LE runtime options in effect on the LPAR are not suitable for Com-plete; for example, if those defaults result in allocation of memory below the 16MB line for each enclave.

>   #### Example:

>       LEPOSIX-RUNTIME-OPTS=’POSIX(ON)
>       RPTOPTS(ON) RPTSTG(ON)
>       ALL31(ON)
>       STACK(16K,16K,ANY,KEEP,0,0)’

>   Notes:

>   1. If this parameter is specified, its value must include the option POSIX(ON).
>   2. This parameter has no effect on other LE applications running under Com-plete.
> LIBRARIAN

>   Value | "'text'"
>   Default | LIBRARIAN='NOLIST,NOEXEC' (z/OS only.)

>   Specifies the parameters that are passed by the Com-plete editor through its interface to LIBRARIAN during a SAVE command. The values will appear on the "-SEL" card.

>   Note that text is a character string and must be enclosed within single quotation marks.

> LICENSE

>   Default | DD:LICENSE

>   Specifies the location of the Com-plete license file, in path notation.

>   #### Examples:

>       LICENSE=/some/pds/license

>   refers to member SOME.PDS(LICENSE).

>       LICENSE=/lib/sublib/license.xml

>   refers to z/VSE library LIB, sublib SUBLIB, member LICENSE.XML.

>   Note that if you store your license as a sequential file, then the file name must be terminated with a slash in the LICENSE parameter:

>       LICENSE=/sequentl/license/file/

> MAXENQS

>   Value | n
>   Default | MAXENQS=15

>   Specifies the maximum number of z/OS ENQs or z/VSE LOCK that may be outstanding for any one application program. Each outstanding ENQ/LOCK resource held will occupy 24 bytes plus the length of RNAME in the general buffer pool while the resource is held (whether it is held as SHR or EXCLUSIVE).

>   Note that n represents any integer from 1 to 256.

> MAXLIBS

>   Value | n
>   Default | MAXLIBS=40 (z/VSE only.)

>   Specifies the maximum number of entries in the z/VSE file table for keeping track of libraries. Each entry in the file table occupies 64 bytes.

>   Note that n represents any integer from 1 to 200.

> MAXPOCOPIES

>   Value | n
>   Default | 255

>   This keyword can be used to limit the number of copies a user can request when creating a printout.

>   n represents any integer from 1 to 255.

> MAXPOLINES

>   Value | n
>   Default | MAXPOLINES=65535

>   Controls the maximum number of printout spool lines which can be written to an individual printout. If this number is exceeded, the application is terminated with message MPO0203.

> MAXPOQUEUE

>   Value | n (0 .. 32767)
>   Default | MAXPOQUEUE=10

>   Specifies ther maximum number of printouts that can be queued to a printer before Com-plete reschedules to the alternative printer.

> MAXPRINTOUT

>   Values | n
>   Default | MAXPRINTOUT=512

>   Specifies the maximum number of printouts that can be held in Com-plete's printout spool data set or spool buffer pool. You must ensure that at least as many blocks are allocated for the COMSPL data set as the MAXPRINTOUT value, otherwise I/O errors may occur.

>   Note that when using a spool dataset, the value for n may only be changed with a Com-plete restart in which MSGSTART=COLD and POSTART=COLD are specified.

> MAXSPOOLSIZE

>   Values | n[M|G]
>   Default | none

>   The presence of this parameter tells Com-plete to use a 64-bit buffer pool rather than a spool dataset for print jobs. When MAXSPOOLSIZE is specified, a COMSPL DD JCL statement is not required and is ignores when present.

>   Specifies the maximum amount of 64-bit memory, in either Megabytes or Gigabytes, to be used for the print jobs buffer pool. Memory is allocated as needed in increments of 1Mbyte or more, up to the maximum specified. The initial allocation is MAXPRINTOUT*2*4K. A print job remains in the buffer pool from when it is being created until it is transferred to VTAM (if ever) or until Com-plete is shut down. When the size limit is reached, attempts to create more print jobs will fail.

>   If you have so far used a VSAM spool dataset, multiply the number of available blocks as shown in USPOOL by 4; this gives you the K value that should be set here.

>   If the value you you set is too small to hold MAXPRINTOUT, the limit will be corrected to MAXPRINTOUT*2*4K.

> MAXTASKS

>   Value | n Where n is the maximum number of tasks within task groups that will be allocated. The number must be greater than zero and less than or equal to 26 for z/VSE (i.e. z/VSE maximum tasks = 32 less 6 Com-plete system tasks) or or 999 for z/OS.
>   Default | MAXTASKS=999 (z/OS) MAXTASKS=26 (z/VSE)

>   This keyword is used to define the maximum number of tasks which will be used within a given Com-plete run.

>   This parameter should be allowed to default unless there is a valid reason for restricting the number of tasks to be attached. The only mechanisms for causing tasks to be attached are through the startup parameters or through the TASKS operator command.

> MESSAGE-ID

>   Value | x
>   Default | Patch-character

>   Com-plete messages have a prefix with the format pppgggnnnn-i, where

>   ppp | Product ID (COM, TPF)
>   ggg | Message Group ID
>   nnnn | Message Number
>   i | System ID

>   By default, the patch character is used as the system ID (see the PATCHAR sysparm). Specify MESSAGE-ID=INSTALLATION to append the installation ID instead of the patch character.

> MSGEXPIRE

>   Value | n
>   Default | None

>   The number of days a mailbox message is to be preserved.

> MSGSTART

>   Value | COLD|WARM|HOT|NO
>   Default | MSGSTART=NO

>   Specifies the restart option to be applied at Com-plete initialization time to the COMSPL dataset for messages not entirely written to their receiving terminals when Com-plete terminates processing (normally or abnormally). Messages with class codes of 3 will always be restarted.

>   MSGSTART=COLD indicates that no messages are to be requeued. In this situation, Com-plete writes zeros to each message record on the COMSPL dataset. All queued messages will be permanently lost. Note that messages are not deleted from the message file except during a COLD start or when overlayed.

>   MSGSTART=WARM indicates that messages not entirely written to their receiving terminals will be requeued. In this situation, all requeued messages will be restarted from their beginning except class 4, 12, 14, or 16 messages.

>   If a message is sent to a multiple number of terminals and not received at one or more of those terminals, it is restarted for those terminals from the beginning of the message. If a terminal user was in the process of recalling a message, it will not be restarted.

>   Note that when Com-plete is started with the WARM option in effect, the same TIBTAB must be used.

>   MSGSTART=HOT indicates that messages not entirely written to their receiving terminals are to be requeued. Printing for requeued messages is to begin from the last checkpoint taken by Com-plete.

>   MSGSTART=NO indicates that no messages are to be requeued. Here, none of the message records in the message queue file are destroyed. In this case, a subsequent WARM or HOT start might requeue a message originally queued before the time MSGSTART=NO was specified. Message requeuing causes the next message number to be one.

>   Messages with class codes 4, 12, or 14 are not requeued, and messages with class code 3 will always be restarted from the beginning.

>   | Warning: If a new TIBTAB is being used, you must specify MSGSTART=COLD or the results may be unpredictable.

>   Note
>   If the MSGSTART parameter is set to NO or COLD, the Mailbox facility will not be effective.

> NATSECDB

>   Value | n
>   Default | NONE

>   Specifies the data base number of the Natural Security file (validates user ID and password during logon to Com-plete) n must be an integer between 1 and 65535. See the description of the interface to Natural Security in section Software Interfaces.

> NATSECFN

>   Value | n
>   Default | NONE

>   Specifies the Natural Security file number (used to validate user ID and password during logon to Com-plete. n must be an integer between 1 and 65535. See the description of the interface to Natural Security in section Software Interfaces.

> OPERLOG

>   Value | YES|NO
>   Default | YES

>   When emulating a z/OS system console for UQ-M or for the Web gateway, Com-plete first attempts to use OPERLOG; if this fails it uses SYSLOG. Specify OPERLOG=NO to avoid this check and force using SYSLOG.

> PASSWORD

>   Value | YES|NO|PHRASE
>   Default | PASSWORD=YES

>   YES/NO specifies whether or not a password is required of the terminal user when the ULOG utility program is invoked with the ON option.

>   PHRASE allows the use of password phrases of up to 100 characters. PHRASE implies YES.

> PASSWORD-EXPIRE

>   Value | n (0..999)
>   Default | PASSWORD-EXPIRE=0

>   n days after the last successfull password alteration, Com-plete will force the user to change the password again.

>   A value of 0 advises Com-plete not to force the user to change the password at all.

> PASSWORD-RETRIES

>   Value | n (0..255)
>   Default | PASSWORD-RETRIES=3

>   Specifies the number of attempts a user has to type in the correct password before his User ID is locked.

> PATCHAR

>   Value | <char>
>   Default | "*"

>   Specifies a character that must, if different from astersik (*), uniquely identify the running Com-plete within the system. If another Com-plete with the same character is active, Com-plete will be terminated during initialization. Any valid printable character can be specified as the patch character.

>   A patch character of "*" allows multiple Com-pletes with this patch character to be active at the same time.

>   This character is of importance in two areas. Firstly, every message sent to the console will have the patch character of the issuing Com-plete following the message dentifier in brackets eg. ABS0006 (2) etc. Prior to the sysparms being processed, the default patch character will be shown in all messages.

>   Secondly, data can be added to the profile system as being specific to a certain system. When the data is read, data relating to the patch character of the running system will be searched for before taking the global information. In this way, you can customize your sessions differently in different Com-pletes using the same Com-plete system data set.

> PGMLOOKASIDE

>   Value | name
>   Default | None

>   Specifies the name of a program to be preloaded into storage at Com-plete initialization from a library in the COMPLIB chain.

>   The program can be any program except those programs linked with overlay. Programs specified are accessible by terminal invocation and via the Com-plete functions ATTACH, COLINK, COLOAD, COXCTL, FETCH, LINK, and LOAD. All attributes such as RG, PV etc. are taken from Com-plete's Program Catalog. To load more than one program, multiple statements can be provided.

>   Note that programs residing in PDSE load libraries are not eligible for Com-plete's Fast Load Facility and are therefore ignored when specified by a PGMLOOKASIDE statement.

> POEXPIRE

>   Value | n
>   Default | None

>   The number of days a printout is to be preserved.

> POLDRV

>   Value | "Program Name"
>   Default | none

>   Specifies a default logical output driver name to be used for all printouts that do not specify a logical output driver themselves. For more information on logical output drivers, refer to section Defining Terminals and Printers.

> POSTART

>   Value | COLD|WARM|HOT|NO
>   Default | POSTART=NO

>   Specifies the restart option to be applied at Com-plete initialization time to the spool dataset for printouts not entirely written to their receiving terminals at the time Com-plete terminates processing (normally or abnormally).

>   POSTART=COLD indicates that no printouts are to be requeued. In this situation, Com-plete writes zeros to each printout record on the spool dataset. All queued printouts will be permanently lost. Note that printouts are not deleted from the spool dataset except during a COLD start or when overlayed.

>   POSTART=WARM indicates that printouts not entirely written to their receiving terminals will be requeued in their entirety. In this situation, all requeued printouts will be restarted from the beginning.

>   Note that when Com-plete is started with the WARM option in effect, the same TIBTAB must be used.

>   POSTART=HOT indicates that printouts not entirely written to their receiving terminals are to be requeued. Printing for requeued printouts is to begin from the last checkpoint taken by Com-plete.

>   POSTART=NO indicates that no printouts are to be requeued; none of the printout records in the message queue file are destroyed. In this case, a subsequent WARM or HOT start might requeue a printout queued before that POSTART=NO was specified.

>   Printouts with class codes 4, 12, or 14 are not requeued, and printouts with class code 3 are always restarted from the beginning.

>   | Warning: If a new TIBTAB is being used, you must specify COLD, or the results may be unpredictable.

> PROGRAMISD

>   Value | n
>   Default | PROGRAMISD=40

>   Specifies the number of In-Storage Directory (ISD) slots to be reserved for Com-plete online programs.

>   Each ISD entry contains the disk address of an online program that has been or is executing. For a given ISD, the entries are dynamically altered to reflect the most current program usage based upon frequency of use.

>   Each program ISD entry occupies 128 bytes of page-fixed storage.

>   Note that n must be an integer from 1 to 16 digits in length. The minimum value is 10.

> RECALLCHAR

>   Value | x
>   Default | RECALLCHAR=NO

>   Specifies whether or not a recall character is available and what that character is. x can be any character which can be entered at a terminal. If this character is printed as the first character on ANY screen, it is taken as the recall character and the data is not passed to the application. This specification is simply the system default. Users can set their own recall characters.

>   The specified character, if any, must not be the same as that specified for the suspend character via the SUSPENDCHAR sysparm.

> RESIDENTPAGE

>   Value | program-name
>   Default | None

>   Specifies the name of a program or map to be loaded and made resident at Com-plete initialization time.

>   Note that the program must be fully reentrant. If it is not marked reentrant, a warning message is issued on the operator's console at Com-plete initialization time.

>   The program or map must reside in the COMPLIB of the Com-plete initialization procedure.

>   The program is subsequently accessible via the COLINK, COLOAD, COXCTL, LINK, LOAD, and XCTL functions.

>   Maps are subsequently accessible by online applications by the use of the WRTM or READM functions.

>   Multiple statements can be used to load more than one program.

> RESOURCE-MANAGER (z/OS only)

>   Value | YES|NO
>   Default | NO

>   Specifies whether or not Com-plete should act as a z/OS Resource Manager in terms of the IBM documentation MVS Programming: Resource Recovery.

>   RESOURCE-MANAGER=YES is required for running DB2 transactions in Com-plete, and it may be required by Software AG or 3rd party transaction managers. If you are using a transaction manager with Com-plete, see the documentation of the product to determine whether or not it requires the transaction environment to be a Resource Manager.

>   If Com-plete is not required as a Resource Manager, leave it turned off; this will save resources and increase performance.

> RJE

>   Value | ALLOW|DISALLOW
>   Default | ALLOW

>   Specifies whether or not Com-plete remote job entry requests are to be honored.

>   The value for this sysparm can be overridden dynamically at any time by use of the Com-plete operator commands ALLOW and DISALLOW.

> ROLL-BUFFERPOOL

>   Value | (Esize,Eno,Expno,Loc)
>   Default | A default Roll-Bufferpool is built internally according to the number of TIBs defined in TIBTAB. It is located in either 64-bit storage or dataspaces (whatever is applicable to your operating system configuration).

>   It is also possible to specify just the location of the ROLL buffer pool, while letting Com-plete do the calculation of the internal structure (subpools). This may be useful in cases where, for whatever reason, it is not requested to have Com-plete build the ROLL buffer pool in 64-bit memory.

>   The syntax in this case is

>        ROLL-BUFFERPOOL= [ 64BIT | 31BIT | DS ]

>   Note
>   Under z/VSE, error messages like
>   `DXRINI0014-2 BP CREATE FOR ROLL BUFFER POOL RETURNED STATUS='00080024' DXROPC0049-2 RETURN CODE 4 FROM MODULE 'TLINROLL'`
>   indicate a lack of Dataspace.

>   Please refer to the section Com-plete Resource Usage and Estimates for more information on specifications for this parameter.

>   The values have the same meaning as for the BUFFERPOOL parameter, except the values for Loc:

>   BELOW | BELOW 16 MB
>   ANY | ABOVE 16 MB
>   DS | Dataspace (default)

>   It is not possible to allocate the ROLL-BUFFERPOOL explicitly in 64bit storage.

>   The following ROLL-BUFFERPOOL SYSPARMs are generated by default:

>       ROLL-BUFFERPOOL=(064K,number_of_TIBs / 2,number_of_TIBS / 2,DS)
>       ROLL-BUFFERPOOL=(128K,number_of_TIBs / 4,number_of_TIBS / 4,DS)
>       ROLL-BUFFERPOOL=(256K,number_of_TIBs / 8,number_of_TIBS / 8,DS)
>       ROLL-BUFFERPOOL=(512K,number_of_TIBs / 16,number_of_TIBS / 16,DS)
>       ROLL-BUFFERPOOL=(biggest_THREAD_size + 4K + 16K +1K,2,2,DS)

>   #### Example:

>   If the number of TIBs in TIBTAB is 256 and the biggest THREAD size is 1536K (512K below and THSIZEABOVE=1024), the following ROLL-BUFFERPOOL statements are generated:

>       ROLL-BUFFERPOOL=(064K,128,128,loc)
>       ROLL-BUFFERPOOL=(128K,064,064,loc)
>       ROLL-BUFFERPOOL=(256K,032,032,loc)
>       ROLL-BUFFERPOOL=(512K,016,016,loc)
>       ROLL-BUFFERPOOL=(1557K,2,2,loc)

>       Loc = 64BIT or DS depending on your OS configuration

>   #### z/VSE Considerations

>   If you allow the roll buffer pool to be built in a data space (the recommended way), you might need to adjust your SYSDEF DSPACE definitions as follows:

>   1. Check with QUERY DSPACE that enough space is left for your intended allocations and also for expansions.

>   2. Since each base subpool and each subpool expansion of the roll buffer pool is allocated in a separate data space, you should consider increasing the value of PARTMAX (default is 16).

> SDLEVEL

>   Value | NO|YES|userid

>   This parameter is supported only for sites that were using it in a previous version of Com-plete. You are strongly recommended to use or omit this parameter as you did before.

> SD-PREFIX

>   Value | dsname
>   Default | none

>   This parameter, when specified, indicates that each SD file is to be allocated as a separate VSAM dataset with a dataset name starting with this prefix. Please refer to Com-plete Files and Associated User Files for the rules describing how the resulting dataset name is built.

>   dsname must adhere to the operating system rules for valid dataset names. Its length must not exceed 28 characters. The last character must not be a dot ('.').

> SD-RLS

>   Value | YES|NO
>   Default | NO

>   This parameter takes effect only for dynamic SD files, i.e., when SD-PREFIX is also specified, and if DFSMS version 1.4 or higher is active on the system.

>   SD-RLS=YES causes Com-plete to access dynamic SD files using VSAM RLS, i.e., the dataset is allocated with parameter RLS=NRI and the ACB is opened with MACRF=RLS.

>   The SMS dataclass specified with SD-SMSCLASS must allow for use of RLS access by means of the parameter LOG(NONE). Note that the LOG parameter of a dataclass does not exist in DFSMS versions prior to 1.4., therefore SD-RLS is ignored if DFSMS version 1.4 or higher is not active on the system.

> SD-SMSCLASS

>   Value | (dataclass,storageclass,managementclass)
>   Default | none

>   This parameter takes effect only when SD-PREFIX is also specified. It defines the SMS classes Com-plete uses for creating dynamic SD files.

>   Each subparameter correspondents to a DYNALLOC parameter. Com-plete does not define any default values for these parameters, i.e., when you omit a subparameter, Com-plete omits the corresponding DYNALLOC parameter causing system defaults, if any exist, to take effect.

> SDSIZE

>   Value | n
>   Default | SDSIZE=1500

>   Specifies the size of the initial SD file that is allocated by the Com-plete utilities UED and UEDIT.

>   Note that n represents the number of records of a member being edited. Here, n must be an integer between 10 and 9999.

> SECDEFAULT

>   Value | ALLOW|DISALLOW
>   Default | SECDEFAULT=DISALLOW (z/OS only.)

>   Specifies whether or not Com-plete will honor all password-protected file requests. This parameter is checked in module ULSRSEC, the password protection routine.

> SECSYS

>   Value | NO|RACF|ACF2|TOPSECRET| COMSEC,R|A|T
>   Default | SECSYS=NO

>   Specifies an alternate security system to be used. This subsystem is used to validate user IDs and passwords during logon and is interrogated in order to determine data set access authority during utility processing.

> SECSYS-APPL

>   Value | name
>   Default | SECSYS-APPL=COMPLETE

>   Specifies the Application Name to be used for uniquely identifying this Com-plete nucleus to the External Security System (see SECSYS). "SECSYS-APPL=&VTAMAPPL" tells Com-plete to copy the name from the SYSPARM VTAMAPPL.

> SECSYS-EXECUTIONCONTROL

>   Value | (class_name,resource_name)
>   Default | None

>   Specifies the name of a SAF class and the name of a resource (key) to be used by Com-plete for checking users’ permissions to execute application programs.

>   See section Controlling Program Execution in Software Interfaces for information on how to setup this SAF class and resource.

>   If this parameter is not specified, then no SAF checks are performed for program execution, and only the traditional security means take effect.

> SERVER

>   Value | (serv-id , init-mod , p1 , p2 .... pn)
>   Default | none
>   serv-id | the ID for this server (1-8 chars)
>   init-mod | the name of the initialization/termination routine.
>   p1...pn | parameters to be passed to the init-routines

>   This will cause Com-plete to build a Server Directory Entry (SDE) for the specific Server and pass control to the initialization routine specified to cause the Server to be initialized. Refer to section Com-plete Servers for more information.

> SESSION-RECONNECT

>   Value | YES|NO|ONREQUEST
>   Default | NO

>   Allows to take over an existing Com-plete session on another terminal of the same type (VTAM, TELNET). If the value is set to 'ONREQUEST', the terminal user can decide on the Logon screen if he wants to reconnect to an old session.

> SMFCHECKPOINT

>   Value | n|nT
>   Default | SMFCHECKPOINT=15

>   Specifies the time in minutes or transactions, allowed to elapse before an SMF checkpoint record is written for a terminal user.

>   n specifies an integer from 1 to 32767 as the number of minutes to elapse before the checkpoint record is to be written.

>   Note that nT specifies the number of transactions (i.e., program dispatches from the ready-to-run queue commonly called a called a ROLLIN) to be executed before the checkpoint record is to be written, where n is an integer from 1 to 256, and T is a constant.

> SMFLOG

>   Value | (r1,r2,r3,r4)
>   Default | SMFLOG=(LOG,NO,NO,LOG)

>   Specifies the logging action to be taken for the various SMF records written by Com-plete. The four positional parameters represent the following SMF records:

>   r1 | ULOG ON record
>   r2 | program termination record
>   r3 | checkpoint record
>   r4 | ULOG OFF record

>   Each positional parameter must be replaced with one of the following values:

>   NO | the corresponding record is not to be logged.
>   LOG | the corresponding record is to be logged to the operating system logging device (WTL/SYSLST logging device)
>   OPERATOR | the corresponding record is to be logged to the operator's console (SYSLST)

> SMFRECORDS

>   Value | (r1,r2,r3,r4,r5)
>   Default | SMFRECORDS=(0,0,0,0,0)

>   Specifies the user SMF record numbers, if any, to be assigned to the corresponding Com-plete accounting records. The five positional parameters represent the following SMF records:

>   r1 | ULOG ON record
>   r2 | program termination record
>   r3 | checkpoint record
>   r4 | ULOG OFF record
>   r5 | User-defined SMF record

>   Each positional parameter must be replaced with either the number 0 or an integer from 128 to 255.

>   Note that 0 (zero) specifies that the corresponding record is not to be written.

>   Valid user SMF record numbers are 128 through 255. Replacing a parameter with a number from this range causes the corresponding accounting record to be written to the SMF file using the designated number.

>   In z/VSE, the SMF accounting records are written to the the Com-plete capture data set(s).

> SSL-KEYRING-FILE

>   Specifies the name of the key database HFS file of the SAF key ring. A key database is used if a stash file is defined either with an USS environment variable or the parameter SSL-KEYRING-STASH-FILE.

>   This parameter maps to the IBM parameter GSK_KEYRING_FILE; see the IBM documentation z/OS System SSL Programming for further details.

>   For z/VSE, specify the lib.sublib (in form SSL-KEYRING-FILE=LIB.SUBLIB) in which the private key and certificates are stored. The lib name must be 7 characters or less, followed by a period, followed by the sublib name.

> SSL-KEYRING-LABEL

>   Specifies the label of the key used to authenticate the application. If no key label is specified, the default key will be used.

>   This parameter maps to the IBM parameter GSK_KEYRING_LABEL; see the IBM documentation z/OS System SSL Programming for further details.

>   For z/VSE, specify the LIBRARY member name for the .cert, .root and .prvk files to be read from the SSL-KEYRING lib.sublib. The member name must be eight characters or less.

> SSL-KEYRING-STASH-FILE

>   Specifies the name of the key database password stash file. This parameter maps to the IBM parameter GSK_KEYRING_STASH_FILE; see the IBM documentation z/OS System SSL Programming for further details.

>   This parameter is not used in z/VSE.

> STACKMAXIMUM

>   Value | n
>   Default | STACKMAXIMUM=9

>   Specifies the maximum number of suspended transactions a COM-PASS user may have.

>   Here, n must be an integer from one to nine.

> STARTUPPGM

>   Value | name|(name1,name2,...,namen)|‘name parmstring’
>   Default | None

>   Specifies the name(s) of programs to be invoked by Com-plete at the end of initialization. The programs specified can be any Com-plete application programs. They will be started in the order in which they are specified and will execute as attached tasks under Com-plete's user ID.

>   Note that there must be sufficient batch or free TIBs in Com-plete's TIBTAB to accommodate the number of programs specified.

>   A parmstring, if present, is passed to the program in the same way as it would when the program is invoked with parameters from a terminal. The program can access the parameters using the API function READ.

>   Note
>   For z/VSE, STARTUPPGM=U2SPIT is required in order to build the LIBRARY TABLE. Failure to do so will result in abnormal conditions for the utilities USERV, UED, and UEDIT.

> SUBSYS-ACTIVATE

>   Value | subsystem name
>   Default | none

>   Activates a subsystem not active by default. Refer to the section Com-plete Subsystems for more information.

> SUBSYS-IGNORE

>   Value | subsystem name
>   Default | none

>   Deactivates a subsystem active by default. Refer to the section Com-plete Subsystems for more information.

> SUSPENDCHAR

>   Value | "x"
>   Default | SUSPENDCHAR=NO

>   Specifies whether or not a suspend character will be available and what that character is. x can be any character which can be entered at a terminal. Entering this character without data has the same effect as pressing the suspend key.

>   If this character is entered as the first character on ANY screen, it will be taken as the suspend character and the data is not passed to the application. This value is simply the system default. Users can set their own suspend characters.

>   The specified character, if any, cannot be the same as that specified for the recall character via the RECALLCHAR keyword.

> SUSPENDKEY

>   Value | NONE|interrupt key
>   Default | SUSPENDKEY=NONE

>   Specifies which key is to be used to suspend a COM-PASS level. Valid values for interrupt key are PA1, PA2, PA3, PF01, PF02 ...... PF24, CLR and TREQ. This is the system default and can be overriden by individual users in their profiles.

>   If SUSPENDKEY is set to any value, SUSPENDCHAR must also be set.

> TASK-GROUP

>   Value | (grp,no.,priority,maxq)
>   Default | TASK-GROUP=(DEFAULT,1)

>   This keyword is used to define the task groups, each containing one or more tasks, which will be available when Com-plete is started.

>   Where:

>   grp | Is the name of the task group being defined.
>   no | Is required and indicates the number of tasks to be allocated in the task group. This value must be greater than 0 and less than 1000 (z/OS) or 26 (z/VSE).
>   priority | Default: 248 is the operating system priority to be assigned to the operating system task which is attached for z/OS and Hitachi systems only. This parameter will be accepted under z/VSE but will have no meaning. The value specified must be between 0 and 255 inclusive. Note that the highest priority which can be assigned is the priority at which the task dependent service processor task is running. Without HPE, this will be 250 therefore, while 255 will be accepted, the task will in fact only be given a priority of 250.
>   maxq | Default: 16 Specifies the maximum number of TIBs which are expected to be on this task groups work queue at the same time. Under normal circumstances, the default should be perfectly adequate. When there are problems and it is not, a secondary Last In First Out (LIFO) queue will be used so that no work is lost. The normal queue is First In First Out (FIFO) which insures that work is done in the order in which it is received which is why the LIFO queue is only used as a secondary backup.

>   Notes:

>   1. A maximum of 16 task groups may be defined.
>   2. Task group names will be upper cased prior to being processed, therefore, entering the parameter in lower case will be treated as, and appear in, upper case letters.
>   3. Where more than one specification appears for a task group, the last valid specification will be used.
>   4. A task group SYSTEM is built internally. If you try and set up your own definitions for this group, the control blocks will be allocated but the group will never be used.
>   5. The task group DEFAULT must always exist in the system. If it is not explicitly defined by the installation, the task group will be built by the system with the default values.
>   6. The total number of tasks to be attached must not exceed the MAXTASKS specification. This is not checked until the task groups are being built and exceeding the value will therefore lead to task group allocation errors as against parameter errors.
>   7. Note that the task group name SYSTEM is reserved for internal use by Com-plete.

>   #### Examples:

>       TASK-GROUP=(DEFAULT,4)

>   This will cause the DEFAULT task group to be allocated with four attached tasks and the default priority and maximum queue size specification.

>       TASK-GROUP=(DEFAULT,4,200)
>       TASK-GROUP=(TASK-GRP,4,150)

>   This will cause the DEFAULT task group to be allocated with four attached tasks with a priority of 200 and the default maximum queue size specification. A second group called TASK-GRP will also be allocated with three attached tasks, a priority of 150 and the default maximum queue size specification.

> THREAD-ESQA-SIZE

>   Value | 6K <= n <= 1024K "K" is mandatory.
>   Default | 6K

>   Under certain circumstances Natural may want to load thousands of modules per app instance (thread). The control blocks required for this in Com-plete would not fit into the default fixed size (6K) of 31-bit thread SQA.

> THREAD-GROUP

>   Value | (grp,(sub,size,no,cpu,real,key),...,(sub,size,no,cpu,real,key))
>   Default | THREAD-GROUP=(DEFAULT,($DEFAULT,128,2))

>   This keyword is used to define the thread groups, each containing one or more thread sub-groups and threads, which will be available when Com-plete is started.

>   Where:

>   grp | Is the name of the thread group being defined.
>   sub | Is the name of the sub-group being defined. If a sub-group name is specified more than once for the same group, the last valid specification will be used when parameter processing has been completed.
>   size | Is required and indicates the amount of storage in Kbytes which will be allocated for each thread below the line. This value must be 8k or greater and less than 1 megabyte. If applymod 35 is set, the maximum is 1008. Each sub-group in a thread group must have a different size.
>   no. | Is required and indicates the number of threads to be allocated in the thread sub-group. This value must be greater than 0 and less than 4,096.
>   cpu | Default: 2.00 seconds Is the CPU time in seconds which a user program can use in the thread sub-group for one Com-plete transaction. This value may be entered as an integer or to a level of hundredths of seconds using the n.nn syntax. If a 0 is provided as the CPUTIME for a thread sub-group, there will be no CPU limit placed upon programs running in the associated threads.
>   real | Default: 3.00 Seconds Specifies the elapse time in seconds for the thread sub-group after which, a message will be issued to the console if the user program has not given up control of it's thread. This value may be entered as an integer or to a level of hundredths of seconds using the n.nn syntax. If 0 is specified, no elapsed time checking will be done for the thread sub-group.
>   key | Default: M This defines the key in which the threads within the sub-groups will be allocated. If 'M' is specified, the thread keys will be a mixture of user keys excluding the key in which Com-plete is running. If 'N' is specified, no storage protection will be implemented and all threads will run in the same key as Com-plete. The user may also explicitly specify a value in the range 1 to 15 inclusive which will cause each thread to be allocated that key explicitly.

>   #### Notes:

>   A maximum of 8 thread groups may be defined.

>   A maximum of eight sub-groups can be allocated per thread group. The thread sub-groups may be defined on one line or may be defined on different lines. When a second THREAD-GROUP statement is used, the same group name must be specified to relate the sub-group entries.

>   Thread group and sub-group names will be upper cased prior to being processed, therefore, entering the parameter in lower case will be treated as, and appear in, upper case letters.

>   Where more than one specification appears for a thread sub-group for a thread group, the last valid specification will be used.

>   The amount of storage specified on the THSIZEABOVE System Parameter will be allocated above the line for each thread defined as a result of the THREAD-GROUP System Parameter.

>   The thread group DEFAULT must always exist in the system. If it is not explicitly defined by the installation, the thread group will be built by the system with the default values. If it is defined, the system insures that a thread sub-group with a thread size at least as large as that required by default is allocated. If not, the system will allocate an additional sub-group for the group. If too many sub-groups have been defined, the last one defined will be overwritten to allow for the default specification.

>   The keyword data is processed from left to right. If more than one thread sub-group is defined on the one line and the line contains an error, even if an error message is issued for the line, any sub-groups processed up to the error will still have been accepted. That is to say, if the first sub-group is correct and the second is not, an error message will be issued but the first thread sub-group will be defined while the second and subsequent specifications in the same statement will be ignored.

>   #### Examples:

>       THREAD-GROUP=(DEFAULT,(SMALUTIL,80,3),(BIGUTIL,300,2,5,9,15))

>   This will cause the DEFAULT thread group to be allocated with two sub-groups. The first sub-group will be called SMALUTIL, will contain three threads with 84K below the line and will take the defaults for CPUTIME, REALTIME and the protectkey to be allocated to the thread. The second sub-group will be called BIGUTIL, will contain two threads with 304K below the line, will have a maximum of CPUTIME of 5 CPU seconds, a REALTIME value of 9 seconds and each thread will have a storage protectkey of 15.

>   The following sets of System Parameters would cause exactly the same thread sub-groups to be defined:

>       THREAD-GROUP=(DEFAULT,(SMALUTIL,80,3))
>       THREAD-GROUP=(DEFAULT,(BIGUTIL,300,2,5,9,15))
>       THREAD-GROUP=(DEFAULT,(SMALUTIL,40,8))
>       THREAD-GROUP=(DEFAULT,(BIGUTIL,300,2,5,9,15))
>       THREAD-GROUP=(DEFAULT,(SMALUTIL,80,3))

>   The following sets of System Parameters would cause exactly the same thread sub-groups to be defined in two thread groups, one called DEFAULT and the other called EXTRAGRP

>       THREAD-GROUP=(DEFAULT,(SMALUTIL,80,3))
>       THREAD-GROUP=(EXTRAGRP,(BIGUTIL,300,2,5,9,15))
>       THREAD-GROUP=(EXTRAGRP,(SMALUTIL,80,3))
>       THREAD-GROUP=(DEFAULT,(BIGUTIL,300,2,5,9,15))

> THSIZEABOVE

>   Value | n[K|M]
>   Default | non

>   Specifies the amount of storage above the 16 MB line, in Kilobytes or Megabytes, to be allocated to each thread. For compatibility with previous versions, a numeric value without “K” or “M” appended is treated as Kilobytes. The maximum size allowed is 16380K (= 16M-4K).

> TIBTAB

>   Value | name|DYNnnnnn|ANYnnnnn
>   Default | TIBTAB=DYN00050

>   Specifies the name of the terminal definition table to be loaded when Com-plete is initialized. A TIBTAB's load module's RMODE attribute is honored.

>   TIBTAB=DYN00050 indicates that a TIBTAB is to be built at initialization containing 50 free TIBs.

>   TIBTAB=ANY01000 indicates that a TIBTAB containing 1000 free TIBs is to be built above the 16 MB line.

> TRACECLASS

>   Value | class|(class,OFF)
>   Default | NONE

>   Specifies that the indicated class of trace event is to be included in, or excluded from, the Com-plete trace table.

>   Note that class is the name of a valid trace class, as follows:

>   GENERIC | Used for support purposes
>   QTIB | TIB queue management
>   OP | Application program requests
>   FIXBPOOL | Fixed-length buffer pool operations
>   VTAM | VTAM operations
>   ROLL | Roll processing events
>   ACCESS | ACCESS terminal support
>   SDFILE | SD File processing
>   RESOURCE | Resource manager get/free
>   DISPATCH | Dispatcher events
>   PRINT | Printout transmission

>   Note also that (class,OFF) indicates exclusion of the specified class.

> TRACEOPTION

>   Value | option
>   Default | No options active

>   Specifies that the indicated option is to be either in effect or not in effect for this execution of Com-plete.

>   Note that option is the name of a valid trace option, as follows:

>   ABEND | the trace will continue to run during Com-plete abnormal termination. (Normally the trace will stop recording at the first indication of abnormal termination.)
>   CAPTURE | The trace data will be written to the capture data set. For this option to have any effect, capture processing must be active. Please be aware that this option can cause a huge increase in the activity on and amount of data written to the capture data sets depending on the classes being traced.
>   EXTENDED | Specifies that trace processing is to use the extended form of the trace record. This should only be used where requested by support personnel where specific information must be found as it decreases the amount of trace records that can be held in a trace buffer.

>   Note
>   TRACEOPTION=ABEND should only be set when requested by Com-plete support personnel.

> TRACETABLE

>   Value | n|nK
>   Default | TRACETABLE=8K

>   Specifies the size of the Com-plete trace table, which is used to trace events occurring within the Com-plete system.

>   Note that use of the TRACETABLE sysparm can be a valuable tool for problem resolution.

>   The minimum size of the trace table is 8K.

>   TRACETABLE=0 indicates that no tracing is performed.

> ULOGM

>   Value | *|password
>   Default | ULOGM=*

>   Specifies an override password for access to the Com-plete online maintenance utilities (for user ID maintenance, global PF key maintenance etc.). This should only be used in an emergency when the current password cannot be established. When "*" is specified, as is the normal case, the current password must be used. password can be a 1 to 12 character string (excluding commas) which will then become the current password only for the current Com-plete run. The current password should immediately be changed during such a run so that this parameter can be set back to "*".

>   The default SYSPARM member provided on the distributed source specifies PASSWORD as the current password. You must set a current password online and remove this specification as soon as possible after the installation is finished.

> UQDEFAULT

>   Value | YES|NO
>   Default | UQDEFAULT=YES

>   Specifies the access restriction option to be exercised by the UQ utility program against terminal users when viewing SYSOUT/SYSLST data sets.

>   UQDEFAULT=YES specifies that all terminal users are allowed to view all SYSOUT/SYSLST files for any job that does not contain UQ authorization control statements.

>   UQDEFAULT=NO specifies that no terminal user can view any sysout files for any job unless the job contains proper UQ authorization control statements.

>   The UQ functions affected by this sysparm are the S, H, C, and R commands and the DE and OC keywords.

>   For more information concerning UQ authorization control statements, see UQ - System Job Queue Display Utility in the Com-plete Utilities documentation.

> UQJCL8 (JES z/OS 2.1 or higher)

>   Value | YES|NO
>   Default | UQJCL8=NO

>   z/OS 2.1 allows for JES2 longer jobclass names. If you use this feature, set the parameter to YES to get the correct display in UQ Q.

> UQWRITER

>   Value | YES|NO
>   Default | UQWRITER=NO

>   If this parameter is set to YES, UQ Q displays the WRITER instead of FLASH (JES2)

> USERID-EXPIRE

>   Value | nn|(nn,LOG)|(nn,LOG,Y)|(nn,Y)

>   nn indicates the number of months this userid has not logged on.

>   LOG causes a message to be sent to the APSLOG with all userids to be deleted.

>   Y causes userids with control status to be ignored during deletion.

>   If this parameter is set, the USERDEF file is read once a month during Com-plete startup, and deletes these unused userid definitions. The first run is done when you set the sysparm for the first time. You will be informed of the number of records which have been deleted and/or the date of the next run. Model userids and special ids like SAGADMIN or $MODLSTD are not deleted. Userid records where no LastLogon date has been set, are only deleted if they were added to the USERDEF file more than nn months ago.

>   If you want to modify the parameter and/or force the DELETE before the monthly interval has expired, start your Com-plete once with USERID-EXP=0 and then again with the desired parameter value.

> VSAMBUFFERS

>   Value | NO|(size=n)|(sizeK=n)| (size=n,sizeK=n,size=n)
>   Default | VSAMBUFFERS=NO

>   Specifies the configuration of the VSAM local shared resource buffer pool, SHRPOOL=0.

>   VSAMBUFFERS=NO specifies that no VSAM LSR pool is to be built.

>   Here, size indicates the size of an individual buffer. Note that size specified without the K option indicates the amount of storage, in bytes, to be reserved; size specified with the K option indicates the amount of storage, in multiples of 1024 bytes, to be reserved. If size is specified without the K option, the permissible values are 512, 1024, 2048, and 4096, or any other number that is a multiple of 4K (4096), up to a maximum of 32K. If size is specified with the K option, the permissible values are 1K, 2K, and 4K, or any number that is a multiple of 4K.

>   Note that n specifies how many buffers are to be allocated. Permissible values for n range from 3 to 32000.

> VSAMDS

>   Value | n
>   Default | 4

>   Specifies the initial number of ACBs in the Com-plete VSAM ACB pool. If necessary during processing, this pool will be expanded dynamically by the same number of ACBs.

>   n must be numeric.

> VSAMFIX

>   Value | BUFFERS|IOBS
>   Default | VSAMFIX=NONE

>   Specifies which VSAM areas, if any, are to be page-fixed in virtual storage.

>   VSAMFIX=BUFFERS and VSAMFIX=IOBS cause the appropriate parts of the VSAM local shared resource pool to be page-fixed. These values have effect only if a local shared resource pool is established using the VSAMBUFFERS sysparm.

> VSAMHIPERSPACE

>   Value | NO|(size=n)|(sizeK=n)|(size=n,sizeK=n,...size=n)
>   Default | NO

>   This parameter is valid for z/OS systems only.

>   Specifies the sizes and numbers of buffers in hiperspace to be allocated for the VSAM LSR pool defined by sysparm VSAMBUFFERS. Here, size indicates the size of an individual buffer in bytes (when specified without the K option) or in Kbytes. Permissible values are 4096 / 4K and multiples thereof, up to a maximum of 32768 / 32K.

>   n specifies the number of buffers of the appropriate size to be allocated.

>   Note
>   If you specify VSAMHIPERSPACE, VSAMBUFFERS must also be specified. Moreover, for each size requested for hiperspace buffers, you must also specify buffers in VSAMBUFFERS.

> VSAMRPL

>   Value | n
>   Default | The number specified or defaulted for sys-parm VSAMDS multiplied by the number of threads defined.

>   1. If a VSAM LSR pool is established using the VSAMBUFFERS sysparm, the VSAMRPL value is used for the STRNO parameter of the VSAM BLDVRP macro when building the local shared resource pool, that is, it specifies the maximum number of requests concurrently active for all data sets sharing the LSR pool. If this value is exceeded, VSAM denies additional requests.

>   2. It specifies the initial number of VSAM RPLs in the Com-plete VSAM RPL pool. If neccessary during processing, this pool will be expanded dynamically by the same number of RPLs.

>      n must be numeric.

> VTAMAPPL

>   Value | name
>   Default | VTAMAPPL=COMPLETE

>   Specifies the name that Com-plete is to use as the application ID with VTAM.

>   For more information concerning VTAM definitions, see Software Interfaces.

> VTAMBUFFER

>   Value | n
>   Default | VTAMBUFFER=3584

>   Specifies the size of the VTAM RECEIVE ANY buffer.

>   Note that n should be set to a value equal to or greater than the size of the largest incoming data. The minimum size is 128 and the maximum is 32767 bytes. If an incoming RU length exceeds the specified buffer size, the message ZVT4010 is logged and the RU is ignored. If the buffer size is too large, storage is wasted.

> VTAMGENERIC

>   Value | name
>   Default | None

>   Specifies the name used by Com-plete to identify itself to VTAM as a generic resource. It is used in Parallel Sysplex installations to achieve system-independence and workload-balancing. For more details and restrictions of generic resource names refer to the section on VTAM interface in Software Interfaces.

> VTAMPASSWORD

>   Value | password
>   Default | None

>   Specifies the password to be used when the VTAM ACB is opened.

> VTAM-PERSIST (not supported on z/VSE)

>   Value | YES|NO
>   Default | NO

>   Specifies whether Com-plete is to handle VTAM sessions as persistent. Support for persistent sessions was first introduced in Com-plete 6.5.

>   With VTAM-PERSIST=YES, sessions are not terminated when Com-plete terminates (either normally through an EOJ command or abnormally), and are recovered automatically when a Com-plete with the same VTAMAPPL name starts again (provided each connection has not been terminated otherwise in the meantime). The scope of session persistence (singlenode or multinode) can be set in the VTAM APPL definition, parameter PERSIST=SINGLE/MULTI.

>   Com-plete uses MVS Sysplex Services for managing persistent sessions (even for singlenode), therefore sysparm XCF-STRUCTURE must refer to a valid Coupling Facility list structure for VTAM-PERSIST=YES to function.

>   Persistent sessions are most useful when used together with APPLICATION-RECOVERY=YES and applications capable of recovery such as Natural (version 4.2.2 or higher).

> VTAMSIMLQ

>   Value | YES|NO
>   Default | VTAMSIMLQ=YES

>   Specifies whether or not the SIMLOGON performed for each LU to be acquired is queued. For more information, see the description of the SIMLOGON in the IBM VTAM Macro Language Reference documentation.

>   VTAMSIMLQ=YES indicates that the SIMLOGON done for each acquired LU is to be queued.

>   VTAMSIMLQ=NO indicates that the SIMLOGON is not to be queued.

> VTAMSIMLREL

>   Value | YES|NO
>   Default | VTAMSIMLREL=YES

>   Specifies whether or not the SIMLOGON performed for each LU to be acquired will include OPTCD=RELREQ. This OPTCD causes VTAM to ask the current owner (if any) to release the LU.

>   VTAMSIMLREL=YES indicates that the SIMLOGON for each acquired LU will include OPTCD=RELREQ. If YES is indicated, the VTAMSIMLO startup option must be YES.

>   VTAMSIMLREL=NO indicates that the SIMLOGON for each acquired LU will not include the OPTCD=RELREQ.

> VTAMSTART

>   Value | YES|NO
>   Default | VTAMSTART=YES

>   Specifies whether or not VTAM processing is to begin when Com-plete is started. (VTAM can be stopped or started using the Com-plete operator commands VTAM START and VTAM STOP.)

>   VTAMSTART=YES indicates that VTAM processing will begin when Com-plete is started.

>   VTAMSTART=NO indicates that VTAM processing will not begin when Com-plete is started.

> WLM-SUBSYSTEM-TYPE

>   Value | Character string of 4 bytes or less
>   Default | none

>   Specifies the name of a subsystem type that Com-plete should use to identify itself to the z/OS Workload Manager (WLM). See the section Workload Manager (WLM) for details. It is recommended to leave the parameter unspecified if WLM is not to be used for managing transactions running in Com-plete; this saves resources and increases the performance.

>   #### Example:

>       WLM-SUBSYSTEM-TYPE=COMP

> WTOBUFFERS

>   Value | n|(n,BELOW)|(n,ANY)
>   Default | WTOBUFFERS=0

>   Specifies the number of messages written by Com-plete to the operators console that are to be retained in storage. These messages can be displayed by the MO function of UUTIL (subfunction CM).

>   Note
>   Each buffer requires approximately 140 bytes of storage. Buffers will be allocated above the line. To allocate buffers below the line, use the notation (n,BELOW).

> XCF-STRUCTURE (not supported on z/VSE)

>   Value | Name (string of 1-16 characters)
>   Default | none

>   Name of the XCF list structure Com-plete is to use for managing persistent sessions etc..