DLSYS - syncsort_scc_monitor - Latest

Syncsort™ Storage Management SCC DLimit Guide
Product type
Software
Portfolio
Integrate
Product family
Syncsort™ software
Product
Syncsort™ Storage Management > Syncsort™ SCC Monitor
Version
Latest
ft:locale
en-US
Product name
Syncsort Storage Management
ft:title
Syncsort™ Storage Management SCC DLimit Guide
Copyright
2021
First publish date
1991
ft:lastEdition
2025-12-05
ft:lastPublication
2025-12-05T05:06:29.654000
L1_Product_Gateway
Integrate
L2_Product_Segment
IBM Infrastructure
L3_Product_Brand
Precisely Syncsort
L4_Investment_Segment
Mainframe
L5_Product_Group
Mainframe Storage Optimization
L6_Product_Name
Syncsort Storage Management

The DLSYS command is used to set or change the defaults that affect the DLimit database currently in use. The DLSYS command changes the contents of the $CONTROL record in the current database to reflect the specified values. The DLSYS command operates on the current DLimit database, that is, the database that was activated when the START DSL command was issued to the DIF started task. If the DLSYS command is being run under control of program DLMAINT, the DLimit database is the database specified by the SET DATABASE control statement.

This command requires UPDATE authority to the DSL.$CONTROL resource in the FACILITY class.

DLSYS

  • AUTOCREATE(option)
  • FULL(WARN(percenttime))
  • LIST
  • LOG(options)
  • MODE(options)
  • SYSTEM

AUTOCREATE

Function: This is an optional parameter. The AUTOCREATE parameter allows new DLimit accounts to be created automatically if they do not already exist. If the DLimit rules set the DACCTn variables to a non-null value, a new account is automatically created in the DLimit database if AUTOCREATE(ACTIVE) is specified. The new account is not created unless the dataset being created or updated is successfully allocated.

If AUTOCREATE(INACTIVE) is specified, automatic creation of new accounts is prevented. In that case, accounts will not be created automatically, and space utilization values will only be updated if the rules set the DACCTn variables to an existing account. If AUTOCREATE(INACTIVE) is specified and the rules assign the dataset to an account that does not exist, an error message is not issued — the product ignores the request.

When a new account is created automatically as a result of AUTOCREATE(ACTIVE), the account values can be taken from a MODEL account, if one exists and is assigned to the new account with the SET MODEL rule statement. These values may be overridden by values set for the ACCT_ variables in the rules, once the DACCTn variables have been set. Any existing account can serve as a MODEL.

Default: AUTOCREATE(ACTIVE)

Format: AUTOCREATE( ACTIVE | INACTIVE )

FULL (WARN)

Function: This is an optional parameter. The FULL parameter can be used to establish a threshold for database record usage. If the database record usage crosses the specified threshold percentage, DLimit will issue a warning message. A time parameter can be specified to limit the number of warning messages — only one will be allowed in the specified time interval. The interval is specified in minutes.

Note: Interval values are in minutes.

For example, the following command sets a warning when the database reaches 90% full; only one message will be issued every 60 minutes:

DLSYS FULL(WARN(90 60))
Note: There is also a new message on the DLSYS LIST command to show the current full/warn values.

Default: None

Format: FULL(WARN( percentminutes ))

LIST

Function: This is an optional parameter. The LIST parameter indicates that the database settings are to be displayed after the command completes. If the LIST parameter is not specified, the values are not displayed.

Default: None

Format: LIST

LOG

Function: This is an optional parameter. The LOG parameter is used to generate trace/logging messages when account information is created or modified.

If an ACCOUNT name is also specified on the LOG request, the log messages will be limited to accounts that match the specified mask. For example, ACCOUNT(ABC*) can be used to limit trace/logging messages to accounts starting with ABC. If the ACCOUNT keyword parameter is not specified, all accounts will be traced.

Default: LOG(INACTIVE)

Format: LOG( ACTIVE | INACTIVE [ ACCOUNT( acct-mask ) ] )

MODE

Function: This is an optional parameter. The MODE parameter determines the type of action taken when a request for space causes an account to exceed its limit value. The limit value is specified for each account using the MAX parameter of the DLADD/DLALTER commands. The default is MODE(INACTIVE), which means that no action is taken when the space assigned to an account exceeds its limit. The MODE parameter specified for an account (via the DLADD/DLALTER commands) takes precedence over the system MODE value specified in the DLSYS command.

The modes available are:

  • MODE(ACTIVE) — When a request for space causes the limit for an account to be exceeded, the space request is denied. This will result in an allocation failure or an out-of-space abend, since the request for space cannot be satisfied. If MODE(ACTIVE) is specified and the account has exceeded its limit value (the MAX value set by DLADD/DLALTER), then DLimit will not allow any further space to be obtained until the amount of space used in the account falls below the MAX value.

  • MODE(WARN) — When a request for space causes the limit for an account to be exceeded, an error message is issued. The request for space is honored and the allocation is allowed to proceed.

  • MODE(INACTIVE) — No action is taken when a request for space is assigned to the account. The space amounts for the accounts in the DLimit database are not changed. The account is essentially dormant.

  • MODE(TRACK) — Specifies that space amounts are to be accumulated for the account in the DLimit database, but no warning messages are to be issued and no space requests are to be denied.

  • MODE(option FORCE|NOFORCE) — The FORCE parameter causes the specified mode to be used for the account regardless of the setting of the MODE value of individual accounts. FORCE overrides the normal order of precedence (account, system). NOFORCE must be used to change the mode when the FORCE parameter has been previously used.

    Note: The use of the FORCE parameter is not recommended.

Default: MODE(INACTIVE)

Format: MODE(ACTIVE | WARN | TRACK | INACTIVE | FORCE | NOFORCE)

SYSTEM

Function: This is an optional parameter. The SYSTEM parameter indicates that debugging information from the DLimit $CONTROL account is to be displayed. This parameter isn't normally required and should be specified only when requested by Customer support.

Default: None

Format: SYSTEM