> Which is harder to parse than, e.g., SMF. Depending on your background. You and I think fixed-length binary and character fields cheek-to-jowl are peachy-keen; the UNIX-y folks are appalled and want something in delimited character form and more-or-less human-readable.
> Only if ISO 8601 requires including the offset. Also, how does ISO 8601 handle fractional time zones? ISO 8601 does not *require* an offset but it does *permit* the designator Z (for Zulu=UTC) or an offset. Offsets are specified in hours and minutes. (No provision for fractional minutes <g>.) Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shmuel Metz (Seymour J.) Sent: Saturday, December 06, 2014 3:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: thought: z/OS structured logging In <CAAJSdjib6t_m-9iKZOshxHvXBz0=683tfnt-hu4jxfj01wg...@mail.gmail.com>, on 12/05/2014 at 07:22 AM, John McKown <john.archie.mck...@gmail.com> said: >Hum, I was thinking more of the UNIX syslog daemon stuff. Which is harder to parse than, e.g., SMF. >Wouldn't including both UTC & local time in ISO8601 be redundant? Only if ISO 8601 requires including the offset. Also, how does ISO 8601 handle fractional time zones? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
