Troubleshooting Guide

Table of contents

IBM eServer zSeries Troubleshooting Checklist

  1. Review the steps in the Program Directory.
  2. Review zSeries information in the Planning, Installing, and Configuring Z and I Emulator for Web guide.
  3. Confirm that the base product was installed with SMP/E.
  4. Verify your application of the manufacturing refresh (PTF) or refresh pack (APAR).
  5. Check the ++HOLD information.
  6. Check for quotation marks in the shell script.
  7. Check the Java level.
  8. Check the PATH and LIBPATH values.
  9. Check for error messages.
  10. Confirm that you have correctly moved your Z and I Emulator for Web Deployment Wizard files to the zSeries computer.
  11. Check that the OS/400 Proxy server port is open.
  12. Are you experiencing printing problems with the zSeries server?
  13. Compress files to send to HCL.

  1. Review the steps in the Program Directory.

    The Program Directory is located in the Z and I Emulator for Web Information Center under 'Books'.

    Note: For more troubleshooting information, check the Hints and Tips section of the Program Directory.

  2. Review zSeries information in the Planning, Installing, and Configuring Z and I Emulator for Web guide.

    Refer to the Configuring Z and I Emulator for Web on zSeries section in the Planning, Installing, and Configuring Z and I Emulator for Web guide for information such as using the configuration servlet and setting up separate read/write private and publish directories on the zSeries operating systems.

  3. Confirm that the base product was installed with SMP/E.

    After confirming that the product was installed with SMP/E, verify that the appropriate hod80mvs.sh script was executed to create the directory structure. Move the files into the file struture.

  4. Verify your application of the manufacturing refresh (PTF) or refresh pack (APAR).

  5. Check the ++HOLD information.

    If you recently applied a manufacturing refresh, review the ++HOLD information for the manufacturing refresh.

  6. Check for quotation marks in the shell script.

    Check the shell scripts to make sure there are no quotations (") on any of the path statements.

  7. Check the Java level.

    Use the java -fullversion command to check the level of Java. Then verify the version with the information in the Program Directory.

  8. Check the PATH, LIBPATH, and CLASSPATH values.

    Verify that the environment variables have been modified for Java.

    1. For PATH use: echo 'PATH='$PATH
    2. For LIBPATH use: echo 'LIBPATH='$LIBPATH
    3. If you are using Java 1.1.8, also verify that the CLASSPATH variable is set.

  9. Check for error messages.
    1. Check the NCoDServices.RAS.txt file for errors with the Service Manager. This file can be found in the /private directory. HCL Support may ask for a Service Manager trace that can be started, stopped, and viewed via the Z and I Emulator for Web Administrator function under the Services option. See Service Manager Trace for more information. This will record additional debug information in the NCoDServices.RAS.txt file. The file is located in the ...\zieweb\zieforweb\private directory. The file is recreated each time you start Z and I Emulator for Web. It is an ASCII file and must be FTPed in binary mode to an ASCII machine when you are sending it to HCL Support.
    2. Check the STDERR and STDOUT files if you experience problems while starting or running the Service Manager.
    3. If the problem occurs when starting the Service Manager, edit the ServiceManager.sh file to change the Java command being executed. Add a # symbol in front of the Java command being executed and remove the # symbol for the Java command after the comment. This line is for problem determination and outputs to ZIEWeb.stdout in the ...\ZIEWeb\ private\ directory. Save a copy of the NCoDServices.RAS.txt, ZIEWebstd, STDERR, and STDOUT files.

  10. Confirm that you have correctly moved your Z and I Emulator for Web Deployment Wizard files to the zSeries computer.
    1. Use the DWunzip utility to set up these files. DWunzip uses the ZIP file created by the Deployment Wizard. DWunzip will uncompress the files into the correct directory with the correct permissions. You will need to FTP the ZIP file to the host in binary format.
    2. Verify the DWunzip-S390 shell script has the correct permissions of 755.
    3. You can verify the Deployment Wizard files are correctly installed by checking the following:
      1. The HTML files you created with the Deployment Wizard are in the publish directory (../zieforweb/ZIEWeb) or in the alternate read/write publish directory with .ascii appended to the name.
      2. The other files are in the ../ZIEWeb/ZIEWebData/htmlname directory with permission bits of 755, where htmlname is the name of your HTML file.
      3. All TXT files named are appended with .ascii in the ../ZIEWeb/ZIEWebData/htmlname directory, where htmlname is the name of your HTML file.
  11. Check that the OS/400 Proxy server port is open.

    If you are concerned about the OS/400 Proxy server port being opened on the OS/390 Service Manager, you can disable it in the Z and I Emulator for Web Administrator by taking the following steps:

    1. Select OS/400 Proxy Server in the left frame of the Administrator client.
    2. Select the No radio button.
    3. Click Apply.
    4. Recycle the Service Manager to reflect the change.
    Once you complete these steps, port 3470 will no longer be opened.
  12. Are you experiencing printing problems with the zSeries server?

    If you are experiencing printing problems on zSeries, see 3270 host printing troubleshooting checklist.

  13. Compress files to send to HCL.

    The HCL Support Team may request a compressed version of your private directory. To compress the contents, cd to the /private directory and issue the following command: 

    pax -wzvf /tmp/private.pax.Z *

    You can send the file that is generated to the HCL Support Team.

Top of page Table of contents