|
Hi Peter, I see there are a bunch of 0037* TCPXLBIN files
on TCPMAINT 592 disk. Hmm, which one to use ? I just checked my printout and
there are 18 characters not printing properly using the CANADIAN TCPXLBIN. I
created the following FRENCH EXEC at one time to put all the French characters
in a CMS file. I wish I remember how and why I did it (maybe to test FTP). /*
*/
Trace
Address
Command
Chars =
'42434445464748495152535455565758626364656667686971727374757677788D9C9EADCBCCCDCECFDBDCDDDEDF'x
Chars =
Chars||'FBFCFDFE'x
Do I = 1 to
Length(Chars)
Record.I =
Copies(Substr(Chars,I,1),10)
End
Record.0 =
Length(Chars)
'PIPE Stem Record. | Pad 80 | > FRENCH
FILE A F 80' I’ve transferred the output file to
my PC. Prints OK there. Have to look at the binary for this file but can’t
remember how to. I mostly use TEXTPAD on my PC. More investigating… Mike From:
Hi Mike, You use the PPS command instead of
PRINT. Though once you have translation set up to your liking you might be able
to go back to using PRINT. You will find the TCPIP translate tables on TCPMAINT
592. You make a new default by copying to TCPMAINT 198 and renaming it
appropriately. For FTP only, we use 00370819 TCPXLBIN renamed as SRVRFTP
TCPXLBIN instead of the standard translate table. Your TN3270 session does not
use the VM TCPIP translate tables, it uses the Attachmate translate tables (By
looking in your Attachmate configuration panels, you may get a hint which
translate tables on VM you should use). Peter -----Original
Message----- Peter, Thanks
for the info. Now to try to find out where this default TCPIP translate table
is. I see the PPS command has the ‘TCPXLBIN’ and the
‘TRANS’ option but not the PRINT command. Also, since I am
connected to zVM through a telnet session and I see the French characters on my
PC screen (running Attachmate myEXTRA! Regards Mike
From:
You need
to change the translation tables used to translate from EBCDIC to ASCII. A
quick look at the RSCS Program Directory does not reveal how to change the
default, but you can use the PPS command with the TCPXLBIN option to experiment
with translation tables. You might want to consider changing the default TCPIP
translate table to the table you find works best. The RSCS exit may be using
the default TCPIP translate table. -----Original
Message----- Greetings, Just getting involved in using RSCS
TCP/IP LPR functionality. My client is trying to print a file (using the CMS
PRINT command) that contains French Canadian characters. The printer is defined to RSCS as LINKDEFINE IPPLAS TYPE LPR FORM *
AST
PARM IPPLAS EXIT=LPRXONE ITO=0
TCP=TCPIP USER=Y PRINTER=RAW # SECURE=NO HOST=172.16.92.97
SYS=Y
# EP='S=N FF=N C=LPR CONV=Y
SUFFIX=1B45' I have the following in RSCS PROFILE
GCS file : 'FILEDEF CONFIG DISK RSCS CONFIG
*' 'FILEDEF LPR DISK LPR CONFIG
*'
'FILEDEF LPRP DISK LPRP CONFIG
*' 'FILEDEF LPRXFORM DISK LPRXFORM
CONFIG *' 'FILEDEF LPD DISK RSCSLPD CONFIG
*' The LPR CONFIG file is the sample
one (LPREXITS Sample Configuration File). If I transfer the file to my PC and
print it out from there it prints OK so I know the printer can handle the
characters. I would appreciate some guidance. Thanks Mike Horlick CGI The information
transmitted is intended only for the person or entity to which it is addressed
and may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of or taking of any action in
reliance upon, this information by persons or entities other than the intended
recipient or delegate is strictly prohibited. If you received this in error,
please contact the sender and delete the material from any computer. The
integrity and security of this message cannot by guaranteed on the Internet.
The Sender accepts no liability for the content of this e-mail, or for the
consequences of any actions taken on basis of the information provided. The
recipient should check this e-mail and any attachments for the presence of
viruses. The sender accepts no liability for any damage caused by any virus transmitted
by this e-mail. This disclaimer is the property of the TTC and must not be
altered or circumvented in any manner. The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of or taking
of any action in reliance upon, this information by persons or entities other
than the intended recipient or delegate is strictly prohibited. If you received
this in error, please contact the sender and delete the material from any
computer. The integrity and security of this message cannot by guaranteed on
the Internet. The Sender accepts no liability for the content of this e-mail,
or for the consequences of any actions taken on basis of the information
provided. The recipient should check this e-mail and any attachments for the
presence of viruses. The sender accepts no liability for any damage caused by
any virus transmitted by this e-mail. This disclaimer is the property of the
TTC and must not be altered or circumvented in any manner. |
- LPR & French Canadian characters Horlick, Michael
- Re: LPR & French Canadian characters Peter . Webb
- Re: LPR & French Canadian characters Horlick, Michael
- Re: LPR & French Canadian characters Horlick, Michael
- Re: LPR & French Canadian characters Peter . Webb
- Re: LPR & French Canadian characters Horlick, Michael
- Re: LPR & French Canadian characters Tony Harminc
- Re: LPR & French Canadian characters Les Geer (607-429-3580)
- Re: LPR & French Canadian characters Horlick, Michael
- Re: LPR & French Canadian characters Tony Harminc
- Re: LPR & French Canadian characters Alan Altmark
- Re: LPR & French Canadian characters Horlick, Michael
- Re: LPR & French Canadian characters Alan Altmark
- Re: LPR & French Canadian characters Horlick, Michael
- Re: LPR & French Canadian characters Alan Altmark
- Re: LPR & French Canadian characters Horlick, Michael
