True enough, it is a bit annoying on the multi-release compatibility. I code
the column-numbers and search-strings of each data-field I need as a
&variable *DEC (3 0) and code the values into a 'user-formatted' data-area.
When an upgrade requires it, the column numbers etc are easily changed, and
the same version of the program can run on systems with different spoolfile
formats.
I have considered coding the column numbers as default values to command
'Additional Parameters', one could also code the spoolfile name ...
However, as I said earlier, for the purists the QUSRJOBI API is the
'correct' way to go in this scenario.
Many years ago, when I was young (aaaah), and an applications development
programmer, we had a saying that you should never write programs without
bugs, and never code in all the bells-and-whistles you can ... we might grow
up to be Support Programmers :-)
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 rob@xxxxxxxxx
Sent: 02 August 2012 15:48
To: Midrange Systems Technical Discussion
Subject: RE: Finding the job date of another job
I gave up on spool files long ago. I got tired of trying to figure out
where IBM had the information I needed whenever a new release came out.
And trying to have programs extract information from spool files and still
work on multiple releases. I've got enough stress on a new release and I
don't need to worry about spool file layout. Or trying to read outfiles
that may have their format change with a new release. Granted IBM 'mostly'
does a good job in adding new fields to the end so you can work around
format level checks. But that can get ridiculous too - like instead of
telling us the object size you now have to multiple this field by that field
to get the object size.
Sample on that spool file that was really frustrating was trying to use
WRKSYSSTS to a spool to get the size of the system ASP. Remember jumping
from MB to GB? That's how long ago I gave up on spool file extraction.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Jeff.Nyco" <jeff.nyco@xxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>,
Date: 08/02/2012 10:39 AM
Subject: RE: Finding the job date of another job
Sent by: midrange-l-bounces@xxxxxxxxxxxx
OK, the QUSRJOBI is the API, this does allow you to specify the 'target
job'; depending on the particular date you are after, Format JOBI0300 or
JOBI0400.
Personally I prefer my extraction of the data from the DSPJOB spoolfile
(or
OUTFILE), a technique I use frequently to retrieve particular bits of
information that has no ready-made RTV-command for it.
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 Paul Therrien
Sent: 02 August 2012 15:03
To: Midrange Systems Technical Discussion
Subject: RE: Finding the job date of another job
? That doesn't appear to work...
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Thursday, August 02, 2012 8:51 AM
To: Midrange Systems Technical Discussion
Subject: RE: Finding the job date of another job
Jeff,
RTVJOBA JOB(MYJOB) USER(ME) NBR(123456)
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff.Nyco
Sent: Thursday, August 02, 2012 7:39 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Finding the job date of another job
RTVJOBA is exclusively for the current job.
I would write a CLP with the following steps:
a) DSPJOB to *PRINT. The spoolfile contains: Date Entered
System, Date
Started, Job Date
b) CPYSPLF to a PF
c) RCVF each record until I found the string containing to
line-label I
was looking for
d) You may also require the date-format ... search for
'DATFMT'
e) Extract the date-data, pass values back to the calling
program
It's a bit of a phaff I know, but the CL is simple enough; with a command
to
simplify the passing of the Job-Id and receiving the return-values, easy
to
incorporate it into other CL programs.
I can hear the purists screaming "API's" at me and I take your point if
it's
performance, but API's can be so much trickier to code, and whether the
GETJOBA command takes 1ms or 1s, it's usually not a hill of beans.
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 Jeff Crosby
Sent: 02 August 2012 13:43
To: Midrange Systems Technical Discussion
Subject: Re: Finding the job date of another job
RTVJOBA
On Wed, Aug 1, 2012 at 8:13 PM, Charles Sallee
<csallee@xxxxxxxxxxxxxxx>wrote:
I am trying to find a way in a CL to determine the job date of another
(a different) job from the one I am currently running. Any ideas?
Thanks,
Chuck Sallee
CIS Manager
Lexington Division of Police
csallee@xxxxxxxxxxxxxxx <mailto:csallee@xxxxxxxxxxxxxxx>
IBM i on Power - For when you can't afford to be out of business.
NOTICE: This electronic transmission is confidential and intended only
for the person(s) to whom it is addressed. If you have received this
transmission in error, please notify the sender by return e-mail and
destroy this message in its entirety (including all attachments).
P Please consider the environment before printing this e-mail.
--
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.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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.
--
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.
--
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.
--
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.
midrange.com
