AllFusion Gen. Installation Guide for Host Encyclopedia and Host Construction. r7.6

Transcription

1 AllFusion Gen Installation Guide for Host Encyclopedia and Host Construction r7.6

2 This documentation (the Documentation ) and related computer software program (the Software ) (hereinafter collectively referred to as the Product ) is for the end user s informational purposes only and is subject to change or withdrawal by CA at any time. This Product may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Product is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the Software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the Software are permitted to have access to such copies. The right to print copies of the Documentation and to make a copy of the Software is limited to the period during which the license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user s responsibility to certify in writing to CA that all copies and partial copies of the Product have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS PRODUCT AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS PRODUCT, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of this Product and any product referenced in the Documentation is governed by the end user s applicable license agreement. The manufacturer of this Product is CA. This Product is provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (c)(1)(ii), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2007 CA. All rights reserved.

3 Contents Chapter 1: Installation Overview Runtime Changes Install Prerequisites Installation Process Overview Chapter 2: Preparing to Install Installation Process Overview Reviewing Cover Letters and PMLs CA Common Services Technical Requirements Site Variables Worksheets AllFusion Gen Library Name Variables JCL Variables Encyclopedia Variables DB2 Database Variables COBOL Compiler Variables DB2 Subsystem Variables Datacom Subsystem Variables CICS Variables IMS Variables RPROF Variables Master Checklist AllFusion Gen Requirements AllFusion Gen Optional Requirements Required for Host Construction Facility Chapter 3: Building Software Libraries Uploading and Installing Establish ISPF Library Concatenation ISPLLIB or STEPLIB LIBDEF Procedure Establish Access to AllFusion Gen Contents iii

4 Other ISPF Considerations Evaluate Return Codes Chapter 4: Establishing the Environment Prerequisites Define Installation Variables Using Saved Parameters to Configure the Environment TILPARMS Modifying TILPARMS TILTAB How Space Parameters Are Created Origins of TILTAB How TILTAB50 Is Used Effect of a Missing TILTAB Relationship between TILTAB50 and TILPARMS Tasks to Define Installation Variables Start the CEINSTAL Dialog Set Library Names Edit Job Cards Set JCL Variables Set Encyclopedia Variables Define Regional Settings Set DB2 Variables Assign Storage Group Names Assign VSAM Names Set Target System Variables Verify Installation Variables Save Installation Variables Display System Information Build CLISTs Build Sample Utility JCL Create a DB2 PLAN_TABLE (Optional) Encyclopedia Number for Multiple Encyclopedias Where Do You Go From Here? iv Installation Guide for Host Encyclopedia and Host Construction

5 Chapter 5: Creating a New Encyclopedia Prerequisites Build SQL and JCL Run Jobs to Create the Encyclopedia Test Encyclopedia Functions RUNSTATS, Rebind AllFusion Gen Packages and Image Copy Package Bind CEJOB07A BINDPACK CEJOB07B BINDPLAN Enable User Access Where Do You Go From Here? Chapter 6: Upgrading an Encyclopedia in Place Prerequisites Considerations Build SQL and JCL Schema Release Levels Transition Guidelines Model Conversion Cross-Model Functionality Dynamic Program Call Compatibility Feature Run Upgrade Jobs Enable User Access Where Do You Go From Here? Chapter 7: Populating a Host Encyclopedia Copying Data to a Host Encyclopedia Prerequisites Build JCL and SQL Unload and Load Enable User Access Display License Information Copying Models to a Host Encyclopedia Download/Upload Method Cross-Copying Models Example Example Where Do You Go From Here? Contents v

6 Chapter 8: Installing the z/os API Preparing for Installation Upload and Install the API Appendix A: Sizing an Encyclopedia DASD Requirements... A-1 Sizing an Encyclopedia... A-2 AllFusion Gen Encyclopedias... A-2 How to Estimate Larger Encyclopedia Sizes... A-2 How to Create Storage Group Parameters... A-9 How to Create VSAM Parameters... A-9 Appendix B: Configuring IMS and CICS Runtime DLLs and LE... B-1 AllFusion Gen requires PDSE... B-2 Threadsafe... B-2 Install Gen Runtime Load Library Modules... B-4 Execution Load Library: IMS... B-4 Execution Load Library: CICS... B-4 Define IMS Block Mode Applications... B-5 Define APPLCTN and TRANSACT Macros... B-5 Define PSBs... B-6 Activate a PSB for MPP Processing... B-6 Define CICS Block Mode Applications... B-7 Define User Transactions... B-7 Define User Load Modules... B-8 Map Transactions to DB2 Plans... B-8 Enable XCTL... B-8 Enable Error Messages... B-9 Establish Client/Server Support... B-9 Customize Code Page Translation... B-9 Define Server Transactions and Programs... B-10 Customize Middleware... B-12 Establish Communications Support... B-12 Customize for LU B-13 Customize for TCP/IP... B-15 Debugging TICONMGR... B-21 Customize for MQSeries... B-24 Customize for ECI... B-27 vi Installation Guide for Host Encyclopedia and Host Construction

7 Debugging Applications...B-29 Diagram Trace Facility...B-29 Debugging Dynamic Runtime...B-30 TIRCRUNC...B-30 TIRCRUNI...B-31 Appendix C: Using Encyclopedia Exits Types of Exits... C-1 Common Encyclopedia Exits... C-2 TICINSTX... C-2 TICJCLX, TICGENB2, TICGENB4 and TIRGENB2... C-2 DB2 Secondary Authorization IDs... C-4 TICINSTX... C-4 TICGENB2 and TIRGENB2 Skeletons... C-6 TICGENB4... C-7 TICJCLX... C-7 TICEXBPK... C-8 TICEXBPL... C-9 Appendix D: Setting Model Code Pages Customizing Code Page Translation...D-2 Customizing the Code Page Translation Table for Your Environment...D-3 MKCRUN JCL...D-4 Code Page Translation Tables...D-5 Index Contents vii

8

9 Chapter 1: Installation Overview AllFusion Gen supports model-based development of application solutions. The Host Encyclopedia is the repository for information captured by the AllFusion Gen workstation toolsets. It may also serve as a central repository, which is networked with one or more client/server encyclopedias. The Host Encyclopedia contains tools for managing, distributing, merging and controlling versioning and access to the business models. The Host Construction enables code generation and installation for block mode or batch applications, or server modules that run on the z/os environment. If you are installing the Host Encyclopedia and Host Construction, you should have a working knowledge of z/os, DB2, ISPF and JCL. You may also need the knowledge of CICS, Datacom or IMS if you select either of these environments as an AllFusion Gen target. The following guides may also help you understand and use the Host Encyclopedia: Release Summary Block Mode Design Guide Encyclopedia API Host Encyclopedia Construction Guide Host Encyclopedia Guide Host Encyclopedia Public Interface Host Encyclopedia Subsetting Guide Host Encyclopedia Version Control Runtime Changes The z/os runtime has changed considerably in the last two releases of AllFusion Gen. AllFusion Gen r7.6 z/os runtime is LE conformant; it uses standard LE call interface routines, is fully re-entrant and threadsafe. These runtimes were changed to exploit LE storage management within the assembler routines, eliminating the need for frequent calling of GETMAIN and FREEMAIN. Most of the runtime routines are now implemented as DLLs, so a single copy is shared by multiple AllFusion Gen applications. Chapter 1: Installation Overview 1 1

10 Install Prerequisites These changes pertain more to the AllFusion Gen runtimes. For more information, see Host Encyclopedia Construction Guide. The TSOAE environment used by the z/os IT and the Application Test Facility is now a 31-bit, LE compliant application. The use of 24-bit storage was changed to be limited to those TSO and I/O functions that require being addressed below the 16-MB line. This version of TSOAE provides virtual storage constraint relief for testing and implementing large AllFusion Gen applications within TSO and batch. Install Prerequisites Before installing AllFusion Gen, make sure you have fulfilled the following prerequisites: Verified all the required operating system components are installed. For more information, see the Technical Requirements document on the CA support website. Identified an individual who has the technical skill and authority to install DB2 and ISPF applications. Identified a distinct DB2 authorization ID for AllFusion Gen. Identified the TSO environment settings required for access to AllFusion Gen. Identified the ISPF changes required for AllFusion Gen. It is recommended that you check with IBM regarding the support of DB2 releases. Note: The terms COBOL, COBOL/390 and COBOL for z/os all refer to the version of COBOL specified in the AllFusion Gen Technical Requirements document. 1 2 Installation Guide for Host Encyclopedia and Host Construction

11 Installation Process Overview Installation Process Overview Installing and populating the Host Encyclopedia is a multi-step process. The process begins with reviewing the installation materials, installing CA License Management Program (LMP) keys, and unloading JCL. The install process ends with running a test to ensure all Host Encyclopedia components are installed properly. The basic steps for installing the encyclopedia are: 1. Installation Prerequisites a. Review the installation package cover letter and any Product Maintenance Letters (PML) included with the installation package for pertinent installation information. b. Fulfill installation prerequisites and fill in worksheet information. c. Add the CA LMP execution keys to CAIRIM. See CA Common Services in Preparing to Install in this guide. 2. Upload and Install from CD or zip file The first step in installing the AllFusion Gen Host Encyclopedia is to move the relevant software and data from the delivery media onto the host. For a detailed explanation of these steps, see the chapter, Building Software Libraries in this guide. 3. Establish ISPF concatenation for the Host Encyclopedia. 4. Install and Configure After the libraries are allocated and the software copied, perform the following tasks: a. Run the CEINSTAL dialog. b. Run the batch jobs generated by the CEINSTAL dialog. Chapter 1: Installation Overview 1 3

12 Installation Process Overview 5. Create and Populate the Encyclopedia There are two ways to create and populate an AllFusion Gen Encyclopedia: a. Upgrade an Encyclopedia. When you upgrade an Encyclopedia, you perform all the necessary conversions and updates that are required to bring the existing information forward into the new release of the Encyclopedia. (For complete instructions, see Upgrading an Encyclopedia in Place. ) b. Create and Populate a New Encyclopedia. If you choose to create a new Encyclopedia and populate with either existing or new data, you perform the following steps: 1. Fulfill the prerequisites, then build SQL and JCL. 2. Run the installation jobs, then test the new Encyclopedia. 3. Execute RUNSTATS, copy, and rebind the AllFusion Gen plans. For complete instructions, see Creating a New Encyclopedia. Populate the Encyclopedia using one or more of the following methods (see Populating a Host Encyclopedia ): 1. Copy data tables from an existing Encyclopedia to the new Encyclopedia. 2. Copy models from an old Encyclopedia to a new Encyclopedia. 3. Upload new models created in the Toolset. 6. Configure Host Construction Environment If you use the Host Construction option to generate and install applications for IMS or CICS, follow the instructions in the appendix, Configuring IMS and CICS. 1 4 Installation Guide for Host Encyclopedia and Host Construction

13 Chapter 2: Preparing to Install Installation Process Overview The best way to ensure a successful installation is to prepare effectively. Preparing the host environment with the CA Common Services software, fulfilling the technical requirements and completing the checklists and worksheets in this chapter will prepare you for a successful installation. Reviewing Cover Letters and PMLs Review cover letters and Product Maintenance Letters (PMLs) in your AllFusion Gen installation package before initiating the installation process. These letters contain additional information not found in this guide. Important! If the cover letter or PML s instructions conflict with this guide, use the instructions in the PML. CA Common Services The CA Common Services media and its installation is described in the CA Common Services Getting Started guide. Note: Release requirements for CA Common Services become dated or obsolete. CA recommends staying current with your CA Common Services maintenance. Chapter 2: Preparing to Install 2 1

14 Installation Process Overview The following table explains the CA Common Services: Service CAIRIM (Resource Initialization Manager) CA LMP (License Management Program) CAISSF (Standard Security Facility) CA-C Runtime CAICCI (Common Communication Interfaces) CAIENF (Event Notification Facility) Description Eliminates the need for user SVCs and other installation requirements commonly encountered when installing systems software by providing a common driver for a collection of dynamic initialization routines. Automated software tracking and validation service. Required by all CA products. CA LMP is a subcomponent of and is installed with CAIRIM. Allows CA solutions to offer standardized security interfaces without regard for the particular needs of underlying access control software. CAISSF invokes AllFusion Gen security features. CAISSF is a subcomponent of and is installed with CAIRIM. CA-C is the C language runtime engine for C language-based solutions. Allows software solutions to work together across platforms, making the software more powerful. Insulates software solutions from changes in the operating system and environment. Since other CA products also require various CA Common Services, the components you need for AllFusion Gen may be installed at your site. Check with your systems group. 2 2 Installation Guide for Host Encyclopedia and Host Construction

15 Installation Process Overview CA LMP Keys AllFusion Gen Host Encyclopedia requires CA LMP keys. CA LMP keys are valid across product releases but not across CPUs. If you are running a prior release of the products and you are installing it on the same CPU, you can skip this section. If you are installing a new product, or you are installing on a different CPU, you must install CA LMP keys. Examine the CA LMP Key Certificates you received with your installation package. You should have a key certificate for every product you are installing that requires one. Fields Product Name Supplement Expiration Date Technical Contact MIS Director CPU Location Execution Key Product Code CPU ID Descriptions The trademarked or registered name of the CA product licensed for the designated site and CPUs. The reference number of your license for the particular product, in the format nnnnnn-nnn. This format differs slightly inside and outside North America. In rare situations, it may not be provided. The date (MONTH dd, yyyy as in January 15, 2005) your license for the product expires. The name of the technical contact at your site that is responsible for the installation and maintenance of the designated product. CA addresses all CA LMP correspondence to this person. The name of the director of MIS, or the person who performs that function at the site. If the title but not the individual s name is indicated on the Certificate, supply the actual name when correcting and verifying the certificate. The address of the building where the CPU is installed. An encrypted code required by CA LMP for product initialization. During the installation, it is referred to as the LMP code. A two-character code corresponding to this particular product. The code identifying the specific CPU for which installation of your product is valid. If your site is already running software from CA, your systems group probably is already running a CAS9 proc (cataloged procedure). If so, add the CA LMP keys for the products you are installing to the CA LMP keys already being used. Chapter 2: Preparing to Install 2 3

16 Installation Process Overview The CAS9 proc runs the CAIRIM program which uses a KEYS DD statement. The KEYS DD statement should point to your CA LMP keys. The KEYS DD statement usually points to a member named KEYS in a PARMLIB or OPTLIB. Each line contains the information from one key certificate. If the information does not fit on one line, code a hyphen in column 72 for a continuation character. The parameter structure for member KEYS is shown next: PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss) LMPCODE(kkkkkkkkkkkkkkk) Note: The parentheses in the parameter list are required. Parameter pp ddmmmyyy tttt-mmmm ssssss kkkkkkkkkkkkk kk Definition Required. The two-character product code. For any given CA LMP software solution, this code agrees with the product code already in use by the CAIRIM initialization parameter for earlier releases of the product. The CA LMP licensing agreement expiration date. Required. The CPU type and model on which the CA LMP software solution is to run. If the CPU type or the model require less than four characters, insert blank spaces for the unused characters. Required. The serial number of the CPU on which the CA LMP software solution is run. Required. The execution key is provided on the Key Certificate shipped with each CA LMP software solution. This is an example of a control card for the CA LMP execution software parameter: PROD(BD) DATE(15JAN02) CPU( /370623) LMPCODE(52H2K06130Z7RZ6) Note: This is an example only, the CA LMP execution key is invalid. For more information about CA LMP execution key definition, see the CA Common Services Getting Started. 2 4 Installation Guide for Host Encyclopedia and Host Construction

17 Site Variables Worksheets Technical Requirements Before you install AllFusion Gen, you must fulfill all of the pertinent technical requirements listed in the Technical Requirements document on the support website. To avoid potential problems, be sure to review this document carefully and verify that all system requirements have been met. Site Variables Worksheets You need all of the information on the following worksheets during software installation. Most of this information requires system knowledge and some insight into where your company is going in the future with regard to capacity, growth, application usage, distribution, deployment and volume. AllFusion Gen Library Name Variables The following table describes the AllFusion Gen library name variables. AllFusion Gen Library Name Variables Data set prefix Default: CA.MVSHE Load library suffix Default: LOAD* DBRM library suffix Default: DBRM SQL library suffix Default: SQL EGEN library suffix Default: EGEN Description All AllFusion Gen libraries must share the same prefix. The prefix can be one or more nodes, but the total length of a data set name (prefix plus suffix) cannot exceed 44 characters. Library containing AllFusion Gen executables and runtime modules. Library containing AllFusion Gen DBRMs. (DBRMs that correspond to the modules linked into AllFusion Gen executables.) CEINSTAL generates the SQL necessary to install AllFusion Gen. The SQL is placed in this library. Contains schema load files. User Notes Must be of DSNTYPE=LIBRARY Chapter 2: Preparing to Install 2 5

18 Site Variables Worksheets AllFusion Gen Library Name Variables TRAN library suffix Default: TRAN JCL library suffix Default: JCL CLIST library suffix Default: CLIST Panel library suffix Default: PLIB Message library suffix Default: MLIB Skeleton library suffix Default: SLIB Table library suffix Default: TLIB X-Late library suffix Default: IEFXLATE SAMPLIB LOADTRCE* Description Location of transaction files for models shipped with AllFusion Gen. CEINSTAL generates the JCL necessary to install AllFusion Gen. The JCL is placed in this library. Library containing AllFusion Gen FB CLISTs and REXX commands. CLISTs generated by CEINSTAL are created in this library. Library containing the AllFusion Gen ISPF panels. Library containing the AllFusion Gen ISPF messages. Library containing the AllFusion Gen ISPF skeletons. Library containing the AllFusion Gen ISPF tables. Library containing the AllFusion Gen translate (international) tables. Library containing samples such as customer exits and source code. Library containing debug versions of dynamic runtime TIRCRUNC and TIRCRUNI. This runtime is used to produce debug information for NLS cooperative processing. User Notes Must be of DSNTYPE=LIBRARY Note: * - Ensure the data sets are allocated as PDSE (DSNType = LIBRARY) data sets. 2 6 Installation Guide for Host Encyclopedia and Host Construction

19 Site Variables Worksheets JCL Variables The following table describes the JCL variables. JCL Variables Description User Notes Jobcard No default TSOID of installer No Default Disk unit Default: SYSDA Tape unit Default: 3480 SYSOUT class Default: * DB2 STEPLIBs No default z/os STEPLIBs No default Job card included in the generated JCL to perform various installation tasks. Used to prefix the names of the temporary data sets built and used during installation Disk unit used in the generated JCL to perform various installation tasks. Tape unit used in the generated JCL to perform various installation tasks. SYSOUT class used in the generated JCL to perform various installation tasks. If specified, these libraries are included in a STEPLIB in the generated JCL to perform various installation tasks. If your site has included the DB2 libraries in the system LINKLIST, do not specify them in a STEPLIB. If specified, this library is included in a STEPLIB in the generated JCL to perform various installation tasks. If your site has included the z/os runtime libraries in the system LINKLIST, do not specify a STEPLIB. Used in several places Chapter 2: Preparing to Install 2 7

20 Site Variables Worksheets Encyclopedia Variables The following table describes the encyclopedia variables. Encyclopedia Variables Description User Notes Site name Default: YOUR_COMPANY_NAME Encyclopedia name Default: HOST01 Install Construction Default: Y Administrator TSOID Default: TSO user ID Administrator Name Default: This field is for information purposes only. This is the name of the encyclopedia. It must be a unique value to prevent cross encyclopedia enqueues. This field is used to determine if Construction is installed. Identifies person doing the install. This field is for information purposes only. System Administrator PLAN Prefix Default: HEPL (4 byte limit) Schema Identifier Mandatory value: 9.1.A5 User data set UNIT type Default: SYSDA User data set prefix Default: &SYSPREF Encyclopedia number AllFusion Gen DB2 plan names are prefixed by this field. Plan prefixes make plan names unique in a DB2 subsystem, allowing different versions of AllFusion Gen software to run against the same AllFusion Gen database. This field identifies the schema. Do not change this value. All user data sets created by AllFusion Gen are allocated using this unit. All user data sets created by AllFusion Gen are prefixed by this field, for example standard error, standard out. Required if using multiple encyclopedias. For more information on setting encyclopedia variables, see Establishing the Environment. 2 8 Installation Guide for Host Encyclopedia and Host Construction

21 Site Variables Worksheets DB2 Database Variables The following table describes the DB2 database variables. DB2 Database Variables Description User Notes Collection ID Default: DBCOLLID DB2 subsystem ID Default: DSN Explicit creator ID No default Secondary authorization ID No default Schema DB name Default: HOSTS Data DB name Default: HOSTD Public Interface DB name Default: HOSTP Data set storage type Default: S DB2 collection ID used in bind processing. Identifier of the DB2 subsystem. If specified, encyclopedia tables and indexes are qualified using this ID. Explicit creator ID and secondary authorization ID are mutually exclusive. If specified, current SQLID is set to this ID before the encyclopedia tables and indexes are defined. Secondary authorization ID and explicit creator ID are mutually exclusive. Name of the schema database. Name of the encyclopedia database. Name of the public interface database. Space for AllFusion Gen database can be allocated using storage groups or VSAM data sets: S storage group allocation V VSAM allocation. Encyclopedia Initial size Default: S S small M medium Chapter 2: Preparing to Install 2 9

22 Site Variables Worksheets DB2 Database Variables Description User Notes Secondary storage factor Default: 0 Storage Group Names No default VSAM Volume Names No default Defines secondary space allocation in relation to primary allocation. (0 to 1.0 times primary allocation.) If you select storage group space allocation, you must know the names of the groups you want to use. If you select VSAM space allocation, you must specify the volume names for VSAM data sets. COBOL Compiler Variables The following table describes the COBOL compiler variables. COBOL Compiler Variables Description User Notes Compiler name Default: IGYCRCTL Size parameter No default Compiler load library Default: IGY.SIGYCOMP Compiler lib in linklist? Default: N Compiler Static runtime library Default: CEE.SCEELKED Compiler Dynamic runtime library Default: CEE.SCEERUN SCEERUN library in linklist Default: N Name of the COBOL compiler. Amount of space for the compiler SIZE parameter; can be specified in kilobytes (for example, 4096 KB), bytes (for example, ), or as MAX. Name of the library containing the compiler used by the environment and various support modules for COBOL. Flag indicating whether the compiler library is defined in the system linklist. Name of library containing static runtime modules for COBOL. Name of library containing z/os LE dynamic runtime modules. Flag indicating whether this library is in the linklist Installation Guide for Host Encyclopedia and Host Construction

23 Site Variables Worksheets DB2 Subsystem Variables The following table describes the DB2 subsystem variables. DB2 Subsystem Variables Description User Notes DB2 precompiler name Default: DSNHPC DB2 link library Default: DB2.SDSNLOAD Link lib in linklist? Default: N Name of the DB2 compiler. Name of the DB2 link library containing the DB2 precompiler and various support modules. Flag indicating if the DB2 link library is defined in the system linklist. Datacom Subsystem Variables The following table describes the Datacom subsystem variables. Datacom Subsystem Variables Datacom preprocessor name Default: DBXMMPR Datacom MUF name Default: DCMMUF Datacom libraries Defaults: CAI.DCM.CUSLIB CAI.DCM.CAILIB Datacom CICS libraries. Defaults: CAI.DCM.CICS.CUSLIB CAI.DCM.CICS.CAILIB Description Name of the Datacom preprocessor. Name of the Datacom MUF. This name must be specified by the customers. Name of the Datacom CUSLIB and CAILIB data sets. These libraries contain the Datacom preprocessor, customized modules, and various support modules. Name of the Datacom libraries containing CICS support modules. Note: Each Datacom z/os subsystem can have a maximum of twenty (20) Datacom MUF names (and associated load data sets). Each MUF name must have four (4) data sets associated with it. User Notes Chapter 2: Preparing to Install 2 11

24 Site Variables Worksheets CICS Variables The following table describes the CICS variables. CICS Variables Description User Notes CICS load library Default: CICS.SDFHLOAD z/os static link library Default: CEE.SCEELKED CICS Flag Default: N Name of CICS load library. z/os static link library. Flag indicating if the CICS system targeted to run AllFusion Gen applications runs on the same CPU as AllFusion Gen. This variable is only used by applications targeting DB2 to decide where and when the DB2 BIND is done. Y-- BIND can be performed by the Host Encyclopedia. N-- You must do a manual BIND on the other CPU. IMS Variables The following table describes the IMS variables. IMS Variables Description User Notes IMS resident load library Default: IMS.RESLIB Maximum segment size Default: 1280 Load library containing IMS modules. Maximum segment size of IMS messages Installation Guide for Host Encyclopedia and Host Construction

25 Site Variables Worksheets IMS Variables Description User Notes IMS shares CPU with this TSO? Default: N Indicates if the IMS system targeted to run AllFusion Gen applications runs on the same CPU as the Host Encyclopedia. This variable is only used by applications targeting DB2 to decide where and when the DB2 BIND is done. Y BIND can be performed by the Host Encyclopedia. N You must do a manual BIND on the other CPU. CPIC Interface Load Lib Name of the system library that contains the CPIC interface modules. Usually this library is SYS1.CSSLIB (a required z/os data set). RPROF Variables The following table describes the RPROF variables. RPROF Variables Description User Notes DB2 subsystem Default: DB2 Explicit creator ID No default Secondary authorization ID No default DB2 subsystem identifier of the subsystem where you want to create an RPROF table. If specified, RPROF table and index are qualified using this ID. Explicit creator ID and secondary authorization ID are mutually exclusive. If specified, the current SQLID is set to this ID before RPROF table and index are defined. Secondary authorization and explicit creator ID are mutually exclusive. DB name Default: RPROF Name of the database in which the RPROF table is to be built. Chapter 2: Preparing to Install 2 13

26 Site Variables Worksheets RPROF Variables Description User Notes Storage Type Default: S VCAT No default Volume No default RPROF initial size Default: KB pages (VSAM), KB pages (storage group) RPROF Secondary size Default: 0 RPROFI1 Initial size Default: KB pages (VSAM), KB pages (storage group) RPROFI1 Secondary size Default: 0 Space for the RPROF database is allocated using storage groups or VSAM data sets. S storage group allocation V VSAM allocation. If you select VSAM as the type of database storage, you must specify the VCAT name to be used when creating the VSAM data sets. If you select VSAM space allocation, you must specify the volume names when creating the VSAM data sets. Primary size of tablespace that contains the RPROF table. Secondary space allocation of tablespace containing the RPROF table. Primary size of RPROF index. Secondary space allocation of RPROF index Installation Guide for Host Encyclopedia and Host Construction

27 Master Checklist Master Checklist This list identifies the hardware and software that must be in place in your environment before installing AllFusion Gen Host Encyclopedia and Host Construction Toolset. For further details of the required items, see the AllFusion Gen Technical Requirements document available on the CA support website: ca.com. From the main menu, select Gen as your product. The document is under Product Information. All required items on the Master Checklist must be complete before installing AllFusion Gen. AllFusion Gen Requirements The following tasks are to be checked for before installing the AllFusion Gen Host Encyclopedia and Host Construction Toolset. All operating system prerequisites are satisfied. DASD requirements are satisfied. DB2 Program Temporary Fixes (PTFs) are applied to DB2. AllFusion Gen Encyclopedia Parameters are captured. AllFusion Gen Optional Requirements Workstation-to-mainframe communications. Required for Host Construction Facility These requirements are needed only if you are installing Host Construction. Check the IMS or the CICS box or both. IMS environment requirements are satisfied. CICS environment requirements are satisfied. COBOL requirements must be satisfied before source code can be compiled. AllFusion Gen Host Construction parameters are captured. Chapter 2: Preparing to Install 2 15

28

29 Chapter 3: Building Software Libraries This chapter explains how to unload the software used to build and run the programs that install the AllFusion Gen Host Encyclopedia. The z/os Host Encyclopedia software is delivered in a zip file on a Windows compatible CD. Important! The IBM utility TRSMAIN (also referred to as the TERSE utility by IBM) is required to install all CA AllFusion Gen products and PTFs. If your site has this utility available, copy it into the AllFusion Gen LOAD data set. If your site does not have this utility, use the following URL address to obtain the TRSMAIN (TERSE) utility, and then copy it into the AllFusion Gen LOAD data set. The TRSMAIN/TERSE is a free/copyrighted IBM utility and thus, cannot be redistributed. The utility can only be downloaded from IBM by each individual customer. Uploading and Installing The steps you need to complete for installing the software libraries are listed next. This installation assumes you are using a Windows compatible Workstation. Workstation directories and z/os data set prefixes are provided as examples. For more information on how to complete these steps, see the chapter "Preparing to Install. 1. Obtain the AllFusion Gen Encyclopedia Server Option for z/os r7.6 Installation CD. The CD contains a zip file named GenHEr76.zip. 2. Expand the zip file from the CD onto the Workstation. Copy the GenHEr76.zip file from the CD onto the Workstation. Extract the contents of the file to: C:\genhe\GenHEr76.ctl (Install-Control) C:\genhe\GenHEr76.mvs (Install-File) C:\genhe\GenHEr76.txt (Install Readme file) Chapter 3: Building Software Libraries 3 1

30 Uploading and Installing 3. Allocate INSTJCL file on TSO. Allocate installation JCL data sets on z/os as follows: Data set name : cai.mvshe.instjcl LRECL = 80 DSORG = PO RECFM = FB 4. Transfer the Install Control File from the Workstation to z/os. Transfer the Install Control File, in BINARY, from the Workstation to z/os. The GenHEr76.ctl file needs to be transferred from c:\genhe to cai.mvshe.instjcl(heinst0). 5. Customize JCL HEINST0. Add Jobcard and customize the JCL cai.mvshe.instjcl(heinst0) (See instructions inside JCL). Submit the JCL member HEINST0 to create the following three new JCL members: 'cai.mvshe.instjcl(heinst1)' 'cai.mvshe.instjcl(heinst2)' 'cai.mvshe.instjcl(heinst3)' This job should end with a COND CODE =0 6. Customize JCL HEINST1. Add Jobcard and customize JCL cai.mvshe.instjcl(heinst1) (See instructions inside JCL). Submit the JCL member HEINST1 to allocate z/os data set : cai.mvshe.instfile This job should end with a COND CODE =0 7. Transfer Install File from the Workstation to z/os Transfer (ftp) the Install-File, in BINARY, from the Workstation to z/os. The GenHEr76.mvs file needs to be transferred from C:\genhe to 'cai.mvshe.instfile'. 8. Expand the INSTFILE data set into a PDS. Add jobcard and customize JCL cai.mvshe.instjcl(heinst2) (See instructions inside JCL). Submit the JCL to Read as input : 'cai.mvshe.instfile' (A sequential data set) Write out: 'cai.mvshe.instpds'. (A partitioned data set) The job should end with a COND CODE = Installation Guide for Host Encyclopedia and Host Construction

31 Uploading and Installing 9. Expand the INSTPDS file members into z/os Data sets. Add jobcard and customize JCL cai.mvshe.instjcl(heinst3) (See instructions inside JCL). Submit JCL member HEINST3 to read each member of the cai.mvshe.instpds data set and create z/os AllFusion Gen installation data sets cai.mvshe.xxxxxx. This job should end with a COND CODE =0 Read as Input 'cai.mvshe.instpds(h#clistx)' 'cai.mvshe.instpds(h#dbrmxx)' 'cai.mvshe.instpds(h#egenxx)' 'cai.mvshe.instpds(h#jclxxx)' 'cai.mvshe.instpds(h#loadtr)' 'cai.mvshe.instpds(h#loadxx)' 'cai.mvshe.instpds(h#mlibxx)' 'cai.mvshe.instpds(h#plibxx)' 'cai.mvshe.instpds(h#ptfctl)' 'cai.mvshe.instpds(h#sampxx)' 'cai.mvshe.instpds(h#slibxx)' 'cai.mvshe.instpds(h#sqlxxx)' 'cai.mvshe.instpds(h#tlibxx)' 'cai.mvshe.instpds(h#tranxx)' 'cai.mvshe.instpds(h#xlatex)' Create AllFusion Gen Data set 'cai.mvshe.clist' 'cai.mvshe.dbrm' 'cai.mvshe.egen' 'cai.mvshe.jcl' 'cai.mvshe.loadtrce' 'cai.mvshe.load' 'cai.mvshe.mlib' 'cai.mvshe.plib' 'cai.mvshe.ptfcntl' 'cai.mvshe.samplib' 'cai.mvshe.slib' 'cai.mvshe.sql' 'cai.mvshe.tlib' 'cai.mvshe.tran' 'cai.mvshe.iefxlate' Note: All Gen LOAD data sets are installed as PDSE (DSNTYPE=LIBRARY) and must stay that way. Chapter 3: Building Software Libraries 3 3

32 Uploading and Installing This following table provides a comprehensive list of all AllFusion Gen JCL members and a brief description of the jobs they perform. These members are created during the installation and upgrade processes. JCL Member BIEFXCPY BLDRPROF Job Description Performs a batch cross-copy by executing CLISTs IEFDOWN and IEFUP. Builds RPROF tables and indexes. (Each DB2 subsystem used for applications generated by AllFusion Gen should have an RPROF table.) If a DB2 subsystem contains only CICS (that is, no IMS or TSO), you may consider using a TSQ RPROF instead. CEJOB02 CEJOB03 CEJOB04 CEJOB05 CAJOB05 CEJOB05A CEJOB06 CAJOB06 CEJOB07A CEJOB07B CEJOB08 CEJOB09 CEJOB10 CEJOB11 CEJOB12 CEJOB13 Allocates VSAM data sets for encyclopedia tables and indexes. (if VSAM data sets are allocated.) Executes a DB2 BIND for dynamic SQL processing program TIUUSQL by executing CLIST IEFBIND. Creates all DB2 objects for a new Host Encyclopedia. Loads the AllFusion Gen schema tables with meta-model data. Executes the IBM s DB2 Load utility. Performs the same task as CEJOB05 using CA s Fast Load utility. Relaxes schema migration rules. Executes the DB2 RUNSTATS utility for all Host Encyclopedia tables. Updates DB2 catalog statistics similar to CEJOB06 using CA s PDASTAT utility. Binds DBRMs into packages. Binds AllFusion Gen plans. Grants to PUBLIC, both DB2 EXECUTE authority on AllFusion Gen plans and DB2 SELECT authority on Public Interface table views. Updates the DMAX table for the AllFusion Gen schema. Loads the Schema Functions Model. Processes the Functions Model to extract information and load it to the schema tables. Loads the Gen Sample Model. Loads the Gen Help Model. 3 4 Installation Guide for Host Encyclopedia and Host Construction

33 Uploading and Installing JCL Member CEUCLEN CEUCOPY CAUCOPY CEUINCR CAUINCR CEUREOR CAUREOR CEUXPND CVJOB04A Job Description Runs a special version of the model delete function that deletes all objects not related to a model (orphan objects). Runs the DB2 COPY utility to take a full image-copy of Encyclopedia tablespaces. This job is also used to create a new Encyclopedia. This member was created as sample utility JCL. Runs the CA DB2 QUICK COPY utility to take a full image-copy of Encyclopedia tablespaces. This job is also used to create a new Encyclopedia. This member was created as sample utility JCL. Runs the DB2 COPY utility to take an incremental imagecopy of Encyclopedia tablespaces. Runs CA DB2 QUICK COPY utility to take an incremental image-copy of Encyclopedia tablespaces. Runs the DB2 REORG utility on tablespaces. Runs CA DB2 RAPID REORG utility on tablespaces. Expands table and indexspaces. Upgrades DB2 objects to AllFusion Gen r7.6 objects: Gen 6.5 to Gen r7.6 CVJOB04B Upgrades DB2 objects to AllFusion Gen r7.6 objects: Gen r7 to Gen r7.6 LAPPHELP CAPPHELP USERLIB Gen r7.5 to Gen r7.6 Runs IBM DB2 LOAD utility to load the application Help Model data. Runs CA DB2 Fast Load utility to load the application Help Model data. Allocates libraries used in testing Host Construction. Can also be used as a model for user allocation of construction libraries. For a list of the libraries allocated by USERLIB, see Testing Host Construction. Note: Any load library must be allocated as PDSE (DSNType = LIBRARY). Chapter 3: Building Software Libraries 3 5

34 Uploading and Installing If a DB2 subsystem contains only CICS (that is, no IMS or TSO), you may consider using a TSQ RPROF instead. You must have IBM utilities to execute the following jobs. CEJOB05 CEJOB06 CEUCOPY CEUREOR CEUINCR LAPPHELP If you are using utilities from other vendors, you must customize these jobs accordingly. You can also use the equivalent job that uses Unicenter DB2 products. You must have Unicenter DB2 products to execute the following jobs: CAJOB05 CAJOB06 CAUCOPY CAUREOR CAUINCR CAPPHELP You can use the equivalent job that uses IBM DB2 utilities. If you are using utilities from other vendors, you must customize these jobs accordingly. Establish ISPF Library Concatenation The ISPF environment must be established before AllFusion Gen can be used. The encyclopedia libraries can be allocated using a logon CLIST, a logon PROC, or the ISPF LIBDEF facility. In all cases, if the logon is used primarily for the encyclopedia, certain libraries must be first in the concatenation. Important! Do not include AllFusion Gen data sets from releases prior to r7.6 in the ISPF logon concatenation. Including data sets from releases prior to r7.6 may produce unpredictable results or cause errors to occur. 3 6 Installation Guide for Host Encyclopedia and Host Construction

35 Uploading and Installing ISPLLIB or STEPLIB A combination of ISPLLIB or STEPLIB can be used to allocate the required AllFusion Gen software libraries and the required z/os program product runtime libraries (such as LE, DB2, and ISPF). If DB2 or LE libraries are not in the linklist, allocate them through a STEPLIB DD or the ISPLLIB DD in the logon CLIST or in the TSO logon procedure. LIBDEF If you use the ISPF LIBDEF facility, note these restrictions: LIBDEF is not supported for the SYSPROC DD. Consequently, you must include the AllFusion Gen CLIST library in the SYSPROC concatenation of a logon CLIST or a TSO logon PROC. Do not use LIBDEF to allocate the required load libraries. AllFusion Gen programs make dynamic calls to LE runtime routines. Using LIBDEF to allocate ISPLLIB results in an S806 module not found abend. This is a limitation of ISPF LIBDEF. There are two CLIST exits for LIBDEF: TIELIBDF and TIELIBFR. TIELIBDF is called at the beginning of various AllFusion Gen functions. TIELIBDF dynamically allocates ISPPLIB, ISPMLIB, ISPTLIB, and ISPSLIB. TIELIBFR is called at the end of some Host Encyclopedia functions and can be used to free libraries allocated using LIBDEF. TIELIBDF and TIELIBFR contain examples of how to use LIBDEF to allocate and free libraries. Procedure 1. Allocate the following libraries: DDNAME Description AllFusion Gen Library Short Name SYSPROC CLIST libraries CLIST ISPPLIB ISPF Panel libraries PLIB ISPMLIB ISPF Message libraries MLIB ISPTLIB ISPF Table libraries TLIB ISPLLIB Load libraries LOAD Chapter 3: Building Software Libraries 3 7

36 Uploading and Installing DDNAME Description AllFusion Gen Library Short Name ISPPROF ISPF User Profile library (not applicable) ISPSLIB ISPF Skeleton libraries SLIB 2. Create and test the logon CLIST or PROC. (Contact the System Administrator if you need assistance for this step or the next step.) 3. If using LIBDEF, modify and test TIELIBDF. Establish Access to AllFusion Gen You must provide an ISPF entry point to AllFusion Gen by modifying an existing ISPF menu. The modified ISPF menu must provide an option that executes the CLIST TICPYRIT to display the CA AllFusion Gen copyright panel, for example, CMD (%TICPYRIT). Other ISPF Considerations Review the default flag in the TSO command table (ISPTCM) header to determine if the command processor entries for the following TSO commands must be added to the ISPTCM: TSOAE required by the TSO testing facility. EXECSQL (Optional) a dynamic SQL utility for diagnostics and problem correction. Most sites do not need to change these commands but, if you modify the ISPTCM defaults, you must add the commands shown. No modification is required if the default flag setting in the ISPTCM header is B...1. This indicates a BLDL is used to determine if a command processor or a CLIST is entered. If your ISPTCM table has a different setting in the header, add a command processor ENTRY for the TSOAE and EXECSQL commands. See the ISPF documentation for more information. Important! Insufficient available space in the ISPPROF profile data set can cause unpredictable results. 3 8 Installation Guide for Host Encyclopedia and Host Construction

37 Uploading and Installing Evaluate Return Codes During the installation process, you may see return codes of 0 and 4. These return codes do not adversely affect the installation process. If the return code is not 0 or 4, check your system output to ensure that the installation was successful. For example, CEJOB04 may return a code of 8 if the database already exists, but the rest of the job completes normally. In this case, you should check the DB2 SYSPRINT. (See the IBM documentation for additional information about return codes.) Return codes of 8, 12, and 16 may indicate problems with the installation. These return codes may indicate that: The data set is full. You are out of directory blocks in the load library. The block size of the load library is wrong. A file was defined improperly. The wrong attributes were defined. Chapter 3: Building Software Libraries 3 9

38

39 Chapter 4: Establishing the Environment Establishing a site-specific environment for AllFusion Gen requires six tasks. The tasks are: 1. Define the installation variables, or pre-populate the installation variables using an existing TILPARMS member. 2. Verify the installation variables. 3. Save the installation variables in TILPARMS, which is an external JCL library member. 4. Build the AllFusion Gen CLISTs. 5. Build sample utility JCL (Optional). 6. Create a DB2 PLAN_TABLE if one does not exist. This chapter explains how to complete each of these tasks. Prerequisites Before you proceed with setting up the environment, you should have completed the following tasks: 1. Read and completed the site variables worksheets. 2. Upload and Install from CD. 3. Established ISPF concatenation. Chapter 4: Establishing the Environment 4 1

40 Define Installation Variables Define Installation Variables The installation dialog CLIST named CEINSTAL specifies installation parameters. This CLIST modifies the installation jobs by substituting variable values specific to your site. The next time you start CEINSTAL, all your sitespecific variables are available. Note: Installation variables are saved in the ISPF profile pool and this pool is associated only with the TSO user ID executing CEINSTAL. When you build installation JCL and SQL, CEINSTAL uses the ISPF profile pool variables. You must use the same TSO user ID until the parameters are saved to the external JCL data set member TILPARMS. If there is an earlier version of the Host Encyclopedia software on your system you probably already have a TILPARMS. For instructions on how to use an existing TILPARMS member, see Using Saved Parameters to Configure the Environment. Using Saved Parameters to Configure the Environment The following sections explain how to use the saved parameters to configure the environment. TILPARMS The CEINSTAL dialog provides an option to save variables to an external data set: CAI.MVSHE.JCL(TILPARMS). If you are not installing the Host Encyclopedia for the first time, you probably already have a set of installation parameters defined in TILPARMS. These parameters can be retrieved, modified, and verified for the new installation. Modifying TILPARMS Use the following procedure to modify the parameters stored in an existing TILPARMS: 1. Copy the TILPARMS member into the JCL data set for the new installation. 2. Edit TILPARMS as follows: Locate the line that Change and verify the value to the right to 9.1.A5 to update the schema to AllFusion Gen r7.6. Locate the line that set prefix> and change the value of <data set prefix> to the new prefix used for AllFusion Gen r7.6. Note: If the CLIST suffix is different, change it now. 4 2 Installation Guide for Host Encyclopedia and Host Construction

41 Using Saved Parameters to Configure the Environment SASCI3 index was new for AllFusion Gen r7. Therefore, TILPARMS copied from an earlier Gen release will not have an entry for SASCI3. To ensure this index is created for r7.6, locate the line containing SASCI2, and then create a new entry SASCI3 below it as shown in the following example:... # SCHM I SASCI SASCI2 # SCHM I SASCI SASCI3 <-- New... The CICS Socket load library is not required to build generated applications so it has been removed. It is used by the AllFusion Gen runtimes and only included in the relevant DLL. Therefore, if a TILPARMS copied from an earlier Gen release contains an entry for the CICS Socket load library TCPIP.SEZATCP you can delete it. 3. Go to the AllFusion Gen Main Menu and type TSO %CEINSTAL on the command line. Then press Enter to display the Encyclopedia Maintenance Menu. 4. Select option 1 and press Enter to display the Installation Variables Management Menu. 5. Select option 1 and press Enter to display the Set Library Names screen. 6. Set the Data set Prefix to point to your new data sets on the Set Library Names screen. 7. Verify that the JCL library suffix is correct, then press F3 to return to the Installation Variables Management Menu. 8. You are now ready to read in the TILPARMS member that you edited. You do this by selecting option 12. Retrieve variables from external data set. 9. At this point, you should step through options 2 through 9 to accept (F2) and save (F6) the edits you made to TILPARMS. When you select option 7 or 8 (one or the other, depending on the type of storage you are using), you build the TILTAB50 table that is explained in TILTAB After you are satisfied that all your settings are correct, select option 10, Check variables, to verify the validity of the settings, then save the new settings (if you want to keep them) to TILPARMS by selecting option 11. Save variables to external data set. Chapter 4: Establishing the Environment 4 3

42 TILTAB50 TILTAB50 TILTAB50 is a TSO/ISPF table that stores space parameters used to create DB2 tables and indexes for Host Encyclopedia installation. How Space Parameters Are Created Values entered in three fields of the Set DB2 Variables screen are used to create space parameters. These fields are: Data set Storage Type Entering S in this field defines Storage Groups and opens the Assign Storage Group Names screen. Entering V in this field defines VSAM and opens the Assign VSAM Names screen. Encyclopedia Initial Size Secondary Storage Factor Storage Groups The parameters on the Assign Storage Group Names screen were created from the values entered in the following fields of the Set DB2 Variables screen: Data set Storage Type=S Encyclopedia Initial Size=S Secondary Storage Factor=0.5 VSAM The parameters on the Assign VSAM Names screen were created from the values entered in the following fields of the Set DB2 Variables screen. Data set Storage Type=V Encyclopedia Initial Size=S Secondary Storage Factor= Installation Guide for Host Encyclopedia and Host Construction

43 TILTAB50 Origins of TILTAB50 The default source values for TILTAB50 are stored in the AllFusion Gen skeleton library (SLIB) member TILTAB50. This default source TILTAB50 is not used in processing. Space parameters are stored in a new TILTAB50 table in the AllFusion Gen Table library (TLIB) member TILTAB50. If there is an existing TILTAB50 table, it is deleted. Important! If one of the sizing fields on the Set DB2 Variables screen is changed (Data set storage type, Encyclopedia initial size, or Secondary storage factor), TILTAB50 is reset to the new values based on the new input and on defaults stored in the skeleton library (SLIB). Any previously stored values are lost. Note: If you do not have the AllFusion Gen TLIB (table library) in your concatenation, TILTAB50 is not found resulting in a TABLE OPEN ERROR on the Installation Variables Management Menu. How TILTAB50 Is Used During the creation of installation JCL and SQL, the space parameters stored in TILTAB50 become input to CEJOB02 for VSAM and to SQL CRNEWSP and CRNEWIX (used by CEJOB04) for Storage Groups. A Sample DB2 DDL used to create AllFusion Gen DASC Table is shown next. CREATE TABLESPACE DASC IN GEN75D USING STOGROUP STO03 (STO03=Storage Group Table DASC) PRIQTY (Primary Space in 1K records) SECQTY 9600 (Secondary Space in 1K records) LOCKSIZE ANY SEGSIZE 64 A sample VSAM JCL of AllFusion Gen DASC Table is shown next. DEFINE CLUSTER + (NAME( AACC2.DSNDBC.GEN75.DASC.I0001.A001 ) + LINEAR + REUSE + VOL(BDS001) + (BDS001 is VSAM data set volume) RECORDS( ) + (4800=primary space in 4K pages) SHR(3.3) ) + (2400=secondary space in 4K pages) DATA + (NAME( AACC2.DSNDBD.GEN75D.DASC.I0001.A001 )) Chapter 4: Establishing the Environment 4 5

44 TILTAB50 Effect of a Missing TILTAB50 There must always be a TILTAB50 member in the TLIB library. If TILTAB50 is missing, variable checking will fail. A TILTAB50 table must be created before processing can continue. To create a new TILTAB50 table, open the Assign Storage Group Names screen or the Assign VSAM Names screen and press F2, F3, or F6. Relationship between TILTAB50 and TILPARMS All installation variables entered during the CEINSTAL dialog (through the options of the Installation Variables Management Menu), including those stored in the TILTAB50 table, can be saved for later retrieval. The saved variables are stored in a JCL library member named TILPARMS. For more information on how TILPARMS can be used to install variables or to restore variables to previously saved values, see TILPARMS. If you use the Retrieve Variables option on the Installation Variables Management Menu, all CEINSTAL variables stored in TILPARMS are retrieved. (Existing TILPARMS variables are overwritten.) If TILTAB50 does not exist, it is created (based on the values in TILPARMS) when you select option 7, Assign Storage Group name, or option 8, Assign VSAM names from the Installation Variables Management Menu. If TILTAB50 already exists, it is replaced when you select one of those two options. 4 6 Installation Guide for Host Encyclopedia and Host Construction

45 Tasks to Define Installation Variables Tasks to Define Installation Variables There are multiple subtasks within the task of defining installation variables. These subtasks are: 1. Start the CEINSTAL dialog. 2. Set library names. 3. Edit job cards. 4. Set JCL variables. 5. Set Encyclopedia variables. 6. Define regional settings. 7. Set DB2 variables. 8. Assign storage group names. 9. Assign VSAM names. 10. Set target system variables. Each of these subtasks is explained in the following sections. Start the CEINSTAL Dialog To begin the variable definition process, start the CEINSTAL dialog from the AllFusion Gen Main Menu, using the following procedure. 1. Log on to TSO/ISPF and the ISPF Main Menu appears. 2. Select AllFusion Gen and press Enter. The CA logo and copyright screen appears. 3. Press Enter to display the Main Menu. COMMAND == > Main Menu Select one of the options below, then press ENTER. 1. Host Encyclopedia functions 2. Public Interface functions 3. Host Encyclopedia reports 4. Application system functions 5. Environment specification F1=Help F3=Exit F12=Cancel Chapter 4: Establishing the Environment 4 7

46 Tasks to Define Installation Variables 4. Type TSO %CEINSTAL on the command line and press Enter. The Host Encyclopedia Maintenance Menu appears. Host Encyclopedia Maintenance Menu COMMAND == > Select one of the options below, and then press ENTER. 1. Installation Variables Management Menu 2. Build Encyclopedia Clists (TIUGLOB, TIRCFIGS, TIXGLOB) 3. Build Sample Encyclopedia Utility JCL 4. Build JCL/SQL for new Encyclopedia Installation 5. Build Unload/Load JCL to copy an existing Host Encyclopedia Data Tables to a new Host Encyclopedia 6. Build JCL/SQL to Upgrade In-Place an existing Host Encyclopedia to a new Host Encyclopedia F. Fix Management menu 5. Select option 1 and press Enter. The Installation Variables Management Menu displays, as follows. COMMAND== > Installation Variables Management Select options 1-9 in sequence, then check variables and save. 1. Set library names 2. Edit JOB cards 3. Set JCL variables 4. Set encyclopedia variables 5. Regional settings 6. Set DB2 variables 7. Assign Storage Group name 8. Assign VSAM names 9. Set target system variables 10. Check variables 11. Save variables to external dataset (JCL member TILPARMS) 12. Retrieve variables from external dataset (JCL member TILPARMS) 13. Clear variables from userid ISPF profile pool F1=Help F3=Exit Note: Options 7 and 8 on the Installation Variables Management Menu are mutually exclusive. Use this menu to define site-specific variables. Options 1 through 9 on this menu are explained as you complete the task of defining your site s variables. The next three tasks explain you learn how to verify and save variables (also driven by this menu). You build CLISTs next. 4 8 Installation Guide for Host Encyclopedia and Host Construction

47 Tasks to Define Installation Variables Function Keys The following function keys apply to CEINSTAL dialogs in which you can enter parameters. Note: Your ISPF profile session must be set to 24 PF-keys for these to work properly. Key F1 (Help) F2 (Accept) F3 (Exit) F6 (Save) F12 (Cancel) Function Displays Help for that screen Verifies the variables and saves them to the user s ISPF profile pool. The verification process may check if data sets exist or a DB2 subsystem exists and so on. If errors are found, messages are displayed on an Activity Display screen. Saves the information to the user s ISPF profile pool and exits the screen. Saves the information to the user s ISPF profile pool without exiting the screen. Exits the screen without making any changes to the ISPF profile pool. Set Library Names The library names created by the installation (from CD) must be the same as those displayed by CEINSTAL. The following procedure describes how to confirm that the library names match. 1. Select option 1 on the Installation Variables Management Menu and press Enter. The Set Library Names screen appears. Set library names COMMAND == > Enter or verify the software libraries dataset prefix and suffixes. Dataset prefix CAI.MVSHE Dataset suffixes: LOAD LOAD DBRM DBRM SQL SQL EGEN EGEN TRAN TRAN JCL JCL CLIST CLIST Panel PLIB Message MLIB Skeleton SLIB Table TLIB X-Late Tables IEFXLATE F1=Help F2=Accept F3=Exit F6=Save F12=Cancel Chapter 4: Establishing the Environment 4 9

48 Tasks to Define Installation Variables 2. Accept the defaults on the Set Library Names screen, or type new values to ensure the library references are the same names that were created by the installation (from CD). 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 4. When verification is complete, press Enter to exit the Activity Display screen. The Set Library Names screen appears. If verification fails, validate the library names and make sure they match the names created during install. 5. Press F3 to exit the screen. The Installation Variables Management Menu appears. AllFusion Gen installations are delivered with a fixed block CLIST library. A variable block CLIST library can be created by doing the following: 1. Install the fixed block CLIST library 2. Allocate a variable block CLIST library 3. Use a PDS data set copy utility or ISPF 3.3 to copy the members from the fixed block CLIST library to the variable block CLIST library. 4. Use the variable block CLIST library in the software allocation. 5. Delete the fixed block CLIST library. Edit Job Cards This option places you in ISPF edit mode for a member called JOBCARD, which is stored in the skeleton library. The following procedure explains how to edit Job Cards. 1. Select option 2 on the Installation Variables Management Menu and press Enter. The Edit Job Card screen appears. EDIT ---- CAI.MVSHE.SLIB(JOBCARD) COLUMNS COMMAND == > SCROLL == > CSR ******************************* TOP OF DATA ******************************** //CEJob JOB CARD INFO HERE //* //* COPY IN JOBCARDS FROM SOME OTHER LIBRARY //* ******************************* BOTTOM OF DATA ***************************** 4 10 Installation Guide for Host Encyclopedia and Host Construction

49 Tasks to Define Installation Variables 2. Create valid job cards for your site, using these considerations: The job cards are included in each installation job built. The USER parameter must be the installer s TSO user ID (some installation jobs use this ID to confirm authorization). The REGION parameter must be at least 4096 KB. 3. When your job cards are complete, press F3 to save the information and exit the screen. The Installation Variables Management Menu appears. Set JCL Variables Use this option to define the values that are used in building installation JCL. The following procedure explains how to set JCL variables. 1. Select option 3 on the Installation Variables Management Menu and press Enter. The Set JCL Variables screen appears. Set JCL Variables COMMAND == > Enter the installation job step JCL variables and any required STEPLIB Dataset names. Installer TSOID DAACADB_ DISK UNIT SYSDA Tape Unit 3480 SYSOUT class * Steplibs used only in installation batchjob JCL. DB2 STEPLIB (optional) DB2 STEPLIB (optional) z/os steplib1 (optional) z/os steplib2 (optional) OTHER STEPLIB (optional) WARNING: Only provide DB2 and/or z/os steplibs if required at Your site. F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Verify and complete the fields on the Set JCL Variables screen, using these considerations: The TSO user ID is required. It is prefixed to the names of the temporary data sets built and used during installation. The installation process includes data sets specified here and data sets allocated in the installer s TSO session to the STEPLIB DD or the ISPLLIB DD into the installation s JCL STEPLIB. This can result in duplicate data set names in the STEPLIB concatenation in the installation JCL. No action is required if this occurs. 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. Chapter 4: Establishing the Environment 4 11

50 Tasks to Define Installation Variables 4. When verification ends, press Enter to exit the screen. 5. Press F3 to exit the screen. Note: The z/os runtime parameters HEAP, ANYHEAP and THREADHEAP, which specify locations for certain types of storage, must be defined with the ANYWHERE parameter specified to ensure that storage used by AllFusion Gen processes can be acquired above the line. Set Encyclopedia Variables Use this option to capture global values for AllFusion Gen as described in the following procedure. 1. Select option 4 on the Installation Variables Management Menu and press Enter. The Set Encyclopedia Variables screen appears. Set Encyclopedia Variables COMMAND == > Enter or verify encyclopedia variables for the current installation. Site name Encyclopedia name Encyclopedia ID Install construction Administrator TSOID Administrator name PLAN prefix Schema identifier User dataset prefix User dataset UNIT type User dataset suffix YOUR_COMPANY_NAME HOST001_ 1 Y TSO user ID SYSTEM_ADMINISTRATOR HEPL 9.1.A5 &SYSPREF SYSDA (Optional) Enter or verify optional variables used in model crosscopy or conversion Old PLAN prefix PL00 (Optional) Old Schema identifier 9.0.A2 (Optional) Old load library F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the Set Encyclopedia Variables screen, based on the following considerations: The Encyclopedia Name must be unique to prevent z/os enqueues. &SYSPREF is defined to create temporary data sets from the Encyclopedia user s TSO ID. The Schema Identifier must be 9.1.A5. Do not change this value. The PLAN Prefix is used to construct plan names for AllFusion Gen. Verify this value is unique for the DB2 subsystem. If the Old PLAN Prefix, Old Schema Identifier, and Old Load Library fields are used, they must contain valid values Installation Guide for Host Encyclopedia and Host Construction

51 Tasks to Define Installation Variables 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 4. When the verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen. Define Regional Settings The value you select from this screen defines the default Encyclopedia code page that is loaded into the DXCPID table during installation. Understanding Regional Settings and Code Pages There are some important aspects of code pages and the DXCPID table that you should understand before selecting a regional setting. All new models are stored in the encyclopedia in the code page associated with the regional setting you select. Existing models maintain their original code page association. The DXCPID table lists all the possible code page values supported by AllFusion Gen and the corresponding code page value in which new models are translated and stored in the Host Encyclopedia. If your country is not listed on the Regional Settings screen, select the Other option. All American and Western European code pages are based on a Latin-1 character set and can be successfully translated from one to the other. Countries based on character sets other than Latin-1 often have only one valid code page. The defaults defined in the DXCPID table will handle these countries regardless of the selection made on the Regional Settings screen. For example, Japan has three regional settings from which to choose: 930, 939, or Other (which exports both code page 930 and code page 939). Loading a DBCS BiDi (Double-Byte Character Set, BiDirectional) code page and a non-western European Latin (such as Turkish) encyclopedia code page entry into DXCPID is not affected by the selection you make in the Regional Settings screen. For an explanation of the code page translation table, see Code Page Translation in the chapter Encyclopedia Communications in the CSE Guide. For a full explanation of code page functionality, see the National Language Support Reference Manual, Volume II published by IBM. Chapter 4: Establishing the Environment 4 13

52 Tasks to Define Installation Variables The following procedure explains how to select a Regional Setting. 1. Select option 5 on the Installation Variables Management Menu and press Enter. The Regional Settings screen appears. COMMAND ===> Regional Settings Select the number for the appropriate country... 'Euro' support (y/n)... _ Number Country Codepage:w/o Euro w Euro USA, Brazil, Canada, Netherland, Portugal (037) (1140) 2 Norway, Denmark (277) (1142) 3 Sweden, Finland (278) (1143) 4 Germany, Austria (273) (1141) 5 Italy (280) (1144) 6 Latin American Spanish and Spain (284) (1145) 7 France (297) (1147) 8 Belgium, Switzerland (500) (1148) 9 United Kingdom (285) (1146) 20 Other (see Help Panel) 21 Japan Traditional (930) 22 Japan Enhanced CUA (939) 23 China Simplified GB2312 only 24 China Simplified GB2312 and GBK. 25 China Simplified GB2312, GBK, and user defined. F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Enter the number that represents the appropriate country and code page for your site. 3. Set the Euro flag to Y if you want to use the Euro sign in your models. Note: If you are upgrading an existing encyclopedia and set the Euro support flag to Y, you must run DXCPISRT in SPUFI or an equivalent query program. This creates a table that cross-references ASCII and EBCDIC code pages that have identical character sets. This facilitates the upload and download of models from workstations that have ASCII code pages to the Host Encyclopedia and its EBCDIC code pages. For more information on the upload and download of models, see the appendix, Setting Model Code Pages. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen Installation Guide for Host Encyclopedia and Host Construction

53 Tasks to Define Installation Variables Set DB2 Variables Use this option to capture the global values required for building DB2 tables and running DB2 utilities. The following procedure explains how to set DB2 variables. 1. Select option 6 on the Installation Variables Management Menu and press Enter. Set DB2 Variables COMMAND ===> Enter or verify the DB2 encyclopedia installation variables and select a dataset type. DB2 Subsystem ID DSN_ Explicit creator ID (Optional) Secondary Authorization ID.. (Optional) DB2 Collection ID DBCOLLID Schema DB name HOSTS Data DB name HOSTD Public Interface DB name...hostp Dataset storage type..... S (S=Storage Group, V=Vsam) Encyclopedia initial size...s (S=Small, M=Medium) Secondary storage factor...0_(.01 to 1.0 X primary, 0=No secondary) Note: Changes to any of the last 3 fields on this panel will require a rebuild of the space values (Option 7 or 8 on previous panel). F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the Set DB2 Variables screen based on the following considerations and according to the information gathered in your site variables worksheets. If the Data set Storage Type is S (Storage Group), the maximum and minimum space values are checked to ensure compliance with DB2 rules. The first seven fields on the Set DB2 Variables screen are blank unless you are using an existing TILPARMS member. You can enter either an Explicit Creator ID or a Secondary Authorization ID, or leave these fields blank. For assistance in choosing the size of the initial Host Encyclopedia, see the appendix Sizing an Encyclopedia. Important! If this is an existing installation, be aware that the values you enter in Data set Storage Type, Initial Data Base Size, or Secondary Storage Factor are used to create space values. These values are stored in member TILTAB50. If you change the values in these fields from prior values, TILTAB50 is deleted and your values are lost. For more information on the tasks before changing the values in these fields, see the section TILTAB50. Chapter 4: Establishing the Environment 4 15

54 Tasks to Define Installation Variables 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 4. When the verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen. Assign Storage Group Names This option is available if you specified Storage Groups as the data set storage type when you set the DB2 variables. The following procedure explains how to assign storage group names 1. Select option 7 on the Installation Variables Management Menu and press Enter. The Assign Storage Group Names screen displays. Assign Storage Group Names ROW 1 TO 12 OF 83 COMMAND == > SCROLL == > Assign 6 distributed Storage Group names, or assign names by table and index Spaces. Adjust space as required. Press F2=Accept, F3=Exit, F6=Save, F12=Can Distributed Storage Group(s) (1) (2) (3) (4) (5) (6) DB Dis Space Storage -Primary space- -Secondary space- Type Grp Name Group -Default Modify- -Default Modify DATA 3 DASC DATA 4 DASCI DATA 4 DASCI DATA 3 DOBJ DATA 4 DOBJI DATA DOBJI DATA 4 DOBJ DATA 5 DPRP DATA 6 DPRPI DATA 1 DSUBEX DATA 2 DSUBEXI DATA 2 DSUBEXI If you want the tablespace and indexspace allocations distributed across your Storage Groups, type the names of the Storage Groups in spaces 1 through 6. Note that: At least one Distributed Storage Group is required. Tablespaces and indexes referencing a blank Distributed Storage Group are distributed to the group specified in 1. Allocating the database over three to six volumes can improve performance. If you specify more than one disk group, complete all the Distributed Storage Group fields. For example, if you only want to assign three groups, complete all the fields by using the same name for 1 and 4, 2 and 5, 3 and Installation Guide for Host Encyclopedia and Host Construction

55 Tasks to Define Installation Variables 3. To specify how individual tablespaces and indices are distributed, modify the Dis Grp (Distribution Group) field. Note: For information about how AllFusion Gen assigns high-use tablespaces and indexes, see the Appendix Sizing an Encyclopedia. 4. To modify a Primary Default storage value for a table or index, type a new value in the Modify Space column. 5. To modify a Secondary Default storage value for a table or index, type a new value in the Modify Space column. Note: The Secondary Default storage space value for a table or index on this screen is calculated by multiplying the Primary Default storage space value by the Secondary Storage Factor entered on the Set DB2 Variables screen described above. 6. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. This also creates the member TILTAB50 in the Table library (TLIB). TILTAB50 is used by the system to create the storage group space variables in the CREATE TABLESPACE SQL member (CRNEWSP). See TILTAB50 in this chapter for more information. 7. When verification is complete, press Enter to exit the Activity Display screen. 8. Press F3 to exit the screen. Chapter 4: Establishing the Environment 4 17

56 Tasks to Define Installation Variables Assign VSAM Names This option is available if you specified VSAM for the data set storage type when you set the DB2 variables. The following procedure explains how to set assign VSAM names. 1. Select option 8 on the Installation Variables Management Menu and press Enter to display the Assign VSAM Names screen. Assign VSAM Names ROW 1 TO 12 OF 83 COMMAND == > SCROLL == > Assign 6 distributed volume names, or assign names by table and index Spaces. Adjust space as required. Press F2=Accept, F3=Exit, F6=Save, F12=Cancel High level VCAT node Distributed Storage Group(s) AAAC2 (1) (2) (3) (4) (5) (6) DB Dis Space VSAM -Primary space- -Secondary space- Type Grp Name Volume -Default Modify- -Default Modify DATA 3 DASC DATA 4 DASCI DATA 4 DASCI DATA 3 DOBJ DATA 4 DOBJI DATA DOBJI DATA 4 DOBJ DATA 5 DPRP DATA 6 DPRPI DATA 1 DSUBEX DATA 2 DSUBEXI DATA 2 DSUBEXI Type the high-level VCAT node used to form the DB2 VSAM space data set names for the Host Encyclopedia. 3. If you want to distribute the tablespace and indexspace allocations across your DASD volumes, type the names of the available volumes in spaces (1) through (6). Note that: At least one volume is required. Tablespaces and indices referencing a blank Distributed VSAM volume are distributed to (1). Allocating the database over three to six volumes can improve performance. If you specify more than one volume, you must complete all the Distributed VSAM volume fields. For example, if you only want to assign three volumes, complete all the fields by using the same volume name for (1) and (4), (2) and (5), (3) and (6). 4. To specify how individual tablespaces and indices are distributed, modify the Dis Grp (Distribution Group) field. For information about how AllFusion Gen assigns high-use tablespaces and indexes, see Sizing an Encyclopedia Installation Guide for Host Encyclopedia and Host Construction

57 Tasks to Define Installation Variables 5. To modify a Primary Default storage value for a table or index, type a new value in the Modify Space column to the right of the Primary Default value. 6. To modify a Secondary Default storage value, type a new value in the Modify Space column to the right of the Secondary Default value. Note: The Secondary Default storage space value for a table or index is calculated by multiplying the Primary Default storage space by the Secondary Storage Factor entered on the Set DB2 Variables screen. 7. Press F2 to verify the entered variables and store them in the user s ISPF profile pool. This also creates member TILTAB50 in the table library (TLIB). TILTAB50 is used by the system to create CEJOB02, the VSAM JCL space variables. For more information on TILTAB50, see TILTAB When verification is complete, press Enter to exit the Activity Display screen. 9. Press F3 to exit the screen. Set Target System Variables Select option 9 on the Installation Variables Management Menu and press Enter to display the Set Target System Variables Menu, as shown next. Set Target System Variables COMMAND == > Select options 1-3 in sequence. Select the other options as required 1. Target environment configuration 2. Set COBOL compiler variables 3. Set DB2 precompiler variables 4. Set Datacom preprocessor variables 5. Set CICS variables 6. Set IMS variables 7. Set RPROF variables 8. Select MFS device types F1=Help F3=Exit Each of the options on this screen leads to another screen in which you can set target system variables. Options 1, 2, and 3 or 1, 2, and 4 (depending on DB2 or Datacom) must be performed in sequence. Options 5 through 8 are optional, depending on the target environment configuration. The following sections explain how to use each of these options. Chapter 4: Establishing the Environment 4 19

58 Tasks to Define Installation Variables Target Environment Configuration Use this option to configure the target environments where applications generated by AllFusion Gen run. The following procedure explains how to configure target environment. 1. Select option 1 on the Set Target System Variables Menu and press Enter to display the Target Environment Configuration screen. Target Environment Configuration COMMAND == > Enter or verify target environment options. Support generated applications under DB2 Support generated applications under Datacom Support generated applications under CICS Support generated applications under IMS Support MFS map generation Create runtime profile table (RPROF) Y N Y Y N Y F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the Target Environment Configuration screen according to the specifics of your environment. The choices you make here enable other options on the Set Target System Variables Menu. 3. Press F2 to verify and save the entered variables in the user s ISPF profile pool. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen Installation Guide for Host Encyclopedia and Host Construction

59 Tasks to Define Installation Variables Set COBOL Compiler Variables Use this option to define variables for the COBOL compiler, which is used during the installation phase of Host Construction. This compiler applies to all environments. The following procedure explains how to set COBOL compiler variables. 1. Select option 2 on the Set Target System Variables Menu and press Enter to display the Set Compiler Variables screen. COMMAND ===> Set Compiler Variables Enter or verify the following COBOL compiler variables. COBOL compiler name..... IGYCRCTL Size parameter COBOL Compiler library IGY.SIGYCOMP Compiler library in linklist N z/os Static runtime z/os Dynamic runtime SCEERUN library in linklist CEE.SCEELKED CEE.SCEERUN N F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the Set Compiler Variables screen. The IBM default name for the COBOL Compiler library is IGY.SIGYCOMP. The IBM default name for the z/os Static runtime library is CEE.SCEELKED. The IBM default name for the z/os Dynamic runtime is CEE.SCEERUN. 3. Press F2 to verify and save the entered variables in the user s ISPF profile pool. Note: The value in the Size Parameter field is passed to the COBOL compiler. If this field is left blank, the site default is used. If the site default is too small, the compiler may fail. The recommended minimum is 3072 KB. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen. Chapter 4: Establishing the Environment 4 21

60 Tasks to Define Installation Variables Set DB2 Precompiler Variables Use this option to define variables for the DB2 precompiler, which is used during the installation phase of Host Construction. The following procedure explains how to set DB2 precompiler variables. 1. Select option 3 on the Set Target System Variables Menu and press Enter to display the Set DB2 Precompiler Variables screen. COMMAND == > Set DB2 Precompiler Variables Enter or verify the following precompiler variables. DB2 precompiler name DB2 link library Link lib in LPA/linklist DSNHPC DB2.SDSNLOAD N F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the DB2 Precompiler Variables screen. 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen. Set Datacom Preprocessor Variables Use this option to define Datacom variables, which are used during the installation phase of AllFusion Gen. The following procedure explains how to set the Datacom variables. 1. Select option 4 on the Set Target System Variables Menu and press Enter to display the Set Datacom preprocessor variables screen. COMMAND == > Set Datacom preprocessor variables 1 Set Datacom preprocessor name. 2. Set Datacom MUF names F1=Help F3=Exit 4 22 Installation Guide for Host Encyclopedia and Host Construction

61 Tasks to Define Installation Variables 2. Select option 1 and press Enter to display the Set Datacom preprocessor name panel shown below. Use this panel to define variables for the Datacom preprocessor name, which is used during the installation phase of AllFusion Gen. COMMAND == > Set Datacom preprocessor name Enter or verify the Datacom preprocessor name. Datacom preprocessor name DBXMMPR_ F1=Help F2=Accept F3=Exit F6=Save F12=Cancel Complete the field on the Datacom preprocessor name screen. 3. Press F2 to verify and save the entered variable in a working copy of the user s ISPF profile pool. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit back to the Set Datacom preprocessor variables screen. 6. Select option 2 and press Enter to display the Set Datacom MUF variables panel shown below. Use this panel to select: Add, Delete and Display MUF names. COMMAND == > Set Datacom MUF variables Select one of the options below, then press <enter> _ 1 Add a MUF name. 2 Delete a MUF name. 3 Display all MUF names. F1=Help F12=Cancel 7. Select option 1 and press <enter> to add a MUF name. Use option 2 to Delete a MUF name if desired. Use option 3 to Display all MUF names currently in AllFusion Gen. Chapter 4: Establishing the Environment 4 23

62 Tasks to Define Installation Variables Use this panel to add MUF names and associated Datacom load datasets. COMMAND == > Set Datacom variables Add Datacom MUF-name and Load Datasets: Datacom MUF name..... DCMMUF Datacom CUSLIB dataset..... CAI.DCM.CUSLIB Datacom CAILIB dataset..... CAI.DCM.CAILIB Datacom CICS CUSLIB dataset... CAI.DCM.CICS.CUSLIB Datacom CICS CAILIB dataset... CAI.DCM.CICS.CAILIB Each MUF-name must be unique and have four (4) Datacom load datasets associated with it. You can have a maximum of 20 Datacom MUF names defined per z/os subsystem. F1=Help F2=Accept F3=Exit-and-Save F12=Cancel a. Enter your Datacom MUF name and four (4) Datacom/CICS load data sets, and press F2 to verify and temporarily save the entered variables. You can add up to twenty (20) MUF names and associated Datacom/CICS load data sets per z/os sub-system. b. When you have completed all input and verified all data sets, press F3 to exit and save all MUF names and load data sets entered to an ISPF table. Then exit back to the Set target variables screen Installation Guide for Host Encyclopedia and Host Construction

63 Tasks to Define Installation Variables Set CICS Variables This option is available if the Support AllFusion Gen Applications Under CICS flag on the Target Environment Configuration screen is set to Y. The following procedure explains how to set CICS variables. 1. Select option 4 on the Set Target System Variables Menu and press Enter to display the Set CICS Variables screen. Set CICS Variables COMMAND == > Enter or verify the following CICS variables. CICS load library (1) z/os Static Link Library (2) CICS shares CPU with this TSO CICS.SDFHLOAD CEE.SCEELKED N (1) -IBM default name: 'CICS.SDFHLOAD' (2) -IBM default name: 'CEE.SCEELKED' F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the Set CICS Variables screen. The z/os Static Link Library should be the runtime library containing CICS-specific COBOL runtime modules (for example, CEE.SCEELKED). Note that the CICS DB2 library is no longer specified. This is because it is the same library as the CICS Load library. The variable TIRCLDB2 in TIRCFIGS clist now points to the CICS Load library. The name of the system library that contains the CICS Sockets interface modules normally called TCPIP.SEZATCP is not required and has been removed. 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen. Chapter 4: Establishing the Environment 4 25

64 Tasks to Define Installation Variables Set IMS Variables This option is available if the Support AllFusion Gen Applications Under IMS flag on the Target Environment Configuration screen is set to Y. The following procedure explains how to set IMS variables. 1. Select option 5 on the Set Target System Variables Menu and press Enter to display the Set IMS Variables screen. Set IMS Variables COMMAND == > Enter or verify the following IMS variables. IMS resident load lib IMS.RESLIB Maximum segment size 1280 IMS shares CPU with this TSO N CPIC interface load lib SYS1.CSSLIB F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the Set IMS Variables screen. The value entered in the Maximum Segment Size field is site-specific; your system administrator knows this value. 3. The name of the system library that contains the CPIC interface modules (CMRCV, CMALLC and so on) is normally SYS1.CSSLIB, which is a required z/os library. 4. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 5. When verification is complete, press Enter to exit the Activity Display screen. 6. Press F3 to exit the screen. Set RPROF Variables This option is available if the Create Runtime Profile Table (RPROF) flag on the Target Environment Configuration screen is set to Y. This option builds the BLDRPROF JCL member, which is stored in the AllFusion Gen JCL library. You can use BLDRPROF to create runtime profile tables (RPROFs) if you do not have them. RPROF tables created under previous versions of AllFusion Gen are compatible. For more information on RPROF, see The Runtime Profile (RPROF) Table Installation Guide for Host Encyclopedia and Host Construction

65 Tasks to Define Installation Variables The following procedure explains how to set RPROF variables. 1. Select option 6 on the Set Target System Variables Menu and press Enter to display the Set RPROF Variables screen. COMMAND ===> Set RPROF Variables Enter or verify the following DB2 RPROF variables. DB2 Subsystem ID DB2_ Explicit creator ID.... (Optional) Secondary Authorization ID. (Optional) DB name RPROF Storage Group S (S=Storage Group, V=Vsam) Storage type RPROF initial size K pages RPROF secondary size K pages RPROFI1 initial size K pages RPROFI1 secondary size K pages F1=Help F2=Accept F3=Exit F6=Save F12=Cancel 2. Complete the fields on the Set RPROF Variables screen. You can enter an Explicit Creator ID, a Secondary Authorization ID, or leave these fields blank. The VCAT and volume fields appear if the VSAM space allocation is configured instead of Storage Group. These fields are required. VSAM page size is 4 KB, Storage Group is 1 KB. Size values do not convert when switching from one storage type to the other. 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen. Chapter 4: Establishing the Environment 4 27

66 Tasks to Define Installation Variables Select MFS Device Types This option is available if the Support MFS Map Generation flag on the Target Environment Configuration screen is set to Y. The following procedure explains how to select MFS device types. 1. Select option 7 on the Set Target System Variables Menu and press Enter to display the Select MFS Device Types screen. COMMAND ===> Select MFS Device Types Listed are the MFS device types supported by Gen. Select the devices defined for your installation requiring the generation of Gen MFS formats Press F1=Help, F2=Accept, F3=Exit, F6=Save, F12=Cancel Sel Device Type Extended attribute Rows Cols support 3270,1 Y Y 3270, P SCS SCS A A A A A A A A08 2. Type Y in the Sel column next to the appropriate device type. 3. Press F2 to verify and save the entered variables in a working copy of the user s ISPF profile pool. This creates the member TILMFS in the table library (TLIB). TILMFS is used by the system when processing IMS. 4. When verification is complete, press Enter to exit the Activity Display screen. 5. Press F3 to exit the screen, press F3 again to exit the menu. For more information about MFS implementation, see the appendix Configuring IMS and CICS Installation Guide for Host Encyclopedia and Host Construction

67 Verify Installation Variables Verify Installation Variables The Check Variables option performs a validity check on the working copy of the variables. The validity check does not perform any updates on errors. You can perform this check anytime during variable definition. The following procedure explains how to verify installation variables. 1. Select option 10 on the Installation Variables Management Menu. This option performs the verify function, used by the F2 key, on all the variables entered into CEINSTAL. 2. Check the messages on the Activity Display screen. Confirm all variables are valid and passed verification. Correct any errors and recheck the variables. 3. Press Enter to exit the Activity Display screen. 4. Press F3 to exit the menu. Save Installation Variables This option creates a snapshot of all ISPF profile pool variables. The variables are saved as a member in the JCL library called TILPARMS. TILPARMS stores installation variables for later use. For more information about TILPARMS, see the appendix Installation and Implementation Information. Note: When you save variables, the save action overwrites any current values in TILPARMS. If you want to save existing values in TILPARMS and you want to create new values, rename TILPARMS before saving the new variables. To save new variables for subsequent recall, select option 11 on the Installation Variables Management Menu. If the new variables are not explicitly saved, they are automatically saved when you select option 2, Build Encyclopedia CLISTs (TIUGLOB, TIRCFIGS, TIXGLOB) from the Host Encyclopedia Maintenance menu. Chapter 4: Establishing the Environment 4 29

68 Build CLISTs Display System Information You can review system information at any time by executing this TSO command from inside CEINSTALL: TSO %HESYSADM. This displays the System Administration Information panel which contains the following useful displays. Option One - Displays the copyright panel which includes the release and levelset numbers. Option Two - Displays a list of all PTFs applied to this Host Encyclopedia. Option Three - Displays a separate panel to access these variables: Host Encyclopedia variables Host Encyclopedia administration variables Host Encyclopedia DB2 variables Host Encyclopedia Datacom variables Host Encyclopedia COBOL variables Host Encyclopedia IMS variables Host Encyclopedia CICS variables Miscellaneous Option Four Makes the current TSO ID a new Host Encyclopedia administrator ID and loads the current TSO ID with the ISPF (profile pool) variables used by the original installer. Build CLISTs Five CLISTs (TIXGLOB, TIUGLOB2, TIELIBDF, TIELIBFR and TIRCFIGS) are built automatically using the variables you defined in the preceding three tasks. These CLISTs are required to define the operating parameters for AllFusion Gen execution. The following procedure explains how to build CLISTs: 1. Select option 2 on the Host Encyclopedia Maintenance Menu and press Enter to display a Confirm Activity screen. 2. Press Enter to start building the CLISTs. The CLISTs are created and stored in the AllFusion Gen CLIST library. 3. When processing is complete, press Enter to return to the AllFusion Gen Encyclopedia Maintenance Menu Installation Guide for Host Encyclopedia and Host Construction

69 Build Sample Utility JCL Build Sample Utility JCL Use this option to build the JCL members you need for testing Host Construction and maintaining the Host Encyclopedia. The following procedure explains how build sample utility JCL. 1. Select option 3 on the Host Encyclopedia Maintenance Menu and press Enter. 2. Press Enter to start the build process. The JCL members are created and stored in the AllFusion Gen JCL library. 3. When processing is complete, press Enter to return to the Host Encyclopedia Maintenance Menu. Create a DB2 PLAN_TABLE (Optional) If you do not have a DB2 table called PLAN_TABLE with the Install Binder ID, you may want to create one for performance management purposes. Instructions on how to create the PLAN_TABLE are included in your IBM DB2 Administration Guide and in the DB2 Application Programming and SQL Guide; both guides are available from IBM Encyclopedia Number for Multiple Encyclopedias If you are using multiple encyclopedias, including Client/Server Encyclopedias, you must create a unique numeric ID for the Host Encyclopedia. This ensures object uniqueness across all encyclopedias. Perform this procedure after you create the Encyclopedia tables using the preceding procedures in this chapter. If you are loading tables from existing encyclopedias into new encyclopedias, you should also complete that task before using this procedure to create the Host Encyclopedia ID. 1. From the Main Menu, type TSO %TIEMAX on the command line and press Enter. 2. Complete the next screen as follows: Do NOT enter a value for the schema. Enter an Encyclopedia name. This field is optional. Enter a non-zero, numeric Encyclopedia ID and press Enter. Chapter 4: Establishing the Environment 4 31

70 Where Do You Go From Here? Where Do You Go From Here? This is the end of the installation process for the Host Encyclopedia and Host Construction. At this point, you have unloaded and allocated libraries. You have established the environment for accessing and using the encyclopedia through definition of variables and execution of jobs. The next step is to build an encyclopedia. The chapter titled Creating a New Encyclopedia, explains how to build a new encyclopedia. The chapter titled Upgrading an Encyclopedia in Place explains how to update the schema tables that control models so that your encyclopedia can handle AllFusion Gen r7.6 models. For more information about copying models and data from a different encyclopedia, see Populating a Host Encyclopedia Installation Guide for Host Encyclopedia and Host Construction

71 Chapter 5: Creating a New Encyclopedia To create a new encyclopedia, you must build and execute SQL and JCL. If you have an existing encyclopedia from which you want to copy data, you must first create the new encyclopedia. The specific tasks to create a new encyclopedia are: 1. Build SQL and JCL. 2. Run jobs to create the encyclopedia. 3. Test encyclopedia functions. 4. Copy and rebind AllFusion Gen plans. 5. Enable user access to the encyclopedia. Prerequisites Before you proceed with creating a new encyclopedia, you must have completed the work from preceding chapters, including: 1. Reading and completing the site variables worksheets 2. Upload and Install from CD. 3. Establishing ISPF concatenation 4. Defining all variables to establish the appropriate environment 5. If appropriate, setting up a numeric Host Encyclopedia ID Chapter 5: Creating a New Encyclopedia 5 1

72 Build SQL and JCL Build SQL and JCL This procedure allows the CEINSTAL program to build the SQL and JCL to create the Encyclopedia: 1. Select option 4 on the Host Encyclopedia Maintenance Menu and press Enter to start building the SQL and JCL. 2. When processing ends, press Enter and the Host Encyclopedia Maintenance Menu reappears. Run Jobs to Create the Encyclopedia Review the following considerations before running the jobs to create a new encyclopedia. The SQL and JCL for the encyclopedia build process are in the SQL and JCL libraries. Run the build jobs defined in the table below in the exact manner and order in which they are presented. Running the jobs in a different sequence, or omitting a job, causes errors and failures. Each job must be run on the CPU containing the unloaded and allocated Host Encyclopedia software and your DB2 subsystem. These jobs create the z/os Host Encyclopedia DB2 tables for AllFusion Gen. Use this table as a checklist as you run the following jobs. You must run the jobs in the order listed in the table. JCL Name CEJOB02 CEJOB03 Description For storage groups, this job is not required. For data set storage type VSAM, this job deletes existing and creates new VSAM data sets for DB2 objects. Ignore return code 8; this means the data set for deletion did not exist. Executes a DB2 BIND of the dynamic SQL program TIUUSQL to AllFusion Gen DB2 subsystem. If your site has Host Construction and the target for generated applications is on a different DB2 subsystem from the Host Encyclopedia, bind TIUUSQL for both subsystems. Also, grant DB2 EXECUTE authority to PUBLIC for plans on the target s subsystem. 5 2 Installation Guide for Host Encyclopedia and Host Construction

73 Run Jobs to Create the Encyclopedia JCL Name CEJOB04 CEJOB05 CAJOB05 Description Creates DB2 objects for AllFusion Gen and populates the DXCPID table. Also inserts the installer ID into the user table with Encyclopedia administrator authority. Ignore SQL code of 552. This means the databases already exist, but do not affect processing. Loads schema tables for 9.1.A5, 9.0.A2, and 8.0.A3, which contain static data representing the meta-model. You must have IBM DB2 utilities to execute this job. You can also use the equivalent job that uses CA Unicenter DB2 products. If you are using utilities from other vendors, customize this job accordingly. Loads schema tables for 9.1.A5, 9.0.A2, and 8.0.A3, which contain static data representing the meta-model. Customers must have CA Unicenter DB2 products to execute this job. You can also use the equivalent job that uses IBM utilities. If you are using utilities from other vendors, customize this job accordingly. This job returns RC=4 if DB2 Products UTIL parmlib contains SET-COPYPENDING TO (NO). RC=4 is acceptable unless the optional job CEJOB05A is to be run subsequently. In that case, you must run DB2 backup (job CAUCOPY) before running CEJOB05A. CEJOB05A (Optional) CEJOB06 CAJOB06 CEJOB07A CEJOB07B CEJOB08 CEJOB09 Relaxes migration rules by modifying values on the schema tables that provide operational rules for object migrations using version control. Executes the DB2 RUNSTATS utility for the Host Encyclopedia tables and index. You must have IBM DB2 utilities to execute this job. You can also use the equivalent job that uses CA Unicenter DB2 products. If you are using utilities from other vendors, customize this job accordingly. Executes the DB2 PDASTATS utility for the Host Encyclopedia and index. Customers must have CA Unicenter DB2 products to execute this job. You can also use the equivalent job that uses IBM utilities. If you are using utilities from other vendors, customize this job accordingly. Binds DBRMs into packages. Binds AllFusion Gen plans to use the packages (only run once). This job grants DB2 authority to PUBLIC on all AllFusion Gen plans and DB2 SELECT authority on Public Interface Table views. Updates the DMAX tables for the AllFusion Gen schema. Chapter 5: Creating a New Encyclopedia 5 3

74 Run Jobs to Create the Encyclopedia JCL Name CEJOB10 Description Loads the Functions model to the new encyclopedia (required): Model name: IEF_SUPPLIED_FUNCTION in the data set CAI.MVSHE.TRAN(FUNC91A5). CEJOB10 may return a condition code of 0 even if it fails. To verify, the Functions model has been added to the list of models, display the AllFusion Gen Main Menu, enter on the command line, and press Enter. On the Model Statistics screen, move the cursor to the Model Name field and press F4 to display the list of models. Verify the Functions model appears on the list. If the model is missing, look for an error message in userid.ief.logfile. If CEJOB10 abends with U3001 ONCODE 84 when SYSPRINT is Allocated, the userid.ief.sysprint data set is unavailable. To correct the error, navigate out of AllFusion Gen concatenation, issue a FREE DA (userid.ief.sysprint) command, delete any added models, and resubmit CEJOB10. CEJOB11 Processes the Functions model. This job inserts the model information into the schema SMDL table and deletes the model information from the data DMDL table. The expected return code is 20. To verify the Functions model is removed from the list of models, display the list of models by entering on the command line and pressing enter. Verify IEF_SUPPLIED_FUNCTIONS is not on the list. CEJOB12 Loads the Sample model to the new encyclopedia (optional): Model name: GEN SAMPLE MODEL R76 in the data set: CAI.MVSHE.TRAN(SAMPMODL) CEJOB12 may return a condition code of 0 even if it fails. CEJOB12 may return a condition code of 0 even if it fails. To verify the model has been added to the list of models, display the AllFusion Gen Main Menu, enter on the command line, and press Enter. On the Model Statistics screen, move the cursor to the Model Name field and press F4 to display the list of models. Verify the Sample model appears on the list. If the model is missing, look for an error message in userid.ief.logfile. If CEJOB12 abends with U3001 ONCODE 84 when SYSPRINT is Allocated, the userid.ief.sysprint data set is unavailable. To correct the error, navigate out of AllFusion Gen concatenation, issue a FREE DA (userid.ief.sysprint) command, delete any added models, and resubmit CEJOB Installation Guide for Host Encyclopedia and Host Construction

75 Run Jobs to Create the Encyclopedia JCL Name CEJOB13 Description Loads the Help model to the new encyclopedia (optional): Model name: GEN SAMPLE HELP MODEL R76 in the data set: CAI.MVSHE.TRAN (HELPMODL) CEJOB13 may return a condition code of 0 even if it fails. To verify the model has been added to the list of models, display the AllFusion Gen Main Menu, enter on the command line, and press Enter. On the Model Statistics screen, move the cursor to the Model Name field and press F4 to display the list of models. Verify the Help model appears on the list. If the model is missing, look for an error message in userid.ief.logfile. If CEJOB13 abends with U3001 ONCODE 84 when SYSPRINT is Allocated, the userid.ief.sysprint data set is unavailable. To correct the error, navigate out of AllFusion Gen concatenation, issue a FREE DA (userid.ief.sysprint) command, delete any added models, and resubmit CEJOB13. CEJOB06 CAJOB06 CEJOB07A Run this job again. It executes the IBM DB2 RUNSTATS utility for the Host Encyclopedia tables and indexes. Run this job again. It executes the DB2 PDASTATS utility for the Host Encyclopedia tables and indexes. A RUNSTATS of the AllFusion Gen data tables (after loading the models in CEJOB10), followed by a REBIND of all AllFusion Gen plans, speeds access of the Encyclopedia. Executes bind replace on all packages. Chapter 5: Creating a New Encyclopedia 5 5

76 Test Encyclopedia Functions Test Encyclopedia Functions Test the functions of the new encyclopedia by exporting a model to the Public Interface and running an Entity Definition Report. Use the Gen Sample Model to export to the Public Interface. Note: Running the export in the foreground can be time consuming, so it is best to run this procedure in a batch mode. The following procedure explains how to test encyclopedia functions. 1. Select option 2 on the AllFusion Gen Main Menu and press Enter. The Public Interface Functions screen appears. a. Select option 1 and press Enter to export a model. b. Type the model name GEN SAMPLE MODEL R76 and press Enter. If an error occurs during the export process, the error message appears in the userid.ief.logfile. If the model was not exported, contact Technical Support. 2. Run the Entity Definition Report as follows: a. Select option 1 on the Main Menu and press Enter. b. Select option 3 and press Enter to display the Host Encyclopedia Reports Menu. c. Select option 13 and press Enter to display the Model Reports screen. d. Type the model name GEN SAMPLE MODEL r76 and press Enter. e. Select option 6 and press Enter. The Entity Definition Report runs and is displayed on your screen. 5 6 Installation Guide for Host Encyclopedia and Host Construction

77 RUNSTATS, Rebind AllFusion Gen Packages and Image Copy RUNSTATS, Rebind AllFusion Gen Packages and Image Copy Before you rebind the packages, update DB2 statistics to optimize encyclopedia access. 1. Run CEJOB06 or CAJOB06 a third time. This job updates the DB2 statistics for the Host Encyclopedia tables and indexes. 2. After the models are uploaded to the Host Encyclopedia and the Gen Sample Model is exported to the public interface, many major AllFusion Gen tables have rows of data. For DB2 optimization, a RUNSTATS of the AllFusion Gen data tables, followed by a BIND of all AllFusion Gen packages, speeds subsequent access to the encyclopedia. 3. Run CEJOB07A. These jobs execute a DB2 BIND of the AllFusion Gen packages taking advantage of the new RUNSTATS statistics. 4. Run CEUCOPY. This job executes the DB2 COPY utility creating an imagecopy of all AllFusion Gen tablespaces. Package Bind The steps for package binds are: 1. JCL - CEJOB07A Bind/remove all DBRMs into packages in a collection. This job may be rerun whenever there are new PTF (replacement) DBRMs. 2. JCL - CEJOB07B Bind all plans to access all packages in a collection. This job need only be executed once. The difference between CEJOB07A and CEJOB07B is that CEJOB07A executes CLIST BINDPACK and CEJOB07B executes CLIST BINDPLAN. Both BINDPACK and BINDPLAN CLISTs take the same input parameters. Chapter 5: Creating a New Encyclopedia 5 7

78 Package Bind CEJOB07A BINDPACK The executable portion of sample JCL is shown next //JOBCARD... //* //* //* //TSOPROC PROC TILCLIB= CAI.MVSHE.CLIST, // SOUT= * //* //PS10 EXEC PGM=IKJEFT01,DYNAMNBR=30 //STEPLIB DD DSN=CAI.MVSHE.LOAD,DISP=SHR //SYSPROC DD DSN=&TILCLIB,DISP=SHR //SYSPRINT DD SYSOUT=&SOUT //SYSTSPRT DD SYSOUT=&SOUT // PEND //* //JS10 EXEC TSOPROC //PS10.SYSTSIN DD * %BINDPACK MEMBER(ALL) + (1) COLLID(XXXXXXXX) + (2) OWNER(2ND_AUTH) + (3) QUALIFIER(XXXXXXXX) + (4) RESTART (5) Note: MEMBER(ALL) Bind all DBRMs into packages in a collection. COLLID(XXXXXXXX) XXXXXXXX is the collection ID. A collection ID must be specified when performing a package bind. A value for the collection ID may be entered on the Set DB2 Variables screen of the CEINSTAL procedure and it will be added to the CEJOB07A JCL. OWNER(2ND_AUTH) A secondary authorization ID may be passed by adding an OWNER parameter and including a value for a secondary auth ID, for example: %BINDPACK MEMBER(ALL) OWNER(2ND_AUTH) A value for the secondary authorization ID may be entered on the Set DB2 Variables screen of the CEINSTAL procedure and it will be added to this JCL. 5 8 Installation Guide for Host Encyclopedia and Host Construction

79 Package Bind QUALIFIER(XXXXXXXX) The QUALIFIER parameter, QUALIFIER(XXXXXXX), may be passed to the BINDPACK CLIST. This value must be added manually, for example: %BINDPACK MEMBER(ALL)... QUALIFIER(XXXXXXX) RESTART This job can be restarted. In the event of a bind error, correct the error, then use the messages provided at the end of the failing BINDPACK CLIST to provide the package DBRM name as input via the MEMBER() parameter. Add the keyword RESTART. For example: %BINDPACK MEMBER(DBRMNAME)... RESTART CEJOB07B BINDPLAN (Only the executable portion of sample JCL is shown) //JOBCARD... //* //* //* //TSOPROC PROC TILCLIB= CA.MVSHE.CLIST, // SOUT= * //* //PS10 EXEC PGM=IKJEFT01,DYNAMNBR=30 //STEPLIB DD DSN=CA.MVSHE.LOAD,DISP=SHR //SYSPROC DD DSN=&TILCLIB,DISP=SHR //SYSPRINT DD SYSOUT=&SOUT //SYSTSPRT DD SYSOUT=&SOUT // PEND //* //JS10 EXEC TSOPROC //PS10.SYSTSIN DD * %BINDPLAN MEMBER(ALL) + (1) COLLID(XXXXXXXX) + (2) OWNER(2ND_AUTH) + (3) QUALIFIER(XXXXXXXX) + (4) RESTART (5) Note: MEMBER(ALL) Bind all plans to use all packages in a collection COLLID(XXXXXXXX) XXXXXXXX is the collection ID. A collection ID must be specified when performing a package bind. A value for the collection ID may be entered on the Set DB2 Variables screen of the CEINSTAL procedure and it will be added to the CEJOB07B JCL. Chapter 5: Creating a New Encyclopedia 5 9

80 Enable User Access OWNER(2ND_AUTH) A secondary authorization ID may be passed by adding an OWNER parameter and including a value for a secondary auth ID, for example: %BINDPLAN MEMBER(ALL) OWNER(2ND_AUTH) A value for the secondary authid may be entered on the Set DB2 Variables screen of the CEINSTAL procedure and it will be added to this JCL. QUALIFIER(XXXXXXXX) The QUALIFIER parameter, QUALIFIER(XXXXXXX), may be passed to the BINDPLAN CLIST. This value has to be added manually, for example: %BINDPLAN MEMBER(ALL)... QUALIFIER(XXXXXXX) RESTART This job can be restarted. In the event of a bind error, correct the error, then use the messages provided at the end of the failing BINDPLAN CLIST to provide the plan name as input via the MEMBER() parameter. Add the keyword RESTART, for example: %BINDPLAN MEMBER(DBRMNAME)... RESTART Enable User Access To enable user access, you must add each of your users to the Encyclopedia by selecting the user access control function from the Host Encyclopedia Functions Menu. Each user requires access to your site-specific ISPF/AllFusion Gen logon CLIST to establish the environment. Where Do You Go From Here? Your next step in installing the Host Encyclopedia is to populate the encyclopedia you just created. To copy existing Host Encyclopedia data tables from an earlier release of AllFusion Gen to an AllFusion Gen Host Encyclopedia, see Populating a Host Encyclopedia in this guide. If you are using Host Construction, see Testing Host Construction in the Host Encyclopedia Construction Guide. Applications generated and installed by AllFusion Gen r7 and later releases require PDSEs. So, if your next step is to use Host Construction, ensure that the Business System data sets specified for NCAL, Executable and RI Trigger compiled load modules are PDSEs. Likewise, if the External Action Block and External System Load Libraries are used, they must be created as PDSEs Installation Guide for Host Encyclopedia and Host Construction

81 Chapter 6: Upgrading an Encyclopedia in Place An upgrade is a complete redistribution of software libraries. This may alter some DB2 objects associated with existing AllFusion Gen Data, Schema, and Public Interface tables. Upgrading an existing encyclopedia to an AllFusion Gen r7.6 Encyclopedia consists of the following tasks: 1. Build SQL and JCL. 2. Run upgrade jobs. 3. Enable user access. This chapter describes how to perform these tasks. Prerequisites Before you proceed with upgrading an encyclopedia, you must complete the work from preceding chapters. You should have completed the DB2/DBA prerequisites of: 1. Starting the databases in Utility status for a consistent point of recovery. 2. Creating an image copy of Data, Schema, and Public Interface libraries. 3. Backing up the software libraries. 4. After the image copy, starting the databases in read or write status. You should have the Host Encyclopedia Maintenance Menu displayed on your monitor. Chapter 6: Upgrading an Encyclopedia in Place 6 1

82 Considerations Considerations Review these important considerations before you begin the upgrade tasks: The JCL and SQL for the upgrade process are in the JCL and SQL libraries. The options selected on the CEINSTAL Host Encyclopedia Maintenance Menu were: 2. Build Encyclopedia CLISTs (TIUGLOB, TIRCFIGS, TIXGLOB) 3. Build Sample Encyclopedia Utility JCL 6. Build JCL/SQL to Upgrade in Place The jobs must be run in the order they appear. Failure to do so causes unpredictable results. The DB2 database status must be read or write. It is recommended you use a new plan prefix. Each job must run on the CPU containing the Host Encyclopedia and the DB2 tables. Important! All models should be checked in, and an image copy of the Encyclopedia made, before beginning an upgrade in place. This establishes a recovery point, should one be needed. Build SQL and JCL Build the JCL and SQL that you execute to upgrade an existing encyclopedia to an AllFusion Gen Encyclopedia, using this procedure: 1. Select option 6 on the Host Encyclopedia Maintenance Menu and press Enter to start building the SQL and JCL. 2. When processing is complete, press Enter to return to the Host Encyclopedia Maintenance Menu. The AllFusion Gen JCL and SQL libraries now contain the JCL and SQL needed to upgrade existing Encyclopedias to AllFusion Gen r Installation Guide for Host Encyclopedia and Host Construction

83 Schema Release Levels Schema Release Levels Information in each model is controlled and processed in accordance with a specific schema release level, as defined in the schema database and the DMAX table of the Data database. When a software release defines new objects, properties, or associations that support new functionality, the schema release level changes. The table next shows the primary schema release level for the last major releases of AllFusion Gen: Release Schema 5.x 8.0.A A A Transition Guidelines The Host Encyclopedia provides full support for the current and immediately prior schema release levels ( 9.1.A5 and 9.0.A2). Transition support is available for the second prior schema release level (8.0.A3) to allow models using this schema to be brought up to date. The following rules and restrictions apply: Both 9.1.A5 and 9.0.A2 models can exist in the Host Encyclopedia. 9.0.A2 models in an encyclopedia can be used by Gen 6.x workstation toolsets, but not by AllFusion Gen r7, r7.5 and r7.6 workstation toolsets. 9.1.A5 models can be used with an AllFusion Gen r7, r7.5, and r7.6 workstation toolset. 9.1.A5 models cannot exist in any encyclopedia earlier than AllFusion Gen r A3 models can be loaded into an AllFusion Gen r7, r7.5, and r7.6 encyclopedia, but access is limited to deletion or conversion to a 9.1.A5 model. Any model containing a schema release prior to 8.0.A3 must be converted to 9.0.A2 or 8.0.A3 using an earlier version of the encyclopedia before it can be accessed from the AllFusion Gen r7.6 Encyclopedia. Chapter 6: Upgrading an Encyclopedia in Place 6 3

84 Model Conversion Model Conversion The AllFusion Gen r7.6 encyclopedia contains a model conversion utility to convert 9.0.A2 or 8.0.A3 models to the 9.1.A5 schema. The conversion updates the model schema and modifies the model s content to conform to the new schema. You must convert existing models to the 9.1.A5 schema, using the Encyclopedia Model Conversion utility, before they can be used on an AllFusion Gen r7, r7.5, and r7.6 workstation. For more information on the conversion utility, see the Host Encyclopedia Guide. 9.0.A2 models in an AllFusion Gen r7.6 Host Encyclopedia can be accessed by Gen 6.x workstation toolsets, but not by AllFusion Gen r7, r7.5, and r7.6 workstation toolset. The models must be converted to 9.1.A5 before they can be accessed by AllFusion Gen r7, r7.5, and r7.6 workstation toolsets. Cross-Model Functionality Some cross-model functionality is supported between the two schema release levels. Migration from a 9.0.A2 source model to a 9.1.A5 destination model is supported, with an implicit conversion of information, as required. That is, you can migrate from a 9.0.A2 to a 9.1.A5 model without repeating model conversion. Models in the 8.0.A3 schema may be uploaded or cross-copied into the AllFusion Gen Host Encyclopedia and converted to 9.1.A5. No other operations, except deletion, are supported for 8.0.A3 models. No operations are supported for models at earlier schema release levels. Dynamic Program Call Compatibility Feature To use the Dynamic Program Call Compatibility Feature, a model must be at schema release level 9.1.A5. However, even though models with a 9.1.A5 schema can be accessed by AllFusion Gen r7, r7.5 and r7.6 workstation toolsets, only the AllFusion Gen r7.6 workstation toolset is enabled to select or display Compatibility as the value of the Dynamically Link Packaging attribute associated with a procedure step, action block, or screen. 6 4 Installation Guide for Host Encyclopedia and Host Construction

85 Run Upgrade Jobs Run Upgrade Jobs These upgrades amend the z/os Host Encyclopedia DB2 tables so they work with the AllFusion Gen software. Use this table as a checklist as you run the following jobs. N/A is used if the job does not apply. JCL Name Description 6.5 to r7.6 r7 to r7.6 r7.5 to r7.6 CVJOB02 CEJOB03 Only if using VSAM allocation for DB2 data sets. Do not use if using STOGROUPs for DB2 data sets. n/a n/a Executes a DB2 BIND of the dynamic SQL program TIUUSQL to AllFusion Gen DB2 subsystem. You should bind this plan and grant DB2 EXECUTE authority to PUBLIC for each DB2 subsystem that is a target for AllFusion Gen-generated applications. You only need to bind TIUUSQL to other DB2 subsystems if you are using TIUUSQL to install DDL or to bind applications onto the subsystems. CVJOB04A Upgrades Host Encyclopedia in place from 6.5 to r7.6. CVJOB04B Upgrades Host Encyclopedia in place from r7/r7.5 to r7.6. n/a n/a n/a Chapter 6: Upgrading an Encyclopedia in Place 6 5

86 Run Upgrade Jobs JCL Name Description 6.5 to r7.6 r7 to r7.6 r7.5 to r7.6 CEJOB05 CAJOB05 Reloads schema tables with releases, 8.0.A3, 9.0.A2, and 9.1.A5. It uses IBM s DB2 LOAD utility. Reloads schema tables with releases 8.0.A3, 9.0.A2, and 9.1.A5. It uses CA s Fast Load utility. n/a n/a n/a n/a CEJOB05A Relaxes migration rules. optional n/a n/a CEUREOR CAUEROR Executes the DB2 REORG utility using IBM s REORG utility. It includes Data, Schema, and Public Interface databases. Same as above. It uses CA s REORG utility. CEUCOPY CAUCOPY Executes the DB2 COPY utility to create a full image copy of all tablespaces. It uses IBM s DB2 COPY utility. Same as above. It uses CA s DB2 QUICK COPY utility. CEJOB06 CAJOB06 Executes the DB2 RUNSTATS utility for the Host Encyclopedia schema tables. Same as above. This job uses CA s PDASTATS utility. CEJOB07A Binds all DBRMs into packages. CEJOB07B Binds all plans. CEJOB08 CEJOB09 CEJOB10 This job grants to PUBLIC, DB2 authority on all AllFusion Gen plans, and DB2 SELECT authority on Public Interface Table views. An SQLCODE of +562 indicates privileges have been granted. Updates the DMAX tables for the AllFusion Gen schema. Loads Schema Functions Model to Host Encyclopedia. n/a n/a n/a n/a 6 6 Installation Guide for Host Encyclopedia and Host Construction

87 Run Upgrade Jobs JCL Name Description 6.5 to r7.6 r7 to r7.6 r7.5 to r7.6 CEJOB11 Processes the Functions Model. This job inserts the model information into the schema SMDL table and deletes the model information from the data DMDL table. The expected return code is 20. To verify the Functions model is removed from the list of models, display the list of models by entering on the command line. Verify that IEF_SUPPLIED_FUNCTIONS is not on the list. n/a n/a CEJOB12 CEJOB13 Loads Sample Model to Host Encyclopedia. Loads Help Model to Host Encyclopedia. optional optional optional optional optional optional You must have IBM DB2 utilities or CA DB2 utilities or equivalent utilities from other vendors to execute the following jobs. If you are using utilities from other vendors, customize these jobs accordingly. CEJOB05 CAJOB05 CEJOB06 CAJOB06 CEUREOR CAUREOR CEUCOPY CAUCOPY If a new and improved sample installation model you want, submit CEJOB12 to load the Sample Model (SAMPMODL) for the current release. Chapter 6: Upgrading an Encyclopedia in Place 6 7

88 Enable User Access Enable User Access Existing user access is automatically enabled for this version of the encyclopedia. However, each user needs access to your site-specific ISPF/AllFusion Gen logon CLIST to establish the environment. Where Do You Go From Here? If you selected a new regional setting value or the Euro sign support, you must convert your models to the new code page. For regional setting value, see the appendix Setting Model Code Pages. For more information on copying any existing model to the new AllFusion Gen encyclopedia, see Populating a Host Encyclopedia. If you do not need to copy any existing models, but are using Host Construction, see the chapter Testing Host Encyclopedia Construction in the Host Encyclopedia Construction Guide. Applications generated and installed by AllFusion Gen r7, r7.5, and r7.6 require PDSEs. So, if your next step is to use Host Construction, ensure that the Business System data sets specified for NCAL, Executable and RI Trigger compiled load modules must be PDSEs. Likewise, if the External Action Block and External System Load Libraries are used, they must be created as PDSEs. If you are developing applications that employ online help, see the chapter Installing the Help Model in the Host Encyclopedia Construction Guide. 6 8 Installation Guide for Host Encyclopedia and Host Construction

89 Chapter 7: Populating a Host Encyclopedia When you have created or upgraded a Host Encyclopedia, you may want to populate the encyclopedia with existing models and data from another encyclopedia. You can do this by either copying data tables or copying complete models or a combination of the two. This chapter describes the tasks involved in both processes. Copying Data to a Host Encyclopedia When you copy data tables, the copy includes subset, version control and security data. The only tables not included in copying existing data to a new encyclopedia are the public interface tables and the schema tables. The Public Interface Export function must be run to re-populate the Public Interface tables. This section explains the tasks required to copy existing data tables to a new AllFusion Gen Host Encyclopedia. These tasks are: Build JCL and SQL Run UNLOAD and LOAD Enable User Access Prerequisites Before you upgrade an encyclopedia, you must complete the work from the preceding chapters. If you have any questions or doubts about the preceding work, review chapters 1 through 5. Before you start, log on to the Host Encyclopedia that is the target for the data tables you are copying and display the Encyclopedia Maintenance Menu. Chapter 7: Populating a Host Encyclopedia 7 1

90 Build JCL and SQL Build JCL and SQL The following procedure uses CEINSTAL to build the JCL and SQL to unload and load the Encyclopedia Data tables. 1. Select option 5 on the Encyclopedia Maintenance Menu and press Enter to display the following screen. Identify Source and Target Encyclopedias COMMAND => It is assumed you are logged onto the Host Encyclopedia that is the target for the Host Encyclopedia Data Tables copy operation. Enter the following information about the source encyclopedia and target encyclopedia. Then press ENTER. Encyclopedia DB2 variables: Source Target Table creator ID... DD (*1) DBIEF67 (*2) DB2 subsystem ID... DD (*1) DSN (*2) *1 These values are entered into JCL as is. *2 If no creatorid has been assigned, a default CREID@40 is assigned. Both values picked up from installation variables. Note: If both source and the target Host Encyclopedias exist on the Same DB2 subsystem, the Table Creator Ids cannot be equal. F1 Help F3 - Exit 2. Enter values for the Source fields and verify the values in the Target fields. (The values for the Target fields derive from the values entered earlier on the Set DB2 Variables screen.) Note: Do not change the values in the Target fields. If these values are incorrect, you are logged on to the wrong Encyclopedia, or the information used to build the Encyclopedia was entered incorrectly in the Set DB2 Variables screen. 3. Press Enter to start building the JCL. 4. When processing is complete, press Enter and the Host Encyclopedia Maintenance Menu reappears. 7 2 Installation Guide for Host Encyclopedia and Host Construction

91 Unload and Load Unload and Load After completing the preceding task, there is load and unload JCL and SQL in the AllFusion Gen JCL and SQL libraries. To complete the unload and load procedure successfully, you must: Check in all models before executing Step 1 of this procedure. Execute the steps of this task in the order in which they appear. Execute each step on the CPU that contains the Host Encyclopedia. Perform the following jobs to complete the unloading and loading of the data tables. Use this table as a checklist as you run the jobs. JCL Name Description HEIUNLD HE2LOAD CEUREOR CEUCOPY CEJOB06 CEJOB07A CEJOB09 Unloads a copy of the existing encyclopedia data tables. Loads the existing encyclopedia data tables into the new Host Encyclopedia. Executes the DB2 REORG utility. If this job fails, there is no restore; you must reload all data tables by re-running HE2LOAD. Executes the DB2 COPY utility and creates a full image copy of all tablespaces. This is required to activate new tables because HE2LOAD runs with LOG NO. Executes the DB2 RUNSTATS utility for the encyclopedia tables. Executes a DB2 BIND of the AllFusion Gen packages to take advantage of the RUNSTATS statistics from CEJOB06. Updates the DMAX table for the new schema. This job replaces the new encyclopedia name in the DMAX table with the name of the old encyclopedia. You need to update MAX_RELEASE with the new encyclopedia s name. To avoid cross-encyclopedia contention, find the row with ENCYNAME in the first column (MAX_MNEMONIC), update MAX_RELEASE with the new encyclopedia name. Chapter 7: Populating a Host Encyclopedia 7 3

92 Unload and Load JCL Name Description CEJOB10 Loads the Functions model to the new encyclopedia (required): Model name: IEF_SUPPLIED_FUNCTION in the data set CAI.MVSHE.TRAN(FUNC91A5). CEJOB10 may return a condition code of 0 even if it fails. To verify, the Functions model has been added to the list of models, display the AllFusion Gen Main Menu, enter on the command line, and press Enter. On the Model Statistics screen, move the cursor to the Model Name field and press F4 to display the list of models. Verify the Functions model appears on the list. If the model is missing, look for an error message in userid.ief.logfile. If CEJOB10 abends with U3001 ONCODE 84 when SYSPRINT is Allocated, the userid.ief.sysprint data set is unavailable. To correct the error, navigate out of AllFusion Gen concatenation, issue a FREE DA (userid.ief.sysprint) command, delete any added models, and resubmit CEJOB10. CEJOB11 Processes the Function Model. This job inserts the model information into the schema SMDL table and deletes the model information from the data DMDL table. The expected return code is 20. To verify that the Functions model is removed from the list of models, display the list of models as in Footnote b and check that IEF_SUPPLIED_FUNCTIONS is not on the list. CEJOB12 Loads the Sample model to the new encyclopedia (optional): Model name: GEN SAMPLE MODEL R76 in the data set: CAI.MVSHE.TRAN(SAMPMODL) CEJOB12 may return a condition code of 0 even if it fails. To verify the model has been added to the list of models, display the AllFusion Gen Main Menu, enter on the command line, and press Enter. On the Model Statistics screen, move the cursor to the Model Name field and press F4 to display the list of models. Verify the Sample model appears on the list. If the model is missing, look for an error message in userid.ief.logfile. If CEJOB12 abends with U3001 ONCODE 84 when SYSPRINT is Allocated, the userid.ief.sysprint data set is unavailable. To correct the error, navigate out of AllFusion Gen concatenation, issue a FREE DA (userid.ief.sysprint) command, delete any added models, and resubmit CEJOB Installation Guide for Host Encyclopedia and Host Construction

93 Enable User Access JCL Name Description CEJOB13 Loads the Help model to the new encyclopedia (optional): Model name: GEN SAMPLE HELP MODEL R76 in the data set: CAI.MVSHE.TRAN (HELPMODL) CEJOB13 may return a condition code of 0 even if it fails. To verify the model has been added to the list of models, display the AllFusion Gen Main Menu, enter on the command line, and press Enter. On the Model Statistics screen, move the cursor to the Model Name field and press F4 to display the list of models. Verify the Help model appears on the list. If the model is missing, look for an error message in userid.ief.logfile. If CEJOB13 abends with U3001 ONCODE 84 when SYSPRINT is Allocated, the userid.ief.sysprint data set is unavailable. To correct the error, navigate out of AllFusion Gen concatenation, issue a FREE DA (userid.ief.sysprint) command, delete any added models, and resubmit CEJOB13. Enable User Access To enable user access, you need to add each of your users to the encyclopedia by selecting the user access control function from the Host Encyclopedia Functions Menu. Each user needs access to your site-specific ISPF/AllFusion Gen logon CLIST to establish the environment. Chapter 7: Populating a Host Encyclopedia 7 5

94 Display License Information Display License Information Verify that appropriate Host Encyclopedia and Construction licenses are installed on the current system. This task can be performed by choosing option 5.4 from the Host Encyclopedia Main Menu. The following example illustrates the license status at a site using the Host Encyclopedia and Host Construction, with the target generation environment CICS. COMMAND ===> License Information Product Encyclopedia Server Construction Server Environment Options CICS Environment Options IMS License Status Product is licensed Product is licensed Product is licensed Product is not licensed F1=Help F3=Exit F12=Cancel Note: If a licensed product does not show as licensed, contact the CA Total License Care group. Their information is posted on the CA website under CA Support Resources. Copying Models to a Host Encyclopedia There are two methods of copying models between Host Encyclopedias: Download from source encyclopedia, and then upload to target Encyclopedia. Cross-copying. The download from source is the preferred method and should be used whenever possible. Both methods preserve the original model s name, objects, properties, and associations; neither method copies subsets, common ancestry, and user access information. The two copy methods are explained in this section. 7 6 Installation Guide for Host Encyclopedia and Host Construction

95 Copying Models to a Host Encyclopedia Download/Upload Method The following procedure the download/upload method for copying models to a host encyclopedia. 1. From the AllFusion Gen Main Menu of the SOURCE host encyclopedia, select 1 for Host Encyclopedia functions. 2. Select 2 for Model Management and the following screen displays: COMMAND ===> Model Management Select one of the options below, then press enter: 1. Copy model 2. Copy model across encyclopedias 3. Delete or rename objects within model 4. Delete entire model 5. Display model statistics 6. Check model for consistency 7. Rename model 8. Create new model from existing subset 9. Override checkout status for model 10. Backup and restore model utilities 11. Model conversion utilities 12. Model history 13. Model reports 14. Change model checkout user ID 15. Download model 16. Upload model F1=Help F3=Exit F12=Cancel 3. Select 15. Download Model, to display the following screen. COMMAND ===> Download Model Type the Model name or request Prompt for list selection. Type the Software version. Type the name of the download transaction file WITHOUT your TSOID prefix if you want to override the default. You may select the Upload option or Extract Option but not both. Type the Codepage. Select an Execution mode, and then press enter. Model name Software version Transaction file name. IEF.TRAN Upload option /No. Yes Extract option /No. Yes Child ency id Child model name (blank if same as parent) Codepage Execution mode / Online. Batch F1=Help F3=Exit F4=Prompt F12=Cancel Chapter 7: Populating a Host Encyclopedia 7 7

96 Copying Models to a Host Encyclopedia 4. Enter the name of the model you want to copy to another encyclopedia. Set the upload option to YES and specify the code page appropriate to your DB2 system. This function creates records in your IEF.TRAN file, in a format that is suitable for upload to the target encyclopedia. 5. Access the AllFusion Gen Main Menu of the TARGET host encyclopedia. 6. Select 1, then 3, as before, to display the Model Management menu. 7. Select 16. Upload Model, to display the following screen. COMMAND ===> Upload Model/Subset Type the name of the upload transaction file WITHOUT your TSOID prefix if you want to override the default. Select an execution mode, and then press enter. Transaction file name. IEF.TRAN Execution mode. / Online. Batch F1=Help F3=Exit F12=Cancel 8. Press Enter and the model is generated, as new, into the TARGET host encyclopedia. 7 8 Installation Guide for Host Encyclopedia and Host Construction

97 Cross-Copying Models Cross-Copying Models If it is not possible to use the Download/Upload method of copying models, you can copy models between Encyclopedias using the CLIST TIEXCPY. Before you use TIEXCPY, you must modify it to point to the source and the target encyclopedias. The following procedure explains how to modify TIEXCPY, with examples. 1. Set the DB2 plan prefixes and load libraries for both the source and the target Encyclopedias. 2. Configure TIEXCPY for the Host Encyclopedia initiating the cross-copy. This is the encyclopedia that you are logged on to when you request cross-copy and is the source Encyclopedia. (The target encyclopedia s CLIST does not need to be modified.) The following steps explain how to configure TIEXCPY. a. Locate the following statements in TIEXCPY: IF &E1PLPR=PRX1 THEN SET &E1LLIB=LOAD.DSN.FOR.PREFIX1 IF &E1PLPR=PRX2 THEN SET &E1LLIB=LOAD.DSN.FOR.PREFIX2 b. Modify the lines beginning with IF &E1PLPR to indicate the source encyclopedia: Change each PRXn to the source encyclopedia s plan ID. Change each LOAD.DSN.FOR.PREFIX# to the load library for the source encyclopedia. Note: In TSO, type %IEFVARS to find the plan prefix and load library. The information is in CLIST TIUGLOB. The plan prefix is in TIUPLPR and the load library is in TIULOADP. c. Locate the following statements in TIEXCPY: IF &E2PLPR=PRX1 THEN SET &E2LLIB=LOAD.DSN.FOR.PREFIX1 IF &E2PLPR=PRX2 THEN SET &E2LLIB=LOAD.DSN.FOR.PREFIX2 d. Modify the lines beginning with IF &E2PLPR to indicate the source encyclopedia: Change each PRXn to the target encyclopedia s plan ID. Change each LOAD.DSN.FOR.PREFIX# to the load library for the target encyclopedia. Chapter 7: Populating a Host Encyclopedia 7 9

98 Where Do You Go From Here? Example 1 Encyclopedia EN01 copies to Encyclopedia EN02; EN01 initiates the crosscopy. TIUGLOB (for Encyclopedia EN01) TIUPLPR=EN01 TUILOADP=AAAC.IEF40.LOAD TIUGLOB (for Encyclopedia EN02) TIUPLPR=EN02 TUILOADP=AAAC.IEF50.LOAD TIEXCPY: SET &E1LLIB = &STR() IF &E1PLPR=EN01 THEN SET &E1LLIB=AAAC.IEF40.LOAD IF &E1PLPR=PRX2 THEN SET &E1LLIB=load.dsn.for.prefix2 IF &E2PLPR=EN02 THEN SET &E2LLIB=AAAC.IEF50.LOAD IF &E2PLPR=PRX2 THEN SET &E2LLIB=load.dsn.for.prefix2 Example 2 Encyclopedia EN01 copies to Encyclopedia EN02 or EN03; EN01 initiates the cross-copy. TIUGLOB (for Encyclopedia EN01) TIUPLPR=EN01 TUILOADP=AAAC.IEF40.LOAD TIUGLOB (for Encyclopedia EN02) TIUPLPR=EN02 TUILOADP=AAAC.IEF50.LOAD TIUGLOB for Encyclopedia EN03: TIUPLPR=EN03 TUILOADP=AAAC.IEF.LOAD TIEXCPY: SET &E1LLIB = &STR() IF &E1PLPR=EN01 THEN SET &E1LLIB=AAAC.IEF40.LOAD IF &E1PLPR=PRX2 THEN SET &E1LLIB=load.dsn.for.prefix2 IF &E2PLPR=EN02 THEN SET &E2LLIB=AAAC.IEF50.LOAD IF &E2PLPR=EN03 THEN SET &E2LLIB=AAAC.IEF.LOAD Where Do You Go From Here? Your encyclopedia is now ready for use. For in-depth information about Encyclopedia maintenance and administration, see the Host Encyclopedia Performance Guide. Application generated and installed by AllFusion Gen r7, r7.5, and r7.6 require PDSEs. So, if your next step is to use Host Construction, ensure that the Business System data sets specified for NCAL, Executable and RI Trigger compiled load modules must be PDSEs. Likewise, if the External Action Block and External System Load Libraries are used, they must be created as PDSEs Installation Guide for Host Encyclopedia and Host Construction

99 Chapter 8: Installing the z/os API The AllFusion Gen z/os API provides a set of (C++ based) subroutines to access schema, model, and administrative information in the Host Encyclopedia. The z/os API is useful for either the customers or CA Partners who require access to the Host Encyclopedia s internal data outside of the Host Encyclopedia software. The z/os API is sold and installed separately from the Host Encyclopedia. The z/os API is available in a zip file on a Windows compatible CD and contains READ and UPDATE functionalities. Important! When using the UPDATE functionality, extreme caution is advised. The z/os API interface does not provide data recovery facilities. The IBM utility TRSMAIN (also referred to as the TERSE utility by IBM) is required to install all CA AllFusion Gen products and PTFs. If your site has this utility available, copy it into the AllFusion Gen LOAD data set. If your site does not have this utility, use the following URL address to obtain the TRSMAIN (TERSE) utility, and then copy it into the AllFusion Gen LOAD data set. The TRSMAIN/TERSE is a free/copyrighted IBM utility and thus, cannot be redistributed. The utility can only be downloaded from IBM by each individual customer. Preparing for Installation The z/os Host Encyclopedia API provides a set of (C++ based) subroutines to read the schema and administrative information and read and update the model information in the Host Encyclopedia. These functions are provided as a static library along with additional development files. The JCL data set contains members: API01, API02 and API03. These members provide information and sample JCL for compiling, linking, binding, and executing a sample z/os application. Preparing for the installation of the Encyclopedia API on the z/os operating system consists of the following tasks: 1. Meet the prerequisites for installation defined on the Encyclopedia API Installation Checklist. 2. Upload and Install from the CD Chapter 8: Installing the z/os API 8 1

100 Upload and Install the API Upload and Install the API The steps you need to complete for installing the API is listed next. This installation assumes you are using a Windows compatible Workstation. Workstation directories and z/os data set prefixes are provided as examples. For more information on how to complete these steps, see "Preparing for Installation. 1. Obtain the AllFusion Gen Encyclopedia Server Update API for z/os CD. The CD contains a zip file named GenAPIr76.zip. 2. Expand the zip file from the CD onto the Workstation. Copy the GenAPIr76.zip file from the CD onto the Workstation. Extract the contents of the file to: C:\genapi\GenAPIr76.ctl (Install-Control) C:\genapi\GenAPIr76.mvs (Install-File) C:\genapi\GenAPIr76.txt (Install Readme file) 3. Allocate INSTJCL file on TSO. Allocate installation JCL data sets on z/os as follows: Data set name : cai.mvsapi.instjcl LRECL = 80 DSORG = PO RECFM = FB 4. Transfer the Install Control File from the Workstation to z/os. Transfer the Install Control File, in BINARY, from the Workstation to z/os. The GenAPIr76.ctl file needs to be transferred from c:\genapi to cai.mvsapi.instjcl(apinst0). 5. Customize JCL APINST0. Add Jobcard and customize the JCL cai.mvsapi.instjcl(apinst0) (See instructions inside JCL). Submit the JCL member APINST0 to create the following three new JCL members: 'cai.mvsapi.instjcl(apinst1)' 'cai.mvsapi.instjcl(apinst2)' 'cai.mvsapi.instjcl(apinst3)' This job should end with a COND CODE =0 6. Customize JCL APINST1. Add Jobcard and customize JCL cai.mvsapi.instjcl(apinst1) (See instructions inside JCL). 8 2 Installation Guide for Host Encyclopedia and Host Construction

101 Upload and Install the API Submit the JCL member APINST1 to allocate z/os data set : cai.mvsapi.instfile This job should end with a COND CODE =0 7. Transfer Install File from the Workstation to z/os Transfer (ftp) the Install-File, in BINARY, from the Workstation to z/os. The GenAPIr76.mvs file needs to be transferred from C:\genapi to 'cai.mvsapi.instfile'. 8. Expand the INSTFILE data set into a PDS. Add jobcard and customize JCL cai.mvsapi.instjcl(apinst2) (See instructions inside JCL). Submit the JCL to read as input : 'cai.mvsapi.instfile' (A sequential data set) write out: 'cai.mvsapi.instpds'. (A partitioned data set) The job should end with a COND CODE = 0 9. Expand the INSTPDS file members into z/os Data sets. Add jobcard and customize JCL cai.mvsapi.instjcl(apinst3) (See instructions inside JCL). Submit JCL member APINST3 to read each member of the cai.mvsapi.instpds data set and create z/os AllFusion Gen installation data sets cai.mvsapi.xxxxxx. This job should end with a COND CODE =0 Read as Input 'cai.mvsapi.instpds(a#jclxxx)' 'cai.mvsapi.instpds(a#cxxxxx)' 'cai.mvsapi.instpds(a#hxxxxx)' 'cai.mvsapi.instpds(a#dbrmxx)' 'cai.mvsapi.instpds(a#objcxx)' 'cai.mvsapi.instpds(a#objasm)' 'cai.mvsapi.instpds(a#loadxx)' Create AllFusion Gen Data set 'cai.mvsapi.jcl' 'cai.mvsapi.c' 'cai.mvsapi.h' 'cai.mvsapi.dbrm' 'cai.mvsapi.objc' 'cai.mvsapi.objasm' 'cai.mvsapi.sampload' Note: All Gen LOAD data sets are installed as PDSE (DSNType=LIBRARY) and must stay that way. Chapter 8: Installing the z/os API 8 3

102

103 Appendix A: Sizing an Encyclopedia This chapter explains the AllFusion Gen Host Encyclopedia size, how to estimate larger encyclopedia sizes, creating storage group parameters and VSAM parameters. DASD Requirements The Host Encyclopedia requires a minimum of cylinders. Of that total, 350 cylinders are for the Host Encyclopedia and 300 cylinders are for AllFusion Gen software libraries. You can control the amount of DB2 DASD by allocating for a small or medium size Host Encyclopedia. For better performance, you should allocate the tables and indexes across 3 to 6 volumes. The number of 4 KB pages for a small Host Encyclopedia is: VOL 4 KB Page Many installations put all Host Encyclopedia data sets on the same volume, but relocate the high-use tablespaces and indexes to separate volumes. Appendix A: Sizing an Encyclopedia A 1

104 Sizing an Encyclopedia Sizing an Encyclopedia This section explains the encyclopedia size and how to estimate larger encyclopedia sizes. AllFusion Gen Encyclopedias Initially, AllFusion Gen provides two Encyclopedia sizes: A small Encyclopedia is 350 cylinders (3390). A medium Encyclopedia is 1400 cylinders (3390). All tables or indexes are the same in the small and medium encyclopedias except for the following, which are seven times larger in the medium Encyclopedia than in the small Encyclopedia: DASC DOBJ DPRP DSUBEX If you need a larger encyclopedia, this section explains how to resize the tables to fit your requirements. Note: Large encyclopedias can be as large as 10,000 cylinders or more. How to Estimate Larger Encyclopedia Sizes This section defines which tables need resizing to accommodate a larger encyclopedia and how to estimate the size of the encyclopedia. Schema Tables These AllFusion Gen tables are never resized by users: SASC SDIV SMDL SOBJ SPRP STRG A 2 Installation Guide for Host Encyclopedia and Host Construction

105 Sizing an Encyclopedia Small User Data Tables that Remain Static The following tables are considered small and usually remain static: DCOPY DMDL DSUBDF DCPYUS DSETDF DSUBID DFAMILY DSETID DSUBUS DGRPUS DUSR DXCPID DMAX User Data Tables that Vary in Size The sizes of the following user data tables depend on usage: DHLOG Model history activity logging. When logging is enabled, archive this table frequently to keep it small. DHOBJ Object history activity logging. When logging is enabled, archive this table frequently to keep it small. DTXT Bulk of data is descriptions inside model. This table may grow as the use of descriptions increases. You can disable DHLOG and DHOBJ for each model by using Host Encyclopedia option Large Data Tables The following tables need to grow as encyclopedia usage increases: DASC DOBJ DPRP DSUBEX Public Interface Table Sizes The Public Interface (PI) tables should be sized according to the use of PI feature: MODEL PIDATA PINAME PITEXT Appendix A: Sizing an Encyclopedia A 3

106 Sizing an Encyclopedia Encyclopedia Estimating Methods Use one of the following methods to estimate a large encyclopedia. Method One Look at the table sizes of an encyclopedia already installed on your system to estimate the space needed for a larger encyclopedia. Method Two Use the relative sizes of the major tables, as shown next. The relativity is based on analyses of several large production Host Encyclopedias. Table Index 1 Index 2 Index 3 DOBJ 30% 40% 40% DASC 50% 50% Not applicable DPRP 16% Not applicable Not applicable DSUBEX 40% 40% Not applicable DTXT 15% Not applicable Not applicable DHLOG 10% Not applicable Not applicable DHOBJ 10% Not applicable Not applicable MODEL 40% 40% Not applicable PIDATA 40% 40% 50% PINAME 25% 20% Not applicable PITEXT 25% 20% Not applicable Using the information in this table, estimate the number of objects and divide by 70 to get the size of the DOBJ table (in 4 KB pages). Calculate the sizes of the DASC, DPRP, and DSUBEX tables: DASC = 1.7 X (DOBJ value) DPRP = 1.7 X (DOBJ value) DSUBEX = 1.0 X (DOBJ value) The factor for DSUBEX is a minimum. If subsetting is not used, or is low, 1.0 is adequate; otherwise, this value needs to be larger. A 4 Installation Guide for Host Encyclopedia and Host Construction

107 Sizing an Encyclopedia Example 50 Models x 30,000 Objects/Model = approximately 1,500,000 Objects 1,500,000 divided by 70 = approximately 22,000 4K DOBJ pages DASC = 1.7 * 22,000 = approximately 36,000 DPRP = 1.7 * 22,000 = approximately 36,000 SUBEX = 1.5 * 22,000 = approximately 33,000 DOBJ = 22,000 (see above) Table Index 1 Index 2 Index 3 DOBJ 22,000 7,000 9,000 9,000 DASC 36,000 18,000 18,000 N/A DPRP 36,000 6,000 N/A N/A DSUBEX 22,000 13,000 13,000 N/A Method Three The following tables show the number of 4 KB pages allocated for the Schema, Data and Public Interface tables or indexes for a small and a medium Host Encyclopedia. (If Storage Group is selected, AllFusion Gen automatically multiplies each value by four when the DDL is generated.) The sizes of the following tables or indexes depend on the number and sizes of models. Table/Index Small Medium DASC DASCI DASCI DOBJ DOBJI DOBJI DPRP DPRPI DPRPI Appendix A: Sizing an Encyclopedia A 5

108 Sizing an Encyclopedia Table/Index Small Medium DSUBEX DSUBEXI DSUBEXI You may need to adjust the sizes of the following tables or indexes: Table/Index Small or Medium DHOBJ 1500 DHOBJI1 150 DHLOG 2500 DHLOGI1 500 DHLOGI2 500 DHLOGI DTXT 6000 DTXTI1 325 The values of the following table or indexes are constant. Table/Index Small, Medium, or Large DCOPY 150 DCOPYI1 150 DCOPYI2 150 DCPYUS 65 DCPYUSI1 10 DCPYUSI2 10 DFAMLY 65 DFAMLYI1 20 DFAMLYI2 20 DGRPUS0 65 DGRPUSI1 5 DGRPUSI2 5 DMAX 65 A 6 Installation Guide for Host Encyclopedia and Host Construction

109 Sizing an Encyclopedia Table/Index Small, Medium, or Large DMDL 65 DMDLI1 12 DMDLI2 24 DSETDF 400 DSETDFI1 400 DSETID 65 DSETIDI1 30 DSETIDI2 30 DSETIDI3 30 DSUBDF 400 DSUBDFI1 100 DSUBDFI2 100 DSUBID 65 DSUBIDI1 20 DSUBIDI2 20 DSUBUS 65 DSUBUSI1 10 DSUBUSI2 10 DUSR 65 DUSRI1 5 DXCPID 65 DXCPIDI1 5 The size of the following table or indexes depends on Public Interface usage. Table/Index Small or Medium MODEL 65 MODELI1 10 MODELI1 10 MODELI PIDATA 400 Appendix A: Sizing an Encyclopedia A 7

110 Sizing an Encyclopedia Table/Index Small or Medium PIDATAI1 400 PIDATAI2 400 PIDATAI3 400 PINAME 100 PINAMEI2 80 PITEXT 1000 PITEXTI1 250 PITEXTI2 250 The following schema tables do not need resizing. Table/Index Small or Medium SASC 600 SASCI1 300 SASCI2 300 SASCI3 300 SDIV 600 SDIVI1 300 SDIVI2 300 SMDL 65 SMDLI10 5 SMDLI2 5 SOBJ 300 SOBJI1 300 SOBJI2 300 SPRP 600 SPRPI1 300 SPRPI2 300 STRG 600 STRGI1 300 A 8 Installation Guide for Host Encyclopedia and Host Construction

111 Sizing an Encyclopedia How to Create Storage Group Parameters The Assign Storage Group Names screen shows the CEINSTAL screen for creating STOGROUP space parameters. The default values are expressed in 1 KB records, which are four times larger than VSAM values. A sample SQL that Creates DASC is shown next CREATE TABLESPACE DASC IN DBIEF67D USING STOGROUP SYSDEFLT PRIQTY SECQTY LOCKSIZE ANY SEGSIZE 64 CLOSE NO; How to Create VSAM Parameters The Assign VSAM Names screen illustrates the CEINSTAL screen for creating VSAM space parameters. The default values are expressed in 4 KB pages. A JCL to create space for table DASC is shown next. DEFINE CLUSTER + (NAME( AAAC.DSNDBC.DBIEF67D.DASC.I0001.A001 ) + LINEAR + REUSE + VOL (XXXXXX) + RECORDS ( ) + SHR (3,3) ) + DATA + (NAME( AAAC.DSNDBD.DBIEF67D.DASC.I0001.A001 )) CREATE TABLESPACE DASC IN DBIEF67D USING VCAT AAAC LOCKSIZE ANY SEGSIZE 64 CLOSE NO; Appendix A: Sizing an Encyclopedia A 9

112

113 Appendix B: Configuring IMS and CICS If the target environment for AllFusion Gen generated application is IMS or CICS, you must configure that environment appropriately before deploying the application. This appendix explains how to configure IMS and CICS for AllFusion Gen applications. Before you configure IMS or CICS for AllFusion Gen applications, confirm the following has been done: The CICS or IMS execution environment has been established according to the AllFusion Gen Technical Requirements. The Technical Requirements document is found in the Product Information section of the AllFusion Gen Product home page, which is accessible from CA SupportConnect website ( If the application generated by AllFusion Gen is the first software to use the DB2 Attachment Facility from within CICS or IMS, make sure the Installation Verification Procedure (IVP) COBOL application has been installed and executed. (IVP COBOL is supplied on the DB2 installation tape; see your IBM documentation for instructions.) This section covers Block Mode Support for IMS and CICS, Client/Server Support for both IMS and CICS and Debugging features for both IMS and CICS. Runtime DLLs and LE AllFusion Gen z/os runtime comprises of a multi-language execution environment made up of C, COBOL, and Assembler code. In AllFusion Gen r7, the C components of the runtime were converted to IBM C. This conversion allowed AllFusion Gen to support dynamic linking of runtime and the use of DLLs, which was done in AllFusion Gen r7.5. Most Assembler and COBOL runtimes are implemented as DLLs. Since these runtimes are dynamically loaded, a single copy of the runtime is shared by multiple processes. The overall load module size for an AllFusion Gen application decreases significantly. AllFusion Gen r7.5 offered improved serviceability from prior releases by letting you update the runtime without requiring that the maintenance items be statically linked into every generated application. Maintenance applied to a DLL is available to all generated applications that use the DLL. Appendix B: Configuring IMS and CICS B 1

114 AllFusion Gen requires PDSE In AllFusion Gen r7.5, the z/os runtime was updated to full IBM LE conformance. These runtimes were updated to use the standard LE call interface which reduced the complexity of the runtime code. The runtimes were made fully re-entrant and threadsafe, which enhanced the reliability and performance of the runtime and the generated applications they support. AllFusion Gen runtimes were changed to exploit LE storage management within the assembler routines, eliminating the need for frequent calling of GETMAIN and FREEMAIN. This reduced CPU usage for runtime modules within certain generated applications, such as batch jobs. AllFusion Gen s C and COBOL runtimes were changed to use similar functionality. Migrating AllFusion Gen s Assembler code to LE functionality decreased the number of OS storage calls resulting in a decrease use of CPU when a generated application invokes the various Assembler runtime functions. The benefit of this change depends on your LE heap and stack settings and how each generated application uses these runtimes (block mode versus batch versus distributed processing server). AllFusion Gen requires PDSE AllFusion Gen runtimes are supplied as Program Objects and must reside in PDSE library (data set type of LIBRARY). The installation jobs provided with the Host Encyclopedia create PDSE data sets for AllFusion Gen LOAD and LOADTRCE libraries. The generated code is also installed as Program Objects so that the Business System data sets specified for NCAL, Executable and RI Trigger Compiled load modules must be PDSEs. Likewise, the External Action block and the External System Load Libraries, if used, must be created as PDSEs. Threadsafe Since CICS/TS 1.3, all user programs defined in CICS have a concurrency attribute of either Quasirent or Threadsafe. In CICS terms, Quasirent indicates that the program requires CICS protection when using sharable resources while threadsafe means that the program handles concurrent access of shared resources in a way that maintains data integrity. CICS uses the concurrency attribute in conjunction with information about the CICS API commands to decide under which TCB to execute the program, switching between TCBs if necessary. B 2 Installation Guide for Host Encyclopedia and Host Construction

115 Threadsafe In CICS/TS 2.2, IBM modified the task-related user exit used by the CICS-DB2 attachment facility so that it executes as threadsafe and has started to modify the CICS API commands to make them threadsafe. However not all CICS API commands have been made threadsafe. CICS starts all tasks using the quasirent TCB and when the program associated with a task executes a SQL command CICS changes the task to the threadsafe TCB. After the SQL command is completed CICS decides on what TCB to continue executing the task based on the concurrency attribute of the executing program and of the CICS API command, if applicable. When the program is defined as quasirent CICS switches the task to the quasirent TCB where it remains until the next SQL command is executed. When the program is defined as threadsafe the task continues executing in the threadsafe TCB until the next non-threadsafe CICS API command is executed. This means that applications that access DB2 resources and are defined as quasirent are forced to do TCB switching. This TCB switching has an impact on the application's overall performance. The Advantage Gen 6.5 CICS runtime is not threadsafe. Advantage Gen 6.5 CICS applications fail with a variety of 0Cx abends if defined as threadsafe so the concurrency attribute of quasirent must be used. In AllFusion Gen r7 the z/os runtimes were made threadsafe. AllFusion Gen applications installed using runtimes from AllFusion Gen r7, r7.5, and r7.6 should be defined as threadsafe and will operate without abending. To benefit from reduced TCB switching the AllFusion Gen DB2 Dynamic Plan Exit TIRC$EXT must also be defined as threadsafe, if used. The DB2 Dynamic Plan Exit is used for plan selection when the Gen CICS option 'XCTL for Flows' is selected. AllFusion Gen programs execute the non-threadsafe API commands at the start of each program (to receive/retrieve the input data) and at the end (to send/xmit the response) while the SQL calls are combined together. So defining AllFusion Gen programs as threadsafe will reduce TCB switching compared to the same programs being defined as quasirent. This applies to both statically and dynamically linked Gen applications. There are a few things to notice: The CICS-DB2 Attach Dynamic Plan Exit TIRC$EXT MUST be defined as threadsafe for applications to benefit from the reduction in TCB switching. TCP/IP DC programs for CICS - TILSTNR and TICONMGR should be defined as quasirent but since these programs do not access DB2 this has no impact. CICS Sockets server programs - TISRVLIS and TIRSLEXT should be defined as quasirent but since these programs do not access DB2 this has no impact. Appendix B: Configuring IMS and CICS B 3

116 Install Gen Runtime Load Library Modules Transaction Dispatcher for CICS - TIRMQTDC does not access DB2, so should be defined as quasirent but since it does not access DB2 this has no impact. If you use EABs remember to place the SQL calls as close together as possible, or at least without interspersing with CICS API non-threadsafe commands. CICS applications that target DBMS Datacom do not use the CICS-DB2 attachment facility so should be defined as quasirent. Install Gen Runtime Load Library Modules After the AllFusion Gen software is uploaded to the z/os platform, the CICS and IMS environments must be configured such that the target CICS or IMS execution environment can access the AllFusion Gen runtime software modules. Execution Load Library: IMS The AllFusion Gen runtime modules must be made available to the target IMS system as part of the IMS STEPLIB data set concatenation. Either add the AllFusion Gen r7.6 load library (ISPLLIB) to the concatenation or copy the relevant modules to a library already in the concatenation. The data set used to contain the AllFusion Gen runtime modules must be a data set of type LIBRARY (PDSE). Modules required for all types of generated IMS applications are TIRORUNI, TIRMTQBZ, TIRTERAZ, TIRARUNI, TIRARUNH, and TIRARUNM. Modules required for generated IMS Block Mode Enhanced Map applications are TIRCGSPZ, TIRCHPZ, TIRCHPRZ, TIRCIIMZ, TIRCO2PZ, TIRCO2SZ, TIRCPINZ, TIRCPUIZ, and TIRCVINZ. Module required for generated IMS server applications is TIRCRUNI. Execution Load Library: CICS The AllFusion Gen runtime modules must be made available to the target CICS region as part of the CICS DFHRPL data set concatenation. Either add the AllFusion Gen r7.6 load library (ISPLLIB) to the data set concatenation or copy the relevant modules to a library already in the concatenation. The data set used to contain the AllFusion Gen runtime modules must be a data set of type LIBRARY (PDSE). B 4 Installation Guide for Host Encyclopedia and Host Construction

117 Define IMS Block Mode Applications Modules required for all types of generated CICS applications targeting DB2 are TIRORUNC, TIRMTQBZ, TIRTERAZ, TIRARUNC, TIRPRFQZ, and TIRSDTNZ. Modules required for all types of generated CICS applications targeting Datacom are TIRODCMC, TIRMTQBZ, TIRTERAZ, TIRARUNC, TIRPRFQZ, and TIRSDTNZ. Modules required for generated CICS Block Mode Enhanced Map applications are TIRCGSPZ, TIRCHPZ, TIRCHPRZ, TIRCIIMZ, TIRCO2PZ, TIRCO2SZ, TIRCPINZ, TIRCPUIZ, and TIRCVINZ. Module required for generated CICS server applications and CICS block mode applications being traced is TIRCRUNC. In addition to making the modules available in CICS, each module must have a corresponding CICS program definition. The program definitions can be added to CICS using the AllFusion Gen supplied DEFCICS job, or by using the CICS Resource Definition Online (RDO) mechanism (for example, the CICS CEDA transaction). If RDO is used, see DEFCICS job for information on how each copied module should be defined. To re-load a new copy of an AllFusion Gen runtime module, log on to CICS and execute the following CICS command: CEMT SET PROGRAM(module name) NEW Define IMS Block Mode Applications Transaction mapping and program definition must be performed before each generated application is deployed in the IMS target environment. Define APPLCTN and TRANSACT Macros Use the IMS APPLCTN and TRANSACT macros to define and associate a program with one or more transactions. For example: APPLCTN PSB=progname,PGMTYPE=(TP,,4) TRANSACT CODE=trancode,PRTY=(7,9,2), MSGTYPE=(MULTSEG,NONRESPONSE,4), PROCLIM=(3,20),SCHD=3, MODE=SNGL, SEGSIZE=0,SEGNO=320 X X X X These macros require continuation characters in column 72. For the APPLCTN macro, PGMTYPE can be either TP for online or BMP for batch. Appendix B: Configuring IMS and CICS B 5

118 Define IMS Block Mode Applications For the TRANSACT macro, MSGTYPE should specify MULTSEG and NONRESPONSE. The remaining parameters are site dependent. Note that you do not specify SPA size. Define PSBs To define the IMS Program Specification Blocks (PSBs) for the IMS application you are deploying, use the following order for the Program Control Blocks (PCBs): AllFusion Gen requires I-O PCB to be first. By default, the I-O PCB is generated automatically from the initial request. AllFusion Gen requires the second PCB to be an alternate, modifiable I-O PCB with EXPRESS=NO. (ALTRESP should not be coded on the second PCB because AllFusion Gen issues CHNG calls to other transactions, not terminals.) All other PCBs must appear after the alternate, modifiable I-O PCB. PCB TYPE=TP,MODIFY=YES PCB TYPE=DB... PCB TYPE=DB... PSBGEN PSBNAME=progname,LANG=COBOL, CMPAT=YES END Note: Failure to create the PSB according to this convention may result in loops or other unpredictable behavior in message switching. DB2 assumes plan name and PSB name are the same. If your installation requirements are different, assemble a DSNMAPN macro and link it into the DB2 load library for each trancode. Activate a PSB for MPP Processing The next step in setting up the IMS environment for deploying AllFusion Gen applications is to create the IMS ACBGEN procedure macro to activate a PSB for MPP application processing, as follows: BUILD PSB=progname B 6 Installation Guide for Host Encyclopedia and Host Construction

119 Define CICS Block Mode Applications MFS When using MFS, ensure the following is done: Install the MFS control blocks into the IMS environment. Follow your installation s procedures for performing this task. A common error is to use extended MFS attributes for terminals (or emulators) that do not support them. You must specify whether or not extended attributes can be used when you specify the target environment. For more information about extended attribute support, see the chapter Target Environment and Construction Libraries in Host Encyclopedia Construction Guide. The MFS source generated uses a copy member called TIMFSEQU, which resides in the Samplib library distributed with AllFusion Gen. This member can be copied into a copy library. Your installation procedure must be changed to either pickup the copy member from the copy library or the samplib library. Note: If the MFS source is compiled outside of AllFusion Gen and the installation procedure has not been changed, the following message is displayed: DFS1479I SC=08 MBRNAME REQUESTED NOT PRESENT IN SYSLIB Install the load module in your IMS load libraries. Follow your installation s procedures for performing this task. Define CICS Block Mode Applications Before CICS can execute a generated AllFusion Gen application, you must define the transaction name to CICS. Depending on how CICS is setup, you may also need to define its load module name. If the target DBMS is DB2 you may also need to define the DB2 plan name. If the target DBMS is Datacom no action is required. Define User Transactions Transaction and load module names are chosen in load module packaging. If the clear screen and dialog flow transaction names are not the same, both must be mapped and defined. Appendix B: Configuring IMS and CICS B 7

120 Define CICS Block Mode Applications For each transaction name, define a transaction using CICS Resource Definition Online (RDO). You can use the following information to run DFHCSDUP: DEFINE TRANSACTION(tttt) DESCRIPTION(AllFusion Gen Trancode) PROGRAM(pppppppp) TASKDATALOC(ANY) TASKDATAKEY(USER) Define User Load Modules If desired, AllFusion Gen application load modules can be auto installed. For those load modules not being auto installed, define a program using Resource Definition Online (RDO). You can use the following information to run DFHCSDUP: DEFINE PROGRAM(pppppppp) DESCRIPTION(AllFusion Gen Program) LANGUAGE(LE370) DATALOCATION(ANY) EXECKEY(USER) CONCURRENCY(THREADSAFE) Map Transactions to DB2 Plans CICS requires that CICS DB2 resources be defined using Resource Definition Online (RDO). The information required can be specified in the DB2CONN definition only, like PLANExitname, or may also be specified for individual transactions by using the DB2ENTRY and DB2TRAN definitions. AllFusion Gen load modules use the load module name as the plan name. For those applications that use a dynamic plan exit specify TIRC$EXT as the PLANExitname. Link TIRC$EXT, include RENT as a linkage editor PARM option and use the following control cards: INCLUDE SYSLIB(DFHEAI) INCLUDE SYSLIB (DFHEAI0) INCLUDE GENLOAD(TIRC$EXT) ENTRY TIRC$EXT NAME TIRC$EXT(R) In the link JCL, include data definition statements for: SYSLIB, pointing to the CICS library containing module DFHEAI. GENLOAD, pointing to the AllFusion Gen load library containing TIRC$EXT. Add an entry to the PPT for TIRC$EXT; language is ASSEMBLER. Place the relinked TIRC$EXT in a library in the CICS DFHRPL concatenation. B 8 Installation Guide for Host Encyclopedia and Host Construction

121 Establish Client/Server Support Enable XCTL The Define Target Environment Parameters screen has an option to Use XCTL for Flows When Possible. If you choose this option and the target DBMS is DB2, you should use Package Binds and a single CICS plan or you can use the Dynamic plan selection exit TIRC$EXT. However, the recommended choice is Package Binds. Enable Error Messages AllFusion Gen dynamically calls the DB2 error message-formatting module DSNTIAR. For the dynamic call to work, add an entry to the Program Definition (PPT) for DSNTIAR (or use the DEFCICS job to do this for you). The program language is ASSEMBLER. For more information about the TIRTIAR user exit, see the AllFusion Gen Host Encyclopedia Construction Guide. Establish Client/Server Support This section explains how to setup CICS and IMS to execute client/server applications. If you are not implementing AllFusion Gen generated client/server applications, you can skip this section. The basic tasks you must complete to establish client/server (C/S) support are: Customize code page translation Define server transactions and programs Customize middleware Depending on the type of middleware used, select from the following tasks: Establish communications support (ECHO for CICS, ECHOI for IMS) Customize for LU6.2 Customize for TCP/IP Customize for MQSeries Customize for ECI The following sections describe the procedures for completing each of these tasks. Customize Code Page Translation For information on customizing code pages, see the appendix Setting Model Code Pages. Appendix B: Configuring IMS and CICS B 9

122 Establish Client/Server Support Define Server Transactions and Programs This section explains how to define IMS and CICS server transactions and programs. These definitions are discussed in the following sections: IMS server transactions and programs CICS server transactions and programs DEFCICS member Note: All CICS samples in this section use IBM supplied transaction CEDA. These samples are for illustration only and may not be pertinent to your particular environment. You should verify applicability before installing any definitions. IMS Server Transaction and Program Definitions Use the IMS APPLCTN and TRANSACT macros to define and associate a program with one or more transactions. For example: APPLCTN GPSB=progname,PGMTYPE=TP,LANG=COBOL TRANSACT CODE=trancode, EDIT=ULC, MSGTYPE=(SNGLSEG,RESPONSE,1) X X 1. For the APPLCTN macro, PGMTYPE is TP for online. 2. Ensure that each IMS C/S trancode has a TRANSACT definition. 3. For the TRANSACT macro, MSGTYPE should specify SNGLSEG and RESPONSE. 4. For the TRANSACT macro, ensure EDIT=ULC to prevent lowercase characters from being translated to uppercase. This also allows the AllFusion Gen cooperative buffer characters to bypass IMS input message translation. CICS Server Program and Transaction Definitions The following example shows a transaction definition that can be used to run DFHCSDUP: DEFINE TRANSACTION(tttt) DESCRIPTION(AllFusion Gen Trancode) PROGRAM(pppppppp) TWASIZE(0) TASKDATALOC(ANY) TASKDATAKEY(USER) AllFusion Gen r7.6 servers no longer require a TWASIZE of 8 bytes. B 10 Installation Guide for Host Encyclopedia and Host Construction

123 Establish Client/Server Support The following example shows a program definition that can be used to run DFHCSDUP: DEFINE PROGRAM(pppppppp) DESCRIPTION(AllFusion Gen Program) LANGUAGE(Le370) DATALOCATION(ANY) EXECKEY(USER) CONCURRENCY(THREADSAFE) DEFCICS Batch Job The DEFCICS batch job can be used to understand and define CICS transactions and programs. The steps to using DEFCICS are: 1. Edit DEFCICS to change the data set names on the lines marked for modification (***MOD***). 2. Edit the group name, if appropriate for your installation. The default group name is GEN. 3. Examine all the settings and definitions in DEFCICS for conflicts and changes from prior releases and make appropriate changes. 4. Uncomment the ADD GROUP segment, if appropriate. 5. Change the LISTNAME on the ADD GROUP to your startup list. 6. Decide whether to keep or remove the DSNTIAR or DSNTIAC definition, depending on the exits you define and use. 7. Submit DEFCICS. Note: If you change the GROUP name, you must ensure that you change it for each occurrence in the job. If the GROUP name currently exists and contains entries, you may wish to avoid potential conflicts by deleting these entries, or moving them to another group. Appendix B: Configuring IMS and CICS B 11

124 Establish Client/Server Support Customize Middleware This section explains how to customize the middleware and establish communications support Establish Communications Support This section shows you how to install ECHO support. ECHO is a transaction used to verify the connection between the workstation and the host. An ECHO request can only be executed from the AllFusion Gen Client Manager or Communications Bridge. IMS The IMS ECHO is found in AllFusion Gen Load library member ECHOI. The program name is actually ECHO. 1. Move ECHOI from the AllFusion Gen load library (ISPLLIB) to a data set in the IMS Steplib concatenation. Ensure this data set is of type LIBRARY (PDSE). Rename ECHOI to ECHO. 2. Add an APPLCTN and TRANSACT macro definition for ECHO to match the server definitions. 3. Ensure that the PSB for ECHO has an IO-PCB and an ALT-IO-PCB. CICS Ensure that the latest version of ECHO supplied in the AllFusion Gen Load Library is used. This version can also be used by requests from the AllFusion Gen Communications Bridge using ECI. 1. Move ECHO from the load library (ISPLLIB) to a data set in the CICS DFHRPL concatenation. Ensure this data set is of type LIBRARY (PDSE). 2. Add a transaction and program definition for ECHO to match the server definitions. B 12 Installation Guide for Host Encyclopedia and Host Construction

125 Establish Client/Server Support Customize for LU6.2 The AllFusion Gen Client Manager or the AllFusion Gen Communications Bridge is required when AllFusion Gen applications use LU6.2 communications. Information regarding installation and configuration of the AllFusion Gen Client Manager and Communications Bridge is found in the Distributed Processing - Client Manager guide and Distributed Processing - Communications Bridge guide. The following details the configuration required to define the necessary resources for LU6.2 communications in the z/os environment: VTAM Log Mode Table LU6.2 Communications and Sessions for CICS APPC z/os LU Definitions for IMS VTAM LOG MODE TABLE ENTRY This is a portion of a sample VTAM log mode table, SAMP62, containing a mode entry for LU62APPC. The addition of this entry enables support of multiple parallel LU6.2 sessions for the Client Manager and the Communications Bridge. Please note this macro requires continuation characters in column 72. SAMP62 MODETAB MODEENT FMPROF=X'13', X TSPROF=X'07', X COS=#CONNECT, X PRIPROT=X'B0', X PSNDPAC=X'08', X SRVPAC=X'08', X SSNDPAC=X'08', X SECPROT=X'B0', X TYPE=X'00', X COMPROT=X'50B5', X RUSIZES=X'8888', X PSERVIC=X' F00 A MODEENT LOGMODE= A, X.. Appendix B: Configuring IMS and CICS B 13

126 Establish Client/Server Support LU62APPC MODEENT LOGMODE=LU62APPC, X FMPROF=X'13', X TSPROF=X'07', X COS=#INTER, X PRIPROT=X'B0', X PSNDPAC=X'08', X SRCVPAC=X'08', X SSNDPAC=X'08', X SECPROT=X'B0', X TYPE=X'00', X COMPROT=X'50B5', X RUSIZES=X'8888', X PSERVIC=X' F00' Z MODEENT LOGMODE= Z, X.. MODEEND. LU6.2 Connection and Session Definitions for CICS LU6.2 communications include a terminal definition comprised of connection and session definitions (LUTYPE 6.2 /APPC links and parallel sessions). This is documented in the CICS Resource Definition Guide. In the following DFHCSDUP connection and session sample definitions, add the relevant GROUP name and description. Connection Definition DEFINE CONNECTION(LU62CONN) GROUP(?????) DESCRIPTION(?????) NETNAME(LUNETNAME) PROTOCOL(APPC) AUTOCONNECT(YES) ATTACHSEC(LOCAL/VERIFY/IDENTIFY)* * - As required. Session Definition DEFINE SESSIONS(LU62SESS) GROUP(?????) DESCRIPTION(?????) CONNECTION(LU62CONN) MODENAME(LU62APPC) PROTOCOL(APPC) B 14 Installation Guide for Host Encyclopedia and Host Construction

127 Establish Client/Server Support APPC z/os LU Definition for IMS This is a sample APPC z/os local LU definition using the utility ATBSDFMU: LUADD ACBNAME(ADVPCI51) /* Add local LU ADVPCI51 */ SCHED(IMS5) /* Specify that the APPC/IMS transaction scheduler is associated with this LU name */ BASE /* Designate this LU as the base LU */ TPDATA(SYS6.APPC.TP) /* Specify that VSAM data set is the permanent repository for TP profiles for this LU */ TPLEVEL(SYSTEM) /* Specify the search order for TP profiles as: TP profiles associated with a specific user TP profiles associated with a group of users TP profiles associated with all users of the LU name */ Customize for TCP/IP The following section explains how to customize CICS for TCP/IP. CICS AllFusion Gen offers two implementations that use TCP/IP CICS Sockets: Direct Connect for CICS - This is Gen's original implementation and remains unchanged. It provides a long running connection with CICS sockets program TICONMGR. Information specific about installing this feature is in the section titled 'Direct Connect for CICS'. CICS Sockets Servers - This is an alternative implementation that passes the socket to the AllFusion Gen server application and closes the socket when the server terminates. It does not use TICONMGR. This new implementation must NOT be used with either the AllFusion Gen Client Manager or the AllFusion Gen Communications Bridge since it is designed to terminate the connection after each flow is processed. For specific information about installing this new feature, see the section CICS Sockets Servers in this chapter. Regardless of which implementation is used the IBM CICS TCP/IP Sockets Interface must be configured to be used by AllFusion Gen generated CICS Server applications. For more information on configuring IBM s CICS TCP/IP sockets interface, see Setting up and Configuring CICS TCP/IP in IBM s z/os V1R7.0 Communications Server IP CICS Sockets Guide. Appendix B: Configuring IMS and CICS B 15

128 Establish Client/Server Support The CICS Sockets Interface must be started before the Listener can be initialized and all Listeners must have terminated before the Interface can be stopped. Use the IBM-provided EZACIC20 program to start or stop the CICS Sockets Interface and to initialize or terminate any Listener programs. To automatically start or stop the CICS Sockets Interface at CICS startup or shut down, add the EZACIC20 program to the CICS Program Load Table (PLT). If the Listener record in the configuration file states IMMED=YES, the Listener automatically initiates when the Interface is started and is terminated before the Interface terminates at CICS shutdown. Both implementations can exploit transactional security. Transactional security refers to starting the server transaction with the userid (not the password) of the client application, if one is provided. The server is started in CICS as a non-terminal task and thus can only use CICS transactional security (with surrogate security checking). The AllFusion Gen programs TILSTNR, TICONMGR, and TISRVLIS are provided on the CD called AllFusion Gen TCP/IP options for CICS. The exits used by both implementations, namely modules TIRSDTN (DLL TIRSDTNZ), TIRSCID, TIRTSEC and TIRSLEXT, are provided as part of AllFusion Gen base product. Depending on which implementation is used TILSTNR, TICONMGR, TIRSDTNZ or TISRVLIS, TIRSLEXT must be made available to CICS in the DFHRPL concatenation. The instructions on how to get the AllFusion Gen TCP/IP programs to the mainframe are provided on the CD. CICS Sockets Servers The Listener provided for the CICS Sockets Server implementation is a program named TISRVLIS. This listener is intended for applications that do not require a long running connection like AllFusion Gen Web Applications. This listener must be defined as a Standard Listener. To use AllFusion Gen Server Listener, the following record is required in the EZACONFG file: TYPE=LISTENER, TRANID=TISL*, TRANTRN=NO, TRANUSR=NO, and leave the SECEXIT and WLM groups parameters blank. CICS definitions are required for: The Listener transaction TISL*. The program TISRVLIS. The program TIRSLEXT. B 16 Installation Guide for Host Encyclopedia and Host Construction

129 Establish Client/Server Support The following information can be used to run DFHCSDUP (add a GROUP of your choice): DEFINE TRANSACTION(TISL*) DESCRIPTION(AllFusion Gen CICS Sockets Server Listener Transaction) PROGRAM(TISRVLIS) TASKDATALOC(ANY) TASKDATAKEY(CICS) DEFINE PROGRAM(TISRVLIS) DESCRIPTION(AllFusion Gen CICS Sockets Server Listener Program) LANGUAGE(ASSEMBLER) DATALOCATION(ANY) EXECKEY(CICS) DEFINE PROGRAM(TIRSLEXT) DESCRIPTION(AllFusion Gen CICS Sockets Server Exit Program) LANGUAGE(ASSEMBLER) DATALOCATION(ANY) EXECKEY(CICS) * The transaction identifier can be something other than TISL, but the same name must be used in the EZACONFG file and in the CICS definition. The Sockets Server listener program TISRVLIS produces both Error and Informational Messages. The Error Messages are always written to the CICS Joblog (CSSL TDQ), while the Information Messages are written to a CICS TDQ with the name used for the TISRVLIS transaction identifier. If this user defined TDQ does not exist, the Informational Messages are suppressed. When using Sockets Server implementation, the messages TIRM615E and TIRM709E are produced for the following conditions: TIRM615E Reported by the client when TISRVLIS cannot receive data from sockets. Each condition also produces an error message written to the CICS joblog documenting the server transaction and the type of error encountered. In some instances, a EWOULDBLOCK error is reported after the call is tried numerous times without success. TIRM709E Reported by the client when TIRSLEXT exit has been customized to verify that encryption is used. However, the client request does not have the encrypted flag set. Appendix B: Configuring IMS and CICS B 17

130 Establish Client/Server Support The Sockets Server implementation allows the server to be routed to a CICS region different from the one where the TISRVLIS listener is executing. Routing may be invoked by using the specific SYSID of where the server is to execute or by using Distributed Routing. If the SYSID is used it must be provided as the variable 'CICS' in the TIRSLEXT user exit. Distributed Routing may be implemented using the DSRTPGM program or the CICS transaction definition. When routing is used the CICS Sockets Interface must be active in the CICS region where the server will be routed to, but an active listener is not required in that CICS region. The Sockets Server listener program TISRVLIS uses a CICS LINK to invoke the exit program TIRSLEXT. This Sockets Server exit program is not used by AllFusion Gen servers. When modifying the TIRSLEXT exit, make the modified program available in CICS (using New Copy, if applicable). There is no need to stop or restart the Sockets Server listener. For more information about the TIRSLEXT user exit, see the appendix Distributed Processing User Exits in AllFusion Gen Distributed Processing - Overview guide. Direct Connect for CICS The Direct Connect for CICS implementation is intended to be used by applications that require a long running connection like AllFusion Gen Client Manager and/or Communications Bridge. This implementation can use either the AllFusion Gen supplied Listener or the IBM-supplied Enhanced Listener. To use AllFusion Gen Listener, the following record is required in the EZACONFG file: TYPE=LISTENER, TRANID=TILL*, TRANTRN=NO, TRANUSR=NO, and leave the SECEXIT and WLM groups parameters blank. B 18 Installation Guide for Host Encyclopedia and Host Construction

131 Establish Client/Server Support To use the IBM-supplied Enhanced Listener, the following record is required in the EZACONFG file: TYPE=LISTENER, TRANID=<any that you want>, CSTRANid=TICM, CSSTTYPe=KC, CSDELAY=0, MSGLENgth=0, PEEKDATa=NO, MSGFORMat=ASCII, and leave the SECEXIT and WLM groups parameters blank. CICS definitions are required for: The Listener transaction TILL*, if using AllFusion Gen Listener. The program TILSTNR, if using AllFusion Gen Listener. A transaction definition for TRANID <any that you want>, if using IBMsupplied Enhanced Listener. Ensure this definition matches the one IBM provides for the IBM-supplied Listener. The Connection Manager transaction TICM and program TICONMGR. The Connection Manager calls a number of user exits, namely TIRSDTN, TIRSCID, and TIRTSEC. These user exits are available in the AllFusion Gen SAMPLIB library and include information on how to compile and link them. For more information about these user exits, see the appendix Distributed Processing User Exits in AllFusion Gen Distributed Processing - Overview guide. AllFusion Gen servers also use TIRSDTN exit. However, only the names of the Shared Data Tables (TIRINSDT and TIROTSDT) and the name of the SDT TSQ (SDTKEY-TSQ-PREF) are applicable to servers. If any of these names are changed, the servers also need to be re-installed (re-linked) to pick up the changes. The following information can be used to run DFHCSDUP (add a GROUP of your choice): DEFINE TRANSACTION(TILL*) DESCRIPTION(AllFusion Gen TCP/IP Listener Transaction) PROGRAM(TILSTNR) TASKDATALOC(ANY) TASKDATAKEY(CICS) Appendix B: Configuring IMS and CICS B 19

132 Establish Client/Server Support DEFINE TRANSACTION(TICM) DESCRIPTION(AllFusion Gen TCP/IP Connection Manager Transaction) PROGRAM(TICONMGR) TASKDATALOC(ANY) TASKDATAKEY(CICS) DEFINE PROGRAM(TILSTNR) DESCRIPTION(AllFusion Gen TCP/IP Listener Program) LANGUAGE(ASSEMBLER) DATALOCATION(ANY) EXECKEY(CICS) DEFINE PROGRAM(TICONMGR) DESCRIPTION(AllFusion Gen TCP/IP Connection Manager Program) LANGUAGE(LE370) DATALOCATION(ANY) EXECKEY(CICS) * The transaction identifier can be something other than TILL. But, the same name must be used in the EZACONFG file and in the CICS definition. AllFusion Gen TCP/IP Direct Connect Option for CICS uses two user maintained shared datatables (VSAM files). Either each Connection Manager has exclusive access to these two files or multiple Connection Managers may access them, depending on choice and transaction volumes. The user exit TIRSDTN lets you customize the ddnames for these files with the defaults being TIRINSDT and TIROTSDT. Depending on your installation s requirements the MAXNUMRECS value may need adjusting. The following sample can be tailored for DFHCSDUP (add a GROUP of your choice): DEFINE FILE(TIRINSDT) DESCRIPTION(Advantage Gen Input Shared Datatable File) DSNAME(HLQ.TIRINSDT) STRINGS(5) RECORDSIZE(32743) RECORDFORMAT(V) KEYLEN(24) TABLE(USER) MAXNUMRECS(8192) ADD(YES) DELETE(YES) READ(YES) BROWSE(YES) DEFINE FILE(TIROTSDT) DESCRIPTION(Advantage Gen Output Shared Datatable File) DSNAME(HLQ.TIROTSDT) STRINGS(5) RECORDSIZE(32743) RECORDFORMAT(V) KEYLEN(24) TABLE(USER) MAXNUMRECS(8192) ADD(YES) DELETE(YES) READ(YES) BROWSE(YES) B 20 Installation Guide for Host Encyclopedia and Host Construction

133 Establish Client/Server Support You can use the following IDCAMS to allocate the VSAM files (name the DATA and INDEX components if required): //IDCAMS EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER(NAME(HLQ.TIRINSDT) - VOLUMES(VVVVVV) - CYLINDERS(5 5) - RECORDSIZE( ) - KEYS(24 0) ) DEFINE CLUSTER(NAME(HLQ.TIROTSDT) - VOLUMES(VVVVVV) - CYLINDERS(5 5) - RECORDSIZE( ) - KEYS(24 0) ) Debugging TICONMGR TICONMGR has been modified to enable it to produce debug information. This feature must only be used when requested to by Technical Support. The debug feature is activated by the presence of a TSQ with a record indicating that debug info is required. This information is logged to one of two VSAM files. VSAM files The debug information is written to a VSAM file. Two VSAM files are required to enable switching. The VSAM files need to be allocated as follows: //JOBCARD //VSAMDEF EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER (NAME(AAAA.BBBB.TICMLOG1) VOLUMES(VVVVVV) - CYL(XX YY) - RECORDSIZE( ) - KEYS(14 0) - REUSE ) DEFINE CLUSTER (NAME(AAAA.BBBB.TICMLOG2) VOLUMES(VVVVVV) - CYL(XX YY) - RECORDSIZE( ) - KEYS(14 0) - REUSE ) //* Appendix B: Configuring IMS and CICS B 21

134 Establish Client/Server Support where the file NAME (AAAA.BBBB.TICMLOGx) must contain three qualifiers with the last one being TICMLOG1 and TICMLOG2. The other 2 can be any name and number of characters greater than or equal to 1. VVVVVV is the volume where the files are allocated and CYL(XX YY) is the space allocation. Ensure that the files allocated are large enough to capture the event being traced. There will be on average 8 records for each request/response processed by TICONMGR. CICS FILE definitions Define the two VSAM files to CICS. The STRINGS value may need adjusting. The following can be used to run the DFHCSDUP CICS utility: DEFINE FILE(TICMLOG1) DESCRIPTION(AllFusion Gen TICONMGR DEBUG LOG 1) DSNAME(AAAA.BBBB.TICMLOG1) STRINGS(5) RECORDSIZE(32751) RECORDFORMAT(V) KEYLEN(14) TABLE(NO) MAXNUMRECS(NOLIMIT) ADD(YES) DELETE(YES) READ(YES) BROWSE(YES) RECOVERY(NONE) DEFINE FILE(TICMLOG2) DESCRIPTION(AllFusion Gen TICONMGR DEBUG LOG 2) DSNAME(AAAA.BBBB.TICMLOG2) STRINGS(5) RECORDSIZE(32751) RECORDFORMAT(V) KEYLEN(14) TABLE(NO) MAXNUMRECS(NOLIMIT) ADD(YES) DELETE(YES) READ(YES) BROWSE(YES) RECOVERY(NONE) TSQ The debug option is enabled by the presence of a TSQ named TICMDBG in the same CICS region as TICONMGR. The first record in the TSQ must contain data of the format XAB NAME where X = N - do not write any information D - write client s IP address and port to CICS joblog only Y - write debug info to one of the TICMLOGx data sets B 22 Installation Guide for Host Encyclopedia and Host Construction

135 Establish Client/Server Support A = Y - first time we start debugging so use the TICMLOGx file specified in the TICMDBG TSQ N - check which log we used previously and switch if necessary B = Y - empty the log we are going to write to (like disp=old) N - continue writing to existing log (like disp=mod) NAME = TICMLOG1 or TICMLOG2, the CICS FILE name of the log we are going to start writing to Either create the TSQ programmatically or using the CICS transaction CECI as follows: CECI WRITEQ TS QUEUE('TICMDBG') FROM('YYY TICMLOG1') Stopping debug After the event is traced, delete TSQ TICMDBG to stop the logging activity. Ensure the TICMLOGx files are closed in CICS. Use IDCAMS REPRO to extract the data from the TICMLOGx files. Ensure the output of the Repro points to a VBA file with a LRECL large enough to contain the largest record processed by TICONMGR. File transfer the output as binary data. IMS AllFusion Gen's TCP/IP Direct Connect option for IMS consists of four Assembler Language exits. The supplied module called CAGRITCP is the User Message Exit for IMS Connect while the other three modules are exits called by CAGRITCP. The user message exit is supplied as a load module only. The other exits are supplied as source code as well as load modules with default behavior. Comments in the exits explain the default behavior and how to modify them. These exits are covered in detail in the Distributed Process Overview Guide. If modifications are required for any of the three exits, these exits must be reassembled and re-linked following the instructions included in the source code. Please ensure the user message exit, CAGRITCP, is also re-linked and the relevant IMS Connect is stopped and restarted. To use the IMS Connect user message exit CAGRITCP, IMS Connect must be configured to include this exit. For information on how to set up and customize IMS Connect, see IMS Connect User's Guide. Ensure that you add the user message exit name CAGRITCP to the IMS Connect EXIT parameter of the TCPIP statement. Appendix B: Configuring IMS and CICS B 23

136 Establish Client/Server Support For example: HWS (ID= ) TCPIP (HOSTENAME= EXIT=(HWSSMPL0,CAGRITCP)) DATASTORE (ID=...,GROUP=IMSXCF,MEMBER=..., TMEMBER=IMSA,DRU=...) The IMS control region must also be configured to use OTMA. For more information, see the IMS documentation, especially the Install Volume 2: System Definition and Tailoring. For example:.. OTMA=Y, GRNAME=IMSXCF, OTMAMN=IMSA,. Where: GRNAME Matches the name specified in the GROUP parameter of the IMS Connect DATASTORE statement. OTMANM Matches the name specified in the TMEMBER parameter of the IMS Connect DATASTORE statement. Customize for MQSeries AllFusion Gen MQSeries server applications can be deployed as z/os CICS or IMS transactions. For more information regarding using MQSeries with AllFusion Gen, see the Distributed Processing - WebSphere MQ guide. CICS AllFusion Gen supports two methods of invoking a CICS DPS application through MQSeries: Using a trigger monitor to dispatch each server manager directory Using a trigger monitor to invoke the Transaction Dispatcher for CICS (TDC) Instructions for dispatching the server directly are documented in the Distributed Processing- WebSphere MQ guide. This guide provides instructions for installing the TDC. B 24 Installation Guide for Host Encyclopedia and Host Construction

137 Establish Client/Server Support MQSeries Transaction Dispatcher The AllFusion Gen Transaction Dispatcher for CICS (TDC) is an optional enhancement that is designed to overcome some of the queuing and triggering limitations experienced with the previous implementations. It also provides additional operational and administrative options within MQSeries (MQS) and CICS. With the TDC enabled: Trigger events cause the queue to be fully processed (emptied). Queues may contain mixed AllFusion Gen messages. Queues are not limited to a single server manager. Multi-programming and dispatching of the TDC may be controlled by userexit. Transaction level security may be implemented, associating client userids with individual server manager transactions in CICS. The TDC consists of a CICS transaction TITD, program TIRMQTDC, and an optional user exit/control program, TIRMQTDX. It is designed to run as a front-end for MQ-enabled existing and new server managers within the CICS region. The TDC is selected by designating the TITD transaction, as opposed to the Server Manager transaction, as the process associated with an MQSeries queue definition. This enhancement does not affect current functionality. Server Managers may continue to use the current methodology (that is, Server Manager direct to MQS) and requires no changes to take advantage of the TDC. MQSeries TDC can take advantage of transactional security. Transactional security refers to starting the server transaction with the userid (not the password) of the client application, if one is provided. The server is started in CICS as a non-terminal task and thus can only use CICS transactional security (surrogate security checking). Installation The base components of TDC are installed as part of the standard z/os install. To access them, they must be defined to CICS. Additionally, VSAM files are necessary if you intend to use this option for temporary storage. Appendix B: Configuring IMS and CICS B 25

138 Establish Client/Server Support Basic CICS Install The modules TIRMQTDC and, if used, TIRMQTDX must be in the DFHRPL concatenation. If the AllFusion Gen Load library is not allocated to DFHRPL, copy TIRMQTDC from the AllFusion Gen Load library to a data set in the DFHRPL concatenation. Ensure this data set is of type LIBRARY (PDSE). The following information can be used to run DFHCSDUP. Add a Group of your choice: DEFINE TRANSACTION(TITD) DESCRIPTION(AllFusion Gen Transaction dispatcher) PROGRAM(TIRMQTDC) TASKDATALOC(ANY) TASKDATAKEY(USER) DEFINE PROGRAM(TIRMQTDC) DESCRIPTION(AllFusion Gen Transaction dispatcher) LANGUAGE(ASSEMBLER) DATALOCATION(ANY) EXECKEY(USER) DEFINE PROGRAM(TIRMQTDX) DESCRIPTION(AllFusion Gen Transaction dispatcher control exit) LANGUAGE(LE370) DATALOCATION(ANY) EXECKEY(USER) CICS VSAM SDT Install Use the following to create the VSAM files if you intend to use VSAM SDT* for temporary storage. Change the data set name to the DSN you are using. The DDNAME may be changed if the corresponding update is made in TIRMQTDX. MAXNUMRECS may be adjusted up or down depending on your installation s needs. Do not use a CICS maintained table. Use only a USER maintained table. Use values specific to your installation for YOUR.TEMP.DATASET in the DSNAME and CLUSTER parameters. Run DFHCSDUP using the following deck: DEFINE FILE(TITDTEMP) DESCRIPTION(AllFusion Gen Transaction dispatcher temp SDT) DSNAME(YOUR.TEMP.DATASET) STRINGS(5) ADD(YES) DELETE(YES) READ(YES) BROWSE(YES) RECOVERY(NONE) RECORDSIZE(32760) RECORDFORMAT(V) KEYLEN(8) TABLE(USER) MAXNUMRECS(4096) GROUP(TDCGROUP) B 26 Installation Guide for Host Encyclopedia and Host Construction

139 Establish Client/Server Support Run IDCAMS as follows: //IDCAMS EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //DD1 DD * /* //SYSIN DD * DEFINE CLUSTER(NAME(YOUR.TEMP.DATASET) - VOLUMES(VVVVVV) - CYLINDERS(5 5) - RECORDSIZE( ) - KEYS(8 0) - ) REPRO INFILE(DD1) OUTDATASET(YOUR.TEMP.DATASET) Note: You may also use a standard VSAM KSDS without using the datatable feature. If this is done, cluster space should be adjusted accordingly, and the cluster should be deleted and redefined on each restart of CICS. SDT is recommended for performance. IMS AllFusion Gen supports MQSeries DPS deployment in the z/os/ims applications environment and is documented in the Distributed Processing- WebSphere MQ guide. The IMS DPS MQSeries environment is implemented similar to the CICS MQSeries runtime, where the DPS is dispatched using the CICS trigger monitor from IBM (the non-tdc implementation). For IMS, the trigger monitor is an IMS transaction called CSQQTRMN. This method dispatches each server manager directly. Customize for ECI An AllFusion Gen CICS server is accessible by AllFusion Gen clients using the CICS Client External Call Interface (ECI). AllFusion Gen C and Java clients and those using Communications Bridge can use ECI communications. Depending on where and how the AllFusion Gen clients are deployed, each client type may require CICS Universal Clients or CICS Transaction Gateway. For more information about CICS Universal Clients and CICS Transaction Gateway, see the CICS Transaction Gateway documentation. An AllFusion Gen server invoked through ECI is started by a Distributed Program Link (DPL) request. The DPL request uses the CICS supplied Mirror Program (DFHMIRS) to start the requested Gen server. By default transaction ID CPMI is used to invoke the CICS Mirror Program. In some cases it may be desirable to use a transaction ID other than CPMI for ECI requests. Appendix B: Configuring IMS and CICS B 27

140 Establish Client/Server Support For Java clients changing the ECIUseSyncTpn to Yes in the commcfg.properties file causes the trancode associated with the target server application in Construction Packaging to be the transaction ID used. For clients using the Communications Bridge the data pointed to by parameter pecitpn of the Communications Bridge exit ioeciclx.c is used. For GUI and C proxy clients the data pointed to by parameter ptpn of the Windows exit cieciclx.c is used. If a transaction ID other than CPMI is used the relevant transaction must be defined in CICS to point to the DFHMIRS program and use profile DFHCICSA. This transaction cannot be shared by Gen applications using ECI and non-eci cooperative flows. The interface assumes that data translation (ASCII to EBCDIC) and code page conversion is required and automatically invokes the conversation table DFHCNV. AllFusion Gen does translation and conversion, so this step is not necessary. However, a conversion table is still required. Code a DFHCNV table with TYPE=INITIAL and TYPE=FINAL macros only. Assemble, link, and make the table available to CICS. Sample DFHCNV as required by AllFusion Gen: DFHCNV TYPE=INITIAL DFHCNV TYPE=FINAL END If this table is used for another application, ensure that no translation or conversion is done for AllFusion Gen server applications. For more information on the DFHCNV table, see the CICS Family Communicating from CICS on S/390. B 28 Installation Guide for Host Encyclopedia and Host Construction

141 Debugging Applications Debugging Applications The following section explains how to debug AllFusion Gen applications. Diagram Trace Facility AllFusion Gen provides a Diagram Trace Facility (DTF) that allows you to trace CICS applications (Block Mode and Servers) at the diagram source level. For this facility to function, you must add a transaction and program definition for DTF and another for TFDI (or use the DEFCICS job to do this for you), as follows: Transaction Definitions DEFINE TRANSACTION(DTF) DESCRIPTION(?????) PROGRAM(DTF) TWASIZE(0) TASKDATALOC(any) TASKDATAKEY(user) DEFINE TRANSACTION(TFDI) DESCRIPTION(?????) PROGRAM(TFDI) TWASIZE(1200) TASKDATALOC(any) TASKDATAKEY(user) Program Definitions DEFINE PROGRAM(DTF) DESCRIPTION(?????) LANGUAGE(Le370) DATALOC(any) EXECKEY(user) DEFINE PROGRAM(TFDI) DESCRIPTION(?????) LANGUAGE(Le370) DATALOC(any) EXECKEY(user) Note: Transaction DTF no longer requires a TWASIZE of 8 bytes but transaction TFDI still requires a TWASIZE of 1200 bytes. Appendix B: Configuring IMS and CICS B 29

142 Debugging Applications Debugging Dynamic Runtime Trace output from the client/server dynamic runtime can be helpful in debugging a runtime error. Like in previous releases AllFusion Gen r7.6 also provides two versions of the Dynamic Runtime, a regular one without debug and a debug version. However the AllFusion Gen r7.6 debug versions of the dynamic runtime have the same name as the regular runtime but are supplied in a separate library - the LOADTRCE library. TIRCRUNC Since there can only be only one copy of TIRCRUNC per CICS region, all AllFusion Gen client/server applications in the region will generate trace output, when the debug version is used. Consequently, trace should only be enabled for a limited time to debug a specific problem. Enable Trace with Debug TIRCRUNC 1. Save a copy of the non-debug version of TIRCRUNC. 2. (Optional) If the regular TIRCRUNC is modified for code page translations, make the same modifications to the debug TIRCRUNC. Use MKCRUN JCL provided in SAMPLIB. 3. Copy the debug TIRCRUNC from the AllFusion Gen LOADTRCE library (or the modified version) to a library in the CICS DFHRPL concatenation. 4. Logon to CICS and execute CEMT to load the new copy of TIRCRUNC as follows: CEMT SET PROGRAM(TIRCRUNC) NEWCOPY 5. Run a client/server transaction. Trace output is written to a temporary storage queue named TIRTxxxx (where xxxx is the terminal ID). Disable Trace with Debug TIRCRUNC 1. (Optional) Back up or rename the debug version of TIRCRUNC. 2. Reinstate the non-debug version of TIRCRUNC by replacing the debug version with the original (non-debug) copy. 3. Logon to CICS and execute CEMT to load a new copy of TIRCRUNC as follows: CEMT SET PR(TIRCRUNC) NEWCOPY. B 30 Installation Guide for Host Encyclopedia and Host Construction

143 Debugging Applications TIRCRUNI Since there can only be one copy of TIRCRUNI per IMS region, all AllFusion Gen client/server applications in the region will generate trace output. Consequently, the trace should be enabled for a limited time to debug a specific problem. Enable Trace with Debug TIRCRUNI The debug version of TIRCRUNI produces trace information that is directed to a selected LTERM. New user exit TIRIDTRM is provided to specify the following information: TIRTMXSZ hex size of the trace buffer TIRTLTRM eight-character Lterm specifying the location of trace data TIRTMODN MFS modname to format the screen before sending data, DFS.EDT is the default and sends data in bypass-edit mode. The TIRIDTRM exit must be customized and included in the server application that needs the tracing because the tracing operation is only executed if a value is specified for TIRTMXSZ and TIRTLTRM. 1. Save a copy of the non-debug version of TIRCRUNI. 2. (Optional) If the regular TIRCRUNI is modified for code page translations, make the same modifications to the debug TIRCRUNI. Use MKCRUN JCL provided in SAMPLIB. 3. Copy the debug TIRCRUNI from the AllFusion Gen LOADTRCE library (or the modified version) to a library in the IMS STEPLIB concatenation. 4. Run a client/server transaction. The runtime sends TIRTMXSZ bytes to the TIRTLTRM with mfsmod TIRTMODN. Disable Trace with Debug TIRCRUNI 1. (Optional) Back up or rename the debug version of TIRCRUNI. 2. Reinstate the non-debug version of TIRCRUNI by replacing the debug version with the original (non-debug) copy. Appendix B: Configuring IMS and CICS B 31

144

145 Appendix C: Using Encyclopedia Exits The chapter documents the types of exits provided by AllFusion Gen and the common encyclopedia exits. In addition, it also explains the DB2 authorization Ids and how to create User CLISTs. Types of Exits AllFusion Gen provides two types of exits: Runtime User Exits These exits allow you to modify the default behavior of an AllFusion Gen application. For example, the termination exit allows the user to alter the default behavior of an AllFusion Gen application that terminates abnormally. Runtime User Exits used by Block Mode and Batch applications are documented in the Host Encyclopedia Construction Guide. Runtime User Exits used by Cooperative applications are documented in the DP - Overview guide. Encyclopedia Exits These exits allow you to modify the default behavior of the encyclopedia and Host Construction at predefined points. For example, the TICINSTX CLIST exit is invoked to link and bind an AllFusion Gen application load module. Note: When making changes to the AllFusion Gen software, use a different library name that can be concatenated ahead of AllFusion Gen software. Appendix C: Using Encyclopedia Exits C 1

146 Common Encyclopedia Exits Common Encyclopedia Exits The most commonly modified components are: TICINSTX Link and DB2 bind CLIST TICJCLX Background JCL generation CLIST TICGENB2 Construction background jobstep skeleton TICGENB4 RI trigger background jobstep skeleton TIRGENB2 Intelligent regeneration background variables skeleton TICEXBPK Package find user exit TICEXBPL Plan bind user exit Important! These components are initially delivered containing code to accomplish documented AllFusion Gen functions. Modifying, adding, or deleting code in them, except in the manner noted in this guide, is not recommended. TICINSTX Depending on the target DBMS being used the CLIST TICINSTX performs a link or a link and bind when a load module is installed, whether you choose background or foreground generation. When the target DBMS is Datacom only the link is done while when the target DBMS is DB2 a link and a bind is performed. As delivered, TICINSTX uses the libraries specified in the z/os Construction Internal Libraries panel and the parameters specified in the Target Environment panel. You can modify TICINSTX to dynamically alter these libraries or parameters, or to add installation steps that may be required at your site. TICJCLX, TICGENB2, TICGENB4 and TIRGENB2 The CLIST TICJCLX creates default JCL for the batch Host Encyclopedia functions. This CLIST runs in the foreground and can be modified to allow you to intercept the JCL it creates and display or modify it. The interception has at least two possible uses: You can use custom panels to add variables to the batch job. If the job is code generation, you must also add the new variables to the skeleton entries in members TICGENB2, TICGENB4, and TIRGENB2. For security reasons, you can submit the job directly from TICJCLX. C 2 Installation Guide for Host Encyclopedia and Host Construction

147 Common Encyclopedia Exits The CLIST that calls TICJCLX passes two variables: JCLTYPE and JOBSUB. JCLTYPE identifies the batch procedure to be submitted. Possible values for JCLTYPE are: C Code generation E Encyclopedia functions JOBSUB contains the name of the JCL skeleton used for JCL creation. The JCL skeleton is made available to this CLIST to allow you to submit your own job. TICJCLX allows the display or input of additional variables for a customized background task if custom variables are used. (Remember to modify SLIB members TICGENB2, TICGENB4, and TIRGENB2 to recognize the new variables.) A return code from TICJCLX is tested to determine subsequent processing. The effect of each return code is: Return Code Effect 0 All OK. AllFusion Gen must perform the job submit and update JCL profile variables. 8 All OK. AllFusion Gen must bypass job submit but still update JCL cards to Profile pool. greater than 8 Error. Do not submit from AllFusion Gen or update JCL cards. Exit with the returned code. Appendix C: Using Encyclopedia Exits C 3

148 DB2 Secondary Authorization IDs DB2 Secondary Authorization IDs AllFusion Gen supports the use of DB2 secondary authorization IDs for Package Binds. However, you can make changes to the AllFusion Gen supplied CLISTs TICINSTX and TICJCLX and to the skeletons TICGENB2 and TIRGENB2 to provide this support. You can use this strategy to pass other ISPF variables to batch codegen. AllFusion Gen automatically installs a generated application into a specified IMS, CICS, or TSO target environment in the foreground or the background. Instructions for changing TICINSTX, TICJCLX, TICGENB2, and TIRGENB2 to support DB2 secondary authorization IDs are provided in the following sections. Use these instructions as examples of how to change the components to adhere to your site standards without affecting AllFusion Gen software. TICINSTX TICINSTX provides a default installation for an application generated by AllFusion Gen. You can modify TICINSTX as follows to meet your site requirements. 1. Create a copy of the CLIST TICINSTX in a library concatenated ahead of the AllFusion Gen supplied Clist library. 2. Modify TICINSTX to accept DB2 secondary authorization IDs when invoked in either foreground or background. a. Find the BIND PLAN (section following the BINDIT label in TICINSTX). The section of Clist TICINSTX for BIND is shown next. BINDIT: + CONTROL MSG /* SAVE VARIABLES FOR USE BY THE USER EXIT */ ISPEXEC VGET TICDSID1 ASIS SET BPLFLAG = Y SET BPLSYS = &STR(&TICDSID1) SET BPLREL = COMMIT SET BPLVAL = BIND ISPEXEC VPUT (BPLFLAG BPLSYS BPLNAME BPLLIST BPLLIBS + BPLISOL BPLVAL BPLREL + BPLMEM0 BPLMEM1 BPLMEM2 BPLMEM3 BPLMEM4 BPLMEM5 + BPLMEM6 BPLMEM7 BPLMEM8 BPLMEM9 BPLMEM10 BPLMEM11 + BPLMEM12 BPLMEM13 BPLMEM14 BPLMEM15 BPLMEM16 + BPLMEM17 BPLMEM18 BPLMEM19 BPLMEM20) SHARED /* CALL THE EXIT */ %TICEXBPL C 4 Installation Guide for Host Encyclopedia and Host Construction

149 DB2 Secondary Authorization IDs /* RETRIEVE THE VARIABLES FROM THE EXIT */ ISPEXEC VGET (BPLFLAG BPLSYS BPLNAME BPLLIST BPLLIBS + BPLISOL BPLVAL BPLREL + BPLMEM0 BPLMEM1 BPLMEM2 BPLMEM3 BPLMEM4 BPLMEM5 + BPLMEM6 BPLMEM7 BPLMEM8 BPLMEM9 BPLMEM10 BPLMEM11 + BPLMEM12 BPLMEM13 BPLMEM14 BPLMEM15 BPLMEM16 + BPLMEM17 BPLMEM18 BPLMEM19 BPLMEM20) SHARED IF &STR(&BPLLIST) ^= &Z THEN SET PKLIST = &STR(PKLIST(&BPLLIST)) /* IF USER REQUESTS IT, SKIP THE BIND IF &BPLFLAG = N THEN GOTO ENDUP %TICSDIS CMD(MSG) OBJ(&STR(&LOADNAME)) + MSG('BIND IN PROGRESS') TEMP(YES) /* IF THERE ARE NO DBRMS, BIND WITHOUT THE MEMBER PARAMETER IF &STR(&BPLMEM0) = &Z THEN GOTO NOMBRS DSN SYSTEM(&BPLSYS) /* IF DSN SESSION FAILS TO START, DO NOT ATTEMPT TO BIND SET RC = &LASTCC IF &RC > 0 THEN DO SET ERRMSG = &STR(BIND FAILED) GOTO ERROR END /* TRAP UP TO 100 ERROR MESSAGES SET SYSOUTTRAP = 100 BIND PLAN(&BPLNAME.) + MEMBER( + &BPLMEM0 + &BPLMEM1 + &BPLMEM2 + &BPLMEM3 + &BPLMEM4 + &BPLMEM5 + &BPLMEM6 + &BPLMEM7 + &BPLMEM8 + &BPLMEM9 + &BPLMEM10 + &BPLMEM11 + &BPLMEM12 + &BPLMEM13 + &BPLMEM14 + &BPLMEM15 + &BPLMEM16 + &BPLMEM17 + Appendix C: Using Encyclopedia Exits C 5

150 DB2 Secondary Authorization IDs &BPLMEM18 + &BPLMEM19 + &BPLMEM20 ) + &PKLIST + LIBRARY(&STR(&BPLLIBS)) + ACTION(REPLACE) RETAIN + ACQUIRE(USE) RELEASE(&BPLREL) + EXPLAIN(NO) VALIDATE(&BPLVAL) + ISOLATION(&BPLISOL) FLAG(W) END /* END DSN SESSION */ SET RC = &LASTCC GOTO ENDBIND b. Change the last line of the bind statement by adding the &OWNER parameter so that the line looks like: ISOLATION(&BPLISOL) FLAG(W) &OWNER TICGENB2 and TIRGENB2 Skeletons TICGENB2 and TIRGENB2 Skeletons The DB2 secondary authorization variable is passed through OWNERID. (Variables are passed as control card input through the DATAIN DD Statements.) Change TICGENB2 and TIRGENB2 as follows so that the DB2 secondary authorization variable is available to background installation: 1. Create a copy of TICGENB2 and TIRGENB2 in a library concatenated ahead of the AllFusion Gen SLIB library. 2. Add the OWNERID variable to TICGENB2 and TIRGENB2. See the samples of TICGENB2 and TIRGENB2 that follow. An example of passing OWNERIDas a variable in TICGENB2 is shown next. TICGENB2 //DATAIN DD * )TB OWNERID!SHR!&OWNERID MODLNAME!SHR!&MODLNAME TISNAME!SHR!&TISNAME TICSLIB1!SHR!&TICSLIB1.. //* END OF RUNTIME VARIABLE INPUT An example of passing OWNERID as a variable in TIRGENB2 is shown next. TIRGENB2 //DATAIN DD * )TB OWNERID!SHR!&OWNERID C 6 Installation Guide for Host Encyclopedia and Host Construction

151 DB2 Secondary Authorization IDs.. //* END OF RUNTIME VARIABLE INPUT Each line after the line beginning with )TB contains the name of an ISPF variable, the pool to which it belongs and the value for that variable being passed to batch codegen. TICGENB4 TICGENB4 builds job steps for RI trigger generation and installation. It does not need to be modified for DB2 secondary authorization because this applies to bind processing. Bind processing is done at the load module level. TICJCLX TICJCLX provides default JCL tailoring for the various batch Host Encyclopedia functions. Change TICJCLX as follows to allow it to pass the DB2 secondary authorization ID variable to batch. 1. Create a copy of AllFusion Gen CLIST TICJCLX in a library concatenated ahead of the AllFusion Gen CLIST library. 2. Find the section with label USER LOGIC HERE A sample section of TICJCLX SET CLSTNAME = &NRSTR(#### STARTING TICJCLX CLIST ####) ISPEXEC VGET (TICCARD1 TICCARD2 TICCARD3 TICCARD4) SHARED ISPEXEC VGET (TICCARD5 TICCARD6 TICCARD7 TICCARD8) SHARED ISPEXEC VGET (TICCARD9 TICCARDA) SHARED /******************************************/ /* USER LOGIC HERE */ /******************************************/ /* ISPEXEC DISPLAY PANEL(????) */ /* SET RC = &LASTCC */ /* IF (&RC = 0) AND (&ZCMD = ) THEN??? */ /* IF (&RC = 8) THEN EXIT CODE(&RC) */ /* IF (&RC > 8) THEN EXIT CODE(&RC) */ /******************************************/ ISPEXEC VPUT (TICCARD1 TICCARD2 TICCARD3 TICCARD4) SHARED ISPEXEC VPUT (TICCARD5 TICCARD6 TICCARD7 TICCARD8) SHARED ISPEXEC VPUT (TICCARD9 TICCARDA) SHARED SET CLSTNAME = &NRSTR(#### STARTING TICJCLX CLIST ####) Appendix C: Using Encyclopedia Exits C 7

152 DB2 Secondary Authorization IDs EXIT CODE(0) 1. and add the following lines after the USER LOGIC HERE label: /*CUSTOMIZATION TO USE DB2 SECONDARY AUTH ID IF &JCLTYPE = C THEN DO IF &JOBSUB = TICGENBT OR + &JOBSUB = TICGENB2 OR + &JOBSUB = TIRGENB2 THEN DO /* CALL USERCLIST FOR OWNERID VALUE */ %USRCLIST END END Create a User CLIST A user CLIST is required to collect the value for the new ISPF variable OWNERID. In the earlier example of TICJCLX, the user CLIST was called USRCLIST. You can modify this name. The user CLIST is called by either TICINSTX or TICJCLX depending on whether foreground or background is requested. For more information on user CLIST, see the Sample User CLIST. A sample user CLIST is shown next /* USER PROVIDED CLIST TO OBTAIN THE VALUE OF THE OWNERID VARIABLE /* PROVIDE SOME METHOD FOR SETTING THE VALUE OF OWNERID WRITER ENTER DB2 OWNER ID ===> READ OWNERID /* SAVE THE VALUE FOR OWNERID IN THE SHARED POOL, SO /* TICINSTX /* CAN USE IN BATCH OR FOREGROUND ISPEXEC VPUT OWNERID SHARED /* TICEXBPK TICEXBPK is invoked prior to a DB2 package bind to allow you to: Change input parameters Suppress or replace the package bind The following ISPF variables are saved (VPUT) in the shared pool prior to the call to this exit. They are populated with the values that will be passed to the bind if the exit does not change them. If the exit changes these variables, the new values are used. C 8 Installation Guide for Host Encyclopedia and Host Construction

153 DB2 Secondary Authorization IDs BPKFLAG Y=do the bind, N=suppress the bind BPKSYS DB2 Subsystem where bind is to be done BPKCOLL Collection ID BPKLOC Location of the DBMS (DB2 subsystem) BPKMBR DBRM name BPLLIBS DDNAMEs of the DBRM libraries BPKOWNER DBRM owner (authorization ID) BPKISOL CS, RR, UR BPKVAL BIND, RUN BPKREL COMMIT, DEALLOCATE To use the input value of a variable, you must provide a VGET for it. To change a variable, you must provide a SET command and a VPUT for it. The CLIST delivered with the product has examples of the VGET and VPUT instructions, but they are commented out. To suppress the bind entirely, change BPKFLAG to N. To replace the bind with your own, change BPKFLAG to N and add your own bind to the exit. See CLIST TICBNPK for an example of a package bind. TICEXBPL TICEXBPL is invoked prior to a DB2 plan bind to allow you to: Change input parameters Suppress or replace the plan bind The following ISPF variables are saved (VPUT) in the shared pool prior to the call to this exit. They are populated with the values that will be passed to the bind if the exit does not change them. If the exit changes these variables, the new values will be used instead. BPLFLAG Y=do the bind, N=suppress the bind BPLSYS DB2 Subsystem where bind is to be done BPLNAME Plan name BPLLIST Package list entries (if any) Appendix C: Using Encyclopedia Exits C 9

154 DB2 Secondary Authorization IDs BPLMEM0-20 DBRM member names (if any) BPLLIBS DDNAMEs of the DBRM libraries BPLISOL CS, RR, UR BPLVAL BIND, RUN BPLREL COMMIT, DEALLOCATE To use the input value of a variable, you must provide a VGET for it. To change a variable, you must provide a SET command and a VPUT for it. The CLIST delivered with the product has examples of the VGET and VPUT instructions, but they are commented out. To suppress the bind entirely, change BPLFLAG to N. To replace the bind with your own, change BPLFLAG to N and add your own bind to the exit. See CLIST TICINSTX for an example of a plan bind. C 10 Installation Guide for Host Encyclopedia and Host Construction

155 Appendix D: Setting Model Code Pages After the encyclopedia s code page is set, the code page of all existing models must be set by one of the following methods: Method 1 If you added the Euro sign to your models and uploaded the changes to the encyclopedia, run the code page translation utility to translate the text to the correct code points and update the MODEL_LANG_CODE column in the DMDL. From the ready prompt or TSO option to run the utility, execute: %TIUXLAT SRCCPID(sss) DSTCPID(dddd) MODEL( model name ) Where: sss the model s current code page. For example, the code page of the encyclopedia before applying the Euro code page update. This value is found by querying the model s DMDL table. SQL member CGHE20 can be used as a template for this query. An error message terminates the command when sss is not equal to the current code page of the model. dddd the new code page for the model. This is the same value set for the encyclopedia in step 1. An error message terminates the command when dddd is not the encyclopedia default code page. Method 2 If your model does not contain the Euro sign, you can run the SQL member CGHE20 to update the MODEL_LANG_CODE column for the model row in the DMDL table. Note: If your encyclopedia contains a combination of models, run the TIUXLAT utility for each model containing a Euro sign. After all the models are translated, run the SQL from step 2 to change the MODEL_LANG_CODE for all other models in the encyclopedia. Appendix D: Setting Model Code Pages D 1

156 Customizing Code Page Translation Customizing Code Page Translation View data that is passed between the client and server is translated from the client s code page to the server s code page, and vice versa. The function that performs this translation, TIRXLAT, uses the client s code page value, which is passed from the client to the server, and the host s code page value to locate a translation table. (For additional information about code pages and internationalization considerations, see the CSE Guide.) In AllFusion Gen r7, r7.5, and r7.6, the Dynamic Runtime modules TIRCRUNC (CICS) and TIRCRUNI (IMS) replace runtimes TIRENTC (CICS) and TIRENTI (IMS). AllFusion Gen applications built with releases prior to AllFusion Gen r7 must still use TIRENTC and TIRENTI runtimes. In many parts of the world, several different code pages can be used within a particular company or country. If your installation uses a code page on the z/os system that is different from the supplied default*, a JCL procedure is provided to build a code page specific version of the Dynamic Runtime modules (TIRCRUNC and TIRCRUNI). The procedure is called MKCRUN for AllFusion Gen r7 and later releases and MKTIRE for previous releases. A sample of MKCRUN can be found in the SAMPLIB data set. For a list of the supported code tables, see Code Page Translation Tables. * Even when you use a code page on the z/os system that matches the supplied default you may benefit from rebuilding the TIRCRUNC and TIRCRUNI runtimes using the MKCRUN procedure. This is because the supplied runtime contains extra code page pairs that you may not need and are removed when using the MKCRUN procedure. Note: If TIRCRUNC and TIRCRUNI do not contain the translation table the client and server are using, the CICS log displays an IEFT abend error and IMS abends with a U3500. Use MKCRUN JCL to build a version of TIRCRUNx modules that support the required code page combination. D 2 Installation Guide for Host Encyclopedia and Host Construction

157 Customizing Code Page Translation Customizing the Code Page Translation Table for Your Environment In AllFusion Gen r7, r7.5, and r7.6, the debug and non-debug versions of the TIRCRUNx runtimes have the same names but are supplied in different libraries: LOAD library for non-debug and LOADTRCE library for debug. The supplied TIRCRUNx runtimes were built using a default code page of 037 (US EBCDIC) only. To change the code page table for your environment before submitting the MKCRUN JCL 1. Modify the JCL and supply a valid job card. 2. In the GEN step supply the indicated data for the following statements: The STEPLIB DD statement, supply the z/os Language Environment Runtime data set and the AllFusion Gen load library In the IEFGXTP DD statement, supply the AllFusion Gen IEFXLATE data set name In the SYSIN DD statement, supply the code page pairs required to support the server default code page. The first number is the EBCDIC code page value. The second number is the ASCII code page value. Note: Leave the entries that are marked required but remove all the comments. 3. In the TIRXINFO step, make the following changes: Note: The CODEPAGE step has been renamed to TIRXINFO. The CODEPAGE CSECT is no longer used. It has been replaced with exit TIRXINFO, the source of which is supplied in the SAMPLIB member of the same name. Change the SYSIN data set name to match the AllFusion Gen SAMPLIB or the location of your TIRXINFO code. Change the supplied TIRXINFO as follows: Locate the line DEFCODEP DC CL8' ' and change to the value of the EBCDIC code page required. Locate the line DEFPADCH DC XL4' ' and change to the value of the padding character for the EBCDIC code page selected. Save the changes but do not assemble or link-edit TIRXINFO. 4. In the LKCICS step, supply the following information: In the SYSLIB DD statement, supply the AllFusion Gen LOAD library. In the SYSLMOD DD statement, supply the load library to write the modified version of TIRCRUNC. Verify that the load library is PDSE (DSNType = library) data set. Appendix D: Setting Model Code Pages D 3

158 Customizing Code Page Translation 5. In the LKIMS step, supply the following information: In the SYSLIB DD statement, supply the AllFusion Gen LOAD library. In the SYSLMOD DD statement, supply the load library to write the modified version of TIRCRUNI. Verify that the load library is PDSE (DSNType = library) data set. Note: Use the next two steps to customize the debug versions of the TIRCRUNC and TIRCRUNI runtimes respectively. 6. In the LKCICSD step, supply the following information: In the SYSLIB DD, supply the AllFusion Gen LOADTRCE library. In the SYSLMOD DD, supply the load library to write the modified version of the debug TIRCRUNC. Verify that the load library is PDSE (DSNType = library) data set. 7. In the LKIMSD step, supply the following information: In the SYSLIB DD statement, supply the AllFusion Gen LOADTRCE library. In the SYSLMOD DD statement, supply the load library to write the modified version of the debug TIRCRUNI. Verify that the load library is PDSE (DSNType = library) data set. 8. After you have the modified versions of TIRCRUNC and TIRCRUNI, follow the steps to deploy these runtimes in Install Gen Runtime Load Library Modules in the appendix Configuring IMS and CICS. Note: If a translation table is defined that TIRCRUNC or TIRCRUNI does not support, the CICS log displays an IEFT abend error, and IMS abends with U3500. Contact CA Technical Support for help in adding the desired translation table to TIRCRUNC or TIRCRUNI. MKCRUN JCL The JCL for the MKCRUN procedure can be found in the AllFusion Gen SAMPLIB library in a member named MKCRUN. The procedure is extensively documented. D 4 Installation Guide for Host Encyclopedia and Host Construction

159 Code Page Translation Tables Code Page Translation Tables The AllFusion Gen suite of products supports a wide variety of code pages. The following is a list of code pages and the supported environments. Code Page Applicable Country or Language z/os Encyclopedia z/os Runtime Workstation Runtime 037 USA, Americas Y Y 273 Germany Y Y 277 Denmark Y Y 278 Finland Y Y 280 Italy Y Y 284 Spain Y Y 285 United Kingdom Y Y 297 France Y Y 420 Egypt, Saudi Arabia Y Y 424 Israel Y Y 437 American PC Y 500 Belgium Y Y 808 RussianA-Euro Y 813 Iso Y 819 Iso8891 Y 838 Thailand Y 848 UkrainianA-Euro Y 849 BelorussianA-Euro Y 850 SwissPC Y 852 AlbanianPC Y 855 IBMPC-Cyrillic Y 857 IBMPC-Turkish Y 858 MultilingualA Y 860 Unused PC Y 862 IBMPC-Hebrew Y 863 French Canadian PC Y Appendix D: Setting Model Code Pages D 5

160 Code Page Translation Tables Code Page Applicable Country or Language z/os Encyclopedia z/os Runtime Workstation Runtime 865 Danish PC Y 869 Greek PC Y 870 Albanian Y Y 871 IcelandE Y 872 CyrllicA-Euro Y 874 Thai PC Y 875 Greek Y 901 BalticA-Euro Y 902 EstoniaA-Euro Y 912 Iso89121 Y 915 Cyrillic Y 916 Iso8858 Y 918 ArabicECUA Y 920 Iso88599 Y 930 Japan Traditional Y Y 931 Japanese Y 932 s-jisx208 large character Y 933 Korea Y Y 935 Simplified Chinese Y Y 936 IBM-936 Chinese Y 937 Traditional Chinese Y Y 939 Japan-new CUA (default) Y Y 940 EUC-0x208 Unix large character Y 942 IBM-CUA large character Y 949 EUC-Korean Y 950 IBM Big 5 Y 1006 ISO S-Arabic Y 1025 Cyrillic Y 1026 Turkish Y D 6 Installation Guide for Host Encyclopedia and Host Construction

161 Code Page Translation Tables Code Page Applicable Country or Language z/os Encyclopedia z/os Runtime Workstation Runtime 1047 POSIX_1 Y 1089 ISO-Arabic Y 1140 Americas Euro, USA Y Y 1141 Austria, Germany Euro Y Y 1142 Denmark, Norway Euro Y Y 1143 Finland, Sweden Euro Y Y 1144 Italy Euro Y Y 1145 Latin American Spanish, Spain E Y Y 1146 United Kingdom Euro Y Y 1147 France Euro Y Y 1148 Belguim, Switzerland Euro Y Y 1149 Iceland Euro Y 1153 Latin Euro Y 1154 Cyrillic Euro Y 1155 Turkey Euro Y 1156 Baltic Euro Y 1157 Estonia Euro Y 1158 Ukraine Euro Y 1164 Vietnamese Euro Y 1201 UTF8 Unicode Y 1250 MS Latin 2 Y 1251 MS Cyrillic Y 1252 Microsoft PC Y 1253 MS Greece Y 1254 MS Turkish Y 1255 MS Hebrew Y 1256 MS Arabic Y 1257 Baltic Euro Y 1258 MS Unknown Y Appendix D: Setting Model Code Pages D 7

162 Code Page Translation Tables Code Page Applicable Country or Language z/os Encyclopedia z/os Runtime Workstation Runtime 1381 IBM 1381 Y 1386 IBM 1386 Y 1388 Simplified Chinese Y Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y ISO Y D 8 Installation Guide for Host Encyclopedia and Host Construction

163 Index & &SYSPREF, 4-12 A AllFusion Gen, establishing access to, 3-8 assign storage group names screen, 4-16 assign VSAM names screen, 4-18 B BIEFXCPY, 3-4 BLDRPROF, 3-4 C CEINSTAL dialog, 4-2 CEINSTAL dialog, starting, 4-7 CEJOB02, 3-4 CEJOB03, 3-4, 5-2, 6-5 CEJOB04, 3-4, 5-3 CEJOB05, 3-4, 5-3, 6-6 CEJOB05A, 3-4, 6-6 CEJOB06, 3-4, 5-3, 7-3 CEJOB07A, 3-4, 5-3, 6-6, 7-3 CEJOB07B, 3-4, 5-3, 6-6 CEJOB08, 3-4, 5-3, 6-6 CEJOB09, 3-4, 5-3, 6-6, 7-3 CEJOB11, 3-4, 6-7, 7-4 CEJOB2, 5-2 CEJOB5A, 5-3 CEUCLEN, 3-5 CEUCOPY, 3-5, 6-6, 7-3 CEUINCR, 3-5 CEUREOR, 3-5, 6-6, 7-3 CEUXPND, 3-5 CICS debugging with TIRENTD, B-30 establishing block mode support, B-7 CICS for TCP/IP, customizing, B-15 CICS variables, setting, 4-25 Client/server support, establishing, B-9 CLISTs, building, 4-30 COBOL compiler variables, setting, 4-21 Code page translation, customizing, D-2 code pages, understanding, 4-13 Communications support, establishing, B-12 CVJOB04A, 3-5, 6-5 CVJOB04B, 3-5, 6-5 D DB2 PLAN_TABLE, creating, 4-31 DB2 precompiler variables, setting, 4-22 DB2 secondary authorization ids, C-4 DB2 variables, setting, 4-15 DEFCICS batch job, B-11 Diagram Trace Facility (DTF), enabling, B-29 CEJOB10, 3-4, 5-4, 7-4 Index 1

164 download model screen, 7-7 DXCPID table, 4-13 E ECHO and ECHOI communications support, B-12 edit job card screen, 4-10 encyclopedia creating VSAM parameters, A-9 how to create storage group parameters, A-9 how to estimate larger encyclopedia sizes, A-2 running jobs to create, 5-2 size estimating methods, A-4 testing functions of, 5-6 upgrading, 6-5 encyclopedia variables, setting, 4-12 External Call Interface (ECI), customizing for, B-27 F function keys, 4-9 H I identify source and target encyclopedias screen, 7-2 IMS, establishing block mode support, B-5 IMS variables, setting, 4-26 installation overview, 1-3 prerequisites, 1-2 installation variables defining, 4-2 installing, 4-29 installation variables management menu, 4-8 ISPF, other considerations, 3-8 ISPLLIB, 3-7 ISPMLIB, 3-7 ISPPLIB, 3-7 ISPPROF, 3-8 ISPSLIB, 3-8 ISPTLIB, 3-7 J JCL variables, setting, 4-11 job cards, editing, 4-10 HE2LOAD, 7-3 HEIUNLD, 7-3 host encyclopedia copying data to, 7-1 copying models to, 7-6 host encyclopedia maintenance menu, 4-8 L LAPPHELP, 3-5 LIBDEF, 3-7 library names, setting, 4-9 LU6.2, customizing for, B-13, B-14 Index 2 Installation Guide for Host Encyclopedia and Host Construction

165 M R main menu, 4-7 master checklist, 2-15 MFS device types, selecting, 4-28 model management screen, 7-7 models conversion, 6-4 cross-copying, 7-9 MQSeries Transaction Dispatcher, installing, B-25 P panels assign storage group names, 4-16 assign VSAM names, 4-18 download model, 7-7 edit job card, 4-10 host encyclopedia maintenance menu, 4-8 identify source and target Encyclopedias, 7-2 installation variables management Menu, 4-8 main menu, 4-7 model management, 7-7 regional settings, 4-14 select MFS device types, 4-28 set CICS variables, 4-25 set compiler variables, 4-21 set DB2 precompiler variables, 4-22, 4-23 set DB2 variables, 4-15 set encyclopedia variables, 4-12 set IMS Variables, 4-26 set JCL variables, 4-11 set library names, 4-9 set RPROF variables, 4-27 set target system variables menu, 4-19 target environment configuration, 4-20 upload model/subset, 7-8 regional settings screen, 4-14 regional settings, defining, 4-13 return codes, evaluating, 3-9 RPROF variables, setting, 4-26 RUNSTATS, 5-7 S schema, release levels, 6-3 screen samples, set compiler variables, 4-21 select MFS device types screen, 4-28 set CICS variables screen, 4-25 set compiler variables screen, 4-21 set DB2 precompiler variables screen, 4-22, 4-23 set DB2 variables screen, 4-15 set encyclopedia variables screen, 4-12 set IMS variables screen, 4-26 set JCL variables screen, 4-11 set library names screen, 4-9 set RPROF variables screen, 4-27 set target system variables menu, 4-19 site-specific variables AllFusion Gen library name, 2-5 CICS, 2-12 COBOL compiler, 2-10 DB2 database, 2-9 DB2 subsystem, 2-11 encyclopedia, 2-8 IMS, 2-12 JCL, 2-7 RPROF, 2-13 worksheets, 2-5 sizing considerations, A-1 SQL and JCL, building, 5-2 Index 3

166 storage group names, assigning, 4-16 SYSPROC, 3-7 T target environment configuration screen, 4-20 target environment, configuration, 4-20 target system variables, setting, 4-19 TCP/IP Direct Connect Option for IMS, B-23 technical requirements, 2-5 TICEXBPK exit, C-8 TICEXBPL exit, C-9 TICGENB2 skeleton, C-6 TICGENB4 skeleton, C-7 TICINSTX CLIST, C-2, C-4 TICJCLX CLIST, C-2, C-7 TILPARMS, how to modify, 4-2 TILTAB50 effect of a missing, 4-6 how space parameters are created, 4-4 how to use, 4-5 origins of, 4-5 relationship between TILTAB50 and TILPARMS, 4-6 TIRENTD load module, B-30 TIRGENB2 skeleton, C-6 transition guidelines, 6-3 U upload model/subset screen, 7-8 user access, enabling, 5-10, 6-8, 7-5 user CLIST, creating, C-8 USERLIB, 3-5 V VSAM names, assigning, 4-18 Z z/os API, overview, 8-1 Index 4 Installation Guide for Host Encyclopedia and Host Construction