Identifies the DC/UCF system being added, modified, deleted, displayed, or punched. Dc/ucf-version-number must be an integer in the range 1 through 9,999. All systems 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 CV's. For more information about cloning CV's, see the CA IDMS System Operations Guide.
Specifies the name (nodename) by which the DC/UCF system 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 you specify after the ADD SYSTEM statement.
The default is SYSTnnnn where nnnn is the value specified as dc-ucf-version in the ADD SYSTEM statement.
Note: System-name is the name of the DC/UCF system you name in the CA IDMS Security DDL CREATE RESOURCE SYSTEM statement. For more information about CA IDMS central security, see the CA IDMS Security Administration Guide.
Specifies the amount of storage, in fullwords, available to the system for processing abends in the event of a task control element (TCE) stack overflow (for example, as a result of a recursive abend).
The STACKSIZE value will be used instead of this value when it is larger.
Abend-storage-size must be an integer in the range 0 through 32,767. The default is 200.
Note: Abend storage is a single-threaded resource.
Specifies whether the system writes a snap dump to the log when an external request unit terminates abnormally.
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.
Count must be an integer in the range 1 through 32,767.
Directs the system not to accumulate area locks until it can acquire all areas needed by a database transaction.
OFF is the default.
Defines a limit on the number of times the system continues trying to gain access to all areas without accumulating area locks.
Count must be an integer in the range 1 through 32,767.
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. You should specify the default of FOREVER unless experience shows that a transaction is not gaining access to areas as needed.
FOREVER is the default.
OFF RETRY FOREVER is the default when you omit the AREA ACQUISITION THRESHOLD parameter from the SYSTEM statement.
For z/OS and z/VSE operating systems only, specifies the number of subtasks to be attached by the system at runtime to detect abnormally terminated batch external request units.
Check-user-task-count must be an integer in the range 0 through 255.
Specify a value equal to the number of CA IDMS batch jobs that execute concurrently in the DC/UCF system.
0, the default, directs the system not to use the check-user mechanism to detect abends.
Specifies the amount of storage, in 1K bytes, to be reserved in the primary storage pool for use by tasks that are already executing.
Storage-cushion-size must be an integer in the range 0 through 16,383. The default is 0.
Note: For more information about relocatable storage, see Storage Pools.
Identifies the DC/UCF system to the CA IDMS SVC. Additionally, if a SYSCTL file is defined, the value specified by the CVNUMBER parameter is written to the SYSCTL file at system startup.
Cvnumber must be an integer in the range 0 through 255. The default is 0.
Note: For more information about the SYSCTL file, see the CA IDMS System Operations Guide.
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.
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.
Cwa-size must be a positive integer in the range 0 through 2,147,483,647; the default is 0.
Specifies the amount of time, in wall clock seconds, that elapses before the system searches for deadlocked tasks.
Deadlock-check-interval must be an integer in the range 0 through 1,200 and must be:
The default is 5.
Specifies the number of debug message buffers to be used by the DEBUG task.
Specifies the number of debug message buffers to be used by the DEBUG task. If this parameter is omitted then the default number of debug message buffers is 5. Increasing the debug message buffers above the default of 5 will increase the amount of storage needed to process the DEBUG task messages. The value specified can be in a range of 5 through 30.
Specifies the number of message buffers 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 needed to execute the debugger.
Limits: 5 - 30
Default: 5 (buffers)
For z/OS systems only, specifies operator-message description codes to be passed to the DESC parameter for write-to-operator (WTO) macros issued by the system.
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.
Clears any previously established operator-message description codes.
Indicates if CA IDMS should automatically tune the DPE count value using execution statistics.
Turns off automatic tuning of DPE count.
Turns on automatic tuning of DPE count.
Default: OFF
Specifies the number of deadlock prevention elements (DPEs) to allocate at system startup.
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.
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.
Directs the system to write a memory dump for all system abend codes (that is, 39nn). In most cases, a dump is not necessary because the abend code itself provides sufficient information to determine the cause of the abend.
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 specify neither DUMP nor NODUMP in the SYSTEM statement.
Note: The DUMP/NODUMP specification does not affect task or external request abend requests issued from DML programs.
Specifies the amount of storage to allocate for the external event control block (ECB) list.
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.
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.
Specifies the base year to be used by EVAL when doing built-in functions DATEDIFF and DATEOFF.
Specifies the EVAL base year when doing built-in functions DATEDIFF and DATEOFF to determine the century associated with the requested date. If this parameter is omitted then 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. The value specified can be in a range of 1 through 99.
Indicates whether century values are to be validated by EVAL when processing built-in functions that accept 4-digit years, such as GOODDATEX.
Indicates that EVAL is to validate century values.
OFF indicates that EVAL is not to validation century values.
The default for new systems is OFF
Specifies the highest century value that EVAL is to consider valid when processing built-in functions that accept 4-digit years, such as GOODDATEX.
Specifies the high century to be used by EVAL when doing built-in functions GOODDATEX century validation.
If this parameter is omitted then the default high century is 20.
The value specified can be in a range of 1 through 99. This parameter has no effect if the setting for EVAL CENTURY VALIDATION is OFF.
Specifies the lowest century value that EVAL is to consider valid when processing built-in functions that accept 4-digit years, such as GOODDATEX
Specifies the low century to be used by EVAL when doing built-in functions GOODDATEX century validation.
If this parameter is omitted then the default low century is 19.
The value specified can be in a range of 1 through 99. This parameter has no effect if the setting for EVAL CENTURY VALIDATION is OFF.
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.
Note: For more information about external user sessions, see External User Sessions.
Specifies the external wait time in wall-clock seconds. External-wait-time must be an integer in the range 0 through 32,767. The default is 600.
Directs the system not to terminate external request units based on an external wait time. FORever and NO are synonyms and can be used interchangeably.
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.
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.
Specifies the inactive interval in wall-clock seconds.
Inactive-wait-time must be an integer in the range 1 through 32,767.
Directs the system not to terminate tasks or external user sessions based on an inactive interval.
OFF is the default when you omit the INACTIVE INTERVAL parameter from the SYSTEM statement.
Specifies the amount of time the system permits an external request unit to wait for a resource before abnormally terminating the request unit.
Important: 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.
Specifies the internal wait time in wall-clock seconds. Internal-wait-time must be an integer in the range 1 through 32,767. The default is 1,800.
Directs the system not to terminate request units based on an internal wait time. FOREVER and NO are synonyms and can be used interchangeably.
Directs the system to write BGIN and ENDJ checkpoints to the journal file for run units that perform no updates (that is, for retrieval run units). JOURNAL RETRIEVAL is the default.
Note: 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.
Directs the system not to write BGIN and ENDJ checkpoints for retrieval run units.
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.
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 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.
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.
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.
Note: 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.
Limits the number of database I/O operations (that is, 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.
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
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.
Indicates the specified limit applies to all tasks defined to the system either during system generation or at runtime.
Indicates the specified limit applies to all tasks associated with external request units (that is, ERUS tasks).
Controls the enforcement of limits on task resource usage. You can code one LIMIT parameter for each system.
Note: Limits on task resource usage can be enforced only if task statistics are being collected.
Indicates the enforcement specification applies to all tasks defined to the system either during system generation or at runtime.
Indicates the enforcement specification applies to all tasks associated with external request units (that is, ERUS tasks).
Directs the system to build a resource limit block (RLB) for each active task and to enforce limits on task resource usage.
Directs the system to build an RLB for each active task but not to enforce limits on task resource usage. Because the system builds RLBs, users can enable the enforcement of limits at runtime by means of the DCMT VARY LIMITS command.
Directs the system not to build RLBs. Because no RLBs are built, limits on task resource usage are not enforced.
OFF is the default when you omit the LIMITS FOR ONLINE parameter from the SYSTEM statement.
Identifies the default load list to be used by the system when searching for programs.
Directs the system to use the predefined SYSLOAD load list.
SYSLOAD is the default when you omit the LOADLIST parameter from the SYSTEM statement.
Directs the system to use a user-defined load list. Load-list-name must be the name of a load list defined by means of the system generation LOADLIST statement.
Defines the system log file.
Directs the system log to the log area (DDLDCLOG) of the data dictionary.
Directs the system log to one or two sequential files and identifies the first (or only) file.
Specifies the z/OS or z/VM ddname of the first log file. The default is CDMSLOGA.
Specifies the z/VSE filename of the first log file. The default is CDMSLGA.
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 file and opens the second log file, if one 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.
Identifies the second of two sequential log files.
Specifies the z/OS or z/VM ddname of the second log file.
Specifies the z/VSE filename of the second log file.
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.
For z/VSE systems only, specifies the device type of the sequential file to which the log is directed.
Note: For more information about how the system logs errors, see the CA IDMS System Operations Guide.
Note: For more information about system currency, see Currency.
Specifies the number of EREs to allocate at system startup. External-request-unit-count must be an integer in the range 0 through 255. The default is 0.
Specify a value equal to the total number of external request units you allow to execute concurrently in the DC/UCF system plus 10% - 20% of the total number of 3270-type terminals defined to the DC/UCF system.
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 chapter "System Performance" in the System Operations Guide.
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.
Specifies the message retention period in days.
Limit: 0 - 255 (0 is synonymous with 1; 255 is synonymous with FOREVER)
Default 7 (days)
Directs the system not to delete reports based on a retention period. FOREVER and OFF are synonyms and can be used interchangeably.
Specifies whether the system allows the same LE process/enclave to be used for multiple COBOL programs in the same task.
Specifies that the same process/enclave can be used for multiple programs.
Specifies that the same process/enclave cannot be used for multiple programs. This is the default.
Specifies if the same user-ID can be signed on to multiple interactive terminals simultaneously.
Specifies the same user-ID can be signed on to multiple interactive terminals simultaneously.
Notes:
Specifies the same user-ID cannot be signed on to multiple interactive terminals simultaneously.
NO is the default.
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.
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.
Directs the system to mark the program for new copy automatically and to reattempt to load the program.
Specifies options that control commit behavior. These options apply only to commit operations in which the database session remains active.
Specifies that a COMT journal record should be written.
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.
Specifies options that control rollback behavior. These options apply only to rollback operations in which the database session remains active.
Specifies that following a rollback, the current local transaction ID should be assigned to the next transaction associated with the database session.
Specifies that following a rollback, a new local transaction ID should be assigned to the next transaction associated with the database session.
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:
For z/OS and z/VSE systems only, specifies whether the system is to invoke operating system services (that is, PGRLSE for z/OS systems, RELPAG for z/VSE systems) to release real page frames associated with virtual pages that are no longer required and whose contents do not need to be saved.
Directs the system to use the page release feature. Real page frames 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.
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.
Specifies the control key to use to print the contents of a terminal screen.
Identifies a program attention key. N must be the integer 1, 2, or 3.
Identifies a program function key. N must be an integer in the range 1 through 24.
Indicates that no system-wide print-screen key is defined.
OFF is the default when you omit the PRINT KEY parameter from the SYSTEM statement.
Specifies the frequency with which the system is to write checkpoints for each report as the report is printed.
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.
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.
Specifies the printer form feed options.
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.
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
A form feed is inserted, if needed.
SUPpress
The report never starts with a form feed, i.e., 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 transmitted to an SCS printer.
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.
Specifies the line length to be used for all reports generated within a DC/UCF system.
Limits: 0 - 255
If this parameter is 0 (zero) or not specified, the line length used is based on the printer terminal’s device type. Because specifying a non-zero value impacts all DC/UCF reports, exercise caution if you set this parameter.
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.
Note: For more information about the 24-bit program pool, see Program Pools.
Enables the use of storage protection. Programs for which the system generation PROGRAM statement specifies PROTECT will run with the alternate protect key defined by the STORAGE KEY parameter.
Disables the use of storage protection. Programs will run with the primary protect key regardless of the PROGRAM statement PROTECT/NOPROTECT specification.
NOPROTECT is the default when you specify neither PROTECT nor NOPROTECT in the SYSTEM statement.
Specifies whether the system is to write after images of queue records to the journal file.
Important! 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.
Directs the system to write only before images of queue records to the journal file. A rollforward operation cannot rebuild queues when you specify QUEUE JOURNAL BEFORE in the system definition.
Directs the system to write both before and after images of queue records to the journal file.
ALL and YES are synonyms and are used interchangeably.
ALL is the default when you omit the QUEUE JOURNAL parameter from the SYSTEM statement.
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 whose retention period has expired are deleted automatically when the system is next started.
Specifies the number of days that queues are to be retained.
Limits: 0 - 255 (255 is synonymous with FOREVER; 0 is synonymous with 1)
Directs the system not to delete queues based on a retention period. FOREVER and OFF are synonyms that you can use interchangeably.
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.
Specifies the quiesce wait time for a task is the same as the task's stall interval. This is the default.
Specifies the quiesce wait interval in wall-clock seconds. quiesce-wait-time must be an integer in the range 1 through 32,767.
Directs the system not to terminate tasks based on quiesce wait time.
Specifies tasks do not wait for quiesce operations to terminate and instead, receive an error indicating an area is unavailable. For navigational DML requests, this results in an error-status value of 'xx66'.
Specifies the number of resource control elements (RCEs) to allocate at system startup.
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.
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.
Indicates if CA IDMS should automatically tune the RCE count value using execution statistics.
Turns off automatic tuning of RCE count.
Turns on automatic tuning of RCE count.
Default: OFF
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.
Directs the system to immediately cancel the task. NOT ALLOWED is the default.
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.
Directs the system to permit a task to wait indefinitely.
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 will execute under the DC/UCF system. The default is 0.
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.
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.
Directs the system always to write relocatable storage to the scratch area across a pseudo-converse. YES is the default.
Directs the system never to write relocatable storage to the scratch area across a pseudo-converse.
Note: For more information about storage pool 0, see Storage Pools.
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.
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.
Directs the system not to delete reports based on a retention period.
FOREVER and OFF are synonyms and can be used interchangeably.
Controls the resource-timeout mechanism.
Specifies the amount of time the system is to wait for input from the terminal operator before invoking the resource timeout program.
Specifies the resource timeout interval in wall-clock seconds.
Resource-timeout-interval must be an integer in the range 0 through 32,767.
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.
Specifies the program the system invokes to handle the resources owned by an inactive terminal when the resource timeout interval expires.
Resource-timeout-prog-name must be the name of a program included in the system definition. The default is RHDCBYE. RHDCBYE deletes all resources owned by the terminal and returns control to the system.
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.
Specifies whether the system is to maintain locks automatically for records in areas accessed in shared retrieval usage mode.
Directs the system to maintain locks for records in areas accessed in shared retrieval usage mode. Records accessed by retrieval run units are prevented from being updated. However, the maintenance of the additional locks adds overhead.
Directs the system not to maintain locks for records in areas accessed in shared retrieval usage mode.
NOLOCK is the default when you omit the RETRIEVAL parameter from the SYSTEM statement.
Specifies the number of resource link elements (RLEs) to allocate at system startup.
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.
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.
Note: For more information about RLEs, see Resource Management.
Indicates if CA IDMS should automatically tune the RLE count value using execution statistics.
Turns off automatic tuning of RLE count.
Turns on automatic tuning of RLE count.
Default: OFF
For z/OS systems only, specifies operator-message routing codes to pass to the ROUTCDE parameter for write-to-operator (WTO) macros issued by the system.
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.
Clears any previously established operator-message routing codes.
Specifies the maximum amount of time the system is to permit a task to execute without returning control to the system.
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.
Directs the system not to check for runaway tasks.
Specifies the number of predefined run units the system is to initiate at startup to service requests for:
Run-unit-count must be an integer in the range 0 through 32,767. The default is 1.
Predefines the specified number of run units for load area processing in the default dictionary.
Predefines the specified number of run units for message area processing.
Predefines the specified number of run units for queue area processing.
Predefines the specified number of run units for security processing on system-level resources.
Predefines the specified number of run units for signon processing in the user catalog.
Predefines the specified number of run units for destination processing.
Specifies whether or not scratch information resides in memory.
Specifies that the scratch information is not memory-resident.
Specifies that the scratch information is memory-resident.
Controls where memory for the scratch information is allocated with the following options:
Determines the storage location. The storage 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.
Notes:
Note: For more information about storage protection, see Storage Protection.
Specifies the primary scratch allocation size.
Specifies the size of the initial storage area acquired 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).
Specifies the system default value. If the DMCL contains a scratch area definition, the default value is the number of pages in the area multiplied by the page size. If no scratch area is defined in the DMCL, the system default value is 1 MB.
Specifies the secondary scratch allocation size.
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).
Specifies the system default value. The size of the secondary allocation is equal to the size of the primary allocation.
Specifies the maximum scratch allocation size.
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 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).
Specifies the system default value. If the DMCL contains a scratch area definition, the default value is the number of pages in the area 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.
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 allocated to all active tasks.
Enables the writing of a system snap dump. This is the default for the ADD SYSTEM statement.
Disables the writing of a system snap dump.
Note: For more information about Snap and System dump reading, see the CA IDMS Navigational DML Programming Guide.
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.
Enables the writing of a system photo snap. This is the default for the ADD SYSTEM statement.
Disables the writing of a system photo snap.
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 allocated to the task being snapped.
Enables the writing of a task snap dump. This is the default for the ADD SYSTEM statement.
Disables the writing of a task snap dump.
Controls the inclusion of trace information in task snaps.
Includes formatted trace information for all tasks in a task snap.
Includes no trace information in a task snap.
Includes only trace information for the task for which the snap is being issued.
Default: ON
Limits the number of trace entries reported in a task snap.
Specifies the maximum number of trace entries that are reported in a task snap.
Limit: 0–32767
Default: 1000
Note: A value of 0 is the same as specifying OFF.
Indicates that there is no limit to the number of trace entries included in a task snap.
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.
Enables the writing of a task photo snap. This is the default for the ADD SYSTEM statement.
Disables the writing of a task photo snap.
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.
Note: 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).
Controls the collection and writing of statistics.
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.
Note: If the system is to write statistics 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 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 Guide.
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.
Directs the system not to write statistics based on a time interval.
OFF is the default when you omit the STATISTICS INTERVAL parameter from the SYSTEM statement.
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 will continue to be every 24 hours from the local time originally used as input. This means that after a time change, such as to daylight savings time, the statistics will run an hour later or earlier in local time. If you want to reset the statistics so that they run at the original local time, you must either restart your system, where the interval will be 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.
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
Specifies the day frequency at which system statistics and histograms are to be written and reset.
Range: 1–999
Default: 1
Directs the system not to perform statistics interval roll.
Directs the system to collect by-line histograms.
Directs the system not to collect by-line histograms.
NOLINE is the default when you specify neither LINE nor NOLINE in the STATISTICS parameter of the SYSTEM statement.
Note: Regardless of the LINE/NOLINE specification, system statistics for lines are always collected.
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.
Directs the system to collect by-task histograms.
COLLECT is the default when you specify neither COLLECT nor WRITE in the STATISTICS TASK parameter of the SYSTEM statement.
Directs the system to collect and write task statistics for each task.
Note: 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.
Directs the system to maintain separate task CPU-time statistics for system-mode time and user-mode time.
Directs the system to maintain one statistic representing total task execution time.
NOUSER is the default when you specify neither USER nor NOUSER in the STATISTICS TASK parameter of the SYSTEM statement.
Enables the collection of transaction statistics.
Note: The collection of transaction statistics must be enabled if CA ADS dialog statistics are collected.
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.
Directs the system not to collect by-task histograms or task statistics.
Note: Regardless of the TASK/NOTASK specification, system statistics for tasks are always collected.
Specifies the value of the alternate protect key to use for programs running with storage protection enabled:
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, and only the PSW key is changed during program execution, thereby, 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.
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.
Specifies whether a CA IDMS SVC is used for communication between 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 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.
Defines the system control (SYSCTL) file batch programs requesting database services from the DC/UCF system will use.
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 will route 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 identified by the NODENAME parameter.
DEFault
Indicates that a program using the SYSCTL file will access the named database only if neither the IDMSOPTI module nor the program name a database.
DEFAULT is the default when you specify neither DEFAULT nor ALWAYS in the SYSCTL DBNAME parameter of the SYSTEM statement.
ALWays
Indicates that programs using the SYSCTL file will always access the named database.
NULl
Specifies the SYSCTL file will not contain a database name.
NODename is
Identifies the nodename (system-name of SYSTEM ID parameter) to which the system will route requests from programs using the SYSCTL file.
node-name
Specifies a node name to be included in the SYSCTL file.
Node-name must be the name of a DC/UCF system 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 neither the IDMSOPTI module nor the program name a node.
DEFAULT is the default when you specify neither DEFAULT nor 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 will not contain a node name.
NO
Specifies that programs requesting services from the DC/UCF system will not use a SYSCTL file.
NO is the default when you omit the SYSCTL parameter from the SYSTEM statement.
Estimates the maximum number of database locks that will be 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.
Indicates if CA IDMS should automatically tune the SYSLOCKS parameter value using execution statistics.
Turns off automatic tuning of SYSLOCKS.
Turns on automatic tuning of SYSLOCKS.
Default: OFF
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.
Specifies system trace options.
Specifies the size of the system trace table in kilobytes (KB) or megabytes (MB).
Limit: 0–9999
Default: 4 MB
Note: Two copies of the system trace table are allocated on all z/OS systems.
Specifies the size of the adjunct trace table in kilobytes (KB) or megabytes (MB).
Limit: 0–9999
Default: 0
Controls whether trace information is saved for future reporting.
Enables saving of trace information.
■Adjunct trace table entries are saved if an adjunct trace table has been allocated. If no adjunct trace table has been allocated system trace table entries are saved.
■Trace entries are written to the trace area if one is defined in the run time DMCL, or they are written to the log area if one is defined. If neither area is defined no trace information is saved.
Disables saving of trace information.
Default: OFF
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.
Specifies the number of null program definition elements (PDEs) to make available to the system.
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.
Specifies the number of null PDEs to include in secondary allocations of null PDEs.
When all existing null PDEs, if any, 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. The default is 0. If the secondary count equals 0, the system will terminate 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.
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 not included in the FOR parameter are ineligible for automatic definition.
For example, FOR (DIALOGS MAPS TABLES) disallows automatic definition of subschemas.
Note: 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.
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.
Allows automatic definition of dialogs created by the CA ADS dialog compiler (ADSC or ADSOBCOM).
Allows automatic definition of maps created by the CA IDMS Mapping Facility.
Allows automatic definition of subschemas created by the subschema compiler.
Allows automatic definition of edit and code tables created by the IDD DD compiler.
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.
Specifies the default transaction sharing option for all tasks within the system.
Specifies transaction sharing is disabled for all tasks in the system.
Specifies transaction sharing is enabled for all tasks in the system.
Specifies whether the system is to maintain locks automatically for records in areas accessed in protected update usage mode.
Directs the system to maintain locks for records in areas 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 in conjunction with the RETRIEVAL LOCK parameter.
Directs the system not to maintain locks for records in areas accessed in protected update usage mode.
NOLOCK is the default when you omit the UPDATE parameter from the SYSTEM statement.
Determines the size of the buffer the user trace facility uses at runtime.
Specifies the number of words 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.
Specifies the system will allocate a minimum user trace buffer of 253 words (or approximately 10 entries) when the user trace facility is enabled for a terminal.
OFF is the default when you omit the USERTRACE parameter from the SYSTEM statement.
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.
Note: An XA PROGRAM pool may be added, or it's size changed, at system generation time. At runtime, the DCMT VARY SYSGEN REFRESH command with the PROGRAM POOL option makes the change effective.
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.
Note: An XA REENTRANT pool may be added, or it's size changed, at system generation time. At runtime, the DCMT VARY SYSGEN REFRESH command with the PROGRAM POOL option makes the change effective.
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.
Note: An XA STORAGE pool may be added, or it's size changed, at system generation time. At runtime, the DCMT VARY SYSGEN REFRESH command with the STORAGE POOL option makes the change effective.
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).
In DISPLAY/PUNCH statements only, directs the system generation compiler to display or punch the definition of the current system.
|
Copyright © 2014 CA.
All rights reserved.
|
|