ibm program directory for ibm rational host on-demand version 11 v11.00.00 program number 5733-a59...

IBMProgram Directory for

IBM Rational Host On-Demand

Version 11

V11.00.00

Program Number 5733-A59

FMID HHOJB00

for Use withz/OS V1.08.00 and higher

Document Date: November 2009

GI11-9140-00

Note

Before using this information and the product it supports, be sure to read the general information under 7.0, “Notices” onpage 40.

A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM anonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1997, 2009. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Host On-Demand Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Host On-Demand FMIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.0 Program Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1 Basic Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2 Optional Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2.1 Basic Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2.2 Optional Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3 Program Source Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.4 Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.0 Program Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.1 Program Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2 Preventive Service Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.3 Statement of Support Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.0 Program and Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.1 Program Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.2 Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.0 Installation Requirements and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1 Driving System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.1.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.2 Target System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2.1 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2.2 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.2.2.1 Installation Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2.2.2 Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.2.2.3 Toleration/Coexistence Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145.2.2.4 Incompatibility (Negative) Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5.2.3 DASD Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145.3 FMIDs Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.4 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6.0 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.1 Installing Host On-Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.1.1 SMP/E Considerations for Installing Host On-Demand . . . . . . . . . . . . . . . . . . . . . . . 216.1.2 SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.1.3 SMP/E CALLLIBS Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.1.4 Sample Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Copyright IBM Corp. 1997, 2009 iii

6.1.5 Perform SMP/E RECEIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.6 Allocate SMP/E Target and Distribution Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.7 Allocate File system Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.8 Create DDDEF Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246.1.9 Perform SMP/E APPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256.1.10 Perform SMP/E ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.1.11 Run REPORT CROSSZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6.2 Activating Host On-Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276.2.1 Completing the Installation of Host On-Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.2.2 Update Web Server Pass Rules and Resource Mapping Directives . . . . . . . . . . . . . . . 296.2.3 Start Host On-Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.2.4 Configuring Host On-Demand (Administration) . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.2.5 Starting the Optional Native (Platform) Authentication Service . . . . . . . . . . . . . . . . . . 31

6.2.5.1 Setup for Starting the Native Authentication Service . . . . . . . . . . . . . . . . . . . . . 326.2.5.2 Starting the Native (Platform) Authentication Service in USS . . . . . . . . . . . . . . . . 32

6.2.6 z/OS LDAP Directory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.2.6.1 To Set Up Schema When Using RDBM Backend . . . . . . . . . . . . . . . . . . . . . . . 346.2.6.2 To Set Up Schema When Using TDBM Backend . . . . . . . . . . . . . . . . . . . . . . . 346.2.6.3 To Set Up the Directory Tree (for either RDBM or TDBM) . . . . . . . . . . . . . . . . . . 356.2.6.4 Performance Considerations (when using RDBM) . . . . . . . . . . . . . . . . . . . . . . . 35

6.2.7 Hints and Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.0 Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407.1 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Reader's Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figures

1. Basic Material: Program Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32. Program File Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43. Basic Material: Unlicensed Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44. Basic Material: Licensed Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65. Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66. Component IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87. Driving System Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118. Target System Mandatory Installation Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119. Target System Conditional Installation Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

10. Target System Mandatory Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211. Target System Conditional Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312. Total DASD Space Required by Host On-Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413. Storage Requirements for SMP/E Work Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

iv Host On-Demand Program Directory

14. Storage Requirements for SMP/E Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615. Storage Requirements for Host On-Demand Target Libraries . . . . . . . . . . . . . . . . . . . . . 1716. Host On-Demand File System Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1717. Storage Requirements for Host On-Demand Distribution Libraries . . . . . . . . . . . . . . . . . . 1718. Alternative Conditional Operational Requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1819. SMP/E Options Subentry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2120. Sample Installation Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figures v

vi Host On-Demand Program Directory

1.0 Introduction

This program directory is intended for system programmers who are responsible for program installationand maintenance. It contains information about the material and procedures associated with theinstallation of . This publication refers to as Host On-Demand.

The Program Directory contains the following sections:

� 2.0, “Program Materials” on page 3 identifies the basic and optional program materials anddocumentation for Host On-Demand.

� 3.0, “Program Support” on page 8 describes the IBM support available for Host On-Demand.

� 4.0, “Program and Service Level Information” on page 9 lists the APARs (program level) and PTFs(service level) that have been incorporated into Host On-Demand.

� 5.0, “Installation Requirements and Considerations” on page 10 identifies the resources andconsiderations that are required for installing and using Host On-Demand.

� 6.0, “Installation Instructions” on page 21 provides detailed installation instructions for HostOn-Demand. It also describes the procedures for activating the functions of Host On-Demand, orrefers to appropriate publications.

Before installing Host On-Demand, read the Program Directory and then keep it for future reference.Section 3.2, “Preventive Service Planning” on page 8 tells you how to find any updates to the informationand procedures in this Program Directory.

1.1 Host On-Demand Description

IBM Rational Host On-Demand is for customers who wish to provide easy, cost-effective host access withsecurity to users in intranet and extranet-based environments. It enables businesses to extend the reachof their host applications and data to new users, including business partners, suppliers, and salespersonnel.

Host On-Demand gives users secure browser access to host applications and data, with Webbrowser-based emulation. With support for TN3270E, TN5250, VT52/100/220, and CICS applicationsincluded in a single package, users need to learn only one interface to reach key host data. BecauseHost On-Demand is Java based, users in different operating environments get the same look and feel, andidentical feature set.

Host On-Demand is installed on the host and the Host On-Demand applet is downloaded via a Web URLto the users' Web browser. The Host On-Demand cached client will reduce download and user idle time,enhance productivity, and help save significant expense in product deployment and maintenance.

A rich Java toolkit, including Host Access Beans for Java and the API, can enable customers to rapidlycreate custom e-business applications to achieve a competitive advantage. Because Host On-Demand is

Copyright IBM Corp. 1997, 2009 1

part of the Rational family, applications developed using the toolkit can be incorporated into other Websoftware projects, helping preserve your Host On-Demand investment and helping provide a quick start tothe Web and e-business.

Host On-Demand is recommended for installations that require low-cost centralized deployment,administration, and support for a broad range of client and server platforms.

1.2 Host On-Demand FMIDs

Host On-Demand consists of the following FMIDs:

HHOJB00

2 Host On-Demand Program Directory

2.0 Program Materials

An IBM program is identified by a program number. The program number for Host On-Demand is5733-A59.

Basic Machine-Readable Materials are materials that are supplied under the base license and featurenumbers, and are required for the use of the product. Optional Machine-Readable Materials are orderableunder separate feature numbers, and are not required for the product to function.

The program announcement material describes the features supported by Host On-Demand. Ask yourIBM representative for this information if you have not already received a copy.

2.1 Basic Machine-Readable Material

The distribution medium for this program is magnetic tape or downloadable files. This program is inSMP/E RELFILE format and is installed by using SMP/E. See 6.0, “Installation Instructions” on page 21for more information about how to install the program.

Figure 2 describes the program file content for Host On-Demand.

Notes:

1. The data set attributes in this table must be used in the JCL of jobs that read the data sets. However,because the data sets are in IEBCOPY unloaded format, their actual attributes might be different.

2. If any RELFILEs are identified as PDSEs, ensure that SMPTLIB data sets are allocated as PDSEs.

Figure 1. Basic Material: Program Tape

MediumPhysicalVolume External Label VOLSER

3490Cart.

1 IBM RationalHost On-DemandV11

HOJB00

3590Cart.

1 IBM RationalHost On-DemandV11

HOJB00


2.2 Optional Machine-Readable Material

No optional machine-readable materials are provided for Host On-Demand.

2.2.1 Basic Program Publications

Figure 3 identifies the basic unlicensed program publications for Host On-Demand. The publications arein softcopy form and can be accesssed by following the information that is presented in the tables and textthat follows:

The publications are available from the Host On-Demand product Information Center:

Figure 2. Program File Content

Name

ORG

RECFM

LRECL

BLKSIZE

SMPMCS SEQ FB 80 6400

IBM.HHOJB00.F1 PDS FB 80 8800

IBM.HHOJB00.F2 PDS U 0 6144

IBM.HHOJB00.F3 PDS VB 27920 27924

Figure 3. Basic Material: Unlicensed Publications

Publication TitleForm

Number

Planning, Installing, and Configuring N/A

Readme N/A

Host Printing Reference N/A

Session Manager API N/A

HOD Macro Programming Guide N/A

Web Express Logon Reference N/A

Trouble Shooting Guide N/A

Programmable HOD Reference N/A

Toolkit Getting Started N/A

J2EE Connector N/A

Host Access Class Library N/A

Host Access Beans for Java N/A


http://publib.boulder.ibm.com/infocenter/hodhelp (continued): v11r0/index.jsp

this site also includes all the product documentation, a search function, tutorials, white papers, and a linkto Hints and Tips.

The main Host On-Demand publication is Planning, Installing, and Configuring which details installation(for non z/OS operating systems), configuration (all operating systems), and administration (all operatingsystems).

The publications are also included in soft copy form (HTML and PDF) with the product and are viewablefrom your browser once the product has been successfully installed using the URL format listed below:

� Host On-Demand Online Documentation:

– http://<server name>/<webserver alias>/<language>/doc/

where <server name> refers to your z/OS server's TCP/IP host name, <webserver alias> refers to yourweb server's Pass Rule alias (look in your /etc/httpd.conf file in the Pass Rule section - default is hod),and <language> refers to your installed language prefix (ie., en for English, de for German, etc.). Anexample of a URL to point to the English language Host On-Demand Planning, Installing, and Configuringis:

