CPYTOIMPF is still broken at V5R4

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hopefully, this will save someone a little aggravation...

Contrary to the help text, CPYTOIMPF ignores the input file CCSID when
the field CCSID is 65535. You get a field like that when you use a
"flat" file (one created with CRTPF RCDLEN(xxx). The official
work-around is to create your file with SQL, specifying a CCSID value
for a single field with a length equal to the length of the file. When
the CCSID of the field is not 65535, the input file CCSID value is
ignored, and the value for the field is used.

You can achieve the same result by using CRTPF with a DDS source member
containing a single field.

IBM is aware of the problem, and will fix it in a future release. There
will be no PTF for V5R4. See APAR SE28511 for a complete description of
the work-around.

- --

Pete Hall
pbhall@xxxxxxxxxxxxx
http://pbhall.us
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGCwTrpcZsDl8OX6kRAi3OAJ9Mu7IVzWZ0b2ZlqMeMrXUCyhxXkACgwA1O
+HgHfu1RjjVOVJs6EP38LNE=
=JvWY
-----END PGP SIGNATURE-----