RE: Finding the job date of another job

I am currently writing a command with a CL-CPP that uses the QUSRJOBI API;
my intention is to provide the same information as the RTVJOBA command, but
with input-parms to allow the job-id to be specified.
It may take me a little while as I'm working away from my desk at a client
site for the next four weeks, but I will post the source code(s) on
midrange-l; stay tuned.



Regards

Jeff Bull
iSeries Technical Consultant
NYCO Ltd - iSeries & AS/400 Automation Specialists
Tel: +44(0)20 8416 3778
Fax: +44(0)20 8416 3779
Mobile: +44(0)77 5692 3335
Email: jeff.bull@xxxxxxxxxx
Website: www.nyco.co.uk
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Sallee
Sent: 02 August 2012 23:39
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Finding the job date of another job

Guys,



I appreciate everyone's comments on this and, 'best practices' aside; I went
with the spool file option for several reasons:



1. I have lots of experience using this method (we always done it
that way! :-) :-)).

2. I can not get the operations staff to load the QSYSINC copy
library.

3. I don't have much experience with APIs and they can also change
with a release.



I know #3 is not likely but a possibility.



Jeff, thanks for your note. I had looked at the DSPJOB printout and
overlooked the job date. So, you helped me finish the task the way I had
started.



All of this brings me back to the reason for writing this code. Has anyone
else experienced a problem with Client Access when the user turns off their
PC before shutting down Client Access? About once a week someone will do so
(or the PC crashes) and I get a runaway job that is eating up a lot of the
CPU.



The job log has the following messages in it:

Session stopped by a request from device SG8BWCP1A1.

Input or Output request failed. See message CPF5140.



For my procedure, after checking the WRTACTJOB printout, I wanted a way to
check the job date before any further logic.



Thanks again for all of your comments and help.



Chuck S. (not to be confused with guru Chuck P.)



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.