http://mvs048/hod/en/doc/install/install.html

Note: Host On-Demand requires the addition of PASS RULES added to your configuration file for yourHTTP web server. Without these PASS RULES added to your web server, you will not be able to viewthe online documentation as well as execute functions within Host On-Demand. Typically, theconfiguration file is named httpd.conf and is typically found in your /etc directory in UNIX SystemServices.

Listed below are the complete set of Pass Rules that you should have to successfully execute HostOn-Demand. Please verify that the following Pass statements exist in your httpd.conf.

Please make sure that the statements are listed in the order below. The default installation path is/usr/lpp/HOD and would need to be modified to your installation path. Also, if a Pass Rule below has a'(continued on next line)' statement, please be aware that the full Pass rule should be BOTH that line andthe next line combined as ONE LINE in the httpd.conf file.

# �� ADD NEW PASS RULES HERE ��

Pass /hod/�.css /usr/lpp/HOD/hostondemand/HOD/�.css.asciiPass /hod/�.jnlp /usr/lpp/HOD/hostondemand/HOD/�.jnlp.asciiPass /hod/�.html /usr/lpp/HOD/hostondemand/HOD/�.html.asciiPass /hod/�.HTML /usr/lpp/HOD/hostondemand/HOD/�.HTML.asciiPass /hod/�.js /usr/lpp/HOD/hostondemand/HOD/�.js.asciiPass /hod/�.properties (continued on next line) /usr/lpp/HOD/hostondemand/HOD/�.properties.asciiPass /hod/�.props /usr/lpp/HOD/hostondemand/HOD/�.props.asciiPass /hod/� /usr/lpp/HOD/hostondemand/HOD/�

Program Materials 5

It is extremely important that the Pass statement "Pass /hod/* /usr/.." is the last Pass rule encountered.If this is not the last statement, problems will occur when you try to access Host On-Demand htmls andonline publications.

The following resource mapping directives should also be included among the other rules in the AddTypesection of the Web Server configuration file.

AddType .jnlp application/x-java-jnlp-file 8bit 1./AddType .cab application/octet-stream binary 1./AddType .jar multipart/x-zip binary 1./

Note: Not all Host On-Demand publications are translated into all languages. An english version will beprovided if a translated version does not exist.

Figure 4 identifies the basic licensed program publications for Host On-Demand. The first copy isavailable at no charge to the licensees of the basic material by ordering the 7xxx feature number. Orderadditional copies by using the 8xxx feature number. A fee is charged for additional copies.

2.2.2 Optional Program Publications

No optional publications are provided for Host On-Demand.

2.3 Program Source Materials

No program source materials or viewable program listings are provided for Host On-Demand.

2.4 Publications Useful During Installation

You might want to use the publications listed in Figure 5 during the installation of Host On-Demand. Toorder copies, contact your IBM representative or visit the IBM Publications Center athttp://www.ibm.com/shop/publications/order.

Figure 4. Basic Material: Licensed Publications


NumberFeatureNumber

No licensed publications

Figure 5 (Page 1 of 2). Publications Useful During Installation


Number

IBM SMP/E for z/OS User's Guide SA22-7773

IBM SMP/E for z/OS Commands SA22-7771


Figure 5 (Page 2 of 2). Publications Useful During Installation


Number

IBM SMP/E for z/OS Reference SA22-7772

IBM SMP/E for z/OS Messages, Codes, and Diagnosis GA22-7770

MVS z/OS Command Reference SA22-7627

MVS z/OS System Codes SA22-7626

MVS z/OS Messages Library, System Messages Vol 1 SA22-7631










UNIX System Services User's Guide SA22-7801

UNIX System Services Command Reference SA22-7802

UNIX System Services Messages and Codes SA22-7807

Program Materials 7

3.0 Program Support

This section describes the IBM support available for Host On-Demand.

3.1 Program Services

Contact your IBM representative for specific information about available program services.

3.2 Preventive Service Planning

Before installing Host On-Demand, you should also review the current support, product information, andHints and Tips on the following Web sites:

� Support site: http://www.ibm.com/software/webservers/hostondemand/support/

� Product information site: http://www.ibm.com/software/webservers/hostondemand/

� Program Directory softcopy: http://publib.boulder.ibm.com/infocenter/hodhelp/ (continued): v11r0/index.jsp

� Hints and Tips site: http://www.ibm.com/software/webservers/hostondemand/support/

If Host On-Demand is more than two weeks old when you install it, you should contact the IBM SupportCenter or check the above websites to get the most current support information.

3.3 Statement of Support Procedures

Report any problems which you feel might be an error in the product materials

Figure 6 identifies the component IDs (COMPID) for Host On-Demand.

Figure 6. Component IDs

FMID COMPID Component NameRETAINRelease

HHOJB00 5733A5900 Host On-Demand V11 B00

8 Copyright IBM Corp. 1997, 2009

4.0 Program and Service Level Information

This section identifies the program and relevant service levels of Host On-Demand. The program levelrefers to the APAR fixes that have been incorpo into the program. The service level refers to the PTFsthat have been incorpora into the program.

4.1 Program Level Information

No APARs have been incorporated into Host On-Demand.

4.2 Service Level Information

No PTFs against this release of Host On-Demand have been incorporated into the product tape.


5.0 Installation Requirements and Considerations

The following sections identify the system requirements for installing and activating Host On-Demand. Thefollowing terminology is used:

� Driving system: the system used to install the program; where SMP/E executes.

The program might have specific operating system or product level requirements for using processes,such as binder or assembly utilities during the installation.

� Target system: the system on which the program is configured and run.

The program might have specific product level requirements, such as needing access to the library ofanother product for link-edits. These requirements, either mandatory or optional, might directly affectthe element during the installation or in its basic or enhanced operation.

In many cases, you can use a system as both a driving system and a target system. However, you canmake a separate IPL-able clone of the running system to use as a target system. The clone must includecopies of all system libraries that SMP/E udpates, copies of the SMP/E CSI data sets that describe thesystem libraries, and your PARMLIB and PROCLIB.

Use separate driving and target systems in the following situations:

� When you install a new level of a product that is already installed, the new level of the product willreplace the old one. By installing the new level onto a separate target system, you can test the newlevel and keep the old one in production at the same time.

� When you install a product that shares libraries or load modules with other products, the installationcan disrupt the other products. By installing the product onto a separate target system, you canaccess these impacts without disrupting your production system.

5.1 Driving System Requirements

This section describes the environment of the driving system that is required to install Host On-Demand.

5.1.1 Machine Requirements

The driving system can run in any hardware environment that supports the required software.

5.1.2 Programming Requirements


Note: Installation may require migration to new z/OS releases to be service supported. Seehttp://www-03.ibm.com/systems/z/os/zos/support/zos_eos_da

5.2 Target System Requirements

This section describes the environment of the target system that is required to install and use HostOn-Demand.

Host On-Demand installs in the z/OS (Z038) SREL.

5.2.1 Machine Requirements

The target system can run in any hardware environment that supports the required software.

5.2.2 Programming Requirements

5.2.2.1 Installation Requisites

Installation requisites identify products that are required by and must be present on the system or productsthat are not required by but should be present on the system for the successful installation of this product.

Mandatory installation requisites identify products that are required on the system for the successfulinstallation of this product. These products are specified as PREs or REQs.

Figure 7. Driving System Software Requirements

ProgramNumber

ProductName

MinimumVRM

MinimumService Levelwill satisfytheseAPARs

Includedin thisproduct'sshipment?

Any one of the following:

5694-A01 z/OS V01.08.00 N/A No

5655-G44 IBM SMP/E forz/OS

V03.04.00 N/A No

Figure 8. Target System Mandatory Installation Requisites

ProgramNumber

ProductName

MinimumVRM

MinimumService Levelwill satisfytheseAPARs


5694-A01 z/OS V01.08.00 or higher N/A No

Installation Requirements and Considerations 11

Note: Installation may require migration to new z/OS releases to be service supported. Seehttp://www-03.ibm.com/systems/z/os/zos/support/zos_eos_da

Conditional installation requisites identify products that are not required for successful installation of thisproduct but can resolve such things as certain warning messages at installation time. These products arespecified as IF REQs.

5.2.2.2 Operational Requisites

Operational requisites are products that are required by and must be present on the system or productsthat are not required by but should be present on the system for this product to operate all or part of itsfunctions.

Mandatory operational requisites identify products that are required for this product to operate its basicfunctions. These products are specified as PREs or REQs.

Note: z/OS Communication Server TCP/IP must be running on your host. Also, needed for the basicfunction of Host On-Demand is a properly configured HTTP server. The IBM HTTP server is provided asa part of your base z/OS operating system (FMID HIMW530). This function can also be found in LotusDomino for z/OS V6.5 and higher (5655-K36).

Conditional operational requisites identify products that are not required for this product to operate itsbasic functions but are required at run time for this product to operate specific functions. These productsare specified as IF REQs.

Figure 9. Target System Conditional Installation Requisites

ProgramNumber

ProductName

MinimumVRM

MinimumSvc Lvlto satisfytheseAPARs

Functionfor whichthis isa Req't


5655-A46 IBM Java V01.05.00 orhigher

N/A N/A No

Figure 10. Target System Mandatory Operational Requisites

ProgramNumber

Product Name andMinimum VRM/Service Level

** see Notebelow


Note: The previous table, Conditional Operational Requisites, include only z/OS operational requisities.Please also reference the non-z/OS Conditional Operational Requisites table which details alternate(primarily non-z/OS) requisites you may need for additional function in Host On-Demand in the "SpecialConsiderations" section. Refer to 5.4, “Special Considerations” on page 18 for the table ofalternative requisites.

