VISION:Builder VISION:Two

Transcription

1 VISION:Builder VISION:Two Release 13.5 Installation and Support Manual for MVS BUINM135.PDF/D

2 Copyright Sterling Software, Inc. All Rights Reserved Sterling Software Information Management Division 5900 Canoga Avenue P.O. Box 4237 Woodland Hills, CA Notice to U.S. Government Users Under Contracts Subject to DFARS Restricted Rights Legend Sterling Software, Inc. makes no warranty, either expressed or implied, with respect to VISION:Builder, VISION:Transact, VISION:Two, and VISION:Workbench, their merchantability or fitness for a particular purpose, other than as expressly provided in the license agreement. This document and the software programs described herein are the proprietary and confidential information of Sterling Software, Inc. No use may be made of these software programs or this document without the express written consent of Sterling Software, Inc. or its authorized licensors. Use, duplication, or disclosure is subject to restrictions stated in the Rights in Technical Data and Computer Software clause at DFAR , or subparagraphs (c) (1) and (2) of the Commercial Computer Software Restricted Rights clause of 48 CFR , as applicable. Notice - Notwithstanding any other lease or license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the Government regarding its use, reproduction and disclosure are as set forth in the applicable Government Contract or Purchase Order. Trademarks Sterling Software and VISION:Builder are registered trademarks of Sterling Software, Inc. VISION:Inform, VISION:Transact, VISION:Two, and VISION:Workbench are trademarks of Sterling Software, Inc. MVS, DB2, and IBM are registered trademarks of IBM Corporation. IMS and DATABASE 2 are trademarks of IBM Corporation. Windows 3.1, Windows 95, and Windows NT are registered trademarks of Microsoft Corporation. Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated. Some of the other designations used in this document are trademarks of other companies not associated with Sterling Software, Inc. Such use of these trademarks is for information purposes only and is not intended to be generic in nature nor to imply that such trademarks are owned by or licensed to Sterling Software, Inc.

3 Contents Chapter 1 Introduction... 1 Description of the Installation Tape... 2 Installation Overview... 3 The System Tape Unload... 3 The System Preparation... 4 The System Setups... 4 Chapter 2 System Tape Unload... 5 Step 1 Transfer System Tape File 1 to a PDS... 5 Step 2 Transfer System Tape Files 2 through 9 to Disk Data Sets... 7 Chapter 3 System Preparation... 9 Step 3 Product Activation... 9 Step 4 Parameter Modules Modification Step 5 Install the DB2 Database Access Module, MARKSQL i

4 Teradata Information Step 6 Verify Basic System Installation Chapter 4 System Setups Step 7 Install Restricted System Modifications (RSMs) Step 8 Install the Program Analyzer File Definitions and Requests Step 9 Static Own Code Integration Relink Step 10 Setup for Use with the TSO Command Processor OQL and BQL Parameter Module Modification TSO Help Data Set OLX Command Processors Step 11 Copy VISION:Builder Message Modules to LPA VISION:Workbench for DOS VISION:Workbench for ISPF Setup Requirements Allocating VISION:Workbench for ISPF Run-Time Libraries Allocation Requirements Additional Information Concerning Load Libraries Using the LIBDEF Feature Additional Information on ISPFILE Allocations The List Data Set and Internal Work Files Invoking VISION:Workbench for ISPF Adding an Option to a standard ISPF Primary Menu Using the ISPSTART Command Using Other VISION:Workbench for ISPF Subsections VISION:Builder Installation and Support Manual (MVS) ii

5 Optional Setup for VISION:Workbench for ISPF Preprocessing Your Panel Library Customizing Job Submission Skeletons LMF SUPPORT Step 12 Quick Start Utility Setup Step 13 Merge Load Libraries Chapter 5 System Support and Maintenance Applying System Modifications Problem Reporting and Processing VISION:Builder and COMLIB Problem Reporting VISION:Workbench for DOS Problem Reporting VISION:Workbench for ISPF Problem Reporting Problems and User Code Appendix A JCL Appendix B VISION:Builder Parameter Modules M4PARAMS and M4LEPARM M4SFPARM Defining Additional Data Validation Symbols Change Automatic Date Validation Format MARKLIBP VISION:Builder Installation and Support Manual (MVS) iii

6 MARKSQL Query Language Parameters BQLPARM Online Language Parameters OQLPARM Appendix C Sample ISPF Startup CLIST Appendix D Invocation Panels Appendix E Skeleton and User Panel Listings Contacting Sterling Software Index VISION:Builder Installation and Support Manual (MVS) iv

7 Chapter 1 Introduction All releases of VISION:Builder and VISION:Two are delivered on 3480 tape cartridges or 9-track reel tapes as specified by the customer. A unique system activation key code for each installation number is included with each system tape. Other identifying information is entered on the external label of the tape. VISION:Builder should be used on MVS System release 4.3 or higher. The instructions that follow describe procedures for the installation and activation of VISION:Builder and VISION:Two software systems. Any questions regarding the installation should be directed to Sterling Software Technical Support. All output generated during the installation, along with the system tape, should be saved for future reference. The basic installation process is identical for all users. The JCL needed to complete the installation is provided in the first file of the system tape. Once the first file is transferred to a PDS, only minor tailoring of the provided JCL is needed to complete the installation. 1

