|
What isn't working? The packed fields again? It works for me.--
CPYTOIMPF FROMFILE(MFCM) TOSTMF('/kevin/testpacked.txt')
MBROPT(*REPLACE)
FROMCCSID(37) STMFCCSID(*PCASCII) RCDDLM(*CR) DTAFMT(*FIXED)
FCUSER 10 A 85 94 LAST CHANGED USER
FCDATE 8 0 P 95 99 LAST CHANGED DATE
FCTIME 6 0 P 100 103 LAST CHANGED TIME
FCNTUS 10 A 104 113 LAST NOTE UPD USER
FCNTDT 8 0 P 114 118 LAST NOTE UPD DATE
FCNTTM 4 0 S 119 122 LAST NOTE UPD TIME
UISOURCE 1 A 123 123 ENTRY SOURCE
Comes out like this.
DIANNEH 20130225 125818 STACEY 20090812 1010
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Jay Vaughn
Sent: Monday, December 02, 2019 9:36 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: sftp from IBMi to remote server
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 surepacked
the
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
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
[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any
other party and is required to destroy the information after its
stated need has been fulfilled. If you are not the intended
recipient, or the employee of agent responsible to deliver it to the
intended recipient, you are hereby notified that any disclosure,
copying, distribution or action taken in reliance on the contents of
these documents is STRICTLY PROHIBITED. If you have received this
email in error, please notify the sender immediately to arrange for return or destruction of these documents.
--
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 mailing list archive is Copyright 1997-2024 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.