TranslateException RC=4, Reason=12

Discussion of Co:Z sftp, a port of OpenSSH sftp for z/OS
Post Reply
the1nfamous
Posts: 9
Joined: Wed May 21, 2014 4:19 am

TranslateException RC=4, Reason=12

Post by the1nfamous »

Hi,

I am attempting to convert an existing FTP to COZSFTP. The existing FTP pulls a file from an AIX box with native CP of UTF-8 to a mainframe with native CP of IBM-285. The existing FTP issues a:

LOCSITE SBDATACONN=(IBM-285,UTF-8).

File comes out fine. Attribs of mainframe file are LRECL=206 BLKSIZE=27810,RECFM=FB although equally successful with LRECL=256 BLKSIZE=27966,RECFM=VB.

For COZSFTP I have coded:

lzopts mode=text,servercp=UTF-8,clientcp=ibm-285

job fails and issues the following:

.12.990. debug3: Sent message SSH2_FXP_OPEN I:6 P:/var/opt/tuxapp/uat2/pomi/POMI0030_20161113_Register_Transfer_Corporate_0015.txt
ZosDataset.I.: Opening dataset ORY7.JI.LR.BDK.POMI0030.JIDR010.INTEXT.E0015 for write with options: old
.13.227. debug3: Request range 0 -> 32767 (0/1)
.13.229. debug3: Received reply T:103 I:7 R:1
.13.229. debug3: Received data 0 -> 15761
ZosDataset.E.: TranslateException: Exception occurred during translation, RC=4,Reason=12
.13.230. debug3: Short data block, re-requesting 15762 -> 32767 ( 1)
.13.231. debug3: Received reply T:101 I:8 R:0
.13.231. Couldn't write to "//ORY7.JI.LR.BDK.POMI0030.JIDR010.INTEXT.E0015": EDC5122I Input/output error.
(errno2=0xC9250001)

Of course, unless writing to cart/tape the max blksize of a DASD based DSN is 32760... so a request of 32767 will fail...

If I try with a different servercp, such as ISO8859-1, I receive the file, however instead of receiving spaces in the file with hex value 40, I get them with hex value 41, which screws the program that tries to process the file.. the attribs in this scenario are back to the usual LRECL=206 BLKSIZE=27810,RECFM=FB although equally successful with LRECL=256 BLKSIZE=27966,RECFM=VB as per the original FTP. If I specify no attribs at all then DSN is created with RECFM=U / LRECL=0 / BLKSIZE=6144, and above error msg is received again...

Any help greatly appreciated...
Post Reply