Re: Printer issue - Very frustrating

Thanks Jim,

Yes, that was the first thing I thought of.

On the IBMi I have it set to SEC15. On the printer I changed it to the
lowest allowed of 40 seconds.

However, we have observed that, generally first thing in the morning, but
not always the job in the queue will show with a *PND status for 30+
minutes.

And, at this time, we are unable to ping the printer from the IBMi.

But if she prints from Word the job prints and then the jobs on the queue
print and then we can ping the printer.

It is almost like the print driver on the PC sends like a "WakeUp" command
then sends the print job.

We have an open ticket with the supplier, and they say it is a network
issue.

As I said to Jack, I am going to get her to run a ping from her PC first
up tomorrow, if that fails then print a word doc, then try the ping again.

That may shed some light ?

Thank you for the response.

Don


-----Original Message-----
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Sent: Monday, February 5, 2024 11:18 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Don Brown <dbrown@xxxxxxxxxx>
Subject: Re: Printer issue - Very frustrating

I’ve run into settings on the printer that do not release the connection
from one server or another to enable the IBM i to reconnect when needed.
Maybe the print server on the printer needs adjustment?


Jim Oberholtzer
Agile Technology Architects

On Feb 4, 2024, at 6:03 PM, Don Brown via MIDRANGE-L <

midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Thanks Jack,

I would agree with you normally but immediately after she prints form

Windows the printer responds to the ping from IBMi.

But one thing I will now get her to do is to try a ping from Windows

first.

Thanks for the reply

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jack Woehr via MIDRANGE-L
Sent: Monday, February 5, 2024 9:22 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Printer issue - Very frustrating

If you can ping it from Windows and can't ping it from IBM I, you don't

have a printer issue, you have a network issue.

On Sun, Feb 4, 2024, 15:27 Don Brown via MIDRANGE-L <

midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hi All,

I have a printer that generally will not print, the configuration is

below.

Let me provide two scenarios.

Scenario #1.
Report generated to the printer.
Reports are in *PND status.
If I try and ping the IP address of the printer it fails.
End writer / start writer no change (As expected if I can't ping the
device)
Turn the printer OFF and back ON.
Reports print.

Scenario #2
Report generated to the printer.
Reports are in *PND status.
If I try and ping the IP address of the printer it fails.
End writer / start writer no change (As expected if I can't ping the
device)
Print from Microsoft Word, word doc prints, then reports print.
Ping response is successful.
Note: The printer on the PC where the word doc was printed from is
configured to print directly to the printer not via a server.

I collected a communications trace and it just shows no response from
the printer.
The trace shows the IBMi send a SYN to the printer, followed by 5
retries then a wait for approximately 1:40 (One minute and forty

seconds.

This is repeated until I believe she printed the word document and
then the pending print job prints.

The printer and the IBMi are on the same network and subnet and local.

The printer is a 'Ricoh MPC2800 Printer'

Printer Definition
CRTDEVPRT DEVD(PRT03)
DEVCLS(*LAN)
TYPE(3812)
MODEL(1)
LANATTACH(*IP)
PORT(9100)
ATTACH(*DIRECT)
ONLINE(*YES)
FONT(11 *NONE)
FORMFEED(*AUTOCUT)
SEPDRAWER(*FILE)
PRTERRMSG(*INQ)
MSGQ(*CTLD)
ACTTMR(170)
INACTTMR(*SEC15)
LINESPEED(19200)
WORDLEN(8)
PARITY(*NONE)
STOPBITS(1)
TRANSFORM(*YES)
MFRTYPMDL(*HPCOLORLJ)
PPRSRC1(*A4)
PPRSRC2(*A4)
ENVELOPE(*NUMBER10)
ASCII899(*NO)
IMGCFG(*NONE)
CHRID(*SYSVAL)
RMTLOCNAME('172.16.25.201')
SYSDRVPGM(*HPPJLDRV)
TEXT('Ricoh MPC2800 Printer')
PUBLISHINF(*DUPLEX *COLOR *UNKNOWN *UNKNOWN *BLANK (*UNKNOWN))

Any suggestion greatly appreciated.

Thank you

Don

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at

https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.