🚀 go-pugleaf

In article <54360002@hpsgm2.sgp.hp.com> klitd@hpsgm2.sgp.hp.com (Raj PUBALA) writes:
>We did multiple buffer trace on the printer LU. Is it true that CICS will 
>unbind (at least clear) the session with the printer LU after the print job
>is complete? Is this true also for multiple print job on the same logon
>session (without logging off and on again)? 

Generally, no. CICS will unbind the session with the printer LU only upon
operator request (via CEMT) or upon receiving a request from another VTAM
application to release the printer. Both of these effects, moreover, depend on
specifications in either the DFHTCT TYPE=TERMINAL macro for that printer (if
you're doing macro-style terminal definition) or the DISCREQ/RELREQ operands
of the TYPETERM entry referenced by that printer's definition in the CSD (if
you're doing RDO, by using the CEDA transaction). If NO is specified for both,
then CICS will never relinquish the terminal...obviously, you only want to do
this if that CICS region is the only one that will ever use that printer.
There is no connection between the terminal user's session with CICS and the
printer's session.

>CICS TCT shows that the session if REL (Release) when it cannot print. Usually
>it shows REL and CRE (Release and Create). VTAM shows the printer LU status
>to be PREALLOC-Q (which translates to printer session is queued and used by
>someone else). Now remember, there is only one application using this printer LU
>and there is only one user.

Are you using autoinstall?

>I suspect, that the CICS application is not releasing the printer LU all the time.
>The problem is corrected by forcing a deactivation on the printer LU.

What does a D NET,E,ID=printerid show the status of the printer to be when
it's locked up? In particular, does it show any active sessions at all, or
just the one session as PREALLOC-Q?

One other note: if you tell CICS not to release the printer, and intend to do
3270 screen printing to that printer, then you need to turn on Between Bracket
Printer Sharing on the controller customization. (It's standard on 3174s, but
not on 3274s.)
-- 
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@oac.hsc.uth.tmc.edu      | adequately be explained by stupidity.
 "Brought to you by the letters O, S, and by the number 2." -- Mike Levis