Missing SECLOG report
DATE: 04/27/2005 TIME: 16:46 RECOVERY MANAGER VER 03.06.00 MISSING SECLOG PAGE: 4
SSID TYPE LOG START SLDS START VOL #1 DATASET NAME COMMENT
IR9O SECLOG 2005 094 08:37:20.3 2005 094 08:37:20.3 DEV514 BMCIRM.QA.ZEG$.IR9O.SLDSS01 IN-ERROR
IRMEG$03 SECLOG 2005 094 09:07:00.7 2005 094 09:07:00.7 N/A BMCIRM.QA.ZEG$01.BLOGP20 MISSING
IRMEG$03 SECLOG 2005 094 09:07:10.9 2005 094 09:07:10.9 DEV221 BMCIRM.QA.ZEG$01.BLOGS40 IN-ERROR
SSID TYPE LOG START SLDS START VOL #1 DATASET NAME COMMENT
IR9O SECLOG 2005 094 08:37:20.3 2005 094 08:37:20.3 DEV514 BMCIRM.QA.ZEG$.IR9O.SLDSS01 IN-ERROR
IRMEG$03 SECLOG 2005 094 09:07:00.7 2005 094 09:07:00.7 N/A BMCIRM.QA.ZEG$01.BLOGP20 MISSING
IRMEG$03 SECLOG 2005 094 09:07:10.9 2005 094 09:07:10.9 DEV221 BMCIRM.QA.ZEG$01.BLOGS40 IN-ERROR
The report contains the fields in the following table.
Field | Description |
|---|---|
SSID | The subsystem ID of the log. |
TYPE | The type of the log, which in this case is SECLOG. |
LOG START | The start date and time of the PRILOG or SECLOG. |
SLDS START | The start date and time of the data set entry that triggered the event. |
VOL #1 | A value that depends on the value in the COMMENT field:
|
DATASET NAME | A data set name that depends on the reason for the event:
|
COMMENT | The reason why this event was triggered. The following values are valid:
|
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*