For Host On-Demand V11, "basic function" consists of:

Figure 11. Target System Conditional Operational Requisites

ProgramNumber

Product Name andMinimum VRM/Service Level Function

For Configuration Servlet Function:

5655-I35 WebSphere Application Server for z/OSV6.0, V6.1, V7.0

Web Application Server

Please also refer to the 5.4, “SpecialConsiderations” on page 18 for non-z/OSproducts that also satisfy the WebApplication Server function if available.

For Web Server Function:

IBM HTTP Server V1.3.28, V2.0.42,V2.0.47, V6.0, V6.1, V7.0

Web Server

Please also refer to the 5.4, “SpecialConsiderations” on page 18 for non-z/OSproducts that also satisfy the Web ServerFunction if available.

For LDAP Function (z/OS requisite only):

5655-G52 IBM LDAP Directory Server V6.0, V6.1, orV6.2

LDAP

5694-A01 IBM LDAP Server running on z/OS V1.9and above

LDAP

Please also refer to the 5.4, “SpecialConsiderations” on page 18 for non-z/OSproducts that also satisfy the LDAPFunction.

Any one of the following for Web Express Logon:

5698-AMZ IBM Tivoli Access Manager for e-businessV5.1, V6.0, or V6.1

Web Express Logon

5625-DB2 IBM DB2 Universal Database V9.1, V9.5 Web Express Logon

Please also refer to the 5.4, “SpecialConsiderations” on page 18 for non-z/OSproducts that also satisfy the Web ExpressLogon function.


� A Host running the Host On-Demand Server� A Workstation client running a terminal emulator session

With this set of basic functions, Java, a HTTP server, and TCP/IP are REQUIRED on the server and abrowser and Java Plug-in are REQUIRED on the workstation (an exception to this is the use of the WebStart Client which does not require a browser). You may also reference the Planning, Installing, andConfiguring Host On-Demand document.

5.2.2.3 Toleration/Coexistence Requisites

Toleration/coexistence requisites identify products that must be present on sharing systems. Thesesystems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASDenvironment (such as test and production), or systems that reuse the same DASD environment at differenttime intervals.

Host On-Demand has no toleration/coexistence requisites.

5.2.2.4 Incompatibility (Negative) Requisites

Negative requisites identify products that must not be installed on the same system as this product.

Host On-Demand has no negative requisites.

5.2.3 DASD Storage Requirements

Host On-Demand libraries can reside on all supported DASD types.

Figure 12 lists the total space that is required for each type of library.

Notes:

1. For non-RECFM U data sets, IBM recommends using system-determined block sizes for efficientDASD utilization. For RECFM U data sets, IBM recommends using a block size of 32760, which ismost efficient from the performance and DASD utilization perspective.

2. Abbreviations used for data set types are shown as follows.

Figure 12. Total DASD Space Required by Host On-Demand

LibraryType

Total Space Requiredin 3390 Trks

Target 1MB

Distribution 960 MB

FileSystem

3700 MB


U Unique data set, allocated by this product and used by only this product. This table providesall the required information to determine the correct storage for this data set. You do not needto refer to other tables or program directories for the data set size.

S Shared data set, allocated by this product and used by this product and other products. Todetermine the correct storage needed for this data set, add the storage size given in this tableto those given in other tables (perhaps in other program directories). If the da already exists, itmust have enough free space to accommodate the storage size given in this table.

E Existing shared data set, used by this product and other products. This data set is notallocated by this product. To determine the correct storage for this data set, add the storagesize given in this table to those given in other tables (perhaps in other program directories). Ifthe data set already exists, it must have enough free space to accommodate the storage sizegiven in this table.

If you currently have a previous release of this product installed in these libraries, the installation ofthis release will delete the old release and reclaim the space that was used by the old release and anyservice t had been installed. You can determine whether these libraries have enough space bydeleting the old release with a dummy function, compressing the libraries, and comparing the spacerequirements with the free space in the libraries.

For more information about the names and sizes of the required data sets, see 6.1.6, “Allocate SMP/ETarget and Distribution Libraries” on page 23.

3. Abbreviations used for the file system path type are as follows.

N New path, created by this product.X Path created by this product, but may already exist from a previous release.P Previously existing path, created by another product.

4. All target and distribution libraries listed have the following attributes:

� The default name of the data set may be changed.� The default block size of the data set may be changed.� The data set may be merged with another data set that has equivalent characteristics.� The data set may be either a PDS or a PDSE.

5. All target libraries listed have the following attributes:

� These data sets can be SMS-managed, but they are not required to be SMS-mana� These data sets are not required to reside on the IPL volume.� The values in the "Member Type" column are not necessarily the actual SMP/E element types that

are identified in the SMPMCS.

6. All target libraries that are listed and contain load modules have the following attributes:

� These data sets can be in the LPA, but they are not required to be in the LP� These data sets can be in the LNKLST.� These data sets are not required to be APF-authorized.


The following figures describe the target and distribution libraries and file system paths required to installHost On-Demand. The storage requirements of Host On-Demand must be added to the storage requiredby other programs having data in the same library or path.

Note: The data in these tables should be used when determining which libraries can be merged intocommon data sets. In addition, since some ALIAS names may not be unique, ensure that no namingconflicts will be introduced before merging libraries.

Figure 13. Storage Requirements for SMP/E Work Data Sets

LibraryDDNAME

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

SMPWRK1 S PDS FB 80 75 216





SYSUT1 U SEQ -- -- 34 0

SYSUT2 U SEQ -- -- 34 0

SYSUT3 U SEQ -- -- 34 0

SYSUT4 U SEQ -- -- 34 0

Figure 14. Storage Requirements for SMP/E Data Sets

LibraryDDNAME

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

SMPLTS E PDS U 0 15 1

SMPMTS E PDS FB 80 15 1

SMPPTS E PDS FB 80 15000 30

SMPSCDS E PDS FB 80 15 35

SMPSTS E PDS FB 80 15 1


5.3 FMIDs Deleted

Installing Host On-Demand might result in the deletion of other FMIDs. To see which FMIDs will bedeleted, examine the ++VER statement in the SMPMCS of the product.

If you do not want to delete these FMIDs at this time, install Host On-Demand into separate SMP/E targetand distribution zones.

Note: These FMIDs are not automatically deleted from the Global Zone. If you want to delete theseFMIDs from the Global Zone, see the SMP/E manuals for instructions.

Figure 15. Storage Requirements for Host On-Demand Target Libraries

LibraryDDNAME

MemberType

TargetVolume

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.of

DIRBlks

SHOMMOD1 LMOD TVOL1 U PDS U 0 7 1

SHOMINST Sample EXEC TVOL1 U PDS FB 80 6 10

Figure 16. Host On-Demand File System Paths

DDNAME

TYPE Path Name

SHOM0001 N /usr/lpp/HOD/IBM

Figure 17. Storage Requirements for Host On-Demand Distribution Libraries

LibraryDDNAME

TYPE

ORG

RECFM

LRECL

No.of

3390Trks

No.

ofDIRBlks

AHOMHFS1 U PDS VB 27920 15000 5

AHOMINST U PDS FB 80 4 10

AHOMMOD1 U PDS U 0 7 1


5.4 Special Considerations

This section includes a table of all the alternative (primarily non-z/OS) Conditional Operation requisites youmight need for the complete operation/function of Host On-Demand

1. The distribution libraries are assumed to be contained in a single file system whose mount point is/usr/lpp/HOD. Host On-Demand can be installed into an existing HFS or zFS. If you wish to createyour own HFS, job HOMHFS can be used to create your own for Host On-Demand. If you wish tocreate a zFS filesystem, reference the job in SYS1.SAMPLIB, BPXISZFS to allocate your own filesystem. The recommended zFS size is LINEAR CYL(1700 75) for the ROOT filesystem. It isrecommended that you create your own file system for Host On-Demand for serviceability. TheHOMISMKD JCL sample is used to create the directory structure for your file system. HOMISMKDalso creates a directory structure under the /usr/lpp/HOD file system, which is assumed to already beallocated and mounted on the target system.

2. After you finish with the SMP/E portion of your installation including running HOMAPPLY andHOMACCPT, you will have to run the shell script hod11mvs.sh to complete the installation. Pleaseread the directions carefully as there is a shell script, setInstPath.sh that you may have to editbefore running the hod11mvs.sh shell script. Refer to 6.2, “Activating Host On-Demand” onpage 27 for more details.

3. The following table lists all the alternative (primarily non-z/OS) Conditional Operational requisites thatyou may alternately use for proper operation and function of Host On-Demand.

Figure 18 (Page 1 of 3). Alternative Conditional Operational Requisites


Any one of the following needed for Browser Function:

Note: Only Java 2 Browsers are supported. The Microsoft JVM or a Java Plugin is required for the properfunction of your Browser. The Plugin must be either Java Plugin 1.5 or above (from IBM, Sun, or HP). Pleasehave this installed for the proper function of your browser.

Microsoft Internet Explorer 6.0, 7.0, 8.0 Browser Function

FireFox 1.5, 2.0, 3.0 Browser Function

Safari 1.0, 2.0, 3.2.2 Browser Function

Any one or more for Client Function:




