RE: FTP RCMD Date Weirdness

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

It is because *date is the job date and the particular ftp job that is being used was started on a previous day.  The ftp jobs are prestarted and any ftp request will usually use a job that is already running.  If you want the current date then you should always use the time op-code to get it.

 

Scott Mildenberger

-----Original Message-----
From: Condon, Mike, /m1c [mailto:m1c@ingersoll-imc.com]
Sent: Thursday, July 19, 2001 7:41 AM
To: 'MIDRANGE-L@midrange.com'
Subject: FW: FTP RCMD Date Weirdness

I got this message from a coworker. Any idea why ftp rcmd executed programs would be getting an incorrect date, or if there is any workaround?

-----Original Message-----

Here's a weird one for you...

 

 Mr. Pink has noticed that the picking slip confirm date stored in Gal appears to be a day behind sometimes.   I checked out the program (RRU12) that stores the date in CS from the manifest upload and it is just moving *DATE into STCNF.  This program is run every half hour and is run from an FTP session using RCMD.

 

Mr. Black and I also had noticed this in something else when he was here.  It appears that sometimes yesterday's date is returned for *DATE when run from an FTP RCMD.   To test this, I wrote a program JKJ/QSRC.TCPDATE to output the date from *DATE.  Last night I ran it via FTP RCMD and it reported the correct date and time.   However, this morning when I ran it via FTP RCMD it still reported yesterday's date.  The results of this are in my spool files.