Messages and Codes

#### Search Results

Search

# Messages and Codes

This section contains messages and codes issued by the HTTP server components of the Com-plete system.

The explanation of the messages is organized as follows:

- Com-plete HTTP ABEND Codes

- HTTP Server Messages ( COMHTP Prefix)

#### Message Format

Com-plete HTTP server messages have the following format:

    COMHTPnnnn - message-id

where

HTP | identifies the HTTP subsystem as issuing the message.
nnnn | is a sequential message number identifying the message within the subsystem.
message-id | identifies the Com-plete address space issuing the message. This value is determined from the Com-plete configuration parameter MESSAGE-ID. It may be a single character in braces (e.g. (X)) or it may contain the installation ID as specified in the Com-plete configuration parameter INSTALLATION.

#### Message Documentation

Messages are documented with the message identifier (excluding the constant 'COM' which is always present) in the heading followed by the message text.

The message text appears something like the following:

    This is a test &1 with three (&2) replacement parms '&3'

When displayed or written to the console, the message contains the text as displayed; however, the placeholders identified by the '&n' construct are replaced by data relevant to the message.

If the data to be displayed is X, y, and AB, the message appears as follows:

    This is a test X with three (y) replacement parms 'AB'

Each message includes the following subsections:

Description | explains why the message was issued.
Placeholders | describes what each of the placeholders (that is, the '&n' values) contains. If the message contains no placeholders, the expression 'Not applicable' is written.
Action | describes the actions to be taken when this message is issued. A number of actions may be listed, if appropriate. If no action is required, the expression 'Not applicable' is written.
Additional References | describes any other additional source(s) of information that may further explain the message. A number of references may be listed, if appropriate. If no additional references are available, the expression 'Not applicable' is written.

## Com-plete HTTP ABEND Codes

### Overview of Messages

`ABEND U2000 | ABEND U2001 | ABEND U2002 | ABEND U2003`

ABEND U2000 | Insufficient Storage
Explanation | ABEND U2000 occurs when insufficient storage is available to obtain a primary control block within the Com-plete HTTP environment. It indicates a problem at a point where it is not possible to issue a Com-plete HTTP error message.
Action | Make sufficient storage available to the program running in the environment to enable the request to be satisfied.

ABEND U2001 | Logic Error in Com-plete HTTP Nucleus
Explanation | ABEND U2001 indicates an unexpected condition within the nucleus for which a message could not be issued.
Action | It could occur due to storage overwrites in the Com-plete HTTP environment or as a result of earlier errors in the environment. If none of these appears to be the case, report the problem to your local support center.

ABEND U2002 | Invalid Com-plete local storage stack area
Explanation | On freeing the Com-plete HTTP server request's local storage stack area, it was found to be corrupt.
Action | See below for storage corruption explanation.

