|
midrange.com
Philipp,
I tried increasing the ACTTMR(300) but instead of getting a message that
"Operator
Action Required" it goes to a "Did not end normally" message.
The job log now shows:
CPD338D Diagnostic 40 08/16/01 08:11:43 QWPPJLDR
QSYS *STMT QWPPJLDR QSYS
From module . . . . . . . . : WPPJLDR
From procedure . . . . . . : Socket_Recv
Statement . . . . . . . . . : 39
To module . . . . . . . . . : WPPJLDR
To procedure . . . . . . . : _C_pep
Statement . . . . . . . . . : *N
Message . . . . : An error occurred while
receiving data.
Cause . . . . . : A communications error
occurred while receiving data from
remote device at RMTLOCNAME 10.2.1.97.
The error
code is 3426. This error
can also occur when the system attempts
to print
to the remote device after
it has been powered off and on while the
printer
writer remains active.
Recovery . . . : Try the request
again. If
the problem continues, end
TCP/IP using the End TCP/IP (ENDTCP)
command,
start TCP/IP by using the
Start TCP/IP (STRTCP) command, and then
try the
request again.
I checked and the Jetdirect has a default gateway of 10.2.0.254:
IP Address : 10.2.1.97
Subnet Mask : 255.255.0.0
Default Gateway : 10.2.0.254
Syslog Server : 10.0.0.1
Idle Timeout : 300 Seconds
Set Cmnty Name : Not Specified
Host Name : WDPR1097
Interestingly, when I telnetted to get the above paste I tried to telnet to the
print
server @ 10.0.0.11 and could not contact it. It would appear that Sprint set the
routers so that 10.0.0.1 is the only address outside the local 10.2.x.x that
can be
reached.
BTW all the LANs are 100Mb but the frame relay is 56Kb.
Thanks.
Roger Vicker, CCP
Philipp Rusch wrote:
> Hello Roger,
>
> I think you got a routing/timing problem on the way back from the jetdiretcs
>to the
> AS/400. The main difference between a rmtoutq and a prt device is the feedback
> of the printer status to control that jobs more closely, as you surely
>noticed.
> The default gate of the jetdirects should then be the cisco router at
>10.2.0.254
> on the way back to the AS/400. Try setting the timer for activity on the devd
> from default 170 to something like 300.
> And, of course, there is no way to define a type *RMT device since these are
> LAN attached printers and *RMT means devices on a remote workstation
> controller like the IBM 5494 for instance.
>
> Regards from germany, Philipp Rusch
>
> "Roger Vicker, CCP" schrieb:
>
> > Paul,
> >
> > The *DFTROUTE is 10.0.0.254 since that is the router that is on the same
>lan as
> > the AS/400. The 10.2.0.254 router is on the remote lan as seen from the
>AS/400
> > end of things.
> >
> > Alistair,
> >
> > The printer is defined as a lan printer by:
> >
> > CRTDEVPRT DEVD(WDPR10971)
> > DEVCLS(*LAN)
> > TYPE(3812)
> > MODEL(1)
> > LANATTACH(*IP)
> > PORT(9100)
> > FONT(11)
> > TRANSFORM(*YES)
> > MFRTYPMDL(*HP4000)
> > RMTLOCNAME('10.2.1.97')
> > SYSDRVPGM(*HPPJLDRV)
> > TEXT('FWD Data Collections Laser')
> >
> > It can not be DEVCLS(*RMT) since it is not connected to a remote workstation
> > controller.
> >
> > As part of trying to figure this out I did try using a remote outq and it
> > worked. However I need the functions of CRTDEVPRT. I've also tried adding a
>name
> > to the host table and using that in the DEVD and OUTQD with no difference.
> >
> > Paul Tykodi wrote:
> >
> > > Dear Roger,
> > >
> > > You might want to execute the command CFGTCP on your IBM host and then
> > > choose option 2 Work with TCP/IP Routes. You should see something that
>looks
> > > like the following when you press enter:
> > >
> > > Work with TCP/IP Routes
> > > System:
> > > S102G6VM
> > > Type options, press Enter.
> > > 1=Add 2=Change 4=Remove 5=Display
> > >
> > > Route Subnet Next Preferred
> > > Opt Destination Mask Hop Interface
> > >
> > > *DFTROUTE *NONE 10.10.5.1 *NONE
> > >
> > > In your case the *DFTROUTE value should point towards the Cisco router at
>IP
> > > Address 10.2.0.254. The OS/400 value *DFTROUTE is used to tell an IBM
> > > iSeries or AS/400 server where to send all requests to contact IP
>addresses
> > > that are not visible to the server on its local segment. You can add other
> > > routing entries that specify certain address ranges and a different IP
> > > address as the next hop as necessary.
> > >
> > > HTH
> > >
> > > /Paul
> > > --
> > > Paul Tykodi
> > > Director of Technical Services
> > > LCI-Intermate US, Inc.
> > >
> > > p: 603.431.0606 x115
> > > f: 603.436.6432
> > > paul@intermate-us.com
> > > www.intermate.com
> > >
> > > >Date: Wed, 15 Aug 2001 08:42:45 -0500
> > > >From: "Roger Vicker, CCP" <rvicker@vicker.com>
> > > >Organization: Vicker Programming Systems
> > > >To: Midrange List <MIDRANGE-L@midrange.com>
> > > >Subject: Getting a HP Jetdirect to work through routers
> > > >Reply-To: midrange-l@midrange.com
> > > >
> > > >Hello,
> > > >
> > > >I am having trouble getting some HP Jetdirect servers to work with an
> > > >AS/400 through routers. The AS/400 is working with Jetdirects on its
> > > >local network (CRTDEVPRT *HPT) but when I use the same process through
> > > >routers the writer times out after about 3 minutes and the spool file
> > > >never changes from RDY. Sprint claims that they didn't block any ports
> > > >in the routers.
> > > >
> > > >The layout is:
> > > >
> > > >AS/400 @ 10.0.0.1 mask 255.255.0.0 on an otherwise Novel network
> > > >Cisco router @ 10.0.0.254
> > > >Frame Relay by Sprint
> > > >Cisco router @ 10.2.0.254
> > > >Local peer to peer (Windows xxxx) network 10.2.#.# mask 255.255.0.0
> > > >but with a WINS server @ 10.2.1.57
> > > >The AS/400 has the WINS tab pointed to the local WINS server.
> > > >
> > > >CAE and file server works OK. Local PCs can use the Jetdirects. The
> > > >AS/400 can ping the Jetdirects by address and the CRTDEVPRT uses the
> > > >address, not a host name.
> > > >
> > > >Where do I look next?
> > > >
> > > >Roger Vicker, CCP
> > > >
> > > >--
> > > >*** Vicker Programming and Service *** Have bits will byte ***
> > > >www.vicker.com ***
> > > >A mule dressed in a tuxedo is still a mule.
> > >
> >
> > --
> > *** Vicker Programming and Service *** Have bits will byte ***
>www.vicker.com
> > ***
> > A mule dressed in a tuxedo is still a mule.
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
--
*** Vicker Pony Farm *** www.vicker.com/vpf.html ***
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com
***
Two terms for congressmen: One in office, one in jail.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
