RE: Log everything for a user

I've got a command exit point program I use which says if QSECOFR uses signoff then to ensure it does a *LIST, generate me a pdf, and shoot me a copy via email.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jeff Crosby
Sent: Thursday, May 23, 2019 11:49 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Log everything for a user

I've got a user who, on Sundays nights only, gets a lock on a particular file in his interactive job that does not get released. Later in his shift it causes an issue for a job he submits that needs exclusive access to that file. I can't figure out where that lock is coming from and not being released. He doesn't do anything different on Sunday than the rest of the week, yet this only happens on Sunday.

I want to capture the joblog from his interactive job. I changed his initial program to include a LOG(4 00 *SECLVL) LOGCLPGM(*YES) on him to capture what he's doing.

However, if he does a SIGNOFF *NOLIST I won't get the job log anyway. He signs off via menu option, but it could be one of several menus. So I either change the option on any menu he could sign off from, or I change the default on the SIGNOFF command for this weekend.

Some other easy way I haven't thought of?

Thanks.