See EZY2640I in your FTP log. Ours:
EZY2640I Using 'TCPIP.FTP.DATA' for local site configuration parameters.
You will want to investigate the SBDATACONN setting.
We encountered translation issues using the default translation table
(TCPIP.STANDARD.TCPXLBIN) that gave a mu in the translated text for a
vertical line (used in formatting comments in code). We ended up
using CONVXLAT to provide a better table for EBCDIC to ASCII
translation, Our JCL:
/SYSTSPRT DD SYSOUT=*
/SYSPRINT DD SYSOUT=*
/SYSIN DD DUMMY
/SYSTSIN DD *
onvxlat 'TCPIP.SEZATCPX(EUS)' +
'TCPIP.eus.tcpxlbin'
*
And in the FTP processing statements include:
LOCSITE SBDataconn=TCPIP.eus.tcpxlbin
to override the FTP default table.
Hope that helps.
Michael
At 03:36 PM 4/4/2024, Radoslaw Skorupka wrote:
Content-Transfer-Encoding: 7bit
Scenario:
ftp client (Windows or Linux) is connecting to z/OS based FTP server.
The user has TSO segment and obviously OMVS one. =>
userid.DATASETS.EXIST and /u/userid/home/exists
I can change translation table, I can use RC file to issue some
commands including SBDATACONN.
However I wanted to use default translation table. I have read
several manuals and I'm still lost.
I have found several (many!) different "translation table
hierarchies", varying depending on various factors. But still don't
know how the hierarchy works. Is it first catch rule or rather last entry wins?
That's important because I want to use different tables for
different users and cannot change server's settings (which are not
specified AFAIK).
Any clue?
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
