Program Directory for IBM Rational Host On-Demand Version 11 V Program Number 5733-A59 FMID HHOJB00. for Use with z/os V1.08.

Transcription

1 IBM Program Directory for IBM Rational Host On-Demand Version 11 V Program Number 5733-A59 FMID HHOJB00 for Use with z/os V and higher Document Date: November 2009 GI

2 Note Before using this information and the product it supports, be sure to read the general information under 7.0, Notices on page 40. A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM a nonexclusive 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, All rights reserved. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

3 Contents 1.0 Introduction Host On-Demand Description Host On-Demand FMIDs Program Materials Basic Machine-Readable Material Optional Machine-Readable Material Basic Program Publications Optional Program Publications Program Source Materials Publications Useful During Installation Program Support Program Services Preventive Service Planning Statement of Support Procedures Program and Service Level Information Program Level Information Service Level Information Installation Requirements and Considerations Driving System Requirements Machine Requirements Programming Requirements Target System Requirements Machine Requirements Programming Requirements Installation Requisites Operational Requisites Toleration/Coexistence Requisites Incompatibility (Negative) Requisites DASD Storage Requirements FMIDs Deleted Special Considerations Installation Instructions Installing Host On-Demand SMP/E Considerations for Installing Host On-Demand SMP/E Options Subentry Values SMP/E CALLLIBS Processing Sample Jobs Copyright IBM Corp. 1997, 2009 iii

4 6.1.5 Perform SMP/E RECEIVE Allocate SMP/E Target and Distribution Libraries Allocate File system Paths Create DDDEF Entries Perform SMP/E APPLY Perform SMP/E ACCEPT Run REPORT CROSSZONE Activating Host On-Demand Completing the Installation of Host On-Demand Update Web Server Pass Rules and Resource Mapping Directives Start Host On-Demand Configuring Host On-Demand (Administration) Starting the Optional Native (Platform) Authentication Service Setup for Starting the Native Authentication Service Starting the Native (Platform) Authentication Service in USS z/os LDAP Directory Configuration To Set Up Schema When Using RDBM Backend To Set Up Schema When Using TDBM Backend To Set Up the Directory Tree (for either RDBM or TDBM) Performance Considerations (when using RDBM) Hints and Tips Notices Trademarks Reader's Comments Figures 1. Basic Material: Program Tape Program File Content Basic Material: Unlicensed Publications Basic Material: Licensed Publications Publications Useful During Installation Component IDs Driving System Software Requirements Target System Mandatory Installation Requisites Target System Conditional Installation Requisites Target System Mandatory Operational Requisites Target System Conditional Operational Requisites Total DASD Space Required by Host On-Demand Storage Requirements for SMP/E Work Data Sets iv Host On-Demand Program Directory

5 14. Storage Requirements for SMP/E Data Sets Storage Requirements for Host On-Demand Target Libraries Host On-Demand File System Paths Storage Requirements for Host On-Demand Distribution Libraries Alternative Conditional Operational Requisites SMP/E Options Subentry Values Sample Installation Jobs Figures v

6 vi Host On-Demand Program Directory

7 1.0 Introduction This program directory is intended for system programmers who are responsible for program installation and maintenance. It contains information about the material and procedures associated with the installation 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 and documentation 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 and considerations that are required for installing and using Host On-Demand. 6.0, Installation Instructions on page 21 provides detailed installation instructions for Host On-Demand. It also describes the procedures for activating the functions of Host On-Demand, or refers 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 information and 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 with security to users in intranet and extranet-based environments. It enables businesses to extend the reach of their host applications and data to new users, including business partners, suppliers, and sales personnel. Host On-Demand gives users secure browser access to host applications and data, with Web browser-based emulation. With support for TN3270E, TN5250, VT52/100/220, and CICS applications included in a single package, users need to learn only one interface to reach key host data. Because Host On-Demand is Java based, users in different operating environments get the same look and feel, and identical feature set. Host On-Demand is installed on the host and the Host On-Demand applet is downloaded via a Web URL to 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 rapidly create custom e-business applications to achieve a competitive advantage. Because Host On-Demand is Copyright IBM Corp. 1997,

8 part of the Rational family, applications developed using the toolkit can be incorporated into other Web software projects, helping preserve your Host On-Demand investment and helping provide a quick start to the 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