Windows XP Professional and HomeEdition(32 & 64 bit), Windows Server 2003Enterprise Editions (32 & 64 bit), WindowsVista Business Edition(N,x86 & x64editions), Windows Vista EnterpriseEdition(N, x86 & x64 editions), WindowsVista Ultimate Edition (N, x86 & x64editions), Windows 2008 server (32 & 64bit), Windows 7 (32 & 64 bit), WindowsTerminal Services for Windows 2003

Client

IBM AIX V5.2, V5.3 (32 & 64 bit), V6.1 (32& 64 bit)

Client

Sun Solaris 8, 9, 10 Client

HP-UX 11.0, 11i, 11iv2, 11iv3 Client

Redhat Enterprise Linux 3.0, 4.0, 5.0 Client

Redhat Linux 9.0 Personal and Professional Client

SUSE Linux V8.2, V9.0 Client

SUSE Linux Enterprise Server 9.0, 10.0, &11.0

Client

TurboLinux V9.0 Workstation Client

Citrix Metaframe 1.8 for Windows TerminalServer 4.0 and 1.8 for Windows 2000Server

Client

Citrix Metaframe XP Presentation Server(Versions S, A, E) for Windows FeatureRelease V2, V3

Client

Mac OS X 10.2.1, 10.3, and 10.4 Client

Optional - Any one or more of the following needed for Web Server

iPlanet Web Server Enterprise Edition V6.0,V7.0

Web Server

Microsoft IIS 5, 5,1, 6 Web Server

Apache HTTP Server 1.3, 2.0, 2.2, 2.2.11 Web Server

Lotus Domino R6.5, R7, R8, R8.5 Web Server

Optional - Needed for Web Express Logon

Netegrity SiteMinder V5.5 Web Express

Optional - Needed for Web Application Servers




iPlanet Application Server V6.0, V7.0 Web Application Server

Lotus Domino R6.5, R7, R8, R8.5 Web Application Server

Optional - Miscellaneous Software

IBM WebSphere Portal for MultiplatformsV6.1

Portal Function

Acrobat Reader (or Acrobat) V6, V7, V8 DBCS PDF support

CICS Transaction Gateway V5.1 and above CICS transaction processing

Lotus Expeditor 6.1 or later and EclipseV3.2 or later

Optional - Development Environment

IBM Rational Application Developer V7.0,V7.5

Development Environment


6.0 Installation Instructions

This chapter describes the installation method and the step-by-step procedures to install and to activatethe functions of Host On-Demand.

Please note the following:

� If you want to install Host On-Demand into its own SMP/E environment, consult the SMP/E manualsfor instructions on creating and initializing the SMPCSI and the SMP/E control data sets.

� You can use the sample jobs that are provided to perform part or all of the installation tasks. TheSMP/E jobs assume that all DDDEF entries that are required for SMP/E execution have been definedin appropriate zones.

� You can use the SMP/E dialogs instead of the sample jobs to accomplish the SMP/E installationsteps.

6.1 Installing Host On-Demand

6.1.1 SMP/E Considerations for Installing Host On-Demand

Use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install this release of Host On-Demand.

6.1.2 SMP/E Options Subentry Values

The recommended values for certain SMP/E CSI subentries are shown in Figure 19. Using values lowerthan the recommended values can result in failures in the installation. DSSPACE is a subentry in theGLOBAL options entry. PEMAX is a subentry of the GENERAL entry in the GLOBAL options entry. Seethe SMP/E manuals for instructions on updating the global zone.

6.1.3 SMP/E CALLLIBS Processing

Host On-Demand uses the CALLLIBS function that is provided in SMP/E to resolve external referencesduring installation. When Host On-Demand is installed, ensure that DDDEFs exist for the followinglibraries:

� CEE.SCEELKED

Figure 19. SMP/E Options Subentry Values

Subentry Value Comment

DSSPACE (2500,500,175) Specifies the primary and secondary (in Tracks) and the number ofdirectory blocks to be allocated for each SMPTLIB dataset.

PEMAX SMP/E Default IBM recommends using the SMP/E default for PEMAX.


Note: CALLLIBs use the previous DDDEFs only to resolve the link-edit for Host On-Demand. These datasets are not updated during the installation of Host On-Demand.

6.1.4 Sample Jobs

The following sample installation jobs are provided as part of the product to help you install HostOn-Demand:

You can access the sample installation jobs by performing an SMP/E RECEIVE and then copying the jobsfrom the relfiles to a work data set for editing and submission. See Figure 20 to find the appropriate relfiledata set.

You can also copy the sample installation jobs from the tape or product files by submitting the followingjob. Depending on your distribution medium, Use either the //TAPEIN or the //FILEIN DD statement andcomment out or delete the other statement. Before you submit the job, add a job card and change thelowercase parameters to uppercase values to meet the requirements of your site.

//STEP1 EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=�//TAPEIN DD DSN=IBM.HHOJB//.F1,UNIT=tunit,// VOL=SER=HOJB,LABEL=(x,SL),// DISP=(OLD,KEEP)//FILEIN DD DSN=IBM.HHOJB//.F1,UNIT=SYSALLDA,DISP=SHR,// VOL=SER=filevol//OUT DD DSNAME=jcl-library-name,// DISP=(NEW,CATLG,DELETE),// VOL=SER=dasdvol,UNIT=SYSALLDA,// SPACE=(TRK,(3,2,2))//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))//SYSIN DD � COPY INDD=xxxxIN,OUTDD=OUT SELECT MEMBER=(HOMACCPT,HOMALLOC,HOMAPPLY)

Figure 20. Sample Installation Jobs

Job Name Job Type Description RELFILE

HOMRECVE RECEIVE Sample RECEIVE job IBM.HHOJB00.F1

HOMALLOC ALLOCATE Sample job to allocate target and distributionlibraries

IBM.HHOJB00.F1

HOMHFS HFS Sample job to allocate HFS (OPTIONAL) IBM.HHOJB00.F1

HOMISMKD MKDIR Sample job to invoke the supplied HOMMKDIREXEC to allocate HFS paths

IBM.HHOJB00.F1

HOMDDDEF DDDEF Sample job to define SMP/E DDDEFs IBM.HHOJB00.F1

HOMAPPLY APPLY Sample APPLY job IBM.HHOJB00.F1

HOMACCPT ACCEPT Sample ACCEPT job IBM.HHOJB00.F1


SELECT MEMBER=(HOMDDDEF,HOMHFS,HOMISMKD,HOMMKDIR) SELECT MEMBER=(HOMRECVE,HOMSAMPU,HOMSERVR)/�

See the following information to update the statements in the previous sample:

TAPEIN:tunit is the unit value that matches the product tape.volser is the volume serial that matches the product tape.x is the tape file number that indicates the location of the data set name on the tape.IBM.HHOJB00.F1 is the 2nd file on the tape.

Note: i.e, x=2 or the 2nd file on the tape. FILEIN:

filevol is the volume serial of the DASD device where the downloaded files reside. OUT

jcl-library-name is the name of the output data set where the sample jobs are stored.dasdvol is the volume serial of the DASD device where the output data set resides.

SYSINxxxxIN is either TAPEIN or FILEIN depending on your input DD statement.

6.1.5 Perform SMP/E RECEIVE

If you install Host On-Demand as a Web download package, the SMP/E RECEIVE is performed during theexecution of the README file. In this case, you can skip this section and continue with the next sectionof the program directory.

If you have received Host On-Demand on tape media, edit and submit sample job HOMRECVE to performthe SMP/E RECEIVE for Host On-Demand. Consult the instructions in the sample job for moreinformation.

Expected Return Codes and Messages: Return Code = 0

6.1.6 Allocate SMP/E Target and Distribution Libraries

Edit and submit sample job HOMALLOC to allocate the SMP/E target and distribution libraries for HostOn-Demand. Consult the instructions in the sample job for more information.


6.1.7 Allocate File system Paths

Host On-Demand can be installed into any existing HFS or zFS file system. However, if you wish tocreate your own HFS for Host On-Demand, edit and submit sample job HOMHFS to allocate the HFS.Consult the instructions in the sample job for more information. This is an optional job. If you choose torun this:

Installation Instructions 23


If you wish to create a zFS file system, reference job SYS1.SAMPLIB(BPXISZFS) to allocate your ownzFS filesystem. The recommended zFS size is LINEAR CYL(1700 75) for the ROOT file system.

It is recommended that you create your own file system for Host On-Demand.

Mount the file system data set of the target system on the driving system when you run the sampleHOMISMKD job because the job will create paths in the file system.

Before you run the sample job to create the paths in the file system, ensure that OMVS is active on thedriving system, and that the file system of the target system is mounted to the driving system. If you installHost On-Demand into a HFS or zFS file system, HFS or zFS must be active on the driving system.

If you plan to install Host On-Demand into a new file system, create the mountpoint and mount the newfile system to the driving system. For Host On-Demand, the recommended mountpoint is /usr/lpp/HOD.For hints and tips on creating a mountpoint, please refer to 6.2.7, “Hints and Tips” on page 35 for moredetails.

Edit and submit sample job HOMISMKD to allocate the file system for Host On-Demand. Consult theinstructions in the sample job for more information.

If you create a new file system for this product, consider updating the BPXPRMxx PARMLIB member tomount the new file system at IPL time. This action can be helpful if an IPL occurs before the installation iscompleted


6.1.8 Create DDDEF Entries

Edit and submit sample job HOMDDDEF to create DDDEF entries for the SMP/E target and distributionlibraries for Host On-Demand. Consult the instructions in the sample job for more information.


This job may receive warning message GIM56501W and rc=4. This message is issued when DDDEFentries are added because they did not exist prior to running the job.

