Console support for DBUTLTY STATUS is similar to support for Multi-User STATUS. The option is for all utilities in general, so the option has been added to the DBSYSID macro that generates the DBSIDPR loaded module. To support the console status of DBUTLTY you must therefore ensure that the DBUTLTY DBSIDPR supports console requests (DBSYSID CONSOLE=YES).
CONSOLE= provides console support for the status of CA Datacom/DB Utility (DBUTLTY) functions. CONSOLE= can be set to YES, NO, or an interval of time, with NO being the default.
Note: The option to select an interval of time is only available in z/OS environments.
If you specify YES, DBUTLTY attaches a subtask during its startup and detaches that subtask during its ending process. With CONSOLE=YES, the STATUS command is supported, meaning that you can inquire as to the status of a given DBUTLTY job by issuing a status console command. DBUTLTY functions that include status support are: BACKUP, EXTRACT, LOAD, REORG, and RETIX.
Note: The DBFLSUB callable load process is not part of DBUTLTY and does not support the console status option.
If you specify NO, you have indicated that no console support is needed.
If you specify an interval of time, CONSOLE=nn, you have indicated that the console STATUS command (CONSOLE=YES) is still supported and an automatic internal STATUS command is to be issued every nn minutes (where nn is a number from 5 to 60), the number representing minutes between intervals. As a general rule, specifying 5 minutes for the interval would be considered to be too often, while specifying 60 minutes would usually be considered to be too long.
With CONSOLE=nn selected, the first interval starts during DBUTLTY initialization. At the end of each interval, a function equivalent to the console STATUS is done. If a status is available, the message is written with the status (same message as console STATUS). If no status is available at this instant, no console message is issued. The internal STATUS does not interact with, interfere with, or hinder your ability to issue a console STATUS at any time manually.
Specifying CONSOLE=nn can be desirable for the following reasons. When long-running DBUTLTY LOAD, BACKUP, and RETIX functions are executed, you may want some way to monitor the progress of DBUTLTY. You could always manually issue a console command to request the status of a utility function that is executing, and DBUTLTY would respond with information on the number of records processed so far, the expected number of records in the function, and so on, thereby giving you an idea of the progress of the function. CONSOLE=nn, however, allows you to request that DBUTLTY automatically issue the console command at an interval of time determined by the value you specify with nn, instead of your having to manually issue the command. This can be particularly helpful if you are a Database Administrator, for example, at a site where your security to issue z/OS console commands is restricted.
For each DBUTLTY execution, you can select a library with the appropriate DBSIDPR assembly to indicate whether the automatic messages are desired. This information is listed to the console without your needing console authority and without having to ask an operator to issue the console command on your behalf. Specifying CONSOLE=nn has no affect on existing users. To implement it, you must do a re-assemble of DBSIDPR. Only DBUTLTY executions pointing at the new DBSIDPR are affected.
From a security viewpoint, the automatic console command feature does not display sensitive information, only information that most Database Administrators would use to monitor the progress of a long-running DBUTLTY LOAD, BACKUP, or RETIX function. DBUTLTY functionality can be secured using external security packages. Therefore, using the automatic console command feature does not cause any security exposure.
YES, NO, or nn (where nn is a number from 5 to 60)
NO
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|