App Builder Host Pi

BluePhoenix AppBuilder 2.0.3.1

Planning and Installing AppBuilder for the Mainframe

BluePhoenix AppBuilder 2.0.3.1Planning and Installing AppBuilder for the MainframeMarch, 2003

Corporate HeadquartersBluePhoenix SolutionsVlierwerf 7B4704 SB RoosendaalThe Netherlands+31 (0) 165 399 401+31 (0) 165 396 308 faxwww.bluephoenixsolutions.nl

USA HeadquartersBluePhoenix Solutions USA, Inc.8000 Regency ParkwayCary, NC 27511United States+1 919.380.5100+1 919.380.5111 faxwww.bluephoenixsolutions.com

© 1992-2003 BluePhoenix Solutions

All rights reserved.

BluePhoenix is a trademark of BluePhoenix Solutions. All other product and company names mentioned herein are for identification purposes only and are the property of, and may be trademarks of, their respective owners.

Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and various other non-U.S. patents.

The software supplied with this document is the property of BluePhoenix Solutions, and is furnished under a license agreement. Neither the software nor this document may be copied or transferred by any means, electronic or mechanical, except as provided in the licensing agreement.

BluePhoenix Solutions has made every effort to ensure that the information contained in this document is accurate; however, there are no representations or warranties regarding this information, including warranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes no responsibility for errors or omissions that may occur in this document. The information in this document is subject to change without prior notice and does not represent a commitment by BluePhoenix Solutions or its representatives.

http://www.bluephoenixsolutions.com


TABLE OF CONTENTS


1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Architecture Evaluation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Project Infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Organization and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Pilot Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Commitment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Development Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Quality Assurance Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Data Management Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Application Development Operations Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Production Team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Finding the Latest Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Before Installing AppBuilder Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12AppBuilder Software Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13AppBuilder Product Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

2 Preinstallation Requirements and Application Maintenance . . . 2-1

Understanding the Installed Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Installing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Execution Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

3 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Hardware and DASD Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Supported Third-party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

4 The Host Installation Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Using the Host Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Packing List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Maintenance History Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2INI Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Repository - System Association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Enable and Disable Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Displaying Information about Systems and Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Planning and Installing AppBuilder for the Mainframe 3

Installation Job Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Installation Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Backing Out a Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Installation Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Installing the Host Installation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

5 Installing the Enterprise Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Packing List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1


Installing the AppBuilder Enterprise Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Starting the Host Installation Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Option 1 - System Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Option 1 - Create System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Perform Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Option 2 - Unload AppBuilder Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21Option 3 - Create System Installation Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Option 4 - Submit System Installation Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

Option 2 - Repository Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Option 1 - Create Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25Optional User Libraries for Component Prepares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41

Postinstallation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

Installing MVS Migration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48

Installing Enterprise Preparation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51Updating Server Repository @SERVER INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Starting the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Adding an Additional Repository to the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52@SERVER INI Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53

Installation Verification Using TIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54

6 Installing Batch Preparation Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1



Installing the Batch Preparation Workbench Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Option 1 - System Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Option 2 - Repository Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Apply Repository Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Postinstallation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Installation Verification Using TIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

4 Planning and Installing AppBuilder for the Mainframe

7 Installing Report Writer Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1



Installing Report Writer Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Option 1—System Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3SYSJOB2 - Set Tape Backup Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Option 2 - Repository Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Postinstallation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Installation Verification Using TIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

8 Installing CICS Online Preparation Workbench and Enterprise Server8-1


Installation Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Installing CICS Online Preparation Workbench and Enterprise Server Software. . . . . . . . . . . . . . 8-2Option 1 - System Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Option 2 - Repository Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Postinstallation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27CICS 3270 Converse Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30

Installing TCP/IP Listener for IBM CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Meeting Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Performing Post-Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34DNAINI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35

Configuring AppBuilder for a Multi-CICS Region Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37AppBuilder Repository CICS Load Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38AppBuilder CICS VSAM Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38AppBuilder/CICS Transient Data Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38AppBuilder/CICS Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38AppBuilder/CICS Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39AppBuilder/CICS Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39

9 Installing IMS Online Preparation Workbench and Enterprise Server9-1


Installation Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Installing IMS Online Preparation and Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Option 1 - System Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Option 2 - Repository Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Postinstallation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-251 - Database DBRC Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-252 - Database Dynamic Allocation Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-253 - IMS Stage 1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26Stage 1 Requirements for AppBuilder User Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27

Table of Contents 5

IMS 3270 Converse Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32

A AppBuilder Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Explanation of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

@HPSENV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2REPOSITORY Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2QUALIFIER Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3DB2 Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4FILES Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5TRACE Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10JCL Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11SKEL Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14METHOD Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14CRUD Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-15RMI Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16REPDSN Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17TSODD Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-19VIEWS Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22COMM Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22EXITS Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-23

@HPSSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24REPOSITORY Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25

@MIGRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25QUALIFIER Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25REPDSN Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-26

MIGENVn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-26MIGRATION Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-26CRUD Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-33MIGSTATE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-36MIGDEFAULT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-36MIGOVERRIDE Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-39QASTATUS Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-42

@MVSENV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-42REPOSITORY Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-42NLS Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-42LINKAGE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-43ASM Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-43COBOL Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-44C Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-44PL/I Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-45MVSPGM Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-46ISPF Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-46DB2 Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-47TSO Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-48HSM Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-48ACCMETH Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-48FILES Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-48CODEGEN Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-49KANJIPRN Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-50

@RBDENVn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-50RBDPKG Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-50


SUPERPR Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-51ANALYZE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-51PREPARE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-52INSTALL Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-55ADVICE Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-57RBDSTATE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-58

@SEERENV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-58RBDCLUP Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-58SUPERPR Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-59ANALYZE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-59PREPARE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-59PREPARE_PLATFORM Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-60EXECENV Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-62INSTALL Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-62RBDSTATE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-63

USRENVn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-63VERSION Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-64QUALIFIERS Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-64PRODUCT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-64PREPARE Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-66HPSRT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-84USRLIBS Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-85DB2 Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-87REGIONS Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-91

CICS Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-92HPSRT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-92PREPOPT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-95CICS Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-95INTRTEST Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-98REGION1 Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-99

HPSBTCH Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-102HPSRT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-102BATCH Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-104

IMS Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-104HPSRT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-104PREPOPT Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-106IMS Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-106REGION1 Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-107

B CICS Table Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Table Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1DFHDCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1DFHFCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2DFHPLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4DFHTCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4DNA531P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-6DSNCRCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-7HMPBTBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-9HPESDUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11HPESDUK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11AB2031 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-12

Table of Contents 7

HPSPLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21

C VTAM Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

MO6HPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

MODELU62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

MODESCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

MODESNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

AppBuilderMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

D HPSCGAP, HPICGAP, HPEUCGP, and Sample Batch JCL . . . . . . . . .D-1

HPSCGAP and HPSIGAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1

HPSCGAP Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-4

HPEUCGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-8

SKLCGAP.JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-9

Host Batch JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-10Batch DB2 JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-10Batch JCL (non-DB2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-12

HPICGAP Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-13

HPICGAPJ.JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-17

E Hardware and Software Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

DASD Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Supported Third-party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

F Host Installation Workbench Customization Worksheets . . . . . . . . F-1

Using Customization Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

G Enterprise Repository Customization Worksheets . . . . . . . . . . . . . . . . . .G-1

Using Customization Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .G-1

H Batch Preparation Workbench Customization Worksheets . . . . .H-1

Using Customization Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H-1

I CICS Online Preparation Workbench and Enterprise Server Customization WorksheetsI-1

Using Customization Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1


J IMS Online Preparation Workbench and Enterprise Server Customization WorksheetsJ-1

Using Customization Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1

Table of Contents 9


CHAPTER

1 PLANNING


The first step in planning a transition to the AppBuilder environment is to develop an AppBuilder implementation plan. BluePhoenix Solutions can work with you to help develop your implementation plan.

Installation OverviewA standard or “base” AppBuilder installation consists of a single host repository with one or two versions, a limited number of development work-stations (two or three) and initial verification of the environment using the Test Installation Process (TIP) application. For all installations a minimum notice period of two weeks should be allowed in order to complete pre-install activities.

Prior to beginning the installation, a planning process is necessary to ensure that your environment is prepared to receive the AppBuilder software. This activity is based upon information provided in this manual and may include a one-day planning meeting at your site — although the entire process can be completed via phone and fax.

Installation of optional products naturally increases the installation period. For example, an optional product, such as Report Writer, typically requires an additional half-day to a day to install and verify.

The success of an installation is dictated largely by the quality of preparation; certainly the time scales indicated above assume a “clean” and “ready” environment at your site. Failure to perform comprehensive installation planning results in significant delays and costs both to AppBuilder and you.

AppBuilder mainframe products can be installed by customers, and experienced customers often perform their own installations, with remote support. However, AppBuilder does provide installation services for newly purchased host products and most organizations utilize a AppBuilder (or, in some countries, IBM) installer. In essence the installation should be deemed to have started once the planning begins and AppBuilder installers begin discussions with the account team. If environmental issues are found then these should be resolved prior to the AppBuilder installer traveling to the client location.

It should also be noted that the installation planning phase provides an opportunity for client systems personnel to become familiar with the AppBuilder installation process and requirements and thus avoid any unwelcome “first day shocks.”

As previously indicated, initial installation verification is carried out by the AppBuilder installer using the TIP test application. This application ensures that each of the elements constituting the “base”

Planning and Installing AppBuilder for the Mainframe 1-1

Installation Overview

AppBuilder product are correctly installed and integrated and that primary development and execution functions are operable.

In addition, it is recommended that further comprehensive verification be conducted to ensure that all lower level functions required for subsequent training and development activities are operable. This can be achieved using scripts prepared by AppBuilder Consulting, which thoroughly exercise the tools by simulating development activities.

Additional verification work is often undertaken during the final days of the installation, while the AppBuilder installer remains on site to address any problems encountered. AppBuilder Field Support, Consulting and Systems Engineer resources have historically engaged in this activity as, on occasion, have client personnel.

Installation ComponentsThe AppBuilder installation can be broken down into a number of logical parts as follows (durations are estimates based on experience and assume complete preparation).

Architecture EvaluationAppBuilder allows you to produce and maintain client/server applications more quickly and more effectively. Careful planning, training, and AppBuilder support can combine to help your development organization fully utilize AppBuilder’s features.

The first requirement is to ensure that your strategic information needs are congruent with your hardware and systems software architecture. To meet this requirement you must consider:

• Your organization’s needs

• The hardware and system software combination required to satisfy them

• The current architecture and how best to make the transition (if one is required)

Table 1-1 Estimated duration of installation

Base Installation Systems Software 1 Day

Enterprise Repository 1 to 2 Days

Optional Products CICS 1/2 Day

Mainframe Batch Preparation 1/2 Day

Batch Report Writer 1/2 Day

IMS 1/2 Day

Installation Verification 3 to 5 Days

1-2 Planning


Develop a plan for your systems

• Determine the technical scope of the new architecture, including hardware and software platforms, flexibility, and so forth

• Develop a hardware configuration and an environment for each platform

• Determine the software environment and development languages for each platform

• Decide on a database management system (DBMS)

• Determine the data communications strategy

• Determine the development hardware and software environment

• Determine the production hardware and software environment

• Establish performance goals

• Define security requirements

Analyze your systems: reuse, buy, or build?

Determine which portions of your existing hardware and information systems can be reused and which need to be replaced.

Described in Chapter 4, “Installation requirements” are tables of hardware and software requirements. Checklists to assist your inventory of host hardware and software can be found in Appendix C, “AppBuilder Host Development Workbench hardware and software checklists.” We recommend that you complete these checklists as part of your planning document. You should perform similar inventories of systems, if any, and of IBM-compatible workstation hardware and software. Your AppBuilder account executive will gladly assist you in completing these checklists.

Objective: Inventory of hardware and software.

Manage the transition to your AppBuilder-built systems

To implement the solutions to your organization’s strategic information requirements, you need to plan for constructing, managing, and maintaining your systems.

Objective: Develop a plan to construct, manage, and maintain your systems.

Project InfrastructureBased on your implementation priorities and conversion/bridgeback requirements, develop an overall implementation plan. This plan should include:

• Phased implementation schedule and objectives

• Staffing requirements

• Hardware, software, and communications requirements for development and execution workstations

• External and internal support requirements

Objective: Phased implementation plan that outlines schedules, objectives, staffing, and resource requirements.



Organization, staffing, and training

Develop an organizational structure to execute your plan. Based on the staffing plan, determine the overall staffing needs. Assess the need for permanent hires and consultants. Determine training requirements. Address office space requirements if appropriate.

Objective: Organizational structure, staffing, hiring, training, and office space plans.

End-user participation and training

Based on the phased implementation schedule, determine the extent of end-user participation at each stage. Estimate the end-user involvement in testing and the amount of training your users will need.

Objective: A document that describes end-user participation needs by level, function, and time period. It also describes training requirements and a training time frame.

Budgets, tracking, and control

Develop cost estimates and budgets based on:

• Resource requirements

• Hiring, staffing, and training plans

• Consultant expenses and off-the-shelf software requirements

Establish a project planning and control system, including a tracking mechanism.

Objective: A budget by category and by month, and a project planning and control system with a track-ing mechanism.

Organization and TrainingWhen you implement the AppBuilder environment, you may need to restructure your IS department and retrain your staff.

One language

One major benefit of AppBuilder software is its ability to consolidate many different IS groups into one team. Although applications might run on two or more different platforms, AppBuilder software developers need to know only one programming language.

Even though they need not be proficient in third-generation languages, AppBuilder software developers should be familiar with the concepts of structured programming, object-oriented design, and information engineering.

Phased introduction to AppBuilder software

If you plan a gradual introduction of the AppBuilder environment, we suggest that soon after installation you schedule high-level overviews for staff who won’t have access to AppBuilder software. When more detailed training becomes necessary for these people, they will already have an

1-4 Planning


understanding of the basics. This approach also allows everyone to participate in the transition to the new environment.

Pilot ProjectA simple and effective way to introduce AppBuilder software is through a pilot project. A pilot project is typically a small-scale effort, staffed by motivated people whose objective is to showcase the technology that will gradually spread throughout the organization. Thus it is important to select a highly competent team.

Project team composition

Each project needs a sponsor—a senior executive with authority and ultimate responsibility. Each team needs a project manager and individual contributors with appropriate business skills. To ensure a cross section of skills and ultimate success, teams should have two to three persons with experience in the traditional development cycle and senior technical or business personnel.

End users and business experts must be part of the team, because they contribute as much to the analysis and design of an application as system developers or business analysts. Incorporating users into the development process accomplishes two objectives: first, it enables you to incorporate good suggestions when it is cost-effective to do so, and second, it enables the end-users to develop a sense of proprietorship in “their” system. Their positive attitudes help assure success, and their contributions make the application perform according to their needs.

The team should have five or six developers and business representatives. Because concepts are new, each member must have an interest in learning new approaches and technology. Members should be innovative, entrepreneurial, and able to assist others in applying new technologies.

Project duration

From inception to completion, each project or phase should take up to four months (or 100 person-weeks with six members per team). The initial projects should contain no more than 50 windows or reports with an average of eight rules per window or report.

Additionally, the scope of the projects should include topics such as mainframe batch reporting, Dynamic Data Exchange (DDE) with third-party software, component definition and usage, and local data retrieval by means of a database manager. For each of these areas, specific standards, conventions, and guidelines must be developed and published for the benefit of future development teams.

CommitmentManagement and users must be committed and involved in order to achieve success in an enterprise-wide project. Adequate resources, planning, and personnel are critical factors in ensuring that the organization’s goals and needs are met.



Management

For an enterprise-wide project to succeed, commitment and sponsorship from management is critical. Management must have long-term vision to see the needs and a short-term orientation to see that the project stays on track. Management must allocate the necessary resources (physical, financial, and personnel) and resolve problems beyond the jurisdiction of individual project managers.

You must obtain top management recognition and support for:

• The need to create an enterprise-wide model

• Treating the enterprise-wide model as a major asset

• The need to develop standards and conventions to promote consistency and reusability

• Ample training for developers and end users

• The project development methodology

End-Users

To achieve success, user commitment and involvement must be constant from start to finish of a project. Throughout the project, user groups must provide sufficient resources and access to personnel with appropriate business knowledge.

Allocation of resources

A primary building block in the using AppBuilder is the data model. A fully attributed data model should be completed and approved by the user representative before actual development begins.

IBM’s Financial Services Industry (FSI) data model simplifies this effort, but management must still allocate resources from both the MIS and business units so the model can be tailored to the company’s needs.

To prove that the model is sufficient, further resources must be committed to build a functional prototype. Constructing a prototype also provides experience for constructing the real system in a subsequent step.

Development TeamMembers of the development team should be motivated and interested in new technology. They should have an understanding of the AppBuilder environment tools, development methodology, and standards. The development group members must have experience or ability in the areas listed below.

Project managers

The project manager is responsible for the day-to-day direction of the development team, including:

• Resource scheduling

• Direction

• Problem solving

1-6 Planning


Candidates must understand enterprise process and data modeling, object-based programming, system design, graphical interface design, and project management.

Managers must have practical experience in leading a development team from analysis through system implementation. These individuals must have the ability to motivate and train their team members and provide direction by establishing a detailed project plan with defined deliverables, achievable milestones, and sufficient checkpoints to ensure project success. Experience in the following areas is desirable:

• Project planning in a CASE environment

• Estimating for AppBuilder environment resources, time frames, and deliverables

• Project life cycle leadership in a CASE environment

• Project standards and procedures

• Functional or technical design issues and considerations, concepts, and conventions; for example, Common User Access (CUA) user interface and cooperative processing implications and usage

• Joint Application Design (JAD) facilitation and usage

• Estimating function points

System architect

The system architect designs information systems and offers strategic technical direction to the project. The system architect must have extensive development experience with a variety of software and hardware platforms.

The system architect understands the concepts and problems of specifying, designing, and building complex systems. He or she knows how to measure and control the design of the system, estimate the required resources, and ensure quality. The architect works with the business analyst to design applications that will satisfy the user’s expectations.

System analysts and programmers

Programmer/analysts should have system analysis and design capabilities and a thorough understanding of hardware and software to translate end-user requirements into viable applications.

Programmer

Programmers should have experience in developing medium-to-large applications. At a minimum, they should have a background in CASE technology and an understanding of object-based design. Experience in the following areas is desirable:

• Applying logical data modeling and Business Object Analysis (BOA) techniques to application design

• Working knowledge and practical expertise with functional and technical design concepts (such as protocycling, coupling and cohesion, cooperative processing application design, and CUA)


• Relational database principles and SQL coding

• Interviewing and communication skills and techniques



Business analyst

The business analyst is a link between users and developers. He or she analyzes the enterprise and translates requirements into solutions. These solutions often involve the design and implementation of computer systems.

The business analyst must understand data and process modeling in the financial services industry. The ideal candidate has five or more years experience in FSI. The business analyst must be able to lead a group to consensus on technical topics. Strong host and workstation computer skills are a major asset.

Specifically, the business analyst models the business, partitions it into cohesive objects, and designs the preliminary user interfaces and window navigation of a new application.

Experience in the following areas is desirable:

• JAD facilitation and use

• Applying logical data modeling and Business Object Analysis techniques to application design

• CUA application design and prototyping


• Interviewing and communication skills and techniques

Production and support personnel

• Quality Assurance (QA) procedures for migrating applications into a production environment

• QA procedures for monitoring CUA standards and conventions for naming and using objects

• Implementation procedures

• Recovery and backout support

• Application security that includes user-terminal and application functionality

• Software migration and distribution

• Workstation/LAN, communications, and support for mainframe DB2 and CICS

End-user services

• Development of standards and training materials

• Communication and publishing techniques

• Graphic design/layout

• Training and presentation

Quality Assurance TeamQuality assurance team members should be self-motivated to ensure that the application performs acceptably and meets user requirements. QA team members should also have a good understanding of the enterprise’s graphical user interface standards and the AppBuilder toolset used to develop applications.

1-8 Planning


QA manager

The QA manager directs the QA team. The manager should have knowledge of unit and system testing, interface design, and validating the business models against the application design.

QA analyst

QA analysts must be meticulous and thorough in testing all facets of an application interface according to a rigorous test plan. They ensure that the application meets requirements and conforms to design standards.

Data Management TeamMembers of the data management team should be motivated to develop, maintain, and provide a stable database on which future applications will be built.

Data modeler

Data modelers develop relational data models to support the business. They work with business analysts, system architects, and designers to identify and analyze the business data, model it, and turn the resulting models into usable logical and physical designs. Modelers should have formal training in relational data modeling and Business Object Analysis concepts, plus a thorough understanding of the enterprise’s naming and modeling standards.

Database administrator

A database administrator implements a physical data model or schema to validate creating the physical data model through DB2 table generation and tunes the performance of the resulting database. The database administrator should have heavy experience in relational database concepts, SQL performance, and tuning.

Application Development Operations TeamMembers of the operations team work with QA to maintain the business models and provide business or system expertise as required. In addition, each member should possess a good understanding of the development methodology, standards, and the AppBuilder environment toolset.

Repository manager

The repository manager maintains and controls the development of objects in the AppBuilder repository. The repository manager validates newly developed business models and checks their conformance to standards before incorporating them into the enterprise-wide model. The repository manager also determines if the functionality of an existing object can be used or modified to suit the new need. If an existing object is modified, the repository manager must determine the impact of the change on existing systems.

Repository model manager

The repository model manager is the “keeper” of the logical business models. This person works with the development team to transfer business expertise (as defined in these models) and collect feedback (corrections, enhancements, or additions) for incorporation.


Finding the Latest Information

Repository administrator

The repository administrator performs daily maintenance of the AppBuilder repository and AppBuilder host environment toolsets. This person must understand repository concepts and relational databases. A background in CASE technology and in-depth understanding of the AppBuilder environment is helpful. Strong host skills are essential and knowledge of intelligent workstations is helpful.

Development support technician

Development support technicians should have experience in developing medium-to-large applications and knowledge of workstation, CICS, and TSO facilities. Technicians should be interested in working with new technologies. Experience in DB2 is essential. This person must be trained in AppBuilder software, be able to answer technical questions on design and implementation, and be able to solve problems.

Production TeamMembers of the production support team supply technical expertise to the project teams and assist them in moving the application to the production environment.

Production support manager

The production support manager needs an understanding of the AppBuilder environment and the production support role in the development life cycle—especially in the protocycling and technical construction phases. The production support leader should have experience with automated system and security maintenance tools and an understanding of current and future production environments.

Production support technician

Production support technicians need extensive knowledge of the host environment, and should be familiar with JCL, TSO, DB2, CICS, Windows, OS/2, the AppBuilder security facility, and RACF or ACF2.


For the latest documentation and product updates, contact Customer Service using the information in this section.

• Internet: http://support.bluephoenixsolutions.com

• E-mail: [email protected]

• Americas ServiceLine: 919-380-5200 or EMEA Support Line: +44-1895-206777

• Fax: 919-319-2235

Contact BluePhoenix Solutions for additional support and training:

• Internet: http://www.bluephoenixsolutions.com

• E-mail: [email protected]

• Phone: 919-380-5100

1-10 Planning

http://support.bluephoenixsolutions.com

mailto:[email protected]


mailto:[email protected]


AppBuilder ServiceLine

The AppBuilder ActionLine provides an efficient, centralized point of contact for all service-related communications between AppBuilder and its clients. You would contact ServiceLine to:

• Ask technical questions about AppBuilder’s products and services

• Report problems with AppBuilder’s products (including Limited Availability products)

• Check the status of a problem

• Obtain explanations of software releases, modifications, and/or program temporary fixes (PTFs)

• Suggest enhancements

• Order products or services (for example, documentation and training classes)

Generally, clients find it best to designate one contact person at each location (typically the AppBuilder or development administrator) to place all ServiceLine calls. This allows your organization to effectively apply local expertise in the AppBuilder products you use, and thus provides the quickest possible answers to basic questions. Designating one contact person also allows the ability to monitor problems and escalate them efficiently as required.

AppBuilder Product Support

Product Support is responsible for ensuring a high level of client satisfaction with AppBuilder products and services. For the U.S. and Far East, contact the AppBuilder ServiceLine to request your AppBuilder Client Services analyst. For EMEA, contact AppBuilder’s United Kingdom office.

An AppBuilder Client Services analyst is assigned to you when a AppBuilder product is installed at your site. This analyst is responsible for satisfaction with AppBuilder products and services at your site, and is available to respond on any questions or issue to ensure your satisfaction. You would contact Client Services to:

• Provide information on software releases, program temporary fixes (PTFs), and emergency fixes currently available

• Pursue emergency fixes for problems

AppBuilder Consulting

AppBuilder Consulting can assist you in addressing any need that might arise, including those related to DB2, CICS, communications hardware, methodology, process and data modeling, and project planning, as well as issues specific to AppBuilder installation.

AppBuilder Consulting also offers the services of highly skilled application specialists who are experienced IS professionals with comprehensive knowledge of the AppBuilder environment and many other hardware and software systems.



Before Installing AppBuilder SoftwareYou must complete the following steps before installing AppBuilder software:

• Complete the non-disclosure agreement

• Review installation requirements in this manual

• Complete preinstallation checklists in this manual and fax or mail them to AppBuilder Field Support

• Schedule an installation date through your BluePhoenix Solutions contact

• Identify all AppBuilder support staff

• Acquire necessary prerequisites

• Install and test necessary prerequisites

• Define DASD space, installation and training user IDs, and data set naming conventions

Field support responsibilities

On receiving a request for installation the Field Support Manager will assign a Field Support Analyst to work with the client and AppBuilder Sales/Consulting to prepare for installation. Whenever possible this Field Support Analyst will then travel to the client location to perform/support the installation.

Week one

• Initial TSR/Consultant contact

• Complete and review Installation Customization Worksheets and checklist

• Contact client Technical Representative and review any “red flag” install issues

• Create action plan to resolve “red flag” issues prior to beginning install

• Customize host install diskettes and ship to client

Week two

• Contact client to review any “red flag” issues and plan for resolution

• Ensure software and documentation have been shipped to client

• Based on planning results and action plan to resolve “red flag” issues confirm installation start date

TSR/consultant responsibilities

• Ensure Client Technical Representative completes and returns Installation Customization Worksheets and checklist to Field Support staff

• Ensure action plan to resolve any “red flag” is implemented

• Ensure host sessions available on workstations to be used during installation

• Ensure client receives and reviews Planning and Installation, and Install manuals

1-12 Planning


Client responsibilities

• Assign technical contact responsible for working with AppBuilder throughout installation period

• Complete Installation Customization Worksheets and checklist

• Review checklists and worksheets with Field Support Analyst

• Install and configure third-party software

• Ensure appropriate technical resources and personnel are available prior to Field Support Analyst traveling to client site

AppBuilder Software OverviewThe AppBuilder environment features an enterprise repository that works in conjunction with the developer’s personal repository or Workgroup repository. The ability to access and share design and development objects enables a high degree of object reuse. Developers can query the enterprise repository for reusable objects, easily download them to their personal repository, and work with multiple versions of AppBuilder-built applications. Newly-defined designs, models, and application specifications can also be uploaded to the host-resident enterprise repository, a DB2-based facility. Intelligent check-in/check-out controls ensure data integrity and security.

Keep in mind the distinction between the operating system under which a workbench runs, and the operating system it supports. For example, the AppBuilder Workstation Preparation Workbench runs only on development workstations equipped with OS/2 Presentation Manager, but it can support creation of applications for production workstations running any combination of OS/2, UNIX, or Microsoft Windows. Table 1-2, “AppBuilder software and typical users,” on page 13 presents a summary of AppBuilder base and optional product software, and indicates the typical users of specific products. Please note that while multiple platform types (for example, OS/2, MS Windows, UNIX, and mainframe) are supported, not every product supports every platform type.

AppBuilder Product DescriptionsAppBuilder offers products to enhance productivity and efficiency. Separate products enable you to tailor options to suit your site’s specific needs. For example, you can choose from various development and production platforms, as well as facilities to distribute and secure applications. The following sections describe various products that you might find useful.

Table 1-2 AppBuilder software and typical users

AppBuilder software

Product

Platform

Users

Code D QA DT EU

Development Workbench 3

AppBuilder Workstation Development Workbench

WSWB-OS2 OS/2 3

Key: D = Development team, QA = Quality assurance team, DT = Delivery team, EU = End user



AppBuilder Enterprise Repository (EREP-TSO)

AppBuilder Enterprise Repository software provides developers with an interface to the enterprise repository and is used to perform three important tasks:

• Accessing the enterprise repository

• Generating host-only and host-server application code

• Testing host-only and host-server application code

The Enterprise Repository is used to store data, process objects, and executables. It provides a single centralized storage facility for all AppBuilder-built applications. You can perform global queries, such as extended where-used reports and keyword searches, against any of these stored objects.

AppBuilder Enterprise Repository

EREP-TSO TSO 3

Preparation Workbench 3 3

AppBuilder Local Client Preparation/Test

CPRP-OS2CPRP-WIN

OS/2, MS Windows, Windows NT, OS/400

3 3

AppBuilder Online Preparation Workbench

ONLP-CICSONLP-IMS

Mainframe/CICS, Mainframe/IMS

3 3

AppBuilder 3270 Converse Preparation Workbench

327P-CICS327P-IMS

Mainframe/CICS, Mainframe/IMS

3 3

AppBuilder Batch Preparation Workbench

BATP-Mainframe

Mainframe 3 3

AppBuilder Report Writer

RPTP-Mainframe

Mainframe 3 3

Production Services 3 3 3

AppBuilder Host Middleware Enterprise Server

MWSE-CICSMWSE-IMS

Mainframe/CICSMainframe/IMS

3 3 3

AppBuilder Host Middleware 3270 Converse Client

MWCL-327CMWCL-327I

Mainframe/CICSMainframe/IMS

3 3

AppBuilder Workstation Middleware Services

OS/2,MS Windows,Windows NT

Table 1-2 AppBuilder software and typical users (Continued)

AppBuilder software

Product

Platform

Users

Code D QA DT EU

Key: D = Development team, QA = Quality assurance team, DT = Delivery team, EU = End user

1-14 Planning


The Enterprise Repository also provides various administration tools. Refer to Managing Enterprise Repositories, Enterprise Migration Facility, Enterprise Rebuild Facility, and Report Writer User’s Manual for more detailed information.

For applications that execute on the host in part or entirely, you need to use the Enterprise Repository to complete the construction and testing phase of application development.

• For construction, the Enterprise Repository is used to prepare all host rules, components, windows, and reports. This creates host-executable modules. This Enterprise Repository is also used to generate the data-definition language (DDL) for DB2 tables.

• For testing, the workbench Batch RuleView facility is invoked through the repository interface to unit test host batch rules and components. For CICS, the testing facility is invoked via a AppBuilder CICS transaction.

Online Preparation Workbench (ONLP-CICS, ONLP-IMS)

The AppBuilder Online Preparation Workbench generates COBOL II code from AppBuilder rules in the Enterprise Repository and compiles it to run on the host. It includes host online RuleView debugging tool and supports CICS and IMS run-time environments.

Batch Preparation Workbench (BATP-Mainframe)

AppBuilder Batch Preparation Workbench software generates COBOL II code from AppBuilder rules in the enterprise repository and compiles it to run on the host. It supports the mainframe Batch run-time environment. It includes host batch RuleView debugging tool.

Report Writer (RPTP-Mainframe)

The Report Writer supports creation of paper-based reports by batch applications.

3270 Converse Preparation (327P-CICS, 327P-IMS)

AppBuilder 3270 Converse Preparation and 3270 Converse Client software allows developers to create WYSIWYG windows for 3270 terminal-based applications. The 3270 Window Painter supports only those objects that can be represented in a character-based display, and enforces restrictions on color identical to those imposed by the 3270 terminal. It is no longer necessary for a window to be initially designed on the workstation Window Painter and converted to the 3270 Window Painter. However, the 3270 Window Painter does provides the option to convert workstation windows to adhere to 3270 implementations.

Two approaches can be used for adapting workstation and host interfaces to the same application. In the first, a single end-user interface can be designed to execute on both the workstation and the host, with comparable displays on each platform, and with minor functional differences in behavior. This approach is convenient, but limits the workstation “notifies” to the technological limitations of a 3270 terminal. In the second approach, distinct workstation and host end-user interfaces can be designed for a single window entity—a single application. This approach allows each interface to take advantage of diverse display capabilities, but requires more effort.



Staff responsibilities

Developers can provide users with a consistent look and feel across applications on the host (using NPTs) and on the workstation.

Product summary

AppBuilder 3270 Converse Preparation generates AppBuilder windows that run on a 3270 NPT in online applications. You can design, construct, prototype, and debug these windows on the Workstation Development Workbench, and then use this product to generate host-based run-time versions. It supports CICS and IMS.

Host Middleware (MWSE-CICS, MWSE-IMS, MWCL-327C, MWCL-327I)

There are two host middleware servers and two host middleware clients—one server and one client each for CICS and IMS. The server products allow server rules to run in CICS or IMS. The client products allow 3270 Converse applications to run so that end users can use 3270 terminals.

Note The Host Middleware Enterprise server is packaged with the Online Preparation Workbench. The Host Middleware client is packaged with 3270 Converse Preparation Workbench.

1-16 Planning

CHAPTER

2 PREINSTALLATION REQUIREMENTS AND APPLICATION MAINTENANCE


Maintaining AppBuilder applications requires planning and monitoring of the mainframe platform by the system administrator. This section provides an overview of the installed system and details about design, tuning, and execution in the AppBuilder environment.

Understanding the Installed EnvironmentThe AppBuilder environment features an enterprise repository that works with a developer’s personal repository or workgroup repository. The capability to access and share design and development objects enables a high degree of object reuse. Developers can query the enterprise repository for reusable objects and easily download them to their personal repository, and work with multiple versions of AppBuilder-built applications. Newly-defined designs, models, and application specifications can also be uploaded to the host-resident enterprise repository, a DB2-based facility. Intelligent check-in/check-out controls ensure data integrity and security. Topics include:

• Installing Components

• Performance Tuning

Installing ComponentsThe AppBuilder environment has been designed to allow you to customize the installation of AppBuilder software to ensure conformance to your system standards. The following section identifies all customizable items that must be determined prior to the start of the installation.

• Data Set Naming Standards

• Short-term Data Sets

• Security

• DB2

• CICS

• VTAM

• IMS


Understanding the Installed Environment

Data Set Naming Standards

AppBuilder system software uses various types of data sets to store product software and user data generated during the development process. Data sets follow specific naming conventions that are custom-configured at your site. A description of the data set qualifiers used in AppBuilder follows:

• GLOBQUAL

• INSTQUAL

• BASEQUAL

• MODQUAL

• REPQUAL

• USRVQUAL

• VSUVQUAL

• VSMQUAL

• MIG_FILE_ID

GLOBQUAL

Defined during the initial load of HIW (Host Installation Workbench), this resides in the REXX member INSTART in &GLOBQUAL..CLIST and names the libraries that comprise HIW.

INSTQUAL

This resides in the INI member @INSTENV and defines that data sets that hold the system and repository installation software.

BASEQUAL

This is initially defined during the AppBuilder System Software Installation and names the libraries that hold the AppBuilder software. The value is stored in the data set &GLOBQUAL..USER.CLIST in the member for each system (for example, if you have a system named NEWSYS, there will be a PDS member named NEWSYS also).

MODQUAL

Analogous to BASEQUAL, this qualifier names system libraries which are created empty and can be used to hold client modifications.

REPQUAL

Defined in @HPSENV, this qualifier defines data sets which hold information specific to a given repository. REPQUAL libraries can also be used to hold software modifications which are to affect only one repository.

USRVQUAL

Defined in the INI member @USRENV for each repository version, this qualifier names the data sets which hold USER application information.

Note The qualifiers BASEQUAL and MODQUAL are also stored in the INI member @HPSENV. Their presence there defines the system that is associated with a given repository.

2-2 Preinstallation Requirements and Application Maintenance


VSUVQUAL

Defined in the INI member @USRENV for each repository version, this qualifier names the VSAM data sets which hold USER application runtime information. This qualifier names the FCT entries which are required with the CICS runtime software.

VSMQUAL

This qualifier defines VSAM data sets which are part of the system software and not specific to a repository. This qualifier is defined in &GLOBQUAL..USER.CLIST (sysid) and in the INI member @HPSENV.

MIG_FILE_ID

Defined in the INI member @MIGENV for each repository version, this qualifier defines the default data set name for migration data sets.

Short-term Data Sets

Short-term data sets are created during the development stage. They are required only for a short period (typically two to three days) after which they may be deleted.

A standard naming convention is followed to ease DASD cleanup of temporary data sets. Three qualifiers are used to name short-term data sets. All variables support more than one node and are listed in Table 2-1. The three variables are defined in the INI member @HPSENV.

Security

This section provides details pertaining to AppBuilder user ID and security requirements. All AppBuilder user IDs must have the following logon attributes:

• At least six megabytes of main storage must be allocated at logon time.

• The AppBuilder IDs require access to the AppBuilder CICS region.

• If your CICS region is secured, you must set up the appropriate accesses for the necessary transactions. To use the LU2 program interface, you must allow the three CICS TCT (see “CICS” on page 2-6) definitions and corresponding VTAM APPLIDs (see “VTAM” on page 2-7) to execute these CICS transactions:

• CEMT

• CEDA

• HS06

• UTBL

Table 2-1 Short-term data set qualifiers

TEMPQUAL GRPQUAL PERMQUAL

Maximum value 10 characters 18 characters 10 characters

Value contents Final node must be seven characters or less

Must contain the value of SYSUID

Example TEMP.NN.* PAY.USERID.* HPS.PERM.*



• Data set access requirements vary based on individual user function.

Table 2-2 summarizes system data set read/execute access needed by AppBuilder installers.

Table 2-3 summarizes system data set read/execute access needed by AppBuilder end users.

Table 2-2 summarizes system data set read/execute access needed by AppBuilder administrators.

Table 2-2 AppBuilder installer data set access requirements

Data set (for installers) Read Write Allocate

HPSOUT..* 3 3 3

&BASEQUAL..* 3 3 3

&GLOBQUAL..* 3 3 3

&GRPQUAL..* 3 3 3

&INSTQUAL..* 3 3 3

&MIG_FILE_ID..* 3 3 3

&MODQUAL..* 3 3 3

&PERMQUAL..* 3 3 3

&REPQUAL..* 3 3 3

&TEMPQUAL..* 3 3 3

&USRVQUAL..* 3 3 3

&VSMQUAL..* 3 3 3

&VSUVQUAL..* 3 3 3

Table 2-3 AppBuilder end-user data set access requirements

Data set (for users) Read Write Allocate

&GRPQUAL..* 3 3 3

&PERMQUAL..* 3 3 3


&MODQUAL..* 3

&BASEQUAL..* 3

&REPQUAL..* 3

&USRVQUAL..* 3 3 3

&TEMPQUAL..* 3 3 3

&VSMQUAL..* 3

&VSUVQUAL..* 3 3

Table 2-4 AppBuilder administrator data set access requirements

Data set (for administrators) Read Write Allocate

&GRPQUAL..* 3 3 3

&PERMQUAL..* 3 3 3



Table 2-5 summarizes system data set access for AppBuilder installers and developers.

DB2

This section provides details pertaining to the DB2 requirements of the AppBuilder software. Your system must be installed with the following requirements installed.

• The use of DB2 packages, as well as plans, must be supported.

• SPUFI or an equivalent DB2 query/update facility must be available and accessible from ISPF.


&GLOBQUAL..* 3 3 3

&MODQUAL..* 3

&REPQUAL..* 3 3 3

&USRVQUAL..* 3 3 3

&BASEQUAL..* 3

&INSTQUAL..* 3

&TEMPQUAL..* 3 3 3

&VSMQUAL..* 3

&VSUVQUAL..* 3 3 3

Table 2-5 System data set access for AppBuilder software installers and developers

System data set Installer access Developer access

Read Execute Read Execute

C compiler library 3 3

CICS LE link library 3 3 3 3

CICS macro library 3 3 3 3

COBOL II compiler library 3 3 3 3

LE link library 3 3 3 3

DB2 link and load libraries 3 3 3 3

DB2 preprocessor 3 3 3 3

DB2 utility library 3 3

H assembler 3 3 3 3

IDCAMS or equivalent utility 3 3 3 3

IEBGENER and IEBCOPY utilities 3 3 3 3

ISPF libraries 3 3 3 3

PL/I transient libraries 3 3 3 3

Table 2-4 AppBuilder administrator data set access requirements (Continued)

Data set (for administrators) Read Write Allocate



• Select access on the DB2 system catalog table SYSIBM.SYSTABLES is required during the installation.

• The allocation of DB2 objects must support the use of VSAM definitions if VCATs are used instead of STOGROUPs.

• Recommended initial size on DB2 Buffer pools is 4K.

• AppBuilder recommends that the installer’s ID have SYSADM authority. If SYSADM authority cannot be granted, specific DB2 authorities needed by the installer’s ID in lieu of SYSADM are as follows:

• System Privileges:

• BINDADD

• CREATEDBA

• Collection and Package Privileges:

• PACKADM on collection ID &PPREFIX..HPS53.*, where &PPREFIX is a one-character customizable identifier used for the AppBuilder system plan.

• The installer’s IDs, administrator’s IDs, and all AppBuilder software developer IDs must have BINDADD authority.

CICS

The installation process will generate a complete CICS CSD file and provide uncustomized JCL to migrate AppBuilder definitions into the target region.

• Configure the target AppBuilder region(s) to support PL/I, COBOL II, and C programs.

• Create the following CICS groups which must be included in the CICS start-up grouplist:

• AB2031, used for AppBuilder object definitions

• HPESDUG, used for utility definitions

• HPESDUK, used for utility definitions

• HPSTIP, used for associating all definitions required for installation verification

• Additional groups are defined to support the CICS Online Server if it has been installed.

• Complete the required VTAM system changes.

• Define three new APPLIDs.

• Define one new LOGMODE entry.

• Review USSTAB entry for CICS.

• Review USSTAB entry for TSO.

• Define 3270 sessions as DFT with four sessions. Four sessions enable the execution of multiple AppBuilder applications.

Note If secondary authorization IDs are used to bind AppBuilder software plans or to create AppBuilder software DB2 objects, the secondary IDs must also have the appropriate authorities.



The following details list the CICS requirements of the AppBuilder software that must be on an installed system.

• Preload the CICS Sign-on Table (SNT).

• Configure and activate the CICS DB2 attach facility. Refer to your CICS documentation for further details on this setup.

• Configure CICS for LE support

• Configure the CICS Destination Control Table (DCT) to include the DCT definition (see Chapter B, “CICS Table Definitions”).

• Configure the CICS Terminal Control Table (TCT) to include the TCT definitions (see Chapter B, “CICS Table Definitions”). The first TCT definition in the DFHTCT table is a sample of a AppBuilder terminal. The three TCT definitions following the sample TCT definition are used for the AppBuilder LU2 program interface. The NETNAMES contained in the TCT correspond to the three APPLIDs defined to VTAM that are used only for reference and may be changed in accordance to your network standards. (These values must be the same in both CICS and VTAM.) The netnames A06HPS1, A06HPS2, and A06HPS3 are the default VTAM application IDs that appear on the installation panel containing the AppBuilder CICS environment.

• CICS processing program table (PPT) and CICS program control table (PCT) will be supplied in CSD file format (see Chapter B, “CICS Table Definitions”).

• Define the transaction security level as public execute for all AppBuilder transactions.

• Set resource-level checking to No for all AppBuilder items.

• Set up your security system to allow execution of the CEDA and CEMT transactions. These commands will be executed through a batch job using one of the three VTAM APPLIDs as the entry point to CICS. Therefore, these three IDs must have execution access to the two commands. The AppBuilder developer’s user ID does not require the ability to execute CEDA or CEMT commands. The AppBuilder transactions HS06 and UTBL and their associated programs, HPSNEWC and HPSUTBL, must also be executed by these three APPLIDs.

• Configure CICS terminals if LU6.2 protocol will be used.

VTAM

AppBuilder software requires the definition of three VTAM APPLIDs and one VTAM LOGMODE entry. The actual names of these definitions are configured and defined before installation.

The installation process completes the following required VTAM system changes:

• TSO IDs must be defined to allow access to both CICS or IMS and TSO.

• AppBuilder software supports the use of session managers. However, the AppBuilder upload/download process requires exclusive use of the session manager for the duration of the upload or download.

• AppBuilder requires three VTAM APPLIDs to be defined to your VTAM configuration. The LABEL A06HPS1, ACBNAME A06HPS1, and DLOGMOD HPSLU2 are only used as references and were changed in accordance to your network standards. Any changes to these netnames must also be reflected in the TCT entries in the AppBuilder CICS or IMS region and the VTAM LOGMODE definition. See Chapter B, “CICS Table Definitions”.

• AppBuilder software requires one VTAM LOGMODE must be added to your network configuration. The LOGMODE name HPSLU2 is used only as a reference and can be changed


Performance Tuning

according to your network standards. Any changes to the name must also be reflected in the APPLID definitions described previously.

IMS

The following details list the IMS requirements of the AppBuilder software that must be on an installed system.

• Configure IMS to support DB2.

• Configure IMS to support APPC if LU6.2 protocol will be used during runtime.

Performance TuningTuning applications to improve performance is a critical issue in any organization. This article describes suggestions for tuning AppBuilder on the host, in both the development and execution environments. However, keep in mind that not all of the tuning recommendations may be appropriate for your site—use caution and common sense when applying them.

Development Environment

You can improve performance in the development environment by making changes outside and inside AppBuilder. Recommendations in both areas are listed below.

Make sure you appreciate the differences between traditional development and development using AppBuilder software. The AppBuilder developer's profile is quite different.

The usage profile also differs at various stages of a project's lifecycle. During analysis, DB2 usage is heavier as there is more emphasis on the use of the analysis tools, and more text and keywords are uploaded. At later stages, there is a heavier reliance on batch prepares, and uploads are likely to be smaller and more specific. During testing, there is more use made of Customer Information Control System (CICS) or Information Management System (IMS) execution.

Keep the number of TSO users to a minimum. TSO jobs tend to have a higher priority than batch jobs—so the more users you have, the slower the system runs.

Increase the number of DB2 threads available for each mainframe transaction—this is especially useful for volume tests. However, a practical limit exists, which you should discuss with your database administrator (DBA).

Tune the AppBuilder sign-on, as this process is very resource-intensive. By tuning the sign-on, you reduce the amount of time that it takes to “get into” AppBuilder each time a developer enters the host workbench, starts an upload, or runs a batch TSO job.

Note If you want to use APPC communications in IMS, Mainframe/APPC communications should be installed on your system. This feature is a required prerequisite of the IMS Online Preparation Workbench. Refer to IBM’s IMS Systems Definition Reference manual for instructions to connect IMS to Mainframe/APPC. Refer to IBM’s IMS DC Admin Guide for instructions about connecting TP names to specific transactions and IMS MPR classes.


Performance Tuning

Consider running AppBuilder in its own logical partition (LPAR) to make management and tuning of the system easier.

Using the Migration Server

The migration automation uses TCP/IP communications. The migration files are automatically uploaded and the Analyze and Import are executed. Results of the import are then automatically transferred down to the workstation for review.

For download, you can query target MRE repositories and select the objects and the scopes to be downloaded. Once satisfied with your choices, the download process is initiated. The host repository exports the data and makes the files available for the client to download. The client then downloads the migration files, executes an import and displays the results to the user.

This enhancement benefits standard migrations and unit of work migrations equally. This option coexists with standard migration processing. With the enhancement implemented, the upload migration steps are simplified to three steps:

1. Specify user connectivity information (userID, password, target repository)

2. Initiate upload process

3. Upon notification of completion of host upload, review the report

The download migration steps are simplified to five steps:

1. Specify user connectivity information

2. Query the objects on a given MRE repository

3. Select objects to be downloaded and the scope of the download

4. Initiate the download process

5. Upon completion, review the report

Migrating Objects

Keep migrations as small as possible. Ask yourself—is it necessary to export an entire hierarchy, or will a partial hierarchy be adequate? Also, use the Automate Migration (MIGRATE) action when possible to speed up the process.

If you are working under time constraints, do not include text or keywords in the migration. You can migrate those parts later. Migrate message sets on their own, because message sets require relationship text to be migrated.

Use DB2 utilities to reorganize the large migration tables more often than other tables. Reorganize tablespaces after all big migrations. Change all tablespaces from simple to segmented. However, note that this change is likely to take some time.

Tables which may need to receive special consideration include:

• INMIG

• ENT_LOGKEY

• RBD_ACTION

• RBD_CONFIG_LOGKEY


Performance Tuning

• RBD_ENTITY_LOGKEY

• RBD_PHASE

• REL_LOGKEY

The following tables should be monitored regularly:

• CRC_ENTITY

• CRC_RELATION

• ENT_SIG_CHANGE

Delete extraneous data using the Clean Up (CLEANUP) action as much as possible without damaging the process—for example, do not clean up analyze and rebuild information that is still part of a delivery cycle. Migration tables continually fill up and require more maintenance than other repository tables. Consider using a separate High Level Qualifier (HLQ) for the migration tables to make managing them much easier.

If, after your migration, you are going to perform a rebuild, make sure that all objects being migrated prepare in the source environment. If your objects do not prepare in the source environment, they will not prepare during the rebuild process.

An additional action that may improve the performance of migrations is to separate the physical location of the INMIG indices from the physical location of the table.

Tuning the AppBuilder Mainframe Environment

The following tuning methods result from a AppBuilder performance survey in which the objective was to minimize the elapsed and CPU times for migration processing.

The following suggestions depend on DB2 being tuned as well.

Run REORGs, RUNSTATS, and rebinds after all large migrations. If the repository or the migration does not include particular object types, do not reorganize those tables. Some AppBuilder users clean up the following tables after each migration:

Note Do not run DB2 RUNSTATS on large tables when they are empty.

Table 2-6 Recommended tables to be cleaned after each migration

CRC_ENTITY CRC_RELATION

E_RULE E_WINDOW

E_VIEW E_PANEL

E_FLD E_WINCON

E_MIGRTN E_SRCTXT

E_SRCBIN ENT_SIG_CHANGE

R_RULRUL R_VUOWNS

R_WNCPNL R_WNDWNC

R_USESVW R_WNCHLP


Performance Tuning

Do not run REORGS or RUNSTATS on empty tables, or while a migration is in progress. A migration is in progress not only when a particular job is running, but also if the process has not finished all the steps it will take in that repository, including all the rebuild steps. For instance, even if a migration has finished the analyze step, do not reorganize if you plan to import the package later.

Tune the SEGSIZE, PCTFREE, FREEPAGE, and SUBPAGE parameters depending on the type of access to which that physical repository is most commonly subjected. Some repositories (such as quality assurance) have a large number of updates and inserts due to migrations. Other repositories (such as development) have many more selects than updates and inserts.

Set CLOSE to NO for all tables. Set the LOCKSIZE to TABLESPACE on the INMIG table in order to minimize the IRLM overhead.

Because of the sort order used in parts of AMI and the download process, the following index prevents an index-space scan and sort:

Create unique index OWNERID.XRVUOWNS3 on OWNERID.R_VUOWNS

• X_ENTITY_TYPE ASC,

• X_INSTANCE_ID ASC,

• Y_ENTITY_TYPE ASC,

• Y_INSTANCE_ID ASC,

• SEP_ID ASC,

• VERSION ASC)

• Using STOGROUP STOGRPA

• PRIQTY... SECQTY...PCTFREE...

• SUBPAGES... CLOSE YES;

Tuning the Enterprise Repository

The following recommendations enhance the performance of the enterprise repository and uploading and downloading. These suggestions are based on the analysis of performance monitors and client feedback. They are not intended to replace the procedures detailed in IBM systems manuals.

CRUD INI Variables

During execution, the enterprise loads certain create, read, update, and delete modules (CRUDs) into memory to satisfy a given request. For example, when you perform a List Relation (LR) action on a rule entity, the enterprise brings a number of CRUDs into memory to determine in which relations the rule participates. The enterprise also loads CRUDs to extract relation instances during uploads and downloads.

The number of modules in memory at any given time is governed by a Least Recently used (LRU) facility. Once the maximum number of CRUDs are loaded, the next fetch releases the maximum number minus the minimum number of CRUDs.

Three sets of INI file control variables control the minimum and maximum numbers of the three different types of DB2 CRUDs. These variables exist in the @HPSENV.INI file, and are prefixed by MN or MX. The MN variable controls the minimum number of CRUDs kept in memory. The MX variable


Performance Tuning

controls the maximum number of CRUDs kept in memory. The MNECRUD and MXECRUD variables control the entity CRUDs, the MNRCRUD and MXRCRUD control the relation CRUDs, and the MNBCRUD and MXBCRUD control the explode CRUDs. The online repository interface uses the entity and relation CRUDs and, as a result, does not benefit from tuning the explode CRUDs. Upload and download performance can be improved by tuning the entity and relation CRUDs, but gains the most from tuning the explode CRUDs.

If you have enough storage, you can increase the MX and MN variables to improve performance. Increasing these variables reduces SVC008 load calls, which in turn reduces CPU usage and improves response time. Conversely, you can lower storage requirements by decreasing the MX and MN variables.

Library Lookaside Facility

The Library Lookaside facility (LLA) is an mainframe system facility that lets mainframe use memory instead of disk reads to eliminate I/O on load libraries. By placing the AppBuilder load module directory into the LLA, you eliminate physical I/O when fetching CRUD modules. This eliminates EXCPs, and improves response time.

Specify the AppBuilder load library FREEZE parameter. The FREEZE parameter tells the LLA facility that no updates will occur to the directory, which allows LLA to place the entire directory into storage. The NOFREEZE parameter is of little benefit to the LLA since the LLA always goes to DASD to read the directory. When using the FREEZE parameter, updates to the load libraries must be managed manually, otherwise those updates will not be picked up properly.

Exits used by the LLA can also directly affect performance. LLA uses two logging exits: CSVLLIX1 and CSVLLIX2. CSVLLIX1 adversely affects the performance of the LLA. CSVLLIX2 incurs less overhead and performs better. You can attain the best performance without any exit.

Program Management Optimizer (PMO) by Legent is a competitor product and provides similar performance increases. The main benefit of PMO is that it automatically identifies updates to libraries across systems. For more information about PMO, call Legent in the United States at 800 676 5468. (Please note that this information is for your reference only. AppBuilder has not tested PMO, and therefore cannot endorse the product.)

Virtual Lookaside Facility

The Virtual Lookaside facility (VLF) is a general-purpose data space manager that starts at initial program load (IPL) time, and is non-swappable. This facility can bring CLISTs into memory, which minimizes DASD hits and improves response time.

During execution, uploads and downloads execute the HPSEFIT and HPSCFIT CLISTs for each upload/download request file. Put the &PREFIXP.&LEVELP.CLIST libraries into a VLF data space to maximize performance. This eliminates EXCPs and improves elapsed time.

Quick-Fetch by Legent provides similar functionality to VLF. It places highly-used modules into storage to reduce I/O during loads. Quick-Fetch identifies when updates occur so it uses the most current version. For more information about Quick-Fetch, call Legent in the United States at 800 676 5468. (Please note that this information is for your reference only. AppBuilder has not tested Quick-Fetch, and therefore cannot endorse the product.)


Execution Environment

Execution EnvironmentThe AppBuilder mainframe application execution (AE) environment supports different national requirements for date, time, and currency formats.

Data Source

Since the requirement for National Language Support (NLS) formats on the host was driven by similar support on the PC workstation, we looked to the PC environment for the source of the basic data.

On the PC, two C header files define the supported countries or national language types (for example, while most countries have a single defined format Canada has Canadian_French and Canadian_English formats), and the data formats for each of those countries. The information defining these formats includes date and time format (month, day, year; day, month, year; etc.), the separators used between the parts of date and time, the currency symbol, the separators used to indicate thousands and decimal positions, and the number of decimal places to be used.

Host Format

On the host, we decided to put this information in a table held in main storage rather than as definitions compiled into each program that might need them. By storing the information this way, the data:

• Is held in only one place

• Can be changed without recompiling any executable programs (with the inherent possibility of missing one or more programs that need to be recompiled)

• Can be modified easily during testing or in the field

This last feature allows, for instance, you to create a program to dynamically modify the data based on user input.

Conversion

The PC C header defining the data formats for each country is uploaded to the host where a REXX program processes it. This program parses the data and creates an output file, which is an Assembler language source macro. This macro is included into the assembler source defining the table, is loaded into storage, and when compiled generates the national language data table*. This data table is link edited into the AppBuilder Global Parameters Program HPEGAPA (for the PCV environment) or HPSCGAP (for the CNV3 environment). Since this NLS table contains data for all supported countries, a AppBuilder country number functions as an index to the data.

In actuality, the data is held as three interconnected tables—one containing character string data, one containing punctuation characters and a third containing edit rules and pointers to the other two tables. The reasons for having three tables are to compress string data and to avoid storing duplicate data, while still permitting flexibility for future expansion.

Country Code and Code Page

Confusion occurs on occasion about the AppBuilder country code and the code page. The country code is a simple index into a data table that matches the PC C header file, which defines the supported countries. It is a number sequentially assigned to the list of supported countries: Albania is 1 and Yugoslavia is 35.



The code page, on the other hand, is an IBM-assigned number that designates the character set used in each country. This is more relevant on a workstation than the host because most (though not all) hosts use the same code page, but a workstation can be set up to use many code pages and can switch between them.

The code page defines which character is produced on a display or printer for a given byte value (0 to 255). Many of these are invariant across code pages, but some produce different results—for example, the value for the dollar sign in the US appears as the monetary pound sign in the UK.

Country Codes for Fields, Panels, and Systems

When a window is painted using the AppBuilder Window Painter and a field that can have national language variants is placed on the panel, you can choose in which country format to display the field. The choices are: any specific country, the panel default, or the system default. You choose the panel default the same way. Thus, for a system running in Switzerland, it is possible to define a panel default of German with fields displaying in French, Italian, and default—and therefore German—formats.

AppBuilder stores the chosen country code as part of the field and panel definition. If the field country is zero, it defaults to the panel, and similarly panel to system. If a specific format is chosen for a field instead of a predefined country format then this specific format is saved along with the other field attributes and used at runtime. The system country code is stored in the AppBuilder Global Area Program HPEGAPA. This country code is initially set to 34 for the United States and so you must change it to the appropriate code when you install AppBuilder.

We provide a small global area customization program called HPEUCGP, in which you can change the country code to simplify the task of customization. This program is then assembled and linked into the HPEGAPA load module.

Supported Countries

In the current implementation of the host NLS, AppBuilder supports thirty-five countries. These are shown below with the data for each.

The columns headed P, T, D, N, and DP indicate the default formatting and punctuation for the country, and are described in Table 2-7.

Table 2-7 Countries supported by NLS

Country name No.Date format and separator

Time format and separator

Cur-rency P T D N DP

ALBANIA 1 %Y/%0m/%d %t:%0m:%0s Lek 0 . , 1 2

ARGENTINA 2 %d/%m/%0y %0t.%0m.%0s A 0 . , 1 2

AUSTRIA 3 %Y-%0m-%0d %0t:%0m:%0s,%0f S 2 . , 1 2

BELGIUM 4 %d/%m/%0y %0t:%0m:%0s,%0f BF 3 . , 5 2

BRAZIL 5 %0d/%0m/%0y %0t:%0m:%0s $ 1 . , 1 2

CANADA_FRENCH 6 %0y-%0m-%0d %0t:%0m:%0s $ 0 , . 1 2

CANADA_ENGLISH 7 %0d/%0m/%0y %0t:%0m:%0s.%0f $ 0 , . 1 2

CHINA 8 %Y.%0m.%0d %0t:%0m:%0s ¥ 0 , . 1 2

CZECHOSLOVAKIA 9 %Y-%0m-%0d %0t:%0m:%0s Kcs 2 . , 1 2

DENMARK 10 %0d-%0m-%0y %0t.%0m.%0s,%0f kr 2 . , 2 2

FINLAND 11 %0d.%0m.%Y %0t.%0m.%0s,%0f Mk 3 , 3 2

FRANCE 12 %0d.%0m.%Y %0t:%0m:%0s,%0f F 3 , 5 2



P represents the currency symbol position. The possible values are as follows:

• 0=prefix

• 1=prefix with a space

• 2=suffix

• 3=suffix with a space

T represents the thousands separator.

D represents the decimal indicator.

GERMANY 13 %0d.%0m.%Y %0t:%0m:%0s DM 0 . , 1 2

GREECE 14 %0d/%0m/%0y %0t:%0m:%0s.%0f Drs 0 . , 1 2

HUNGARY 15 %Y-%0m-%0d %0t:%0m:%0s FT 0 , 1 2

ICELAND 16 %Y-%0m-%0d %0t:%0m:%0s kr 3 . , 5 2

ITALY 17 %0d/%0m/%0y %0t.%0m.%0s,%0f L 2 . , 1 0

JAPAN 18 %Y-%0m-%0d %0t:%0m:%0s ¥ 0 , . 1 0

NETHERLANDS 19 %0d-%0m-%0y %0t:%0m:%0s F 2 . , 2 2

NEW_ZEALAND 20 %0d/%0m/%0y %0t:%0m:%0s $ 0 , . 1 2

NORWAY 21 %0d.%0m.%0y %0t:%0m:%0s,%0f kr 0 . , 3 2

POLAND 22 %Y-%0m-%0d %0t:%0m:%0s Zl 0 . , 1 2

PORTUGAL 23 %0d-%0m-%Y %0t:%0m:%0s Esc. 3 . , 1 2

ROMANIA 24 %Y-%0m-%0d %0t:%0m:%0s Lei 2 . , 1 2

SOUTH_AFRICA 25 %Y-%0m-%0d %0hh%0m:%0s.%0f R 0 , 0 2

SOUTH_KOREA 26 %Y.%0m.%0d %0t:%0m:%0s W 0 , . 1 2

SPAIN 27 %0d/%0m/%0y %0t:%0m:%0s Pts 2 . , 1 0

SWEDEN 28 %Y-%0m-%0d kl %0t.%0m.%0s Kr 3 . , 5 2

SWITZERLAND 29 %0d.%0m.%0y %0t,%0m,%0s Fr. 0 ‘ . 1 2

TAIWAN 30 %0y/%0m/%0d %0t:%0m:%0s.%0f $ 0 , . 1 2

THAILAND 31 %0d/%0m/%0y %0t:%0m:%0s B 0 , . 2 2

TURKEY 32 %0d/%0m/%0y %0t:%0m:%0s TL 0 . , 1 0

UNITED_KINGDOM 33 %0d/%0m/%0y %0t:%0m:%0s £ 0 , . 1 2

UNITED_STATES 34 %0m/%0d/%0y %0h:%0m:%0s%x $ 0 , . 1 2

YUGOSLAVIA 35 %Y-%0m-%0d %0t:%0m:%0s Din 2 . , 1 2

Table 2-7 Countries supported by NLS (Continued)

Country name No.Date format and separator

Time format and separator

Cur-rency P T D N DP



N represents the negative number format The possible values are as follows (1 represents the number and $ represents the currency symbol):

• 0=($1)

• 1=-$1

• 2=$-1

• 3=$1-

• 4=(1$)

• 5=-1$

• 6=1-$

• 7=1$-

DP represents the default number of decimal places displayed.

Monitoring Data Set Space Allocations

Several data sets need to be monitored for adequate space allocation, particularly during periods of heavy application development. An example is when developers are repreparing all rules for an application just before migrating an application from the development region to the testing region.

While the space allocation for all data sets should be watched, those approaching capacity should be noted and acted on. Keep an eye on all AppBuilder user data sets and panel and view files. The following list contains AppBuilder data sets that may exceed 90% and should be monitored:

• &USRVQUAL..LOADBT (Batch)

• &USRVQUAL..NCALBT (Batch)

• &USRVQUAL..LOADCI (CICS)

• &USRVQUAL..NCALCI (CICS)

• &USRVQUAL..LOADIM (IMS)

• &USRVQUAL..NCALIM (IMS)

We recommend the repository administrator or AppBuilder tool/environment support analyst develop and run a batch job periodically (perhaps weekly, depending on the volume of activity at your site) to check for at least these three things:

1. Which AppBuilder data sets (PDS) are over 90% full? Also, which are with directory blocks that are more than 90% used?

2. Which AppBuilder files (VSAM) have over 75 extents?

3. What AppBuilder VSAM volume is over 90% full?

Observe the data sets approaching their capacities. When you have answers to the three questions above, take appropriate action to relieve space problems.

• Question 1: several actions are available—compress the PDS, add directory blocks, and/or add tracks.

• Question 2: work with systems programmers to expand the VSAM data sets. The expansion requires their deallocation from CICS (unless the VSAM is batch) and about 30 minutes downtime. Because



of the downtime, first notify the application developers. Also, ensure that no CASIM migrations are running during the expansion activity.

• Question 3: the REORG jobs that run nightly at most sites may reallocate the space. If not, coordinate this work with your onsite DASD group.

It is also important to ‘clean up’ the repository by deleting orphaned objects. Orphan objects are candidates for deletion from the repository because they are obsolete and take up valuable space. Some users run orphan reports to identify the objects unrelated to other objects. A program of periodic clean up reduces data set space allocation problems.




CHAPTER

3 INSTALLATION REQUIREMENTS


This section summarizes the hardware and software prerequisites and corequisites for the AppBuilderHost Development Workbench. See the checklists in Chapter E, “Hardware and Software Checklists” to verify that your system is ready to install AppBuilder.

Hardware and DASD RequirementsTable 3-1 shows the hardware requirements for the AppBuilder Host Development Workbench.

Table 3-2 shows the DASD cylinder allocations for the base AppBuilder Host Development Workbench and its optional products. The DASD cylinder allocations are based on a DASD class of 3380.

Table 3-1 Hardware requirements

Mainframe Model IBM 3090 or equivalent

Communications 3270 SDLC communication protocol

Magnetic Media 3840/3490 BPI (tape cartridge)

Note Approximate DASD allocations for AppBuilder are derived from AppBuilder's QA testing, and limited to specified parameters. Customers should consider their own experience, normal system usage, and growth when determining their overall DASD requirements.

Table 3-2 DASD cylinder allocations

AppBuilder Host Development Workbench

AppBuilder Enterprise Repository (Base)This is the DASD requirement to install and use base AppBuilder Host Development Workbench (Enterprise Repository, Host Installation Workbench, and one repository version) for approximately 6 months.

2550 cylinders (total), comprised of:1350 cylinders for base software and one repository version980 cylinders for DB2 data sets220 cylinders for temporary work data sets

DASD cylinder allocation for each additional repository version 660 cylinders per version (includes repository software and data for each version)

Optional products

CICS Online Preparation70 cylinders for data sets250 cylinders for backups15 cylinders per repository version

CICS 3270 Converse Preparation Workbench 5 cylinders for data sets250 cylinders for backups


Supported Third-party Products

Supported Third-party ProductsThe following is a summary of supported versions. For updated information, contact the ActionLine..

Mainframe Batch60 cylinders for data sets250 cylinders for backups15 cylinders per repository version

Mainframe Report Writer 5 cylinders for data sets250 cylinders for backups

IMS Online Preparation70 cylinders for data sets250 cylinders for backups15 cylinders per repository version

IMS 3270 Converse Preparation Workbench 5 cylinders for data sets250 cylinders for backups

Table 3-4 Third-party Support

Third-party Product PublisherSupported Versions for AppBuilder 2.0.3.1

Mainframe Operating SystemOS/390 IBM 2.9, 2.10

z/OS IBM 1.1, 1.2, 1.3

System Software

CICS/ESA IBM 4.1

CICS Transaction Server for OS/390 IBM 1.1, 1.2, 1.3

CICS Transaction Server for z/OS IBM 2.2

IMS IBM 7.1

IMS/ESA IBM 6.1

MQSeries Workflow for OS/390 IBM 3.2

MQSeries Workflow for z/OS IBM 3.3

WebSphere Application Server for OS/390 (Standard Edition) IBM 3.5

Compilers and Runtime Libraries

Assembler H IBM 2.1

High Level Assembler IBM 2.1

COBOL for OS/390 & VM IBM 2.1, 2.2

Enterprise COBOL for z/OS and OS/390 IBM 3.1

Enterprise PL/I for z/OS and OS/390 IBM 3.1

VisualAge PL/I for OS/390 IBM 2.2

PL/I for MVS and VM IBM 1.1.1

LE Runtime OS/390 IBM 2.9, 2.10

DatabaseDB2 UDB for OS/390 IBM 6

DB2 UDB for OS/390 and z/OS IBM 7

Table 3-2 DASD cylinder allocations (Continued)

3-2 Installation Requirements

CHAPTER

4 THE HOST INSTALLATION WORKBENCH


This section describes how to use the AppBuilder 2.0.3.1 Host Development Workbench.

Using the Host Installation WorkbenchAll host installation is done through the Host Installation Workbench (HIW), an ISPF dialog that provides installation and maintenance functions for AppBuilder systems and repositories. Once HIW is installed on a mainframe machine it can be used to manage an unlimited number of systems and repositories resident on the same machine. In this sense, HIW is considered global.

Another feature is the decoupling of the repository and system. The system contains the AppBuilder software in mod level and base level libraries and the INI members @MVSENV and @SEERENV. The repository includes the DB2 database, user data sets (VSAM and non-VSAM) and repository data sets including the INI members @HPSENV, @INSTENV, @HPSSTAT, @USRENVn, @RBDENVn and @MIGENVn. One system can support many repositories, allowing the addition of repositories as growth demands it without the re-installation of system software. Topics include:

• Maintenance History Log File

• INI Files

• Repository - System Association

• Enable and Disable Functions

• Displaying Information about Systems and Repositories

• Installation Data Sets

• Installation Notes

• Installation Procedure

Packing ListYou should have received the following software. If you did not receive all the pieces listed below, please contact AppBuilder Distribution.

• AppBuilder REL 2.0.3.1

Volume Serial No. xxxxxx

where xxxxxx is the unique six digit volume serial number of the tapes provided.


Using the Host Installation Workbench

• One CD that contains the following:

The installation document entitled: Hostpi.pdf

The release notes entitled: ReleaseNoteBaseInstall.pdf

The release roadmap entitled: RoadMap.pdf

Two emergency fixes (see Readme.txt)

Readme document entitled: Readme.txt

Maintenance History Log FileThe primary control mechanism for the workbench is the Maintenance History Log file (MHLOG) which exists at the global (HIW) level. It is a sequential file containing records which detail the application of AppBuilder releases at the system, repository and version level. The file is updated via two HIW programs - ILOG001 and ILOG002 - and should not be updated manually. The integrity of the file is crucial to smooth operation of the workbench, therefore the file should be backed up. The following table details the record layout of MHLOG. Please note that all fields are character.

The MHLOG file is initially delivered with a DUMMY record as the first record so that the file will never be empty. This record should be left in place.

Table 4-1 Maintenance History Log file record layout

Col 001 to 001: Record Type (1 system, 2 repository, 3 version)

Col 002 to 009: System ID

Col 010 to 017: Repository ID

Col 018 to 019: Version ID

Col 020 to 027: Release ID

Col 028 to 033: Product ID

Col 034 to 034: Version Optional Indicator

Col 035 to 035: Roll-up Indicator

Col 036 to 036: Disregard Indicator

Col 037 to 044: “Cloned From” System ID

Col 045 to 052: “Associated From” System ID

Col 053 to 069: Timestamp for start of an action (clone etc.)

Col 070 to 086: Timestamp for completion of software applied.

Col 087 to 103: Timestamp for completion of clone system

Col 104 to 120: Timestamp for completion of backout

Table 4-2 MHLOG field descriptions

Field Description

Record type

A 1 in this column indicates a system record - that is, a record of an action performed on a system. A 2 in this column indicates a repository record and a 3 indicates a version record. A record is kept for each software release that is applied to a system, repository and version.

System IDThe system name. Each system must be identified by a unique name of up to 8 characters. The system name must be a valid PDS member name.

4-2 The Host Installation Workbench

Using the Host Installation Workbench

Another HIW file that is populated during installation is &GLOBQUAL..USER.CLIST (See GLOBQUAL for an explanation of the qualifier &GLOBQUAL). This PDS contains one member for each system and repository. The member has the same name as the entity it describes. The members hold minimal information needed to describe the entity to HIW. Note that since the system and repository members are in the same PDS, all systems and repositories must have unique names.

INI FilesThe AppBuilder REL 2.0.3.x correlation of the environmental CLIST is the INI file. Control variables are not accessed via the ISPF variable pools but are read directly into the active program space from PDS members called INI files. The INI PDS exists at the &BASEQUAL, &MODQUAL and &REPQUAL levels. The INI members which contain system-wide parameters are @MVSENV and @SEERENV. Variables which pertain to (and should vary between) repositories are held in @HPSENV and @INSTENV. Variables which pertain to a specific version are held in @USRENV, @MIGENV, and @RBDENV. The concatenation of the three PDS levels allows flexibility in altering variables: If a system variable such as the PL/I compiler name is to be changed and checked out against a single repository, the member @MVSENV should be copied up to the @REPQUAL level where the variable change will affect only the repository described by &REPQUAL..* A change at the &BASEQUAL or &MODQUAL will affect all repositories associated with the system described by &BASEQUAL..* and &MODQUAL..*.

Repository - System AssociationEach repository is associated with a system when it is created. That means that the repository “runs off of” the copy of AppBuilder software in a given system. The association is accomplished by the setting of the variables &BASEQUAL and &MODQUAL in @HPSENV. These variables act as pointers to the related system libraries. The association based on these variables is also expressed in the repository allocation clist HPSALLOC, the skeleton TSODD and the panel ISR@PRIM. HIW includes a facility for selecting a different system to be associated with a repository. This action is called Associate Repository and is available on the Repository Workbench menu.

Repository ID

The repository name. Each repository must be identified by a unique name of up to 8 characters. The repository name must be a valid PDS member name. A repository name cannot be the same as a system name.

Version ID The version number.

Release IDThis is the short release name i.e. HPS2031or SVB2031 which identifies each release of AppBuilder software.

Product ID This identifies the product line to which a release belongs.

Version Optional IndicatorThis flag designates releases that may be optionally applied to a version. It is for AppBuilder use only.

Rollup Indicator If a release includes other releases in it this column will be set to “Y”.

Disregard IndicatorThis column may be used to indicate a release which affects system software only.

Cloned-from System ID This column is not currently used.

Associated-from System IDIf a repository is moved from one system to another, the source SYSID will be here. This allows tracking of the repository history.

Timestamp

The four timestamp fields are populated when the indicated actions are performed. If the backout timestamp is populated, the record will be displayed as “DELETED” when the software history is viewed.

Table 4-2 MHLOG field descriptions (Continued)

Field Description


Installation Job Processing

The Associate Repository action could be performed in the following scenario:

Repository R1 is associated with system S1 which is at the AB2031 level. System S2 is created using AB2031 and then upgraded with the optional release AB2032. Repository R1 can be associated with System S2 and then upgraded to AB2032, preserving the applications in the repository. This would be an alternative approach to creating new repository R2 associated with system S2 and then migrating applications from R1 to R2.

Association is only allowed between a repository and a system that is at the same or higher level of software as the repository. If any product or release has been applied to a repository, the repository cannot be associated with a system which does not have that product or release. If a repository is associated with a system which has products or releases applied to it that are not applied to the repository, the repository will be disabled pending upgrade to the software level of the target system.

Enable and Disable FunctionsHIW provides the means to enable and disable a repository or version. This function can be used to prevent access to a resource while it is being maintained. The Enable/Disable Repository action is selected from the Repository Workbench menu; the Enable/Disable Version actions is accessed from the Maintain Version menu. The repository variable Enable is kept in the INI member @HPSSTAT; the version variable is kept in the @USRENVn INI member. The repository variable has precedence; an enabled version cannot be accessed within a disabled repository.

Displaying Information about Systems and RepositoriesHIW provides two ways to display information about systems and repositories. The Display Software History function is available from both the System Workbench and Repository Workbench menus. This function reads information from the MHLOG file pertaining to the specified system or repository and formats it for display. Information about each release applied is presented in chronological order indicating whether the release was backed out. The List Systems and Repositories function, also available from either workbench, provides an overview of all systems and repositories and their associations. The repository status column indicates whether the repository is enabled or disabled. Repositories which are not currently associated with any system are indicated with a status of “ORPHAN”. A status of “UNKNOWN” indicates a possible problem with the MHLOG which could be due to an aborted release or processing failure and should be resolved.

Installation Job ProcessingHIW employs ISPF tables to control processing of installation jobs. After the release software is unloaded using the System Workbench, a job table is created which displays the jobs needed to install the release. Some of the jobs may be optional such as the tape backup job. Others are required. HIW enforces the order in which the jobs are run by checking the Status column in the job table. A job cannot be run until its prerequisite job has completed successfully. To ensure smooth job processing it is essential to submit the jobs from the job table panel rather than from a TSO edit session. Jobs that must be altered should be edited and saved, then submitted from the job panel. When a job has completed successfully, the Status column will be updated to reflect this. Repository processing is similar and involves two tables. The first table presented is the installation table and includes all releases which are


Backing Out a Release

needed to bring the repository in line with the system software. These must be selected in order. Within each release there will be a table of jobs needed to complete that release. Processing of this table is identical to the system function.

Installation Data SetsSeveral data sets are created during installation to hold generated jobs and file tailored items which are copied to production via batch jobs—for example, INI files. These data sets following naming conventions described here:

System jobs and members are written to data sets beginning with &INSTQUAL..&RELNUM where &RELNUM is the release name such as AB2031, SVB2031 etc. and &INSTQUAL has the value entered for the system. Generated jobs are written to &INSTQUAL..&RELNUM..CNTL. Generated members, such as edit macro drivers, are written to &INSTQUAL..&RELNUM..ICLIST.

Since many repositories can be created from one system, the repository installation jobs are kept in separate data sets for each repository. These data sets are &INSTQUAL..&REPOSID..&RELNUM..CNTL for optional releases, and &INSTQUAL..&REPOSID..CNTL for the base release (AB2031). File tailored output is written to one of two data sets depending on the required DCB. Examples follow for a repository called NEWRISE where &INSTQUAL is “SS0221.INSTALL”:

Backing Out a ReleaseEach PTF includes a job to back out the release by restoring backed up data sets (note that this only works if the optional backup job is run) and completing the deletion timestamp in the MHLOG record. Backout accomplishes reversion to the state prior to installation except with respect to the MHLOG file which is updated rather than reverted. With respect to an initial installation of a release such as AppBuilder 2.0.3.1 Host Development Workbench which creates new AppBuilder data sets, there is no backed-up software to restore. Therefore to back out an initial AppBuilder installation the user should delete all data sets beginning with &INSTQUAL, &BASEQUAL, &MODQUAL, &REPQUAL, &USRQUAL, &VSMQUAL and &VSUVQUAL. In addition, the MHLOG records for the deleted system or repository should be removed from the log file to allow the system or repository to be re-added in the future. Also, the entry in &GLOBQUAL..USER.CLIST should be deleted for completeness.

PrerequisitesRefer to Chapter E, “Hardware and Software Checklists” and Chapter F, “Host Installation Workbench Customization Worksheets” in this document to prepare for this installation.

Table 4-3 Sample Repository Data Sets

SS0221.INSTALL.NEWRISE.CNTL holds repository creation jobs for base release

SS0221.INSTALL.NEWRISE.SVC2031.CNTL holds repository jobs for release SVC2031

SS0221.INSTALL.NEWRISE.ICLIST holds file tailored output with DCB same as client’s CLIST data set (VB if required)

SS0221.INSTALL.NEWRISE.ISPFREP holds file tailored output with FB DCB

Note Data sets ending in IREP4TB*, IREP400A, ISYS150M and ISYS4TB* hold the job tables.


Installation Notes

Installation NotesThe installation procedure described in this document is as follows:

1. Install AppBuilder Host Installation Workbench software.

2. Install AppBuilder Enterprise Repository software, as described in Chapter 5, “Installing the Enterprise Repository”

a. Install the system portion of AppBuilder Enterprise Repository software.

Create System

First you must perform Option 1, Create System.

b. Install the repository portion of AppBuilder Enterprise Repository software.

Create Repository

The AppBuilder Host Installation Workbench (HIW) software is used to install all subsequent AppBuilder software on an IBM mainframe. After HIW software is installed, it also provides functions for reviewing and maintaining your AppBuilder software. For information on HIW post-installation options, see the AppBuilder Enterprise Administration Reference Guide .

Using the AppBuilder Host Installation Workbench, you can stop an installation after the successful completion of any function, then return to the next function later. You can also install the system portions of multiple AppBuilder products before continuing with the repository functions. Figure 4-1 shows the order in which AppBuilder software is installed. To use the chart, locate the software you wish to install. Read from left to right to see which AppBuilder software must be installed prior to the software you want to install.

Figure 4-1 Software installation order

Note The AppBuilder Host Installation Workbench and the AppBuilder Enterprise Repository must be installed before any other AppBuilder mainframe-based software is installed.

Ap

pB

uild

er Ho

st Installatio

n W

orkb

ench

(install co

de: IN

S2031)

Ap

pB

uild

er E

nterp

rise Rep

osito

ry(in

stall cod

e: AB

2031)

AppBuilder Mainframe Batch Preparation Workbench(install code: SVB2031)

AppBuilder IMS Online Preparation Workbench(install code: SVI2031)

AppBuilder CICS Online Preparation Workbench(install code: SVC2031)

AppBuilder Report Writer Preparation(install code: RPW2031)


Installing the Host Installation Workbench

The outline below shows all AppBuilder Host Installation Workbench function options you will use to install AppBuilder Enterprise Repository software. Option steps must be completed successfully in order. Use the checkboxes provided here to keep track of your completed installation steps.

Installing the Host Installation WorkbenchBefore you can install Host Installation Workbench software, JCL instructions to create bootstrap data sets for the installation must be loaded on the mainframe. The basic steps in this process are:

a. Create a partitioned data set (PDS) to hold the installation dialog members.

b. Unload the members from the AppBuilder REL 2.0.3.1 tape to the newly-created PDS.

c. Specify your site-specific variables.

d. Submit the Unload job.

e. The Installation Workbench installation is completed once steps (a) to (d) have been successfully completed. You can then use the Installation Workbench to install all other AppBuilder software.

The previous steps (a to e) outline the highlights of the installation. The next section shows the step-by-step installation procedure.

Table 4-4 Host Installation Workbench function options

Option 1—System functions

Create system software

Unload installation data sets

Perform installation

Capture system variables

Unload AppBuilder software

Create system installation jobs

Submit system installation jobs

Option 2—Repository functions

Create repository

Create installation table

Process installation table

Capture repository values

Create repository installation jobs

Submit repository installation jobs

Activate repository

Note The repository installation includes a job to create the AppBuilder DB2 database, tablespaces, and tables. If you choose to allocate VSAM files for the DB2 objects, this job will contain approximately 18000 lines. Some client sites may use ISPF work files that are too small to allow the file-tailoring of this jobstream. In this case, the files ISPWRK1, ISPWRK2, ISPWRK3, and ISPWRK4 should be reallocated with additional space. BluePhoenix Solutions suggests a space parameter of (CYL, (5,5)) for each file.



Installation ProcedureThe following procedure gives detailed instructions about installing the Host Development Workbench, release code INS2031.

1. Unload the JCL from the install tape labeled “AppBuilder REL 2.0.3.1” to the PDS which is created in the job. Use the following JCL to perform the unload:

//JOBCARD JOB (ACCOUNT),'NAME',MSGCLASS=?,CLASS=? //* //******************************************************************* //* CHANGE THE ABOVE JOBCARD TO THE REQUIREMENTS OF YOUR SITE * //******************************************************************* //* //******************************************************************* //* THIS JOB UNLOADS THE FIRST FILE FROM THE INSTALL TAPE * //******************************************************************* //* //******************************************************************* //* * //* STEP 1: ALLOCATES THE PDS THAT WILL HOLD THE JCL MEMBERS * //* * //******************************************************************* //STEP1 EXEC PGM=IEFBR14,REGION=2000K //******************************************************************* //* CHANGE "&OUTDSN" TO A VALID PDS NAME ON THE FOLLOWING JCL LINE * //* SUGGESTED NAME: "HLQ.DIALOG" WHERE HLQ = HIGH LEVEL QUALIFIER * //******************************************************************* //PDSOUT DD DSN=&OUTDSN, // DISP=(NEW,CATLG,DELETE), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120), // UNIT=SYSDA,SPACE=(TRK,(5,1,20)) //* //SYSOUT DD DUMMY //SYSUDUMP DD DUMMY //* //******************************************************************* //* * //* STEP 2: UNLOADS FILE 1 FROM THE INSTALL TAPE TO PDS CREATED IN * //* STEP 1.* //* * //******************************************************************* //STEP2 EXEC PGM=IEBCOPY,COND=(0,NE)//SYSPRINT DD SYSOUT=* //******************************************************************* //* CHANGE "&OUTDSN" TO THE NAME OF THE PDS CREATED IN STEP 1. * //* CHANGE "CART" TO A VALID UNIT NAME FOR A TAPE DRIVE * //******************************************************************* //INTAPE DD DSN=HPSOUT.BOOTSTRP.JCL,DISP=OLD, // UNIT=CART,LABEL=(1,SL), // DCB=&OUTDSN, // VOL=(PRIVATE,RETAIN,,SER=008000) //******************************************************************* //* CHANGE "&OUTDSN" TO THE NAME OF THE PDS CREATED IN STEP 1. * //******************************************************************* //OUTDS DD DSN=&OUTDSN,DISP=OLD //SYSUT3 DD UNIT=SYSDA,



// SPACE=(CYL,(3)) //SYSUT4 DD UNIT=SYSDA, // SPACE=(CYL,(3)) //SYSIN DD * COPY INDD=INTAPE,OUTDD=OUTDS /* //

2. The following members should be included in the PDS after the unload from the install tape:

• BOOTPNL

• BOOTSKL

• INSBOOT

• INSKEL

• STARTSKL

3. Edit the member INSBOOT according to the instructions in the top of the member: Change the string DIALOG.DSNAME in line 14 to the name of the data set created in step 1. Do not make any other edits.

4. Execute the member INSBOOT from the ISPF environment, using the TSO EXEC command, for example, TSO EXEC 'ABINST.DIALOG(INSBOOT)'. Figure 4-2 shows the Bootstrap Information panel that prompts for workbench installation information. (After entering that information, you see a jobstream displayed for edit in the UNLOAD member. Edit the job card information in the jobstream, and submit the job.)

Figure 4-2 Host Installation Workbench

100.1 Installation Workbench Dataset Qualifier [Default: AB.INS2031]

Enter the data set qualifier to be used for Installation Workbench data sets at your site. This qualifier forms the basis of all data set names used in this installation. Enter a maximum of 24 characters.

100.2 Volume Serial Number of your INS2031 tape [Default: None]

Enter the six-digit volume serial number located on the label of your Installation Workbench tape.



100.3 Unit used to read your INS2031 tape [Default: CART]

Enter the unit (up to 8 characters) used to read your Installation Workbench tape.

100.4 Use Bypass Label Processing to unload tape? (Y/N) [Default: None]

Enter Y to use Bypass Label Processing and N to not use it.

100.5 DASD Unit for Installation Workbench Datasets [Default: SYSDA]

Enter the unit of the DASD containing the installation workbench data sets.

100.6 Volume for Installation Workbench Datasets (Optional) [Default: None]

Enter the volume ID for the installation workbench data sets.

100.7 DASD Unit for Temporary Datasets [Default: SYSDA]

Enter the DASD unit for temporary data sets.

100.8 Volume for Temporary Datasets (Optional) [Default: None]

Enter the volume ID for your temporary data set.

100.9 Access Method Services Program -[Default: IDCAMS]

Enter the name of your access method services program.

100.10 Access Method Services Loadlib (Optional) [no default]

Enter the name of your Access Method Services Loadlib.

100.11 LE Link Library [Default:CEE.SCEELKED]

Enter the name of your LE link library.

100.12 LE Runtime Library [Default: CEE.SCEERUN]

Enter the name of your LE Runtime library.

5. The unload job is brought up in an edit session. Review and edit if necessary. Submit the JCL by typing SUB at the command prompt. Verify the job completed successfully. This job creates the following data sets:

&globqual..CLIST

&globqual..CNTL

&globqual..LNKT

&globqual..LOADLIB

&globqual..MHLOG

&globqual..MSGS

&globqual..OBJ

&globqual..PANELS

&globqual..ROLLUPS



&globqual..SKELS

&globqual..TABLES

&globqual..USER.CLIST

where &globqual is the value you entered in step 6 for the Host Installation Workbench Dataset Qualifier. See prompt 100.1 in step 6 above.

6. During the HIW installation, the following members will be created in your PDS:

7. The installation of the AppBuilder Host Installation Workbench is now complete.

INSTART This REXX invokes the Host Installation Workbench dialog.

STARTUP

This REXX can be executed from the READY prompt to allocate the LE runtime libraries needed by Host Installation Workbench if they are not in the STEPLIB of the user's TSO session.If they are not in the STEPLIB of the user's TSO logon procedure, they may be allocated by executing the member STARTUP (in the data set created in #1) from the READY prompt. This member may be moved to a library in the SYSPROC concatenation for convenience.

UNLOAD This job unloads the Host Installation Workbench data sets.




CHAPTER

5 INSTALLING THE ENTERPRISE REPOSITORY


The information in this section describes the detailed requirements and procedures for installing an AppBuilder enterprise repository.

PrerequisitesRefer to “Hardware and Software Checklists” and “Enterprise Repository Customization Worksheets” to prepare for this installation.

Packing ListYou should have received the following software. If you did not receive all the pieces listed below, please contact AppBuilder Distribution. See USA Headquarters for details.




• One CD that contains the following:

The installation document entitled: Hostpi.pdf

The release notes entitled: ReleaseNoteBaseInstall.pdf

The release roadmap entitled: RoadMap.pdf

Readme document entitled: Readme.txt

Two emergency fixes (see Readme.txt)

Installation NotesThe installation procedure is as follows:

1. Install AppBuilder Host Installation Workbench software. (See Chapter 4, “The Host Installation Workbench” for installation instructions.)

2. Install AppBuilder Enterprise Repository software.

a. Install the system portion of AppBuilder Enterprise Repository software.


Installing the AppBuilder Enterprise Repository

First you must perform Option 1, Create System.

b. Install the repository portion of AppBuilder Enterprise Repository software.

Using the AppBuilder Host Installation Workbench, you can stop an installation after the successful completion of any function, then return to the next function later. You can also install the system portions of multiple AppBuilder products before continuing with the repository functions. Figure 5-1 shows the order in which AppBuilder software is installed. To use the chart, locate the software you wish to install. Read from left to right to see what AppBuilder software must be installed prior to the software you want to install.

Figure 5-1 AppBuilder Installation Order

Installing the AppBuilder Enterprise RepositoryTo begin installing the Enterprise Repository, you must first start up the Host Installation Workbench.

Starting the Host Installation Workbench 1. The Host Installation Workbench (HIW) requires the LE runtime libraries in your TSO STEPLIB. If

they are not in the STEPLIB of your TSO logon procedure, you can allocate them by executing the REXX member STARTUP. This REXX is in the same data set created from the unload of the five members from the AppBuilder REL 2.0.3.1 install tape, see Chapter 4, “Installing the Host Installation Workbench”. For convenience, you can move this member to a library in the SYSPROC concatenation.

Note Only function options which will be used to install AppBuilder Enterprise Repository are described.

Note The AppBuilder Host Installation Workbench and the AppBuilder Enterprise Repository must be installed before any other mainframe-based software is installed.

Ap

pB

uild

er Ho

st Installatio

n W

orkb

ench

(install co

de: IN

S2031)

Ap

pB

uild

er E

nterp

rise Rep

osito

ry(in

stall cod

e: AB

20

31

)

AppBuilder Mainframe Batch Preparation Workbench(install code: SVB2031)

AppBuilder IMS Online Preparation Workbench(install code: SVI2031)

AppBuilder CICS Online Preparation Workbench(install code: SVC2031)

AppBuilder Report Writer Preparation(install code: RPW2031)

5-2 Installing the Enterprise Repository


The STARTUP REXX contains the ISPF command to display an ISPF main panel. If this command is not used at your location, edit the REXX with the appropriate command. You must execute STARTUP from the READY prompt. For example, type:

EX 'AB.INS2031.DIALOG(STARTUP)'

2. After the STARTUP REXX executes, it displays an ISPF main panel. To start the Host Installation Workbench, execute the REXX member INSTART located in the same data set as the STARTUP REXX. You must execute INSTART in the ISPF environment. For example, type from the COMMAND prompt in ISPF:

EX 'AB.INS2031.DIALOG(INSTART)'

3. After the INSTART REXX executes, it displays the main panel for AppBuilder Host Installation Workbench—Workbench Functions, shown in Figure 5-2.

4. There are two major steps to installing AppBuilder software: Option 1 - System Functions and Option 2, Repository Functions. Installing system functions is described next, and installing repository functions is described in Option 2 - Repository Functions.

Figure 5-2 Workbench Functions

Option 1 - System FunctionsThe system function portion of a AppBuilder software installation occurs first. This portion of the installation allows you to customize AppBuilder software to access your mainframe environment.

1. Enter 1 on the option line, as shown in Figure 5-3. The Create System Software option creates a new full installation of AppBuilder base system software. This option is only used for AppBuilder Enterprise Repository software.

200.1 Enter the System ID of the new system [Default: None]

Specify up to eight (8) alphanumeric characters per system name for your AppBuilder base system software. This name will be used to associate your AppBuilder base system software to one or more AppBuilder repositories. It must be a valid PDS member name which does not exist in the PDS

Note For this installation, the installer’s TSO session must have a minimum memory allocation of 6 MB.



&globqual..USER.CLIST. Refer to Chapter 4, “The Host Installation Workbench” section “Repository - System Association” for more information.

2. Press Enter. If you entered an existing System ID, a panel appears informing you that the ID already exists. You can then either specify that you want to enter another ID, or continue using the existing ID.

Figure 5-3 System Functions

Option 1 - Create System SoftwareFigure 5-4 shows the Create System Software panel. It allows you to create a new installation of AppBuilder base system software. In its first option, Option 1 - Unload Installation Data Sets, you enter data needed to create the unload JCL. In the second option, Perform Installation, you enter data needed to install and customize the software for your site.

Figure 5-4 Create System Software



Option 1 - Unload Installation Data Sets

1. Select option 1 Unload Installation Data sets in the panel in Figure 5-4 and press Enter.

2. Figure 5-5 is displayed. Enter the requested information and press Enter to continue.

After entering the data set information, if a duplicate data set name qualifier is detected, a panel is displayed alerting you to this situation. You must either select (N) and enter another qualifier or (Y) to allow the duplicate data sets to be deleted and recreated.

3. A panel is displayed to edit the Job Control card information. Edit if necessary and press Enter to continue.

4. The unload job is brought up in an edit session. Review, and edit if necessary. Submit the JCL by typing SUB at the command prompt. Verify the job completed successfully. This job creates the following data sets:

&instqual..AB2031.CNTL

&instqual..AB2031.ICLIST

&instqual..AB2031.IPANELS

&instqual..AB2031.ISKELS

where &instqual is the value entered for the prompt in step 200.2 below.

5. After the job completes successfully, select option 2 Perform Installation in Figure 5-4 and press Enter. See Perform Installation for more information.

Figure 5-5 Unload Installation Data Sets

6. Enter the following information:

200.2 Enter Installation Dataset Qualifier [Default: AB1.INSTALL]

Enter the name of the installation data set qualifier. This must be a different qualifier than that entered for 100.1. This qualifier defines data sets that hold the AppBuilder system and repository installation software. Enter a maximum of 17 characters.



200.3 Enter System Dataset Qualifier [Default: AB1.BASE]

Enter the name of the system data set qualifier. This qualifier defines data sets which hold the AppBuilder system software. Enter a maximum of 17 characters.

200.4 Enter Maintenance Dataset Qualifier [Default: AB1.MOD]

Enter the name of the maintenance data set qualifier. This qualifier defines data sets which are created empty and can be used to hold client modifications or product fixes received from AppBuilder. Enter a maximum of 17 characters.

200.5 Enter System VSAM data set qualifier [Default: AB1.BASE]

Enter the name of the system VSAM data set qualifier. This qualifier defines VSAM data sets which are part of the AppBuilder system software and not specific to a repository. Enter a maximum of 17 characters.

200.6 Enter language for Messages & Panels [Default:ENG]

Enter the language code for the messages and panels. Enter ENG (English) or DB for double byte characters (Japanese).

200.7 Enter the AppBuilder Release Name [Default: None]

You must enter AB2031. This code indicates which AppBuilder product you are installing.

200.8 Enter the Volume Serial Number of your AppBuilder tape [Default: None]

Enter the volume serial number of the AppBuilder tape. Each tape shipped by AppBuilder has a unique number. This number can be found on the tape and in the packing list provided with the tape.

200.9 Enter the Unit used to read your AppBuilder tape [Default: CART]

Enter the name of the unit used to read your AppBuilder tape.

200.10 Use Bypass Label Processing to unload tape? (Y/N) [Default: None]

Specify Y or N to use Bypass Label Processing to unload tape.

200.11 Enter the DASD Unit for AppBuilder Datasets [Default: SYSDA]

Enter the DASD unit for AppBuilder data sets.

200.12 Enter the DASD Volume for AppBuilder Datasets (Optional) [Default: None]

Enter the DASD volume for AppBuilder data sets, if applicable.

200.13 Enter the following for VSAM data sets if they apply:

Enter either a volume or management class.

200.13a Volume [Default: SYSDA]

Enter the volume for VSAM data sets, if applicable.

200.13b Management class [Default: None]

Enter the management class for VSAM data sets, if applicable.



200.14 Create FB or VB Clists for SYSPROC DD? (F/V) [Default: F]

Specify if the SYSPROC DD concatenation uses F (fixed block) or V (variable block) CLISTS.

200.15 If VB, specify LRECL and BLKSIZE:

If V (variable block CLISTs) entered in step 200.14, enter the required LRECL and BLKSIZE.

200.15a LRECL [Default: None]

Enter the record length if variable blocked CLISTs are used in step 200.14 (LRECL).

200.15b BLKSIZE [Default: None]

Enter the block size if variable blocked CLISTS are used in step 200.14 (BLKSIZE).

Perform InstallationPerform in sequence the following four options in Figure 5-6.

Figure 5-6 Perform Installation Menu Options

Option 1 - Capture System Variables

1. Select option 1, “Capture System Variables” to display a series of mainframe environment panels. Panel explanations begin with step 200.16 on page 5-8 and end with step 200.72 on page 5-20.

2. In each panel, customize the variables for your environment as needed. Press Enter.



Figure 5-7 Capture System Variables — mainframe environment, panel 1 of 9

200.16 LE Link Library [Default: CEE.SCEELKED]

Enter the name of the LE Link Library.

200.17 LE Runtime Library [Default: CEE.SCEERUN]

Enter the name of the LE Runtime Library.

200.18 PL/I Math Library [Default: blank]

Enter the name of the PL/I Math Library. If you do not use a PL/I Math Library, leave it blank.

200.19 PL/I Call Library [Default: blank]

Enter the name of the PL/I Call Library. If you do not use a PL/I Call Library, leave it blank.

200.20 COBOL II Compiler Library [Default: IGY.V2R1M0.SIGYCOMP]

Enter the name of the COBOL II Compiler Library.

200.21 Include STEPLIB in the Cobol Compile step (Y/N)? [Default: Y]

Do you want to include STEPLIB in the COBOL Compile step of rule preparation?

200.22 COBOL II Compiler Name [Default: IGYCRCTL]

Enter the name of the COBOL II Compiler.



Required Parameters

[Default: RENT,'TRUNC(BIN)', LIB]

You cannot change the required parameters.

Optional Parameters

[Default: LIST,'FLAG(W)', OPT]

You can modify the optional parameters to conform to your site specifications. The parameters that appear are needed for compiles within the product. The required and optional parameters are associated with CPARM1 and CPARM2 in the @MVSENV ini member and CPARM1 will be concatenated with CPARM2.

For Double Byte sites, the DBCS parameter should be added to the Optional parameter list.

200.23 H Assembler Name [Default: ASMA90]

Enter the Assembler H program name.

Required Parameters

[Default: NODECK,OBJECT]


Optional Parameters

[Default: LIST]

You can modify the optional parameters to conform to your site specifications. The parameters that appear are needed for compiles within the product. The required and optional parameters are associated with APARM1 and APARM2 in the @MVSENV ini member and APARM1 will be concatenated with APARM2.

For Double Byte sites, the DBCS parameter should be added to the Optional parameter list.

200.24 Mainframe Macro Library [Default: SYS1.MACLIB]

Enter the mainframe Macro library name.

200.25 Mainframe Distribution MGEN Library [Default: SYS1.AMODGEN]

Enter the name of the mainframe Distribution MGEN library.

200.26 Mainframe Target MGEN Library (Optional) [Default: SYS1.MODGEN]

Enter the name of the mainframe Target MGEN library if the IBM default name is not used.

3. Enter all information in the required data fields, then press Enter .




200.27 Is the PL/I Compiler Installed? [Default: N]

Specify if the PL/I compiler is installed. If not installed, the following PL/I items are optional. Enter Y or N.

200.28 PL/I Compiler Library [Default: IEL.V1R1M1.SIELCOMP]

Enter the name of the PL/I Compiler Library.

200.29 Include STEPLIB in the PL/I Compile step? (Y/N) [Default: Y]

200.30 PL/I Compiler Name [Default: IEL0AA]

Enter the PL/I Compiler name. Define the required and optional parameters needed by the PL/I Compiler.

200.31 Is the MQ Series installed? [Default: N]

200.32 MQ Series Load Library (optional)

Enter the name of the MQ Series Load Library.

Required Parameters

[Default: INC,OP,AG,NEST,STMT,GRAPHIC,'OPTIMIZE(TIME)']




Optional Parameters

[Default: 'A(F)','X(F)',MAP,OF,STG]

You can modify the optional parameters if necessary. Optional parameters are concatenated with required parameters.

4. Enter all information in the required data fields, then press Enter to advance to the next panel in the mainframe environment (see Figure 5-9).


200.33 C Compiler Library [Default: CBC.SCBCCMP]

Enter the name of the library that contains the C Pre-link module EDCPRLK.

• For Version 2.0.3.1, this will be in the compiler library.

• For Version 2.2, this will be in one of the runtime libraries.

The C compiler module is not required.

200.34 C Messages [Default: CEE.SCEEMSGP(EDCPMSGE)]

Enter the library containing the C/370 compiler messages.

• For Version 2.0.3.1, the displayed default is correct.

• For Version 2.2, the correct default is EDC.V2R2M0.SEDCMSGP(EDCPMSGE).

200.35 Enter the following if you will be creating C components.

Steps 200.33 thru 200.35c are optional. They are only required if C components will be written.

200.35a Include STEP:LIB in the C compile step? (Y/N) - [Default: Y]

200.35b C Compiler Name [Default: CBCDRVR]

Enter the name of the C compiler.

200.35c C Headers [Default: CEE.SCEEH.H]

Enter the library containing the C header files.



200.36 200.36 TCPIP SEZATCP Library [Default: TCPIP.SEZATCP]

200.37 200.37 TCPIP SEZACMTX Library [Default: TCPIP.SEZACMTX]

5. Enter all information in the required data fields, then press Enter.


200.38 Sort Program [Default: SORT]

Enter the sort program name.

200.39 Access Method Program [Default: IDCAMS]

Enter name if not IDCAMS.

200.40 Access Method Library (optional) [Default: None]

Enter library only if access method is not IDCAMS.

200.41 PDS Utility Program [Default: IEBCOPY]

Enter the name of the PDS copy utility program if not IEBCOPY.

200.42 PDS Utility Library (optional) [Default: None]

Enter the library name only if PDS copy utility program is not IEBCOPY.

Note If this value is blank, you must manually edit the @MVSENV INI file and set the IEBLIB variable to ‘N/A’.



200.43 TSO Command to clear the screen [Default: CLRSCRN]

200.44 Reason Code from LISTDSI if Dataset is Not Found [Default: 5]

If a third party package translates return codes from TSO LISTDSI, specify the TSO LISTDSI equivalent. [5] is returned by TSO LISTDSI. Used to designate the reason code from LISTDSI for data sets that are not found.

200.45 Is Dataset Archival Software such as HSM Used? (Y/N) [Default: Y]

Specify if data set archival software is used on this system.

200.45a Name of Program to Delete Archived Data Set [Default: HDELETE]

If “Y” entered for step 200.45, (data set archival software used) enter the name of the program used to delete archived data sets.

200.45b Delete Program Parameter String [Default: PURGE WAIT]

If “Y” entered for step 200.45, (data set archival software used) enter the delete program parameter string.

200.45c Reason Code Issued if Data Set is Migrated [Default: 9]

If “Y” entered for step 200.45, (data set archival software used) enter the return code issued if the data set is migrated.

6. Enter all information in the required data fields, then press Enter to advance to the next panel in the mainframe environment.


200.46 Linkage Editor AMODE [Default: 31]

Enter the addressing mode of AppBuilder generated modules.



200.47 Linkage Editor RMODE [Default: ANY]

Enter the residency mode of AppBuilder generated modules.

The following table lists valid and invalid combinations of AMODE and RMODE.

200.48 Link Pack Area Library [Default: SYS1.LPALIB]

Enter the library name of the link pack area if not SYS1.LPALIB.

200.49 DB2 Load Library [Default: DSN610.DSNLOAD]

Enter the name of the DB2 load library that has the DSN command processor.

200.50 DB2 Link Library [Default: DSN610.DSNLINK]

Enter the name of the DB2 link library that will be used to link DB2 programs.

200.51 DB2 Preprocessor Name [Default: DSNHPC]

Enter the DB2 preprocessor program name.

200.52 Include STEPLIB in the DB2 Preprocessor step? (Y/N) [Default: Y]

200.53 DB2 Utility Proc Name [Default: DSNUPROC]

Enter the DB2 utility procedure name.

200.54 DB2 Utility Load Library [Default: DSN610.DSNLOAD]

Enter the DB2 load library that contains the load module DSNUPROC or its equivalent at your site.

200.55 ISPF Link Library [Default: ISP.ISPLOAD]

The name of the ISPF link library used to link AppBuilder ISPF modules.

200.56 ISPF Profile Library [Default: None]

The name of the common ISPF table library that contains member ISPPROF.

200.57 Specify Mainframe Codepage [Default: 037]

The codepage is a number assigned by IBM to designate the character set in each country. It defines which character will be produced on a display or printer for a given byte value (0 to 255). Many of these

Table 5-1 Valid and Invalid Combinations of AMODE and RMODE

RMODE

AMODE 24 ANY

24 valid invalid

31 valid valid

ANY valid invalid

Note ISPF library names should not be left blank.



are unvarying across codepages, but some produce different results—for example, the value that produces a dollar sign in the US shows as a monetary pound sign in the UK.

Specify the host codepage for your national language.

200.58 Specify OS/2 Codepage -[Default: 437]

Enter the OS/2 codepage used on the development workstation. 437 is default codepage for US or UK English: 850 is the MLS codepage (US and UK English, French, Spanish, Italian, German, Danish, etc.). The [NLS] Codepage_OS2 value can be found on the development workstation in \HPS\HPS.INI.

200.59 Specify AIX Codepage [Default: 2]

Enter the AIX codepage used on the development workstation:1—IBM-850, or 2—IS08859-1.

200.60 PC Equivalent of ‘AT’ Character [Default: @]

If the codepage you have selected does not support the “@” character, enter the character that maps to the equivalent host value (for example, the character EBCDIC hex 7C is mapped to on the host).

200.61 Default Language for Repository Objects (Abbreviation) [Default: ENU]

Enter the default language abbreviation for the repository objects. For example, ENU means US English.

The following table lists valid codepage and default language combinations between mainframe, OS/2, and AIX, referenced by items 200.54, 200.55, 200.56, and 200.58.

The following table provides the definitions of default language abbreviations used in the proceeding table.

Table 5-2 Valid Codepage and Default Languages

Mainframe PC Default language abbreviation

037 437, 850, 860, 863 FRC, NLD, ENU, PTF, PTB, ENA

273 437, 850 DEU

280 437, 850 ITA

284 437, 850 ESP

297 437, 850 FRA

500 437, 850 FRS, DES, FRB, NLB

838 437, 874 THA

277 865, 850 DAN, NON, NOR

278 437, 850 FIN, SVE

285 437, 850 ENG

930 942 JPN

933 949 KOR

939 942 JPN

Table 5-3 Definition of Default Language Abbreviations

Default Language Abbreviation Language

DAN Danish

DEU German

DES Swiss German





ENA Australian English

ENG UK English

ENU US English

ESP Spanish

FIN Finnish

FRA French

FRB Belgian French

FRC French Canadian

FRS Swiss French

ITA Italian

JPN Japanese

KOR Korean

NLB Belgian Dutch

NLD Dutch

NON Nynorsk Norwegian

NOR Bokmal Norwegian

PTB Brazilian Portuguese

PTG Portuguese

SVE Swedish

THA Thai

Table 5-3 Definition of Default Language Abbreviations (Continued)

Default Language Abbreviation Language



200.62 Default Retrieval Format for DB2 DATE Values [Default: ISO]

Specify the retrieval format of DB2 DATE values. Valid values are:

• EUR—IBM European Standard

• ISO—International Standards Organization

• JIS—Japanese Industrial Standard

• USA—IBM USA Standard

• LOCAL—Site defined

200.63 If a LOCAL Date Format is used, enter it Here [Default: None]

Specify the DB2 date format if LOCAL specified in the previous step. This value must match the DATE format defined when DB2 was installed at your site. Example: %Y-%0m-%0d—year-month-day.

200.64 Default Retrieval Format for DB2 TIME Values [Default: ISO]

Specify the retrieval format of DB2 TIME values. Valid values are:

• EUR—IBM European Standard

• ISO—International Standards Organization

• JIS—Japanese Industrial Standard

• USA—IBM USA Standard

• LOCAL—Site defined

200.65 If a LOCAL Time Format is used, Enter it Here [Default: None]

Specify the DB2 date format if LOCAL specified in the previous step. This value must match the TIME format defined when DB2 was installed at your site. Example: %0t.%0m.%0s—hour.minute.second.

200.66 Maximum Nested IF statements in HPS Rules [Default: 40]

Specify the maximum level allowed for nesting IF statements consecutively. When rules code exceeds this limit, severe error #87959 will occur.

200.67 Retention Period for Tape Datasets in Days [Default: None]

Specify the number of days tape data sets will be kept. Input is required in this field.





These screens request names for CLIST and ISPF libraries, used when running TSO in background mode (IKJEFT01). Enter the name of at least one library for each of the following.

200.68 SYSPROC [Default: None]

Enter the CLIST libraries (SYSPROC) for background TSO jobs.

200.69 ISPPLIB [Default: None]

Enter the ISPF PANEL libraries (ISPPLIB) for background TSO jobs.


Note If more than five libraries are required for each concatenation, you must manually edit the TSODD skeleton found in &REPQUAL..FTSKEL.




Enter the names of at least one library for each of the following. These libraries will be included in AppBuilder batch jobs and must include the ISPF libraries.

200.70 ISPMLIB [Default: None]

Enter the ISPF MESSAGE libraries used for background TSO jobs.

200.71 ISPSLIB [Default: None]

Enter the ISPF SKELETON libraries used for background TSO jobs.

Continue to the next panel.

10. Enter the names of at least one library for each of the following. These libraries will be included in AppBuilder batch jobs and must include the ISPF libraries.




200.72 ISPTLIB [Default: None]

Enter the ISPF TABLE libraries used for background TSO jobs.

200.73 The ISPLLIB entries are optional. Omit if not used at your site. [Default: None]

Enter the optional ISPL libraries used for background TSO jobs.

11. After entering the appropriate libraries, press Enter to return to the Create System Software panel in Figure 5-16. With successful completion, the message “VARIABLES CREATED” appears in the top right corner of this panel.

Figure 5-16 Create System Software Menu



Option 2 - Unload AppBuilder Software1. From the Create System Software panel, select option 2 Unload AppBuilder Software.

Figure 5-17 Unload System Software

2. A panel displays Job Control Card information. Edit if necessary and press Enter.

3. The unload job is brought up in an edit session. Review and edit if necessary. Submit JCL by typing SUB at the COMMAND prompt. Verify that jobsteps have completed with a return code of "0". Some steps use the IEBCOPY utility and will have a return code of "4" because there is a missing member. You should check for missing members because these members are used later in the product. If you cannot find the member, take note of it and report it to the BluePhoenix Solutions Service Line. Then continue with job by verifying that all members are copied and all steps have completed. This job creates the data sets in Table 5-4 through Table 5-7.

• &BASEQUAL is the value you entered in prompt 200.3.

• &MODQUAL is the value you entered in prompt 200.4.

• &VSMQUAL is the value you entered in prompt 200.5.

• &INSTID is the installer’s TSO userid. This is the data set qualifier used for the Migration data sets as shown in Table 5-6 and Table 5-7.

Note After entering the data set information, if a duplicate data set name qualifier is detected, a panel is displayed alerting you to this situation. Select (N) to enter another qualifier or (Y) to allow the duplicate data sets to be deleted and recreated.

Table 5-4 Base Libraries

&BASEQUAL..CGCGINC &BASEQUAL..CGTABLE

&BASEQUAL..CHDR &BASEQUAL..CLIST

&BASEQUAL..COPYASM &BASEQUAL..COPYC

&BASEQUAL..COPYCOB &BASEQUAL..COPYPL1

&BASEQUAL..CSOURCE &BASEQUAL..DBRMLIB

&BASEQUAL..DDL &BASEQUAL..DDLVSAM

&BASEQUAL..ERESFILE.LOADRECS &BASEQUAL..EHPSFILE.LOADRECS






&BASEQUAL..FTSKELS &BASEQUAL..ERRMSG

&BASEQUAL..INIDFTIN &BASEQUAL..INI

&BASEQUAL..LKBS00 &BASEQUAL..LANGCFG

&BASEQUAL..LOADLIB &BASEQUAL..LKBSEC

&BASEQUAL..MESSAGIN &BASEQUAL..MSGS

&BASEQUAL..OBJ &BASEQUAL.OLDOC

&BASEQUAL.OLINST &BASEQUAL.OLMSGS

&BASEQUAL..PANELS &BASEQUAL..PCKGBASE

&BASEQUAL..PCKGRANT &BASEQUAL..PLANBASE

&BASEQUAL..PLKOBJ &BASEQUAL..PRELINK

&BASEQUAL..PRTLOG &BASEQUAL..RMIJCL

&BASEQUAL.SAMPLE &BASEQUAL.SAMP255

&BASEQUAL.SAMP80 &BASEQUAL..SKELS

&BASEQUAL..TABLES

&VSMQUAL..INIDFT &VSMQUAL..MESSAGES

Table 5-5 Maintenance libraries

&MODQUAL.CGTABLE &MODQUAL..CLIST

&MODQUAL..DBRMLIB &MODQUAL..FTSKELS

&MODQUAL..INI &MODQUAL..LOADLIB

&MODQUAL..MSGS &MODQUAL..OBJ

&MODQUAL...PANELS &MODQUAL..PLKOBJ

&MODQUAL..SKELS

Table 5-6 Default Repository

&INSTID..DEF2031.MIG.ELOGKEY &INSTID..DEF2031.MIG.EMIG

&INSTID..DEF2031.MIG.ENTITY &INSTID..DEF2031.MIG.INMIG

&INSTID..DEF2031.MIG.KEYWORD &INSTID..DEF2031.MIG.MIGCNTL

&INSTID..DEF2031.MIG.MIGXX &INSTID..DEF2031.MIG.RELATE

&INSTID..DEF2031.MIG.RLOGKEY &INSTID..DEF2031.MIG.SOURCE

&INSTID..DEF2031.MIG.SRCBDAT &INSTID..DEF2031.MIG.SRCBHDR

&INSTID..DEF2031.MIG.TEXT

Table 5-7 Test Installation Process (TIP) Application

&INSTID..TIP2031.MIG.ELOGKEY &INSTID..TIP2031.MIG.EMIG

&INSTID..TIP2031.MIG.ENTITY &INSTID..TIP2031.MIG.INMIG

&INSTID..TIP2031.MIG.KEYWORD &INSTID..TIP2031.MIG.MIGCNTL

Table 5-4 Base Libraries (Continued)



Option 3 - Create System Installation Jobs1. The Create System Software panel (Figure 5-16) opens. Select option 3 Create System Installation

Jobs.

2. The panel in Figure 5-18 is optional. If it does not appear, proceed to step 3. If the panel does appear, it indicates this system was started but not completed.

Figure 5-18 Create System Installation Jobs

This panel indicates the jobs to install this system have already been generated but not completed.

In this panel, you can choose to:

• Type N and press Enter to complete the system generation in progress. In this case, you proceed to the next step in the process, “Option 4 - Submit System Installation Jobs.”

• Type Y and press Enter to abandon the installation in progress and begin again. In this case, you continue with this process and perform step 3.

3. A panel displays Job Control Card information. Edit if necessary, and press Enter.

4. When the system installation jobs are created, a message appears in the top right corner of the panel in Figure 5-19. You will see either “JOBS CREATED” for a successful creation or an error message for unsuccessful creation.

&INSTID..TIP2031.MIG.MIGXX &INSTID..TIP2031.MIG.RELATE

&INSTID..TIP2031.MIG.RLOGKEY &INSTID..TIP2031.MIG.SOURCE

&INSTID..TIP2031.MIG.SRCBDAT &INSTID..TIP2031.MIG.SRCBHDR

&INSTID..TIP2031.MIG.TEXT

Table 5-7 Test Installation Process (TIP) Application (Continued)


Option 2 - Repository Functions

Option 4 - Submit System Installation Jobs1. From the Create System Software panel, select option 4 Submit System Installation Jobs.

2. A panel displays Job Control Card information. Edit if necessary and press Enter.

3. The panel in Figure 5-19 appears. This panel lists the installation jobs that are ready to be submitted. Submit each job in order from the top down. Enter SUB to submit a job for processing. Confirm that each job posts a “COMPLETED” status before progressing. Enter V or VIEW to display a job.

Figure 5-19 Submit Installation Jobs

4. When all jobs have completed successfully, you have completed the System Functions installation. Press F3 repeatedly to return to the starting panel. You return through the hierarchy of installation windows to the Create System Software panel.

5. Having successfully completed the System Functions settings, you should continue the installation of the software by completing the Option 2 - Repository Functions installation.

Option 2 - Repository FunctionsThis option installs the repository portion of the Enterprise Repository. You must complete option 1 System Functions as shown in Figure 5-2 before proceeding with option 2 Repository Functions.

Figure 5-20 Repository Functions Main Menu



Option 1 - Create Repository1. Select option 1 Create Repository and press Enter.

200.74 Enter the repository ID (name) of the new repository.

Specify up to eight (8) alphanumeric characters per repository name for your AppBuilder repository software. This name will be associated with your AppBuilder base system software which was created during the System Functions installation. (Refer to Chapter 4, “The Host Installation Workbench” for more information.)

In the example used in this document, “repname” is used as a sample repository name and “sysname” is used as a sample system name. Panels displayed on your system will display the repository name you have entered.

200.75 Enter the System ID which will be associated with the new repository [Default: None]

2. Enter X or press End to exit the panel.

3. If a duplicate repository name is detected, the following panel will appear:

Figure 5-21 Create Repository Panel

4. Press Enter to continue with the installation. The newly-created member in this installation will overwrite the existing one.

5. Press End to enter another repository ID. You will return to the panel shown in Figure 5-20.

Create Installation Table

There are three steps you must follow in the Create Repository process.

1. Associate the repository with a system ID, as Figure 5-22 shows.

Warning The Repository ID name cannot be the same as the System ID.



Figure 5-22 Associating a System ID and the new repository

.

Figure 5-23 Create Installation Table Options

.

This panel shows a completion message in the top right corner. Select option 2 to start processing the installation table.

Process Installation Table

Process all releases in order. If you installed the system portion of more than one release, those items will appear in the list. Otherwise, only 2031, shown in Figure 5-24, will appear. Make your selection by typing S or SEL in the Action column next to the desired release.



Figure 5-24 Selecting the Installation Table

Capture Repository Variables

This section allows you to customize variables pertaining to database, job, migration, and user environments at your site. Complete all three steps in order.

1. Choose option 1 to start processing repository variables.

Figure 5-25 Selecting the Capture Repository Variables

The panel in Figure 5-25 is optional. If it does not appear, proceed to “Capture DB2 Information”. If the panel appears, it means this installation was started but not completed.



Figure 5-26 Create Repository Installation Jobs

This panel indicates the jobs to install this repository have already been generated but not completed.

This panel lets you choose:

• Type N and press Enter to complete the repository installation in progress. In this case, you proceed to the next step in the process, “Submit Repository Installation Jobs”.

• Type Y and press Enter to abandon the installation in progress and begin again. In this case, you continue with this process and perform “Capture DB2 Information”.

Capture DB2 Information

After selecting, Option 1—Capture Repository Variables, the panel shown in Figure 5-27 will appear. A total of five panels will appear, each allowing you to customize repository variables. Use this panel to capture information about your DB2 environment.

Figure 5-27 Capture Repository Variables—DB2 environment, panel 1 of 5

----------------------- HOST INSTALLATION WORKBENCH ---------------------- COMMAND ===> CREATE REPOSITORY INSTALLATION JOBS The jobs to install this repository have already been generated but may not have been completed. To complete the installation already in progress, enter N below to return to the Create Repository menu panel and select option 3 (SUBMIT INSTALLATION JOBS). To abandon the installation in progress and begin again, enter Y below. Note that you may encounter difficulty in attempting to run jobs which have been previously run. Do you want to regenerate the installation jobs? (Y/N)==>



Enter the required information appropriate to this installation. Specify all data about your DB2 installation and press Enter.

200.76 DB2 Subsystem ID [Default: DSN]

Enter the subsystem ID where AppBuilder DB2 objects will reside.

200.77 DB2 Object Creator ID [Default: <Installer’s ID>]

Enter the creator or owner ID for all AppBuilder system tables. This ID can either be the installer’s ID or a secondary auth ID.

200.78 DB2 Plan Owner ID [Default: Installer’s ID]

Enter the DB2 Plan Owner ID. This ID can either be the installer’s ID or a secondary auth ID for the installers’ ID. For an upgrade, this must be a different ID than INST1ADM.

200.79 AB DataBase Name [Default: AB203]

Enter the name of the database in which AppBuilder system DB2 objects are to reside.

200.80 DB2 VCAT or Storage Group [Default: None]

Specify whether VCATs or storage groups are used. Enter V for VCAT or S for storage groups. V—you create VSAM manually, S—creates objects in an existing storage groups and VSAM is automatically created.

200.81 DB2 Storage Group Name [Default: None]

If you chose “S” (storage group) in step 200.80, enter the storage group name of an existing storage group you want to use.

200.82 DB2 VCAT Name [Default: None

If you chose “V” (VCAT) in step 200.80, enter the VCAT name.

200.83 Volume ID for DB2 Tablespaces [Default: None]

If you chose VCAT in step 200.80, enter the DASD device where AppBuilder’ DB2 tablespaces are to be stored. The same volume name can be used for DB2 tablespaces and indexspaces.

200.84 Volume ID for DB2 Indexspaces [Default: None]

If you chose VCAT in step 200.80, enter the DASD device where HPS’ DB2 indexspaces are to be stored. The same volume name can be used for DB2 tablespaces and indexspaces.

200.85 DB2 Plan Prefix [Default: A]

Enter the one-character prefix used for AppBuilder system plans. If multiple repositories of AppBuilder will be supported within a DB2 subsystem, each repository must have a unique prefix.

200.86 Owner of Application DB2 Tables [Default: &SYSUID]

Enter the owner ID of the AppBuilder application tables.



200.87 Repository ID [Default: None]

Enter the unique two-character alphabetical suffix used in AppBuilder short name object generation.

200.88 Number of Versions [Default: 1]

Enter the number of versions or partitions within the repository. You may define a minimum of 1 and a maximum of 10 versions per enterprise repository. Additional versions can be installed. Individual versions require additional allocations of DASD as non-DB2 data sets must be allocated for each version.

Capture Data Set Information

Panels 2 and 3 deal with the data set specifications. Panel 2 is shown in Figure 5-28.

Figure 5-28 Capture Repository Variables—Data sets, panel 2 of 5

Enter the required information appropriate to this installation. Specify the information about your data sets and press Enter. The next panel, Figure 5-29, completes the data set specifications.

200.89 Specify the prefix for each of these non-versioned data sets:

Enter a prefix for each of the following. The prefix entered will be used in the data set name at your site. All variables support more than one node.

200.89a Repository Modification [Default: AB1.REP]

Enter the repository modification data set prefix. This qualifier defines data sets which hold infor-mation specific to a given repository. You can also use these data sets to hold software modifica-tions which are to affect only one repository. Enter a maximum of 18 characters.

200.89b User Datasets [Default: AB1.USER]

Enter the user data set prefix. This qualifier defines data sets which hold user application informa-tion for specific repository versions. Enter a maximum of 17 characters.



200.89c VSAM User [Default: AB1.USER]

Enter the VSAM data set prefix. This qualifier defines VSAM data sets which hold user application runtime information for CICS, IMS, and Batch. Enter a maximum of 17 characters.

200.89d Temporary Output [Default: TEMP.NN]

Enter the temporary output data set prefix. This qualifier defines data sets that will be generated by the user while working in the AppBuilder Enterprise Repository. May be a maximum of 10 charac-ters, with the final node being seven (7) characters or less since it is specific to a repository version. The repository version number is concatenated to the final node.

200.89e User-ID (Short-term) [Default: &SYSUID]

Enter the prefix for output user ID data sets which are short-term, to a maximum of 18 characters. This qualifier defines data sets that will be generated by the user while working in the AppBuilder Enterprise Repository. This value must contain the &SYSUID variable since it is specific to each user. For example, you can specify HPS.&SYSUID.

200.89f User-ID (Permanent) [Default: AB1OUT]

Enter the prefix for user output data sets that are permanent or long-term. This qualifier defines data sets that will be generated by the user while working in the AppBuilder Enterprise Repository. May be a maximum of 10 characters.

200.90 Should VIEW Copybooks Include Alignment Bytes? (Y/N) [Default: N]

Specify if VIEW copybooks should include alignment bytes.

Figure 5-29 Capture Repository Variables—Data sets, panel 3 of 5

Enter the required information appropriate to this installation. Specify the units and volume IDs for the permanent, temporary, and VIO data sets. Press Enter.

Note The &SYSUID variable is not allowed to be used as part of the prefix.




200.91 Permanent data sets

Enter the following information for permanent data sets.

200.91a Unit [Default: SYSDA]

Enter the name of the direct access storage device that will store AppBuilder permanent data sets.

200.91b Volume ID Required? [Default: N]

If pool DASD is used (that is, JCL parameter VOL=SER is not used), then enter N and leave Perma-nent Volume ID blank. Otherwise, enter Y and a volume ID.

200.91c Volume ID [Default: None]

Enter the Volume ID.

200.92 Temporary data sets

Enter the following information for temporary data sets.


Enter the name of the direct access storage device that will store AppBuilder temporary data sets.


If pool DASD is used (JCL parameter VOL=SER not used), enter N and leave Temporary Volume ID blank. If DASD must be specified, enter Y and a volume ID.



200.93 VIO data sets

Enter the following information for VIO data sets.


Enter the name of the direct access storage device that will store AppBuilder VIO data sets.


If pool DASD is used (that is, JCL parameter VOL=SER is not used), then enter N and leave VIO Volume ID blank. If DASD must be specified, then enter Y and a Volume ID.



Capture Job Parameters

Enter the JOB Parameters information appropriate to this installation. Then press Enter in the following panel shown in Figure 5-30.



Figure 5-30 Capture Repository Variables—JOB Parameters, panel 4 of 5

200.94 Job Class (CLASS) [Default: 1]

Enter the JCL Job Class used for user-submitted jobs through the repository interface.

200.95 Message Class (MSGCLASS) [Default: A]

Enter the JCL Message Class used for user-submitted jobs through the repository interface.

200.96 Time Parameter (TIME) [Default: None]

Enter the JCL time parameter if required for the job card.

200.97 Priority (PRTY) [Default: 12]

Enter the JCL priority parameter if required for the job card.

200.98 Region size (REGION) [Default: 4M]

Enter the JCL region size parameter if more than 4M is required.

200.99 Default Jobname Suffix Character [Default: M]

Enter a default JCL suffix character.

200.100 Default Job Description [Default: JOB]

Enter a default job description for AppBuilder jobs.

200.101 Overnight Job Class [Default: 1]

Enter the job class used to defer jobs for overnight execution.



200.102 SYSOUT Class for Batch Jobs [Default: *]

Enter SYSOUT class for batch job processing and batch reports.

200.103 Internal Reader Name [Default: INTRDR]

Enter the name of the internal reader if different from the default name.

200.104 Internal Reader Output Class [Default: 1]

Enter the output class for the internal reader.

200.105 Default Printer [Default: None]

Enter default printer ID to be used for printing reports.

200.106 Use Customized Job Card Skeleton [Default: N]

Specify Y or N to use a customized job skeleton.

200.107 Batch JOB Submission Option [Default: Y]

Specify Y to submit jobs automatically or N to save jobs in a data set. The JCL will be saved in data set &USRVQUAL..JCL. To override this, specify the fully qualified data set name in the INI variable called JCLDSN in &REPQUAL..INI(@HPSENV). Y or N for an external scheduling interface.

200.108 Is there an External Scheduling Interface? [Default: N]

Enter the default value only.

Enter the required information appropriate to this installation and press Enter.

Capture Batch File Allocations

The last panel, page five of five, specifies batch file allocations, as shown in Figure 5-31.

Figure 5-31 Capture Repository Variables—Batch File Allocations, panel 5 of 5



Specify the batch file allocations by entering Y or N to include or exclude the specified parameters. Press Enter.

200.109 Include the STEPLIB DD in batch jobs?

Specify Y or N if the STEPLIB DD should be included in batch jobs.

200.110 Include the STEPLIB DD in non-DB2 steps?

Specify Y or N if the STEPLIB DD should be included in non-DB2 steps.

200.111 Include each of the following in STEPLIB:

Specify with Y or N whether to include each of the following in STEPLIB. TSODD is a batch job skeleton.

200.111a DB2 Load Libraries [Default: Y]

Specify if the DB2 load libraries should be in the STEPLIB of TSODD.

200.111b MODQUAL Load Library [Default: Y]

Specify if the AppBuilder modification load libraries should be in the STEPLIB of TSODD.

Capture Migration Information

The next three panels allow you to customize your migration environment. Figure 5-32 defines the general environment.

Figure 5-32 Capture Repository Variables—Migration environment, panel 1 of 3

200.112 Specify the CICS or IMS Transaction ID Option:

Specify the following option, as appropriate. The following are valid values: S-Use Source ID, T-Use Target ID, B-Blank.

200.112a CICS [Default: T]

Specify the CICS transaction ID option.



200.112b IMS [Default: T]

Specify the IMS transaction ID option.

200.113 Default Migration Dataset High Level Qualifier [Default: HPSOUT]

Enter the default migration data set high level qualifier. May be a maximum of 8 characters.

200.114 Analyze Collisions During Import? (Y/N) [Default: Y]

Specify if collisions are analyzed during import.

200.115 Analyze Collisions on SYSTEMID or LONGNAME?(S/L) [Default: L]

Specify if collisions are analyzed on SYTEMID or LONGNAME.

200.116 Process User Exits During Migration? (Y/N) [Default: N]

Specify if user exits are processed during migration.

200.116a If ‘Y’ Enter Name of Optional Exit Rexx Exec [Default: None]

If ‘Y’ is selected, enter the name of the exit REXX.

Figure 5-33 defines default options and user modification capabilities; they require Y or N to specify whether the user can modify the migration options, as shown in Figure 5-33.


200.117 For each of the following enter Y to include the item in a migration or N to exclude it from

migration:

Enter Y or N for the following

200.117a Default Option for ‘Create’ Entities (Y/N) [Default: Y]

Specify Y or N to allow default option for ‘Create’ entities.



200.117b Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the ‘Create’ entities option. ‘

200.117c Default Option for ‘Update’ Entities (Y/N) [Default: Y]

Specify Y or N to allow default option for ‘Update’ entities.

200.117d Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the ‘Update’ entities option.

200.117e Default Option for ‘Delete’ Entities (Y/N) [Default: Y]

Specify Y or N to allow default option for ‘Delete’ entities.

200.117f Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the ‘Delete’ entities option.

200.117g Default Option for Source (Y/N) [Default: Y]

Specify Y or N to allow default option for Source.

200.117h Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the Source option.

200.117i Default Option for Keywords (Y/N) [Default: Y]

Specify Y or N to allow default option for Keywords.

200.117j Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the Keywords option.

200.117k Default Option for Text (Y/N) [Default: Y]

Specify Y or N to allow default option for Text.

200.117l Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the Text option.

Enter the required information appropriate to this installation. Press Enter.

The last page defines whether the user can modify the import step, rebuild analyzer, rebuild prepare, and rebuild install, as shown in Figure 5-34.




200.118 Enter Y to include the following steps in MIGRATE method processing or N to exclude them:

Enter Y or N for the following.

200.118a Include IMPORT Step? (Y/N) [Default: N]

Specify Y or N to include the IMPORT step.

200.118b Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include IMPORT step option.

200.118c Include REBUILD Analyzer? (Y/N) [Default: N]

Specify Y or N to include the REBUILD Analyzer.

200.118d Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Analyzer option.

200.118e Include REBUILD Prepare? (Y/N) [Default: Y]

Specify Y or N to include the REBUILD Prepare.

200.118f Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Prepare option.

200.118g Include REBUILD Install? (Y/N) [Default: Y]

Specify Y or N to include the REBUILD Install.

200.118h Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Install option.

200.118i Include REBUILD Export? (Y/N) [Default: N]

Specify Y or N to include the REBUILD Export.

200.118j Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Export option.



Enter the required information appropriate to this installation. Press Enter.

Capture User Information

The last two panels define your user environment. (Two panels appears for each version you are asked to create.) Figure 5-35 shows the application DB2 environment, configuration units, and begins the list of user libraries for component preparations.

Figure 5-35 Capture Repository Variables—User environment, panel 1 of 2

200.119 Application DB2 environment

200.119a Support DB2 Packages? (V/N/P) [Default: N]

Specify V or P to support DB2 packages. N indicates that packages are not supported. V indicates DB2 packages will be supported for all the projects within a repository version. P indicates DB2 packages will be supported per project within a repository version. Please refer to the Enterprise Administration Guide for more information on DB2 package support.

200.119b If V or P, specify Collection ID [Default: None]

If using packages, specify the default Collection ID for this repository version.

200.119c If V or P, specify Owner ID [Default: None]

If using packages, specify the default Owner ID for this repository version.

200.119d If V or P, specify Qualifier ID [Default: None]

If using packages, specify the default Qualifier ID for this repository version.

200.119e If V or P, specify Plan Name [Default: None]

If using packages, specify the default Plan Name for this repository version.



200.119f If V or P, specify E if a Package List is Required or W if the Wildcard (*) is Supported

(E/W) [Default: W]

If you use Packages, specify E to require an explicit package list or specify W to support the asterisk (*) for wildcards for this repository version.

200.119g Perform GRANT as part of Prepare Method? (Y/N) [Default: Y]

Specify Y or N to perform GRANT as a part of the Prepare method.

200.119h Use Configuration Units for Preparation? (Y/N) [Default: N]

Specify Y or N to use configuration units for preparation.

200.120 Optional User Libraries for Component Prepares

Enter the following library names.

200.120a NCAL Batch Library [Default: None]

Define the NCAL batch library.

200.120b NCAL CICS Library [Default: None]

Define the NCAL CICS library.

200.120c NCAL IMS Library [Default: None]

Define the NCAL IMS library.

Figure 5-36 completes the list of user libraries for component preparations.

Figure 5-36 Capture Repository Variables—User environment, panel 2 of 2



Optional User Libraries for Component Prepares200.120d Other NCAL Library [Default: None]

Define the other NCAL batch library.

200.120e Batch Load Library [Default: None]

Define the batch load library.

200.120f CICS Load Library [Default: None]

Define the CICS load library.

200.120g IMS Load Library [Default: None]

Define the IMS load library.

200.120h Other Load Library [Default: None]

Define the other load library.

200.120i ASM Copylib [Default: None]

Define the ASM copylib.

200.120j COBOL Copylib [Default: None]

Define the COBOL copylib.

200.120k C Copylib [Default: None]

Define the C language copylib.

200.120l PL/I Copylib [Default: None]

Define the PL/I copylib.

200.120m ASM DCLGEN [Default: None]

Define the ASM DCLGEN.

200.120n COBOL DCLGEN [Default: None]

Define the COBOL DCLGEN.

200.120o C DCLGEN [Default: None]

Define the C Language DCLGEN

200.120p PL/I DCLGEN [Default: None]

Define the PL/I DCLGEN.

The two panels defining the user environment complete the series of ten panels that capture repository variables. At the end of series Figure 5-37 appears. Press Enter to continue the installation.



Figure 5-37 Variables Captured

Create Repository Installation Jobs

Continuing the installation, you return to the panel in Figure 5-23 to create installation jobs. Initiate this action by selecting option 2 in the panel. A “JOBS CREATED” message should appear in the top right corner when the action has completed.

If the installation software detects existing DB2 data sets, the panel in Figure 5-38 appears.

Figure 5-38 Drop Database



Submit Repository Installation Jobs

Continuing the installation, you return to the panel in Figure 5-16 to submit installation jobs. Initiate this action by selecting option 4. Figure 5-39 appears.

Figure 5-39 Submit Installation Jobs

From this panel, you can either view or submit the jobs. Type V or VIEW to examine the results of the job creation for correctness. When ready, type SUB to submit it for processing. To modify a job, split the screen and edit. After saving the member, return to the “Submit Installation Jobs” panel to submit the job.

The Status column will display either one of two messages for submitted jobs—‘SUBMITTED’ (in process) or ‘COMPLETED’. Submit all jobs in order.

The jobs and their purposes are:

• REPJOB— handle all the non-DB2 work, such as allocating repository data sets. This job creates the following data sets:

In Table 5-8 &REPQUAL is the value defined in Figure 5-26 for the prefix of the Repository Modification data sets.

In Table 5-9 there can be more than one set of user libraries if the Number of Versions was set to more than one. Refer to Figure 5-19 and the panel entry for Number of Versions. &USRVQUAL is the qualifier

Note Ensure that each job completes before submitting the next one.

Table 5-8 Repository modification libraries

&REPQUAL..CGTABLE &REPQUAL..CLIST

&REPQUAL..DBRMLIB &REPQUAL..FTSKELS

&REPQUAL..INI &REPQUAL..LOADLIB

&REPQUAL..MSGS &REPQUAL..OBJ

&REPQUAL..PANELS &REPQUAL..SKELS



used for AppBuilder user level data sets that are versioned. The value for &USRVQUAL is contained in &REPQUAL..INI(@USRENVn), where n is the version number of the repository.

• DB2OBJ—create the DB2 objects. This job creates the following data set: &USRVQUAL.TRAN.

• DB2BIND—bind the DB2 plans

When you finish submitting all jobs and the status of each is “COMPLETED”, press F3 until the panel in Figure 5-33 reappears.

Activate Repository

Figure 5-40 shows the screen appearing next. Choose option 3 to activate the new repository.

Figure 5-40 Create Repository choices appearing after creating an installation table

Table 5-9 User libraries

&USRVQUAL..APPLDBRM &USRVQUAL..CGTABLE

&USRVQUAL..COPYASM &USRVQUAL..COPYC

&USRVQUAL..COPYCOB &USRVQUAL..COPYPL1

&USRVQUAL..DCLGNC &USRVQUAL..DCLGNCOB

&USRVQUAL..DCLGNPL1 &USRVQUAL..JCL

&USRVQUAL..LOADBS &USRVQUAL..NCALBS

&USRVQUAL..SETC &USRVQUAL..SETCOB

&USRVQUAL..SETERR &USRVQUAL..SETPL1

&USRVQUAL..SETREF &USRVQUAL..VIEWASM

&USRVQUAL..VIEWASMA &USRVQUAL..VIEWC

&USRVQUAL..VIEWCA &USRVQUAL..VIEWCOB

&USRVQUAL..VIEWCOBA &USRVQUAL..VIEWPL1

&USRVQUAL..VIEWPL1A

--------------------------- HOST INSTALLATION WORKBENCH ---------------------COMMAND ===> CREATE REPOSITORY repname OPTION ===> 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT Enter END Command to exit. Press ENTER to continue.


Postinstallation Notes

Wait for the activation of the repository to complete. A confirmation message in the top right corner notifies you when it is complete.

Postinstallation NotesPerform the following steps to complete and verify the successful installation of the AppBuilder REL 2.0.3.1 Enterprise Repository.

1. Edit your ISPF Primary Option Menu panel to allow entry to the Enterprise Repository. Replace &REPQUAL, &MODQUAL, &BASEQUAL, and &VSMQUAL with the qualifiers shown in Figure 5-5 and Figure 5-28. Replace &OCLASS with the output class to be used for SYSOUT data sets to be allocated during a TSO session. For an example of where to edit these items, see the sample ISR@PRIM in Figure 5-41.

2. Copy the repository CLIST from &REPQUAL..CLIST to a data set included in the SYSPROC concatenation of AppBuilder users’ TSO sessions.

3. Edit the member HPSALLOC in &REPQUAL..CLIST to remove unwanted data sets or add more data sets to the ISPF library concatenations. These concatenations are in effect for AppBuilder TSO sessions for all users and should not contain any data sets that are exclusively for the AppBuilder installer’s TSO session. It also contains the ISPF command to display an ISPF main panel. If this is not used at your location, edit HPSALLOC with the appropriate command. Also, you will need to add the following to the ISPTLIB concatenation:

‘&GRPQUAL..&USRQUAL..TABLES’

4. At the TSO Ready prompt, enter the name of the repository CLIST to set up your TSO session to use AppBuilder and to allow you to invoke AppBuilder software from a primary ISPF panel (ISR@PRIM).

5. Make sure to set your PF (function) keys to 24 before invoking AppBuilder. After you invoke the AppBuilder option from the primary ISPF panel, select option 1 to invoke the AppBuilder Enterprise Repository from the AppBuilder Main Option panel.

6. A window will appear with a list of projects and corresponding versions that your ID can access. The installer’s ID will have access to the HPS and ADM projects. Select the ADM project for version A.

7. Next to the Users entity, type LE (List Entities) to list the users in the repository. At this point only the installer’s ID is listed. Type ME (Maintain Entity) next to the installer’s ID to update the job accounting information for your site. After entering required information, press F3 to save and return. Be certain to update the installer’s ID for each of the versions listed.

8. Next to the Groups entity, type ADDE (Add Entity) to add the TIP (Test Installation Process) group to the repository. After entering required information, press F3 to save and return.

9. Next to the Projects entity, type ADDE to add TIP project to the repository. Select the "HPS Model" for the type field. After entering the required information, press F3 to save and return.

10. Next to the Groups entity, type LE to list groups. Next to the TIP group, type ADDR to add the installer’s ID to the TIP group. The Relation type will be option 5 “Has-As-A-Member User” and

Note If the&ZPLACE variable is used, make sure it is initialized with a valid value.

Note Refer to the @HPSENV INI file in Appendix A for the values of these two variables.

Note You need to repeat steps 6 through 13 for each version of the repository.



press Enter. Set “User Authority Level” to 1 for Project Leader. After entering required information, press F3 to save and return.

11. Next to the Groups entity, type LE to list groups. Next to the TIP group type ADDR (Add Relationship) to add the TIP project to the TIP group. The Relation type will be option 4 “Has Project” and press Enter. Set Method Name and Scope to *, and set Scope Mode to 1 for include. After entering required information, press F3 to save and return.

12. Migrate TIP:

a. Within the Enterprise Repository, type PROJECTS at the command line, and select TIP for version 1.

b. Next to the Migration entity, type ADDE to create a migration entity for TIP (TIP is the application that verifies installations). For the migration data set prefix, enter &INSTID..TIP2031, where &INSTID is the installer’s User ID. After entering required information, press F3 to save and return.

c. Next to the Migration entity type LE to list the migration entities. Next to the TIP entity, type ANALYZE. When the ANALYZE finishes successfully, type IMPORT next to the TIP entity. Type RES next to the TIP entity to look at the ANALYZE and IMPORT messages and counts.

13. Migrate Default Repository:

a. Within the Enterprise Repository, type PROJECTS at the command line and select HPS for version 1.

b. Next to the Migration entity, type ADDE to create a migration entity for Default Repository. For the migration data set prefix, enter &INSTID.DEF2031, where &INSTID is the installer’s TSO User ID. After entering required information, press F3 to save and return.

c. Next to the Migration entity, type LE to list the migration entities. Next to the Default Repository entity, type ANALYZE. When the ANALYZE finishes successfully, type IMPORT next to the Default Repository entity. Type RES next to the Default Repository entity to look at the ANALYZE and IMPORT messages and counts.

14. Add a new INI variable to @MVSENV to support the DBCS upload/download process. Go to the BASEQUAL.INI data set and edit the @MVSENV member. Add the following lines in the (NLS) section:

;DESCRIPTION: Use DBCS (Double Byte Character Set) on the Host.;Validation:Y or N;Default=YDBCS=Y



Figure 5-41 Main ISPF/PDF Option panel for sample ISR@PRIM%---------------------- ISPF/PDF PRIMARY OPTION MENU ---------------------------

%OPTION ===>_ZCMD +

% USERID -&ZUSER

% 0 +ISPF PARMS - Specify terminal and user parameters %TIME -&ZTIME

% 1 +BROWSE - Display source data or output listings %TERMINAL-&ZTERM

% 2 +EDIT - Create or change source data %PF KEYS -&ZKEYS

% 3 +UTILITIES - Perform utilitiy functions %DATE -&ZDATE

% 4 +FOREGROUND - Compile, assemble, link edit or debug %JULIAN -&ZJDATE

% 5 +File-Aid - File-Aid Data Handling Utility

% 6 +COMMAND - Enter TSO command or CLIST

% 7 +DIALOG TEST - Perform dialog testing

%

% A +APPBUILDER - APPBUILDER% D +DB2 - Database 2 Management Facility and Tools

% F +FORTE - PC File Transfer Program

% P +PANVALET - Browse, edit and utilities

% R +SARSPF - Retrieve SYSOUT

% S +SDSF - SPOOL Display and Search Facility

%

% T +TUTORIAL - Display information about ISPF/PDF

% X +EXIT - Terminate ISPF using log and list defaults

%

+Enter%END+command to terminate ISPF.

)INIT

.HELP = ISR00003

&ZPRIM = YES /* Always a primary option menu */

&ZHTOP = ISR00003 /* Tutorial Table of Contents */

&ZHINDEX = ISR91000 /* Tutorial Index - 1st page */

VPUT (ZHTOP,ZHINDEX) PROFILE

VGET (ZPLACE) PROFILE

&PLACE = &ZPLACE

IF (&ZPLACE = ' ')

&ZPLACE = 'BOTTOM'

)PROC

&ZQ = &Z

IF (&ZCMD ™= ' ')

&ZQ = TRUNC(&ZCMD,'.')

IF (&ZQ = ' ')

.MSG = ISRU000

&ZSEL = TRANS( &ZQ

0,'panel(ispopta)'

1,'pgm(isrbro) parm(isrbro01)'

2,'pgm(isredit) parm(p,isredm01)'

3,'panel(isrutil)'

4,'panel(isrfpa)'

5,'PANEL(DXSMAIN) NEWAPPL(DXP)'

6,'pgm(isrptc)'

7,'pgm(ispyxdr) nocheck'

H,'CMD(%HMFISPF &REPQUAL &MODQUAL &BASEQUAL + &VSMQUAL &ZPLACE N &OCLASS) NEWAPPL(HRIS) NOCHECK' P,'PGM(PSPILINI) NOCHECK'

D,'panel(db2@prim)'

R,'PGM(SARSPF) PARM(MV.SAR) NEWAPPL(SAR)

Edit with values for your site, where &OCLASS is the output class to be used for SYSOUT data sets to be allocated during this session

Item to edit


Installing MVS Migration Server

Installing MVS Migration ServerFollow the procedures outlined in the steps that follow to install the migration server.

STEP 1: INI File

Edit the @SERVER ini file (found in the BASEQUAL level) with the following instructions found below. There will be variable values that will not be answered because they are for future use. In this case, the variable is noted below but the comment will state: "Do not change".

(SKELTON)DSNAME=

Enter the name of the data set that will contain the TCP/IP JCL. A recommended name would be MODQUAL.TCPIP.JCL but it is not required.

(FTPLOCATION)ADDRESS=

Enter the IP address that your site uses for FTP.

(MIGRATION)MIG_LONGNAME=

Enter the longname for the TCPIP import method. This will be the qualifer that will be used to create a migration entity during the import to the Host. For example, TCP_DFT_MIG can be the value and then when the import begins, a migration entity will be created like TCP_DFT_MIG_nnnnnn, where nnnnn = an assigned number by the system.

(TCPIP) PREPORT=

Do not change.

TCPQUAL=

Do not change.

PORT=

Enter the TCP/IP port number that will be used for the upload and download process to the Host.

CODEPAGE=

Enter the Mainframe code page for your site. This value would be the same value found in the @MVSENV ini file for the variable MFCODEPG in the NLS section.

(SRVDB2)QUALIFIER=

Enter the DB2 qualifier for your DB2 tables. This value would be the same value found in the @HPSENV ini file for the variable INST1ADM in the DB2 section.

DATABASE=

Enter the name of the DB2 database that the Host repository uses. This value would be the same value found in the @INSTENV ini file for the variable DATABASE in the DB2 section.

DB2MEDIA=

Enter "S" if your site uses DB2 storage groups or "V" if your site uses DB2 volume catalogs. This value would be the same value found in the @INSTENV ini file for the variable DB2MEDIA in the DB2 section.



DB2VCAT=

Enter the DB2 Volume catalog name if you have entered "V" for the DB2MEDIA variable. This value would be the same value found in the @INSTENV ini file for the variable DB2VCAT in the DB2 section.

DDLSIZE=

Do not change.

DB2STOG=

Enter the DB2 storage group if you have entered "S" for the DB2MEDIA variable. This value would be the same value found in the @INSTENV ini file for the variable DB2STOG in the DB2 section.

(TRACE)LOGLEVEL=0

Do not change.

USEPASS=N

Do not change.

(FILES)PREPPRIQTY = 5

Do not change.

PREPSECQTY = 10

Do not change.

DIRBLK = 10

Do not change.

REC290BK = 31320Do not change.

(Place your Repository Name here)

Place the name of the Repository that you will be perfoming an upload/download operation on between the parentheses. This value would be the same value found in the @HPSENV ini file for the variable REPNAME in the REPOSITORY section.

BASEQUAL=

Enter the BASE qualifier of the Repository.

MODQUAL=

Enter the MOD qualifier of the Repository.

REPQUAL=

Enter the REP qualifier of the Repository.

STEP 2: CRSRVJCL Execution

Access the AppBuilder repository only after completion of STEP 1: INI File. Go to the ADM project of any version (except version “A”) to find a selection of Management Services.

Enter the command CRSRVJCL on the line next to Management Services. After entering the CRSRVJCL command, a panel will appear entitled "Method Handler-Create JCL panel", shown in Figure 5-42.



Figure 5-42 Method Handler Panel

This EXEC creates the library defined by the @SERVER INI variable SKELTON.DSNAME. This library contains the following members and their functions:

• SERVER – JCL to start the Server

• JOBHEAD - JOBCARD information used by the Method Handler

• REPNAME – the member name equals the value of the REPNAME variable in the @SERVER INI

This is the Method Handler and contains JCL to run the IMPORT Migration method.

For entries for the panel, follow the instructions below:

1. On the line entitled Server ini dataset name......, enter the INI data set name that contains the @SERVER member that you performed an edit on in Step 1, for example, AB.BASE.INI. If you do not enter a valid name, the screen will not continue with the process.

2. For the section entitled Select Migration Server:

• Enter any character for the line entitled Create Server JCL.

• Enter any character for the line entitled Bypass DB2 if Tables/Views already exist.

The line Bypass DB2 if Tables/Views already exist. will be removed in the next release. If a character was not placed on this line and the Enter key is hit, an attempt will be made to create the DB2 tables for the three tables that are used by the Migration Server. The three tables that the Migration Server uses are: JOB_RESFILE, JOB_STATUS, and MIG_SEEDS. They were created earlier in the process and you do not need to create them again.

Warning If the command CRRPJCL (which creates the Preparation Server) is executed, then the JOBHEAD and RENAME members will be recreated. This will not cause any problems because the Migration Server and Preparation Server use these two members.


Installing Enterprise Preparation Server

Special Notes for Migration Server

The automated migration system runs outside of AppBuilder. In order to turn trace ON, go to the TRACE section and set LOGLEVEL = 1; to turn trace OFF set LOGLEVEL= 0.

The member SERVER exists within the SKELTON.DSNAME data set. Within that member, the JCL allocates a user data set in the ISPTLIB DD name concatenation. This user data set name will start with the INSTALLID and should be the first data set in the concatenation. If you do not prefer to use this name, you can change it to any ISPF table data set that has write access by the user community. The data set must exist or the server will fail.

The DOWNLOAD and UPLOAD methods that exist on the migration object are not to be used outside of the Migration Server. (These are internal methods and will not be supported in future releases.)

When the server is cancelled in SDSF, the TCPIP socket associated with the server may hang for several minutes before releasing. This restricts the startup of the server until the socket frees. The following TCPIP error message will appear:

EZY4098E Address already in use (EADDRINUSE)

Installing Enterprise Preparation ServerOne of the features of AppBuilder is the ability to prepare entities on the mainframe while keeping the entities on the workstation platform. You can create AppBuilder applications with a workgroup repository and from the Construction Workbench you can generate the necessary information, transfer this data to the mainframe and initiate a job to perform the preparation. This is remote preparation to the mainframe and is made possible by the Enterprise Preparation Server. This does NOT provide the ability to initiate a prepare on the mainframe using data stored in an enterprise repository.

Installation of the Enterprise Preparation Server for remote preparation to a mainframe includes these procedures:

• Updating Server Repository @SERVER INI

• Adding an Additional Repository to the Server

• Starting the Server

Throughout these procedures, these terms are used:

• server repository – the repository where the server parameters reside

• additional repository – an additional repository that can be prepared against by the server

This topic also includes the @SERVER INI Example

As in a typical mainframe prepare, the results contain several files including the compiler listing and link listing. Due to the size of these files, an INI setting was created to control these files. The variable SNDLIST in section REMPREP in the @USRENVn is defaulted to "N", so that these files are not sent. If you would like these files sent, set the INI setting to 'Y' for the repository and version to which you are preparing.



Updating Server Repository @SERVER INIThis process is mandatory for new and existing migration servers.

STEP 1: Edit the @SERVER ini file

Edit the @SERVER ini file (found in the BASEQUAL level) with the following instructions found below:

(TCPIP) PREPORT=

Enter the TCP/IP port number that will be used for the Remote Prepare process to the Host. This must be a different port from the Migration Server.

STEP 2: Execute CRRPJCL to create Server and Method Handler JCL

After completion of STEP 1: Add the server repository to the @SERVER section, startup AppBuilder with the current repository. Go to the ADM project of any version (except version A) and enter the command CRRPJCL next to the Management Services option. The CRRPJCL command creates the member RPSERV, used to start the server. The CRRPJCL command also creates a member named JOBHEAD and a member with a name of the REPNAME value from @HPSENV INI. These members are used to submit the Method Handler job. These members are put in the skeleton data set name SKELTON.DSNAME from the @SERVER INI file.

Starting the ServerOpen the skeleton data set name SKELTON.DSNAME and select RPSERV. Submit the job. The server should be running on the specified port. To turn on logging, use the TRACE.LOGLEVEL option in the @SERVER ini.

Adding an Additional Repository to the ServerThis section is optional and can be performed if you have another repository that will be accessed by the Preparation Server. If this situation does not exist, then omit this section and continue on with the installation.

STEP 1: Add the new repository to the @SERVER

Make a new section in the server repository @SERVER INI with the same name as the repository name REPOSITORY.REPNAME in the @HPSENV INI from the additional repository. In that new section, copy the BASEQUAL, MODQUAL, and REPQUAL values from the QUALIFIERS section of the @HPSENV INI from the additional repository.

Warning If you don't set up the Migration Server, but want to set up the Remote Preparation Server, you will have to update the @SERVER ini file as explained in the Migration Server section.



STEP 2: Update the Additional repository @SERVER ini

Edit the @SERVER ini associated with the additional repository. Change the SKELTON.DSNAME variable to the value of the SKELTON.DSNAME variable of the server repository. The REPNAME member will then be placed in the JCL library of the server repository. REPNAME will equal the name of the additional repository name.

STEP 3: Execute CRRPJCL to create Method Handler JCL

After completion of STEP 2: Startup AppBuilder in the additional repository. Go to the ADM project of any version (except version A) and enter the command CRRPJCL next to the Management Services option. The CRRPJCL command creates the member RPSERV, used to start the server. The CRRPJCL command creates the RPSERV and JOBHEAD members, plus a member with the name equal to the additional repository name. These members are placed in the JCL library with the name equal to SKELTON.DSNAME from the @SERVER ini within the server repository. These members are used to submit the Method Handler job.

STEP 4: Execute CRRPJCL from the Server Repository

This step is performed to place the correct version of RPSERV and JOBHEAD into the JCL library of the server repository. This step will be eliminated in a future release but it is necessary to have the correct members before starting the Preparation Server.

After completion of Step 3, start up Appbuilder from the server repository. Go to the ADM project of any version (except version A) and enter the command CRRPJCL next to the Management Services option.

After completion of the CRRPJCL command the following members should be JCL library of the server repository:

• SERVER - used to start the Migration Server (see Migration section from above)

• RPSERV - used to start the Preparation server

• JOBHEAD - used for JOBCARD information

• REPNAME - this will have the name of the repository name that will be used in the Migration and Preparation processes. There could be as many REPNAMEs as there are repositories that you want to access.

@SERVER INI Example…(REPNAME);Description: Prefix for BASE level data sets;Validation : DSN qualifiers with a max length of 17 ; Default: None.BASEQUAL=HPSLE.BASE501;;Description: Prefix for MOD level data sets;Validation : DSN qualifiers with a max length of 17 ; Default: None.MODQUAL=HPSLE.MOD54102;


Installation Verification Using TIP

;Description: Prefix for REPOSITORY level data sets;Validation : DSN qualifiers with a max length of 17 ; Default: None.REPQUAL=HPSLE.REP54102(REPNAME2);Description: Prefix for BASE level data sets;Validation : DSN qualifiers with a max length of 17 ; Default: None.BASEQUAL=HPSLE.BASE502…(REPNAME3);Description: Prefix for BASE level data sets;Validation : DSN qualifiers with a max length of 17 ; Default: None.BASEQUAL=HPSLE.BASE503

•

Installation Verification Using TIP1. Use the Migration Server to Download the TIP application to a Personal Repository on the

workstation and logoff the Mainframe before starting the Download process.

a. Login to the Personal Repository using Freeway Explorer.

b. Select Tools>Download from the menu.

c. You will be prompted for your userID and password. This is your userID and password for the HOST, which may differ from the one on your PC.

d. From the download window, use the Query menu to query the TIP_FUNCTION from the host.

e. Once queried, you can select objects in the query window and click the "Load" button to put them into the download window.

f. Now that you have all the objects you want to download in the download window press the download button to begin.

From here, the LRE will make the request to the Host Migration Server to export and download the objects to the LRE.

2. Prepare the TIP application:

a. Invoke AppBuilder Preparation Workbench on the workstation.

b. Select Rule as the object type and select Query push button. Select any rule from the Object instance list box, select Prepare Action and then Arguments. The Rule Preparation Arguments window appears. Make sure Prepare mainframe Rules on PC is not selected. Save and cancel.

c. Select Function as the object type and select Query. Select Object instance of TIP_FUNCTION, Super Prepare action and Apply Action.

d. Make sure the following objects prepared successfully by selecting Open status in the Window pulldown menu:

• TIP_PC_RULE

• TIP_PC_WINDOW

• TIP_PC_C_COMP

• TIP_DRIVER_RULE



• TIP_DRIVER_WINDOW

• TIP_FUNCTION

3. Execute the TIP application:

a. Invoke AppBuilder Execution Workbench on the workstation.

b. A menu is displayed with the TIP Function pulldown. Select the TIP Function pulldown menu and select TIP Cooperative Process. A window with push buttons is displayed. Click only on the PC NESTED and C COMP push buttons to verify. Use the mainframe push buttons to verify mainframe/CICS execution when the AppBuilder CICS Online product has been installed on the host.

4. Verification of AppBuilder Enterprise Repository (AB2031) installation is now complete.

Note You will observe several objects in addition to those listed above, but ignore them because they are mainframe objects.




CHAPTER

6 INSTALLING BATCH PREPARATION WORKBENCH


The information in this section describes the detailed requirements and procedures for installing a Batch Preparation Workbench.

PrerequisitesThe following AppBuilder software is required prior to the installation of this software.

• AppBuilder REL 2.0.3.1 Host Installation Workbench

• AppBuilder REL 2.0.3.1 Enterprise Repository

• Refer to Chapter E, “Hardware and Software Checklists” and Chapter H, “Batch Preparation Workbench Customization Worksheets” to prepare for this installation.



• Volume Serial No. xxxxxx



Installation Notes

Installation NotesThe following list shows the options and panels you will use when installing this software.

Option 1—System Functions

Apply System Upgrade

Update System Software

Option 1 Unload Installation Data Sets

Option 2 Continue

Create System Upgrade Jobs

Regenerate/Edit/Submit Installation Jobs

SYSJOB2—Set Tape Backup Parameters

SYSJOB5—Confirm Update Job Submission

Option 2—Repository Functions

Apply Repository Upgrade

Option 1 Create Installation Table

Upgrade Repository

Option 2 Process Installation Table

Selecting an Installation Table to Process

Create Repository Upgrade Job

Batch environment Variables


Option 3 Activate Repository

Installing the Batch Preparation Workbench Software

The Host Installation Workbench Functions panel (Figure 6-1) is the starting point for installing the system and repository portions of AppBuilder software. You must complete the system functions before continuing with the repository functions. However, you can complete the system function (option 1) portion of multiple pieces of AppBuilder software before starting the repository functions (option 2) for the software.

1. System Functions—see Option 1 - System Functions

2. Repository Functions—see Option 2 - Repository Functions.

6-2 Installing Batch Preparation Workbench

Option 1 - System Functions

Figure 6-1 Workbench Functions

Option 1 - System Functions1. After you enter 1 in the option line of the Workbench Functions panel shown in Figure 6-1, the

System Functions panel in Figure 6-2 appears.

2. Enter 2 Apply System Upgrade on the option line to begin the system installation portion of this software.

3. Enter the ID of the system where the software will be installed. Examples are shown in this document as “sysname.”

4. Press Enter to advance to the selected panel, or enter X or press END to exit the panel.

5. If you press Enter, the Apply System Upgrade panel in Figure 6-3 appears.

Figure 6-2 Host Installation Workbench System Functions




1. Enter specific information about the software and tape you are installing. This information is used to unload the installation data sets required for the system installation.

2. In option 1, Unload Installation data sets, enter the data needed to create the unload JCL.

3. In option 2, Continue, activate the actual unloading of the data from tape to your system.

Figure 6-3 Workbench Update System Software

4. Enter the following items on the Update Software panel (Figure 6-3).

Release: Enter SVB2031, which is the installation code for this software.

Unit: Enter the name of the tape unit from which this software will be installed.

Tape Vol Serial Number: Enter the tape volume serial number. The volume serial number is a unique six-digit number assigned by BluePhoenix Solutions to the tape. The number can be found on the packing list for this software, and is also located on the tape itself.

5. Enter 1, Unload installation data sets, in the option line after entering values for the above three items in step 6. This option puts you in edit mode for the unload job. Review the JCL and submit it. Press F3, and check the output of execution. Confirm the output contains the following data sets:

• &instqual..SVB2031.CNTL

• &instqual..SVB2031.ICLIST

• &instqual..SVB2031.IPANELS

• &instqual..SVB2031.ISKELS

where &instqual is the installation data set qualifier for your site. This value was entered in step 200.1 during your AppBuilder REL 2.0.3.1 Enterprise Repository installation.

6. Enter 2, Continue, in the option line after confirming the above data sets were created correctly. This option allows you to continue the system software installation. Press Enter to continue to the next panel.



7. If this is the first time the system portion of this software has been installed, the Regenerate/Edit/Submit Installation Jobs panel in Figure 6-4 appears. Otherwise, a panel appears notifying you the installation tables to update this system have already been generated. You can either enter N to continue with the current installation or Y to recreate the table and begin the installation again. This action resets the status of the jobs but does not regenerate them. The status is reported in the Status column in the Regenerate/Edit/Submit Installation Jobs panel.

8. The panel shown in Figure 6-4 controls the unloading of data sets. Jobs must be submitted in order (beginning with SYSJOB1). Each job should complete successfully before submitting the next. SYSJOB1, SYSJOB4, and SYSJOB5 must be performed—all other jobs are optional.

Valid actions are regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the software. You can monitor each jobs progress in the Status column. The status of a job may be [blank] — no activity is occurring, SUBMITTED — a job is in progress, or COMPLETED — a job is completed.

If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status column. Press Enter to clear this message and continue

Figure 6-4 Update System Software - Regenerate/Edit/Submit

• SYSJOB1—Unload the rest of the tape

Note When a job has completed successfully, press the Enter key twice to refresh the status from SUBMITTED to COMPLETED.

Note Backups are not required; however, they are recommended.

----------------------- HOST INSTALLATION WORKBENCH ---------------------- COMMAND ===> PF3-END PF7-UP PF8-DOWN UPDATE SYSTEM SOFTWARE - REGENERATE/EDIT/SUBMIT INSTALLATION JOBS System ID: sysname Release: SVB2031 Type REGEN in the Action column to regenerate a job. Type V in the Action column to view a job. Type SUB in the Action column to submit a job. Action Jobname Description Status ______ SYSJOB1 UNLOAD REST OF TAPE ______ SYSJOB2 BACKUP DATASETS TO TAPE ______ SYSJOB3 BACKUP DATASETS TO DASD ______ SYSJOB4 LINK LOAD MODULES ______ SYSJOB5 COPY TO SYSTEM DATASETS ______ SYSJOB6 RESTORE DATASETS FROM TAPE ______ SYSJOB7 RESTORE DATASETS FROM DASD



Proceed with the unload process. You can view, regenerate, or submit the job for execution. The fol-lowing data sets are created by SYSJOB1:

• SYSJOB2—Backup data sets to tape

When you regenerate or submit SYSJOB2, the “Set Tape Backup Parameters” panel appears. Specify the tape unit type (such as CART), the volume serial number of your tape (if desired), and the num-ber of days that you want the taped data to be retained. Enter the required tape backup information, and press Enter to activate these parameters. The backup process executes, and you return to the Regenerate/Edit/Submit Installation Jobs panel.

• SYSJOB3—Backup data sets to DASD

This job to sends your backup to DASD.

• SYSJOB4—Link load modules

When the data sets are unloaded successfully, perform the link of the load modules.

• SYSJOB5—Copy to system data sets

When the load modules are linked successfully, copy the modules to the system data sets. If you have not performed a backup, the “Update System Software–Confirm Update Job Submission” panel alerts you. If a backup is not made, you will not be able to backout this software. A backup option will not be available later in this installation-any subsequent backup would have to be done manu-ally.

After SYSJOB5 completes, the following new data sets are created or updated.

• System data set libraries:

• &BASEQUAL is the system data set qualifier for AppBuilder data sets.

• Maintenance libraries

• SYSJOB6—Restore data sets from tape

The restore data sets process can be used to recover (or restore) system software data sets from the tape or DASD backups made in SYSJOB2 or SYSJOB3 in the event that the outcome of the system software upgrade is unsatisfactory. Of course, the restore process can be used only if SYSJOB2 or

Table 6-1 Data sets created by SYSJOB1

&BASEQUAL.SVB2031.LKBTEC &BASEQUAL.SVB2031.OBJ

&BASEQUAL.SVB2031.LKBTEN &BASEQUAL.SVB2031.PLKOBJ

&BASEQUAL.SVB2031.LKBTNC &BASEQUAL.SVB2031.SAMPLE

&BASEQUAL.SVB2031.LKBTUC &BASEQUAL.SVB2031.PRELINK

&BASEQUAL.SVB2031.LOADBT

Table 6-2 System Data Set Libraries from SYSJOB5

&BASEQUAL..LKBTEC &BASEQUAL.SVB2031.PLKOBJ

&BASEQUAL..LKBTEN &BASEQUAL.SVB2031.PRELINK

&BASEQUAL..LKBTUC &BASEQUAL..OBJ

&BASEQUAL..LOADBT &BASEQUAL..SAMPLE

Table 6-3 Maintenance libraries from SYSJOB5

&MODQUAL..LOADBT

Note &MODQUAL is the maintenance data set qualifier for AppBuilder data sets.



SYSJOB3 was run. To restore data sets from a tape backup, select SYSJOB6. To restore data sets from DASD backups select SYSJOB7. The restore process does not affect any repository data sets. If the repository installation was also completed, any updated repository information must be manually restored and any DB2 plans rebound using the restored software level.

We recommend that you use the View or REGAN action on SYSJOB6 or SYSJOB7 at this time in order to create the job for later use, if necessary.

Before submitting the job, edit the tape number of the backup volume used in SYSJOB2 into the job as directed by the job stream comments.

• SYSJOB7—Restore data sets from DASD

See the comment above for SYSJOB6.

9. When this panel completes successfully, you have completed the System Functions installation. Return to the starting panel (Figure 6-1) by typing X and pressing Enter. You can also press F3 repeatedly to return through the hierarchy of installation windows to Figure 6-1.

10. Having successfully completed step 1—System Functions, you can either:

a. Continue the installation of this software by completing the “Option 2 - Repository Functions” installation section.

or

b. Install the system portion of other AppBuilder software. Refer to the installation instructions of specific software for more information. You can then complete “Option 2 - Repository Functions” for each piece of software.

Option 2 - Repository Functions1. After entering 2 in the option line of the panel shown in Figure 6-1, the panel in Figure 6-5 will

appear. Before beginning this portion of the installation, all system functions described in “Apply System Upgrade” must have been successfully completed.

2. Enter 4 Apply Repository Upgrade on the option line of this panel (Figure 6-5) to begin the repository installation portion of this software.

3. Enter the ID of the repository to be updated. Examples are shown in this document as “repname.”

4. Press Enter to advance to the panel selected. To exit the panel, enter X or press END.

5. The panel in Figure 6-6 appears. This begins the installation of the repository functions.

Note If you choose procedure (a), ensure all software is installed in the proper order.

Note To prevent user access to the repository during the repository upgrade, use option 2, “Enable/Disable Repository” to disable the repository before beginning the repository upgrade.



Figure 6-5 Repository Functions

Apply Repository UpgradeFigure 6-6 shows the menu items you use to begin the installation of the repository software. From this panel you identify the repository you want to update, choose the options to create and process its installation table, and finally activate the repository. Perform the following options in order, as described below:

• Create Installation Table

• Process Installation Table

• Activate

Figure 6-6 Apply Upgrade to Repository menu



Option 1 - Create installation table

6. Enter 1 Create Installation Table on the option line of this panel (Figure 6-6) and the name of the repository to be updated and press Enter.

7. If this is the first time this repository has been updated, no subsequent panels will appear when you enter this option. Option 1 has completed when the “TABLE CREATED” message appears in the top-right corner of the panel. See Figure 6-7.

Otherwise, a panel will appear notifying you the jobs to update this repository have already been generated. This panel allows you to continue an in-progress installation, or abandon the installa-tion. You can either enter N to continue with current the installation or Y to recreate the table and begin the installation again.

Figure 6-7 Create installation table completion notification

Option 2 - Process Installation Table

8. Enter 2 Process Installation Table on the option line of this panel (Figure 6-6),and press Enter. The panel (Figure 6-8) will appear. This panel contains a table of releases ready to process. You will see an entry for this software, SVB2031, and any other AppBuilder 2.0.3.1 software for which the system installation has been completed. If there is more than release, select each one individually and check that it completes successfully before selecting the next release. You can monitor each release’s progress in the Status column. The status of a release may be [blank] — no activity is occurring, SUBMITTED — a release is in progress, or COMPLETED — a release is completed.

9. When you have executed all entries in the release table successfully, press F3.

Figure 6-8 Process Installation Table

10. If this is the first time this repository has been updated, the panel in Figure 6-9 will appear. Otherwise, a panel will appear notifying you that the jobs to update this repository have already been generated. You can continue an in-progress installation or abandon the installation by entering N to continue with current the installation or Y to recreate the table and begin the installation again.

Note If you have stopped the installation and are simply resuming the installation, select N. If you have altered the input data sets or have made other changes, enter Y to abandon this installation and start over.

--------------------- HOST INSTALLATION WORKBENCH ---------------------- COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===>

----------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> PF3-END PF7-UP PF8-DOWN PROCESS INSTALLATION TABLE Type S or SEL in the Action column to process a release. Action Release Status ______ SVB2031



11. The variables entered in Figure 6-9 are used to create two jobs that update the repository, REPJOB1 and REPJOB2.

Figure 6-9 Batch environment Variables

12. Review the following and change if needed:

300.1 Plan name prefix or suffix - [Default: B]

You can form DB2 plan names by using the generated bitmap as the plan name prefix or suffix. Enter B as the prefix or P to use the bitmap as the suffix.

300.2 Use AppBuilder Project name in Batch plan name? (Y/N) - [Default: N]

Enter Y or N to specify if you want to use the AppBuilder project name in the Batch plan name.

300.3 If not, enter the string to use here: - [Default: PLNB]

If you specified N above, enter the string you want to use for the Batch plan name.

300.4 Use the repository version number in plan name (Y/N) - [Default: N]

Enter Y or N to specify if you want to use the repository version number in the Batch plan name.

13. When you press Enter to accept this panel, a job card is displayed. Job card information is incorporated from the install into the REPJOB1 and REPJOB2 jobs. Review job card information, alter if needed, and press Enter to proceed.

14. After accepting the jobs, the panel in Figure 5-19 will appear. Submit the jobs listed in order from the top down (REPJOB1 then REPJOB2). You can view, submit, or regenerate a job from the Action column. Monitor its progress in the Status column.

Valid actions are regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the software. You can monitor each jobs progress in the Status column. The status of a job may be [blank] — no activity is occurring, SUBMITTED — a job is in progress, or COMPLETED — a job is completed.

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> BATCH ENVIRONMENT VARIABLES Repository ID: repname Release: SVB2031 You may form Batch DB2 plan names by using the generated bitmap as the plan name prefix or suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix: ==> B Use AppBuilder Project name in Batch plan name? (Y/N)==> N If not, enter the string to use here: ==> PLNB Use the repository version number in plan name? (Y/N)==> N Press END Command to Terminate. Press ENTER to Continue.



If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status column. Press Enter to clear this message and continue.

Figure 6-10 Regenerate/Edit/Submit Installation Jobs

• REPJOB1 — Performs non-DB2 processing. After the job completes, the following new data sets are created. (You may have more than one set of the following data sets if more than one version was specified during the Enterprise Repository installation).

Refer to Chapter 5, “Installing the Enterprise Repository” in this document for additional information about the AppBuilder data sets.

• REPJOB2 — Performs DB2 processing.

Option 3 - Activate Repository

15. Enter 3 Activate Repository on the option line of this panel (Figure 6-6) and press Enter. This will enable the repository with the new software. A message will appear in the top right corner, notifying you that the process has completed. At this point, the installation is complete.

16. After exiting out of the AppBuilder Host Installation Workbench, complete the “Postinstallation Notes” steps before executing the software.

Note &REPQUAL is the data set qualifier for AppBuilder repository level data sets.

Table 6-4 Repository Modification Libraries

&REPQUAL..LOADBT

Note &USRVQUAL is the data set qualifier for AppBuilder user data sets.

Table 6-5 User Libraries

&USRVQUAL..LOADBT &USRVQUAL..NCALBT

Note &VSUVQUAL is the VSAM user qualifier for AppBuilder VSAM data sets.

Table 6-6 User VSAM data sets

&VSUVQUAL..BATCH.RLRELATN &VSUVQUAL.BATCH.RULESRC

&VSUVQUAL..BATCH.VIEWDEF

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> PF3-END PF7-UP PF8-DOWN UPDATE REPOSITORY SOFTWARE - REGENERATE/EDIT/SUBMIT INSTALLATION JOBS Repository ID: repname Release: SVB2031 Type REGEN in the Action column to regenerate a job. Type V in the Action column to view a job. Type SUB in the Action column to submit a job. Action Jobname Description Status ______ REPJOB1 NON-DB2 PROCESSING ______ REPJOB2 DB2 PROCESSING



Figure 6-11 Activate repository completion notification

Postinstallation NotesPerform the following steps to complete and verify the successful installation of the AppBuilder REL 2.0.3.1 Batch Preparation Workbench.

1. Default Repository and Test Installation Process (TIP) application should already be migrated into the Enterprise Repository. If not, refer to the postinstallation instructions in Chapter 5, “Installing the Enterprise Repository” for the migration procedure.

2. Super Prepare TIP batch process:

a. Within the Enterprise Repository, make sure you are in the TIP Project.

b. Next to the Rebuild Package entity, type ADDE (Add Entity) to add a Rebuild Package for TIP. Name the package whatever you like. Press F3 to save and return.

c. Next to Rebuild Package entity, type LE to list the Rebuild Package entities. Next to the Rebuild Package you just created, type ADDR (Add Relationship) to add the tip batch process to the Rebuild Package for TIP. Select option 6 “Has-Root Process” in popup window and press Enter. Enter TIP_BATCH_PROCESS as the “Has-Root Process” name. Press F3 to save and end.

d. Next to the Rebuild Package for TIP, type SUPERPR. A message states the job was submitted and also displays the job number. Several jobs will be submitted at various times.

e. After the last job finishes, check the results be typing LISTRBD next to the Rebuild Package for TIP. Information will be displayed stating whether SUPERPR was successful or not. Press F3 to save and return.

3. Verify the country code and currency symbol in the program HPSCGAP included in &BASEQUAL..SVB2031.SAMPLE, and change these appropriately. These values are identified by the labels HGACSTOK, HGACTRYD and HGACTRYC. Assemble the program, saving the

object module into the relevant object library. Then rerun the COPY1, COPY2, and COPY3 steps

in the DSALLOC member found in the &INSTQUAL.AB2031.CNTL data set. This will place the

correct version of the translate objects in the &BASEQUAL.OBJ data set. This problem will be

corrected in the next release so that the translate objects will be delivered in the runtime products.

Then link the member HPSCGAP into your AppBuilder Batch load library using the link function

accessed from the Host Installation Workbench System Functions menu. See Chapter D, “HPSCGAP, HPICGAP, HPEUCGP, and Sample Batch JCL” for more information about HPSCGAP.

repname ENABLED ---------------------- HOST INSTALLATION WORKBENCH ------------------- COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 3



Installation Verification Using TIP1. Verify the TIP batch process has been prepared successfully.

2. Within the Enterprise Repository, verify you are in the TIP project. If not, enter PROJECTS at the command line. Select TIP for version 1. Complete steps 2 through 4 for each version of the repository.

3. Type LE next to the Rules entity to list the rules.

4. Allocate the TIPOUTdata set to avoid receiving abends by using the following TSO commands:

ALLOCATE FI(TIPOUT) SYSOUT(*)

5. Test the following batch rules by typing TE next to each. Select break points if you wish, and press F16 or SHIFT+F4 to continue. A message will be displayed for each rule stating whether it is successful or not.

• TIP_BATCH_ASM_RULE

• TIP_BATCH_ASMDB2_RULE

• TIP_BATCH_COB_RULE

• TIP_BATCH_COBDB2_RULE

• TIP_BATCH_PLI_RULE *

• TIP_BATCH_PLIDB2_RULE *

• TIP_MVS_RULE

Note Items marked with an asterisk (*) are optional, only for testing PL/I components. Do not execute these two rules if PL/I components are not used.




CHAPTER

7 INSTALLING REPORT WRITER PREPARATION


The information in this section describes the detailed requirements and procedures for installing Report Writer Perparation.

PrerequisitesThe following software is required prior to the installation of this software:



• AppBuilder REL 2.0.3.1 Batch Preparation





Note Customization worksheets are not required for this product.


Installation Notes

Installation NotesThis section contains the following hierarchy of panels for installing the AppBuilder REL 2.0.3.1 Report Writer Preparation software:




Option 1, Unload Installation Data Sets

Option 2, Continue


Confirm Update Job Submission


SYSJOB2, Set Tape Backup Parameters



Apply Upgrade to Repository

Option 1, Create Installation Table

Upgrade Repository

Option 2, Process Installation Table


Create Repository Upgrade Job


Option 3, Activate Repository

Installing Report Writer PreparationThere are two parts to installing the Report Writer Preparation product option: “Option 1—System Functions” and “Option 2 - Repository Functions”. Use the panel in Figure 7-1 to navigate to both parts through the Host Installation Workbench—Workbench Functions.

7-2 Installing Report Writer Preparation

Installing Report Writer Preparation

Figure 7-1 Host Installation Workbench Functions panel

The Workbench Functions panel is the starting point for installing system functions and repository functions. You must first apply the system functions and then the repository functions:

• Option 1, System Functions—see “Option 1—System Functions”.

• Option 2, Repository Functions—see “Option 2 - Repository Functions”.

You must complete Option 1 before installing Option 2. However, you can apply system functions (Option 1) for all products before starting the repository functions (Option 2).

Option 1—System FunctionsSystem functions are those installation processes you start when you choose Option 1, System Functions in Figure 7-1. This option lets you apply the system upgrade for Report Writer Preparation.


When you install the Report Writer Preparation product system functions, first select System Functions using Option 1 in Figure 7-1. See the System Functions panel in Figure 7-2.

------------------------ HOST INSTALLATION WORKBENCH -------------------COMMAND ===> WORKBENCH FUNCTIONS OPTION ===> 1 System Functions 2 Repository Functions X EXIT Enter END Command to exit. Press ENTER to continue.



Figure 7-2 Apply System Upgrade panel to install product options

Use this panel to perform option 2 Apply System Upgrade.

Select option 2 on the panel.

1. Enter the ID of the system to be upgraded, shown here as “sysname”.

2. Press ENTER to advance to the panel selected.

3. Enter X or press END to exit the panel.

The next panel you see appears in Figure 7-3, and it begins the installation of the system functions.

Update system software

Figure 7-3 begins the installation of the system software, starting with unloading the data sets.

Figure 7-3 Update System Software panel to unload installation Data sets

----------------------- HOST INSTALLATION WORKBENCH ----------------------- COMMAND ===> SYSTEM FUNCTIONS OPTION ===> 2 SYSTEM ID ===> 1 Create System Software 2 Apply System Upgrade 3 Display Software History 4 Link AppBuilder Modules 5 Prelink AppBuilder C Modules 6 List Systems and Repositories X EXIT Enter END Command to exit. Press ENTER to continue.

------------------------ HOST INSTALLATION WORKBENCH -------------------- UPDATE SYSTEM SOFTWARE COMMAND ===> System ID to be updated: sysname Enter the Release Details: Release: RPW2031 Unit: CART Tape Vol Ser Number: OPTION ===> ( 1 Unload installation data sets) ( 2 Continue) ( X EXIT) JOB STATEMENT INFORMATION: (Required - Enter/Verify JOB control statements ===> //SS0221I JOB (ACCOUNT),’NAME’ , ===> // NOTIFY=SS0221,MSGCLASS=?,CLASS=? ===> //* ===> //* Enter END command to exit. Press ENTER to continue.



This option unloads the installation data sets required for the system installation. In option 1 Unload Installation data sets, you enter the data needed to create the unload JCL. In option 2 Continue, you activate the actual unloading of the data from tape to your system. First, we define what you do in this panel.

Enter the Release Details

• Release: - [DEFAULT: RPW2031] Enter RPW2031, which is the release number for this system upgrade.

• Unit: Enter the name of the unit used to read your AppBuilder tape.

• Tape Vol Serial Number: Enter the tape volume serial number for the tape.

Option 1 - Unload installation data sets

Selecting option 1 puts you in edit mode for the unload job. Review the JCL and submit it. Press F3, and check the output of execution. Confirm it contains these three data sets with installation software:

• &instqual..&RPW2031.CNTL

• &instqual..&RPW2031.ICLIST

• &instqual..&RPW2031.IPANELS

• &instqual..&RPW2031.ISKELS

where &instqual is the installation data set qualifier. Refer to Chapter 5, “Installing the Enterprise Repository” in this document for additional information about the AppBuilder data sets.

Option 2 - Continue

Select option 2 in Figure 7-3 to continue the system software installation. Press Enter.


Figure 7-5 appears the first time you perform this installation. The panel in Figure 7-4 is optional; the first time you apply a system upgrade, it does not appear. But it does in subsequent passes. Its text says that the installation tables are already generated; consequently, do not generate them again unless you want to begin the installation again.



Figure 7-4 Create system upgrade jobs panel, to regenerate the installation table

Under normal circumstances, select N (No) and proceed. But if you want to begin the installation again with the first job, select Y (Yes). This action resets the status of the jobs but does not regenerate them. The status is reported in the panel in Figure 7-6.

Depending on your response, regeneration either occurs or does not. Regenerating the table clears the status of any jobs that are ‘SUBMITTED’ or ‘COMPLETED’. On successful completion of either choice, you are ready to update the system software. This figure appears only if have already applied a system upgrade if this system.


The next panel, confirming the update of your job submission, is in Figure 7-5.

-------------------- HOST INSTALLATION WORKBENCH ----------------------- COMMAND ===> CREATE SYSTEM UPGRADE JOBS The jobs to upgrade this system have already been generated. To complete the installation using the existing jobs, enter N below. To recreate the the table and begin the installation again, enter Y below. Note that you may encounter difficulty in attempting to rerun jobs which have already been completed. Do you want to regenerate the installation table? (Y/N)==> Enter END command to exit. Press ENTER to continue.



Figure 7-5 Confirm Update Job Submission panel

This panel notifies you that no backup has been made. It is recommended that you back up your installation.

Under normal circumstances, select Y (Yes) and proceed. But if you have a strong reason for not backing up the installation, press N (No). You will not be able backup this PTF later.

After this selection, the Regenerate/Edit/Submit panel appears.

Regenerate/edit/submit Installation Jobs

This panel provides the controls to regenerate, view, and submit installation jobs. Figure 7-6 shows the panel that controls the actual unloading, backing up, copying, linking, and restoring of installation data sets.

Figure 7-6 Regenerate/View/Submit Installation Jobs panel

----------------------- HOST INSTALLATION WORKBENCH -------------------- COMMAND ===> UPDATE SYSTEM SOFTWARE - CONFIRM UPDATE JOB SUBMISSION System ID to be Updated: sysname Release: RPW2031 This job will update your System Software,but you have not made a backup. If you proceed, you will be unable to backout this PTF later on. If you wish to proceed anyway, enter Y below. Otherwise enter N below to return to the UPDATE SYSTEM SOFTWARE - REGENERATE/EDIT/SUBMIT JOBS panel. Do you want to proceed without a backup?(Y/N)==> Enter END command for previous screen. Press ENTER to continue.

------------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> PF3-END PF7-UP PF8-DO UPDATE SYSTEM SOFTWARE - REGENERATE/EDIT/SUBMIT INSTALLATION JOBS System ID: sysname Release: RPW2031 Type REGEN in the Action column to regenerate a job. Type V in the Action column to view a job. Type SUB in the Action column to submit a job. Action Jobname Description Status _____ SYSJOB1 UNLOAD REST OF TAPE ______ SYSJOB2 BACKUP DATASETS TO TAPE ______ SYSJOB3 BACKUP DATASETS TO DASD ______ SYSJOB4 LINK LOAD MODULES ______ SYSJOB5 COPY TO SYSTEM DATASETS ______ SYSJOB6 RESTORE DATASETS FROM TAPE ______ SYSJOB7 RESTORE DATASETS FROM DASD



This screen controls unloading of data sets. Perform the appropriate steps top down. You can unload the tape, back up to tape or DASD, link the load modules, and copy the results to system data sets; or restore the data sets if dissatisfied with the results. Monitor its progress in the Status column and in additional panels that alert you of specific situations.

The Actions you can make are to regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the software. You can monitor each jobs progress in the Status column. The status of a job may be [blank] — no activity is occurring, SUBMITTED — a job is in progress, or COMPLETED — a job is completed.


You must perform jobs 1, 4, and 5; the rest are optional. The following describes the system jobs:


Proceed with the unload process. You can view, regenerate, or submit the job for execution. The following data sets are unloaded from the tape by SYSJOB1:


When you regenerate or submit SYSJOB2, you see another panel that sets tape backup parameters, as shown in Figure 7-3.


Use this job to direct your backup to DASD.


When the data sets are unloaded successfully, perform the link of the load modules. Before that can be completed, you must define additional information in another panel, shown in Figure 7-8.


When the load modules are linked successfully, copy the modules to the system data sets. If you have not performed a backup, the panel in Figure 7-4 alerts you. The following data sets are updated or created by SYSJOB5:

Table 7-1 Data sets

&BASEQUAL..RPW2031.LKBS00 &BASEQUAL..RPW2031.LOADLIB

&BASEQUAL..RPW2031.MVSCODE &BASEQUAL..RPW2031.PLKOBJ

&BASEQUAL..RPW2031.PRELINK &BASEQUAL..RPW2031.PSFCODE

&BASEQUAL..RPW2031.PSFDCL &BASEQUAL..RPW2031.RWMSG

&BASEQUAL..RPW2031.RWPRTLOG &BASEQUAL..RPW2031.MVSDCL

&BASEQUAL..RPW2031.OBJ &BASEQUAL..RPW2031.RWLNCFG

&BASEQUAL..RPW2031.RWERRMSG &BASEQUAL..RPW2031.STDCODE

&BASEQUAL..RPW2031.STDDCL




The restore data sets process can be used to recover (or restore) system software data sets from the tape or DASD backups made in SYSJOB2 or SYSJOB3 in the event that the outcome of the system software upgrade is unsatisfactory. Of course, the restore process can be used only if SYSJOB2 or SYSJOB3 was run. To restore data sets from a tape backup, select SYSJOB6. To restore data sets from DASD backups select SYSJOB7. The restore process does not affect any repository data sets. If the repository installation was also completed, any updated repository information must be manually restored and any DB2 plans rebound using the restored software level.

BluePhoenix recommends that you use the View or REGAN action on SYSJOB6 or SYSJOB7 at this time in order to create the job for later use, if necessary.



• Status—[blank]

The following lists indicators displayed in the Status column. Observe the status of the Actions you initiate.

• [blank] — No activity is occurring.

• SUBMITTED — A job is in progress.

• COMPLETED — A job is completed.

When this panel completes successfully, you have completed the System Functions installation. Return to the starting panel by typing X and pressing Enter or by pressing F3 repeatedly. You return through the hierarchy of installation windows to the Workbench Functions panel in Figure 7-1.

Having successfully completed option 1 System functions, you can either:

a. Continue the installation of this software by completing the “Option 2 - Repository Functions” installation

or

b. Install the system portion of other AppBuilder software. Refer to installation instructions of specific software for more information—for example, Chapter 5, “Installing the Enterprise

Table 7-2 SYSJOB5 Data Sets

&BASEQUAL..LKBS00 &BASEQUAL..LOADLIB

&BASEQUAL..MVSCODE &BASEQUAL..MVSDCL

&BASEQUAL..OBJ &BASEQUAL..PSFCODE

&BASEQUAL..PSFDCL &BASEQUAL..RWERRMSG

&BASEQUAL..RWLNCFG &BASEQUAL..RWMSG

&BASEQUAL..RWPRTLOG &BASEQUAL..STDCODE

&BASEQUAL..STDDCL

Note Before submitting this job, edit the tape number of the backup volume used in SYSJOB2 into the job as directed by the job stream comments.




Repository” You would then complete the “Option 2 - Repository Functions” for each piece of software.

SYSJOB2 - Set Tape Backup ParametersWhen you start a backup of data sets to tape, see a panel that identifies the taping parameters as shown in Figure 7-7.

Figure 7-7 Set Tape Backup Parameters panel

1. Enter the UNIT for the tape being used for the backup.

2. Enter the volume serial number of the tape being used for the backup.

3. Enter the number of days that you want the taped data to be retained.

4. Specify the required tape backup information, and press ENTER to activate these parameters. The backup process executes, and you return to the panel in Figure 7-6.

Option 2 - Repository FunctionsRepository functions are those installation processes you start when you choose Option 2, Repository Functions in Figure 7-1. This option lets you apply the repository upgrade for Report Writer Preparation. You must complete the Option 1, System Functions before proceeding with Option 2, Repository Functions.


Option 2, Repository Functions, allows you to start installing repository functions, as shown in Figure 7-8.

Note If you choose procedure a, ensure all software is installed in the proper order.


----------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> SET TAPE BACKUP PARAMETERS System ID to be Updated: sysname Release: RPW2031 Enter UNIT ===> CART Enter Volser ===> NONE Enter Retention Period ===> 30 Enter END Command to Terminate, Enter HELP for help panels.



Figure 7-8 Apply repository upgrade panel to install product options

Use the panel above to perform option 4, Apply Repository Upgrades. The valid actions for this panel are:

1. Select option 4 on the panel.

2. Enter the ID of the repository to be updated.



The next panel you see appears in Figure 7-9, and it starts the installation of the repository functions.


This panel begins the installation of the repository software, starting with creating installation tables, as shown in Figure 7-9.

------------------------- HOST INSTALLATION WORKBENCH -------------------- COMMAND ===> REPOSITORY FUNCTIONS OPTION ===> REPOSITORY ID ===> 1 Create Repository 6 Display Software History 2 Enable/Disable Repository 7 Create New Version 3 Bind DB2 Objects 8 Maintain Version 4 Apply Repository Upgrade 9 List Systems and Repositories 5 Associate Repository X EXIT Enter END Command to exit. Press ENTER to continue.



Figure 7-9 Apply Upgrade to Repository panel

This panel starts upgrading the repository portion of the Report Writer Preparation product option. But, you cannot start this portion until you have completed the system functions described in “Update system software”.

From this panel identify the repository you want to create; choose the options to create and process its installation table, and finally activate the resultant repository. Perform the following options in order, as described below:



• Activate


Initiate the panel in Figure 7-9 with option 1. Begin by naming the repository to upgrade and selecting option 1 Create Installation Table. (You will return to this panel to perform Option 2 and 3 later.)

If this is the first time upgrading this repository, you know that option 1 is done when the “TABLE CREATED” message appears in the top-right corner of Figure 7-9. In this case, perform Option 2 and proceed to the panel in Figure 7-11.

After the initial upgrade of the repository using Option 1, you see the panel on Figure 7-10. After you make your selection, you return to this panel for action. Assuming you are continuing with the upgrade at hand, proceed to the panel in Figure 7-11 to perform Option 2.

Additional information about Options 2 and 3 appears in sequence later.

----------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT Enter END Command to exit. Press ENTER to continue.



Upgrade Repository

Figure 7-11 will appear the first time you perform this installation. The panel appearing next in Figure 7-10 is optional; the first time you apply a system upgrade, it does not appear. It does appear in subsequent passes. Its text says that the installation tables are already generated; consequently, do not generate them again unless you have introduced some change requiring another generation pass.

Figure 7-10 Upgrade Repository panel

This panel allows you to restart the installation if special circumstances demand it.

Under normal circumstances, select N (No) and proceed. But if you have altered the input data sets or introduced other changes, press Y (Yes) to abandon this upgrade and start again.

This optional panel allows you to decide if the upgrade you are starting is the correct one. Depending on your response, this repository upgrade can be continued or terminated so another can be started from the beginning:

• If you want to continue the upgrade currently in progress, enter N.

• If you want to stop this upgrade, not allowing it to continue, so you can initiate another modified upgrade, enter Y.

On successful completion of either choice, you move to the next panel in Figure 7-11.


You return to the Apply Upgrade to Repository panel (Figure 7-11), and enter Option 2, Process Installation Table.

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> UPGRADE REPOSITORY The process of upgrading this repository has already been begun but has not been completed. To complete the installation already in progress, enter N below to return to the Apply Repository Upgrade menu panel. Then select Step 2 (PROCESS INSTALLATION TABLE). To abandon the installation in progress and begin again, enter Y below. Note that you may encounter difficulty in attempting to run jobs which have been previously run. Do you want to begin the upgrade again? (Y/N) ==> Enter END command for previous screen. Press ENTER to continue.



Figure 7-11 Apply Upgrade to Repository

Select Option 2 for the same repository, and press Enter. Figure 7-12 appears.


Figure 7-12 shows the next panel from which you start processing the installation table.

Figure 7-12 Process Installation Table panel

This panel contains a table of releases that you are to process. Select each in top-down order, and assure each executes completely. The following lists indicators displayed in the Status column. Observe the status of the Actions you initiate.


• SELECTED — A job is in progress.


When you have executed all entries in the release table successfully, press F3. See the next panel.

----------------------- HOST INSTALLATION WORKBENCH ------------------- COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 2 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT Enter END Command to exit. Press ENTER to continue.

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> PF3-END PF7-UP PF8-DOWN PROCESS INSTALLATION TABLE Type S or SEL in the Action column to process a release. Action Release Status ______ RPW2031



Create Repository Upgrade Jobs

Figure 7-14 will appear the first time you perform this installation. The panel appearing next in Figure 7-13 is optional; the first time you apply a repository upgrade, it does not appear. But it does in subsequent passes. Its text says that the installation job table is already generated; consequently, do not generate it again unless you want to restart the installation from the beginning. The next panel is optional, appearing only if you are executing this process more than once. This panel in Figure 7-13 enables you to recreate the job table and restart the release selected in Figure 7-12.

Figure 7-13 Create Repository Upgrade Jobs panel

This panel appears when jobs to generate the repository have been created previously. You can accept them as they are (specify N for No) or recreate the table and restart the installation (specify Y for Yes). Select N or Y, and press Enter. Figure 7-14 establishes batch variables.


Figure 7-14 defines the repository jobs that install updates to your repository.

Figure 7-14 Regenerate/Edit/Submit Installation Jobs panel

Execute the jobs in order from the top down. You can view, submit, or regenerate a job from the Action column. Monitor its progress in the Status column and in additional panels that alert you of specific situations.

----------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> CREATE REPOSITORY UPGRADE JOBS The jobs to upgrade this repository have already been generated.To completethe installation using the existing jobs, enter N below. To recreate the the table and begin the installation again, enter Y below. Note that you may encounter difficulty in attempting to rerun jobs which have already been completed. Do you want to regenerate the installation table? (Y/N)==>

----------------------- HOST INSTALLATION WORKBENCH ---------------------COMMAND ===> PF3-END PF7-UP PF8-DOWN UPDATE REPOSITORY SOFTWARE - REGENERATE/EDIT/SUBMIT INSTALLATION JOBS Repository ID: repname Release: RPW2031 Type REGEN in the Action column to regenerate a job. Type V in the Action column to view a job. Type SUB in the Action column to submit a job. Action Jobname Description Status ______ REPJOB1 NON-DB2 PROCESSING



This panel is a major control panel for the repository functions update. Its choices are:

• Regenerate (REGEN)

• Vew (V or VIEW)

• Submit (SUB) jobs to update the software

You monitor each jobs progress in the Status column. If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status column. Press Enter to clear this message and continue.

The following list describes the repository job:

• REPJOB1 — NON-DB2 PROCESSING



• SUBMITTED — An action is in process.

• COMPLETED — An action is completed.

When you have completed this job successfully, press the Enter key twice to refresh the status panel and F3 to exit this panel. You return to the Apply Upgrade to Repository panel, shown in Figure 7-15.


After completing the previous panel, you have applied all the repository updates for RPW2031. The last action in this series activates the repository, as Figure 7-15 shows.


Figure 7-15 appears for you to select Option 3, Activate Repository. This option concludes the installation of the Report Writer Preparation upgrade to your repository.

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 3 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT




Installation Verification Using TIPPerform the following steps to verify the installation:

Verify the TIP batch process has been prepared successfully. If not, refer to “Postinstallation Notes” for the Batch Preparation installation.

1. Within the Enterprise Repository, verify that you are in the TIP project. If not enter PROJECTS at the command line. Select TIP for version 1. Complete the remaining steps for each version of the repository.

2. Type LE next to the pubs entity to list the rules.

3. Make the following allocations to your session at the command line:

• TSO ALLOC F(HTPRPT) DA(*)

• TSO ALLOC F(SYSOUT) DA(*) [Note: This may already be allocated.]

4. Test the following TIP batch report rule by typing TE next to TIP_REPORT_RULE. Select break points if you wish, and press F16 or SHIFT+F4 to continue. The TIP report will be displayed on your screen.

5. Test the report method by typing REP next to any rule listed. A panel will be displayed requesting more information about the report. Enter the following:

A batch job will be submitted. After the job finishes, view the report by typing RES next to the rule that the report was run against. Select the “AppBuilder Reporting Facility” results file to display the report.

Table 7-3 TIP Verification

Object Parts to Process: Use defaults

Report Output Options: Select 1 for softcopy

Printer Destination: Leave blank

Defer Report for Overnight Execution: Use default

Report Selection Options: Select 2 for Object Hierarchy




CHAPTER

8 INSTALLING CICS ONLINE PREPARATION WORKBENCH AND ENTERPRISE SERVER


The information in this section describes the detailed requirements and procedures for installing a CICS Online Prepration Workbench and enterprise server.

PrerequisitesThe following AppBuilder software is required prior to the installation of this software:






where xxxxxx is the volume number on the tape you received.

Note Complete the checklists and worksheets provided in Chapter E, “Hardware and Software Checklists” and Chapter I, “CICS Online Preparation Workbench and Enterprise Server Customization Worksheets” in this document before proceeding with this installation.


Installation Notes

Installation NotesThis section contains the following hierarchy of panels for installing the AppBuilder REL 2.0.3.1 CICS Online Preparation Workbench and Enterprise Server software.




Option 1, Unload Installation Data Sets

Option 2, Continue




SYSJOB2, Set Tape Backup Parameters

SYSJOB4, Capture System Variables





Upgrade Repository

Option 2, Process Installation Table


Apply SVC2031 to Repository

Option 1, Capture Version Variables

Capture Version Variables (6 panels)

Option 2, Capture/Submit Installation Jobs



Installing CICS Online Preparation Workbench and Enterprise Server Software

There are two parts to installing AppBuilder REL 2.0.3.1 CICS Online Preparation Workbench and CICS Enterprise Server software: “Option 1 - System Functions” and “Option 2 - Repository Functions”.

Use the panel in Figure 8-1 to navigate to both parts through the AppBuilder REL 2.0.3.1 Host Installation Workbench—Workbench Functions (Figure 8-1).

8-2 Installing CICS Online Preparation Workbench and Enterprise Server

Installation Notes

Figure 8-1 Host Installation Workbench Functions

The Workbench Functions panel is the starting point for installing system functions and repository functions. You must first apply the system functions and then the repository functions:

• “Option 1 - System Functions”

• “Option 2 - Repository Functions”

Complete option 1 before installing option 2. However, you can apply system functions (Option 1) for all products before starting the repository functions (Option 2).

Option 1 - System FunctionsSystem functions are those installation processes you start when you choose Option 1, System Functions in Figure 8-1. This option lets you apply the system upgrade for AppBuilder REL 2.0.3.1 CICS Online Preparation Workbench and CICS Enterprise Server software.


When you install the AppBuilder REL 2.0.3.1 CICS Online Preparation Workbench and CICS Enterprise Server software system functions, select System Functions using option 1 in Figure 8-1. The System Functions panel opens (Figure 8-2).


Installation Notes

Figure 8-2 Apply System Upgrade panel to install product options



2. Enter the ID of the system to be upgraded, shown here as “sysname.”



Figure 8-3 appears, and it begins the installation of the system functions.


This panel begins the installation of the system software, starting with unloading the data sets, as shown in Figure 8-3.

Figure 8-3 Update System Software


Installation Notes

This option unloads the installation data sets required for the system installation. In option 1 Unload Installation Data Sets, you will enter the data needed to create the unload JCL.

In option 2 Continue, you activate the actual unloading of the data from tape to your system. First, however, you must enter the following information.

• Release: Enter SVC2031, the installation code for this software. This number is on the packaging list provided with the tape.

• Unit: Enter the name of the unit used to read your AppBuilder tape.

• Tape Vol Serial Number: Enter the tape volume serial number for the tape. This number is on the packaging list provided with the tape.

Option 1 - Unload Installation Data Sets

Selecting option 1 displays job card information. Review the data and submit it. Check the output of execution and confirm it contains the following data sets:

• &instqual..&SVC2031.CNTL

• &instqual..&SVC2031.ICLIST

• &instqual..&SVC2031.IPANELS

• &instquaL..&SVC2031.ISKELS

where &instqual is the installation data set qualifier. Refer to Chapter , “Installing the Enterprise Repository” in this document for additional information about the AppBuilder data sets.

Option 2 - Continue

Selecting option 2 in Figure 8-3 allows you to continue the system software installation. Press Enter to continue to Figure 8-4.


Figure 8-5 appears the first time you perform this installation. The panel shown here in Figure 8-4 is optional; the first time you apply a system upgrade, it does not appear. But it does in subsequent passes. Its indicates that the installation tables are already generated; consequently, do not generate them again unless you have introduced some change requiring another generation pass


Installation Notes

Figure 8-4 Create System Upgrade Jobs panel, to regenerate the installation table

Under normal circumstances, select N (No) and proceed. If you want to begin the installation again with the first job, select Y (Yes). This action resets the status of the jobs but does not regenerate them. The status is reported in the panel in Figure 8-1.

Depending on your response, regeneration either occurs or does not. Regenerating the table clears the status of any jobs that are ‘SUBMITTED’ or ‘COMPLETED’. On successful completion of either choice, you are ready to update the system software. Figure 8-4 appears only if you have already applied a system upgrade to this system.


Figure 8-5 appears, confirming the update of your job submission.

----------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> CREATE SYSTEM UPGRADE JOBS The jobs to upgrade this system have already been generated. To complete the installation using the existing jobs, enter N below. To recreate the the table and begin the installation again, enter Y below. Note that you may encounter difficulty in attempting to rerun jobs which have already been completed. Do you want to regenerate the installation table? (Y/N)==> Enter END command to exit. Press ENTER to continue.


Installation Notes

Figure 8-5 Confirm Update Job Submission panel

This panel notifies you that no backup has been made. It is recommended that you back up your installation.

Under normal circumstances, select N (No) and proceed with the backup job. But you choose to not back up the installation by pressing Y (Yes).

After this selection, the Regenerate/Edit/Submit panel (Figure 8-6) appears.


This panel provides the controls to regenerate, view, and submit installation jobs. Figure 8-6 shows the panel that controls the actual unloading, backing up, copying, linking, and restoring of installation data set.

Note You will not be able back out this software later.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> UPDATE SYSTEM SOFTWARE - CONFIRM UPDATE JOB SUBMISSION System ID to be Updated: Release: SVC2031 This job will update your System Software, but you have not made a backup. If you proceed, you will be unable to backout this PTF later on. If you wish to proceed anyway, enter Y below. Otherwise enter N below to return to the UPDATE SYSTEM SOFTWARE - REGENERATE/EDIT/SUBMIT JOBS panel. Do you want to proceed without a backup?(Y/N)==> Enter END command for previous screen. Press ENTER to continue.


Installation Notes


This screen controls unloading of data sets. Perform the appropriate steps top down. You can unload the tape, backup to tape or DASD, link the load modules, and copy the results to system data sets; or restore the data sets if you are not satisfied with the results. Monitor its progress in the Status column and in additional panels that alert you of specific situations.

The actions you can take are to regenerate (REGEN), view (V or VIEW), or submit (SUB) jobs to update the software. You can monitor each jobs progress in the Status column. The status of a job may be [blank] — no activity is occurring, SUBMITTED — a job is in progress, or COMPLETED — a job is completed.


You must perform jobs 1, 4, and 5; the rest are optional. The following describes the system jobs:


Proceed with the unload process; you can view, regenerate, or submit the job for execution. The fol-lowing data sets are unloaded by SYSJOB1:


When you regenerate or submit SYSJOB1, you see another panel that sets tape backup parameters, as shown in Figure 8-2.

Table H-1 Data sets created by SYSJOB1

&BASEQUAL.SVC2031.HPSDNAER &BASEQUAL.SVC2031.OBJ

&BASEQUAL.SVC2031.HPSDNAIN &BASEQUAL.SVC2031.PLKOBJ

&BASEQUAL.SVC2031.HPSDNART &BASEQUAL.SVC2031.PRELINK

&BASEQUAL.SVC2031.LKCIEC &BASEQUAL.SVC2031.SAMPLE

&BASEQUAL.SVC2031.LKCIEN &BASEQUAL.SVC2031.SAMP255

&BASEQUAL.SVC2031.LKCIUC &BASEQUAL.SVC2031.SAMP80

&BASEQUAL.SVC2031.LOADCI &BASEQUAL.SVC2031.VIDTEXT


Installation Notes





When creating the link edit job, a panel is displayed requesting the CICS LINK and RUNTIME libraries. If you press END to terminate instead of continuing, the JCL for SYSJOB4 is still created with the values present on the panel at that time. To rectify this error, it is necessary to type REGEN against JOB.


When the load modules are linked successfully, copy the modules to the system data sets. After this job completes the following data sets are created or updated:

• System libraries:

• System VSAM libraries:

• Maintenance libraries:



We recommend that you use the View or REGAN action on SYSJOB6 or SYSJOB7 at this time in order to create the job for later use if necessary.


Table H-2 System libraries created or updated by SYSJOB5

&BASEQUAL..COPYC &BASEQUAL..LKCIEC

&BASEQUAL..LKCIEN &BASEQUAL..LKCIUC

&BASEQUAL..LOADCI &BASEQUAL..OBJ

&BASEQUAL..PLKOBJ &BASEQUAL..PRELINK

Note &BASEQUAL is the System Data Set Qualifier for AppBuilder data sets.

Table H-3 VSAM libraries created or updated by SYSJOB5

&VSMQUAL..HPSDNAER.CAT

Note &VSMQUAL is the System VSAM Data Set Qualifier for AppBuilder data sets.

Table H-4 Maintenance libraries created or updated by SYSJOB5

&MODQUAL..LOADCI

Note &MODQUAL is the Maintenance Data Set Qualifier for AppBuilder data sets.



Installation Notes



Observe the status of the Actions you initiate. The following lists indicators that are displayed in the Status column:


• SUBMITTED — An action is in process.


When all jobs have completed successfully, you have completed the System Functions installation. Return to the starting panel by typing X and pressing ENTER, or press F3 repeatedly. You return through the hierarchy of installation windows to the Workbench Functions panel in Figure 8-7.

Having successfully completed 1—System Functions, you can:

a. Continue the installation of this software by completing the “Option 2 - Repository Functions” installation

or

b. Install the system portion of other AppBuilder software. Refer to the installation instructions of specific software for more information. You can then complete the “Option 2 - Repository Functions” for each piece of software.

SYSJOB2 - Set Tape Backup Parameters

When you start a backup of data sets to tape, you will see a panel that identifies the tape parameters, as shown in Figure 8-7.

Figure 8-7 Set Tape Backup Parameters




Note If you choose procedure (b), ensure all software is installed in the proper order.

---------------------- HOST INSTALLATION WORKBENCH -------------------- COMMAND ===> SET TAPE BACKUP PARAMETERS System ID to be Updated: sysname Release: SVC2031 Enter UNIT ===> CART Enter Volser ===> NONE Enter Retention Period ===> 30 Enter END Command to Terminate, Enter HELP for help panels.


Installation Notes


4. Specify the required tape backup information, and press ENTER to activate these parameters. The backup process executes, and you return to the panel in Figure 8-1.

SYSJOB4 - Capture System Variables

To perform the load link modules step (Action: SYSJOB4) in Figure 8-1, the process needs certain information you provide in the panel shown in Figure 8-3.

Figure 8-8 Capture System Variables

The choices in this panel are:

400.1 CICS Runtime Library -[Default: CICSTS13.SDFHLOAD]

Enter the name of the CICS runtime library used to link AppBuilder modules.

When you have specified the variables, press ENTER. You return to the panel in Figure 8-1.

Option 2 - Repository FunctionsRepository functions are those installation processes you start when you choose option 2, Repository Functions. This option lets you apply the repository upgrade for AppBuilder REL 2.0.3.1 CICS Online Preparation Workbench and CICS Enterprise Server software. You must complete the option 1, System Functions before proceeding with option 2, Repository Functions.

Installing Repository Upgrades

Select option 2 Repository Functions to start installing repository functions, as shown in Figure 8-9.

Note To prevent user access to the repository during the repository upgrade, use option 2 Enable/Disable Repository to disable the repository before beginning the repository upgrade.

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> CAPTURE SYSTEM VARIABLES System ID: sysname Release: SVC2031 CICS Runtime Library ==> CICSTS13.SDFHLOAD


Installation Notes

Figure 8-9 Apply Repository Upgrade

Use the panel above to perform option 4 Apply Repository Upgrades. The actions for this panel are:





The next panel begins the installation of the repository functions.




Installation Notes

Figure 8-10 Apply Upgrade to your Repository

This panel starts upgrading the repository portion of the AppBuilder REL 2.0.3.1 CICS Online Preparation Workbench and CICS Enterprise Server software.

From this panel you identify the repository you want to create, and choose the options to create and process its installation table, and finally activate the resultant repository. Perform the following options, as described below:



• Activate

Option 1 - Create Installation Table

Initiate the panel in Figure 8-10 by identifying the repository to upgrade and selecting option 1 Create Installation Table. (You will return to this panel to perform option 2 and 3 later.)

If this is the first time upgrading this repository, the “TABLE CREATED” message appears in the top-right corner of Figure 8-10. In this case, perform option 2 and proceed to the panel in Figure 8-11.

After the initial upgrade of the repository using option 1, you see the panel. on Figure 8-6. After you handle that panel, you will return to this panel for action.

Additional information about option 2 and 3 appears in sequence later.

Warning Do not begin this part of the installation until you have completed the system functions portion of the installation.


Installation Notes

Upgrade Repository

Figure 8-10 will appear the first time you perform this installation. The panel appearing next in Figure 8-11 is optional. The first time you apply a repository upgrade, this panel does not appear; but it does appear subsequently. It indicates that the installation tables are already generated; consequently, do not generate them again unless you have introduced some change requiring another generation pass.

Figure 8-11 Upgrade Repository





• If you want to stop this upgrade, not allowing it to continue, so you can initiate another modified upgrade, press Y.


Figure 8-12 shows the Apply Upgrade to Repository panel, enter option 2 Process Installation Table and press ENTER.

---------------------- HOST INSTALLATION WORKBENCH -------------------- COMMAND ===> UPGRADE REPOSITORY The process of upgrading this repository has already been begun but has not been completed. To complete the installation already in progress, enter N below to return to the Apply Repository Upgrade menu panel. Then select Step 2 (PROCESS INSTALLATION TABLE). To abandon the installation in progress and begin again, enter Y below. Note that you may encounter difficulty in attempting to run jobs which have been previously run. Do you want to begin the upgrade again? (Y/N) ==>


Installation Notes





This panel contains a table of releases that you are to process. If there are more than one, select each in top-down order and ensure each executes completely. The following lists indicators displayed in the Status column. Observe the status of the Actions you initiate.


• SELECTED — An action is in progress.


When you have executed all entries in the release table successfully, press F3.

Apply SVC2031 to the Repository

Figure 8-14 applies the repository upgrade to the repository.

------------------------ HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT

---------------------- HOST INSTALLATION WORKBENCH ---------------------- COMMAND ===> PF3-END PF7-UP PF8-DOWN PROCESS INSTALLATION TABLE Type S or SEL in the Action column to process a release. Action Release Status ______ SVC2031


Installation Notes

Figure 8-14 Apply SVC2031 to Repository

This panel applies the repository upgrade to the repository in two optional steps. Select from the following options:

1. Capture Version Variables

2. Create/Submit Installation Jobs

Option 1 - Capture Version Variables

Capture Version Variables starts a group of panels in which you specify the requisite information for each version of a repository. The panels appear in Figure 8-15 to Figure 8-20. Handle these panels in the order they appear.

Option 2 - Create/Submit Installation Jobs

Create/Submit Installation Jobs is discussed after the six variables panels in Figure 8-16.


The next series of six panels capture repository variables needed to apply the repository upgrade to the CICS environment. The first of these panels is in Figure 8-15.

----------------------- HOST INSTALLATION WORKBENCH ---------------------- COMMAND ===> APPLY SVC2031 TO REPOSITORY repname OPTION ===> 1 Capture Version Variables 2 Create/Submit Installation Jobs X EXIT Enter END Command to exit. Press ENTER to continue.


Installation Notes

Figure 8-15 Capture Repository Variables—CICS environment (1 of 6)

Enter the information required by this panel.

400.2 Runtime Dataset Name Suffixes:

Enter the runtime data set name suffix.

400.2a Load Library Output - [Default: LOADCI]

Enter the load library output suffix, to a maximum of eight (8) characters.

400.2b NCAL Library Output - [Default: NCALCI]

Enter the NCAL library output suffix, to a maximum of eight (8) characters.

400.2c VSAM View Definition File - [Default: HPS001D1.VIEWDEF]

Enter the VSAM view definition file suffix.

400.2d VSAM Rule Source Output - [Default: HPS003D1.RULESRC]

Enter the VSAM rule source output suffix.

400.2e VSAM Rule Relation Output - [Default:HPS004D1.RLRELATN]

Enter the VSAM rule relation output suffix.

400.2f VSAM View Definition (PCNV) - [Default: HPS021D1.VIDTEXT]

Enter the VSAM view definition output suffix.

400.3 Runtime Dataset DDNAMES:

Enter the following DDNAMEs.

400.3a VSAM View Definition File - [Default: HPS001D1]

Enter the DDNAME for the VSAM view definition file.

400.3b VSAM Rule Source Output - [Default: HPS003D1]

Enter the DDNAME for the VSAM rule source output.

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> CAPTURE REPOSITORY VARIABLES - CICS environment - Version 1 Runtime Dataset Name Suffixes: Load Library Output ==> LOADCI NCAL Library Output ==> NCALCI VSAM View Definition File ==> HPS001D1.VIEWDEF VSAM Rule Source Output ==> HPS003D1.RULESRC VSAM Rule Relation Output ==> HPS004D1.RLRELATN VSAM View Definition (PCNV)==> HPS021D1.VIDTEXT Runtime Dataset DDNAMES: VSAM View Definition File ==> HPS001D1 VSAM Rule Source Output ==> HPS003D1 VSAM Rule Relation Output ==> HPS004D1 VSAM View Definition (PCNV)==> HPS021D1 Enter END command for previous page. Press ENTER to continue.


Installation Notes

400.3c VSAM Rule Relation Output - [Default: HPS004D1]

Enter the DDNAME for the VSAM rule relation output.

400.3d VSAM View Definition (PCNV) - [Default: HPS021D1]


The second of six panels capturing repository variables is in Figure 8-16.


Enter the information required by this panel:

400.4 CICS Runtime Library - [Default: CICS33.LOADLIB]

Enter the CICS runtime library name at your site.

400.5 CICS Macro Library - [Default: CICS.MACLIB]

Enter the CICS macro library name at your site.

400.6 CICS PL/I Library - [Default: CICS.PLILIB]

Enter the PL/I library name at your site.

400.7 CICS COBOL Library - [Default: CICS.COBLIB]

Enter the CICS COBOL library name at your site.

400.8 CICS ASM Translator - [Default: DFHEAP1$]

Enter the CICS ASM translator name at your site.

---------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> CAPTURE REPOSITORY VARIABLES - CICS environment - Version 1 CICS Runtime Library ==> CICS33.LOADLIB Include Runtime Library in Translator Steplib? (Y/N) ==> N CICS Macro Library ==> CICS.MACLIB CICS PL/I Library ==> CICS.PL1LIB CICS COBOL Library ==> CICS.COBLIB CICS ASM Translator ==> DFHEAP1$ CICS PL/I Translator ==> DFHEPP1$ CICS COBOL Translator ==> DFHECP1$ CICS C370 Translator ==> DFHEDP1$ Use HPS/CICS Autoinstall? ==> Y (Y/N) CEDA Transaction Name ==> CEDA CEMT Transaction Name ==> CEMT CICS Version ==> 4 CICS Release ==> 1 Enter END command for previous page. Press ENTER to continue.


Installation Notes

400.9 CICS PL/I Translator - [Default: DFHEPP1$]

Enter the CICS PL/I translator name at your site.

400.10 CICS COBOL Translator - [Default: DFHECP1$]

Enter the CICS COBOL translator name at your site.

400.11 CICS C370 Translator - [Default: DFHEDP1$]

Enter the CICS 3270 translator library name at your site.

400.12 Use HPS/CICS Autoinstall? (Y/N)

If Y is entered, AppBuilder software automatically makes the program and transaction definitions in the CICS region available during preparation of user rules and components. It will also process AppBuilder user VSAM files and update the AppBuilder incore table with the rule and its associated transid.

400.13 CEDA Transaction Name - [Default: CEDA]

Enter the CEDA transaction name used at your site.

400.14 CEMT Transaction Name - [Default: CEMT]

Enter the CEMT transaction name used at your site.

400.15 CICS Version - [Default: 4]

Enter the CICS version number used at your site.

400.16 CICS Release - [Default: 1]

Enter the CICS release number used at your site.

Complete this panel and proceed to the next.

The third of six panels capturing repository variables is in Figure 8-17.


Installation Notes



400.17 You may form CICS DB2 plan names by using the generated bitmap as the plan name prefix

or suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default:

B]

Specify how the generated bitmap is used in the CICS DB2 plan name.

400.18 Use AppBuilder Project name in CICS plan name? (Y/N) - [Default: N]

Specify if the AppBuilder project name is used in the CICS plan name.

400.19 If not, enter the string to use here: - [Default: PLNC]

If the AppBuilder project name is not used in the CICS plan name, enter the name to use.

400.20 Use the repository version number in plan name? (Y/N): - [Default: N]

Specify if the repository version number is used in the plan name.

400.21 Use the region type (‘C’) in the plan name? (Y/N) - [Default: N]

Specify if the region type is used in the plan name.

Complete this panel and proceed to the next panel which is used to capture repository variables (Figure 8-18).

-------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> CAPTURE REPOSITORY VARIABLES - CICS environment - Version 1 You may form CICS DB2 plan names by using the generated bitmap as the plan name prefix or suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix: ==> B Use AppBuilder Project name in CICS plan name? (Y/N) ==> N If not, enter the string to use here: ==> PLNC Use the repository version number in plan name? (Y/N) ==> N Use the region type (‘C’) in the plan name? (Y/N) ==> N Press END Command to Terminate. Press ENTER to Continue.


Installation Notes



400.22 INTERTEST (Supply these values if INTERTEST is installed):

Enter the following if INTERTEST debugging feature is installed in this region.

400.22a Intertest ASM Program - [Default: IN25SYMA]

Enter the ASM program name.

400.22b Intertest COBOL Program - [Default: IN25COB2]

Enter the COBOL program name.

400.22c Intertest PL/I Program - [Default: IN25SYMP]

Enter the PL/I program name.

400.22d Intertest PROTSYM Dataset - [Default: None]

Enter the PROTSYM data set name.

400.22e Intertest STEPLIB - [Default: None]

Enter the STEPLIB program name.

400.23 Minimum Transaction ID for this Version: - [Default: AAAA]

Enter the minimum transaction ID for this version.

400.24 Maximum Transaction ID for this Version: - [Default: AA99]

Enter the maximum transaction ID for this version.

400.25 Number of CICS Regions you want to configure for version 1 - [Default: None]

Enter the number of CICS regions you want to configure for repository version 1.

---------------------- HOST INSTALLATION WORKBENCH ---------------------- COMMAND ===> CAPTURE REPOSITORY VARIABLES - CICS environment - Version 1 INTERTEST (Supply these values if INTERTEST is installed): Intertest ASM Program ==> IN25SYMA Intertest COBOL Program ==> IN25COB2 Intertest PL/I Program ==> IN25SYMP Intertest PROTSYM Dataset ==> Intertest STEPLIB ==> Minimum Transaction ID for this Version: ==> AAAA Maximum Transaction ID for this Version: ==> AA99 Number of CICS Regions you want to configure for version 1 ==>>> The following two panels will be presented for each region requested to allow you to configure each region separately. Enter END command for previous page. Press ENTER to continue.


Installation Notes

The following two panels are presented for each region requested to allow you to configure each region separately. Complete this panel and proceed to the next. The fifth of six panels capturing repository variables is shown in Figure 8-19.



400.26 Enter the VTAM name of this region - [Default: None]

Enter the VTAM name of this region.

400.27 Enter the VTAM APPLIDs for LU2 processing: 1 - [Default: A06HPS1] 2 - [Default: A06HPS2]

3 - [Default: A06HPS3]

The AppBuilder LU2 CICS Auto-install feature allows AppBuilder objects (rules, components, etc.) to be automatically defined to CICS during AppBuilder preparation (compile, linkedit, etc.). Depending on the object being prepared, it will connect to CICS via the VTAM applids and execute the following transactions:

• HS06 - AppBuilder newcopy transaction

• CEDA - CICS transaction to define AppBuilder objects

• CEMT - CICS transaction to close and open AppBuilder VSAM files

• UTBL - AppBuilder transaction to add rule/tranid to AppBuilder incore table (HPSTBLE2)

Enter three VTAM application IDs.

400.28 Define HPS CICS group to the startup group list? (Y/N) - [Default: N]

Specify whether the AppBuilder CICS groups should be defined to the startup group list during a rule or component prepare.

---------------- HOST INSTALLATION WORKBENCH -------------------- COMMAND ===> CAPTURE REPOSITORY VARIABLES - CICS environment - Version 1 Enter the VTAM name of this region ==> Enter the VTAM APPLID’s for LU2 processing: 1 ==> A06HPS1 2 ==> A06HPS2 3 ==> A06HPS3 Define HPS CICS group to the startup group list? (Y/N)==> N Define HPS transactions during rule prepare? (Y/N)==> Y Should the HPS transaction UTBL be executed? (Y/N)==> Y Enter the startup group list name for HPS groups ==> HPS groups will be added to the startup list AFTER or BEFORE a specified group. Enter the specified group name here. ==> Enter A to add new groups AFTER this group or B for BEFORE ==> B Temporary groups will be built from a one-character prefix and the Userid. Specify the one-character prefix for temporary groups ==> H Enter END command for previous page. Press ENTER to continue.


Installation Notes

400.29 Define HPS transactions during rule prepare? (Y/N) - [Default: Y]

Specify if transactions are defined during a rule prepare.

400.30 Should the HPS transaction UTBL be executed? (Y/N) - [Default: Y]

Specify if the UTBL transaction should be executed during a rule prepare.

400.31 Enter the startup group list name for HPS groups - [Default: None]

Enter the startup group list name for AppBuilder groups.

400.32 HPS groups will be added to the startup list AFTER or BEFORE a specified group. Enter the

specified group name here. - [Default: None]

Enter the specified group name.

400.33 Enter A to add new groups AFTER this group or B for BEFORE - [Default: B]

Specify where the AppBuilder group will be added to the group named above.

400.34 Temporary groups will be built from a one-character prefix and the Userid. Specify the one-

character prefix for temporary groups - [Default: H]

Enter a one character prefix for temporary groups.


The last of six panels capturing repository variables is in Figure 8-20.



-------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> CAPTURE REPOSITORY VARIABLES - CICS environment - Version 1 REGION: CICS group names for HPS objects may be a constant string OR a constant string combined with the HPS project name. The combined length may not exceed 8 characters. If you use the project name in the group name, enter H if the HPS project should come first or C if the constant string should come first ==> H For PPT’s: Use HPS project name as part of the group name? (Y/N)==> Y Enter the optional string to use in the group name ==> HPS For PCT’s: Use HPS project name as part of the group name? (Y/N)==> Y Enter the optional string to use in the group name ==> HPS Enter END command for previous page. Press ENTER to continue.


Installation Notes

400.35 CICS group names for HPS objects may be a constant string OR a constant string combined

with the HPS project name. The combined length may not exceed 8 characters. [Default: H]

If you use the project name in the group name, enter H if the AppBuilder project should come first or C if the constant string should come first - [Default: H]

400.36 For PPTs:

Enter the following information for PPTs.

400.36a Use HPS project name as part of the group name? (Y/N) - [Default: Y]

Specify if the AppBuilder project name is used as part of the group name.

400.36b Enter the optional string to use in the group name - [Default: HPS]

Enter an optional string to use in the group name.

400.37 For PCTs:

Enter the following information for PCTs.

400.37a Use HPS project name as part of the group name? (Y/N) - [Default: Y]


400.37b Enter the optional string to use in the group name - [Default: HPS]


Complete this panel, and proceed to the next.


Figure 8-21 shows you returning to the panel you saw previously in Figure 8-14. This time you perform option 2 Create/Submit Installation Jobs.

Figure 8-21 Apply SVC2031 to Repository, Capture/Submit Installation Jobs

This panel applies the repository upgrade to the repository in two option steps. Select from among the following options:

1. Capture Version Variables

2. Create/Submit Installation Jobs

When you have completed option 1, perform option 2.

Option 2 Create/Submit Installation Jobs shows two jobs that you need to process, Figure 8-22.

----------------------- HOST INSTALLATION WORKBENCH -------------------- COMMAND ===> APPLY SVC2031 TO REPOSITORY repname OPTION ===> 1 Capture Version Variables 2 Create/Submit Installation Jobs X EXIT


Installation Notes


The next panel defines the repository jobs that install updates to your repository, as Figure 8-22 shows.


Execute the jobs in order from the top down. Select from the following actions:


• View (V or VIEW)



The following describes the repository jobs:

• REPJOB1 — NonDB2 processing. After this job completes, the following new data sets are created:

Note &REPQUAL is the Repository Modification Data Set Qualifier for AppBuilder data sets.

Table H-5 Repository Modification Libraries

&REPQUAL..LOADCI

Note &USRVQUAL is the System Data Set Qualifier for AppBuilder data sets. You have more than one set of the following data sets if you specified more than one version during the Enterprise Repository installation.

Table H-6 User Libraries

&USRVQUAL..LOADCI &USRVQUAL..NCALCI

Note &VSUVQUAL is the VSAM User Qualifier for AppBuilder VSAM data sets. You have more than one set of the following data sets if you specified more than one version during the Enterprise Repository installation.

Table H-7 User VSAM Data Sets

&VSUVQUAL..&VIEWDEF &VSUVQUAL..&RULESRC

&VSUVQUAL..HPS004D1.RLRELATN &VSUVQUAL..&VIDTEXT

&VSUVQUAL..HPS002D1.TESTDATA &VSUVQUAL..HPS006D1.ERRLOG

&VSUVQUAL..HPSBC1D1.BDCTDATA &VSUVQUAL..HPSBC2D1.BDCTTBL

------------------------- HOST INSTALLATION WORKBENCH --------------------- COMMAND ===> PF3-END PF7-UP PF8-DO UPDATE REPOSITORY SOFTWARE - REGENERATE/EDIT/SUBMIT INSTALLATION JOBS Repository ID: repname Release: SVC2031 Type REGEN in the Action column to regenerate a job. Type V in the Action column to view a job. Type SUB in the Action column to submit a job. Action Jobname Description Status ______ REPJOB1 NON-DB2 PROCESSING COMPLETED ______ REPJOB2 DB2 PROCESSING COMPLETED


Installation Notes

Refer to Chapter 5, “Installing the Enterprise Repository” in this document for additional information about AppBuilder data sets.

• REPJOB2 — DB2 PROCESSING

You can monitor each jobs progress in the Status column. The following lists indicators that are displayed in the Status column.




When you have competed these jobs successfully, press F3 to exit this panel. Return to the Apply Upgrade to Repository panel, Figure 8-23.

Activate Repository

After completing Figure 8-22, you have applied all the repository updates for SVC2031. Figure 8-23 activates the repository.

Figure 8-23 Activate Repository

This panel appears for you to select option 3 Activate Repository. This option concludes the installation of the CICS Online upgrade to your repository.

&VSUVQUAL..HPSDNART.RTABLE &VSUVQUAL..HPSDNAIN.INI

&VSUVQUAL..DNAFXFER

Note &VIEWDEFC, &RULESRCC, &RLRELATC, and VIDTEXTC are the values entered in prompt 400.3.

Table H-7 User VSAM Data Sets (Continued)

-------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 3 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT



Postinstallation NotesPerform the following steps to complete and verify the successful installation of the AppBuilder CICS Online Preparation Workbench and CICS Enterprise Server.

1. Refer to sample member AB2031C in &BASEQUAL..SVC2031.SAMPLE for required CICS definitions. This member contains all of the definitions that can be added via RDO or using the CICS utility DFHCSDUP. It has been created to support v1.3 of CICS Transaction Server, please note the comments contained within this member for pre-CICS_TS versions and other modifications required for site-specific naming standards (especially the file definitions for AppBuilder). For pre-CICS_TS you need to define macro definitions for the following:

a. Refer to sample AB2031CD in BASE&..SVC2031.SAMPLE for DCT definitions.

b. Refer to sample AB2031CR in &BASEQUAL..SVC2031.SAMPLE for RCT definitions.

2. Define the following libraries to the DFHRPL concatenation of the target AppBuilder CICS regions:

• &USRVQUAL..LOADCI

• &USRVQUAL..LOADBS

• &REPQUAL..LOADCI

• &MODQUAL..LOADCI

• &BASEQUAL..LOADCI

3. Define the member DFHPLT in &BASEQUAL..SVC2031.SAMPLE in the target AppBuilder CICS regions. The programs in this PLT set up the AppBuilder environment in the target CICS regions. These programs must execute during the third stage of initialization. Refer to “Configuring AppBuilder for a Multi-CICS Region Environment” for additional information.

• The HPSSTART PLT program issues the following:

START TRAN(‘ENAE’)

The transaction ENAE executes program HPSENAEP - Enable Exit Print program. The program loads HPSCGAP and HPSTBLE1 through 5 with the HOLD option. Then it loads HPSXZCAT, enabling the XZCAT attach exit in CICS, and stores the CICS version in HPSCGAP along with addresses of the incore tables.

• The HPESI19 PLT program issues the following:

START TRAN(‘HPI0’)

The transaction HPI0 executes program HPESI10 which controls the initialization of the AppBuilder Kernel. A number of control modules are loaded, including HPEGAPA along with HPSTBLE1 through 5, and, as with Converse, the CICS HOLD option is used. The table and

Note Please note that HPSENAEP and HPSXZCAT are defined with EXECKEY (CICS). The HPSENAEP program starts the HPSXZCAT exit program. In order to start the HPSXZCAT exit program, the HPSENAEP program must acquire a CICS GLOBAL Storage area that can be used by the HPSXZCAT exit program. In order to acquire and use the CICS GWA, the HPSENAEP and HPSXZCAT must execute in CICS Storage Key.

Note &USRVQUAL is the qualifier of your AppBuilder User Libraries. &REPQUAL is the qualifier of your AppBuilder Repository Modification Libraries. &MODQUAL is the qualifier of your AppBuilder Maintenance Libraries. &BASEQUAL is the qualifier of your AppBuilder System Libraries.



module addresses are stored in HPEGAPA along with the CICS version and other pertinent information,e.g., codepage.

• The DNAINIRD PLT program performs the initialization processing for the NetEssential product. The DNA.INI host variables are stored in a VSAM data set which is read during processing to set incore variables. Addressability for other required data sets is also performed at this point.

4. The sample member AB2031C in &BASEQUAL..SVC2031.SAMPLE contains sample entries for both LU2 and LU6.2 terminals, AppBuilder LU2 Auto-install terminals, and SNA SCS printers. For AppBuilder LU2 Auto-install, SNA SCS printers, and LU6.2 protocol, the VTAM definitions are noted below in the following items:

a. The following sample VTAM members in &BASEQUAL..SVC2031.SAMPLE must be defined if you plan to use the AppBuilder Auto-install feature.

MODSNA - this is the VTAM Logmode Table definition

M06HPS - this is the VTAM Application Definitions

5. Include the member HMPBTBL&V in &BASEQUAL..SVC2031.SAMPLE in the target AppBuilder CICS startup procedures or started tasks. If this cannot be included, make sure this job runs before CICS is brought up. The HMPBTBL&V member builds the HPSTBLE1 program and compiles and links the code. HPSTBLE1 is a table identifying the AppBuilder transaction IDs and rule names. (&V is the repository version number).

6. Member HPSPLAN in &BASEQUAL..SVC2031.SAMPLE is an optional plan exit logic to avoid defining a transaction and plan name for each application program. Review the member, making any necessary adjustments to the actual plan name (as described by the comments in the member) before implementing the member in each target CICS region. Use the sample member ASMLKCIC to assemble and link HPSPLAN.

7. Verify the country code and currency symbol in the programs HPSCGAP and HPEUCGP included in &BASEQUAL..SVC2031.SAMPLE, and change these appropriately. A description of these parameters is in member TXTCGAP. Assemble both programs to an object library that you will use during the link process. Then rerun the COPY1, COPY2, and COPY3 steps in the DSALLOC member found in the &INSTQUAL.AB2031.CNTL data set. This will place the correct version of the translate objects in the &BASEQUAL.OBJ data set. (This problem will be corrected in the next release so the translate objects will be delivered in the runtime products.) Then link edit HPSCGAP and HPEGAPA into your AppBuilder CICS load library using the link function accessed from the Host Installation Workbench System Functions menu. Be sure to insert the object library that you used for the compilation of HPSCGAP and HPEUCGP in the first position of the object library concatenation of the link job. The Sample JCL to assemble HPSCGAP and HPEUCGP is available in the member SKLCGAP. Please refer to Appendix D, “HPSCGAP, HPICGAP, HPEUCGP, and Sample Batch JCL” for more information about HPSCGAP and HPEUCGP.

8. You can use the DFHPEP3 and DFHZNEP3 programs in &BASEQUAL..SVC2031.SAMPLE for the target AppBuilder CICS regions. Use members LKCPEP3 and LKCZNEP3 for sample link cards.

9. The Default Repository and TIP (Test Installation Process) application should already be migrated into the Enterprise Repository. If not, refer to the postinstallation instructions in Chapter 5, “Installing the Enterprise Repository” of this document for the migration procedure.

10. Edit the CICS region INI member in &REPQUAL..INI and change the value of the CICSLNK variable from NORENT to RENT.

Note A transaction definition, NE3I, is supplied as part of the AB2031C sample CICS definition that allows this program to be executed from a CICS session. This will reload the VSAM data set information into core, and will typically be used when configuration changes are made.

Note Please ensure that you link and then load the modules in the following sequence: HPSCGAP first, then HPEGAPA.



11. Edit the @USRENV member in &REPQUAL..INI and change the value of the PCNV3270 variable from "N" to "Y".

12. Within the Enterprise Repository, make sure you are in the TIP project. If not, type PROJECTS at the command line. Select TIP for version 1.

13. Super Prepare TIP Cooperative process:

a. Next to the Rebuild Package entity, type ADDE (Add Entity) to add a Rebuild Package for TIP. Name the package whatever you like. Press F3 to save and return.

b. Next to Rebuild Package entity, type LE to list the Rebuild Package entities. Next to the Rebuild Package you just created, type ADDR (Add Relationship) to add the TIP cooperative process to the Rebuild Package for TIP. Select “Has-Root Process” in popup window, and press ENTER. Enter TIP_COOP_PROCESS as the “Has-Root Process” name. Press F3 to save and end.

c. Next to the Rebuild Package for TIP, type SUPERPR. A message states the job was submitted and displays the job number. Several jobs will be submitted at various times.

d. After the last job finishes, check the results be typing LISTRBD next to the Rebuild Package for TIP. Information will be displayed stating whether SUPERPR was successful or not. Press F3 to save and return.


1. Verify the TIP cooperative process has been prepared successfully in the Enterprise Repository.

2. Logon to AppBuilder CICS region.

3. Type HPR0 to display a list of rules for TIP. Select by entering a slash (/) next to each rule you want to test. Select break points if you want, and press F15 or Shift+F3 to continue. A message will display for each rule, stating whether it is successful or not.

• TIP_CICS_ASM_RULE

• TIP_CICS_ASMDB2_RULE

• TIP_CICS_COB_RULE

• TIP_CICS_COBDB2_RULE

• TIP_CICS_PLI_RULE *

• TIP_CICS_PLIDB2_RULE *

• TIP_DB2_RULE

• TIP_MVS_RULE

4. TIP should already be downloaded and prepared on the workstation. If not, refer to the Installation Verification instructions in Chapter 5, “Installing the Enterprise Repository” for the download and prepare procedures.

5. Execute the TIP application:

a. Refer to the workstation postinstallation instructions for the proper configuration and communications protocol for host logon.

b. Start the AppBuilder Execution Workbench on the workstation.

Warning You must complete step 10 and 11 for each version of the repository.

Note Items marked with an asterisk (*) are optional, only for testing PL/I components; do not execute these two rules if PL/I components are not used.



c. A menu appears with the TIP Function pulldown. Select the TIP Function pulldown menu, and then select TIP Cooperative Process. A window with pushbuttons appears. Click the mainframe pushbuttons to verify cooperative processing. Do not click the PL/I buttons if PL/I components are not used.

Verification of the AppBuilder CICS Online Preparation and CICS Enterprise Server (SVC2031) installation is now complete.

CICS 3270 Converse VerificationPerform the following steps for the postinstallation procedure:

1. Default Repository and TIP (Test Installation Process application) should already be migrated into the Enterprise Repository. If not, refer to the postinstallation instructions in Chapter 5, “Installing the Enterprise Repository” for the migration procedure.

2. Within the Enterprise Repository, make sure you are in the TIP project. If not, type PROJECTS at the command line. Select TIP for version 1.

3. Make sure the TIP Cooperative process was prepared successfully. If not, refer to Chapter 8, “Installing CICS Online Preparation Workbench and Enterprise Server” postinstallation instructions.

4. Next to the Window Entity, type LE to list the window entities.

5. Next to the TIP_PCCICS_DRIVER_WINDOW entity and the TIP_PCCICS_WINDOW entity, type PR to prepare those two entities. After the job finishes, type RES next to each to check successful preparation. Press F3 to return.

6. Next to the Rule Entity, type LE to list the rule entities.

7. Next to the TIP_PCCICS_DRIVER_RULE entity and the TIP_PCCICS_RULE entity, type PR to prepare those two entities. After the job finishes, type RES next to each to check successful preparation. Press F3 to return.

CICS 3270 Converse Verification Using TIP

1. Verify that the TIP CICS 3270 Converse entities have been prepared successfully in the Enterprise Repository.

2. Logon to AppBuilder CICS 3270 Converse region.

3. Type the following transaction to display the text portions of the window only:

HPC7,WTPCDVR

4. To execute the TIP CICS 3270 Converse application, enter its assigned transaction code. Determine the assigned transaction code for the TIP rule TIP_PCCICS_DRIVER_RULE by entering ME next to the TIP_PCCICS_DRIVER_RULE rule in the Enterprise Repository. The transaction code is listed next to the attribute CICS/IMS transaction ID. Execute each of the PF (function) keys displayed on the window or screen.

Note The following steps will need to be done for each version in the repository you are verifying.

Note Do not execute the PF keys assigned to test PL/I components if you do not use PL/Icomponents.


Installing TCP/IP Listener for IBM CICS

5. Verification of AppBuilder CICS 3270 Converse Preparation and CICS 3270 Converse Client (release CVC531) installation is now complete.

Installing TCP/IP Listener for IBM CICSAlthough it is not typically part of the installation, you can install the TCP/IP Listener for IBM CICS using the instructions in this section. This installation is optional and only applies to specific customers.

The TCP/IP Listener for IBM CICS enables AppBuilder rules for IBM OS/390 CICS to communicate over TCP/IP with AppBuilder communications programs on other platforms. This topic describes how to install the product in an IBM OS/390 environment.

• Meeting Software Requirements

• Performing Post-Installation Steps

Meeting Software RequirementsThe installation requires that some NetEssential modules be linked non-reentrant, as specified in section 7.3 of the TCP/IP V3R2 for MVS: CICS TCP/IP Socket Interface Guide and Reference published by IBM.

These modules are:

• DNALSTNR

• HPSDNA00

The TCP/IP Listener for IBM CICS has the following software requirements:

• TCP/IP V3R2 for MVS: CICS TCP/IP Socket Interface. You can verify the version by running the TSO command NETSTAT. The EZA0217I message displays the version. Successful execution of the CICS transaction EZAO indicates that the CICS TCP/IP Socket Interface has been installed.

• NetEssential client authentication exit. Samples are shipped with AppBuilder. See the Configuring Communications Guide for details.

The Listener uses the CICS VERIFY command to validate the end user’s CICS user ID and password. You use the Security Node or client authentication exit to pass the user information to CICS from the client. You can also bypass the CICS VERIFY by coding a DNAINI parameter. See DNAINI Settings for details.

Performing Post-Installation StepsPerform the following steps after the installation is complete:

STEP 1 - Define the NetEssential resources to CICS

The samples provided in this section contain the necessary program, transaction, files, and definitions for CICS.



Sample - Define the program DNALSTNR to the CICS region

DEFINE PROGRAM(DNALSTNR) GROUP(nnnnnnnn)DESCRIPTION(NETESSENTIAL TCP LISTENER)LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)USELPACOPY(NO) STATUS(ENABLED) CEDF(YES)DATALOCATION(ANY) EXECKEY(CICS) EXECUTIONSET(FULLAPI)

Sample - Define a listener transaction with any valid transaction ID

DEFINE TRANSACTION(tranid) GROUP(nnnnnnnn)DESCRIPTION(NETESSENTIAL TCPIP LISTENER)PROGRAM(DNALSTNR) TWASIZE(0) PROFILE(DFHCICST)STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(CICS)DYNAMIC(NO) PRIORITY(255) TCLASS(NO) DTIMOUT(NO)INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO)DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)

Note that the NetEssential TCP/IP Listener program and transaction ID must be defined with EXECKEY(CICS). If it is not and storage-protection is enabled, the transaction will fail with an ASRA abend code indicating an incorrect attempt to overwrite the CDSA by EZACIC01. In addition to storage-protection being disabled, if the EZA* resources are defined with EXECKey=USER, DNALSTNR can also fail.

You can rename the NetEssential TCP/IP Listener transaction to conform to your environment standards. Do not forget to create a EZAC configuration record for the new transaction ID.

Note that if the last (fourth) character of the Listener’s transaction ID is 'L', when the Listener is started with the EZAO transaction, it will be started and execute under a separate TCB.

STEP 2 - Define the listener transaction(s) to the CICS Socket interface

Use the IBM-supplied EZAC transaction to create a configuration record for each Listener transaction. If you use multiple TCP/IP Listeners for IBM CICS applications, be sure to assign each a unique transaction ID and port number. Define the transaction IDs to the DNALSTNR program and configure the port numbers for the CICS region. For details on the EZAC transaction, refer to the CICS TCP/IP Socket Interface Guide and Reference.

Configuration Record Fields

The NetEssential Listener uses the following EZAC configuration record fields:

APPLID and TRANID are used to identify (are the keys to) the Listener's record. In the APPLID field, specify the name of the CICS region and in the TRANID field, specify the Listener’s transaction ID.

NUMSOCK is the maximum number of connections used in the INIAPI() call (including those that are pending to be taken and those that are to be read) that the Listener will handle. When reached, the Listener will not process any new connection requests until one of the existing sessions terminates. Messages are displayed when the MAXSOCK condition is reached and when MAXSOCK is no longer valid.

The current limitation for a CICS C program, such as the Listener, is 255. It can also be limited by the SOMAXCONN value from the TCPIP configuration file <profile.tcpip> for the system. The value used is 255, unless SOMAXCONN is less than this value.



Note that this is not the maximum number of started rule transactions, it is only the maximum number of concurrent sockets the Listener can handle. Once they are taken by the rule transaction and closed by the Listener, they are no longer charged to the Listener.

The number of concurrent CICS transactions using the Sockets’ interface is specified in the NTASKS parameter in the EZAC CICS record. NTASKS specifies the number of reusable MVS subtasks to be allocated. This should be the highest number of concurrent CICS transactions that will use Sockets’ interface, excluding the Listener(s).

ACCTIME specifies the timeout used in the SELECT() API call when the Listener waits for socket activity. "Activity" can be either a new connection request where data is available on an already accepted or started connection, or the rule transaction has taken the socket. During this time, the Listener is in a wait state and cannot check for shutdown requests or process any other timeouts, such as GIVESOCKET.

A larger value reduces overhead but may increase the time it takes for the Listener to detect a shutdown request because the call is not interrupted for such requests. The default value is 60 seconds.

GIVTIME specifies the GIVESOCKET timeout. The Listener attempts to pass the socket to the started rule transaction by issuing a GIVESOCKET. If the GIVTIME expires before the rule takes the socket (TAKESOCKET), the Listener issues an error message and closes the socket. Note that this process is not exact because the Listener does not set GIVESOCKET timers, but during each SELECT cycle, as defined in ACCTIME, expired GIVESOCKET timeouts are checked.

WLM groups are used to register the service with WLM and are passed “as is” to EZACIC12 (the WLM De-/Registration module).

Other fields in the EZAC Configuration record are used by the Listener, such as:

PORT specifies the port number the listener will use.

IMMEDIATE - A value of YES indicates that the Listener is to be automatically started when the CICS Sockets interface is started.

BACKLOG specifies the depth of the backlog queue or number of connection requests used in the LISTEN() call that will queue for the Listener to accept. Specify the value depending on whether it is more desirable to have the client wait for the listener or for the connection request to fail and retry. It works in conjunction with the NUMSOCK parameter.

STEP 3 - Configure the NetEssential runtime options

NetEssential is highly configurable. Some parameters are specified with the CICS Sockets EZAC configuration record, as described in Configuration Record Fields. Most configuration parameters are specified with DNAINI settings. Use the NEAD transaction to update the NetEssential initialization file (DNAINI). Select option 2 ‘Initialization File’ from the main menu and add or modify the settings.

In most cases, the Listener reads the configuration settings once, at startup. Therefore, the Listener should be restarted in order to read modifications to the settings. Use Option 6 (Cache Initialization File) on the Operations menu (Option 1 ‘Operations’ from the main menu) to activate (re-cache) the changes to the initialization file.

Note After creating new records, the CICS Sockets interface must be restarted to pick up the new definition. Use the EZAO transaction to stop and restart the sockets interface.



It is recommended that you specify keywords and their values even when using default values because the DNAINI settings are cached in order to improve performance. However, when an entry is not in the cache, NetEssential will issue a physical I/O request in an attempt to read it from the file. For example, every rule transaction must check for an OpenCOBOL environment, so it will always attempt to access the OPEN-COBOL /ENABLED setting. See DNAINI Settings for a list of the settings.

STEP 4 - Start the CICS Socket Interface

Use the EZAO transaction to re-start the CICS TCP/IP Socket Interface, as described in TCP/IP V3R2 for MVS: CICS TCP/IP Socket Interface Guide and Reference published by IBM.

For example, to stop the CICS Sockets interface issue the following command:

EZAO,STOP,CICS

Use the following command to start the CICS Sockets interface:

EZAO,START,CICS

STEP 5 - Starting the Listener

All the TCP/IP Listeners configured to start automatically (IMMEDIATE=YES. See STEP 2 - Define the listener transaction(s) to the CICS Socket interface) will be started as a result of successfully starting the CICS Sockets interface (EZAO,START,CICS). All other Listeners must be manually started using the EZAO transaction. For example:

EZAO,START,LIST(NETL)

where NETL is the Listener’s transaction ID. Use the TSO command NETSTAT to verify the start of the Listener.

STEP 6 - Routing service requests to the CICS region

Use the NetEssential Configurator on the client workstation to route service requests to the CICS region over TCP/IP. Note that you need to specify the CICS transaction ID of the NetEssential execution server, not the listener, in the Server ID field.

Usage NotesWhen using the CICS Listener in an MRO/Sysplex environment, TCP/IP should be installed in the front-end running the Listener transaction; and in any back-end region running AppBuilder transactions.

Before using the CICS Listener with MRO/Sysplex, the fixes m117077a and m119439a must be applied. When a RPC call is received, the front-end CICS looks at the message sent by the client and passes the socket opened by the client request to the back-end CICS, which receives the message and calls the rule requested and sends the reply.

The BACKLOG parameter for the port should be adjusted depending on the transaction load, using the EZAC transaction. Symptoms of the value being too low can be communication errors with tcpip protocol error code 10060.

Warning A CICS Sockets restriction requires all regions in question to be in the same LPAR.



DNAINI SettingsThe following is a list of the available DNAINI settings used to configure the NetEssential TCP/IP parameters. Note that there are other required generic settings.

• TCP/IP Port Number

• Security Authentication

• Session Termination Semantics

• TCP/IP Listener Abend Handler

• DoS Prevention

• NetEssential Tracing

TCP/IP Port Number

We strongly recommend maintaining an EZAC configuration record; however, if none exists, the Listener may attempt to use the value specified for the TCP_PORT_NUMBER variable in the DNA_SERVER section. You can add it with a value of nnnn, where nnnn is the port number assigned to the CICS region. For example:

Security Authentication

Add the variable LISTENER_SECURITY to the new MVS_LISTNER section. This variable determines how the Listener authenticates the provided user credentials.

The valid values are:

• YES – issues a CICS VERIFY on the user ID and password and starts the rule using the user ID.

• NO - No security check is done in the Listener.

• PART - the user ID and password are not checked but the rule is started with the user ID.

For example:

Session Termination Semantics

There are numerous enhancements in NetEssential regarding session termination semantics. These enhancements provide control over session termination processing and are implemented with two DNAINI settings:

where nnn is the timeout value, specified in seconds. The values for these variables may be different.

After sending the last response to the client, the CICS service (NetEssential) closes the connection. This can be done in any of the following ways:

DNA_SERVER TCPIP_PORT_NUMBER nnnn

MVS_LISTENER LISTENER_SECURITY YES

DNA_SERVER TCPIP_CLOSEWAIT nnn

DNA_SERVER TCPIP_LINGERTIME nnn



1. Issue a CLOSE() for the socket.

2. Issue a SELECT with a timeout as specified for TCPIP_CLOSEWAIT, and after either receiving data (the close indication) from the client or when the timeout expires, issue a CLOSE() for the socket.

3. Issue a blocking RECV() and after receiving data (the close indication) from the client, issue a CLOSE() for the socket.

This behavior is determined primarily according to the value of TCPIP_CLOSEWAIT:

• If the TCPIP_CLOSEWAIT timeout is not specified or is empty - Do NOTHING (option 1).

• If the TCPIP_CLOSEWAIT timeout is a positive number - Issue a SELECT (option 2).

• Else (TCPIP_CLOSEWAIT timeout is invalid, negative or zero) - Issue a blocking RECV (option 3).

Regardless of the SELECT/RECV, you can also optionally specify a LINGER time.

• If the TCPIP_LINGERTIME is a positive number - Set SO_LINGER to TCPIP_LINGERTIME.

• Else only in the event of SELECT/RECV errors - Set SO_LINGER to default (5 seconds).

If the SELECT timeout or setting blocking mode (IOCTL) fails, SO_LINGER will always be set. If a valid value is not specified, SO_LINGER is set to the default value (5 seconds).

To disable the Linger option, specify a LingerTime of 0 (zero); SO_LINGER will not be set.

TCP/IP Listener Abend Handler

It may be required to perform some clean-up operation, such as WLM de-registration, in the unexpected case of a Listener Abend. This would need to be done in an external abend handler program. A sample program, DNAABEND, is provided in both source (C) and object format that performs WLM de-registration.

To activate the Abend Handler for the NetEssential TCP/IP Listener, specify DNAABEND as the value for the TCPIP_ABENDPROGRAM variable in the DNA_SERVER section. For example:

The Listener checks the value and issues a 'HANDLE ABEND PROGRAM(DNAABEND)' if it is not empty.

Setting Up the Sample

The source is standard C and does not have any special compiler requirements. It contains EXEC CICS statements and needs to be translated by the CICS C translator. When linking (binding), the CICS TCP/IP module must be included.

The Linkage-Editor cards might be similar to the following entries:

INCLUDE OBJLIB(DNAABEND) INCLUDE SYSLIB(EZACIC07) INCLUDE SYSLIB(DFHELII) INCLUDE SYSLIB(DFHCPLC) INCLUDE SYSLIB(DFHCPLRR)

Note In the event of SELECT/RECV errors, SO_LINGER will not be set.

DNA_SERVER TCPIP_ABENDPROGRAM DNAABEND


Configuring AppBuilder for a Multi-CICS Region Environment

NAME DNAABEND(R)

The program must be defined to CICS as a C program.

DoS Prevention

In order to defend against DoS attacks, the NetEssential CICS TCP/IP Listener incorporates an "emergency brake". It consists of a configurable timeout and the Listener will issue an error message and close the socket if it expires before data is received.

The desired timeout value in seconds is specified with a DNAINI setting:

NetEssential Tracing

NetEssential has a tracing feature that can be used in a test environment or to troubleshoot problems. The level of trace output is specified with the DEBUGLVL variable in the TRACING section. In the same section, HPSCATS specifies the CICS file (DD) name that points to the VSAM error message text file. The name does not have to be DNAERROR, any valid CICS name is acceptable.

where n can be one of the following values, either numeric or text (as-is):

• 0 - ERRORS = report only ERROR + status view

• 1 - ERRORS_AND_LENGTHS = report level 0 + additional messages + data lengths

• 2 - ERRORS_AND_DATA = report level 1 + contents of input/output data

3 - ERRORS_AND_TRACES = report level 2 + internal tracing.


This section describes how to configure your AppBuilder/CICS Runtime environment for Multi-CICS Region support with a single Terminal Owning Region (TOR) and a single Application Owning Region

Note The Abend Handler (DNAABEND) program's definition must match that of the Listener. For example, if the Listener transaction is defined as TASKDATAKEY(CICS), the Abend Handler program's definition must specify EXECKEY(CICS) or An 'AEZD' abend will occur if not.

Note During the timeout period, the Listener will probably consume CPU cycles, as there is always "data" waiting to be processed. However, other connections, existing and new requests, will be processed.

DNA_SERVER SERVER_RECV_TIMEOUT nnn

Note Use caution when specifying the timeout value. Ensure that is takes into account the slowest network connection, yet keep it as low as possible to avoid unnecessary CPU cycles.

TRACING DEBUGLVL n

TRACING HPSCATS 0:DNAERROR



(AOR). It is assumed that the TOR will be used solely to support terminals and the AOR will be used to support the execution of all AppBuilder applications.

AppBuilder Repository CICS Load LibrariesThe AppBuilder Repository CICS Load Libraries are:

• &USRVQUAL..LOADCI


• &REPQUAL..LOADCI

• &MODQUAL..LOADCI

• &BASEQUAL..LOADCI

These libraries must be added to the DFHRPL concatenation of both the TOR and AOR CICS Regions in the order listed above.

AppBuilder CICS VSAM FilesOnly the HPS006D1.ERRLOG VSAM file needs to be defined to the TOR. This ERRLOG file can be unique from the ERRLOG file defined to the AOR or can be the same file by being remotely defined to the TOR and locally defined to the AOR. All AppBuilder/CICS files must be defined to the AOR.

AppBuilder/CICS Transient Data QueuesOnly the HPEL Error Log Transient Data Queue needs to be defined to the TOR. All AppBuilder/CICS Transient Data Queues must be defined to the AOR.

AppBuilder/CICS TransactionsThe following AppBuilder/CICS Transactions must be defined locally to the TOR:

• ENAE - Enable AppBuilder/CICS environment

• HPEL - Log AppBuilder/CICS Error Messages

• UTBL - Update HPSTBLE2 incore table

• HPI0 - Initialize AppBuilder Kernel

• NE2I - Initialize NetEssential middleware

All other AppBuilder/CICS Transactions must be defined as remote transactions to the TOR so that they can be Transaction Routed to the AOR. All AppBuilder/CICS Transaction must be defined to the AOR.



AppBuilder/CICS Programs

The HPSSTART, HPESI10, and HPSINIRD programs must be placed in the Program List Table Post Initialization (PLTPI) for both the TOR and the AOR.

• HPESI10

• HPSCGAP

• HPSENAEP

• HPSERRLG

• HPSINIRD

• HPSLMSG

• HPSSTART

• HPSTBLE1

• HPSTBLE2

• HPSTBLE3

• HPSTBLE4

• HPSTBLE5

• HPSUTBL

• HPSXZCAT

AppBuilder/CICS TerminalsThe AppBuilder LU2TYPE terminals that are used to support the Batch interface (the AppBuilder Auto-install feature) must be defined locally to both the TOR and the AOR.




CHAPTER

9 INSTALLING IMS ONLINE PREPARATION WORKBENCH AND ENTERPRISE SERVER


The information in this section describes the detailed requirements and procedures for installing an IMS Online Preparation Workbench and enterprise server.

PrerequisitesThe following AppBuilder software is required prior to the installation:


• AppBuilder Enterprise Repository

Complete the checklists and worksheets provided in Chapter E, “Hardware and Software Checklists” and Chapter J, “IMS Online Preparation Workbench and Enterprise Server Customization Worksheets” before proceeding with this installation.






Installation Notes

Installation NotesThis section contains the following hierarchy of panels for installing the IMS Online product

1—System functions


Update system software

Option 1, Unload installation data sets

Option 2, Continue

Create system upgrade jobs

Confirm update job submission

Regenerate/edit/submit installation jobs

SYSJOB2, Set tape backup parameters

SYSJOB4, Capture system variables

2—Repository functions


Apply upgrade to repository

Option 1, Create installation table

Upgrade repository

Option 2, Process installation table

Selecting an installation table to process

Apply SVI2031 to repository

Option 1, Capture version variables

Capture version variables (4 panels)

Option 2, Capture/submit installation jobs


Option 3, Activate repository

Installing IMS Online Preparation and Enterprise ServerThere are two parts to installing the AppBuilder IMS Online product option: “Option 1 - System Functions” and “Option 2 - Repository Functions”. Use the panel in Figure 9-1 to navigate to both parts through the Host Installation Workbench—Workbench Functions.

9-2 Installing IMS Online Preparation Workbench and Enterprise Server

Installation Notes

Figure 9-1 Host Installation Workbench Functions

The Workbench Functions panel is the starting point for installing system and repository functions. You must apply the system functions prior to the repository functions:

Option 1, System Functions—see “Option 1 - System Functions”.

Option 2, Repository Functions—see “Option 2 - Repository Functions”.

Before installing option 2, you must complete option 1 and perform four preparation steps described at the beginning of “Option 2 - Repository Functions”. However, you can apply the system functions (option 1) for all products before starting to install the repository functions (option 2).

Option 1 - System FunctionsSystem functions are those installation processes you start when you choose option 1 System Functions in Figure 9-1. This option lets you apply the system upgrade for IMS Online.


1. When you install the IMS Online product system functions, select 1 System Functions in Figure 9-1. The System Functions panel opens (Figure 9-2).


Installation Notes

Figure 9-2 System Functions Main



2. Enter the ID of the system to be upgraded.

3. Press Enter to advance to the panel selected.


5. The next panel opens (Figure 9-3) to begin the installation of the system functions.


Figure 9-3 begins the installation of the system software, starting with unloading the data sets.

Figure 9-3 Update System Software

Updating system software involves the unloading of the installation data sets required for the system installation. In Option 1, Unload installation Data sets, you enter the data needed to create the unload


Installation Notes

JCL. In Option 2, Continue, you activate the actual unloading of the data from tape to your system. Before selecting the options, provide the following information.

1. Release: [Default: SVI2031] Enter SVI2031, the release number for this system upgrade. This number is on the packaging list provided with the tape.

2. Unit: [Default: CART] Enter the name of the unit used to read your AppBuilder tape.

3. Tape Vol Serial Number: [Default: None] Enter the tape volume serial number for the tape. This number is on the packaging list provided with the tape.

Option 1 - Unload installation data Sets

Select option 1 Unload installation data sets to display job card information. Review the data and submit it. Check the output of execution and confirm it contains these three data sets with installation software:

• &instqual..&SVI2031.CNTL

• &instqual..SVI2031.ICLIST

• &instqual..SVI2031.IPANELS

• &instqual..SVI2031.ISKELS

where &instqual is the installation data set qualifier. Refer to Chapter 5, “Installing the Enterprise Repository” in this document for additional information about AppBuilder data sets.

Option 2 - Continue

Select option 2 in Figure 9-3 to continue the system software installation. Press Enter to continue to the next panel.


Figure 9-5 appears the first time you perform this installation. The panel shown in Figure 9-4 is optional; the first time you apply a system upgrade, it does not appear, but it does in subsequent passes. Its text says that the installation tables are already generated; consequently, do not generate them again unless you have introduced some change requiring another generation pass.


Installation Notes

Figure 9-4 Create System Upgrade Jobs

.

Under normal circumstances, select N (No) and proceed. If you want to begin the installation again with the first job, select Y (Yes). This action resets the status of the jobs but does not regenerate them. The status is reported in the Regenerate/Edit/Submit Installation Jobs panel shown in Figure 9-6.

Depending on your response, regeneration either occurs or does not occur. Regenerating the table clears the status of any jobs that are ‘SUBMITTED’ or ‘COMPLETED’. On successful completion of either choice, you are ready to update the system software. The panel in Figure 9-4 appears only if you have already applied a system upgrade to this system.


When the regeneration is completed, Figure 9-5 opens, confirming the update of your job submission.

Figure 9-5 Confirm Update Job Submission

------------------------- HOST INSTALLATION WORKBENCH ----------------------- COMMAND ===> CREATE SYSTEM UPGRADE JOBS The jobs to upgrade this system have already been generated. To complete the installation using the existing jobs, enter N below. To recreate the the table and begin the installation again, enter Y below. Note that you may encounter difficulty in attempting to rerun jobs which have already been completed. Do you want to regenerate the installation table? (Y/N)==> Enter END command to exit. Press ENTER to continue.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> UPDATE SYSTEM SOFTWARE - CONFIRM UPDATE JOB SUBMISSION System ID to be Updated: Release: SVI2031 This job will update your System Software, but you have not made a backup. If you proceed, you will be unable to backout this PTF later on. If you wish to proceed anyway, enter Y below. Otherwise enter N below to return to the UPDATE SYSTEM SOFTWARE - REGENERATE/EDIT/SUBMIT JOBS panel. Do you want to proceed without a backup?(Y/N)==> Enter END command for previous screen. Press ENTER to continue.


Installation Notes

The panel notifies you that no backup has been made. Under normal circumstances, select N (No) and proceed with the backup procedure. If you have a strong reason for not backing up the installation, press Y (Yes).

After this selection, the Regenerate/Edit/Submit panel appears.


Figure 9-6 provides the controls to regenerate, view, and submit installation jobs. Figure 9-6 shows the panel that controls the actual unloading, backing up, copying, linking, and restoring of installation data set.


Perform the appropriate steps top down. You can unload the tape, back up to tape or DASD, link the load modules, and copy the results to system data sets, or restore the data sets, if you are not satisfied with the results. Monitor the unload progress in the Status column and in additional panels that alert you of specific situations.

The following actions are supported:


• View (V or VIEW)


You must perform SYSJOB1, 4, and 5; the other steps are optional. The system jobs are described in the following section:


Proceed with the unload process. You can view, regenerate, or submit the job for execution. The data sets listed in Table 9-1 are unloaded by SYSJOB1.

Note You cannot backup the existing system later. It is recommended that you back up your installation.


Installation Notes


When you regenerate or submit SYSJOB1, and then submit SYSJOB2, the panel in Figure 9-7 opens.

Figure 9-7 Set Tape Backup Parameters




4. Specify the required tape backup information, and press Enter to activate these parameters. The backup process executes, and you return to the panel in Figure 9-6.





Table 9-1 Data Sets Unloaded or Created by SYSJOB1

&BASEQUAL.SVI2031.HPSDNAER &BASEQUAL..SVI2031.MFSSRCE

&BASEQUAL.SVI2031.HPSDNAIN &BASEQUAL..SVI2031.NCALIM

&BASEQUAL.SVI2031.HPSDNART &BASEQUAL.SVI2031.OBJ

&BASEQUAL..SVI2031.IMSRES &BASEQUAL.SVI2031.PRELINK

&BASEQUAL..SVI2031.IMSVSAM &BASEQUAL..SVI2031.PLKOBJ

&BASEQUAL..SVI2031.LKIMEC &BASEQUAL.SVI2031.PSBSRCE

&BASEQUAL..SVI2031.LKIMEN &BASEQUAL.SVI2031.SAMPLE

&BASEQUAL..SVI2031.LKIMUC &BASEQUAL..SVI2031.SAMP255

&BASEQUAL..SVI2031.LKIRNC &BASEQUAL..SVI2031.SAMP80

&BASEQUAL..SVI2031.LOADIM &BASEQUAL..SVI2031.VIDTEXT

&BASEQUAL..SVI2031.LOADLIB &BASEQUAL.SVI2031.DBDSRCE

&BASEQUAL.SVI2031.DBRMLIB &BASEQUAL.SVI2031.DDL

&BASEQUAL.SVI2031.DDLVSAM &BASEQUAL.SVI2031.LKBS00

&BASEQUAL.SVI2031.PCKGBASE &BASEQUAL.SVI2031.PCKGRANT

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> SET TAPE BACKUP PARAMETERS System ID to be Updated: sysname Release: SVI2031 Enter UNIT ===> CART Enter Volser ===> NONE Enter Retention Period ===> 30 Enter END Command to Terminate, Enter HELP for help panels.


Installation Notes

Figure 9-8 Capture System Variables.


This panel is a major control panel for the repository functions update. Its options are:

600.1 IMS RESLIB -[Default: SYS1.RESLIB]

Enter the qualified name of the IMS resident library used to link AppBuilder modules.

600.2 IMS CSSLIB - [Default: SYS1.CSSLIB]

Enter the qualified name of the CSS library used to link AppBuilder modules to support LU6.2 processing for AppBuilder’s NetEssential middleware.

When you have specified these variables, press Enter. You return to the panel in Figure 9-6.


When the load modules are linked successfully, copy the modules to the system data sets. After this job completes the data sets in Table 9-2 and Table 9-3 are created or updated.


Installation Notes

• SYSJOB6 — Restore data sets from tape


BluePhoenix Solutions recommends that you use the View or REGAN action on SYSJOB6 or SYSJOB7 at this time in order to create the job for later use, if necessary.




Table 9-2 System Libraries created or updated by SYSJOB5

&BASEQUAL..ACBLIB &BASEQUAL..DBDSRCE

&BASEQUAL..DBDLIB &BASEQUAL..HPSDNAER

&BASEQUAL..DBRMLIB &BASEQUAL..SAMPLE

&BASEQUAL..HPSDNAIN &BASEQUAL..SAMP80

&BASEQUAL..HPSDNART &BASEQUAL..SAMP255

&BASEQUAL..LKIMEC &BASEQUAL..LKIMEN

&BASEQUAL..LKIMUC &BASEQUAL..LKIRNC

&BASEQUAL..LKBS00 &BASEQUAL..LOADLIB

&BASEQUAL..LOADIM &BASEQUAL..MFSSRCE

&BASEQUAL..NCALIM &BASEQUAL..PSBLIB

&BASEQUAL..PSBSRCE &BASEQUAL..IMSVSAM

&BASEQUAL..OBJ &BASEQUAL..PCKGRANT

&BASEQUAL..PCKGBASE &BASEQUAL..PRELINK

&MODQUAL..ACBLIB &MODQUAL..DBDLIB

&MODQUAL..DBDSRCE &MODQUAL..LOADIM

&MODQUAL..MFSSRCE &MODQUAL..NCALIM

&MODQUAL..PSBLIB &MODQUAL..PSBSRCE

Note &BASEQUAL is the System Data Set Qualifier for AppBuilder data sets.

Note &MODQUAL is the Maintenance Data Set Qualifier for AppBuilder data sets.

Note Before submitting SYSJOB5, change the following data set names in steps entitled SAMPLE, SAM80, and SAMP255:change BASEQUAL.SVC2031.SAMPLE to BASEQUAL.SVI2031.SAMPLEchange BASEQUAL.SVC2031.SAMP80 to BASEQUAL.SVI2031.SAMP80change BASEQUAL.SVC2031.SAMP255 to BASEQUAL.SVI2031.SAMP255



Installation Notes

The following lists indicators are displayed in the Status column:




When this panel completes successfully, you have completed the System Functions installation. Return to the starting panel by typing X and pressing Enter or by pressing F3 repeatedly. You return through the hierarchy of installation windows to the Workbench Functions panel in Figure 9-1.

Having successfully completed the “Option 1 - System Functions,” you can either:

a. Continue the installation of this software by completing the option 2—Repository functions installation

or

b. Install the system portion of other AppBuilder software. Refer to installation instructions of specific software for more information—for example, Chapter 5, “Installing the Enterprise Repository” in this document. You would then complete the “Option 2 - Repository Functions” for each piece of software.

Option 2 - Repository FunctionsRepository functions are those installation processes you start when you choose option 2, Repository Functions in Figure 9-1. This option lets you apply the repository upgrade for IMS Online.

These steps are standard requirements for installing an IMS application. However, it is recommended you use existing IMS JCL procedures already available at the installation site. See “Preparation Step 3—Application Control Block Generation” for important information on target libraries.

Preparation Step 1—DBD Generation

Perform an IMS DBDGEN for each of the AppBuilder database descriptors (DBD) source members in &DBDSRCE.

Use the standard DBDGEN utility supplied in your installation’s library and modify as required. In the supplied DBD source, you may need to change the DEVICE=xxxx in the DBD statement to suit your local environment.

Note If you choose option a, ensure that all software is installed in the proper order.


Note You must perform the following four steps after installing the system functions, and before installing the repository functions.


Installation Notes

Preparation Step 2—Program Specification Block Generation

Perform an IMS PSBGEN for each of the AppBuilder PSB source members in &BASEQUAL..SVI2031.PSBSRCE.

Use the standard PSBGEN utility supplied in your installation’s library and change as required.

Preparation Step 3—Application Control Block Generation

Perform an IMS ACBGEN for each of the online application PSBs in &BASEQUAL..SVI2031.PSBSRCE. Use the standard ACBGEN utility supplied in your installation’s library and modify as required. A sample job to perform the ACBGENs for all AppBuilder PSBs and databases is provided in &BASEQUAL..SVI2031.SAMPLE member ACBGEN.

The ACBs generated will need to be staged onto the IMS executable libraries. You will need to customize either your site’s staging routine (with the IMS Systems Programmer) to include &BASEQUAL..ACBLIB, or change the name of the target library to the name assigned by the IMS Systems Programmer. The following is a list of ACBs to be generated:

• BUILD PSB=HPIERRL

• BUILD PSB=HPISEC4

• BUILD PSB=HPICACF

• BUILD PSB=HPIUTBL

• BUILD PSB=HPI100P

• BUILD PSB=HPIHPC7

• BUILD PSB=HPIRCP1




• BUILD PSB=HPISEC1

• BUILD PSB=HPIVSAM

• BUILD PSB=HPRC

• BUILD PSB=HPRT

• BUILD PSB=HPR0

• BUILD PSB=HPT0

• BUILD PSB=PCIO0000

• BUILD PSB=DNAIEVNT

Preparation Step 4—AppBuilder Software Format Library

Run an IMS MFS Generation for each MFS format source member in &BASEQUAL..SVI2031.MFSSRCE. Three members must be generated. Two members, HPISEC4 and HPISEC5, are part of the Message Log screen program. The third member, HPIMFS1, is the AppBuilder Main Driver format.


Installation Notes

AppBuilder provides an optional MFS screen that may be included if desired. HPINFO is AppBuilder utility that retrieves date and time and obtains the LTERM name.

Use your installation’s existing version of MFSGEN to generate the three members into your site’s correct libraries.


Selecting Option 2 - Repository Functions, allows you to start installing repository functions, as shown in Figure 9-9.

Figure 9-9 Apply Repository Upgrade

Use the panel above to perform option 4 Apply Repository Upgrades.



3. Press Enter to advance to the panel selected.


Figure 9-10 begins the installation of the repository functions.



Note If the base repository was installed using DB2 VCATs instead of DB2 storage groups, you will have to modify the DB2VCAT JCL skeleton in &INSTQUAL..SVI2031.ISKELS. Change line 29 to read as follows:SEL &IDCMLIB NE Z

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> REPOSITORY FUNCTIONS OPTION ===> REPOSITORY ID ===> 1 Create Repository 6 Display Software History 2 Enable/Disable Repository 7 Create New Version 3 Bind DB2 Objects 8 Maintain Version 4 Apply Repository Upgrade 9 List Systems and Repositories 5 Associate Repository X EXIT Enter END Command to exit. Press ENTER to continue.


Installation Notes

Figure 9-10 Apply Upgrade to your Repository

This panel starts upgrading the repository portion of the IMS Online option. Do not start this section until you complete the system functions described in “Apply System Upgrade”.

From this panel you identify the repository you want to create, and choose the options to create and process its installation table, and finally activate the resultant repository. Perform the following options, as described below:



• Activate

Option 1 - Create Installation Table

Initiate the panel in Figure 9-10 with option 1. Begin by naming the repository to upgrade and selecting option 1 Create Installation Table. (You will return to this panel to perform option 2 and 3 later.)

If this is the first time upgrading this repository, you know that option 1 is done when the “TABLE CREATED” message appears in the top-right corner of Figure 9-10. In this case, perform option 2 and proceed to the panel in Figure 9-12.

After the initial upgrade of the repository using option 1, you see the panel on Figure 9-11. After you complete that panel, return to this panel for action. Assuming you are continuing with the upgrade at hand, proceed to the panel in Figure 9-12 to perform option 2.

Additional information about option 2 and 3 appears in sequence later.

Upgrade Repository

Figure 9-12 will appear the first time you perform this installation. The panel appearing next in Figure 9-11 is optional. The first time you apply a repository upgrade, this panel does not appear. But it does subsequently. Its text informs that the installation tables are already generated; consequently, do not generate them again unless you have introduced some change requiring another generation pass.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT Enter END Command to exit. Press ENTER to continue. . . . . . . . . . . . . . . . . . . . . . . . . . . .


Installation Notes

Figure 9-11 Upgrade Repository





• If you want to stop this upgrade, not allowing it to continue, so you can initiate another modified upgrade, press Y.

On successful completion of either choice, you move to the next panel in Figure 9-12.


Figure 9-12 shows the Apply Upgrade to Repository panel, where you now enter option 2 Process Installation Table.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> UPGRADE REPOSITORY The process of upgrading this repository has already been begun but has not been completed. To complete the installation already in progress, enter N below to return to the Apply Repository Upgrade menu panel. Then select Step 2 (PROCESS INSTALLATION TABLE). To abandon the installation in progress and begin again, enter Y below. Note that you may encounter difficulty in attempting to run jobs which have been previously run. Do you want to begin the upgrade again? (Y/N) ==> Enter END command for previous screen. Press ENTER to continue.


Installation Notes


Select option 2 for the same repository and press Enter. That action provides the following panel.




This panel contains a table of releases that you are to process. If there are more than one, select each in top-down order, and assure each executes completely. The following lists indicators displayed in the Status column. Observe the status of the Actions you initiate.


• SELECTED — An action is in progress.


When you have executed all entries in the release table successfully, press F3. See the next panel.

Apply SVI2031 to Repository

The next panel applies the repository upgrade to the repository, as shown in Figure 9-14.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT Enter END Command to exit. Press ENTER to continue. . . . . . . . . . . . . . . . . . . . . . . . . . . .

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> PF3-END PF7-UP PF8-DOWN PROCESS INSTALLATION TABLE Type S or SEL in the Action column to process a release. Action Release Status ______ SVI2031


Installation Notes

Figure 9-14 Apply SVI2031 to Repository

This panel applies the repository upgrade to the repository in two option steps. The panel contains:

Select from among the following options:

• Capture Version Variables

• Create/Submit Installation Jobs

Option 1 - Capture Version Variables

Option 1 - Capture Version Variables starts a group of panels in which you specify the requisite information. The panels appear in Figure 9-15 to Figure 9-18. Handle these panels in the order they appear.


Option 2 - Create/Submit Installation Jobs is discussed after the six variables panels in Figure 9-19.


This series of four panels captures repository variables needed to apply the repository upgrade to the IMS environment. The first of these panels is shown in Figure 9-15.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> APPLY SVI2031 TO REPOSITORY repname OPTION ===> 1 Capture Version Variables 2 Create/Submit Installation Jobs X EXIT Enter END Command to exit. Press ENTER to continue.


Installation Notes

Figure 9-15 Capture Repository Variables—IMS environment (1 of 4)

Enter the runtime data set name suffixes.

600.3 Runtime Dataset Name Suffixes:

Complete the following values.

600.3a Load Library Output - [Default: LOADIM]

Enter the name of the suffix for the Load Library Output data sets for IMS.

600.3b NCAL Library Output - [Default: NCALIM]

Enter the name of the suffix for the NCAL Library Output data sets for IMS.

600.3c VSAM View Definition File - [Default: HPI001D1.VIEWDEF]

Enter the name of the suffix for the VSAM View Definition File data sets for IMS.

600.3d VSAM Rule Source Output - [Default: HPI003D1.RULESRC]

Enter the name of the suffix for the VSAM Rule Source Output file for IMS.

600.3e VSAM Rule Relation Output - [Default:HPI004D1.RLRELATN]

Enter the name of the suffix for the VSAM Rule Relation Output file for IMS.

600.4 Specify the Jobname for IMS Control Region - [Default: None]

Enter the jobname for the IMS Control Region at your site.

600.5 Specify the dataset name which contains the IMS VSAM Buffer Cards - [Default:

SS0216.SVI2031.SAMPLE(DFSVSM)]

Complete this panel, and proceed to the next.

The second of four panels capturing repository variables is shown in Figure 9-16.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> CAPTURE REPOSITORY VARIABLES - IMS environment - Version 1 Runtime Dataset Name Suffixes: Load Library Output ==> LOADIM NCAL Library Output ==> NCALIM VSAM View Definition File ==> HPI001D1.VIEWDEF VSAM Rule Source Output ==> HPI003D1.RULESRC VSAM Rule Relation Output ==> HPI004D1.RLRELATN Specify the Jobname for IMS Control Region ==> Specify the dataset name which contains the IMS VSAM Buffer Cards ==> SS0216.SVI2031.SAMPLE(DFSVSM) Enter END command for previous page. Press ENTER to continue.


Installation Notes


Enter the information required by this panel. These parameters are intended for future use, so enter the defaults.

600.6 You may form IMS DB2 plan names by using the generated bitmap as the plan name prefix or

suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default: P]

Enter the default value to use the bitmap as a suffix.

600.7 Use AppBuilder Project name in IMS plan name? (Y/N) - [Default: Y]

Enter the default value to use the AppBuilder project name in the IMS plan name.

600.8 If not, enter the string to use here: - [Default: HP]


600.9 Use the repository version number in plan name? (Y/N): - [Default: Y]

Enter the default value to use the repository version number in the plan name.

600.10 Use the region type (‘M’) in the plan name? (Y/N) - [Default: Y]

Enter the default value to use the region type M in the plan name.

600.11 Should a separate plan be generated for Batch Rules (Y/N) - [Default: N]

If you want to generate a separate plan for Batch Rules, enter Y. If not, enter N.

600.12 Use HPS/IMS Autoinstall? (Y/N) - [Default: None]

If you want to use HPS/IMS Autoinstall, enter Y. If not, enter N. This feature is a batch interface that automatically connects to IMS to open and close AppBuilder databases and to update the HPS incore table with the AppBuilder IMS rule and transaction ID.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> CAPTURE REPOSITORY VARIABLES - IMS environment - Version 1 You may form IMS DB2 plan names by using the generated bitmap as the plan name prefix or suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix: ==> P Use AppBuilder Project name in IMS plan name? (Y/N) ==> Y If not, enter the string to use here: ==> HP Use the repository version number in plan name? (Y/N) ==> Y Use the region type (‘M’) in the plan name? (Y/N) ==> Y Should a separate plan be generated for Batch Rules? (Y/N) ==> N Use HPS/IMS Autoinstall? (Y/N) ==> Press END Command to Terminate. Press ENTER to Continue.


Installation Notes


The third of four panels capturing repository variables is shown in Figure 9-17.



600.13 IMS General Library Names:

600.13a General IMS Lib Prefix - [Default: IMS410.VENDOR]

Enter the name of your general IMS library prefix.

600.13b VTAM NAME FOR IMS SYSTEM - [Default: IMS41]

Enter the VTAM region ID for this IMS system.

600.13c IMS Region name - [Default: IMSB]

Enter the IMS system name.

600.13d IMS MACLIB Library - [Default: SYS1.IMS.MACLIB]

Enter the name of your IMS Macro library (MACLIB).

600.13e IMS Res Library - [Default: IMS410.VENDOR.RESLIB]

Enter the name of your IMS Resident Library (Res Library).

600.13f IMS AGN name - [Default: None]

Enter the AGN (Application Group Name) value if AGNs are used at your site.

600.13g IMS HPS Log Message - [Default: IMS410.LGMSG]

Enter any fully qualified data set name used by the IMS Control Region. This library is used to determine if IMS is up before submitting AppBuilder BMP jobs.

600.14 Maximum Transaction ID for this Version: - [Default: None]

Currently this value is set by a AppBuilder internal program for IMS transactions.

------------------------- HOST INSTALLATION WORKBENCH ------------------------COMMAND ===> CAPTURE REPOSITORY VARIABLES - IMS environment - Version 1 IMS General Library Names: General IMS Lib Prefix ==> IMS410.VENDOR VTAM NAME FOR IMS SYSTEM ==> IMS41 IMS Region name ==> IMSB IMS MACLIB Library ==> SYS1.IMS.MACLIB IMS Res Library ==> IMS410.VENDOR.RESLIB IMS AGN name ==> IMS HPS Long Message ==> IMS410.LGMSG Maximum Transaction ID for this Version: ==> Number of IMS Regions you want to configure for version 1 ==> The following two panels will be presented for each region requested to allow you to configure each region separately. Enter END command for previous page. Press ENTER to continue.


Installation Notes

600.15 Number of IMS Regions you want to configure for version 1 - [Default: None]

Please enter the number of regions you want to configure for version 1.

Complete this panel and proceed to the next. The following panel appears once for each requested region to allow you to configure each region separately.

The last of four panels capturing repository variables is shown in Figure 9-18.



600.16 Enter the VTAM APPLIDs for LU2 processing:

If you specified Y for item 600.12, then you must enter the names of the three VTAM APPLIDs for LU2 processing.

600.16a 1 - [Default: A06HPS1]

Specify the name of the first VTAM APPLID.

600.16b 2 - [Default: A06HPS2]

Specify the name of the second VTAM APPLID.

600.16c 3 - [Default: A06HPS3]

Specify the name of the third VTAM APPLID.

600.17 Define HPS transactions during rule prepare? (Y/N) - [Default: Y]

Enter the default value to define AppBuilder transactions during rule prepare.

600.18 Should the HPS databases be processed? (Y/N) - [Default: Y]

If you want the AppBuilder databases to be processed (used to populate RuleView), enter Y. If not, enter N.

600.19 Should the HPS transaction UTBL0000 be executed? - [Default: Y]

If you want the AppBuilder transaction UTBL0000 to be executed, enter Y. If not, enter N.


------------------------- HOST INSTALLATION WORKBENCH ------------------------COMMAND ===> CAPTURE REPOSITORY VARIABLES - IMS environment - Version 1 Enter the VTAM APPLID's for LU2 processing: 1 ==> A06HPS1 2 ==> A06HPS2 3 ==> A06HPS3 Define HPS transactions during rule prepare? (Y/N)==> Y Should HPS databases be processed? (Y/N)==> Y Should the HPS transaction UTBL0000 be executed? (Y/N)==> Y Enter END command for previous page. Press ENTER to continue.


Installation Notes

Option 2 - Capture/Submit Installation Jobs

Figure 9-19 shows you returning to the panel you saw previously in Figure 9-14. This time you perform option 2 Create/Submit Installation Jobs.

Figure 9-19 Apply SVI2031 to Repository, Option 2 Capture/Submit Installation Jobs

This panel applies the repository upgrade to the repository in two optional steps.

Select from the following options:

• Capture Version Variables

• Create/Submit Installation Jobs

Because you have completed option 1, perform option 2.

Option 2 - Create/Submit Installation Jobs shows two jobs that you need to process, as shown in Figure 9-20.


The next panel defines the repository jobs that install updates to your repository, as Figure 9-20 shows.


------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> APPLY SVI2031 TO REPOSITORY repname OPTION ===> 1 Capture Version Variables 2 Create/Submit Installation Jobs X EXIT Enter END Command to exit. Press ENTER to continue.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> PF3-END PF7-UP PF8-DOWN UPDATE REPOSITORY SOFTWARE - REGENERATE/EDIT/SUBMIT INSTALLATION JOBS Repository ID: repname Release: SVI2031 Type REGEN in the Action column to regenerate a job. Type V in the Action column to view a job. Type SUB in the Action column to submit a job. Action Jobname Description Status ______ REPJOB1 NON-DB2 PROCESSING COMPLETED ______ REPJOB2 DB2 PROCESSING COMPLETED


Installation Notes


This panel controls the repository functions update. Its choices are:

The Actions you can make are to regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the software. The following describes the repository jobs:

• REPJOB1 — NON-DB2 PROCESSING

This step processes the non-DB2 jobs, which must be handled first.

After this job completes, the following new data sets are created:

• REPJOB2 — DB2 PROCESSING

This step processes the DB2 jobs, which must be handled secondly.

Note &REPQUAL is the qualifier used for AppBuilder repository level data sets.

Table 9-3 Repository Libraries

&REPQUAL..LOADIM

Note &USRVQUAL is the qualifier used for AppBuilder user level data sets that are versioned. You have more than one set of the following data sets if you specified more than one version during the Enterprise Repository installation. The value for &USRVQUAL is contained in &REPQUAL..INI(@USRENVn) where n is the version number of the repository.

Table 9-4 User Libraries

&USRVQUAL..LOADIM &USRVQUAL..NCALIM

&USRVQUAL..ACBLIB &USRVQUAL..DBDLIB

&USRVQUAL..DBDSRCE &USRVQUAL..PSBLIB

&USRVQUAL..PSBSRCE

Note &VSUVQUAL is the qualifier used for AppBuilder user VSAM data sets. You have more than one set of the following data sets if you specified more than one version during the Enterprise Repository installation. The value for &VSUVQUAL is contained in &REPQUAL..INI(@USRENVn), where n is the version number of the repository.

Table 9-5 User VSAM data sets

&VSUVQUAL..&VIEWDEFI &VSUVQUAL..&RULESRCI

&VSUVQUAL..&RLRELATI &VSUVQUAL..HPI002D1.TESTDATA

&VSUVQUAL..HPI006D1.ERRLOG &VSUVQUAL..HPSDNADI

&VSUVQUAL..HPI030D1.HPIRULS &VSUVQUAL..HPI030D1.HPIRULX

&VSUVQUAL..HPI040D1.HPIRCP &VSUVQUAL..HPI040D1.HPIRCX

&VSUVQUAL..HPI041D1.STGMNGR

Note &VIEWDEFC, &RULESRCC, and &RLRELATC are the values entered in prompt 600.1, refer to Figure 9-15.


Installation Notes





When you have competed these jobs successfully, press F3 to exit this panel. Return to the Apply Upgrade to Repository panel, appearing in the next figure.

Activate Repository

After completing the previous panel, you have applied all the repository updates for SVI2031. The last panel in this series activates the repository, as Figure 9-21 shows.

Figure 9-21 Activate Repository

Select option 3 Activate Repository. This option concludes the installation of the IMS Online upgrade to your repository.

------------------------- HOST INSTALLATION WORKBENCH ------------------------ COMMAND ===> APPLY UPGRADE TO REPOSITORY repname OPTION ===> 3 1 Create Installation Table 2 Process Installation Table 3 Activate Repository X EXIT Enter END Command to exit. Press ENTER to continue.



Postinstallation NotesPerform the following steps to complete and verify the successful installation of the AppBuilder IMS Online Preparation and IMS Enterprise Server.

1 - Database DBRC DefinitionDefine the AppBuilder databases to the DBRC utility (database recovery) if your site uses this utility.

Edit the DBRC member in &BASEQUAL..SVI2031.SAMPLE for the database data set and supply to the IMS Systems Programmer for inclusion into DBRC.

2 - Database Dynamic Allocation DefinitionDefine the AppBuilder databases to the IMS Dynamic Allocation utility. The AppBuilder databases to be defined are:

• HPI001D1— AppBuilder RuleView Definition database

• HPI002D1—AppBuilder Rule View Test Data database

• HPI003D1—AppBuilder Rule View Rule Source database

• HPI004D1—AppBuilder Rule View Rule Relationship database

• HPI006D1—AppBuilder message log database

• HPI030D1/HPI030X1—AppBuilder rule/transaction relationship database (and index)

• HPI040D1/HPI040X1—AppBuilder/IMS Run Control database (and index)

• HPI041D1—AppBuilder IMS storage manager database

a. Define databases—Edit the &BASEQUAL..SVI2031.SAMPLE member HPSDYNAM by filling in the appropriate value for the &VSUVQUAL variable. Make any other customizations needed for your site. Supply the edited HPSDYNAM to the IMS Systems Programmer.

b. IMS buffers—In the &BASEQUAL..SVI2031.SAMPLE data set, the member DFSVSM contains the buffer cards required for the AppBuilder/IMS databases.

5. IMS preload—In the &BASEQUAL..SVI2031.SAMPLE data set, the member DFSMPL contains the programs to be preloaded. Insert these programs in the preload member for your site. Change PRLD=, accordingly.

6. For better performance, it is recommended that you preload the following NetEssential modules into the Message processing region: HPSDI200, HPSDI600, DNAPOSTE, and DNAIEVNT.

Additionally, if you are running any COBOL services, we recommend preloading the following rou-tines from SYS1.COB2LIB in order to eliminate the overhead of setting up the COBOL environ-ment:

Table 9-6 NetEssential Routine Modules

IGZCPAC IGZCPCO

IGZEINI IGZEPCL

IGZEPSU IGZETCO

IGZEOPD IGZEOPT



3 - IMS Stage 1 InputThis step is performed manually by the IMS Systems Programmer.

AppBuilder applications, databases, and some special terminals must be defined to IMS. This is done by control record input in the IMS Stage 1 generation. The following is a description of the supplied input control records for AppBuilder applications that must be specified in the IMS stage 1 generation.

• Terminal Input

• DFSCMTR0 Terminal Routing Exit

Terminal Input

Define each physical terminal from which AppBuilder software will be run to IMS. Add the terminal IDs to the stage 1 generation. Refer to your IBM IMS/ESA Installation manual for more information.

All 3270 terminals defined to process AppBuilder PCIO0000 input must have the OPTION macro parameter—TRANRESP—specified. 3270 terminals must also be defined as SNA to keep the terminal session locked until the reply message is received. This parameter can be coded in the TYPE macro, which defines parameters for all terminal definitions that follow.

TYPE UNITYPE=SLUTYPE2,MODEL=2,FEAT=IGNORE, * OPTIONS=(TRANRESP,PAGDEL,NOPNDST,NOCOPY) TERMINAL NAME=LE02,FEAT=F4 NAME LE02 TERMINAL NAME=LE03.... etc.. \

In addition, three special terminals are typically defined for AppBuilder software’s exclusive use. Each special terminal contains a VTAM application ID with a location-dependent NAME. The terminal NAME can be found in the LOGAPPLI1, LOGAPPLI2, and LOGAPPLI3 variables defined in the @ “IMS System Name” member of the &REPQUAL..INI data set.

The following example is a special LU2 terminal from the TERMINAL member of the &BASEQUAL..SVI2031.SAMPLE data set. Use this member as a basis for each special terminal definition.

TYPE UNITYPE=SLUTYPE2,MODEL=2,FEAT=IGNORE, * OPTIONS=(TRANRESP,PAGDEL,NOPNDST,NOCOPY) TERMINAL NAME=A05HPS1,FEAT=F4,MSGDEL=NOTERM,OUTBUF=1536, * OPTIONS=(FORCRESP) NAME A05HPS1

The default terminal names are A05HPS1, A05HPS2, and A05HPS3. The option FORCRESP is required.

DFSCMTR0 Terminal Routing Exit

1. The COMM Macro in the IMSGEN must have MSCEXIT specified in order for Terminal Exit Routine DFSCMTR0 to be executed. If you are using IMS version 5.1, this step is not necessary.

2. The output from this IMS stage 1 needs to be modified. Modification is limited to one area—the final link-edit step that generates the IMS nucleus.

Note The USERLIB DD statement needs to specify the DSN of the library where the AppBuilder version of DFSCMTR0 load module resides.



3. If IMS is a single system setup (not MSC), add ORDER DFSCMTR0 after INCLUDE SYSPUNCH(DFSCVB0I), then add INCLUDE USERLIB(DFSCMTR0).

4. The output of the stage 1 IMS generation is submitted to perform the build of the IMS nucleus, the stage 2 IMS generation.

5. The output of the stage 2 linking of DFSCMTR0 which includes HPICMTR0 must reside in the RESLIB. DFSCMTR0, HPICMTR0, HPITBL1, and HPITBL2 are also linked into &BASEQUAL..SVI2031.IMSRES.

6. A sample terminal routing exit program is contained in &BASEQUAL..SVI2031.SAMPLE (DFSCMTR0).

Stage 1 Requirements for AppBuilder User ApplicationsAt this point, you have all necessary IMSGEN input for the AppBuilder IMS run-time environment. However, each AppBuilder application will need to supply input to IMSGEN. This input is generated by using the AppBuilder IMS utilities. Therefore, use the AppBuilder IMS utilities to define the IMSGEN input for online conversational, non-conversational, and batch message processing applications.

• 4 - IMS Security Generation

• 5 - Changes to Control Region JCL

• 6 - Set Up HMPBTBLI

• HMPBTBLI is used to update the AppBuilder software incore table. Always run HMPBTBLI when bringing up IMS. The sample JCL is contained in &BASEQUAL..SVI2031.SAMPLE(HMPBTBLI).

• 7 - HPICGAP and HPEUCGP

• 8 - Modify NetEssential Middleware for IMS

• 9 - Cold Start IMS

• 10 - Completing the Installation

4 - IMS Security Generation

Define two AppBuilder software BMPs with special authorities to the IMS security generation. A sample is provided in member SECURITY in &BASEQUAL..SVI2031.SAMPLE. The first BMP is the Automated Operator command application (HPI100P). This program performs the IMS /STA and /DBR database operator commands for the HPI001D1 Rule View Definition database. The second BMP is the HPS Run Control (HPIRCP1), which performs the stopping and starting of IMS regions and batch jobs, based on the application’s use of USE RULE INIT.

Use the standard IMS security utility, SECURITY, located in the IMS PROCLIB or your installation’s modified version.

Note See the “HMPBTBLI is used to update the AppBuilder software incore table. Always run HMPBTBLI when bringing up IMS. The sample JCL is contained in &BASEQUAL..SVI2031.SAMPLE(HMPBTBLI).” on page 9-28 for more information on how the terminal user exit is used in AppBuilder software.

Note HPITBL1 and HPITBL2 can either be copied into RESLIB or may reside in a library accessed by the control region.



5 - Changes to Control Region JCL

Add the following AppBuilder load libraries to the IMS region STEPLIB concatenation for those regions that will be executing AppBuilder software transactions:

• &USRVQUAL..LOADIM


• &REPQUAL..LOADIM

• &MODQUAL..LOADIM

• &BASEQUAL..LOADIM

If Global Eventing will be used, you must define the following VSAM file as shown:

DEFINE CLUSTER (NAME(&VSMQUAL..HPSDNADV) –TRACKS (1,1) –VOLUMES (?) or MANAGEMENTCLASS (?) –SHAREOPTIONS (2,3) –LINEAR)

where &VSMQUAL is the prefix for base VSAM data sets. The value for this is contained in &REPQUAL..INI(@HPSENV).

To support LU6.2 and AppBuilderNetEssentialmiddleware, the following files must be added to the Message Processing Region JCL:

//DIVDD DD DSN=&VSMQUAL..HPSDNADV//DNAERR DD DSN=&BASEQUAL..HPSDNAER//DNAINI DD DSN=&BASEQUAL..HPSDNAIN//PSBTAB DD DSN=&BASEQUAL..HPSDNAPS//SCTABLE DD DSN=&BASEQUAL..HPSDNASC//DNARTBL DD DSN=&BASEQUAL..HPSDNART

6 - Set Up HMPBTBLI

HMPBTBLI is used to update the AppBuilder software incore table. Always run HMPBTBLI when bringing up IMS. The sample JCL is contained in &BASEQUAL..SVI2031.SAMPLE(HMPBTBLI).

Use of HMPBTBLI

DFSCMTR0 uses the rule/transaction relationship incore tables to associate an AppBuilder rule with its assigned IMS transaction code. Table 1 is built by a program (HMPBTBLI) reading the E_RULE DB2 table and creating a row for each AppBuilder rule and IMS transaction code relationship. Table 2 has the same format as Table 1 and contains entries for the rules that have been prepared since Table 1 was created.

When an AppBuilder IMS rule is prepared, a UTBL0000 IMS transaction along with the associated rule name and IMS transaction code is put on the IMS queue for the routing exit to process. The exit scans both Tables 1 and 2 for the existence of that relationship. If the relationship is new it is added to Table 2. When a relationship exists but the transaction code has changed, the entry in either Table 1 or 2 will be updated.

When IMS is cold started Table 2 is empty and can have 100 new entries added to it. If the table becomes full an error message is returned to the terminal that issued the UTBL0000 transaction. Because of this,



you must be able to run the HMPBTBLI table build program during the IMS startup procedure’s management system and while IMS is up.

7 - HPICGAP and HPEUCGP

Review the AppBuilder IMS Global Parameters Table (HPICGAP) delivered in the &BASEQUAL..SVI2031.SAMPLE data set. This source should be modified and reassembled to satisfy site requirements. Also included in the &BASEQUAL..SVI2031.SAMPLE data set is JCL to assemble HPICGAP. The member is HPICGAPJ. Then rerun the COPY1, COPY2, and COPY3 steps in the DSALLOC member found in the &INSTQUAL.AB2031.CNTL data set. This will place the correct version of the translate objects in the &BASEQUAL.OBJ data set. (This problem will be corrected in the next release so the translate objects will be delivered in the runtime products.) Link the programs into your AppBuilder IMS load library using the link function accessed from the Host Installation Workbench-Systems Functions menu. Refer to Appendix D, “HPSCGAP, HPICGAP, HPEUCGP, and Sample Batch JCL” for more information about HPICGAP and HPEUCGP. Repeat this exercise for the &BASEQUAL..SVI2031.SAMPLE(HPEUCGP) member using the HPICGP JCL member to assemble the HPIGAPA load module

8 - Modify NetEssential Middleware for IMS

The following must be completed to provide NetEssential support for IMS:

1. Setup PSB table for NetEssential middleware running over LU6.2. To make different services run with different DL/I access restrictions, setup the PSB look-up table, &BASEQUAL..HPSDNAPS. The server responds to service requests by accessing the table to determine what PSB is to be allocated.

The PSB look-up table is a sequential, fixed-length file with lrecl=25. Each entry in the table has these fields:

.Service name (rule name) : positions 1 - 8

.Blank : position 9

.PSB name : positions 10 - 17

2. For Global Events routing, setup the following:

.Subcell table, &BASEQUAL..HPSDNASC.

.SMA section of NetEssential initialization file, &BASEQUAL..HPSDNAIN.

3. Make sure Mainframe/APPC and IMS/APPC have been set up.

4. Make sure that the VTAM definitions have been defined to support LU6.2. For sample definitions refer to the members MODELU6.2 and AppBuilderMN in &BASEQUAL..SVI2031.SAMPLE.

5. Refer to the sample TP profile SDFMU in &BASEQUAL..SVI2031.SAMPLE to set up your TP profile. Ensure that the transcode value is HPSDI600.

6. Set up the OS/2 Communications Manager LU6.2 session. You will need to provide the following:

• NCP domain name

• Partner LU for IMS (This can be obtained by the side information file in mainframe/APPC.)

Note The MPR has to be taken down each time you want to update the files in steps 1 and 2 above.

Note If samples have not been provided, contact AppBuilder’s ActionLine.



• TP name specified in the TP profile.

• LOCAL LU as defined in step 4 above.

9 - Cold Start IMS

The IMS system must be cold started before completing the installation.

10 - Completing the Installation

Complete the following on the host (mainframe) before Host IMS Development Workbench software can run.

1. Copy LOADs, ACBs, MATRIX, MFSs, and MODBLKS to staging libraries and then onto the active libraries.

2. Define AppBuilder software regions and make them part of the standard IMS start-up.

3. Define the classes of the AppBuilder software transactions (both AppBuilder system and AppBuilder applications) and create regions accordingly.

4. If required, define AGNs (via DFSISMP0) to authorize specific users to use AppBuilder software transactions.


The Test Installation Process (TIP) application should already be migrated into the Enterprise Repository. If not, refer the postinstallation instructions for the migration procedure in Chapter 5, “Installing the Enterprise Repository”

1. Edit the IMS region INI member in &REPQUAL..INI and change the value for the IMSLNK variable from NORENT to RENT.

2. Within the Enterprise Repository, go into the ADM project. Type PROJECTS at the command line, list entities (LE), and select ADM for version 1.

3. Within the ADM project, type IMS against the TIP project for version 1. This will select the IMS Utilities option.

4. Select Option 1 to create the DM_TRAN record for the TIP version 1 project.

5. Select Option 4 to create the necessary stub programs required at runtime. Use a suitable range—for example, “AA” through to “AI” and submit the presented JCL.

6. Execute the following options:

Option 2 (Stage 1 input), Option 3 (PSBGEN), and Option 5 (ACBGEN).

7. Within the Enterprise Repository, make sure you are in the TIP project. If not, type PROJECTS at the command line, list entities (LE), and then select TIP for version 1.

Superprepare the TIP IMS Process

1. Next to the Rebuild Package entity, type ADDE (Add Entity) to add a Rebuild Package for TIP. Name the package whatever you like. Press F3 to save and return.



2. Next to the Rebuild Package entity, type LE to list the Rebuild Package entities. Next to the one you have just created, type ADDR (Add Relationship) to add the TIP IMS process to the Rebuild Package for TIP. Select Option 6 “Has Root Process” in the popup window and press ENTER. Enter TIP_IMS_COOP_PROCESS as the “Has Root Process” name. Press F3 to save and end.

3. Next to the Rebuild Package for TIP, type SUPERPR. A message states that the job was submitted. Several jobs will be submitted at various times.

4. After the last job finishes, check the results by typing LISTRBD next to the Rebuild Package for TIP. Information will be displayed stating whether SUPERPR was successful or not. Press F3 to save and return.

TIP Verification

1. Logon to the IMS test system.

2. Type HPR0 (and a space) to display a list of rules for TIP. Select by entering a slash (/) next to each rule you want to test. Select break points if you want, and press F15 or SHFT+F3 to continue. A message will display for each rule stating whether it is successful or not.

3. Test the following rules:

• TIP_IMS_ASM_RULE

• TIP_IMS_ASMDB2_RULE

• TIP_IMS_COB_RULE

• TIP_IMS_COBDB2_RULE

• TIP_IMS_PLI_RULE *

• TIP_IMS_PLIDB2_RULE *

• TIP_IMS_DB2_RULE

• TIP_IMS_RULE

4. TIP should already be downloaded and prepared on the workstation. If not, refer to the Installation Verification instructions in Chapter , “Installing the Enterprise Repository” for the download and prepare procedures.

5. Refer to the AppBuilder Workstation Development Workbench Installation Instructions for the instructions for proper configuration and communications protocol for host logon for both LU2 and LU6.2.

6. Execute the TIP application by selecting the AppBuilder Execution Workbench on the workstation. A menu appears with the TIP Function pulldown. Select the TIP Function pulldown menu, and then select the TIP IMS Coop Process. Click the mainframe pushbuttons to verify the cooperative processing.

7. Verification of the AppBuilder IMS Online Preparation and IMS Enterprise Server (SVI2031) installation is now complete.

Note The items marked with an asterisk (*) are only required if you are going to be using PL/I components.

Warning Do not click the PL/I buttons if PL/I components are not used.



IMS 3270 Converse VerificationPerform the following steps to complete and verify the successful installation of AppBuilder REL 2.0.3.1 IMS Online Preparation.

1. The Default Repository and Test Installation Procedure (TIP) application should already be migrated into the Enterprise Repository. If not, refer to the postinstallation instructions in Chapter 5, “Installing the Enterprise Repository” for the migration procedure.

2. Within the Enterprise Repository, make sure you are in the TIP Project. If not, type PROJECTS at the command line. Select TIP for version 1. The following steps will need to be done for each version in the Repository you wish to verify.

3. Ensure that the TIP_IMS_PROCESS has been prepared. Refer to the section IMS 3270 Converse Verification Using TIP for more information.

4. Create an IMS 3270 Driver Rule by typing SA against the TIP_IMS_DRIVER_RULE rule (the execution environment of IMS) and copy all of the relationships.

5. Create a new IMS rule by typing SA against the TIP_PC_RULE; copy the relationships but replace the relationship to the TIP_IMS_DRIVER_RULE with a new relationship to the rule created in the previous step.

6. Download the TIP_IMS_PROCESS to a AppBuilder AD repository.

7. Create IMS 3270 clones for the TIP_IMS_DRIVER_WINDOW and TIP_PC_WINDOW windows. Refer to the Design and Construction Tools manual for instructions if required.

8. Upload the windows and Prepare (PR action) them using the Enterprise Repository. Refer to the Managing Enterprise Repositories manual if further instructions are required.

9. Prepare the two new IMS rules created in the previous step using the Enterprise Repository.

10. The new IMS 3270 IMS Driver rule will attract an IMS Transaction code and PSB. Ensure that these have been defined and prepared to IMS. Refer to Chapter 9, “Installing IMS Online Preparation Workbench and Enterprise Server” for further instructions.

IMS 3270 Converse Verification Using TIP

1. Log on to the AppBuilder 3270 IMS region.

2. Type the following to verify the text content of the IMS windows:

HPC7 WTPIDVR (and two spaces)

3. To execute the IMS 3270 TIP application, type in the assigned transaction code and a space. The IMS transaction code can be determined by typing ME against the rule in the Enterprise Repository; the value is shown against the CICS/IMS Transaction ID.

4. Execute each of the PF (function) keys display on the window or screen.

5. Verification of IMS Online Preparation (CVI2031) is now complete.

Note Do not use the PF keys assigned to the PL/I rules if you do not wish to use PL/I components.


APPENDIX

A APPBUILDER VARIABLES


This appendix contains the updated HPSINI variables and configuration files for AppBuilder Host Development Workbench.

• @HPSENV

• @HPSSTAT

• @MIGRATE

• MIGENVn

• @MVSENV

• @RBDENVn

• @SEERENV

• USRENVn

Explanation of Terms1. Validation - Describe all the valid values for a specific variable.

2. Default - the initial value presented to the user; the value used if one is not specified by the client.

3. Mod - Indicate if the client may modify this variable.

4. Use Legend - categorize how the variable is used

• D - Specify default options for user prompts

• E - Define external system configuration (i.e. CICS library)

• F - Specify features to be used

• H - Define the AppBuilder system configuration (i.e. data set qualifiers)

• I - Internal use - not to be modified

• P - Performance tuning

Note Variables marked I or P: Should the variable be prompted for during the installation, use the default value.

Planning and Installing AppBuilder for the Mainframe A-1

@HPSENV

@HPSENVThe following tables define and describe the variables found in each section of the @HPSENV file.

REPOSITORY Section

Table A-1 REPOSITORY section of @HPSENV

Variable Name Description Validation Default MOD USE IP

CSDLEVEL CSD level for the repository

Maximum Length of (7) seven characters

N/A N

GLBLLOCK

Is the lock attribute respected when objects are being updated. (Y) indicates that a locked object may not be updated and (N) indicates that updates on objects may occur even if the object was previously locked by another user.Invalid data: Locked objects may be updated when it is not desired by the user.

Y or N Y Y F N

REPID

Unique two characters used to generate systemids and data sets. This should be unique for all repositories for any client.Invalid data: N /A.

Alpha None Y H Y

REPNAME

Specify the repository name. This is displayed in the repository online dialog and is also used when performing the MIGRATE command. This is also the implementation name of the repository entity if it is used.Invalid data: Any particular name can not considered invalid, however, if there are mismatches between the REPNAME and the implementation name defined in the repository entity, the MIGRATE function will not operate properly.

Maximum of 8 characters None Y H Y

REPDOWN1Specify custom message to be used when the repository is unavailable.Invalid data: N /A..


REPDOWN2Specify a second custom message to be used when the repository is unavailable.Invalid data: N /A..


A-2 AppBuilder Variables

@HPSENV

QUALIFIER Section

Table A-2 QUALIFIER section of @HPSENV


BASEQUAL

Specify the data set prefix to be used when referencing all base level data sets. This is where the base system software is installed.Invalid data: JCL errors will occur when referencing AppBuilder base level data sets.

Valid data set qualifier(s) with a maximum length of 20

None Y H Y

GRPQUAL

Specify the data set prefix to be used when allocating data sets designated by user. This string must include the userid in the string.Invalid data: JCL errors will occur when referencing user data sets.


TSO userid which is entered as <@E_USER.USER_ID>

Y H Y

MODQUAL

Specify the data set prefix to be used when referencing all mod level data sets. This is where the client stores local modifications.Invalid data: JCL errors will occur when referencing AppBuilder mod level data sets.


None Y H Y

REPQUAL

Specify the data set prefix to be used when referencing all repository level data sets. This is where the client stores local modifications which pertain to a specific repository. This may be different from the mod level data sets since the AppBuilder system software may be shared between one or more repositories.Invalid data: JCL errors will occur when referencing AppBuilder repository level data sets.


None Y H Y

PERMQUAL

Specify the data set prefix to be used when referencing permanent output data sets.<@E_USER.USER_ID> STRING IS NOT ALLOWED TO BE USED AS PART OF THE PREFIX.Invalid data: JCL errors will occur when referencing permanent data sets.


None Y H Y

TEMPQUAL

Specify the data set prefix to be used when referencing temporary output data sets.<@E_USER.USER_ID> STRING IS NOT ALLOWED TO BE USED AS PART OF THE PREFIX.Invalid data: JCL errors will occur when referencing temporary data sets.


None Y H Y


@HPSENV

DB2 Section

USRQUAL

Specify the data set prefix to be used when referencing user data sets which are not versioned.Invalid data: JCL errors will occur when referencing user level data sets.


None Y H Y

VSMQUAL

Specify the data set prefix to be used when referencing base VSAM data sets.Invalid data: JCL errors will occur when referencing base VSAM data sets.


None Y H Y

VSUQUAL

Specify the data set prefix to be used when referencing USER VSAM data sets which are not versioned.Invalid data: JCL errors will occur when referencing user VSAM data sets.


None Y H Y

Table A-3 DB2 section of @HPSENV


DB2SUBID

Specify the DB2 subsystem name where AppBuilder is installed.Invalid data: AppBuilder will not operate since it can not determined where to start the system

Valid DB2 subsystem id None Y E Y

PPREFIX

Specify the DB2 plan prefix used to bind the AppBuilder system software.Invalid data: AppBuilder will fail with a connection error.

One character None Y H Y

PLAN1

Specify the DB2 plan name used to bind the AppBuilder system software. This value is PPREFIX value concatenated with HPS53.Invalid data: AppBuilder will fail with a connection error.

PPREFIX + HPS53 None Y H N

INST1ADM

Specify the ownerid of the DB2 tables used by the AppBuilder system software. Invalid data: AppBuilder will fail with errors accessing and/or binding the system.

Valid DB2 owner id None Y H Y

TIADPGMTEP2PGMTIAULPGM

Specify the dynamic DB2 programs used within AppBuilder. Invalid data: Any feature using these modules may fail

N / A

HMATIADHMPTEP2HMATIAUL

N I N

Table A-2 QUALIFIER section of @HPSENV (Continued)



@HPSENV

FILES Section

DB2OWNR

Specify the ownerid of the user developed application DB2 tables for non-configured applications. If the TSO user id is desired, specify E_USER.USER_ID. Please refer to the mainframe environment manual for additional details on DB2 configurations.Invalid data: File prepares may result in errors.

Valid DB2 owner id None Y F Y

Table A-4 FILES section of @HPSENV


PUNIT

Specify the unit type to be used when allocating new permanent data sets.Invalid data: JCL errors will occur when referencing new permanent data sets.

None SYSDA Y E Y

PVOLREQ

Specify if a volume id is required when allocating new permanent data sets. (Y) indicates a volume id is required and the value stored in PVOL will be used. A (N) indicates that no volume id is required when allocating new permanent data sets.Invalid data: JCL errors will occur when referencing permanent data sets.

Y or N N Y E Y

PVOL

Specify the volume id to be used for allocating new permanent data sets.Invalid data: JCL errors will occur when referencing permanent data sets.

Y or N or NOVOL NOVOL Y E Y

PUNITVOL

Specify the combined unit type and volume id requirement to be used for creating new permanent data sets. This value should be exactly the same as the combination of the PVOL and PVOLREQ and PUNIT from above. This values improves the performance.Invalid data: JCL errors will occur when referencing permanent data sets.

None UNIT=SYSDA Y E Y

TUNIT

Specify the unit type to be used when allocating new temporary data sets.Invalid data: JCL errors will occur when referencing new temporary data sets.

None SYSDA Y E Y

TVOLREQ

Specify if a volume id is required when allocating new temporary data sets. (Y) indicates a volume id is required and the value stored in TVOL will be used. A (N) indicates that no volume id is required when allocating new temporary data sets.Invalid data: JCL errors will occur when referencing temporary data sets.

Y or N N Y E Y

Table A-3 DB2 section of @HPSENV (Continued)



@HPSENV

TVOL

Specify the volume id to be used for allocating new temporary data sets.Invalid data: JCL errors will occur when referencing temporary data sets.


TUNITVOL

Specify the combined unit type and volume id requirement to be used for creating new temporary data sets. This value should be exactly the same as the combination of the TVOL and TVOLREQ and TUNIT from above. This values improves the performance.Invalid data: JCL errors will occur when referencing temporary data sets.


VUNIT

Specify the unit type to be used when allocating “virtual” data sets (VIO). Virtual data sets will allow a client, where applicable, to deploy high speed DASD to improve performance. When this is not available, these values should be set to the same as the temporary values.Invalid data: JCL errors will occur when referencing VIO data sets.

None SYSDA Y E Y

VVOLREQ

Specify if a volume id is required when allocating new virtual data sets. (Y) indicates a volume id is required and the value stored in PVOL will be used. A (N) indicates that no volume id is required when allocating new virtual data sets.Invalid data: JCL errors will occur when referencing virtual data sets.

Y or N N Y E Y

VVOL

Specify the volume id to be used for allocating new virtual data sets.Invalid data: JCL errors will occur when referencing virtual data sets.


VUNITVOL

Specify the combined unit type and volume id requirement to be used for creating new virtual data sets. This value should be exactly the same as the combination of the VVOL and VVOLREQ and VUNIT from above. This values improves the performance.Invalid data: JCL errors will occur when referencing virtual data sets.


FTOTSPUO

Specify the unit type to be used for allocating the file tailor output used during online sessions on the host repository.Invalid data: Initial start-up for Enterprise repository will fail due to failure allocating the file tailor output data set.

Valid UNIT specification TRK Y E N

FTOTSPUB

Specify the unit type to be used for allocating the file tailor output used during batch jobs.Invalid data: will result in failure of batch jobs attempting to allocate the file tailor output data set.


Table A-4 FILES section of @HPSENV (Continued)



@HPSENV

FTSQSPUO

Specify the unit type to be used for allocating the sequential file tailor output used during Hirise.Invalid data: will result in failure of Hirise start-up attempting to allocate the sequential file tailor output data set.


FTSQSPUB

Specify the unit type to be used for allocating the sequential file tailor output used during batch jobs.Invalid data: will result in failure of batch jobs attempting to allocate the sequential file tailor output data set.


FTOTPRMO

Specify the primary allocation to be used when allocating the file tailor output data set during an online session.Invalid data: will result in failure during initial satrap for Enterprise repository due to failure allocating the file tailor output data set.

Numeric 45 Y E N

FTOTPRMB

Specify the primary allocation to be used when allocating the file tailor output data set to be used in batch jobs.Invalid data: will result in failure of batch jobs attempting to allocate the file tailor output data set.

Numeric 45 Y E N

FTSQPRMO

Specify the primary allocation to be used when allocating the sequential file tailor output data set during an online session.Invalid data: will result in failure during initial start-up for Enterprise repository due to failure allocating the sequential file tailor output data set.

Numeric 45 Y E N

FTSQPRMB

Specify the primary allocation to be used when allocating the sequential file tailor output data set during a batch execution.Invalid data: will result in failure of batch jobs attempting to allocate the sequential file tailor output.

Numeric 60 Y E N

FTOTSECO

Specify the secondary allocation to be used when allocating the file tailor output data set used during an online sessions.Invalid data: will result in failure during initial start-up for Enterprise repository due to failure allocating the file tailor output data set.

Numeric 20 Y E Y

FTOTSECB

Specify the secondary allocation to be used when allocating the file tailor output data set to be used in batch jobs.Invalid data: will result in failure of batch jobs attempting to allocate the file tailor output data set.

Numeric 30 Y E N

FTSQSECO

Specify the secondary allocation to be used when allocating the sequential file tailor output data set to be used in hirise.Invalid data: will result in failure of start-up of hirise attempting to allocate the sequential file tailor output data set.

Numeric 20 Y E N




@HPSENV

FTSQSECB

Specify the secondary allocation to be used when allocating the sequential file tailor output data set to be used in batch jobs.Invalid data: will result in failure of batch jobs attempting to allocate the sequential file tailor output data set.

Numeric 20 Y E N

FTSQBLKO

Specify the blocksize to be used when allocating the sequential file tailor output data set to be used in hirise.Invalid data: will result in failure in start-up of hirise attempting to allocate the sequential file tailor output data set.

Numeric 23440 Y E N

FTSQBLKB

Specify the blocksize to be used when allocating the sequential file tailor output data set to be used in batch jobs.Invalid data: will result in failure of batch jobs attempting to allocate the sequential file tailor output data set.

Numeric 23440 Y E N

SYSLINBK

Specify the blocksize to be used for all SYSLIN output. A good blocksize will improve performance during the prepares. Invalid data: will result in possible failures during object prepares.

Numeric 3120 Y P N

RLDBSYBK

Specify the blocksize to be used when referencing the DB2 syslib DDcard during the Rule Prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card. A blocksize may be necessary if the mainframe system has problems allocating concatenated PDSs which have varying blocksize.Invalid data: will result in possible failures during object prepares.

Numeric 23440 Y P N

RLC2SYBK

Specify the blocksize to be used when referencing the COBOL II syslib DDcard during the Rule Prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23440 Y P N

RLLKSYBK

Specify the blocksize to be used when referencing the LINK EDIT syslib DDcard during the Rule Prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23200 Y P N




@HPSENV

CMPASYBK

Specify the blocksize to be used when referencing the syslib DDcard during the Assemble step of the Component Prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23440 Y P N

CMP2SYBK

Specify the blocksize to be used when referencing the syslib DDcard during the Cobol compile step of the Component Prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23440 Y P N

CMPCSYBK

Specify the blocksize to be used when referencing the syslib DDcard during the C compile step of the Component Prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23440 Y P N

CMPPSYBK

Specify the blocksize to be used when referencing the syslib DDcard during the PL/I compile step of the Component Prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23440 Y P N

IEWLSYSBK

Specify the blocksize to be used when referencing the syslib DDcard during the link-edit step of any prepare. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23200 Y P N

DBRMBLK

Specify the blocksize to be used when referencing DBRM library during the bind plan step. If the value is set to 0, then the blocksize keyword is not used for that particular DD card.Invalid data: will result in possible failures during object prepares.

Numeric 23440 Y P N

REC80BK = 23440 STANDARD BLKSIZE FOR ALL

LRECL=80 DATASETS NUMERIC 23440

REC133BK = 23474

STANDARD BLKSIZE FOR ALL LRECL=121 DATASETS NUMERIC 23474

REC133BK = 23408 STANDARD BLKSIZE FOR ALL

LRECL=133 DATASETS NUMERIC 23408




@HPSENV

TRACE Section

REC512FB = 27648

STANDARD BLKSIZE FOR ALL LRECL=512 DATASETS NUMERIC 27648

Table A-5 TRACE section of @HPSENV


PLIDUMP

Specify if the PLIDUMP DDcard should be included in the batch JCL. (Y) indicates the PLIDUMP DDcard will be included and (N) indicates there will be no PLIDUMP DDcard.Invalid data: will result in no PLIDUMP card being allocated to the batch job.

Y or N Y Y P N

CEEDUMP

Specify if the CEEDUMP DDcard should be included in the batch JCL (Y) indicates the CEEDUMP DDcard will be included and (N) indicates there will be no CEEDUMP DDcard.Invalid data: will result in no CEEDUMP card being allocated to the batch job.

Y or N Y Y P N

SYSUDUMP

Specify if the SYSUDUMP DDcard should be included in the batch JCL. (Y) indicates the SYSUDUMP DDcard will be included and (N) indicates there will be no SYSUDUMP DDcard.Invalid data: will result in no SYSUDUMP card being allocated to the batch job.

Y or N Y Y P N

CTRACE

Specify if the C trace function will be executed. (Y) indicates that the function will be executed and (N) indicates that it is unnecessary..Invalid data: will result in no C trace function when an abend occurs.

Y or N Y Y P N

EDIT

Specify if the JCL for a batch method should be edited. (Y) indicates that the method should display the JCL in edit mode and (N) indicates that the batch method will be submitted. This value only has impact when it is executed within the repository. When a method is processed with EDIT=Y, then the method job is not submitted.Invalid data: will result in no edit of the JCL

Y or N N Y P N

DFLTLOG

Specify the default program log level. This value is copied to TRACE.LOGLEVEL during the initialization of the repository. Invalid data: will result in no edit of the JCL

0 - 9 0 Y P N

DFLTLOGB

Specify the default program log level for background processing. This value is copied to TRACE.LOGLVLBG during the initialization of the repository. Invalid data: will result in tracing data that does not match the user’s desire

0 - 9 0 Y P N




@HPSENV

JCL Section

DFLEXVCU

Specify the default exec log level. This value is copied to TRACE.EXCLEVEL during the initialization of the repository. Invalid data: will result in tracing data that does not match the user’s desire.

0 - 9 0 Y P N

DFLEXBG

Specify the default exec log level for batch processing. This value is copied to TRACE.EXCLVLBG during the initialization of the repository. Invalid data: will result in tracing data that does not match the user’s desire.

0 - 9 0 Y P N

RUN_VERIFY_INI

Specify if the INI verification program should be executed when starting the enterprise repository.Invalid data: will result in the verification program not being executed.

Y or N N Y P N

VERIFY_INI_VALUES

Specify if the INI verification should check the variable validations.Invalid data: will result in the repository continuing normal operation.

Y or N Y N F N

VERIFY_INI_DSNTHIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: N / A

Y or N N N F N

Table A-6 JCL section of @HPSENV


INTRDR_CLASS

Specify the output class of the internal reader. This is used for submitting jobs. Invalid data: will result in possible failures during submission of jobs.

NONE 1 Y E Y

INTRDR_NAME

Specify the name of the internal reader. This is used to write JCL directly to the VSAM RPL to submit jobs. It allows the retrieval of the job number from the job submission. If the function is not supported, than please specify _INTRDR and the VSAM RPL will not be used and jobs will be submitted using the standard SUB function. There will be job number posted since it will not be available. Invalid data: will result in possible failures during submission of jobs.

NONE INTRDR Y E Y

Table A-5 TRACE section of @HPSENV (Continued)



@HPSENV

JOB_CUST

Specify if the client will have a customized skeleton to process the JCL cards. (Y) indicates that the client has a custom job card and the member JCLCST will be imbedded prior to processing the AppBuilder job card and (N) indicates that the AppBuilder supplied job card is being used. If theInvalid data: will result in no customized processing for all job cards.

Y or N N Y E N

JOB_CUST_MTH

Specify if the client will have a customized skeleton to process the JCL cards. (Y) indicates that the client has a custom job card and the member JCLCSTMR will be imbedded prior to processing the AppBuilder job card and (N) indicates that the AppBuilder supplied job card is being used. Invalid data: will result in no customized processing.

Y or N N Y E N

JOB_CUST_MIG

Specify if the client will have a customized skeleton to process the JCL cards. (Y) indicates that the client has a custom job card and the member JCLCSTMG will be imbedded prior to processing the AppBuilder job card and (N) indicates that the AppBuilder supplied job card is being used. Invalid data: will result in no customized processing.

Y or N N Y E N

JOB_CUST_SDS

Specify if the client will have a customized skeleton to process the JCL cards. (Y) indicates that the client has a custom job card and the member JCLCSTSD will be imbedded prior to processing the AppBuilder job card and (N) indicates that the AppBuilder supplied job card is being used. Invalid data: will result in no customized processing.

Y or N N Y E N

JOB_CUST_SEC

Specify if the client will have a customized skeleton to process the JCL cards. (Y) indicates that the client has a custom job card and the member JCLCSTSC will be imbedded prior to processing the AppBuilder job card and (N) indicates that the AppBuilder supplied job card is being used. Invalid data: will result in no customized processing.

Y or N N Y E N

Table A-6 JCL section of @HPSENV (Continued)



@HPSENV

JOB_CUST_IMS

Specify if the client will have a customized skeleton to process the JCL cards. (Y) indicates that the client has a custom job card and the member JCLCSTIM will be imbedded prior to processing the AppBuilder job card and (N) indicates that the AppBuilder supplied job card is being used. Invalid data: will result in no customized processing.

Y or N N Y E N

JOB_CLASS

Specify the job class to be used for batch jobs. Invalid data: will result in possible failures during batch job processing.

NONE 1 Y E Y

JOB_MSGCLASS

Specify the message to be used for the batch jobs submitted. Invalid data: will result in possible failures during batch job processing.

NONE X Y E Y

JOB_TIME

Specify the time parameter to be used in the job card. This will only be included if the value is not blank. Invalid data: will result in possible failures during submission of jobs or batch processing.

NONE NONE Y E N

JOB_PRIORITY

Specify the priority to be used on batch jobs.Invalid data: will result in possible failures during submission of jobs or batch processing.

NONE 12 Y E Y

JOB_REGION

Specify the amount of region size to be used in batch jobs. Invalid data: will result in possible failures during submission of jobs or batch processing.

NONE 6M Y E N

JOB_NIGHTCLA

Specify the job class used to indicate a job is to be executed overnight. This would be an initiator that will hold the job processing until a specified time. Invalid data: will result in possible failures during submission of jobs or batch processing.

NONE 1 Y E Y

JOB_CHAR

Specify the default job character to be used for batch jobs if one is not specified.Invalid data: will result in possible failures during submission of jobs.

NONE M Y E N

JOB_TEXT

Specify the default job description to be used for batch jobs if one is not specified.Invalid data: will result in possible failures during submission of jobs.

NONE JOB Y E N




@HPSENV

SKEL Section

METHOD Section

ZSYSOUT

Specify the sysout class to be used for printed reports.Invalid data: will result in possible failures during submission of jobs.

NONE * Y E N

HPSPRNT

Specify the printer id to be used for printing reports.Invalid data: will result in possible failures during submission of jobs.

NONE NONE Y E Y

Table A-7 SKEL section of @HPSENV


DEFAULT_CHARTHIS VALUE IS RESERVED FOR FUTURE USE.Invalid data: N / A

CHARACTER ? Y E N

RETRY_CODE

Specify the error number returned from C/370 when a file contention exists. This should only be modified if the C/370 runtime has been modified to return a different value (or if SMS has modified this return code).Invalid data: will result in possible failures when data set contentions are encountered.

NONE 61 Y E N

RETRY_COUNT

Specify the number of retries to access a file which is currently used by another user. Invalid data: will result in possible failures when data set contentions are encountered.

Numeric value 10 Y F N

Table A-8 METHOD section of @HPSENV


SORTKW

Specify if the keywords should be stored in collating sequence or as is based on entry by the user. (Y) indicates that the data will be sorted in alphabetic sequence and (N) indicates that data will be stored based on the order entered by the user. Invalid data: will result keywords stored in entry sequence.

Y or N N Y F N




@HPSENV

CRUD Section

Table A-9 CRUD section of @HPSENV


MNEISPF

The minimum number of AppBuilder entity ISPF CRUDs to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 12

Numeric value which is less than the maximum number of entity ISPF cruds

20 Y P N

MXEISPF

The maximum number of AppBuilder entity ISPF cruds to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 28

Numeric value < 999 45 Y P N

MNRISPF

The minimum number of AppBuilder relation ISPF cruds to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 16

Numeric value which is less than the maximum number of relation ISPF cruds

20 Y P N

MXRISPF

The maximum number of AppBuilder relation ISPF cruds to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 36


MNECRUD

The minimum number of AppBuilder entity DB2 cruds to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in value of 8

Numeric value which is less than the maximum number of entity DB2 cruds

20 Y P N

MXECRUD

The maximum number of AppBuilder entity DB2 cruds to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 18



@HPSENV

RMI Section

MNRCRUD

The minimum number of AppBuilder relation DB2 cruds to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 10

Numeric value which is less than the maximum number of relation DB2 cruds

20 Y P N

MXRCRUD

The maximum number of AppBuilder relation DB2 cruds to be retained in storage during online session with the enterprise repository. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 24


MNBCRUD

The minimum number of AppBuilder relation DB2 B-cruds to be retained in storage during online session with the enterprise repository. B-cruds are used to traverse the relationships of the hierarchy. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 32

Numeric value which is less than the maximum number of B-cruds (DB2)

30 Y P N

MXBCRUD

The maximum number of AppBuilder relation DB2 B-cruds to be retained in storage during online session with the enterprise repository. B-cruds are used to traverse the relationships of the hierarchy. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 48


Table A-10 RMI section of @HPSENV


JCLDSNDS

Specify the disposition of the JCL data set. (P) indicates that the JCL data set is a permanent data set. This must be a partitioned data set. (T) indicates that the JCL is stored in a temporary data set. (P) should only be used if the JCL needs to be saved, otherwise the performance is improved when it is not saved.Invalid data: will result in the JCL being saved.

T or P T Y P N

Table A-9 CRUD section of @HPSENV (Continued)



@HPSENV

REPDSN Section

JCLDSN

Specify the data set name where the saved JCL will be saved. The default is to save the JCL in USRVQUAL.JCL which is specified by setting this variable to DEFAULT. If a custom data set is used, this must be a fully qualified partitioned data set.Invalid data: will result in possible error during the processing of batch jobs

DEFAULT or fully qualified partitioned data set

DEFAULT Y P N

STATLOCL

Specify if each method executed should be posted to a status table. (Y) indicates that the data should be logged and (N) indicates that no status will be posted.Invalid data: will result in the method status not being posted

Y or N N Y P N

STATREMT THIS VARIABLE IS RESERVED FOR FUTURE USE. N / A N / A N P N

SUBJOB

Specify if batch jobs should be submitted or should they be saved in the JCL data set only. (Y) indicates that the job should be submitted automatically and (N) indicates that the generated JCL should be saved into the specified data set.Invalid data: will result in the job not being submitted.

Y or N Y Y F N

XTSCHDL THIS VARIABLE IS RESERVED FOR FUTURE USE. N / A N / A N P N

Table A-11 REPDSN section of @HPSENV

Variable Name Description Validation Default MOD USEIP

REPCLST

Specify if the repository level data set should be referenced when accessing clist libraries. (Y) indicates that the repository level clist data set should be used and (N) indicates that the repository level clist library will not be used.Invalid data: will result in the repository level clist data set will not be used.

Y or N N Y H Y

REPDBRM

Specify if the repository level data set should be referenced when accessing DBRM libraries. (Y) indicates that the repository level DBRM data set should be used and (N) indicates that the repository level DBRM library will not be used.Invalid data: will result in the repository level DBRM data set will not be used.

Y or N N Y H Y

Table A-10 RMI section of @HPSENV (Continued)



@HPSENV

REPFTSK

Specify if the repository level data set should be referenced when accessing FTSKELS libraries. (Y) indicates that the repository level FTSKELS data set should be used and (N) indicates that the repository level FTSKELS library will not be used.Invalid data: will result in the repository level FTSKELS data set will not be used.

Y or N N Y H Y

REPINI

Specify if the repository level data set should be referenced when accessing INI libraries. (Y) indicates that the repository level INI data set should be used and (N) indicates that the repository level INI library will not be used.Invalid data: will result in the repository level INI data set will not be used.

Y or N N Y H Y

REPLOAD

Specify if the repository level data set should be referenced when accessing LOAD libraries. (Y) indicates that the repository level LOAD data set should be used and (N) indicates that the repository level LOAD library will not be used.Invalid data: will result in the repository level LOAD data set will not be used.

Y or N N Y H Y

REPMLIB

Specify if the repository level data set should be referenced when accessing ISPF message libraries. (Y) indicates that the repository level ISPF message data set should be used and (N) indicates that the repository level ISPF message library will not be used.Invalid data: will result in the repository level ISPF message data set will not be used.

Y or N N Y H Y

REPPLIB

Specify if the repository level data set should be referenced when accessing ISPF panel libraries. (Y) indicates that the repository level ISPF panel data set should be used and (N) indicates that the repository level ISPF panel library will not be used.Invalid data: will result in the repository level ISPF panel data set will not be used.

Y or N N Y H Y

REPLLIB

Specify if the repository level data set should be referenced when accessing ISPF load libraries. (Y) indicates that the repository level ISPF load data set should be used and (N) indicates that the repository level ISPF load library will not be used.Invalid data: will result in the repository level ISPF load data set will not be used.

Y or N N Y H Y

Table A-11 REPDSN section of @HPSENV (Continued)

Variable Name Description Validation Default MOD USEIP


@HPSENV

TSODD Section

Table A-12 TSODD section of @HPSENV


NTSTEPLB

Specify if the steplib DDcard should be allocated for non-DB2 steps. (Y) indicates that the STEPLIB will be included and (N) indicates that the STEPLIB will not be included for non DB2 processing steps.Invalid data: will result in the STEPLIB not being included.

Y or N Y Y H Y

TSSTEPLB

Specify if the steplib DDcard should be allocated for TSO steps. (Y) indicates that the STEPLIB will be included and (N) indicates that the STEPLIB will not be included for TSO processing steps.Invalid data: will result in the STEPLIB not being included.

Y or N Y Y H Y

TSDB2LOD

Specify if the DB2 load library should be included in the steplib DDcard. (Y) indicates that the DB2 load library will be included and (N) indicates that the DB2 load library will not be included.Invalid data: will result in the DB2 load library not being included.

Y or N N Y H Y

TSPLILNK

Specify if the PL/I load library should be included in the steplib DDcard. (Y) indicates that the PL/I load library will be included and (N) indicates that the PL/I load library will not be included.Invalid data: will result in the PL/I load library not being included.

Y or N N Y H Y

TSPLILIB

Specify if the PL/I load library should be included in the steplib DDcard. (Y) indicates that the PL/I load library will be included and (N) indicates that the PL/I load library will not be included.Invalid data: will result in the PL/I load library not being included.

Y or N N Y H Y

TSC37LNK

Specify if the C/370 load library should be included in the steplib DDcard. (Y) indicates that the C/370 load library will be included and (N) indicates that the C/370 load library will not be included.Invalid data: will result in the C/370 load library not being included.

Y or N N Y H Y

TSC37STP

Specify if the C/370 step load library should be included in the steplib DDcard. (Y) indicates that the c/370 step load library will be included and (N) indicates that the c/370 step load library will not be included.Invalid data: will result in the c/370 step load library not being included.

Y or N N Y H Y


@HPSENV

TSCOBLNK

Specify if the COBOL link library should be included in the steplib DDcard. (Y) indicates that the COBOL link library will be included and (N) indicates that the COBOL link library will not be included.Invalid data: will result in the COBOL link library not being included.

Y or N N Y H Y

TSCOBSTP

Specify if the COBOL step library should be included in the steplib DDcard. (Y) indicates that the COBOL step library will be included and (N) indicates that the COBOL step library will not be included.Invalid data: will result in the COBOL step library not being included.

Y or N N Y H Y

TSIMSRES

Specify if the IMS resident library should be included in the steplib DDcard. (Y) indicates that the IMS resident library will be included and (N) indicates that the IMS resident library will not be included.Invalid data: will result in the IMS resident library not being included.

Y or N N Y H Y

TSMDLOAD

Specify if the AppBuilder mod level load library should be included in the steplib DDcard. (Y) indicates that the mod level load library will be included and (N) indicates that the mod level load library will not be included.Invalid data: will result in the AppBuilder mod level load library not being included.

Y or N N Y H Y

TSMDMSG

Specify if the AppBuilder mod level ISPF message library should be included in the ISPMLIB DDcard. (Y) indicates that the mod level message library will be included and (N) indicates that the mod level message library will not be included.Invalid data: will result in the AppBuilder mod level ISPF message library not being included.

Y or N N Y H Y

TSMDPNL

Specify if the AppBuilder mod level ISPF panel library should be included in the ISPPLIB DDcard. (Y) indicates that the mod level panel library will be included and (N) indicates that the mod level panel library will not be included.Invalid data: will result in the AppBuilder mod level ISPF panel library not being included.

Y or N N Y H Y

TSMDSKL

Specify if the AppBuilder mod level ISPF skeleton library should be included in the ISPSLIB DDcard. (Y) indicates that the mod level skeleton library will be included and (N) indicates that the mod level skeleton library will not be included.Invalid data: will result in the AppBuilder mod level ISPF skeleton library not being included.

Y or N N Y H Y

Table A-12 TSODD section of @HPSENV (Continued)



@HPSENV

TSMDLLIB

Specify if the AppBuilder mod level ISPF load library should be included in the ISPLLIB DDcard. (Y) indicates that the mod level load library will be included and (N) indicates that the mod level load library will not be included.Invalid data: will result in the AppBuilder mod level ISPF load library not being included.

Y or N N Y H Y

TSMDINI

Specify if the AppBuilder mod level INI library should be used. (Y) indicates that the mod level INI library will be included and (N) indicates that the mod level INI library will not be included.Invalid data: will result in the AppBuilder mod level INI library not being included.

Y or N N Y H Y

TSGLBCLS

Specify if global clist libraries should included in the SYSPROC DDcard. (Y) indicates that the global clist libraries will be included and (N) indicates that the global clist libraries will not be included.Invalid data: will result in the global clist libraries not being included.

Y or N Y Y H Y

TSISPTLB

Specify if ISPTLIB should be allocated. (Y) indicates that the ISPTLIB DDcard will be allocated and (N) indicates that it will not be allocated.Invalid data: will result in the ISPTLIB DDcard not being allocated.

Y or N Y Y H Y

TSISPPLB

Specify if ISPPLIB should be allocated. (Y) indicates that the ISPPLIB DDcard will be allocated and (N) indicates that it will not be allocated.Invalid data: will result in the ISPPLIB DDcard not being allocated.

Y or N Y Y H Y

TSISPMLB

Specify if ISPMLIB should be allocated. (Y) indicates that the ISPMLIB DDcard will be allocated and (N) indicates that it will not be allocated.Invalid data: will result in the ISPMLIB DDcard not being allocated.

Y or N Y Y H Y

TSISPSLB

Specify if ISPSLIB should be allocated. (Y) indicates that the ISPSLIB DDcard will be allocated and (N) indicates that it will not be allocated.Invalid data: will result in the ISPSLIB DDcard not being allocated.

Y or N Y Y H Y

Table A-12 TSODD section of @HPSENV (Continued)



@HPSENV

VIEWS Section

COMM Section

Table A-13 VIEWS section of @HPSENV


VWALIGN

Specify if the generated copybooks will contain alignment bytes. These are bytes inserted by the product to ensure that all numeric fields begin on an even boundary. (Y) indicates that the alignment bytes should be added and (N) indicates that the copybooks will not contain the alignment bytes. This value will alter the output of View prepare and component prepare which may result in errors during the execution of the application caused by mis-matching input and output views. Caution must be exercised when this option is modified.Invalid data: will result in the no alignment bytes in the copybook.

Y or N N Y F N

VWDB2L49

Specify if the generated copybooks will use the AppBuilder method of defining variable characters (varchars) or will it use the standard DB2 format. (Y) indicates that the generated COBOL copybook will contain level 49 fields which are used to represent var char fields and (N) indicates that the var chars will be defined using a length field and a char field. This option will only apply to the view prepare method and when the view is prepared as part of a component prepare.Invalid data: will result in the no level 49 support.

Y or N Y Y F N

VWDECLRG

Specify if the size of the decimal field which will result in extended decimal support. When the actual length of the field is larger than this value, then extended decimal support will be used.Invalid data: will result in extended decimal support for decimals with a length greater than 15.

Numeric value less than 31 15 Y F N

Table A-14 COMM section of @HPSENV


EXPLEXC

Specify if the special logic for drawings should be used. (Y) indicates that it ill be and (N) indicates that the standard scoping will be used. Please refer to the Managing Enterprise Repositories manual for additional details.Invalid data: will result in using the special processing for drawings.

Y or N Y Y F N


@HPSENV

EXITS Section

EXPLBOTH

Specify the direction to be used when processing drawing downloads. (Y) indicates that the drawing should be exploded in both directions and (N) indicates that it will only process in one direction. Please refer to the Managing Enterprise Repositories manual for additional details.Invalid data: will result in downloading the drawing using one direction processing.

Y or N N Y F N

FETCHLM

Specify the maximum number of records to be processed during the upload/download processing. This value must match the supported values from the workstation. This value should not be modified by the client.Invalid data: will result in potential system abends during the transfer process.

Numeric 10 N I N

Table A-15 EXITS section of @HPSENV


COMP

Specify if a user exit should be used during Component prepare. (Y) indicates that an exit exists by the name of XCOMP and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

FILE

Specify if a user exit should be used during File prepare. (Y) indicates that an exit exists by the name of XFILE and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

PROCES

Specify if a user exit should be used during Process prepare. (Y) indicates that an exit exists by the name of XPROCES and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

REPORT

Specify if a user exit should be used during Report prepare. (Y) indicates that an exit exists by the name of XREPORT and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

Table A-14 COMM section of @HPSENV (Continued)



@HPSSTAT

@HPSSTATThis file describes the configuration used for the indicate the status of the repository. It is used by the installation workbench to determine if the repository is active.

RULE

Specify if a user exit should be used during Rule prepare. (Y) indicates that an exit exists by the name of XRULE and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

SET

Specify if a user exit should be used during Set prepare. (Y) indicates that an exit exists by the name of XSET and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

VIEW

Specify if a user exit exists for view processing. (Y) indicates that an exit exists by the name of XVIEW and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

WINDOW

Specify if a user exit exists for window processing. (Y) indicates that an exit exists by the name of XWINDOW and (N) indicates that no exit exists.Invalid data: will result in no user exit processing.

Y or N N Y F N

Table A-16 MODEL Section of @HPSENV


MHPS530=GCM530 MHPS531=GCM531 GHPS531=GCGH53 MHPS53AR=GCMA53 GHPS53AR=GCGA53

PROGRAM NAMES FOR SUPPORTED MODELS

Table A-15 EXITS section of @HPSENV (Continued)



@MIGRATE

REPOSITORY Section

@MIGRATEThis file describes the configuration used for the migration processing when using the MIGRATE function. This is a sample skeleton that is used as a template for creating the actual INI files for the MIGRATE function. The name of the actual INI file must be the same as the name of the repository. For example, if MIGRATE is used to move data to a repository called QATEST. Then the name of the INI file must be called QATEST. This file must be stored on the source repository. This is the minimum information necessary to access the target repository to allow a MIGRATE function to operate.

QUALIFIER Section

Table A-17 REPOSITORY section of @HPSSTAT


ENABLE

Specify the current status of the repository. (Y) indicates the repository is active and available and (N) indicates that the repository is unavailable. If the repository is accessed online, the message stored in @HPSENV.REPDOWN/REPDOWN2 is displayed to the user.Invalid data: The repository is considered inactive

Y or N Y Y F N

Table A-18 QUALIFIER section of @MIGRATE


BASEQUAL

Specify the data set prefix to be used when referencing all Base data sets of the target repository.Invalid data: will result in errors during the processing of the Migrate function.


None Y H Y

MODQUAL

Specify the data set prefix to be used when referencing all MOD data sets of the target repository.Invalid data: will result in errors during the processing of the Migrate function.


None Y H Y

REPQUAL

Specify the data set prefix to be used when referencing all REPOSITORY data sets of the target repository.Invalid data: will result in errors during the processing of the Migrate function.


None Y H Y


MIGENVn

REPDSN Section

MIGENVnThis file describes the configuration used for the migration processing. This file exists by version allowing the client to configure the options within each version differently.

MIGRATION Section

REPINI

Specify if the target repository uses the repository level for INI files. (Y) indicates that is has one and (N) indicates that it only uses mod and base levels.Invalid data: The migrate function may reference incorrect data since it could be reading the wrong INI file.

Y or N N Y F N

Table A-19 REPDSN section of @MIGRATE


REPINI

Specify if the target repository uses the repository level for INI files. (Y) indicates that is has one and (N) indicates that it only uses mod and base levels.Invalid data: The migrate function may reference incorrect data since it could be reading the wrong INI file.

Y or N N Y F N

Table A-20 MIGRATION section of @MIGENVn


OPERATING_MODE

Indicates how the migration processing should be performed. THIS VALUE SHOULD NOT BE MODIFIED

N / A NORMAL N I N

TEST_INI_DSN THIS VALUE SHOULD NOT BE MODIFIED. N / A N / A N I N

TEST_PNL_DSN THIS VALUE SHOULD NOT BE MODIFIED. N / A N / A N I N

Table A-18 QUALIFIER section of @MIGRATE (Continued)



MIGENVn

ANALYZEKEY

Specify if collision analysis should be performed using a key of (S)ystemid or (L)ongname. Please refer to the Enterprise Migration Facility manual for additional information regarding collision analysis.Invalid data: Perform the analyze using systemid

S or L L Y F N

CICSTRX

Specify how the CICS transaction id is processed during the import. (S)ource indicates that the source value is migrated into the target repository. (B)lank indicates that the attribute should be blank upon completion of the import. (T)arget indicates that the rule record will be imported, but the current transaction id on the target will be preserved. This option will only operate when the AppBuilderTRX is set to Y. Invalid data: will create problems during AppBuilder internal processing.

S or B or T T Y F Y

IMSTRX

Specify how the IMS transaction id is processed during the import. (S)ource indicates that the source value is migrated into the target repository. (B)lank indicates that the attribute should be blank upon completion of the import. (T)arget indicates that the rule record will be imported, but the current transaction id on the target will be preserved. This option will only operate when the AppBuilderTRX is set to Y. Invalid data: will create problems during AppBuilder internal processing.

S or B or T T Y F Y

EXP_COMMIT

Specify the frequency of DB2 commits. The value indicates the number of objects (entities or relations) processed prior to the commit. An object includes the parts such as source, text and keywords. Together, these form one object. Commit points allow improved concurrency across multiple users with a trade-off in performance. The actual value used will be a factor of the amount of DB2 storage available, the number of concurrent users and overall system performance.Invalid data: will create problems during AppBuilder internal processing.

Numeric value 100 Y P N

Table A-20 MIGRATION section of @MIGENVn (Continued)



MIGENVn

AMI_COMMIT



IMP_COMMIT



DELMIG

Indicate if a migration entity may be deleted by a user. This allows retention of one or more migrations. within the repository. A (Y) indicates that a user may delete a migration entity assuming the appropriate security rights within the repository. A (N) indicates that no migration entities may be deleted.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N




MIGENVn

MIGREL

Identifies the release level of the migration software. Any modifications to the value may result in errors during the processing of any migration files. THIS VALUE MUST NOT BE MODIFIED BY THE USER.Invalid data: will result in possible errors during the migration processing since the value will not be recognized.

N / A MHPS53AR N I N

MIG_FILE_ID

Default high level qualifier for migration files when it is not specified by the user. This is used with the generated second qualifier to form the two node high level qualifier used for all migration files. The second qualifier begins with M followed by a generated number based on the value stored in E_CONTROL.Invalid data: system will result in JCL errors for any exports where the user does not specify a data set prefix.

One valid data set qualifier

HPSOUT Y D Y

RES_TO_FILE

Specify if the results of the migration job processing should be directed to the SDSF output queue or a data set which may be viewed through the repository interface using the RESults method. (Y) indicates the results will be directed to the data set and N specifies that the output should remain in the output queue. One use of the data set is the ability to save the results if so desired. One advantage of the SDSF queue is the reduction in DASD usage.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

RUN_COUNT

Specify if the Count method should be executed automatically at the completion of export, analyze, and import. This information produced is a summary report containing the count of the objects which has completed processing. (Y) indicates that the count should be executed and an (N) indicates that the count method should NOT be executed.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N




MIGENVn

RUN_DETAIL

Specify if the detail report should be executed automatically at the completion of export, analyze and import. This information produced is a detail of the processing which has completed. (Y) indicates that the report should be executed and an (N) indicates that the report should NOT be executed.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

RUN_TREE

Specify printing of the Migration Methods Tree when running Migration methods. (Y) indicates the tree is printed with Migration Export, Analyze and Rebuild Analyze, and (N) indicates the tree is NOT printed.At this time, there is no way to specify that the printing of the tree is desired on some migrations, but not on others. This variable can only be set (Y) or (N) for all Migrations within a version.

Y or N Y Y

RUN_DELTA

Specify if the delta report should be executed automatically at the completion of Analyze. The information produced is a detailed report of the pending changes for the migration. (Y) indicates that the report should be executed and an (N) indicates that the report should NOT be executed.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

FAST_PATH_RUN_DELTA

Specify if the delta report should be executed automatically when performing migrations using the “fastpath” method The information produced is a detailed report of the pending changes for the migration. (Y) indicates that the report should be executed and an (N) indicates that the report should NOT be executed.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N




MIGENVn

RUN_COLLISION

Specify if the collision analysis should be executed automatically during the execution of an Analyze method. (Y) indicates that the method should be executed and an (N) indicates that the method should NOT be executed.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y P N

CONSIDER_COLLISION_AN_ERROR

Specify if collisions detected should be considered an error. (Y) indicates they will be treated as errors and an (N) indicates they will be treated as warning; thus allowing processing to continue.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

RUN_IMP_IF_COLLISION

Specify if import processing should proceed if collisions are detected during the analyze. These objects will potentially fail during the import. (Y) indicates an import may execute with collisions discovered during the analyze and (N) indicates the collisions must be corrected prior to executing the import. This analyze must be executed again to eliminate the collisions.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

RUN_RBDETECTOR

Specify if the rebuild detector should be executed automatically during the migration analyze. This option provides a preview of what will be marked for rebuild upon completion of this set of migration files. This is required if migrations will be used as seeds to the rebuild processing. (Y) indicates the rebuild detector will be executed and (N) indicates that it will not be executed. Invalid data: will result in the rebuild detector being bypassed.

Y or N N Y F N

SIGNAMI

Specify if migration analyze requires an independent approval prior to an import.. (Y) indicates that approval is required and an (N) indicates that no approvals are required.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N




MIGENVn

SIGNIMP

Specify if migration import requires an independent approval prior to a rebuild.. (Y) indicates that approval is required and an (N) indicates that no approval are required. (This is RESERVED FOR FUTURE USE on)Invalid data: N / A

Y or N N Y P N

SIGNRBD

Specify if rebuild analyze requires an independent approval prior to a rebuild prepare. (Y) indicates that approval is required and an (N) indicates that no approval are required. (This is RESERVED FOR FUTURE USE)Invalid data: N / A

Y or N N Y P N

RESPECT_IMP_LOCK

Specify if the import processing will respect outstanding locks in the repository. A locked object may not be updated by another user or process until the original lock has been released. (Y) indicates that current locks will be honored and an (N) indicates that no locks will be honored which may result in lost changes.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y P N

RESPECT_RBD_LOCK

Specify if the Rebuild Package can be deleted during a migrate function where the user has selected rebuild functions. (Y) indicates that the rebuild package will NOT be deleted if the target rebuild package is locked and (N) indicates that the rebuild package will be deleted on the target if it exists.Invalid data: will use N

Y or N Y Y P N

USEREXIT

Specify if a customer developed exit will be activated during the analyze migration processing This exit must be developed using C/370. Please refer to the Enterprise Migration Facility manual for additional details regarding this exit. (Y) indicates the exit will be active and (N) indicates that the exit is not deployed.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N




MIGENVn

CRUD Section

AppBuilderEXIT

Specify if the analyze exit provided by AppBuilder should be activated. This is required if the CICSTRX and / or IMSTRX options are used. (Y) indicates the exit will be active and (N) indicates that the exit is not deployed.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

CHECK_REPOSIT

Validate migration from Source REPOSIT to Target REPOSIT.Specify if migration commands will respect predefined repository paths specified by the Administrator in the Repository to Repository relationship. A locked object may not be updated by another user or process until the original lock has been released. (Y) indicates that current locks will be honored and an (N) indicates that no locks will be honored which may result in lost changes. Invalid data: will create problems during AppBuilder internal processing.

Y or N N

Table A-21 CRUD section of @MIGENVn


MNBCRUD

The minimum number of AppBuilder relation DB2 B-cruds to be retained in storage during migration processing. B-cruds are used to traverse the relationships of the hierarchy. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 32

Numeric value which is less than the maximum number of B-cruds (DB2)

55 Y P N




MIGENVn

MXBCRUD

The maximum number of AppBuilder relation DB2 B-cruds to be retained in storage during migration processing. B-cruds are used to traverse the relationships of the hierarchy. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 48


MNECRUD

The minimum number of AppBuilder entity DB2 cruds to be retained in storage during migration processing. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in value of 8

Numeric value which is less than the maximum number of entity DB2 cruds

35 Y P N

MXECRUD

The maximum number of AppBuilder entity DB2 cruds to be retained in storage during migration processing. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 18


MNEISPF

The minimum number of AppBuilder entity ISPF cruds to be retained in storage during migration processing. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 12

Numeric value which is less than the maximum number of entity ISPF cruds

30 Y P N

MXEISPF

The maximum number of AppBuilder entity ISPF cruds to be retained in storage during migration processing. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 28


Table A-21 CRUD section of @MIGENVn (Continued)



MIGENVn

MNRCRUD

The minimum number of AppBuilder relation DB2 cruds to be retained in storage during migration processing. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 10

Numeric value which is less than the maximum number of relation DB2 cruds

35 Y P N

MXRCRUD

The maximum number of AppBuilder relation DB2 cruds to be retained in storage during migration processing. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 24


MNRISPF

The minimum number of AppBuilder relation ISPF cruds to be retained in storage during migration processing. The LRU routine will release modules once the specified maximum is reached; the number of modules released is the difference between the maximum and the minimum values specified.Invalid data: will result in a value of 16

Numeric value which is less than the maximum number of relation ISPF cruds

30 Y P N

MXRISPF

The maximum number of AppBuilder relation ISPF cruds to be retained in storage during migration processing. The LRU routine will release modules once this value is reached.Invalid data: will result in a value of 36


Table A-21 CRUD section of @MIGENVn (Continued)



MIGENVn

MIGSTATE Section

MIGDEFAULT Section

Table A-22 MIGSTATE section of @MIGENVn


N_AEXP_SUBEXP_EXECEXP_FAILEXP_PASSAMI_SUBAMI_EXECAMI_FAILAMI_PASSAMI_APPRIMP_SUBIMP_EXECIMP_FAILIMP_PASS

THESE VALUES ARE USED INTERNALLY AND MUST NOT BE MODIFIED.

N / A N / A N I N

N_A=0000 THIS VALUE IS USED INTERNALLY AND MUST NOT BE MODIFIED. N/A N/A N I N

MIG_EXIT

Specify the name of a customer developed rexx exec which is executed during the migration processing. Please refer to the Enterprise Migration Facility manual for additional details regarding this exit. Any value other than N/A will activate the exit.Invalid data: errors will occur during the migration processing if this option is set to an exit that does not exists or contains errors within it.

N / A or a valid member name

N / A Y F N

Table A-23 MIGDEFAULT section of @MIGENVn


PRSOURCE

Specify the default option for source processing. This represents the initial value displayed to the user during migration processing. (Y) indicates source should be processed and (N) indicates that source data should not be processed.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y D N


MIGENVn

PRTEXT

Specify the default option for text processing. This represents the initial value displayed to the user during migration processing. (Y) indicates text should be processed and (N) indicates that text data should not be processed.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y D N

PRKEYS

Specify the default option for keyword processing. This represents the initial value displayed to the user during migration processing. (Y) indicates keywords should be processed and (N) indicates that keywords data should not be processed.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y D N

PRCREATE

Specify the default option for import actions; should objects pending create be processed. (Y) indicates that the import will process creates and (N) indicates that creates will not be processed during the import processing.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y D N

PRUPDATE

Specify the default option for import actions; should objects pending update be processed. (Y) indicates that the import will process updates and (N) indicates that updates will not be processed during the import processing.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y D N

PRDELETE

Specify the default option for import actions; should objects pending delete be processed. (Y) indicates that the import will process deletes and (N) indicates that deletes will not be processed during the import processing.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y D N

Table A-23 MIGDEFAULT section of @MIGENVn (Continued)



MIGENVn

RUNIMP

Specify the default import processing option for migrate action. (Y) indicates that the import will selected by default and (N) indicates that import will not be selected by default.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y D N

RUNRBDA

Specify the default rebuild analyze processing option for migrate action. (Y) indicates that the rebuild analyze will be selected by default and (N) indicates that rebuild analyze will not be selected by default. THIS VARIABLE IS RESERVED for future use.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y D N

RUNRBDPR

Specify the default rebuild prepare processing option for migrate action. (Y) indicates that the rebuild prepare will be selected by default and (N) indicates that rebuild prepare will not be selected by default. THIS VARIABLE IS RESERVED for future use.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y D N

RUNRBDIN

Specify the default rebuild install processing option for migrate action. (Y) indicates that the rebuild install will be selected by default and (N) indicates that rebuild install will not be selected by default. THIS VARIABLE IS RESERVED for future used.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y D N

RUNRBDEX

Specify the default rebuild export processing option for migrate action. The rebuild export creates data files which may be used as input into the rebuild workbench to allow preparation of workstation objects. (Y) indicates that the rebuild export will be selected by default and (N) indicates that rebuild export will not be selected by default. THIS VARIABLE IS RESERVED for future used.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y D N




MIGENVn

MIGOVERRIDE Section

RUNDRELS

Specify the default delete relations processing option for migrate action. (Y) indicates that the Delete relations will be selected by default and (N) indicates that Delete relations will not be selected by default. THIS VARIABLE IS RESERVED for future used.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y D N

Table A-24 MIGOVERRIDE section of @MIGENVn


OVSOURCE

Specify if a user may override the default source processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVTEXT

Specify if a user may override the default text processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVKEYS

Specify if a user may override the default keywords processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N




MIGENVn

OVCREATE

Specify if a user may override the default import create processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVUPDATE

Specify if a user may override the default import update processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVDELETE

Specify if a user may override the default import delete processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVIMP

Specify if a user may override the default migrate import processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVRBDA

Specify if a user may override the default migrate rebuild analyze processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

Table A-24 MIGOVERRIDE section of @MIGENVn (Continued)



MIGENVn

OVRBDPR

Specify if a user may override the default migrate rebuild prepare processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVRBDIN

Specify if a user may override the default migrate rebuild install processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVRBDEX

Specify if a user may override the default migrate rebuild export processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

OVDRELS

Specify if a user may override the default migrate delete relations processing option configured by the installation. The user specified value will only apply to the migration being processed. (Y) indicates that the user may override the default and specify their own option and (N) indicates that the default value may not be modified. THIS VARIABLE IS RESERVED for future use.Invalid data: will result in delete relations not being processed.

Y or N N N F N

Table A-24 MIGOVERRIDE section of @MIGENVn (Continued)



@MVSENV

QASTATUS Section

@MVSENVThe following tables define and describe the variables found in each section of the @MVSENV file. These variables identify the mainframe operating environment.

REPOSITORY Section

NLS Section

Table A-25 QASTATUS section of @MIGENVn


VALUE1User defined QA status. These pairs of variables are defined with an increasing suffix

One character N / A Y D N

DESCRIPTION1User defined QA status. These pairs of variables are defined with a increasing suffix

30 upper case characters

N / A Y D N

Table A-26 REPOSITORY section of @MVSENV


HPSREL Identifies the HPS software release. AB2031 AB2031 N I N

Table A-27 NLS section of @MVSENV


NLSCHARIdentifies the AT character (@) for your codepage (hex equivalent should be '7C).

@ @ Y D Y

USDSIGN

Identifies the currency symbol used to determine the hexadecimal value of the dollar sign "$" in the local codepage. This value is set by the installation software to display the dollar in the local code page.

$ $ Y I N

MFCODEPG

Identifies the local code page on the mainframe. This codepage is a number assigned by IBM to designate the character set in each country. This value effects the setting of the USDSIGN variable above.

Valid codepage value in conjunction w/PCCODEPG

037 Y D Y


@MVSENV

LINKAGE Section

ASM Section

PCCODEPG Identifies the OS/2 codepage on the development workstation.

Valid codepage value in conjunction w/MFCODEPG

437 Y D Y

AXCODEPG Identifies the AIX codepage used on development workstation. 850 or 8591 8591 Y D Y

LANGABRV

Identifies the default language abbreviation for repository objects for MLS support at runtime.

Valid language abbreviation in conjunction w/MFCODEPG and PCCODEPG

ENU Y D Y

Table A-28 LINKAGE section of @MVSENV


AMODE Identifies the addressing mode of AppBuilder generated modules.

24, 31 or ANY 31 Y D Y

RMODE Identifies the residency mode of AppBuilder generated modules. 24 or ANY ANY Y D Y

Table A-29 ASM section of @MVSENV


MACLIB Identifies the mainframe Macro library name.

Valid data set name

SYS1.MACLIB Y D Y

MODGEN Identifies the mainframe target MGEN library if the IBM default name is not used.

Valid data set name SYS1.MODGEN Y D Y

HASMMODG Identifies the mainframe Distribution MGEN library.

Valid data set name

SYS1.AMODGEN Y D Y

HASMPGM Identifies the Assembler H program name. Not blank IEV90 Y D Y

APARM1 These are the required compiler options for Assembler H.

NODECK, OBJECT

NODECK, OBJECT N D N

APARM2 These are the optional compiler options for Assembler H. NONE LIST Y D Y

Table A-27 NLS section of @MVSENV



@MVSENV

COBOL Section

C Section

Table A-30 COBOL section of @MVSENV


COBLINK Identifies the VS COBOL Link library.

Valid data set name containing member ILBOCLS

SYS1.COBLIB Y D Y

COB2LINK Identifies the COBOL II Link library.

Valid data set name containing member IGZEBST

COB.V1R3M0.COB2LIB

Y D Y

COB2STEP Identifies the COBOL II Compiler library.

Valid data set name containing member defined by COB2PGM variable below

COB.V1R3M0.COB2COMP

Y D Y

COB2STPISpecify whether to include STEPLIB in the COBOL compile step of rule preparation.

Y or N Y Y D Y

COB2PGM Identifies the name of the COBOL II compiler. Not blank IGYCRCTL Y D Y

CPARM1 These are the required compiler options for COBOL II.

RES, RENT, OBJECT, LIB, NOCMPR2, 'TRUNC(BIN)'

RES, RENT, OBJECT, LIB, NOCMPR2, 'TRUNC(BIN)'

N D N

CPARM2 These are the optional compiler options for COBOL II. NONE

SEQ, LIST, MAP, XREF, 'FLAG(W)', 'DATA(31)', OPT

Y D Y

Table A-31 C section of @MVSENV


C370BAS1 Identifies the C/370 Base Link library.

Valid data set name

EDC.V2R1M0.SEDCBASE Y D Y

C370BAS2

Identifies a second C/370 Base Link library. The common library for PLI may be used here if the C/370 does not exist or is not as current as the PLI.

Valid data set name

EDC.V2R1M0.SIBMBASE Y D Y

C370LNK1 Identifies the C/370 Runtime Link library.

Valid data set name

EDC.V2R1M0.SEDCLINK Y D Y


@MVSENV

PL/I Section

C370LNK2

Identifies a second C Runtime Link library. The common library for PLI may be used here if the C/370 does not exist or is not as current as the PLI.

Valid data set name

EDC.V2R1M0.SIBMLINK Y D Y

C370STEP Identifies the C/370 Compiler library.

Valid data set name containing member defined by C370PGM variable below

EDC.V2R1M0.SEDCCOMP Y D Y

C370PGM Identifies the C/370 compiler program. NONE EDCCOMP Y D Y

C370MSGS Identifies the C/370 Message library.

Valid data set name.

EDC.V2R1M0.SEDCMSGS(EDCMSGE)

Y D Y

C370HDRS Identifies the C/370 Header files. Valid data set name

EDC.V2R1M0.SEDCHDRS Y D Y

C37PARM1 Identifies required C/370 compiler options.

LIST, XREF, SOURCE, OFFSET, AGG

LIST, XREF, SOURCE, OFFSET, AGG

N D N

C37PARM2 Identifies the optional C/370 compiler options. NONE NOMARGINS Y D Y

CSTEPISpecify whether the STEPLIB should be included in the C/370 compile step.

Y or N Y Y D Y

Table A-32 PL/I section of @MVSENV


PLICOMP

Specify whether the PL/I compiler is installed. If so you must enter values for the Variables PLISTEPI, PLISTEP, PLIPGM, and PPARM2 below.

Y or N N Y D Y

PLIBASE Identifies the PL/I Base Link library.

Valid data set name containing member PLIMAIN

PLI.V2R3M0.PLIBASE Y D Y

PLIBASE2Identifies a second PL/I Base Link library which is usually the common library.

Valid data set name containing member PLIMAIN if not in PLIBASE data set above

PLI.V2R3M0.SIBMBASE Y D Y

PLILINK Identifies the PL/I Transient Runtime library.

Valid data set name

PLI.V2R3M0.PLILINK Y D Y

Table A-31 C section of @MVSENV (Continued)



@MVSENV

MVSPGM Section

ISPF Section

PLILINK2Identifies a second PL/I Transient Runtime library which is usually the common library.

PLI.V2R3M0.SIBMLINK

Valid data set name Y D Y

PLISTEPISpecify whether the STEPLIB should be included in the PL/I compile step.

Y or N Y D Y

PLISTEP Identifies the PL/I Compiler library.

Valid data set name containing member defined by variable PLIPGM below

PLI.V2R3M0.PLICOMP Y D Y

PLIPGM Identifies the PL/I compiler program. NONE IEL0AA Y D Y

PARM1 Identifies the required PL/I compiler options.

INC, OP, AG, NEST, STMT, ''OPTIMIZE(TIME)"

INC, OP, AG, NEST, STMT, ''OPTIMIZE(TIME)"

N D N

PPARM2 Identifies the optional PL/I compiler options NONE ''A(F)'', ''X(F)'',

MAP, OF, STG Y D Y

Table A-33 MVSPGM section of @MVSENV


SORTPGM Identifies the mainframe sort program name. Not blank SORT Y D Y

IEBPGMIdentifies the name of the PDS copy utility program if not IEBCOPY.

Not blank IEBCOPY Y D Y

IEBLIBIdentifies the name of the data set which contains the PDS copy utility program if not IEBCOPY.

None Valid data set name if entered Y D Y

LPALIB Identifies the name of the link pack area library.

Valid data set name SYS1.LPALIB Y D Y

Table A-34 ISPF section of @MVSENV


SPFLINK Identifies the name of the ISPF Link library.

Valid data set name ISP.ISPLOAD Y D Y

SPFPROFIdentifies the name of the common ISPF table library which contains member ISPPROF.

Valid data set name NONE Y D Y

Table A-32 PL/I section of @MVSENV (Continued)



@MVSENV

DB2 Section

SPFMLIB1SPFMLIB2SPFMLIB3SPFMLIB4SPFMLIB5

Identifies the names of the ISPF Message libraries used for background TSO jobs.

Valid data set names. NONE Y D Y

SPFPLIB1SPFPLIB2SPFPLIB3SPFPLIB4SPFPLIB5

Identifies the names of the ISPF Panel libraries used for background TSO jobs.


SPFSLIB1SPFSLIB2SPFSLIB3SPFSLIB4SPFSLIB5

Identifies the names of the ISPF Skeleton libraries used for background TSO jobs.


SPFTLIB1SPFTLIB2SPFTLIB3SPFTLIB4SPFTLIB5

Identifies the names of the ISPF Table libraries used for background TSO jobs.


GLBCLST1GLBCLST2GLBCLST3GLBCLST4GLBCLST5

Identifies the names of the ISPF CLIST libraries (SYSPROC) used for background TSO jobs.


Table A-35 DB2 section of @MVSENV


DB2LINK Identifies the name of the DB2 Link library.

Valid data set name

DSN230.DSNLOAD Y D Y

DB2LOADISpecify whether the STEPLIB should be included in the DB2 Preprocessor step.

Y or N Y Y D Y

DB2LOAD Identifies the name of the DB2 Load library.

Valid data set name containing member defined by DB2PRE variable below


DSNUPROC Identifies the name of the DB2 Utility procedure. Not blank DSNUPROC Y D Y

DSNULOAD Identifies the name of the DB2 utility load library.

Valid data set name


DB2PRE Identifies the name of the DB2 Preprocessor program. Not blank DSNHPC Y D Y

Table A-34 ISPF section of @MVSENV (Continued)



@MVSENV

TSO Section

HSM Section

ACCMETH Section

FILES Section

Table A-36 TSO section of @MVSENV


TSOCLSRN Identifies the name of the TSO clear screen command of not CLRSCRN. Not blank CLRSCRN Y D Y

Table A-37 HSM section of @MVSENV


HSMDLPRMIdentifies the parameter string for the delete program in Data set Archival Software.

Not blank PURGE_WAIT Y D Y

HSMDLPGMIdentifies the name of the delete program in Data set Archival Software.

Not blank HDELETE Y D Y

HSNREASN Identifies the reason code issued if the data set is migrated. Numeric 9 Y D Y

Table A-38 ACCMETH section of @MVSENV


IDCMPGMIdentifies the name of the Access Method Services program if not IDCAMS.

Not blank IDCAMS Y D Y

IDCMLIBIdentifies the name of the data set which contains the Access Method Services program.

Valid data set name if entered

NONE Y D Y

NOTFNDRSIdentifies the reason code issued from TSO LISTDSI if the data set is not found.

Numeric 5 Y D Y

Table A-39 FILES section of @MVSENV


RLSEPARM THIS VALUE SHOULD NOT BE MODIFIED. N/A N/A N I N

TAPEUNIT Identifies the name of the unit used to read the AppBuilder cartridge tapes. Not blank CART Y D Y

TAPERETSpecify the number of days to keep tape data sets generated by the AppBuilder users.

Not blank NONE Y D Y


@MVSENV

CODEGEN Section

APRIM Identifies the primary allocation value for AppBuilder VIO data sets. Numeric 15 Y D N

ASEC Identifies the secondary allocation value fro AppBuilder VIO data sets. Numeric 30 Y D N

ADIRBLK Identifies the directory block value for AppBuilder temporary data sets. Numeric 100 Y D N

Table A-40 CODEGEN section of @MVSENV


CGDBCS THIS VALUE SHOULD NOT BE MODIFIED. S or D S N I N

CGLEVEL THIS VALUE SHOULD NOT BE MODIFIED. N/A H(5.1) N I N

CGVER THIS VALUE SHOULD NOT BE MODIFIED. N/A VER53 N I N

DATFM Identifies the default retrieval format for DB2 date values.

EUR, ISO, JIS, USA or LOCAL

ISO Y D Y

TIMFM Identifies the default retrieval format for DB2 time values

EUR, ISO, JIS, USA or LOCAL

ISO Y D Y

DB2DTFMT

If LOCAL entered above on variable DATFM then specify the DB2 date format which matches the date format defined when DB2 was installed at your site.

NONE %Y-%0m-%0d Y D Y

DB2TMFMT

If LOCAL entered above on variable TIMFM then specify the DB2 time format which matches the time format defined when DB2 was installed at your site.

NONE %0t.%0m.%0s Y D Y

BTCHDFMTIdentifies the default date format for the Batch environment.

Not blank MMDDCCYY Y D N

BTCHTFMTIdentifies the default time format for the Batch environment.

Not blank HHHHMMSS N D N

DATESEP Identifies the date separator. Not blank 61 N D N

TIMESEP Identifies the time separator. Not blank 7A N D N

CGDCPIC THIS VALUE SHOULD NOT BE MODIFIED. N/A -PS(15) N I N

CGLOWDTE THIS VALUE SHOULD NOT BE MODIFIED. N/A N/A N I N

NESTLIM

Identifies the maximum nested IF statements in AppBuilder rules. When rules code exceeds this limit, severe error #87959 will occur.

Numeric 40 Y D Y

Table A-39 FILES section of @MVSENV (Continued)



@RBDENVn

KANJIPRN Section

@RBDENVnThis file describes the configuration used for the rebuild processing. A copy of the file exists for each version allowing various configurations within one repository.

RBDPKG Section

Table A-41 KANJIPRN section of @MVSENV


KJPRINT THIS VALUE SHOULD NOT BE MODIFIED. Y or N N N I N

DATACK THIS VALUE SHOULD NOT BE MODIFIED. N/A BLOCK N I N

SBCSFONT THIS VALUE SHOULD NOT BE MODIFIED. N/A H16N N I N

DBCSFONT THIS VALUE SHOULD NOT BE MODIFIED. N/A M32F N I N

PRMODE THIS VALUE SHOULD NOT BE MODIFIED. N/A SOSI2 N I N

FORMDEF THIS VALUE SHOULD NOT BE MODIFIED. N/A A10110 N I N

PAGEDEF THIS VALUE SHOULD NOT BE MODIFIED. N/A D08462 N I N

KJPRTOC THIS VALUE SHOULD NOT BE MODIFIED. N/A U N I N

KJCOPY THIS VALUE SHOULD NOT BE MODIFIED. N/A 1 N I N

Table A-42 RBDPKG section of @RBDENVn


OPERATING_MODE

Indicates how the rebuild processing should be performed. THIS VALUE MUST NOT BE MODIFIED.

N / A NORMAL N I N

TEST_INI_DSN

Indicates how rebuild processing should be tested.THIS VALUE MUST NOT BE MODIFIED.

N/A N/A N I N

ALLOC_DISP

Specify the disposition of temporary data sets created during the rebuild process. Invalid data: will create problems during AppBuilder internal processing.

DELETE orCATLG orKEEP

DELETE Y F N


@RBDENVn

SUPERPR Section

ANALYZE Section

DELETE_REBUILD_PACKAGE

Specify if the rebuild package entity may be deleted once processing has started. (Y) indicates that the entity may be deleted at any time and (N) indicates that it may not be deleted once the rebuild processing has started.Invalid data: will result in no delete of the rebuild package entity once processing has started.

Y or N N Y F N

Table A-43 SUPERPR section of @RBDENVn


EXCEPTION_RPRT

Specify if the prepare function should be initiated when the analyze returns exception processes during the super prepare. (Y) indicates the processing will continue and (N) indicates that the prepare will not be submitted when exceptional processes are discovered.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

Table A-44 ANALYZE section of @RBDENVn


SKIP_AppBuilder1

Specify if preparable objects with a project of AppBuilder1 should be skipped. This allows the client to process AppBuilder delivered objects only when necessary. (Y) indicates that the items will be skipped and (N) indicates that the AppBuilder objects will be included in the processing.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

SKIP_AppBuilder2

Specify if preparable objects with a project of AppBuilder2 should be skipped. This allows the client to process AppBuilder delivered objects only when necessary. (Y) indicates that the items will be skipped and (N) indicates that the AppBuilder objects will be included in the processing.Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F N

Table A-42 RBDPKG section of @RBDENVn (Continued)



@RBDENVn

PREPARE Section

COMMIT_LEVEL

Specify the frequency of DB2 commits during the rebuild analyze processing. The value indicates the number of objects (entities or relations) processed prior to the commit. Commit points allow improved concurrency across multiple users with minor trade-offs in performance.Invalid data: will create problems during AppBuilder internal processing.


RUN_REPORT

Specify if the rebuild report should be executed automatically at the completion of a successful prepare validation. The information produced is a detail of the processing which has completed. (Y) indicates that the report should be executed and an (N) indicates that the report should NOT be executed. Invalid data: will create problems during AppBuilder internal processing.

Y or N Y

STORAGE_INCREMENT

Specify the amount of storage to be allocated when additional storage is required. The amount is in units of 128 bytes. i.e. 100 represents approximately 12,800 bytes to be allocated each time additional storage is required. A larger value indicates large chunks of storage will be available and will improve performance. If small amounts of storage are available, then the lower values will result in more GETMAINS of smaller units. Caution should be exercised when modifying this value.Invalid data: will result in out of memory conditions or poor performance


Table A-45 PREPARE section of @RBDENVn


PROCESS52

Specify if Process prepare should be performed. This is only necessary for compatibility with AppBuilder 5.2. (Y) indicates that the Process will be included in the prepare list and (N) indicates that it will not be included.Invalid data: will result in no Process prepares

Y or N N Y F N

Table A-44 ANALYZE section of @RBDENVn (Continued)



@RBDENVn

RESUBMIT_INCOMPLETE

Specify the default option for processing resubmit of incomplete prepares. This status will most likely occur when prepares abend, thus not updating the object to a failed status. (Y) indicates that the default on the panel is to resubmit the uncompleted items and (N) indicates that incomplete items will not be resubmitted.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

RESUBMIT_FAILED

Specify the default option for processing resubmit of failed prepares. These are objects which have a failed status from a previous prepare. (Y) indicates that the default on the panel is to resubmit the failed items and (N) indicates that failed items will not be resubmitted.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

DISPLAY_PREV_FAILED

Specify if the option to select ignore previous failed is presented to the user. The option allows the user to ignore failed items and proceed with the processing of the rebuild package. This may lead to an application which is either incompletely rebuilt or built incorrectly. (Y) indicates that the option will be presented to the user and (N) indicates that the user may not change this option.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

IGNORE_PREV_FAILED

Specify if the user may ignore previously failed items. The option allows the user to ignore failed items and proceed with the processing of the rebuild package. This may lead to an application which is either incompletely rebuilt or built incorrectly. (Y) indicates that the option will be presented to the user and (N) indicates that the user may not change this option.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

CONT_SUBMIT

Specify the default value for the option to submit jobs continuously. This option is necessary to continue submitting jobs once the specified threshold of jobs is surpassed. Additional jobs are submitted as each job completes, thus keeping the number of active jobs in the queue approximately the same as the specified threshold. (Y) indicates that the default is to end processing after the initially specified threshold has been reached and (N) indicates that jobs will stop submitting once the threshold has been reached. In addition, no jobs will be submitted as the initially submitted jobs are completed.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y D N

MINIMUM_SUBMIT

Specify the minimum number of jobs to submit for each prepare. Numeric 1

Table A-45 PREPARE section of @RBDENVn (Continued)



@RBDENVn

RUN_REPORT

Specify if the rebuild report should be executed automatically at the completion of a successful prepare. This information produced is a detail of the processing which has completed. (Y) indicates that the report should be executed and an (N) indicates that the report should NOT be executed. Invalid data: will create problems during AppBuilder internal processing.

Y OR N Y

NIGHTRUN

Specify if the jobs submitted by the rebuild drivers be executed during the night cycle. (Y) indicates that the jobs will use a special night class initiator specified in @HPSENV. (N) indicates that the jobs submitted should be processed in the normal job classes.Invalid data: will result in using the standard initiators

Y or N N Y F N

TRESHOLD

Specify the default value for the maximum number of jobs to be submitted at any one time. This value also represents the maximum number of jobs in the active queue.Invalid data: will create problems during AppBuilder internal processing.

Numeric value 10 Y D N

PHASE_1

Specify the objects which pertain to phase 1 of the rebuild prepare process.Invalid data: will result in incorrect prepare output from the rebuild analysis processing

N / A SET N I N

PHASE_2


N / A

FILE WINDOW REPORT

N I N

PHASE_3


N / A COMP RULE N I N

PHASE_4


N / A PROCES N I N

Table A-45 PREPARE section of @RBDENVn (Continued)



@RBDENVn

INSTALL Section

Table A-46 INSTALL section of @RBDENVn


IGNORE_FAILED_PREPARES

Specify if the user may ignore previously failed prepares. The option allows the user to ignore failed items and proceed with the processing of the rebuild package. This may lead to an application which is either incompletely rebuilt or built incorrectly. (Y) indicates that the option will be presented to the user and (N) indicates that the user may not change this option.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

DISPLAY_PREV_FAILED

Specify if the option to select ignore previous failed is presented to the user. The option allows the user to ignore failed items and proceed with the processing of the rebuild package. This may lead to an application which is either incompletely rebuilt or built incorrectly. (Y) indicates that the option will be presented to the user and (N) indicates that the user may not change this option.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

RESUBMIT_FAILED

Specify the default option for processing resubmit of failed installs. These are objects which have a failed status from a previous install process. (Y) indicates that the default on the panel is to resubmit the failed items and (N) indicates that failed items will not be resubmitted.Invalid data: will result in errors during the resubmission of Rebuild processing.

Y or N N Y F N

RESUBMIT_INCOMPLETE

Specify if the incomplete jobs should be re-submitted for processing. These are objects have an incomplete status from a previous install process. (Y) indicates that the incomplete objects should be re-submitted and (N) indicates that incomplete items will not be resubmitted.Invalid data: will result in incomplete items not being resubmitted.

Y or N N Y F N


@RBDENVn

IGNORE_PREV_FAILED

Specify if the user may ignore previously failed items. The option allows the user to ignore failed items and proceed with the processing of the rebuild package. This may lead to an application which is either incompletely rebuilt or built incorrectly. (Y) indicates that the option will be presented to the user and (N) indicates that the user may not change this option.Invalid data: will create problems during AppBuilder internal processing.

Y or N N Y F N

NIGHTRUN

Specify if the jobs submitted by the rebuild drivers be executed during the night cycle. (Y) indicates that the jobs will use a special night class initiator specified in @HPSENV. (N) indicates that the jobs submitted should be processed in the normal job classes.Invalid data: will result in using the standard initiators

Y or N N Y F N

REGEN_BIND

Specify if the user wants to change DB2 owner id and/or qualifier in INI files and regenerate DB2 Bind control cards during Rebuild Install. (Y) indicates the user wants to change DB2 owner id and/or qualifier in INI files and regenerate DB2 bind control cards during Rebuild Install, and (N) indicates the user does NOT want to change DB2 owner id and/or qualifier in INI files and regenerate DB2 bind control cards during Rebuild Install.

Y or N N Y N

REGEN_LU2

Specifiy if the user wants to regenerate LU2 install control cards during Rebuild Install. The option allows the user to make corrections to INI variables and regenerate LU2 control cards during Rebuild Install (Y) indicates that the LU2 control cards should be regenerated during Rebuild Install, and (N) indicates that the LU2 control cards should NOT be regenerated during Rebuild Install.

Y or N N

UPDATE_ENT_METHOD_PC

Specify if user wants to update Update ENT_METHOD_STATUS table for PC prepares. (Y) indicates that the ENT_METHOD_STATUS table for PC prepares will be updated, and (N) indicates that the table will not be updated.

Y or N N Y

Table A-46 INSTALL section of @RBDENVn (Continued)



@RBDENVn

ADVICE Section

UPDATE_INTER_BINDS

Specify if user wants to update Update ENT_METHOD_STATUS table for intermediate binds. (Y) indicates that the ENT_METHOD_STATUS table for intermediate binds will be updated, and (N) indicates that the table will not be updated.

Y or N N Y

VSAM_COMMIT Specify the commit level for VSAM copies during rebuild install. Numeric 100

RUN_REPORT

Specify the rebuild report processing option for a successful install. (Y) indicates that the report should be executed and an (N) indicates that the report should NOT be executed. Invalid data: will create problems during AppBuilder external processing.

Y OR N Y

INTERMEDIATE_BIND

Specify if the rebuild install should process intermediate binds. (Y) indicates that they will be processed and (N) indicates that only top binds will be processed.Invalid data: will result in no intermediate binds being processed

Y or N N Y F N

Table A-47 ADVICE section of @RBDENVn


MACHINE

Specify if the machine unit to be used when advice files are passed from the enterprise repository to the workstation preparation workbench. This value is the default and is case sensitive. At this time, the only valid option is Local.Invalid data: will result in no failures on the workstation prepares when the advice file is used.

Local Local N F N

DATABASE_TYPE

Specify if the default database type to be used when advice files are passed from the enterprise repository to the workstation preparation workbench. This value is case sensitive.Invalid data: will result in no failures on the workstation prepares when the advice file is used.

DB2/2InformixSybaseOracle

DB2/2 N F N

Table A-46 INSTALL section of @RBDENVn (Continued)



@SEERENV

RBDSTATE Section

@SEERENVThis file contains configurations that are delivered by AppBuilder and MUST not be modified. This INI file may be accepted from turnovers and placed in the INI data set as is; no customization is necessary.

RBDCLUP Section

OS_TYPE

Specify if the default operating environment to be used when advice files are passed from the enterprise repository to the workstation preparation workbench. This value is case sensitive.Invalid data: will result in no failures on the workstation prepares when the advice file is used.

OS/2WindowsWindows-NTUnixAIX

OS/2 N F N

INCLUDE_MF

Specify if the advice file should include mainframe objects. (N) indicates that the file will only contain PC objects and (Y) indicates that the file will include mainframe objectsInvalid data: will result in no failures on the workstation prepares when the advice file is used.

Y or N N N F N

Table A-48 RBDSTATE section of @RBDENVn


RBD_EXIT

Specify if a rebuild exit is to be used. (Y) indicates that it will be and (N) indicates that it will not be.Invalid data: will create problems during AppBuilder internal processing.

Y or N / A N / A Y F N

Table A-49 RBDCLUP section of @SEERENV


METHOD_ID

Specify the method name to be used for the cleanup procedure. Invalid data: The cleanup of a rebuild package will fail with errors

RBDCLUP RBDCLUP N I N

Table A-47 ADVICE section of @RBDENVn (Continued)



@SEERENV

SUPERPR Section

ANALYZE Section

PREPARE Section

Table A-50 SUPERPR section of @SEERENV


METHOD_ID

Specify the method name to be used for the super prepare procedure. Invalid data: The super prepare of a rebuild package will fail with errors

SUPERPR SUPERPR N I N

Table A-51 ANALYZE section of @SEERENV


METHOD_ID

Specify the method name to be used for the rebuild analyze procedure. Invalid data: The analyze of a rebuild package will fail with errors

RANALYZE RANALYZE N I N

Table A-52 PREPARE section of @SEERENV


METHOD_ID

Specify the method name to be used for the rebuild prepare procedure. Invalid data: The prepare of a rebuild package will fail with errors

RPREPARE RPREPARE N I N

PHASE_CNTSpecify the number of Prepare phases.Invalid data: will result in incorrect analysis of prepare actions

N / A 5 N I N

COMP

Specify the method name to be executed during the prepare phase for each type of object.Invalid data: will result in a failure during the preparation of the objects

N / A PREPCOMP N I N

FILE


N / A PREPFILE N I N

REPORT


N / A PREPREP N I N

RULE


N / A PREPRULE N I N


@SEERENV

PREPARE_PLATFORM Section

SET


N / A PREPSET N I N

WINDOW


N / A PREPWIN N I N

PROCES


N / A PREPPRCB N I N

Table A-53 PREPARE_PLATFORM section of @SEERENV


IMS

Specify the platform where the prepare action must be performed based on the execution environment.Invalid data: will result in a failure during the preparation of the objects

N / A M N I N

MAINFR


N / A M N I N

MVSBAT


N / A M N I N

PC


N / A P N I N

PCCICS


N / A B N I N

PCIMS


N / A B N I N

Table A-52 PREPARE section of @SEERENV (Continued)



@SEERENV

PCCMPS


N / A P N I N

PCCMPU


N / A P N I N

1


N / A P N I N

2


N / A M N I N

3


N / A P N I N

4


N / A M N I N

5


N / A P N I N

6


N / A P N I N

7


N / A P N I N

8


N / A P N I N

9


N / A P N I N

Table A-53 PREPARE_PLATFORM section of @SEERENV (Continued)



@SEERENV

EXECENV Section

INSTALL Section

A


N / A P N I N

B


N / A P N I N

C


N / A P N I N

D


N / A P N I N

Table A-54 EXECENV section of @SEERENV


2

Specify the platform transaction between execution environment and configuration environments.Invalid data: will result in a failure during the preparation of the objects

N / A MAINFR N I N

4

Specify the platform transaction between execution environment and configuration environments.Invalid data: will result in a failure during the preparation of the objects

N / A MVSBAT N I N

Table A-55 INSTALL section of @SEERENV


METHOD_ID

Specify the method name to be used for the rebuild install procedure. Invalid data: The install of a rebuild package will fail with errors

N / A RINSTALL N I N

Table A-53 PREPARE_PLATFORM section of @SEERENV (Continued)



USRENVn

RBDSTATE Section

USRENVnThis file describes the configuration used to describe each version. It will allow each version to be configured based on its particular needs. A copy of the file exists for each version.

FILE_1FILE_2FILE_N

Installation attributes used to allocate data sets used during the rebuild processing.

N / A N / A N I N

PHASE_CNT

Specify the number of install phases.Invalid data: will result in incorrect analysis of install actions

N / A 5 N I N

FILE_62= 1 TGRK PO 80 3120 NEWFREE CATALOG PREPARE SVSTEDSN

N/A N/A N

Table A-56 RBDSTATE section of @AppBuilderENV


ADDESUCCADDRSUCCRBDASUBMRBDAEXCURBDSERRSRBDAEXCPRBDASUCCPREPSUBMPREPEXCUPREPERRSPREPICMPPREPSUCCINSTSUBMINSTEXCUINSTERRSINSTICMPINSTSUCC

Table A-55 INSTALL section of @SEERENV (Continued)



USRENVn

VERSION Section

QUALIFIERS Section

PRODUCT Section

Table A-57 VERSION section of @USRENVn


V

Specify the repository version this file configures. Invalid data: will result in errors processing the data since it will not contain the version information.

One character 0-9, B-Z

NONE Y I Y

ENABLE

Specify the status of the version. (Y) indicates that the version may be used at this time and (N) indicates that the version is currently disabled. Invalid data: will result in no access to this version.

Y or N Y Y F N

Table A-58 QUALIFIERS section of @USRENVn


BASVQUAL

Specify the data set prefix to be used when referencing all base level data sets that are version specific.Invalid data: JCL errors will occur when referencing AppBuilder base level data sets which are versioned.


None Y H Y

USRVQUAL

Specify the data set prefix to be used when referencing user data sets which are versioned.Invalid data: JCL errors will occur when referencing user level data sets which are versioned.


None Y H Y

VSMVQUAL

Specify the data set prefix to be used when referencing base VSAM data sets which are versioned.Invalid data: JCL errors will occur when referencing base VSAM data sets.


None Y H Y

VSUVQUAL

Specify the data set prefix to be used when referencing user VSAM data sets which are versioned.Invalid data: JCL errors will occur when referencing user VSAM data sets. which are versioned.


None Y H Y

Table A-59 PRODUCT section of @USRENVn


BATCH

Specify if the BATCH optional product has been installed. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to batch.

Y or N N Y F N


USRENVn

CFGWB

Specify if the configuration workbench option has been enabled. (Y) indicates that the software is enabled and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to configuration processing.

Y or N N Y F N

CICS

Specify if the CICS cooperative optional product has been installed. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to CICS.

Y or N N Y F N

ENDEVOR THIS VARIABLE IS RESERVED FOR FUTURE USE Y or N N Y F N

HAX THIS VARIABLE IS RESERVED FOR FUTURE USE Y or N N Y F N

ICNV3270

Specify if the IMS 3270 optional product has been installed. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to IMS 3270.

Y or N N Y F N

IMS

Specify if the IMS cooperative optional product has been installed. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to IMS.

Y or N N Y F N

INTERTEST

Specify if Intertest product is installed and the interface should be activated. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to CICS.

Y or N N Y F N

MLS THIS VARIABLE IS RESERVED FOR FUTURE USE. Y or N N Y F N

PCNV3270

Specify if the Pseudo conversational 3270 optional product has been installed. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to CICS 3270.

Y or N N Y F N

RBWB

Specify if the Rebuild Workbench optional product has been installed. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing entities which pertain to rebuild processing.

Y or N N Y F N

RPW

Specify if the Report Writer optional product has been installed. (Y) indicates that the software is installed and (N) indicates that it is not.Invalid data: will result in errors processing reports.

Y or N N Y F N

SDSM THIS VARIABLE IS RESERVED FOR FUTURE USE. Y or N N Y F N

THIS VARIABLE IS RESERVED FOR FUTURE USE. Y or N N Y F N

SECM THIS VARIABLE IS RESERVED FOR FUTURE USE. Y or N N Y F N

SECR THIS VARIABLE IS RESERVED FOR FUTURE USE. Y or N N Y F N

Table A-59 PRODUCT section of @USRENVn (Continued)



USRENVn

PREPARE Section

ARCH The software component for Archetype has been installed. Y or N N Y F N

Table A-60 PREPARE section of @USRENVn


CMPICICS

Specify if mainframe components contain EXEC CICS calls. (Y) indicates that the CICS libraries will be included in the compile and the link edit will include DFHECI and (N) indicates that the components do not contain EXEC CICS calls.Invalid data: will result in not including the CICS stubs.

Y or N N Y F N

GENLIST

Specify if prepare listings should be contained in the SDSF output queue. (Y) indicates that the output will exist in both the results data sets and the output queue and (N) indicates the results will only be available through the RES method. The N option will save space and improve performance.Invalid data: will result in not creating the output in the output queue.

Y or N N Y F N

GENLEX

Specify if rule lexical analyzer should be processed. (Y) indicates that the analyzer will be executed and (N) indicates that it will not.Invalid data: will result in not executing the anlayzer.

Y or N N Y F N

GENSYSCO

Specify if AppBuilder system components may be prepared. (Y) indicates that they may be prepared and (N) indicates that they may not be prepared.Invalid data: will result in no system components prepared.

Y or N N Y F N

FLEPRFGN

Specify if the foreign key index will be generated when the GD method is executed for a file. (Y) indicates that an index will be generated for the foreign key and (N) indicates that the index will not be generated.Invalid data: will result in no foreign index generation.

Y or N N Y F N

FLEPRSFX

Specify if File prepare method should create the output stored in partitioned data sets with suffices in the member name (compatibility for AppBuilder 52). (Y) indicates that a suffix will be used and (N) indicates that the suffix will not be used. There are separate data sets to store the output of the file prepare, thus not needing the suffix. This variable is a compatibility option.Invalid data: will result in no suffix in the member names of the file prepare output.

Y or N N Y F N

Table A-59 PRODUCT section of @USRENVn (Continued)



USRENVn

FLEPRPL1

Specify if the PL/I DCLGEN should be executed during a file prepare. (Y) indicates that PL/I output is created and (N) indicates that PL/I output is not required. The output of File prepare should be configured based on the languages used when creating components since that is the only time the DCLGEN output is necessary.Invalid data: will result in no PL/I output.

Y or N N Y F N

FLEPRCOB

Specify if the COBOL DCLGEN should be executed during a file prepare. (Y) indicates that COBOL output is created and (N) indicates that COBOL output is not required. The output of File prepare should be configured based on the languages used when creating components since that is the only time the DCLGEN output is necessary.Invalid data: will result in no COBOL output.

Y or N Y Y F N

FLEPRC

Specify if the C DCLGEN should be executed during a file prepare. (Y) indicates that C output is created and (N) indicates that C output is not required. The output of File prepare should be configured based on the languages used when creating components since that is the only time the DCLGEN output is necessary.Invalid data: will result in no C output.

Y or N N N F N

VWPRPL1

Specify if the PL/I View copybook should be generated during the View prepare. (Y) indicates that PL/I output is created and (N) indicates that PL/I output is not required. The output of View prepare should be configured based on the languages used when creating components since that is the only time the View prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no PL/I output.

Y or N N N F N

VWPRC

Specify if the C View copybook should be generated during the View prepare. (Y) indicates that C output is created and (N) indicates that C output is not required. The output of View prepare should be configured based on the languages used when creating components since that is the only time the View prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no C output.

Y or N N N F N

VWPRCOB

Specify if the Cobol View copybook should be generated during the View prepare. (Y) indicates that Cobol output is created and (N) indicates that Cobol output is not required. The output of View prepare should be configured based on the languages used when creating components since that is the only time the View prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no Cobol output.

Y or N N N F N

Table A-60 PREPARE section of @USRENVn (Continued)



USRENVn

VWPRASM

Specify if the Assembler View copybook should be generated during the View prepare. (Y) indicates that PL/I output is created and (N) indicates that Assembler output is not required. The output of View prepare should be configured based on the languages used when creating components since that is the only time the View prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no Assembler output.

Y or N N N F N

STPRPL1

Specify if the PL/I Set copybook should be generated during the Set prepare. (Y) indicates that PL/I output is created and (N) indicates that PL/I output is not required. The output of Set prepare should be configured based on the languages used when creating components since that is the only time the Set prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no PL/I output.

Y or N N N F N

STPRC

Specify if the C Set copybook should be generated during the Set prepare. (Y) indicates that C output is created and (N) indicates that C output is not required. The output of Set prepare should be configured based on the languages used when creating components since that is the only time the Set prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no C output.

Y or N N N F N

STPRCOB

Specify if the Cobol Set copybook should be generated during the Set prepare. (Y) indicates that Cobol output is created and (N) indicates that Cobol output is not required. The output of Set prepare should be configured based on the languages used when creating components since that is the only time the Set prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no Cobol output.

Y or N N N F N

STPRASM

Specify if the Assembler Set copybook should be generated during the Set prepare. (Y) indicates that Assembler output is created and (N) indicates that Assembler output is not required. The output of Set prepare should be configured based on the languages used when creating components since that is the only time the Set prepare output is necessary. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in no Assembler output.

Y or N N N F N

SVXFER

Specify if the generated XFER (cobol code) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. If the data is saved, it will be available for review using the RES method.Invalid data: will result in not saving the XFER file at the end of the prepare.

Y or N N Y F N




USRENVn

SVDDX

Specify if the generated DDXFILE (also known as BIND FILE) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. If the data is saved, it will be available for review using the RES method.Invalid data: will result in not saving the DDXFILE file at the end of the prepare.

Y or N N Y F N

SVBNDX

Specify if the generated BNDX file should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVBNXDSN using the implementation name as the member name.Invalid data: will result in not saving the BNDX file at the completion of the prepare.

Y or N N Y F N

SVSETSRC

Specify if the generated Set source should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVSETDSN.Invalid data: will result in not saving the generated Set at the end of the prepare.

Y or N N Y F N

SVCOBSRC

Specify if the generated COBOL source for Rules and Reports should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVCOBDSN.Invalid data: will result in not saving the generated COBOL at the end of the prepare.

Y or N N Y F N

SVCMPSRC

Specify if the extracted component source should be saved. (Y) indicates that it should be saved and (N) indicates that the extracted file will not be saved. The saved data will be stored in the user data set specified by the variable SVCMPDSN.Invalid data: will result in not saving the extracted component source at the end of the prepare.

Y or N N Y F N

SVCMVSRC

Specify if the extracted component views should be saved. (Y) indicates that it should be saved and (N) indicates that the extracted file will not be saved. The saved data will be stored in the user data set specified by the variable SVCMVDSN.Invalid data: will result in not saving the extracted component view at the end of the prepare.

Y or N N Y F N

SVVBSRC

Specify if the generated COBOL view should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVCBDSN.Invalid data: will result in not saving the generated COBOL view at the completion of the prepare.

Y or N N Y F N




USRENVn

SVVBSRC

Specify if the generated COBOL view should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVCBDSN.Invalid data: will result in not saving the generated COBOL view at the completion of the prepare.

Y or N N Y F N

SVVBASRC

Specify if the generated COBOL view (with alignment bytes) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVCADSN.Invalid data: will result in not saving the generated COBOL view (with alignment bytes) at the completion of the prepare.

Y or N N Y F N

SVVPSRC

Specify if the generated PL/I view should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVPLDSN.Invalid data: will result in not saving the generated PL/I view at the completion of the prepare.

Y or N N Y F N

SVVPASRC

Specify if the generated PL/I view (with alignment bytes) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVPADSN.Invalid data: will result in not saving the generated PL/I view (with alignment bytes) at the completion of the prepare.

Y or N N Y F N

SVVASRC

Specify if the generated Assembler view should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVASDSN. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result In not saving the generated Assembler view at the completion of the prepare.

Y or N N N F N

SVVAASRC

Specify if the generated Assembler view (with alignment bytes) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVAADSN. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in not saving the generated Assembler view (with alignment bytes) at the completion of the prepare.

Y or N N N F N




USRENVn

SVVCSRC

Specify if the generated C view should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVCDSN. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result In not saving the generated C view at the completion of the prepare.

Y or N N N F N

SVVCASRC

Specify if the generated C view (with alignment bytes) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVVCADSN. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in not saving the generated C view (with alignment bytes) at the completion of the prepare.

Y or N N N F N

SVSTBCPY

Specify if the generated Cobol set copybooks should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVSTBDSN.Invalid data: will result in not saving the generated COBOL set copybooks at the completion of the prepare.

Y or N N Y F N

SVSTRCPY

Specify if the generated set reference file should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVSTRDSN.Invalid data: will result in not saving the generated set reference file at the completion of the prepare.

Y or N N Y F N

SVSTPCPY

Specify if the generated PL/I set copybooks should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVSTPDSN.Invalid data: will result in not saving the generated PL/I set copybooks at the completion of the prepare.

Y or N N Y F N

SVSTCCPY

Specify if the generated C set copybooks should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVSTCDSN.Invalid data: will result in not saving the generated C set copybooks at the completion of the prepare.

Y or N N Y F N

SVSTECPY

Specify if the generated set error file should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVSTEDSN.Invalid data: will result in not saving the generated set error file at the completion of the prepare.

Y or N N Y F N




USRENVn

SVFLEPL1

Specify if the generated file prepare output for PL/I should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVFLPDSN.Invalid data: will result in not saving the generated file prepare output for PL/I at the completion of the prepare.

Y or N N Y F N

SVFLECOB

Specify if the generated file prepare output for COBOL should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVFLBDSN.Invalid data: will result in not saving the generated file prepare output for COBOL at the completion of the prepare.

Y or N N Y F N

SVFLEC

Specify if the generated file prepare output for C should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVFLCDSN.Invalid data: will result in not saving the generated file prepare output for C at the completion of the prepare.

Y or N N Y F N

SVWNDSRC

Specify if the extracted window (panel) source should be saved. (Y) indicates that it should be saved and (N) indicates that the extracted file will not be saved. The saved data will be stored in the user data set specified by the variable SVWNDDSN.Invalid data: will result in not saving the extracted window (panel) source at the completion of the prepare.

Y or N N Y F N

SVHLPSRC

Specify if the extracted Help source should be saved. (Y) indicates that it should be saved and (N) indicates that the extracted file will not be saved. The saved data will be stored in the user data set specified by the variable SVHLPDSN.Invalid data: will result in not saving the extracted Help source at the completion of the prepare.

Y or N N Y F N

SVSCTSRC

Specify if the extracted Section source should be saved. (Y) indicates that it should be saved and (N) indicates that the extracted file will not be saved. The saved data will be stored in the user data set specified by the variable SVSCTDSN.Invalid data: will result in not saving the extracted Section source at the completion of the prepare.

Y or N N Y F N

SVFRMSRC

Specify if the extracted Form source should be saved. (Y) indicates that it should be saved and (N) indicates that the extracted file will not be saved. The saved data will be stored in the user data set specified by the variable SVFRMDSN.Invalid data: will result in not saving the extracted Form source at the completion of the prepare.

Y or N N Y F N




USRENVn

SVBNDCTL

Specify if the DB2 bind control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVBNDDSN.Invalid data: will result in not saving the DB2 bind control cards at the completion of the prepare.

Y or N N Y F N

SVBNDLST

Specify if the DB2 bind control cards (in textual format) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVBNTDSN.Invalid data: will result in not saving the DB2 bind control cards (in textual format) at the completion of the prepare.

Y or N N Y F N

SVBPKCTL

Specify if the DB2 package bind control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVBPKDSN.Invalid data: will result in not saving the DB2 package bind control cards at the completion of the prepare.

Y or N N Y F N

SVGRTCTL

Specify if the DB2 grant control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVGRTDSN.Invalid data: will result in not saving the DB2 grant control cards at the completion of the prepare.

Y or N N Y F N

SVGPKCTL

Specify if the DB2 package grant control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVGPKDSN.Invalid data: will result in not saving the DB2 package grant control cards at the completion of the prepare.

Y or N N Y F N

SVLNKCTI

Specify if the IMS link control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVLNIDSN.Invalid data: will result in not saving the link control cards at the completion of the prepare.

Y or N N Y F N

SVLNKCTB

Specify if the Batch link control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVLNBDSN.Invalid data: will result in not saving the link control cards at the completion of the prepare.

Y or N N Y F N




USRENVn

SVLNKCTC

Specify if the CICS link control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVLNCDSN.Invalid data: will result in not saving the link control cards at the completion of the prepare.

Y or N N Y F N

SVLNKCTS

Specify if the non-execution environment link control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVLNSDSN.Invalid data: will result in not saving the link control cards at the completion of the prepare.

Y or N N Y F N

SVLNKLST

Specify if the link control cards (in textual format) should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVLKTDSN.Invalid data: will result in not saving the link control cards (in textual format) at the completion of the prepare.

Y or N N Y F N

SVLU2CTL

Specify if the LU2 control cards should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVLU2DSN.Invalid data: will result in not saving the LU2 control cards at the completion of the prepare.

Y or N N Y F N

SVBTVIEW

Specify if the batch viewdef information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVBVWDSN.Invalid data: will result in not saving the batch viewdef data at the completion of the prepare.

Y or N N Y F N

SVBTRLSC

Specify if the batch rule source information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVBRSDSN.Invalid data: will result in not saving the batch rule source data at the completion of the prepare.

Y or N N Y F N

SVBTRLRL

Specify if the batch rule relation information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVBRRDSN.Invalid data: will result in not saving the batch rule relation data at the completion of the prepare.

Y or N N Y F N




USRENVn

SVCIVIEW

Specify if the CICS viewdef information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVCVWDSN.Invalid data: will result in not saving the CICS viewdef data at the completion of the prepare.

Y or N N Y F N

SVCIRLSC

Specify if the CICS rule source information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVCRSDSN.Invalid data: will result in not saving the CICS rule source data at the completion of the prepare.

Y or N N Y F N

SVCIRLRL

Specify if the CICS rule relation information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVCRRDSN.Invalid data: will result in not saving the CICS rule relation data at the completion of the prepare.

Y or N N Y F N

SVCIVDTX

Specify if the CICS vidtext information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVCVIDSN.Invalid data: will result in not saving the CICS vidtext data at the completion of the prepare.

Y or N N Y F N

SVIMVIEW

Specify if the IMS viewdef information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVIVWDSN.Invalid data: will result in not saving the IMS viewdef data at the completion of the prepare.

Y or N N Y F N

SVIMRLSC

Specify if the IMS rule source information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVIRSDSN.Invalid data: will result in not saving the IMS rule source data at the completion of the prepare.

Y or N N Y F N

SVIMRLRL

Specify if the IMS rule relation information should be saved. (Y) indicates that it should be saved and (N) indicates that the generated file will not be saved. The saved data will be stored in the user data set specified by the variable SVIRRDSN.Invalid data: will result in not saving the IMS rule relation data at the completion of the prepare.

Y or N N Y F N

DCFLCDSN

Specify the data set qualifier used to store the DCLGEN output for C. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during the file prepare. attempting to access the data set.

One PDS qualifier

DCLGNC Y F N




USRENVn

DCFLPDSN

Specify the data set qualifier used to store the DCLGEN output for PL/I. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during the file prepare attempting to access the data set.

One PDS qualifier

DCLGNPL1 Y F N

DCFLBDSN

Specify the data set qualifier used to store the DCLGEN output for COBOL. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during the file prepare attempting to access the data set.

One PDS qualifier

DCLGNCOB Y F N

DBRMDSN

Specify the data set qualifier used to store the generated DBRMs. This qualifier is concatenated to the USRVQUAL to form the actual data set name. When using the Configuration workbench, this value maybe over-ridden by the value contained in the database specification.Invalid data: will result errors during any method requiring access to the DBRM library.

One PDS qualifier

APPLDBRM Y F N

STCOBDSN

Specify the data set qualifier used to store the generated set COBOL copybook. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the set copybook library.

One PDS qualifier

SETCOB Y F N

STREFDSN

Specify the data set qualifier used to store the generated set reference data. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the set reference library.

One PDS qualifier

SETREF Y F N

STPL1DSN

Specify the data set qualifier used to store the generated set PL/I copybook. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the set copybook library.

One PDS qualifier SETPL1 Y F N

STCDSN

Specify the data set qualifier used to store the generated set C copybook. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the set copybook library.

One PDS qualifier SETC Y F N

STERRDSN

Specify the data set qualifier used to store the generated set error data. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the set error data library.

One PDS qualifier

SETERR Y F N

VWCOBDSN

Specify the data set qualifier used to store the generated COBOL views. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the View COBOL copybook library.

One PDS qualifier

VIEWCOB Y F N




USRENVn

VWPL1DSN

Specify the data set qualifier used to store the generated PL/I views. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the View PL/I copybook library.

One PDS qualifier

VIEWPL1 Y F N

VWASMDSN

Specify the data set qualifier used to store the generated Assembler views. This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result errors during any method requiring access to the View Assembler copybook library.

One PDS qualifier

VIEWASM Y F N

VWCDSN

Specify the data set qualifier used to store the generated C views. This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result errors during any method requiring access to the View C copybook library.

One PDS qualifier VIEWC Y F N

VWCBADSN

Specify the data set qualifier used to store the generated COBOL views with alignment bytes. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the View COBOL copybook library (with alignment bytes).

One PDS qualifier

VIEWCOBA Y F N

VWPLADSN

Specify the data set qualifier used to store the generated PL/I views with alignment bytes. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result errors during any method requiring access to the View PL/I copybook library (with alignment bytes).

One PDS qualifier

VIEWPL1A Y F N

VWASADSN

Specify the data set qualifier used to store the generated Assembler views with alignment bytes. This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result errors during any method requiring access to the View Assembler copybook library (with alignment bytes).

One PDS qualifier

VIEWASMA Y F N

VWCADSN

Specify the data set qualifier used to store the generated C views with alignment bytes. This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result errors during any method requiring access to the View C copybook library (with alignment bytes).

One PDS qualifier

VIEWCA Y F N




USRENVn

SVSETDSN

Specify the data set qualifier used to store the generated Set source. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved set data.

One PDS qualifier

SRCSTASM Y F N

SVBNXDSN

Specify the data set qualifier used to store the generated BNDX file. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved BNDX data.

One PDS qualifier

SRCBNDX Y F N

SVCOBDSN

Specify the data set qualifier used to store the generated COBOL source. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved generated COBOL source.

One PDS qualifier

SRCCOBOL Y F N

SVCMPDSN

Specify the data set qualifier used to store the extracted component source. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved extracted component source.

One PDS qualifier

SRCCOMP Y F N

SVCMVDSN

Specify the data set qualifier used to store the extracted component views. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved extracted component views.

One PDS qualifier

SRCCMPVW Y F N

SVRULDSN

Specify the data set qualifier used to store the extracted Rule source. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved extracted Rule source.

One PDS qualifier

SRCRULE Y F N

SVSCTDSN

Specify the data set qualifier used to store the extracted Section source. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved extracted Section source.

One PDS qualifier

SRCSECT Y F N

SVFRMDSN

Specify the data set qualifier used to store the extracted Form source. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved extracted Form source.

One PDS qualifier

SRCFORM Y F N




USRENVn

SVVCBDSN

Specify the data set qualifier used to store the generated COBOL views. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved generated COBOL views.

One PDS qualifier

SRCVWCOB Y F N

SVVPLDSN

Specify the data set qualifier used to store the generated PL/I views. This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved generated PL/I views.

One PDS qualifier

SRCVWPL1 Y F N

SVVPADSN

Specify the data set qualifier used to store the generated PL/I views (with alignment bytes). This qualifier is concatenated to the USRVQUAL to form the actual data set name.Invalid data: will result in errors during any method requiring to access the saved generated PL/I views (with alignment bytes).

One PDS qualifier

SRCVWCPLA Y F N

SVVASDSN

Specify the data set qualifier used to store the generated Assembler views. This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in errors during any method requiring to access the saved generated Assembler views.

One PDS qualifier

SRCVWASM Y F N

SVVAADSN

Specify the data set qualifier used to store the generated Assembler views (with alignment bytes). This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in errors during any method requiring to access the saved generated Assembler views (with alignment bytes).

One PDS qualifier

SRCVWASA Y F N

SVVCDSN

Specify the data set qualifier used to store the generated C views. This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in errors during any method requiring to access the saved generated C views.

One PDS qualifier

SRCVWC Y F N

SVVCADSN

Specify the data set qualifier used to store the generated C views (with alignment bytes). This qualifier is concatenated to the USRVQUAL to form the actual data set name. THIS VARIABLE IS RESERVED FOR FUTURE USE.Invalid data: will result in errors during any method requiring to access the saved generated C views (with alignment bytes).

One PDS qualifier

SRCVWCA Y F N




USRENVn

SVSTBDSN

Specify the data set qualifier used to store the generated COBOL set copybooks. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated COBOL set copybooks.

One PDS qualifier

SRCSTCOB Y F N

SVSTRDSN

Specify the data set qualifier used to store the generated set reference file. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated set reference file.

One PDS qualifier

SRCSTREF Y F N

SVSTPDSN

Specify the data set qualifier used to store the generated PL/I set copybooks. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated PL/I set copybooks.

One PDS qualifier

SRCSTPL1 Y F N

SVSTCDSN

Specify the data set qualifier used to store the generated C set copybooks. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated C set copybooks.

One PDS qualifier

SRCSTC Y F N

SVSTEDSN

Specify the data set qualifier used to store the generated set error file. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated set error file.

One PDS qualifier

SRCSTERR Y F N

SVFLPDSN

Specify the data set qualifier used to store the generated File prepare output for PL/I. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated file prepare output for PL/I.

One PDS qualifier

SRCDCPL1 Y F N

SVFLBDSN

Specify the data set qualifier used to store the generated File prepare output for COBOL. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated File prepare output for COBOL.

One PDS qualifier

SRCDCCOB Y F N

SVFLCDSN

Specify the data set qualifier used to store the generated File prepare output for C. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved generated File prepare output for C.

One PDS qualifier

SRCDCC Y F N




USRENVn

SVWNDDSN

Specify the data set qualifier used to store the extracted window (panel) source. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved extracted window (panel) source.

One PDS qualifier

SRCWND Y F N

SVHLPDSN

Specify the data set qualifier used to store the extracted help source. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved extracted help source.

One PDS qualifier

SRCHLP Y F N

SVCPTDSN

Specify the data set qualifier used to store the copybook control information. This is an explicit list of copybooks. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved copybook control data.

One PDS qualifier

SRCCPLS Y F N

SVBNDDSN

Specify the data set qualifier used to store the DB2 bind control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved DB2 bind control cards.

One PDS qualifier

SRCBNDCC Y F N

SVGRTDSN

Specify the data set qualifier used to store the DB2 grant control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved DB2 grant control cards.

One PDS qualifier

SRCGRTCC Y F N

SVBNTDSN

Specify the data set qualifier used to store the DB2 bind control cards (in textual format). This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved DB2 bind control cards (in textual format).

One PDS qualifier

SRCBNDLS Y F N

SVBPKDSN

Specify the data set qualifier used to store the DB2 package bind control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved DB2 package bind control cards.

One PDS qualifier

SRCBPKCC Y F N

SVGPKDSN

Specify the data set qualifier used to store the DB2 package grant control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved DB2 package grant control cards.

One PDS qualifier

SRCGPKCC Y F N




USRENVn

SVLNIDSN

Specify the data set qualifier used to store the IMS link control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved link control cards.

One PDS qualifier

SRCLNKCC Y F N

SVLNCDSN

Specify the data set qualifier used to store the CICS link control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved link control cards.

One PDS qualifier

SRCLNKCC Y F N

SVLNBDSN

Specify the data set qualifier used to store the Batch link control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved link control cards.

One PDS qualifier

SRCLNKCC Y F N

SVLNSDSN

Specify the data set qualifier used to store the non execution environment link control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved link control cards.

One PDS qualifier

SRCLNKCC Y F N

SVLKTDSN

Specify the data set qualifier used to store the link control cards (in textual format). This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved link control cards (in textual format).

One PDS qualifier

SRCLNKLS Y F N

SVLU2DSN

Specify the data set qualifier used to store the LU2 control cards. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved LU2 control cards.

One PDS qualifier

SRCLU2CT Y F N

SVBVWDSN

Specify the data set qualifier used to store the batch viewdef information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved batch viewdef information.

One PDS qualifier

SRCBTVW Y F N

SVBRSDSN

Specify the data set qualifier used to store the batch rule source information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved batch rule source information.

One PDS qualifier

SRCBTRLS Y F N

SVBRRDSN

Specify the data set qualifier used to store the batch rule relation information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved batch rule relation information.

One PDS qualifier

SRCBTRRL Y F N




USRENVn

SVCVWDSN

Specify the data set qualifier used to store the CICS viewdef information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved CICS viewdef information.

One PDS qualifier

SRCCIVW Y F N

SVCRSDSN

Specify the data set qualifier used to store the CICS rule source information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved CICS rule source information.

One PDS qualifier

SRCCIRLS Y F N

SVCRRDSN

Specify the data set qualifier used to store the CICS rule relation information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved CICS rule relation information.

One PDS qualifier

SRCCIRRL Y F N

SVCVIDSN

Specify the data set qualifier used to store the CICS vidtext information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved CICS vidtext information.

One PDS qualifier

SRCCIVID Y F N

SVIVWDSN

Specify the data set qualifier used to store the IMS viewdef information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved IMS viewdef information.

One PDS qualifier

SRCIMVW Y F N

SVIRSDSN

Specify the data set qualifier used to store the IMS rule source information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved IMS rule source information.

One PDS qualifier

SRCIMRLS Y F N

SVIRRDSN

Specify the data set qualifier used to store the IMS rule relation information. This qualifier is concatenated to the USRVQUAL to form the actual data set name. Invalid data: will result in errors during any method requiring to access the saved IMS rule relation information.

One PDS qualifier

SRCIMRRL Y F N




USRENVn

HPSRT Section

Table A-61 HPSRT section of @USRENVn


RUNTDBG

Specify if the RuleView information should be generated. (Y) indicates to generate and update all Ruleview data sets and (N) indicates that they will not be generated. This is a trade-off of performance vs. debugging. By not generating the data, the time required to perform a prepare is reduced, but the use of AppBuilder Ruleview is not allowed. Invalid data: will result in no Ruleview information being generated.

Y or N N Y P N

LOADBS

Specify the data set qualifier used to store the generated load modules which are not specific to any particular execution environment. The output of Sets is an example of this type of generated information.Invalid data: will result in errors during any method requiring to access this data set.

One PDS qualifier

LOADBS Y F N

LOADBT


One PDS qualifier

LOADBT Y F N

LOADCI


One PDS qualifier

LOADCI Y F N

LOADIM


One PDS qualifier

LOADIM

NCALBS

Specify the data set qualifier used to store the generated NCAL modules which are not specific to any particular execution environment. The output of Sets is an example of this type of generated information.Invalid data: will result in errors during any method requiring to access this data set.

One PDS qualifier

NCALBS Y F N


USRENVn

USRLIBS Section

Table A-62 USRLIBS section of @USRENVn


USRNCLBT

Specify the fully qualified data set used to store user batch NCAL modules. This data set is included in all the appropriate link edit jobs.Invalid data: will result in errors during any method requiring to access this data set.

Fully qualified PDS N / A Y F N

USRNCLCI

Specify the fully qualified data set used to store user CICS NCAL modules. This data set is included in all the appropriate link edit jobsInvalid data: will result in errors during any method requiring to access this data set.


USRNCLIM

Specify the fully qualified data set used to store user IMS NCAL modules. This data set is included in all the appropriate link edit jobsInvalid data: will result in errors during any method requiring to access this data set.


USRNCLBS

Specify the fully qualified data set used to store user non-execution environment specific NCAL modules. This data set is included in all the appropriate link edit jobsInvalid data: will result in errors during any method requiring to access this data set.


USRLDBT

Specify the fully qualified data set used to store user batch load modules. This data set is included in all the appropriate link edit jobs.Invalid data: will result in errors during any method requiring to access this data set.


USRLDCI

Specify the fully qualified data set used to store user CICS load modules. This data set is included in all the appropriate link edit jobs.Invalid data: will result in errors during any method requiring to access this data set.


USRLDIM

Specify the fully qualified data set used to store user IMS load modules. This data set is included in all the appropriate link edit jobs.Invalid data: will result in errors during any method requiring to access this data set.


USRLDBS

Specify the fully qualified data set used to store user non-execution environment specific load modules. This data set is included in all the appropriate link edit jobs.Invalid data: will result in errors during any method requiring to access this data set.


USRCPASM

Specify the fully qualified data set used to store user Assembler copybooks. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.


USRCPCOB

Specify the fully qualified data set used to store user COBOL copybooks. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.



USRENVn

USRCPC

Specify the fully qualified data set used to store user C copybooks. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.


USRCPPL1

Specify the fully qualified data set used to store user PL/I copybooks. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.


USRDCASM

Specify the fully qualified data set used to store user Assembler DCLGEN data. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.


USRDCCOB

Specify the fully qualified data set used to store user COBOL DCLGEN data. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.


USRDCC

Specify the fully qualified data set used to store user C DCLGEN data. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.


USRDCPL1

Specify the fully qualified data set used to store user PL/I DCLGEN data. This data set is included in all the appropriate compile jobsInvalid data: will result in errors during any method requiring to access this data set.


Table A-62 USRLIBS section of @USRENVn (Continued)



USRENVn

DB2 Section

Table A-63 DB2 section of @USRENVn


COLLECTION_ID

Specify the collection id to be used for all packages as follows. If PCKG = V, then this value is used and must be populated with a valid collection id. If PCKG = P, the project level collection id is searched first; if it is found, then it will be used, otherwise this value will be used. When PCKG = P, this value must be populated with a valid collection id. If configuration work bench is used, when PCKG = V, then processing is the same as non-config. When PCKG = P, the R_CUECXX is searched first, followed by the CU, if it is found, then it will be used, otherwise this value will be used.In summary, when PCKG = V or P, this value must be populated with a valid collection id.Invalid data: will result in errors during any method requiring to access this value.

Valid DB2 collection id. NONE Y F N

DB2SUBID_ID

Specify the DB2 subsystem id to be used for application plans and packages. This value is optional; it is required if the user wants the application subsystem to be different from the AppBuilder subsystem. The processing will search for this value followed by DB2.DB2SUBID stored in the @HPSENV INI file. Please refer to the mainframe environment manual for additional details regarding DB2 packages.Invalid data: will result in errors during any method requiring to access this value.

Valid DB2 subsystem id NONE Y F N

PLAN_NAME_ID

Specify the plan name to be used for the version when unique plan names are not generated. This is only valid when used with DB2 packages. This value is required to be populated with a valid plan name if PCKG = V or P. This option simplifies administration and reduces clutter in the DB2 catalog. Please refer to the mainframe environment manual for additional details regarding DB2 packages.Invalid data: will result in errors during any method requiring to access this value.

Valid DB2 plan id NONE Y F N


USRENVn

OWNER_ID

Specify the owner id to be used for the version when specific ownerids are not specified. This value is required when PCKG = V. When PCKG = P, the search order begins with the project level value, followed by this value, followed by DB2.DBWOWNR in the @HPSENV. When config workbench is used and PCKG =P, the search order is R_CUECXX, followed by the CU, followed by this value. When PCKG = N, then the search order is project level value, followed by this value, followed by DB2.DB2OWNR from @HPSENV. Please refer to the mainframe environment manual for additional details regarding DB2 packages.In summary, this value is always required when PCKG = V or P, and is optional when PCKG = N.Invalid data: will result in errors during any method requiring to access this value.

Valid DB2 owner id NONE Y F N

QUALIFIER_ID

Specify the qualifier id to be used for the version when specific qualifiers ar not specified. This value is required when PCKG = V. When PCKG = P, the search order begins with the project level value, followed by this value, followed by DB2.DBWOWNR in the @HPSENV. When config workbench is used and PCKG =P, the search order is R_CUECXX, followed by the CU, followed by this value. When PCKG = N, then the search order is project level value, followed by this value, followed by DB2.DB2OWNR from @HPSENV. Please refer to the mainframe environment manual for additional details regarding DB2 packages.In summary, this value is always required when PCKG = V or P, and is optional when PCKG = N.Invalid data: will result in errors during any method requiring to access this value.

Valid DB2 qualifier id NONE Y F N

Table A-63 DB2 section of @USRENVn (Continued)



USRENVn

PROJ-OWNER

i.e. PROJ: DEV VRSN: 1VarName: DEV1OWNER

Specify the owner id to be used for objects with a project of xxxx. The actual variable name is created by concatenating the PROJECT + VERSION + “OWNER”. This owner is the table owner.Invalid data: will result in errors during the prepare of rules and components which contain files.

Valid DB2 owner NONE Y F N

PROJ-QUALIFIERi.e. PROJ: DEV VRSN: 1VarName: DEV1QUALIFIER

Specify the qualifier to be used during bind of rules and components for objects with a project of xxxx. The actual variable name is created by concatenating the PROJECT + VERSION + “QUALIFIER”. This qualifier is used as a parameter to the bind.Invalid data: will result in errors during the prepare of rules and components which contain files.

Valid DB2 qualifier NONE Y F N

PROJ-COLLECTIONi.e. PROJ: DEV VRSN: 1VarName: DEV1COLLECTION

Specify the collection id to be used during bind of rules and components for objects with a project of xxxx. The actual variable name is created by concatenating the PROJECT + VERSION + “COLLECTION”. This collection is only required when DB2 packages are used.Invalid data: will result in errors during the prepare of rules and components which contain files.

Valid DB2 collection id NONE Y F N

PKLIST

Specify if package support should use an explicit packing list or should it use a wildcard list. (E) indicates an explicit list and (W) indicates a wildcard list.Invalid data: will result in errors during the prepare of rules and components which contain files.

E or W W Y F N




USRENVn

PCKG

Specify if package support should be used and how it is used. (V) indicates that packages are available and will use “version” parameters for processing resulting in global plans, collections, etc. (P) indicates that packages are available and projects specific parameters will be used and if they are not found, the version parameters will be used. (N) indicates that packages are NOT supported (standard DBRM member list is used). Please refer to the mainframe environment manual for additional details on plan and package configuration.Invalid data: will result in plan support only

V or P or N N Y F N

DB2GRANT

Specify if grants should be executed. (Y) indicates that they will be and (N) indicates that no grants will be performed.Invalid data: will result in no grants being performed.

Y or N Y Y F N

TEP2PGM=&amp.HMPTEP2 (variable specified during base install located in @HPSenv)

DB2 dynamic program used to perform grant statements. NONE NONE

TEP2PLAN=&amp.PLAN1 (variable specified during base install located in @HPSENV)

Plan name containing dynamic program specified above. NONE NONE

GD_PRIQTY

Specify the primary quantity to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.


GD_SECQTY

Specify the secondary quantity to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.


GD_ERASE

Specify the ERASE option to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.

YES or NO NO Y F N

GD_FREEPG

Specify the FREE PAGE option to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.

Numeric 0 Y F N

GD_PCTFREE

Specify the percentage free option to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.

Numeric 10 Y F N




USRENVn

REGIONS Section

GD_NUMPART

Specify the number of parts to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.

NONE NONE Y F N

GD_PART1GD_PART2GD_PART3GD_PART4GD_PART5

Specify the information required to generate DDL for partitioned tables.Invalid data: will result in errors in the generated DDL.

NONE NONE Y F N

GD_BUFPL

Specify the DB2 buffer pool option to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.

BP0, BP1, BP2, BP32K BP0 Y F N

GD_SUBPAGES

Specify the SUBPAGES option in the index during the generation of the file DDLInvalid data: will result in errors in the generated DDL.

Numeric 4 Y F N

GD_LOCKSZ

Specify the LOCKSIZE option to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.

ANY, PAGE, TABLESPACE ANY Y F N

GD_CLOSE

Specify the CLOSE option to be used during the generation of the file DDL.Invalid data: will result in errors in the generated DDL.

YES or NO NO Y F N

Table A-64 REGIONS section of @USRENVn


CICSREG

Specify the name of the CICS region. This name is also the name of the INI file which describes how the CICS region is configured.Invalid data: will result in errors during the prepare of rules, components and files which are CICS, mainframe and PCCICS.

Valid member name NONE Y E Y

IMSREG

Specify the name of the IMS region. This name is also the name of the INI file which describes how the IMS region is configured.Invalid data: will result in errors during the prepare of rules, components and files which are IMS and PCIMS.





CICS Configuration File

CICS Configuration FileThis file describes the configuration for CICS processing. The name of the file is determined by the CICS name specified in @USRENV REGIONS.CICSREG. This CICS region must also exist in the CM_TRAN table which is used to generate DB2 plan names. All references to AppBuilderdata sets are allocated during the installation of the software unless otherwise specified.

HPSRT Section

IMSAGN

Specify the name of the IMS AGN region. This name is also the name of the INI file which describes how the IMS region is configured.Invalid data: will result in errors during the prepare of rules, components and files which are IMS and PCIMS.


BTCHREG

Specify the name of the BATCH region. This name is also the name of the INI file which describes how the BATCH region is configured.Invalid data: will result in errors during the prepare of rules, components and files which are BATCH and mainframe.


Note All variables contained in the INTRTEST section name should only be prompted when the INTRTEST indicator is set to Y.

Table A-65 HPSRT section of CICS configuration file


TBL1DATA

Is the CICS in-core Table 1 data read from the repository tables or VSAM file?Invalid data: will create problems during AppBuilder internal processing.

VSAM or REPOSIT REPOSIT Y D N

LOADCI

Qualifier for data set used to store the generate CICS load modules. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of CICS objects.

One valid data set qualifier LOADCI Y H Y

NCALCI

Qualifier for data set used to store the generated CICS NCAL modules. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of CICS objects.

One valid data set qualifier NCALCI Y H Y

RLRELATC

Qualifier(s) for VSAM data set used to store the rule relation data for CICS ruleview. This is concatenated with VSMVQUAL.Invalid data: system will result in JCL errors during preparation of CICS objects.


HPS004D1.RLRELATN

Y H Y

Table A-64 REGIONS section of @USRENVn (Continued)




RULESRCC

Qualifier(s) for VSAM data set used to store the rule source data for CICS ruleview. This is concatenated with VSMVQUAL.Invalid data: system will result in JCL errors during preparation of CICS objects.


HPS003D1.RULESRC

Y H Y

Table A-65 HPSRT section of CICS configuration file (Continued)





VIEWDEFC

Qualifier(s) for VSAM data set used to store the rule input/output view data for CICS ruleview. This is concatenated with VSMVQUAL.Invalid data: system will result in JCL errors during preparation of CICS objects.


HPS001D1.VIEWDEF

Y H Y

VIDTEXTC

Qualifier(s) for VSAM data set used to store the rule input/output view and window and set data for CICS runtime. This is concatenated with VSMVQUAL.Invalid data: system will result in JCL errors during preparation of CICS objects.


HPS021D1.VIDTEXT

Y H Y

PLNPROJ

Specify if the object’s project attribute should be used when generating the CICS DB2 plan name. Please refer to the Managing Enterprise Repositories manual for complete details regarding plan name configuration.Invalid data: the project will not be used in the DB2 plan.

Y or N N Y F Y

PLNDFLT

Specify the string to be used in generating the plan name when the AppBuilder project is not used.Invalid data: N / A.

Alphanumeric string with a maximum length of 2 to 4. The actual maximum length is based on the user specification on how PLNTYPE and PLNVRSN are used.

HP Y F Y

PLNTYPE

Specify if the region type (C for CICS) should be included in the plan name.Invalid data: the region type will not be used in the DB2 plan.

Y or N Y Y F Y

PLNVRSN

Specify if the repository version should be included in the plan name.Invalid data: the repository version will not be used in the DB2 plan.

Y or N Y Y F Y

PLNPREF

Specify what string is used as the prefix of the generated plan name. (B) indicates that the generated bitmap value is the prefix while (P) specifies the AppBuilder project is used as the prefix.Invalid data: the BITMAP will be used as the prefix in the generated plan name.

B or P B Y F Y

Table A-65 HPSRT section of CICS configuration file (Continued)



PREPOPT Section

CICS Section

Table A-66 PREPOPT section of CICS configuration file


RDOLU2

Specify if the AppBuilder CICS autoinstall feature should be used. This function will perform LU2 updates in batch mode. (Y) indicates that the feature will be executed and (N) indicates that the feature will not be deployed. This function requires that CICS be active, otherwise an error code is returned to the user during the preparation.Invalid data: the LU2 step will not be executed

Y or N Y Y F Y

RDOCSDGN THIS VARIABLE IS RESERVED FOR FUTURE USE. N / A N / A N F N

RDOCSDLD THIS VARIABLE IS RESERVED FOR FUTURE USE. N / A N / A N F N

RDOASM THIS VARIABLE IS RESERVED FOR FUTURE USE. N / A N / A N F N

Table A-67 CICS section of CICS configuration file


REGIONCNT

Specify the number of CICS regions to be processed during the preparation. This value allows for MRO processing. There is no predefined processing for any particular region. Each region is customized using the INI variables. For non-MRO processing, this value will be set to one. Invalid data: the preparation will fail when processing the information for each region.

Numeric value 1 Y F Y

CICSVERSpecify the version of CICS used for HPS processing. Invalid data: N / A

3 or 4 3 Y E Y

CICSREL

Specify the release of CICS used for HPS processing. Invalid data: will create problems during AppBuilder internal processing.

2 or 3 2 Y E Y

CICSTRAN

Specify if the CICS translator will be executed for rule prepares. (Y) indicates that the translator will be executed and (N) indicates that it will not. Invalid data: will create problems during AppBuilder internal processing.

Y or N Y Y F Y



CICSLNK

Specify whether Rules and Components should be linked with the RENT or NORENT link edit parameter.Invalid data: system will result in JCL errors during preparation of CICS objects.

RENT or NORENT NORENT Y D N

CLI

Specify which DB2 interface module should be included for dynamic linking. (Y) indicates that the AppBuilder DB2 interface (HPSCLI) is used and a (N) indicates the standard DB2 interface DSNHLI is used. the AppBuilder DB2 interface is required when using Ruleview and breakpoints are required for every SQL call. The standard DB2 interface provides improved performance. For static linking, dynamic COBOL and component load modules, the standard DB2 interface is always used.Invalid data: the AppBuilder CLI will be included during link of rule.

Y or N N Y F N

NEWCPYPM

Specify the name of the AppBuilder newcopy transaction used to update CICS during the LU2 processing. Invalid data: the LU2 update processing will fail.

Valid CICS transaction HS06 N H N

CEDA

Specify the name of the CICS CEDA transaction. Invalid data: the LU2 update processing will fail.

Valid CICS transaction CEDA Y E Y

CEMT

Specify the name of the CICS CEMT transaction. Invalid data: the LU2 update processing will fail.

Valid CICS transaction CEMT Y E Y

ONE_CICS_TRX

Specify if only one CICS transaction will be used within a CICS region. When this value is set, all transactions generated will have the same value. This type of setup should only be used when DB2 packages is deployed. It simplifies administration. This is an optional valueInvalid data: the CICS rules will have the incorrect transaction id generated.

Valid CICS transaction NONE Y E Y

PCIOPGM

Specify the name of the AppBuilder cooperative communications program. This is used to define generated transactions. Invalid data: the LU2 update processing will fail.

Valid CICS program name

HPETM10 N H N

PSDOPGM

Specify the name of the AppBuilder pseudo conversation communications program. This is used to define generated transactions. Invalid data: the LU2 update processing will fail.

Valid CICS program name

HPETM10 N H N

Table A-67 CICS section of CICS configuration file (Continued)




UTBLTRAN

Specify the transaction name used to update the AppBuilder in-core table. Invalid data: the LU2 update processing will fail.

Valid CICS transaction UTBL N H N

FCTRLRLN

Specify the FCT name associated with the AppBuilder rule relations VSAM file. Invalid data: the LU2 update processing will fail.

Valid CICS FCT name HPS004D1 N H N

FCTRULES

Specify the FCT name associated with the AppBuilder rule source VSAM file. Invalid data: the LU2 update processing will fail.


FCTVIEW

Specify the FCT name associated with the AppBuilder rule input and output view vsam file. Invalid data: the LU2 update processing will fail.


FCTVIDTX

Specify the FCT name associated with the AppBuilder rule, window and set vsam file. Invalid data: the LU2 update processing will fail.


CPLITRN

Specify the CICS PL/I translator program name. This is used during prepare of PL1 components.Invalid data: the preparation of CICS PL/I objects will fail.

Valid member name DFHEPP1$ Y E Y

HASMTRN

Specify the CICS Assembler translator program name. This is used during prepare of Assembler components.Invalid data: the preparation of CICS Assembler objects will fail.

Valid member name DFHEAP1$ Y E Y

CCOBTRN

Specify the CICS Cobol translator program name. This is used during prepare of Cobol components.Invalid data: the preparation of CICS Cobol objects will fail.

Valid member name DFHECP1$ Y E Y

C370TRN

Specify the CICS C/370 translator program name. This is used during prepare of C/370 components.Invalid data: the preparation of CICS C/370 objects will fail.

Valid member name DFHEDP1$ Y E Y

CICSLCOB

Specify the data set which contains the CICS cobol compiler module. Invalid data: the preparation of CICS objects will fail.

Valid data set which exists

CICS.COBLIB Y E Y

CICSLPLI

Specify the data set which contains the CICS PL/I compiler module. Invalid data: the preparation of CICS objects will fail.

Valid data set which contains????

CICS.PL1LIB Y E Y

CICSLMAC

Specify the data set which contains the CICS assembler compiler module. Invalid data: the preparation of CICS objects will fail.


CICS.MACLIB Y E Y





INTRTEST Section

CICSRUNI

Specify if the CICS runtime library will be included in the steplib of the translator step. (Y) indicates that it will be included and N indicates that it will not. Invalid data: the preparation of CICS objects will fail.

Y or N N Y E Y

CICSRUNT

Specify the data set which contains the CICS runtime modules.Invalid data: the preparation of CICS objects will fail.


CICS.SDFHLOAD Y E Y

COBCLINK

Specify the data set which contains the CICS cobol II link modules. Invalid data: the preparation of CICS objects will fail.


COBOLII.COB2CICS Y E Y

Table A-68 INTRTEST section of CICS


INTRASM

Specify the Intertest Assembler module. Invalid data: the preparation of CICS assembler components will fail if the INTERTEST option is set to Y in the PRODUCT section of the @USRENVn.

Valid member name

IN25SYMA Y E Y

INTRCOB

Specify the Intertest Cobol module. Invalid data: the preparation of CICS cobol components will fail if the INTERTEST option is set to Y in the PRODUCT section of the @USRENVn.

Valid member name

IN25SCOB2 Y E Y

INTRPLI

Specify the Intertest PL/I module. Invalid data: the preparation of CICS PL/I components will fail if the INTERTEST option is set to Y in the PRODUCT section of the @USRENVn.

Valid member name

IN25SYMP Y E Y

INTRSTEP

Specify the data set which contains the intertest modules. Invalid data: the preparation of CICS components will fail with JCL error if the INTERTEST option is set to Y in the PRODUCT section of the @USRENVn.

Valid data set name

CICS.INTR.LOADLIB Y E Y

PROTSYM

Specify the Intertest PROTSYM data set. Invalid data: the preparation of CICS components will fail with JCL error if the INTERTEST option is set to Y in the PRODUCT section of the @USRENVn.

Valid data set name

VCICS.INTR.PROTSYM Y E Y





REGION1 Section

Table A-69 REGION1 section of CICS configuration file


REGIONID

Specify the VTAM applid of the AppBuilder CICS region. Invalid data: the preparation of CICS objects will fail attempting to update the CICS definitions.

N / A NONE Y E Y

DOGRPLS

Specify if the AppBuilder groups should be added to the CICS start-up group list during the processing of CICS objects. (Y) indicates that the AppBuilder group will be added and (N) indicates that the AppBuilder group will not be added. Invalid data: the group will not be added.

Y or N N Y F Y

DOTRANS

Specify if the AppBuilder transactions should be defined to the CICS during the processing of CICS objects. (Y) indicates that new transactions will be defined and (N) indicates that new transactions will not be defined. Invalid data: the transaction will not be added.

Y or N Y Y F Y

DOFILEVW

Specify if the FCT for the AppBuilder view definitions should be updated when CICS objects are processed. (Y) indicates that the FCTVIEW will be updated and (N) indicates that it will not. Invalid data: the FCTVIEW will not be updated

Y or N Y Y F Y

DOFILERL

Specify if the FCT for the AppBuilder rule relations should be updated when CICS objects are processed. (Y) indicates that the FCTRLRLN will be updated and (N) indicates that it will not. Invalid data: the FCTRLRLN will not be updated

Y or N Y Y F Y

DOFILESR

Specify if the FCT for the AppBuilder rule source should be updated when CICS objects are processed. (Y) indicates that the FCTRULES will be updated and (N) indicates that it will not. Invalid data: the FCTRULES will not be updated

Y or N Y Y F Y

DOFILEVD

Specify if the FCT for the AppBuilder Rule, Window, Set definitions should be updated when CICS objects are processed. (Y) indicates that the FCTVIDTX will be updated and (N) indicates that it will not. Invalid data: the FCTVIDTX will not be updated

Y or N Y Y F Y



DOUTBL

Specify if the AppBuilder UTBL transaction should be executed when processing CICS objects. This transaction will update the AppBuilder in-core tables. (Y) indicates that the transaction is executed and (N) indicates that it is not. Invalid data: the UTBL transaction will not be executed

Y or N Y Y F Y

GRPSTART

Specify the name of the CICS start-up group list when CICS is started. This is used if the DOGRPLS is set to Y. This is the group list the AppBuilder group will be added to. Invalid data: the adding of the AppBuilder group to the start-up group will fail

Valid CICS group name NONE Y F Y

GRPLOC

Specify where the AppBuilder group should be added when it is defined to the start-up grouplist. (B)efore indicates that the AppBuilder group will be added to the start-up list before the group defined to the variable GRPLOCNM and (A)fter indicates the group will be added after the GRPLOCNM. Invalid data: the adding of the AppBuilder group to the start-up group will fail

B or A B Y F Y

GRPLOCNM

Specify the group name that is used as the reference point for adding HPS groups to he CICS start-up list. Invalid data: the adding of the AppBuilder group to the start-up group will fail

Valid CICS group name NONE Y F Y

GRPPREFX

Specify how the AppBuilder group names are generated. The group name is a combination of HPS project and CICS group. This indicates if the whether the AppBuilder project or the CICS group is used as the prefix. C indicates the CICS group will be used as the prefix and H indicates the AppBuilder project will be used as the prefix. Invalid data: will create problems during AppBuilder internal processing.

C or H H Y F Y

PPHPSPRJ

Specify if the AppBuilder project is used as part of the generated CICS group name for PPTs. (Y) indicates that the project is used and (N) indicates the project is not used. Invalid data: the AppBuilder project will not be used when defining the groups

Y or N Y Y F Y

Table A-69 REGION1 section of CICS configuration file (Continued)




PCHPSPRJ

Specify if the AppBuilder project is used as part of the generated CICS group name for PCTs. (Y) indicates that the project is used and (N) indicates the project is not used. Invalid data: the AppBuilder project will not be used when defining the groups

Y or N Y Y F Y

PPTGROUP

Specify the CICS group name to be used for defining PPTs.. Invalid data: the PPT definitions will be defined to the invalid group

Valid CICS group name HPS Y F Y

PCTGROUP

Specify the CICS group name to be used for defining PCTs.. Invalid data: the PCT definitions will be defined to the invalid group

Valid CICS group name HPS Y F Y

TMPGRP

Specify the prefix used for defining the temporary group which includes the userid as the suffix. Invalid data: the CICS definitions will be defined to the invalid group

A alphabetic character H Y F Y

USE_LU2_TEMP_GROUP

Specify whether to eliminate LU2 Install statements for TEMP groups, during rebuild or superprepares. (Y) indicates that the LU2 statements for TEMP groups are eliminated, and (N) indicates that they are not eliminated.

Y or N N

LOGAPLL1LOGAPPL2LOGAPPL3

Specify VTAM applids used for HPS lu2 processing. These ids must be defined to both CICS and VTAM. Invalid data: the processing of LU2 functions will fill during update

Valid member names

A05HPS1A05HPS2A05HPS3

Y F Y

CSDNAME THIS VARIABLE IS RESERVED FOR FUTURE USE. N / A N / A N F N

ASMOUT THIS VARIABLE IS RESERVED FOR FUTURE USE. N / A N / A N F N

Table A-69 REGION1 section of CICS configuration file (Continued)



HPSBTCH Configuration File

HPSBTCH Configuration FileThis file describes the configuration for batch processing. The name of the file is determined by the batch name specified in @USRENV. This batch region must also exist in the CM_TRAN table which is used to generate DB2 plan names.

HPSRT Section

Table A-70 HPSRT section of HPSBTCH configuration file


LOADBT

Qualifier for data set used to store the generated batch load modules. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of batch objects.


LOADBT Y H Y

NCALBT

Qualifier for data set used to store the batch generated NCAL modules. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of batch objects.


NCALBT Y H Y

RLRELATB

Qualifier(s) for VSAM data set used to store the rule relation data for batch ruleview. This is concatenated with VSMVQUAL.Invalid data: system will result in JCL errors during preparation of batch objects.


BATCH.RLRELATN Y H Y

RULESRCB

Qualifier(s) for VSAM data set used to store the rule source data for batch ruleview. This is concatenated with VSMVQUAL.Invalid data: system will result in JCL errors during preparation of batch objects.


BATCH.RULESRC Y H Y

VIEWDEFB

Qualifier(s) for VSAM data set used to store the rule input/output view data for batch ruleview. This is concatenated with VSMVQUAL.Invalid data: system will result in JCL errors during preparation of batch objects.


BATCH.VIEWDEF Y H Y

PLNPROJ

Specify if the object’s project attribute should be used when generating the batch DB2 plan name. Please refer to the Managing Enterprise Repositories manual for complete details regarding plan name configuration.Invalid data: the project will not be used in the DB2 plan.

Y or N N Y F Y


HPSBTCH Configuration File

PLNDFLT

Specify the string to be used in generating the plan name when the AppBuilder project is not used.Invalid data: N / A.

An alphanumeric string with a maximum length of 4. The actual length used will be constrained to 2 or three based on the combination on whether PLNTYPE and PLNVRSN are used.

PL Y F Y

PLNTYPE

Specify if the region type (B for batch) should be included in the plan name.Invalid data: the region type will not be used in the DB2 plan.

Y or N Y Y F Y

PLNVRSN

Specify if the repository version should be included in the plan name.Invalid data: the repository version will not be used in the DB2 plan.

Y or N Y Y F Y

PLNPREF

Specify what string is used as the prefix of the generated plan name. B indicates that the BITMAP value is the prefix while P specifies the AppBuilder project is used as the prefix.Invalid data: the BITMAP will be used as the prefix in the generated plan name.

B or P B Y F Y

Table A-70 HPSRT section of HPSBTCH configuration file (Continued)



IMS Configuration File

BATCH Section

IMS Configuration FileThis file describes the configuration for IMS processing. The name of the file is determined by the IMS name specified in @USRENV REGIONS.IMSREG. This IMS region must also exist in the CM_TRAN table which is used to generate DB2 plan names. All references to AppBuilder data sets are allocated during the installation of the software unless otherwise specified.

HPSRT Section

Table A-71 BATCH section of HPSBTCH configuration file


HLI

Specify which DB2 interface module should be included for dynamic linking. (Y) indicates that the AppBuilder DB2 interface (HPSHLI) is used and a (N) indicates the standard DB2 interface DSNHLI is used. the AppBuilder DB2 interface is required when using Ruleview and breakpoints are required for every SQL call. The standard DB2 interface provides improved performance. For static linking, dynamic COBOL and component load modules, the standard DB2 interface is always used.Invalid data: the AppBuilder CLI will be included during link of rule.

Y or N N Y F N

BTCHLNK

Specify whether Rules and Components should be linked with the RENT or NORENT link edit parameter.Invalid data: system will result in JCL errors during preparation of Batch objects.

RENT or NORENT

NORENT Y D N

Table A-72 HPSRT section of IMS configuration file


LOADIM

Qualifier for data set used to store the generated IMS load modules. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of IMS objects.

One valid data set qualifier LOADIM Y H Y

NCALIM

Qualifier for data set used to store the generated IMS NCAL modules. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of IMS objects.

One valid data set qualifier NCALIM Y H Y



RLRELATI

Qualifier(s) for VSAM data set used to store the rule relation data for IMS ruleview. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of IMS objects.


HPI004D1. RLRELATN Y H Y

RULESRCI

Qualifier(s) for VSAM data set used to store the rule source data for IMS ruleview. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of IMS objects.


HPI004D1. RULESRC Y H Y

VIEWDEFI

Qualifier(s) for VSAM data set used to store the rule input/output view data for IMS ruleview. This is concatenated with USRVQUAL.Invalid data: system will result in JCL errors during preparation of IMS objects.


HPI004D1. VIEWDEF Y H Y

PLNPROJ

Specify if the object’s project attribute should be used when generating the IMS DB2 plan name. PLEASE USE THE DEFAULT VALUE ONLY.

Y or N Y N D Y

PLNDFLT Reserved for future use in IMS. N/A N/A D D Y

PLNTYPE

Specify if the region type should be included in the plan name. PLEASE USE THE DEFAULT ONLY.

Y or N Y N D Y

PLNVRSN

Specify if the repository version should be included in the plan name.PLEASE USE THE DEFAULT ONLY.

Y or N Y N D Y

PLNPREF

Specify what string is used as the prefix of the generated plan name. P specifies AppBuilder project is used as the prefix. B indicates that the BITMAP value is the prefix.PLEASE USE THE DEFAULT ONLY.

P or B P N D Y

PLNBTCH

Specify if you want a separate plan to be generated for batch rules.Invalid data: a separate plan will not be generated.

Y or N N Y D Y

Table A-72 HPSRT section of IMS configuration file (Continued)




PREPOPT Section

IMS Section

Table A-73 PREPOPT section of IMS configuration file


RDOLU2

Specify if the AppBuilder IMS auto-install feature should be used. This function will perform LU2 updates in batch mode. (Y) indicates that the feature will be executed and (N) indicates that the feature will not be deployed. The function requires that IMS be active, otherwise an error code is returned to the user during the preparation.Invalid data: the LU2 step will not be executed.

Y or N Y Y F Y

Table A-74 IMS section of IMS configuration file


REGIONCNT

Specify the number of IMS regions to be processed during the preparation. There is no predefined processing for any particular region. Each region is customized using the INI variables.Invalid data: the preparation will fail when processing the information for each region.

Numeric value 1 Y F Y

REGIONID Specify IMS region’s APPLID. Valid APPLID name NONE Y F Y

IMSREG Specify IMS system name. Valid member name NONE Y E Y

IMSLNK

Specify whether Rules and Components should be linked with the RENT or NORENT link edit parameter.Invalid data: system will result in JCL errors during preparation of IMS objects.

RENT or NORENT NORENT Y D N

MACLIB

Specify IMS library containing macros for running PSBGENs.Invalid data: system will result in JCL errors during PSBGENs.

Valid data set name

SYS1.IMS. MACLIB Y D Y

IMSCAP

Specify whether to use the old style generation of CM_TRAN table consisting of PROJECT + ‘M’ + Version Project is zero filled, i.e., DEV0. PLEASE USE THE DEFAULT VALUE ONLY.

Y or N Y N D N

IMSRES Specify the IMS resident library. Valid data set name

IMS410.VENDOR.RESLIB

Y D Y



REGION1 Section

IMSAGN Not used anymore.

IMSDD Not used anymore.

UTBLTRAN Specify the AppBuilder transaction for updating in-core table. Valid Tran. UTBL0000 N D N

CREGJOB Specify the jobname for IMS control region. Valid jobname NONE Y F Y

IMSPROC Specify the VSAM buffer cards for AppBuilder/IMS Database access.

Valid data set name NONE Y F Y

DBVIEW Specify database name for view definitions.

Valid database name HPI001D1 N D N

DBRLSRC Specify database name for rule source definitions.


DBRLREL Specify database name for rule relations definitions.


Table A-75 REGION1 section of IMS configuration file


REGIONID Specify the IMS region name to be used for BMPs.

Valid region name NONE N F N

DOTRANS Specify if AppBuilder transaction should be defined during rule prepare. Y or N Y N D Y

DODB Specify whether AppBuilder/IMS databases should be processed. Y or N Y N D Y

DOUTBLSpecify whether the AppBuilder transaction UTBL0000 should be executed.

Y or N Y Y D Y

LOGAPPL1LOGAPPL2LOGAPPL3

Specify VTAM APPLIDs used for AppBuilder LU2 processing. These IDs must be defined to both IMS and VTAM.Invalid data: the processing of LU2 functions will fail during update.

Valid member names

A06HPS1A06HPS2A06HPS3

Y D Y

Table A-74 IMS section of IMS configuration file (Continued)





APPENDIX

B CICS TABLE DEFINITIONS

This appendix contains the updated CICS table definitions for AppBuilder Host Development Workbench.

Table Definitions

DFHDCT* ** HPS/CICS PROGRAMS USE THIS DESTINATION TO LOG ERROR MESSAGES.* WHEN AN ERROR MESSAGE IS WRITTEN TO THIS TRANSIENT DATA QUEUE* THE HPEL TRANSACTION IS INITIATED. THE HPEL TRANSACTION WILL* INVOKE THE HPSERRLG PROGRAM WHICH WILL COPY THE ERROR MESSAGE* FROM THE TRANSIENT DATA QUEUE TO THE HPS006D1 RRDS VSAM FILE.** THE HS04 TRANSACTION CAN BE USED TO BROWSE THE ERROR MESSAGES* CONTAINED ON THE HPS006D1 ERRLOG FILE.*HPEL DFHDCT TYPE=INTRA,DESID=HPEL,REUSE=YES,DESTRCV=NO, X DESTFAC=FILE,TRIGLEV=1,TRANSID=HPEL** HPS/CICS TERMINAL PRINT DCT ENTRY** HPS/CICS APPLICATIONS SPECIFY THIS DESTINATION IN THE APPLICATION* RULE AS THE TARGET OF THE REPORT OUTPUT. EACH TRANSIENT DATA QUEUE* IS ASSOCIATED WITH AN SNA SCS PRINTER, WHERE THE NAME OF THE* CICS TERMINAL NAME OF THE PRINTER IS THE SAME NAME AS THE TRANSIENT* DATA QUEUE. THE HPRT TRANSACTION THAT IS TRIGGER BY DATA IN THE* TRANSIENT DATA QUEUE WILL READ RECORDS FROM THE QUEUE AND FORMAT* THE DATA TO BE SENT TO THE SNA SCS PRINTER.** IN THE FOLLOWING EXAMPLE, THE TRANSIENT DATA QUEUE NAME AND THE* SNA SCS PRINTER TERMINAL NAME IS "S57P". A TRANSIENT DATA QUEUE* AND SNA SCS PRINTER MUST BE DEFINED TO CICS FOR EVERY ELIGIBLE

B-1

Table Definitions

* PRINTER THAT WILL RECEIVE THE HPS GENERATED REPORTS.** A SAMPLE CICS TERMINAL DEFINITION FOR THE S57P SNA SCS PRINTER* IS INCLUDED IN THIS SAMPLE DATASET AND IN THE INSTALLATION* DOCUMENTATION.*S57P DFHDCT TYPE=INTRA,DETID=S57P,REUSE=YES,DESTRCV=LG X DESTFAC=TERMINAL,TRIGLEV=1,TRANSID=HPRT

DFHFCT************************************************************* HPS 5.3.1 FILES (FCT) FOR MAINFRAME CICS ************************************************************* DEFINE FILE(HPSDNAER) GROUP(DNA531P) DSNAME(&VSMQUAL..HPSDNAER.CAT) TABLE(NO ) STRINGS(020) BROWSE(YES) READ(YES) RECOVERY(BACKOUTONLY) DEFINE FILE(HPSDNAIN) GROUP(DNA531P) DSNAME(&VSUVQUAL..HPSDNAIN.INI) TABLE(NO ) STRINGS(020) BROWSE(YES) READ(YES) ADD(YES) DELETE(YES) UPDATE(YES) RECOVERY(BACKOUTONLY) DEFINE FILE(HPSDNART) GROUP(DNA531P) DSNAME(&VSUVQUAL..HPSDNART.RTABLE) TABLE(NO ) STRINGS(020) BROWSE(YES) READ(YES) ADD(YES) DELETE(YES) UPDATE(YES) RECOVERY(BACKOUTONLY)

DEFINE FILE(DNAFXFER) GROUP(DNA531P) DSNAME(&VSUVQUAL..DNAFXFER) TABLE(NO ) STRINGS(020) BROWSE(YES) READ(YES) ADD(YES) DELETE(YES) UPDATE(YES) RECOVERY(BACKOUTONLY)

DEFINE FILE(HPSDNASC) GROUP(DNA531P) DSNAME(&VSUVQUAL..HPSDNASC.SCTABLE) TABLE(NO ) STRINGS(020) BROWSE(YES) READ(YES) ADD(YES) DELETE(YES) UPDATE(YES) RECOVERY(BACKOUTONLY)

DEFINE FILE(HPSBC1D1) GROUP(HPS531F)DESCRIPTION(HPS BROADCAST DATA FILE) DSNAME(&VSUVQUAL..HPSBC1D1.BDCTDATA) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO) RECORDFORMAT(V) ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

B-2 CICS Table Definitions

Table Definitions

DEFINE FILE(HPSBC2D1) GROUP(HPS531F)DESCRIPTION(HPS BROADCAST ID FILE) DSNAME(&VSUVQUAL..HPSBC2D1.BDCTTBL) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO) RECORDFORMAT(F) ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

DEFINE FILE(&FCTVIEW) GROUP(HPS531F)DESCRIPTION(HPS VIEW DEFINITION FILE) DSNAME(&VSUVQUAL..&VIEWDEFC.) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(10) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(11) INDEXBUFFERS(10) TABLE(NO) RECORDFORMAT(V) ADD(NO) BROWSE(YES) DELETE(NO) READ(YES) UPDATE(NO) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

DEFINE FILE(HPS002D1) GROUP(HPS531F)DESCRIPTION(HPS TEST DATA FILE) DSNAME(&VSUVQUAL..HPS002D1.TESTDATA) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO) RECORDFORMAT(V) ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

DEFINE FILE(&FCTRULES) GROUP(HPS531F)DESCRIPTION(HPS RULE SOURCE FILE) DSNAME(&VSUVQUAL..&RULESRCC.) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO) RECORDFORMAT(F) ADD(NO) BROWSE(YES) DELETE(NO) READ(YES) UPDATE(NO) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

DEFINE FILE(&FCTRLRLN) GROUP(HPS531F)DESCRIPTION(HPS RULE RELATIONSHIP FILE) DSNAME(&VSUVQUAL..&RLRELATC.) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO) RECORDFORMAT(F) ADD(NO) BROWSE(YES) DELETE(NO) READ(YES) UPDATE(NO) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

B-3

Table Definitions

DEFINE FILE(HPS006D1) GROUP(HPS531F)DESCRIPTION(HPS ERROR LOG FILE) DSNAME(&VSUVQUAL..HPS006D1.ERRLOG) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(4) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(5) INDEXBUFFERS(4) TABLE(NO) RECORDFORMAT(F) ADD(YES) BROWSE(YES) DELETE(YES) READ(YES) UPDATE(YES) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

DEFINE FILE(&FCTVIDTX) GROUP(HPS531F)DESCRIPTION(HPS VIDTEXT FILE) DSNAME(&VSUVQUAL..&VIDTEXTC.) LSRPOOLID(4) DSNSHARING(ALLREQS) STRINGS(10) STATUS(ENABLED) OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(11) INDEXBUFFERS(10) TABLE(NO) RECORDFORMAT(V) ADD(NO) BROWSE(YES) DELETE(NO) READ(YES) UPDATE(NO) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)

DFHPLT** REQUIRED CICS PROGRAM LIST POST INITIALIZATION TABLE* ENTRY FOR HPS/CICS.** FOR CICS 3.X, THIS ENTRY SHOULD BE DEFINED IN THE* THIRD STAGE OF INITIALIZATION.* DFHPLT TYPE=ENTRY,PROGRAM=HPSSTART INITIALIZE XZCAT EXIT DFHPLT TYPE=ENTRY,PROGRAM=HPESI19 INITIALIZE HPS KERNAL DFHPLT TYPE=ENTRY,PROGRAM=HPSINIRD INITIALIZE DNA KERNAL

DFHTCT TITLE 'HPS/CICS TERMINAL CONTROL TABLE ENTRIES'** SAMPLE CICS TERMINAL CONTROL TABLE ENTRY FOR HPS/CICS*TCTHP DFHTCT TYPE=INITIAL,SUFFIX=HP, X ACCMETH=(NONVTAM,VTAM) DFHTCT TYPE=GROUP,GROUP=HSAMPTCT** REQUIRED TCT ENTRIES FOR THE HPSLU2B PROGRAM* DFHTCT TYPE=TERMINAL,TRMIDNT=HPS1,CHNASSY=YES, X ERRATT=(LASTLINE),NETNAME=&LOGAPPL1,TRMTYPE=LUTYPE2, X BRACKET=YES,GMMSG=NO,PGESIZE=(24,80),DEFSCRN=(24,80), X


Table Definitions

ACCMETH=VTAM,TIOAL=(4048,4048),TRMMODL=2, X FEATURE=UCTRAN, X RELREQ=(NO,YES),BUFFER=1536,RUSIZE=256, X TRMSTAT=TRANSCEIVE DFHTCT TYPE=TERMINAL,TRMIDNT=HPS2,CHNASSY=YES, X ERRATT=(LASTLINE),NETNAME=&LOGAPPL2,TRMTYPE=LUTYPE2, X BRACKET=YES,GMMSG=NO,PGESIZE=(24,80),DEFSCRN=(24,80), X ACCMETH=VTAM,TIOAL=(4048,4048),TRMMODL=2, X FEATURE=UCTRAN, X RELREQ=(NO,YES),BUFFER=1536,RUSIZE=256, X TRMSTAT=TRANSCEIVE DFHTCT TYPE=TERMINAL,TRMIDNT=HPS3,CHNASSY=YES, X ERRATT=(LASTLINE),NETNAME=&LOGAPPL3,TRMTYPE=LUTYPE2, X BRACKET=YES,GMMSG=NO,PGESIZE=(24,80),DEFSCRN=(24,80), X ACCMETH=VTAM,TIOAL=(4048,4048),TRMMODL=2, X FEATURE=UCTRAN, X RELREQ=(NO,YES),BUFFER=1536,RUSIZE=256, X TRMSTAT=TRANSCEIVE** SAMPLE TCT ENTRY PARAMETERS FOR AN LU2 TERMINAL* DFHTCT TYPE=TERMINAL,TRMIDNT=SERC,NETNAME=AppBuilderC, X ERRATT=(LASTLINE),CHNASSY=YES,TRMTYPE=LUTYPE2, X ACCMETH=VTAM,TIOAL=(200,8192),TRMMODL=2, X FEATURE=(AUDALARM,COLOR,EXTDS,HILIGHT,UCTRAN), X RELREQ=(NO,YES),GMMSG=YES,BUFFER=1536,RUSIZE=256, X TRMSTAT=(TRANSCEIVE,NOINTLOG)** SAMPLE TCT ENTRY PARAMETERS FOR AN LU6.2 TERMINAL** NOTE: PLEASE REFER TO YOUR VTAM PROGRAMMER FOR ACTUAL NETNAMES* AND MODENAME* DFHTCT TYPE=SYSTEM, X00410000 TRMTYPE=LUTYPE62, X00420000 ACCMETH=VTAM, X00430000 FEATURE=SINGLE, X00430000 MODENAM=AppBuilderLU62, X00430000 SYSIDNT=AppBuilder, X00440000 NETNAME=AppBuilderB, X00440000 BUFFER=256, X00440000 RUSIZE=256, X00440000 USERSEC=LOCAL, X00440000 OPERSEC=1, X00440000 TRMSTAT=TRANSCEIVE 00450000** SAMPLE TCT ENTRY PARAMETERS FOR AN LU1 SNA SCS PRINTER* DFHTCT TYPE=TERMINAL,TRMIDNT=SERF,NETNAME=AppBuilderF, X TRMTYPE=SCSPRT,BUFFER=256, X ACCMETH=VTAM,TIOAL=(1,4000), X TRMSTAT=(TRANSCEIVE)*ENDOFTCT DFHTCT TYPE=FINAL

B-5

Table Definitions

* END

DNA531PDEFINE PROGRAM(DNACEVNT) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL GLOBAL EVENTING MODULE) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(DNAGVERS) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL GET VERSION SYSTEM SERVICE) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(DNAPOSTE) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL GLOBAL EVENTING STUB MODULE) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(DNASASRV) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL SUBCELL TABLE UPDATE SYSTEM SERVICE) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSDNA00) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL SERVER MODULE) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSINIRD) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL INITIALIZATION MODULE) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSSTIRD) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL INITIALIZATION DATA MODULE) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE TRANSACTION(DEVT) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL GLOBAL EVENT SUPPORT) PROGRAM(DNACEVNT) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) XTRANID(8485A5A3) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(NE2I) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL INITIALIZATION) PROGRAM(HPSINIRD) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) XTRANID(9585F289) DTIMOUT(NO) INDOUBT(BACKOUT)


Table Definitions

RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(NE20) GROUP(DNA531P)DESCRIPTION(NETESSENTIAL SERVER) PROGRAM(HPSDNA00) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) XTRANID(9585F2F0) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)

DSNCRCT** CICS / DB2 RESOURCE CONTROL TABLE ENTRIES FOR HPS/CICS** &REGCHAR = CICS DB2 APPLICATION PLAN PREFIX* FROM CLIENT WORKSHEETS*** THE FOLLOWING SAMPLE TYPE=ENTRY DEFINITIONS ARE FOR AN INITIAL* SET OF 36 TRANSACTIONS AND PLANS USED BY HPS/CICS APPLICATIONS.* THE ACTUAL PLAN NAMES ARE DETERMINED BY THE VALUES OF PLNDFLT,* PLNVRSN, PLNTYPE AND PLNPREF IN THE INI MEMBER FOR THIS REGION* IN &REPQUAL..INI . THE ACTUAL TRANSACTION NAMES ARE DETERMINED* BY THE TRANSACTION RANGE DEFINED FOR THIS REGION IN THE TABLE* CM_TRAN. THE EXAMPLES HERE REFLECT THE DEFAULT VALUES PROVIDED* WITH RELEASE SVC2031. YOU MAY CHOOSE TO DEFINE ENTRIES FOR EACH* TRANSACTION, OR USE THE POOL EXIT LOGIC PROVIDED IN THE MEMBER* &INSTQUAL..SVC2031.SAMPLE(HPSPLAN). YOU MAY ALSO COMBINE THE TWO* METHODS.** FOR A DEVELOPMENT ENVIRONMENT WHERE DEDICATED ENTRIES ARE NOT* REQUIRED FOR PERFORMANCE REASONS THE TYPE=POOL AND THE SUPPLIED* PLAN EXIT PROGRAM SHOULD BE USED TO MINIMIZE THE MAINTENANCE* EFFORT.** FOR A PRODUCTION ENVIRONMENT, DEDICATED ENTRIES SHOULD BE USED* WHEN CERTAIN PERFORMANCE CRITERIA MUST BE MET BY THE APPLICATION.* DSNCRCT TYPE=POOL, POOL THREAD DEFINITION X THRDM=20, MAXIMUM NUMBER OF THREADS X THRDA=20, INITIAL NUMBER OF THREADS X AUTH=(TXID), AUTHORIZATIONS X PLNEXIT=YES, USE PLAN EXIT FOR POOL THREADS X PLNPGME=HPSPLAN PLAN EXIT NAME FOR POOL THREADS* DSNCRCT TYPE=ENTRY,TXID=AAAA,PLAN=AAAAPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAB,PLAN=AAABPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAC,PLAN=AAACPLNC, X THRDM=3,THRDA=0,TWAIT=POOL

B-7

Table Definitions

DSNCRCT TYPE=ENTRY,TXID=AAAD,PLAN=AAADPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAE,PLAN=AAAEPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAF,PLAN=AAAFPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAG,PLAN=AAAGPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAH,PLAN=AAAHPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAI,PLAN=AAAIPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAJ,PLAN=AAAJPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAK,PLAN=AAAKPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAL,PLAN=AAALPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAM,PLAN=AAAMPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAN,PLAN=AAANPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAO,PLAN=AAAOPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAP,PLAN=AAAPPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAQ,PLAN=AAAQPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAR,PLAN=AAARPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAS,PLAN=AAASPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAT,PLAN=AAATPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAU,PLAN=AAAUPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAV,PLAN=AAAVPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAW,PLAN=AAAWPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAX,PLAN=AAAXPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAY,PLAN=AAAYPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAAZ,PLAN=AAAZPLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA0,PLAN=AAA0PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA1,PLAN=AAA1PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA2,PLAN=AAA2PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA3,PLAN=AAA3PLNC, X THRDM=3,THRDA=0,TWAIT=POOL


Table Definitions

DSNCRCT TYPE=ENTRY,TXID=AAA4,PLAN=AAA4PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA5,PLAN=AAA5PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA6,PLAN=AAA6PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA7,PLAN=AAA7PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA8,PLAN=AAA8PLNC, X THRDM=3,THRDA=0,TWAIT=POOL DSNCRCT TYPE=ENTRY,TXID=AAA9,PLAN=AAA9PLNC, X THRDM=3,THRDA=0,TWAIT=POOL

HMPBTBL//* SKELETON NAME ====>> HMPBTBL <<==== SKELETON NAME 00081000//************************************************************//* *//* THIS JOBSTREAM MUST BE EXECUTED BEFORE THE STARTUP OF THE *//* HPS/CICS SYSTEM. THE PURPOSE OF THIS JOBSTREAM IS TO: *//* *//* 1) BUILD THE HPS/CICS RULE - TRANSID INCORE TABLE1 *//* *//*********************************************************************//*//* ACCESS THE HPS DATA DICTIONARY TO DEFINE THE RULE - TRANSID//* RELATIONSHIPS//*//HMPBTBL EXEC PGM=IKJEFT01,DYNAMNBR=20 00030000//STEPLIB DD DSN=&DB2LOAD.,DISP=SHR 00040000// DD DSN=&MODQUAL..LOADLIB,DISP=SHR 00040000// DD DSN=&BASEQUAL..LOADLIB,DISP=SHR 00040000// DD DSN=&PLILINK.,DISP=SHR 00040000// DD DSN=&PLILINK2.,DISP=SHR 00040000// DD DSN=&C370LNK1.,DISP=SHR 00040000// DD DSN=&C370LNK2.,DISP=SHR 00040000//SRCEFLE DD DSN=&&&&TBL1SRC,DISP=(NEW,PASS), 00060001// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120), 00061001// SPACE=(CYL,(1,1)), 00062001)SEL &VVOLREQ = Y// VOL=SER=&VVOL,)ENDSEL// UNIT=&VUNIT 00062001//SYSTSPRT DD SYSOUT=* 00070000//SYSPRINT DD SYSOUT=* 00080000//SYSUDUMP DD SYSOUT=* 00090000//SYSIN DD * 00100000//SYSTSIN DD * 00110000 DSN SYSTEM(&DB2SUBID.) 00120000 RUN PROGRAM(HMPBTBL) PARMS('/&V.CICS') PLAN(&PPREFIX.HPS53) 00130001 END

B-9

Table Definitions

/*//HMFMSG DD SYSOUT=*//HMFVMSG DD DSN=&VSMQUAL..MESSAGES,DISP=SHR/*//*//* ASSEMBLE AND LINK HPSTBLE1//*//ASM EXEC PGM=&HASMPGM.,PARM='DECK,NOOBJECT', 00029200// REGION=512K 00029300//SYSLIB DD DSN=&MACLIB.,DISP=SHR,DCB=BLKSIZE=19069 00029400)SEL &MODGEN ™= &Z// DD DSN=&MODGEN.,DISP=SHR 00029600)ENDSEL// DD DSN=&HASMMODG.,DISP=SHR 00029600// DD DSN=&CICSLMAC.,DISP=SHR 00029500//SYSIN DD DSN=&&&&TBL1SRC,DISP=(OLD,DELETE) 00029800//SYSUT1 DD SPACE=(CYL,(2,1)), 00029900)SEL &VVOLREQ = Y// VOL=SER=&VVOL,)ENDSEL// UNIT=&VUNIT//SYSUT2 DD SPACE=(CYL,(2,1)), 00029900)SEL &VVOLREQ = Y// VOL=SER=&VVOL,)ENDSEL// UNIT=&VUNIT//SYSUT3 DD SPACE=(CYL,(2,1)), 00029900)SEL &VVOLREQ = Y// VOL=SER=&VVOL,)ENDSEL// UNIT=&VUNIT//SYSPUNCH DD DSN=&&&&LOADSET, 00030000// DISP=(,PASS), 00030100// SPACE=(400,(100,100,1)), 00030200// DCB=(RECFM=FB,LRECL=80,BLKSIZE=400), 00030300)SEL &VVOLREQ = Y// VOL=SER=&VVOL,)ENDSEL// UNIT=&VUNIT//SYSPRINT DD SYSOUT=* 00030400//LKED EXEC PGM=IEWL,PARM=(XREF,MAP,LIST,'AMODE=24','RMODE=24') 00030500//SYSLIB DD DSN=&CICSRUNT.,DISP=SHR 00030600//SYSLMOD DD DSN=&USRVQUAL..LOADCI(HPSTBLE1),DISP=SHR 00030800//SYSPRINT DD SYSOUT=* 00030900//SYSUT1 DD DCB=BLKSIZE=1024, 00031000// SPACE=(1024,(200,20)), 00031100)SEL &VVOLREQ = Y// VOL=SER=&VVOL,)ENDSEL// UNIT=&VUNIT//SYSLIN DD DSN=&&&&LOADSET,DISP=(OLD,DELETE) 00031200


Table Definitions

HPESDUGDEFINE PROGRAM(KKACGPI) GROUP(HPESDUG) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(KKACGPS) GROUP(HPESDUG) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(KKACGPT) GROUP(HPESDUG) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(KKACGPU) GROUP(HPESDUG) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE TRANSACTION(KGPI) GROUP(HPESDUG) PROGRAM(KKACGPI) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(KGPS) GROUP(HPESDUG) PROGRAM(KKACGPS) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(KGPT) GROUP(HPESDUG) PROGRAM(KKACGPT) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(KGPU) GROUP(HPESDUG) PROGRAM(KKACGPU) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)

HPESDUKDEFINE PROGRAM(KKACGPG) GROUP(HPESDUK) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(KKACGPL) GROUP(HPESDUK) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(KKACGPN) GROUP(HPESDUK) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)

B-11

Table Definitions

EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(KKACGPV) GROUP(HPESDUK) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE TRANSACTION(KGPG) GROUP(HPESDUK) PROGRAM(KKACGPG) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(KGPL) GROUP(HPESDUK) PROGRAM(KKACGPL) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(KGPN) GROUP(HPESDUK) PROGRAM(KKACGPN) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(KGPV) GROUP(HPESDUK) PROGRAM(KKACGPV) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)

AB2031************************************************************* CICS 3.3 STORAGE PROTECTION ** ** IF YOUR SITE HAS STORAGE PROTECTION ACTIVATED ** ** PLEASE CHANGE PCT ENTRIES FOR ** 'HPSXZCAT' AND 'HPSENAEP' ** TO ** EXECKEY(CICS) ** ** HPS DEFINITIONS DO NOT INCLUDE STORAGE PROTECTION ** **************************************************************DEFINE MAPSET(HPSFM0A) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM0D) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM2A) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM2D) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM3A) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM3D) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM5A) GROUP(AB2031)


Table Definitions

RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM5D) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM6A) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM6D) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM9A) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM9B) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM9D) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSFM9F) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE MAPSET(HPSSM4) GROUP(AB2031) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)DEFINE PROFILE(HPECICST) GROUP(AB2031) SCRNSIZE(ALTERNATE) UCTRAN(NO) PRINTERCOMP(NO) JOURNAL(NO) MSGJRNL(NO) MSGINTEG(NO) ONEWTE(NO) PROTECT(NO) CHAINCONTROL(NO) DVSUPRT(ALL) INBFMH(NO) RAQ(NO) LOGREC(NO) NEPCLASS(0) RTIMOUT(NO)DEFINE PROFILE(HPSPROF) GROUP(AB2031) SCRNSIZE(DEFAULT) UCTRAN(NO) PRINTERCOMP(NO) JOURNAL(NO) MSGJRNL(NO) MSGINTEG(NO) ONEWTE(NO) PROTECT(NO) CHAINCONTROL(NO) DVSUPRT(ALL) INBFMH(NO) RAQ(NO) LOGREC(NO) NEPCLASS(0) RTIMOUT(1000)DEFINE PROGRAM(CGETENV) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(DB2) GROUP(AB2031)DESCRIPTION(HPS DB2 SYSTEM COMPONENT USED FOR RULEVIEW BREAKPOINTS) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPCLOSEC) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPDCLOS) GROUP(AB2031) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPDDELE) GROUP(AB2031) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPDGENN) GROUP(AB2031) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPDOPEN) GROUP(AB2031) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)

B-13

Table Definitions

STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPDREAD) GROUP(AB2031) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPDWRIT) GROUP(AB2031) LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPECAPI) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPECO10) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPECV10) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPECV47) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPECV86) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEGAPA) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEHI10) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEHS10) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEHS11) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEHS17) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEHS75) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)


Table Definitions

DEFINE PROGRAM(HPELM10) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPERV41) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPESI10) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPESI19) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPETM10) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEYC10) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEYP11) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEYP84) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEYP86) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEYS06) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPEYS16) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPFAMSG) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPFINDC) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPFREEC) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)

B-15

Table Definitions

USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPGETC) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPGTAID) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPOPENC) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSAMSG) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSASND) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSCGAP) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSCMPT1) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSCONVI) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSCONVO) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSENAEP) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(CICS) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSEQTBL) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSERRLG) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT00) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)


Table Definitions

DEFINE PROGRAM(HPSFLT01) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT02) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT03) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT04) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT05) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT06) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT07) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT08) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT09) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSFLT10) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSINIT) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSLMSG) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSLMSW) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSMODE) GROUP(AB2031)DESCRIPTION(HPS SYSTEM COMPONENT THAT RETURNS EXECUTION ENVIRONMENT)

B-17

Table Definitions

LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSNEWC) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI00) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI10) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI2I) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI2O) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI20) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI30) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI40) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPCI50) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPEP) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(YES) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(CICS) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPEP3) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(YES) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(CICS) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSPRNT) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSSEC4) GROUP(AB2031) LANGUAGE(PLI) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)


Table Definitions

EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSSTART) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSTBLE1) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSTBLE2) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSTBLE3) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSTBLE4) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSTBLE5) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSTRSM) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSUTBL) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSVINIT) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSXSEC) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSXZCAT) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(CICS) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPSXZCIN) GROUP(AB2031) LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPUBDTB) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPUCV10) GROUP(AB2031)

B-19

Table Definitions

LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE PROGRAM(HPWRITEC) GROUP(AB2031) LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER) EXECUTIONSET(FULLAPI)DEFINE TRANSACTION(ENAE) GROUP(AB2031) PROGRAM(HPSENAEP) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HPC7) GROUP(AB2031) PROGRAM(HPECV47) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HPEL) GROUP(AB2031) PROGRAM(HPSERRLG) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HPI0) GROUP(AB2031) PROGRAM(HPESI10) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HPRT) GROUP(AB2031) PROGRAM(HPSPRNT) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HPR0) GROUP(AB2031) PROGRAM(HPERV41) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HPT0) GROUP(AB2031) PROGRAM(HPETM10) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HSND) GROUP(AB2031) PROGRAM(HPSASND) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HS04) GROUP(AB2031) PROGRAM(HPSSEC4) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HS06) GROUP(AB2031) PROGRAM(HPSNEWC) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)


Table Definitions

TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(HS08) GROUP(AB2031) PROGRAM(HPSLMSW) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(PCIO) GROUP(AB2031) PROGRAM(HPSPCI00) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(STRT) GROUP(AB2031) PROGRAM(HPSSTART) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(TRCL) GROUP(AB2031) PROGRAM(HPSFLT00) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(TRLE) GROUP(AB2031) PROGRAM(HPSCMPT1) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED) TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(TRLS) GROUP(AB2031) PROGRAM(HPSFLT10) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)DEFINE TRANSACTION(UTBL) GROUP(AB2031) PROGRAM(HPSUTBL) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1) TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)

HPSPLAN*ASM XOPTS(NOPROLOG,NOEPILOG)*-------------------------------------------------------*The following MUST be done to use the DB2 RCT Plan Exit:*-------------------------------------------------------*--*(1) An RCT entry must be made as follows:*--* DSNCRCT TYPE=POOL, Pool thread definition* THRDM=20, Maximum number of threads* THRDA=20, Initial number of threads* PLNEXIT=YES, Use plan exit for pool threads* PLNPGME=HPSPLAN Plan exit name for pool threads

B-21

Table Definitions

*---*and*---* (2) A PPT entry must be made as follows:*--* HPSPLAN DFHPPT TYPE=ENTRY,PROGRAM=HPSPLAN,PGMLANG=ASSEMBLER** (3) The following code must be assembled, link-edited and placed* into your CICS load libraries.* NOTE: The 1st line '*ASM XOPTS(NOPROLOG,NOEPILOG)' is not a* ---- comment but an assembler directive - DO NOT ERASE.* NOTE: The SP option needs to be specifed on the CICS translate* ---- step.* NOTE: The DB2 macro library needs to be specifed in the STEPLIB* ---- of the compile step.** .$.0 031793 HPS DB2 Plan Exit for CICS HPSPLAN0.ASM 0 NS********************************************************************** ** Classification = BluePhoenix Solutions, Inc. ** (c) Copyright 2002 ** ** ** $$NAME NAME=HPSPLAN ** ** $$VERSION ID=5.2.0 ** ** $$CALL TYPE=PROGRM NAME=&&&& ID=3.1.0 ** ** Programmer = Field Support ** ** Date = Oct. 5, 2002 ** ** Brief Module = HPS DB2 Plan Exit FOR CICS ** Description ** ** Detailed Description = ** This is the DB2 RCT plan exit for the HPS/CICS Pool threads. ** ** It checks the name of the program that is tied to the current ** transaction and alters the plan name to be executed. ** ** Rules: ** If the transaction is defined to either program HPSPCI00 or ** HPETM10 then the transaction ID is concatenated with the ** characters 'PLNC'. Thus the DAAW transaction would use the ** DAAWPLNC plan. Otherwise exit back to CICS. ** ** Inputs = ** ** Outputs = ** ** External Routines = ** ** ASM Copy Statements = *


Table Definitions

* ** EXEC SQL INCLUDE's = None ** ** Modification History = ** ** CHANGE ACTIVITY: ** SEQ RVML PI YYMMDD --- Description ------------------------------ ** ********************************************************************** DSNCPRMAPROGRAM DS CL8 EJECTHPSPLAN DFHEIENT CODEREG=12, R12 is base register X DATAREG=13, R13 for dynamic storage X EIBREG=11 and R11 for the EIB B STARTSTART EQU * L R2,DFHEICAP Get COMMAREA address USING CPRMPARM,R2 Map the commarea MVC CPRMPLAN,=CL8' ' Clear out existing plan name MVC PROGRAM,=CL8' ' Initialize variable EXEC CICS INQUIRE TRANSACTION(EIBTRNID) X PROGRAM(PROGRAM) X NOHANDLE SPACE* The following compare statements check the programs defined to the* CICS transaction. CLC PROGRAM,=CL8'HPSPCI00' Is it an HPS transaction ? BE $LMOVE CLC PROGRAM,=CL8'HPETM10 ' Is it a PCV 3270 transaction ? BNE $LRETURN No, back to CICS$LMOVE MVC CPRMPLAN(4),EIBTRNID Else move TRAN ID ... MVC CPRMPLAN+4(4),=CL4'PLNC' ... plus 'PLNC'$LRETURN DS 0H Back to CICS EXEC CICS RETURN LTORG DFHEISTG DFHEIENDR0 EQU 0R1 EQU 1R2 EQU 2R3 EQU 3R4 EQU 4R5 EQU 5R6 EQU 6R7 EQU 7R8 EQU 8R9 EQU 9R10 EQU 10R11 EQU 11R12 EQU 12R13 EQU 13R14 EQU 14R15 EQU 15 END

B-23

Table Definitions


APPENDIX

C VTAM DEFINITIONS

This appendix contains the sample VTAM definitions that apply to AppBuilderon CICS and IMS.

MO6HPS** VTAM APPLICATION DEFINITIONS REQUIRED BY THE HPSLU2B PROGRAM* WHICH EMULATES A LU2 DEVICE** YOU MAY SUBSTITUTE DIFFERENT ACBNAMES FOR THE ONES GIVEN BELOW.*M05HPS VBUILD TYPE=APPLA06HPS1 APPL ACBNAME=A06HPS1, APPLID FOR ACB X AUTH=(ACQ,PASS,VPACE), HPS CAN ACQUIRE, PASS, & VPACE X MODETAB=MODESNA, DEFAULT MODE TABLE X DLOGMOD=HPSLU2, HPS LU2 MODE ENTRY X EAS=1 ESTIMATED SESSIONS = 1*A06HPS2 APPL ACBNAME=A06HPS2, APPLID FOR ACB X AUTH=(ACQ,PASS,VPACE), HPS CAN ACQUIRE, PASS, & VPACE X MODETAB=MODESNA, DEFAULT MODE TABLE X DLOGMOD=HPSLU2, HPS LU2 MODE ENTRY X EAS=1 ESTIMATED SESSIONS = 1*A06HPS3 APPL ACBNAME=A06HPS3, APPLID FOR ACB X AUTH=(ACQ,PASS,VPACE), HPS CAN ACQUIRE, PASS, & VPACE X MODETAB=MODESNA, DEFAULT MODE TABLE X DLOGMOD=HPSLU2, HPS LU2 MODE ENTRY X EAS=1 ESTIMATED SESSIONS = 1*

C-1

MODELU62

MODELU62** SAMPLE VTAM LOGMODE TABLE DEFINITIONS FOR LU62 COMMUNICATIONS* USED BY OS/2 COMMUNICATIONS MANAGER AND CICS*MODELU62 MODETABAppBuilderLU62 MODEENT LOGMODE=AppBuilderLU62, X TYPE=0, X FMPROF=X'13', X TSPROF=X'07', X PRIPROT=X'B0', X SECPROT=X'B0', X COMPROT=X'50B1', X SSNDPAC=X'00', X SRCVPAC=X'03', X RUSIZES=X'8585', X PSNDPAC=X'03', X PSERVIC=X'060200000000000000002C00'*A32792B MODEENT LOGMODE=A32792B, LOCAL SNA(3274-X1A) 3279-2B X FMPROF=X'03', X TSPROF=X'03', X PRIPROT=X'B1', X SECPROT=X'90', X COMPROT=X'3080', X RUSIZES=X'87C7', X LANG=X'80', X PSERVIC=X'02C000000000185000007E00'* MODEEND END

MODESCS*************************************************************THIS LOGMODE ENTRY DEFINES A LU1 SCS PRINTER WITH THE QUERYFACILITY ** WHICH IS REQUIRED FOR THE IBM 5577 PRINTER. ************************************************************MODESCS MODETABSCSPRTQ MODEENT LOGMODE=SCSPRTQ, X TYPE=1, X FMPROF=X'03', X TSPROF=X'03', X PRIPROT=X'B1', X SECPROT=X'90', X COMPROT=X'7080', X RUSIZES=X'85C7', X PSERVIC=X'01000001E100000001000000' MODEEND END

C-2 VTAM Definitions

MODESNA

MODESNA** VTAM LOGMODE TABLE DEFINITIONS REQUIRED BY THE HPSLU2B PROGRAM* WHICH EMULATES A LU2 DEVICE*MODESNA MODETABHPSLU2 MODEENT LOGMODE=HPSLU2, HPS/CICS RUNTIME ENVIRONMENT X FMPROF=X'03', X TSPROF=X'03', X PRIPROT=X'B1', X SECPROT=X'B0', X COMPROT=X'3080', X RUSIZES=X'E8E8', X PSERVIC=X'0200000000002B502B507F00' MODEEND END

AppBuilderMN* 00010000* SAMPLE VTAM DEFINITION FOR AN HPS OS/2 WORKSTATION THAT COMMUNICATES 00020000* TO THE HOST ACROSS A TOKEN RING VIA DLC. THE SECOND LOGICAL UNIT 00030000* IS DEFINED TO AS AN APPC TERMINAL AND THE SIXTH LU IS DEFINED AS AN 00040000* SNA SCS PRINTER. 00050000* 00060000AppBuilderMN VBUILD TYPE=SWNET, SWITCHED MAJOR NODE X00070000 MAXGRP=2, NUMBER OF UNIQUE PATH GROUPS X00080000 MAXNO=2 NUMBER OF UNIQUE DIALNO NUMBERS 00090000* 00100000AppBuilderPU PU ADDR=01, ANY VALUE (NOT USED, BUT REQ'D) X00110000 IDBLK=05D, FOR VTAM XID (DO NOT CHANGE) X00120000 IDNUM=0010A, FOR VTAM XID, COULD BE SERIAL # X00130000 MAXPATH=2, NUMBER OF PATHS TO THE PU X00140000 MAXOUT=7, MAX PIUS TO PU BEFORE RESP REQ X00150000 MODETAB=MODELU62, MODE TABLE X00160000 DLOGMOD=A32792B, MODE TABLE ENTRY X00170000 PACING=7, # NORM RUS BEFORE PACING RESP X00180000 PASSLIM=7, MAX CONGTIGOUS PIUS AT 1 TIME X00190000 SSCPFM=USSSCS, CHARACTER CODED RUS X00200000 USSTAB=USSSNA, USS TABLE X00210000 VPACING=0 NO VPACING FOR LU 00220000* 00230000AppBuilderA LU LOCADDR=0 00240000AppBuilderB LU LOCADDR=2,DLOGMOD=AppBuilderLU62 00250000AppBuilderC LU LOCADDR=3 00260000AppBuilderD LU LOCADDR=4 00270000AppBuilderE LU LOCADDR=5 00280000AppBuilderF LU LOCADDR=6,DLOGMOD=SCSPRTQ,MODETAB=MODESCS 00290000* 00300000

C-3

AppBuilderMN

C-4 VTAM Definitions

APPENDIX

D HPSCGAP, HPICGAP, HPEUCGP, AND SAMPLE BATCH JCL

Planning and Installaing AppBuilder for the Mainframe

This appendix contains the detailed descriptions for HPSCGAP, HPICGAP, and HPEUCGP—load module tables that contain site-specific information required by AppBuildersoftware.

HPSCGAP and HPSIGAPThe AppBuilder CICS Global Parameters Table (HPSCGAP) is a load module holding site-specific information AppBuilder requires. It is located in &BASEQUAL..LOADBT and &BASEQUAL..LOADCI.

For IMS, the corresponding file is the AppBuilder IMS Global Parameters Table (HPSIGAP). The files are located in &BASEQUAL..LOADIM

For CICS, the source is located in &BASEQUAL..SVC2031.SAMPLE(HPSCGAP) and sample JCL is located in &BASEQUAL..SVC2031.SAMPLE(SKLCGAP). HPSCGAP is a CSECT containing site-specific information and is accessed during AppBuilder processing. Modify the source to reflect parameters at your site, then reassemble the source. You should ensure the currency symbol (HGACSTOK) and default country (HGAXTRYD and HGACTRYC) variables are correct for your site.

For IMS, the source is located in &BASEQUAL..SVI531.SAMPLE(HPICGAP) and sample JCL is located in &BASEQUAL..SVI531.SAMPLE(HPICAPJ).

Note Two links are required if you change HPSCGAP or HPSIGAP.

Planning and Installaing AppBuilder for the Mainframe D-1

HPSCGAP and HPSIGAP

Table D-1 is a description of the significant parameters for HPSCGAP and HPSIGAP. Table D-D-1 provides the supported country/language numbers for HPSCGAP and HPSIGAP variables.

Table D-1 HPSCGAP and HPSIGAP Variables

Variable Description

TCTUAOFFThe requirement for a TCTUA has been removed in AppBuilder. Must be set to the default value (0).

EXECENVType of CICS or IMS execution environment. D for Development and P for Production. The default value is D.

SECURITY Mainframe Security Active (Y or N). The default value is Y.

SAF No longer used. Must be set to the default value (N).

NOTIFY No longer used. Must be set to the default value (N).

STRAT62 Mainframe to Stratus LU6.2 Link Active (Y or N). The default value is (N).

HPS No longer used. Must be set to the default value (N).

CNV3270 3270 Converse Product Active (Y or N). The default value is (Y).

SDS Software Distribution System Active (Y or N). The default value is (Y).

LU62SAF No longer used. Must be set to the default value (N).

WKSSECR

Workstation Security Active (Y or N). This applies only to 3270 Converse Logic. If this is set to Y, the 3270 Converse modules validate Workstation Security when AppBuilder Security is active. The default value is (Y).

XSECEXITInvoke user exit from the HPSXSEC external security interface module (Y or N). The default value is (N).

ASYNC Asynchronous communications support to workstations active (Y or N). The default value is (Y).

HGACSTOK

Currency symbol token used to determine the hexadecimal value of the dollar sign "$" in the local code page. This value must be set too display the dollar in the local code page. the default value is $ (x’5B’).

HGAHREPLAppBuilder repository version. This is set to the character that identifies the current AppBuilder repository version this CICS region supports. The default value is (1).

HGAHREPNAppBuilder repository name. A character string that uniquely identifies the current AppBuilder repository version this CICS or IMS region supports. The default value is blank.

HGACTRYD Default country this CICS or IMS region supports. The default value is USA (34). See Table D-2.

HGACTRYCCurrent country this CICS or IMS region supports. The default value is USA (34). These two fields should both be set to the required country number. See Table D-2.

HGANLNGD

Default Language Abbreviation for MLS support. The default value is ENU for the United States. Refer to Table 5-3, “Definition of Default Language Abbreviations,” on page 15 in Chapter , “Installing the Enterprise Repository” for more information.

HPS001D1DDNAME for the view definition file. The default value is HPS001D1 for CICS or HPI001D1 for IMS.

HPS002D1 DDNAME for the test data file. The default value is HPS002D1 for CICS or HPI002D1 for IMS.

HPS003D1 DDNAME for the rule source file. The default value is HPS003D1 for CICS or HPI003D1 for IMS.

HPS004D1DDNAME for the rule relationship file. The default value is HPS004D1 for CICS or HPI004D1 for IMS

SEC001H1 DDNAME for the menu file. The default value is SEC001H1 for CICS or SEI001H1 for IMS

HPS006D1DDNAME for the ERROR LOG file. The default value is HPS006D1 for CICS or HPI006D1 for IMS

SEC003H1 DDNAME for the security log file. The default value is SEC003H1 for CICS or SEI003H1 for IMS

HPS008D1 No longer used. The default value is HPS008D1.

D-2 HPSCGAP, HPICGAP, HPEUCGP, and Sample Batch JCL

HPSCGAP and HPSIGAP

Table D-D-2 defines the supported country and language numbers supported in the AppBuilder environment.

HPSBC1D1 DDNAME for asynchronous broadcast data. The default value is HPSBC1D1.

HPSBC2D1 DDNAME for asynchronous broadcast ID table. The default value is HPSBC2D1.

HPEL Transient data queue for error logging. The default value is HPEL.

HCSW Transient data queue for security logging. The default value is HCSW.

HPNL No longer used. The default value is HPNL.

Table D-2 Supported AppBuilder environment country/language numbers

Country # Country #

Albania 1 Netherlands 19

Argentina 2 New Zealand 20

Austria 3 Norway 21

Belgium 4 Poland 22

Brazil 5 Portugal 23

Canada—French 6 Romania 24

Canada—English 7 South Africa 25

China 8 South Korea 26

Czechoslovakia 9 Spain 27

Denmark 10 Sweden 28

Finland 11 Switzerland 29

France 12 Taiwan 30

Germany 13 Thailand 31

Greece 14 Turkey 32

Hungary 15 United Kingdom 33

Iceland 16 United States 34

Italy 17 Yugoslavia 35

Japan 18

Table D-1 HPSCGAP and HPSIGAP Variables (Continued)

Variable Description


HPSCGAP Code

HPSCGAP CodeThe following is the source code for HPSCGAP for CICS and Batch.

• The CICS file is located in: &BASEQUAL..SVC2031.SAMPLE(HPSCGAP).

• The Batch file is located in: &BASEQUAL..SVB2031.SAMPLE(HPSCGAP).

* .$.0 081094 HPS/CICS GLOBAL PARAM CSECT HPSCGAP.ASM DC 25********************************************************************** ** Classification = BluePhoenix Solutions, Inc. ** (c) Copyright 2002 ** ** ** $$NAME NAME=HPSCGAP ** ** $$VERSION ID=3.4.0 ** ** $$CALL TYPE=PROGRM NAME=&&&&&&&& ID=3.4.0 ** ** Programmer = N. Shing, M. Dolciger ** ** Date = October 11, 2002 ** ** Brief Module = HPS/CICS incore global parameters ** Description table used to configure the HPS/CICS ** run time environment. ** ** Detailed Description = ** THIS CSECT GENERATES A LOAD MODULE WHICH IS USED ** AS A GLOBAL PARAMETER TABLE FOR ALL HPS/CICS PROGRAMS. ** THIS PARAMETER TABLE WILL ALLOW FOR ONSITE CUSTOMIZATION.** ** Inputs = ** ** Outputs = ** ** External Routines = ** ** ASM Copy Statements = ** ** EXEC SQL INCLUDE's = None ** ** Modification History = ** ** CHANGE ACTIVITY: ** SEQ RVML PI YYMMDD --- Description ------------------------------** 025 5300 DC 940810 Add Default National Language ** 024 3700 DC 931111 Add file read parameters ** 023 3480 DC 930413 Add CICS release level ** 022 3480 NS 930408 Set HPS Error Log DDNAME to HPS006D1 ** 021 3480 NS 930312 Default Version Number to One ** 020 3480 DC 930201 Add address of Codepage translation routine *


HPSCGAP Code

* 019 3480 NS 930201 Restored Correct Broadcast File Names **018 3400 DM 930121 Chg WXTRNs into EXTRNs, Link-Ed fail if missing ** 017 3400 DM 921215 Match to DSECT chgs, Repos name, Nat Lang Supp ** 016 3400 JL 920603 Changed fields for CASIM security support ** 015 3400 NS 920116 Added fields for ASYNC support ** 014 3400 DC 910726 Added new flag to switch the user signon exit ** on or off. ** 013 3400 NS 910717 Added new parameter to switch Workstation ** Security on or off. ** 012 3400 DM 910530 Add HGACONP addr of HPSCONP converse text ** constants CSECT. ** 011 3200 JAK 900912 Add HGALMGP addr of HPSLMGP message tabl CSECT.** 010 3200 DM 900807 Split off SDS constants and Exit Code in a new ** CSECT. ** 009 3200 JAK 900711 Converse constants and exit code in new CSECT. ** 008 3200 JDS 900715 Added HPS API Exit Area. ** 007 3200 MD 900522 Changed defaults as following: ** NOTIFY=N,LU62SAF=N ** 006 3200 MD 900419 Added LU62 SAF Program Name. ** 005 3200 MD 900309 Added Time Interval Value for Post Wait Event- ** Cancel Mechanism. ** 004 3200 DM 900213 Changed SDS Default to 'Y'. ** 003 3200 MD 900213 Changed HPO Defualt to 'Y' and filled some ** fields of the Converse Global Area. ** 002 3200 DM 900131 Filled some of the SDS Area ** 001 3200 MD 900124 Added 256 Bytes Area for SDS ** ********************************************************************** EJECT TITLE ' HPS/CICS GLOBAL PARAMETERS TABLE'HPSCGAP CSECT EXTRN HPSCVGP CONVERSE GLOBAL AREA EXTRN HPSGXIP API GLOBAL EXIT AREA EXTRN HPSSDSP SDS GLOBAL AREA 10 EXTRN HPSLMGP HPS ERROR MESSAGE ROUTE TABLE 11 EXTRN HPSCONP HPS CONVERSE TEXT CONSTANTS 12 EXTRN HPEHL64 HPS CTRY/LANG SUPPORT TABLE 17 EXTRN HPELX10 CODEPAGE TRANSLATION ROUTINE 19 DC CL8'HPSCGAP' DC CL16'&SYSDATE-&SYSTIME' DC CL8' V3R4M8 ' SPACE 2HGADDR EQU *HGCPARMA DC A(HGCPARM) @ OF CONFIGURATION PARAMETER AREAHGTBLA DC A(HGTBL) @ OF HPS INCORE TABLES AREAHGFILEA DC A(HGFILE) @ OF HPS FILES AREAHGTDQA DC A(HGTDQ) @ OF HPS TDQ'S AREAHGTSQA DC A(HGTSQ) @ OF HPS TSQ'S AREAHGCONSTA DC A(HGCONST) @ OF HPS CONSTANTS AREAHGACVGL DC A(HPSCVGP) @ OF CONVERSE GLOBAL AREA 09HGADBUG DC A(HGRDBUG) @ OF DEBUG AREAHGASDSA DC A(HPSSDSP) @ OF SOFTWARE DISTRIBUTION PARM 10HGARESV DC A(HGRESV) @ OF FUTURE USE AREAHGAEXIT DC A(HPSGXIP) @ OF HPS API EXIT AREA 09


HPSCGAP Code

HGALMGP DC A(HPSLMGP) @ HPS ERROR MESSAGE ROUTE TABLE 11HGACONP DC A(HPSCONP) @ HPS CONVERSE TEXT CONSTANTS 12HGALANG DC A(HPEHL64) @ HPS CTRY/LANG SUPPORT TABLE 17HGACPTR DC A(HPELX10) @ HPS CODEPAGE TRANSLATION 19HGADDRF EQU HPSCGAP+256-* LENGTH TO PAD DC (HGADDRF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256) ALIGN TO X'100'HGCPARM EQU *TCTUAOFF DC H'0' TCTUA OFFSETEXECENV DC C'D' EXECUTION ENVIRONMENTDEVELOP EQU C'D' DEVELOPMENT ENVIRONMENTPROD EQU C'P' PRODUCTION ENVIRONMENTSECURITY DC C'N' SECURITY ON (YES/NO)SAF DC C'N' INVOKE HPSSAF (YES/NO)NOTIFY DC C'N' PHASEII NOTIFICATION (YES/NO)STRAT62 DC C'N' STRATUS LU6.2 INTERFACEHPO DC C'N' HIGH PERFORMANCE OPTION(YES/NO)CONV3270 DC C'Y' 3270 CONVERSE SUPPORT (YES/NO)SDS DC C'Y' SOFTWARE DISTRUBUTION(YES/MO)LU62SAF DC C'N' LU62 SAF ACTIVEWKSSECR DC C'Y' WORKSTATION SECURITY (YES/NO)* CURRENTLY APPLIES ONLY TO* 3270 CONVERSE SECURITY LOGICXSECEXIT DC C'N' USER SECURITY SIGNON EXIT (Y/N)ASYNC DC C'Y' ASYNCH SUPPORT (YES/NO)HGACSTOK DC C'$' DOLLAR THE CURRENCY SYMBOL TOKEN 17* USED TO DETERMINE HEX VALUE OF $ IN LOCAL CODE PAGE 17HGAHREPL DC C'1' HPS REPOSITORY LEVEL 21HGAHREPN DC CL8' ' HPS REPOSITORY NAME 17HGACTRYD DC H'34' USA HPS COUNTRY - DEFAULT 17HGACTRYC DC H'34' USA HPS COUNTRY - CURRENT 17HGANLNGD DC CL3'ENU' English - USA National Lng - default 25 DC CL1' ' Unused 25HGCPARMF EQU HGCPARM+256-* LENGTH TO PAD DC (HGCPARMF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGTBL EQU * HPS INCORE TABLES AREATBL1ADDR DS F RULE/TRANSID TABLE 1TBL2ADDR DS F RULE/TRANSID TABLE 2TBL3ADDR DS F USRUSG/WKSNGP/BP TABLETBL4ADDR DS F NOTIFICATION TABLETBL5ADDR DS F USER/WRKSTN TABLETBL6ADDR DS F CONNECTIONS/SESSIONS TABLETBL7ADDR DS F HPS PROGRAMS TABLETBL8ADDR DS F RESERVEDTBL9ADDR DS F RESERVEDTBL10ADR DS F RESERVEDHGTBLF EQU HGTBL+256-* LENGTH TO PAD DC (HGTBLF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGFILE EQU * HPS FILES AREAHPS000D1 DS CL8 RESERVEDHPS001D1 DC CL8'HPS001D1' VIEW DEFINITION FILEHPS002D1 DC CL8'HPS002D1' TEST DATA FILE


HPSCGAP Code

HPS003D1 DC CL8'HPS003D1' RULE SOURCE FILEHPS004D1 DC CL8'HPS004D1' RULE RELATIONSHIP FILESEC001H1 DC CL8'SEC001H1' MENU FILEHPS006D1 DC CL8'HPS006D1' ERROR LOGSEC003H1 DC CL8'SEC003H1' SECURITY LOGHPS008D1 DC CL8'HPS008D1' NOTIFICATION LOGHPSBC1D1 DC CL8'HPSBC1D1' BROADCAST MESSAGE DATAHPSBC2D1 DC CL8'HPSBC2D1' BROADCAST ID TABLEHGFILEF EQU HGFILE+256-* LENGTH TO PAD DC (HGFILEF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGTDQ EQU * HPS TDQS AREAHPEL DC CL4'HPEL' ERROR LOG TD QUEUEHCSW DC CL4'HCSW' SECURITY LOG TD QUEUEHPNL DC CL4'HPNL' NOTIFICATION LOG TD QUEUEHGTDQF EQU HGTDQ+256-* LENGTH TO PAD DC (HGTDQF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGTSQ EQU * HPS TSQS AREA DC XL256'00'HGTSQF EQU HGTSQ+256-* LENGTH TO PAD DC (HGTSQF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGCONST EQU * HPS CONSTANTS AREAAPPCTERM DC X'C0F0' -APPC TERMINALT3270 DC X'91F2' -3270 TERMINALPOSTWAIT DC PL4'5959' -ALMOST ONE HOURLU62SAFN DC CL8'FBCSAFZ' -LU62 SAF PGMNAMEHGACREL DC CL4'0000' -CICS RELEASE LEVEL 23 DS CL4 Unused 24 DS CL16 Reserved for HPEGAPA 24HGAFIWAT DC PL4'5' Wait 5 secs bet reads (0HHMMSSs)24HGAFIRET DC H'1' Retry VSAM read once 24HGCONSTF EQU HGCONST+256-* LENGTH TO PAD DC (HGCONSTF)X'0' PAD WITH BINARY ZEROS* ORG , ORG TO TOP OF AREA USED 11 ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256) 11**-- Please name all reserved areas with HGRxxxx here.*HGRDBUG DC XL256'00' HPS DEBUG AREA*HGRESV DC XL256'00' HPS FUTURE USE*HPSCGAPE EQU * END OF PROGRAM 08 END HPSCGAP


HPEUCGP

HPEUCGPThis sample file defines the area of AppBuilder/CICS that users can customize for their site.

TITLE 'H P E U C G P HPS User Customizable Constants '* .$.0 081094 HPS/CICS User Custom Constants HPEUCGP.ASM DC 02***UCGP HCEEAAG VER=2.0.3.1,TYPE=TABL, Documentation Only !*** MSG=' User Customizable Constants !'**-*-** HPSCPYR ' (c) Copyright 2002, BluePhoenix Solutions, Inc. '** $$NAME NAME=HPEUCGP** $$VERSION ID=3.7.0** $$CALL TYPE=PROGRM NAME=&&&&&&&& ID=3.7.0** Programmer = Jeffrey Katz** Date = August 2002** Brief Description = Constants Area Changed by End User** Detailed Description = This program defines an area in which the* end user may customize constants.** Inputs = None** Outputs = None** External Routines = none** ASM Copy Statements =** EXEC SQL INCLUDE's = None** MODE: AMODE=31,RMODE=ANY** Modification History =* .SEQ RVML PI YYMMDD --- Description +---------+--------+--------+-* 02 5300 DC 940810 Added Default National Language* 01 3700 JAK 930831 First version for Country specific information**-*-**--HPEUCGP CSECT , \UCAP User Customizable Constants area DC CL08'HPEUCGP ' DC CL16'&SYSDATE-&SYSTIME' DC CL08' V3R7M0 '****** USER: DO NOT ALTER ANYTHING BEFORE THIS LINE***HGACSTOK DC CL1'$' Dollar Sign Currency Symbol Token* Defines the binary value of the Currency Symbol in the* Local Code Page. Set to a single national character.*HGAHREPL DC CL1'1' Default HPS Repository Level


SKLCGAP.JCL

DC CL8' ' Do NOT ALTER*HGACTRYD DC H'34' USA Default HPS Country NumberHGACTRYC DC H'34' USA Current HPS Country NumberHGANLNGD DC CL3'ENU' English - USA Default National Language 02 DC CL1' ' Do NOT ALTER 02******* USER: DO NOT ALTER ANYTHING AFTER THIS LINE***PGMEND DC 0D'0' End of program END , \PGMEND

SKLCGAP.JCLThe following is the sample JCL file for CICS, located in &BASEQUAL..SVC2031.SAMPLE(SKLCGAP).

//* PLACE JOBCARD HERE//*------------------------------------------------------------------//* THIS JOBSTREAM ASSEMBLES HPSCGAP INTO THE LEVELC OBJECT LIBRARY//* AND LINKS IT INTO THE &MODQUAL.LOADCI LIBRARY.//*------------------------------------------------------------------//* ASSEMBLE AND LINK HPSCGAP//*------------------------------------------------------------------//ASM EXEC PGM=&HASMPGM.,PARM='DECK,NOOBJECT',// REGION=512K//SYSLIB DD DSN=SYS1.MACLIB,DISP=SHR// DD DSN=&MODGEN,DISP=SHR// DD DSN=&CICSLMAC,DISP=SHR//SYSIN DD DSN=&BASEQUAL..SAMPLE(HPSCGAP),// DISP=SHR//SYSUT1 DD SPACE=(CYL,(2,1)),// UNIT=&TUNIT//SYSUT2 DD SPACE=(CYL,(2,1)),// UNIT=&TUNIT//SYSUT3 DD SPACE=(CYL,(2,1)),// UNIT=&TUNIT//SYSPUNCH DD DSN=&MODQUAL..OBJ(HPSCGAP),DISP=OLD// UNIT=&TUNIT//SYSPRINT DD SYSOUT=*//LKED EXEC PGM=IEWL,PARM=(REUS,XREF,LIST,'AMODE=31','RMODE=ANY')//SYSLIB DD DSN=&CICSRUNT,DISP=SHR//OBJECT DD DSN=&MODQUAL..OBJ,DISP=SHR// DD DSN=&BASEQUAL..OBJ,DISP=SHR//SYSLMOD DD DSN=&MODQUAL..LOADCI,DISP=OLD//SYSPRINT DD SYSOUT=*//SYSUT1 DD DCB=BLKSIZE=1024,// SPACE=(1024,(200,20)),// UNIT=&TUNIT//SYSLIN DD * SETSSI 01039407 .$.0 NEW NLS INFO GLOBAL HPSCGAP.LKC DC 07


Host Batch JCL

INCLUDE OBJECT(HPSCGAP) INCLUDE OBJECT(HPSCVGP) INCLUDE OBJECT(HPSGXIP) INCLUDE OBJECT(HPSSDSP) INCLUDE OBJECT(HPSLMGP) INCLUDE OBJECT(HPSCONP) INCLUDE OBJECT(HPSCNVC) INCLUDE OBJECT(HRNTBL) NLS UPPER, LOWER TRANS TABLES INCLUDE OBJECT(HPEHL64) INCLUDE OBJECT(HPEHL10) ENTRY PTS HPEHL00 AND HPEUE10 INCLUDE OBJECT(HPETODT) INCLUDE OBJECT(HPETOTM) INCLUDE OBJECT(HPEUE11) INCLUDE OBJECT(HPEUE12) INCLUDE OBJECT(HPEUE13) INCLUDE OBJECT(HPEUE14) INCLUDE OBJECT(HPEUE15) INCLUDE OBJECT(HPEUE16) INCLUDE OBJECT(HPEUE17) INCLUDE OBJECT(HPEUE18) 03 INCLUDE OBJECT(HPEUE19) 06 INCLUDE OBJECT(HPEUE20) TIMESTAMP ROUTINE 07 INCLUDE OBJECT(HPEUE50) INCLUDE OBJECT(HPELX10) CODEPAGE TRANSLATION ROUTINE INCLUDE OBJECT(HLXOS2) TRANS TABLE FOR OS2 INCLUDE OBJECT(HLXUNIX) TRANS TABLE FOR UNIX INCLUDE OBJECT(HLXWIN) TRANS TABLE FOR WINDOWS INCLUDE OBJECT(HLX9999) TRAILER TABLE ENTRY ENTRY HPSCGAP NAME HPSCGAP(R)

Host Batch JCLThe following code samples show the JCL for AppBuilder batch DB2 and non-DB2 rules. The chief difference between them is that the DB2 version runs under the DB2 command processor DSN

Batch DB2 JCLThe code sample below shows the JCL for AppBuilder batch DB2 rules.

//***********************************************************//* SAMPLE BATCH DB2 JCL *//***********************************************************// RUNBATCH EXEC PGM=IKJEFT01,DYNAMNBR=50,REGION=4096K//***********************************************************//* THE STEPLIB SHOULD CONTAIN//* 1. THE DB2 RUNTIME LIBRARIES//* 2. THE COBOL RUNTIME LIBRARIES//* 3. THE PLI RUNTIME LIBRARIES


Host Batch JCL

//* 4. THE C/370 RUNTIME LIBRARIES//* 5. HPS USER BATCH LOADLIB//* 6. HPS BASE BATCH LOADLIB//* 7. HPS BASE LOADLIB//***********************************************************//STEPLIB DD DSN=&DB2LOAD.,DISP=SHR// DD DSN=&DB2LINK.,DISP=SHR// DD DSN=&COB2LINK.,DISP=SHR// DD DSN=&PLILINK.,DISP=SHR// DD DSN=&PLILINK2.,DISP=SHR// DD DSN=&C370LNK1.,DISP=SHR// DD DSN=&C370LNK2.,DISP=SHR// DD DSN=&USRVQUAL..LOADBT,DISP=SHR// DD DSN=&REPQUAL..LOADBT,DISP=SHR// DD DSN=&MODQUAL..LOADBT,DISP=SHR// DD DSN=&BASEQUAL..LOADBT,DISP=SHR// DD DSN=&REPQUAL..LOADLIB,DISP=SHR// DD DSN=&MODQUAL..LOADLIB,DISP=SHR// DD DSN=&BASEQUAL..LOADLIB,DISP=SHR//***********************************************************//* INPUT DD REQUIRED//***********************************************************// INPUTDD DUMMY//***********************************************************//* OUTPUT DD REQUIRED - USED FOR MESSAGES//***********************************************************//OUTPUTDD SYSOUT=*//***********************************************************//* USERS VIEWDEF VSAM FILE//***********************************************************//VIEWFILE DD DSN=&VSUVQUAL..BATCH.VIEWDEF,DISP=SHR//***********************************************************//* ALLOCATE APPLICATION INPUT AND OUTPUT FILES HERE//* (E.G., REPORT, INPUT FILES, OUTPUT FILES)//***********************************************************//SYSTSPRT DD SYSOUT=*//SYSABOUT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//CEEDUMP DD SYSOUT=*//PLIDUMP DD SYSOUT=*//***********************************************************//* INPUT FOR RUNNING UNDER DB2://* SYSTEM - THE DB2 SUBSYSTEM YOU ARE RUNNING UNDER//* PROG - ALWAYS EXECUTING HPSBATCH//* PLAN - PLAN NAME FOR RULE//* PARM - SYSTEM ID OF RULE//***********************************************************//SYSTSIN DD * DSN SYSTEM(&DB2SVBID.) RUN PROG(HPSBATCH) + PLAN(B1A1PLNB) + PARM(’AAQANR’)END


Host Batch JCL

Batch JCL (non-DB2)The code sample below shows the JCL for AppBuilder non-DB2 batch rules.

//***********************************************************//* SAMPLE BATCH JCL //***********************************************************//***********************************************************//* PARM IS RULE SYSTEM ID//***********************************************************// RUNBATCH PGM=HPSBATCH,PARM=’AAMNNR’ //***********************************************************//* THE STEPLIB SHOULD CONTAIN//* 1. THE COBOL RUNTIME LIBRARIES//* 2. THE PLI RUNTIME LIBRARIES//* 3. THE C/370 RUNTIME LIBRARIES//* 4. HPS USER BATCH LOADLIB//* 5. HPS BASE BATCH LOADLIB//* 6. HPS BASE LOADLIB//***********************************************************//STEPLIBDD DSN=&COB2LINK.,DISP=SHR// DD DSN=&PLILINK.,DISP=SHR// DD DSN=&PLILINK2.,DISP=SHR// DD DSN=&C370LNK1.,DISP=SHR// DD DSN=&C370LNK2.,DISP=SHR// DD DSN=&USRVQUAL..LOADBT,DISP=SHR// DD DSN=&REPQUAL..LOADBT,DISP=SHR// DD DSN=&MODQUAL..LOADBT,DISP=SHR// DD DSN=&BASEQUAL..LOADBT,DISP=SHR// DD DSN=&REPQUAL..LOADLIB,DISP=SHR// DD DSN=&MODQUAL..LOADLIB,DISP=SHR// DD DSN=&BASEQUAL..LOADLIB,DISP=SHR//***********************************************************//* INPUT DD REQUIRED//***********************************************************// INPUT DD DUMMY//***********************************************************//* OUTPUT DD REQUIRED - USED FOR MESSAGES//***********************************************************//OUTPUT DD SYSOUT=*//***********************************************************//* USERS VIEWDEF VSAM FILE//***********************************************************//VIEWFILE DD DSN=&VSUVQUAL..BATCH.VIEWDEF,DISP=SHR//***********************************************************//* ALLOCATE APPLICATION INPUT AND OUTPUT FILES HERE//* (E.G., REPORT, INPUT FILES, OUTPUT FILES)//***********************************************************//OUTPUTF DD DSN=&&OUTPUT1,DISP=(,CATLG,DELETE),// DCB=(RECFM=FBA,LRECL=133,BLDSIZE=23408)//SYSTSPRT DD SYSOUT=*//SYSABOUT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*


HPICGAP Code

//CEEDUMP DD SYSOUT=*//PLIDUMP DD SYSOUT=*/*

HPICGAP CodeThe following is the source code for HPICGAP for IMS, located in: &BASEQUAL..SVI531.SAMPLE (HPICGAP).

*.$.0 031793 HPS/IMS GLOBAL PARAM CSECT HPICGAP.ASM 1 PC 22

************************************************************** ** Classification = BluePhoenix Solutions, Inc. ** (c) Copyright 2002 ** ** ** $$NAME NAME=HPICGAP ** ** $$VERSION ID=3.4.0 ** ** $$CALL TYPE=PROGRM NAME=&&&&&&&& ID=3.4.0 ** ** Programmer = P. Cobley ** ** Date = October 17, 2002 ** ** Brief Module = HPS/IMS incore global parameters ** Description table used to configure the HPS/IMS ** run time environment. ** ** Detailed Description = ** THIS CSECT GENERATES A LOAD MODULE WHICH IS USED ** AS A GLOBAL PARAMETER TABLE FOR ALL HPS/IMS PROGRAMS. ** THIS PARAMETER TABLE WILL ALLOW FOR ONSITE CUSTOMIZATION. ** ** Inputs = ** ** Outputs = ** ** External Routines = ** ** ASM Copy Statements = ** ** EXEC SQL INCLUDE's = None ** ** Modification History = ** ** CHANGE ACTIVITY: ** SEQ RVML PI YYMMDD --- Description --------------------- ** 022 3600 PC 930317 Program created from HPSCGAP to ** avoid any differences *


HPICGAP Code

*021 3600 PC 930305 Created the IMS File library names ** for the HPS0 references ** 020 3480 DC 930201 Add address of Codepage ** translation routine **019 3480 NS 930201 Restored Correct Broadcast File Names **018 3400 DM 930121 Chg WXTRNs into EXTRNs, Link-Ed fail ** if missing ** 017 3400 DM 921215 Match to DSECT chgs, Repos name, ** Nat Lang Supp ** 016 3400 JL 920603 Changed fields for CASIM security ** support ** 015 3400 NS 920116 Added fields for ASYNC support ** 014 3400 DC 910726 Added new flag to switch the user ** signon exit on or off. **013 3400 NS 910717 Added new parameter to switch ** Workstation Security on or off. ** 012 3400 DM 910530 Add HGACONP addr of HPSCONP ** converse text constants CSECT. ** 011 3200 JAK 900912 Add HGALMGP addr of HPSLMGP ** message table CSECT. ** 010 3200 DM 900807 Split off SDS constants and Exit Code ** in a new CSECT. ** 009 3200 JAK 900711 Converse constants and exit code in ** new CSECT. ** 008 3200 JDS 900715 Added HPS API Exit Area. ** 007 3200 MD 900522 Changed defaults as following: ** NOTIFY=N,LU62SAF=N ** 006 3200 MD 900419 Added LU62 SAF Program Name. ** 005 3200 MD 900309 Added Time Interval Value for ** Post Wait Event- ** Cancel Mechanism. ** 004 3200 DM 900213 Changed SDS Default to 'Y'. ** 003 3200 MD 900213 Changed HPO Defualt to 'Y' and filled ** somefields of the Converse Global Area. ** 002 3200 DM 900131 Filled some of the SDS Area ** 001 3200 MD 900124 Added 256 Bytes Area for SDS ** ************************************************************ EJECT TITLE ' HPS/IMS GLOBAL PARAMETERS TABLE'HPSCGAP CSECT EXTRN HPSCVGP CONVERSE GLOBAL AREA EXTRN HPSGXIP API GLOBAL EXIT AREA EXTRN HPSSDSP SDS GLOBAL AREA 10 EXTRN HPSLMGP HPS ERROR MESSAGE ROUTE TABLE 11 EXTRN HPSCONP HPS CONVERSE TEXT CONSTANTS 12 EXTRN HPEHL64 HPS CTRY/LANG SUPPORT TABLE 17 EXTRN HPELX10 CODEPAGE TRANSLATION ROUTINE 19 DC CL8'HPSCGAP' DC CL16'&SYSDATE-&SYSTIME' DC CL8' V6R0M0 ' SPACE 2HGADDR EQU *HGCPARMA DC A(HGCPARM) @ OF CONFIGURATION PARAMETER AREA


HPICGAP Code

HGTBLA DC A(HGTBL) @ OF HPS INCORE TABLES AREAHGFILEA DC A(HGFILE) @ OF HPS FILES AREAHGTDQA DC A(HGTDQ) @ OF HPS TDQ'S AREAHGTSQA DC A(HGTSQ) @ OF HPS TSQ'S AREAHGCONSTA DC A(HGCONST) @ OF HPS CONSTANTS AREAHGACVGL DC A(HPSCVGP) @ OF CONVERSE GLOBAL AREA 09HGADBUG DC A(HGRDBUG) @ OF DEBUG AREAHGASDSA DC A(HPSSDSP) @ OF SOFTWARE DISTRIBUTION PARM 10HGARESV DC A(HGRESV) @ OF FUTURE USE AREAHGAEXIT DC A(HPSGXIP) @ OF HPS API EXIT AREA 09HGALMGP DC A(HPSLMGP) @ HPS ERROR MESSAGE ROUTE TABLE 11HGACONP DC A(HPSCONP) @ HPS CONVERSE TEXT CONSTANTS 12HGALANG DC A(HPEHL64) @ HPS CTRY/LANG SUPPORT TABLE 17HGACPTR DC A(HPELX10) @ HPS CODEPAGE TRANSLATION 19HGADDRF EQU HPSCGAP+256-* LENGTH TO PAD DC (HGADDRF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256) ALIGN TO X'100'HGCPARM EQU *TCTUAOFF DC H'0' TCTUA OFFSETEXECENV DC C'D' EXECUTION ENVIRONMENTDEVELOP EQU C'D' DEVELOPMENT ENVIRONMENTPROD EQU C'P' PRODUCTION ENVIRONMENTSECURITY DC C'N' SECURITY ON (YES/NO)SAF DC C'N' INVOKE HPSSAF (YES/NO)NOTIFY DC C'N' PHASEII NOTIFICATION (YES/NO)STRAT62 DC C'N' STRATUS LU6.2 INTERFACEHPO DC C'N' HIGH PERFORMANCE OPTION(YES/NO)CONV3270 DC C'Y' 3270 CONVERSE SUPPORT (YES/NO)SDS DC C'Y' SOFTWARE DISTRUBUTION(YES/MO)LU62SAF DC C'N' LU62 SAF ACTIVEWKSSECR DC C'Y' WORKSTATION SECURITY (YES/NO)* CURRENTLY APPLIES ONLY TO* 3270 CONVERSE SECURITY LOGICXSECEXIT DC C'N' USER SECURITY SIGNON EXIT (Y/N)ASYNC DC C'Y' ASYNCH SUPPORT (YES/NO)HGACSTOK DC C'$' DOLLAR THE CURRENCY SYMBOL TOKEN 17* USED TO DETERMINE HEX VALUE OF $ IN LOCAL CODE PAGE 17HGAHREPL DC C' ' HPS REPOSITORY LEVEL 17HGAHREPN DC CL8' ' HPS REPOSITORY NAME 17HGACTRYD DC H'34' USA HPS COUNTRY - DEFAULT 17HGACTRYC DC H'34' USA HPS COUNTRY - CURRENT 17HGCPARMF EQU HGCPARM+256-* LENGTH TO PAD DC (HGCPARMF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGTBL EQU * HPS INCORE TABLES AREATBL1ADDR DS F RULE/TRANSID TABLE 1TBL2ADDR DS F RULE/TRANSID TABLE 2TBL3ADDR DS F USRUSG/WKSNGP/BP TABLETBL4ADDR DS F NOTIFICATION TABLETBL5ADDR DS F USER/WRKSTN TABLETBL6ADDR DS F CONNECTIONS/SESSIONS TABLETBL7ADDR DS F HPS PROGRAMS TABLETBL8ADDR DS F RESERVEDTBL9ADDR DS F RESERVEDTBL10ADR DS F RESERVEDHGTBLF EQU HGTBL+256-* LENGTH TO PAD


HPICGAP Code

DC (HGTBLF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGFILE EQU * HPS FILES AREAHPS000D1 DS CL8 RESERVEDHPS001D1 DC CL8'HPI001D1' VIEW DEFINITION FILE 021HPS002D1 DC CL8'HPI002D1' TEST DATA FILE 021HPS003D1 DC CL8'HPI003D1' RULE SOURCE FILE 021HPS004D1 DC CL8'HPI004D1' RULE RELATIONSHIP FILE 021SEC001H1 DC CL8'SEI001H1' MENU FILESEC002H1 DC CL8'HPI006D1' ERROR LOG 021SEC003H1 DC CL8'SEI003H1' SECURITY LOGHPS008D1 DC CL8'HPI008D1' NOTIFICATION LOG 021HPSBC1D1 DC CL8'HPSBC1D1' BROADCAST MESSAGE DATAHPSBC2D1 DC CL8'HPSBC2D1' BROADCAST ID TABLEHPS030D1 DC CL8'HPI030D1' Rule Tran Relationship DB 021HPS031D1 DC CL8'HPI031D1' Sign-On Database 021HPS032D1 DC CL8'HPI032D1' Control Directory AllocDB 021HPS033D1 DC CL8'HPI033D1' List Directory Database 021HPS034D1 DC CL8'HPI034D1' Controls Extent Alloc DB 021HPS035D1 DC CL8'HPI035D1' Object Database 021HPS040D1 DC CL8'HPI040D1' Run Control Database 021HGFILEF EQU HGFILE+256-* LENGTH TO PAD DC (HGFILEF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGTDQ EQU * HPS TDQS AREAHPEL DC CL4'HPEL' ERROR LOG TD QUEUEHCSW DC CL4'HCSW' SECURITY LOG TD QUEUEHPNL DC CL4'HPNL' NOTIFICATION LOG TD QUEUEHGTDQF EQU HGTDQ+256-* LENGTH TO PAD DC (HGTDQF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGTSQ EQU * HPS TSQS AREA DC XL256'00'HGTSQF EQU HGTSQ+256-* LENGTH TO PAD DC (HGTSQF)X'0' PAD WITH BINARY ZEROS ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)HGCONST EQU * HPS CONSTANTS AREAAPPCTERM DC X'C0F0' -APPC TERMINALT3270 DC X'91F2' -3270 TERMINALPOSTWAIT DC PL4'5959' -ALMOST ONE HOURLU62SAFN DC CL8'FBCSAFZ' -LU62 SAF PGMNAMEHGCONSTF EQU HGCONST+256-* LENGTH TO PAD DC (HGCONSTF)X'0' PAD WITH BINARY ZEROS* ORG , ORG TO TOP OF AREA USED 11 ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256) 11** Please name all reserved areas with HGRxxxx here.*HGRDBUG DC XL256'00' HPS DEBUG AREA*HGRESV DC XL256'00' HPS FUTURE USE*HPSCGAPE EQU * END OF PROGRAM 08 END HPSCGAP


HPICGAPJ.JCL

HPICGAPJ.JCLThis sample JCL file for IMS is located in: &BASEQUAL..SVI531.SAMPLE (HPICGAPJ).

//* PLACE JOBCARD HERE//*-----------------------------------------------------------------//* THIS JOBSTREAM ASSEMBLES HPICGAP INTO THE &MODQUAL..OBJ LIBRARY.//* USE THE LINK OPTION IN THE AppBuilder HOST INSTALLATION WORKBENCH//* TO RE-LINK HPICGAP FOR IMS.//*-----------------------------------------------------------------//*//*//*REFER TO INI FILE MEMBERS (@MVSENV AND @HPSENV) TO RESOLVE VARIABLE//*//* ASSEMBLE AND LINK EDIT FOR HPICGAP//*//ASM EXEC PGM=IEV90,REGION=4M,// PARM=(NODECK,OBJECT,'SYSPARM=AppBuilder',LIST,SOURCE)//SYSLIB DD DSN=&MACLIB,DISP=SHR// DD DSN=&MODGEN,DISP=SHR//SYSLIN DD DSN=&MODQUAL..OBJ(HPICGAP),DISP=OLD//SYSPRINT DD SYSOUT=*//SYSUT1 DD SPACE=(CYL,(2,1),RLSE,CONTIG),// DCB=BLKSIZE=1024,UNIT=SYSDA//SYSIN DD DSN=&BASEQUAL..SVI531.SAMPLE(HPICGAP),// DISP=SHR//*//LKED EXEC PGM=IEWL,REGION=4M,// PARM=(LIST,XREF,'AMODE=31','RMODE=ANY',NORENT,REUS),// COND=(4,LT,ASM)//SYSLIB DD DSN=&BASEQUAL..LOADIM,DISP=SHR// DD DSN=&BASEQUAL..LOADLIB,DISP=SHR// DD DSN=&SPFLINK,DISP=SHR//SYSUT1 DD DCB=BLKSIZE=1024,// SPACE=(CYL,(2,1),RLSE),UNIT=SYSDA//SYSPRINT DD SYSOUT=*//SYSLIN DD DSN=&BASEQUAL..LKIMUC(HPICGAP),DISP=SHR//OBJECT DD DSN=&MODQUAL..OBJ,DISP=SHR// DD DSN=&BASEQUAL..OBJ,DISP=SHR//SYSLMOD DD DSN=&MODQUAL..LOADIM,DISP=SHR//*------- END OF JOB TO COMPILE HPICGAP


HPICGAPJ.JCL


APPENDIX

E HARDWARE AND SOFTWARE CHECKLISTS


Use the following checklists to verify that you have the necessary hardware and appropriate software versions supported by AppBuilder Host Development Workbench installed at your site. Enter all values on the lines provided. If you have versions of third-party software that differ from those listed, please contact AppBuilder’s ActionLine or your AppBuilder account manager for information and instructions.

After completing the checklists, return all of the pages to BluePhoenix Solutions by facsimile machine or return mail.

BluePhoenix Solutions, Inc.8000 Regency ParkwayCary, NC 27511United States

+1 919.380.5100+1 919.380.5111 faxwww.bluephoenixsolutions.com

Hardware RequirementsThis section summarizes the hardware and software prerequisites and corequisites for the AppBuilder 2.0.3.1 Host Development Workbench.

Table E-1 shows the hardware requirements for the AppBuilder 5.3.1 Host Development Workbench. Complete the checklist by defining the computer system and peripherals that will be used to install AppBuilder Host Development Workbench.

Table E-1 Hardware Requirements

Mainframe Model IBM 3090 or equivalent

Communications 3270 SDLC communication protocol

Magnetic Media 6250 BPI (tape cartridge)

Planning and Installing AppBuilder for the Mainframe E-1


DASD Requirements

DASD RequirementsTable E-2 shows the DASD cylinder allocations for the base AppBuilder Host Development Workbench and its optional products. The DASD cylinder allocations are based on a DASD class of 3380. Complete the checklist by calculating the amount of DASD allocations required to install and run AppBuilder Host Development Workbench at your site.

Supported Third-party ProductsThe following is a summary of supported versions of operating systems, compilers, runtime libraries, and databases. Complete the checklist with the versions of applicable software installed at your site.

Note Approximate DASD allocations for AppBuilder are derived from AppBuilder's QA testing, and limited to specified parameters. Customers should consider their own experience, normal system usage, and growth when determining their overall DASD requirements.

Table E-2 DASD cylinder allocations

DASD Allocation AppBuilder Host Development Workbench

AppBuilder Enterprise Repository (Base)This is the DASD requirement to install and use base AppBuilder Host Development Workbench (Host Installation Workbench, Enterprise Repository, and one repository version) for approximately 6 months.

2550 cylinders (total), comprised of:1350 cylinders for base software and one repository version980 cylinders for DB2 data sets220 cylinders for temporary work data sets

DASD cylinder allocation for each additional repository version

660 cylinders per version (includes repository software and data for each version)

Optional products

CICS Online Preparation70 cylinders for data sets250 cylinders for backups15 cylinders per repository version

CICS 3270 Converse Preparation Workbench 5 cylinders for data sets250 cylinders for backups

Mainframe Batch Preparation60 cylinders for data sets250 cylinders for backups15 cylinders per repository version

Mainframe Report Writer 5 cylinders for data sets250 cylinders for backups

IMS Online Preparation70 cylinders for data sets250 cylinders for backups15 cylinders per repository version

IMS 3270 Converse Preparation Workbench 5 cylinders for data sets250 cylinders for backups

Note Refer to Chapter 3, “Installation Requirements” for additional information about required put levels, PTFs, and notes about optional products. For further details, contact AppBuilder’s ActionLine

E-2 Hardware and Software Checklists


Table 5-4 Third-party Support

Versions Installed at Your Site Categories Third-party Product Publisher

Supported Versions for AppBuilder 2.0.3.1

Mainframe Operating System

OS/390 IBM 2.9, 2.10

z/OS IBM 1.1, 1.2, 1.3

System Software

CICS TS IBM 1.3, 2.1, 2.2

IMS IBM 6.0, 7.0

MQSeries IBM 1.2

WebSphere Application Server for OS/390 (Standard Edition)

IBM 3.5

Compilers and Runtime Libraries

Assembler H IBM 2.1

High Level Assembler IBM 2.1

IBM Cobol for OS/390 IBM 2.1, 2.2

IBM Cobol for z/OS IBM 3.1

OS PL/I IBM 2

Visualage PL/I for OS/390 IBM 2

PL/I for MVS IBM 1.1

LE Runtime OS/390 IBM 2.9, 2.10

Database DB2 IBM 6.1, 7.1

Planning and Installing AppBuilder for the Mainframe E-3


E-4 Hardware and Software Checklists

APPENDIX

F HOST INSTALLATION WORKBENCH CUSTOMIZATION WORKSHEETS

Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are from the actual installation. Enter all values which must be customized for your site on the lines provided.After completing this worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.

BluePhoenix Solutions USA, Inc.8000 Regency ParkwayCary, NC 27511United States


Using Customization Worksheets Numbers in this worksheet correspond to items in Chapter 4, “The Host Installation Workbench” the installation instructions for this product.

____________ 100.1 Installation Workbench D ataset Qualifier [Default: AB.INS2031]

Enter the dataset qualifier to be used for Installation Workbench data sets at your site. This qualifier forms the basis of all data set names used in this installation. Enter a maximum of 24 characters.

____________ 100.2 Volume Serial Number of your INS2031 tape [Default: None]

Enter the six-digit volume serial number located on the label of your Installation Workbench tape.

____________ 100.3 Unit used to read your INS2031 tape [Default: CART]

Enter the unit used to read your Installation Workbench tape.

____________ 100.4 Use Bypass Label Processing to unload tape? (Y/N) [Default: None]

Enter Y to use Bypass Label Processing and N to not use it.

Note In some cases, you may wish to use the default values provided by AppBuilder.

F-1


Using Customization Worksheets

____________ 100.5 DASD Unit for Installation Workbench Datasets [Default: SYSDA]

Enter the unit of the DASD containing the installation workbench data sets.

____________ 100.6 Volume for Installation Workbench Datasets (Optional) [Default: None]

Enter the volume ID for the installation workbench data sets.

____________ 100.7 DASD Unit for Temporary Datasets [Default: SYSDA]

Enter the DASD unit for temporary data sets.

____________ 100.8 Volume for Temporary Datasets (Optional) [Default: None]

Enter the volume ID for your temporary data set.

____________ 100.9 Access Method Services Program -[Default: IDCAMS]

Enter the name of your access method services program.

____________ 100.10 Access Method Services Loadlib (Optional)[Default: None]

Enter the name of your Access Method Services Loadlib.

____________ 100.11 LE Link Library [Default:CEE.SCEELKED]

Enter the name of your LE link library.

____________ 100.12 LE Runtime Library [Default:CEE.SCEERUN]

Enter the name of your LE Runtime library.

F-2 Host Installation Workbench Customization Worksheets

APPENDIX

G ENTERPRISE REPOSITORY CUSTOMIZATION WORKSHEETS


The following worksheet can assist you in planning how AppBuilder software will be installed at your site. All items are from the actual installation.Enter all values which must be customized for your site on the lines provided.

After completing this worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.



Using Customization WorksheetsNumbers in this worksheet correspond to items in Chapter 5, “Installing the Enterprise Repository” the installation instructions for this product.


Planning and Installing AppBuilder for the Mainframe G-1



____________ 200.1 Enter the System ID of the new system [Default: None]

Specify up to eight (8) alphanumeric characters per system name for your AppBuilder base system software. This name will be used to associate your AppBuilder base system software to one or more AppBuilder repositories. It must be a valid PDS member name which does not exist in the PDS &globqual..USER.CLIST. Refer to Chapter 4, “The Host Installation Workbench” section “Repository - System Association” for more information.

____________ 200.2 Enter Installation Dataset Qualifier [Default: AB1.INSTALL]

Enter the name of the installation data set qualifier. This must be a different qualifier than that entered for 100.1. This qualifier defines data sets that hold the AppBuilder system and repository installation software. Enter a maximum of 17 characters.

____________ 200.3 Enter System Dataset Qualifier [Default: AB1.BASE]

Enter the name of the system data set qualifier. This qualifier defines data sets which hold the AppBuilder system software. Enter a maximum of 17 characters.

____________ 200.4 Enter Maintenance Dataset Qualifier [Default: AB1.MOD]

Enter the name of the maintenance data set qualifier. This qualifier defines data sets which are created empty and can be used to hold client modifications or product fixes received from AppBuilder. Enter a maximum of 17 characters.

____________ 200.5 Enter System VSAM data set qualifier [Default: AB1.BASE]

Enter the name of the system VSAM data set qualifier. This qualifier defines VSAM data sets which are part of the AppBuilder system software and not specific to a repository. Enter a maximum of 17 characters.

____________ 200.6 Enter Language for Messages and Panels [Default: ENG]

Enter the language code for the messages and panels. Enter ENG (English) or DB for double-byte characters (Japanese).

____________ 200.7 Enter the AppBuilder Release Name [Default:None]

You must enter AB2031. This code indicates which AppBuilder product you are installing.

____________ 200.8 Enter the Volume Serial Number of your AppBuilder tape [Default: None]

Enter the volume serial number of the AppBuilder tape. Each tape shipped by AppBuilder has a unique number. This number can be found on the tape and in the packing list provided with the tape.

____________ 200.9 Enter the Unit used to read your AppBuilder tape [Default: CART]

Enter the name of the unit used to read your AppBuilder tape.

____________ 200.10 Use Bypass Label Processing to unload tape? (Y/N) [Default: None]

Specify Y or N to use Bypass Label Processing to unload tape.

____________ 200.11 Enter the DASD Unit for AppBuilder Datasets [Default: SYSDA]

Enter the DASD unit for AppBuilder data sets.

G-2 Enterprise Repository Customization Worksheets


____________ 200.12 Enter the DASD Volume for AppBuilder Datasets (Optional) [Default: None]

Enter the DASD volume for AppBuilder data sets, if applicable.

____________ 200.13 Enter the following for VSAM data sets if they apply:

Enter either a volume or management class.

__________ 200.13a Volume [Default: SYSDA]

Enter the volume for VSAM data sets, if applicable.

__________ 200.13b Management class [Default: None]

Enter the management class for VSAM data sets, if applicable.

____________ 200.14 Create FB or VB Clists for SYSPROC DD? (F/V) [Default: F]

Specify if the SYSPROC DD concatenation uses F (fixed block) or V (variable block) CLISTS.

____________ 200.15 If VB, specify LRECL and BLKSIZE:

If V (variable block CLISTs) entered in step 200.14, enter the required LRECL and BLKSIZE.

__________ 200.15a LRECL [Default: None]

Enter the record length if variable blocked CLISTs are used in step 200.14 (LRECL).

__________ 200.15b BLKSIZE [Default: None]

Enter the block size if variable blocked CLISTS are used in step 200.14 (BLKSIZE).

____________ 200.16 LE Link Library [Default: CEE.SCEELKED]

Enter the name of the LE Link Library.

____________ 200.17 LE Runtime Library [Default: CEE.SCEERUN]

Enter the name of the LE Runtime Library.

____________ 200.18 PL/I Math Library [Default:blank].

Enter the name of the PL/I Math Library. If you do not use a PL/I Math Library, leave it blank..

____________ 200.19 PL/I Call Library [Default: blank]

Enter the name of the PL/I Call Library. If you do not use a PL/I Call Library, leave it blank..

____________ 200.20 COBOL II Compiler Library [Default: IGY.V2R1M0.SIGYCOMP]

Enter the name of the COBOL II Compiler Library.

____________ 200.21 Include STEPLIB in the Cobol Compile step (Y/N)? [Default: Y]

Do you want to include STEPLIB in the COBOL Compile step of rule preparation?



____________ 200.22 COBOL II Compiler Name [Default: IGYCRCTL]

Enter the name of the COBOL II Compiler.

Required Parameters

__________ [Default:RENT,'TRUNC(BIN)',LIB]


Optional Parameters

__________ [Default:LIST,'FLAG(W)',OPT]

You can modify the optional parameters if necessary. CPARM1 will be concatenated with CPARM2.

____________ 200.23 H Assembler Name [Default: ASMA90]

Enter the Assembler H program name.

Required Parameters

__________ [Default: NODECK,OBJECT]


Optional Parameters

__________ [Default: LIST]

Modify the optional parameters if necessary.

____________ 200.24 Mainframe Macro Library [Default: SYS1.MACLIB]

Enter the mainframe Macro library name.

____________ 200.25 Mainframe Distribution MGEN Library [Default: SYS1.AMODGEN]

Enter the name of the mainframe Distribution MGEN library.

____________ 200.26 Mainframe Target MGEN Library (Optional) [Default: SYS1.MODGEN]

Enter the name of the mainframe Target MGEN library if the IBM default name is not used.

____________ 200.27 Is the PL/I Compiler Installed? [Default: N]

Specify if the PL/I compiler is installed. Enter Y or N. If not installed, the following PL/I items are optional.

____________ 200.28 PL/I Compiler Library [Default: PLI.V2R3M0.PLICOMP]

Enter the name of the PL/I Compiler Library.

____________ 200.29 Include STEPLIB in the PL/I Compile step? (Y/N) [Default: Y]

Do you want to include STEPLIB in the PL/I Compile step?



____________ 200.30 PL/I Compiler Name [Default: IEL0AA]

Enter the PL/I Compiler name. Define the required and optional parameters needed by the PL/I Compiler.

Required Parameters

__________ [Default: INC,OP,AG,NEST,STMT,GRAPHIC,'OPTIMIZE(TIME)']


Optional Parameters

__________ [Default: 'A(F)','X(F)',MAP,OF,STG]

You can modify the optional parameters if necessary. Optional parameters are concatenated with required parameters.

____________ 200.31 Is the MQ Series installed? [Default: N]

____________ 200.32 MQ Series Load Library (optional)

Enter the name of the MQ Series Load Library.

____________ 200.33 C Compiler Library [Default: CBC.SCBCCMP]

Enter the name of the C Compiler Library.

____________ 200.34 C Messages [Default: CEE.SCEEMSGP(EDCPMSGE)]

Enter the library containing the C compiler messages.

____________ 200.35 Enter the following if you will be creating C components.

Steps 200.33 thru 200.35c are optional. They are only required if C components will be written.

__________ 200.35a Include STEP:LIB in the C compile step? (Y/N) - [Default: Y]

__________ 200.35b C Compiler Name [Default: CBCDRVR]

Enter the name of the C compiler.

__________ 200.35c C Headers [Default: CEE.SCEEH.H]

Enter the library containing the C header files.

____________ 200.36 TCPIP SEZATCP Library [Default: TCPIP.SEZATCP]

____________ 200.37 TCPIP SEZACMTX Library [Default: TCIP.SEZACMTX]

____________ 200.38 Sort Program [Default: SORT]

Enter the sort program name.



____________ 200.39 Access Method Program [Default: IDCAMS]

Enter name if not IDCAMS.

____________ 200.40 Access Method Library (optional) [Default: None]

Enter library only if access method is not IDCAMS.

____________ 200.41 PDS Utility Program [Default: IEBCOPY]

Enter the name of the PDS copy utility program if not IEBCOPY.

____________ 200.42 PDS Utility Library (optional) [Default: None]

Enter the library name only if PDS copy utility program is not IEBCOPY.

____________ 200.43 TSO Command to clear the screen [Default: CLRSCRN]

____________ 200.44 Reason Code from LISTDSI if Dataset is Not Found [Default: 5]

If a third party package translates return codes from TSO LISTDSI, specify the TSO LISTDSI equivalent. [5] is returned by TSO LISTDSI. Used to designate the reason code from LISTDSI for data sets that are not found.

____________ 200.45 Is Dataset Archival Software such as HSM Used? (Y/N) [Default: Y]

Specify if data set archival software is used on this system.

__________ 200.45a Name of Program to Delete Archived Data Set [Default: HDELETE]

If “Y” entered for step 200.45, (data set archival software used) enter the name of the program used to delete archived data sets.

__________ 200.45b Delete Program Parameter String [Default: PURGE WAIT]

If “Y” entered for step 200.45, (data set archival software used) enter the delete program parameter string.

__________ 200.45c Reason Code Issued if Data Set is Migrated [Default: 9]

If “Y” entered for step 200.45, (data set archival software used) enter the return code issued if the data set is migrated.

____________ 200.46 Linkage Editor AMODE [Default: 31]

Enter the addressing mode of AppBuilder generated modules.

____________ 200.47 Linkage Editor RMODE [Default: ANY]

Enter the residency mode of AppBuilder generated modules.

____________ 200.48 Link Pack Area Library [Default: SYS1.LPALIB]

Enter the library name of the link pack area if not SYS1.LPALIB.

Note If this value is blank, you must manually edit the @MVSENV INI file and set the IEBLIB variable to ‘N/A’.



____________ 200.49 DB2 Load Library [Default: DSN610.DSNLOAD]

Enter the name of the DB2 load library that has the DSN command processor.

____________ 200.50 DB2 Link Library [Default: DSN610.DSNLINK]

Enter the name of the DB2 link library that will be used to link DB2 programs.

____________ 200.51 DB2 Preprocessor Name [Default: DSNHPC]

Enter the DB2 preprocessor program name.

____________ 200.52 Include STEPLIB in the DB2 Preprocessor step? (Y/N) [Default: Y]

____________ 200.53 DB2 Utility Proc Name [Default: DSNUPROC]

Enter the DB2 utility procedure name.

____________ 200.54 DB2 Utility Load Library [Default: DSN610.DSNLOAD]

Enter the DB2 load library that contains the load module DSNUPROC or its equivalent at your site.

____________ 200.55 ISPF Link Library [Default: ISP.ISPLOAD]

The name of the ISPF link library used to link AppBuilder ISPF modules.

____________ 200.56 ISPF Profile Library [Default: None]

The name of the common ISPF table library that contains member ISPPROF.

____________ 200.57 Specify Mainframe Codepage [Default: 037]

The codepage is a number assigned by IBM to designate the character set in each country. It defines which character will be produced on a display or printer for a given byte value (0 to 255). Many of these are unvarying across codepages, but some produce different results—for example, the value that produces a dollar sign in the US shows as a monetary pound sign in the UK.

Specify the host codepage for your national language.

____________ 200.58 Specify OS/2 Codepage -[Default: 437]

Enter the OS/2 codepage used on the development workstation. 437 is default codepage for US or UK English: 850 is the MLS codepage (US and UK English, French, Spanish, Italian, German, Danish, etc.). The [NLS] Codepage_OS2 value can be found on the development workstation in \HPS\HPS.INI.

____________ 200.59 Specify AIX Codepage [Default: 2]

Enter the AIX codepage used on the development workstation:1—IBM-850, or 2—IS08859-1.

____________ 200.60 PC Equivalent of ‘AT’ Character [Default: @]

If the codepage you have selected does not support the “@” character, enter the character that maps to the equivalent host value (for example, the character EBCDIC hex 7C is mapped to on the host).

Note ISPF library names should not be left blank.



____________ 200.61 Default Language for Repository Objects (Abbreviation) [Default: ENU]

Enter the default language abbreviation for the repository objects. For example, ENU means US English.

The following table lists valid codepage and default language combinations between mainframe, OS/2, and AIX, referenced by items 200.54, 200.55, 200.56, and 200.58

____________ 200.62 Default Retrieval Format for DB2 DATE Values [Default: ISO]

Specify the retrieval format of DB2 DATE values. Valid values are EUR—IBM European Standard, ISO—International Standards Organization, JIS—Japanese Industrial Standard, USA—IBM USA Standard or LOCAL—Site defined.

____________ 200.63 If a LOCAL Date Format is used, enter it Here [Default: None]

Specify the DB2 date format if LOCAL specified in the previous step. This value must match the DATE format defined when DB2 was installed at your site. Example: %Y-%0m-%0d—year-month-day.

____________ 200.64 Default Retrieval Format for DB2 TIME Values [Default: ISO]

Specify the retrieval format of DB2 TIME values. Valid values are:EUR—IBM European Standard, ISO—International Standards Organization, JIS—Japanese Industrial Standard, USA—IBM USA Standard or LOCAL—Site defined.

____________ 200.65 If a LOCAL Time Format is used, Enter it Here [Default: None]

Specify the DB2 date format if LOCAL specified in the previous step. This value must match the TIME format defined when DB2 was installed at your site. Example: %0t.%0m.%0s—hour.minute.second.

____________ 200.66 Maximum Nested IF statements in Rules [Default: 40]

Specify the maximum level allowed for nesting IF statements consecutively. When rules code exceeds this limit, severe error #87959 will occur.

____________ 200.67 Retention Period for Tape Datasets in Days [Default: None]

Enter the following for HPS tape data sets. Specify the number of days tape data sets will be kept. Retention Period in Days: number of days data sets will be kept.

____________ 200.68 CLIST Libraries [Default: None]

Enter the CLIST libraries (SYSPROC) for background TSO jobs

(5 entries)



____________ 200.69 ISPF Panel Libraries [Default: ISR.ISRPLIB]

Enter the ISPF PANEL libraries (ISPPLIB) for background TSO jobs.

(5 entries)

____________ 200.70 ISPMLIB [Default: None]

Enter the ISPF MESSAGE libraries used for background TSO jobs.

(5 entries)



____________ 200.71 ISPSLIB [Default: None]

Enter the ISPF SKELETON libraries used for background TSO jobs.

(5 entries)

____________ 200.72 ISPTLIB [Default: None]

Enter the ISPF TABLE libraries used for background TSO jobs.

(5 entries)



____________ 200.73 The ISPLLIB entries are optional. Omit if not used at your site. [Default: None]

Enter the optional ISPL libraries used for background TSO jobs.

(5 entries)

____________ 200.74 Enter the repository ID (name) of the new repository.

Specify up to eight (8) alphanumeric characters per repository name for your AppBuilder repository software. This name will be associated with your AppBuilder base system software which was created during the System Functions installation. (Refer to Chapter 4, “The Host Installation Workbench” section “Repository - System Association” on page -3 for more information.) In the example used in this document, “repname” is used as a sample repository name and “sysname” is used as a sample system name. Panels displayed on your system will display the repository name you have entered.

____________ 200.75 Enter the System ID which will be associated with the new repository [Default: None]

The Repository ID name cannot be the same as the System ID.

____________ 200.76 DB2 Subsystem ID [Default: DSN]

Enter the subsystem ID where AppBuilder DB2 objects will reside.

____________ 200.77 DB2 Object Creator ID [Default: <Installer’s ID>]

Enter the creator or owner ID for all AppBuilder system tables. This ID can either be the installer’s ID or a secondary auth ID.

____________ 200.78 DB2 Plan Owner ID [Default: Installer’s ID]

Enter the DB2 Plan Owner ID. This ID can either be the installer’s ID or a secondary auth ID for the installers’ ID. For an upgrade, this must be a different ID than INST1ADM.

____________ 200.79 AB DataBase Name [Default: AB203]

Enter the name of the database in which AppBuilder system DB2 objects are to reside.



____________ 200.80 DB2 VCAT or Storage Group [Default: None]

Specify whether VCATs or storage groups are used. Enter V for VCAT or S for storage groups. V—you create VSAM manually, S—creates objects in an existing storage groups and VSAM is automatically created.

____________ 200.81 DB2 Storage Group Name [Default: None]

If you chose “S” (storage group) in step 200.80, enter the storage group name of an existing storage group you want to use.

____________ 200.82 DB2 VCAT Name [Default: None

If you chose “V” (VCAT) in step 200.80, enter the VCAT name.

____________ 200.83 Volume ID for DB2 Tablespaces [Default: None]

If you chose VCAT in step 200.80, enter the DASD device where AppBuilder’ DB2 tablespaces are to be stored. The same volume name can be used for DB2 tablespaces and indexspaces.

____________ 200.84 Volume ID for DB2 Indexspaces [Default: None]

If you chose VCAT in step 200.80, enter the DASD device where HPS’ DB2 indexspaces are to be stored. The same volume name can be used for DB2 tablespaces and indexspaces.

____________ 200.85 DB2 Plan Prefix [Default: A]

Enter the one-character prefix used for AppBuilder system plans. If multiple repositories of AppBuilder will be supported within a DB2 subsystem, each repository must have a unique prefix.

____________ 200.86 Owner of Application DB2 Tables [Default: &SYSUID]

Enter the owner ID of the AppBuilder application tables.

____________ 200.87 Repository ID [Default: None]

Enter the unique two-character alphabetical suffix used in AppBuilder short name object generation.

____________ 200.88 Number of Versions [Default: 1]

Enter the number of versions or partitions within the repository. You may define a minimum of 1 and a maximum of 10 versions per enterprise repository. Additional versions can be installed. Individual versions require additional allocations of DASD as non-DB2 data sets must be allocated for each version.

____________ 200.89 Specify the prefix for each of these non-versioned data sets:

Enter a prefix for each of the following. The prefix entered will be used in the data set name at your site. All variables support more than one node.

__________ 200.89a Repository Modification [Default: AB1.REP]

Enter the repository modification data set prefix. This qualifier defines data sets which hold information specific to a given repository. You can also use these data sets to hold software modifications which are to affect only one repository. Enter a maximum of 18 characters.



__________ 200.89b User Datasets [Default: AB1.USER]

Enter the user data set prefix. This qualifier defines data sets which hold user application information for specific repository versions. Enter a maximum of 17 characters.

__________ 200.89c VSAM User [Default: AB1.USER]

Enter the VSAM data set prefix. This qualifier defines VSAM data sets which hold user application runtime information for CICS, IMS, and Batch. Enter a maximum of 17 characters.

__________ 200.89d Temporary Output [Default: TEMP.NN]

Enter the temporary output data set prefix. This qualifier defines data sets that will be generated by the user while working in the AppBuilder Enterprise Repository. May be a maximum of 10 characters, with the final node being seven (7) characters or less since it is specific to a repository version. The repository version number is concatenated to the final node.

__________ 200.89e User-ID (Short-term) [Default: &SYSUID]

Enter the prefix for output user ID data sets which are short-term, to a maximum of 18 characters. This qualifier defines data sets that will be generated by the user while work-ing in the AppBuilder Enterprise Repository. This value must contain the &SYSUID vari-able since it is specific to each user. For example, you can specify HPS.&SYSUID.

__________ 200.89f User-ID (Permanent) [Default: AB1OUT]

Enter the prefix for user output data sets that are permanent or long-term. This qualifier defines data sets that will be generated by the user while working in the AppBuilder Enterprise Repository. May be a maximum of 10 characters.

____________ 200.90 Should VIEW Copybooks Include Alignment Bytes? (Y/N) [Default: N]

Specify if VIEW copybooks should include alignment bytes.

____________ 200.91 Permanent data sets

Enter the following information for permanent data sets.

__________ 200.91a Unit [Default: SYSDA]

Enter the name of the direct access storage device that will store AppBuilder permanent data sets.

__________ 200.91b Volume ID Required? [Default: N]

If pool DASD is used (that is, JCL parameter VOL=SER is not used), then enter N and leave Permanent Volume ID blank. Otherwise, enter Y and a volume ID.





__________ 200.91c Volume ID


____________ 200.92 Temporary data sets

Enter the following information for temporary data sets.


Enter the name of the direct access storage device that will store AppBuilder temporary data sets.


If pool DASD is used (JCL parameter VOL=SER not used), enter N and leave Tempo-rary Volume ID blank. If DASD must be specified, enter Y and a volume ID.

__________ 200.92c Volume ID [Default: None]


____________ 200.93 VIO data sets

Enter the following information for VIO data sets.


Enter the name of the direct access storage device that will store AppBuilder VIO data sets.


If pool DASD is used (that is, JCL parameter VOL=SER is not used), then enter N and leave VIO Volume ID blank. If DASD must be specified, then enter Y and a Volume ID.

__________ 200.93c Volume ID [Default: None]


____________ 200.94 Job Class (CLASS) [Default: 1]

Enter the JCL Job Class used for user-submitted jobs through the repository interface.

____________ 200.95 Message Class (MSGCLASS) [Default: A]

Enter the JCL Message Class used for user-submitted jobs through the repository interface.

____________ 200.96 Time Parameter (TIME) [Default: None]

Enter the JCL time parameter if required for the job card.

____________ 200.97 Priority (PRTY) [Default: 12]

Enter the JCL priority parameter if required for the job card.



____________ 200.98 Region size (REGION) [Default: 4M]

Enter the JCL region size parameter if more than 4M is required.

____________ 200.99 Default Jobname Suffix Character [Default: M]

Enter a default JCL suffix character.

____________ 200.100 Default Job Description [Default: JOB]

Enter a default job description for AppBuilder jobs.

____________ 200.101 Overnight Job Class [Default: 1]

Enter the job class used to defer jobs for overnight execution.

____________ 200.102 SYSOUT Class for Batch Jobs [Default: *]

Enter SYSOUT class for batch job processing and batch reports.

____________ 200.103 Internal Reader Name [Default: INTRDR]

Enter the name of the internal reader if different from the default name.

____________ 200.104 Internal Reader Output Class [Default: 1]

Enter the output class for the internal reader.

____________ 200.105 Default Printer [Default: None]

Enter default printer ID to be used for printing reports.

____________ 200.106 Use Customized Job Card Skeleton [Default: N]

Specify Y or N to use a customized job skeleton.

____________ 200.107 Batch JOB Submission Option [Default: Y]

Specify Y to submit jobs automatically or N to save jobs in a data set. The JCL will be saved in data set &USRVQUAL..JCL. To override this, you must specify the fully qualified data set name in the INI variable called JCLDSN in &REPQUAL..INI(@HPSENV). Y or N for an external scheduling interface.

____________ 200.108 Is there an External Scheduling Interface? [Default: N]


____________ 200.109 Include the STEPLIB DD in batch jobs?

Specify Y or N if the STEPLIB DD should be included in batch jobs.

____________ 200.110 Include the STEPLIB DD in non-DB2 steps?

Specify Y or N if the STEPLIB DD should be included in non-DB2 steps.



____________ 200.111 Include each of the following in STEPLIB:

Specify with Y or N whether to include each of the following in STEPLIB. TSODD is a batch job skeleton.

__________ 200.111a DB2 Load Libraries [Default: Y]

Specify if the DB2 load libraries should be in the STEPLIB of TSODD.

__________ 200.111b MODQUAL Load Library [Default: Y]

Specify if the AppBuilder modification load libraries should be in the STEPLIB of TSODD.

____________ 200.112 Specify the CICS or IMS Transaction ID Option:

Specify the following option, as appropriate. The following are valid values: S-Use Source ID, T-Use Target ID, B-Blank.

__________ 200.112a CICS [Default: T]

Specify the CICS transaction ID option.

__________ 200.112b IMS [Default: T]

Specify the IMS transaction ID option.

____________ 200.113 Default Migration Dataset High Level Qualifier [Default: HPSOUT]

Enter the default migration data set high level qualifier. May be a maximum of 8 characters.

____________ 200.114 Analyze Collisions During Import? (Y/N) [Default: Y]

Specify if collisions are analyzed during import.

____________ 200.115 Analyze Collisions on SYSTEMID or LONGNAME?(S/L) [Default: L]

Specify if collisions are analyzed on SYTEMID or LONGNAME.

____________ 200.116 Process User Exits During Migration? (Y/N) [Default: N]

Specify if user exits are processed during migration.

__________ 200.116a If ‘Y’ Enter Name of Optional Exit Rexx Exec [Default: None]

If “Y” entered for 200.116a, enter the name of the exit REXX.

____________ 200.117 For each of the following enter Y to include the item in a migration or N to exclude it from

migration:

Enter Y or N for the following

__________ 200.117a Default Option for ‘Create’ Entities (Y/N) [Default: Y]

Specify Y or N to allow default option for ‘Create’ entities.



__________ 200.117b Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the ‘Create’ entities option. ‘

__________ 200.117c Default Option for ‘Update’ Entities (Y/N) [Default: Y]

Specify Y or N to allow default option for ‘Update’ entities.

__________ 200.117d Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the ‘Update’ entities option.

__________ 200.117e Default Option for ‘Delete’ Entities (Y/N) [Default: Y]

Specify Y or N to allow default option for ‘Delete’ entities.

__________ 200.117f Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the ‘Delete’ entities option.

__________ 200.117g Default Option for Source (Y/N) [Default: Y]

Specify Y or N to allow default option for Source.

__________ 200.117h Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the Source option.

__________ 200.117i Default Option for Keywords (Y/N) [Default: Y]

Specify Y or N to allow default option for Keywords.

__________ 200.117j Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the Keywords option.

__________ 200.117k Default Option for Text (Y/N) [Default: Y]

Specify Y or N to allow default option for Text.

__________ 200.117l Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the Text option.

____________ 200.118 Enter Y to include the following steps in MIGRATE method processing or N to exclude

them:

Enter Y or N for the following.

__________ 200.118a Include IMPORT Step? (Y/N) [Default: N]

Specify Y or N to include the IMPORT step.

__________ 200.118b Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include IMPORT step option.



__________ 200.118c Include REBUILD Analyzer? (Y/N) [Default: N]

Specify Y or N to include the REBUILD Analyzer.

__________ 200.118d Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Analyzer option.

__________ 200.118e Include REBUILD Prepare? (Y/N) [Default: Y]

Specify Y or N to include the REBUILD Prepare.

__________ 200.118f Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Prepare option.

__________ 200.118g Include REBUILD Install? (Y/N) [Default: Y]

Specify Y or N to include the REBUILD Install.

__________ 200.118h Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Install option.

__________ 200.118i Include REBUILD Export? (Y/N) [Default: N]

Specify Y or N to include the REBUILD Export.

__________ 200.118j Can the User Modify this Option? (Y/N) [Default: N]

Specify Y or N whether the user can modify the include REBUILD Export option.

____________ 200.119 Application DB2 environment

__________ 200.119a Support DB2 Packages? (V/N/P) [Default: N]

Specify V or P to support DB2 packages. N indicates that packages are not supported. V indicates DB2 packages will be supported for all the projects within a repository version. P indicates DB2 packages will be supported per project within a repository version. Please refer to the Managing Enterprise Repositories manual for more information on DB2 package support.

__________ 200.119b If V or P, specify Collection ID [Default: None]

If using packages, specify the default Collection ID for this repository version.

__________ 200.119c If V or P, specify Owner ID [Default: None]

If using packages, specify the default Owner ID for this repository version.

__________ 200.119d If V or P, specify Qualifier ID [Default: None]

If using packages, specify the default Qualifier ID for this repository version.



__________ 200.119e If V or P, specify Plan Name [Default: None]

If using packages, specify the default Plan Name for this repository version.

__________ 200.119f If V or P, specify E if a Package List is Required or W if the Wildcard (*) is

Supported (E/W) [Default: W]

If you use Packages, specify E to require an explicit package list or specify W to support the asterisk (*) for wildcards for this repository version.

__________ 200.119g Perform GRANT as part of Prepare Method? (Y/N) [Default: Y]

Specify Y or N to perform GRANT as a part of the Prepare method.

__________ 200.119h Use Configuration Units for Preparation? (Y/N) [Default: N]

Specify Y or N to use configuration units for preparation.

____________ 200.120 Optional User Libraries for Component Prepares

Enter the following library names.

__________ 200.120a NCAL Batch Library [Default: None]

Define the NCAL batch library.

__________ 200.120b NCAL CICS Library [Default: None]

Define the NCAL CICS library.

__________ 200.120c NCAL IMS Library [Default: None]

Define the NCAL IMS library.

__________ 200.120d Other NCAL Library [Default: None]

Define the other NCAL batch library.

__________ 200.120e Batch Load Library [Default: None]

Define the batch load library.

__________ 200.120f CICS Load Library [Default: None]

Define the CICS load library.

__________ 200.120g IMS Load Library [Default: None]

Define the IMS load library.

__________ 200.120h Other Load Library [Default: None]

Define the other load library.



__________ 200.120i ASM Copylib [Default: None]

Define the ASM copylib.

__________ 200.120j COBOL Copylib [Default: None]

Define the COBOL copylib.

__________ 200.120k C Copylib [Default: None]

Define the C language copylib.

__________ 200.120l PL/I Copylib [Default: None]

Define the PL/I copylib.

__________ 200.120m ASM DCLGEN [Default: None]

Define the ASM DCLGEN.

__________ 200.120n COBOL DCLGEN [Default: None]

Define the COBOL DCLGEN.

__________ 200.120o C DCLGEN [Default: None]

Define the C Language DCLGEN

__________ 200.120p PL/I DCLGEN [Default: None]

Define the PL/I DCLGEN.


APPENDIX

H BATCH PREPARATION WORKBENCH CUSTOMIZATION WORKSHEETS

Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are from the actual installation. Enter all values which must be customized for your site on the lines provided.After completing the worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.



Using Customization WorksheetsNumbers in this worksheet correspond to items in Chapter 6, “Installing Batch Preparation Workbench” the installation instructions for this product.

_____________ 300.1 Plan name prefix or suffix - [Default: B]

You can form DB2 plan names by using the generated bitmap as the plan name prefix or suffix. Enter B as the prefix or P to use the bitmap as the suffix.

_____________ 300.1 Use AppBuilder Project name in Batch plan name? (Y/N) - [Default: N]

Enter Y or N to specify if you want to use the AppBuilder project name in the Batch plan name.

_____________ 300.1 If not, enter the string to use here: - [Default: PLNB]

If you specified N above, enter the string you want to use for the Batch plan name.

_____________ 300.1 Use the repository version number in plan name (Y/N) - [Default: N]

Enter Y or N to specify if you want to use the repository version number in the Batch plan name.


H-1



H2 Batch Preparation Workbench Customization Worksheets

APPENDIX

I CICS ONLINE PREPARATION WORKBENCH AND ENTERPRISE SERVER CUSTOMIZATION WORKSHEETS


Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are
from the actual installation. Enter all values which must be customized for your site on the lines provided.After completing the worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.


Using Customization Worksheets Numbers in this worksheet correspond to items in the installation instructions for this product described in Chapter 8, “Installing CICS Online Preparation Workbench and Enterprise Server”

_____________ 400.1 CICS Runtime Library -[Default: CICS33.LOADLIB]

Enter the name of the CICS runtime library used to link AppBuilder modules.

_____________ 400.2 Runtime Dataset Name Suffixes:

Enter the runtime data set name suffix.

_____________ 400.3 Load Library Output - [Default: LOADCI]

Enter the load library output suffix, to a maximum of eight (8) characters.

_____________ 400.4 NCAL Library Output - [Default: NCALCI]

Enter the NCAL library output suffix, to a maximum of eight (8) characters.


Planning and Installing AppBuilder for the Mainframe I-1



_____________ 400.5 VSAM View Definition File - [Default: HPS001D1.VIEWDEF]

Enter the VSAM view definition file suffix.

_____________ 400.6 VSAM Rule Source Output - [Default: HPS003D1.RULESRC]

Enter the VSAM rule source output suffix.

_____________ 400.7 VSAM Rule Relation Output - [Default:HPS004D1.RLRELATN]

Enter the VSAM rule relation output suffix.

_____________ 400.8 VSAM View Definition (PCNV) - [Default: HPS021D1.VIDTEXT]

Enter the VSAM view definition output suffix.

_____________ 400.9 Runtime Dataset DDNAMES:

Enter the following DDNAMEs.

_____________ 400.10 VSAM View Definition File - [Default: HPS001D1]


_____________ 400.11 VSAM Rule Source Output - [Default: HPS003D1]

Enter the DDNAME for the VSAM rule source output.

_____________ 400.12 VSAM Rule Relation Output - [Default: HPS004D1]

Enter the DDNAME for the VSAM rule relation output.

_____________ 400.13 VSAM View Definition (PCNV) - [Default: HPS021D1]


_____________ 400.14 CICS Runtime Library - [Default: CICS33.LOADLIB]

Enter the CICS runtime library name at your site.

_____________ 400.15 CICS Macro Library - [Default: CICS.MACLIB]

Enter the CICS macro library name at your site.

_____________ 400.16 CICS PL/I Library - [Default: CICS.PLILIB]

Enter the PL/I library name at your site.

_____________ 400.17 CICS COBOL Library - [Default: CICS.COBLIB]

Enter the CICS COBOL library name at your site.

_____________ 400.18 CICS ASM Translator - [Default: DFHEAP1$]

Enter the CICS ASM translator name at your site.

I-2 CICS Online Preparation Workbench and Enterprise Server Customization Worksheets


_____________ 400.19 CICS PL/I Translator - [Default: DFHEPP1$]

Enter the CICS PL/I translator name at your site.

_____________ 400.20 CICS COBOL Translator - [Default: DFHECP1$]

Enter the CICS COBOL translator name at your site.

_____________ 400.21 CICS C370 Translator - [Default: DFHEDP1$]

Enter the CICS 3270 translator library name at your site.

_____________ 400.22 Use HPS/CICS Autoinstall? (Y/N)

If Y is entered, AppBuilder software automatically makes the program definitions in the CICS region available during preparation of user rules and components. It will also process AppBuilder user VSAM files and update the AppBuilder incore table with the rule and its associated trans ID.

_____________ 400.23 CEDA Transaction Name - [Default: CEDA]

Enter the CEDA transaction name used at your site.

_____________ 400.24 CEMT Transaction Name - [Default: CEMT]

Enter the CEMT transaction name used at your site.

_____________ 400.25 CICS Version - [Default: 4]

Enter the CICS version number used at your site.

_____________ 400.26 CICS Release - [Default: 4]

Enter the CICS release number used at your site.

_____________ 400.27 You may form CICS DB2 plan names by using the generated bitmap as the plan name prefix

or suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default: B]

Specify how the generated bitmap is used in the CICS DB2 plan name.

_____________ 400.28 Use AppBuilder Project name in CICS plan name? (Y/N) - [Default: N]

Specify if the AppBuilder project name is used in the CICS plan name.

_____________ 400.29 If not, enter the string to use here: - [Default: PLNC]

If the AppBuilder project name is not used in the CICS plan name, enter the name to use.

_____________ 400.30 Use the repository version number in plan name? (Y/N): - [Default: N]

Specify if the repository version number is used in the plan name.

_____________ 400.31 Use the region type (‘C’) in the plan name? (Y/N) - [Default: N]

Specify if the region type is used in the plan name.



_____________ 400.32 INTERTEST (Supply these values if INTERTEST is installed):

Enter the following if INTERTEST debugging feature is installed in this region.

_____________ 400.33 Intertest ASM Program - [Default: IN25SYMA]

Enter the ASM program name.

_____________ 400.34 Intertest COBOL Program - [Default: IN25COB2]

Enter the COBOL program name.

_____________ 400.35 Intertest PL/I Program - [Default: IN25SYMP]

Enter the PL/I program name.

_____________ 400.36 Intertest PROTSYM Dataset - [Default: None]

Enter the PROTSYM data set name.

_____________ 400.37 Intertest STEPLIB - [Default: None]

Enter the STEPLIB program name.

_____________ 400.38 Minimum Transaction ID for this Version: - [Default: AAAA]

Enter the minimum transaction ID for this version.

_____________ 400.39 Maximum Transaction ID for this Version: - [Default: AA99]

Enter the maximum transaction ID for this version.

_____________ 400.40 Number of CICS Regions you want to configure for version 1 - [Default: None]

Enter the number of CICS regions you want to configure for repository version 1.

_____________ 400.41 Enter the VTAM name of this region - [Default: None]

Enter the VTAM name of this region.

• Enter the VTAM APPLID’s for LU2 processing: 1 - [Default: A06HPS1] 2 - [Default: A06HPS2] 3 - [Default: A06HPS3]

The AppBuilder LU2 CICS Auto-install feature allows AppBuilder objects (rules, components, etc.) to be automatically defined to CICS during AppBuilder preparation (compile, linkedit, etc.). Depending on the object being prepared, it will connect to CICS via the VTAM applids and execute the following transactions:

• HS96 - AppBuilder newcopy transaction

• CEDA - CICS transaction to define AppBuilder objects

• CEMT - CICS transaction to close and open AppBuilder VSAM files

• UTBL - AppBuilder transaction to add rule/tranid to AppBuilder incore table 2 (HPSTBLE2)

Enter three VTAM application IDs.



_____________ 400.42 Define HPS CICS group to the startup group list? (Y/N) - [Default: N]

Specify whether the AppBuilder CICS groups should be defined to the startup group list during a rule or component prepare.

_____________ 400.43 Define HPS transactions during rule prepare? (Y/N) - [Default: Y]

Specify if transactions are defined during a rule prepare.

_____________ 400.44 Should the HPS transaction UTBL be executed? (Y/N) - [Default: Y]

Specify if the UTBL transaction should be executed during a rule prepare.

_____________ 400.45 Enter the startup group list name for HPS groups - [Default: None]

Enter the startup group list name for AppBuilder groups.

_____________ 400.46 HPS groups will be added to the startup list AFTER or BEFORE a specified group. Enter the

specified group name here. - [Default: None]

Enter the specified group name.

_____________ 400.47 Enter A to add new groups AFTER this group or B for BEFORE - [Default: B]

Specify where the AppBuilder group will be added to the group named above.

_____________ 400.48 Temporary groups will be built from a one-character prefix and the Userid. Specify the one-

character prefix for temporary groups - [Default: H]

Enter a one character prefix for temporary groups.

_____________ 400.49 CICS group names for HPS objects may be a constant string OR a constant string combined

with the HPS project name. The combined length may not exceed 8 characters.

If you use the project name in the group name, enter H if the HPS project should come first or C if the constant string should come first - [Default: H]

_____________ 400.50 For PPTs:

Enter the following information for PPTs.

_____________ 400.51 Use HPS project name as part of the group name? (Y/N) - [Default: Y]


_____________ 400.52 Enter the optional string to use in the group name - [Default: HPS]


_____________ 400.53 For PCTs:

Enter the following information for PCTs.

_____________ 400.54 Use HPS project name as part of the group name? (Y/N) - [Default: Y]




_____________ 400.55 Enter the optional string to use in the group name - [Default: HPS]



APPENDIX

J IMS ONLINE PREPARATION WORKBENCH AND ENTERPRISE SERVER CUSTOMIZATION WORKSHEETS


Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are from the actual installation. Enter all values which must be customized for your site on the lines provided. After completing this worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.

BluePhoenix Solutions, Inc.8000 Regency ParkwayCary, NC 27511United States


Using Customization WorksheetsNumbers in this worksheet correspond to items in the installation instructions for this product described in Chapter 9, “Installing IMS Online Preparation Workbench and Enterprise Server”.

______________ 600.1 IMS RESLIB -[Default: SYS1.RESLIB]

Enter the qualified name of the IMS resident library used to link AppBuilder modules.

______________ 600.2 IMS CSSLIB - [Default: SYS1.CSSLIB]

Enter the qualified name of the CSS library used to link AppBuilder modules to support LU6.2 processing for AppBuilder’s NetEssential middleware.

______________ 600.3 Runtime Dataset Name Suffixes:

Complete the following values.

______________ 600.4 Load Library Output - [Default: LOADIM]

Enter the name of the suffix for the Load Library Output data sets for IMS.


Planning and Installing AppBuilder for the Mainframe J-1



______________ 600.5 NCAL Library Output - [Default: NCALIM]

Enter the name of the suffix for the NCAL Library Output data sets for IMS.

______________ 600.6 VSAM View Definition File - [Default: HPI001D1.VIEWDEF]

Enter the name of the suffix for the VSAM View Definition File data sets for IMS.

______________ 600.7 VSAM Rule Source Output - [Default: HPI003D1.RULESRC]

Enter the name of the suffix for the VSAM Rule Source Output file for IMS.

______________ 600.8 VSAM Rule Relation Output - [Default:HPI004D1.RLRELATN]

Enter the name of the suffix for the VSAM Rule Relation Output file for IMS

______________ 600.9 Specify the Jobname for IMS Control Region - [Default: None]

Enter the jobname for the IMS Control Region at your site.

______________ 600.10 Specify the dataset name which contains the IMS VSAM Buffer Cards - [Default:

SS0216.SVI531.SAMPLE(DFSVSM)]

______________ 600.11 You may form IMS DB2 plan names by using the generated bitmap as the plan name prefix or

suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default: P]

Enter the default value to use the bitmap as a suffix.

______________ 600.12 Use AppBuilder Project name in IMS plan name? (Y/N) - [Default: Y]

Enter the default value to use the AppBuilder project name in the IMS plan name.

______________ 600.13 If not, enter the string to use here: - [Default: HP]


______________ 600.14 Use the repository version number in plan name? (Y/N): - [Default: Y]

Enter the default value to use the repository version number in the plan name.

______________ 600.15 Use the region type (‘M’) in the plan name? (Y/N) - [Default: Y]

Enter the default value to use the region type M in the plan name.

______________ 600.16 Should a separate plan be generated for Batch Rules (Y/N) - [Default: N]

If you want to generate a separate plan for Batch Rules, enter Y. If not, enter N.

______________ 600.17 Use HPS/IMS Autoinstall? (Y/N) - [Default: none]

If you want to use HPS/IMS Autoinstall, enter Y. If not, enter N. This feature is a batch interface that automatically connects to IMS to open and close AppBuilder databases and to update the HPS incore table with the AppBuilder IMS rule and transaction ID.

J2 IMS Online Preparation Workbench and Enterprise Server Customization Worksheets


______________ 600.18 IMS General Library Names:

______________ 600.19 General IMS Lib Prefix - [Default: IMS410.VENDOR]

Enter the name of your general IMS library prefix.

______________ 600.20 IMS VTAM ID - [Default: IMS41]

Enter the VTAM applid for this IMS system.

______________ 600.21 IMS Region name - [Default: IMSB]

Enter the IMS system name.

______________ 600.22 IMS MACLIB Library - [Default: SYS1.IMS.MACLIB]

Enter the name of your IMS Macro library (MACLIB).

______________ 600.23 IMS Res Library - [Default: IMS410.VENDOR.RESLIB]

Enter the name of your IMS Resident Library (Res Library).

______________ 600.24 IMS AGN name - [Default: none]

Enter the AGN (Application Group Name) value if AGNs are used at your site.

______________ 600.25 IMS HPS Log Message - [Default: IMS410.LGMSG]

Enter any fully qualified data set name used by the IMS Control Region. This library is used to determine if IMS is up before submitting AppBuilder BMP jobs.

______________ 600.26 Maximum Transaction ID for this Version: - [Default: none]

Currently this value is set by a AppBuilder internal program for IMS transactions.

______________ 600.27 Number of IMS Regions you want to configure for this version - [Default: none]

Please use the default value.

______________ 600.28 Enter the VTAM APPLIDs for LU2 processing:

If you specified Y for item 600.17, then you must enter the names of the three VTAM APPLIDs for LU2 processing.

______________ 600.29 1 - [Default: A06HPS1]

Specify the name of the first VTAM APPLID.

______________ 600.30 2 - [Default: A06HPS2]

Specify the name of the second VTAM APPLID.

______________ 600.31 3 - [Default: A06HPS3]

Specify the name of the third VTAM APPLID.

Planning and Installing AppBuilder for the Mainframe J-3


______________ 600.32 Define HPS transactions during rule prepare? (Y/N) - [Default: Y]

Enter the default value to define AppBuilder transactions during rule prepare.

______________ 600.33 Should the HPS databases be processed? (Y/N) - [Default: Y]

If you want the AppBuilder databases to be processed (used to populate RuleView), enter Y. If not, enter N.

______________ 600.34 Should the HPS transaction UTBL0000 be executed? - [Default: Y]

If you want the HPS transaction UTBL0000 to be executed, enter Y. If not, enter N.

J4 IMS Online Preparation Workbench and Enterprise Server Customization Worksheets

Index

INDEX


Symbols@SERVER INI

example 5-53

Numerics3270 Converse 1-163270 session 2-6

AABCGAP D-1ABINI variables

initialization variables A-1Americas ServiceLine 1-10AppBuilder Software Format Library 9-12Application Control Block Generation 9-12APPLID 2-6architecture

evaluation 1-2system outlook plan 1-3

Bbatch DB2 and non-DB2 rules

JCL D-10Batch DB2 JCL D-10Batch JCL (non-DB2) D-12Batch Preparation Workbench 6-2budget planning 1-4business analyst 1-8

CChanges to Control Region JCL 9-28checklists

hardware and software E-1

CICSCEDA 2-7CEMT 2-7destination control table 2-7enterprise server software 8-2Global Parameters Table D-1Load Libraries 8-38Programs 8-39routing service requests 8-34sample JCL file D-9security 2-3table definitions B-1terminal control table 2-7Terminals 8-39Transactions 8-38Transient Data Queues 8-38USSTAB entry 2-6VSAM Files 8-38

CICS Online Preparation Workbench 8-2CICS Socket interface

defining the listener transaction 8-32Configuration Record Fields 8-32contact 1-10cost estimates 1-4CRSRVJCL Execution 5-49

DDASD

space 1-12DASD Requirements E-2data management team 1-9data modeling 1-11data set naming conventions 1-12database administrator 1-9Database DBRC Definition 9-25Database Dynamic Allocation Definition 9-25DB2

Plan owner 5-29, G-11SPUFI 2-5system catalog tables 2-6VCAT or Storage Group 5-29, G-12

DB2 rules D-10

Planning and Installing AppBuilder for the Mainframe 1

DBD Generation 9-11DDE 1-5destination control table

CICS requirements 2-7development methodology 1-6development personnel 1-8development support technician 1-10development team 1-6DFHDCT 2-7DFHTCT 2-7DFSCMTR0 Terminal Routing Exit 9-26DNAINI Settings 8-35DNALSTNR

defining to the CICS region 8-32DoS Prevention 8-37

EEMEA Support Line 1-10end user

involvement 1-4, 1-6training 1-4

Enterprise Preparation Server 5-51enterprise repository 1-13, 1-15, 2-1enterprise-wide model 1-6

FFSI data model 1-6

HHardware Requirements E-1HMPBTBLI

IMS setup 9-28use of in IMS 9-28

Host Batch JCL D-10HPEUCGP D-1

in IMS 9-29HPICGAP D-1

IMS D-13in IMS 9-29

HPSBASE 2-6HPSTIP 2-6

Iimplementation plan 1-3IMS

cold start 9-30enterprise server 9-2sample JCL file D-17

IMS Online Preparation 9-2IMS Security Generation 9-27IMS Stage 1 Input 9-26

installationcomponents 1-2date 1-12installer ID authority 2-6minimum installer ID access 2-6overview 1-1, 1-12requirements 1-12

Installation Tableselecting for CICS 8-15selecting for IMS 9-16

Installation Verification Using TIPCICS 8-29IMS 9-30

LListener

starting 8-34listener transaction

defining 8-32load module tables D-1LOGMODE 2-6LU2 2-3

Mmainframe batch reporting 1-5Mainframe codepage 5-30, G-12management involvement 1-6Method Handler JCL

executing CRRPJCL 5-53methodology 1-11Migration Server 5-48modifications 1-11Multi-CICS Region 8-37

Nnaming conventions

DASD cleanup 2-3short-term qualifier 2-3

NetEssentialCICS 8-31configuring runtime options 8-33Middleware for IMS 9-29Tracing 8-37

non-DB2 rules D-10NPT 1-16

Oobjectives 1-3office space 1-4overview

installation 1-1

2

Ppersonal repository 1-13, 2-1personnel

data management 1-9development 1-6, 1-8production 1-8, 1-10quality assurance (QA) 1-8

pilot project 1-5platforms 1-4Postinstallation Notes

CICS 8-27, 8-30IMS 9-25, 9-32

preinstallationarchitecture evaluation 1-2checklists 1-12requirements 1-12

prerequisites 1-12production support team 1-10Program Specification Block Generation 9-12program temporary fixes 1-11programmer/analysts 1-7programmers 1-7project leader 1-6project planning 1-11Protocycling and Technical Construction phases 1-10

QQA analyst 1-9QA manager 1-9quality assurance team 1-8

Rreleases 1-11Report Writer Preparation 7-2reporting problems 1-11Repository

adding 5-52repository

applying for CICS 8-15repository administrator 1-10Repository ID 5-29, 5-30, G-12repository manager 1-9repository model manager 1-9resource 1-3resource scheduling 1-6

Sschedules 1-3security

administrator data set permissions 2-4CEDA 2-7CEMT 2-7CICS 2-3user data set permissions 2-4

Security Authenticationfor listener security 8-35

Serverstarting 5-52

Server Repository @SERVER INI 5-52ServiceLine 1-10Session Termination Semantics 8-35short-term qualifier 2-3software requirements

for TCP/IP Listener 8-31sponsor 1-5SPUFI 2-5staffing 1-3standards and conventions 1-6Storage Group 2-6, 5-29, G-12Superprepare

IMS 9-30SYSADM 2-6system architect 1-7

TTCP/IP Listener Abend Handler 8-36TCP/IP Listener for IBM CICS

installing 8-31TCP/IP Port Number 8-35terminal control table

VTAM requirements 2-7Terminal Input 9-26third-generation languages 1-4Third-party Products

support E-2third-party software 1-5TIP Verification

IMS 9-31tools 1-6training

organizational 1-4transition 1-1TSO

USSTAB entry 2-6

Index 3

UUser Applications

requirements 9-27user commitment 1-6user ID 1-12user interfaces 1-8USSTAB entry 2-6

Vvariables

INI A-1VCAT 2-6, 5-29, G-12Versions 5-30, G-12VTAM

APPLID 2-6, 2-7LOGMODE 2-6, 2-7preinstallation requirements 2-7system changes 2-6USSTAB entry 2-6

VTAM definitionsCICS and IMS C-1

Wworksheet

batch preparation workbench H-1CICS online preparation workbench I-1enterprise repository installation G-1enterprise server for IMS J-1enterprise server installation I-1IMS online preparation workbench J-1installation workbench F-1

Workstation codepage 5-30, G-12

4

Documents

App Builder Host Pi