This job may also receive warning message GIM27701W and rc=4. This message is issued when DDDEFentries are added because they did not exist prior to running the job.

This job may also receive the following messages:

GIM356/1E �� DATASET SUBENTRY WAS NOT ADDED BECAUSEIT ALREADY EXISTS.

GIM256/1I - THE SPECIFIED ENTRY WAS NOT UPDATEDBECAUSE OF AN ERROR DURING UCLIN PROCESSING.


with a rc=8 if the SCEELKED DDDEF entry already exists. You can either delete the ADD forSCEELKED or change the ADD to a REP and rerun the job.

Note: If you do not have a SYSLIB on your system (i.e., new Host On-Demand environment/SMP/Ezone), you must create one, at a minimum, to include the SMPMTS. You must have both a DDDEF entryfor the SMPMTS and a DDDEF entry for the SYSLIB that includes (CONCAT) the SMPMTS.

As an example:

ADD DDDEF (SMPMTS) DA(HOM.SMPMTS) SHR UNIT(SYSALLDA) .ADD DDDEF (SYSLIB) CONCAT (SMPMTS) .

Consult your SMP/E manuals for further information.

6.1.9 Perform SMP/E APPLY1. Ensure that you have the latest HOLDDATA; then edit and submit sample job HOMAPPLY to perform

an SMP/E APPLY CHECK for Host On-Demand. Consult the instructions in the sample job for moreinformation.

Perform an SMP/E APPLY CHECK for Host On-Demand.

HOLDDATA introduces ERROR HOLDs against FMIDs for HIPER APARs. Before the installation,ensure that you have the latest HOLDDATA, which is available through several different portals,including http://service.software.ibm.com/holdata/390holddata.html. Install the FMIDs regardless of thestatus of unresolved HIPERs. However, don't deploy the software until the unresolved HIPERs areanalyzed to determine applicability.

To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the PRE,ID, REQ, and IFREQ on the APPLY CHECK. This is because the SMP/E root cause analysisidentifies the cause only of errors and not of warnings (SMP/E treats bypassed PRE, ID, REQ, andIFREQ conditions as warnings, instead of errors).

Here are two methods to install FMIDs when ++HOLDs for HIPERs exist for the FMIDs that youinstall:

a. To ensure that all recommended and critical service is installed with the FMIDs, if you are usingSMP/E 3.5 or higher and have received the latest HOLDDATA, add the FIXCAT operand to theAPPLY command as shown below. If you are using a prior release of SMP/E, add theSOURCEID(HIPER,RSU*) operand to the APPLY command.

If using SMP/E V3.5 or higher:APPLY S(fmid,fmid,...)FORFMID(fmid,fmid,...)SOURCEID(RSU�)FIXCAT(IBM.ProductInstall-RequiredService)GROUPEXTEND .If using SMP/E V3.4 or prior:APPLY S(fmid,fmid,...)FORFMID(fmid,fmid,...)SOURCEID(HIPER,RSU�)GROUPEXTEND .


Some HIPER APARs might not have PTFs available yet. You have to analyze the symptom flagsto determine if you want to bypass the specific ERROR HOLDs and continue the installation of theFMIDs.

This method requires more initial research, but can provide resolution for all HIPERs that havefixes available and are not in a PE chain. Unresolved PEs or HIPERs might still exist and requirethe use of BYPASS.

b. To install the FMIDs without regard for the HIPERs, you can add aBYPASS(HOLDCLASS(HIPER)) operand to the APPLY command. In this way, you can installFMIDs even though HIPER ERROR HOLDs against them still exist. Only the HIPER ERRORHOLDs are bypassed. After the FMIDs are installed, run the SMP/E REPORT ERRSYSMODScommand to identify missing HIPER maintenance.

APPLY S(fmid,fmid,...)FORFMID(fmid,fmid,...)SOURCEID(RSU�)GROUPEXTENDBYPASS(HOLDCLASS(HIPER)) . ..any other parameters documented in the program directory

This method is the quicker of the two, but requires subsequent review of the REPORTERRSYSMODS to investigate any HIPERs. If you are running SMP/E V3.5 or higher and havereceived the latest HOLDDATA, you can also choose to run REPORT MISSINGFIX for FixCategory IBM.ProductInstall-RequiredService to investigate missing recommended service.

If you bypass HOLDs during the installation of the FMIDs because PTFs are not yet available, youcan make yourself notified when the PTFs are available by using the APAR Status Tracking (AST)function of ServiceLink or the APAR Tracking function of ResourceLink.

2. After you take actions that are indicated by the APPLY CHECK, remove the CHECK operand and runthe job again to perform the APPLY.

Note: The GROUPEXTEND operand indicates that SMP/E applies all requisite SYSMODs. Therequisite SYSMODS might be applicable to other functions.

Expected Return Codes and Messages from APPLY CHECK: You will receive a return code of 0 ifthis job runs correctly.

Expected Return Codes and Messages from APPLY: You will receive a return code of 0 if this jobruns correctly.

6.1.10 Perform SMP/E ACCEPT

Edit and submit sample job HOMACCPT to perform an SMP/E ACCEPT CHECK for Host On-Demand.Consult the instructions in the sample job for more information.

Perform an SMP/E ACCEPT CHECK for Host On-Demand.

To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the PRE, ID,REQ, and IFREQ on the ACCEPT CHECK. This is because the SMP/E root cause analysis identifies the


cause of only errors but not warnings (SMP/E treats bypassed PRE, ID, REQ, and IFREQ conditions aswarnings rather than errors).

Before you use SMP/E to load new distribution libraries, it is recommended that you set the ACCJCLINindicator in the distribution zone. In this way, you can save the entries that are produced from JCLIN inthe distribution zone whenever a SYSMOD that contains inline JCLIN is accepted. For more informationabout the ACCJCLIN indicator, see the description of inline JCLIN in the SMP/E manuals.

After you take actions that are indicated by the ACCEPT CHECK, remove the CHECK operand and runthe job again to perform the ACCEPT.

Note: The GROUPEXTEND operand indicates that SMP/E accepts all requisite SYSMODs. Therequisite SYSMODS might be applicable to other functions.

Expected Return Codes and Messages from ACCEPT CHECK: Return Code = 0

If PTFs that contain replacement modules are accepted, SMP/E ACCEPT processing will link-edits orbinds the modules into the distribution libraries. During this processing, the Linkage Editor or Binder mightissue messages that indicate unresolved external references, which will result i a return code of 4 duringthe ACCEPT phase. You can ignore these messages, because the distribution libraries are notexecutable and the unresolved external references do not affect the executable system libraries.

Expected Return Codes and Messages from ACCEPT: Return Code = 0

6.1.11 Run REPORT CROSSZONE

The SMP/E REPORT CROSSZONE command identifies requisites for products that are installed inseparate zones. This command also creates APPLY and ACCEPT commands in the SMPPUNCH dataset. You can use the APPLY and ACCEPT commands to install those cross-zone requisites that theSMP/E REPORT CROSSZONE command identifies.

After you install Host On-Demand, it is recommended that you run REPORT CROSSZONE against thenew or updated target and distribution zones. REPORT CROSSZONE requires a global zone withZONEINDEX entries that describe all the target and distribution libraries to be reported on.

For more information about REPORT CROSSZONE, see the SMP/E manuals.

6.2 Activating Host On-Demand

If you mount the file system in which you have installed Host On-Demand in read-only mode duringexecution, then complete the following tasks to activate Host On-Demand:


6.2.1 Completing the Installation of Host On-Demand

All SMP/E portions of your installation have completed, but to complete the install of Host On-Demand,you will need to edit the shell script setInstPath.sh. The shell script, setInstPath.sh, was added as away to export your base SMP/E installation directory path, web published directory path (defaults are/usr/lpp/HOD and /usr/lpp/HOD/hostondemand/HOD), java engine and java class path to frequently usedz/OS shell scripts. This should lessen the editing of shell scripts that were required in past releasesbefore one could execute the shell script.

Once the setInstPath.sh has been edited you will have to execute (run) in USS the hod11mvs.sh shellscript to complete the install.

Both the setInstPath.sh and hod11mvs.sh shell scripts are located in the default /usr/lpp/HOD SMP/Einstallation directory. If you installed to another directory, the shell scripts will be found there.

The hod11mvs.sh shell script must be executed with the Unix Systems Services (USS) umaskenvironment variable set to 022 (root user). The umask variable is used to control the default filepermissions on newly-created files. The umask variable must be set correctly before running the shellscript so that the HOD V11 directories are created with the correct permissions. To set your umaskvariable to 022, enter the following USS command in your USS environment:

% umask /22

Or place the following statement in the /etc/profile:

umask /22

To complete the Host On-Demand installation, follow the steps below in UNIX System Services:

1. Edit the setInstPath.sh shell script found in your base SMP/E Host On-Demand directory to set yourbase Host On-Demand installation directory path, web published directory path, java engine, and javaclass paths. The default is /usr/lpp/HOD and /usr/lpp/HOD/hostondemand/HOD for the base installand web published directory paths.

2. Execute the hod11mvs.sh shell script in UNIX System Services:

� In UNIX System Services, change directory into the directory of your base SMP/E HOD directory ifnot currently at that directory level (i.e., cd /usr/lpp/HOD in most instances).

� Type in at the USS prompt: hod11mvs.sh and <ENTER> to execute the shell script.

Here is a description of what the hod11mvs.sh shell script does:

� Deletes the Host On-Demand directories if installed (default /usr/lpp/HOD):

– /usr/lpp/HOD/hostondemand/lib

– /usr/lpp/HOD/hostondemand/HOD