8 Chapter 1 Introduction Description of the Installation Tape When the unique system activation key code is installed, the system becomes operational and is set to the system model along with the features selected for the specific installation number. If you are a VISION:Two user, whenever VISION:Builder is used in this manual, assume VISION:Two. There are notations within the installation instructions to indicate which steps are optional based on the features and capabilities selected and utilized at each customer site. Description of the Installation Tape The VISION:Builder System Tape supplied for the MVS environment is a standard labeled tape containing nine files. The following table shows the order and content of the nine files on the tape. File File 1 File 2 File 3 File 4 File 5 File 6 Description VISION:Builder System WORKLIB PDS COMLIB Release 4.5 Load Library VISION:Workbench for ISPF Release CLIST Library VISION:Workbench for ISPF Release Panel Library VISION:Workbench for ISPF Release Message Library VISION:Workbench for ISPF Release Skeleton Library VISION:Builder Installation and Support Manual (MVS) 2

9 Chapter 1 Introduction Installation Overview File File 7 File 8 File 9 Description VISION:Workbench for ISPF Release Load Library VISION:Builder Release Load Library VISION:Builder System and component RSMLIB PDS. Installation Overview The VISION:Builder installation is divided into three major sections: The System Tape Unload The System Preparation The System Setups The System Tape Unload All the JCL, Source Code, and Control Statements required during the installation process are provided for the installer in file 1 of the system tape. The only JCL that needs to be prepared by the installer is the IEBCOPY JCL to transfer the contents of file 1 to a PDS. This JCL is shown in Figure 1 on page 6 as part of the first step of the installation procedure. Appendix A JCL starting on page 56 contains all the JCL members referenced in the following installation procedures. An alphabetic list and the complete detail of each member is shown. Once the first file is transferred to a PDS, all remaining installation JCL is available for tailoring and use. In Step 2, the remaining files from the system tape will be transferred to disk. At this point, the system tape can be saved, and only the disk data sets will be used to complete the installation process. VISION:Builder Installation and Support Manual (MVS) 3

10 Chapter 1 Introduction The System Preparation The System Setups Installation Overview This portion of the installation process prepares the VISION:Builder software system and its components for use. The system is activated for execution for each customer (installation number) based on their system model and features. Also, some of the general portions of the system and components can be tailored, customized, and prepared for use according to the specific needs and requirements of the installation site. In the final portion of the preparation process, a simple job is run to demonstrate that the basic VISION:Builder System installation was successful. With a software system as diverse as VISION:Builder, there are several capabilities and facilities that need some additional setup in order to operate within each installation site environment. The setup steps that apply to each site will vary, depending on how the software system and components are utilized at each site. VISION:Builder Installation and Support Manual (MVS) 4

11 Chapter 2 System Tape Unload In this portion of the VISION:Builder system installation, you transfer the elements and components from the system tape to disk data sets. Two simple steps are performed to create a group of disk data sets that contain the entire host portion of the VISION:Builder software system and components. Everything you need to prepare and set up the system is contained in the disk data sets. Step 1 Transfer System Tape File 1 to a PDS The contents of file 1 on the VISION:Builder system tape must be transferred from the tape to a PDS. The PDS will contain all the JCL, source code, and control statements The WORKLIB PDS data set that is created by this step will be referenced throughout the remainder of the installation process. needed to complete the installation. Figure 1 shows the JCL to transfer file 1 to a PDS. Please prepare the IEBCOPY job as described in Figure 1. 5

12 Chapter 2 System Tape Unload Step 1 Transfer System Tape File 1 to a PDS //* MEMBER BLCOPY1 //********************************************************************** //* THIS JOB COPIES FILE 1 //* FROM THE VISION:Builder SYSTEM TAPE TO DISK //* //* BEFORE YOU RUN THIS JOB, REVIEW JCL AND SPECIFY: //* //* THE INPUT TAPE VOLUME SERIAL NUMBER AND UNIT TYPE. //* THE OUTPUT DISK DATASET NAME, UNIT AND VOLUME SERIAL NUMBER. //* (THE DISK DATASET SPACE IS MINIMUM FOR A 3380 DASD DEVICE.) //* //* NOTE - THE DISK DATASET DCB MUST BE CODED AS SHOWN. //* SOME MEMBERS OF THE PDS ARE INPUT TO UTILITIES THAT //* HAVE "BLKSIZE" SPECIFICATION REQUIREMENTS. //* //********************************************************************** //* //COPY1 EXEC PGM=IEBCOPY,REGION=1024K //SYSPRINT DD SYSOUT=* //INPUT DD DSN=VISION.BUILDER.FILE1,DISP=OLD, // UNIT=TAPEC,LABEL=(1,SL,EXPDT=98000), // VOL=(PRIVATE,RETAIN,SER=(TAPVOL)) //OUTPUT DD DSN=BUILDER.BL135.WORKLIB,DISP=(NEW,CATLG), // UNIT=SYSDA,VOL=SER=DSKVOL, // SPACE=(TRK,(20,5,15)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200) //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,15) //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,15) //SYSIN DD * COPY INDD=INPUT,OUTDD=OUTPUT /* Figure 1 Transfer System Tape File 1 to a WORKLIB PDS VISION:Builder Installation and Support Manual (MVS) 6

