Peter,
Our jobd for the compile is set to log 4 0 *nolist, if the compile is
good then no job log. But if it fails we get the job log and we always
delete it, no need to read the compile job log, since the compile source
listing is what we look at to see why it failed. So we want to not have
to delete the job log on a failure.
Jim
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Peter Dow (ML)
Sent: Tuesday, March 11, 2008 12:16
To: RPG programming on the AS400 / iSeries
Subject: Re: When a compile fails
Hi Jim,
I assume you're submitting your compilations to batch, right? Change
the association job description to have a logging level of LOG(4 0
*NOLIST). If the compile is successful, there will be no job log; if it
fails, you may want the job log, especially if it has a problem
resolving procedure names.
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /
Rubino, Jim wrote:
The system creates a job log along with the compile spool file. Is
there a way to stop the compile from producing the job log and only
produce the source compile spool file?
TIA
Jim Rubino
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
