|
On Oct 19, 2023, at 8:30 AM, Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Vern,
We have a situation now where a developer is using VS Code, but it doesn’t "lock" the source member as in use. I was able to open it in RDi, but then (thankfully) RDi says something like "the object on the source system has changed".
Is there a setting in VS Code we are missing?
Greg
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Vern Hamberg via MIDRANGE-L
Sent: Tuesday, October 17, 2023 11:17 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Subject: Re: How to identify source members still "locked" open by SEU sessions whose interactive jobs were ended
Allow me to suggest a free alternative - VS Code for IBM i. You can go
to this -
https://marketplace.visualstudio.com/items?itemName=HalcyonTechLtd.code-for-ibmi
and find links to tutorials and all.
Cheers
Vern
On 10/17/2023 9:05 PM, Gavin Inman wrote:
SEU still has it's place for smaller programs that only require a
quick edit.
and besides, some people don't want to incur the extra cost, and the
pain and suffering of passport Advantage to get RDI.
Gavin.
On 10/17/2023 9:48 PM, Jack Woehr via MIDRANGE-L wrote:
On Tue, Oct 17, 2023 at 3:38 PM Dan Bale<dan.bale@xxxxxxxxxxxxxxxxxxxxx>
wrote:
Scenario:If they're still developing in SEU, they *should* be fired on the spot
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...
... 😁
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.