13 Chapter 2 System Tape Unload Step 2 Transfer System Tape Files 2 through 9 to Disk Data Sets Step 2 Transfer System Tape Files 2 through 9 to Disk Data Sets This step transfers all the remaining VISION:Builder System Tape Files to Disk Data sets. The data sets created by Step 2, along with the WORKLIB PDS created by Step 1, comprise the entire VISION:Builder software system and components. Using the JCL member BLCOPY2 in the WORKLIB PDS, run a job to transfer files 2 through 9 from the system tape to disk. The following table shows the list of all the data sets that are to be created by the system unload Steps 1 and 2. The characteristics are shown along with basic space requirements. Refer to Appendix A JCL starting on page 56 for the BLCOPY2 (and BLCOPY1) JCL that contains the detail characteristics for each data set. The disk data set names assigned to the unloaded system tape files, and shown in this table, are default names. For continuity purposes, the names shown here are used throughout the installation process instructions and in all the JCL examples. The BUILDER.BL135.LOADLIB data set contains SAS-C Routine Modules, Release These modules are needed during executions of the VISION:Builder system. Data Set Name DSORG RECFM LRECL BLKSIZE TRKS DIRBLKS BUILDER.BL135.LOADLIB PO U BUILDER.BL135.RSMLIB PO FB BUILDER.BL135.WORKLIB PO FB BUILDER.CL045.LOADLIB PO U BUILDER.WB055.CLIST PO FB BUILDER.WB055.LOADLIB PO U BUILDER.WB055.MSGS PO FB BUILDER.WB055.PANELS PO FB BUILDER.WB055.SKELS PO FB VISION:Builder Installation and Support Manual (MVS) 7

14 Chapter 2 System Tape Unload Step 2 Transfer System Tape Files 2 through 9 to Disk Data Sets The system tape unload is complete. The disk data sets contain the entire VISION:Builder software system and all the elements needed to complete the installation. Save the system tape as a backup. VISION:Builder Installation and Support Manual (MVS) 8

15 Chapter 3 System Preparation The VISION:Builder system and its components are now installed in disk data sets. In order to get the system operational, some preparation must be done. This chapter has information on the steps and preparation activities that need to be performed to get the basic system operational. Some of the steps are not required for every installation site. Some steps are optional. It all depends on the system model and features and the extent to which the system and its capabilities are utilized at each site. Step 3 Product Activation This step must be performed to make the VISION:Builder system operational. Each installation has a unique system activation key code and installation number that are included on the letter accompanying the system tape. The code unlocks the system and sets the model and features as designated for the installation. There are two methods that can be used to install the system activation key code: a TSO CLIST or a batch job. 9

16 Chapter 3 System Preparation Step 3 Product Activation To activate the system using TSO, perform the following steps to execute the CLIST member ABUILDER from the WORKLIB PDS 1 While in TSO, type: EXEC 'BUILDER.BL135.WORKLIB(ABUILDER)' 2 Press the Enter key to execute. 3 Enter your 5-character installation number. For example, type and press the Enter key. 4 Enter your system activation key code. The code is entered without quotation marks as one continuous string, dashes included. For example, type 1111-ABCD E4F and press the Enter key. 5 Enter the name of the VISION:Builder load library in quotation marks. For example, type BUILDER.BL135.LOADLIB and press the Enter key. 6 The information entered is now displayed for review. If the information is correct, type Y and press the Enter key. A message is displayed indicating that the activation key code was successfully applied. If the information keyed is not correct, type N and press the Enter key. The CLIST is terminated and you just start over again. If there is a problem, messages are displayed indicating the problem and the CLIST is terminated. To apply the system activation key code using a batch job, use the JCL member BLACTIV in the WORKLIB PDS. You supply the installation number and the system activation code as PARM information. The program APPLYACT is in the VISION:Builder load library and the activation code is applied to the same load library. The output directed to the SYSPRINT DD indicates the result of the run and tells you that the activation code has been successfully installed. VISION:Builder Installation and Support Manual (MVS) 10

17 Chapter 3 System Preparation Step 4 Parameter Modules Modification If any errors are encountered, they are listed in the SYSPRINT output. Correct the problem and rerun the job. With either method, once the system activation key code is successfully installed, your system is operational. Please contact Sterling Software Technical Support if you have any problems with the installation of the system activation key code. Now you can run a job to produce a VISION:Builder banner page. The banner page contains information about the software, your system model number, your system options, and the standard system parameter settings currently in the M4PARAMS and MARKLIBP modules. The banner page information will be useful during the remainder of the installation process. To produce the banner page, use the JCL member BLBANR in the WORKLIB PDS. You need to supply the data set names of the VISION:Builder and COMLIB component load libraries. Save the banner page output that is directed to the M4LIST DD for reference. Note that with Release 13.5, VISION:Builder utilizes the IBM Language Environment (LE, formerly LE/370). The LE run-time time library must be available when running VISION:Builder jobs. If the LE modules are not available at your facility, an RSM (Restricted System Modification) is available that, when installed in the VISION:Builder loadlib, will cause VISION:Builder to bypass using any LE modules. See Step 7 Install Restricted System Modifications (RSMs) on page 21 that will point you to the information needed to apply RSMs to your system. Step 4 Parameter Modules Modification The VISION:Builder system and the COMLIB component contain parameters, options, and settings that can be tailored for each installation. The default values are contained in modules that can be modified, assembled, and link edited as needed at any time. VISION:Builder Installation and Support Manual (MVS) 11

