Re: How to identify source members still "locked" open by SEU sessions whose interactive jobs were ended

What's your definition of "locked"? If it's locked like Ake thought then
I'd suggest his solution. Or the JOB_LOCK_INFO, or look for any jobs, SEU
or client/server based, which may have a lock on his user profile with
ACTIVE_JOB_INFO table focusing on CURRENT_USER_LIST_FILTER.

Now, if you want to find what source members were modified in the last
duration you can easily do that with a few methods like

select
SOURCE_TYPE, SYSTEM_TABLE_SCHEMA, SYSTEM_TABLE_NAME, SYSTEM_TABLE_MEMBER
from qsys2.syspartitionstat
where LAST_SOURCE_UPDATE_TIMESTAMP > *current timestamp* - *30* *days*
order by last_source_update_timestamp desc

There's probably a service to analyze journals to tell you what they've
changed.

If you use stream files in the ifs to store your source there's ways to
tell you recently changed stream files.

There are services you can use to examine OPM or ILE programs to see their
last source changed dates and see if the source change dates are newer then
these indicating a work in progress. For example, an ILE RPG program is
composed of 1 or more modules. Each module has a source date. See DSPPGM
PGM(ROB/AAA) DETAIL(*MODULE) and option 5. There are services which will
retrieve that and you can compare that to other services (like the one
listed at the top) to see if the dates differ.

If you are using a change management system you can see what is 'checked
out'

IFS has the CHKOUT and CHKIN commands.

On Tue, Oct 17, 2023 at 5:38 PM Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:

Scenario:
Developer has a source member open for edit using SEU and the interactive
job gets ended via time out. Developer gets sidetracked for a week or more
and loses track of what he was working on before.

Or maybe someone quit or was fired on the spot...


*** CONFIDENTIALITY NOTICE: The information contained in this
communication may be confidential, and is intended only for the use of the
recipients named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please return
it to the sender immediately and delete the original message and any copy
of it from your computer system. If you have any questions concerning this
message, please contact the sender. ***
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.