RE: Copy source file member to pc -- MIDRANGE-L

To be clear, I agree that source brought down for use by PC utilities other
than software maintenance should lack the sequence and date fields. My
point was that, if you are bringing the source to the PC for maintenance and
other use by programs like rpgNextGen, some value may be lost when the
source is replaced on the i system. Although most installations that I have
encountered have change management systems, the ability to see what date a
certain change or block of changes was made has retained value.

I did not mean to imply that we need to muddy up ability to compare, et
cetera. (Though I do believe that Ultra Compare could handle that famously,
I would not do it either.)

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"April 1. This is the day upon which we are reminded of what we are on the
other three hundred sixty-four."
-- Mark Twain

Keeping source date in a copy brought down to the PC? Depends on what
you need. I regularly print source out of RDp, and I hardly ever print
source date or sequence numbers, although those are options.

For comparisons, the dates can make those unusable. Option 54 in SEU
doesn't deal with dates or sequence numbers - only the source. There
are
at least 2 kinds of compare tools - 3 with SoftLanding's - in WDSC, etc.
At least one includes date and sequence and is a joke. This has been
discussed in these lists before - long time ago now.

I don't personally see much use for dates and sequence when looking at
source on a PC - I can always go into RDp for that.

I'm pretty old-school, as well, and have reservations about using
source
stored in the IFS. OTOH, I'm told that change management works quite
well with those - diffs are kept that are dated, maybe that covers the
change-by-date issue, maybe even better.

JMNSHO
Vern

On 10/20/2010 4:23 AM, Dennis Lovelady wrote:

Maybe I'm old school. Certainly the PC has vastly superior tools for

source

comparison, printing and the like, but I think the loss of source

date is a

mistake. This is true especially but not exclusively for those
installations where there is no change management installed. For

that

reason I have developed my own set of source exchange utilities that

pull

source files to the IFS (and back again). It also optionally zips

and

optionally puts into a flat structure instead of lib/file/member.

But it

also maintains the sequence number / source date (also optionally),

and as

an added benefit, the date of the IFS file will match the date of the

last

change. I really designed it for exchange between my work and my

home

systems, but it could have other uses. (My not-ready-for-prime-time
makeRGPfree utility deals with both formats (with/without change

date.)

I hadn't thought about making SRCTOSTMF and STMFTOSRC shareable until

now,

but if others are interested....

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"We lived for days on nothing but food and water."
-- W.C. Fields

i am a little bit late on that topic but perhaps for the archives:

RPG Next Gen Editor has an Export Wizard which lets you export

source

members to your local PC. It has the following options:

- flat export (no directory structure)
- export with directory structure (lib/sourcefile/member)
- make file names lowercase
- put all sources in a zip archive

You will get just the source. No last changed date. No line numbers.
You can select multiple members from one or more source files and
libraries.

http://rpgnextgen.sf.net

Regards

Mihael

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Richard Reeve
Sent: Tuesday, October 19, 2010 4:48 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Copy source file member to pc

All,

I'm having a brain freeze - I know that I used to copy source

file

members
from the AS/400 to a pc but can't recall how I did it. I searched

the

archives
and googled but can't seem to find the answer.

Would one of you kind folks please refresh my memory?

Thanks so much.

Warmest Regards,

Richard Reeve

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.