Re: Date problems -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Date problems
From: oliver.wenzel@xxxxxxxxxxxxxxxxxxxxxxx
Date: Wed, 28 Aug 2002 11:56:27 +0200
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hello,

I had something similar in another situation. Could it be that the job
under that you ran the program was started
on the 26th?

I believe I had the problem with a prestart job. When I started a batch
program from a pc, it would run under prestart job
QZDxxx and the date was set to the start date of the prestart job.

Yep, I just found it. We have a packing list print that is started from a
pc as rmtcmd. It has a program described
printer file and uses UDATE to show the date on top of the list. The date
is 02.08.25 today!

HTH,

Oliver

This mailing list archive is Copyright 1997-2026 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.