Installation on z/OS

Software AG recommends that you keep unmodified copies of all materials distributed or created as part of the installation process. This may assist with problem diagnosis later by providing an untouched sample of any given item.

Note:
Additional installation steps for Natural CGI are documented in section Installing Natural CGI.

This document covers the following topics:

The Installation Tape

Tape Contents

The following table lists the product datasets, what the dataset contains, and how it is created. While you are free to rename the datasets, the dataset names used in the table are used consistently throughout the product documentation to ensure clarity.

Dataset Contains ...
HTPvrs.LOAD all load modules required by Com-plete HTTP server
HTPvrs.SRCE all sample source members and macros
HTPvrs.JOBS all sample JCL required
HTPvrs.INPL an INPL file for Natural modules and example programs (required only for Natural CGI)

Copying Contents of the Tape to Disk

Copy the installation datasets to disk.

Step-by-Step Installation

Step 1: Modify the Com-plete Start-up Procedure or Job

  • Include the following datasets in the COMPLIB dataset concatenation: 

    // DD DISP=SHR,DSN=HTPvrs.LOAD

    You may optionally add the following DD statement in the JCL to direct output to a specific job class or dataset:

    HTPTRCE the HTTP server trace output when HTTP server tracing is active

Step 2: Configure the HTTP Server

  • Copy member HAANCONF from HTPvrs.SRCE and use it as a pattern for setting up your configuration. For a basic installation, modify only the port number, leaving the fine-tuning for later.

    The default port numbers are 80 for HTTP and 443 for HTTPS. If the desired port number is not available on the default IP address of your machine, you must either specify some other port number in parameter PORT here, or a different IP address in Com-plete sysparm IPADDRESS. If in doubt, ask your TCP/IP administrator.

    Store the configuration member into some parmlib, e.g. MY.PARMLIB(HAANCONF).

Step 3: Modify the Com-plete Start-up Parameters

  • Add a parameter

    SERVER=(HTTP,HAENSERV,CONF=/my.parmlib/haanconf)

    specifying the configuration member created in the previous step.

Where Next ?

Restart Com-plete in order to pick up the changes made above.

From a web browser, enter

http://ip-addr:port

where

ip-addr is the IP address of the TCP/IP subsystem where the HTTP server is running
port is the port number specified in your HTTP server configuration

You should get the start page of the Com-plete web interface, or whatever resource you specified in the DFLTURL parameter in your HTTP server configuration.

Troubleshooting

Com-plete Initializes, but the HTTP Server Initialization Fails

The HTTP server configuration is probably invalid.

  • Check for messages during the HTTP server initialization process that may identify the problem.

  • Check in particular for socket errors that occur if the specified port is already in use by another application in your system.

The HTTP Server Initializes, but Access Attempts Fail

The problem is probably in the request being issued or the port number being used. Ensure that

  • the IP address or host name used to identify the target host actually identifies the TCP/IP stack with which Com-plete is communicating. More than one IP address is possible on a mainframe system: if you use the wrong one, your request will time out or be rejected.

  • you can connect to the IP addresses by pinging that node. If the ping fails, you have no physical connection to that host.

  • the port specified is the one the HTTP server is configured to work with.

Where Next?

Familiarize yourself with the customization and configuration options available in the product. Following the customization sections are a number of sections detailing specific functionalities and their implementation.

For specific information about the programming interfaces and how to use them, refer to the section Programming CGI Requests.