Dear Rui,

Here is a little information from the RFC2877 that describes the Telnet
TN5250E protocol.

7. Enhanced Printer Emulation Support

   RFC 1572 style USERVAR variables have been defined to allow a
   compliant Telnet client more control over the Telnet server virtual
   device on the AS/400.  These USERVAR's allow the client Telnet to
   select a previously created virtual device or auto-create a new
   virtual device with requested attributes.

   This makes the enhancements available to any Telnet client that
   chooses to support the new negotiations.

   The USERVAR's defined to accomplish this are:

   USERVAR       VALUE            EXAMPLE           DESCRIPTION
   ------------- ---------------- ----------------  -------------------
   DEVNAME       us-ascii char(x) PRINTER1          Printer device name
   IBMIGCFEAT    us-ascii char(6) 2424J0            IGC feature (DBCS)
   IBMMSGQNAME   us-ascii char(x) QSYSOPR           *MSGQ name
   IBMMSGQLIB    us-ascii char(x) QSYS              *MSGQ library
   IBMFONT       us-ascii char(x) 12                Font
   IBMFORMFEED   us-ascii char(1) C | U | A         Formfeed
   IBMTRANSFORM  us-ascii char(1) 1 | 0             Transform
   IBMMFRTYPMDL  us-ascii char(x) *IBM42023         Mfg. type and model
   IBMPPRSRC1    binary(1)        1-byte hex field  Paper source 1
   IBMPPRSRC2    binary(1)        1-byte hex field  Paper source 2
   IBMENVELOPE   binary(1)        1-byte hex field  Envelope hopper
   IBMASCII899   us-ascii char(1) 1 | 0             ASCII 899 support
   IBMWSCSTNAME  us-ascii char(x) *NONE             WSCST name
   IBMWSCSTLIB   us-ascii char(x) *LIBL             WSCST library

   x - up to a maximum of 10 characters

   The "IBM" prefix on the USERVAR's denotes AS/400 specific attributes.

   The DEVNAME USERVAR is used both for displays and printers.  The
   IBMFONT and IBMASCII899 are used only for SBCS environments.

   The IBMPPRSRC1, IBMPPRSRC2 and IBMENVELOPE custom USERVAR's do not
   map directly to their descriptions in Chapter 8 in the Communications
   Configuration Reference [5].  To map these, use the index listed
   here:

   IBMPPRSRC1    HEX     IBMPPRSRC2    HEX     IBMENVELOPE    HEX
   ----------   -----    ----------   -----    -----------   -----
   *NONE        'FF'X    *NONE        'FF'X    *NONE         'FF'X
   *MFRTYPMDL   '00'X    *MFRTYPMDL   '00'X    *MFRTYPMDL    '00'X
   *LETTER      '01'X    *LETTER      '01'X    *B5           '06'X
   *LEGAL       '02'X    *LEGAL       '02'X    *MONARCH      '09'X
   *EXECUTIVE   '03'X    *EXECUTIVE   '03'X    *NUMBER9      '0A'X
   *A4          '04'X    *A4          '04'X    *NUMBER10     '0B'X
   *A5          '05'X    *A5          '05'X    *C5           '0C'X
   *B5          '06'X    *B5          '06'X    *DL           '0D'X
   *CONT80      '07'X    *CONT80      '07'X
   *CONT132     '08'X    *CONT132     '08'X
   *A3          '0E'X    *A3          '0E'X
   *B4          '0F'X    *B4          '0F'X
   *LEDGER      '10'X    *LEDGER      '10'X

   Note 1:  For IBMPPRSRC2, *CONT80 and *CONT132 support starts at V3R7.

   Note 2:  For IBMPPRSRC1 and IBMPPRSRC2, *A3, *B4 and *LEDGER support
   starts at V3R7.

