RE: BRMS IFS save start and end times - IFS locks

Rob,

I'm not against changing joblogs to *PND.
But there are several items that first need to be addressed from a save/restore viewpoint and other existing processes that are checking/monitoring joblogs.

1) All BRMS saves would need a change/addition to include the below SQL you previously suggested.
<snip>
insert into My_custom_joblog_history_table (
select a.job_name, b.*
from table(qsys2.active_job_info()) a,
lateral (select * from table(qsys2.joblog_info(a.job_name)) x) b)

Any regular save can save a table.
</snip>

2) Maintaining " My_custom_joblog_history_table".
Does this table ever get purged or would it simply grow?
If not purged, it would be a log of every job that ever ran on the system,
Could be useful?

3) 3rd party products currently checking/monitoring joblogs would need enhancements to use the SQL/table.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, May 01, 2018 1:34 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS IFS save start and end times - IFS locks

Do you still have your joblogs go to spool files? If so you may want to
change that.

You could create a unique job description
CHGJOBD JOBD(...) LOGOUTPUT(*PND)
You could change the job schedule entry to use this new job description

Or do a SBMJOB
SBMJOB ... LOGOUTPUT(*PND)

Or when you're ready to leap past stone knives and bear skins
CHGSYSVAL SYSVAL(QLOGOUTPUT) VALUE(*PND)


Rob Berendt