Re: Using CPYTOIMPF to copy a source member to the IFS does not copy fields SRCSEQ and SRCDAT

Journals? :-)


--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno mer 28 apr 2021 alle ore 14:25 a4g atl <a4ginatl2@xxxxxxxxx> ha
scritto:

For the moment, I work in an environment that does not believe in mod
markers and so I have to rely on the date to find what others have
changed.So I simply want a copy that can go back and see what changed.

On Wed, Apr 28, 2021 at 8:18 AM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

Not sure if you plan to move this source into a Git repository, but the
SRCTOGIT command that's part of the iForgit client I'm offering allows

you

to keep line numbers and date sequences and manage those as part of your
Git repo for use with RDI or SEU. http://www.iforgit.com

In general I personally try not to use the source dates and sequences any
more when I can rely on a good diff view of previous changes.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx

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

message: 4
date: Tue, 27 Apr 2021 18:10:00 -0400
from: a4g atl <a4ginatl2@xxxxxxxxx>
subject: Re: Using CPYTOIMPF to copy a source member to the IFS does
not copy fields SRCSEQ and SRCDAT

Jon, its for a backup. It is for source that will not be backed up. I am
also experimenting moving source to the IFS where we do backup the

folders.

Darryl.

On Mon, Apr 26, 2021 at 6:35 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

Why do you want all of it Daryl? It won't be maintained if the source
remains in the IFS. If just for backup then a save file would make
more sense.

On Apr 26, 2021, at 3:48 PM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:

Thanks all. I used RDi to copy and it gave me all the fields.

I would have preferred a method using the commands, It looks like I
need

to

write some code to get what I need using commands.

Darryl.

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

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com