The following directory will remain if installed (default /usr/lpp/HOD):

– /usr/lpp/HOD/hostondemand/private

This shell script will install the hod11mvs.tar file into the following default directory:


– /usr/lpp/HOD/hostondemand

� This shell script will also create the necessary installation directories for the Native AuthenticationService (HODRAPD). Two directories will be created in the default/usr/lpp/HOD/hostondemand/private directory which will link to the HODRAPD module that wasinstalled and link-edited by SMP/E during the Host On-Demand V11 SMP/E installation.

Note: If you find that after you successfully install Host On-Demand (after the execution of hod11mvs.sh),you are running out of space on your file system, you may take the following steps (your SMP/Eenvironment must be available):

1. Remove the files in the default /usr/lpp/HOD directory. These are actually hardlinks of the files in the/usr/lpp/HOD/IBM directory.

2. Delete the files in the /usr/lpp/HOD/IBM directory, specifically the HOMTARx files.

3. To restore these files to your file system, run the SMP/E APPLY job with the REDO option in theSMP/E control statements. The APPLY will create the hardlinks in the /usr/lpp/HOD directory.

6.2.2 Update Web Server Pass Rules and Resource MappingDirectives

To activate the functions of Host On-Demand, add the Pass Rules listed below to the Pass Rule section ofyour Web Server configuration file. The configuration file name is typically httpd.conf. (For IBMWebSphere Application Server and Domino Go Webserver). The httpd.conf file is typically found in your/etc directory in UNIX System Services.

Listed below are the Pass Rules that you will need to have in your httpd.conf file.

