|
Folks:
V5R4 CLLE program.
With further testing it turns out that with SAVRST at V5R4 when you use
the CHGPERIOD keyword, the only value that winds up being accepted is
the start date:
Time period for last change: CHGPERIOD
Start date . . . . . . . . . . *ALL
Start time . . . . . . . . . . *ALL
End date . . . . . . . . . . . *ALL
End time . . . . . . . . . . . *ALL
The other values cause an error when called from a CL program (submit
too from CL to answer Joe's question) When called from the command
line, you can use them all.
This behavior changes at V7R1 (I don't have a V6 system I'm willing to
test with right now) where it works properly with all the values
specified from a program.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.