No need for all this if you use the pertinent CEE* date APIs - the IBM knowledge base article cited shows how simple it is - and always works.

Vern

On 1/6/2020 11:45 AM, dlclark@xxxxxxxxxxxxxxxx wrote:
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 01/06/2020
12:16:42 PM:
The logic does the following, all in CL:

* Retrieves the system date into a character field, 6 long.
* Uses CVTDAT to convert the date into a Long Julian format,
field is character, length 7
* Then it puts the Long Julian value into a decimal field,
length 7 and subtracts 7 from that
* It then moves that result back to the character field, length
7, used in step 2
* Then tries a CVTDAT to convert that to an ISO date and blows up

To do it in CL, you would have to handle the subtraction yourself
-- meaning, if the days portion is <= to 7 then subtract 1 from the year
portion and move 366 to the days portion. then MONMSG the CVTDAT and
subtract 1 from the days portion if an error occurs. A bit of a kludge
but it would work.


Sincerely,

Dave Clark


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.