ABEND U2003 | Storage Corrupted
Explanation | While freeing storage within the Com-plete nucleus, a corruption failure was detected.
Action | When storage is allocated, Com-plete puts a storage accounting prefix at the start of the storage and an identical suffix at the end of the storage. If these do not match when the storage is freed, this ABEND occurs. A mismatch indicates that either the user that allocated the storage requested "n" bytes but used more than "n" bytes thus overwriting the storage accounting area at the end; or a user of storage before the storage area being freed overwrote the prefix of the storage area. In any event, register 7 will point to the prefix accounting area of the storage. The length of the storage is found at register 7 + 4 (if it hasn't been corrupted) while the storage area itself returned to the user can be found at register 7 + 8.

## HTTP Server Messages ( COMHTP Prefix)

### Overview of Messages

`HTP0001 | HTP0002 | HTP0003 | HTP0004 | HTP0005 | HTP0006 | HTP0007 | HTP0008 | HTP0009 | HTP0010 | HTP0011 | HTP0012 | HTP0013 | HTP0014 | HTP0015 | HTP0016 | HTP0017 | HTP0018 | HTP0020 | HTP0021 | HTP0022 | HTP0023 | HTP0024 | HTP0026 | HTP0027 | HTP0028 | HTP0030 | HTP0031 | HTP0032 | HTP0033 | HTP0034 | HTP0035 | HTP0036 | HTP0037 | HTP0039 | HTP0040 | HTP0041 | HTP0042 | HTP0043 | HTP0044 | HTP0047 | HTP0048 | HTP0054 | HTP0055 | HTP0056 | HTP0057 | HTP9001 | HTP9002 | HTP9003 | HTP9005`

HTP0001 | HTTP server already active
Explanation | An attempt was made to issue an INIT command to an HTTP server; however, the HTTP server was already active.
Placeholder | Not applicable
Action | Not applicable
References | Not applicable

HTP0002 | Insufficient storage for $2 ($1 bytes)
Explanation | An attempt by the HTTP server to acquire storage failed due to insufficient storage either in a user program thread or in the Com-plete address space.
Placeholders |
$1 | Number of bytes that the system tried to acquire. The number may be suffixed with a 'K' or an 'M' to denote KBYTES or MBYTES, respectively. '0' indicates that the HTTP server was not in a position to determine the amount of storage that could not be acquired. This could occur if a request to an underlying system failed due to a storage shortage without indicating how much was required.
$2 | A character string indicating what the storage was for and possibly a four-digit code in braces indicating which control block this storage was for, if applicable.
- Action | If the storage is thread-related, use the ULIB utility to increase the catalog size of the HTTP server application program that suffered the error. Note that the thread sizes in general may have to be increased in the Com-plete region depending on how much thread space the application requires. If the storage is outside of the thread, there is a shortage of storage in the Com-plete region itself. Where possible, Com-plete will expand it storage areas so it is likely that such an expansion request failed thus resulting in this message. Check for other errors related to any attempted expansion for more details. The following table identifies the storage areas by name, where they may be located and what they are used for:
  Storage name | Location | Description
  --- | --- | ---
  Master control block (HMCB) | Above | The main control block used by the HTTP server; acquired from the Com-plete environment general buffer pool.
  Working storage | Above | The generic term used for storage acquired on a temporary basis. It will normally be allocated in the HTTP server application program thread.
  HTTP request areas (HPRQ and buffers) | Above | The main HTTP server request processing block and associated buffers acquired by the HTTP server request processing program HAANRQST from the application program thread.
  HTTP request header (HPRH) | Above | The request header control block acquired per request header found in any given HTTP request. It is allocated from the HTTP server request processing program (HAANRQST) thread.
  HTTP environment variable work area | Above | Area allocated from the HTTP server request program thread storage to issue 'putenv' requests to the Com-plete environment to build environment variables for CGI requests.

HTP0003 | Invalid parameter specified $1
Explanation | An invalid parameter was specified on the HTTP server startup. This may have been supplied in the Com-plete SERVER configuration parameter or operator command.
Placeholders |
$1 | The string presented as a parameter to the HTTP server, which was not recognized.
Action | Correct the Com-plete configuration parameter SERVER to start the HTTP server. Reissue the Com-plete operator command SERVER INIT with a valid parameter value.

HTP0004 | Server initialization failed
Explanation | An attempt to start an HTTP server failed. The reason for the failure is indicated in a previously issued message.
Placeholders | Not applicable
Action | Correct the problem that caused the HTTP initialization failure as specified in the preceding message.
References | Not applicable

HTP0005 | URL parameter data exceeds maximum ($1 Bytes)
Explanation | A user issued an HTTP request with a parameter on the URL that exceeded the length of the URL parameter area. The URL parameter is the data following the question mark, which in turn follows the actual URL itself. The URL parameter buffer is allocated based on the HTTP server configuration parameter URLPBUFL.
Placeholders |
$1 | The maximum URL parameter length of data in bytes that is acceptable to the instance of the HTTP server on which the error occurred.
Action | Determine if the request itself is valid and if so, increase the specification of the HTTP server configuration parameter URLPBUFL accordingly.
References | See section Customizing and Using the HTTP Server.

HTP0006 | Content length exceeds maximum ($1 Bytes)
Explanation | A user issued an HTTP request with content that exceeded the length of the allocated content area. The content of an HTTP request is the data that follows the last HTTP header provided for a request. The content buffer is allocated based on the specification of the HTTP server configuration parameter CONTBUFL.
Placeholders |
$1 | The maximum length of content data in bytes which is acceptable to the instance of the HTTP server on which the error occurred.
Action | Determine if the request itself is valid and, if so, increase the specification of the HTTP server configuration parameter CONTBUFL accordingly.
References | See section Customizing and Using the HTTP Server.

HTP0007 | Content length required for request
Explanation | Where content is provided for an HTTP request, a 'CONTENT-LENGTH' header must be provided on the request to determine how much content to expect. This message is issued when the last HTTP header is received that is followed by content data; however, no content length header has been received.
Placeholders | Not applicable
Action | Determine which client is submitting the HTTP request and change it to either submit no content data or to submit a content length header indicating how much content data will follow.
References | The HTTP V1/1 Protocol specification

HTP0008 | Server is not active
Explanation | An operator command has been issued to an HTTP server or an attempt has been made to terminate an HTTP server that is not active.
Placeholders | Not applicable
Action | Not applicable
References | Not applicable

HTP0009 | Content length '$1' invalid for request
Explanation | Content data has been provided on a HTTP request. Content data has been detected and a content length header has been provided; however, the content data provided was less than or greater that the length specified in the content length header.
Placeholders |
$1 | The length of data expected based on the length provided in the content length HTTP header.
Action | Determine which client issued the HTTP request and correct its content length processing.
References | The HTTP V1/1 Protocol specification

HTP0010 | URL '$1' not found
Explanation | A client requested that the URL indicated in placeholder $1 be returned; however, the URL does not exists.
Placeholders |
$1 | The URL as requested by the client program.
Action | This generally occurs for a dataset or dataset and member request. The HTTP server translates a URL of the form /a/b/c/ to a sequential dataset name of the form a.b.c , or a URL of the form /x/y/z to a PDS member name of the form x.y(z). The sequential dataset or PDS member as translated from the URL by the HTTP server was not found on the system. This indicates that either it doesn't exist or it has not been cataloged.
References | Not applicable

HTP0011 | Unable to load CGI program '$1'
Explanation | A request was issued that resulted in the URL being interpreted as a CGI request for the program identified by placeholder $1. This program was not available to the Com-plete address space and therefore the CGI request could not be completed.
Placeholders |
$1 | Name of the program identified by the CGI request which could not be loaded in the Com-plete region where the request was received.
Action | Determine if the request was valid and if it was, make the program available in the Com-plete region where the request should be processed.
References | See section Running CGI Programs under SMARTS.

HTP0012 | Natural startup module '$1' not found: '$2' NATCGI request failed
Explanation | A request was received by the HTTP server that resulted in an attempt to execute the Natural CGI program identified by the $2 placeholder. It was not possible to process this request as the Natural thread-resident portion identified by the $1 placeholder could not be loaded in the Com-plete region where the request was received.
Placeholders |
$1 | Name of the thread-resident Natural portion that is identified on the HTTP server configuration parameter NATTHRD.
$2 | Name of the Natural program that the Natural CGI request was attempting to execute.
Action | Correct the specification of the HTTP configuration parameter NATTHRD to identify the correct Natural thread portion; or make the Natural thread portion named available to the Com-plete region where the request was received.
References | See section Installing Natural CGI.

HTP0013 | Module $1 loaded
Explanation | The module identified by the $1 placeholder was loaded by the nucleus. This message is issued in the following cases: When more than one version of a module exists, it indicates which version of the module was loaded. For exits that may not normally be part of the nucleus, this indicates when an exit has been loaded and is active in the system.
Placeholders |
$1 | Name of the module that was loaded.
Action | This is an informational message, no action is necessary.
References | Not applicable

HTP0014 | Server initialization in progress
Explanation | The HTTP server has commenced its initialization processing.
Placeholders | Not applicable
Action | Not applicable
References | Not applicable

HTP0015 | Read error '$1' processing URL '$2'
Explanation | A URL identifying a sequential dataset or PDS member has been received. This dataset or PDS member has been found; however, an error occurred while reading the data to transmit it to the user.
Placeholders |
$1 | The error number returned by the Com-plete API function being used to read the dataset or PDS member. The HTTP server uses the 'gets' and 'read' functions to access data, so refer to the descriptions of these functions for details of the cause of the identified error number being returned.
$2 | The URL as requested by the user.
Action | Use the returned information to identify the problem and correct it.

HTP0016 | 'putenv' failed processing environment variables errno=$1
Explanation | When a CGI request is identified, the HTTP server must make a number of specific environment variables available to the CGI program. This is done by using the Com-plete API 'putenv' function to set the environment variables before calling the CGI program. This indicates that the function request failed and therefore one or more environment variables will not be available to the CGI program called.
Placeholders |
$1 | The error number as returned by the 'putenv' function.
Action | Based on the information returned, determine why the 'putenv' function failed and correct the problem. Normally, 'putenv' only fails when insufficient storage is available in the thread where the CGI program runs. This is determined by the size at which the HTTP server request processing module (default name HAANRQST) is catalogued using the ULIB utility.

HTP0017 | $1 Sockets $2 request error errno=$3
Explanation | The HTTP server uses the Com-plete API sockets functions to communicate with clients. This message indicates that the request indicated by the $1 placeholder failed with the error number indicated.
Placeholders |
$1 | Name of the sockets function request that failed
$2 | Error number
$3 | Error number
Action | Sockets errors generally occur when the peer program terminates the conversation, or a transport error occurs on the network.

HTP0018 | Access to URL '$1' forbidden
Explanation | A user attempted to access the URL identified by $1 but access to the resource was denied. This occurs depending on the specification of the HTTP server configuration parameter LOGON as follows: When LOGON=REQUIRED is specified, or LOGON=ALLOWED is specified and the user supplies authorization information (user ID and password) for the request, this error indicates that access to the resource based on the provided information was not granted. When LOGON=DISALLOWED is specified and the 'public' user ID does not have access to the requested resource, the user is not permitted to provide authorization information so the request is refused.
Placeholders |
$1 | The URL that the user attempted to access.
Action | If the resource should be accessible to users of the HTTP server in question, grant the necessary access rights. If not, determine why users are attempting to access the resource in question.
References | The information on Security.

HTP0020 | Internal logic error in $1+x$2
Explanation | Something unexpected has occurred in the HTTP server nucleus. Additional errors are likely to follow any occurrence of this error message.
Placeholders |
$1 | Name of the HTTP server nucleus program in which the error was detected.
$2 | Hexadecimal offset in the program where the error was detected.
Action | Report the error message and the steps taken to produce the error to your local support center.
References | Not applicable

HTP0021 | Server is quiescing
Explanation | The HTTP server is quiescing. In this state, current requests may continue to completion; however, no new requests are allowed.
Placeholders | Not applicable
Action | This is an informational message: no action is necessary.
References | Not applicable

HTP0022 | SAF Logon for default userid $1 failed
Explanation | The default user ID specified is not authorized.
Placeholders |
$1 | Default user ID
Action | Check that the default user ID specified in the HMANCONF macro by the parameter HTTPUSER is valid.
References | The information on Security.

HTP0023 | Invalid URL '$1'
Explanation | The URL requested by a client is invalid.
Placeholders |
$1 | The URL as requested by the client
Action | Specify a URL that the HTTP Server can understand. Refer to the appropriate IETF standards for information on what constitutes a valid URL.
References | Not applicable

HTP0024 | Natural initialization failure, RC=$1
Explanation | A request was received by the HTTP server that resulted in an attempt to execute a Natural CGI program. The Natural thread-resident portion that is identified on the HTTP server configuration parameter NATTRD was loaded, but an error occurred at startup.
Placeholders |
$1 | The return code received from the Natural thread-resident portion.
Action | Determine from the Natural documentation why the return code is returned and correct the error.
References | Natural Installation and Operations documentation

HTP0026 | Conversation $1 no longer exists
Explanation | When a conversation is started with a WWW browser, it is assigned an internal identifier known only to the HTTP server and the browser with which it is conversing. This error indicates that when the browser eventually sent data in response to a request, the original conversation no longer existed. This could occur due to a timeout, a system ABEND, or even a stored URL being sent minutes, hours, days, or even weeks after the conversation was terminated normally by the user.
Placeholders |
$1 | Name of the conversational cookie.
Action | Restart the conversational application as appropriate.
References | Not applicable

HTP0027 | Input buffer space $1 bytes exhausted
Explanation | This error occurs if pooled sessions are in use and the entire request from the user must fit into the input buffer. The message is longer than the input buffer length specified in the configuration for the HTTP server.
Placeholders |
$1 | The length of the buffer used for receiving input data from the network.
Action | Increase the specification of the HTTP server configuration parameter RECVBUFL.
References | See section Customizing and Using the HTTP Server.

HTP0028 | Server interface $1 request failed rc=$2
Explanation | A call to the environment independent server interface failed.
Placeholders |
$1 | The server function requested: initialization, termination, command
$2 | Return code
Action | One or more messages will be written to the console to indicate the nature of the error. Correct these problems and restart the server.
References | Not applicable

HTP0030 | HTTP header '$1' unrecognized
Explanation | A header was detected in an HTTP request that was not recognized by the HTTP server. The header is ignored and the request is processed normally, ignoring the specified header.
Placeholders |
$1 | Name of the header found in the HTTP request that was not recognized by the HTTP server.
Action | Report this to your technical support representative. While this is not an error as such, it is possible that the HTTP header should be recognized in a future release of the HTTP server.
References | Not applicable

HTP0031 | Unsupported request data $1/x$2
Explanation | In the unformatted portion of an HTTP request, the HTTP server expects data as specified in the HTTP V1/1 protocol standard. If more information than normal is provided, or if the HTTP server makes an error interpreting the request, this message is issued. The request is processed normally; however, the data indicated in the message placeholders is be taken into account in the processing of the request.
Placeholders |
$1 | The data provided on the request that the HTTP server ignored in character format.
$2 | The data provided on the request that the HTTP server ignored in hexadecimal format.
Action | Report this to your technical support representative. While this is not an error as such, it is possible that the HTTP request data should be recognized in a future release of the HTTP server.
References | Not applicable

HTP0032 | Header '$1' data '$2' ignored
Explanation | The HTTP server recognized the header identified by the $1 placeholder, however, it had to ignore the data as identified by the $2 placeholder. This generally occurs due to a shortage of working space in the HTTP server request processing areas. The request is processed, however, the ignored header data, as shown in this message, is not taken into account while processing the request.
Placeholders |
$1 | Name of the HTTP header for which the data was ignored.
$2 | The data (or at least the start of the data) that was ignored for the header identified by $1.
Action | Report this to your technical support representative. While this is not an error as such, it indicates that certain values within the HTTP server request interpretation processing may need to be reviewed.
References | Not applicable

HTP0033 | Environment interface $1 request failed rc=$2
Explanation | A call to the environment dependent interface failed. Environmental components are called for initialization, termination and for initialization of the listening task.
Placeholders |
$1 | The server function requested: ENVINIT, ENVTERM, or LISTINIT
$2 | Return code
Action | Report the error to your local support center.
References | Not applicable

HTP0034 | $1 Invalid data $2/x$3 for program
Explanation | One of the HTTP server thread processing programs HAANLIST or HAANRQST is started by a mechanism apart from the internal processing of the HTTP server. These programs expect specific parameters that can only be provided via the internal HTTP server mechanisms.
Placeholders |
$1 | Name of the program that was started with the invalid data.
$2 | The invalid data provided to the program in character format.
$3 | The invalid data provided to the program in hexadecimal format.
Action | Determine who or what is attempting to start these programs in an incorrect way and force them to stop.
References | Not applicable

HTP0035 | Com-plete API $1 Request failed rc=$2/errno=$3
Explanation | An error occurred for a request made to the Com-plete environment.
Placeholders |
$1 | Name of the request.
$2 | Return code.
$3 | Error number.
Action | Note that in many cases these "errors" may be normal due to general activity on the TCP/IP network, for example.

HTP0036 | Server waiting for $1 user(s) to terminate
Explanation | The server cannot terminate correctly until all users have terminated. The message indicates the number of users upon which the server is waiting.
Placeholders |
$1 | The number of users still active.
Action | Wait until all users have terminated and reissue the request to QUIESCE or TERMINATE the server. The server may be forced; however, this is not recommended due to the subsequent problems it can cause.
References | Not applicable

HTP0037 | Operator command $1 issued successfully
Explanation | The operator command identified in the message has been successfully issued to the server.
Placeholders |
$1 | Name of the operator command issued.
Action | This is an informational message: no action is necessary.
References | Not applicable

HTP0039 | HTTP server $1 active on port $2
Explanation | The HTTP listening task attached for the server indicated by the $1 placeholder has been started successfully and is now listening for incoming HTTP requests on the TCP/IP port identified by the $2 placeholder.
Placeholders |
$1 | Name of the HTTP server as specified on the Com-plete SERVER configuration parameter or operator command.
$2 | The TCP/IP port number on which the HTTP server is listening. This is set using the HTTP server configuration parameter PORT.
Action | Not applicable
References | The HTTP Server installation ionformation.

HTP0040 | Module not found $1
Explanation | The module identified by the $1 placeholder cannot be found. A request to the operating system to load the module has failed. Modules to be loaded by the HTTP server must be available either in the COMPLIB DD concatenation or system LNKLST for z/OS and MSP systems; or a library identified in the search path for z/VSE. If this message is issued during the initialization process, initialization fails if the module is required for the correct operation of the HTTP server. Otherwise, initialization continues. If this message is issued during the termination process, termination continues; however, depending on the function of the module, the termination process may not complete successfully.
Placeholders |
$1 | Name of the module that could not be found
Action | If the module should be available during initialization and/or termination processing, determine why it cannot be found.
References | Not applicable

HTP0041 | Module $1 load error rc=$2/$3
Explanation | The module identified by the $1 placeholder could not be loaded due to an error during LOAD processing. A request to the operating system to load the module failed for some reason other than the fact that the module could not be found. If this message is issued during the initialization process, initialization fails if the module is required for the correct operation of the HTTP server. Otherwise, initialization continues. If this message is issued during the termination process, termination continues; however, depending on the function of the module, the termination process may not complete successfully.
Placeholders |
$1 | Name of the module for which the LOAD request failed.
$2 | Return code from the operating system LOAD request.
$3 | Reason code from the operating system LOAD request.
Action | Determine from the return and reason codes why the LOAD request failed and correct the error.
References | z/OS Assembler Programmers Macro Reference Manual VSE/ESA Assembler Programmers Macro Reference Manual

HTP0042 | Module $1 issued return code $2
Explanation | A number of modules are called internally during HTTP server initialization and termination. These modules generally issue a 0 return code when they complete successfully. This message is issued when a module is called and its return code is not 0. When a non-zero return code is issued, the module responsible issues a message itself to indicate where the problem lies. Initialization processing continues if the return code is less than 8 and terminates if the return code is 8 or greater. Termination processing continues; however, if the return code is 8 or greater, there may be additional failures later in the termination process.
Placeholders |
$1 | Name of the module that issued the return code
$2 | Return code issued by the module identified by $1.
Action | Refer to preceding messages in the log to determine why the return code was issued. Correct the situation.
References | Not applicable

HTP0043 | Server $1 initialization successful
Explanation | Initialization processing for the HTTP server identified by the $1 placeholder completed successfully.
Placeholders |
$1 | Name of the HTTP server as specified on the Com-plete SERVER configuration parameter or operator command.
Action | Not applicable
References | Not applicable

HTP0044 | Server $1 terminating on port $2
Explanation | The HTTP server as identified in the $1 placeholder is no longer listening for incoming HTTP requests on the port specified by placeholder $2. This generally indicates that an error has occurred on the sockets 'listen' or 'accept' request, which in turn indicates that the TCP/IP connection has problems.
Placeholders |
$1 | Name of the HTTP server as specified on the Com-plete SERVER configuration parameter or operator command.
$2 | The TCP/IP port number on which the HTTP server was listening.
Action | Not applicable

HTP0047 | Server $1 terminated
Explanation | The HTTP server identified by the $1 placeholder terminated successfully.
Placeholders |
$1 | Name of the HTTP server as specified on the Com-plete SERVER configuration parameter or operator command.
Action | Not applicable
References | Not applicable

HTP0048 | Unrecognized operator command $1
Explanation | An operator command was issued to the HTTP server using the Com-plete SERVER operator command; however, the operator command was not processed because it was not recognized by the HTTP server.
Placeholders |
$1 | The operator command provided in the Com-plete SERVER operator command for the HTTP server that was not recognized by the HTTP server.
Action | Issue a valid operator command.
References | See section Customizing and Using the HTTP Server.

HTP0054 | Server $1 using $2 configuration
Explanation | The HTTP server identified by the $1 placeholder is initializing with the HTTP server configuration parameters specified by the $2 placeholder.
Placeholders |
$1 | Name of the HTTP server as specified on the Com-plete SERVER configuration parameter or operator command.
$2 | Name of the HTTP server configuration parameter module that will be used by this instance of the HTTP server for its configuration information.
Action | Not applicable
References | See section Customizing and Using the HTTP Server.

HTP0055 | Invalid configuration file $1 data=$2/x$3
Explanation | The HTTP server configuration file identified by the $1 placeholder starts with invalid data and thus cannot be used by the HTTP server for its configuration processing. The HTTP server initialization process terminates.
Placeholders |
$1 | Name of the configuration file found to be invalid.
$2 | The data found at the start of the invalid module in character format.
$3 | The data found at the start of the invalid module in hexadecimal format.
Ensure that the module was generated using the procedures and samples provided with Com-plete. Ensure that another module of the same name is not higher in the COMPLIB concatenation or z/VSE search path than the HTTP configuration module you wish to use.
References | The information on installation, as well as customization and use of the HTTP Server.

HTP0056 | Server cannot initialize - SMARTS environment not active
Explanation | The SMARTS environment must be active before the HTTP server can be activated. During its initialization processing, the HTTP server determined that the SMARTS environment was not active.
Placeholders | Not applicable
Action | Ensure the POSIX SERVER statement appears before the HTTP SERVER statement(s) in the Com-plete sysparms.

HTP0057 | Module '$1' attach failed rc=$2
Explanation | The HTTP server uses internal Com-plete functions to start new processes in the Com-plete region. An attempt to attach the program identified by the $1 placeholder failed. If this program is HAANLIST, no task was available to listen on the appropriate port for a given instance of the HTTP server. If the module name is HAANRQST (or an alternate name assigned by the user), that particular request itself fails; however, the HTTP server remains active and listening
Placeholders |
$1 | Name of the program for which the attach request failed
$2 | Return code from the Com-plete request issued as follows:
4 | Insufficient TIBs available in the system.
8 | Program to be attached was not found.
12 | Security error.
16 | Invalid program name to be attached.
20 | Insufficient space in the Com-plete general buffer pool.
Action |
RC | Action
--- | ---
4 | The number of TIBs available in the system is determined by the Com-plete configuration parameter TIBTAB.
8 | The program cannot be found if the HTTP server configuration parameter HTTPRQST specifies a program name that is not available to the Com-plete system.
8, 16 | Report these errors to your technical support representative.
20 | Review the Com-plete storage configuration parameters.
References | Com-plete System Programming documentation

HTP9001 | NATURAL PROGRAM '$1' not found in library '$2'
Explanation | A request was issued that resulted in the URL being interpreted as a NATCGI request for the Natural program $1, in the Natural library $2. This Natural program could not be located in the Natural library.
Placeholders |
$1 | Name of the Natural program identified by the NATCGI request.
$2 | Name of the Natural library in which the HTTP server is attempting to locate the Natural program. This could either have been supplied in the requesting URL or as a default in the configuration module.
Action | Determine if the request is valid, and the Natural program is available in the requested library. If it is, then check, and correct if necessary, the HTTP server parameters NATLIB, NATPARM and NATTHRD.
References | Section Customizing and Using the HTTP Server and section Installing Natural CGI.

HTP9002 | NATURAL Object '$1' in library '$2' not type 'Program' (is type '$3')
Explanation | A request was issued that resulted in the URL being interpreted as a NATCGI request for the Natural program $1, in the Natural library $2. This Natural object was located in the Natural library, but it is not of type program.
Placeholders |
$1 | Name of the Natural object identified by the NATCGI request.
$2 | Name of the Natural library in which the HTTP server is attempting to locate the Natural program. This could either have been supplied in the requesting URL or as a default in the configuration module.
$3 | The actual type of the Natural object:
M | is Map
L | is Local
C | is Global
N | is Subprogram
S | is Subroutine
Action | Determine if the request is valid, and the Natural program is available in the requested library. If it is, then check, and correct if necessary, the HTTP server parameters NATLIB, NATPARM and NATTHRD.
References | Section Customizing and Using the HTTP Server and section Installing Natural CGI.

HTP9003 | HAANUPR REQUEST failed, RC=$1 Reason=$2
Explanation | An internal error occurred during NATCGI processing. This message will usually be preceded by another error message.
Placeholders |
$1 | Error return code.
$2 | Error reason code.
Action | Check for a preceding error message and take action to correct that error. If no other error messages are available, report this error to your technical support representative.
References | Not applicable

HTP9005 | '$1'
Explanation | A Natural error condition has occurred while trying to execute a NATCGI program. The module HNANERR has gained control and issues the error message based on the status code.
Placeholders |
$1 | Error message text dependent on the error status code, as follows:
C | Command processing error
L | Logon processing error
O | Object time error
S | Non-correctable syntax error
Action | Check that the Natural CGI installation is correct. In the case of a 'Logon processing error' check the Natural Security settings. In particular, check that the default user ID (named in the HTTP server parameter HTTPUSER) has been correctly defined.
References | Section Customizing and Using the HTTP Server and section Installing Natural CGI. See also the Natural Programming and the Natural Security documentation.