These Pass Rules must be in the order listed and must be placed prior to the Pass /* Pass Rule. Therules assume an alias of /hod/. Also, if a Pass Rule below has a '(continued on next line)' statement,please be aware that the full Pass rule should be BOTH that line and the next line combined as ONELINE in the httpd.conf file. Consult your Web Server documentation for further details.

The Pass Rules are:

# �� ADD NEW PASS RULES HERE ��

Pass /hod/�.css /usr/lpp/HOD/hostondemand/HOD/�.css.asciiPass /hod/�.jnlp /usr/lpp/HOD/hostondemand/HOD/�.jnlp.asciiPass /hod/�.html /usr/lpp/HOD/hostondemand/HOD/�.html.asciiPass /hod/�.HTML /usr/lpp/HOD/hostondemand/HOD/�.HTML.asciiPass /hod/�.js /usr/lpp/HOD/hostondemand/HOD/�.js.asciiPass /hod/�.properties (continued on next line) /usr/lpp/HOD/hostondemand/HOD/�.properties.asciiPass /hod/�.props /usr/lpp/HOD/hostondemand/HOD/�.props.asciiPass /hod/� /usr/lpp/HOD/hostondemand/HOD/�

The following resource mapping directives should also be included among the other rules in the AddTypesection of the Web Server configuration file.


AddType .jnlp application/x-java-jnlp-file 8bit 1./AddType .cab application/octet-stream binary 1./AddType .jar multipart/x-zip binary 1./

6.2.3 Start Host On-Demand

The HOMSERVR sample JCL job is supplied to start Host On-Demand. You can find this job in yourSHOMINST target library. This job starts the ServiceManager.sh shell script, which starts the HostOn-Demand Service Manager. The ServiceManager.sh shell script is found in the/usr/lpp/HOD/hostondemand/private directory (if installing to the default directory) and may need to bemodified for correct execution of Host On-Demand. For example, this shell script is edited to change thedebug level or java optimization parameters. The setInstPath.sh script should have been previouslyedited to set your correct installation path. Please note the comments and edit appropriately.

Note: You may want to rename the HOMSERVR sample job to a started PROC name of less than 8characters (ie., HOMSRV). This will help when displaying subprocesses and stopping HOD. You will beable to cancel HOD and all subprocesses at once if your started PROC name is less than 8 characters. Ifyou decide to rename the job name for the Host On-Demand server from HOMSERVR to something fewerthan eight characters, beware that the job names for the tasks listening on ports 8999 and 3470 will get adigit appended to them. This is important if you decide to make port reservations in your TCPIP.PROFILEusing the explicit job names.

Prior to starting Host On-Demand, copy the HOMSERVR sample job from your install library SHOMINSTto an authorized PROCLIB. If you are installing in a directory other than the default directory(/usr/lpp/HOD) you must change the PARM parameter to point to the location where you haveServiceManager.sh installed.

The HOMSERVR procedure can be started from a RACF USERID with root authority in UNIX SystemServices. It can also be started with a USERID that does not have root authority. Here are the basicinstructions to enable Host On-Demand to be assigned to the appropriate USERID. These are not detailedinstructions. If you need assistance or authorization, contact your RACF System Administrator.

� Create a USERID for the HOMSERVR procedure, (for example you might create a HOMSERVRUSERID)

– Choose a default group that is defined to UNIX System Services (has an UNIX System Servicessegment with a GID (Groupid) defined; for example you might have a group called OMVSGRPwhich contains all UNIX System Services users).

– Determine if you can run the HOMSERVR procedure with a USERID that has a UID of 0 or not,depending on the security restrictions for your environment. Add a UNIX System Servicessegment (an OMVS segment) giving the userid root authority by assigning it a UID of 0 or byassigning a UID not 0. If you choose a UID not 0, then you must do the following:

1. You must have all directories in the path to the ServiceManager.sh script set to at least 755.The script is located in default path /usr/lpp/HOD/hostondemand/private.

2. All files must have mpermissions of at least 644 except executable shell scripts which musthave permissions of 755.


3. All directories and files must be owned by the same RACF USERID that is associated with thestarted task. Use the 'chown -R path' command to set the owner.

� Create a started class entry (or update ICHRIN03) for the HOMSERVR procedure

– Make the entry name procname.* (for example, HOMSERVR.* )

– Assign "=Member" to the user thereby making userid and the procname the same (for exampleHOMSERVR.*).

– Assign the procname to the USSgroup that is the default group for the user (for exampleOMVSGRP).

To start Host On-Demand, start the sample job HOMSERVR.

To stop Host On-Demand, cancel sample job HOMSERVR.

Note: With a procname of 8 characters, you will need to provide the job's address space value to cancelthe main proc. You will also need the address space value to cancel the subprocesses. If your procnameis > 8 characters (ie., HOMSRV), you will only need to issue the 'cancel HOMSRV' command to cancelboth the main process as well as the subprocesses.

6.2.4 Configuring Host On-Demand (Administration)

Refer to the Configuring Host On-Demand section in the Planning, Installing, and Configuring Guide forinformation on the different models supported by Host On-Demand and the steps needed to create thesession definition files for each model.

6.2.5 Starting the Optional Native (Platform) Authentication ServiceNote: The following can be done only after the hod11mvs.sh has been successfully completed. Thehod11mvs.sh shell script sets up hodrapd directories in your (default)/usr/lpp/HOD/hostondemand/private directory for accessing the HODRAPD module that was installedduring the SMP/E CALLLIBS processing in the SHOMMOD1 data set. When the Native (Platform)Authentication Service is started from USS (UNIX System Services), the HODRAPD module is executed.

Provided below are the statements and links that are set-up for the HODRAPD module by thehod11mvs.sh shell script. These statements and links are provided in the event they are somehowremoved at a later time:

################################################################### Create installation directories for Native Authentication## Two directories will be created in the# $HOD_INSTALL_DIR/hostondemand/private directories which will# execute the HODRAPD module that was installed by SMP/E# during the Host On-Demand V11./ SMP/E installation.###################################################################


touch $HOD_INSTALL_DIR/hostondemand/private/HODRAPDln -s $HOD_INSTALL_DIR/hostondemand/private/(cont. on next line) HODRAPD $HOD_INSTALL_DIR/hostondemand/private/hodrapd

chmod 744 $HOD_INSTALL_DIR/hostondemand/private/HODRAPDchmod +t $HOD_INSTALL_DIR/hostondemand/private/HODRAPD

6.2.5.1 Setup for Starting the Native Authentication Service

The installation is designed to install the server load module into your new SHOMMOD1 dataset. Themodule is automatically link-edited during the the JCLIN CALLLIBS processing during the APPLY. Thisdataset must be accessed by the system LNKLST or LPALIB concatenation.

The authentication server is invoked as a USS (UNIX) command. The server must run under theownership of an ID that has an OMVS segment defined that includes superuser authority.

The following example illustrates the RACF command used to create a user profile with superuserauthority:

AU userid DFLTGRP(oegroup) name(AUTHSERV) OMVS(UID(/) HOME('/'))

Additionally, if your site is running in a BPX.DAEMON environment, then RACF NOPADCHK processingmust be enabled for the dataset containing the HOMRAPD load module. The following example gives theappropriate RACF commands:

RALTER PROGRAM � ADDMEM ('your.rapd.dataset'/volser/NOPADCHK)SETROPTS WHEN(PROGRAM) REFRESH

6.2.5.2 Starting the Native (Platform) Authentication Service in USS

To start the Native Authentication Service (HODRAPD) using USS (Unix System Services), go to the yourdefault SMP/E installation directory (i.e., /usr/lpp/HOD) and at the command prompt, enter:

hodrapd.sh

Options such as logging, time-out values, and maximum number of requests the server will allow can bespecified when you start the Native Authentication Service. To change the options, edit (oedit)hodrapd.sh in the /usr/lpp/HOD default directory. You must keep the (-x) option, but you can append thefollowing options to the (-x) where the options are:

l (ie., -xl) Enable logging.t (ie., -xt) Set socket timeout value, in seconds. The default is 20.c (ie., -xc) Set the maximum number of requests the server will allow.

For example, to start the native authentication service and set the socket timeout to 100 seconds, edit theline where the hodrapd module is called (line 82) and change the call (i.e., hodrapd -x) to:

hodrapd -xt1//


To start the platform authentication service with a maximum number of requests, edit the line where thehodraps module is called (i.e., hodrapd -x) to:

hodrapd -xc1//

You will see a message displayed to USS that the Native Authentication Service is starting. When theService has completely started, you will see a message display to your z/OS console as follows:

BPXF/24I (USER2) /8/11//4 /9:32:27 hodrapd: PAS///1 Starting IBMPlatform Authentication Service.

You can also check the status of the Native Authentication Service by issuing the following from your USSprompt:

netstat -a

This command will display the status of the Service. The Native Authentication Service uses thewell_known_port=2569. The netstat -a command will display the following based on your USERID for theNative Authentication Service:

MVS TCP/IP onetstat CS V2R8 TCPIP Name: TCPIP /9:37:37User Id Conn Local Socket Foreign Socket State------- ---- ------------ -------------- -----USER25 /////2E5 /./././..2569 /./././../ Listen

where USER2 is the USERID where the Native Authentication has been started from and USER25 is theNative Authenticated process that has started.

The hodrapd.sh shell script appends to your LIBPATH and NLSPATH. You may want to take thestatements found in the shell script and add them to your /etc/profile on USS. You will need to re-executeyour /etc/profile to activate the changes. You do this by entering . profile from your /etc directory. TheLIBPATH and NLSPATH statements are provided below (using default paths):

export NLSPATH=$NLSPATH:/usr/lpp/HOD/hostondemand/lib/msgs/%Nexport LIBPATH=$LIBPATH:/usr/lpp/HOD/hostondemand/lib/

6.2.6 z/OS LDAP Directory Configuration

If you have an existing z/OS LDAP Server and are running on z/OS V1.9 and above, verify the followingbefore configuring it for Host On-Demand:

� Verify that the LDAP Server is configured as described in the z/OS V1R8 LDAP Server Admin andUsage Guide (SC24-5923).

� Verify that a suffix has been added and associated with an object class.

You can use this suffix as the parent distinguised name (DN) for Host On-Demand or you can use alower-level object.

To configure an existing LDAP directory for Host On-Demand, familiarize yourself with the LDAP directoryand the default schema shipped with it. You will need to use the IBM schema shipped with the LDAP


Server in order to use Host On-Demand with LDAP. The process for setting up this IBM Schema isdifferent depending on the DB2 backend you are using, RDBM or TDBM.

Note: When using an LDAP server on z/OS with HOD, the userIDs and passwords cannot be controlledby RACF. The userIDs and passwords must be stored in the LDAP server. HOD cannot interface withRACF.

6.2.6.1 To Set Up Schema When Using RDBM Backend

To add the IBM schema to the existing LDAP Directory:

1. Edit the LDAP directory configuration file slapd.conf that the LDAP Server is using.2. Change the includes from the original files to the IBM files as listed below. Refer to "Using IBM

Schema Configuration Files" in the Security Server LDAP Server Administration and Usage Guide formore information.

Original IBM__________________________________slapd.at.system schema.system.atslapd.cb.at.conf schema.IBM.atslapd.at.conf schema.user.atslapd.oc.system schema.system.ocslapd.cb.oc.conf schema.IBM.ocslapd.oc.conf schema.user.oc

3. Save your changes to slapd.conf.4. Restart the LDAP Server.

Note: The original schema files shipped with LDAP Server create about 100 DB2 tables. The originalschema definitions create about 600 tables. Before attempting to use these schema files, be sure thatDB2 is configured to allow over 600 DB2 tables to be created and used. LDAP32K is the tablespace formost of the over 600 created tables. The SPUFI command for creating this tablespace should look similarto:

create large tablespace eeeeeee in ddddddddnumparts 1 bufferpool BP32Kusing stogroup sysdeflt priqty 72/ secqty 72/;

where sysdeflt is the installation-dependent, systems default stogroup that you obtain from your local DB2administrator.

6.2.6.2 To Set Up Schema When Using TDBM Backend

To add the IBM schema to the existing LDAP Directory:

1. Use ldapmodify command to add the schema.user.ldif that is shipped with the LDAP Server.2. Use ldapmodify command to add the schema.IBM.ldif that is shipped with the LDAP Server.

Note: See chapter 17 of the z/OS V1R8.0 Security Server LDAP Server Administration and Usepublication (SC24-5923-02) for detailed information on using ldapmodify to update schema in TDBM.


6.2.6.3 To Set Up the Directory Tree (for either RDBM or TDBM)

Decide how Host On-Demand will fit into your network and organizational structure, and design the LDAPdirectory information tree. For example,

� To build a directory information tree for an entire organization, use the organization object class for thesuffix:

dn: o=MyOrganizationobjectclass: organizationo: MyOrganization

� To build a directory information tree for one division of an organization, use the organizationalUnitobject class for the suffix:

dn: ou=MyDivision, o=MyOrganizationobjectclass: organizationalUnitou: MyDivision

The directory information tree should be defined in an LDAP Data Interchange Format (LDIF) file andadded in the LDAP directory using the ldapadd command. Details on using the ldapadd command canbe found in the LDAP Server Admin documentation.

6.2.6.4 Performance Considerations (when using RDBM)

The following configuration changes are offered as possible performance enhancements:

� Add the following lines to slapd.conf:

ndex pr nc palPtr eqndex dc eqndex o eqndex name eqndex objectClass eqndex u d eq

� Sizelimit is the number of entries LDAP will return on a search request; change the sizelimit to 5000(this applies when using either RDBM or TDBM).

6.2.7 Hints and Tips1. Creating and initializing your own CSI - Sample job HOMSAMPU has been provided in your

SHOMINST target library for creating and initializing your own SMP/E environment. Follow thedirections given in HOMSAMPU to create your own Host On-Demand CSI. This is optional as HostOn-Demand can be installed into an existing CSI.

2. Creating mount points -

Note: The TSO MKDIR commands must be invoked using a RACF userid with root authority in theUNIX System Services. Path as well as mount point specification in UNIX System Services is casesensitive.


Follow these steps to create the mount point and directories for an HFS file system. To create themountpoint for a zFS file system, reference job SYS1.SAMPLIB(BPXISZFS) which will create your zFSfile system as well as create the mountpoints.

a. From TSO issue the following TSO MKDIR command to create the /usr/lpp/HOD mount point.

TSO MKDIR '-PATHPREFIX-/usr/lpp/HOD' MODE (7,5,5)

Note: Change the occurrences of the string -pathprefix- to the appropriate high level directoryname. For users installing in the root, this would be null. For others, the high level directory maybe something like /service/ or a more meaningful name. Please note the replacement string iscase sensitive.

b. Issue the following MOUNT command to mount the file system on the /usr/lpp/HOD mount point.

Note: The mount command should be on one line.

Note: Change the fsprfx qualifier to the name of the qualifer used to create your HFS filesystem.

TSO MOUNT FILESYSTEM('fsprfx.HOM.HFS')MOUNTPOINT('-PATHPREFIX-/usr/lpp/HOD') TYPE(HFS)

Note: Change the occurrences of the string -pathprefix- to the appropriate high level directoryname. For users installing in the root, this would be null. For others, the high level directory maybe something like /service/ or a more meaningful name. Please note the replacement string iscase sensitive.

3. Running out of space on HFS - If your Host On-Demand HFS or zFS is running out of space onyour z/OS platform, you may take the following steps after the install shell script and any PTF shellscripts have been successfully run. Your SMP/E environment must be available.

a. Remove the files in the default /usr/lpp/HOD directory. These are actually hardlinks of the files inthe /usr/lpp/HOD/IBM directory.

b. Delete the files in the /usr/lpp/HOD/IBM directory, specifically the HOMTARx files.

c. To restore these files to your HFS or zFS, run the SMP/E APPLY job with the REDO option in theSMP/E control statements. The APPLY will create the hardlinks in the /usr/lpp/HOD directory.

4. For the best performance of Host On-Demand, we recommend that you install the latest version ofJava for z/OS. For information on how to download Java, go to this web site:http://www.ibm.com/developerworks/java/

5. If you are installing Host On-Demand in a directory other than the default directory (/usr/lpp/HOD), youmust first change the path in your setInstPath.sh shell script. This shell script will export the baseSMP/E install path and web published path to the following shell scripts:

� hod11mvs.sh -default path is: /usr/lpp/HOD/hod11mvs.sh� ServiceManager.sh -default path is: /usr/lpp/HOD/hostondemand/private/ServiceManager.sh� hodrapd.sh -default path is: /usr/lpp/HOD/hodrapd.sh� InfBnd-S390 -default path is: /usr/lpp/HOD/hostondemand/lib/samples/InfBndCommandFiles

(cont on same line) /InfBnd-S390� DirUtil-S390 -default path is: /usr/lpp/HOD/hostondemand/lib/samples/DirUtilCommandFiles


(cont on same line) /DirUtil-S390� DWunzip-S390 -default path is: /usr/lpp/HOD/hostondemand/lib/samples/DWunzipCommandfiles

(cont on same line) /DWunzip-S390� stophodsrv.sh -default path is: /usr/lpp/HOD/hostondemand/lib/samples/zSeriesCommandFiles

(cont on same line) /stophodsrv.sh� PdtCompilerApplication-S390 -default path is:

/usr/lpp/HOD/hostondemand/HOD/samples/PdtCompilerCommandFiles(cont on same line) /PdtCompilerApplication-S390

Refer to the shell script comments for instructions.

6. When you run Host On-Demand Service Manager (HODSRV) as a started task on zSeries platforms,you no longer need to use the cancel command to stop it (which often resulted in a CEE3DMP SVCcall). Included with Host On-Demand V11 is a shell script for stopping the Service Manager and all ofits child processes: stophodsrv.sh. The file is located by default (assuming you installed under/usr/lpp/HOD) under pathname /usr/lpp/HOD/hostondemand/lib/samples/zSeriesCommandFiles. Youcan of course, move stophodsrv.sh to your /private directory.

Start the script from USS or run it as an MVS procedure as shown in the examples below (which alsoappear in the comments of the script file itself):

� Executing in USS: Start the script by typing stophodsrv.sh on your USS command line and<ENTER>.

� As an MVS procedure:

//STOPHOD PROC HODINST='/usr/lpp/HOD/',// SCRPTDIR='hostondemand/lib/samples/zSeriesCommandFiles'//��//STOPHOD EXEC PGM=BPXBATCH,REGION=/K,TIME=NOLIMIT,// PARM='sh &HODINST/&SCRPTDIR/stophodsrv.sh'//SYSPRINT DD SYSOUT=T//SYSIN DD DUMMY//SYSERR DD SYSOUT=T//STDOUT DD SYSOUT=T//STDERR DD SYSOUT=T//SYSOUT DD SYSOUT=T//��STDENV DD PATH='/etc/leopt'

Note: When you perform the MVS procedure, Host On-Demand Service Manager may end witha 0143 condition code. This is not an error. The condition code merely notifies you that the currentprocess is ending.

7. When running shell scripts in the OMVS shell from a 3270 terminal session the USS(OMVS) shell hasa status indicator in the lower right part of the screen that states Running when the terminal sessionis active. If no data is being typed into the screen, after about 15 seconds the session goes into sleepmode and the status indicator changes to Input. The install shell scripts for Host On-Demandnormally take more than 15 seconds to run, so the indicator changes from Running to Input. Theshell script is not waiting for input; instead, it is running in the foreground. The terminal has gone intosleep mode.


Press F10 to Refresh the screen or F8 to page forward, both of which wake the session. The indicatorchanges back to Running for another 15 seconds. Do not stop the shell script. The command promptappears when the shell script has run to completion, and when the terminal session has beenawakened by pressing F10 or F8. It is not recommended to press Enter to wake the session.

The Java command for the keyrng utility produces the same behavior of the USS terminal session.

This behavior of USS(OMVS) is only for 3270 terminal sessions, not telnet sessions to UNIX SystemServices.

8. The program tape has all the documentation including the Planning, Installing, and Configuringguide which can be viewed via your browser once the product has been installed or from the HostOn-Demand Web site. Please see Section 2.3 on how to access the publications via your browser.

9. Make sure that the LIBPATH and PATH statements are all set correctly in your USS profile. For theLIBPATH and PATH statements, you will need updates for your installed Java libraries as detailedbelow. These statements should point to your installed level of Java. You should also make sure thatthe LIBPATH, PATH, and CLASSPATH statements also include the proper WebSphere ApplicationServer product statements (ie., usually /usr/lpp/internet/bin). The USS profile is usually is found inyour /etc directory in USS.

� The LIBPATH environment variable should point to the correct Java libs. The LIBPATH statementwould include the proper path to your java /lib path. An example follows:

LIBPATH=/usr/lpp/java/IBM/J1.5/lib

� The PATH environment variable should point to the correct Java binaries. The PATH statementshould include the proper path to your java /bin. An example follows:

PATH=/usr/lpp/java/IBM/J1.5/bin

10. Be aware that whatever method you may use to edit files in UNIX System Services (ie., configurationfiles), you may see problems such as carriage returns or blanks being inserted. To alleviate thisproblem use a flat-text editor or simply use FTP to ftp your file to a Windows based text editor andthen ftp back the modified file to your USS Host.

11. The private dirctory can be a separate HFS or zFS with a mountpoint of/usr/lpp/HOD/hostondemand/private. This file system must be mounted read/write and the main HostOn-Demand file system can be mounted in read only.

12. If you are running multiple stacks and you want the Host On-Demand server to run on one stack only,you need to create stack affinity by adding the respective environment variable to theServiceManager.sh shell script:

export _BPXK_SETIBMOPT_TRANSPORT=XXXXXXXX

where XXXXXXXX is the name of the TCP/IP stack with which you want to establish affinity.

13. If you experience java Service Manager 'out-of-memory' errors, causing various tasks to fail such as:

� Saving session information

� Loading a large number of users

� Attempting to save large blocks of trace data


The following two parameters can be used on the start-up command in the Host On-Demand ServiceManager shell start-up script (/usr/lpp/HOD/hostondemand/private/ServiceManager.sh)

a. -mx32m (or larger if needed, ie., -mx64m)

� The mx32m parameter increases the maximum Java heap size. The heap size is increasedfrom the default value of 3 to 32MB.

b. -oss256k

� The oss256k parameter increses the maximum Java stack size (per thread). The value ischanged from the default of 128 KB to 256 KB.

These parameters have been added as a start-up option line in your ServiceManager.sh script. Theline is commented out by default. If you need to run Host On-Demand with increased Java heap andstack parameters, uncomment the line in the ServiceManager.sh shell script that begins as follows(making sure to comment out your previous executable statement):

java -mx32m -oss256k -classpath .:sm.zip:.....


7.0 Notices

References in this document to IBM products, programs, or services do not imply that IBM intends tomake these available in all countries in which IBM operates. Any reference to an IBM product, program,or service is not intended to state or imply that only IBM's product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe on any of IBM's intellectualproperty rights may be used instead of the IBM product, program, or service. Evaluation and verificationof operation in conjunction with other products, except those expressly designated by IBM, is the user'sresponsibility.

APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoingproblem reporting may result in additional APARs being created. Therefore, the APAR lists in thisdocument may not be complete. To obtain current service recommendations and to identify currentproduct service requirements, always contact the IBM Customer Support Center.

IBM may have patents or pending patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to the

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, New York 10504-1785USA

For online versions of this book, we authorize you to:

� Copy, modify, and print the documentation contained on the media, for use within your enterprise,provided you reproduce the copyright notice, all warning statements, and other required statements oneach copy or partial copy.

� Transfer the original unaltered copy of the documentation when you transfer the related IBM product(which may be either machines you own, or programs, if the program's license terms permit atransfer). You must, at the same time, destroy all other copies of the documentation.

You are responsible for payment of any taxes, including personal property taxes, resulting from thisauthorization.

THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not applyto you.

Your failure to comply with the terms above terminates this authorization. Upon termination, you mustdestroy your machine readable documentation.


7.1 Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web atCopyright and trademark information˜ at www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks of other companies as follows:

Acrobat Adobe, Inc.Apple Mac Apple, Inc.Citrix Citrix SystemsHP-UX Hewlet PackardiPlanet Sun Microsystems, Inc.Mac Apple Computer, Inc.Microsoft Microsoft CorporationWindows Microsoft CorporationWindows XP Microsoft CorporationWindows Server 2003 Microsoft CorporationWindows Vista Microsoft CorporationWindows Terminal Services Microsoft CorporationNetegrity Netegrity, Inc.Java Hewlett Packard, Inc.Java Sun Microsystems, Inc.Redhat Linux Redhat, Inc.Safari Apple Computer, Inc.Sun Solaris Sun Microsystems, Inc.SUSE Linux Novell, Inc.Turbo Linux Turbolinux, Inc.UNIX X/Open Company Limited

Notices 41

Reader's Comments

Program Directory for , November 2009

You may use this form to comment about this document, its organization, or subject matter with the understanding thatIBM may use or distribute whatever information you supply in any way it believes appropriate without incurring anyobligation to you.

For each of the topics below please indicate your satisfaction level by circling your choice from the rating scale. If astatement does not apply, please circle N.

RATING SCALE

very very notsatisfied <=====================> dissatisfied applicable

1 2 3 4 5 N

Satisfaction

Ease of product installation 1 2 3 4 5 N

Contents of Program Directory 1 2 3 4 5 N

Installation Verification Programs 1 2 3 4 5 N

Time to install the product 1 2 3 4 5 N

Readability and organization of Program Directory tasks 1 2 3 4 5 N

Necessity of all installation tasks 1 2 3 4 5 N

Accuracy of the definition of the installation tasks 1 2 3 4 5 N

Technical level of the installation tasks 1 2 3 4 5 N

Ease of getting the system into production afterinstallation

1 2 3 4 5 N

How did you order this product?

CustomPac ServerPac Independent Other

Is this the first time your organization has installed this product?

Yes No

Were the people who did the installation experienced with the installation of z/OS products?

Yes No


If yes, how many years? __

If you have any comments to make about your ratings above, or any other aspect of the product installation, pleaselist them below:

Please provide the following contact information:

Name and Job Title

Organization Address Telephone

Thank you for your participation.

Please send the completed form to (or give to your IBM representative who will forward it to the Development group):

IBM CorporationHost Integration Build and InstallationDept. DGYA/Bldg 501P.O. Box 12195Research Triangle Park, NC27709USA

Reader's Comments 43

˚ ˚


IBM

Printed in USA

GI11-914/-//

ibm program directory for ibm rational host on-demand version 11 v11.00.00 program number 5733-a59...

Documents