I have not made it work yet but I am convinced that the best way to handle 
sending files that use LF as the new line indicator to a system that 
understands CRLF as the new line indicator is to use a special translation 
table (Translate x'15' to x'25'). In the z/OS case I updated the 
ASCII-to-EBCDIC table. I simply have not been able to get FTP to read my 
special table yet.

Maybe someone has already created a translation table and had FTP use it. Here 
is what I did:

I found the translation source table used by IBM (TCPIP.SEZATCPX(STANDARD)) and 
copied to my library. There I made the following change:

000005 ; 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
 000006 ;
 000007   00 01 02 03 37 2D 2E 2F 16 05 25 0B 0C 0D 0E 0F    ; 00 ;
 000008 ; 10 11 12 13 3C 3D 32 26 18 19 3F 27 22 1D 35 1F    ; 10 ; std
 000009   10 11 12 13 3C 25 32 26 18 19 3F 27 22 1D 35 1F    ; 10 ; LF > CRLF
 000010 ;                           --

I then issued the following TSO command:

convxlat 'tssdon.amqp.source(ftpate)' AMQP.TCPSCBIN 

I looked at AMQP.TCPSCBIN and as far as I could tell it looked valid.

But when I tried:
EZA1736I  SITE XLATE=TSSDON.AMQP.TCPSCBIN                             
EZA1701I >>> SITE XLATE=TSSDON.AMQP.TCPSCBIN                          
200-Xlate parameter (TSSDON.AMQP.TCPSCBIN) is more than 8 characters. 

And when I tried:

ftp 192.86.33.123 -t amqp.tcpscbin

I get:

EZA1451E Cannot load translate table specified by TRANSLATE parameter 
amqp.tcpscbin

The -d parameter indicated:

CX0296 main: Exit with error: 14                        
PC0911 setClientRC: entered                             
PC0981 setClientRC: std_rc=00000, rc_type=CEC, rc=0014  
CZ1196 ftpQuit: entered                                 
CZ1268 ftpClose: entered                                
CZ1268 ftpClose: entered                                
CX0499 removeAff: entered                               

I tried all the variation of this dataset name I could think of (with quotes, 
without, upper case) and nothing changed. I am setting it aside for now and 
will create another listsrv thread for this problem. 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Reply via email to