9 2.0 Program Materials An IBM program is identified by a program number. The program number for Host On-Demand is 5733-A59. Basic Machine-Readable Materials are materials that are supplied under the base license and feature numbers, and are required for the use of the product. Optional Machine-Readable Materials are orderable under 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 your IBM 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 in SMP/E RELFILE format and is installed by using SMP/E. See 6.0, Installation Instructions on page 21 for more information about how to install the program. Figure 1. Basic Material: Program Tape Medium 3490 Cart Cart. Physical Volume External Label VOLSER 1 IBM Rational Host On-Demand V11 1 IBM Rational Host On-Demand V11 HOJB00 HOJB00 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. Copyright IBM Corp. 1997,

10 Figure 2. Program File Content Name SMPMCS SEQ FB IBM.HHOJB00.F1 PDS FB IBM.HHOJB00.F2 PDS U O R G R E C F M L R E C L BLK SIZE IBM.HHOJB00.F3 PDS VB Optional Machine-Readable Material No optional machine-readable materials are provided for Host On-Demand Basic Program Publications Figure 3 identifies the basic unlicensed program publications for Host On-Demand. The publications are in softcopy form and can be accesssed by following the information that is presented in the tables and text that follows: Figure 3. Basic Material: Unlicensed Publications Publication Title Planning, Installing, and Configuring Readme Host Printing Reference Session Manager API HOD Macro Programming Guide Web Express Logon Reference Trouble Shooting Guide Programmable HOD Reference Toolkit Getting Started J2EE Connector Host Access Class Library Host Access Beans for Java Form Number N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A The publications are available from the Host On-Demand product Information Center: 4 Host On-Demand Program Directory

11 (continued): v11r0/index.jsp this site also includes all the product documentation, a search function, tutorials, white papers, and a link to 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 operating systems). The publications are also included in soft copy form (HTML and PDF) with the product and are viewable from your browser once the product has been successfully installed using the URL format listed below: Host On-Demand Online Documentation: name>/<webserver alias>/<language>/doc/ where <server name> refers to your z/os server's TCP/IP host name, <webserver alias> refers to your web 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.). An example of a URL to point to the English language Host On-Demand Planning, Installing, and Configuring is: Note: Host On-Demand requires the addition of PASS RULES added to your configuration file for your HTTP web server. Without these PASS RULES added to your web server, you will not be able to view the online documentation as well as execute functions within Host On-Demand. Typically, the configuration file is named httpd.conf and is typically found in your /etc directory in UNIX System Services. Listed below are the complete set of Pass Rules that you should have to successfully execute Host On-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 and the 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.ascii Pass /hod/.jnlp /usr/lpp/hod/hostondemand/hod/.jnlp.ascii Pass /hod/.html /usr/lpp/hod/hostondemand/hod/.html.ascii Pass /hod/.html /usr/lpp/hod/hostondemand/hod/.html.ascii Pass /hod/.js /usr/lpp/hod/hostondemand/hod/.js.ascii Pass /hod/.properties (continued on next line) /usr/lpp/hod/hostondemand/hod/.properties.ascii Pass /hod/.props /usr/lpp/hod/hostondemand/hod/.props.ascii Pass /hod/ /usr/lpp/hod/hostondemand/hod/ Program Materials 5

12 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 and online publications. The following resource mapping directives should also be included among the other rules in the AddType section of the Web Server configuration file. AddType.jnlp application/x-java-jnlp-file 8bit 1. AddType.cab application/octet-streambinary 1. AddType.jar multipart/x-zip binary 1. Note: Not all Host On-Demand publications are translated into all languages. provided if a translated version does not exist. An english version will be Figure 4 identifies the basic licensed program publications for Host On-Demand. The first copy is available at no charge to the licensees of the basic material by ordering the 7xxx feature number. Order additional copies by using the 8xxx feature number. A fee is charged for additional copies. Figure 4. Basic Material: Licensed Publications Publication Title No licensed publications Form Number Feature Number 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. To order copies, contact your IBM representative or visit the IBM Publications Center at Figure 5 (Page 1 of 2). Publications Useful During Installation Publication Title IBM SMP/E for z/os User's Guide IBM SMP/E for z/os Commands Form Number SA SA Host On-Demand Program Directory

