Re: Wierd CA Printer problem -- MIDRANGE-L

Dear Larry,

The Client Access TCP/IP printer support uses the TN5250E protocol. One 
difference between TN5250E support for Client Access defined printers and the 
older SNA based APPC connectivity for Client Access defined printers is that 
TN5250E does not support virtual devices. The only TN5250E printer model 
supported is 3812/1 and the only error messages and conditions currently 
supported generally are those supported by the true 3812/1. The list is as 
follows:

<Text from current TN5250E Draft Specification Starts Here>
Internet Draft          5250 Telnet Enhancements              April 1999

     If BYTE 7 = x1xx xxxx then bytes 10-LL may contain: (2)
        Command/parameter not valid  C9 00 03 02 2x 00
        Print check                  C9 00 03 02 3x 00
        Forms check                  C9 00 03 02 4x 00
        Normal periodic condition    C9 00 03 02 5x 00
        Data stream error            C9 00 03 02 6x 00
        Machine/print/ribbon check   C9 00 03 02 8x 00

     If BYTE 7 = 1xxx xxxx then bytes 10-LL may contain: (3)
        Cancel                       08 11 02 00 00 00
        Invalid print parameter      08 11 02 29 00 00
        Invalid print command        08 11 02 28 00 00

   Diagnostic information notes:

   1.  LL is the length of the structure defined in Byte 6.  If
       no additional data is present, the remainder of the
       structure must be padded with zeroes.

   2.  These are printer SIGNAL commands.  Further information on
       these commands may be obtained from the 5494 Remote Control
       Unit Functions Reference guide [2].  Refer to your AS/400 printer
       documentation for more specific information on these data stream
       exceptions.  Some 3812 and 5553 errors that may be seen:

       Machine check           C9 00 03 02 11 00
       Graphics check          C9 00 03 02 26 00
       Print check             C9 00 03 02 31 00
       Form jam                C9 00 03 02 41 00
       Paper jam               C9 00 03 02 47 00
       End of forms            C9 00 03 02 50 00
       Printer not ready       C9 00 03 02 51 00
       Data stream - class 1   C9 00 03 02 66 00 loss of text
       Data stream - class 2   C9 00 03 02 67 00 text appearance
       Data stream - class 3   C9 00 03 02 68 00 multibyte control error
       Data stream - class 4   C9 00 03 02 69 00 multibyte control parm
       Cover unexpectedly open C9 00 03 02 81 00
       Machine check           C9 00 03 02 86 00
       Machine check           C9 00 03 02 87 00
       Ribbon check            C9 00 03 02 88 00

   3.  These are printer negative responses.  Further information
       on these commands may be obtained from the 5494 Remote
       Control Unit Functions Reference guide [2].

   The print data will start in byte LL+1.
<Text from current TN5250E Draft Specification Ends Here>

In looking through the closed APAR database regarding Client Access TCP/IP 
printing sessions, you will find a number of instances where a particular 
printer session became hung up due to an unexpected error condition reported by 
the print device. IBM has been enhancing the error handling of the Telnet 
server regarding printer sessions as problems are reported to them.

If this is what happened to this one printer ID on your system, ending and 
restarting the Telnet server should clear the problem.

Best Regards,

/Paul
--
Paul Tykodi, Technical Director                 E-mail: pault@praim.com
Praim Inc.                                           Tel: 603-431-0606
140 Congress St., #2                                Fax: 603-436-6432
Portsmouth, NH  03801-4019

Further information about Praim Products can be found at http://www.praim.com.


Date:   Fri, 23 Jul 1999 09:14:25 -0400
From:   Larry Bolhuis <lbolhui@ibm.net>
Subject:        Wierd CA Printer problem

Has anyone seen this:
CA V3R2M0 with previous to current fixpack connecting to V4R2 of OS/400.  All 
connections are TCP/IP on ethernet.  Over thirty stations setup up with 
multiple sessions and printers. Everything works except ONE printer.  Start the 
session and you see the gray printer control box appear for about 2 seconds and 
quits.  Device on AS/400 is vary on pending.  Tried varyoff-same, tried 
deleting it-it will not come back.  Tried a new CA session-same. Changed 
printer name in original session-it creates and works fine!  Renamed this newly 
created device to desired name-fails again!  NOTHING in QSYSOPR, DSPLOG, 
QSYSMSG, WRKPRB and no writer joblog is created.  Attempting to view NETSTAT 
*CNN during the startup shows no additional sockets being created, or they are 
gone before I can see them.
I truly suspect an IPL or possibly a shutdown/restart of TCP/IP on the 400 will 
solve this but howcum?
* Larry

- -- 
Larry Bolhuis         | Trivia Question: What famous car carried
Arbor Solutions, Inc  |  the tags:   BDR 529 ?
(616) 451-2500        |
(616) 451-2571 -fax   | Two rules to success in life:
lbolhui@ibm.net       | 1. Never tell people everything you know.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---