Re: Upgraded to V5R4 and joblogs for normal completed jobs are now being produced

Jim,

In the "Memo to Users" for V5R4 there is a note about a change in the way
the system manages the job log. Check this:

******************************

*Job log pending status more common in V5R4 *

* *

Starting in V5R4, it will be much more common to have jobs that have a
status of job log pending. In previous releases, this status was usually a
result of a Power Down System (PWRDWNSYS) command. The *Job log output
*(LOGOUTPUT)
job attribute now determines how a job log is written. A completed job that
has a job log pending has a job state of OUTQ even though the job might
currently have no spooled files associated with it.



In previous releases, job logs were written by the SCPF job. In V5R4, the
SCPF job no longer writes job logs; instead, they are written by job log
server jobs. See the Start Job Log Server (STRLOGSVR) command information
for details.



The shipped default for system value QLOGOUTPUT is *JOBEND, but the
recommended value for QLOGOUTPUT is *JOBLOGSVR. Applications that require
job logs to be produced when the job completes its activity should specify
LOGOUTPUT(*JOBEND) in the job description or on the Submit Job (SBMJOB) CL
command. You might need to create additional job descriptions so that
different applications can easily get different job attributes.



The procedures you use to manage and remove old job logs might need to be
changed to handle the pending job log status. In previous releases, if a job
had a status of job log pending, a job log would eventually be written.
Starting in V5R4, a job log can remain in pending status indefinitely. If
you use Operational Assistant to remove old job logs, pending job logs will
now also be removed. See the Change Cleanup (CHGCLNUP) command for
information on how to set the number of days that job logs should be
retained. If you do not use Operational Assistant, you need to add the
cleanup of pending job logs to your normal cleanup procedures. See the
Remove Pending Job Log (QWTRMVJL) API and the Add Job Schedule Entry
(ADDJOBSCDE) command for more information. You can use the Display Job
Tables (DSPJOBTBL) command to see if your clean up is working. You can also
use the Work with Job Logs (WRKJOBLOG) command to help manage both pending
and spooled job logs
******************************

Hope this helps.

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries



On Fri, Oct 16, 2009 at 9:23 AM, Rubino, Jim <Jim.Rubino@xxxxxxxx> wrote:

The signoff command is still set to *nolist and all of our users jobd
are set like this:
Message logging:
Level . . . . . . . . . . . . 4 0-4, *SAME
Severity . . . . . . . . . . . 00 0-99, *SAME
Text . . . . . . . . . . . . . *NOLIST *SAME, *MSG, *SECLVL,
*NOLIST
Log CL program commands . . . . *NO *SAME, *NO, *YES

I looked into the spooled file loblog and the job logs that are getting
created are from the user being signed on and the system timing them out
for inactivity and then the system ending their job.

Is there a way to NOT have a loblog for when this happens?

TIA
Jim



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
Sent: Friday, October 16, 2009 8:29 AM
To: Midrange Systems Technical Discussion
Subject: Re: Upgraded to V5R4 and joblogs for normal completed jobs
arenow being produced

Don't forget to look if the user is closing the client access session
without doing a sign off.. This will cause a joblog, because the session

ends in error.



From:
CRPence <CRPbottle@xxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
10/15/2009 05:09 PM
Subject:
Re: Upgraded to V5R4 and joblogs for normal completed jobs are now being

produced
Sent by:
<midrange-l-bounces@xxxxxxxxxxxx>



Rubino, Jim wrote:

What did the upgrade change to cause user when they sign off at
the end of the day to have joblogs produced, whereas on the
previous release (V5R3) did not? Is there a system setting or
user profile setting or jobd setting?

Any help will be greatly appreciated.

How the user signs off from an interactive session is what
determines whether a joblog is produced. So neither a *JOBD nor an
attribute of the *USRPRF apply, and the effective system setting is
the LOG() parameter of QSYS/SIGNOFF; i.e. there is no LOG(*JOBD),
LOG(*USRPRF), nor LOG(*SYSVAL) available on the QSYS/SIGNOFF command
used to sign off from the interactive session. The default behavior
was unchanged from prior releases; i.e. was, and remains, LOG(*NOLIST)

Review one of the joblogs and determine the last command issued.
If the last command was an unqualified SIGNOFF with no parameter
specifications, then investigate the LOG() parameter default on all
of the SIGNOFF commands; e.g. see result of ?ALTQSYS/SIGNOFF. If
the last request was a custom command such as unqualified LOGOFF,
then investigate each command definition by that name using DSPCMD &
review of parameter [defaults] by prompting; determine if any of its
parameter defaults or the CPP [command processing program] might be
effecting LOG(*YES) on its qualified invocation of QSYS/SIGNOFF.

Regards, Chuck
--
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.