Yeah, and further, they are called "Julian" dates in the Z community and that is a misnomer. https://en.wikipedia.org/wiki/Julian_day
I like one thing about them: they are compact. 18158 is the most compact (generally acceptable) way to represent June 7, 2018. Here are conversion tables if you are interested: https://www.fs.fed.us/fire/partners/fepp/DODprogram/juliandate.htm Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Thursday, June 7, 2018 6:02 AM To: [email protected] Subject: SYSLOG / OPERLOG displaying date. I may do the following in a "post processing" job for my SYSLOG archiving. One thing which is "nasty" about z/OS, vs, z/VSE and other systems is that it prefers to display the calendar date as year.day-in-year. IMNSHO, this is a real PITA to people in the "real" world because nobody really much cares what day it is since the start of the year. So SYSLOG/OPERLOG's use of "yy.ddd" or "yyyy.ddd" is fairly useless, again, IMO. I do like what CA does in some of their products which would be nice to have in these facilities. They display the date as either dd/mm/yyyy.ddd or mm/dd/yyyy.ddd . I think that having a new value for HCFORMAT(...) in the CONSOLnn member would be nice. I don't really know, or particularily care, what the keyword might be to do this. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
