RE: TCP Job Date problem

["Carl Galgano" <cgalgano@xxxxxxxxxxxxxxxxx>]

Yup, it picks up the job date of when the server was started.  Always best to go out and get the system date (RTVSYSVAL QDATE) and use it.

cjg

 

Carl J. Galgano
EDI Consulting Services, Inc.
540 Powder Springs Street, Suite C19
Marietta, GA  30064
(770) 422-2995 - voice
(419) 730-8212 - fax
mailto:cgalgano@ediconsulting.com
http://www.ediconsulting.com
AS400 EDI, Networking, E-Commerce and Communications Consulting and Implementation
http://www.icecreamovernight.com
Premium Ice Cream Brands shipped Overnight

"You ain't gonna learn what you don't want to know" - rw

-----Original Message-----
From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Jim Franz
Sent: Monday, October 02, 2000 10:02 PM
To: MIDRANGE-L@midrange.com
Subject: TCP Job Date problem

This is as much a warning as a question. I have data

sent to our system via FTP, then a remote cmd (RCMD)

runs a job on our system. We keep TCP up 24x7. Just

realized if the FTP server job has been up since yesterday,

the remote command runs with a job date of yesterday.

It makes sense now that I think of it, but boy, did

it mess our order entry when todays orders posted

to last month! This is 1st month end we didn't

ipl after.

Jim (still fixin the goof)