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

The problem with both RDI and VScode when programming in CLP is prompting for CL commands relies on communicating back to the host to get the parameters etc, and then formulating up the display screen. To suggest that is painfully slow is being polite. Unfortunately I don’t see a way around that so we just either live with it, or use SEU instead. Another reason not to stop shipping SEU.


--
Jim Oberholtzer
Agile Technology Architects

On Oct 18, 2023, at 7:53 AM, Vern Hamberg via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

In RDi, there is some outline support for CLLE - variables, at lease, and also helpful. We don't usually have large CL source, and there is not a need for much more than variables.

Cheers
Vern

On 10/18/2023 5:09 AM, Åke Olsson wrote:

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.

--
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.