13 Figure 5 (Page 2 of 2). Publications Useful During Installation Publication Title IBM SMP/E for z/os Reference IBM SMP/E for z/os Messages, Codes, and Diagnosis MVS z/os Command Reference MVS z/os System Codes MVS z/os Messages Library, System Messages Vol 1 MVS z/os Messages Library, System Messages Vol 2 MVS z/os Messages Library, System Messages Vol 3 MVS z/os Messages Library, System Messages Vol 4 MVS z/os Messages Library, System Messages Vol 5 MVS z/os Messages Library, System Messages Vol 6 MVS z/os Messages Library, System Messages Vol 7 MVS z/os Messages Library, System Messages Vol 8 MVS z/os Messages Library, System Messages Vol 9 MVS z/os Messages Library, System Messages Vol 10 UNIX System Services User's Guide UNIX System Services Command Reference UNIX System Services Messages and Codes Form Number SA GA SA SA SA SA SA SA SA SA SA SA SA SA SA SA SA Program Materials 7

14 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, and Hints and Tips on the following Web sites: Support site: Product information site: Program Directory softcopy: (continued): v11r0/index.jsp Hints and Tips site: If Host On-Demand is more than two weeks old when you install it, you should contact the IBM Support Center 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 Name HHOJB A5900 Host On-Demand V11 B00 RETAIN Release 8 Copyright IBM Corp. 1997, 2009

15 4.0 Program and Service Level Information This section identifies the program and relevant service levels of Host On-Demand. The program level refers to the APAR fixes that have been incorpo into the program. The service level refers to the PTFs that 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. Copyright IBM Corp. 1997,

16 5.0 Installation Requirements and Considerations The following sections identify the system requirements for installing and activating Host On-Demand. The following 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 of another product for link-edits. These requirements, either mandatory or optional, might directly affect the 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 can make a separate IPL-able clone of the running system to use as a target system. The clone must include copies of all system libraries that SMP/E udpates, copies of the SMP/E CSI data sets that describe the system 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 will replace the old one. By installing the new level onto a separate target system, you can test the new level 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 installation can disrupt the other products. By installing the product onto a separate target system, you can access 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 Machine Requirements The driving system can run in any hardware environment that supports the required software Programming Requirements 10 Copyright IBM Corp. 1997, 2009

17 Figure 7. Driving System Software Requirements Program Number Any one of the following: Product Name Minimum VRM Minimum Service Level will satisfy these APARs 5694-A01 z/os V N/A No 5655-G44 IBM SMP/E for z/os V N/A No Included in this product's shipment? Note: Installation may require migration to new z/os releases to be service supported. See Target System Requirements This section describes the environment of the target system that is required to install and use Host On-Demand. Host On-Demand installs in the z/os (Z038) SREL Machine Requirements The target system can run in any hardware environment that supports the required software Programming Requirements Installation Requisites Installation requisites identify products that are required by and must be present on the system or products that 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 successful installation of this product. These products are specified as PREs or REQs. Figure 8. Target System Mandatory Installation Requisites Program Number Product Name Minimum VRM Minimum Service Level will satisfy these APARs 5694-A01 z/os V or higher N/A No Included in this product's shipment? Installation Requirements and Considerations 11

18 Note: Installation may require migration to new z/os releases to be service supported. See Conditional installation requisites identify products that are not required for successful installation of this product but can resolve such things as certain warning messages at installation time. These products are specified as IF REQs. Figure 9. Target System Conditional Installation Requisites Program Number Product Name Minimum VRM 5655-A46 IBM Java V or higher Minimum Svc Lvl to satisfy these APARs Function for which this is a Req't N/A N/A No Included in this product's shipment? Operational Requisites Operational requisites are products that are required by and must be present on the system or products that are not required by but should be present on the system for this product to operate all or part of its functions. Mandatory operational requisites identify products that are required for this product to operate its basic functions. These products are specified as PREs or REQs. Figure 10. Target System Mandatory Operational Requisites Program Number ** see Note below Product Name and Minimum VRM/Service Level Note: z/os Communication Server TCP/IP must be running on your host. Also, needed for the basic function of Host On-Demand is a properly configured HTTP server. The IBM HTTP server is provided as a part of your base z/os operating system (FMID HIMW530). This function can also be found in Lotus Domino for z/os V6.5 and higher (5655-K36). Conditional operational requisites identify products that are not required for this product to operate its basic functions but are required at run time for this product to operate specific functions. These products are specified as IF REQs. 12 Host On-Demand Program Directory

