cpytoimpf is not working... nor did it work before when we tried it...

using parms

mbropt(*replace)
fromccsid(37) - if we don't, the result looks EBCDIC? symbols - no clear
text
stmfcodpag(*pcascii)
rcddlm(*cr) - required with dtafmt(*fixed)
dtafmt(*fixed)

any suggestions on what is missing?

jay

On Mon, Dec 2, 2019 at 10:14 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

thats funny - i actually started with your suggestion but was not
achieving the correct formatted stmf result.(probably didn't have the
cpytoimpf parms just right).
Consulted with a couple of vets at my company and they suggested the cpyf
method.

got it - i guess i'll need to play with the correct parms in cpytoimpf to
achieve this correctly.

thanks John



On Mon, Dec 2, 2019 at 10:08 AM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

So what is the solution to do a cpyf to a flat text to be sure the
packed
are going to be clear text in the flat text file?

The solution is to not use CPYF at all. The whole point of CPYTOIMPF
is to copy data from a PF into either a flat file or stream file. In
this case, you would go straight to 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@xxxxxxxxxxxx for any subscription related
questions.

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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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