Out of curiosity, exactly where do you see the lowercase letter e? Is it on a separate line, or between the hex numbers on each line? Or are you referring to the file produced by CONVXLAT?
I tested it with TCIP.STANDARD.TCPXLBIN, and it looks ok on my system. I also ran CONVXLAT with the resulting file and it produced an identical binary table. Bill On Mon, 24 Feb 2014 15:10:06 +0200, Gadi wrote: >It's not perfect (I see the lowercase letter e between the entries), but it's >something I can work with. >Thanks. >Gadi > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Bill Godfrey >Sent: Monday, February 24, 2014 12:26 PM >To: [email protected] >Subject: Re: Convert Tcp/IP translate tables from binary to source > >On Mon, 24 Feb 2014 09:06:11 +0200, Gadi wrote: > >>Hi, >> >>I need to convert a customized binary version of a TCP/IP translation table >>to the source version. >> >>Is there a way to do this? >> >>I know that the CONVXLAT program will do the reverse. >> >>Thanks >> >>Gadi > >If it is an SBCS table named prefix.WHATEVER.TCPXLBIN: > >(from ISPF 6 or TSO READY) > >oput whatever.tcpxlbin 'xlbin_2' binary >omvs >od -An -tx1 -j256 xlbin_2 | tr -s ' ' >tcpx_2 >exit >oget 'tcpx_2' tcpx2 > >(there is a space between the 2 quotes after tr -s) > >(cleanup: in omvs remove xlbin_2 and tcpx_2) > >The sequential data set tcpx2 will contain source suitable for CONVXLAT. > >There will be a blank line at the end of tcpx2, but it is harmless. > >Bill ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
