RE: Emulex pocket que -- MIDRANGE-L

Ken,

  I forgot to include the other parameters for a standard Remote Writer OUTQ
using LPR to send print directly to the WINNT LAN print resource.  Here is
the general settings we use:

Queue Name=xxxxx
Library=QUSRSYS
Authority to check=*DTAAUT
Remote System=NT Server Name
Remote Printer Queue=LAN Printer Queue Name     
Queue for messages=QSYSOPR
Library=*LIBL
Connection Type=*IP
Destination Type=*OTHER
Transform to ASCII=*YES

Hope this helps......

James A. Olliges
Smurfit-Stone ITD Chicago
jolliges@smurfit.com


-----Original Message-----
From: Olliges, James [mailto:JOLLIGES@SMURFIT.COM]
Sent: Friday, October 13, 2000 10:51 AM
To: MIDRANGE-L@midrange.com
Subject: RE: Emulex pocket que


Ken,

  If you have a LAN print environment already defined using WINNT you should
be able to define a Remote Writer OUTQ (LPR/LPD) to route output to the NT
print resource from the AS/400.  Use CRTOUTQ command and specify the NT
server name for the RMTSYS "Remote System" parameter and the print resource
for the LAN printer as the RMTPRTQ "Remote Printer Queue" parameter.  You
may see an issue where the output queue goes to a SND state but nothing
prints.  This can be caused by an invalid NT server or print resource name
or a spooling performance issue on your AS/400.  Issue the WRKSHRPOOL
command and check that your *SPOOL storage is set to at least 4MB (4000)
*fixed.  Older CISC AS/400's with dynamic performance adjustment set on
often steal storage from *SPOOL.  We found that are older V3R2 and V3R7
systems required manual adjustment of *SPOOL storage to allow LPR/LPD to
work correctly.  Also increase the priority for the QSPL4 class in library
QGPL to 30 from 50 for better performance and give it a higher timeslice
setting (10000) if you print large reports using LPR.  These changes did not
hurt our interactive performance but you should test this out with some
trial and error before you commit to production use. Don't forget to order
the latest TCP/IP protocol fixes from IBM for your release if you are behind
on maintenance as well.      

James A. Olliges
Smurfit-Stone ITD Chicago
jolliges@smurfit.com


-----Original Message-----
From: KenEggleston@debssystems.com [mailto:KenEggleston@debssystems.com]
Sent: Friday, October 13, 2000 7:58 AM
To: midrange-l@midrange.com
Subject: FW: Emulex pocket que




- Forwarded by Ken Eggleston/DEBS on 10/13/00 08:56 AM -----


I did contact Emulex Corp before I submitted this and was told to use port
2501. I can print from Win NT with MS TCP printing with that port so I know
it's the correct one. I tried using LPR/LPD with no luck. I did manage to
get a little garbage to print out from a laser printer indicating maybe a
driver problem, but tried every sysdrvpgm that was available, again with no
luck. Thanks for the input though


----- Original Message -----
From:     Marco Facchinetti [SMTP:facchinetti@yahoo.com]
Reply To: MIDRANGE-L@midrange.com [SMTP:MIDRANGE-L@midrange.com]
Sent:     October 13, 1900, 4:50:04
To:       MIDRANGE-L@midrange.com
Subject:  Re: Emulex pocket que

In TCP/IP printing (not via LPR/LPD) with a device type
*LAN (DEVCLS *LAN and LANATTACH *IP) an important parameter
is the port (keyword PORT) since is the number AS400 will
use to dialog with the printer. If your printer server has
a declared port number available you probably will be able
to print (also check out the firewall if you got one
running in your network).
Otherwise the only way is to use a remote queue (LPR or
LPD) but it's not the same.
Anyway this is working with a laser printer connected via
print server (HP 500X):
    DEVD        MORANDINI
    OPTION      *BASIC
                *PRT
    DEVCLS      *LAN
    TYPE        3812
    MODEL       1
    LANATTACH   *IP
    PORT        9100
    ATTACH      *DIRECT
    ONLINE      *YES
    FONT
                11
                *NONE
    FORMFEED    *AUTOCUT
    SEPDRAWER   *FILE
    SEPPGM      *NONE
    PRTERRMSG   *INQ
    MSGQ        *CTLD
                QSYSOPR
                 QSYS
    ACTTMR      170
    INACTTMR    *SEC15
    LINESPEED   19200
    WORDLEN     8
    PARITY      *NONE
    STOPBITS    1
    TRANSFORM   *YES
    MFRTYPMDL   *HP4
    PPRSRC1     *LETTER
    PPRSRC2     *LETTER
    ENVELOPE    *NUMBER10
    ASCII899    *NO
    IMGCFG      *NONE
    CHRID       *SYSVAL
    RMTLOCNAME  192.168.2.91
    WSCST       *NONE
    USRDFNOBJ   *NONE
                 *NONE
    USRDTATFM   *NONE
    SYSDRVPGM   *HPPJLDRV

this is working fine on our AS (V4.4)
I also noticed a problem using ports 9101 and 9102: you
must set the timer on your print server to 0.
I hope it can help
Bye

--- KenEggleston@debssystems.com wrote:
> I have an Emulex pocket que Model NQP0 that hooks to a
> centronics parallel
> port on a printer and is accessed via twisted pair port.
> I'm trying to get
> this to work on our 400. I can address it via the arp
> command and even
> print to it via Windows NT, and the 400 can ping it, but
> I can't get it to
> print. I did a crtdevprt using all the settings as
> suggested in an IBM
> document "Setting up a 3812 PJL TCP/LAN printer". I asked
> our IBM support
> and he suggested a half of dozen PTF's for printing but
> before doing that I
> wanted to check here. If anyone has any info on using
> these I would
> appreciated it.
>
> Thank you,
> keneggleston@debssystems.com
>
>
> +---
> | 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
> +---


__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/
+---
| 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
+---
----- End Of Original Message -----




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