The TN5250E protocol places the responsibility for starting a communication
with the client requesting a connection from the IBM server. The server
responds by creating a virtual session to manage the communication with the
client. In your specific case, I believe that I saw in one of your postings
that you were using OS/400 Host Print Transform. If you activate this
function and do not tell the host the default paper sizes for at least Paper
Source 1, you are requesting the IBM host to enter its own default
information into these paper tray parameters in the virtual device
description that it is creating to communicate with your lp5250d enabled
print session. If your IBM server selected *NONE as its default entries for
the paper source parameters, you would continually get the prompting for a
form type as you have mentioned.

The other thing to note is that the execution of the STRPRTWTR command is
hard coded into the OS/400 Telnet server. For each TN5250E client requesting
that a print session be started, the OS/400 Telnet server will automatically
start the print writer for the virtual printer device that is created (or
re-created) at the time the connection is established. If you request a
connection to a specific device name that already exists, OS/400 rebuilds
the virtual session using the same name and the criteria being presented by
your client for this particular connection. You can type the command
STRPRTWTR on a command line and then press F4 to view the default parameters
of the command on your system. On my AS/400, the default Form Type value is
*ALL. If the parameter was empty by default on your system, the messages you
are describing would be generated for each spool file printed as well.

HTH

Best Regards,

/Paul
--
Paul Tykodi
National Product Manager
Print 4Sight Inc.

p: 603-431-0606 x115
f: 603-436-6432
E-mail: paul@intermate-us.com

Special Note: On November 30th, 2002, Print 4Sight Inc. acquired the
business assets and business activity of Intermate US Inc.

Print 4Sight Inc. as an official North American distributor will continue to
sell and support Intermate and Praim Printing products from current offices
in Portsmouth, NH, USA.


>Date: Tue, 7 Jan 2003 11:49:47 -0000
>From: GOMES Rui Pedro <rpgomes@contacto.sonae.pt>
>To: "'linux5250@midrange.com'" <linux5250@midrange.com>
>Subject: RE: [LINUX5250] lp5250d
>
>Hello,
>
>Thank you for the tip! But the problem remains:
>
>There are, already, some printers attached. Most of them are attached
>through Windows Client Access. If I order a print to a printer, lets call
it
>Client Access (CA) printer, and then release the job, it prints without any
>more intervention. But that same printer, started through lp5250d, gives
the
>paper msg. Even if I order the print to the CA printer and, on the spool
>changing the queue atributes to print on the lp5250d printer, it gives the
>same msg.
>
>Its very odd, but it could be an iseries issue.
>
>I'm checking again the as400.
>
>Meanwhile do you have any more sugestions?
>
>Thank you for your time!
>
>Rui Polido
>
>
>-----Original Message-----
>From: Scott Klement [mailto:klemscot@klements.com]
>Sent: sexta-feira, 3 de Janeiro de 2003 17:19
>To: 'linux5250@midrange.com'
>Subject: Re: [LINUX5250] lp5250d
>
>
>
>Hello,
>
>I think that this problem is probably on the iSeries.  It sounds like
>you're running a program that uses a print file or override where you
>are leaving the form type blank.
>
>I could be mistaken, but I don't think lp5250d is involved with the form
>type at all.   I think this is handled by OS/400 before it even sends any
>data to lp5250d.
>
>Perhaps a CL program (or similar) was changed to add an OVRPRTF command
>to your new lp5250d printer, and a mistake was made on the OVRPRTF
>command?   Or maybe the print file itself was changed, and the form type
>was accidentally erased?
>
>If you run this same report to a SNA/Twinax attached printer, do you
>have different results?
>
>
>On Tue, 31 Dec 2002, GOMES Rui Pedro wrote:
>
>> Hello everyone!
>>
>> I have set up lp5250d in linux correctectely and it prints fine, but with
>> the exception of one small detail: everytime I release a print job on the
>> as400 to the printer (env.DEVNAME = CONTLIN), it gives a msg saying that
I
>> should "Put the *STD paper type in the printer CONTLIN." and that the
paper
>> type was left blank. I always disregard the message, and press the G
option,
>> and the printing turns out great.
>>



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.