The 'J' option is not part of The Rexx Language Version 1 (TRL1) , TRL2, nor the ANSI Standard even though it is included in Rexx on TSO. Here is a simple ooRexx function that will return the current date in 'J' format:
-- simple function to return the current date in yyddd (Julian) format
-- takes no arguments
t_day = .datetime~today
return t_day~year~right(2) || t_day~yearDay
Feel free to adapt to your needs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the info. So guess that's a no. I always assumed IBM REXX was the grandfather and all wanna be emulators would at least support all grandfathered functions. But I guess was mistaken. I also guess there is no project in the works to add IBM REXX functionality? Is there a published list of functions not supported in ooRexx that are supported in IBM REXX? Also thanks for the code snippit, but I prefer a more traditional REXX approach:
Sent: Tuesday, May 14, 2019 at 1:41 PM From: "Gil Barmwater" <orange-e@users.sourceforge.net> To: "[oorexx:feature-requests] " <762@feature-requests.oorexx.p.re.sourceforge.net> Subject: [oorexx:feature-requests] #762 Date('J')
The 'J' option is not part of The Rexx Language Version 1 (TRL1) , TRL2, nor the ANSI Standard even though it is included in Rexx on TSO. Here is a simple ooRexx function that will return the current date in 'J' format:
-- simple function to return the current date in yyddd (Julian) format
-- takes no arguments
t_day = .datetime~today
return t_day~year~right(2) || t_day~yearDay
Feel free to adapt to your needs.
I don't get to say Yes or No to these requests; that is up to the development team. My point was that the Rexx language has evolved since its early days on VM and TSO and some of the features on those platforms have not been continued in the newer language levels. An implementation has the option of being "backward" compatible or not and ooRexx has gone with the ANSI standard version as its base language level. So my guess is that this request is not likely to be added. And, BTW, your procedural code solution is perfectly valid and a good choice if it is easier to understand for you. I do not know of a published list of features that are in IBM Rexx but not in ooRexx but perhaps someone else might.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 'J' option is not part of The Rexx Language Version 1 (TRL1) , TRL2, nor the ANSI Standard even though it is included in Rexx on TSO. Here is a simple ooRexx function that will return the current date in 'J' format:
-- simple function to return the current date in yyddd (Julian) format
-- takes no arguments
t_day = .datetime~today
return t_day~year~right(2) || t_day~yearDay
Feel free to adapt to your needs.
From: "Gil Barmwater" <orange-e@users.sourceforge.net>
To: "[oorexx:feature-requests] " <762@feature-requests.oorexx.p.re.sourceforge.net>
Subject: [oorexx:feature-requests] #762 Date('J')
The 'J' option is not part of The Rexx Language Version 1 (TRL1) , TRL2, nor the ANSI Standard even though it is included in Rexx on TSO. Here is a simple ooRexx function that will return the current date in 'J' format:
-- simple function to return the current date in yyddd (Julian) format
-- takes no arguments
t_day = .datetime~today
return t_day~year~right(2) || t_day~yearDay
Feel free to adapt to your needs.
[feature-requests:#762] Date('J')
Status: unread
Milestone: None
Created: Tue May 14, 2019 02:21 PM UTC by Ren Brenton
Last Updated: Tue May 14, 2019 02:21 PM UTC
Owner: nobody
Please add the function Date('J') to return julian date yyddd as described in https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ikja300/date.htm
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/oorexx/feature-requests/762/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
I don't get to say Yes or No to these requests; that is up to the development team. My point was that the Rexx language has evolved since its early days on VM and TSO and some of the features on those platforms have not been continued in the newer language levels. An implementation has the option of being "backward" compatible or not and ooRexx has gone with the ANSI standard version as its base language level. So my guess is that this request is not likely to be added. And, BTW, your procedural code solution is perfectly valid and a good choice if it is easier to understand for you. I do not know of a published list of features that are in IBM Rexx but not in ooRexx but perhaps someone else might.