19 Figure 11. Target System Conditional Operational Requisites Program Number Product Name and Minimum VRM/Service Level For Configuration Servlet Function: 5655-I35 WebSphere Application Server for z/os V6.0, V6.1, V7.0 For Web Server Function: Please also refer to the 5.4, Special Considerations on page 18 for non-z/os products that also satisfy the Web Application Server function if available. IBM HTTP Server V1.3.28, V2.0.42, V2.0.47, V6.0, V6.1, V7.0 For LDAP Function (z/os requisite only): Please also refer to the 5.4, Special Considerations on page 18 for non-z/os products that also satisfy the Web Server Function if available G52 IBM LDAP Directory Server V6.0, V6.1, or V A01 IBM LDAP Server running on z/os V1.9 and above Please also refer to the 5.4, Special Considerations on page 18 for non-z/os products that also satisfy the LDAP Function. Any one of the following for Web Express Logon: 5698-AMZ IBM Tivoli Access Manager for e-business V5.1, V6.0, or V6.1 Function Web Application Server Web Server LDAP LDAP Web Express Logon 5625-DB2 IBM DB2 Universal Database V9.1, V9.5 Web Express Logon Please also refer to the 5.4, Special Considerations on page 18 for non-z/os products that also satisfy the Web Express Logon function. 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 "Special Considerations" section. Refer to 5.4, Special Considerations on page 18 for the table of alternative requisites. For Host On-Demand V11, "basic function" consists of: Installation Requirements and Considerations 13

20 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 a browser and Java Plug-in are REQUIRED on the workstation (an exception to this is the use of the Web Start Client which does not require a browser). You may also reference the Planning, Installing, and Configuring Host On-Demand document Toleration/Coexistence Requisites Toleration/coexistence requisites identify products that must be present on sharing systems. These systems can be other systems in a multisystem environment (not necessarily sysplex), a shared DASD environment (such as test and production), or systems that reuse the same DASD environment at different time intervals. Host On-Demand has no toleration/coexistence requisites 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 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. Figure 12. Total DASD Space Required by Host On-Demand Library Type Target Distribution File System Total Space Required in 3390 Trks 1MB 960 MB 3700 MB Notes: 1. For non-recfm U data sets, IBM recommends using system-determined block sizes for efficient DASD utilization. For RECFM U data sets, IBM recommends using a block size of 32760, which is most efficient from the performance and DASD utilization perspective. 2. Abbreviations used for data set types are shown as follows. 14 Host On-Demand Program Directory

21 U S E Unique data set, allocated by this product and used by only this product. This table provides all the required information to determine the correct storage for this data set. You do not need to refer to other tables or program directories for the data set size. Shared data set, allocated by this product and used by this product and other products. To determine the correct storage needed for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the da already exists, it must have enough free space to accommodate the storage size given in this table. Existing shared data set, used by this product and other products. This data set is not allocated by this product. To determine the correct storage for this data set, add the storage size given in this table to those given in other tables (perhaps in other program directories). If the data set already exists, it must have enough free space to accommodate the storage size given in this table. If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old release and reclaim the space that was used by the old release and any service t had been installed. You can determine whether these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements 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/E Target and Distribution Libraries on page Abbreviations used for the file system path type are as follows. N X P New path, created by this product. Path created by this product, but may already exist from a previous release. 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. Installation Requirements and Considerations 15

22 Figure 13. Storage Requirements for SMP/E Work Data Sets Library DDNAME T Y P E O R G R E C F M L R E C L No. of 3390 Trks SMPWRK1 S PDS FB SMPWRK2 S PDS FB SMPWRK3 S PDS FB SMPWRK4 S PDS FB SMPWRK6 S PDS FB SYSUT1 U SEQ SYSUT2 U SEQ SYSUT3 U SEQ SYSUT4 U SEQ No. of DIR Blks Figure 14. Storage Requirements for SMP/E Data Sets Library DDNAME T Y P E O R G R E C F M L R E C L No. of 3390 Trks SMPLTS E PDS U SMPMTS E PDS FB SMPPTS E PDS FB SMPSCDS E PDS FB SMPSTS E PDS FB No. of DIR Blks The following figures describe the target and distribution libraries and file system paths required to install Host On-Demand. The storage requirements of Host On-Demand must be added to the storage required by 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 into common data sets. In addition, since some ALIAS names may not be unique, ensure that no naming conflicts will be introduced before merging libraries. 16 Host On-Demand Program Directory

