Re: OpenSSH: How to Stop SSH from Creating Thousands of Job Logs - N1015450

On 30-Jan-2015 12:42 -0600, Steinmetz, Paul wrote:

Every time we call QSH, as a client, 3 jobs with 3 empty job logs
are created.
I would like to turn these off.

QPJOBLOG PAULS QEZJOBLOG QP0ZSPWP RDY 1
QPJOBLOG PAULS QEZJOBLOG QZSHSH RDY 1
QPJOBLOG PAULS QEZJOBLOG QP0ZSPWP RDY 1

I reviewed the link/doc below, however, all our SSH jobs run under
the job user that called them and the jobd of that user, so I'm not
sure if this doc applies.

That doc seems to imply the use of special-purpose user profiles that perform the SSH, such that each could be changed to use the one *JOBD named SSHJOBD with the desired logging; thus also easily allowing activation of all SSH job logging by changing just that one Job Description. So unless the intention is to replace the current SSH by the typical /user/ rather than having an alternate SSH-specific user, then the CHGJOBD LOG(0 0 *NOLIST) LOGCLPGM(*NO) against the JOBDs of those typical users is likely an undesirable choice.

I was able to turn off the 3 joblogs by changing PAULS jobd, but
this is really not an option.

Any other tricks or suggestions.

<<SNIP>>

<http://www.ibm.com/support/docview.wss?uid=nas8N1015450>

FWiW: I have a program that I call [that I named CLR] to clear my external (*EXT) message queue and [optionally] also clear those joblogs; i.e. I reactively purge rather than prevent their occurrence:

dltsplf *select select(&usr *n *n QP0ZSPWP)
dltsplf *select select(&usr *n *n QZSHSH )

There are no MONMSG for each of those Delete Spooled File command requests, because the msg CPC3305 is the effect [a completion] stating that zero to however many spool files were deleted by the specified selection. The final command request in that program eliminates those completion messages:

rmvmsg pgmq(*same (*)) msgq(*pgmq) clear(*all) rmvexcp(*no)