18 Chapter 3 System Preparation Step 4 Parameter Modules Modification If no modifications are required, this step can be bypassed. You can always perform this step at a later time. The four parameter modules are: M4PARAMS VISION:Builder primary parameter module M4SFPARM VISION:Builder special validation parameter module M4LEPARM VISION:Builder Language Environment Parameter Module MARKLIBP COMLIB Component parameter module These are listed in detail in Appendix B VISION:Builder Parameter Modules starting on page 111 of this manual. The source code for the parameter modules is contained in the WORKLIB PDS. If you are using IBM LE services, you must have access to the LE Run-time library using concatenation to your VISION: Builder load library or other method. Before you modify any of these modules, you should create a backup copy of the original source code for future reference. Once you have reviewed and modified the parameter modules as needed, use the JCL member BLASM1 in the WORKLIB PDS to assemble and link edit the M4PARAMS, M4LEPARM, and M4SFPARM modules into the VISION:Builder load library. Use JCL member CLASM1 in the WORKLIB PDS to assemble and link edit the MARKLIBP module into the COMLIB load library. You only need to run the job steps that correspond to the modules being changed. For each step you choose to run, specify the WORKLIB PDS name, the source member name, and the load library name. The M4PARAMS, M4LEPARM, M4SFPARM, and MARKLIBP modules are independently loaded at run time and, therefore, can be stored in load libraries that are separate from VISION:Builder and COMLIB. If used, the separate load library will need to be VISION:Builder Installation and Support Manual (MVS) 12

19 Chapter 3 System Preparation Step 5 Install the DB2 Database Access Module, MARKSQL concatenated before the VISION:Builder and COMLIB load libraries. In this way, you can tailor several different versions of these modules to satisfy varying requirements for separate user groups. Step 5 Install the DB2 Database Access Module, MARKSQL Only customers with the DB2 Interface system option and RS2 need to perform this step. The MARKSQL module contains slots used to hold the SQL statements needed to access the tables of your DB2 databases during application processing runs. This module must go through the DB2 application program preparation process described in IBM's DATABASE 2 Application Programming Guide manuals. The MARKSQL source code module supplied in the WORKLIB PDS is assembled ito generate source statements that become the plan required by DB2 to run VISION:Builder applications that access DB2 tables. The number of statement slots in the generated MARKSQL plan modules limits the number of tables that can be accessed in an application run. In the MARKSQL module, the parameter &MAX controls the number of statement slots generated. The number of statements needed to access DB2 tables in an execution run varies according to which processing options are used in the application. For example, if MOSAIC processing is not used, the number of tables that can be accessed is equal to the &MAX value. However, if MOSAIC processing is used to access a DB2 table, three statement slots within the MARKSQL plan module are used instead of one. This results in lowering the number of tables available in the run. Applications using the updating facility can also cause multiple statement slots to be used per table. The application source listing shows the total number of statements that are prepared for use during a particular processing run. An explanation describes the purpose for each prepared statement. VISION:Builder Installation and Support Manual (MVS) 13

20 Chapter 3 System Preparation Step 5 Install the DB2 Database Access Module, MARKSQL The MARKSQL source module supplied in the WORKLIB PDS allows for 50 statement slots. An application program can use up to 50 individual DB2 tables. You can change the parameter within the MARKSQL module to allow for access to more or less than 50 tables (statement slots). To change the parameter, simply change the value in the following statement that appears after the introductory comments of the MARKSQL module: During the link edit step, some linkage editors may issue warning messages and a condition code 4. These can be ignored. For example, message IEW2646W issued by the Binder Linkage Editor is a warning about RMODE Conflicts when the IBM Module DSNALI is included. The module MARKSQLC is correctly linked and the message can be ignored. &MAX SETA 50 MAXIMUM NUMBER OF SQL STATEMENTS PER APPL. Once the appropriate parameter value has been set or the default value accepted, the MARKSQL module must be assembled to generate the final source statements to be prepared for DB2. This assembly does not generate any object code but uses the assembler as a source code generator. The source code generated is precompiled (to produce a DBRM), assembled (to produce an object module), and link edited (to produce a load module). Use the JCL member BLDB2A in the WORKLIB PDS to assemble and prepare the MARKSQL modules. There are three ways the MARKSQL module is prepared, to correspond with the three methods for attaching to DB2. The three attachment facilities used are CALL, IMS, and TSO. The JCL member BLDB2A uses the standard IBM procedure DSNHASMH to accomplish the prepares and produce three separate modules named MARKSQLC, MARKSQLI, and MARKSQLT. Also, the MEM parameter is used to specify plan names. The module names and default plan names for each attach facility are as follows: Module Name Attach Facility Plan Name MARKSQLC CALL MARKDB2 MARKSQLI IMS MARKDLI MARKSQLT TSO MARKIV VISION:Builder Installation and Support Manual (MVS) 14

21 Chapter 3 System Preparation Step 5 Install the DB2 Database Access Module, MARKSQL You might need to confer with your DB2 database administrator before proceeding with this process. You only need to prepare the MARKSQL modules that correspond to the attach facilities you will use. When executing your application under one of the attach facilities, the plan name must be provided to DB2. When using CALL Attach, supply the plan name in the Run Parameter (RP) DB2 statement within the application source code. When using IMS Attach, supply the plan name on the control statement input from the specified DDITV02 DD. When using TSO Attach, the terminal monitor program RUN control statement contains the plan name entry. See the Environment Manual for samples of the JCL needed to run your application using the three attach facilities. After the required MARKSQL modules are preprocessed, compiled, and link edited, the application plans generated by the DB2 preprocessor must undergo an additional process called binding. The BIND function can be invoked using either DB2I (DB2 Interactive) using the TSO terminal monitor program with the appropriate control statements or using batch JCL. Note that VISION:Builder does not require repeatable read isolation, and you should specify cursor stability isolation when binding the plans to allow greater concurrent access to your DB2 tables. See the IBM DATABASE2 Application Programming Guide for your environment for additional information on the bind process. You may need to confer with your DB2 database administrator before proceeding with the BIND process. You only need to BIND the plan names for the attach facilities that you will be using. You can choose either of the two methods to perform the BIND process for the prepared MARKSQL modules that will be used to Attach to DB2. Figure 2 shows the panels displayed when doing the BIND using the DB2I (DB2 Interactive) facility. Or, you can use the JCL member BLDB2B in the WORKLIB PDS to BIND the plan names in a batch job. If VISION:Builder Installation and Support Manual (MVS) 15

