Printing problems

We just installed SP21. Now we are having problems printing when we submit any UBE. When we change the printer location to a "real" printer (we use QPRINT as our default), one page of garbage prints. If we go into View, User Options, Submitted Reports and view and print the report is prints just fine. This did not occur prior to the upgrade to SP21. Everything worked just fine. It does not matter which environment or if we submit from TS or FAT client. Any ideas?

Thanks
Tom

You don't say whether this is normal printing or whether this is through Formscape or some other third party package. Assuming normal AS/400 and JDE printing I'd look to see if the ASCII / EBCDIC encoding on the JDE side got changed in the upgrade. It should be EBCDIC. If that's not it, I'd like to know what it turns out to be.

Darrell Allison
Systems Programmer
AS/400 V4R5 9406-730 8-Way / OneWorld B7332 SP11.3

Found the answer to my problem. I need to apply the ne off" to SP21. There is a known problem that was fixed with SAR #6522475.

Just some more FYI for anybody hat reads this post. Do *NOT* run the JDEUPDATE program that is specified in the AS400 install instructions for SP21_F1. If you do, your services will not come up. This is a known issue. Instead of running JDEUPDATE, run LINKBSFN for each of your environments. I learned about this the hard way. After working wirh JDE they gave the workaround. If you have already encountered this, you will have to restore your B733xSYS from the save file and re-install the "one off".

Tom

Did you also install the SPX_005 one-off?

And did you by chance install the SPX_005, run JDEUPDATE, then instal F1,
run JDEUPDATE again?

I have found that the above order of operations caused the JDENET_K to fail
to start with E1.

However, reversing the order of installation, E1, JDEUPDATE, SPX_005,
JDEUPDATE works without a hitch.

It has to do with the fact that the JDEUPDATE following E1 updates all
'appropriate' *SRVPGM objects in B7334SYS library with new information
(program signatures or some such nonsense). One of the updated *SRVPGM
objects is JDENET_K.

Now, when E1 was installed, it delivered a new JDENET_K. This new JDENET_K
knows nothing about the SPX_005 enhancements that were communicated via the
previous JDEUPDATE. The E1 JDEUPDATE utility updates all the 'appropriate'
*SRVPGM objects with new information about the JDENET_K.

BUT it fails to consider those objects delivered with SPX_005, as not all
customers install this little gem. Therefore, when the E1 JDENET_K program
attempts to start and use the SPX_005 objects, it pukes due to unexpected
patched code.

Reversing the installation order, allows the E1 JDENET_K process to receive
the 'knowledge' about the SPX_005 enhancements prior to starting.

I can only assume this is the same problem you encountered with F1.

Determined this during some gut wrenching, anxious moments examining the job
log produced by the JDENET_K.

The good news is that, if done properly, this WILL solve the printing
problems you are experiencing.

Brent Marxhausen
DBT, Inc.
Independent CNC Consultant
email: [email protected]