The SHOW-LOG-INFORMATION statement can be used to output the following information:
status of realms of the assigned database with respect to the log interval required in order to reach a common consistency point
attributes of the database “with logging or without logging” and whether “online copies are allowed”
information on up to 63 ALOG files (history, sequence numbers in ascending order)
The displayed times reflect the local time.
In addition, useful information for the application of updates is stored in a job variable, provided such a job variable has been created with LINK-NAME=JVBMEND (see section “Supplying the BMEND job variable”).
The SHOW-LOG-INFORMATION statement can be specified alone and may also be entered in the course of DBH operations.
SHOW-LOG-INFORMATION | ||||||||||||||||||||
|
REALM-NAME = *ALL
Shows information for all realms of the assigned database.
REALM-NAME = *ALL-EXCEPT(...)
Shows information for all realms except for those specified.
NAME = list-poss(30): <realm-name>
Name(s) of the realm(s) for which no information is to be shown.
REALM-NAME = list-poss(30): <realm-name>
Shows information for all specified realms.
LOG-FILE = *STD
Shows information as of the current ALOG file, i.e. the one specified in the DBDIR.
LOG-FILE = *NONE
No information on ALOG files is output.
LOG-FILE = <alog-seq-no>
Shows information as of the specified ALOG file.
OUTPUT = list-poss: *SYSLST / *SYSOUT
Defines where the information is to be output.
*SYSLST
Log information is output to SYSLST.
*SYSOUT
Log information is output to SYSOUT.
Message texts
The following information is output:
(1) Details with respect to the processed database
***** LOG INFORMATION FOR DATABASE $userid.dbname[.copy-name]
dbname
Name of the assigned database
copy-name
is output if a shadow database was assigned
(2) List of specified realms indicating the ALOG SEQ NR (e.g. with differing ALOG sequence numbers at the start and end of an online copy)
realm-name
Names of the specified realms
ALOG SEQ NR
BEGIN: alog-seq-no of the realm at the start of the backup operation (of the online backup)
END: alog-seq-no of the realm at the end of the backup operation (of the online backup)
CONSISTENT
YES: The consistency point date at the start and end of the backup operation is the same, and no SYSTEM BREAK is set.
NO: The status of the realm differs from that of a consistency point (the consistency date at the start and end of the backup operation differ, or a SYSTEM BREAK is set)
(3) Specification of the log interval required to apply the update
***** TO MAKE THE SPECIFIED REALMS CONSISTENT, THE FOLLOWING
LOG FILES ARE NECESSARY :
FROM ALOG SEQ NR alog-seq-no1 TO ALOG SEQ NR alog-seq-no2
OR FROM LOG INTERVAL BEGIN datetime-1 TO LOG INTERVAL END datetime-2
alog-seq-no1
The update must be applied starting with this ALOG SEQ NR. This value is saved in a job variable.
alog-seq-no2
This value represents the DEADLINE the must be given in order to make all specified realms consistent.
datetime-1
Date and time of the first log
datetime-2
Date and time of the last log
If no updates need to be applied, this output is suppressed.
(4) Log mode with volume information; Message 4 is not output for shadow databases.
***** SUPPORTS OF ACTUAL LOG FILE:
DEFAULT SUPPORT:{VOLUME = vol-1 DEVICE = dev-1
[... ] /
PVS ID = {DEFAULT PVS / catid}}
RESERVE SUPPORT:{VOLUME = vol-4 DEVICE = dev-4
[... ] /
PVS ID = {DEFAULT PVS / catid}}
(5) Logging history
ALOG SEQ NR
Starting with the sequence number specified via the LOG-FILE operand, information on a maximum of 63 ALOG files is output (with sequence numbers in descending order)
LOG INTERVAL
BEGIN: time-1 Time of the first log
END: time-2 Time of the last log
If the time is not unique, daylight saving time (summer time) is assumed, and a warning is issued.
AFIM
*:
AFIMs are recorded in the ALOG file
'BLANK'
: Gap in the AFIM log
BACKOUT BFIM
*:
BFIMs are recorded in the ALOG file
'BLANK'
: No BFIMs are recorded in the ALOG file
LOGGING GAP
*: The LOG INTERVAL END is less than the LOG INTERVAL BEGIN of the next ALOG file in the sequence or less than the BACK UP DATA of the DBDIR (LOG-FILE=*STD)
?: The continuation of logging in the ALOG file with the next sequence number cannot be examined (LOG-FILE=alog-seq-no)
'BLANK'
: Logging was continued to the next ALOG file in the sequence without interruption
If the ALOG file that is specified in the LOG-FILE operand cannot be read, an error message is output instead of the table.
(6) Whether online copies are allowed
***** ONLINE COPIES BY ARCHIVE ARE [NOT] ALLOWED
Example
/ASSIGN-SYSDTA TO-FILE=*SYSCMD
/ADD-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=SHIPPING.DBDIR
/SELECT-PRODUCT-VERSION PRODUCT-NAME=UDS-SQL, VERSION=02.8A00
/START-UDS-BMEND
***** START BMEND (UDS/SQL V2.9 1801 ) 2019-01-29 09:27:49
//SHOW-LOG-INFORMATION REALM-NAME=*ALL,LOG-FILE=4,OUTPUT=*SYSOUT
SYSTEM_BREAK OCCURRED IN REALM DATABASE-DIRECTORY
***** INCONSISTENT DATABASE DIRECTORY
SYSTEM_BREAK OCCURRED IN REALM PURCHASE-ORDER-RLM
SYSTEM_BREAK OCCURRED IN REALM FOOD
SYSTEM_BREAK OCCURRED IN REALM ARTICLE-RLM
***** INCONSISTENT DATABASE DIRECTORY
FUNCTION ADD NOT AVAILABLE
FUNCTION REMOVE NOT AVAILABLE
FUNCTION START NOT AVAILABLE
FUNCTION STOP NOT AVAILABLE
//END
***** BEGIN FUNCTION SHOW LOG INFORMATION AT 09:55:16
***** LOG INFORMATION FOR DATABASE $XXXXXXXX.SHIPPING __________________________________(1)
***** LOG INTERVAL OF SPECIFIED REALMS _________________________________________________(2)
! ALOG SEQ NR ! !
REALM-NAME ! BEGIN ! END ! CONSISTENT !
------------------------------+-----------+-----------+------------+
DATABASE-DIRECTORY ! 2 ! 2 ! NO !
DATABASE-COMPILER-REALM ! 1 ! 1 ! YES !
CUSTOMER-ORDER-RLM ! 1 ! 1 ! YES !
PURCHASE-ORDER-RLM ! 2 ! 2 ! NO !
CLOTHING ! 1 ! 1 ! YES !
HOUSEHOLD-GOODS ! 1 ! 1 ! YES !
SPORTS-ARTICLES ! 1 ! 1 ! YES !
FOOD ! 2 ! 2 ! NO !
LEISURE ! 1 ! 1 ! YES !
STATIONERY ! 1 ! 1 ! YES !
ARTICLE-RLM ! 2 ! 2 ! NO !
***** TO MAKE THE SPECIFIED REALMS CONSISTENT, THE FOLLOWING LOG FILES ARE _____________(3)
NECESSARY :
FROM ALOG SEQ NR 2 TO ALOG SEQ NR 2
OR FROM LOG INTERVAL BEGIN 20150628095452 TO LOG INTERVAL END
20150628095452
***** LOG MODE : AFIM LOGGING ______________________________________________________(4)
***** SUPPORTS OF ACTUAL LOG FILE :
DEFAULT SUPPORT :PVS ID = DEFAULT PVS
RESERVE SUPPORT :PVS ID = :SQL2:
***** INFORMATION ABOUT LOG HISTORY : ________________________________________________(5)
ALOG SEQ NR! LOG INTERVAL ! AFIM !BACKOUT! LOGGING !
*--------------*--------------* ! ! !
! BEGIN ! END ! ! BFIM ! GAP !
-----------*--------------*--------------*------*-------*---------*
4 !20190129092738!20190129092739! * ! ! ? !
3 !20190129092737!20190129092738! * ! ! !
2 !20190129092727!20190129092737! * ! ! !
1 !20190129092725!20190129092727! * ! ! !
***** ONLINE COPIES BY ARCHIVE ARE ALLOWED ___________________________________________(6)
***** NORMAL END FUNCTION SHOW LOG INFORMATION AT 09:55:16
***** DIAGNOSTIC SUMMARY OF BMEND
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NR OF DATABASE ACCESSES : 51
***** NORMAL END BMEND (UDS/SQL V2.9 1801 ) 2019-01-29 09:27:49