22 Chapter 3 System Preparation Step 5 Install the DB2 Database Access Module, MARKSQL at any time you make changes to the MARKSQL modules, you need to repeat the preparation and bind process. Be aware that you must use a BIND REPLACE action, not REBIND, when you perform a new bind. VISION:Builder Installation and Support Manual (MVS) 16

23 Chapter 3 System Preparation Step 5 Install the DB2 Database Access Module, MARKSQL Member name MARKDB2 on the third display is for the CALL Attach. For the IMS Attach, change it to MARKDLI. For the TSO Attach, change it to MARKIV. COMMAND === 5 DB2I PRIMARY OPTION MENU Select one of the following DB2 functions and press ENTER. 1 SPUFI (Process SQL statements) 2 DCLGEN (Generate SQL and source language declarations) 3 PROGRAM PREPARATION (Prepare a DB2 application program to run) 4 PRECOMPILE (Invoke DB2 precompiler) 5 BIND/REBIND/FREE (BIND, REBIND, or FREE plans or packages) 6 RUN (RUN an SQL program) 7 DB2 COMMANDS (Issue DB2 commands) 8 UTILITIES (Invoke DB2 utilities) 9 CATALOG VISIBILITY (Invoke catalog dialogs) D DB2I DEFAULTS (Set global parameters) X EXIT (Leave DB2I) PRESS: END to exit HELP for more information BIND/REBIND/FREE COMMAND === 1 Select one of the following and press ENTER: 1 BIND PLAN (Add or replace an application plan) 2 REBIND PLAN (Rebind existing application plan or plans) 3 FREE PLAN (Erase application plan or plans) 4 BIND PACKAGE (Add or replace a package) 5 REBIND PACKAGE (Rebind existing package or packages) 6 FREE PACKAGE (Erase a package or packages) PRESS: ENTER to process END to exit HELP for more information BIND PLAN COMMAND === Enter DBRM data set name(s): 1 MEMBER... === MARKDB2 2 PASSWORD... === 3 LIBRARY... === DBRMLIB.DATA 4 ADDITIONAL DBRMS?... === NO (YES to include more DBRMs) Enter options as desired: 5 PLAN NAME... === MARKDB2 (Required to create a plan) 6 CHANGE CURRENT DEFAULTS?.. === NO (NO or YES) 7 ENABLE/DISABLE CONNECTIONS? === NO (NO or YES) 8 INCLUDE PACKAGE LIST?... === NO (NO or YES) 9 OWNER OF PLAN (AUTHID)... === (Leave blank for your primaryid) 10 QUALIFIER... === (For tables, views, and aliases) 11 CACHESIZE... === (Blank, or value ) 12 ACTION ON PLAN... === REPLACE (REPLACE or ADD) 13 RETAIN EXECUTION AUTHORITY. === YES (YES to retain user list) 14 CURRENT SERVER... === (Location name) PRESS: ENTER to process END to save and exit HELP for more information Figure 2 Using DB2I to Perform the BIND Function VISION:Builder Installation and Support Manual (MVS) 17

24 Chapter 3 System Preparation Step 6 Verify Basic System Installation Teradata Information Customer sites using the Teradata Database System need to prepare their MARKSQL module in a slightly different manner. To install the MARKSQL module for use with Teradata databases, use the JCL member BLDB2T in the WORKLIB PDS to assemble and prepare the MARKSQL module. The result will be the module named MARKSQLT. Once the module is prepared, you can perform any Teradata tasks needed to get the module ready for run-time use (such as binding). This module name is the same as the TSO Attach module used for access to IBM DB2 tables. You may want to store the Teradata version of MARKSQLT in a separate load library, especially if your site uses both IBM and Teradata databases. When running your VISION:Builder application, you must provide the appropriate DD statements needed by Teradata for profile and control information. See your Teradata manuals for the proper coding of this information. In addition, the Teradata run-time library must be included in the STEPLIB, JOBLIB, or link list concatenation when running your applications. The VISION:Builder application source code MUST NOT contain a Run Parameter (RP) DB2 statement because this will cause VISION:Builder to attempt a Call Attach using the MARKSQLC module. The absence of an RP DB2 statement, when running a standard (non-ims) VISION:Builder processing step will cause an Attach using the MARKSQLT module. Step 6 Verify Basic System Installation At this point the basic VISION:Builder System is installed. Chapter 4 System Setups starting on page 21 details additional setup steps for utilizing other VISION:Builder capabilities. The use of these other capabilities is dependent on the preferences at each installation site. In order to verify that the basic VISION:Builder system is installed and operational, a simple job stream is run. This job stream exercises several different functions of the system. VISION:Builder Installation and Support Manual (MVS) 18

