Net.Data Reference Guide

Problem Analysis

For the following problems, assume that the Net.Data CGI-BIN program object, DB2WWW, has been moved to a library named WWWCGI, where CGI-BIN programs reside.

• Symptom: Error 500 (text of message follows)

      Bad script request -- '/QSYS.LIB/WWWCGI.LIB/DB2WWW.PGM/
      QSYS.LIB' not executable
  

  Cause: Incorrect Exec rule

  Exec /QSYS.LIB/WWWCGI.LIB/DB2WWW.PGM/*
  Exec /qsys.lib/wwwcgi.lib/db2www.pgm/*
  

  Solution: Specify an Exec rule that only supplies the path to the DB2WWW program. For example:

  Exec /QSYS.LIB/WWWCGI.LIB/*
  Exec /qsys.lib/wwwcgi.lib/*
  

• Symptom: Error 404(Text of message follows)

      Not found - file doesn't exist or is read protected
      Yeven tried multi"
  

  Cause: There is an Exec rule missing.

  Solution: Specify an Exec rule that supplies the path to the DB2WWW program in both upper and lower case. For example:

  Exec /QSYS.LIB/WWWCGI.LIB/*
  Exec /qsys.lib/wwwcgi.lib/*
  

• Symptom: Error 403(Text of message follows)

      Forbidden - by rule
  

  Cause: A Map or Exec rule is missing or incorrect.

  Solution: Specify a Map and Exec rule for the DB2WWW program in both upper and lower case. For example:

  Map /cgi-bin/db2www/* /QSYS.LIB/WWWCGI.LIB/DB2WWW.PGM/*
  Map /CGI-BIN/DB2WWW/* /QSYS.LIB/WWWCGI.LIB/DB2WWW.PGM/*
  Exec /QSYS.LIB/WWWCGI.LIB/*
  

• Symptom: Configuration Statements Correct but Net.Data Not Working. This problem occurs when all configurations are present and correct but Net.Data is still not serving data or documents correctly (or at all). There are several possible causes and solutions:

  • Cause: Map, Exec or Pass rules are not in the correct order.

    Solution: When a URL is evaluated against a Map, Exec or Pass rule, it is acted on based on the first matching rule. Therefore, you must be very careful to ensure that the statement to be evaluated is not remapped or altered prior to reaching the desired rule. Also, make sure that the user does not have a "Pass /*" in their configuration file.

  • Cause: User profile QTMHHTP1 does not have proper authority to access Net.Data macros.

    Solution: All CGI-BIN programs run under the user profile QTMHHTP1. The QTMHHTP1 user profile must be granted authority to all objects that Net.Data will access while processing a Net.Data macro.

  • Cause: Path statements in the Net.Data initialization file are not correct.

    Solution: Net.Data uses the path statements in the initialization file (if there is one) to resolve to any Net.Data macro or executable references in the Net.Data macro that is being processed. If the object references are not fully qualified and the path statements in the initialization file are not correct, Net.Data will indicate that the object being referenced is not found. Therefore, you must make sure that either the object references are fully qualified or the Net.Data initialization file has the proper path statements.