Re: Infoprint, Extended Mode, and Old Style Translation

[Carmen Vitullo]

Good luck Anne, I had a syncsort sample also but I can't seem to find it :( 



Carmen Vitullo 

- Original Message -

From: "Anne Adams (DTI)" <anne.ad...@state.de.us> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Tuesday, April 10, 2018 8:50:03 AM 
Subject: Re: Infoprint, Extended Mode, and Old Style Translation 

Thanks Carmen. I'll give it a try. 

Anne R. Adams, CISSP 
DTI, Systems Engineering 
Lead Mainframe Services Analyst 
302.739.9500 

We support the mainframe, it just works. 


-Original Message- 
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Carmen Vitullo 
Sent: Tuesday, April 10, 2018 9:43 AM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Infoprint, Extended Mode, and Old Style Translation 

Hi Anne, maybe a XLAT table? 



look in the TCPIP.SEZATCPX library for an XLAT TABLE 
- copy to a private library 
update as required 
convxlat '.srce.cntl(ftpate)' AMQP.TCPSCBIN tables are in TCPIP.SEZATCPX 


we did this years ago to help in a conversion project that unloaded some DB2 
table. an EOL char was required to load the data to I forget where, been 
too long. 
I worked with one of the DBA's there. 
HTH's some. 







Carmen Vitullo 

- Original Message - 

From: "Anne Adams (DTI)" <anne.ad...@state.de.us> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Tuesday, April 10, 2018 8:10:55 AM 
Subject: Infoprint, Extended Mode, and Old Style Translation 

Hello friends, 

The Subject Line pretty much sums up the question. We're converting our 
printers to Infopint Extended mode and discovered that our programs send a 
‘¢1B¢’ for the ESC character. It should be x'1B'. It appears that in the past 
under Basic mode the ‘¢' was ignored or used as a delimiter and the 1B was 
translated correctly to ESC. Conversations with IBM suggested that because we 
use "Old-Style Translation" while in Basic mode the ‘¢1B¢’ is being translated 
incorrectly now that we're using Extended Mode. We stopped using Old-Style 
Translation but the problem remained. We could recode all our print jobs (which 
Apps is none too happy about) or we could write an exit (which Systems is none 
too happy about) but I would prefer to think there is a third alternative. Any 
ideas on how to get Extended to translate the ‘¢1B¢’ to 1B? 

Many thanks. 


Anne R Adams, CISSP 
DTI, Systems Engineering 
Lead Mainframe Services Analyst 
302.739.9500 

We support the mainframe, it just works. 

This communication is for use by the intended recipient and contains 
information that may be Privileged, confidential or copyrighted under 
applicable law. If you are not the intended recipient, you are hereby formally 
notified that any use, copying or distribution of this e-mail, in whole or in 
part, is strictly prohibited. Please notify the sender by return e-mail and 
delete this e-mail from your system. Unless explicitly and conspicuously 
designated as "E-Contract Intended", this e-mail does not constitute a contract 
offer, a contract amendment, or an acceptance of a contract offer. This e-mail 
does not constitute a consent to the use of sender's contact information for 
direct marketing purposes or for transfers of data to third parties. 



-- 
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 

-- 
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

Re: Infoprint, Extended Mode, and Old Style Translation

[Adams, Anne (DTI)]

Thanks Carmen. I'll give it a try.

Anne R. Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst 
302.739.9500

We support the mainframe, it just works.


-Original Message-
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Carmen Vitullo
Sent: Tuesday, April 10, 2018 9:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Infoprint, Extended Mode, and Old Style Translation

Hi Anne, maybe a XLAT table? 



look in the TCPIP.SEZATCPX library for an XLAT TABLE
- copy to a private library
update as required
convxlat '.srce.cntl(ftpate)' AMQP.TCPSCBIN tables are in TCPIP.SEZATCPX 


we did this years ago to help in a conversion project that unloaded some DB2 
table. an EOL char was required to load the data to I forget where, been 
too long. 
I worked with one of the DBA's there. 
HTH's some. 







Carmen Vitullo 

- Original Message -

