The following operator commands can be entered from the console to monitor and control Adabas nucleus operation.
Use the ADAEND command to terminate Adabas session normally. No new users are accepted after this command has been issued. ET logic updating is continued until the end of the current logical transaction for each user. After all activity has been completed as described above, the Adabas session is terminated. In nucleus cluster environments, the GLOBAL option can be used to terminate the Adabas session in all active cluster nuclei.
Use the ALOCKF command to lock a file in advance to ensure that an EXU, EXF, or UTI user will be able to obtain exclusive control of the specified file. The advance-lock prevents new transactions from using the file. Once all current users have stopped using the file, the exclusive-control user will get the lock. Until then, Adabas keeps the exclusive-control user waiting.
To remove the advance lock without running the utility, see the RALOCKF command.
This command is not available in single user mode or for a read-only nucleus. It is available in cluster and non-cluster environments.
The following key points should be noted about advance-locks on files:
An advance-lock can be set while a file is being used.
A command requesting exclusive control (UTI, EXF, or EXU) over an advance-locked file will wait in the command queue until all other users stop using the file before it starts processing the file.
Advance-locks are automatically removed when a user gets exclusive control over the file. However, if a file is locked (via the LOCKF, LOCKU, or LOCKX commands), the locks are not removed when a user gets exclusive control over the file. (Locks must be explicitly removed, whereas advance-locks are automatically removed.)
Adabas will reject an advance-lock on a file that is already locked (via the LOCKF, LOCKU, LOCKX or ALOCKF commands) but will accept a lock request on an advance-locked file.
To ensure you have uninterrupted exclusive control over a file in a situation where you have multiple steps to run that require uninterrupted exclusive control while all steps have been processed, use a combination of advance-locking the file (ALOCKF), stopping all users of the file (STOPF), and locking the file (LOCKU).
In the case of expanded files, an ALOCKF command is applied to the anchor file (representing the entire expanded file chain).
In a cluster environment, advance-locks are effective in all nuclei of the cluster.
In the following example, issuing the ALOCKF request to advance-lock file 32 ensures that file 32 will be available so the ADALOD UPDATE function can take exclusive control (via a UTI request) of the file for its processing:
ADADBS OPERCOM ALOCKF=32 ADALOD UPDATE FILE=32
Adabas processing proceeds in the following manner for these utility functions:
When the ADADBS OPERCOM ALOCKF request is submitted, file 32 is marked as advance-locked.
If there are any active users of file 32, the ADALOD UTI request cannot be granted immediately and will wait for the active users to end their transactions or sessions. Active users continue to issue commands against file 32. However, requests by new users for file 32 are rejected because of the advance-lock on the file.
When all active users of file 32 have ended their transactions or sessions, the ADALOD UTI request for exclusive control can be granted. Once exclusive control is established, ADALOD UPDATE processing can occur.
As part of the successful execution of the ADALOD UTI request, the advance-lock is removed from the file. However, because ADALOD processing now has exclusive control of file 32, other users still cannot access it.
To accelerate the process and limit the wait time for the ADALOD UTI request, you can simply stop all active users of the file by force using the STOPF operator command:
ADADBS OPERCOM ALOCKF=32 ADADBS OPERCOM STOPF=32 ADALOD UPDATE FILE=32
In this case, the STOPF command will cause the nucleus to back out and stop users of file 32 before the ADALOD UTI request is granted. In addition, the advance-lock request specified by the ALOCKF command will prevent new users from accessing the file until the ADALOD UTI request for exclusive control is processed.
One limitation of ALOCKF processing is that it cannot ensure that a job gets uninterrupted exclusive control if the job consists of multiple job steps in a series. Suppose an installation wants to run the following utility sequence:
ADAULD UNLOAD FILE=45 ADADBS REFRESH FILE=45 ADALOD UPDATE FILE=45
An ALOCKF request to advance-lock file 45 in this case would only work for the ADAULD UNLOAD function, because the ADAULD EXU request for exclusive control of file 45 would remove the advance-lock. If there are active users who try to issue commands against file 45, there is a chance that one of them will execute a command between the UNLOAD and REFRESH steps, or between the REFRESH and UPDATE steps. Such a user may also prevent the REFRESH or UPDATE step from obtaining exclusive control of file 45.
To ensure you have uninterrupted exclusive control over the file in this situation, use a combination of advance-locking the file (ALOCKF), stopping the file (STOPF), and locking the file (LOCKU):
ADADBS OPERCOM ALOCKF=45 ADADBS OPERCOM STOPF=45 ADADBS OPERCOM LOCKU=45 ADAULD UNLOAD FILE=45 ADADBS REFRESH FILE=45 ADALOD UPDATE FILE=45 ADADBS OPERCOM UNLOCKU=45
In this example, Adabas processing proceeds in the following manner:
When the ADADBS OPERCOM ALOCKF request is submitted, file 45 is marked as advance-locked.
The ADADBS OPERCOM STOPF request causes the nucleus to back out and stop users of file 45. (This step is optional.)
The ADADBS OPERCOM LOCKU request locks the file more permanently than the ALOCKF request since the LOCKU lock will stay in effect until it is explicitly released.
If there are any active users updating file 45, the ADAULD EXU request cannot be granted immediately and will wait for the update users to end their transactions or sessions. Active users may continue to issue commands against file 45. However, requests by new users for file 45 are rejected because of the advance-lock on the file.
When all active users of file 45 have ended their transactions or sessions, the ADAULD EXU request for exclusive control can be granted. Once exclusive control is established, ADAULD UNLOAD processing can occur.
As part of the successful execution of the ADAULD UTI request, the advance-lock is removed from the file. However, because ADAULD processing now has exclusive control of file 45, other users still cannot access it.
When ADAULD processing completes, it releases exclusive control of file 45. However, the LOCKU lock ensures that other users still cannot access it.
The ADADBS utility will issue a UTI request for exclusive control of file 45, which will be granted. ADADBS REFRESH processing will then occur. When it completes, ADADBS will release exclusive control of file 45. However, the LOCKU lock ensures that other users still cannot access it.
The ADALOD utility will issue a UTI request for exclusive control of file 45, which will be granted. ADALOD UPDATE processing will then occur. When it completes, ADALOD will release exclusive control of file 45. However, the LOCKU lock ensures that other users still cannot access it.
The ADADBS OPERCOM UNLOCKU request explicitly unlocks file 45, making it available for other users.
Use the AOSLOG command to activate and deactivate logging of certain Adabas calls that modify the nucleus to DDPRINT. These calls are issued either by ADADBS OPERCOM or Adabas Online System. Read and display calls are not logged.
Use the ASSOSPACEWARN command to specify up to three pairs of threshold percentages and percentage change increments, expressed as percentages of the total Associator (ASSO) portion of the database. When ASSO space use reaches a specified threshold percentage, a space usage message is issued. In addition, when the ASSO space use changes by the increment specified for that threshold, additional space usage messages are issued.
Note:
For the purposes of database space notifications, the space used in the
Adabas database comprises all database blocks that have been assigned either to
some common purpose (for example, DSST, PPT, DLOG area) or to a file in the
database. Only space listed in the free space table (FST) is not calculated as
used. In particular, free space allocated for some file but not yet used is
calculated as used.
The following specifications can be made in the ASSOSPACEWARN command:
| Parameter | Description |
|---|---|
| threshold# | A threshold, expressed as a percentage of the total
Associator portion of the database. When ASSO space use exceeds or falls below
any of the thresholds set, a space usage message is issued. The default is zero
(0). If zero is specified for the first threshold setting, no space messages
are issued.
When more than one threshold is specified, the second threshold specification must be greater than the first. Likewise, the third threshold specification (if made) must be greater than the second. |
| inc# | An increment percentage, expressed as a percentage of the total ASSO portion of the database. When ASSO space use changes (increases or decreases) from the associated threshold by the amount given in this increment percentage, another space usage message is issued. The default is five percent (5). |
Up to three threshold-increment pairs can be specified.
Use the ASYTVS command to activate or deactivate asynchronous flushing of buffers based on volume serial number.
Force a connection attempt with all related Auditing servers or databases or to the specified Adabas database ID.
Use the AUDCONNECT command to dynamically force a connection attempt to either a specific Auditing Server or Adabas database ID or to all related Auditing Server or Adabas database IDs.
One of the parameters of the
AUDCONNECT
command must be specified. There is no default. The parameters are described in the following table:
| Parameter | Forces a reconnection attempt with |
|---|---|
| ALL | All known Auditing Server or Adabas database IDs |
| dbid | The specified Auditing Server or Adabas database ID. |
Use the AUDITLOG command to change the setting of the AUDITLOG ADARUN parameter from NO to CONSOLE which activates the AUDITLOG to start writing all utility, and AOS audit data to the console.
Use the AUTOINCASSOSIZE command to modify the setting of the AUTOINCASSOSIZE ADARUN parameter while the database is running. AUTOINCASSOSIZE specifies the size, in cylinders or blocks, by which the highest-numbered (last-defined) Associator (ASSO) data set will be increased by an automatic database increase process.
This parameter only has an effect if the AUTOINCASSOTHRESHOLD setting has a non-zero value. A numeric value followed by the letter B indicates the value specifies a number of blocks, which is then rounded up to the next highest amount that fills the final track or other platform-dependent minimum space allocation unit. A numeric value without the suffix B indicates the increment is in cylinders.
If an automatic database increase process is started to increase the ASSO component of the database, the last ASSO container data set will be increased by the number of cylinders or blocks specified by AUTOINCASSOSIZE. (The number of cylinders or blocks added may be less, however, if the limit set by the AUTOINCASSOTOTAL parameter is reached.)
If the last ASSO container data set cannot be increased by the specified size, but only by a lesser amount, the automatic increase process will increase the data set by the amount of space that it can get. Note that one data set can span at most 59 volumes with up to 16 extents on each volume. When these limits are reached, the database should be increased manually by adding a new container data set with the ADADBS ONLADD utility function.
When 4-byte RABNs are used, valid values for this parameter range from zero (0) to 2147483647 cylinders or from zero (0) to 2147483647B blocks. When 3-byte RABNs are used, the limits range from zero (0) to 16777215 blocks or the equivalent in cylinders. A value of "0" or "0B" means that no automatic increase will be performed for ASSO space. The default value for this parameter is zero, which functionally disables auto-increase for ASSO space.
If AUTOINCASSOSIZE is set to a small value, the automatic database increase process may be initiated multiple times and cause the container allocation to reach platform-dependent limits on extents and volumes. Once that occurs, there can be no more auto-increases until the container allocations are consolidated, which requires stopping all nuclei using the container. Alternatively, a manual increase can be used to add another container without stopping the Adabas nucleus.
Use the AUTOINCASSOTHRESHOLD command to modify the setting of the AUTOINCASSOTHRESHOLD ADARUN parameter while the database is running. AUTOINCASSOTHRESHOLD specifies the Associator space threshold at which Adabas automatically initiates a database increase process. This threshold is expressed as a percentage of used Associator (ASSO) space to total ASSO space available in the database. ASSO space is considered used if it is not listed as free in the Free Space Table (FST).
If the used ASSO space matches or exceeds the percentage defined by the specified AUTOINCASSOTHRESHOLD setting, Adabas automatically initiates a database increase process for ASSO space.
Note that the database increase process may take some time, the length of which is related to the size by which the database is increased (the value of the AUTOINCASSOSIZE setting). The AUTOINCASSOTHRESHOLD setting should be configured so that the increase process is given sufficient time to complete before the database fills up, assuming a reasonable space consumption rate.
Once a database increase process has been initiated, another automatic increase for ASSO space may be started only after the first process has finished and the ASSO space usage again (or still) matches or exceeds the specified threshold.
Valid values for this command are either zero (0) or integers ranging from 50 through 100. A value of zero means that no automatic increase will be performed for ASSO space. A value of 100 means that an automatic increase process will be initiated only when the ASSO space grows full (i.e., no free space is left at all). The default value is zero, which functionally disables auto-increase processes for ASSO space.
Use the AUTOINCASSOTOTAL command to modify the setting of the AUTOINCASSOTOTAL ADARUN parameter while the database is running. AUTOINCASSOTOTAL specifies the maximum total size, in cylinders or blocks, of the entire Associator space of the database that is not to be exceeded by automatic database increase processes.
A numeric value followed by the letter B indicates the value specifies a number of blocks, which is then rounded up to the next highest amount that fills the final track or other platform-dependent minimum space allocation unit. A numeric value without a suffix B indicates the increment is in cylinders.
An automatic database increase process for ASSO space will not exceed the size specified by the AUTOINCASSOTOTAL setting. This setting can be used to limit the total amount of disk space used for the database, in order to protect the disk space remaining available for other databases and other users of the system. Note that this setting limits only automatic increases by Adabas; it does not limit increasing the database manually using the ADADBS ADD, INCREASE, ONLADD or ONLINCREASE utility functions.
AUTOINCASSOTOTAL specifies the number of cylinders or blocks beyond which automatic database increase processes will not extend the ASSO space of the database. If the AUTOINCASSOTOTAL setting is less than the current number of cylinders in the ASSO space plus the AUTOINCASSOSIZE value, an automatic increase will increase the ASSO space only by the difference between the AUTOINCASSOTOTAL value and the current size – that is, by less than the increase requested by the AUTOINCASSOSIZE setting. If AUTOINCASSOTOTAL is not greater than the current number of cylinders in ASSO, no further automatic increases will be performed for ASSO space.
When 4-byte RABNs are used, valid values for this parameter range from zero (0) to 2147483647 cylinders or from zero (0) to 2147483647B blocks. When 3-byte RABNs are used, the limits range from zero (0) to 16777215 blocks or the equivalent in cylinders. A value of "0" or "0B" means that no automatic increase will be performed for ASSO space. The default value for this parameter is zero, which functionally disables auto-increase for ASSO space.
The total size of ASSO space may be constrained to less than the AUTOINCASSOTOTAL value for either of the following reasons.
There may not be enough storage resources to extend to the specified limit.
When using 4-byte RABNs, a component can have at most 2147483647 blocks, and for 3-byte RABNs the limit is 16777215 blocks.
Use the AUTOINCDATASIZE command to modify the setting of the AUTOINCDATASIZE ADARUN parameter while the database is running. AUTOINCDATASIZE specifies the size, in cylinders or blocks, by which the highest-numbered (last-defined) Data Storage (DATA) data set will be increased by an automatic database increase process.
This parameter only has an effect if the AUTOINCDATATHRESHOLD has a non-zero value. A numeric value followed by the letter B indicates the value specifies a number of blocks, which is then rounded up to the next highest amount that fills the final track or other platform-dependent minimum space allocation unit. A numeric value without the suffix B indicates the increment is in cylinders.
If an automatic database increase process is started to increase the DATA component of the database, the last DATA container data set will be increased by the number of cylinders or blocks specified by AUTOINCDATASIZE. (The number of cylinders or blocks added may be less, however, if the limit set by the AUTOINCDATATOTAL parameter is reached.)
If the last DATA container data set cannot be increased by the specified size, but only by a lesser amount, the automatic increase process will increase the data set by the amount of space that it can get. Note that one data set can span at most 59 volumes with up to 16 extents on each volume. When these limits are reached, the database should be increased manually by adding a new container data set with the ADADBS ONLADD utility function.
When 4-byte RABNs are used, valid values for this parameter range from zero (0) to 2147483647 cylinders or from zero (0) to 2147483647B blocks. When 3-byte RABNs are used, the limits range from zero (0) to 16777215 blocks or the equivalent in cylinders. A value of "0" or "0B" means that no automatic increase will be performed for DATA space. The default value for this parameter is zero, which functionally disables auto-increase for DATA space.
If AUTOINCDATASIZE is set to a small value, the automatic database increase process may be initiated multiple times and cause the container allocation to reach platform-dependent limits on extents and volumes. Once that occurs, there can be no more auto-increases until the container allocations are consolidated, which requires stopping all nuclei using the container. Alternatively, a manual increase can be used to add another container without stopping the Adabas nucleus.
Use the AUTOINCDATATHRESHOLD command to modify the setting of the AUTOINCDATATHRESHOLD ADARUN parameter while the database is running. AUTOINCDATATHRESHOLD specifies the Data Storage space threshold at which Adabas automatically initiates a database increase process. This threshold is expressed as a percentage of used Data Storage (DATA) space to total Data Storage space available in the database. DATA space is considered used if it is not listed as free in the Free Space Table (FST).
If the used Data Storage space matches or exceeds the percentage defined by the specified AUTOINCDATATHRESHOLD setting, Adabas automatically initiates a database increase process for DATA space.
Note that the database increase process may take some time, the length of which is related to the size by which the database is increased (the value of the AUTOINCDATASIZE setting). The AUTOINCDATATHRESHOLD setting should be configured so that the increase process is given sufficient time to complete before the database fills up, assuming a reasonable space consumption rate.
Once a database increase process has been initiated, another automatic increase for DATA space may be started only after the first process has finished and the DATA space usage again (or still) matches or exceeds the specified threshold.
Valid values for this command are either zero (0) or integers ranging from 50 through 100. A value of zero means that no automatic increase will be performed for DATA space. A value of 100 means that an automatic increase process will be initiated only when the DATA space grows full (i.e., no free space is left at all). The default value is zero, which functionally disables auto-increase processes for DATA space.
Use the AUTOINCDATATOTAL command to modify the setting of the AUTOINCDATATOTAL ADARUN parameter while the database is running. AUTOINCDATATOTAL specifies the maximum total size, in cylinders or blocks, of the entire Data Storage space of the database that is not to be exceeded by automatic database increase processes.
A numeric value followed by the letter B indicates the value specifies a number of blocks, which is then rounded up to the next highest amount that fills the final track or other platform-dependent minimum space allocation unit. A numeric value without a suffix B indicates the increment is in cylinders.
An automatic database increase process for DATA space will not exceed the size specified by the AUTOINCDATATOTAL setting. This setting can be used to limit the total amount of disk space used for the database, in order to protect the disk space remaining available for other databases and other users of the system. Note that this setting limits only automatic increases by Adabas; it does not limit increasing the database manually using the ADADBS ADD, INCREASE, ONLADD or ONLINCREASE utility functions.
AUTOINCDATATOTAL specifies the number of cylinders or blocks beyond which automatic database increase processes will not extend the DATA space of the database. If AUTOINCDATATOTAL setting is less than the current DATA size plus the AUTOINCDATASIZE value, an automatic increase will increase the DATA space only by the difference between the AUTOINCDATATOTAL value and the current size – that is, by less than the increase requested by the AUTOINCDATASIZE setting. If the AUTOINCDATATOTAL setting is not greater than the current DATA size, no further automatic increases will be performed for DATA space.
When 4-byte RABNs are used, valid values for this parameter range from from zero (0) to 2147483647 blocks or the equivalent in cylinders. When 3-byte RABNs are used, the limits range from zero (0) to 16777215 blocks or the equivalent in cylinders. A value of "0" or "0B" means that no automatic increase will be performed for DATA space. The default value for this parameter is zero, which functionally disables auto-increase for DATA space.
The total size of DATA space may be constrained to less than the AUTOINCDATATOTAL value for either of the following reasons.
There may not be enough storage resources to extend to the specified limit.
When using 4-byte RABNs, a component can have at most 2147483647 blocks, and for 3-byte RABNs the limit is 16777215 blocks.
Use the CANCEL command to cancel the Adabas session immediately. All command processing is immediately suspended. A pending autorestart will be in effect which in turn will cause the autorestart routine to be executed during the initialization of the next Adabas session. In nucleus cluster environments, the GLOBAL option can be used to cancel the Adabas session in all active cluster nuclei.
Use the CLOGMRG command to dynamically modify the setting of the ADARUN CLOGMRG parameter.
The CLOGMRG command is only valid in cluster environments. It is global by definition and affects all nuclei in the cluster.
Note:
The CLUFREEUSER command is
only valid in cluster environments. It can be issued against the local nucleus
only or, with the GLOBAL option, against all active and inactive nuclei in the
cluster.
Use the CLUFREEUSER command to delete leftover cluster user table elements (UTEs or PLXUSERs) in common storage that are no longer associated with user queue elements (UQEs) in a nucleus.
| TNA | TNA specifies a decimal number specifying the timeout value in seconds (max-time). PLXUSERs that are not used during the time specified may be deleted if other conditions are fulfilled. If TNA= is not specified, PLXUSERs may be deleted without regard to their recent use. | ||||||||||
| UID |
|
||||||||||
| UIDPRFX | UIDPRFX accepts the same operands as UID. It operates
in the same manner as UID, except that the operand is considered a prefix and
there is no implicit padding. If the operand matches the initial bytes of the
last eight bytes of the 28-byte communication ID, that PLXUSER may be deleted
if other conditions are fulfilled. "UIDPRFX" may be
abbreviated to "UP".
UID and UIDPRFX are mutually exclusive; one or the other, but not both, can be specified. |
||||||||||
| FORCE | FORCE indicates that leftover PLXUSERs are to be deleted even if the users are due a response code 9 (ADARSP009), subcode 20. If FORCE is not specified, such PLXUSERs are not deleted. Before using the FORCE parameter, ensure that the users owning the PLXUSERs to be deleted will not expect any of their transactions to remain open. | ||||||||||
| GLOBAL | GLOBAL indicates that leftover PLXUSERs throughout the Adabas cluster are to be deleted if they are no longer associated with UQEs and are eligible according to the other specified parameters. Additionally and subject to the other rules, leftover PLXUSERs are deleted if their assigned nuclei have terminated since their last use. If GLOBAL is not specified, only PLXUSERs assigned to the local nucleus and used since the nucleus start are eligible for deletion. | ||||||||||
Use the CT command to dynamically override the ADARUN CT parameter value; that is, the maximum number of seconds that can elapse from the time an Adabas command has been completed until the results are returned to the user through interregion communication (which depends on the particular operating system being used). The minimum setting is 1; the maximum is 16777215.
In nucleus cluster environments, the CT command is global by definition and affects all nuclei in the cluster.
Use the DATASPACEWARN command to specify up to three pairs of threshold percentages and percentage change increments, expressed as percentages of the total Data Storage (DATA) portion of the database. When Data Storage space use reaches a specified threshold percentage, a space usage message is issued. In addition, when the Data Storage space use changes by the increment specified for that threshold, additional space usage messages are issued.
Note:
For the purposes of database space notifications, the space used in the
Adabas database comprises all database blocks that have been assigned either to
some common purpose (for example, DSST, PPT, DLOG area) or to a file in the
database. Only space listed in the free space table (FST) is not calculated as
used. In particular, free space allocated for some file but not yet used is
calculated as used.
The following specifications can be made in the DATASPACEWARN command:
| Parameter | Description |
|---|---|
| threshold# | A threshold, expressed as a percentage of the total
Data Storage (DATA) portion of the database. When DATA space use exceeds or
falls below any of the thresholds set, a space usage message is issued. The
default is zero (0). If zero is specified for the first threshold setting, no
space messages are issued.
When more than one threshold is specified, the second threshold specification must be greater than the first. Likewise, the third threshold specification (if made) must be greater than the second. |
| inc# | An increment percentage, expressed as a percentage of the total DATA portion of the database. When DATA space use changes (increases or decreases) from the associated threshold by the amount given in this increment percentage, another space usage message is issued. The default is five percent (5). |
Up to three threshold-increment pairs can be specified.
Use the DAUQ command to display the user queue elements of those users who have executed at least one Adabas command within the last 15 minutes. Up to 100 user queue elements will be displayed.
Use the DCMDSTAT command to display statistics about the number of commands per command type. Message ADAN1C is issued to display the statistics.
Use the DCQ command to display all posted command queue elements (CQEs). The DCQ command displays each CQE's user ID, job name, and buffer length.
Use the DDIB command to display the data integrity block (DIB). This block contains entries indicating which Adabas utilities are active and the resources being used by each utility.
Use the DDSF command to display Adabas Delta Save Facility status. The DDSF command is only available if the Adabas nucleus is run with the parameter ADARUN DSF=YES.
Use the DELCQ command to explicitly request that the command queue be reviewed for unprocessed commands that have been waiting in the command queue for a specified period of time (or longer).
The DELCQ command can be issued any time during a nucleus session; it is not limited to instances when an online recovery process is ongoing. A one-time pass is made through the command queue once the DELCQ command is issued. Only user commands for which processing has not yet been started may be returned.
During these command queue reviews, any commands from the environments identified by the DELCQ command, with the job name identified in the command, and with wait times that match or exceed the timeout time specified by the DELCQ command will be returned to the user with response code 22 (ADARSP022), subcode 55. When a command in the command queue is returned to the user, no related information is written to the CLOG data set.
The following table describes the substitutions in the syntax of the DELCQ command.
| Parameter | Required? | Description . . . | Default |
|---|---|---|---|
| seconds | Yes | Specify the timeout time, in seconds, for a command in the command
queue. When the wait time for a command in the command queue reaches or exceeds
this timeout value, the command is returned to the issuing user with response
code 22 (ADARSP022), subcode 55.
Valid values range from 1 through 86400 seconds. There is no default. |
— |
| E | No | Specify ALL (to return commands in the command queue from all users) or CICS (to return commands only from CICS sessions). | ALL |
| J | No | Specify a job name to return only commands in the command queue with that job name. The default value is blanks; all commands exceeding the timeout limit coming from any job are returned. | (blanks) |
| GLOBAL | No | This parameter applies only to cluster nuclei. When specified, the
timeout value specified by the DELCQ command applies to all active nuclei in
the cluster.
The default is not to use the GLOBAL parameter; the timeout value then applies only to the command queue for the current nucleus and is ignored by any other nuclei in the cluster. |
— |
Use the DELUF command to delete all users who are using the specified file. Any open transactions of the deleted users are backed out.
This command does not delete EXF or UTI users.
The DELUF command corresponds to the ADADBS OPERCOM STOPF=file-number,PURGE function.
Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are
not required to issue an OP as the first command of the session), run the DELUF
command only if you are certain that the users to be deleted are no longer
active. If a user with an open transaction is deleted, but then returns (by
sending a command), no indication is given about the transaction backout. If
the user continues the transaction, logical inconsistencies in the database
could occur.
Use the DELUI command to delete all users who have not executed a command during the specified time interval (in seconds). Any open transactions of the deleted users are backed out.
This command does not delete EXF or UTI users.
The DELUI command corresponds to the ADADBS OPERCOM STOPI=time,PURGE function.
Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are
not required to issue an OP as the first command of the session), run the DELUI
command only if you are certain that the users to be deleted are no longer
active. If a user with an open transaction is deleted, but then returns (by
sending a command), no indication is given about the transaction backout. If
the user continues the transaction, logical inconsistencies in the database
could occur.
Use the DFILES command to display the number of users currently accessing, updating, or controlling either a specific file (n) or a series of individual files, specified in a list (n1,...,n5). A maximum of five files can be specified in the list. Users are displayed by job name and Adabas-assigned user ID, and listed by file. Only the first 5 users are displayed. If there are more than five users, the number of remaining users is also shown.
Use the DFILESTAT command to display statistics for the number of commands by file. Message ADAN1B is issued to display the statistics.
Use the DFILUSE command to display the number of total commands processed so far for the specified file during the current session. The count is displayed in the nucleus message ADAN33.
Use the DHQ command to display up to five hold queue elements (HQEs) and up to five users of each element.
Use the DHQA command to display up to 100 hold queue elements and up to 10 users of each element.
Use the DLOCKF command to display the locked files. The type of lock is shown in the output. With the exception of advanced file locks, the type of lock appears in parentheses after the file number in console message ADAN30. Possible types are described in the following table:
| Type | Description |
|---|---|
| F | The file was locked by LOCKF. |
| U | The file was locked by LOCKU. |
| X | The file was locked by LOCKX. |
Files locked by ALOCKF (advanced file locks) are identified with the "A-Files=nn" version of the ADAN30 console message.
The DMEMTB command can be issued against Adabas cluster nuclei to display the member state table, which provides information about all of the active nuclei in an Adabas cluster. The information produced by this command may be used by Software AG technical support.
The output produced by the DMEMTB command includes a third flag that indicates whether a system- or message-level XCF status monitoring exception has been encountered and whether a message was issued for the exception.
ADAX61 00226 2009-06-24 16:53:26 Member Status Table ADAX61 00226 2009-06-24 16:53:26 Other members: 1 ADAX61 00226 2009-06-24 16:53:26 This system: 1 ADAX61 00226 2009-06-24 16:53:26 ADAX61 00226 2009-06-24 16:53:26 NUCID: 2,261 ADAX61 00226 2009-06-24 16:53:26 Internal ID: 2 ADAX61 00226 2009-06-24 16:53:26 System: DA2F ADAX61 00226 2009-06-24 16:53:26 Job Name: USACHPD1 ADAX61 00226 2009-06-24 16:53:26 Flags 1/2/3: 11/00/00 ADAX61 00226 2009-06-24 16:53:26 ADAX61 00226 2009-06-24 16:53:26 NUCID: 2,262 ADAX61 00226 2009-06-24 16:53:26 Internal ID: 3 ADAX61 00226 2009-06-24 16:53:26 System: DA2F ADAX61 00226 2009-06-24 16:53:26 Job Name: USACHPD2 ADAX61 00226 2009-06-24 16:53:26 Flags 1/2/3: D7/00/00 ADAN41 00226 2009-06-24 16:53:26 Function completed
Flags 1, 2, and 3 in this report are hexadecimal values that provide the following information about each nucleus:
| Flag | Provides |
|---|---|
| 1 |
The cluster member service summary, as a combination of one or more of the following values:
For example, a value of 97 for Flag 1 indicates that all services are active (X’80’), the nucleus is accepting and processing intracluster commands (X’10’), and cache (X’04’), lock (X’02’) and messaging (X’01’) services are all available (80+10+4+2+1=97). |
| 2 |
The cluster member failure status, as a combination of one or more of the following values:
|
| 3 |
The cluster XCF status monitoring summary, as a combination of one or more of the following values:
For example, a value of 41 for Flag 3 indicates that a member-level XCF status monitoring exception occurred (X’40’) and that a warning message (X’01’) was issued for it (40+1=41). |
Use the DNC command to display the number of posted command queue elements waiting to be selected.
Use the DNFV command to display information about current file use.
This command provides information about the files in use at a particular point in time. It also indicates which other nucleus has exclusive file control if, for example, a user program receives a response 148 (ADARSP148), subcode 15.
Here is some sample output:
ADAI29 OPER CMD: DNFV FNR=00008 A=Y U=Y ID= CA=00000 CU=00001
where;
| FNR=nnnnn | is the file number |
| A={Y | N} | (yes or no) indicates whether the file is used for access (read and/or search) |
| U={Y | N} | (yes or no) indicates whether the file is used for update. Use for update includes use for access. |
| ID=nucid | is the ID of the nucleus that owns the file lock, if the file is locked. |
| CA=nnnnn | is the number of users on this nucleus who are currently accessing this file. |
| CU=nnnnn | is the number of users on this nucleus who are currently updating this file. |
Use the DNH command to display the number of ISNs currently in the hold queue.
Use the DNU command to display the number of current users.
Use the DONLSTAT command to display the status of each active reorder, invert online, or Event Replicator for Adabas initial-state process together with the process ID.
Use the DPARM command to display the Adabas session parameters currently in effect. Here is an example:
23:17:08 ADAI29 OPER CMD: DPARM 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AOSLOG=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 ARNWORKBUFFERS=270 23:17:08 ADAN16 61934 2016-02-24 23:17:06 ASSOSPACEWARN=50,10 23:17:08 ADAN16 61934 2016-02-24 23:17:06 ASYTVS=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUDITLOG=CONSOLE 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOCQENV=ALL 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOCQTIME=60 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOINCASSOSIZE=500 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOINCASSOTHRESHOLD=80 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOINCASSOTOTAL=10,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOINCDATASIZE=1000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOINCDATATHRESHOLD=80 23:17:08 ADAN16 61934 2016-02-24 23:17:06 AUTOINCDATATOTAL=20,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 CT=900 23:17:08 ADAN16 61934 2016-02-24 23:17:06 DATASPACEWARN=60,5 23:17:08 ADAN16 61934 2016-02-24 23:17:06 FMXIO=1 23:17:08 ADAN16 61934 2016-02-24 23:17:06 INDEXCROSSCHECK=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 INDEXUPDATE=ADVANCED 23:17:08 ADAN16 61934 2016-02-24 23:17:06 INTNAS=3,600 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LARGEPAGE=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LBP= 104,860,416 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LCP=10,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LDEUQP=5,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LFIOP=1 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LFP=10,240,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LI=819,200 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGCB=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGFB=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGGING=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGIB=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGIO=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGMB=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGRB=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGSB=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGUX=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGVB=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGVOLIO=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LOGWARN=30 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LP=4,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LQ=220,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LRPL=104,857,600 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LS=29,952 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LU=64,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 LWP=1,200,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 MXTNA=7,200 23:17:08 ADAN16 61934 2016-02-24 23:17:06 MXTSX=7,200 23:17:08 ADAN16 61934 2016-02-24 23:17:06 MXTT=900 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NC=2,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NH=5,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NISNHQ=1,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NONDES=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NPLOGBUFFERS=9 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NQCID=10 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NSISN=51 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NT=30 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NU=10,000 23:17:08 ADAN16 61934 2016-02-24 23:17:06 NWORK1BUFFERS=9 23:17:08 ADAN16 61934 2016-02-24 23:17:06 READONLY=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 REFSTPRT=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 REVIEW=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 RIAFTERUPDATE=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 SECUID=WARN 23:17:08 ADAN16 61934 2016-02-24 23:17:06 SMF=YES 23:17:08 ADAN16 61934 2016-02-24 23:17:06 SMFDETAIL=NONE 23:17:08 ADAN16 61934 2016-02-24 23:17:06 SMFINTERVAL=5 23:17:08 ADAN16 61934 2016-02-24 23:17:06 SMFRECNO=255 23:17:08 ADAN16 61934 2016-02-24 23:17:06 SMFSUBSYS=CURR 23:17:08 ADAN16 61934 2016-02-24 23:17:06 SMF89=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 TLSCMD=900 23:17:08 ADAN16 61934 2016-02-24 23:17:06 TNAA=3,600 23:17:08 ADAN16 61934 2016-02-24 23:17:06 TNAE=3,600 23:17:08 ADAN16 61934 2016-02-24 23:17:06 TNAX=300 23:17:08 ADAN16 61934 2016-02-24 23:17:06 TT=300 23:17:08 ADAN16 61934 2016-02-24 23:17:06 UPDATECONTROL=NODELAY 23:17:08 ADAN16 61934 2016-02-24 23:17:06 UTIONLY=NO 23:17:08 ADAN16 61934 2016-02-24 23:17:06 V64BIT=YES 23:17:08 ADAN41 61934 2016-02-24 23:17:06 FUNCTION COMPLETED
Additional Adabas add-on products and nucleus components may display more parameters than are shown in this sample. For example, the DPARM command includes settings for the ADARUN parameters related to Adabas Cluster Services and Adabas Parallel Services alert and timeout statistics.
Use the DPPT command to display the parallel participant table (PPT) block for a nucleus.
This command produces internal information for use by Software AG technical support.
ADAI29 Oper cmd: DPPT ADAN24 00199 2009-01-27 22:31:35 Display PPT RABNs 00000083 to 000000A2 ADAN24 00199 2009-01-27 22:31:35 ADAN24 00199 2009-01-27 22:31:35 PPT RABN: 00000083 ADAN24 00199 2009-01-27 22:31:35 Number of entries: 05 ADAN24 00199 2009-01-27 22:31:35 Nucleus indicator: E2 ADAN24 00199 2009-01-27 22:31:35 NUCID: 0000 ADAN24 00199 2009-01-27 22:31:35 Session number: 0005 ADAN24 00199 2009-01-27 22:31:35 Last PLOG block: 00000000 ADAN24 00199 2009-01-27 22:31:35 PLOG block ind: 00 ADAN24 00199 2009-01-27 22:31:35 PPT Entry length: 0023 ADAN24 00199 2009-01-27 22:31:35 Entry ID: E6 ADAN24 00199 2009-01-27 22:31:35 Dataset=/SAGUID/PLX2/V7/WORKR1/ ADAN24 00199 2009-01-27 22:31:35 PPT Entry length: 0023 ADAN24 00199 2009-01-27 22:31:35 Entry ID: 61 ADAN24 00199 2009-01-27 22:31:35 Dataset=/ SAGUID /PLX2/V7/PLOGR1/ ADAN24 00199 2009-01-27 22:31:35 PPT Entry length: 0023 ADAN24 00199 2009-01-27 22:31:35 Entry ID: 62 ADAN24 00199 2009-01-27 22:31:35 Dataset=/ SAGUID /PLX2/V7/PLOGR2/ ADAN24 00199 2009-01-27 22:31:35 PPT Entry length: 0023 ADAN24 00199 2009-01-27 22:31:35 Entry ID: 41 ADAN24 00199 2009-01-27 22:31:35 Dataset=/ SAGUID /PLX2/V7/CLOGR1/ ADAN24 00199 2009-01-27 22:31:35 PPT Entry length: 0023 ADAN24 00199 2009-01-27 22:31:35 Entry ID: 42 ADAN24 00199 2009-01-27 22:31:35 Dataset=/ SAGUID /PLX2/V7/CLOGR2/ ADAN41 00199 2009-01-27 22:31:35 Function completed
Use the DRES command to display the allocated pool space and the highest use level (high water mark) reached so far during the current interval by record count for the following resources:
pool for global transaction IDs (XIDs; nonzero only with Adabas Transaction Manager)
cluster block update redo pool (nonzero only for a cluster nucleus with ADARUN LRDP greater than zero)
Note:
The maximum pool value of Work part 1 is derived from the LP parameter. It corresponds
to the maximum number of blocks a transaction can spend on Work Part 1 before Adabas
decides to back it out.
The actual values for the current interval are displayed in the nucleus message ADAN28.
By default, the DRES operator command returns High Watermark statistics for the current interval, which are High Watermark statistics collected after the last refresh. If ADADBS REFRESHSTATS ALL or ADADBS REFRESHSTATS POOLUSAGE has not been invoked, High Watermark statics for the session are returned, which are collected from the start of the nucleus. See ADADBS REFRESHSTATS for more information about invoking statistic refreshes.
When the SESSION parameter is specified, high watermark statistics collected from the start of the nucleus will be displayed in the nucleus with the message ADAN2H. However, if Session statistics have not been generated yet using ADADBS REFRESHSTATS, the message ADAN2J will be printed to inform the user and Interval statistics will be displayed using the ADAN28 message.
When the TS parameter is specified, the time and date of the recorded high watermark will be included in the output. The date time will correspond to the interval, or the session, depending on which is specified. If only the TS parameter is specified, interval statistics with the corresponding timestamp will be displayed in the nucleus with the message ADAN2G. If the SESSION parameter is also specified, the session statistics with the corresponding timestamp will be displayed in the nucleus with the message ADAN2I. If the SESSION parameter is specified with the TS parameter, but the statistics are not available, the message ADAN2J will be displayed in the nucleus, and only interval data and timestamps will be displayed in the nucleus using the ADAN2G message.
Use this command to display the replication-related statistics for an Adabas database (with replication turned on) or for an Event Replicator Server.
When issued against an Adabas database (with replication turned on), the statistics listed include:
The total number of replication transactions completely processed.
The current number of pending replicated transactions (transactions that have been committed, but not yet processed)
The current number of incomplete transactions that will be replicated (but are not yet committed).
When issued against an Event Replicator Server, the statistics related to destinations, global values, and subscriptions in the database are listed. Replay Utility (ADARPL) statistics are also included.
The syntax for DRPLSTAT is:
The DRPLSTAT parameters are always optional and should be used only when the command is issued against an Event Replicator Server; the parameters are not valid when DRPLSTAT is issued for an Adabas database.
Note:
Errors will occur if you attempt to run DRPLSTAT for an Adabas database
using any of the parameters.
DRPLSTAT parameters are described in the following table. If you do not specify any of these parameters, replication-related statistics about all destinations, global values, and subscriptions in the Event Replicator Server are displayed.
| Parameter | Displays replication-related statistics for: |
|---|---|
| D=destname | The specified destination (destname). |
| GLOBALS | All global values only. |
| S=sname | The specified subscription (sname). |
| TOKENS | ADARPL or ADALOD tokens. When a synchronized or replay-only request is submitted, a token is created in the Event Replicator Server nucleus. The TOKENS option of the DRPLSTAT facility allows you to view the details of the token, including the DBID, subscription, destination, start date, start time, end date, and end time in the token. |
Use the DSPACE command to display space defined and used in ASSO and DATA. Message ADANS5 is issued with usage statistics.
Use the DSTAT command to display statistics about the current Adabas nucleus status.
When this command is issued against a running Event Replicator ADARPL job, the Replay Utility (ADARPL) statistics are displayed.
Note:
After issuing a REFRESHSTATS, DSTAT displays the refreshed
statistics.
Use the DTARG command to display the system image currently servicing commands routed using the Entire Net-Work DBID target. This command can be issued against Adabas cluster nuclei.
The Entire Net-Work DBID target is used to route commands from users on remote systems with no active PLXCB. Such systems may be part of the z/OS sysplex or other Entire Net-Work nodes outside the sysplex.
Use the DTH command to display thread status.
Use the DUQ command to display up to five active and inactive user queue elements.
Note:
The ETID field has been enhanced to display the ETID in hex if it
contains non-displayable characters, otherwise it will be displayed in
character format. Trailing spaces are removed.
Use the DUQA command to display up to 100 user queue elements.
Note:
The ETID field has been enhanced to display the ETID in hex if it
contains non-displayable characters, otherwise it will be displayed in
character format. Trailing spaces are removed.
Use the DUQE command to display the user queue element for the specified Adabas-assigned user ID. The user ID must be entered in hexadecimal format as follows:
DUQE=X'A3C1F2'
Do not enter a job name in place of the user ID.
Note:
The ETID field has been enhanced to display the ETID in hex if it
contains non-displayable characters, otherwise it will be displayed in
character format. Trailing spaces are removed.
Use the DUUQE command to display utility user queue elements. Up to 100 user queue elements will be displayed.
Note:
The ETID field has been enhanced to display the ETID in hex if it
contains non-displayable characters, otherwise it will be displayed in
character format. Trailing spaces are removed.
Use the DVOLIO command to display ASSO and DATA I/Os by volume serial (VOLSER) number. The number of reads and writes to each volume is displayed. Message ADAN1A is issued with these statistics.
In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Issue the DXCACHE command against cluster nuclei to display the primary cache-related statistics. Statistics are displayed in messages on the console. The kinds of statistics displayed are described in External Cache Statistics (Cluster Nucleus Only), in the Adabas Cluster Services Operations Guide or in Global Cache Statistics (Cluster Nucleus Only) in the Adabas Parallel Services Operations Guide.
The full set of statistics shown in this output is displayed only for users who have the selectable unit Adabas Online System (AOS) installed.
If you have installed only the demo version of AOS delivered with Adabas, only the statistics in the sections Totals, Data Storage, and Normal Index are displayed using this command.
Issue the DXFILE command against cluster nuclei to display cache-related statistics for one to five files.
Statistics are displayed in messages on the console. The kinds of statistics displayed are described in External Cache Statistics (Cluster Nucleus Only), in the Adabas Cluster Services Operations Guide or in Global Cache Statistics (Cluster Nucleus Only), in the Adabas Parallel Services Operations Guide.
Issue the DXLOCK command against cluster nuclei to display lock-related statistics. Statistics are displayed in messages on the console. The kinds of statistics displayed are described in External Lock Statistics (Cluster Nucleus Only), in the Adabas Cluster Services Operations Guide or in Global Lock Statistics (Cluster Nucleus Only), in the Adabas Parallel Services Operations Guide.
The DXMSG command can be used to display the messaging performance statistics available for Adabas Cluster Services or Adabas Parallel Services. Statistics are displayed in messages on the console. The kinds of statistics displayed are described in Messaging Statistics, in the Adabas Cluster Services Operations Guide or Adabas Parallel Services Operations Guide.
The statistics produced by the DXMSG command can be used to determine the impact of messaging on system performance and to determine how to set the ADARUN MXMSG parameter.
Use the DXSTAT command against cluster nuclei to display all cache- and lock-related statistics as well as I/O statistics for WORK datasets in the cluster. Statistics are displayed in messages on the console. The kinds of statistics displayed are described in External Cache Statistics (Cluster Nucleus Only), External Lock Statistics (Cluster Nucleus Only) and WORK Data Set I/O Statistics (Cluster Nucleus Only), in the Adabas Cluster Services Operations Guide and in Global Cache Statistics (Cluster Nucleus Only), Global Lock Statistics (Cluster Nucleus Only) and WORK Data Set I/O Statistics (Cluster Nucleus Only), in the Adabas Parallel Services Operations Guide.
The full set of external cache statistics shown in this output is displayed only for users who have the selectable unit Adabas Online System (AOS) installed.
If you have installed only the demo version of AOS delivered with Adabas, only the external cache statistics in the sections Totals, Data Storage, and Normal Index are displayed using this command. All file cache statistics for files and all external lock statistics are displayed.
Use the FEOFCL command to close the current dual or multiple command log and switch to another command log. This command is valid only if dual or multiple command logging is in effect.
In nucleus cluster environments, the GLOBAL option can be used to close and switch dual or multiple command logs in all active cluster nuclei.
Use the FEOFPL command to close the current dual or multiple data protection log and switch to the another protection log. This command is valid only if dual or multiple data protection logging is in effect.
In nucleus cluster environments, the GLOBAL option can be used to close and switch dual or multiple protection logs in all active cluster nuclei.
Use the FMXIO command to dynamically modify the setting of the ADARUN FMXIO parameter.
Use the HALT command to perform a BT (back out transaction) for each active ET logic user's session, then terminate the Adabas session. No dumps are produced by HALT.
In nucleus cluster environments, the GLOBAL option can be used to perform a BT for all active ET logic user sessions and terminate the Adabas session in all active cluster nuclei.
Use the INDEXCROSSCHECK command to turn index cross-checking on and off. Index cross-checking is a process Adabas uses to ensure that a data storage record it is reading actually matches the descriptor value in the index by which the record was found. When index cross-checking is turned on, Adabas extracts the descriptor value from the record being read and compares it to the value used for positioning in the index. If there is a mismatch, Adabas returns response code 175 (ADARSP175). Valid values are "YES" and "NO".
If "YES" is specified (the default value), Adabas extracts the descriptor value from the record being read and compares it to the value used for positioning in the index. If the two values are not equal, Adabas checks for a parallel update command on the same record and retries after that update has finished. If there is no parallel update command, Adabas returns response code 175 (ADARSP175) to indicate an inconsistency between the data storage and the index.
If "NO" is specified, Adabas does not extract the descriptor value from the record, but immediately checks for a parallel update command on the same record. If there is one, even if it does not update the descriptor in question, Adabas waits until the update has finished and then retries. With this parameter setting, Adabas does not validate the index against the data storage record and does not return response code 175 (ADARSP175).
Note:
Attempts to change the INDEXCROSSCHECK setting (via this command) in a
cluster environment will be rejected. In a cluster nucleus (CLUSTER=SYSPLEX or
CLUSTER=LOCAL), Adabas sets INDEXCROSSCHECK to
"YES", overriding any user-specified INDEXCROSSCHECK
value, and validates the descriptor value from the index against the
corresponding value from the data storage.
Setting INDEXCROSSCHECK to "NO" may, under certain circumstances, reduce the CPU time required for ensuring that the Data Storage record being read matches the descriptor value by which the record was found. This applies in particular to cases where neither the descriptor itself nor (if it is a special descriptor) its parent field(s) occur in the format buffer specifying the fields to be returned and where the descriptor or one of its parents were defined near the end of the FDT.
Use the LICREFRESH command to:
reload the license module or reread the license file from the library identified by the DDLIC JCL statement in the startup job for the nucleus
display and check the license identified by the DDLIC JCL statement in the startup job for the nucleus.
In cluster environments, the LICREFRESH command must be run on each nucleus in the cluster.
Use the LOCKF command to lock the specified file. No use of the specified file is possible at any security level.
Use the LOCKU command to lock the specified file for all non-utility users. Adabas utilities can use the specified file normally.
Use the LOCKX command to lock the specified file for all users except EXU or EXF users. EXU and EXF users can use the file normally. The lock is released automatically when an EXU user issues an OP command.
Use the LOGGING command to start command logging.
Use the LOGCB command to start logging of the Adabas control block for each command logged.
Use the LOGFB command to start logging of the Adabas format buffer for each command logged.
Use the LOGIB command to start logging of the Adabas ISN buffer for each command logged.
Use the LOGIO command to start logging of Adabas I/O activity for each command logged.
Use the LOGRB command to start logging of the Adabas record buffer for each command logged.
Use the LOGSB command to start logging of the Adabas search buffer for each command logged.
Use the LOGUX command to start logging of user exit B data for inclusion in the CLOG record.
Use the LOGVB command to start logging of the Adabas value buffer for each command logged.
Use the LOGVOLIO command to initiate writing of the extended I/O list to the command log.
Use the LOGWARN command to specify how often the PLOG and CLOG status is checked and resulting alert messages are produced. Valid values range from zero (0) through 2147483647 seconds. The default is 0, indicating that no PLOG or CLOG status checking occurs and no corresponding alert messages are produced. If a non-zero value is specified for LOGWARN, a valid user exit 2 or user exit 12 must also be specified.
The MXCANCEL command can be used against cluster nuclei to dynamically change (while the Adabas nucleus is running) the setting of the MXCANCEL ADARUN parameter for a nucleus. This command can be used to specify the maximum number of seconds for which one cluster nucleus waits for the termination of another nucleus in the cluster that it has canceled for not responding to an internal, intracluster command. Valid values range from 15 through 2147483647.
If the new MXCANCEL value is less than or equal to the current MXCANCELWARN setting, the MXCANCELWARN setting is automatically set to zero (0). (You can then use the MXCANCELWARN command to dynamically set the MXCANCELWARN setting appropriately.)
For more information about the MXCANCEL setting for a nucleus, read about the ADARUN MXCANCEL parameter in the Adabas Operations Manual.
The MXCANCELWARN command can be used to dynamically change (while the Adabas nucleus is running) the setting of the MXCANCELWARN ADARUN parameter for a nucleus. This command can be used to specify the number of seconds after an intracluster cancellation request is made when the cluster nucleus requesting the cancellation should issue warnings about the inability of the canceled peer nucleus to terminate. Valid values can be zero (0) or an integer ranging from 4 through the value of MXCANCEL minus 1 (MXCANCEL-1).
The value of the MXCANCELWARN setting must be less than the value of the MXCANCEL setting. If MXCANCELWARN is set to a value greater than or equal to the value specified for MXCANCEL, the value is rejected. If MXCANCELWARN is set to zero, no warnings are issued about canceled cluster nuclei that are slow to terminate.
For more information about the MXCANCELWARN setting for a nucleus, read about the ADARUN MXCANCELWARN parameter in the Adabas Operations Manual.
The MXMSG command can be used to dynamically change (while the Adabas nucleus is running) the setting of the MXMSG ADARUN parameter for a cluster nucleus. This command can be used to specify the maximum number of seconds in which one cluster nucleus waits for the response of another nucleus in the cluster to an internal, intracluster command. Valid values range from 15 through 32767.
If the new MXMSG value is less than or equal to the current MXMSGWARN setting, the MXMSGWARN setting is automatically set to zero (0). (You can then use the MXMSGWARN command to dynamically set the MXMSGWARN setting appropriately.)
For more information about the MXMSG setting for a nucleus, read about the ADARUN MXMSG parameter in the Adabas Operations Manual.
The MXMSGWARN command can be used to dynamically change (while the Adabas nucleus is running) the setting of the MXMSGWARN ADARUN parameter for a cluster nucleus. This command can be used to specify the number of seconds after an intracluster request is made when the cluster nucleus issuing the intracluster request should issue warnings about the failure of the target cluster nucleus to respond. Valid values can be zero (0) or an integer ranging from 4 through the value of MXMSG minus 1 (MXMSG-1).
The value of MXMSGWARN must be less than the value of MXMSG. If MXMSGWARN is set to a value greater than or equal to the value specified for MXMSG, the value is rejected. If MXMSGWARN is set to zero, no warnings are issued about cluster nuclei that are slow to respond.
For more information about the MXMSGWARN setting for a nucleus, read about the ADARUN MXMSGWARN parameter in the Adabas Operations Manual.
The MXSTATUS command can be used to dynamically change (while the Adabas nucleus is running) the setting of the MXSTATUS ADARUN parameter for a cluster nucleus. This command can be used to specify the number of seconds between member-level XCF status monitoring heartbeats. Valid values range from 15 through 21474836.
Note:
The MXSTATUS command is only used for Adabas Cluster Services and not for
Adabas Parallel Services. Adabas Parallel Services does not use XCF and ignores
the setting.
The MXSTATUS command can only be used to change the value of the MXSTATUS parameter if the ADARUN MXSTATUS parameter is not zero (0). This command cannot be used to turn status monitoring on (by specifying a nonzero value if the ADARUN MXSTATUS setting is zero) or to turn it off (by specifying a value of zero when the ADARUN MXSTATUS setting is nonzero). However, setting MXSTATUS to a very high value is effectively the same as turning status monitoring off (monitoring will occur very infrequently at least).
For more information about the MXSTATUS setting for a nucleus, read about the ADARUN MXSTATUS parameter in the Adabas Operations Manual.
The optional MXWTOR command can be used to dynamically change (while the Adabas nucleus is running) the setting of the MXWTOR ADARUN parameter for a cluster nucleus. This command can be used to specify the maximum number of seconds that a cluster nucleus should wait for an operator response to a self-terminating operator query. Valid values range from 15 through 64800 or zero (0).
If MXWTOR is set to zero, the operator query does not occur (no ADAX9J messages are written) and no operator intervention is expected.
For more information about the MXWTOR setting for a nucleus, read about the ADARUN MXWTOR parameter in the Adabas Operations Manual.
Use the NOLOGGING command to stop or prevent command logging.
Use the NOLOGCB command to stop or prevent logging of the Adabas control block.
Use the NOLOGFB command to stop or prevent logging of the Adabas format buffer.
Use the NOLOGIB command to stop or prevent logging of the Adabas ISN buffer.
Use the NOLOGIO command to stop or prevent logging of Adabas I/O activity.
Use the NOLOGRB command to stop or prevent logging of the Adabas record buffer.
Use the NOLOGSB command to stop or prevent logging of the Adabas search buffer.
Use the NOLOGUX command to stop logging of user exit B data for inclusion in the CLOG record.
Use the NOLOGVB command to stop or prevent logging of the Adabas value buffer.
Use the NOLOGVOLIO command to terminate (stop) writing the extended I/O list to the command log.
Use the NWCONNECT command to retry establishing the Entire Net-Work target associated with the nucleus’s IDT entry. For classic Adabas nuclei, this is the DBID; for Adabas Cluster Services or Adabas Parallel Services, this is the nucleus ID (NUCID).
During nucleus initialization, certain Entire Net-Work errors may have prevented the target from being established, resulting in message ADAM76. Other errors may prevent Entire Net-Work from defining the target when it is started after the nucleus is initialized. The Entire Net-Work operator command DISPLAY TARGETS may be used to see whether the DBID target is known to Entire Net-Work.
Note:
Adabas Cluster Services and Adabas Parallel Services maintain the Entire
Net-Work DBID target using a different protocol. The nucleus will attempt to
reestablish the DBID target automatically at timed intervals.
Use the ONLRESUME command to resume a previously suspended online reorder, invert, or Event Replicator for Adabas initial-state process.
Use the ONLSTOP command to stop an online reorder, invert, or Event Replicator for Adabas initial-state process cleanly. The process continues up to its next interrupt point in order to produce a consistent state, and then terminates after performing all necessary cleanup.
Use the ONLSUSPEND command to suspend an online reorder, invert, or Event Replicator for Adabas initial-state process. The process continues up to its next interrupt point in order to produce a consistent state, performs a command throwback, and enters a state where it cannot be selected for processing. This command is useful if the online process is consuming too much of the nucleus resources.
Use the RALOCKF command to release the advance-lock on the specified file (see ALOCKF command) without running the utility.
This command is available in cluster and non-cluster environments.
Use the RALOCKFA command to release the advance-lock on all files for which it has been set (see ALOCKF command) without running the utility.
This command is available in cluster and non-cluster environments.
Use the RDUMPST command to terminate online dump status. This command is normally used if online execution of the ADASAV utility has terminated abnormally.
Use the READONLY command to switch READONLY status on or off. A value of "YES" switches it on; a value of NO switches it off.
Use the REFSTPRT command to alter the setting of the ADARUN REFSTPRT parameter while the nucleus is active. This operator command allows you to dynamically specify whether printing of statistics is done before an ADADBS REFRESHSTATS utility function run or before interval statistics have been refreshed using Adabas Online System. For more information, read REFSTPRT Parameter: Print Statistics after Refresh Statistics.
deactivate Adabas Review,
change from hub mode to local mode, or
to specify or change the Adabas Review hub with which a nucleus communicates.
Use this command to perform the replication cross-check function for all active databases known (defined in one or more subscriptions) to the Event Replicator Server. When this command is run using the ADADBS OPERCOM function, the information about the cross-check function is printed to the ADADBS DDDRUCK data set. The information printed by ADADBS is the same as the information printed by the Event Replicator Server during the cross-check process initiated by the RPLCHECK operator command.
Note:
This command can only be issued against an Event Replicator Server; it is not valid for
the Adabas nucleus. If this command is issued against a database that is not an
Event Replicator Server, error messages result.
Use this command to dynamically force a connection attempt to either a specific Event Replicator Server or Adabas database ID or to all related Event Replicator Server or Adabas database IDs.
One of the parameters of the RPLCONNECT command must be specified. There is no default. The parameters are described in the following table:
| Parameter | Forces a reconnection attempt with: |
|---|---|
| ALL | All known Event Replicator Server or Adabas database IDs |
| dbid | The specified Event Replicator Server or Adabas database ID. |
Use this command to dynamically specify the number of connection attempts made for the Adabas or Event Replicator Server nucleus after an attempt fails (response 148 is issued).
For nnn, specify a valid integer ranging from zero (0) through 2147483647. A value of zero indicates that no connection attempts should occur; a value of zero makes the most sense in situations where the Adabas database and the Event Replicator Server execute together on the same logical partition (LPAR). If the Adabas database and the Event Replicator Server execute on different LPARs, however, setting a real value using this command helps avoid errors that might arise if network problems occur because the network is not started or a network connection between the Adabas database and the Event Replicator Server is lost.
Use this command to dynamically specify the interval between connection attempts made for the Adabas or Event Replicator Server nucleus after an attempt fails (response 148 is issued).
For nnn, specify the number of seconds for the interval, ranging from zero (0) through 2147483647 seconds. A value of zero indicates that no connection attempts should occur; a value of zero makes the most sense in situations where the Adabas database and the Event Replicator Server execute together on the same logical partition (LPAR). If the Adabas database and the Event Replicator Server execute on different LPARs, however, setting a real value using this command helps avoid errors that might arise if network problems occur because the network is not started or a network connection between the Adabas database and the Event Replicator Server is lost.
Use the SECUID command to alter the ADARUN SECUID parameter while the nucleus is active. For complete information about the SECUID ADARUN parameter, read SECUID Parameter: Security System User ID Requirement Level.
Adabas SMF records can contain a variable set of detail sections in Interval and Termination records (subtypes 2 and 3). This command allows you to override the setting of the SMFDETAIL ADARUN parameter defined for this Adabas sesssion. Using this command you can select the detail section types in Interval and Termination records that should be included in the Adabas SMF records. Unlike the SMFDETAIL ADARUN parameter, the value or values you specify for the SMFDETAIL command do not need to be enclosed in parentheses. If you specify NONE or ALL, they should be specified alone. However, you can specify one or more of the other detail section names (CMD, CSHB, CSHF, CSHG, CSHP, FILE, IODD, LOCK, MSGB, MSGC, MSGH, PARM, STG, THRD, ZIIP or USER) in one SMFDETAIL parameter, separating each value with a comma.
The following table describes the meaning of the possible detail section names that can be used in the SMFDETAIL command:
| Detail Section Name | Description |
|---|---|
| ALL | Generate all possible detail sections in the Adabas SMF records. If this value is specified, no others can be specified on the SMFDETAIL parameter. |
| CMD | Generate Adabas command activity detail sections in the Adabas SMF records. |
| CSHB1 | Generate global cache activity by block detail sections in the Adabas SMF records. |
| CSHF1 | Generate global cache activity by Adabas file number detail sections in the Adabas SMF records. |
| CSHG1 | Generate global cache activity detail sections in the Adabas SMF records. |
| CSHP2 | Generate Adabas Parallel Services cache activity detail sections in the Adabas SMF records. |
| FILE | Generate Adabas file activity detail sections in the Adabas SMF records. |
| IODD | Generate I/O activity by DD statement detail sections in the Adabas SMF records. |
| LOCK1 | Generate global lock activity detail sections in the Adabas SMF records. |
| MSGB1 | Generate internucleus messaging control block activity detail sections in the Adabas SMF records. |
| MSGC1 | Generate internucleus messaging count detail sections in the Adabas SMF records. |
| MSGH1 | Generate internucleus messaging service time histogram detail sections in the Adabas SMF records. |
| NONE | Generate no detail sections in the Adabas SMF records. If this value is specified, no others can be specified on the SMFDETAIL parameter. |
| PARM | Generate ADARUN parameter value detail sections in the Adabas SMF records. |
| STG | Generate Adabas storage pool detail sections in the Adabas SMF records. |
| THRD | Generate thread activity detail sections in the Adabas SMF records. |
| ZIIP | Generate zIIP statistics detail sections in the Adabas SMF records. |
| USER | Generate user-defined details sections in the Adabas SMF records. If USER is specified, a value for the UEXSMF parameter should also be specified to identify the user exit to be invoked to generate the user-defined detail section. |
| 1 Available only in
cluster environments (Adabas Cluster Services or Adabas Parallel Services must
be installed).
2 Available only in cluster environments with Adabas Parallel Services installed. |
|
Adabas SMF records can contain a variable set of detail sections in Interval and Termination records (subtypes 2 and 3). This command allows you to add specific detail sections to your Adabas SMF records for the running Adabas session. The sections you specify are added to those already specified for the Adabas sesssion. If more than one section is listed on an SMFDETAILADD command, separate the section names with commas.
The following table describes the meaning of the possible detail section names that can be used in the SMFDETAILADD command:
| Detail Section Name | Description |
|---|---|
| CMD | Generate Adabas command activity detail sections in the Adabas SMF records. |
| CSHB1 | Generate global cache activity by block detail sections in the Adabas SMF records. |
| CSHF1 | Generate global cache activity by Adabas file number detail sections in the Adabas SMF records. |
| CSHG1 | Generate global cache activity detail sections in the Adabas SMF records. |
| CSHP2 | Generate Adabas Parallel Services cache activity detail sections in the Adabas SMF records. |
| FILE | Generate Adabas file activity detail sections in the Adabas SMF records. |
| IODD | Generate I/O activity by DD statement detail sections in the Adabas SMF recods. |
| LOCK1 | Generate global lock activity detail sections in the Adabas SMF records. |
| MSGB1 | Generate internucleus messaging control block activity detail sections in the Adabas SMF records. |
| MSGC1 | Generate internucleus messaging count detail sections in the Adabas SMF records. |
| MSGH1 | Generate internucleus messaging service time histogram detail sections in the Adabas SMF records. |
| PARM | Generate ADARUN parameter value detail sections in the Adabas SMF records. |
| STG | Generate Adabas storage pool detail sections in the Adabas SMF records. |
| THRD | Generate thread activity detail sections in the Adabas SMF records. |
| ZIIP | Generate zIIP statistics detail sections in the Adabas SMF records. |
| USER | Generate user-defined details section sin the Adabas SMF records. If USER is specified, a value for the UEXSMF ADARUN parameter can also be specified to identify the user exit that should be used to generate the user-defined detail section. |
| 1 Available only in
cluster environments (Adabas Cluster Services or Adabas Parallel Services must
be installed).
2 Available only in cluster environments with Adabas Parallel Services installed. |
|
Adabas SMF records can contain a variable set of detail sections in Interval and Termination records (subtypes 2 and 3). This command allows you to remove specific detail sections from your Adabas SMF records for the running Adabas session. The sections you specify are removed from those already specified for the Adabas sesssion. If more than one section is listed on an SMFDETAILDEL command, separate the section names with commas.
The following table describes the meaning of the possible detail section names that can be used in the SMFDETAILDEL command:
| Detail Section Name | Deletes |
|---|---|
| CMD | Adabas command activity detail sections in the Adabas SMF records. |
| CSHB1 | Global cache activity by block detail sections in the Adabas SMF records. |
| CSHF1 | Global cache activity by Adabas file number detail sections in the Adabas SMF records. |
| CSHG1 | Global cache activity detail sections in the Adabas SMF records. |
| CSHP2 | Adabas Parallel Services cache activity detail sections in the Adabas SMF records. |
| FILE | Adabas file activity detail sections in the Adabas SMF records. |
| IODD | I/O activity by DD statement detail sections in the Adabas SMF records. |
| PARM | ADARUN parameter value detail sections in the Adabas SMF records. |
| LOCK1 | Global lock activity detail sections in the Adabas SMF records. |
| MSGB1 | Internucleus messaging control block activity detail sections in the Adabas SMF records. |
| MSGC1 | Internucleus messaging count detail sections in the Adabas SMF records. |
| MSGH1 | Internucleus messaging service time histogram detail sections in the Adabas SMF records. |
| STG | Adabas storage pool detail sections in the Adabas SMF records. |
| THRD | Thread activity detail sections in the Adabas SMF records. |
| ZIIP | zIIP statistics detail sections in the Adabas SMF records. |
| USER | User-defined details section sin the Adabas SMF records. |
| 1 Available only in
cluster environments (Adabas Cluster Services or Adabas Parallel Services must
be installed).
2 Available only in cluster environments with Adabas Parallel Services installed. |
|
Adabas SMF records can be generated at specific intervals. The SMFINTERVAL command enables and disables interval recording and specifies the interval or the source from which the interval can be derived.
The interval can be one of several values from z/OS specifications or an explicit interval in minutes. Interval records contain a product detail section and whatever detail sections are selected in the SMFDETAIL parameter, except for the ADARUN parameter detail section which are not included in SMF interval records.
The following table describes the meaning of the specifications that can be used in the SMFINTERVAL command:
| Valid Value | Description |
|---|---|
| GLOBAL | Generate all interval SMF records at the rate established by the INTVL and SYNCVAL SMF parameters in PARMLIB member SMFPRMxx. |
| NONE | Generate no interval SMF records. |
| SUBSYS | Generate interval SMF records at the rate specified in PARMLIB member SMFPRMxx for the subsystem identified in the ADARUN SMFSUBSYS parameter. |
| minutes | Generate interval SMF records at the specified interval, in minutes. Valid minute values can range from 1 through 9999.. |
Use this command to override the SMFRECNO setting currently specified for this Adabas session (either through the SMFRECNO ADARUN parameter or by another SMFRECNO command). This command sets the Adabas SMF record number used for user-defined SMF records. IBM designates the range of SMF numbers from 128 through 255 for user-defined records, so valid values range from 128 through 255.
This command overrides any other SMFSUBSYS setting active in the Adabas session (either via the ADARUN SMFSUBSYS parameter or another SMFSUBSYS command). It allows you to associate the Adabas SMF records with an IBM or user-defined subsystem. The z/OS systems staff can provide different sets of SMF system parameters for IBM-defined subsystems. Up to eight user-specified subsystems can be defined, each with their own set of system parameters. This parameter allows you to optionally identify one of these subsystem names to be used with Adabas SMF recording, if the one you want is different from the current one.
The possible values for this command are:
CURRENT: This is the default value and associates the Adabas SMF record with the IBM-defined subsystem under which the Adabas nucleus is active. The subsystem may be TSO for a nucleus running in a TSO session, STC for a starting task or the name of the job entry subsystem under which a batch job is running, JES2 or JES3.
An explicit subsystem name can be specified. It may be either an IBM-defined name or a user-defined name from PARMLIB member SMFPRMxx. The subsystem name is one to four characters long. The first character must be alphabetic or national (#, @, or $) and the remaining characters can be either alphanumeric or national characters. Contact your z/OS administrator for more information about the subsystem names available in your z/OS environment.
Use the STOPF command to stop all users who are using the specified file. Any open transactions of the stopped users will be backed out. A stopped user who returns (by sending a command) will receive response code 9 (ADARSP009).
This command does not stop EXF or UTI users.
Use the STOPI command to stop all users who have not executed a command during the specified time interval (in seconds). Any open transactions of the stopped users will be backed out. A stopped user who returns (by sending a command) will receive response code 9 (ADARSP009).
This command does not stop EXF or UTI users.
Use the STOPSU command to stop and delete all users with the specified security user ID (secuid). Any open transactions of the stopped users will be backed out. No response code is issued; the next time the stopped user issues a command, a new user queue element (UQE) is created.
Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are
not required to issue an OP as the first command of the session), run the
STOPSU command only if you are certain that the users to be deleted are no
longer active. If a user with an open transaction is deleted, but then returns
(by sending a command), no indication is given about the transaction backout.
If the user continues the transaction, logical inconsistencies in the database
could occur. If this is a concern, use the STOPSUR command instead.
Note:
The STOPSU=secuid command is not allowed for
online reorder or invert processes. Use the
ONLSTOP=X'identifier' command instead.
Use the STOPSUR command to stop a user with a specified security user ID (secuid). Any open transactions of the stopped user are backed out. The stopped user is only deleted after he or she has issued a subsequent command and response code 22 (ADARSP22), subcode 54 has been issued in response to that command. This response code-subcode combination is used to notify users that their Adabas activity has been halted and their user session resources have been freed. Only after the response code-subcode combination has been issued is the user queue element (UQE) of the stopped user deleted.
Note:
The STOPSUR=secuid command is not allowed for
online reorder or invert processes. Use the
ONLSTOP=X'identifier' command instead.
Use the STOPU command to stop and delete the user with the Adabas-assigned user ID (in the form shown in the display commands), or stop and delete all users with the specified job name (job-name). Any open transactions of the stopped users will be backed out. No response code is issued; the next time a stopped user issues a command, a new user queue element (UQE) is created.
Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are
not required to issue an OP as the first command of the session), run the STOPU
command only if you are certain that the users to be deleted are no longer
active. If a user with an open transaction is deleted, but then returns (by
sending a command), no indication is given about the transaction backout. If
the user continues the transaction, logical inconsistencies in the database
could occur. If this is a concern, use the STOPUR command instead.
Note:
The STOPU=X'userid' command is not allowed for
online reorder or invert processes. Use the
ONLSTOP=X'identifier' command instead.
The user ID must be specified in hexadecimal format; for example:
STOPU=X'1CF2'
Use the STOPUR command to stop a user with the Adabas-assigned user ID (in the form shown in the display command) or to stop a user with the specified job name. Any open transactions of the stopped user are backed out. The stopped user is only deleted after he or she has issued a subsequent command and response code 22 (ADARSP22), subcode 54 has been issued in response to that command. This response code-subcode combination is used to notify users that their Adabas activity has been halted and their user session resources have been freed. Only after the response code-subcode combination has been issued is the user queue element (UQE) of the stopped user deleted.
Note:
The STOPUR=X'userid' command is not allowed
for online reorder or invert processes. Use the
ONLSTOP=X'identifier' command instead.
The user ID must be specified in hexadecimal format; for example:
STOPUR=X'1CF2'
Use the SYNCC command to force synchronization for all ET users. The nucleus waits for all ET users to reach ET status.
Use this command against an Adabas Cluster Services nucleus to specify the system on which the Entire Net-Work DBID target for the cluster database is to be established. Specify a system name or the NUCID of a cluster nucleus on that system. The DBID target can be established on any system where a nucleus of the cluster is active. It is used to route commands from users on remote systems with no active PLXCB. Such systems may be part of the z/OS sysplex or other Entire Net-Work nodes outside the sysplex.
The command instructs Entire Net-Work to route requests to an Entire Net-Work node on an implicitly or explicitly specified system image. All future commands will be routed to the new destination. If there are existing users who have been routed using the DBID target and the target is relocated to another Entire Net-Work node, they will be reassigned to any cluster nuclei on the new node. These users lose their existing sessions with their previously assigned nuclei. As a consequence, they may receive response code 9 (ADARSP009) on the first command after the target is moved. Furthermore, they may receive response code 21 (ADARSP021) if they attempt to reuse previously defined command IDs (logical read sequences or search results).
Several possible operands can be used to specify the desired DBID target assignment, as described in the following table.
| Operand | Description |
|---|---|
| * | Specify an asterisk (*) to assign the DBID target to the Entire Net-Work node associated with the nucleus receiving the command. |
| nucid | Specify the nucleus ID (as defined in the ADARUN NUCID parameter) of an active cluster nucleus to assign the DBID target to the Entire Net-Work node associated with that nucleus. |
| sysname | Specify a system name (LPAR name) to assign the DBID target to the Entire Net-Work node associated with an active cluster nucleus on that system. |
Note:
The DBID target identifies an Entire Net-Work node, not a specific
nucleus on a system. The DBID target is jointly serviced by all nuclei on that
Entire Net-Work node.
Use the TCPIP command to open or close a direct TCP/IP link to the Adabas nucleus or to close all TCP/IP links when no URL is specified. You can also use the TCP/IP command to perform any valid Entire Net-Work operator command (net-work_cmd) or direct it to a TCP/IP link to the Adabas nucleus. The Entire Net-Work operator commands you can use are described in the section entitled Entire Net-Work Operator Commands under the section Statement and Command Reference in the Entire Net-Work Reference Guide. These Entire Net-Work commands must be preceded by a plus character ("+").
Note:
The OPEN command can be replaced by the START command and the CLOSE
command can be replaced by ADAEND, END, HALT, STOP or TERMINATE, as used by
Entire Net-Work.
This command is only possible when the ADARUN parameter
TCPIP is set to
"YES" and all conditions for that setting have been
met. This command can be used to close the URL set in the ADARUN
TCPURL parameter, or to open or close
additional TCP/IP links.
You must identify the universal resource locator (URL) for the TCP/IP link you want to open or close. The URL is a 20-byte address that conforms to the RFC specification for URLs. For information on how these URLs should be specified, read about the TCPURL ADARUN parameter, elsewhere in your Adabas documentation.
TCPIP=OPEN=OES::12216
TCPIP=CLOSE
To turn logging on:
TCPIP=+LOG=YES
Use the TNAA command to set the non-activity time limit for access-only users. This value must be greater than zero and replaces the value set by the TNAA ADARUN parameter.
In nucleus cluster environments, the TNAA command is global by definition and affects all nuclei in the cluster.
Use the TNAE command to set the non-activity time limit for ET logic users. This value must be greater than zero and replaces the value set by the TNAE ADARUN parameter.
In nucleus cluster environments, the TNAE command is global by definition and affects all nuclei in the cluster.
Use the TNAX command to set the non-activity time limit for exclusive control users. This value must be greater than zero and replaces the value set by the TNAX ADARUN parameter.
In nucleus cluster environments, the TNAX command is global by definition and affects all nuclei in the cluster.
Use the TT command to set the transaction time limit for ET logic users. This value must be greater than zero and replaces the value set by the TT ADARUN parameter.
In nucleus cluster environments, the TT command is global by definition and affects all nuclei in the cluster.
Use the UNLOCKF command to unlock the specified file. File usage is restored to its pre-locked status.
Use the UNLOCKU command to unlock the specified file that was previously locked for all non-utility users. File usage is restored to its pre-locked status.
Use the UNLOCKX command to unlock the specified file that was previously locked for non-exclusive control users. File usage is restored to its pre-locked status.
Use the UTIONLY command to switch the ADARUN UTIONLY status parameter on or off. The default is NO.
Use the DSTAT command to display the current ADACHK, ADALOD, ADAORD, ADARES, ADASAV, or ADAULD operating status. The following are examples of the output that results when DSTAT is entered during specific Adabas utility operations:
Note:
ADAORD, ADARES, and ADAULD do not accept operator commands if
they run in MODE=SINGLE.
Messages ADAU93 appears in addition to the following statistics:
19:53:04 ADAU08 44824 Operator Type-In: DSTAT 19:53:04 ADAU93 ADACHK File=1, Processing in progress 19:53:04 19:53:04 *****ADACHK Nucleus Statistics - Error Verifications***** 19:53:04 Number of transient errors = 0 19:53:04 Number of nucleus verification calls = 0 19:53:05 Number of nucleus retries = 0 19:53:05 Number of AC blocks returned from nucleus = 0 19:53:05 Number of Index blocks returned from nucleus = 0 19:53:05 Number of Data blocks returned from nucleus = 0 19:53:05 Number of nucleus status changes = 0 19:53:05 Number of Buffer flushes = 0
For a description of these statistics, read ADACHK Statistics.
ADAU00 dbid OPERATOR TYPE-IN : DSTAT ADAU22 dbid LOADING DATA STORAGE. REC-NO=3599 ADAU00 dbid OPERATOR TYPE-IN : DSTAT ADAU21 dbid SORTING/LOADING DESCRIPTOR AA
ADAU08 dbid OPERATOR TYPE-IN : DSTAT ADAU26 dbid UNLOADING INDEX. FILE=1 ADAU08 dbid OPERATOR TYPE-IN : DSTAT ADAU25 dbid UNLOADING DATASTORAGE. FILE=2 ADAU08 dbid OPERATOR TYPE-IN : DSTAT ADAU29 dbid LOADING DATASTORAGE. FILE=2
ADAU08 dbid OPERATOR TYPE-IN : DSTAT REGENERATE INPUT VOLUME = BMC002, PLOG-NUM = 12 FROMBLK = 1, FROMTIME = 1996-04-10 11:27:56 TOBLK = 1, TOTIME = 1996-04-10 11:27:56
ADAU08 dbid OPERATOR TYPE-IN : DSTAT ADAU92 dbid STILL INITIALIZING ADAU08 dbid OPERATOR TYPE-IN : DSTAT ADAU10 dbid 435 BLOCKS OUT OF 465 SAVED ADAU08 dbid OPERATOR TYPE-IN : DSTAT ADAU11 dbid 342 BLOCKS OUT OF 451 RESTORED
ADAU08 dbid OPERATOR TYPE-IN : DSTAT ADAU67 dbid UNLOADING FILE=17, RECNO=2875
The Adabas error handling and message buffering facility uses a single operator command, SMGT, followed by a comma and one or more operands:
Valid operands are: ABNORMAL, ACTPIN, ADDPIN, DEACTPIN, DELPIN, DISPLAY, DUMP, MSGBUF, OFF, ON, SNAP, XACTIVATE, XCRITICAL, XDEACTIVATE, XLOAD, and XNOTCRITICAL. Some of these operands are mutually exclusive. All operands are described in Operands for SMGT.
Operands may require that you enter one or more of the following variables:
| Variable Type | Description |
|---|---|
| exit-code | The code that identifies an exit routine to an SMGT
operator command is one of the following:
|
| start, end | The range of addresses for the SNAP operand where start is the hexadecimal address where the SNAP dump begins and end is the hexadecimal address where it ends. |
| module-name | The name of the module. For the XLOAD operand, it is the name of the exit routine module to be loaded; for ADDPIN and DELPIN operands, it is the name of the PIN module to be added or deleted, respectively. |
| pin-number | When a PIN is added, it is assigned a number that can be found using the DISPLAY=PINS operand. This pin number is used for the ACTPIN and DEACTPIN operands to identify the PIN routine to be activated or deactivated, respectively. |
Acceptable abbreviations for operands are provided in mixed case notation (capital letters required, lowercase letters optional). Default values for operands are underlined.
The ABNORMALTERM (ABN) operand determines whether the error handling and message buffering facility will handle abnormal termination errors.
The MSGBUF (MSG) operand temporarily deactivates (OFF) or reactivates (ON) message buffering.
The ABN and MSG operands are mutually exclusive; if one is specified on an individual SMGT command, the other cannot be.
The ACTPIN (ACT) operand is used to activate an individual PIN routine or to reactivate it after it has been temporarily deactivated.
The DEACTPIN (DEACT) operand is used to deactivate an individual PIN routine.
The ACT and DEACT operands are mutually exclusive; if one is specified on an individual SMGT command, the other cannot be.
The ADDPIN (ADD) operand adds PIN routines to the error handling facility. The PIN routine module indicated is loaded and the PINs that are found in it are added to the facility. When a PIN is added, it is assigned a number which can be found using the DISPLAY=PINS operand.
The DELPIN (DEL) operand deletes a PIN module and all the PINs it contains from the facility.
The ADD and DEL operands are mutually exclusive; if one is specified on an individual SMGT command, the other cannot be.
The DISPLAY (D) operand writes status and history information about the error handling and message buffering facility to the job log and to DDPRINT:
| ALL | (the default) displays all reports |
| EXITS | displays current user exit, hyperdescriptor exit, and other exit status |
| MSGBUF | displays message buffering status |
| PINS | displays PIN routine status |
| SUMMARY | displays only the summary information from ALL |
| LAST | displays details of the most recent recovery action |
Sample output for the various DISPLAY values is provided in SMGT Display Output Samples.
The DUMP operand determines whether a full system dump is taken for the Adabas nucleus in the event of an error. The default (OFF) means that only a snap dump is taken.
Note:
To use this command successfully under z/OS, the data set ADASNAP
must be provided in the Adabas startup JCL. For more information, read
Adabas Session
Execution.
The OFF operand deactivates the error handling and message buffering facility temporarily; the ON operand reactivates it.
When SMGT=OFF:
The only valid SMGT operands that can be specified after SMGT=OFF is specified are ON (in a new SMGT command) and DISPLAY. All other SMGT commands are rejected until SMGT=ON is issued.
All other functions of the error handling facility are disabled. PIN modules cannot be invoked. Any user exits marked NOTCRITICAL are treated as CRITICAL; that is, the nucleus terminates abnormally if an error occurs in the exit.
The ON and OFF operands are mutually exclusive; if one is specified on an individual SMGT command, the other cannot be.
The SNAP operand displays a formatted dump of the nucleus without error diagnostics. If SNAP is specified without any additional parameters, the whole nucleus is displayed; if hexadecimal addresses are specified for start and end, the SNAP dump is displayed only for that range of addresses.
The SNAP operand can degrade system performance as long as it is active.
Note:
To use this command successfully under z/OS, the data set ADASNAP
must be provided in the Adabas startup JCL. For more information, read
Adabas Session
Execution.
The XACTIVATE (XA) operand activates a loaded exit module; the XDEACTIVATE (XD) operand deactivates an active exit module.
The XA and XD operands are mutually exclusive; if one is specified on an individual SMGT command, the other cannot be.
The XNOTCRITICAL (XN) operand changes the status of an exit from the default critical to noncritical for the functioning of the Adabas nucleus. Any abnormal termination or program check in a noncritical exit results in the exit being automatically deactivated; however, the Adabas nucleus continues to run. The disabled user exit is not recalled until it is reset. Once the exit error has been corrected, the exit can be reactivated using the XACTIVATE operand.
The XCRITICAL (XC) operand changes the status of an exit from noncritical back to the default critical for the functioning of the Adabas nucleus. Any abnormal termination or program check in a critical exit causes the Adabas nucleus to terminate.
The XN and XC operands are mutually exclusive; if one is specified on an individual SMGT command, the other cannot be.
The XLOAD (XL) operand loads a new version of an exit module.
The module-name parameter is required only for new exits. Because the default is the previous module name, the parameter is optional for exits that have previously been used. The parameter is also optional for any exit defined with a number of zero; for example, the ADACSH exit which is always named ADACSHUX.
 |
Warning: ADACSHUX is a sample user program and is not supported under any maintenance contract agreement. |