RE: Exit Point When Opening a Source Member with RDP ?

Not sure if you're poking holes in my strategy or offering assistance ?

More clarity please :-)

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

------------------------------

message: 5
date: Tue, 22 Jan 2013 13:44:11 -0500
from: Buck Calabro <kc2hiz@xxxxxxxxx>
subject: Re: Exit Point When Opening a Source Member with RDP ?

On 1/19/2013 10:49 AM, Richard Schoen wrote:

I wrote an EDTF wrapper as well, so that's covered. Anything else I missed ?

Looks like you've moved from handling your own developers' habits to a
more generic question of how many ways can source be edited on the i.

If you were to hire me to help for a week or two, I'd bring my laptop
with a copy of Notepad++ on it. No licence issues with my RDP on your
IBM i, etc. I have a script that uses FTP to download a source member
to my laptop, invoke Notepad++ and then FTP it back up to your machine.

In a pinch, QSH and sed can also be used to, er, modify source.
sed s/TESTLIB/PRODLIB/ </qsys.lib/buck.lib/qrpglesrc.file/sed.mbr

/qsys.lib/buck.lib/qrpglesrc.file/sed1.mbr Let's say you had a pile of

these things you wanted to do. Instead of manually editing each one,
wrap the lot in a QSH script file and automate the process. Of course,
something similar could be done with a simple RPG program and a CL wrapper.
--buck