23 Figure 15. Storage Requirements for Host On-Demand Target Libraries Library DDNAME Member Type Target Volume T Y P E O R G R E C F M L R E C L No. of 3390 Trks SHOMMOD1 LMOD TVOL1 U PDS U SHOMINST Sample EXEC TVOL1 U PDS FB No. of DIR Blks Figure 16. Host On-Demand File System Paths DDNAME T Y P E Path Name SHOM0001 N /usr/lpp/hod/ibm Figure 17. Storage Requirements for Host On-Demand Distribution Libraries Library DDNAME T Y P E O R G R E C F M L R E C L No. of 3390 Trks AHOMHFS1 U PDS VB AHOMINST U PDS FB AHOMMOD1 U PDS U No. of DIR Blks 5.3 FMIDs Deleted Installing Host On-Demand might result in the deletion of other FMIDs. To see which FMIDs will be deleted, 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 target and distribution zones. Note: These FMIDs are not automatically deleted from the Global Zone. If you want to delete these FMIDs from the Global Zone, see the SMP/E manuals for instructions. Installation Requirements and Considerations 17

24 5.4 Special Considerations This section includes a table of all the alternative (primarily non-z/os) Conditional Operation requisites you might 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 create your own HFS, job HOMHFS can be used to create your own for Host On-Demand. If you wish to create a zfs filesystem, reference the job in SYS1.SAMPLIB, BPXISZFS to allocate your own file system. The recommended zfs size is LINEAR CYL( ) for the ROOT filesystem. It is recommended that you create your own file system for Host On-Demand for serviceability. The HOMISMKD JCL sample is used to create the directory structure for your file system. HOMISMKD also creates a directory structure under the /usr/lpp/hod file system, which is assumed to already be allocated and mounted on the target system. 2. After you finish with the SMP/E portion of your installation including running HOMAPPLY and HOMACCPT, you will have to run the shell script hod11mvs.sh to complete the installation. Please read the directions carefully as there is a shell script, setinstpath.sh that you may have to edit before running the hod11mvs.sh shell script. Refer to 6.2, Activating Host On-Demand on page 27 for more details. 3. The following table lists all the alternative (primarily non-z/os) Conditional Operational requisites that you may alternately use for proper operation and function of Host On-Demand. Figure 18 (Page 1 of 3). Alternative Conditional Operational Requisites Product Name and Minimum VRM/Service Level Function 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 proper function of your Browser. The Plugin must be either Java Plugin 1.5 or above (from IBM, Sun, or HP). Please have this installed for the proper function of your browser. Microsoft Internet Explorer 6.0, 7.0, 8.0 FireFox 1.5, 2.0, 3.0 Safari 1.0, 2.0, Any one or more for Client Function: Browser Function Browser Function Browser Function 18 Host On-Demand Program Directory

25 Figure 18 (Page 2 of 3). Alternative Conditional Operational Requisites Product Name and Minimum VRM/Service Level Windows XP Professional and Home Edition(32 & 64 bit), Windows Server 2003 Enterprise Editions (32 & 64 bit), Windows Vista Business Edition(N,x86 & x64 editions), Windows Vista Enterprise Edition(N, x86 & x64 editions), Windows Vista Ultimate Edition (N, x86 & x64 editions), Windows 2008 server (32 & 64 bit), Windows 7 (32 & 64 bit), Windows Terminal Services for Windows 2003 IBM AIX V5.2, V5.3 (32 & 64 bit), V6.1 (32 & 64 bit) Sun Solaris 8, 9, 10 HP-UX 11.0, 11i, 11iv2, 11iv3 Redhat Enterprise Linux 3.0, 4.0, 5.0 Redhat Linux 9.0 Personal and Professional SUSE Linux V8.2, V9.0 SUSE Linux Enterprise Server 9.0, 10.0, & 11.0 TurboLinux V9.0 Workstation Citrix Metaframe 1.8 for Windows Terminal Server 4.0 and 1.8 for Windows 2000 Server Citrix Metaframe XP Presentation Server (Versions S, A, E) for Windows Feature Release V2, V3 Mac OS X , 10.3, and 10.4 Optional - Any one or more of the following needed for Web Server iplanet Web Server Enterprise Edition V6.0, V7.0 Microsoft IIS 5, 5,1, 6 Apache HTTP Server 1.3, 2.0, 2.2, Lotus Domino R6.5, R7, R8, R8.5 Optional - Needed for Web Express Logon Netegrity SiteMinder V5.5 Optional - Needed for Web Application Servers Client Client Client Client Client Client Client Client Client Client Client Client Function Web Server Web Server Web Server Web Server Web Express Installation Requirements and Considerations 19