25 Chapter 3 System Preparation Step 6 Verify Basic System Installation Use the JCL member BLIVP in the WORKLIB PDS to perform the installation verification process. All that you need to supply is the JOBLIB DD data set names for the VISION:Builder and COMLIB component load libraries. No permanent data sets are created by this job stream. Note that VISION:Builder utilizes the IBM Language Environment (LE, formerly LE/370). The LE run-time library must available when running VISION:Builder jobs. If the LE modules are not available at your facility, an RSM (Restricted System Modification) is available that, when installed in the VISION:Builder loadlib, will cause VISION:Builder to bypass using any LE modules. See Step 7 Install Restricted System Modifications (RSMs) on page 21, which will point you to the information needed to apply RSMs to your system. The job stream contains the following steps. Each step will complete with a condition code zero (0000). If you are using IBM LE services, you must have access to the LE Run-time library using concatenation to your VISION: Builder load library or other method. INIT DEFRUN1 PROCRUN A library utility run to allocate and initialize a common library (M4LIB). If you set Item Tracking in MARKLIBP to 1 or 3, then you must add an IT statement to the M4INPUT for this step. A definition run that catalogs a file and a table definition in the M4LIB. A single step processing run to read an instream data file and produce two reports. The cataloged file and table definitions are utilized from the M4LIB. The Advanced Syntax Language (ASL) translator is invoked. Your standard SORT program is called to sort the report data. The input file data is processed and two reports are produced. VISION:Builder Installation and Support Manual (MVS) 19

26 Chapter 3 System Preparation Step 6 Verify Basic System Installation LIBRUN DEFRUN2 A library utility run to back up (dump), reinitialize, and restore the contents of the M4LIB. This is a process that condenses the M4LIB. A definition run to produce glossary listings of the file and table definitions. The basic installation is complete and verified. Please review Chapter 4 System Setups starting on page 21 to determine which optional setup steps are needed for your site. VISION:Builder Installation and Support Manual (MVS) 20

27 Chapter 4 System Setups This chapter contains a variety of system setups that you may need to perform. The specific steps that you perform depend on which of the following capabilities and facilities your installation site is using or plans to use. Any of the steps in this chapter can be performed as required. Step 7 Install Restricted System Modifications (RSMs) An RSM is a customization to the system that satisfies unique site requirements. If the previous release of your VISION:Builder system had RSMs installed, you may need to install the current release of the RSMs. This should make your system functionally equivalent to that of your previous version. You can tell if your system has an RSM applied by looking at the banner page. Any system modification with a value less than 200 is an RSM and a candidate for a comparable upgrade RSM. If in doubt, contact Technical Support. 21

28 Chapter 4 System Setups Step 8 Install the Program Analyzer File Definitions and Requests All the RSMs for VISION:Builder, COMLIB, and VISION:Workbench for ISPF are contained as members in the RSMLIB PDS transferred to disk from the system tape. The JCL members BLZARK, CLZARK, and WBZARK in the WORKLIB PDS contain sample job steps to apply and remove SMs from the various components. Please see the ANSRZARK Utility Manual for more information about RSMs and the use of ANSRZARK. Contact Sterling Software Technical Support if you have any questions regarding the use of RSMs for your site. The RSMs member names start with BL, CL, and WB, indicating the applicable component (VISION:Builder, COMLIB, and VISION:Workbench for ISPF, respectively). The number portion of the RSM member name is sequenced 100 through 200. The numbers for the current component releases correspond to the same number in the previous release. The letter following the RSM number is an operating environment indicator. Each member name contains a suffix of XX or ZZ. The XX means the member contains the description and the purpose of the RSM. The ZZ means the member contains the input control statements for the ANSRZARK utility program. Step 8 Install the Program Analyzer File Definitions and Requests If you will be using the Program Analyzer Facility (PAL), you need to perform this step. The VISION:Builder file definitions and application requests are cataloged into a common library (M4LIB) for use in the production of the various PAL Reports. VISION:Builder Installation and Support Manual (MVS) 22

29 Chapter 4 System Setups Step 9 Static Own Code Integration Relink For proper Program Analyzer support, three file definitions (IGCPALVB, IGCPALWK, and IGCPALRS) and a request group (IGCPAL) must be cataloged. The request group IGCPAL contains the following request names: IGCPALFT IGCPALDR IGCPAL2P IGCPAL4 IGCPAL5P IGCPALRS IGCPAL1 IGCPAL3 IGCPAL4P IGCPAL6 IGCPALEF IGCPAL2 IGCPAL3P IGCPAL5 IGCPAL7 To install the Program Analyzer, you must initialize an M4LIB and catalog the file definitions, the individual requests, and the request group into the M4LIB. Use the JCL member BLPAL in the WORKLIB PDS to catalog the PAL items. The job will catalog the items into a BDAM format M4LIB. The INIT (initialize an M4LIB) and DEFRUN1 (definition run) steps should receive a condition code 0, indicating successful completion. The PROCRUN (processing scan only run) step receives a condition code 4, indicating successful completion of the scan only run. Review the source listing to insure that no type 3 or higher error messages were issued. The PAL facility is now ready to use. The M4LIB data set will be needed when the PAL facility is used to produce reports. Step 9 Static Own Code Integration Relink This step is only needed if you use the Static Integration Facility for your user-written M4OWN module. The purpose and use of this facility is described in the Environment Manual. This step can be skipped if static own code integration is not used. VISION:Builder Installation and Support Manual (MVS) 23

