IBM 4247 printing problem
kj
We have a IBM4247-003 IPDS enabled printer with a LAN-card and I am having
problems to
get it to work on Monday mornings 8-)
Our AS400 machine performs an IPL during the weekend and after that the
printer won'n print anything. Only solution is to turn off power on the
printer and vary off/on the printer.
Another thing that is of interest is that the built-in web-server also don't
work unless U restart the printer !!
So, the problem seem to be with the network card...and not with AS...?
But, after restart that the printer works well all week....!!
Any tweaks for the NIC???
In qsysopr's messagequeue I find this:
- Connection with device VP03L is being retried.
And this is what the system says when I check info:
Cause . . . . . : A session cannot be established with the device at
RMTLOCNAME 10.10.10.8, using PORT 5001. The error code is 15. This
indicates one of the following conditions:
15: The activation timer (ACTTMR) value configured for the device
expired before the device was available.
------------------------------------------------------------------------
I checked the activation timer setting and it is: 2550
We also have a PSFCFG for this printer, it looks like this:
User resource library . . . . . . . . . . . . . : *JOBLIBL
IPDS pass through . . . . . . . . . . . . . . . : *NO
Activate release timer . . . . . . . . . . . . . : *NORDYF
Release timer . . . . . . . . . . . . . . . . . : *NOMAX
Restart timer . . . . . . . . . . . . . . . . . : *IMMED
APPC and TCP/IP retry count . . . . . . . . . . : *NOMAX
Delay between APPC retries . . . . . . . . . . . : 90
Auto Session Recovery:
Enabled . . . . . . . . . . . . . . . . . . . : *NO
Message option . . . . . . . . . . . . . . . . :
Acknowledgment frequency . . . . . . . . . . . . : 100
Printer response timer . . . . . . . . . . . . . : *NOMAX
Blank page . . . . . . . . . . . . . . . . . . . : *YES
Page size control . . . . . . . . . . . . . . . : *NO
Resident fonts . . . . . . . . . . . . . . . . . : *YES
Resource retention . . . . . . . . . . . . . . . : *YES
Edge orient . . . . . . . . . . . . . . . . . . : *NO
Use outline fonts . . . . . . . . . . . . . . . : *NO
PSF defined options:
*NONE
Font substitution messages . . . . . . . . . . . : *YES
Capture host fonts at printer . . . . . . . . . : *NO
Font resolution for formatting . . . . . . . . . : *SEARCH
Font mapping table . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . . . . . . :
PSF configuration: VP03L Library: QGPL
Cut sheet emulation mode . . . . . . . . . . . . : *NONE
Use DBCS simulation font . . . . . . . . . . . . : *NO
Generate PDF output . . . . . . . . . . . . . . : *NONE
PDF device emulation type . . . . . . . . . . . : *IP40240
PDF paper size drawer 1 . . . . . . . . . . . . : *LETTER
PDF paper size drawer 2 . . . . . . . . . . . . : *LETTER
PDF multipe group handling:
Acknowledge multiple groups . . . . . . . . . : *NO
Process option . . . . . . . . . . . . . . . . :
PDF fonts inline . . . . . . . . . . . . . . . . : *YES
PDF data queue . . . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . . . . . . :
Paul Tykodi
My suggestion is to change the PSFCFG release timer value from *NOMAX
to a value like 1 (measured in minutes).
The reason is that the connection from your IBM server to the printer
is a TCP socket based connection. When you set the release timer value
to the system default of *NOMAX, the socket connection is maintained
so long as the print writer is started.
This condition can cause the printer to refuse work from any other
hosts and it will generally not tolerate the automatic ending of the
writer executed by an IPL very well.
When you put a numeric value into the release timer field, the system
will close the TCP socket connection when the queue contains no files
in ready status for the number of minutes specified. It will
automatically re-establish the connection when another file enters the
queue. This opening and closing of the transport connection is
independent of the print writer so the writer remains started - only
the physical connection across the wire is started and stopped as
necessary.
This small change is likely to allow the NIC in the printer to better
tolerate the print writer ending process initiated by the IPL.
HTH
Best Regards,
/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC
E-mail: pty...@tykodi.com
Daniel
If it s a NIC Problem. Do you use DHCP or fixed IP address on the box.
If it s DHCP who is doing the Server? What switch do you use?
Besides. I wonder if you don t have to state:
IPDS pass through . . . . . . . . . . . . . . . : *YES
Release timer . . . . . . . . . . . . . . . . . : *SEC15
Page size control . . . . . . . . . . . . . . . : *YES
Font substitution messages . . . . . . . . . . . : *NO <- for
convenience
in the PSFCFG to make IPDS possible?
Daniel
Font substitution messages . . . . . . . . . . . : *YES
On Mon, 29 Aug 2005 12:24:23 +0300, "kj" <jh...@uiui.net> wrote:
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
kj
Thanx for the tips!
The printer has a fixed IP adress config.
Btw: is there any way to simulate the situation I have with the printer?
Otherwise i guess I hav to wait until Monday morning before I can se if
things start to work...
kj
Tested to remove the ethernet cable from the printer and inserted it back
after a while (about 30 min). Result: the printer did not respond to
AS-connection attempts ("connection being retried" messages in QSYSOPR's
queue). After the ethernet cable was inserted an errormessage appeared
stating that the printer has ended in an error state. Had to power off/on
printer and issue command STRPRTWTR to get it back on line. The built in web
server did also not work after insertion of ethernet cable! After powering
off/on it works fine..
What's the problem with the NIC, I ask....
Paul Tykodi
This isn't necessarily a fair test of your IPL issue because the IPL
creates a software failing condition at the NIC (print writer ended
and thus TCP socket connection ended as well).
Cutting the Ethernet connectivity in an electronic fashion (hardware
failure as if the cable was cut) can definitely cause devices to get
hung requiring a power off/power on to recover.
HTH
Best Regards,
/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC
E-mail: pty...@tykodi.com
kj
Is it any difference if I put a *sec15 value or a numerical value of 1 in
the "release timer" field in my PSFCFG
Paul Tykodi
The most aggressive settings you can select are 15 seconds (*SEC15)
and 30 seconds (*SEC30).
I usually like to be a little less aggressive and choose something
between 1 and 5 minutes as a value.
If you have a network with some amount of propagation delay built into
it, the 15 second choice can sometimes cause your IBM host to close
the TCP socket connection too quickly (before a spool file has been
completely processed).
HTH
Best Regards,
/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC
E-mail: pty...@tykodi.com