26 Figure 18 (Page 3 of 3). Alternative Conditional Operational Requisites Product Name and Minimum VRM/Service Level Optional - Miscellaneous Software Optional - Development Environment iplanet Application Server V6.0, V7.0 Lotus Domino R6.5, R7, R8, R8.5 IBM WebSphere Portal for Multiplatforms V6.1 Acrobat Reader (or Acrobat) V6, V7, V8 CICS Transaction Gateway V5.1 and above Lotus Expeditor 6.1 or later and Eclipse V3.2 or later IBM Rational Application Developer V7.0, V7.5 Function Web Application Server Web Application Server Portal Function DBCS PDF support CICS transaction processing Development Environment 20 Host On-Demand Program Directory

27 6.0 Installation Instructions This chapter describes the installation method and the step-by-step procedures to install and to activate the 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 manuals for 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. The SMP/E jobs assume that all DDDEF entries that are required for SMP/E execution have been defined in appropriate zones. You can use the SMP/E dialogs instead of the sample jobs to accomplish the SMP/E installation steps. 6.1 Installing Host On-Demand 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 SMP/E Options Subentry Values The recommended values for certain SMP/E CSI subentries are shown in Figure 19. Using values lower than the recommended values can result in failures in the installation. DSSPACE is a subentry in the GLOBAL options entry. PEMAX is a subentry of the GENERAL entry in the GLOBAL options entry. See the SMP/E manuals for instructions on updating the global zone. Figure 19. SMP/E Options Subentry Values Subentry Value Comment DSSPACE (2500,500,175) Specifies the primary and secondary (in Tracks) and the number of directory blocks to be allocated for each SMPTLIB dataset. PEMAX SMP/E Default IBM recommends using the SMP/E default for PEMAX SMP/E CALLLIBS Processing Host On-Demand uses the CALLLIBS function that is provided in SMP/E to resolve external references during installation. When Host On-Demand is installed, ensure that DDDEFs exist for the following libraries: CEE.SCEELKED Copyright IBM Corp. 1997,

28 Note: CALLLIBs use the previous DDDEFs only to resolve the link-edit for Host On-Demand. These data sets are not updated during the installation of Host On-Demand Sample Jobs The following sample installation jobs are provided as part of the product to help you install Host On-Demand: 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 distribution libraries IBM.HHOJB00.F1 HOMHFS HFS Sample job to allocate HFS (OPTIONAL) IBM.HHOJB00.F1 HOMISMKD MKDIR Sample job to invoke the supplied HOMMKDIR EXEC 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 You can access the sample installation jobs by performing an SMP/E RECEIVE and then copying the jobs from the relfiles to a work data set for editing and submission. See Figure 20 to find the appropriate relfile data set. You can also copy the sample installation jobs from the tape or product files by submitting the following job. Depending on your distribution medium, Use either the //TAPEIN or the //FILEIN DD statement and comment out or delete the other statement. Before you submit the job, add a job card and change the lowercase 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) 22 Host On-Demand Program Directory

29 / 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. SYSIN xxxxin is either TAPEIN or FILEIN depending on your input DD statement Perform SMP/E RECEIVE If you install Host On-Demand as a Web download package, the SMP/E RECEIVE is performed during the execution of the README file. In this case, you can skip this section and continue with the next section of the program directory. If you have received Host On-Demand on tape media, edit and submit sample job HOMRECVE to perform the SMP/E RECEIVE for Host On-Demand. Consult the instructions in the sample job for more information. Expected Return Codes and Messages: Return Code = Allocate SMP/E Target and Distribution Libraries Edit and submit sample job HOMALLOC to allocate the SMP/E target and distribution libraries for Host On-Demand. Consult the instructions in the sample job for more information. Expected Return Codes and Messages: Return Code = Allocate File system Paths Host On-Demand can be installed into any existing HFS or zfs file system. However, if you wish to create 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 to run this: Installation Instructions 23