30 Chapter 4 System Setups Step 9 Static Own Code Integration Relink Use JCL member BLRLNK in the WORKLIB PDS to run a job that relinks the VISION:Builder main program module and includes your user-written version of the module M4OWN. You need to supply your M4OWN module as an object or a load module. See the JCL comments that indicate the data sets needed for the link edit job. During the link edit, various warning and error messages are issued. The following messages can be safely ignored: IEW0461 IEW0161 WARNING-SYMBOL PRINTED IS AN UNRESOLVED EXTERNAL REFERENCE, NCAL WAS SPECIFIED. WARNING-EXCLUSIVE CALL FROM SEGMENT NUMBER PRINTED TO SYMBOL PRINTED - XCAL WAS SPECIFIED. These messages cause a condition code 4, which can be safely ignored. Also, if you comment out the DLILIB DD (or the OBJLIB DD) statement in the link edit JCL, a condition code 8 will occur and the following message is issued and can be ignored: If you need to restore the original M4OWN module delivered with the system to turn off and remove Static Own Code, the WORKLIB PDS contains the original M4OWN object code. Point to the WORKLIB PDS on the OBJLIB DD statement and run the BLRLNK job. IEW0432 ERROR-LIBRARY NAME PRINTED CANNOT BE OPENED, DD STATEMENT MAY BE MISSING. Link edit storage requirements vary from installation to installation. However, the normal region size and default link edit size parameter values used at your installation for links to a loadlib should be suitable for this link edit step. If you have a problem, you can use a region size of 1024K and a link edit size parameter of (310K, 84K) as a guideline. VISION:Builder Installation and Support Manual (MVS) 24

31 Chapter 4 System Setups Step 10 Setup for Use with the TSO Command Processor Step 10 Setup for Use with the TSO Command Processor The following sections are for sites that use the OLX, OQL, OFI, BQL, and BFI features of VISION:Builder. If you do not use any of these facilities, proceed to Step 11 Copy VISION:Builder Message Modules to LPA on page 27. These features continue to be delivered as part of the system for compatibility purposes and in support of legacy systems still using these features of the product. OQL and BQL Parameter Module Modification The Online Executive (OLX) facility uses modules containing parameters, options, and settings that can be tailored to each installation. The default values are contained in modules that can be modified, assembled, and link edited as needed at anytime. If no modifications are required, this section can be bypassed. The two parameter modules are: OQLPARM BQLPARM Online Query Language (OQL, OLX, OFI) parameter module Batch Query Language (BQL, BFI) parameter module These are listed in detail in Appendix B VISION:Builder Parameter Modules starting on page 111 of this manual. The source code for the parameter modules is contained in the WORKLIB PDS. If you are going to modify any of these modules, you should create a backup copy of the original source code. Once you have reviewed and modified the parameter modules as needed, you can use the JCL member BLASM2 in the WORKLIB PDS to assemble and link edit new versions of the modules into the VISION:Builder component load libraries. The JCL in member BLASM2 has examples for the assembly and link edit of both of the parameter modules. You only need to run the steps that correspond to the modules you change. VISION:Builder Installation and Support Manual (MVS) 25

32 Chapter 4 System Setups Step 10 Setup for Use with the TSO Command Processor For each step you choose to run, specify the WORKLIB PDS name, the source member name, and the load library name. TSO Help Data Set OLX Command Processors If your site does not utilize the OLX, OFI, or OQL facility, this section can be skipped. The TSO help members for the OLX, OFI, or OQL facility must be made available to the general TSO help processor during terminal sessions. The TSO help members can be copied to a separate help data set that is concatenated with the other data sets specified on the SYSHELP DD statement in the TSO logon procedure. Another option is to copy the help members directly into one of the help data sets already specified on the SYSHELP DD statement in the TSO logon procedure. Use the JCL member BLCOPY3 in the WORKLIB PDS to copy the TSO help members to a help data set. The BLCOPY3 job allocates a new data set and copies the help members from the WORKLIB PDS to the new data set. If you are using an existing data set, skip the ALLOC step in the BLCOPY3 JCL. The copy job replaces members of the same name in the existing data set. Users of the OLX facility may want to copy some of the command processing modules to the SYS1.LINKLIB (or concatenation thereof) so that TSO can find them. This allows users to specify the VISION:Builder load library as an operand of the M4EXEC command. Otherwise, the VISION:Builder load library must be part of the STEPLIB DD or allocated as a STEPLIB for the TSO session. This specification is optional. Use the JCL member BLCOPY4 in the WORKLIB PDS to copy some of the OLX Command Modules to a SYS1.LINKLIB or concatenation thereof. Specify the VISION:Builder load library and the SYS1.LINKLIB data set names. The copy job replaces members of the same name in the copied to data set. VISION:Builder Installation and Support Manual (MVS) 26

33 Chapter 4 System Setups Step 11 Copy VISION:Builder Message Modules to LPA Step 11 Copy VISION:Builder Message Modules to LPA This optional step can be done if you want to copy the VISION:Builder messages modules to your LPA libraries for shared access. The VISION:Builder messages are contained in modules within the VISION:Builder load library. These modules are loaded into memory (the region) as needed during the various execution runs. The messages modules are marked as reentrant and could be placed in the LPA. They are then shared by all VISION:Builder runs and reduce the amount of storage used in the region for each job. The size of each message module is 4K. Also, an index module and a global message module are used in the message handling mechanism. Use the JCL member BLCOPY5 in the WORKLIB PDS to copy the VISION:Builder messages modules from the VISION:Builder load library to an LPA load library. Specify the VISION:Builder load library and the LPA load library data set names. The copy job replaces members of the same name in the copied to data set. VISION:Workbench for DOS One of the components of the VISION:Builder software system is a PC based application programming development tool. This component runs on a PC workstation under DOS. It can also be run in a DOS window under Windows 3.1, Windows 95, and Windows NT. This tool helps VISION:Builder users to prepare their definitions and applications. All coding is checked for errors and inconsistencies at the PC without the need to connect to the host. Once the application and definitions are ready, the users transfer the VISION:Builder source statements to the host for actual submission and processing. VISION:Builder Installation and Support Manual (MVS) 27

