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

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.

On Mon, Apr 26, 2021 at 3:10 PM Rob Berendt <rob@xxxxxxxxx> wrote:

My suggestion would be to open the source file with RDi and save it to a
stream file (or on the end point you wanted it).

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
John Yeung
Sent: Monday, April 26, 2021 3:02 PM
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxxxxxxxx>

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

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


On Mon, Apr 26, 2021 at 2:35 PM a4g atl <a4ginatl2@xxxxxxxxx> wrote:

Thought this would be simple....

How do I copy a source member to the IFS or a network drive?

I tried using CPYTOIMPF and CPYTOSTMF and get the data but the 2 fields
SRSEQ and SRCDAT (sequence number and date) do not get copied to the

IFS.

What am I doing wrong?

Some would probably argue what you're doing wrong is caring about
SRCSEQ and SRCDAT.

I am guessing there are two main approaches for dealing with this if
you do want all the fields.

First, older school way: Dump the source member into a data (not
source!) PF with a single field big enough to hold all three source
fields, using FMTOPT(*NOCHK). Then use whatever means you like to copy
the data PF to a stream file.

Second, newer and perhaps cleaner-feeling way: Use SQL to treat the
source file as any other PF with three fields.

I can't give you "best" specifics for the second approach. There is
probably some built-in stream file stuff already available in SQL. For
me personally, I would reach for Python here, slurping up the source
with SQL and writing out a stream file.

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

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