IBM eServer iSeries troubleshooting checklist

1. Are you experiencing problems with your Host On-Demand installation?
2. Confirm that the Service Manager is running.
3. Check the Java level on the iSeries server.
4. Check the job log for QHODSVM for error messages.
5. Check the Start Job.
6. Is the Web server configured properly?
7. Are you experiencing printing problems with the iSeries server?
8. Are you experiencing Host File Transfer problems with the iSeries server?

1. Are you experiencing problems with your Host On-Demand installation?
   • If you are installing Host On-Demand for the first time, read the following sections in the Planning, Installing and Configuring Host On-Demand guide:
   • Installing on iSeries
   • Configuring Host On-Demand on iSeries
   • If you are installing Host On-Demand on a system where Host On-Demand already exists, verify that you have stopped the Host On-Demand Service Manager prior to installing a new version of the software. Use the ENDHODSVM command to stop the Service Manager.

2. Confirm that the Service Manager is running.
   1. At the command line, enter WRKACTJOB.
   2. Look for the QSYSWRK SUBSYSTEM:
   • Job QHODSVM should be in TIMW state.
   • Job QJVACMDSVR should be in JVAW state.

3. Check the Java level on the iSeries server.

   To check which level of Java the iSeries server is using by default, do the following:

   1. At the command line, type QSH to use qshell.
   2. Type java -version.

   If it returns version 1.3.1 and you have configured your Host On-Demand session to use Java 1, then do one of the following:

   • Configure your iSeries server to use Java version 1.1.8 for Java 1, or
   • Configure the Java options property in one of the following two ways:
     1. Review the installed licensed program product OPTIONS for IBM Developer Kit for Java. You can display this information via the 'Display Software Resources' iSeries server command DSPSFWRSC or via the 'Work with Licensed Programs' menu (GO LICPGM). The Product Option column provides information about installed optional parts for that licensed program. If a newer JDK is now installed, the Host On-Demand server uses it by default. If you do not want to use this JDK, modify the Java Options parameter in the Service Manager configuration to point to the JDK level of choice.
     2. Complete the following steps from the Host On-Demand Main Menu (GO HOD):
        1. Select option 3: End Host On-Demand Service Manager (ENDHODSVM).
        2. Select option 1: Configure HOD Service Manager (CHGHODSVM).
        3. Page down to the Java Options parameter and add the desired JDK value to the PROP parameter: (java.version ''n.n''), where n.n = 1.1.8, 1.2, 1.3, or later.

           The '' is not a double quote mark, but rather two single quotes.

           The Java options field should now be similar to the following:

           Java options . . . . . . . . . . > 'OPTIMIZE(10) PROP((java.version ''n.n'') 
           	 (os400.verify.checks.disable 3)) OPTION(*VERBOSE)'

        4. Restart the Service Manager.
   • Use the Deployment Wizard to change your Host On-Demand application page to auto-detect the user's level of Java 1 or Java 2.

The following are the minimum levels of Group PTFs recommended.

• V5R1: SF99069
• V5R2: SF99169

To verify your i5/OS or OS/400 operating system has the latest level of fixes for Java, do the following:

• Use the Display Data Area command for OS/400 V5.1 and earlier, for example, DSPDTAARA QJAVA/SFnnnnn, where SFnnnnn is the Group PTF identifier for the OS/400 Version/Release you are using.
• For OS/400 V5R2, use the WRKPTFGRP PTFGRP(SF99169) command. Install is the correct status returned by this command when you apply the Group PTF.

Java PTFs must be ordered separately from the cumulative fixes. PTFs can be found at http://www-912.ibm.com/supporthome.nsf/document/17403848.

4. Check the job log for QHODSVM for error messages.
5. Check the Start job.
   1. At the command line, enter GO HOD.
   2. Select option 1.
      • If no DATA - Enter the command DLTDTAARA QUSRSYS/QHODCFGD, then select option 1 again.
      • If the start job is still blank, repeat these steps.

6. Is the Web server configured properly?

   If you are not able to access http://server_name/hod/HODMain.html, you should check your Web server settings. First take the following steps to verify that the HTTP server is running:

   Alternately, you can perform these steps through the Web interface, for example, http://fullyqualifiedsystemname:2001. You will need to start the HTTP ADMIN instance first.

   1. Stop the Web server using the following command:

      ENDTCPSVR *HTTP HTTPSVR(DEFAULT) 

      Note that this command assumes that you are using the default instance of the IBM HTTP server. If you created an instance other than the default supplied by IBM, substitute the name of the instance created for Host On-Demand in this command. For example, if you created an instance called HODWEBSVR, enter the following to stop the instance:

      ENDTCPSVR *HTTP HTTPSVR(HODWEBSVR) 

   2. Configure the Web server using the following command:

      WRKHTTPCFG 

      Make sure that active Enable POST and Enable GET entries exist and are not commented out. Add the following entry (there must be one space before the first slash (/) and after the first asterisk (*)):

      pass /hod/* /QIBM/ProdData/hostondemand/HOD/* 

      This entry creates an alias, hod, for the path to the Host On-Demand files. You must type it exactly as you typed the original directory names, matching upper and lower case.

      Press F3 to exit the WRKHTTPCFG tool.

   3. Start the Web server using the following command:

      STRTCPSVR *HTTP HTTPSVR(DEFAULT)

7. Are you experiencing printing problems with the iSeries server?
   1. Refer to the iSeries printing problems checklist.

8. Are you experiencing Host File Transfer problems with the iSeries server?
   1. Refer to Host File Transfer troubleshooting checklist.