This section explains the procedure for checking for synchronization point dump validation when the KFPS02183-I message cannot be used for this verification due to a problem with respect to the HiRDB version, etc. This procedure uses the pdlogls command to check for status changes in system log files immediately after restart and after synchronization point dump validation.

pdlogls command execution results (immediately after restart)

pdlogls -d sys -s bes1 HOSTNAME : dcm3500(170302) Group Type Server Gen No. Status Run ID Block No. logfg01 sys bes1 11 oc-d--u 365d303d 93 97 logfg02 sys bes1 b os----u 365d303d 66 66 logfg03 sys bes1 c os----u 365d303d 67 68 logfg04 sys bes1 d osud--u 365d303d 69 73 logfg05 sys bes1 e osud--u 365d303d 74 7a logfg06 sys bes1 f osud--u 365d303d 7b 82 logfg07 sys bes1 10 osudb-u 365d303d 83 92 logfg08 sys bes1 0 cn----- 00000000 0 0

Explanation

These execution results indicate that the files in overwrite disabled status in existence immediately after the restart are logfg01 and logfg04 to logfg07.

pdlogls command execution results (after synchronization point dump validation)

pdlogls -d sys -s bes1 HOSTNAME : dcm3500(170424) Group Type Server Gen No. Status Run ID Block No. logfg01 sys bes1 11 osu---u 365d303d 93 99 logfg02 sys bes1 12 osu---u 365d303d 9a a2 logfg03 sys bes1 13 osu---u 365d303d a3 a9 logfg04 sys bes1 d osu---u 365d303d 69 73 logfg05 sys bes1 e osu---u 365d303d 74 7a logfg06 sys bes1 f osu---u 365d303d 7b 82 logfg07 sys bes1 10 osu---u 365d303d 83 92 logfg08 sys bes1 14 oc-d--u 365d303d aa af

Explanation

These execution results indicate that the file in overwrite disabled status in existence after synchronization point dump validation is logfg08. It is clear that the synchronization point dump was validated because the file in overwrite disabled status followed the system log input start point during restart.