SYSTEM Statement Parameters Information

This topic discusses the parameters for the SYSTEM statement.
If not specified, the operating system defaults to the following information:
  • SYStem
    dc/ucf-version-number
    Identifies the DC/UCF system being added, modified, deleted, displayed, or punched.
    Limits:
    1 through 9,999.
    All systems that are defined in the data dictionary with the system generation compiler are automatically assigned the name DCSYSTEM.
    Note:
    The DBA may elect to reserve consecutive SYSTEM (and CV) numbers for use in cloning CVs. For more information about cloning CVs, see "Administrating CA IDMS System Operations."
  • SYSTem
    ID is
    system-name
    Specifies the DC/UCF system node name that is known to other nodes in the DC/UCF communications network.
    System-name
    must be a one- through eight- character name that is unique throughout the DC/UCF communications network and must be the first parameter that you specify after the ADD SYSTEM statement.
    Default:
    SYST
    nnnn
    where
    nnnn
    is the value that is specified as
    dc-ucf-version
    in the ADD SYSTEM statement.
    System-name
    is the name of the DC/UCF system you name in the CA IDMS Security DDL CREATE RESOURCE SYSTEM statement.
  • ABEnd storage is
    abend-storage-size
    Specifies the amount of storage, in full words, available to the system for processing abends of a task control element (TCE) stack overflow (for example, as a result of a recursive abend).
    The STACKSIZE value is used instead of this value when it is larger.
    Limits:
    0 through 32,767
    Default:
    200
    Abend storage is a single-threaded resource.
  • ABRu SNAp/NOSnap
    Specifies whether the system writes a snap dump to the log when an external request unit terminates abnormally.
  • AREa acquisition THReshold is
    count
    Specifies the point at which, during ready processing, the system begins to accumulate area locks for a database transaction. This value only applies if the system is readying multiple areas at one time.
    Limits:
    1 through 32,767.
    • OFF
      Directs the system not to accumulate area locks until it can acquire all areas that are needed by a database transaction.
      Default:
      OFF
    • RETry
      count
      Defines a limit on the number of times the system continues trying to gain access to all areas without accumulating area locks.
      Limits:
      1 through 32,767.
    • RETry FORever
      Directs the system to continue to try to gain access to all needed areas until it successfully acquires all areas or until operating system resource and time limits are exceeded. If transactions are not gaining access to areas as needed, you should specify the default of FOREVER .
      Default:
      FOREVER
      OFF RETRY FOREVER is the default when you omit the AREA ACQUISITION THRESHOLD parameter from the SYSTEM statement.
  • CHKuser tasks IS
    check-user-task-count
    Specifies the number of subtasks to be attached by the system at runtime to detect abnormally terminated batch external request units, for only z/OS and z/VSE operating systems, .
    Limits:
    0 through 255.
    Specify a value equal to the number of CA IDMS batch jobs that execute concurrently in the DC/UCF system.
    Default:
    0. Directs the system not to use the check-user mechanism to detect abends.
  • CUShion is
    storage-cushion-size
    Specifies amount of free storage, in 1K bytes, to be reserved in the System XA storage pool to preserve space in the storage pool by warning of possible short-on-storage conditions.
    Limits:
    0 through 16,383.
    Default:
    0.
  • CVNumber is
    cvnumber
    Identifies the DC/UCF system to the CA IDMS SVC. Also, if a SYSCTL file is defined, the value that is specified by the CVNUMBER parameter is written to the SYSCTL file at system startup.
    Limits:
    0 through 255.
    Up to 256 DC/UCF systems can execute concurrently and independently in a single machine. Systems executing concurrently must be defined with unique CVNUMBER values, even if the systems use different SVCs.
    z/VM systems
    : A DC/UCF system running in a CMS virtual machine must be defined with CVNUMBER IS 0.
    Default:
    0.
  • CWA size is
    cwa-size
    Specifies the size, in bytes, of the common work area (CWA). The CWA is a block of shared user storage that is available to all user tasks. A program accesses the CWA by issuing a GET STORAGE request with a storage id of CWA. Use of the CWA facilitates communication among tasks.
    Limits:
    0 through 2,147,483,647
    Default:
    0.
  • DEAdlock DETection INTerval is
    deadlock-check-interval
    Specifies the amount of time, in wall clock seconds, that elapses before the system searches for deadlocked tasks.
    Limits:
    0 through 1,200 and must be:
    • Less than the value that is specified in the INACTIVE INTERVAL parameter of the SYSTEM statement
    • Greater than or equal to the value that is specified in the TICKER INTERVAL parameter of the SYSTEM statement
    Default:
    5.
  • DEBug MESsage BUFfers is
    Specifies the number of debug message buffers to be used by the DEBUG task.
    • number-of-buffers
      Specifies the number of debug message buffers to be used by the DEBUG task. If this parameter is omitted, the default number of debug message buffers is five. Increasing the debug message buffers above five increases the amount of storage that is necessary to process the DEBUG task messages.
      Limits:
      5 through 30.
  • DEBug MESsage BUFfers is buffer-count
    Specifies the number of message buffers that are used by the CA IDMS online debugger.
    Increasing the number of message buffers enables the debugger to display more symbols and list more information. However, the larger the value you specify, the more storage is necessary to execute the debugger.
    Limits:
    5 - 30
    Default:
    5 (buffers)
  • DEScription codes =
    For z/OS systems only, specifies operator-message description codes to be passed to the DESC parameter for write-to-operator (WTO) macros that are issued by the system.
    • (
      Os-description-code
      )
      Specifies one or more operator-message description codes, as described in the applicable operating system supervisor services and macro instructions.
      Os-description-code
      must be an integer in the range 1 through 16. Multiple description codes must be separated by blanks or commas.
    • 0
      Clears any previously established operator-message description codes.
  • DPE AUTotune is
    Indicates if CA IDMS should automatically tune the DPE count value using execution statistics.
    • OFF
      Turns off automatic tuning of DPE count.
    • ON
      Turns on automatic tuning of DPE count.
    Default:
    OFF
  • DPE count is
    Specifies the number of deadlock prevention elements (DPEs) to allocate at system startup.
    • dpe-count
      Directs the system to allocate the specified number of DPEs at startup.
      Dpe-count
      must be an integer in the range 1 through 32,767.
    • DEFault/0
      Directs the system generation compiler to calculate the number of DPEs to allocate. DEFAULT and 0 are synonyms and can be used interchangeably.
      DEFAULT is the default when you omit the DPE COUNT parameter from the SYSTEM statement.
  • DUMp
    Directs the system to write a memory dump for all system abend codes (39
    nn
    ). Usually, a dump is not necessary because the abend code itself provides sufficient information to determine the cause of the abend.
  • DYNamic EXPansion
    Specifies whether the storage pool should be dynamically expanded if remaining free space is insufficient for a storage request.
    • ON
    Indicates that the storage pool will be expanded up to four times.
    • OFF
    Indicates that the storage pool will not be expanded.
  • ECB list is
    Specifies the amount of storage to allocate for the external event control block (ECB) list.
    • ecb-list-size
      Specifies the size, in words, of the amount of storage to allocate for the ECB list.
      Ecb-list-size
      must be an integer in the range 0 through 32,767.
    • DEFault/0
      Directs the system generation compiler to calculate the size of the ECB list. The compiler calculates the size to equal two times the number of TCEs.
      DEFAULT and 0 are synonyms and can be used interchangeably.
      DEFAULT is the default when you omit the DPE COUNT parameter from the SYSTEM statement.
  • ERUS FETCH PROTECT is
    Indicates whether the system allocates External Run Unit Storage (ERE/ESE) in a storage sub-pool that is or is not fetch protected.
    • ON
      Allocate ERE/ESE in a storage sub-pool that is fetch protected.
    • OFF
      Allocates ERE/ESE in a storage sub-pool that is not fetch protected.
      Default:
      ON
  • EVAl BASe YEAr is
    Specifies the base year to be used by EVAL when doing built-in functions DATEDIFF and DATEOFF.
    • base-year
      Specifies the EVAL base year when doing built-in functions DATEDIFF and DATEOFF to determine the century that is associated with the requested date. If this parameter is omitted, the default base year is 68 meaning that years 69 and greater are in the 20th century, and years 68 and lower are in the 21th century.
      Limits:
      1 through 99.
  • E
    VAl CENtury VALidation is
    Indicates whether century values are to be validated by EVAL when processing built-in functions that accept four-digit years, such as GOODDATEX.
    • ON
      Indicates that EVAL is to validate century values.
    • OFF
      OFF indicates that EVAL is not to validation century values.
      Default:
      OFF
  • EVAl HIGh CENtury is
    Specifies the highest century value that EVAL is to consider valid when processing built-in functions that accept four-digit years, such as GOODDATEX.
    • high-century
      Specifies the high century to be used by EVAL when doing built-in functions GOODDATEX century validation.
      If this parameter is omitted, the default high century is 20.
      Limits:
      1 through 99. This parameter has no effect if the setting for EVAL CENTURY VALIDATION is OFF.
  • EVAl LOW CENtury is
    Specifies the lowest century value that EVAL is to consider valid when processing built-in functions that accept four-digit years, such as GOODDATEX
    • low-century
      Specifies the low century to be used by EVAL when doing built-in functions GOODDATEX century validation.
      If this parameter is omitted, the default low century is 19.
      Limits:
      1 through 99. This parameter has no effect if the setting for EVAL CENTURY VALIDATION is OFF.
  • EXTernal wait is
    Specifies the amount of time the system is to wait for the next request to be issued within an external request unit before abnormally terminating the task. For more information about external user sessions, see External User Sessions.
  • GENeration identification is
    generation-id
    Specifies a unique identifier for the system. The identifier is included in the system options table, which is built in the DC/UCF region/partition during system startup. In a memory dump, the identifier appears at the beginning of the system options table.
    Generation-id
    must be a one- through eight-character alphanumeric value.
  • INActive interval is
    Specifies the amount of time the system permits an online task or an external user session to wait for a resource before abnormally terminating the task or session.
    • inactive-wait-time
      Specifies the inactive interval in wall-clock seconds.
      Limits:
      1 through 32,767.
    • OFF
      Directs the system not to terminate tasks or external user sessions that are based on an inactive interval.
      OFF is the default when you omit the INACTIVE INTERVAL parameter from the SYSTEM statement.
  • INTernal wait is
    Specifies the amount of time the system permits an external request unit to wait for a resource before abnormally terminating the request unit.
    The INTERNAL WAIT parameter is not functional. Its function is performed by the INACTIVE INTERVAL parameter of the TASK statement for task RHDCNP3S. You can specify wait times for individual batch or CICS run-units by defining TASK statements where the task name is the first batch program that establishes communication with the CV for the run-unit or the CICS task code.
  • JOUrnal retrieval
    Directs the system to write BGIN and ENDJ checkpoints to the journal file for run units that perform no updates (for retrieval run units). JOURNAL RETRIEVAL is the default.
    For the purposes of this parameter, a run unit that readies an area in an update usage mode but that does not update the database is considered a retrieval run unit.
  • NOJournal retrieval
    Directs the system not to write BGIN and ENDJ checkpoints for retrieval run units.
  • JOUrnal FRAgment INTerval is
    fragment-interval-number
    Specifies the maximum number of journal blocks to write to the journal file before the system writes a dummy segment (DSEG) record to the journal file.
    Fragment-interval
    must be an integer in the range 100 through 32,767.
    0, the default, turns off the journal fragment interval.
  • JOUrnal TRAnsaction LEVel is
    transaction-level-number
    Specifies the number of active transactions that must be running in a DC/UCF system to defer the writing of a journal block.
    Transaction-level-number
    must be an integer in the range 1 through 100.
    If the number of active transactions is less than the value that is specified, the system performs journal I/O each time a transaction checkpoint is written to the journal buffer page.
    0, the default, directs the system to write a journal buffer to the journal block each time a transaction checkpoint is taken or when the journal buffer is full.
  • LIMit for tasks is
    limit
    Defines limits for task resource usage.
    Limit
    specifies the limit for each resource.
    0, the default, directs the system not to limit task usage of the named resource.
    You can code two limit parameters for each resource: one for online tasks and one for ERUS tasks. Specify only one resource in each LIMIT parameter.
    • CALl
      Limits the number of system service calls (for example, #GETSTG, #LOAD, or OBTAIN CALC) a task can issue. When you specify CALL,
      limit
      must be an integer in the range 0 through 2,147,483,647.
      For performance purposes, external limits are only checked after every 100 calls. Therefore, if the SYSTEM statement specifies CALL LIMIT FOR EXTERNAL TASK IS 150, a batch program could issue 200 DML calls before the system determines that the limit is exceeded.
    • DBIo
      Limits the number of database I/O operations (reads and writes) that are performed for a task. When you specify DBIO,
      limit
      must be an integer in the range 0 through 2,147,483,647.
    • LOCk
      Limits the number of record locks that a transaction can concurrently hold. When LOCK is specified,
      limit-n
      must be an integer in the range 0 through 2,147,483,647.
      Note:
      For more information about record locks, see Database Locks.
    • STOrage
      Limits the amount of storage that a task holds at one time. The limit is expressed in 1K bytes.
      When you specify STORAGE,
      limit
      must be an integer in the range 0 through 16,383.
    • ONLine
      Indicates that the specified limitt applies to all tasks defined to the system either during system generation or at runtime.
    • EXTernal
      Indicates that the specified limit applies to all tasks associated with external request units (ERUS tasks
  • LIMits for ... are
    Controls the enforcement of limits on task resource usage. You can code one LIMIT parameter for each system.
    Limits on task resource usage can be enforced only if task statistics are being collected.
  • LOAdlist is
    Identifies the default load list to be used by the system when searching for programs.
    • SYSLOAD
      Directs the system to use the predefined SYSLOAD load list.
      SYSLOAD is the default when you omit the LOADLIST parameter from the SYSTEM statement.
    • load-list-name
      Directs the system to use a user-defined load list.
      Load-list-name
      must be the name of a load list that is defined by means of the system generation LOADLIST statement.
  • LOG
    Defines the system log file.
    • DATabase
      Directs the system log to the log area (DDLDCLOG) of the data dictionary.
    • FILE1
      Directs the system log to one or two sequential files and identifies the first (or only) file.
    • ddname-1
      Specifies the z/OS or z/VM ddname of the first log file. The default is CDMSLOGA.
    • filename-1
      Specifies the z/VSE filename of the first log file. The default is CDMSLGA.
    • COUNT1
      record-count-1
      Specifies the maximum number of records to write to the first log file. When the specified number of records is reached, the system closes the first file and opens a second log file that is defined. If a second log file is not defined, the system reopens the first log file.
      Record-count-1
      can be any positive integer.
      The COUNT1 parameter is required when the log is being directed to sequential disk files.
    • FILE2
      Identifies the second of two sequential log files.
    • ddname-2
      Specifies the z/OS or z/VM ddname of the second log file.
    • filename-2
      Specifies the z/VSE filename of the second log file.
    • COUNT2
      record-count-2
      Specifies the maximum number of records to write to the alternate log file. When the specified number of records is reached, the system closes the alternate log file and opens the first log file.
      Record-count-2
      can be any positive integer.
      The COUNT2 parameter is required when the log is directed to sequential disk files.
    • TYPe
      device-type
      For z/VSE systems only, specifies the device type of the sequential file to which the log is directed. For more information about how the system logs errors, see the
      CA IDMS System Operations section
      .
  • MAXimum ERUs is
    external-request-unit-count
    Specifies the number of EREs to allocate at system startup.
    External-request-unit-count
    must be an integer in the range 0 through 1000.
    Default:
    0
    Specify a value equal to the total number of external request units that you allow to execute concurrently in the DC/UCF system, plus 10 percent to 20 percent of the total number of 3270-type terminals that are defined to the DC/UCF system.
    When up to 255 EREs are requested, a corresponding TCE/DCE pair is allocated for each one during startup. If more than 255 ERES are requested, a maximum of 255 TCE/DCE pairs are allocated for these external request units.
  • MAXimum TASks is
    task-count
    Specifies the maximum number of application and transient system tasks that can be active at a given time. The system generation compiler uses this value when calculating the number of TCEs to allocate at system startup.
    Task-count
    must be an integer in the range 0 through 255. The default is 0.
    Note:
    For more information about Task-Count, see Task Resource Usage, and also the section "System Performance" in the
    System Operations section
    .
  • MESsage RETention is
    Specifies the amount of time the system is to retain a message that was created by the SEND command in the queue area. Messages that exceed the specified retention period are deleted automatically at system startup.
    • message-retention-period
      Specifies the message retention period in days.
      Limits: 0 - 255 (0 is synonymous with 1; 255 is synonymous with FOREVER)
      Default 7 (days
    • FORever|OFF
      Directs the system not to delete reports that are based on a retention period. FOREVER and OFF are synonyms and can be used interchangeably.
  • MULtiple ENClave is
    Specifies whether the system allows the same LE process/enclave to be used for multiple COBOL programs in the same task
    • ON
      Specifies that the same process/enclave can be used for multiple programs.
    • OFF
      Specifies that the same process/enclave cannot be used for multiple programs.
      Default:
      OFF
  • MULtiple SIGnon is
    Specifies if the same user-ID can be signed on to multiple interactive terminals simultaneously.
    • YES
      Specifies the same user-ID can be signed on to multiple interactive terminals simultaneously.
    • NO
      Specifies the same user-ID cannot be signed on to multiple interactive terminals simultaneously.
      Default:
      NO
  • NEW COPy is
    Specifies the action the system is to take when a load request for a program in the load area (DDLDCLOD) of the data dictionary names a program that is deleted from its program pool.
    • MANual
      Directs the system not to attempt to load the program until the user issues a DCMT VARY PROGRAM NEW COPY command. The system disables the program and terminates the task or run unit that issued the load request.
      MANUAL is the default when you omit the NEW COPY parameter from the SYSTEM statement.
    • AUTomatic
      Directs the system to mark the program for new copy automatically and to reattempt to load the program.
  • NODump
    Directs the system to write a memory dump only for system abend codes that do not provide sufficient information to determine the cause of the abend.
    NODUMP is the default when you do not specify DUMP or NODUMP in the SYSTEM statement. The DUMP/NODUMP specification does not affect task or external request abend requests issued from DML programs.
  • ON COMmit
    Specifies options that control commit behavior. These options apply only to commit operations in which the database session remains active.
    • WRIte COMT
      Specifies that a COMT journal record should be written.
    • WRIte ENDJ
      Specifies that an ENDJ journal record should be written.
      NEW ID
      Specifies that a new local transaction ID should be assigned to the next transaction associated with the database session.
      RETain ID
      Specifies that the existing local transaction ID should be assigned to the next transaction associated with the database session.
  • ON ROLlback continue
    Specifies options that control roll back behavior. These options apply only to roll back operations in which the database session remains active.
    • RETain ID
      Specifies that following a roll back, the current local transaction ID should be assigned to the next transaction associated with the database session.
    • NEW ID
      Specifies that following a roll back, a new local transaction ID should be assigned to the next transaction associated with the database session.
  • OPErating system is
    operating-system
    Identifies the host operating system under which the DC/UCF system is to run.
    Operating-system
    must be one of the following values:
Value
Operating System
CMS
z/VM
VSE
z/VSE
MVS
z/OS
If not specified, the operating system defaults to:
  • MVS
    for z/OS and z/VM systems
  • VSE
    for z/VSE systems
  • PAGe release is
    For z/OS and z/VSE systems only, specifies whether the system is to invoke operating system services (PGRLSE for z/OS systems, RELPAG for z/VSE systems) to release real page frames that are associated with virtual pages that are no longer required and which contents do not need to be saved.
    • YES
      Directs the system to use the page release feature. Real page frames that are associated with virtual pages that are no longer needed are available to other operating system tasks.
      z/VSE systems:
      When you specify YES, the operating system SUPVR macro must specify PAGEIN=
      n
      .
    • NO
      Directs the system not to use the page release feature. z/OS users should specify NO.
      NO is the default when you omit the PAGE RELEASE parameter from the SYSTEM statement.
  • PRInt KEY is
    Specifies the control key to use to print the contents of a terminal screen.
    • PA
      n
      Identifies a program attention key.
      N
      must be the integer 1, 2, or 3.
    • PF
      n
      Identifies a program function key.
      N
      must be an integer in the range 1 through 24.
    • OFF
      Indicates that no systemwide print-screen key is defined.
      OFF is the default when you omit the PRINT KEY parameter from the SYSTEM statement.
  • PRInter CHEckpoint is
    Specifies the frequency with which the system is to write checkpoints for each report as the report is printed.
    • page-count
      Directs the system to write printer checkpoints for all active reports. The system writes checkpoints for a given report every
      page-count
      pages. If printing is interrupted (for example, by a task or system abend), the system resumes printing the report at the last checkpoint.
      Page-count
      must be an integer in the range 0 through 32,767. A value of 0 is synonymous with OFF.
    • OFF
      Directs the system not to write printer checkpoints. The system resumes printing interrupted reports at the beginning of the file.
      OFF is the default when you omit the PRINTER CHECKPOINT parameter from the SYSTEM statement.
  • PRInter CONtrol is
    Specifies the printer form feed options.
    • SCS FORmfeed is
      Specifies the form feed sequence sent to SCS devices.
      FF-NL
      Specifies the form feed sequence is "FF" (form feed) followed by "NL" (new line). FF-NL is the default.
      FF
      Specifies the form feed sequence contains "FF" only.
    • ON REPort STArt
      Specifies what happens when a report starts printing.
      FORmfeed for NATive print is
      Specifies the form feed processing for native mode print reports.
      FORmfeed for NON-Native print is
      Specifies the form feed processing for non-native mode print reports.
      Parameters for the two FORmfeed options are:
      INSert
      If needed, a form feed is inserted.
      SUPpress
      The report never starts with a form feed. If the report starts with a form feed, it is removed.
      NO-Insert
      No change to the report contents is made.
      SCS CR-LF is
      Suppresses the Carriage Return/Line Feed sequence at the beginning of a report that is transmitted to an SCS printer.
    • ON REPort END
      Specifies what happens when a report finishes printing.
      FORmfeed for NATive print is
      Specifies the form feed processing for native mode print reports.
      FORmfeed for NON-Native print is
      Specifies the form feed processing for non-native mode print reports.
      Parameters for the two FORmfeed options are:
      • INSert
        A form feed is inserted.
      • NO-Insert
        No form feed is inserted.
  • OVErriding REPort LINe LENgth is report-line-length
    Specifies the line length to be used for all reports that are generated within a DC/UCF system.
    Limits:
    0 - 255
    If this parameter is zero or not specified, the line length that is used is based on the printer terminal device type. Because specifying a non-zero value impacts all DC/UCF reports, exercise caution if you set this parameter.
  • PROgram pool is
    program-pool-size
    Specifies the size, in 1K bytes, of the 24-bit program pool.
    Program-pool-size
    must be an integer in the range 4 through 16,383. The default is 50.
  • PROTect
    Enables the use of storage protection. Programs for which the system generation PROGRAM statement specifies PROTECT runs with the alternate protect key that is defined by the STORAGE KEY parameter.
  • NOProtect
    Disables the use of storage protection. Programs run with the primary protect key regardless of the PROGRAM statement PROTECT/NOPROTECT specification.
    Default:
    NOPROTECT is the default when you do not specify PROTECT or NOPROTECT in the SYSTEM statement.
  • QUEue JOUrnal
    Specifies whether the system is to write after images of queue records to the journal file.
    If you code the QUEUE JOURNAL parameter immediately following the RUNUNITS parameter, the system generation compiler interprets the keyword QUEUE as a continuation of the RUNUNITS parameter.
  • QUEue RETention is
    Specifies the default time period that the system retains queues that are created dynamically. This value is used only if no retention period is specified when a queue is created. Queues for expired retention periods are deleted automatically the next time the system is started.
    • queue-retention-period
      Specifies the number of days that queues are retained.
      Limits:
      0 - 255 (255 is synonymous with FOREVER; 0 is synonymous with 1)
    • FORever/OFF
      Directs the system not to delete queues that are based on a retention period. FOREVER and OFF are synonyms that you can use interchangeably.
  • QUIesce wait is
    Specifies if the system permits a task to wait for a quiesce operation to terminate; and if waiting is permitted the amount of time the task waits before it is abnormally terminated.
    • STAll interval
      Specifies that the quiesce wait time for a task is the same as the task stall interval. STAll interval is the default.
    • quiesce-wait-time
      Specifies the quiesce wait interval in wall-clock seconds.
      quiesce-wait-time
      must be an integer in the range 1 through 32,767.
    • FORever
      Directs the system not to terminate tasks that are based on quiesce wait time.
    • NOWait
      Specifies that tasks do not wait for quiesce operations to terminate, and instead receive an error indicating an area is unavailable. For navigational DML requests, an error-status value of 'xx66' occurs.
  • RCE count is
    Specifies the number of resource control elements (RCEs) to allocate at system startup.
    • rce-count
      Directs the system to allocate the specified number of RCEs at startup.
      Rce-count
      must be an integer in the range 0 through 32,767.
    • DEFault/0
      Directs the system generation compiler to calculate the number of RCEs to allocate. DEFAULT and 0 are synonyms and are used interchangeably.
      DEFAULT is the default when you omit the RCE COUNT parameter from the SYSTEM statement.
      Note:
      For more information about RCEs, see Resource Management.
  • RCE AUTotune is
    Indicates if CA IDMS should automatically tune the RCE count value using execution statistics.
    • OFF
      Turns off automatic tuning of RCE count.
    • ON
      Turns on automatic tuning of RCE count.
      Default:
      OFF
  • RECovery wait is
    Specifies the amount of time the system permits a task to wait for a resource to be recovered by a failed data sharing group member before the task is abnormally terminated.
    • NOT ALLowed
      Directs the system to cancel the task immediately.
      Default:
      NOT ALLOWED.
    • recovery-wait-time
      Specifies the recovery wait time in seconds.
      Recovery-wait-time
      must be an integer in the range 1 through 32,767. A value of zero is treated as if NOT ALLOWED was specified.
    • FORever
      Directs the system to permit a task to wait indefinitely.
  • REEntrant pool is
    reentrant-pool-size
    Specifies the size, in 1K bytes, of the 24-bit reentrant pool.
    Reentrant-pool-size
    must be an integer in the range 0 through 16,383 and must be large enough to hold the largest reentrant program that executes under the DC/UCF system. The default is 0.
  • RELocatable threshold is
    Specifies the point at which the system is to write relocatable storage in storage pool 0 to the scratch area (DDLDCSCR) of the data dictionary.
    • threshold-percentage
      Directs the system to write relocatable storage to the scratch area across a pseudo-converse when the amount of used space in the storage pool exceeds the specified threshold.
      Threshold-percentage
      must be an integer in the range 0 through 100. A value of 0 is synonymous with YES. A value of 100 is synonymous with NO.
    • YES
      Directs the system always to write relocatable storage to the scratch area across a pseudo-converse. YES is the default.
    • NO
      Directs the system never to write relocatable storage to the scratch area across a pseudo-converse.
  • REPort retention is
    Specifies the amount of time the system is to retain a report in the queue area. Reports that exceed the specified retention period are deleted automatically at system startup.
    • report-retention-period
      Specifies the report retention period in days.
      Report-retention-period
      must be an integer in the range 0 through 255. The default is 7. A value of 255 is synonymous with FOREVER.
    • FORever/OFF
      Directs the system not to delete reports that are based on a retention period.
      FOREVER and OFF are synonyms and can be used interchangeably.
  • RESource timeout
    Controls the resource-timeout mechanism.
    • INTerval is
      Specifies the amount of time the system is to wait for input from the terminal operator before invoking the resource timeout program.
    • resource-timeout-interval
      Specifies the resource timeout interval in wall-clock seconds.
      Resource-timeout-interval
      must be an integer in the range 0 through 32,767.
    • FORever/OFF
      Disables the resource-timeout mechanism.
      FOREVER and OFF are synonyms and can be used interchangeably.
      FOREVER is the default when you omit the RESOURCE TIMEOUT INTERVAL parameter from the SYSTEM statement.
    • PROgram is resource-timeout-prog-name
      Specifies the program that the system invokes to handle the resources that are owned by an inactive terminal when the resource timeout interval expires.
      Resource-timeout-prog-name
      must be the name of a program that is included in the system definition. The default is RHDCBYE. RHDCBYE deletes all resources that are owned by the terminal and returns control to the system.
    • Version version-num
      Qualifies the named program with a version number.
      Version-num
      must be an integer in the range 1 through 9,999. The default is 1.
      Note:
      For more information about the resource-timeout mechanism, see Abend Detection and Timed Functions.
  • RETrieval
    Specifies whether the system is to maintain locks automatically for records in areas that are accessed in shared retrieval usage mode.
    • LOCk
      Directs the system to maintain locks for records in areas that are accessed in shared retrieval usage mode. records that are accessed by retrieval run units are prevented from being updated. However, the maintenance of the additional locks adds overhead.
    • NOLock
      Directs the system not to maintain locks for records in areas that are accessed in shared retrieval usage mode.
      NOLOCK is the default when you omit the RETRIEVAL parameter from the SYSTEM statement.
  • RLE count is
    Specifies the number of resource link elements (RLEs) to allocate at system startup.
    • rle-count
      Directs the system to allocate the specified number of RLEs at startup.
      Rle-count
      must be an integer in the range 0 through 32,767.
    • DEFault/0
      Directs the system generation compiler to calculate the number of RLEs to allocate. DEFAULT and 0 are synonyms and are used interchangeably.
      DEFAULT is the default when you omit the RLE COUNT parameter from the SYSTEM statement.
  • RLE AUTotune is
    Indicates if CA IDMS should automatically tune the RLE count value using execution statistics.
    • OFF
      Turns off automatic tuning of RLE count.
    • ON
      Turns on automatic tuning of RLE count.
    Default:
    OFF
  • ROUte codes =
    For z/OS systems only, specifies operator-message routing codes to pass to the ROUTCDE parameter for write-to-operator (WTO) macros that are issued by the system.
    • (Os-routing-code)
      Specifies one or more operator-message routing codes, as described in the applicable operating system supervisor services and macro instructions.
      Os-routing-code
      must be an integer in the range 1 through 16. You must separate multiple routing codes by blanks or commas.
    • 0
      Clears any previously established operator-message routing codes.
  • RUNaway interval is
    Specifies the maximum amount of time the system is to permit a task to execute without returning control to the system.
    • runaway-task-time
      Specifies the runaway interval in wall-clock seconds.
      Runaway-task-time
      must be an integer in the range 1 through 32,767. The default is 10.
    • OFF
      Directs the system not to check for runaway tasks.
  • RUNUnits for ... =
    run-unit-count
    Specifies the number of predefined run units the system is to initiate at startup to service requests for:
    • Load area processing in the system default dictionary
    • Message area processing
    • Queue area processing
    • Security checking for system-level resources such as tasks, queues, and load modules
    • Signon processing in the user catalog
    • Destination processing in the system default dictionary
    Run-unit-count
    must be an integer in the range 0 through 32,767. The default is 1.
    • LOAder
      Predefines the specified number of run units for load area processing in the default dictionary.
    • MSGdict
      Predefines the specified number of run units for message area processing.
    • QUEue
      Predefines the specified number of run units for queue area processing.
    • SECurity
      Predefines the specified number of run units for security processing on system-level resources.
    • SIGnon
      Predefines the specified number of run units for signon processing in the user catalog.
    • SYStem/dest
      Predefines the specified number of run units for destination processing.
  • SCRatch in STOrage is
    Specifies whether scratch information resides in memory.
    • NO
      Specifies that the scratch information is not memory-resident.
    • YES
      Specifies that the scratch information is memory-resident.
  • LOCation
    Controls where memory for the scratch information is allocated with the following options:
    • ANY|XA|64-bit
      Determines the storage location. The storage that is needed for scratch processing is allocated directly from the operating system and not from the CA IDMS storage pools.
      ANY
      Acquires 64-bit storage, if possible. If the request to allocate 64-bit storage fails, XA storage is acquired.
      XA
      Acquires 31-bit storage.
      64-bit
      Acquires 64-bit storage. If the request to allocate 64-bit storage fails, no attempt to acquire XA storage is done.
      • SCRATCH IN XA STORAGE IS YES is synonymous to SCRATCH IN STORAGE IS YES LOCATION XA.
      • Usage of 64-bit storage is controlled by the MEMLIMIT parameter of the JOB or EXEC JCL statement.
  • PRImary extent is
    Specifies the primary scratch allocation size.
    • prim-size-with-unit
      Specifies the size of the initial storage area that is required for scratch use. Enter a number in the range 1-32767 followed by a unit of KB (Kilobyte: 2**10), MB (Megabyte: 2**20), GB (Gigabyte: 2**30), TB (Terabyte: 2**40), or PB (Petabyte: 2**50).
    • DEFAULT
      Specifies the system default value. If the DMCL contains a scratch area definition, the default value is the number of pages in the area that is multiplied by the page size. If no scratch area is defined in the DMCL, the system default value is 1 MB.
  • SECondary extent is
    Specifies the secondary scratch allocation size.
    • sec-size-with-unit
      Specifies the amount of additional storage acquired when all existing scratch storage is in use. Enter a number in the range 1-32767 followed by a unit of KB (Kilobyte: 2**10), MB (Megabyte: 2**20), GB (Gigabyte: 2**30), TB (Terabyte: 2**40), or PB (Petabyte: 2**50).
    • DEFAULT
      Specifies the system default value. The size of the secondary allocation is equal to the size of the primary allocation.
  • LIMit is
    Specifies the maximum scratch allocation size.
    • limit-with-unit
      Specifies the maximum amount of scratch storage. The system continues to allocate more storage for scratch processing until the sum of all allocations reaches the value that is specified by
      limit-with-unit
      . Enter a number in the range 1-32767 followed by a unit of KB (Kilobyte: 2**10), MB (Megabyte: 2**20), GB (Gigabyte: 2**30), TB (Terabyte: 2**40), or PB (Petabyte: 2**50).
    • DEFAULT
      Specifies the system default value. If the DMCL contains a scratch area definition, the default value is the number of pages in the area that is multiplied by the page size. If no scratch area is defined in the DMCL, the system default value is the size of the primary allocation plus 99 times the size of the secondary allocation.
  • SNAp SYStem is
    Specifies whether to write a system snap dump to the DC/UCF log file. A system snap dump writes a formatted display of the resources that are allocated to all active tasks.
    • ON
      Enables the writing of a system snap dump.
      Default:
      ON
      is the default for the ADD SYSTEM statement.
    • OFF
      Disables the writing of a system snap dump.
  • SNAp SYStem PHOto is
    Specifies whether to write a system photo snap to the DC/UCF log file. A system photo snap provides a summary of resources for all active tasks.
    • ON
      Enables the writing of a system photo snap.
      Default:
      ON
      is the default for the ADD SYSTEM statement.
    • OFF
      Disables the writing of a system photo snap.
  • SNAp TASk is
    Specifies whether to write a task snap dump to the DC/UCF log file. A task snap dump writes a formatted display of the resources that are allocated to the task being snapped.
    • ON
      Enables the writing of a task snap dump.
      Default:
      ON
      is the default for the ADD SYSTEM statement.
    • OFF
      Disables the writing of a task snap dump.
    • TRAce is ON|OFF|TASk
      Controls the inclusion of trace information in task snaps.
      • ON
        Includes formatted trace information for all tasks in a task snap.
      • OFF
        Includes no trace information in a task snap.
      • TASk
        Includes only trace information for the task for which the snap is being issued.
            Default:
      ON
      • LIMit is snap-trace-limit|OFF
        Limits the number of trace entries reported in a task snap.
      • snap-trace-limit
        Specifies the maximum number of trace entries that are reported in a task snap.
        Limits:
        0 - 32767
        Default:
        1000.  A value of zero is the same as specifying OFF.
      • OFF
        Indicates that there is no limit to the number of trace entries that are included in a task snap.
  • SNAp TASk PHOto is
    Specifies whether to write a task photo snap to the DC/UCF log file. A task photo snap provides a summary of the resources for the task being snapped.
    • ON
      Enables the writing of a task photo snap.
      Default:
      ON
      is the default for the ADD SYSTEM statement.
    • OFF
      Disables the writing of a task photo snap.
  • SQL ROW LIMit is
    Specifies the maximum number of rows that can be read or updated by a single SQL statement. Includes rows that are processed internally, for example by a sort or an aggregate function, not only the number of rows updated or returned to the user. The calls to a table procedure or procedure are also counted toward the limit. SQL ROW LIMit can be used to limit database I/O activity.
    Limits:
    0 through 2,147,483,647
    Default:
    0. A value of zero indicates that there is no limit.
  • STAcksize is
    tce-stack-size
    Specifies the size, in words, of the work storage stack in each task control element (TCE).
    Tce-stack-size
    must be an integer in the range 0 through 32,767. The default is 1200.
    Usage of the stack increases when the system is extended with applications that run in system mode. Examples of such applications are numbered exits, database procedures, TCP/IP generic listeners (defined with MODE IS SYSTEM), and SQL-invoked routines (defined with SYSTEM MODE).
  • STATistics
    Controls the collection and writing of statistics.
    • INTerval
      Specifies the frequency with which system statistics and histograms are written to the log file.
      Regardless of the STATISTICS INTERVAL specification, system statistics and histograms are written to the log at normal system shutdown and upon explicit request by means of a DCMT WRITE STATISTICS command.
      If the system is to write statistics that are based on a time interval, the internal statistics task, RHDCSTTS, and the program it invokes, RHDCSTTS, must both be accessible to the DC/UCF system. If these programs are secured through CA IDMS central security, you should assign them to a category and should grant public access to that category. If these programs are secured through an external security package, you should grant public access to them. For more information about the CA IDMS central security facility, see the
      CA IDMS Security Administration section
      .
    • statistics-interval
      Specifies the statistics interval in wall-clock seconds.
      Statistics-interval
      must be an integer in the range 0 through 32,767. A value of 0 is synonymous with OFF.
    • OFF
      Directs the system not to write statistics that are based on a time interval.
      OFF is the default when you omit the STATISTICS INTERVAL parameter from the SYSTEM statement.
    • ROLl
      Directs the system to write system statistics and histograms to the log file and roll them out at specified time and day interval.
      If you change the local time while Statistics Interval Roll is active, the interval continues to be every 24 hours from the local time originally used as input. For example, after a time change, such as to daylight savings time, the statistics run an hour later or earlier in local time. If you want to reset the statistics to run at the original local time, you must either restart your system, where the interval is reset based on the values in the SYSGEN, or use the DCMT VARY STATISTICS ROLL TIME HH:MM command to reset the interval to the local time.
      • TIMe is interval-roll-time
        Specifies the time of day in twenty-four-hour format (HH:MM) at which statistics are to be written and reset. The time is interpreted as local time.
        Default:
        24:00
      • FREquency is day-frequency
        Specifies the day frequency at which system statistics and histograms are to be written and reset.
        Range:
        1 - 999
        Default:
        1
    • NOROLl
      Directs the system not to perform statistics interval roll.
    • LINe
      Directs the system to collect by-line histograms.
    • NOLine
      Directs the system not to collect by-line histograms.
      NOLINE is the default when you do not specify LINE or NOLINE in the STATISTICS parameter of the SYSTEM statement.
      Regardless of the LINE/NOLINE specification, system statistics for lines are always collected.
    • TASk
      Directs the system to collect by-task histograms or task statistics.
      TASK is the default when you specify neither TASK nor NOTASK in the STATISTICS parameter of the SYSTEM statement.
    • COLlect
      Directs the system to collect by-task histograms.
      COLLECT is the default when you do not specify COLLECT or WRITE in the STATISTICS TASK parameter of the SYSTEM statement.
    • WRIte
      Directs the system to collect and write task statistics for each task.
      Task statistics must be collected to implement limits on task resource usage.
      z/VSE systems
      : Task statistics are collected only if the IDMS$SVC macro is assembled with DC=YES.
    • USEr
      Directs the system to maintain separate task CPU-time statistics for system-mode time and user-mode time.
    • NOUser
      Directs the system to maintain one statistic representing total task execution time.
      NOUSER is the default when you do not specify USER or NOUSER in the STATISTICS TASK parameter of the SYSTEM statement.
    • TRAnsaction
      Enables the collection of transaction statistics.
      The collection of transaction statistics must be enabled if CA ADS dialog statistics are collected.
    • NOTransaction
      Disables the collection of transaction statistics.
      NOTRANSACTION is the default when you specify neither TRANSACTION nor NOTRANSACTION in the STATISTICS TASK parameter of the SYSTEM statement.
    • NOTask
      Directs the system not to collect by-task histograms or task statistics.
      Regardless of the TASK/NOTASK specification, system statistics for tasks are always collected.
  • STOrage KEY is
    storage-protect-key
    Specifies the value of the alternate protect key to use for programs running with storage protection enabled:
    • For z/OS, z/VSE, and z/VM systems
      ,
      storage-protect-key
      must be an integer in the range 1 through 15
    The default value for
    storage-protect-key
    is 9.
    When key 9, the default, is used as the alternate protect key, the CA IDMS system and, the operating system are protected from user written code. However, non-reentrant programs and user storage are not protected from each other. Alternate protect key 9 is explicitly intended for the high-performance requirements of the production CV. When key 9 is used as the alternate protect key, all user storage and non-reentrant programs are swapped into key 9 at startup. Only the PSW key is changed during program execution, providing negligible CPU overhead compared to running without storage protection.
    The storage pools must be defined in such a manner that all forms of user-oriented storage are segregated from the system storage. In other words, define both an XA and a non-XA storage pool for user storage types. Storage types: user, user-kept, shared, and shared-kept, can be together, but they must be defined to secondary storage pools and must be isolated from any secondary pools that contain database or terminal type storage. Program development should not be done with key 9 as the alternate protect key.
  • STOrage POOl is
    storage-pool-size
    Specifies the size, in 1K bytes, of storage pool 0 (the primary storage pool).
    Storage-pool-size
    must be an integer in the range 1 through 16,383. The default is 50.
  • SVC is
    Specifies whether a CA IDMS SVC is used for communication between the the DC/UCF system and programs executing in other regions/partitions.
  • svc-number
    Identifies the CA IDMS SVC.
    Svc-number
    must be an integer in the range 1 through 255.
    If a SYSCTL file is defined, the value that is specified by the SVC parameter is written to the SYSCTL file at system startup.
    NO
    Specifies the system does not use an SVC for communication.
    NO is the default when you omit the SVC parameter from the SYSTEM statement.
    z/VM systems
    : The IDMSVSVC module, and not the CA IDMS SVC, is used for communication under z/VM. The SYSTEM statement, therefore, must specify SVC IS NO
  • SYSctl is
    Defines the system control (SYSCTL) file batch programs requesting database services from which the DC/UCF system uses.
  • ddname
    Specifies the z/OS or z/VM ddname of the SYSCTL file.
  • filename
    Specifies the z/VSE filename of the SYSCTL file.
    Note:
    To change the filename for z/VSE, the filename must also be included in an idmsopti module.
  • SYSctl
    Specifies SYSCTL as the default value for the z/OS ddname, or the z/VSE filename of the SYSCTL file.
  • DBName is
    Identifies the database or data dictionary to which the system routes requests from programs using the SYSCTL file.
  • NODename is
    Identifies the node name (
    system-name
    (
    system-name
    of SYSTEM ID parameter) to which the system routes requests from programs using the SYSCTL file.
  • database-name
    Specifies a database name included in the SYSCTL file.
    Database-name
    must be the name of a database accessible by the system being defined or by the system that is identifiedby the NODENAME parameter.
    DEFault
    Indicates that a program using the SYSCTL file accesses the named database, only if the IDMSOPTI module or the program do not name a database.
    DEFAULT is the default when you do not specify DEFAULT or ALWAYS in the SYSCTL DBNAME parameter of the SYSTEM statement.
    ALWays
    Indicates that programs using the SYSCTL file always accesses the named database.
    NULl
    Specifies the SYSCTL file does not contain a database name.
  • node-name
    Specifies a node name to be included in the SYSCTL file.
    Node-name
    must be the name of a DC/UCF system that is defined in the CA IDMS communications network.
    DEFault
    Indicates that database requests from programs using the SYSCTL file are directed to the named node only if the IDMSOPTI module or the program do not name a node.
    DEFAULT is the default when you do not specify DEFAULT or ALWAYS in the SYSCTL NODENAME parameter of the SYSTEM statement.
    ALWays
    Indicates that database requests from programs using the SYSCTL file are always directed to the named node.
    NULl
    Specifies the SYSCTL file does not contain a node name.
    NO
    NO is the default when you omit the SYSCTL parameter from the SYSTEM statement.
  • SYSLocks is
    system-lock-count
    Estimates the maximum number of database locks that are held at one time within the system.
    System-lock-count
    must be an integer in the range 1 through 2,147,483,647.
    The default is 40,000.
  • SYSLocks AUTotune is
    Indicates if CA IDMS should automatically tune the SYSLOCKS parameter value using execution statistics.
    OFF
    Turns off automatic tuning of SYSLOCKS.
    ON
    Turns on automatic tuning of SYSLOCKS.
  • SYSTrace
    Enables or disables the system trace facility.
    ON
    Enables the system trace facility.
    OFF
    Disables the system trace facility. Typically, OFF is specified in production environments to eliminate storage and processing overhead.
    OFF is the default when you omit the SYSTRACE parameter from the SYSTEM statement.
  • TRAce
    Specifies system trace options.
  • TABle SIZe table-size KB|MB
    Specifies the size of the system trace table in kilobytes (KB) or megabytes (MB).
    Limits
    : 0 - 9999
    Default
    : 4 MB
  • ADJunct table SIZe adjunct-size KB|MB
    Specifies the size of the adjunct trace table in kilobytes (KB) or megabytes (MB).
    Limits:
    0 - 9999
    Default
    : 0
  • SAVe ON|OFF
    Controls whether trace information is saved for future reporting.
    ON
    Enables saving of trace information.
    If an adjunct trace table is allocated, adjunct trace table entries are saved. If no adjunct trace table is allocated, system trace table entries are saved.
    If one is defined in the run time DMCL or written to a defined log area, trace entries are written to the trace area. If neither area is defined, no trace information is saved.
    OFF
    Default
    : OFF
  • TICker interval is
    time-check-interval
    Specifies the frequency, in wall-clock seconds, with which the system is to check timed functions (such as the runaway interval).
    Time-check-interval
    must be an integer in the range 1 through 32,767. The default is 1.
    z/VSE systems with BTAM terminals should accept the default value of 1. The recommended value for all other systems is 5.
  • UNDefined program count is
    Specifies the number of null program definition elements (PDEs) to make available to the system.
    • primary count
      Specifies the number of null PDEs to include in the program definition table at system startup.
      Primary-count must be an integer in the range 0 through 32,767. The default is 0.
    • secondary-count
      Specifies the number of null PDEs to include in secondary allocations of null PDEs.
      If there are existing null PDEs that are occupied, the system allocates additional null PDEs from Storage pool 0. Secondary-count must be an integer in the range 0 through 32,767. If the secondary count equals 0, the system terminates tasks requesting null PDEs when all the null PDEs allocated at startup are occupied. The comma separating the primary and secondary count values is optional.
      Default:
      0
    • FOR
      Identifies the types of programs that are eligible for automatic definition. Enclose the program type specification in parentheses. Multiple types must be separated by blanks or commas. Program types that are not included in the FOR parameter are ineligible for automatic definition.
      For example, FOR (DIALOGS MAPS TABLES) disallows automatic definition of subschemas.
      At runtime, the DC/UCF system enforces restrictions on automatic definition only for programs that reside in the load area of a data dictionary and subschemas that reside in a load library. Dialogs, maps, and tables that reside in a load library are always eligible for automatic definition.
    • ACCess MODule
      Allows automatic definition of access modules. An access module is an executable form of the SQL statements that programs issue when using the CA IDMS SQL.
    • DIAlogs
      Allows automatic definition of dialogs that are created by the CA ADS dialog compiler (ADSC or ADSOBCOM).
    • MAPs
      Allows automatic definition of maps that are created by the CA IDMS Mapping Facility.
    • SUBschemas
      Allows automatic definition of subschemas that are created by the subschema compiler.
    • TABles
      Allows automatic definition of edit and code tables that are created by the IDD DD compiler.
    • ALL
      Allows automatic definition of CA ADS dialogs, maps, edit, and code tables, and subschemas.
      ALL is the default when you omit the FOR parameter from the UNDEFINED PROGRAM COUNT parameter in the SYSTEM statement.
  • TRAnsaction SHAring is
    Specifies the default transaction sharing option for all tasks within the system.
    • OFF
      Specifies transaction sharing is disabled for all tasks in the system.
    • ON
      Specifies transaction sharing is enabled for all tasks in the system.
  • UPDate
    Specifies whether the system is to maintain locks automatically for records in areas that are accessed in protected update usage mode.
    • LOCk
      Directs the system to maintain locks for records in areas that are accessed in protected update usage mode. Records updated are not accessed by retrieval run units. However, the maintenance of the additional locks adds overhead.
      Typically, LOCK is specified with the RETRIEVAL LOCK parameter.
    • NOLock
      Directs the system not to maintain locks for records in areas that are accessed in protected update usage mode.
      NOLOCK is the default when you omit the UPDATE parameter from the SYSTEM statement.
  • USErtrace
    Determines the size of the buffer the user trace facility uses at runtime.
    • ON entries = user-trace-buffer-entry-count
      Specifies the number of words that are allocated to the user trace buffer when the user trace facility is enabled for a terminal. Each user trace entry requires approximately 25 words of storage.
      User-trace-buffer-entry-count
      must be an integer in the range 1 through 9,999.
    • OFF
      Specifies that the system allocates a minimum user trace buffer of 253 words (or approximately 10 entries) when the user trace facility is enabled for a terminal.
      Default:
      OFF, when you omit the USERTRACE parameter from the SYSTEM statement.
  • XA PROgram pool is
    xa-program-pool-size
    For systems supporting 31-bit addressing only, specifies the size, in 1K bytes, of the 31-bit program pool.
    Xa-program-pool-size
    must be an integer in the range 0 through 2,097,151. The default is 0.
    An XA PROGRAM pool may be added, or its size changed, at system generation time. At runtime, the DCMT VARY SYSGEN REFRESH command with the PROGRAM POOL option makes the change effective.
  • XA REEntrant pool is
    xa-reentrant-pool-size
    For systems supporting 31-bit addressing only, specifies the size, in 1K bytes, of the 31-bit reentrant pool.
    Xa-reentrant-pool-size
    must be an integer in the range 0 through 2,097,151. The default is 0.
    An XA REENTRANT pool may be added, or its size changed, at system generation time. At runtime, the DCMT VARY SYSGEN REFRESH command with the PROGRAM POOL option makes the change effective.
  • XA STOrage pool is
    xa-storage-pool-size
    For systems supporting 31-bit addressing only, specifies the size, in 1K bytes, of storage pool number 255 (31-bit storage pool). Storage pool 255 is used to allocate XA storage for database processing.
    XA-storage-pool-size
    must be an integer in the range 0 through 2,097,151. The default is 0.
    Use the XA STORAGE POOL statement to define storage pools 128 through 254. These storage pools are used to allocate XA storage for user applications.
    An XA STORAGE pool may be added, or its size changed, at system generation time. At runtime, the DCMT VARY SYSGEN REFRESH command with the STORAGE POOL option makes the change effective.
  • ALL
    In DISPLAY/PUNCH statements only, directs the system generation compiler to display or punch the entire system definition (that is, the system entity and all entities associated with the specified system).
  • URrent SYStem
    In DISPLAY/PUNCH statements only, directs the system generation compiler to display or punch the definition of the current system.