- Review the steps in the Program Directory.
The Program Directory is located in the
Host On-Demand Information Center under 'Books'.
 |
For more troubleshooting information, check the Hints and Tips
section of the Program Directory. |
- Review zSeries information in the Planning, Installing, and Configuring
Host On-Demand guide.
Refer to the Configuring Host On-Demand on
zSeries section in the Planning, Installing, and Configuring Host On-Demand
guide for information
such as using the configuration servlet
and setting up separate read/write private and publish directories on the zSeries
operating systems.
- 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.
- Verify your application of the manufacturing refresh
(PTF) or refresh pack (APAR).
- Manufacturing refreshes (PTF) and refresh packs are available
at the Service Key site.
Use hod80ptf.sh to install
a Manufacturing Refresh according to the
++HOLD information in the manufacturing refresh. The hod80ptf.sh completes the
installation started by the SMP/E program by coping the files
into the Host On-Demand directory structure.
- Use hodxxmvs.aupsh to install the Refresh Pack.
Follow the instructions provided on the service key Web site.
- Check the ++HOLD information.
If you recently applied a manufacturing refresh, review the ++HOLD information for the manufacturing refresh.
- 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.
- 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.
- Check the PATH, LIBPATH, and CLASSPATH values.
Verify that the environment variables have been modified
for Java.
- For PATH use:
echo 'PATH='$PATH
- For LIBPATH use:
echo 'LIBPATH='$LIBPATH
- If you are using Java 1.1.8, also verify that the CLASSPATH variable is set.
- Check for error messages.
- Check the NCoDServices.RAS.txt file for errors with the Service Manager. This file can
be found in the /private directory. IBM Support may ask for a Service Manager trace that
can be started, stopped, and viewed via the Host On-Demand Adminstrator 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 ...\hod\hostondemand\private directory. The file is
recreated each time you start Host On-Demand. It is an ASCII file and must be FTPed in
binary mode to an ASCII machine when you are sending it to IBM Support.
- Check the STDERR and STDOUT files if you experience problems while starting or
running the Service Manager.
- 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 HOD.stdout in the ...\HOD\
private\ directory. Save a copy of the NCoDServices.RAS.txt, HODstd, STDERR, and
STDOUT files.
- Confirm that you have correctly moved your Host On-Demand Deployment Wizard files
to the zSeries computer.
- 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.
- Verify the DWunzip-S390 shell script has the correct permissions
of 755.
- You can verify the Deployment Wizard files are correctly installed by checking the following:
- The HTML files you created with the Deployment Wizard are in the publish
directory (../hostondemand/HOD) or in the
alternate read/write publish directory
with .ascii appended to the name.
- The other files are in the ../HOD/HODData/htmlname directory
with permission bits of 755, where htmlname is the name of your HTML file.
- All TXT files named are appended with .ascii in the
../HOD/HODData/htmlname directory, where htmlname is the name of your HTML file.
- Check httpd.conf when upgrading Host On-Demand.
When upgrading from Host On-Demand Version 5,6, or 7, remember to modify the
httpd.conf file to change the Pass directives for the PROPS, PROPERTIES and JS files.
You must change the names to include the .ascii extension. If these Pass rules are not
changed, the clients will not download because the files cannot be found.
Review the Program Directory for more information on this topic.
- 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 Host On-Demand Adminstrator by taking the following steps:
- Select OS/400 Proxy Server in the left frame of the Administrator client.
- Select the No radio button.
- Click Apply.
- Recycle the Service Manager to reflect the change.
Once you complete these steps, port 3470 will no longer be opened.
- Are you getting an error message when migrating from an earlier version
of Host On-Demand?
If you are migrating from Host On-Demand V6 or earlier, you may get the following error message
when starting the Service Manager:
Error - Incorrect install path; NCServiceManager not started
To avoid this message, move the NSMprop file into the /private directory.
- Are you experiencing printing problems with the zSeries server?
If you are experiencing printing problems on zSeries, see 3270 host printing troubleshooting checklist.
- Compress files to send to IBM.
The IBM 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 IBM Support Team.
