Re: how to always get joblog from interactive job

On 21-Nov-2014 11:54 -0600, Steve Richter wrote:

I want the joblog of my warehouse users to always print when they
signoff. I thought I could do that by setting their JOBD to
log(4 00 *seclvl). But I still do not get a joblog.

The design is such that the user, if allowed to effect their own sign-off request, should be able to decide if the logging is required. When the Work Management and application will control the actions of the user, then that individual control can be restricted.

Can I get an interactive job joblog using a parameter in the JOBD
they use when they logon?

The Routing Data (RTGDTA) parameter, effecting routing that could effect what is desired.

As it is, I will change the SIGNOFF command the user runs to SIGNOFF
LOG(*LIST). But even this is not ideal in that LOG(*LIST) overrides
the LOG(4 00 *NOLIST) setting of the job.

The Replace Command exit-point feature can enable supplanting a *NOLIST request.

What is the least intrusive way, in terms of not changing code or
affecting all the jobs on the system, of having a joblog printed
when a set of users SIGNOFF?

Most typically, an invocation of the Send Scope Message (QMHSNDSM) API to register a message with the *EXT scope\message-queue; the Scope Program would effect any necessary overrides and spooling [or whatever is the desired method of logging]. Placing the call in the processing of the Routing Program of the Routing Entries for the interactive subsystem(s) is usually a non-intrusive and comprehensive means to apply the desired effect for all\selected interactive jobs; filtering of jobs for which the effect applies, can be coded as part of the routing program itself [if for example all /warehouse users/ are not all restricted to a specific subsystem or routing(s).