z/OS Infoprint Server Messages and Diagnosis
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Diagnosing problems in Infoprint Central

z/OS Infoprint Server Messages and Diagnosis
GA32-0927-00

Diagnosing problems in Infoprint Central

To set up, customize, and diagnose problems with Infoprint Central, see:

Infoprint Central writes error messages to the z/OS® HTTP Server log file, httpd-errors.date. The default location is /usr/lpp/internet/server_root/logs/httpd-errors.date.

The service representative in the IBM® Support Center might ask you to run a trace to aid in diagnosing the problem. Be sure to stop the z/OS HTTP Server and then restart it before you run the trace. For more information, see Tracing Infoprint Server.

In addition, try these fixes before calling your IBM service representative:

Table 11. Installation problems with Infoprint Central
If you have this problem:Make sure:
z/OS HTTP Server does not startEach directive is coded on one line in the HTTP Server httpd.conf and httpd.envvars files.
Error 404 – Page not found or blank web page
  • The JCL in the z/OS HTTP Server points to the correct httpd.conf and httpd.envvars files if you start or stop the server from TSO.
  • The directives are in the correct order and are grouped correctly in the HTTP Server httpd.conf file. For information about how to specify directives, see z/OS Infoprint Server Customization.
JavaScript errorsThe directives are in the correct location in the HTTP Server httpd.conf file. For information about how to specify directives, see z/OS Infoprint Server Customization.
Date or time information is wrongThe value in the TZ environment variable is set to the same value in the HTTP Server httpd.envvars file and in either the aopstart EXEC or the AOPSTART procedure.
Table 12. Browser problems with Infoprint Central
If you have this problem:Make sure:
JavaScript errors or incorrect web page formatsYou use the correct version of a supported web browser.
Incorrect or outdated information
  • You customize the settings in the web browser to retrieve the latest pages from the web so that the Infoprint Central refresh function works correctly.
  • You periodically refresh the Infoprint Central web page to update the latest information.
Search criteria not savedYou enable cookies in the web browser.
Unexpected informationThe value in the LC_ALL environment variable is set to the same value in the HTTP Server httpd.envvars file and in either the aopstart EXEC or the AOPSTART procedure.
Table 13. Other problems with Infoprint Central
If you have this problem:Do this:
HTTP error or blank web page
  1. Look in the z/OS HTTP Server log file, httpd-errors.date. If the log contains the message “Address Space Dirty”, the extended attributes that SMP/E set during installation might have been modified. During installation, SMP/E marks the aopcentral.so and aopeapi.dll files program-controlled. Use the z/OS UNIX extattr command to verify that these files are program-controlled:
    • /usr/lpp/Printsrv/lib/aopcentral.so
    • /usr/lpp/Printsrv/lib/aopeapi.dll
    • /usr/lpp/Printsrv/lib/aop.so
    If you installed Infoprint Server in a directory other than /usr/lpp/Printsrv/lib, display the attributes of these files in that directory. If the problem persists, stop the server and look in the z/OS HTTP Server's SYSOUT data sets on the HOLD queue for more information.
  2. Clear the cache from the web browser. For example, for Microsoft Internet Explorer, select Tools –> Internet Options –> General –> Delete Files –> Delete all offline content.
Timeout errorsNarrow the search in Infoprint Central by specifying more precise search values, increase the HTTP Server's timeout value (OutputTimeout directive), or decrease the maximum number of objects that Infoprint Central displays after a search (AOPLIMIT environment variable).
Infinite loop in Netscape with Find Printer DefinitionsWiden the web browser window slightly.
Response is slow
  • Start a separate z/OS HTTP Server that Infoprint Central uses exclusively.
  • Use the z/OS HTTP Server tuning parameters to tune it.
Incorrect national language characters in Location fieldsSet the AOPCENTRAL_CODEPAGE environment variable (national language characters are those that are not encoded using the IBM-1047 code page).
An action could not be performed because of an Infoprint Server logic errorLook in the z/OS HTTP Server log file, httpd-errors.date. If the log contains a message in this format: 
----IPA/Penguin Error:----
message="...."
For example: 
message="DeviceControlFactory:  
{timeout=200 snmp_readCommunityName=\"public\"...
  1. Make sure that the required jar files (ipa.jar, modelplugin.jar, penguin.jar, and snmp.jar) are installed in the default directory (usr/lpp/Printsrv/classes) or in the directory specified in the CLASSPATH statement.

    If the files specified in the CLASSPATH statement are installed in the default directory, comment out the CLASSPATH statement and restart the z/OS HTTP Server.

  2. Check the CLASSPATH syntax and spelling. Also make sure that no trailing space characters exist.

    Tip: Use the ishell facility to browse the /etc/httpd.envvars file. While browsing the file turn hex on. Remove any trailing X'40' data in the statements.

  3. Remove any directories from the CLASSPATH statement that Infoprint Central does not require, and restart the z/OS HTTP Server.
  4. Make sure that Java™ 5.0 or Java 6.0 is installed and that JAVA_HOME is set correctly.
  5. If the Infoprint Central trace is turned on (AOPTRACEON=1 in /etc/httpd.envvars), make sure that the permissions are set correctly for the trace file. AOPTRACEDIR specifies the directory where trace files are created. The user ID of the user who starts the z/OS HTTP Server must have permission to write to the specified trace directory, and the trace directory must exist.

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014