🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.protocols.ibm
3 messages
3 total messages Started by Raj PUBALA Wed, 30 Dec 1992 11:32
Help!!! 3287 printing problem.
#977
Author: Raj PUBALA
Date: Wed, 30 Dec 1992 11:32
40 lines
2257 bytes
I need some CICS and VTAM help here. Here is the following scenario:-

A user logons to a CICS application. He does a print from the application. The
output gets printed. He does it a few times and it works all the time. He logs
off from the application. Now, this user is the only user on the PU. The printer
is attached to the same PU (PU type 2, printer is 3287 and terminal is 3278).

Then he logs in to the application again. He tried printing. Sometimes it worked
and sometimes it does not. (the printing problem occurs after he logs off from
a successful print).

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

The buffer trace does not show a relinquishing of the printer LU after each
print job (i.e. an UNBIND from CICS to printer LU). So when the user logons
again and print from the application, it does not print.

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.

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.

Any advise or confirmation? Is there a way to confirm these beside showing
a buffer trace of print jobs that does not have UNBIND or SHUTDOWN?


Thanks for reading this help message.

Warm Regards and "Happy New Year 1993"

David LEE

dlee@hpsm8471.kl-mal.hp.com
Re: Help!!! 3287 printing problem.
#979
Author: Michael C. Cambria
Date: Wed, 30 Dec 1992 20:21
69 lines
3598 bytes
In article <54360002@hpsgm2.sgp.hp.com>, klitd@hpsgm2.sgp.hp.com (Raj PUBALA) writes...
>I need some CICS and VTAM help here. Here is the following scenario:-
> 
>A user logons to a CICS application. He does a print from the application. The
>output gets printed. He does it a few times and it works all the time. He logs
>off from the application. Now, this user is the only user on the PU. The printer
>is attached to the same PU (PU type 2, printer is 3287 and terminal is 3278).
> 
>Then he logs in to the application again. He tried printing. Sometimes it worked
>and sometimes it does not. (the printing problem occurs after he logs off from
>a successful print).
> 
>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)? 
> 

A PLU does not have to UNBIND a printer after printing.
If another (P)LU wants to use the printer, it will "tell"
the current PLU (via an Notify RU) and the RELREQ exit will be driven.
The PLU will then UNBIND the printer (allowing the other PLU to us it.)
I don't remember off the top of my head if CICS behaves this way or 
not.  I'll drink on it.

> 
>The buffer trace does not show a relinquishing of the printer LU after each
>print job (i.e. an UNBIND from CICS to printer LU). So when the user logons
>again and print from the application, it does not print.
> 

The above explains why a PLU doesn't have to relinquish the printer after
each print job.  A PLU *should* be able to print again .....

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

Is the printer predefined to CICS?  The "Create" doesn't sound right.
If I remember correctly, it has to do with autoinstall.  I don't 
belive that printers can be autoinstalled.

What does VTAM show as the PLU for the printer LU status of PREALLOC-Q?
The applid of *some* application should be given.  Is it the CICS in 
question?  Another application?

If the session is queued to CICS, there should be an LU-LU session to
the printer which is causing CICS to queue.

What does cemt sho when things are working?
What does VTAM show for the printer when printing is taking place?
What does VTAM show for the printer when printing stops?
Be sure to use ,e (ie. d net,e,id=printer)
Note also the IST597I (capability slu enabled, disabled etc.)

> 
>Any advise or confirmation? Is there a way to confirm these beside showing
>a buffer trace of print jobs that does not have UNBIND or SHUTDOWN?
> 

Do you have netview?  You can use NLDM to see the session history.

Good Luck,
/Mike
Re: Help!!! 3287 printing problem.
#978
Author: Jay Maynard
Date: Wed, 30 Dec 1992 21:03
41 lines
2838 bytes
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
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads