Program Directory for CICS Transaction Server for z/os Value Unit Edition V5.1 V Program Number 5722-DFJ. FMIDs HCI6800, HCV6800

Transcription

1 IBM Program Directory for CICS Transaction Server for z/os Value Unit Edition V5.1 V5.1.0 Program Number 5722-DFJ FMIDs HCI6800, HCV6800 for Use with z/os on znalc Document Date: April 2013 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 43. 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 1974, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents 1.0 Introduction CICS TS Description CICS TS VUE V5.1 FMIDs Program Materials Basic Machine-Readable Material Optional Machine-Readable Material 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 IBM CICS Explorer Availability Service and Support SMP/E Considerations Installation Instructions Installing CICS TS VUE V SMP/E Options Subentry Values Copyright IBM Corp. 1974, 2013 iii

4 6.1.2 SMP/E CALLLIBS Processing Sample Jobs Run the installation Jobs for CICS TS for z/os v The DFHIHFS0 Job The DFHIHFS1 Job The DFHISMKD Job The DFHALLOC Job The DFHSMPSU Job The DFHDDDEF Job The DFHRECV Job The DFHRECVE Job The DFHAPPLY Job The DFHACCPT Job The DFHIJVMS Job The DFHCSVCU Job Run REPORT CROSSZONE Run the installation Jobs for CICS TS VUE V The DFHVALOC Job The DFHVSMPS Job The DFHVDDEF Job The DFHVRECV Job The DFHVRCVE Job The DFHVAPLY Job The DFHVACPT Job Activating CICS TS VUE V Notices Trademarks Reader's Comments Figures 1. Basic Material: Unlicensed Publications Useful During Installation PSP Upgrade and Subset ID Component IDs Driving System Software Requirements Target System Mandatory Installation Requisites Target System Mandatory Operational Requisites Total DASD Space Required by CICS TS VUE V Storage Requirements for CICS TS VUE V5.1 Target Libraries iv CICS TS VUE V5.1 Program Directory

5 10. CICS TS VUE V5.1 File System Paths Storage Requirements for CICS TS VUE V5.1 Distribution Libraries SMP/E Options Subentry Values Sample Installation Jobs Figures v

6 vi CICS TS VUE V5.1 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 CICS Transaction Server for z/os Value Unit Edition V5.1. This publication refers to CICS Transaction Server for z/os Value Unit Edition V5.1 as CICS TS VUE V5.1. The Program Directory contains the following sections: 2.0, Program Materials on page 3 identifies the basic program materials and documentation for CICS TS VUE V , Program Support on page 9 describes the IBM support available for CICS TS VUE V , Program and Service Level Information on page 13 lists the APARs (program level) and PTFs (service level) that have been incorporated into CICS TS VUE V , Installation Requirements and Considerations on page 15 identifies the resources and considerations that are required for installing and using CICS TS VUE V , Installation Instructions on page 27 provides detailed installation instructions for CICS TS VUE V5.1. It also describes the procedures for activating the functions of CICS TS VUE V5.1, or refers to appropriate publications. 1.1 CICS TS Description CICS TS is IBM's leading product for transaction processing on the mainframe, and is used by a high proportion of the world's largest companies for their critical business processes. It is designed to execute mixed language application workloads, supporting both modern and traditional programming languages and models. Its extensive data communication services, and its foundations in service-oriented architecture (SOA), provide unparalleled connectivity and scalability. As a result, CICS TS VUE V5.1 fits naturally into a smart infrastructure of the kind needed for a flexible, global enterprise. CICS TS Value Unit Edition (VUE) V5.1 introduces support for deploying qualified new CICS TS workloads on IBM System z New Application License Charges (znalc) Logical Partitions (LPARs). Qualified new CICS TS applications, including approved mobile and service-enabled applications running in the CICS TS Java Virtual Machine (JVM) Server, will be eligible for CICS TS one-time-charge (OTC) pricing when deployed to a znalc LPAR. 1.2 CICS TS VUE V5.1 FMIDs CICS TS VUE V5.1 consists of the following FMIDs: HCI6800 JCI6801 JCI6802 Copyright IBM Corp. 1974,

8 JCI6803 JCI680D JCI680L JCI680M JCI680W HCIZ300 H0B5110 H0B7110 H0Z2110 HCV CICS TS VUE V5.1 Program Directory

9 2.0 Program Materials An IBM program is identified by a program number. The program number for CICS TS VUE V5.1 is 5722-DFJ. 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. For more information, visit Basic Machine-Readable Material The distribution medium for this program is physical media. This program is in SMP/E RELFILE format and is installed by using SMP/E. See 6.0, Installation Instructions on page 27 for more information about how to install the program. 2.2 Optional Machine-Readable Material No optional machine-readable materials are provided for CICS TS VUE V Program Publications The following sections identify the basic publications for CICS TS VUE V5.1. Figure 1 identifies the basic unlicensed or licensed publications. Those that are softcopy format can be obtained from the IBM Publications Website at URL: Figure 1 (Page 1 of 4). Basic Material: Unlicensed Publication Title CICS Transaction Server for z/os Value Unit Edition V5.1 Memo to Licensees CICS Transaction Server for z/os Value Unit Edition V5.1 License Information CD CICS Transaction Server for z/os Value Unit Edition V5.1 Information Flyer Form Number GI GC GI Media Format Hardcopy Hardcopy Hardcopy CICS Technical Services Flyer GI Hardcopy CICS Transaction Server for z/os V5.1: Application Programming Guide SC Copyright IBM Corp. 1974,

10 Figure 1 (Page 2 of 4). Basic Material: Unlicensed Publication Title CICS Transaction Server for z/os V5.1: Application Programming Reference CICS Transaction Server for z/os V5.1: Business Transaction Services CICS Transaction Server for z/os V5.1: Customization Guide CICS Transaction Server for z/os V5.1: C++ OO Class Libraries Form Number SC SC SC SC Media Format CICS Transaction Server for z/os V5.1: Data Areas GC CICS Transaction Server for z/os V5.1: CICS DB2 Guide SC CICS Transaction Server for z/os V5.1: Debugging Tools Interfaces Reference CICS Transaction Server for z/os V5.1: Diagnosis Reference CICS Transaction Server for z/os V5.1: Distributed Programming Reference CICS Transaction Server for z/os V5.1: CICS External Interfaces Guide CICS Transaction Server for z/os V5.1: Front End Programming Interface Guide CICS Transaction Server for z/os V5.1: CICS IMS Database Control Guide GC GC SC SC SC SC CICS Transaction Server for z/os V5.1: Installation Guide GC CICS Transaction Server for z/os V5.1: CICS Intercommunication Guide SC CICS Transaction Server for z/os V5.1: Internet Guide SC CICS Transaction Server for z/os V5.1: Java Applications in CICS CICS Transaction Server for z/os V5.1: CICS Messages and Codes Vol 1 CICS Transaction Server for z/os V5.1: CICS Messages and Codes Vol 2 SC GC GC CICS TS VUE V5.1 Program Directory

11 Figure 1 (Page 3 of 4). Basic Material: Unlicensed Publication Title CICS Transaction Server for z/os V5.1: Operations and Utilities Guide Form Number SC Media Format CICS Transaction Server for z/os V5.1: Performance Guide SC CICS Transaction Server for z/os V5.1: CICS Problem Determination Guide CICS Transaction Server for z/os V5.1: RACF Security Guide CICS Transaction Server for z/os V5.1: Recovery and Restart Guide CICS Transaction Server for z/os V5.1: Resource Definition Guide CICS Transaction Server for z/os V5.1: CICS Shared Data Tables Guide CICS Transaction Server for z/os V5.1: CICS-Supplied Transactions CICS Transaction Server for z/os V5.1: System Definition Guide CICS Transaction Server for z/os V5.1: System Programming Reference GC SC SC SC SC SC SC SC CICS Transaction Server for z/os V5.1: CICS Trace Entries SC CICS Transaction Server for z/os V5.1: Upgrading from Version 3.1 CICS Transaction Server for z/os V5.1: Upgrading from Version 3.2 CICS Transaction Server for z/os V5.1: Upgrading from Version 4.1 CICS Transaction Server for z/os V5.1: Upgrading from Version 4.2 CICS Transaction Server for z/os V5.1: Web Services Guide GC GC GC GC SC CICS Transaction Server for z/os V5.1: What's new GC CICS Transaction Server for z/os V5.1: CICSPlex SM Administration SC Program Materials 5

12 Figure 1 (Page 4 of 4). Basic Material: Unlicensed Publication Title CICS Transaction Server for z/os V5.1: CICSPlex SM Application Programming Guide CICS Transaction Server for z/os V5.1: CICSPlex SM Application Programming Reference CICS Transaction Server for z/os V5.1: CICSPlex SM Concepts and Planning CICS Transaction Server for z/os V5.1: CICSPlex SM Managing Business Applications CICS Transaction Server for z/os V5.1: CICSPlex SM Managing Resource Usage CICS Transaction Server for z/os V5.1: CICSPlex SM Managing Workloads CICS Transaction Server for z/os V5.1: CICSPlex SM Messages and Codes CICS Transaction Server for z/os V5.1: CICSPlex SM Monitor Views Reference CICS Transaction Server for z/os V5.1: CICSPlex SM Operations View Reference CICS Transaction Server for z/os V5.1: CICSPlex SM Problem Determination Guide CICS Transaction Server for z/os V5.1: CICSPlex SM Resource Tables Reference Vol 1 CICS Transaction Server for z/os V5.1: CICSPlex SM Resource Tables Reference Vol 2 CICS Transaction Server for z/os V5.1: CICSPlex SM Web User Interface Form Number SC SC SC SC SC SC GC SC SC GC SC SC SC Media Format CICS Transaction Server for z/os V5.1: Program Directory GI No optional publications are provided for CICS TS VUE V Program Source Materials No program source materials or viewable program listings are provided for CICS TS VUE V CICS TS VUE V5.1 Program Directory

13 2.5 Publications Useful During Installation You might want to use the publications listed in Figure 2 on page 7 during the installation of CICS TS VUE V5.1. Figure 2. Publications Useful During Installation Publication Title Form Number Media Format IBM SMP/E for z/os User's Guide SA Softcopy IBM SMP/E for z/os Commands SA Softcopy IBM SMP/E for z/os Reference SA Softcopy IBM SMP/E for z/os Messages, Codes, and Diagnosis GA Softcopy z/os UNIX System Services User's Guide SA Softcopy CICS Transaction Server for z/os V5.1 Information for AIX CICS Transaction Server for z/os V5.1 Information for Linux Intel CICS Transaction Server for z/os V5.1 Information for Microsoft Windows CICS Transaction Server for z/os V5.1 Information for z/os SK4T-2692 SK4T-2693 SK4T-2694 SK4T-2695 CICS Transaction Server for z/os V5.1: Installation Guide GC Softcopy Hardcopy and Softcopy Hardcopy and Softcopy Hardcopy and Softcopy Hardcopy and Softcopy Program Materials 7

14 8 CICS TS VUE V5.1 Program Directory

15 3.0 Program Support This section describes the IBM support available for CICS TS VUE V Program Services Contact your IBM representative for specific information about available program services. 3.2 Preventive Service Planning Before you install CICS TS VUE V5.1, make sure that you have reviewed the current Preventive Service Planning (PSP) information. Review the PSP Bucket for General Information, Installation Documentation, and the Cross Product Dependencies sections. For the Recommended Service section, instead of reviewing the PSP Bucket, it is recommended you use the IBM.ProductInstall-RequiredService fix category in SMP/E to ensure you have all the recommended service installed. Use the FIXCAT(IBM.ProductInstall-RequiredService) operand on the APPLY CHECK command. See , The DFHAPPLY Job on page 34 for a sample APPLY command. If you obtained CICS TS VUE V5.1 as part of a CBPDO, HOLDDATA is included. If the CBPDO for CICS TS VUE V5.1 is older than two weeks by the time you install the product materials, you can obtain the latest PSP Bucket information by going to the following website: You can also use S/390 SoftwareXcel or contact the IBM Support to obtain the latest PSP Bucket information. For program support, access the Software Support Website at PSP Buckets are identified by UPGRADEs, which specify product levels; and SUBSETs, which specify the FMIDs for a product level. The UPGRADE and SUBSET values for CICS TS VUE V5.1 are included in Figure 3 Figure 3 (Page 1 of 2). PSP Upgrade and Subset ID UPGRADE SUBSET Description CICSTS51 HCI6800 CICS TS Base JCI6801 COBOL Language Parts JCI6802 PL/I Language Parts JCI6803 C Language Parts Copyright IBM Corp. 1974,

16 Figure 3 (Page 2 of 2). PSP Upgrade and Subset ID UPGRADE SUBSET Description JCI680D Java JCI680M CICSPlex System Manager H0B5110 CICS REXX Runtime Facility H0B7110 CICS REXX Development System H0Z2110 CICS REXX Common for CICS/ESA JCI680W WS-Security HCIZ300 Service Flow Runtime JCI680L WAS Liberty Profile Web feature HCV6800 CICS TS Value Unit Edition feature 3.3 Statement of Support Procedures Report any problems which you feel might be an error in the product materials to your IBM Support. You may be asked to gather and submit additional diagnostics to assist the IBM Support in their analysis. Figure 4 identifies the component IDs (COMPID) for CICS TS VUE V5.1. Figure 4 (Page 1 of 2). Component IDs FMID COMPID Component Name HCI Y0400 CICS TS Base 800 JCI Y0400 COBOL Language Parts 801 JCI Y0400 PL/I Language Parts 802 JCI Y0400 C Language Parts 803 JCI680D 5655Y0400 Java 80D JCI680L 5655Y0400 WAS Liberty Profile Web feature 80L JCI680M 5655Y0400 CICSPlex System Manager 80M JCI680W 5655Y0400 WS-Security 80W HCIZ M1502 Service Flow Runtime 300 H0B CICS REXX Runtime Facility 110 H0B CICS REXX Development System 110 H0Z CICS REXX Common for CICS/ESA 110 HCV DFJ00 CICS TS Value Unit Edition feature 800 RETAIN Release 10 CICS TS VUE V5.1 Program Directory

17 Figure 4 (Page 2 of 2). Component IDs FMID COMPID Component Name CICS Explorer Feature RETAIN Release Program Support 11

18 12 CICS TS VUE V5.1 Program Directory

19 4.0 Program and Service Level Information This section identifies the program and relevant service levels of CICS TS VUE V5.1. The program level refers to the APAR fixes that have been incorporated into the program. The service level refers to the PTFs that have been incorporated into the program. 4.1 Program Level Information You can find the APARs against previous releases of CICS TS for z/os that have been incorporated into this release by going to: Service Level Information No PTFs against this release of CICS TS VUE V5.1 have been incorporated into the product package. It is highly recommended that you frequently check the CICS TS VUE V5.1 PSP Bucket for HIPER and SPECIAL attention PTFs against all FMIDs that you must install. You can also receive the latest HOLDDATA, then add the FIXCAT(IBM.PRODUCTINSTALL-REQUIREDSERVICE) operand on your APPLY CHECK command. This will allow you to review the recommended and critical service that should be installed with your FMIDs. Copyright IBM Corp. 1974,

20 14 CICS TS VUE V5.1 Program Directory

21 5.0 Installation Requirements and Considerations The following sections identify the system requirements for installing and activating CICS TS VUE V5.1. The following terminology is used: Driving system: the system on which SMP/E is executed to install the program. 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 updates, 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 assess these impacts without disrupting your production system. 5.1 Driving System Requirements This section describes the environment of the driving system required to install CICS TS VUE V Machine Requirements The driving system can run in any hardware environment that supports the required software Programming Requirements Copyright IBM Corp. 1974,

22 Figure 5. Driving System Software Requirements Program Number Product Name Minimum VRM Minimum Service Level will satisfy these APARs 5694-A01 z/os V01.13 and above N/A No Included in this product's shipment? Note: Installation might 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 CICS TS VUE V 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 6. Target System Mandatory Installation Requisites Program Number Product Name Minimum VRM Minimum Service Level will satisfy these APARs 5694-A01 z/os V01.13 and above N/A No Included in the shipped product? Note: Installation might require migration to new z/os releases to be service supported. See 16 CICS TS VUE V5.1 Program Directory

23 In order for CICS to record the CPU time consumed by transactions on zaap and ziip specialty engines in monitoring performance records (SMF type 110), the PTF for z/os APAR OA38409 is required. To use the new replication logging support for VSAM and RLS files, PTFs for the following z/os APARs are required: OA38200 OA38209 OA38201 OA38198 OA38550 OA38205 OA38203 OA38202 OA38210 OA38204 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. CICS TS VUE V5.1 has no conditional installation requisites 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 7. Target System Mandatory Operational Requisites Program Number Product Name and Minimum VRM/Service Level 5694-A01 V01.13 and above 5655-Y04 CICS TS V5.1 with APAR PM82106 and above 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. Please refer to the following web page for the latest operational requisite product information for CICS TS for z/os V5.1 and CICS TS VUE V Installation Requirements and Considerations 17

24 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. CICS TS VUE V5.1 has no toleration/coexistence requisites Incompatibility (Negative) Requisites: Negative requisites identify products that must not be installed on the same system as this product. CICS TS VUE V5.1 has no negative requisites DASD Storage Requirements CICS TS VUE V5.1 libraries can reside on all supported DASD types. Figure 8 lists the total space that is required for each type of library. Figure 8. Total DASD Space Required by CICS TS VUE V5.1 Library Type Target Distribution 9793 zfs 3000 Total Space Required in 3390 Trks File System Description 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. 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 data set 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 18 CICS TS VUE V5.1 Program Directory

25 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 that 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 , The DFHALLOC Job 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 might 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 can be changed. The default block size of the data set can be changed. The data set can be merged with another data set that has equivalent characteristics. The data set can 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-managed. 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 LPA. 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 install CICS TS VUE V5.1. The storage requirements of CICS TS VUE V5.1 must be added to the storage required by other programs that have data in the same library or path. Note: Use the data in these tables to determine 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. Installation Requirements and Considerations 19

26 Figure 9 (Page 1 of 2). Storage Requirements for CICS TS VUE V5.1 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 SDFHINST SAMP ANY U PDS FB SDFHAPD1 SAMP ANY U PDS FB SDFHAPD2 SAMP ANY U PDS FB SDFHENV SAMP ANY U PDS V SDFHMAC SAMP ANY U PDS FB SDFHMSGS SAMP ANY U PDS V SDFHPARM SAMP ANY U PDS FB SDFHPROC SAMP ANY U PDS FB SDFHSAMP SAMP ANY U PDS FB SDFHLINK LMOD ANY U PDS U SDFHLOAD LMOD ANY U PDS U SDFHEXCI LMOD ANY U PDS U SDFHAUTH LMOD ANY U PDS U SDFHLPA LMOD ANY U PDS U SDFHCOB SAMP ANY U PDS FB SDFHPL1 SAMP ANY U PDS FB SDFHC370 SAMP ANY U PDS FB SDFHSDCK SAMP ANY U PDS FB SDFJAUTH LMOD ANY U PDSE U 0 30 NA SDFHDLL1 LMOD ANY U PDS U SDFHWSLD LMOD ANY U PDSE U NA SDFHWSSX SAMP ANY U PDS FB SEYUVIEW SAMP ANY U PDSE VB NA SEYUCLIB SAMP ANY U PDS FB SEYUCOB SAMP ANY U PDS FB SEYUC370 SAMP ANY U PDS FB SEYUDEF SAMP ANY U PDS FB SEYUMAC SAMP ANY U PDS FB SEYUPARM SAMP ANY U PDS FB No. of DIR Blks 20 CICS TS VUE V5.1 Program Directory

27 Figure 9 (Page 2 of 2). Storage Requirements for CICS TS VUE V5.1 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 SEYUPL1 SAMP ANY U PDS FB SEYUPROC SAMP ANY U PDS FB SEYUSAMP SAMP ANY U PDS FB SEYULOAD LMOD ANY U PDS U SEYUAUTH LMOD ANY U PDS U SEYULINK LMOD ANY U PDS U SEYULPA LMOD ANY U PDS U SCICJCL SAMP ANY U PDS FB SCICLOAD LMOD ANY U PDS U SCICPNL SAMP ANY U PDS FB SCICDBRM SAMP ANY U PDS FB SCICBOOK SAMP ANY U PDS FB SCICDOC SAMP ANY U PDS VB SCICCMDS SAMP ANY U PDS VB SCICEXEC SAMP ANY U PDS VB SCICUSER SAMP ANY U PDS VB SCIZINST SAMP ANY U PDS FB SCIZMAC SAMP ANY U PDS FB SCIZSAMP SAMP ANY U PDS FB SCIZLOAD LMOD ANY U PDS U SDFHVINS SAMP ANY U PDS FB SDFHVUE LMOD ANY U PDS U No. of DIR Blks Figure 10. CICS TS VUE V5.1 File System Paths DDNAME T Y P E Path Name SDFHH001 N /usr/lpp/cicsts/@ussdir@/ibm SDFHL001 N /usr/lpp/cicsts/@ussdir@/wlp/ibm Installation Requirements and Considerations 21

28 Figure 11 (Page 1 of 2). Storage Requirements for CICS TS VUE V5.1 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 ADFHINST U PDS FB ADFHMOD U PDS U ADFHAPD1 U PDS FB ADFHAPD2 U PDS FB ADFHENV U PDS V ADFHMAC U PDS FB ADFHMSGS U PDS V ADFHPARM U PDS FB ADFHPROC U PDS FB ADFHSAMP U PDS FB ADFHCOB U PDS FB ADFHPL1 U PDS FB ADFJMOD U PDSE U 0 45 NA ADFHC370 U PDS FB ADFHSDCK U PDS FB ADFHH001 U PDS V ADFHL001 U PDS V ADFHLSCR U PDS VB ADFHMOD2 U PDSE U NA AEYUMOD U PDS U AEYUVIEW U PDSE VB NA AEYUCLIB U PDS FB AEYUCOB U PDS FB AEYUC370 U PDS FB AEYUDEF U PDS FB AEYUMAC U PDS FB AEYUPARM U PDS FB AEYUPL1 U PDS FB AEYUPROC U PDS FB No. of DIR Blks 22 CICS TS VUE V5.1 Program Directory

29 Figure 11 (Page 2 of 2). Storage Requirements for CICS TS VUE V5.1 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 AEYUSAMP U PDS FB ACICRMOD U PDS U ACICJCL U PDS FB ACICMOD U PDS U ACICPNL U PDS FB ACICDBRM U PDS FB ACICBOOK U PDS FB ACICDOC U PDS VB ACICCMDS U PDS VB ACICEXEC U PDS VB ACICUSER U PDS VB ACICDMOD U PDS U ACICDUSR U PDS VB ACIZINST U PDS FB ACIZMOD U PDS U ACIZMAC U PDS FB ACIZSAMP U PDS FB ADFHVINS U PDS FB ADFHVMOD U PDS U No. of DIR Blks 5.3 FMIDs Deleted Installing CICS TS VUE V5.1 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 CICS TS VUE V5.1 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, use the SMP/E REJECT NOFMID DELETEFMID command. See the SMP/E manuals for instructions. Installation Requirements and Considerations 23

30 5.4 Special Considerations For this release the Java level required is V7.0 SR 1. Please remember this if using DFHISTAR. You have a choice of installation methods: DFHISTAR when coded and run will generate the install jobs and some post install jobs for you. DFHIHELP contains documentation to assist the coding of DFHISTAR. The standard method of install whereby those sample installation jobs listed in Figure 17 are each edited and submitted in turn IBM CICS Explorer IBM CICS Explorer is an integration point for CICS TS, CICS tools, and CICS Transaction Gateway. It provides a common, intuitive, easy-to-use way of managing one or more CICS regions, using an Eclipse-based environment that is aimed at architects, developers, administrators, system programmers and operators. The CICS Explorer Software Development Kit (SDK) is also available to create, extend and integrate software tools as plug-ins to the CICS Explorer framework Availability: Customers can download and use a fully featured version of the CICS Explorer and a selection of plug-ins for CICS tools products Service and Support: For details on getting started with CICS Explorer, visit For details on the latest version of CICS Explorer, and CICS tools plug-ins for CICS Explorer, visit For details on ordering maintenance for CICS Explorer, and CICS tools plug-ins for CICS Explorer, visit SMP/E Considerations IBM recommends that you install CICS TS VUE V5.1 into a new set of SMP/E zones, including SMPCSI, target, distribution, and zfs data sets, to allow independent maintenance of CICS TS VUE V5.1, z/os, and other subsystems. This program directory provides sample jobs and instructions to create such an SMP/E environment For the FMIDs listed below, the same version FMIDs are provided in this and previous releases and as such the SMPMCS rework dates have not changed. H0B5110 CICS REXX Runtime Facility H0B7110 CICS REXX Development System H0Z2110 CICS REXX Common for CICS/ESA 24 CICS TS VUE V5.1 Program Directory

31 HCIZ300 Service Flow Runtime If you intend to install CICS TS 5.1 in to an existing CICS SMP/E environment you may get an error message stating that these FMIDS are are already installed. In this case you can remove these FMIDS from the SMP/E APPLY and ACCEPT Installation job. If you install CICS TS 5.1 into a new CICS SMP/E environment, as recommended, these errors will not occur. In both cases, please ensure you apply all available service to these FMIDS. For users of CICS REXX, the PTF for APAR OA40674 is mandatory. This must be applied, as REXX will not work in CICS 5.1 without it. Installation Requirements and Considerations 25

32 26 CICS TS VUE V5.1 Program Directory

33 6.0 Installation Instructions This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of CICS TS VUE V5.1. Please note the following: 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. You can use the SMP/E manuals when working with the sample jobs for information about creating and initializing the SMPCSI and SMP/E control data sets. 6.1 Installing CICS TS VUE V5.1 To install CICS TS VUE V5.1 you must have installed CICS TS for z/os V5.1 on a znalc LPAR. If you do not have CICS TS for z/os V5.1 installed, use the SMP/E RECEIVE, APPLY, and ACCEPT commands to install it. This installation is detailed in 6.2, Run the installation Jobs for CICS TS for z/os v5.1 on page 30. When this is completed you can install CICS TS VUE V5.1 by following the instructions in 6.3, Run the installation Jobs for CICS TS VUE V5.1 on page SMP/E Options Subentry Values The recommended values for certain SMP/E CSI subentries are shown in Figure 12. 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 12. SMP/E Options Subentry Values Subentry Value Comment DSSPACE 3130,950,733 The space used if SMP/E allocates the RELFILE data sets PEMAX SMP/E Default IBM recommends using the SMP/E default for PEMAX. Binder return code 4 IBM recommends using a minimum return code of 4 for the binder. Copyright IBM Corp. 1974,

34 6.1.2 SMP/E CALLLIBS Processing CICS TS VUE V5.1 uses the CALLLIBS function that is provided in SMP/E to resolve external references during installation. When CICS TS VUE V5.1 is installed, ensure that DDDEFs exist for the following libraries: CSSLIB DSNLOAD MACLIB MODGEN SCEELIB SCEELKED SCEELKEX SCEEBND2 SCEEOBJ SCEECPP SCLBSID SCSFMOD0 SEZARPCL SEZACMTX SISPLOAD Note: CALLLIBS uses the previous DDDEFs only to resolve the link-edit for CICS TS VUE V5.1. These data sets are not updated during the installation of CICS TS VUE V Sample Jobs The following sample installation jobs are provided as part of the product to help you install CICS TS VUE V5.1: Figure 13 (Page 1 of 2). Sample Installation Jobs Job Name Job Type Description RELFILE DFHIHFS0 Sample job to create zfs data set and directory IBM.HCI6800.F2 DFHIHFS1 Sample job to create and mount zfs directory IBM.HCI6800.F2 DFHISMKD MKDIR Sample job to invoke the supplied DFHMKDIR EXEC to allocate zfs paths DFHALLOC ALLOCATE Sample job to allocate target and distribution libraries IBM.HCI6800.F2 IBM.HCI6800.F2 DFHSMPSU ZONES Sample job to setup SMP/E zones IBM.HCI6800.F2 DFHDDDEF DDDEF Sample job to create DDDEF entries for Target and Distribution libraries IBM.HCI6800.F2 DFHRECV RECEIVE Sample RECEIVE job from tape IBM.HCI6800.F2 28 CICS TS VUE V5.1 Program Directory

35 Figure 13 (Page 2 of 2). Sample Installation Jobs Job Name Job Type Description RELFILE DFHRECVE RECEIVE Sample RECEIVE job from DASD IBM.HCI6800.F2 DFHAPPLY APPLY Sample APPLY job IBM.HCI6800.F2 DFHACCPT ACCEPT Sample ACCEPT job IBM.HCI6800.F2 DFHIJVMS Optional sample to add JVM profiles to zfs IBM.HCI6800.F2 DFHCSVCU Optional sample to dynamically update the CICS SVC DFHVALOC ALLOCATE Sample job to allocate target and distribution libraries for CICS TS VUE V5.1 DFHVSMPS ZONES Sample job to setup SMP/E zones for CICS TS VUE V5.1 DFHVDDEF DDDEF Sample job to create DDDEF entries for Target and Distribution libraries for CICS TS VUE V5.1 DFHVRECV RECEIVE Sample RECEIVE job from tape for CICS TS VUE V5.1 DFHVRCVE RECEIVE Sample RECEIVE job from DASD for CICS TS VUE V5.1 IBM.HCI6800.F2 IBM.HCV6800.F2 IBM.HCV6800.F2 IBM.HCV6800.F2 IBM.HCV6800.F2 IBM.HCV6800.F2 DFHVAPLY APPLY Sample APPLY job for CICS TS VUE V5.1 IBM.HCV6800.F2 DFHVACPT ACCEPT Sample ACCEPT job for CICS TS VUE V5.1 IBM.HCV6800.F2 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 13 on page 28 to find the appropriate relfile data set. There are two installation methods provided, the first follows the IBM Corporate Standards. However, some users may be familiar with DFHISTAR and this method is still available. For more information on DFHISTAR refer to member DFHIHELP in data set 'IBM.HCI6800.F2' or refer to the "Installing CICS TS using DFHISTAR" section of the CICS Transaction Server Installation Guide. 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.HCI68.F2,UNIT=tunit, // VOL=SER=volser,LABEL=(x,SL), // DISP=(OLD,KEEP) //FILEIN DD DSN=IBM.HCI68.F2,UNIT=SYSALLDA,DISP=SHR, // VOL=SER=filevol Installation Instructions 29

36 //OUT DD DSNAME=jcl-library-name, // DISP=(NEW,CATLG,DELETE), // VOL=SER=dasdvol,UNIT=SYSALLDA, // SPACE=(TRK,(75,75,75 )) //SYSUT3 DD UNIT=SYSALLDA,SPACE=(TRK,(15,15)) //SYSIN DD COPY INDD=xxxxIN,OUTDD=OUT / 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. See the documentation that is provided by CBPDO for the location of IBM.HCI6800.F2 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. 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. 6.2 Run the installation Jobs for CICS TS for z/os v5.1 This section relates to the installation of CICS TS for z/os v5.1, which must be installed before CICS TS VUE V5.1 can be installed. If you already have CICS TS for z/os v5.1 installed, proceed to 6.3, Run the installation Jobs for CICS TS VUE V5.1 on page 38. OMVS requirement Before running the installation jobs: Ensure the MVS image was IPLed with OMVS in full-function mode. Ensure the user ID under which you are running the jobs has superuser authority. 30 CICS TS VUE V5.1 Program Directory

37 Installation method choice You must now choose which installation method to use: The traditional method which is documented below. The DFHISTAR method which will code all your install and post install JCL for you. Documentation for this can be found in SDFHINST member DFHIHELP. Note: If you wish to install into a non-sms managed environment add the appropriate STORCLAS and VOLUME parameters accordingly to the sample JCL. This section describes the CICS Transaction Server installation jobs, and gives considerations that may affect how you use them. The CICS Transaction Server jobs are in the library you created as a result of copying the installation file from the distribution tape These jobs should be run one at a time. Before you run a job, read the information about it (starting in topic DFHIHFS0 on page 31). After you have run a job, check its output before proceeding to the next job. If a job terminates abnormally, find out why it failed (the job log lists the error messages produced on each run). Correct the error, and then proceed as advised in the job description. In any case, do not attempt to run the next job until the previous job has run successfully. All references below to 'zfs data set' means the data set created by the jobs for use within the z/os UNIX File System The DFHIHFS0 Job: creates a directory (/usr/lpp/cicsts) that is used as a parent directory for the zfs mounts required for each CICS release. This directory and mount is only ever created once for all CICS releases, and if the directory currently exists the job should not be run. The follow up job DFHIHFS1 creates a release specific zfs mounted in this directory for this release of CICS. Edit and submit sample job DFHALLOC to allocate the SMP/E target and distribution libraries for CICS Transaction Server. Consult the instructions in the sample job for more information. Expected Return Codes and Messages: 0 This job Creates the cicsts directory at /usr/lpp Mounts the zfs at directory /usr/lpp/cicsts Changes the permission settings for the /usr/lpp/cicsts directory to: Installation Instructions 31

38 Notes: Owner=RWX Group=RWX Other=R-X (In octal form: 775) Where: R equates to Read W equates to Write X equates to Execute - equates to no permission 1. DFHIHFS0 only ever needs to be run once. 2. RACF ALTER ACCESS to the zfs data sets must be granted before running this DFHIHFS0. 3. The /usr/lpp/cicsts directory contains only directories, each being a mount point. 4. CICS requires the MOUNT issued by DFHIHFS0 to access files stored in the zfs, but the MOUNT command is lost when you re-ipl MVS. SDFHINST member DFHBPXP0 contains a MOUNT command for /usr/lpp/cicsts. Copy this command into a BPXPRMxx member of the SYS1.PARMLIB data set to ensure the mount is restored when MVS is IPLed. 5. All steps of DFHIHFS0 must end with return code zero for the job to be successful The DFHIHFS1 Job: creates a release specific zfs mounted in /usr/lpp/cicsts for this release of CICS. It Unmounts the zfs at directory /usr/lpp/cicsts/ussdir to allow the job to be rerun, and if necessary forces return code zero. Deletes from /usr/lpp/cicsts the directory defined by the ussdir parameter. This is to allow the job to rerun, and if necessary forces return code zero. Deletes the zfs specified in variable to allow the job to rerun, and if necessary forces return code zero. Creates the zfs specified by variable Creates the ussdir directory at /usr/lpp/cicsts, where ussdir is the name of the directory specified on the ussdir parameter. Mounts the zfs at directory /usr/lpp/cicsts/ussdir Changes the permission settings for the ussdir directory to 775. All steps of DFHIHFS1 must end with return code zero for the job to be successful. 32 CICS TS VUE V5.1 Program Directory

39 CICS requires the MOUNT issued by DFHIHFS1 to access files stored in the zfs, but the MOUNT command is lost when you re-ipl MVS. SDFHINST member DFHBPXP1 contains a MOUNT command for /usr/lpp/cicsts/ussdir. Copy this command into a BPXPRMxx member of the SYS1.PARMLIB dataset to ensure the mount is restored when MVS is IPLed The DFHISMKD Job: This job creates the directories in zfs. The highest expected return code is The DFHALLOC Job: This job allocates and catalogs CICS Transaction Server distribution and target libraries. To ensure that this job can be rerun, it deletes (and uncatalogs) the data sets that are allocated in the second step of the job. If the DFHALLOC job terminates abnormally, examine the job log to determine the cause, correct the problem, then rerun the job. The highest expected return code is The DFHSMPSU Job: This job sets up the SMP/E zones. Note : Only run this job if you are installing CICS Transaction Server into its own zone. Edit and submit the sample job DFHSMPSU to set up the zones for CICS Transaction Server. Consult the instructions in the sample job for more information. The highest expected return code is The DFHDDDEF Job: This job creates DDDEF entries for the SMP/E target, and distribution zones. If the DFHDDDEF job terminates abnormally, examine the job log to determine the cause, correct the problem, then re-run DFHDDDEF The highest expected return code is 0, if you install into new zones and 8 if you are installing into existing zones. Before you run the DFHDDDEF job If you have a DB2 SDSNLOAD library on your system, with the dataset name. If you do not have DB2 on your system, with the name of the SDFHLOAD dataset for this install, which contains a DB2 stub. Installation Instructions 33