Reason:
This message provides the access status of one or more databases.
The nnnn in the message text is replaced by the DBID of the database, if only one database is involved, or the literal ALL, if more than one database is involved. The DBUTLTY ACCESS function keyword WRITE, READ, or OFF is displayed in place of status in the message.
If the status is WRITE, the job names are always omitted, and the portion for information is blank, unless a catalog is being done on this database. In this case, the literal CATALOG ACTIVE is displayed. If the CATALOG ACTIVE message is presented, the database can be opened based on the access rights when the catalog is complete.
If the option is READ or OFF and no jobs have the database(s) open that is being restricted, the information and job names portion of the message are not present.
If any jobs have the database(s) open, the information section contains the literal ACTIVE JOB(S) and the job names are displayed. If one through five jobs have the database(s) open, then all their names are printed. If more than five are open, four names are printed followed by the literal AND MORE. If the job running is through CA Datacom STAR from a remote location, the ***STARU replaces job names in the message text.
The ACCESS task waiting on any jobs to complete has a status of waiting on exclusive control. The value of the control is DBSACCnnnnn, where DBSACC indicates a system access lock and nnnnn is the database ID. If all bases are being processed, it is one of the bases found open. If the ACCESS is done through DBUTLTY, the DB00607I message printed on the console by the Multi-User Facility is also printed on the report at the utility completion. If IGNORE or FAIL is used and if jobs were found active, the same job name or set of job names printed in Multi-User is in the report.
As soon as the database is marked as the new access status, a write of all pending buffers for the index(s) and data area(s) are done (unless the WAIT value is specified for USERS= option with the ACCESS function). This provides a means for continuous operation backups to have more current information. This is also done for WRITE status so you can cause the write pending with no loss of any current or planned activity.
When the ACCESS function USERS=WAIT option is used, and active jobs are found, the DB00607I message is written to the console indicating the jobs being waited on before the DBUTLTY starts waiting. After every close, the task again searches the open list and sees if the database(s) is now closed. If active jobs still exist and there is now a different list than before, the message is printed with the current list of open jobs. If all jobs are found to have closed, the final DB00607I message is printed indicating that now all jobs are complete. This final DB00607I is returned to DBUTLTY for its report.
The (x) in the message text is simply blanks if the BASE is set to ALL or if (job names) is not blanks. Otherwise, (x) is replaced by (STATUS Y) where Y is replaced by:
If the database is not open.
If the database is open with all users UPDATE=NO.
If the database is OPEN with update.
The ACCESS performs all processing even though it does not exist in the Directory (CXX) in the Multi-User Facility memory. If it does not exist, when the Multi-User Facility is enabled or is deleted by the Multi-User Facility (CXXMAINT OPTION=DELETE,DBID=nnnn), it is considered as not existing until the Multi-User Facility is recycled or the database is opened as part of a User Requirements Table open.
If no active jobs exist, (information) and (job names) are not present in the message text but the (j) option is. The (j) option is the job name and number of the job requesting the access.
Action:
None. This message is for information only.
|
Copyright © 2014 CA.
All rights reserved.
|
|