home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.ibm
- Path: sparky!uunet!paladin.american.edu!gatech!darwin.sura.net!haven.umd.edu!decuac!pa.dec.com!e2big.mko.dec.com!nntpd.lkg.dec.com!smaug.enet.dec.com!cambria
- From: cambria@smaug.enet.dec.com (Michael C. Cambria)
- Subject: Re: Help!!! 3287 printing problem.
- Message-ID: <1992Dec30.214838.4114@nntpd.lkg.dec.com>
- Sender: usenet@nntpd.lkg.dec.com (USENET News System)
- Organization: Digital Equipment Corporation
- References: <54360002@hpsgm2.sgp.hp.com>
- Date: Wed, 30 Dec 1992 20:21:33 GMT
- Lines: 69
-
-
- 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
-