Re: How to identify source members still "locked" open by SEU

First locks are easily identified using QSYS2/OBJ_LOCK. In this case you are
looking for member locks.

If I for instance have a library "BGCONV" with a bunch of source files where
names (as per usual) begin with "Q" the SQL statement would look something
like this:

SELECT SYSTEM_OBJECT_SCHEMA, SYSTEM_OBJECT_NAME,
SYSTEM_TABLE_MEMBER, OBJECT_TYPE, MEMBER_LOCK_TYPE, LOCK_STATE,
LOCK_STATUS, LOCK_SCOPE, JOB_NAME FROM QSYS2/OBJ_LOCK WHERE
OBJECT_SCHEMA = 'BGCONV' and MEMBER_LOCK_TYPE = 'MEMBER'

And would give the following result set (assuming one member is locked):

System System System Object Member Lock Lock
Lock Job
Object Object Table Type Lock State Status
Scope Name
Schema Name Member Type

BGCONV QRPGLESRC BG_IBAN *FILE MEMBER *SHRRD HELD
JOB 591437/AO/QPADEV0005
******** End of data ********

Then regarding SEU vs RDI. I have found that for any RPGLE programming RDI
is worth whatever it costs. It saves so much time. The outline feature
where you can navigate through all definitions helps a lot. Also compiling
without exiting the editor and easy access to the error listing. It is
simply such a productivity boost!

When it comes to CL I do not feel that I am helped as much by RDI. There
could be a place for SEU there. I guess.