From: "Anne Adams (DTI)" <anne.ad...@state.de.us>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, April 10, 2018 8:10:55 AM
Subject: Infoprint, Extended Mode, and Old Style Translation 

Hello friends, 

The Subject Line pretty much sums up the question. We're converting our 
printers to Infopint Extended mode and discovered that our programs send a 
‘¢1B¢’ for the ESC character. It should be x'1B'. It appears that in the past 
under Basic mode the ‘¢' was ignored or used as a delimiter and the 1B was 
translated correctly to ESC. Conversations with IBM suggested that because we 
use "Old-Style Translation" while in Basic mode the ‘¢1B¢’ is being translated 
incorrectly now that we're using Extended Mode. We stopped using Old-Style 
Translation but the problem remained. We could recode all our print jobs (which 
Apps is none too happy about) or we could write an exit (which Systems is none 
too happy about) but I would prefer to think there is a third alternative. Any 
ideas on how to get Extended to translate the ‘¢1B¢’ to 1B? 

Many thanks. 


Anne R Adams, CISSP
DTI, Systems Engineering
Lead Mainframe Services Analyst
302.739.9500 

We support the mainframe, it just works. 

This communication is for use by the intended recipient and contains 
information that may be Privileged, confidential or copyrighted under 
applicable law. If you are not the intended recipient, you are hereby formally 
notified that any use, copying or distribution of this e-mail, in whole or in 
part, is strictly prohibited. Please notify the sender by return e-mail and 
delete this e-mail from your system. Unless explicitly and conspicuously 
designated as "E-Contract Intended", this e-mail does not constitute a contract 
offer, a contract amendment, or an acceptance of a contract offer. This e-mail 
does not constitute a consent to the use of sender's contact information for 
direct marketing purposes or for transfers of data to third parties. 



--
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

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

Re: Infoprint, Extended Mode, and Old Style Translation

[Carmen Vitullo]

Hi Anne, maybe a XLAT table? 



look in the TCPIP.SEZATCPX library for an XLAT TABLE 
- copy to a private library 
update as required 
convxlat '.srce.cntl(ftpate)' AMQP.TCPSCBIN 
tables are in TCPIP.SEZATCPX 


we did this years ago to help in a conversion project that unloaded some DB2 
table. an EOL char was required to load the data to I forget where, been 
too long. 
I worked with one of the DBA's there. 
HTH's some. 







Carmen Vitullo 

- Original Message -

From: "Anne Adams (DTI)"  
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Tuesday, April 10, 2018 8:10:55 AM 
Subject: Infoprint, Extended Mode, and Old Style Translation 

Hello friends, 

The Subject Line pretty much sums up the question. We're converting our 
printers to Infopint Extended mode and discovered that our programs send a 
‘¢1B¢’ for the ESC character. It should be x'1B'. It appears that in the past 
under Basic mode the ‘¢' was ignored or used as a delimiter and the 1B was 
translated correctly to ESC. Conversations with IBM suggested that because we 
use "Old-Style Translation" while in Basic mode the ‘¢1B¢’ is being translated 
incorrectly now that we're using Extended Mode. We stopped using Old-Style 
Translation but the problem remained. We could recode all our print jobs (which 
Apps is none too happy about) or we could write an exit (which Systems is none 
too happy about) but I would prefer to think there is a third alternative. Any 
ideas on how to get Extended to translate the ‘¢1B¢’ to 1B? 

Many thanks. 


Anne R Adams, CISSP 
DTI, Systems Engineering 
Lead Mainframe Services Analyst 
302.739.9500 

We support the mainframe, it just works. 

This communication is for use by the intended recipient and contains 
information that may be Privileged, confidential or copyrighted under 
applicable law. If you are not the intended recipient, you are hereby formally 
notified that any use, copying or distribution of this e-mail, in whole or in 
part, is strictly prohibited. Please notify the sender by return e-mail and 
delete this e-mail from your system. Unless explicitly and conspicuously 
designated as "E-Contract Intended", this e-mail does not constitute a contract 
offer, a contract amendment, or an acceptance of a contract offer. This e-mail 
does not constitute a consent to the use of sender's contact information for 
direct marketing purposes or for transfers of data to third parties. 



-- 
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