Deployment Wizard troubleshooting checklist

1. Check the HODWIZARD.LOG for error messages.
2. Check that there is enough disk space.
3. If your clients use Netscape 6.1, check your applet size.
4. Double check that your values were saved correctly.
5. Troubleshooting Host On-Demand Deployment Wizard Unzip utility on z/OS

If you experience problems with the Deployment Wizard, check the following:

1. Check the HODWIZARD.LOG for error messages that the Deployment Wizard might have written as you created your files.
2. Check that there is enough space to write files on the workstation where the Deployment Wizard is running. Refer to your operating system documentation for information regarding disk space.
3. If your clients use Netscape 6.1, make sure that you select a value of Small, Medium, or Large in the Applet Size field under Appearance > Applet size in the Advanced Options tree view. The default value of Autosize to browser does not work.
4. Use the Deployment Wizard to edit the files again to verify that the values you set for your selections were saved correctly. If any values are incorrect, correct them and save your files, and then replace the files on the Host On-Demand server.
   
5. If you experience problems with the Deployment Wizard Unzip utility on z/OS, check the following:
   
1. The *.zip file was transferred in binary to the Host On-Demand Publish directory or user publish directory
2. The PASS rules in httpd.conf are correct, refer to the Program Directory in the InfoCenter.
   The variables in setInstPath.sh in the install directory are set correctly
3. DWunzip-S390 is being run from /usr/lpp/HOD/hostondemand/lib/samples/DWunzipCommandFiles directory
4. The relative path in DWunzip-S390 has not been changed. It should read
   . ../../../../setInstPath.sh
5. Verify JAVA_ENGINE variable in DWunzip-S390 points to the correct level
6. Verify the DWunzip-S390 shell script has the correct permissions of 755
7. Make sure you are not running out of heap or region size. 

8. Modify the DWunzip-S390 script as follows:
   if $JAVA_ENGINE -Xmx1m -Djava.compiler=NONE -classpath $DWUNCLASSPATH ..

This sets the maximum heapsize and turn off the JIT compiler to give you more space to load the classes.

If that does not work, you can telnet directly into UNIX System Services which gets around the region size restriction.