30 Expected Return Codes and Messages: Return Code = 0 If you wish to create a zfs file system, reference job SYS1.SAMPLIB(BPXISZFS) to allocate your own zfs filesystem. The recommended zfs size is LINEAR CYL( ) 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 sample HOMISMKD 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 the driving system, and that the file system of the target system is mounted to the driving system. If you install Host 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 new file 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 more details. Edit and submit sample job HOMISMKD to allocate the file system for Host On-Demand. Consult the instructions in the sample job for more information. If you create a new file system for this product, consider updating the BPXPRMxx PARMLIB member to mount the new file system at IPL time. This action can be helpful if an IPL occurs before the installation is completed Expected Return Codes and Messages: Return Code = Create DDDEF Entries Edit and submit sample job HOMDDDEF to create DDDEF entries for the SMP/E target and distribution libraries for Host On-Demand. Consult the instructions in the sample job for more information. Expected Return Codes and Messages: Return Code = 0 This job may receive warning message GIM56501W and rc=4. This message is issued when DDDEF entries 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 DDDEF entries 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 BECAUSE IT ALREADY EXISTS. GIM256 1I - THE SPECIFIED ENTRY WAS NOT UPDATED BECAUSE OF AN ERROR DURING UCLIN PROCESSING. 24 Host On-Demand Program Directory

31 with a rc=8 if the SCEELKED DDDEF entry already exists. You can either delete the ADD for SCEELKED 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/e zone), you must create one, at a minimum, to include the SMPMTS. You must have both a DDDEF entry for 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 Perform SMP/E APPLY 1. 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 more information. 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 Install the FMIDs regardless of the status of unresolved HIPERs. However, don't deploy the software until the unresolved HIPERs are analyzed 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 analysis identifies the cause only of errors and not of warnings (SMP/E treats bypassed PRE, ID, REQ, and IFREQ conditions as warnings, instead of errors). Here are two methods to install FMIDs when ++HOLDs for HIPERs exist for the FMIDs that you install: a. To ensure that all recommended and critical service is installed with the FMIDs, if you are using SMP/E 3.5 or higher and have received the latest HOLDDATA, add the FIXCAT operand to the APPLY command as shown below. If you are using a prior release of SMP/E, add the SOURCEID(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. Installation Instructions 25

32 Some HIPER APARs might not have PTFs available yet. You have to analyze the symptom flags to determine if you want to bypass the specific ERROR HOLDs and continue the installation of the FMIDs. This method requires more initial research, but can provide resolution for all HIPERs that have fixes available and are not in a PE chain. Unresolved PEs or HIPERs might still exist and require the use of BYPASS. b. To install the FMIDs without regard for the HIPERs, you can add a BYPASS(HOLDCLASS(HIPER)) operand to the APPLY command. In this way, you can install FMIDs even though HIPER ERROR HOLDs against them still exist. Only the HIPER ERROR HOLDs are bypassed. After the FMIDs are installed, run the SMP/E REPORT ERRSYSMODS command to identify missing HIPER maintenance. APPLY S(fmid,fmid,...) FORFMID(fmid,fmid,...) SOURCEID(RSU ) GROUPEXTEND BYPASS(HOLDCLASS(HIPER))...any other parameters documented in the program directory This method is the quicker of the two, but requires subsequent review of the REPORT ERRSYSMODS to investigate any HIPERs. If you are running SMP/E V3.5 or higher and have received the latest HOLDDATA, you can also choose to run REPORT MISSINGFIX for Fix Category IBM.ProductInstall-RequiredService to investigate missing recommended service. If you bypass HOLDs during the installation of the FMIDs because PTFs are not yet available, you can 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 run the job again to perform the APPLY. Note: The GROUPEXTEND operand indicates that SMP/E applies all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions. Expected Return Codes and Messages from APPLY CHECK: You will receive a return code of 0 if this job runs correctly. Expected Return Codes and Messages from APPLY: You will receive a return code of 0 if this job runs correctly 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 26 Host On-Demand Program Directory