ok, actually it is not the cpytoimpf...

just before we do the cpytoimpf, we create a flat text file with one field
the same length as the record length of the file we are wanting to sftp.
then do a simple cpyf of the file we want to sftp into the flat text file.
If that from file has packed fields, they come across to the flat text file
as non-readable (non clear text) data.
and it is that flat text file that is moved to the ifs with a cpytoimpf to
sftp away.

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?


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

so discovered that the fields that are not converting to clear text ASCII
in my cpytoimpf are packed fields.

Does anyone know what the correct parms are to handle packed fields with


On Wed, Nov 27, 2019 at 4:22 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Jerry,

Am 26.11.2019 um 22:11 schrieb Jerry Draper <midrangel@xxxxxxxxxxxxx>:

I know that the private key needs to be secured but with an ssh key
exchange connection the partner needs your public key in their
authorized_keys file and the partner's RSA fingerprint needs to be in your
known_hosts file.

Yes but the entry in authorized_keys is usually not further restricted.
You can restrict there to certain commands and source IP addresses, though.

The fingerprint just prevents tampering if the remote system pretends to
be someone else. If a possible attacker got hold of the privkey, he needs
just to connect, accept the host fingerprint.

Given that probably any system is breakable the ssh key exchange offers
a pretty good solution.

Yes, it does, most preferably to passwords. I'm just pointing out that
even with keys is a chance to have a system becoming compromised.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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

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