View Job Log of Completed Job

[Chad]

Is there a way to view a job log of jobs that have ended/completed? I
can use the DSPLOG command and see where a job started and ended.
Example:

CPC1236 00 COMPLETION Job 104683/CONS/LDRTEINF submitted for job
schedule entry LDRTEINF number 000028.
QJOBSCD QSYS 104405
02/21/11 04:51:00.579832

CPF1124 00 INFO Job 104683/CONS/LDRTEINF started on 02/21/11
at 04:51:00 in subsystem QBASE in QSYS. Job entered system on 02/21/11
at
04:51:00.

X
LDRTEINF CONS 104683
02/21/11 04:51:00.693640
SSP0305 00 INFO PROCEDURE
NAME=LDRTEINF
LDRTEINF CONS 104683
02/21/11 04:51:00.705744
CPF1164 00 COMPLETION Job 104683/CONS/LDRTEINF ended on 02/21/11
at 04:51:00; 1 seconds used; end code 0

but I would like to be able to see detail of the job 104683/CONS/
LDRTEINF.

Thanks,
Chad

[iseriesflorida]

Try wrkjob ldrteinf

[Chad]

I get the same thing when I try DSPJOBLOG, with the reason - The job
has completed.

[iseriesflorida]

> has completed.- Hide quoted text -
>
> - Show quoted text -

Wrong command use the wrkjob command.

[ken]

wrkusrjob ldrteinf (there may be many status=OUTQ in the list, find
the job based on date and time) and look in the ended job's spool file
for the file QPDSPJOB (although it will probably be in status=FIN).
This seems to work only for submitted jobs though and the spool file
will be named QPJOBLOG.

If you need a job log for a successfully ended interactive job you
might need to temporarily change job logging levels for a given user
or job etc.

[Dr.Ugo Gagliardelli]

il 22.02.2011 18.45, Scrive Chad 65172256:

> On Feb 22, 12:30 pm, iseriesflorida<iseriesflor...@yahoo.com> wrote:
>> On Feb 22, 12:15 pm, Chad<chadwhit...@gmail.com> wrote:
>>
>>
>>
>>> Is there a way to view a job log of jobs that have ended/completed? I
>>> can use the DSPLOG command and see where a job started and ended.
>>> Example:

[...]

> I get the same thing when I try DSPJOBLOG, with the reason - The job
> has completed.

When a job completed, you can see its log only if the job is in a status
of OUTQ or JOBLOGPENDING. In the 1st case using WRKJOB command you can
use option 4 and try to see whether a QPJOBLOG spooled file is present
or not. In the 2nd case you can still see the joblog even with DSPJOBLOG
command.

--
Dr. Ugo Gagliardelli, Modena, Italy
Spaccamaroni andate a cagare/Spammers not welcome

[CRPence]

On 2/22/11 9:15 AM, Chad wrote:
> Is there a way to view a job log of jobs that have ended/completed?
> I can use the DSPLOG command and see where a job started and ended.
> Example:
>
> CPC1236 00 COMPLETION Job 104683/CONS/LDRTEINF submitted for job
> schedule entry LDRTEINF number 000028.
> QJOBSCD QSYS 104405 02/21/11 04:51:00.579832
> CPF1124 00 INFO Job 104683/CONS/LDRTEINF started on 02/21/11
> at 04:51:00 in subsystem QBASE in QSYS. Job entered system on 02/21/11
> at 04:51:00.

> LDRTEINF CONS 104683 02/21/11 04:51:00.693640
> SSP0305 00 INFO PROCEDURE NAME=LDRTEINF
> LDRTEINF CONS 104683 02/21/11 04:51:00.705744
> CPF1164 00 COMPLETION Job 104683/CONS/LDRTEINF ended on 02/21/11
> at 04:51:00; 1 seconds used; end code 0
>
> but I would like to be able to see detail of the job
> 104683/CONS/LDRTEINF.
>

If the error "job not found" occurs for the following request, then
the joblog is not available; only auditing, history, and any other
output produced by the programs that had run in that job might be
available still:
WRKJOB 104683/CONS/LDRTEINF

The joblog may not be available for a job that completed normally,
because default logging of *NOLIST asks that the OS not produce the
spooled file QPJOBLOG as listing of the job message queue for a job that
completes normally; i.e. only a job ending abnormally should produce the
QPJOBLOG spooled listing with the *NOLIST logging specified.

If the job should always produce the listing, then either the job
should issue a DSPJOBLOG request inline to [at the end of] its
processing, or the job should be defined or revised [e.g. CHGJOBD or
CHGJOB] to request the listing should be produced for the desired level
of message logging after the job completes. The job schedule entry
should be defined, perhaps available only via the specified *JOBD, such
that the joblog should be maintained even when the job completes
normally. Specifying LOG(4 0 *SECLVL) is one example, optionally also
LOGCLPGM(*YES) to log the CL requests within a CLP where the CLP allows
logging.

Note that the SPLFACN() setting for the job may play a role as well,
in how the spooled listing is made available [to DSPSPLF and WRKJOB];
SPLFACN(*KEEP) along with the logging level other than *NOLIST will
ensure the joblog listing should be produced, and will remain as long as
the SPLF is not printed or deleted.

Regards, Chuck