× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Tue, 25 Jun 2019 at 10:49, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

Or, if you want to eliminate the sequence number once it's already
downloaded, that is perhaps even easier. There may be a way to create
an RDi macro to do this. (I can't remember if Buck Calabro has already
talked about this very thing.)

In days past, there was an Eclipse Foundation Incubator project called
Eclipse Monkey, which allowed one to write macros.
That project was archived due to lack of activity. As incredible as it
sounds, developers (us, you and I) aren't apparently interested in
scripting their IDE.

Today, the only real way to manipulate the RDi runtime environment is
via a plug-in. That's probably overkill for the subject. If I were
tasked with this, I'd write a pair of CLP/CMDs. One to 'Export without
SRCSEQ' and one to 'Import without SRCSEQ'. They would operate between
QRPGLESRC and the Bitbucket stream file. These would be your SVN
checkout/checkin commands - the things your SEU/PDM brethren would
use. Once written and working, you could map them into RDi user
actions, and they'd work exactly like they do in PDM. You could use
the Table (or PDM) view and operate on a number of source members at
once. If CL hasn't got enough power (no Bitbucket API interface) I'd
consider a Bash script, or Python. These can be called from a CMD/CLP
and are amazingly easy to use.

--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.