Default printer on the web

We have a problem where users cannot run UBEs when logged onto JDE through the web because when they attempt to launch the UBE the printer fields on the launch screen are blank.

There is a default printer for the environment (JPD7333) and it works when the user launches a UBE from a Thick Client.

This has only surfaced since we upgraded to SP23 2 weeks ago.

Any ideas?

Thanks.

Are the users able to select a printer? Or are you saying that the printer selection application also shows blank?

This may or may not be the same thing - we had old, invalid printers instead of blanks but the net effect was the same. You might be having the same issue. A 'gift' from a long ago SP we figured. Since we started with SP13, who knows. The below was the response from the vendor on our call.

This issue occurs when there is an invalid printer in the RDA specs for the report version. When the version is generated to the HTML client, the generator includes this information for the version and this results in the submission problem when submitting the version from the HTML client. The solution is to correct the specifications of the version and remove the invalid printer information in the report specs.

To see the invalid specification, go into the Universal Table Browser (UTB) on a fat client workstation and open the local TAM specs. (You need TAMMenus=Show in [INTERACTIVE RUNTIME] to see tam files). Select the RDASPEC and inquire on the report and version name. Focus on record type 1, the header record for the version that appears on the left. Scroll all they way down on the right-hand pane, until you find the field "szServerString1' which will contain the incorrect value for the printer. This should be *NONE.

The following are the steps to correct the issue:
1. Check-out the versions and template in Object Management Workbench (OMW)
2. Go into Report Design Aid and from the File menu, select the option for Print Setup. It is probably set to *NONE.
3. Under the printer selection, change the printer to any existing printer, press OK and save the report. Then go back into the printer selection window and change the printer back to a value of *NONE. Press OK and save the report again. This will update the report specifications to have a value of *NONE for the printer.
4. Repeat these steps for each of the affected versions and the report template.
4. Check in the report template and versions.
5. From the machine where the generator runs, check out all of the versions and the report template to get the corrected report specs and then regenerate them so the web server now has the correct specs.

NOTE: After updating the report specs to *NONE in step 3, the results can be verified in UTB where the ServerString1 is now set to *NONE.

We wrote a utility to find them - we had hundreds of versions. We got this response from the vendor when we asked for a way to find them - I have entered ICE 1250026000 / SAR 7573119 on your behalf, which requests a method to identify batch versions with incorrect printer information without having to open each one individually.

Hope this helps.

Sue Shaw
Xe Coexistent SP23J1 iSeries V5R3 all client platforms

If you need it, our case number was Case 3826026.

[ QUOTE ]
3. Under the printer selection, change the printer to any existing printer, press OK and save the report. Then go back into the printer selection window and change the printer back to a value of *NONE. Press OK and save the report again. This will update the report specifications to have a value of *NONE for the printer.


[/ QUOTE ]

My experience of this has been: click on the edit control where *NONE is, and type a space, and then backspace to delete the space character, and after this, saving specs will put *NONE in the RDASPEC type 1 record. This is a little more efficient than having to go into the dialog twice.

I always try to maximize my laziness^H^H^H^H^H^H^H^Hefficiency.