Ansicht
Dokumentation
01391 - FW: Bad PTF for V4R4 - RMTWTR
RFUMSV00 - Advance Return for Tax on Sales/Purchases rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
FW: Bad PTF for V4R4 - RMTWTR
Hi Mike,We had this occur yesterday, but it was only a minor problem for us and only
in one location on two printers. I was checking into network problems on
our end. Thanks for posting this. I'll wait for your post tomorrow to see
how your solution worked.
Regards,
****************************
Diane Piccirello
Twin Laboratories, Inc.
150 Motor Parkway, Suite 210
Hauppauge, NY 11788
Phone: 631.467.3140, Ext. 8321
Fax: 631.630.3588
Email: dpiccirelloZt...
-----Original Message-----
From: Mike Martin, IS, Sousa [mailto:MMartinZs...]
Sent: Tuesday, March 20, 2001 14:59
To: SAP - AS/400 List (E-mail)
Subject: FW: Bad PTF for V4R4 - RMTWTR
Thanks to IBM rallying their developers around this problem, we may have a
solution. Unfortunately, we won't be able to apply this change until
tonight, and we won't be able to verify until tomorrow. I want to share
this solution with the group in case any of you are able to make this
change, and verify its success, sooner than us.
The change is simple, but requires stopping SAP and restarting TCP/IP.
Simply change network attributes (CHGNETA) and set ANYNET to *NO. There was
some discussions on this list previously about the implications of setting
this value. IBM's developers were confident that this would eliminate the
problem (there was a binding problem with the ANYNET code and IP).
I will update the group on our progress tomorrow. If any of you are able to
obtain results quicker, please let me know.
Thanks,
Mike D. Martin<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
-----Original Message-----
From: Mike Martin, IS, Sousa
Sent: Tuesday, March 20, 2001 8:25 AM
To: SAP - AS/400 List (E-mail)
Subject: FW: Bad PTF for V4R4 - RMTWTR
Thanks to all for responding so quickly. I have forwarded the information
to IBM for their perusal. Our IBM PMR is: 62965 branch 49R.
I will update the list as new information arises. However, any further
information from this list is warmly welcomed.
Thanks,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
-----Original Message-----
From: Mike Martin, IS, Sousa [mailto:MMartinZs...]
Sent: Monday, March 19, 2001 4:09 PM
To: SAP - AS/400 List (E-mail)
Cc: Michael Hutchison, IS, Sousa
Subject: Bad PTF for V4R4 - RMTWTR
AS/400ers,
This weekend we applied a variety of PTFs to our systems in an attempt to
get relatively current as to DB, Cum., APAR, Hipers, etc. We applied all of
these PTFs to our development system weeks ago. Immediately following the
IPL of DEV, we experienced problems with our remote writers. On
development, however, the problem only happened on two occurrences. Working
with IBM, I set the 'Idle-Timeout' on the JetDirect card to 3600 seconds and
restarted the writer. The problem went away, and we attributed the cause to
'heightened network traffic' (another way of saying, who knows!).
After weeks without experiencing that problem or any others, we applied the
PTFs to our PRD system yesterday. Immediately following, all of our remote
writers began experiencing this problem. First, jobs will be printing fine.
Then, a job seems to get 'stuck' in SND status. This apparently occurs
because the network connection is dropped (NETSTAT entry is dropped for that
IP). We then have to end and restart the remote writer. This usually helps
for a few jobs until it gets 'stuck' again. Occasionally, this work-around
process will create duplicate print jobs as well.
We have a high priority message with IBM opened (this could cost us our
company if not resolved quickly, or if the work-around fails). IBM
suggested that we update the firmware for our HP JetDirect Cards. We did
this successfully, yet the problem continues. We also set the Idle-Timeout
to 3600, yet the problem continues. We have also provided a communications
trace, but have heard nothing yet.
HELP!
Has anyone seen this problem. Can anyone help with the diagnosis or another
workaround for this problem? We currently have 1400 pick jobs waiting to be
printed at our San Diego Warehouse...some date back to early this morning
(since we promise next day delivery to our customers, this is extremely
bad!).
I have included the long list of PTFs that were applied on Sunday. Any help
would be greatly appreciated, but remember, since I am mostly a SAP guy, you
might have to speak slowly! 🙂
DB Fix Package
#13
CUM Package
C0350440
Individual PTFs
(5769SS1) SELECT(SF65293)
(5769SS1) SELECT(SF64914)
(5769SS1) SELECT(SF64894)
(5769SS1) SELECT(SF64882)
(5769SS1) SELECT(SF64627)
(5769SS1) SELECT(SF64093)
(5769SS1) SELECT(SF64890)
...
(5769999) SELECT(MF25534)
5769999) SELECT(MF25966)
(5769999) SELECT(MF25903)
5769999) SELECT(MF25848)
(5769999) SELECT(MF25487)
(5769999) SELECT(MF25481)
(5769999) SELECT(MF25687)
Thanks in advance,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
[Non-text portions of this message have been removed]
To unsubscribe from this group, send an email to:
SAP on System i-unsubscribeZegroups.com
Your use of consolut is subject to http://www.consolut.net
Durban Tours - Südafrika Safari
General Material Data Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 7034 Date: 20240603 Time: 144219 sap01-206 ( 3 ms )
