Peter, The program first searches for a customized table that you have built. If the program fails to find one of the customized tables, it uses the default table supplied in hlq.STANDARD.TCPXLBIN.
The following link explains the hierarchy of the translation tables used SBCS hierarchy http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/A.1 DBCS hierarchy http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/A.4 Thanks, Kolusu IBM Mainframe Discussion List <[email protected]> wrote on 03/09/2016 07:55:34 AM: > From: Peter Ten Eyck <[email protected]> > To: [email protected] > Date: 03/09/2016 07:55 AM > Subject: Default translation table > Sent by: IBM Mainframe Discussion List <[email protected]> > > Does anyone know why an ftp would be using the default translation > table TCPIP.STANDARD.TCPXLBIN when DATASETPREFIX SYS1.TCPIP is > specified in the TCPIP and RESOLVER parms? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
