Messages and Codes

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.

Make sufficient storage available to the program running in the environment to enable the request to be satisfied.

ABEND U2001 indicates an unexpected condition within the nucleus for which a message could not be issued.

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.

On freeing the Com-plete HTTP server request's local storage stack area, it was found to be corrupt.

See below for storage corruption explanation.

While freeing storage within the Com-plete nucleus, a corruption failure was detected.

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.

An attempt was made to issue an INIT command to an HTTP server; however, the HTTP server was already active.

Not applicable

Not applicable

Not applicable

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.

• 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.

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.

• 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.

An attempt to start an HTTP server failed. The reason for the failure is indicated in a previously issued message.

Not applicable

Correct the problem that caused the HTTP initialization failure as specified in the preceding message.

Not applicable

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.

Determine if the request itself is valid and if so, increase the specification of the HTTP server configuration parameter URLPBUFL accordingly.

See section Customizing and Using the HTTP Server.

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.

Determine if the request itself is valid and, if so, increase the specification of the HTTP server configuration parameter CONTBUFL accordingly.

See section Customizing and Using the HTTP Server.

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.

Not applicable

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.

The HTTP V1/1 Protocol specification

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.

Not applicable

Not applicable

Not applicable

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.

Determine which client issued the HTTP request and correct its content length processing.

The HTTP V1/1 Protocol specification

A client requested that the URL indicated in placeholder $1 be returned; however, the URL does not exists.

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.

Not applicable

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.

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.

See section Running CGI Programs under SMARTS.

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.

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.

See section Installing Natural CGI.

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.

This is an informational message, no action is necessary.

Not applicable

The HTTP server has commenced its initialization processing.

Not applicable

Not applicable

Not applicable

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.

Use the returned information to identify the problem and correct it.

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.

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.

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.

Sockets errors generally occur when the peer program terminates the conversation, or a transport error occurs on the network.

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.

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.

The information on Security.

Something unexpected has occurred in the HTTP server nucleus. Additional errors are likely to follow any occurrence of this error message.

Report the error message and the steps taken to produce the error to your local support center.

Not applicable

The HTTP server is quiescing. In this state, current requests may continue to completion; however, no new requests are allowed.

Not applicable

This is an informational message: no action is necessary.

Not applicable

The default user ID specified is not authorized.

Check that the default user ID specified in the HMANCONF macro by the parameter HTTPUSER is valid.

The information on Security.

The URL requested by a client is invalid.

Specify a URL that the HTTP Server can understand. Refer to the appropriate IETF standards for information on what constitutes a valid URL.

Not applicable

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.

Determine from the Natural documentation why the return code is returned and correct the error.

Natural Installation and Operations documentation

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.

Restart the conversational application as appropriate.

Not applicable

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.

Increase the specification of the HTTP server configuration parameter RECVBUFL.

See section Customizing and Using the HTTP Server.

A call to the environment independent server interface failed.

One or more messages will be written to the console to indicate the nature of the error. Correct these problems and restart the server.

Not applicable

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.

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.

Not applicable

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.

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.

Not applicable

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.

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.

Not applicable

A call to the environment dependent interface failed. Environmental components are called for initialization, termination and for initialization of the listening task.

Report the error to your local support center.

Not applicable

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.

Determine who or what is attempting to start these programs in an incorrect way and force them to stop.

Not applicable

An error occurred for a request made to the Com-plete environment.

Note that in many cases these "errors" may be normal due to general activity on the TCP/IP network, for example.

The server cannot terminate correctly until all users have terminated. The message indicates the number of users upon which the server is waiting.

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.

Not applicable

The operator command identified in the message has been successfully issued to the server.

This is an informational message: no action is necessary.

Not applicable

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.

Not applicable

The HTTP Server installation ionformation.

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.

If the module should be available during initialization and/or termination processing, determine why it cannot be found.

Not applicable

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.

Determine from the return and reason codes why the LOAD request failed and correct the error.

z/OS Assembler Programmers Macro Reference Manual
VSE/ESA Assembler Programmers Macro Reference Manual

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.

Refer to preceding messages in the log to determine why the return code was issued. Correct the situation.

Not applicable

Initialization processing for the HTTP server identified by the $1 placeholder completed successfully.

Not applicable

Not applicable

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.

Not applicable

The HTTP server identified by the $1 placeholder terminated successfully.

Not applicable

Not applicable

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.

Issue a valid operator command.

See section Customizing and Using the HTTP Server.

The HTTP server identified by the $1 placeholder is initializing with the HTTP server configuration parameters specified by the $2 placeholder.

Not applicable

See section Customizing and Using the HTTP Server.

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.

• 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.

The information on installation, as well as customization and use of the HTTP Server.

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.

Not applicable

Ensure the POSIX SERVER statement appears before the HTTP SERVER statement(s) in the Com-plete sysparms.

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

Com-plete System Programming documentation

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.

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.

Section Customizing and Using the HTTP Server and section Installing Natural CGI.

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.

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.

Section Customizing and Using the HTTP Server and section Installing Natural CGI.

An internal error occurred during NATCGI processing. This message will usually be preceded by another error message.

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.

Not applicable

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.

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.

Section Customizing and Using the HTTP Server and section Installing Natural CGI. See also the Natural Programming and the Natural Security documentation.