On 24 Jan 2013 11:24, rob@xxxxxxxxx wrote:
on GDIHQ (our 'db2' lpar), I ran this:
md '/testexport'
edtf '/testexport/test.txt'
....+....1....+....2....+....3....+....4....+
************Beginning of data**************
This is a test
************End of Data********************
STRNFSSVR SERVER(*ALL)
The file was created with
Coded character set ID . . . . . . . . : 37
On MAIL1 (a 'Domino' lpar), I ran this:
md '/gdihqmount'
MOUNT TYPE(*NFS) MFS('gdihq:/testexport') MNTOVRDIR('/gdihqmount')
File system mounted.
dspf '/gdihqmount/test.txt'
But it looked like hieroglyphics to me.
....+....1....+....2....+....3....+....4....
************Beginning of data**************
êëó@ëó@ü@úàóú
%
************End of Data********************
The docs say the ADDMFS [or MOUNT] command defaults to treating the
files as Binary rather than text. Seems maybe you need to "Specify a
CCSID to be assumed for data files on the remote system."?
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/cl/mount.htm
_i Add Mounted FS (MOUNT) i_
"...
Coded character set ID (CCSID)
Specifies, for Network File Systems, a pair of coded character set
identifiers (CCSIDs) to identify a specific character representation to
be used. The first CCSID specifies what encoding scheme should be
assumed for data files on the remote system. The second CCSID specifies
what encoding scheme should be assumed for path names on the remote system.
This parameter is only valid if mounting a Network File System.
Element 1: Data file CCSID
*BINARY
No conversion is used.
*ASCII
The ASCII equivalent of the default job CCSID associated with the
current job is used.
*JOBCCSID
The CCSID from the default job CCSID is used.
1-65533
Specify a CCSID to be assumed for data files on the remote system.
..."