34 Chapter 4 System Setups VISION:Workbench for ISPF Setup Requirements VISION:Workbench for DOS is delivered on diskette. The diskette should be distributed among all VISION:Builder users. The diskette is NOT copy protected, you can make unlimited copies as needed. Contact Sterling Software Technical Support if you cannot locate the diskette in your installation package or have other problems. The details for installing and using VISION:Workbench for DOS are in the VISION:Workbench for DOS User's Guide. Refer the user to that manual to install the software on a PC workstation. VISION:Workbench for ISPF Setup Requirements Allocating VISION:Workbench for ISPF Run-Time Libraries VISION:Workbench for ISPF runs as an application under IBM s ISPF/PDF Facility, which is an extension of TSO, and takes advantage of the many standard services available under ISPF. In order to integrate VISION:Workbench for ISPF into the ISPF environment, the VISION:Workbench for ISPF libraries and the appropriate VISION:Builder, VISION:Transact, VISION:Inform, and COMLIB component load libraries must be made available to the ISPF facility. There are two primary methods for making the VISION:Workbench for ISPF libraries known to ISPF. One method is to add the libraries to the TSO logon procedure or the ISPF startup CLIST. The other method is to use the ISPF LIBDEF service to dynamically modify your ISPF library concatenations. Check with the systems group at your facility to confirm which method you should use to get the VISION:Workbench for ISPF libraries allocated for ISPF sessions. VISION:Builder Installation and Support Manual (MVS) 28

35 Chapter 4 System Setups VISION:Workbench for ISPF Setup Requirements Once you have determined how your existing ISPF libraries are being allocated, you can allocate the necessary VISION:Workbench for ISPF libraries by concatenating them to the existing ISPF library allocations and allocating the VISION:Workbench for ISPF libraries in the front of each concatenation sequence. Allocation Requirements The following list shows the required ISPF ddnames and the VISION:Workbench for ISPF data sets that should be associated with them. All VISION:Workbench for ISPF data set names displayed are the suggested names shown earlier in this document. These names should be changed to reflect those names actually used during your installation process. Note that the VISION:Workbench for ISPF CLIST library was delivered on the installation tape as a fixed blocked data set with a record length of 80 and a block size of If your installation prefers a variable blocked format, you may want to copy the contents of this library over to a different CLIST library of the proper format for your site. ddname: Data set name: ddname: Data set names: SYSPROC BUILDER.WB055.CLIST ISPLLIB BUILDER.WB055.LOADLIB (all sites) BUILDER.CL045.LOADLIB (all sites) BUILDER.BL135.LOADLIB (VISION:Builder sites) TRANSACT.TR075.GENLIB (VISION:Transact sites) INFORM.LOADLIB (VISION:Inform sites) ISPLLIB functions as a task library. It is searched before the STEPLIB allocations, system link libraries, or the system link pack area. VISION:Builder Installation and Support Manual (MVS) 29

36 Chapter 4 System Setups VISION:Workbench for ISPF Setup Requirements VISION:Workbench for ISPF Release 5.5 requires the specific releases of the associated software products and components, as shown in the following table: Software Product Release Number VISION:Builder Release 13.5 VISION:Transact Release 7.5 VISION:Inform Release 3.0 COMLIB Release 4.5 Additionally, with Release 13.5 of VISION:Builder and Release 7.5 of VISION:Transact, the IBM Language Environment (LE, formerly LE/370) is utilitized. The LE run-time library must be available when running the validation function of VISION:Workbench for ISPF. If the LE modules are not available at your facility, RSMs (Restricted System Modifications) are available that, when installed in the VISION:Builder and VISION:Transact loadlibs, will cause VISION:Builder and VISION:Transact to bypass using any LE modules. ddname: Data set name: ISPPLIB BUILDER.WB055.PANELS VISION:Builder Installation and Support Manual (MVS) 30

37 Chapter 4 System Setups VISION:Workbench for ISPF Setup Requirements If you have chosen to preprocess your VISION:Workbench for ISPF panel library, you should concatenate the preprocessed panel library, rather than the panel source library, to this ddname. Preprocessing the panel library is an optional installation step discussed in Optional Setup for VISION:Workbench for ISPF on page 45 of this document. ddname: Data set name: ISPMLIB BUILDER.WB055.MSGS This ddname is used by ISPF to locate the text of all messages issued by ISPF applications like VISION:Workbench for ISPF. ddname: Data set name: ISPSLIB BUILDER.WB055.SKELS The ISPSLIB ddname is used to specify the location of ISPF file tailoring skeletons used by VISION:Workbench for ISPF. ddname: Data set name: ISPFILE This data set name should reference a file tailoring output library. Sites that use the VISION:Workbench for ISPF Generate facility must preallocate this file. VISION:Builder Installation and Support Manual (MVS) 31

38 Chapter 4 System Setups VISION:Workbench for ISPF Setup Requirements The IMPORT option of VISION:Workbench for ISPF requires a data set to save information entered during the IMPORT function dialogs. The entered information is then available from session to session. The data set should be preallocated and cataloged. The data set characteristics are as follows: DSORG PO RECFM FB LRECL 80 BLKSIZE multiple of 80 SPACE (TRK,(5,2,2)) Once the data set has been defined, you need to add the data set to the ISPF startup CLIST allocations. The free and allocation entries for the ddname DEFTLIB should be coded as follows: FREE F(DEFTLIB) ALLOC F(DEFTLIB) DA( user.defined.name ) SHR VISION:Builder Installation and Support Manual (MVS) 32