|
|
| Author |
Message |
Vinj
New User
Joined: 26 May 2009
Posts: 2
Location: Kansas, USA
|
|
|
|
Our application runs on CICS and it has many screens, Every user is assigned with printer id when that user is set up on this application. Users can issue a printout(screen print) from any screen on the application. When the user issues a screen print, program will write the data to a TDQ which has a ATI on it and display “Screen print issues” on the user screen. In the back ground, ATI on the TDQ will trigger a generic program which handles prints. This program will find the printer id and the printer mapping using the user id and issue a printout to the correct printer.
For those users who do not have the printer id setup on the application, the default printer id will be assumed. When these users issue printouts, they will be printed on the printer assigned to default id. For such users we want to change this process and display some message (Say”printer id not defined, please contact helpdesk”) on the user screen. As I said there are may screens in our applications making this change to all the programs will be labourious(about 185 pgms). On the other hand, I am looking for a way where I can handle this from the generic print routine(back ground program). If I can do some thing in this program to send back the message to user, it will be simple one program change. When I tried looking at the possibility, I am not having the details of terminal id of the user who wrote the data into TDQ. All the data that is passed to generic program is user id, screen name and a screen data.
Can any one suggest a optimal solution for this please. Thanks for your help!!! |
|
| Back to top |
|
 |
References
|
|
 |
dbzTHEdinosauer
Senior Member
Joined: 20 Oct 2006
Posts: 3385
Location: germany
|
|
|
|
| are you saying that every module that receives a screen, checks for this 'screen print request', and then formats and outputs an image to the TDQ? |
|
| Back to top |
|
|
Vinj
New User
Joined: 26 May 2009
Posts: 2
Location: Kansas, USA
|
|
|
|
Hi Dick Brenholtz,
Yes Every module checks for print request and if requested, it writes the user id, map name, mapset name, symbolic map and length to TDQ. The ATI on the TDQ triggers the print program which will read all the information from TDQ, formats the symbolic map using the map and mapset and then prints on the printer that is mapped to user id using the SPOOL WRITE.
Thanks,
Praveen. |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 418
|
|
|
|
Vinj,
| Quote: |
| using the SPOOL WRITE |
In my experience, "exec cics spoolwrite"
sends print to CICS SYSOUT.
Are you sure you understand what your print application is doing ? |
|
| Back to top |
|
|
|
|
|
