First let me state we are copying the hardcopy log to disk in two ways: 1. External writer proc, SLOGWTR, which writes to a GDG 2. OPLOGCPY job which copies from system Logger OPERLOG to disk
I haven't convinced others to rely on OPERLOG yet :-(. In any case, I have a small issue. Wonder if it is "working as designed", or a bug (but it's been going on for years so probably not)? We copy OPERLOG to disk, there is one message that does not have a 4-digit year. - IEE042I (see below) =========================================================================== 2018096 00:00:00.10 STC01917 00000290 W L 2018096 00:00:00.10 STC01917 00000090 AFTRAP *** AFOPER SLOGWTR SLOGWTRX: S S 2018096 00:00:00.10 STC01917 00000290 S SLOGWTR.L 2018096 00:00:00.10 00000281 IEF196I IEF237I JES2 ALLOCATED TO SYSLOG4 2018096 00:00:00.11 00000281 IEF196I IEF285I +MASTER+.SYSLOG.STC0190 2018096 00:00:00.10 STC00003 00000090 IEF453I PPSJOB01 - JOB FAILED - JCL ERROR 2018096 00:00:00.11 00000281 IEE043I A SYSTEM LOG DATA SET HAS BEEN QU 18096 00:00:00.11 SYSLOG 00000000 IEE042I SYSTEM LOG DATA SET INITIALIZED 2018096 00:00:00.11 STC00003 00000090 $HASP395 PPSJOB01 ENDED =========================================================================== HCFORMAT is not coded in PARMLIB so defaults to the 2-digit year for SYSLOG. Nothing in the manual that I could find about HCFORMAT for OPERLOG (I always assumed OPERLOG was 4-digits always, until noticing this anomaly). Has anyone else run into this? Is HCFORMAT(CENTURY) the only solution? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
