WRKJOB duplicate jobs -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: WRKJOB duplicate jobs
From: Jerry Draper <midrangel@xxxxxxxxxxxxx>
Date: Tue, 15 Mar 2011 14:42:49 -0700
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/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

We have a CL that is trying to determine the last instance for a particular job.

The CL does a WRKJOB <job number> to *PRINT and then interrogates the messages until the last job instance is discovered.

It looks like WRKJOB is showing instances by job number and not by date.

We are at job number 900222 and we are wondering what will happen when the job number rolls over to 000001.

What order will the jobs show up in for the WRKJOB command?

Jerry

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.