In ISPF if you open the calendar in the status area and (for my setup) double 
click on the 'Day of year' a pop-up allows you to get any ddd/yyyy converted.

<paste>
------------------------ Standard Date ---------------------
Enter the day and year below:                               
                                                            
Day . . . . 158   (Between 1 and 365 or 366 if leap year)   
Year  . . . 2018  (Between 1801 and 2099)                   
                                                            
Day   158  of year   2018  is   Thursday      ,   2018/06/07
</paste>

...chris.
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Charles Mills
Sent: June-07-18 8:00 AM
To: [email protected]
Subject: Re: SYSLOG / OPERLOG displaying date.

I am just talking off the top of my head here but couldn't one write an SDSF 
macro where if the user positioned the cursor on a "Julian" date and hit the 
appropriate PF key, a pop-up would display the date in a more user-familiar 
format?

I know it burns me sometimes. I will do an F whatever PREV on the log and hit 
some problem and say "aha! X happened" only to finally realize it happened 
three days ago, and that fact did not jump out because "Julian" dates are not 
"intuitive."

Charles


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of John McKown
Sent: Thursday, June 7, 2018 6:33 AM
To: [email protected]
Subject: Re: SYSLOG / OPERLOG displaying date.

On Thu, Jun 7, 2018 at 8:21 AM Charles Mills <[email protected]> wrote:

> Yeah, and further, they are called "Julian" dates in the Z community 
> and that is a misnomer. 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_
> wiki_Julian-5Fday&d=DwIFaQ&c=UrUhmHsiTVT5qkaA4d_oSzcamb9hmamiCDMzBAEwC
> 7E&r=RI5WP1BN1KW_B4HrO2twbFFOhk97OdY6xsy0TwKReZE&m=1q6EkLI-VpOT47EOois
> SoCwovNIjq7Hbgpgf7j0K7is&s=bbbCPheZKUE3shBLIV8MTFQzfvPl8E09UhagbqTZyk0
> &e=
>
> 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.fs.fed.us_fir
> e_partners_fepp_DODprogram_juliandate.htm&d=DwIFaQ&c=UrUhmHsiTVT5qkaA4
> d_oSzcamb9hmamiCDMzBAEwC7E&r=RI5WP1BN1KW_B4HrO2twbFFOhk97OdY6xsy0TwKRe
> ZE&m=1q6EkLI-VpOT47EOoisSoCwovNIjq7Hbgpgf7j0K7is&s=tXG7NQ58w3q04k_iWo4
> HFC6nzdL4bNW0Ap335eYXJKM&e=
>

​Thanks for that URL. I have a short REXX program which will do it for me using 
the DATE() builtin. What my user (really only one left now) would really like 
would be something similar to: MM/DD/YYYY.JJJ MON  ... She is our single 
remaining production scheduler and sometimes peruses the SYSLOG when 
researching jobs. Having all that information right there would really help her.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to