Ah, but there are ISODATE and FULLDATE options in both FILELIST and LISTFILE.
IBM has provided for one of your gripes. All you have to do is supply the
leading 0 for the month and hour. That is easy enough in a program, e.g. "dt =
right('0' || dt,10)". The same applies to the time value, except that the
length is 8.
True, you do have a problem typing a fulldate on the line in FILELIST. That can
be easily fixed in EXECUTE by converting the hard-coded '/' references to use a
variable and provide a way of setting it (I used GLOBALV, creating a variable
to manipulate in DEFAULTS will also work). It is only a very few lines of code.
I have done it as an experiment and it works nicely. With it in place you can
enter a command like this
DMSPLU ! mm/dd/yyyy hh:mm:ss
on the filelist line simply by first setting the GLOBALV variable to !. Since
this is EXECUTE XEDIT, the change applies to all of the functions that use it.
Regards,
Richard Schuh
> -----Original Message-----
> From: CMSTSO Pipelines Discussion List
> [mailto:[email protected]] On Behalf Of Glenn Knickerbocker
> Sent: Thursday, October 22, 2009 4:54 PM
> To: [email protected]
> Subject: Re: Move files and preserve timestamps
>
> "Schuh, Richard" wrote:
> > What is unmanageable about "'DMSPLU' fn ft fm dt tm"? Of course the
> > date and time must be properly formatted,
>
> That's exactly it. DMSPLU accepts only FULLDATE format--but
> with the leading zeroes filled in. On FILELIST file lines,
> it's impossible to enter because of the slashes. In commands
> built from LISTFILE responses, the leading zeroes are missing.
>
> (And of course the new FIXDATE was designed as a drop-in
> replacement for the old one, which didn't have the same
> syntax as DMSPLU.)
>
> ¬R
>
