A fix is available
APAR status
Closed as new function.
Error description
The IBM Domino Go Web server will not be supported after z/OS 2.1. Web Access for IBM Tivoli Information/Management for z/OS V1.3 needs to be updated so it can run under the Apache web server on z/OS.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IBM Tivoli Web Access for IBM Tivoli * * Information management for z/OS users * * migrating to z/OS 2.2 or later * **************************************************************** * PROBLEM DESCRIPTION: IBM z/OS V2.2 has replaced the DominoGo * * Web Server with Apache for z/OS. The * * Apache API is not compatible with the * * DGW API, which renders Web Access for * * Infoman inoperable on systems running * * z/OS V2R2 or later * * Symptoms include ABEND806 accompanied * * by messages: * * CSV003I REQUESTED MODULE IMWHTTPD NOT * * FOUND * * CSV028I ABEND806-04 JOBNAME=xxxxxxxx * * STEPNAME=xxxxxxxx * * Additional search criteria: * * msgCSV003I msgCSV028I * * ABENDS806 S806 * **************************************************************** * RECOMMENDATION: Apply the PTF. * **************************************************************** An Apache module is required to enable Web Access to utilize various Apache server functions. Fix category: ZOS0202T/K
Problem conclusion
Temporary fix
Comments
This enhancement provides the following new samples stored in data set BLQ.V1R3M0.SBLMSAMP: * BLQUACFG - Sample Apache configuration directives Configures Apache so it can run Web Access. * BLQUAINS - sample JCL for building mod_InfoMan Apache module Performs final link edit process for dynamically binding mod_InfoMan with required Apache API services. * BLQUAPRC - Sample Apache server start up JCL procedure Starts an Apache instance with required Web Access and Infoman resources. Rexx routines BLQADMIN, BLQWRPFA, BLQWSSOF and BLQWSWRT are being modified to make them compatible with both DominoGo and Apache servers. The following information should be added to "IBM Tivoli Web Access for Information Management Planning, Installation, and Operations Guide", document number: SC32-1427-01, in Chapter 2: "Installation". Configuring Web Access for IBM Information Management for z/OS under IBM HTTP Server Version 9 for WebSphere Application Server for z/OS. This feature requires knowledge about administering an Apache web server configuration. Apache Documentation is available on the web at: http://httpd.apache.org. Familiarity with "IBM HTTP Server Version 9 for WebSphere Application Server for z/OS" is also required, the documentation for which is available on the web in the IBM Knowledge Center at: http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com. ibm.websphere.ihs.doc/ae/welcome_ihs.html The above two lines are the entire url which had to be split to fit within the margins of this file. Before you begin, read the instructions for creating an Apache server instance on z/OS. Configure Web Access for Information Management for z/OS, from here on refered to as WAI, to run under Apache on z/OS, by performing the following tasks: 1. Create an Apache instance to run WAI. On z/OS 2.2, Apache V2.4 is installed as part of z/OS. WAI is only compatible with the 31-bit version of Apache. Use an "install_ihs" command similar to: install_ihs -31 /etc/WAIWEB <non-SSL_port_number> and specify other options as desired. /etc/WAIWEB is the path where the new instance will be created, you may specify a more suitable name if needed. Verify that the new instance is functional. 2. Complete the installation of the Apache mod_InfoMan DLL. Modify the JCL in the Web Access SAMPLE library, (usually named BLQ.V1R3M0.SBLMSAMP) member BLQUAINS. You will need to change the JCL as described in that member to match path and library names at your installation. Submit the JCL which must complete with return code zero. It will complete the link edit of the mod_InfoMan DLL module for Apache and place it in the Info DLL library usually named BLM.V7R1M0.SBLMCMOD. NOTE: mod_InfoMan has only been tested with Apache V2.4. 3. Add a symbolic link to the Apache mod_InfoMan DLL as follows: ln -e BLMUAMOD /etc/WAIWEB/modules/mod_InfoMan.so Substitute /etc/WAIWEB with the path name of the Apache instance created in step 1. This will enable Apache to locate the mod_InfoMan DLL. 4. Create a subdirectory in the Apache configuration directory to contain Apache configuration directives required by Web Access. For example: mkdir /etc/WAIWEB/conf/local where /etc/WAIWEB is the name of the directory containing the Apache instance created in step one above. 5. Copy the sample Apache configuration directives for WAI installed in: /usr/lpp/InfoMan/web/samples/BLQUACFG into the "local" directory, created in step 2, nnaming it: /etc/WAIWEB/conf/local/BLQUACFG.conf again where /etc/WAIWEB/ is the path of the Apache instance created in step 1. 6. Modify the copied Web Access Apache configuration directives to contain the directory paths where Web Access is installed. 7. Modify the main Apache config file for the Web Access Apache instance, changing any directives to match your installation. There probably won't be any changes needed except that Web Access for Info can only run in a server with a single child instance. This is due to the use of "Rexx Global Variable Pools" which contain user session values which are stored in the memory of the child process. 8. Add an "include" directive in the main Apache config file for the Web Access Apache instance. For simplicity place it at the bottom of the file. include /etc/WAIWEB/conf/local/BLQUACFG.conf 9. Sample member BLQ.V1R3M0.SBLMSAMP(BLQUAPRC) contains an example of a JCL procedure which can be used to start the server instance. Make a copy of it and Modify the copy to conform to your installation and place it in a dataset in the PROCLIB concatenation. After completing the above steps/customizations, start the server instance and verify that WAI is available at: <url:portA/TESTME.REXX If needed, the following sources will contain helpful troubleshooting information: 1. The system log 2. The Apache STDOUT and STDERR files as specified in the Apache start up procedure. 3. The Apache error_log, usually located in the /etc/WAIWEBG/logs directory.
APAR Information
APAR number
OA45753
Reported component name
WEB ACC FOR INF
Reported component ID
5698WAI00
Reported release
320
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2014-07-30
Closed date
2015-12-18
Last modified date
2016-02-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA80183
Modules/Macros
BLQADMIN BLQUACFG BLQUAINS BLQUAPRC BLQWRPFA BLQWSSOF BLQWSWRT
SC32142701 |
Fix information
Fixed component name
WEB ACC FOR INF
Fixed component ID
5698WAI00
Applicable component levels
R320 PSY UA80183
UP15/12/23 P F512
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSWRDZ","label":"Tivoli Web Access for Information Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
11 February 2016