XCICS-supplied default analyzer program DFHWBAHX

XCICS supplies a default analyzer program, DFHWBAHX. If you need to provide request handling through your analyzer program, as well as or instead of through URIMAP definitions, you can use DFHWBAHX itself as a starting point for writing your own analyzer program. It is C language program and ut is located in the $XFRAMEHOME/xcics/src directory.

 
As supplied, DFHWBAHX does not perform any analysis of a request when a matching URIMAP definition has been found for the request, even if the URIMAP specifies "analyzer=yes". This means that the settings specified in the URIMAP definition for the alias transaction, converter program and application program are automatically accepted and used to determine subsequent processing stages.

DFHWBAHX uses the wbra_urimap input parameter to test for the presence of a URIMAP definition, and if the result is positive, returns without performing any analysis on the request URL.

Otherwise it interprets the HTTP requests in which the path component of the URL has the following syntax:

_/_converter_/_alias_/_program_ ___________ _________ _
                  |_/_ignored_|_?_token_|

 
All fields processed by the analyzer program are translated to upper case.

After translation:

converter: Specifies the name of the converter program to be used for the request. It can be up to eight characters in length. As a special case, the four character value 'CICS' denotes that no converter program is used.

alias: Specifies the transaction ID of the alias transaction for subsequent request processing. It can be up to four characters in length.

program: Specifies the name of the XCICS application program that is to be used to service the request. It can be up to eight characters in length.

ignored: This part of the path is ignored by DFHWBAHX (but may be used by the converter program or the application program).

token: The first eight bytes specify the user token that is passed to the converter program. Data following the first eight bytes of the token is ignored by DFHWBAHX (but may be used by the converter program or the application program).

 
Responses from DFHWBAHX

The meanings of the responses produced by DFHWBAHX are as follows:

URP_OK: The analyzer found that the request conformed to the default HTTP request format, and generated the appropriate outputs for
the alias.

URP_EXCEPTION: The analyzer found that the request did not conform to the default format.

URP_INVALID: The eye-catcher was invalid. This indicates an internal error.