sg245440

Installin g BaanERP Applications on OS/390

Kathryn Arrell , Lou Doran, Nicholas Rodoflich, Lee Siegmund, Jeff Wiese

International Technical Support Organization

http://www.redbooks.ibm.com

SG24-5440-00

International Technical Support Organization

Installing BaanERP Applications on OS/390

August 1999

SG24-5440-00

Take Note!

Before using this information and the product it supports, be sure to read the general information inAppendix L, “Special Notices” on page 177.

First Edition (August 1999)

This edition applies to BaanERP Applications with DB2 V5.1 for use with the OS/390 V2R6.

Comments may be addressed to:IBM Corporation, International Technical Support OrganizationDept. HYJ Mail Station P099522 South RoadPoughkeepsie, New York 12601-5400

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1999. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure issubject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiThe Team That Wrote This Redbook . . . . . . . . . . . . . . . . . . . . . . . . . xiComments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1. Architecture Overview of BaanERP Applications on OS/390 . . . . 11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Presentation Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Database Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.3.1 Baan Database Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.4 Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.4.1 The Baan Software Environment (BSE) . . . . . . . . . . . . . . . . . . 51.5 Baan Applications That Run on S/390 . . . . . . . . . . . . . . . . . . . . . . 61.6 Baan Application Structure - the Company Story . . . . . . . . . . . . . . . 71.7 Baan Software Alliances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.8 Dynamic Enterprise Modeling (DEM) . . . . . . . . . . . . . . . . . . . . . . 81.9 OS/390 UNIX System Services Connection Scaling Kit . . . . . . . . . . . . 8

1.9.1 Connection Manager (CM) . . . . . . . . . . . . . . . . . . . . . . . . . . 91.9.2 Process Manager (PM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.10 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.11 Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.12 OS/390 Features for Baan Applications . . . . . . . . . . . . . . . . . . . . 111.13 DB2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.14 Strengths of RVA and SnapShot for Baan Applications for OS/390 . . . . 13

Chapter 2. Installation Overview - Preparing for the Installation . . . . . . . . 152.1 BaanERP Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1.1 Preparing the Environment . . . . . . . . . . . . . . . . . . . . . . . . . 162.1.2 Set Up the TSO User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1.3 DASD Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1.4 Client Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.1.5 Customizing DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.1.6 Customizing CM and PM . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.1.7 Setting Up To Load the BaanERP Software from CD-ROM . . . . . . . 182.1.8 UNIX System Services File Structures . . . . . . . . . . . . . . . . . . . 18

2.2 Keeping Track of Names Used . . . . . . . . . . . . . . . . . . . . . . . . . . 182.3 Disk Space Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.4 BaanERP for OS/390 Release Notes . . . . . . . . . . . . . . . . . . . . . . 20

2.4.1 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.4.2 Post Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3. DB2 and BaanERP Applications on OS/390 . . . . . . . . . . . . . . 233.1 Set Up DB2 Databases and Tablespaces . . . . . . . . . . . . . . . . . . . . 233.2 DB2 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2.1 JCL Used to Create Tablespaces . . . . . . . . . . . . . . . . . . . . . . 293.2.2 Binding the Plan That BaanERP Uses . . . . . . . . . . . . . . . . . . . 313.2.3 DB2 Files BaanERP Uses . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.3 Points to Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Copyright IBM Corp. 1999 iii

Chapter 4. Enabling UNIX System Services . . . . . . . . . . . . . . . . . . . . . 334.1 Customizing Connection Manager (CM) . . . . . . . . . . . . . . . . . . . . 334.2 JCL Used to BIND the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.3 Set Environment Variables for CM and PM ger . . . . . . . 34

4.3.1 Set Environment Variables for OS/390 Connection Scaling Kit . . . . 354.4 Using a Second CMXPLAN Name . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 5. BaanERP Applications Installation . . . . . . . . . . . . . . . . . . . 375.1 Allocation of the HFS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.2 Creating the Mount Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.2.2 Mounting the HFS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.3 Unloading the Baan Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.3.1 Setting Up to Load the Baan Software from the CD-ROM . . . . . . . 405.3.2 Unpacking Files into Install Directories . . . . . . . . . . . . . . . . . . 41

5.4 Set Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.4.1 Set Environment Variables - OS/390 Connection Scaling Kit . . . . . 425.4.2 Set Environment Variables - Installation of Baan Applications . . . . 42

5.5 Executing the install6.2 Script . . . . . . . . . . . . . . . . . . . . . . . . . . 435.5.1 Answering the Questions in the install6.2 Script . . . . . . . . . . . . . 445.5.2 Using the db2install6.2 Script . . . . . . . . . . . . . . . . . . . . . . . . 495.5.3 Listing Environment Variables . . . . . . . . . . . . . . . . . . . . . . . 515.5.4 Storage Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.5.5 Creating DB2 Reference Files for the Baan Script . . . . . . . . . . . . 525.5.6 Continuing with the install6.2 Script . . . . . . . . . . . . . . . . . . . . 545.5.7 Changes before Continuing . . . . . . . . . . . . . . . . . . . . . . . . . 555.5.8 Configure the BW Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.5.9 Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . 60

5.6 Setting Up the Profile for bsp User ID . . . . . . . . . . . . . . . . . . . . . . 625.7 Starting the Baan Application Manually . . . . . . . . . . . . . . . . . . . . 62

Chapter 6. Client Connection Configurations . . . . . . . . . . . . . . . . . . . . 656.1 Setting Up the BW Baan Client Code on a Windows 95 Client . . . . . . . 65

6.1.1 Getting the Baan Client from the FTP Site . . . . . . . . . . . . . . . . 666.2 Configuring the Baan Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 676.3 Connecting as bsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 7. Install the bi Client and Set Up the Webserver on S/390 . . . . . . 717.1 Set Up a S/390 WebServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717.2 Set Up the BI HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

7.2.1 Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727.2.2 HTTP Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 727.2.3 HTTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 777.2.4 Starting the BI HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.3 Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797.3.1 Using Netscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.4 Starting the Webserver and Baan Internet Client . . . . . . . . . . . . . . . 807.5 Started Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.5.1 Started Procedure for BI HTTP Server . . . . . . . . . . . . . . . . . . . 807.5.2 Started Procedure for Webserver . . . . . . . . . . . . . . . . . . . . . 81

Chapter 8. Cloning/Customizing the HTTP Server for OS/390 . . . . . . . . . . 838.1 Setting Up Server Configuration Files . . . . . . . . . . . . . . . . . . . . . . 838.2 Setting Up a Single Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

8.2.1 Basic Single Server Configuration . . . . . . . . . . . . . . . . . . . . . 848.2.2 Locating Your Web Content . . . . . . . . . . . . . . . . . . . . . . . . . 86

iv Installing BaanERP Applications on OS/390

8.2.3 Customizing Your Web Server . . . . . . . . . . . . . . . . . . . . . . . 888.2.4 Create a Default Home Page for Your Web Server . . . . . . . . . . . 908.2.5 Create/Update a Started Procedure for Your Web Server . . . . . . . 90

Chapter 9. Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 919.1 JCL to Create Company 813 . . . . . . . . . . . . . . . . . . . . . . . . . . . 919.2 JCL to Create Company 900 . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

9.2.1 db2_storage file for Companies 813 and 900 . . . . . . . . . . . . . . . 92

Chapter 10. Enabling Process Man ager on UNIX System Services . . . . . . . 9310.1 Process Manager (PM) Installation . . . . . . . . . . . . . . . . . . . . . . 9310.2 Customizing the Process Manager . . . . . . . . . . . . . . . . . . . . . . . 93

10.2.1 Process Manager Parameters . . . . . . . . . . . . . . . . . . . . . . . 9410.2.2 Starting and Stopping the Process Manager . . . . . . . . . . . . . . 97

Chapter 11. Administration of DB2 for Baan Applications on OS/390 . . . . . 9911.1 DB2/BaanERP Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

11.1.1 DB2/BaanERP Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . 9911.1.2 DB2/BaanERP User-Written Queries . . . . . . . . . . . . . . . . . . . 9911.1.3 Baan's Use of SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

11.2 DB2/BaanERP Operational Observations . . . . . . . . . . . . . . . . . . 10011.3 DB2/BaanERP Database and Table Space Recommendations . . . . . 10011.4 DB2/BaanERP DSNZPARM Recommendation . . . . . . . . . . . . . . . 10111.5 DB2/BaanERP Buffer Pool, Free Space, and Space Allocation . . . . . 102

11.5.1 DB2/BaanERP Buffer Pool Recommendations . . . . . . . . . . . . 10211.5.2 DB2/BaanERP Free Space Recommendations . . . . . . . . . . . . 10311.5.3 DB2/BaanERP Primary/Secondary Allocations . . . . . . . . . . . . 104

11.6 DB2/BaanERP Reorganization and Runstats Recommendations . . . . 10411.7 DB2/BaanERP Index Usage . . . . . . . . . . . . . . . . . . . . . . . . . . 10511.8 DB2/BaanERP Point-in-Time Recovery Recommendations . . . . . . . 106

11.8.1 Point-in-Time Recovery Preventive Measures . . . . . . . . . . . . 10611.8.2 Point-in-Time Recovery Techniques . . . . . . . . . . . . . . . . . . 10611.8.3 Point-in-Time Recovery Recommendations . . . . . . . . . . . . . . 108

Appendix A. BPX Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Appendix B. The vi Editor and Common UNIX Commands . . . . . . . . . . 115B.1 Using the vi Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115B.2 Common UNIX Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Appendix C. The hostname Command . . . . . . . . . . . . . . . . . . . . . . 119C.1 Using the hostname Command . . . . . . . . . . . . . . . . . . . . . . . . 119

C.1.1 Source Code for the hostname Command . . . . . . . . . . . . . . . 119

Appendix D. Executing the db2_install6.2 Script . . . . . . . . . . . . . . . . . 121D.1.1 Listing Environment Variables . . . . . . . . . . . . . . . . . . . . . . 122D.1.2 Storage Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . 123D.1.3 Database Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123D.1.4 Tablespace Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124D.1.5 Creating DB2 Reference Files for Baan Script . . . . . . . . . . . . . 126D.1.6 Files Baan Will Use to Define the Database . . . . . . . . . . . . . . 128D.1.7 Adding More Users and Data Later . . . . . . . . . . . . . . . . . . . 129

Appendix E. RAMAC Virtual Array (RVA) . . . . . . . . . . . . . . . . . . . . . 131E.1 Overview of RAMAC Virtual Array . . . . . . . . . . . . . . . . . . . . . . . 131

Contents v

E.2 Log Structured File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131E.3 Data Compression and Compaction . . . . . . . . . . . . . . . . . . . . . . 132

E.3.1 Effect of Data Compression . . . . . . . . . . . . . . . . . . . . . . . . 133

Appendix F. SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135F.1 How SnapShot Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135F.2 What Is Virtual Concurrent Copy . . . . . . . . . . . . . . . . . . . . . . . . 136

F.2.1 DFSMSdss SnapShot . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136F.2.2 Virtual Concurrent Copy . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Appendix G. Installation Problems We Encountered . . . . . . . . . . . . . . 139G.1 Problems and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . 139G.2 Restarting after Encountering Problems . . . . . . . . . . . . . . . . . . . 141

G.2.1 Restarting the install6.2 Script . . . . . . . . . . . . . . . . . . . . . . 142G.2.2 Restarting install6.2 from the Beginning . . . . . . . . . . . . . . . . 144

G.3 Using Baan Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Appendix H. Alternate DB2 Layout . . . . . . . . . . . . . . . . . . . . . . . . . 149H.1 JCL Used to Create Tablespaces . . . . . . . . . . . . . . . . . . . . . . . 149H.2 DB2 Files BaanERP Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Appendix I. Set the Environment Variables for Baan . . . . . . . . . . . . . . 161I.1.1 Setting Environment Variables for OS/390 Connection Scaling Kit . 161I.1.2 Set Environment Variables-Installation of Baan Applications . . . . 162

I.2 Setting Up the Profile for the bsp User ID . . . . . . . . . . . . . . . . . . . 163I.3 Restarting the install6.2 Script . . . . . . . . . . . . . . . . . . . . . . . . . 164I.4 Default Profile Before Starting the install6.2 Script . . . . . . . . . . . . . 164

Appendix J. Using UNIX System Services for UNIX-Trained Baan Specialist 169J.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169J.2 Interface Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Appendix K. DDF Customization . . . . . . . . . . . . . . . . . . . . . . . . . . 173K.1 Installing and Customizing DRDA . . . . . . . . . . . . . . . . . . . . . . . 173

Appendix L. Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Appendix M. Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . 179M.1 International Technical Support Organization Publications . . . . . . . 179M.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179M.3 Other IBM Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179M.4 Baan Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180M.5 Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

How to Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181IBM Redbook Fax Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

ITSO Redbook Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

vi Installing BaanERP Applications on OS/390

Figures

1. BaanERP architecture for OS/390 . . . . . . . . . . . . . . . . . . . . . . . 22. Baan's Logical Three-Tier Architecture . . . . . . . . . . . . . . . . . . . . 23. Baan Application Environment . . . . . . . . . . . . . . . . . . . . . . . . . 54. Connection Manager and Process Manager . . . . . . . . . . . . . . . . . 95. User IDs in Uppercase and Lowercase . . . . . . . . . . . . . . . . . . . . 176. DB2 Parameters Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247. JCL to Create Tablespaces with Company 000, Detailed Setup . . . . . 308. Simple db2_storage File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329. Customizing the Connection Manager . . . . . . . . . . . . . . . . . . . . 33

10. JCL to BIND the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3411. Allocation HFS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3812. Mount Production HFS File . . . . . . . . . . . . . . . . . . . . . . . . . . . 3913. Mount Installation HFS File . . . . . . . . . . . . . . . . . . . . . . . . . . . 4014. Mount Storage HFS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4015. Package Combinations to Create . . . . . . . . . . . . . . . . . . . . . . . 4816. BaanERP Configuration Panel . . . . . . . . . . . . . . . . . . . . . . . . . 5617. Baan Logon Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5618. Baan Initialization Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5719. Importing Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5720. Creating New Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5821. Starting Baan Module ottadv5211 . . . . . . . . . . . . . . . . . . . . . . . 5822. Creating Table Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5923. Message about User ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . 5924. Message about User BSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5925. Installation Has Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . 6026. Baan Message to Return to Window . . . . . . . . . . . . . . . . . . . . . 6027. Environment Variables for bsp User . . . . . . . . . . . . . . . . . . . . . . 6228. Starting the Baan Applications Manually . . . . . . . . . . . . . . . . . . . 6329. Successful Installation of Baan Client . . . . . . . . . . . . . . . . . . . . . 6630. Baan Environment and Configuration Selector Window . . . . . . . . . . 6731. Configuring the Baan Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 6832. Connecting to the Baan Client . . . . . . . . . . . . . . . . . . . . . . . . . 6933. Client Connection Completed to Baan . . . . . . . . . . . . . . . . . . . . 6934. Graphical Window Displayed while Setting Up BI HTTP Server . . . . . . 7435. Instructions for Sett Up of BI HTTP Server . . . . . . . . . . . . . . . . . . 7536. Location for BI HTTP Server Program . . . . . . . . . . . . . . . . . . . . . 7537. Completion of Setting Up BI HTTP Server . . . . . . . . . . . . . . . . . . 7638. Changing the bi.html File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7839. Choice of Microsoft SDK for APF 10 . . . . . . . . . . . . . . . . . . . . . . 7940. Web Server Administration Protection Directives . . . . . . . . . . . . . . 8541. SSL Directives in IBM-Supplied Configuration File (httpd.conf) . . . . . . 8542. Standard Web Content Setup Directives . . . . . . . . . . . . . . . . . . . 8643. HTML Example - frntpage.html . . . . . . . . . . . . . . . . . . . . . . . . . 8744. Single Server - Logging and Reporting Changes to httpd.conf . . . . . . 8945. Single Server - Modified Web Content Setup Directives . . . . . . . . . . 8946. Single Server - HTML Example for a Home Page (index.html) . . . . . . 9047. db2_storage File for Companies 813 and 900 . . . . . . . . . . . . . . . . 9248. Adding Port Number to /windows/services . . . . . . . . . . . . . . . . . . 9349. Adding the IP Address to /bpares.cfg . . . . . . . . . . . . . . . . . . . . . 9450. Parameters for Process Manager . . . . . . . . . . . . . . . . . . . . . . . 9551. Virtual Disk Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Copyright IBM Corp. 1999 vii

52. SnapShot Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13553. Virtual Concurrent Copy Operation . . . . . . . . . . . . . . . . . . . . . 13754. Result of ipcs Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14255. Dropping the DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . 14656. Baan Llogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14657. JCL to Create Tablespaces with Company 000 Detailed Setup . . . . . 15058. Sample db2_storage File . . . . . . . . . . . . . . . . . . . . . . . . . . . 15859. Environment Variables for bsp User . . . . . . . . . . . . . . . . . . . . . 16460. Profile in /etc/profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16561. Accessing S/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17062. DDF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17363. APPL Entries in SYS1.LOCAL.VTAMLST . . . . . . . . . . . . . . . . . . 17464. PORT Definitions for DRDA . . . . . . . . . . . . . . . . . . . . . . . . . . 175

viii Installing BaanERP Applications on OS/390

Tables

1. Names Used in the BaanERP Installation . . . . . . . . . . . . . . . . . . . 182. Disk Space Required for BaanERP . . . . . . . . . . . . . . . . . . . . . . . 19

Copyright IBM Corp. 1999 ix

x Installing BaanERP Applications on OS/390

Preface

This redbook is based on the installation experiences gained while installingBaanERP Applications with DB2 V5.1 for use with OS/390 V2R6 at the ITSO inPoughkeepsie. This redbook will help you install and customize BaanERPApplications for OS/390 with DB2. It is based on using the CD-ROM from theApril 1999 release of the BaanERP Applications for S/390.

It contains an introduction to the architecture of the BaanERP Applications forOS/390 Solution. It also describes the customization needed for OS/390 and DB2V5.1 and the BaanERP installation process to install the applications and to setup Company 000 and the demo companies. It includes guidelines for setting upand administering DB2 for BaanERP.

We recommend that BaanERP Applications be installed by a person trained inperforming such installations. This redbook is not meant to replace having atrained consultant to do the installation. Instead, it provides S/390 SystemProgrammers with detailed information about the installation process,particularly how it relates to OS/390.

The Team That Wrote This RedbookThis redbook was produced by a team of specialists from around the worldworking at the International Technical Support Organization PoughkeepsieCenter.

Kathryn Arrell is an ERP Specialist with the International Technical SupportOrganization, Poughkeepsie Center. Before joining ITSO, Kathryn worked inRS/6000 Marketing for IBM Canada.

Lou Doran is an ERP Solutions Specialist with the North American ERPCompetency Center in Philadelphia. Before joining the ERP Group, Lou workedin Network Marketing and has a large systems background.

Nicholas Rodoflich is a consultant with the IBM Global Services ERP NationalPractice specializing in IT Infrastructure for ERP and engineering applications.He has over ten years of experience with UNIX, networking and RDBMSadministration on various platforms including RS/6000, SUN, and HP. He holds aBS degree in Computer Science and Telecommunications Engineering from theUniversity of Mississippi.

Lee Siegmund is a Consulting Marketing Support Representative from the DB2Relational Support Unit of the Dallas Systems Center. He has worked at IBM for29 years. For the past 15 years, he has supported DB2 starting with Version 1Release 1 to the current Version 5. His areas of expertise include highavailability, recovery, data sharing, and application design. He has presentedDB2 availability topics to user groups around the world.

Jeff Wiese is a Market Support Representative in the US. He joined IBM in 1973and was a PSR, Instructor, SE, and Large Systems Marketing Specialist beforejoining the S/390 New Technology Center in Poughkeepsie, New York.

Thanks to the following people for their invaluable contributions to this project:

Copyright IBM Corp. 1999 xi

Paolo BruniAlison PateInternational Technical Support Organization, San Jose Center

Richard ConwayBob HaimowitzVasilis KarrasElla BuslovichInternational Technical Support Organization, Poughkeepsie Center

Erik de JeuIBM Baan International Competency Center

Vicky PollienSteve HenkelsRichard KoBrad ForrestMythili VenkatakrishnanIBM S/390 Division, Poughkeepsie

Yvon-Marie AvrilHerve SabrieJean-Jacques NogueraLaurence NicolasIBM Parallel Solution Support Center, Montpellier

Jos OdijkRenze KlammerBaan

Val ChavezFrank SnyderChris SutterLawson Products, USA

Comments WelcomeYour comments are important to us!

We want our redbooks to be as helpful as possible. Please send us yourcomments about this or other redbooks in one of the following ways:

Fax the evaluation form found in “ITSO Redbook Evaluation” on page 187 tothe fax number shown on the form.

Use the online evaluation form found at http://www.redbooks.ibm.com/

Send your comments in an Internet note to [email protected]

xii Installing BaanERP Applications on OS/390

Chapter 1. Architecture Overview of BaanERP Applications onOS/390

This chapter introduces the architecture of the BaanERP Enterprise ResourcePlanning (ERP) solution for the S/390 as implemented at the ITSO for its“installation experience” documented in this redbook. BaanERP was formerlyknown as Baan V.

1.1 IntroductionERP solutions have gained market share and mind share as an enterprisesolution to both business problems, such as reengineering business processes,and technical problems, such as the Year 2000 problem. ERP solutions provide“run your business” information technology for enterprises that have chosen topurchase solutions rather than develop them. As the ERP industry is maturing,these solutions are becoming the foundation for organizations expanding their“front office” solutions, such as supply chain management and customerrelationship management, as well as integrating into e-business and BusinessIntelligence/Data Warehousing.

Baan is a major ERP solution provider, and S/390 is the industrial strengthcomputing platform that can complement such an ERP. BaanERP, for S/390,became available in 2Q/99.

BaanERP is part of the Baan Series Product. BaanERP applications include:

ManufacturingFinanceProjectDistributionService

BaanERP for the S/390 is implemented using “Baan's Client/Server” mode, thatis, all functions are usually implemented on two hardware platforms. Theapplication layer and the database layer reside on the S/390 Server as shown inFigure 1 on page 2.

Copyright IBM Corp. 1999 1

Figure 1. BaanERP architecture for OS/390. The network connection can be Token-Ring,Ethernet, Fast Ethernet, FDDI, Escon or ATM.

Note that while the term “host” has historically been used to describe themainframes (for example, the S/390), you should not confuse this with Baan'sterm “Host Mode” where all components of the three layers (including thepresentation or client layer) reside on one machine.

Logically, it is a three-tier mode from a functional point of view as shown inFigure 2.

______________ _____________ _____________| | | | | || | | | | || Presentation |____| Application |____| Database || Layer | | Layer | | Layer || | | | | ||______________| |_____________| |_____________|

Figure 2. Baan's Logical Three-Tier Architecture

1.2 Presentation LayerThe presentation layer (client) contains the display driver, which is the userinterface to the system. BaanERP, under OS/390, provides two client interfaces,Microsoft Windows (BW), and an Internet Client (BI) that is, a Web Client. TheASCII Client (BA), available on Baan IV, is no longer supported, except for use inthe part on the initial install (until enough function is enabled to support the BWClient). The Xwindows client (bx) is not supported for OS/390. Note that the twoletters in parenthesis are Baan's terms for the particular client.

Like Baan IV, data flows from the client to the application layer at the field level.As each field on the screen is completed (the user tabs to the next field), thedata for that field is sent to the application server. When the final field isreceived, the majority of the business logic is triggered. In addition to this

2 Installing BaanERP Applications on OS/390

“normal” mode, BaanERP provides for an “expert” mode, which waits until allappropriate fields are filled in and then sends the entire screen. This optionreduces network load at the cost of field-by-field verification.

The BI Client uses a Java-capable browser. Both Netscape and InternetExplorer, at the appropriate release levels, with the appropriate Java Classlibraries, can be used. There is no special Web server required, and the BaanInternet HTTP Server can reside on UNIX, NT, or S/390 as well.

1.3 Database LayerThe database layer uses a relational database to support all the online usersand batch processes that are part of the BaanERP applications.

The Relational Database Management System (RDBMS) used for Baan, whenimplemented on S/390, is DB2 V5. Baan does not support any other RDBMS onS/390. The S/390 and DB2 combine to make an ideal database server. For moreinformation on the DB2 features available for Baan applications see 1.13, “DB2Features” on page 12.

DB2 tables can store data in either ASCII or EBCDIC. Baan applications have anASCII bias, that is to say, the applications operate on data presuming ASCII.Unlike the prior release of Baan, Baan's HFS files are in EBCDIC, the nativestate of S/390. This change was made (Baan IVc's HFS files were in ASCII) toeliminate some problems of mixing EBCDIC and ASCII in the same file, andsince utilization of this data is low, the ASCII to EBCDIC conversions, whennecessary, are minimal. The operations on the data from DB2, however, isextensive, hence Baan recommends storing DB2 data in ASCII, to eliminate themore significant amount of EBCDIC-to-ASCII translation overhead.

You may have other DB2 applications that store data in EBCDIC. Although youcan store both ASCII and EDCDIC data in the same DB2 subsystem, it is notrecommended for Baan. In fact, because of database recovery reasons that arecovered in Chapter 11, “Administration of DB2 for Baan Applications on OS/390”on page 99, the recommendation is to give Baan its own DB2 subsystem.

Note: Mixing or joining of ASCII and EBCDIC tables in one SQL statement is notallowed, so if you need to join both types of data (due to some customapplication), you need to convert the format of one of the tables.

1.3.1 Baan Database DriversBaan provides database drivers to facilitate its open platform architecture. Onthe S/390, Baan's database driver acts as an interface between the applicationand DB2. The application being executed sends database requests to thedatabase driver, which transfers the request to the DB2. Data returned by DB2is sent back to the application by the driver.

There are two types of drivers, level 1 and level 2. The driver that composessingle table queries is called the level 1 driver.

In this architecture, the Baan SQL is transformed into a single table selectstatement and if a join on rows is necessary, the join is performed by the driver.This technique is very efficient for online usage, but can create a lot of trafficbetween the database and application servers.

Chapter 1. Architecture Overview of BaanERP Applications on OS/390 3

The level 2 driver does not transform Baan SQL and relies on the RDBMS toperform any table joins. The resulting rows returned by the RDBMS are simplypassed on to the application. The primary purpose of the level 2 driver (versusthe level 1 driver) is to reduce data traffic between database and applicationservers.

Driver usage is of no consequence to the end user, but understanding thisarchitecture may be important for administrators. Currently, only the level 1driver is implemented in the S/390 - DB2 solution for BaanERP. A S/390 DB2level 2 driver is planned for late 1999. The design of level 2 drivers facilitatesaccess through a more direct means, such as DB2 Connect, as special hashingindices and all their associated aspects are eliminated.

1.4 Application LayerThe application layer provides the logic that manages all of the BaanERPprocesses.

The application tier has been ported to the UNIX System Services of OS/390, andthus resides on the same platform as the database. This eliminates the need fora network connection between the application layer and database layer tiers(typical of other ERP solutions), and the movement of data between applicationlayer and RDBMS (DB2) becomes a memory-to-memory move.

There is a subset of programs on the application layer commonly known as theporting set. This subset interfaces directly with the operating system; that is, itis the hardware-dependent code. It is kept separate from the“hardware-independent code” that contains of all the BaanERP applicationobjects: menus, reports, screens, database object definitions, referential integrityrules and so on. This is the way Baan implements open architecture, andprovides a consistent end-user view, regardless of hardware platform andRDBMS.

As shown in Figure 3 on page 5, part of the porting set is Baan's bshell, whichis the logic interface between the Baan software (applications) and the platformoperating system (OS/390 UNIX System Services for OS/390). The logic server(bshell) controls the application process. The application code (objects) iswritten in Baan 4GL.


Figure 3. Baan Application Environment. IPC is the interprocess communication.

1.4.1 The Baan Software Environment (BSE)The BSE refers to the HFS files that contain the Baan application code.

After our installation, the following directories were in the BaanERP SoftwareEnvironment (BSE) in our directory /baanerp/bse:

/baanerp/bse/BaanOle/baanerp/bse/additional_files/baanerp/bse/api/baanerp/bse/application/baanerp/bse/bin/baanerp/bse/c_plus/baanerp/bse/doc/baanerp/bse/eme/baanerp/bse/etc/baanerp/bse/gif/baanerp/bse/home/baanerp/bse/includes6.2/baanerp/bse/install/baanerp/bse/integration/baanerp/bse/internet/baanerp/bse/lib/baanerp/bse/log/baanerp/bse/mswindows/baanerp/bse/ps/baanerp/bse/sec/baanerp/bse/tmp/baanerp/bse/tools/baanerp/audit/baanerp/dict


/baanerp/tables/baanerp/test

1.5 Baan Applications That Run on S/390The Baan applications that run on OS/390 are:

ManufacturingProjectFinanceServiceDistribution

You will see the following abbreviations for the Baan applications packages. TheBaan product was formerly called Triton, which is the reason for the t in theabbreviation.

tc Common

td Distribution-part of Order Mgmt and Warehousing

tf Finance

tg Orgware

ti Manufacturing

tp Project

ts Services

tt Tools

tu Utilities - found under Connectivity and Exchange

bc Conversion

cf Configuration - new for BaanERP

ci Central Invoicing - new for BaanERP

cp Constraint Planning - found under Enterprise Planning

dc Development Control - new for BaanERP

ec Electronic Commerce - new for BaanERP

ed Enterprise Model Data - new for BaanERP

qm Quality Management - new for BaanERP

wh Warehousing - new for BaanERP

Note: The Baan Transportation and Process modules from BaanIV are notincluded in BaanERP.

Other common abbreviations and terms used by Baan are:

aad Application Administration (part of Tools).

adv Application Development (part of Tools).

iex Import/Export (part of Tools).

ba Baan ASCII Client.

bi Baan Internet (Web) Client.

BW Baan Windows Client.


BX Baan X-Windows Client.

BSE Baan Software Environment.

bshell A virtual machine; there is one for every user. It is theconnection between the user and the Baan application andthe connection between the application and the database.It is where the application code runs.

Company Combination of package and tables.

Form The Baan data entry interface.

Localization Customer-specific information such as language currencyand so on.

Menu The Baan user interface.

Module A set of related software components.

Object The runtime object created by program and report scriptsand executed by the BShell.

Package A series of related modules.

Report Output from Baan sessions.

Session The action being performed.

Software Component Menus, sessions, forms, and so on.

Table Baan data storage.

vrc Version Release customer extension. This is a packageset of Baan modules and data definitions.

1.6 Baan Application Structure - the Company StoryBaan organizes tables into companies. Each company is a self-contained set oftables that are independent of each other. Baan Tools are used to definecompanies.

For Baan, a company is denoted by a three-digit number. Note that company000 is a special Baan company. It corresponds to a set of tables that store all ofthe data that is part of the Baan Data Dictionary, including applicationconfiguration, user definition and privileges, programs, reports, applicationlocking and other run-time data. Database tables that are part of Company 000are accessed by the application programs in the Baan Tools package. There areabout 380 tables and 1100 indexes in Company 000.

Important

Note that every other company will access Company 000.

In addition to Company 000, there are demo companies such as Company 813and Company 900. New companies will be created for production use based onhow you want to organize your environment. For example, you might have:

Company 100 for your manufacturing production usersCompany 110 for your manufacturing test usersCompany 200 for your finance production usersCompany 210 for your finance test users


The company numbers are the user's choice. These other companies generallyhave about 2700+ tables and 9000+ indexes, depending on the number ofinstalled modules.

A end user attaches to a company, which is a combination of a package andversions of database tables.

1.7 Baan Software AlliancesBaan's software alliances bring added openness, robustness and flexibility toBaan's software solutions and give Baan customers a high level ofinteroperability with complementary software applications. Baan works with itsalliances from an engineering standpoint to ensure that the resulting productsare well integrated by offering increased levels of connectivity within the Baansoftware environment, generic APIs, Business Object Interfaces (BOIs), datadictionary interfaces, a data exchange module, and distributed data.

A list of Baan Software Alliance Partners can be found on the Baan Web page:

http://www.baan.com

Some are porting their applications to S/390; some are able to integrate to BaanApplications independent of the database and application server platform.

1.8 Dynamic Enterprise Modeling (DEM)In order to improve the time and speed to implement, Baan uses the concept ofDynamic Enterprise Modeling (DEM). Dynamic Enterprise Modeling is based onthe definition of generic business models for certain organization topologies.These business models (modeling organization topologies) are not rigid, and canbe adapted to specific requirements and future changes. Baan refers to thesebusiness models as reference models..

The technology implementation (hardware and software) is a relative ly smallpart of an ERP's implementation. The majority of time is spent on the businessside, performing re-engineering, “gap” analysis and so forth.

1.9 OS/390 UNIX System Services Connection Scaling KitEnhancements have been made to OS/390 to complement Baan's architecture.The Connection Manager (CM) and the Process Manager (PM) functions havebeen added to OS/390 UNIX System Services.

Introduced with OS/390 V2R6, the OS/390 UNIX System Services ConnectionScaling Kit, was a no charge, separately orderable feature, that contained thesefunctions (CM and PM). Starting with OS/390 V2R7, these enhancementsbecame part of OS/390 UNIX System Services and thus the OS/390 UNIX SystemServices Connection Scaling Kit feature is no longer needed. In fact, whenOS/390 V2R7 became available, even the original OS/390 R6 Connection ScalingKit became unavailable and is no longer orderable through normal channels.

So if release 6 is going to be used, the OS/390 UNIX Systems Services DB2Connection Scaling Kit F/C 5785 is required and special ordering, in order toopen up the archives, is needed to obtain this kit.


As shown in Figure 4 on page 9, the Connection Manager and the ProcessManager are both part of UNIX System Services.

Figure 4. Connection Manager and Process Manager

1.9.1 Connection Manager (CM)DB2 has a limit of 2000 local connections. Because of this limit, the ConnectionManager (CM) was developed to reduce the number of database connectionsthat would normally occur when running Baan applications.

For example, a typical Baan user may require from four to five databaseconnections. The Connection Manager maintains static data to allow these“logical connect requests” to be funnelled into one physical DB2 thread; that is,the Connection Manager maintains a single connection to DB2 from a givenprocess, the Task Control Block (TCB).

Note: If a user has more than one outstanding commit scope, an adjunct threadis created by the Connection Manager to allow a separate physical connect toDB2.

CM uses DB2/MVS CLI interfaces to provide a thin layer database attach andaccess mechanism using the Open Database Connectivity (ODBC) protocol thatsupports connection to DB2. Connection Manager supports two types of localconnection attachments to DB2: Call Attach Facility (CAF) and ResourceRecovery Services (RRS). Consider the following when deciding the attach type.

Resource Recovery Services (RRS)

RRS is the strategic direction for DB2 for OS/390.

It requires:


− No change to DB2 authorization exits when using the Process Managercomponent of OS/390 UNIX System Services Connection Scaling Kit.

− OS/390 Logger customization.

− RRS to be a separately started OS/390 subsystem.

It supports:

− Retry on lock timeout or deadlock.

− Distributed transaction semantics (currently not used by BAAN IV).

Call Attach Facility (CAF)

It requires:

− No special customization to install.

− Changes to the authorization exit when used with the Process Managercomponent of OS/390 UNIX System Services Connection Scaling Kit.

It supports implicit rollback on all deadlocks or timeouts.

1.9.2 Process Manager (PM)Baan, as implemented on OS390, has been modified to allow all of a singleuser's processes in a single address space, using the UNIX System servicesmultiprocess feature. A typical Baan user could have four to five processesrunning, and without this modification, each process would be assigned anaddress space.

PM takes this a step further and provides the ability for multiple users to coexistin a single address space. These enhancements significantly reduce the amountof address space resources required by the Baan system.

1.10 PrintingThe OS/390 Print Server nicely facilitates printing as it handles IP andSNA-attached printers. After proper configuration, printing is done as with anytypical Windows client. After “triggering a print,” a menu is presented to selecta (configured) printer, whether on the network, JES, to the display and so forth.

Baan generates two kinds of printer data streams: text (ascii) and Printer ControlLanguage (PCL). For PCL data streams, there may be conversion issues. If, forexample, the targeted printer is an Advanced Function Printing (AFP) printer, aPCL-to-AFP conversion is necessary. Note that the current version of the OS/390Print Server does such conversion.

1.11 ConnectivityThe installation client and the Baan user clients can be connected to the S/390via TCP/IP on any transport capable of connecting to the S/390, such asToken-Ring, Ethernet, Fast Ethernet, FDDI or ATM.


1.12 OS/390 Features for Baan ApplicationsOS/390 is an integrated enterprise server operating system environment. Itincorporates into one product an open communication server, distributed dataand file services, Parallel Sysplex support, object-oriented programming, andopen application interfaces.

OS/390 continues to build on the classic strengths of MVS—reliability, continuousavailability, serviceability, data integrity, workload management, and security.OS/390 gives you a scalable system that supports massive transaction volumesand large numbers of users with high performance, as well as advanced systemand network management.

Through its support of UNIX interfaces via the robust UNIX System Services,OS/390 becomes a database server and an application server for BaanApplications, allowing you to profit from client/server technology benefits.

Baan application programs and user data, including data and process models,are stored on the database server. Baan uses DB2 as the database server,which can manage large amounts of data on behalf of many users.

The strengths that OS/390 and System/390 bring to the Baan environmentinclude:

Reliability, availability, and serviceability

Baan S/390 customers need continuous data availability and integrity.OS/390 reliability and availability is unsurpassed and it has a history ofunmatched security and integrity. Baan benefits from these underlyingcharacteristics.

Scalability

The System/390 platform ranges from small uniprocessors to 10-wayprocessors to Parallel Sysplex environments which allow you to connect upto 32 OS/390 systems. The platform can thus support thousands of users.The architecture of the System/390 I/O subsystem and the OS/390 operatingsystem allow data to be transferred into memory from many devicessimultaneously, allowing the processing of data requests for many users athigh data rates. The requests may require accessing data residing inmultiple-terabyte repositories.

System management

OS/390 has many system management capabilities, providing data security,strong operations tools, and the ability to manage diverse workloads.System/390 has proven procedures and tools to manage systems in a veryefficient way.

Cost of ownership

System/390 is acknowledged by consultants such as IDC, GartnerGroup,Xephon, ITG, and others as having one of the lowest overall costs ofownership in a client/server environment when calculated over multipleyears. CMOS technology and software pricing actions have drasticallyreduced the cost of System/390 enterprise computing.


1.13 DB2 FeaturesDB2 is engineered to deliver the high performance and high levels of availability,integrity, and security needed for your business applications. The strengths DB2brings to the Baan Applications environment include:

Continuous operation and high availability

DB2 can operate for long periods without interruption. With data sharing,work can be transferred between DB2 subsystems within a Parallel Sysplexas a result of a planned or unplanned outage.

Online reorganization provides greater availability during database unloadand reload processes.

Data sharing in a Parallel Sysplex environment

DB2 exploits the Parallel Sysplex environment through data sharing, whichallows applications running on more than one DB2 subsystem to read fromand write to the same set of data concurrently.

High data integrity

DB2 provides high data integrity through capabilities such as a sophisticatedlock manager and integration with IBM system security products. DB2 alsoprotects data from subsystem, media, and application failures with integratedrecovery schemes.

Very large database support

DB2 works with the System/390 I/O subsystem to allow the rapid parallelprocesses needed for very large database backup, reorganization, andrecovery of data.

Database and system administration aids

To help database administrators manage their database environments, DB2offers an integrated set of tools and functions, including flexible securitymechanisms, an extensive set of logging and recovery utilities, tracefacilities for tuning, and functions and tools to monitor and tune subsystems.

Other features

In addition to the preceding items, the following features have been added toDB2:

− Data compression− Dynamic Statement Cache− ASCII tables− Isolation level read stability− Keep exclusive locks− Improvements in DDL concurrency− SQL RENAME of tables− SQL STRIP Function

These features are particularly beneficial for an enterprise using BaanApplications for OS/390.


1.14 Strengths of RVA and SnapShot for Baan Applications for OS/390The RAMAC Virtual Array (RVA) provides a high availability, scalable,easy-to-manage storage subsystem that complements the strengths of S/390.

The virtual disk architecture of the RVA spreads all data across all the availabledisks, reducing the requirement for data placement to avoid “hot-spots.” Onlydata that is actually written is stored on the RVA, which allows you to allocatedata sets for peak production use without penalty. Additional physical storagecapacity can be added non-disruptively.

The RVA's architecture also enables SnapShot. SnapShot is an data duplicatorthat manipulates pointers in the RVA to make instant copies of data at the dataset and volume level. SnapShot is integrated in the DB2 utilities using theconcurrent copy interface. This can significantly increase application availabilitywhen making point-in-time copies.

An overview of RVA and SnapShot is provided in Appendix E, “RAMAC VirtualArray (RVA)” on page 131 and Appendix F, “SnapShot” on page 135.

A discussion of RVA and SnapShot for point-in-time recovery is provided inChapter 11, “Administration of DB2 for Baan Applications on OS/390” onpage 99.



Chapter 2. Installation Overview - Preparing for the Installation

This chapter describes the steps we did to prepare the S/390 for the BaanERPinstallation. The team that will be installing BaanERP Applications for OS/390need to have skills in the following areas:

DB2 installation including DB2 UtilitiesTCP/IP including setting up of telnet and ftpUNIX System ServicesBaanERP installation process

The reference manuals we used were:

BaanERP - Installation Guide for BaanERP on OS/390 UNIX System Services,available from Baan

BaanERP - DB2 Installation Guide for BaanERP, available from Baan

UNIX System Services Connection Scaling Reference, SA22-7305, availablefrom IBM

These publications, available from Baan, are also relevant as further informationsources. Contact Baan or the IBM Baan International Competency Center for thelatest information on any PTFs that are required. For information on how tocontact Baan go to: http://www.baan.com .

2.1 BaanERP Installation StepsThe detailed installation process is described in Chapter 5, “BaanERPApplications Installation” on page 37. A summary of the steps in the installationprocess is:

1. Prepare the OS/390 environment.

Customize DB2 and plan the database layout.

Customize the Connection Manager and Process Manager, which arepart of the UNIX System Services Connection Scaling Kit for OS/390

Set up TSO BaanERP user IDs.

Prepare the UNIX System Services environment.

− Set up the HFS file systems.

− Unload and explode the BaanERP CD-ROM files to an HFS

− Set up the environment variables and the profiles.

2. Run the installation script to install the BaanERP applications and Company000 (using install6.2 script).

3. Run the DB2 script (db2_install6.2) to create DB2 files needed for theinstallation, or use JCL and sample DB2 files

4. Set up the BaanERP Client (BW).

5. Execute the post-installation tasks

6. Install demo companies using BaanERP tools on the BW Client.

7. Set up the Process Manager.

8. Set up printers.


9. Set up BaanERP applications to run in the Link Pack Area (LPA).

10. Set up the localization customization.

Loading Company 000 takes about 10 to 15 hours, depending on your hardwareconfiguration.

2.1.1 Preparing the EnvironmentThe following software items were installed on our LPAR:

OS/390 V2R6

OS/390 eNetwork Communications Server TCP/IP V2R6

For Telnet access, port numbers are needed for TSO and for UNIX SystemServices

DB2 V5.1 with current maintenance

Connection Manager

Process Manager

Code for hostname program

Note: The vi editor can be used for the EBCDIC files when logged on through atelnet session or oedit can be used when accessing HFS files through the ishcommand. The viascii editor is needed for editing the Baan internet html files.See Appendix B, “The vi Editor and Common UNIX Commands” on page 115, forinformation on how to obtain the viascii editor and how to use the vi and viasciieditors. A short list of common vi commands is included for those not familiarwith the vi commands.

2.1.1.1 HostnameA hostname command is used by the db2_install6.2 script to retrieve the hostname. This command is not part of UNIX System Services. See Appendix C,“The hostname Command” on page 119 for the source code. The hostnameexecutable should be placed in a directory such as /bin that the BaanERPApplications can use.

The hostname program can be obtained at:

http//www.s390.ibm.com/products/oe/bpxa1toy.html

The host name is stored in the following files;

/etc/resolv.conf

TCPIPDATA (where ever you point to in your TCP/IP started task)

/etc/host

The host name is used to generate the BaanERP license. We found that the hostname must be stored in same case (upper or lower case) in all these places. Itis stored in the file /$BSE/lib/licence6.2. For example, you must ensure that allthese files have the host name in lower case and that you request the BaanERPlicense using lower case.

You can test to see that you have /etc/resolv.conf set correctly by issuing thecommand onslookup in UNIX System Services. If you are using two TCP/IPstacks you can also issue the command nslookup as a TSO command. This willreturn the host name as the system has it.


2.1.2 Set Up the TSO User IDsFor BaanERP Installation user IDs, we created two user IDs, bsp and root, (forBaan, these must be in lowercase) as shown in Figure 5. The alias fileassociates the uppercase TSO user ID with the lowercase UNIX System Servicesuser ID.

à ðFile Edit Confirm Menu Utilities Compilers Test Help

ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssEDIT /etc/alias Columns 00001Command ===> Scroll ===****** ***************************** Top of Data ***********************000001 :UserIDs000002 ROOT root000003 BSP bsp000004 OMVSKERN root000005 :Groups000006 BSPGRP bsp****** **************************** Bottom of Data *********************

á ñ

Figure 5. User IDs in Uppercase and Lowercase. Note that the lowercase entries muststart in column 10.

To activate this, at the console we issued the command:

setomvs useridaliastable='/etc/alias'

This activates the table until the next IPL. To permanently activate it, add it toBPX parms, as shown in Appendix A, “BPX Parameters” on page 111.

Note: If you try to issue this command through TSO, it is translated to uppercaseand does not work correctly.

To verify the ID that owns the files, issue the command id . This shows you whothe owner is for the root user ID file. A typical output of the id command is:

uid=0(OMVSKERN) gid=125(BSPGRP)

In our case there were several userids with the uid of 0. As OMVSKERN was thefirst in the stack (before ROOT) that is what appears as the owner id.OMVSKERN is shown to be the owner when the ls -l command is issued. Asthe BaanERP installation manual stated, the owner that is shown in the idcommand must be entered in the /etc/alias table pointing to root.

For BaanERP users, create user IDs such as BAAN01 and BAAN02 in the groupbspgrp. These require unique uids (not 125). User IDs for those using NT orOS/2 workstations should be in uppercase. To enable access to BaanERPapplications, user IDs are created both as a OMVS user in RACF and also inBaanERP using Baan Tools.

2.1.3 DASD RequiredWe started with eight DASD packs of 3390: BAAPK0, BAAPK1, BAAPK2,BAAPK3, BAAPK4, BAAPK5, BAAPK6 and BAAPK7. Three were put into storagegroup SGBAAN to be used by HFS, two were used for the DB2 code and threewere used for the Baan DB@ databases.

Chapter 2. Installation Overview - Preparing for the Installation 17

2.1.4 Client WorkstationWe found using a product such as EXCEED (or ONNET or WTELNET) for Telnetinterface was easier than just using Windows telnet.

2.1.5 Customizing DB2The details of the DB2 customization are in Chapter 3, “DB2 and BaanERPApplications on OS/390” on page 23. The DB2 Utilities should be availableunder TSO as they will be needed in the installation process.

2.1.6 Customizing CM and PMThe details of the CM customization are in Chapter 4, “Enabling UNIX SystemServices” on page 33. The details of the PM customization are in Chapter 10,“Enabling Process Manager on UNIX System Services” on page 93.

2.1.7 Setting Up To Load the B aanERP Software from CD-ROMThe steps that enabled us to load the installation code from CD-ROM aredescribed in 5.3, “Unloading the Baan Code” on page 40.

2.1.8 UNIX System Services File StructuresThe HFS file systems that BaanERP are used for:

A copy of the CD-ROM file - in our case, this was BAANERP.CDROM.

The source data for installation - in our case, this was BAANERP.INSTALL.

The target data from the installation process - in our case, this wasBAANERP.APPL.BSE.

Note: We recommend you put the version number (in our case ERP) in thehigh-level directory name (but not the release number), as it will be easier towork with when you are migrating to a later version and have several versionsactive in the system. The instructions on how to create and mount the files areincluded as part of the installation procedure described in Chapter 5, “BaanERPApplications Installation” on page 37.

2.2 Keeping Track of Names UsedWe found there were many pieces of information that were needed throughoutthe installation process. If these were not readily available and accurate, itcaused problems and delays in the install process. We created the followingtable to store this information.

Table 1 (Page 1 of 2). Names Used in the BaanERP Installation

Name Value Description

BSE /baanerp/bseBaanERP software environmentdirectory

$BSE /baanerp/bse value of variable BSE

User ID root Install user ID

User ID for TSO ROOTInstall user ID must be in capitals fromthe telnet session

User ID bsp BaanERP user IDs


Table 1 (Page 2 of 2). Names Used in the BaanERP Installation

Name Value Description

Port number 6000 For Process Manager Connection

Port number 1180 For BI HTTP Server for bi client

Database instancename

DB2D

hlq for DB2 DB2V510D

Plan name forBIND

CMXPLNE

DBRM library CMX.SCMXDBRM contains Connection Manager modules

StoGroup for HFS SCBAAN

StoGroup for DB2 BERPGRP

VSAM catalog DB2V510D

Databases BERP000 Database for Company 000

Tablespace TS000 Table space for Company 000

2.3 Disk Space RequiredTable 2 shows the size of the HFS and DB2 files we allocated.

If you have the DASD available or are using an RVA, it is recommended that youallocate an entire 3390 - 003 for each of the three HFS files. After the installationphase is complete, you can release two of the packs. If you are short of DASD,use the space recommendation in BaanERP - Installation Guide for BaanERP onOS/390 UNIX System Services.

In our initial installation, we used one tablespace per company. This meant wehad the same primary and secondary extent for each index and table. Furthertesting in IBM and Baan showed that to optimize the layout, it was better to setup a customized allocation. This customized layout is in the sample db2_storagefile that is shown in detail in Appendix H, “Alternate DB2 Layout” on page 149.For Company 000, it puts approximately 34 indexes and 50 tables in their owntablespaces.

Table 2. Disk Space Required for BaanERP

File File type Primary Secondary

Dump of CD-ROM files HFS 2000 cyls 0

Install files HFS 3300 cyls 0

Target files HFS 3300 cyls 0

Company 000 index DB2 12 Kb 960 Kb

Company 000 tables DB2 1440000 Kb 144000 Kb






2.4 BaanERP for OS/390 Release NotesFor your reference, the following is a copy of the release notes we received fromBaan with the April 1999 CD-ROM for BaanERP. There are several key points tonote.

2.4.1 Release NotesThe following problems represent those which were encountered after we madethe installation CDs, or are commonly made mistakes in BaanIVc installations.

2.4.1.1 Pre-InstallThe OS/390 setup must be complete. For instance, the file command must workas designed. In our case, it happened a couple of times that /samples/magicwas not copied to /etc , so file did not work. This causes the install process tofail.

2.4.1.2 InstallWe shipped an IBM file with our Baan Portingset. After paxing the portingset,issue the command

rm ln.0000/bse/bin/cmxdll

from your installation directory before starting the install script.

The file ipc_info which is in /$BSE/lib must be changed during the installationprocess. The shell server (sh_server) does not communicate with sockets, butjust pipes. Change the s to a p in the fifth column on the sh_server line.

There is an error in the fd6.2.Install file. Change the $BSE/lib/user/uROOT (oruroot, if you are able to logon with a lowercase userid) file. The PACC: line mustpoint to the package combination specified during the install (default b50b, check$BSE/lib/fd*). Both of these changes must be made just before starting the BW toperform the second part of the installation.

The BaanWindows client should not be converted from ASCII to EBCDIC duringinstallation time, but it is. Therefore, before copying its files to your workstation,you need to convert them back.

To do this, first make a directory (BSE/mswindows/ascii) and issue a commandsuch as:

pax -wvmswindows/BW_english/i386/* | pax -rv -pe -o from=IBM-1047,to=ISO8859-1-s!mswindows!ascii!

The files in the ASCII directory can then be copied to the workstation.

Note: Do not try to convert them using an ASCII FTP; that will not work.

The same requirement must be applied to the Internet server, the $BSE/internetdirectory. Convert it to ASCII using this method before installing it. The latestversion of the BW Client can be retrieved from ftp.support.baan.com(ftp://ftp.support.baan.com). This one is, of course, in ASCII format.

Exiting the shell might cause a protection exception. This can be solved bysetting BPX_SHAREAS=NO. This might result in a performance degradation.


During the second part of the installation, a message box about user ROOT willpop up. Press OK to continue. This might happen for user bsp as well. PressOK again. This will happen approximately one hour after starting the BW (on aslow machine, this might take longer).

2.4.2 Post InstallAfter starting the license daemon, you need to wait a couple of minutes beforethe validation can begin. DB2 needs to be checked for licensing. Do not checkthe box with DB2 V5.

When importing data or patches, remember to convert the files to EBCDIC beforedoing the actual import. The following describes the best way to do thisconversion:

Copy your files in the way you are used to, to a dedicated directory($BSE/patches). If you use FTP, make sure it is in binary.

Create a new directory ($BSE/patches_ebcdic).

Issue the following command:

pax -wv $BSE/patches/* | pax -rv -pe -o from=ISO8859-1,to=IBM-1047s !$BSE/patches!$BSE/patches_ebcdic!

Start the normal import session. Note that it might take some time beforethe actual import starts.

There is a little bug in the Connection Manager and thread reusage. This mightresult in the absence of locks. Therefore, you are advised to set theenvironment variable CMX_THREAD_WAIT to 0.



Chapter 3. DB2 and BaanERP Applications on OS/390

This chapter describes the steps for the customization needed to set up DB2 forthe BaanERP installation, and the initial database layout for Company 000.

3.1 Set Up DB2 Databases and TablespacesThese are the steps to customize DB2 for BaanERP applications:

Install DB2 V5.1 with maintenance level as of 06/98 (or later).

Update the DB2 parameters (DSNZPARM and DSNHDECP) as described in3.2, “DB2 Parameters.”

Grant sysadm privilege to TSO user ID ROOT for your database subsystem.

Create the DB2 databases and tablespaces, as described in Figure 7 onpage 30.

Note: There are three ways you can set up your DB2 databases andtablespaces:

− Use the db2_install6.2 script

− Use the sample JCL files provided with the BaanERP code.

− Create your own layout with JCL.

For our first installation, we used JCL to create a simple layout with onedatabase and one tablespace for Company 000.

Create the DB2 files that the Baan DB2 driver requires, as shown in 3.2.3,“DB2 Files BaanERP Uses” on page 31 and Appendix D, “Executing thedb2_install6.2 Script” on page 121.

We used the db2_install6.2 script during the installation process to createfiles in /BSE/lib/db2 that the Baan db2 driver requires.

Grant privileges to user ID bsp.

Bind the plan with the DB2 system as shown in 4.2, “JCL Used to BIND thePlan” on page 34.

Note: For our installation, we choose to store the BaanERP data in ASCII format,which is the recommended format.

3.2 DB2 ParametersThe DB2 parameters we used for our installation are shown in Figure 6 onpage 24. The ones we changed from our standard set of parameters are notedas changed for BaanERP subsystem. These changes were made based on aconsensus of opinion from the IBM BaanERP test team and the DB2 Specialistworking on this project.


à ð

//ZPARMS JOB (999,POK),'DB2V510D',CLASS=A,MSGCLASS=T, 00000001// NOTIFY=&SYSUID,TIME=1440,REGION=4M 00000002/*JOBPARM L=999,SYSAFF=SC55 00000003//*********************************************************************/00010000//* JOB NAME = DSNTIJUZ */00020000//* */00030000//* CHANGES: 8/11/98 UPDATES PARMS FOR BAAN */00050000//* 8/20/98 CREATED SDSNEXIT.SC55 FOR BAAN ONLY */00090000//* */00090000//* */00090000//* STATUS = VERSION 5.1 */00100000//* */00110000//* FUNCTION = DSNZPARM AND DSNHDECP UPDATES */00120000//* */00130000//* PSEUDOCODE = */00140000//* DSNTIZA STEP ASSEMBLE DSN6.... MACROS, CREATE DSNZPARM */00150000//* DSNTIZL STEP LINK EDIT DSNZPARM */00160000//* DSNTLOG STEP UPDATE PASSWORDS */00170000//* DSNTIZP STEP ASSEMBLE DSNHDECP DATA-ONLY LOAD MODULE */00180000//* DSNTIZQ STEP LINK EDIT DSNHDECP LOAD MODULE */00190000//* DSNTIMQ STEP SMP/E PROCESSING FOR DSNHDECP */00200000//* */00201990//* NOTES = STEP DSNTIMQ MUST BE CUSTOMIZED FOR SMP. SEE THE NOTES */00203980//* NOTES PRECEDING STEP DSNTIMQ BEFORE RUNNING THIS JOB. */00205970//* */00210000//*********************************************************************/00220000//DSNTIZA EXEC PGM=ASMA90,PARM='OBJECT,NODECK' 00230000//SYSLIB DD DISP=SHR, 00240000// DSN=DB2V510.SDSNMACS 00250000// DD DISP=SHR, 00260000// DSN=SYS1.MACLIB 00270000//SYSLIN DD DSN=&&LOADSET(DSNTILMD),DISP=(NEW,PASS), 00280000// UNIT=SYSALLDA, 00290000// SPACE=(800,(50,50,2)),DCB=(BLKSIZE=800) 00300000//SYSPRINT DD SYSOUT=* 00310000//SYSUDUMP DD SYSOUT=* 00320000//SYSUT1 DD UNIT=SYSALLDA,SPACE=(800,(50,50),,,ROUND) 00330000//SYSUT2 DD UNIT=SYSALLDA,SPACE=(800,(50,50),,,ROUND) 00340000//SYSUT3 DD UNIT=SYSALLDA,SPACE=(800,(50,50),,,ROUND) 00350000//SYSIN DD * 00360000

DSN6ENV MVS=XA 00370000DSN6SPRM RESTART, X00370001

ALL, X00370002ABEXP=YES, X00370003ABIND=YES, X00370004AUTH=YES, X00370005AUTHCACH=1024, X00370006BINDNV=BINDADD, X00370007BMPTOUT=0, X00370008CACHEDYN=YES, X00370009CACHEPAC=32768, X00370010

á ñ

Figure 6 (Part 1 of 6). DB2 Parameters Used


à ðCATALOG=DB2V510D, X00370011CDSSRDEF=1, X00370012CHGDC=NO, X00370013CONTSTOR=YES, Needed with PTF UQ19012 X00370013DECDIV3=NO, X00370014DEFIXTP=2, X00370015DEFLTID=IBMUSER, X00370016DESCSTAT=NO, X00370017DLITOUT=0, X00370018DSMAX=3000, X00370019EDMPOOL=100000, changed for BaanERP from 1368 X00370020EDPROP=NO, X00370021HOPAUTH=YES, X00370022IRLMAUT=YES, X00370023IRLMPRC=IRLDPROC, X00370024IRLMSID=IRLD, X00370025IRLMRWT=60, X00370026IRLMSWT=300, X00370027MAXRBLK=4384, X00370028MAXKEEPD=65535, changed for BaanERP from 5000 X00370029NUMLKTS=1000, X00370030NUMLKUS=10000, X00370031RECALL=YES, X00370032RECALLD=120, X00370033RELCURHL=NO, X00370034RETLWAIT=NO, X00370035RETVLCFK=NO, X00370036RGFCOLID=DSNRGCOL, X00370037RGFDBNAM=DSNRGFDB, X00370038RGFDEDPL=NO, X00370039RGFDEFLT=ACCEPT, X00370040RGFESCP=, X00370041RGFFULLQ=YES, X00370042RGFINSTL=NO, X00370043RGFNMORT=DSN_REGISTER_OBJT, X00370044RGFNMPRT=DSN_REGISTER_APPL, X00370045RRULOCK=NO, X00370046SEQCACH=BYPASS, X00370047SEQPRES=NO, X00370048SITETYP=LOCALSITE, X00370049SRTPOOL=876, X00370050SYSADM=BAARES1, X00370051SYSADM2=HAIMO, X00370052SYSOPR1=SYSOPR, X00370053SYSOPR2=SYSOPR, X00370054TRKRSITE=NO, X00370055UTIMOUT=6 00370056

DSN6ARVP ALCUNIT=BLK, X00370057ARCWRTC=(1,3,4), X00370058ARCWTOR=YES, X00370059

á ñ


Chapter 3. DB2 and BaanERP Applications on OS/390 25

à ðARCPFX1=DB2V510D.ARCHLOG1, X00370060ARCPFX2=DB2V510D.ARCHLOG2, X00370061ARCRETN=9999, X00370062BLKSIZE=28672, X00370063CATALOG=NO, X00370064COMPACT=NO, X00370065PRIQTY=1234, X00370066PROTECT=NO, X00370067QUIESCE=5, X00370068SECQTY=154, X00370069TSTAMP=NO, X00370070UNIT=SYSALLDA, X00370071UNIT2=SYSALLDA 00370072

DSN6LOGP DEALLCT=(0), X00370073INBUFF=28, X00370074MAXARCH=1000, X00370075MAXRTU=2, X00370076OUTBUFF=400, X00370077TWOACTV=YES, X00370078TWOARCH=YES, X00370079WRTHRSH=20 00370080

DSN6SYSP AUDITST=NO, X00370081CONDBAT=64, X00370082CTHREAD=2000, changed for BaanERP from 70 X00370083DLDFREQ=5, X00370084IDBACK=2000, changed for BaanERP from 20 X00370085IDFORE=40, X00370086LOGLOAD=50000, X00370087MAXDBAT=64, X00370088MON=NO, X00370089MONSIZE=8192, X00370090RLF=NO, X00370091RLFTBL=01, X00370092RLFERR=NOLIMIT, X00370093RLFAUTH=SYSIBM, X00370094ROUTCDE=(1), X00370095EXTSEC=NO, X00370096SMFACCT=(1), X00370097SMFSTAT=YES, X00370098STATIME=30, X00370099STORMXAB=0, X00370100STORPROC=DB2DSPAS, X00370101STORTIME=60, changed for BaanERP from 180 X00370102TRACSTR=NO, X00370103TRACTBL=16, X00370104URCHKTH=0 00370105

á ñ



à ðDSN6FAC DDF=AUTO, X00370106

CMTSTAT=ACTIVE, X00370107IDTHTOIN=0, X00370108RESYNC=2, X00370109RLFERRD=NOLIMIT, X00370110TCPALVER=NO 00370111

DSN6GRP DSHARE=NO, X00370112GRPNAME=DSNCAT, X00370113MEMBNAME=DB2D, X00370114COORDNTR=NO, X00370115ASSIST=NO 00370116

END 01370000//********************************************************************* 01380000//* LINK EDIT THE NEW DSNZPARM MEMBER. PUT LOAD MODULE IN SDSNEXIT. * 01390000//********************************************************************* 01400000//DSNTIZL EXEC PGM=IEWL,PARM='LIST,XREF,LET,RENT', 01410000// COND=(4,LT) 01420000//ADSNLOAD DD DISP=SHR, 01430000// DSN=DB2V510.SDSNLOAD 01440000// DD DISP=SHR, 01450000// DSN=DB2V510.ADSNLOAD 01460000//SYSPUNCH DD DSN=&&LOADSET(DSNTILMD),DISP=(OLD,DELETE) 01470000//SYSLMOD DD DISP=SHR, 01480000// DSN=DB2V510.SDSNEXIT.SC55 01490000//SYSPRINT DD SYSOUT=* 01500000//SYSUDUMP DD SYSOUT=* 01510000//SYSUT1 DD UNIT=SYSALLDA,SPACE=(1024,(50,50)) 01520000//SYSLIN DD * 01530000

INCLUDE SYSPUNCH(DSNTILMD) 01540000INCLUDE ADSNLOAD(DSNZPARM) 01550000ORDER DSNAA 01560000INCLUDE ADSNLOAD(DSNAA) 01570000INCLUDE ADSNLOAD(DSNFSYSP) 01580000INCLUDE ADSNLOAD(DSNJARVP) 01590000INCLUDE ADSNLOAD(DSNJLOGP) 01600000INCLUDE ADSNLOAD(DSNTSPRM) 01610000INCLUDE ADSNLOAD(DSNVDIR1) 01620000INCLUDE ADSNLOAD(DSNZMSTR) 01630000INCLUDE ADSNLOAD(DSN3DIR1) 01640000INCLUDE ADSNLOAD(DSN7GRP) 01650000ENTRY DSNZMSTR 01660000NAME DSNZDB2D(R) 01670000

//* 01680000//* CHANGE LOG INVENTORY: 01690000//* UPDATE BSDS WITH PASSWORDS, 01700000//* UPDATE BSDS WITH DISTRIBUTED VALUES 01710000//* 01720000//DSNTLOG EXEC PGM=DSNJU003,COND=(4,LT) 01730000//STEPLIB DD DISP=SHR,DSN=DB2V510.SDSNLOAD 01740000//SYSUT1 DD DISP=OLD,DSN=DB2V510D.BSDS01 01750000//SYSUT2 DD DISP=OLD,DSN=DB2V510D.BSDS02 01760000//SYSPRINT DD SYSOUT=* 01770000//SYSUDUMP DD SYSOUT=* 01780000//SYSIN DD * 01790000

DDF LOCATION=DB2D,LUNAME=SCPDB2D, 01790001NOPASSWD,RESPORT=33305,PORT=33304 01790002

//* 02630000á ñ



à ð//********************************************************************* 02640000//* ASSEMBLE AND LINK EDIT DATA-ONLY LOAD MODULE DSNHDECP. 02650000//* THE FOLLOWING STEPS ARE NEEDED ONLY IF THE 02660000//* VALUES ARE CHANGED FROM THOSE WHICH ARE SHIPPED. 02670000//********************************************************************* 02680000//DSNTIZP EXEC PGM=ASMA90,PARM='OBJECT,NODECK',COND=(4,LT) 02690000//SYSLIB DD DISP=SHR, 02700000// DSN=DB2V510.SDSNMACS 02710000//SYSLIN DD DSN=&&LOADSET(DSNHDECA),DISP=(NEW,PASS),UNIT=SYSALLDA, 02720000// SPACE=(80,(50,50,2)),DCB=(BLKSIZE=80) 02730000//SYSPRINT DD SYSOUT=* 02740000//SYSUDUMP DD SYSOUT=* 02750000//SYSUT1 DD UNIT=SYSALLDA,SPACE=(800,(50,50),,,ROUND) 02760000//SYSUT2 DD UNIT=SYSALLDA,SPACE=(800,(50,50),,,ROUND) 02770000//SYSUT3 DD UNIT=SYSALLDA,SPACE=(800,(50,50),,,ROUND) 02780000//SYSIN DD * 02790000

DSNHDECM CHARSET=ALPHANUM, X02790001ASCCSID=819, changed for BaanERP from 2 X02790002AMCCSID=65534, X02790003AGCCSID=65534, X02790004SCCSID=37, changed for BaanERP from 1 X02790005MCCSID=65534, X02790006GCCSID=65534, X02790007ENSCHEME=ASCII, changed for BaanERP from EBCDIC X02790008DATE=ISO, You must have this for BaanERP X02790009DATELEN=0, X02790010DECARTH=DEC15, X02790011DECIMAL=PERIOD, X02790012DEFLANG=IBMCOB, X02790013DELIM=DEFAULT, X02790014MIXED=NO, X02790015SQLDELI=DEFAULT, X02790016DSQLDELI=APOST, X02790017SSID=DB2D, X02790018STDSQL=NO, X02790019TIME=ISO, X02790020TIMELEN=0 02790021

END 02970000//* 02980000

á ñ



à ð//********************************************************************* 02990000//* LINK EDIT DSNHDECP. * 03000000//* DSNHDECP IS A DATA-ONLY LOAD MODULE CONTAINING DEFAULT VALUES * 03010000//* REQUIRED BY DB2 AND APPLICATION PROGRAMS. * 03020000//* THIS STEP IS CREATED ONLY WHEN THE DEFAULTS SUPPLIED IN * 03030000//* DSNHDECP ARE NOT SUITABLE. * 03040000//********************************************************************* 03050000//DSNTIZQ EXEC PGM=IEWL,PARM='LIST,XREF,LET,RENT', 03060000// COND=(4,LT) 03070000//ADSNLOAD DD DISP=SHR, 03080000// DSN=DB2V510.SDSNEXIT 03090000// DD DISP=SHR, 03100000// DSN=DB2V510.ADSNLOAD 03110000//SYSPUNCH DD DSN=&&LOADSET(DSNHDECA),DISP=(OLD,DELETE) 03120000//SYSLMOD DD DISP=SHR, 03130000// DSN=DB2V510.SDSNEXIT.SC55 03140000//SYSPRINT DD SYSOUT=* 03150000//SYSUDUMP DD SYSOUT=* 03160000//SYSUT1 DD UNIT=SYSALLDA,SPACE=(1024,(50,50)) 03170000//SYSLIN DD * 03180000

INCLUDE SYSPUNCH(DSNHDECA) 03190000ORDER DSNAA 03200000INCLUDE ADSNLOAD(DSNAA) 03210000INCLUDE ADSNLOAD(DSNARIB) 03220000INCLUDE ADSNLOAD(DSNHDECP) 03230000ENTRY DSNHDECP 03240000MODE AMODE(24),RMODE(24) 03250000NAME DSNHDECP(R) 03260000

á ñ


The BaanERP load process will produce many archive logs as each SQL insertcauses the image of the row to be logged. Ensure there are procedures in placeto handle the heavy logging of data during the installation.

3.2.1 JCL Used to Create TablespacesThe JCL we used to create the database is shown in Figure 7 on page 30.Because we restarted several times during the loading of Company 000, weplaced the drop commands at the beginning of the job. When you are creatingthe database and tablespaces, you should also consider assigning bufferpools.This topic is covered in more detail in 11.5.1, “DB2/BaanERP Buffer PoolRecommendations” on page 102. Our JCL uses the following allocation of bufferpools:

BP2 for database for Company 000BP4 for tablespaces for Company 000

The db2_storage file, shown in Figure 8 on page 32, has the bufferpoolallocations for indexes:

BP3 for indexes for Company 000

Attention

If you choose to use the supplied db2_install6.2 script to create the database,you do not have to run this job.


à ð//BAANDB2 JOB (999,POK),'BAAN INSTALL',NOTIFY=&SYSUID, 00010023//*********************************************************************///* NAME = BAANDDL *///* *///* DESCRIPTIVE NAME = SAMPLE DDL TO CREATE DATABASES & TABLESPACES *///* FOR BAAN IV INSTALLATION *///* *///* STATUS = VERSION 1 *///* *///* FUNCTION = THIS JCL PERFORMS THE NECESSARY DDL TO BUILD THE *///* BAAN IV DB2 DATABASE. THE FOLLOWING DDL MATCHES THE *///* SETUP SUPPLIED IN THE $BSE/lib/db2/db2_storage FILE. *///* *///* ANY CHANGES TO STOGROUP, DATABASE AND/OR TABLESPACE *///* NAMES REQUIRES THE CORRESPONDING CHANGE IN THE *///* $BSE/lib/db2/db2_storage FILE. *///* *///* YOU MUST UPDATE THE hlq IN THE JOBLIB. *///* *///* CHANGE ACTIVITY = *///*********************************************************************/

//JOBLIB DD DSN=DB2V510D.RUNLOAD,DISP=SHR// DD DSN=DB2V510.SDSNLOAD,DISP=SHR//CREATDDL EXEC PGM=IKJEFT01,DYNAMNBR=20//SYSPRINT DD SYSOUT=*//SYSTSPRT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSTSIN DD *

DSN S(DB2D)RUN PROG(DSNTIAD) PLAN(DSNTIA51)END

//SYSIN DD *

DROP DATABASE BERP000;DROP STOGROUP BERPGRP;

COMMIT;

CREATE STOGROUP BERPGRP

VOLUMES (BAAPK5,BAAPK6,BAAPK7) VCAT DB2V510D;COMMIT;

CREATE DATABASE BERP000STOGROUP BERPGRPBUFFERPOOL BP2;

COMMIT;

CREATE TABLESPACE TS000 IN BERP000 BUFFERPOOL BP4USING STOGROUP BERPGRP

PRIQTY 1440000 SECQTY 144000LOCKSIZE ROW SEGSIZE 32 CLOSE NO;

á ñ

Figure 7 (Part 1 of 2). JCL to Create Tablespaces with Company 000, Detailed Setup


à ðCOMMIT;

GRANT DBADM ON DATABASE BERP000 TO BSPGRP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP000 TO BSP WITH GRANT OPTION;GRANT USE OF STOGROUP BERPGRP TO BSPGRP;GRANT USE OF STOGROUP BERPGRP TO BSP;

GRANT USE OF ALL BUFFERPOOLS TO PUBLIC;/*//

á ñ

Figure 7 (Part 2 of 2). JCL to Create Tablespaces with Company 000, Detailed Setup

3.2.2 Binding the Plan That BaanERP UsesAfter you have customized the Connection Manager, you must bind the plan tothe DB2 subsystem. This is described in 4.2, “JCL Used to BIND the Plan” onpage 34.

3.2.3 DB2 Files BaanERP UsesThere are three files that the BaanERP DB2 driver uses to set up the tables inthe database. These are created using the db2_install6.2 script that is executedduring the installation process. The process to do this is described in 5.5.2,“Using the db2install6.2 Script” on page 49. After executing this script, thefollowing three files will be placed in /baanerp/bse/lib/db2.

à ðcd /baanerp/bse/lib/db2

$ ls

db2_groups db2_storage db2_usersá ñ

The following shows db2_groups. The group name db2berp becomes the ownerID or create ID.

à ðdb2berp:qZ.m7rcL}G3WW"t6L{79r$,<[email protected]

á ñ

The following shows db2_users; these unintelligible character strings areencrypted passwords that are not used for OS/390, but are used in the UNIXimplementation. These files are the same as used in the UNIX implementation.

à ðBSP:BSP:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:bspgrpbsp:bsp:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:bspgrproot:root:&l%d(43‘"Bd5g+jaj2I1/o,-0H){c3&colonE:bspgrpROOT:ROOT:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:bspgrp

á ñ

Figure 8 on page 32 shows a very simple db2_storage that puts everything inone database and one tablespace:


à ð*:*:I::01::STOGROUP BERPGRP PRIQTY 64 SECQTY 960 BUFFERPOOL BP3*:*:T:group:01:5: ARR_SIZE 1 OPT_ROWS 5 T_SPACE BERP000.TS000.

á ñ

Figure 8. Simple db2_storage File

3.3 Points to NoteThe following points address the problems that we encountered:

During the load process of Company 000, there will be a lot of archivingactivity as the load is done thru SQL inserts to the database. Be sure thereare procedures in place to handle the archive logs either on disk or on tape.You do not need to keep these logs after you have made backup at the endthe installation process.Do not share databases among companies. Company 000 must be in adifferent database than the others or you will get a lock condition when youtry to load the next company.To avoid DB2 timeouts, use the kill command to terminate the pdaemonthread (started by the install6.2 script) before loading demo companies.To avoid the problems in the load process, include the statement GRANTUSE OF ALL BUFFERPOOLS TO PUBLIC.To improve performance by avoiding table scans during the load phase,include the statement OPT_ROWS_5 in the db2_storage file.To accommodate all the entries that are made during the load phase, ensurethe OS/390 catalog used by DB2 is at least eight cylinders.


Chapter 4. Enabling UNIX System Services

This chapter describes how we customized the Connection Manager functions ofthe UNIX System Services Connection Scaling Kit for our installation.

The steps to customize the Connection Manager are:

Update the configuration file - /etc/cmx.conf

BIND the plan

Set the variables

The installation of this new OS/390 feature was straightforward and is welldocumented in the Program Directory for OS/390 UNIX System ServicesConnection Scaling Kit, GI10-0635, which is shipped with the OS/390 PTF.

Note: We discovered that customization had to be done through a Telnetscreen, rather than through a TSO session, in order to enable special charactersdisplay correctly.

4.1 Customizing Connection Manager (CM)The sample connection manager configuration file needs to be copied to the/etc/cmx directory. The /etc/cmx directory was created during the installation ofthe UNIX System Services Connection Scaling Kit. The following command willcopy the file:

cp /usr/lpp/cmx/samples/cmx.conf /etc/cmx/cmx.conf

We used the vi editor from a Telnet screen to customize the ConnectionManager, as shown in Figure 9.

These entries must match the entries in DNSZPARM and DNSDECHPparameters. See Figure 6 on page 24 for our DB2 parameter files.

à ð// Connection Manager Resources

[NAMES]DB2SubSystem=DB2DDB2PlanName=CMXPLNEDB2Attach=CAF

[CCSID]DB2ccsid=819

[TRACE]Trace=0TraceWrap=0TraceUser=ALL

[ERROR]DB2ErrorLog=1

á ñ

Figure 9. Customizing the Connection Manager


Note:

You should run the installation process with the entry for D2ErrorLog=0. This isto prevent you from creating a large file of messages about unique indexes thatmay be ignored and that do not affect the installation process. You could havetwo customization files, or your could change the file after you have completedthe installation.

There are two DB2Attach options: CAF or RRS. To use RRS, see the informationin UNIX System Services Connection Scaling Reference, SA22-7305.

4.2 JCL Used to BIND the PlanThere is a sample job provided with the PID tape. The JCL we used to BIND theplan to DB2 is shown in Figure 10. This JCL should be in SYS1.SAMPLIB asmember CMXBIND, after you have installed the IBM Connection Scaling Kit.

The parameter DYNAMICRULES(RUN) is required for loading the databases. Itshould be changed to DYNAMICRULES(BIND) after all databases have beenloaded. See 4.4, “Using a Second CMXPLAN Name” on page 36, for moreinformation.

à ð//BIND JOB (999,POK),'BAAN INSTALL',NOTIFY=&SYSUID, 00010023// CLASS=A,MSGCLASS=T,TIME=1439, 00020017// REGION=5000K,MSGLEVEL=(1,1) 00030017//DBBIND EXEC PGM=IKJEFT01//STEPLIB DD DISP=SHR,DSN=DB2V510D.RUNLIB.LOAD// DD DISP=SHR,DSN=DB2V510.SDSNLOAD//SYSPRIN T DD SYSOUT=*//SYSTSPR T DD SYSOUT=*//SYSTSIN DD *

DSN SYSTEM(DB2D)BIN D PLAN(CMXPLNE) MEMBER(CMXSQ1,CMXSQ2,CMXSQT) -

LIBRARY('CMX.SCMXDBRM') -ACTION(REPLACE) ISOLATION(UR) DYNAMICRULES(RUN) -ACQUIRE(USE) RELEASE(COMMIT) CURRENTDATA(NO) -KEEPDYNAMIC(YES)

RUN PROG(DSNTIAD) PLAN(DSNTIA51)END

/*//SYSI N DD *

GRANT EXECUTE ON PLAN CMXPLNE TO PUBLIC;COMMIT;

/*//

á ñ

Figure 10. JCL to BIND the Plan

4.3 Set Environmen t Variable s for CM and PM An important part of the installation process is to have all the necessaryenvironment variables set correctly for CM and PM. This section describesthose that are necessary for the install scripts to work correctly.


4.3.1 Set Environment Va riables for OS/390 Connection Scaling KitAttention

Since this change to the variables will be seen system-wide, you need tocheck with the OS/390 systems programmer to ensure you will not affect anyother users.

During the installation of the OS/390 UNIX System Services Connection ScalingKit, the following strings should have been added to /etc/profile:

Variable Value to be includedPATH /usr/lpp/bpa/binPATH /usr/lpp/cmx/binLIBPATH /usr/lpp/bpa/libLIBPATH /usr/lpp/cmx/libNLSPATH /usr/lpp/bpa/nls/msg/C/%NNLSPATH /usr/lpp/cmx/nls/msg/C/%N

Note: C and N must be capitalized. Sometimes these may be shown as %Lwhere the variable L has the value of C in the profile.

If these values are not set, you need to set them at this time by modifying theprofile in the /etc directory. To verify the setting, issue the following commands:echo $PATHecho $LIBPATHecho $NLSPATH

If the following line is commented out in the /etc/profile, you need to uncommentit:

1. Find the line: export _C89_INCDIRS=" /usr/include" , then add/usr/lpp/cmx/include to it so that it reads:export _C89_INCDIRS=" /usr/include /usr/lpp/cmx/include"

Note: The separator between the include directories is a space character.

2. Find the line with the eval command:eval "export $(typeset -x | grep "¬_C89_" | awk '{sub("_C89_","_CC_");printf "%s ",$0}')"

eval "export $(typeset -x | grep "¬_C89_" | awk '{sub("_C89_","_CXX_");printf "%s ",$0}')"

3. Find the line: export _C89_LIBDIRS=" /lib /usr/lib" , then add/usr/lpp/cmx/lib to it so it reads:export _C89_LIBDIRS= " /lib /usr/lib /usr/lpp/cmx/lib"

Note: The separators between the library directories (/lib,/usr/lib, and /usr/lpp/cmx/lib) are space characters.

Again, this change is seen systemwide, so you need to check with theinstallation systems programmer first before modifying the profile.

Chapter 4. Enabling UNIX System Services 35

4.4 Using a Second CMXPLAN NameFor the installation process, you must set DYNAMICRULES(RUN) in the BIND job;but later, to improve performance when running the application, you should setDYNAMICRULES(BIND).

To do this, you may want to set up two plans. If you are going to still be loadingnew companies you must create a second plan that has DYNAMICRULES(RUN),for user BSP.

The variable CMXCONF='Location of new plan', must be placed in either the.profile or the .bpaprofile for user BSP.

The steps to set up the second plan are:

Create a new configuration file:cp /etc/cmx/cmx.conf /etc/cmx/cmxrun.conf

Edit cmxrun.conf and change the plan name to CMXRUN.

Run the CMXBIND JCL to bind the DBRMLIB to the new plan name CMXRUN.

Add the variable CMXCONF=/etc/cmx/cmxrun.conf to the .profile of bsp.

Using a JCL job, or DB2 SPUFI, you must GRANT authority to PUBLIC for theplan name you have chosen (in our case, CMXRUN).


Chapter 5. BaanERP Applications Installation

This chapter is based on the installation process for BaanERP Applications onOS/390 and covers the following topics:

1. Allocating the installation, production, and user (storage) HFS data sets

2. Creating directories for mount points and mounting the HFS files

3. Unloading the BaanERP code from the CD-ROM

4. Set the Environment Variables

5. Executing the install6.2 script

6. Executing the db2_install6.2 script to create the DDL and Baan DB2 files

7. Connecting to BaanERP via the BW Client to complete the installation

8. Using the Baan log files

Ensure you follow the steps in the following documentation:

BaanERP - Installation Guide for BaanERP on OS/390 UNIX System Services

BaanERP - DB2 Installation Guide for BaanERP

Verify that DB2 is up and running before you start these steps. If you have torestart the installation, review the instructions in G.2.2, “Restarting install6.2from the Beginning” on page 144.

5.1 Allocation of the HFS FilesYou create the HFS using TSO, by executing the following steps:

1. Choose ISPF option 6, then issue the ish command.

The ish command gets you to the ishell so you can access USS files.

2. Press PF10 to put the cursor on the action bar (top of screen).

3. Tab to file_systems, then press Enter .

4. Enter 2 for new from the pull-down menu.

We entered the information shown in Figure 11 on page 38 to create ourthree HFS files.


à ðInstallation Library

File system name BAANERP.INSTALL.Primary Cylinders 3300Secondary cylinders 0Storage Class SCBAANManagement Class StandardData Class DCPDSE

Production LibraryFile system name BAANERP.APPL.BSEPrimary Cylinders 2700Secondary cylinders 0Storage Class SCBAANManagement Class StandardData Class DCPDSE

Storage LibraryFile system name BAANERP.CDROMPrimary Cylinders 1000Secondary cylinders 500Storage Class SCCOMPManagement Class StandardData Class DCPDSE

á ñFigure 11. Allocation HFS Files

Note: The storage class, management class and data class are the ones weset up for our system. Check with your OS/390 systems programmer for theproper storage class, management class, and data class to use.

5.2 Creating the Mount PointMount points are directories over which an HFS is mounted. An HFS cannot beaccessed though OS/390 UNIX System Services unless it has been mounted.

The member BPXPRM00 in SYS1.PARMLIB can be used to automatically mountthe HFS datasets at IPL time. Appendix A, “BPX Parameters” on page 111shows the BPXPRM00 we used in our installation. Refer to UNIX SystemServices Connection Scaling Reference for the suggested settings for BPXparameters for Baan.

Attention

In our sysplex environment we do not put LPAR-specific mount points inBPMXPARM in the SYS1.PARMLIB library because it is shared. We create astarted task that does the mkdir and mount commands for HFS files.

These mount points should be made permanent for the next IPL of yoursystem by updating your BPMXPARM, or by using the preceding procedure,or by using your own operational procedure.

To put this session into OS/390 UNIX System Services, again logon as ROOT,select option 6, and type omvs. Then create directories for the mount points,using the following commands:


5.2.1.1 Creating the Directory for the Installation Mount Pointcd /mkdir baanerpinstall

5.2.1.2 Creating the Directory for the Production Mount Pointcd /mkdir baanerp

5.2.1.3 Creating the Directory for the Storage Mount Pointcd /mkdir baanerpcdrom

At this point, issue the exit command at the prompt and press Enter .

5.2.2 Mounting the HFS FilesAn HFS file cannot be accessed through OS/390 UNIX System Services unless ithas been mounted. The HFS files must have been already allocated and themount point created before a mount point command can be issued.

As previously mentioned, member BPXPRM00 in SYS1.PARMLIB can be used toautomatically mount at IPL time. HFS files are manually mounted through TSO.To manually mount HFS files:

1. Logon to TSO.

2. Choose option 6 (commands).

3. Enter ish .

4. Press PF10 to go to the action bar.

5. Tab to file_systems, press Enter .

6. Choose 3 for mount on the pull-down menu.

7. Complete the menu to mount a file system.

Figure 12 through Figure 14 on page 40 show the information we entered forour three HFS files:

5.2.2.1 Mounting the Production HFS File

à ðMount Point /baanerpFile System Name BAANERP.APPL.BSEFile System Type HFSNew Owner ROOT

á ñ

Figure 12. Mount Production HFS File

Chapter 5. BaanERP Applications Installation 39

5.2.2.2 Mounting the Installation HFS File

à ðMount Point /baanerpinstallFile System Name BAANERP.INSTALLFile System Type HFSNew Owner ROOT

á ñ

Figure 13. Mount Installation HFS File

5.2.2.3 Mounting the Storage HFS File

à ðMount Point /baanerpcdromFile System Name BAANERP.CDROMFile System Type HFSNew Owner ROOT

á ñ

Figure 14. Mount Storage HFS File

5.3 Unloading the Baan CodeThe Baan code is delivered on a CD-ROM.

5.3.1 Setting Up to Load the Baan Software from the CD-ROMWe used the CD-ROM drive of an WINNT workstation to read the Baaninstallation files in order to move the files to the HFS file system on UNIX SystemServices for OS/390.

On the CD-ROM, we had the following two files:

appl.tar

port_390.pax

5.3.1.1 Moving the Files to OS/390 System ServiceWe used FTP to upload to S/390.

Issue the ftp command to connect to the OS/390 system: (substitute yourappropriate IP address)

ftp 9.12.14.207

User:

ROOT

Password: (use the RACF password for ROOT)

xxxx

At the FTP prompt, enter:

bin

This tells the FTP to send the file in binary mode:


cd /baanerpcdrom

This sets the TARGET directory (that is,the HFS directory the files from theCD-ROM are stored into):

put e:\appl.tar

put e:\port_390.pax

quit

We recommend you keep these installation files in directory /baanerpcdrom (onUNIX System Services) in case a restart from the beginning is required.

5.3.2 Unpacking Files into Install DirectoriesThe files must be unpacked in this specific order. The two files were unpackedinto the install directories by issuing the following commands in an OMVSsession on UNIX System Services:

cd /baanerpinstallpax -rvf /baanerpcdrom/appl.tar -o from=ISO8859-1,to=IBM-1047pax -rvf /baanerpcdrom/port_390.pax

Note: PAX is used on the appl.tar file because an ASCII-to-EBCIDIC conversionis required. These commands must be done in this order as some of the portingset files replace some application files that are required for OS/390.

The USS pax command can be used for tar files as well as pax files. Theinstallation libraries are ready for use at the completion of the pax commands.

Attention

Client code required in ASCII:

The /baanerp/bse/mswindows files come from the appl.tar file that has beenconverted from ASCII to EBCDIC. However, the mswindows files (and theInternet files) need to be in ASCII. Rather than convert the files back up fromEBCDIC back to ASCII using the ICONV command, we issued the pax.command again and used this temporary directory to retrieve the mswindowsand Internet files in ASCII, as follows.

mkdir /baanerp/asciicd /baanerppax -rvf /baancdrom/appl.tar

We then used the files in ln.0000/bse/mswindows and ln.0000/bse/internet toget an ASCII version of these files.

5.4 Set Environment Va riablesAn important part of the installation process is to have all the necessaryenvironment variables set correctly. This section describes those variables thatare necessary for the install scripts to work correctly.


5.4.1 Set Environment Va riables - OS/390 Connection Scaling KitThe environment variable required for the connection managers are described in4.3, “Set Environment Variables for CM and PM ger” on page 34.At this point, verify that they are correct using the echo command.

Variable Value to be includedPATH /usr/lpp/bpa/binPATH /usr/lpp/cmx/binLIBPATH /usr/lpp/bpa/libLIBPATH /usr/lpp/cmx/libNLSPATH /usr/lpp/bpa/nls/msg/C/%NNLSPATH /usr/lpp/cmx/nls/msg/C/%N

Note: C and N must be capitalized.

5.4.2 Set Environment Va riables - Installation of Baan ApplicationsTo use the install6.2 script, HEAP(24M) must be added to the variable_CEE_RUNOPTS. To set this up, enter:

_CEE_RUNOPTS=$_CEE_RUNOPTS' HEAP(24M)'export _CEE_RUNOPTS

Note: There is a space character before the word HEAP.

To verify, issue the following command:echo $_CEE_RUNOPTS

Note: The HEAP value of 24M in the _CEE_RUNOPTS was used for ourinstallation without any problems. If the HEAP value is not set correctly, theinstall6.2 script will abort the installation due to shared memory problems.

Various problems arose during our execution of the install6.2 script (could notfind modules) which were corrected by setting the values of $PATH and$LIBPATH to contain new directory entries.

Before running the install6.2 script, the following commands were used:export PATH=$PATH:/baanerp/bse/binexport LIBPATH=$LIBPATH:/baanerp/bse/bin:/baanerpinstall/install/bse/binexport TERM=vt100export _CEE_RUNOPTSexport _BPX_SHAREAS=YESexport _BPX_SPAWN_SCRIPT=YESexport DB2_MVS_SYNTAX=1export CMX_THREAD_WAIT=0

Check that at this point that BSE and BSE_TMP are not set. To verify allvariables are set correctly, enter the following command:

env

Following is our list of environment variables before we ran install6.2:


à ðroot @ SC55:/>env

_CXX_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/libMAIL=/usr/mail/rootHOSTNAME=SC55PATH=/bin:/usr/lpp/tcpip/sbin:/usr/lpp/tcpip/bin:.:/usr/lpp/bpa/bin:/usr/lpp/cmx/bin:/baanerp/bse/bin_CXX_INCDIRS=/usr/include /usr/lpp/cmx/include /usr/lpp/bpa/includeSHELL=/bin/sh

_CC_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/lib_CC_INCDIRS=/usr/include /usr/lpp/cmx/include /usr/lpp/bpa/includePS1=$LOGNAME @ $HOSTNAME:$PWD>

_CEE_RUNOPTS=$_CEE_RUNOPTS' HEAP(24M)',STACK(131072,131072,ANYWHERE,KEEP),ALL31(ON),TERMTHDACT(USDUMP)'_=/bin/env_BPXK_SETIBMOPT_TRANSPORT=TCPIPOE

LOGNAME=rootSTEPLIB=noneLANG=CLIBPATH=/lib:/usr/lib:.:/usr/lpp/bpa/lib:/baanerpinstall/install/bse/bin:/baanerp/bse/bin_C89_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/libTERM=vt100

_BPX_SHAREAS=YES_BPX_SPAWN_SCRIPT=YESDB2_MVS_SYNTAX=1_C89_INCDIRS=/usr/include /usr/lpp/cmx/include /usr/lpp/bpa/includeHOME=/

TZ=EST5EDTMANPATH=/usr/man/%LNLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lpp/bpa/nls/msg/C/%N:/usr/lpp/cmx/nls/msg/C/%NCMX_THREAD_WAIT=0

á ñ

5.5 Executing the install6.2 ScriptAt this point, verify that the proper DB2 subsystem is available. To begininstalling the Baan applications, you must telnet into the OS/390 system, logonas ROOT, then execute the following steps. (Make sure ROOT is in capitalletters and has the dbadm privilege.)

We found it was easier to use a telnet session product such as EXCEED fromHummingbird rather then using Windows telnet command. Others have usedproducts such as ONNET, Reflection, Powerterm, Simpterm, WTLENET, and soon.

Note: It is best to verify the shared memory is ready (by using the ipcscommand) and to check if you have dangling processes (by using the ps -efcommand). These processes could result from an aborted install (if this is thesecond time you are at this point, see G.2.2, “Restarting install6.2 from theBeginning” on page 144 for information on restarting the install6.2 script). Also,check that BSE and BSE_TMP are not set.

First change to the correct directory:cd /baanerpinstall

Then again check the environment variables TERM, _CEE_RUNOPTS, PATH,and LIBPATH. Issue the env command to check the environment settings.


Then to execute the install script, enter:. ./install6.2

Note: There is a blank between the two periods.

At this point the script will ask you many questions; 5.5.1, “Answering theQuestions in the install6.2 Script” describes the questions and ourresponses.

5.5.1 Answering the Questions in the install6.2 ScriptThe following series of screens show how we answered these questions:

1. To start the installation, issue the . ./install6.2 command and answer thequestions as follows:

à ðroot @ SC55:/baanerp/install>. ./install6.2

Installation started: Tue Apr 20 07:48:25 EDT 1999

Creating a temporary BSE, moment please

á ñ2. Creating a temporary BSE path:

à ðInstallation Program

Select file system to install the BSE directory onPlease enter the full pathname:/baanerp/bse

á ñ3. Creating a directory for BSE:

à ðDirectory not present, create ? Yes

á ñNote: If you do not get to this point successfully the first time because ofsetup problems, remove the files in baanerpinstall and re-issue the paxcommands to start over.

à ðInstallation Program

Select file system to install the BSE directory onPlease enter the full pathname:/baanerp/bse

The environment variable 'BSE_TMP' has been set to $BSE/tmp ok? Yes

Directory not present, create ? Yes

Continue? Yes

Press <ctrl Z> to display file systemá ñThe default that is displayed first is /usr/bse. Change this to the BSE pathyou plan to use; in our case, it is /baanerp/bse.


Note: The message Press <ctrl Z> to display file system at the bottom ofthe screen does not work in OS/390 at this time. The create directorymessage displays at the bottom of the screen if you have not already createdthis directory.

4. Path names (This is shown in three screens.)

à ðTHIS IS A FIRST INSTALLATIONBSE variables set to:

BSE=/baanerp/bseBSE_TMP=/baanerp/bse/tmpPATH=$BSE/bin:$PATH

Write BSE variables to /etc/profile ? NoWrite BSE variable to profiles of user ? No

Continue? Yesá ñAt this point, you should answer no or else ASCII information will be added toexisting EBCDIC profile files.

5. Host name

à ðEnter 'hosts' for which license is required (e.g. sys1,sys2, etc)

Hosts: wtsc55oe (example)

Continue? Yesá ñThe host name should be the same as the one in the /etc/resolv.conf and/etc/host files.

Note: We found that we had to ensure that the hostname was in lowercasein all files including the file $BSE/lib/licence6.2 after the installation.

6. Database driver

à ðPresent database drivers:

1 db2 2 db2400Which database driver do you want to use for:

Company 000 1

Enter the value of environment variable DB2INSTANCE (your SSID)Give instance: DB2D

á ñYou are asked the same question for each company. We have not showedeach screen. After answering the question several times, the followingscreen is displayed.


à ð

Selected drivers:

Comp Driver

000 db2(DB2INSTANCE=DB2D)813 db2(DB2INSTANCE=DB2D)900 db2(DB2INSTANCE=DB2D)

Continue? Yes

á ñ7. Directory table path

à ðSelect file system to install the DICTIONARY table definitionPlease enter the full pathname:/baanerp/dict

Press <Ctrl> Z to display filesystem

Directory not present, create Yesá ñAgain the message Press <Ctrl Z> does not work for OS/390.

8. Operational table and dump table paths

These questions are repeated for tables and dumps.

à ðSelect file system to install the DICTIONARY table definitionsPlease enter the full pathname:/baanerp/dict

Select file system to install the dumps of the demo tablesPlease enter the full pathname:/baanerp/test

Directory not present, create Yes

Continue? Yes

á ñWe were asked to confirm (answer Yes) that we wanted to create each ofthese directories.

Note: These files are not in the $BSE path. This is to make it easier tomove these to a different file system later if required.

9. Choice of vrc


à ðWhich vrc of package bc do you want in the package combination

Version Release Customer Description

1 B50 b Conversion2 B50U b stnd Conversion

Enter vrc: 2

Continue? Yes

á ñThis question will show the highest version that is available. You shouldcheck with the Baan Consultant to decide what version you should choose.We were told to choose the highest version VRC for the version you areinstalling.

In this case, the version number is u and the release number is 2. Thisquestion was repeated for packages cf, ci, cp, dc, ec, ed, qm, tc, td, tf, tg, ti,tp, ts, tu, and wh.

10. Package combination

After answering this question for all packages you will have the list ofpackages that will be installed, as shown in Figure 15 on page 48.


à ðGive package combination to create

Package Combination : b50bDescription : BaanERP_B50b

Following package(s) will be installed:ttB50_b_____Tools_B50_bbcB50_b_____ConversionbcB50Ub_stndConversioncfB50_b_____ConfiguratorcfB50Ub_stndConfiguratorciB50_b_____Central_InvoicingciB50Ub_stndInvoicingcpB50_b_____Constraint_PlanningcpB50Ub_stndConstr._PlanningdcB50_b_____Development_ControldcB50Ub_stndDev.ContrlecB50_b_____Electr._CommerceecB50Ub_stndElec._CommerceedB50_b_____Enterprise_Mod.DataedB50Ub_stndDEM_dataqmB50_b_____Quality_ManagementqmB50Ub_stndQualitytcB50_b_____CommontcB50Ub_stndCommontdB50_b_____DistributiontdB50Ub_stndDistributiontfB50_b_____FinancetfB50Ub_stndFinancetgB50_b_____OrgwaretgB50Ub_stndOrgwaretiB50_b_____ManufacturingtiB50Ub_stndManufacturingtpB50_b_____ProjecttpB50Ub_stndProjecttsB50_b_____ServicetsB50Ub_stndServicetuB50_b_____UtilitiestuB50Ub_stndUtilitieswhB50_b_____WarehousingWhB50Ub_stndWarehousing

Continue? Yesá ñFigure 15. Package Combinations to Create

11. Choice for Multi bshell

à ðDo you want to run multiple bshells to speed up the installation? No

(You MUST say NO for S/390)

Continue? Yesá ñNote: This is not supported on S/390.

12. Choice for Multi Byte:


à ðDo you want to run Multi Byte ? No

Continue? Yesá ñ

13. Ready to install? Change the default of No to Yes.

à ðAre you ready for installation? Yes

Installation started...

Moving files...

á ñThis change takes several minutes. The yes may be displayed in only twocharacters, first ye and then es . Press Enter to continue.

14. Ready to set up DB2 files:

à ðInitialize your db2 parameters by using db2_install6.2.

Initializing for environment variables:DB2INSTANCE=DB2D

After initializing type 'exit' to return.

Go to shell? Yes

á ñ

15. Answering the go to shell question :

At this point you can answer yes to go to the shell to execute thedb2_install6.2 script or you can start another telnet session to execute thedb2_install6.2 script to set up DB2 files, as described in Appendix D,“Executing the db2_install6.2 Script” on page 121. If you go to anothersession, you must reset BSE and BSE_TMP.

Before proceeding, we used JCL to do the following:

Create a STOGROUP, database and tablespace for Company 000

Grant access to all three

We were advised not just to copy our Baan db2 files from BaanIVc in casethe format had changed, so we used the the db2_install.2 to create thedb2_user, db2_group and db2_storage files.

5.5.2 Using the db2install6.2 ScriptThis section describes how we used the db2_install6.2 script to set up a simpleconfiguration to create the DB2 environment. You can use this script to provideyour customized environment, or you can use the sample JCL and db2_(files)that are provided by Baan.


The script db2_install6.2 is designed to assist you in creation of the DB2environment to:

Perform DB2 system administration tasks such as:Create the DB2 databasesCreate tablespaces in the databaseGrant dbadm authority to the user IDs

We did not use these features.

Create the control files required by Baan to load the data for Company 000and the Demo companies

db2_groupdb2_usersdb2_storage

We used the script to create these three files.

The following screens show the questions and answers we used to create thedb2_(files). We took the defaults whenever we could.

Attention

Be patient in replying to the questions, as generally the script will provide adefault answer after a few seconds. Also, do not type Yes and then pressEnter as the enter will be taken as the answer to the following question.Instead, just type Y or N.

This is the first screen:

à ðDB2 Server Installation

Before invoking this script, a DB2 subsystem must have been defined

This script will do following things for the DB2 subsystem.

- Create storage group and grant privileges to use thestorage group.

- Create database and grant privileges on database.- Create tablespace and grant privileges to use the tablespace- Create group and user files.

Add initial group to group file.Add users root, bsp, ROOT, and BSP to group.

- Create storage file.Add default entries for table & index to storage file.

Note: Check db2_inst.log in the current directory for any errorRead Installation Document Carefully regarding specification

of DB2 for OS/390.O.K to continue ? Y

á ñ


5.5.3 Listing Environment VariablesThis screen shows the environment variables.

à ðEnvironment Variables

*** db2_install6.2 Started ***

- HOST wtsc55oe

- LOGNAME root

- BSE /baanerp/bse

Press any key .

á ñ

Note: If you have not installed the hostname command as described inAppendix C, “The hostname Command” on page 119, you will get the followingerror message but it will not cause any problem:

hostname: initial_setup: db2_install6.2 1677: FSUM7351 not found:

If you have gone to the shell you will not see a LOGNAME, and the errormessage might change the structure of the messages but you can continuewithout a problem.

At this point there are a series of questions to answer about the layout of yourdatabase. The order of the questions will change, depending on how youanswer these questions. Remember not to press Enter; instead, just type y or n.A single key stroke is all that is necessary.

5.5.4 Storage Group CreationThese are the questions you must answer to create the STOGROUP if you wantthe Baan db2_install6.2 script to do this for you.

5.5.4.1 Creating STOGROUPSince we had used JCL to create our STOGROUP BERPGRP, we answered N.

à ðStorage Group Creation

Want to create storage groups (Y?N) ? N

á ñ

5.5.4.2 Creating a DatabaseSince we had used JCL and DDL to create our database, we answered N.

à ðDatabase Creation

Want to create a database (Y?N) ? Ná ñ


5.5.4.3 Tablespace CreationSince we used JCL and DDL to create our tablespace, we answered N.

à ðTablespace Creation

Want to create a database (Y?N) ? Ná ñ

5.5.5 Creating DB2 Reference Files for the Baan ScriptThis step creates three files that the Baan install6.2 script uses to build and loadthe database. We used the db2_install6.2 script to create the three db2_(files).

5.5.5.1 Group file CreationThe following will create db2_groups.

à ðGroup File Creation

Want to create initial group (Y/N)? Y

á ñ

à ð

Group File Creation

Initial Group : db2berp

Group Password : db2berp

Is above data correct (Y/N) ? Y

Add group “db2berp” (Y/N) ? Y

Adding group “db2berp”Group added.

Press any key .

á ñ

5.5.5.2 Creating the User FileThe following will create db2_users.

à ðUser File Creation

Add users "root", "bsp", "ROOT", "BSP" (Y /N) ? Y

á ñ


à ð

User File Creation

dd Baan user “root” to Group “db2berp” (Y/N) ? Y

DB User : root

Adding user “root” to group “db2berp”User added to group.

Press any keyá ñ

This is repeated four times, once for each user: bsp, BSP, root, and ROOT.

à ð

User File Creation

Add other users (Y/N)? N

á ñ

5.5.5.3 Creating the Storage FileThe following will create db2_storage.

Note: We did not specify any particular tablespaces at this time for Company000, and the script used the defaults of * *.

à ð

Storage File Creation

Create db2_storage Entries ? Y

á ñ

à ðDo you want to specify Company Data ? Y

Update Index Parameters

Company: * Table spec: *

Current Index parameters:

STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP0Do you wish to modify ? N

'/baanerp/bse/lib/db2/db2_storage' updated successfulCompany: * , Table: *

á ñ

Then we got the message that the script had completed.


à ðdb2_install6.2 completedbshell6.2> exit

á ñ

5.5.5.4 Files Baan Will Use to Define the DatabaseAfter the script has been run, the following files will be in directory/baanerp/bse/lib/db2:

à ð$ ls


This is db2_storage:

à ð*:*:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP0*:*:T:group:01:5: ARR_SIZE 1 OPT_ROWS 5 T_SPACE BERP000.TS000..

á ñ

This is db2_groups:


á ñ

This is db2_users:

à ðBSP:BSP:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:db2berpbsp:bsp:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:db2berproot:root:&l%d(43‘"Bd5g+jaj2I1/o,-0H){c3:E:db2berpROOT:ROOT:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:db2berp

á ñ

5.5.6 Continuing with the install6.2 ScriptTo continue with the installation:

Go back to original telnet and respond: yes . Then, the following messageswill appear:

à ðInitialize your db2 parameters by using db2_install6.2.

Initializing for environment variables:DB2INSTANCE=DB2D

After initializing type 'exit' to return.

Go to shell? Yes

Continue: Yes

Setting permissions, moment please...

á ñStarting Bshell

Just before the load starts,you will get the following messages:


à ðStop shared memory for temporary environment...

Running rc.start for BSE environment

BUFSZ 4194304, MAXATTCH 30, START 0x18000000, STEP 0x400000Start /baanerp/bse/bin/shmtimer6.2:

Starting successfulá ñContinuing with the BW Client

Check that the profile for root reflects the correct values. The followingscreen will ask you to go to the BW Client:

à ðInstallation interrupted: Fri Apr 23 08:53:53 EDT 1999You can use BI or BW to continue the installation

When using BI:------------------------------------------------------------------------------

- install BI on your HTTP server- copy the HTML page '/baanerpinstall/install.html'

to the BI subdirectory 'client'- start your internet browser and select page 'install.html'

------------------------------------------------------------------------------

When using BW:------------------------------------------------------------------------------

- install BW on your workstation (from /baanerp/bse/mswindows)- start BW using the following configuration:

Hostname: wtsc55oeConnect As: rootBSE: /baanerp/bseBshell name: bshell.instCommand: -- ottiex1287 /baanerpinstall

------------------------------------------------------------------------------

When BI or BW has finished executing, you can continue this installationContinue? (y/n):

á ñ

5.5.7 Changes before ContinuingWe made the following changes according to the release notes:

Change the s to p in the fifth column for sh_server in the file/$BSE/lib/ipc_info.

à ðbshell s 0 0 p ${BSE}/bin/bshell6.2bshell.inst s 0 0 p ${BSE}/bin/bshell_inst6.2audit s 501 510 p ${BSE}/bin/audit_srv6.2sh_server s 0 0 p ${BSE}/bin/sh_server6.2fs6.2 s 303 335 m ${BSE}/bin/fs6.2nserver s 0 0 s ${BSE}/bin/nserver6.2db2 s 310 301 p ${BSE}/bin/db2_srv6.2db2400 s 307 370 s ${BSE}/bin/db4_srv6.2

á ñChange a field in uROOT file.

Edit the file $BSE/lib/user/uROOT and change the field from

pacc:Install to pacc:b50b .

We found it was easier to edit these files by using the ish menus rather thanusing the vi editor.


5.5.8 Configure the BW ClientYou must set up a BW Client to use for the rest of the installation process. Theprocedure to set up a BW Client is described in Chapter 6, “Client ConnectionConfigurations” on page 65. Enter the fields as shown for hostname, Bshellenvironment, then press RUN! as shown in Figure 16.

Figure 16. BaanERP Configuration Panel

5.5.8.1 Enter the Logon PasswordYou are asked if you want to save your configuration, and then you will bepresented with the logon screen, as shown in Figure 17.

Figure 17. Baan Logon Panel


5.5.8.2 Wait for the Installation Process to ContinueAs shown in Figure 18, the Baan initialization panel will appear for 10 to 15seconds.

Figure 18. Baan Initialization Panel

5.5.8.3 Continuing the Installation ProcessThe following series of screens appears as the load process continues for thenext hour.

Figure 19. Importing Data Dictionary


Figure 20. Creating New Tables

Figure 21. Starting Baan Module ottadv5211


Figure 22. Creating Table Definitions

Messages during the Load Phase: In our system, after one hour and a half wehad the following message:

Figure 23. Message about User ROOT

As instructed in the release notes, we pressed OK and received the followingmessage:

Figure 24. Message about User BSP

We pressed OK and the database load continued.


After 15 hours or so, we received the following messages:

Figure 25. Installation Has Completed

Figure 26. Baan Message to Return to Window

You can monitor the process of the load phase by checking the entries in the file/baanerp/bse/log/log.oiex1288. There are 32 programs to run that start withln.00xx. If you find that the load is going very slowly, check to make sure youhave used the OPT_ROWS 5 option for the tables in the db2_storage file.

If you have to log off the ROOT user ID and restart the install6.2 script, you mustexecute the following steps:

1. export BSE=/baanerp/bse.

2. export BSE_TMP=/baanerp/bse/tmp.

3. export DB_AS=bshell.inst.

4. Change the pacc option in the uROOT file from install to b50b.

5.5.9 Completing the InstallationThe length of time needed to load Company 000 varies, depending upon thefollowing:

The number of DB2 Workfiles (DSNDB07) and the number of packs they aredistributed on

The amount of central storage your OS/390 has

The amount of expanded storage your OS/390 has


The number of CPs allocated to your LPAR

At this point, return to the ASCII window and reply yes . The install6.2 script willfinish.

à ðInstallation interrupted: Fri Apr 23 08:53:53 EDT 1999You can use BI or BW to continue the installation

When using BI:-------------------------------------------------------------------------

- install BI on your HTTP server- copy the HTML page '/baanerpinstall/install.html'

to the BI subdirectory 'client'- start your internet browser and select page 'install.html'

-------------------------------------------------------------------------

When using BW:-------------------------------------------------------------------------

- install BW on your workstation (from /baanerp/bse/mswindows)- start BW using the following configuration:

Hostname: wtsc55oeConnect As: rootBSE: /baanerp/bseBshell name: bshell.instCommand: -- ottiex1287 /baanerpinstall

-------------------------------------------------------------------------

When BI or BW has finished executing, you can continue this installationContinue? (y/n): Yes

á ñ

After entering Yes, you will get the following messages:

à ðInstallation continued: Tue May 4 08:49:42 EDT 1999

pdaemon6.2: Lpcmd /baanerp/bse/bin/lp6.2 changed to mode 0755pdaemon6.2: /baanerp/bse/bin/pdaemon6.2 started.

Installation Completedá ñ

At this point you are ready to load the demo database.

The steps are:

1. First make a backup copy of the DB2 database.

2. Set up the profile for bsp.

3. Logon to Baan using the BW Client and user ID bsp.

4. Load the demo companies.

5. Run RUNSTATS on Company 000.

You can log off from ROOT and logon on to the bsp user ID as long as you haveset up the correct profile for bsp as described in 5.6, “Setting Up the Profile forbsp User ID” on page 62.


5.6 Setting Up the Profile for bsp User IDAfter Company 000 was loaded, we set up the profile for user bsp, as shown inFigure 27. Then you can proceed to set up the Baan Windows client for userbsp and then install the demo companies.

The environment variables we set for the bsp user are shown in Figure 27.

à ð_CXX_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/libMAIL=/usr/mail/bspHOSTNAME=SC55PATH=/bin:/usr/lpp/tcpip/sbin:/usr/lpp/tcpip/bin:.:/usr/lpp/bpa/bin:/usr/lpp/cmx/bin_CXX_INCDIRS=/usr/include /usr/lpp/cmx/includeSHELL=/bin/sh_CC_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/lib_CC_INCDIRS=/usr/include /usr/lpp/cmx/includePS1=$LOGNAME @ $HOSTNAME:$PWD>_CEE_RUNOPTS=HEAP(24M) AL(ON) ENVAR("_BPXK_SETIBMOPT_TRANSPORT=TCPIPOE") POS(ON)_=/bin/env_BPXK_SETIBMOPT_TRANSPORT=TCPIPOELOGNAME=bspSTEPLIB=noneLANG=CLIBPATH=/lib:/usr/lib:.:/usr/lpp/bpa/lib_C89_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/libTERM=vt100_BPX_SHAREAS=YES_C89_INCDIRS=/usr/include /usr/lpp/cmx/includeHOME=/baanerp/bseTZ=EST5EDTMANPATH=/usr/man/%LNLSPATH=/usr/lib/nls/msg/C/%N:/usr/lpp/bpa/nls/msg/C/%N

export _CEE_RUNOPTS="HEAP(24M,1M,ANYWHERE,KEEP),STACK(131072,131072,ANYWHERE,KEEP),ALL31(ON),LIBSTACK(8),TERMTHDACT(UADUMP)"export TERM=vt100

export DB2_MVS_SYNTAX=1export _BPX_SHAREAS=YESexport _BPX_SPAWN_SCRIPT=YES

export PATH=$PATH:/baanerp/bse/binexport LIBPATH=$LIBPATH:/baanerp/bse/binexport BSE=/baanerp/bseexport BSE_TMP=$BSE/tmp

á ñ

Figure 27. Environment Variables for bsp User

5.7 Starting the Baan Application ManuallyThe Baan applications are started as part of the successful load of Company 000.If at some time you must start the Baan applications manually, change directoryto the $BSE/etc directory and issue the command: rc.start .

This initializes the Baan production environment, as shown in Figure 28 onpage 63


à ðroot @ SC55:/baanerp/bse/etc>rc.startInitializing...

Initialize Shared Memory

Shared Memory still running

Initializing Licence Daemon...

Initialize Printer Daemon

Printer Daemon Initialized

á ñ

Figure 28. Starting the Baan Applications Manually

The command rc.stop is used to stop the Baan applications.



Chapter 6. Client Connection Configurations

This chapter describes how we set up the Baan client. There are two types ofBaanERP clients:

BW For Baan Windows 95 Client

BI For the Baan Internet Client

We used the BW and BI Clients for our installation. The setup for the BW Clientis described in Chapter 7, “Install the bi Client and Set Up the Webserver onS/390” on page 71.

6.1 Setting Up the BW Baan Client Code on a Windows 95 C lientAfter the moving files section of the installation process (about 15 or 20 minutesinto the process), you are asked to continue the installation using the BW Client.At this point, the BaanERP client code was found in the/baanerp/bse/mswindows directory after the installation is completed.

Attention

Client code required in ASCII

The /baanerp/bse/mswindows files come from the appl.tar file that has beenconverted from ASCII to EBCDIC. However, the mswindows files (and theInternet files) need to be in ASCII. Rather than convert the files back up fromEBCDIC back to ASCII using the ICONV command, we issued the pax paxcommand again and used this temporary directory to retrieve the mswindowsand Internet files in ASCII.

mkdir /baanerp/asciicd /baanerppax -rvf /baancdrom/appl.tar

We then used the files in ln.0000/bse/mswindows and ln.0000/bse/internet toget an ASCII versions of these files. There are instructions in the BaanERPrelease notes for another method to convert the file from EBCIDIC to ASCII;refer to 2.4, “BaanERP for OS/390 Release Notes” on page 20.

The steps to follow are:

1. FTP the code to the Baan client (a PC running Windows 95).

2. Store the file in a directory, for example c:\baanbw.

3. Issue the command setup to explode the file into 12 files.

4. In this directory, issue the setup command.

When the client code is successfully installed, a message appears to say the bwsoftware installation is complete, as shown in Figure 29 on page 66.

Next, follow the steps in 6.2, “Configuring the Baan Client” on page 67.


Figure 29. Successful Installation of Baan Client

6.1.1 Getting the Baan Client from the FTP SiteAnother source of the Baan client code is the Baan FTP Web site. From anetwork browser:

1. Issue the following command:ftp://support.baan.com/updates/B50/bw50/

2. Select the latest appropriate version; we chose: bw5intel113

3. Store the file in a directory, for example c:\baanbw.

4. Execute this (self-exploding) file.

5. Issue the setup command (created in step 4).

This will create the Baan Environment and Configuration Selector window, asshown in Figure 30 on page 67.

Next, follow the steps in 6.2, “Configuring the Baan Client” on page 67. Awindow is opened to display the Baan Configuration Screen: Figure 30 onpage 67.


Figure 30. Baan Environment and Configuration Selector Window

To configure the connection from the client to the S/390, follow the steps in 6.2,“Configuring the Baan Client.”

6.2 Configuring the Baan ClientTo complete this configuration, the following information is required:

Host name or IP address of the S/390Baan user IDPasswordPath for $BSE

From the Window shown in Figure 30, click the BW5intel line icon. This givesyou a screen to input the connection parameters and creates a file used toestablish connectivity to the application, as shown in Figure 31 on page 68.

6.3 Connecting as bspAfter the installation phase is completed, the steps to complete the configurationare:

1. Check that the .profile for bsp is in the home directory.

2. Click the BW5intel line and the screen shown in Figure 31 on page 68 willappear.

3. Input the host name: wtsc55oe

4. Input the connect ID: bsp

5. Choose use saved password .

Chapter 6. Client Connection Configurations 67

6. Input the password: xxxxxx

7. Input the BSE: /baanerp/bse

8. Choose Save .

9. Choose Close to close the configuration.

Figure 31. Configuring the Baan Client

Now click the Baan application icon to access the Baan applications, or clickRUN. This takes a few moments.

If this step is not successful, you should check the following:

Telnet for OMVS is running (the INETD process).

The user IDs are in RACF.

Try the user ID in uppercase.

The permissions of the /baanerp files are bsp:bsp.

After selecting Run! , the following screen will appear for about 10 seconds:


Figure 32. Connecting to the Baan Client

After this, the Baan Application screen appears; refer to Figure 33.

Figure 33. Client Connection Completed to Baan

Chapter 6. Client Connection Configurations 69

To navigate through the Baan file folders:

Double-click down through the file folders until you get to the application youwant to execute.

Double-click on the executable icon.

Note: Users have to be created in Baan in lowercase for BaanERP.


Chapter 7. Install the bi Client and Set Up the Webserver on S/390

To enable the bi client for BaanERP applications, do the following:

1. Set up a Webserver.

2. Install Java on the system that will have the BI HTTP server

3. Set up the BI HTTP server.

4. Set up the client workstation.

The Baan reference for this is BaanERP Internet Server Installation and ConfigGuide Document Information, Code: U7089A.

The Baan code you require is found in the directory /baanerp/bse/internet. Yourequire the ASCII format for this file. If you have not created a separate HFSwith the ASCII format of the Baan code, you will have to issue the iconvcommand for five of the files as noted in 7.2.2, “HTTP Server Installation” onpage 72. The BI HTTP server requires the files to be in ASCII. The fourelements of this solution are:

______________ ___________________________________________________| | | Web Server . BI HTTP Server . Baan Application || Browser | | . . || |____| listening . listening . || SDKAFC10 code| | on port 80 . on port 1180 . || | | . . || | | . rexec logon to .-----> bshell ||______________| |___________________________________________________|

Client S/390 UNIX System Services

7.1 Set Up a S/390 WebServerIn our case, we used a S/390 Webserver. The steps we followed to set up thisS/390 Webserver are provided in Chapter 8, “Cloning/Customizing the HTTPServer for OS/390” on page 83. Tests have also been done with an NTWebserver.

The WEBBAAN procedure in SYS1.PROCLIB we used to start our Webserver isshown in 7.5.2, “Started Procedure for Webserver” on page 81.

7.2 Set Up the BI HTTP ServerTo set up the BI HTTP server you must do the following:

Create a user ID with a home directory (in our case BAANWEB and/u/baanweb).

Create a .profile, as shown in 7.2.1, “Profile” on page 72.

Move the /baanerp/bse/internet/bisetup.class file to the home directory.

Start Java.

Export the DISPLAY for GUI interface.

Execute the bi.setup class file.


Change the name of the bi.html file to bi.html.ascii.

Choose port numbers (our Webserver was listening on 9.12.2.10:80 and ourBI HTTP server was listening on 9.12.2.10:1180).

Edit bi.html.ascii to point to the Baan bshell.

Move files to the /web/baan/pub directory.

Note: The Baan applet is signed, so it will work in this configuration.

7.2.1 ProfileIn our case, we created a user ID BAANWEB to install the Baan BI HTTP server.Following are the entries we added to the .profile in the home directory/u/baanweb.

à ð# ====================================================# Java section# ====================================================export PATH=/usr/lpp/java/J1.1/bin:$PATH:.export CLASSPATH=/usr/lpp/java/J1.1/lib/classes.zip:.export LIBPATH=/usr/lpp/java/J1.1/lib/mvs/native_threads::$LIBPATH# ====================================================# Java servlet support# ====================================================export JAVA_HOME=/usr/lpp/java/J1.1#umask 022# End of Java section# ====================================================

# ====================================================# Your personal settings# ====================================================export CLASSPATH=/u/baanweb:$CLASSPATH# ====================================================echo PATH : $PATHecho LIBPATH : $LIBPATHecho CLASSPATH : $CLASSPATHecho LD_LIBRARY_PATH: $LD_LIBRARY_PATHecho STEPLIB : $STEPLIB# ====================================================

á ñ

7.2.2 HTTP Server InstallationTo install an HTTP server, go to a S/390 LPAR with Webserver installed andstarted. Logon with the user ID BAANWEB, then do the following:

Create directory /u/baanweb

cd /u/baanweb

FTP (or copy) BiSetup.class from the Baan application server/baanerp/bse/internet (make sure it is an ASCII version).

The BiSetup expects a GUI interface, so we had to use the EXCEEDHummingbird PC X server product. We started EXCEED and then issued thefollowing command, using the IP address of the PC we were using.

export DISPLAY=9.12.14.80:0

Note: To obtain the IP address of our workstation, we first issued thecommand netstat -a to get the host name (which was syslab02), and then


we issued the command ping syslab02 , which gave us the IP address (in ourcase 9.12.14.80).

Start Java. Check that Java is installed on your system and then start Javaby issuing the following commands:

à ðcd /usr/lpp/java/J1.1/binBAANWEB:/u/baanweb: >java -fullversion (or ./.java -fullversion)java -fullversion"JDK 1.1.6 IBM build m116-19981201 R04 (JIT enabled: ji

á ñExecute bisetup

Change the directory using the command:cd /u/baanweb

Note: Ensure that /u/baanweb is part of the Classpath or you will get themessage: Can't find class bisetup . You should not get the message if youhave the following statement in your .profile:

export CLASSPATH=$CLASSPATH:/u/baanweb

Check that you have an XWindows session running, then issue the followingcommand to set up the BI Server:

à ðBAANWEB:/u/baanweb: >java bisetup

á ñInitially we did not have the XWindows interface, so we received thesemessages:

à ðInstallShield JavaTM Edition

Extracting installation code...............................doneSorry, could not extract this archivejava.lang.InternalError: Can't connect to X11 window server using ':0.0'value of the DISPLAY variable.

at sun.awt.motif.MToolkit.<init>(Compiled Code)at java.awt.Toolkit.getDefaultToolkit(Compiled Code)at java.awt.Font.initializeFont(Compiled Code)at java.awt.Font.<init>(Compiled Code)at installshield.jshield.runtime.InfoContainer.load(Compiled Codeat installshield.jshield.runtime.InfoContainer.equals(Compiled Coat bisetup.initiateGUI(Compiled Code)at bisetup.<init>(Compiled Code)at bisetup.main(Compiled Code)

á ñ

Chapter 7. Install the bi Client and Set Up the Webserver on S/390 73

After installing and starting the Xwindows interface and reissuing thecommand java bisetup , the graphical interface will display the followingscreens as it creates the BI Server. You may have to go to the XWindowswindow manually to see the screen shown in Figure 34 It will be hidden inanother window.

Figure 34. Graphical Window Displayed while Setting Up BI HTTP Server

Continue by clicking Next , and you will see the screen shown in Figure 35 onpage 75.


Figure 35. Instructions for Sett Up of BI HTTP Server

On this display, enter the path where you want the BI Server to be installed.In our case, it was /u/baanweb, as shown in Figure 36.

Figure 36. Location for BI HTTP Server Program


When you receive this screen, the graphical interface part of the installationis complete. Click Finish to return to the telnet session.

Figure 37. Completion of Setting Up BI HTTP Server

This has put one file (uninstall.class) and three directories (install.idb, client,and server) into /u/baanweb.

Customize the html file.

Go to the client directory by issuing the command: cd /u/baanweb/client

Attention

You need ASCII version of some the files in the client directory.

These files are found originally in the $BSE/internet directory. They areconverted to EBCDIC as part of the installation process. but need to bein ASCII. You can create an ASCII copy of the Baan files, by issuing thepax command without the conversion options that are shown in 5.3.2,“Unpacking Files into Install Directories” on page 41.

Alternatively, if your bi.html file is in EBCDIC after the installation, andneeds to be in ASCII, you can issue the commands:iconv -f IBM-1047 -t ISO8859-1 <bi .html bi.html.ascii >iconv -f IBM-1047 -t ISO8859-1 <bi .help bi.help.ascii >iconv -f IBM-1047 -t ISO8859-1 <bi.graphics32.html graphics32.html.ascii

>iconv -f IBM-1047 -t ISO8859-1 <readme.txt readme.txt.ascii >iconv -f IBM-1047 -t ISO8859-1 <BIautomatio.html

BIautomation.html.ascii >

Edit the bi.html file. Use either the oedit bi.html.ascii command or theviascii bi.html command.


Note: Since bi.html is in ASCII, we found it easier to logon through a telnetsession and use viascii to edit bi.html. The command viascii can bedownloaded from the Web. See Appendix B, “The vi Editor and CommonUNIX Commands” on page 115 for more information.

Change the path to /baanerp/bse and the port to 1180. File to save the newconfig file as bi.html.ascii.

Copy the files to the pub directory:

à ðcp /u/baanweb/client/bi.html.ascii /web/baan/pub/bi.html.asciicp /u/baanweb/client/netscape/bi.jar /web/baan/pub/netscpae/bi.jarcp /u/baanweb/client/ie4/bi.cab /web/baan/pub/ie4/bi.cabcp /u/baanweb/client/ie4/grid.cab /web/baan/pub/ie4/grid.cabcp /u/baanweb/client/ie4/ssl.cab /web/baan/pub/ie4/ssl.cab

á ñ

7.2.3 HTTP Server ConfigurationFigure 38 on page 78 shows the bi.html.ascii file after we made the changes.We found it was easier to use viascii to edit this file.

Copy the file /u/baanweb/bi.html to /web/baan/pub/bi.html.ascii and makethe changes to the BSE VALUE and PORT VALUE as shown in Figure 38 onpage 78.

Note: If the Webserver is on a different host, change the HOSTNAME valueas well.


à ð<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"><HTML><HEAD><TITLE>Bi Startup Page</TITLE><style type="text/css"></style> </head>

<body bgcolor="#FFFFFF">

<p id="p1"><span id="s1">BI Server</span> </p>

<p id="p2"><span id="s2">Enter your configuration here</span> </p>

<hr noshade size="2">

<applet code="BiLogon.class" archive="netscape/bi.jar" width="559"height="360">

<PARAM NAME=cabinets VALUE="ie4/bi.cab, ie4/grid.cab,ie4/ssl.cab"><PARAM NAME=BSE VALUE=/baanerp/bse><PARAM NAME=BSHELL VALUE=bshell><PARAM NAME=COMMAND VALUE=""><PARAM NAME=SECURITY VALUE=NONE><PARAM NAME=HOSTNAME VALUE=""><PARAM NAME=PORT VALUE=1180><PARAM NAME=CONFIG VALUE=BI><PARAM NAME=AUTOMATION VALUE=true><PARAM NAME=DEBUG VALUE="-window-connection-messages-events-objects">

</applet><HR noshade size="2"></BODY></HTML>

á ñFigure 38. Changing the bi.html File

7.2.4 Starting the BI HTTP ServerTo start the BI HTTP server, open an omvs session and enter the followingcommands:

cd /u/baanwebjava -Dfile.encoding=8859_1 BiServer -l bi.log -c -t 3 -p 1180 -a wtsc04oe


Port 1180 is the port number where the BI Server is listening. This will tie up thetelnet session, so you may want to start the BI HTTP Server as a started task asshown in 7.5, “Started Procedures” on page 80.

7.3 Client InstallationFor the client installation, you need either Internet Explorer (version 4.01 orhigher) or the Netscape browser (version 4.04 or higher).

7.3.1 Using NetscapeTo prepare to use the Netscape browser, do the following:

Get the SDKAFC10.exe file.

− Go to www.microsoft.com/java

− Click Download .

− Scroll down to the bottom of the page.

− Click Microsoft SDK for APC 10 .

The file you need to download is on the last line of the MicrosoftWebpage that is shown in Figure 39.

Figure 39. Choice of Microsoft SDK for APF 10

− Download this file to a directory on your PC (such as c:\msoft).

− Execute the file SDKAFC10.exe Without this code, the Logon button willnot activate.

Check that you have Java 1.1.5 on your browser by searching the top line ofthe Netscape browser and clicking communicator , then tools and javaconsole .


To start the Netscape browser, do the following:

At the URL line, enter the following address, where 9.12.2.10 is the IPaddress of the Webserver and the bi.html.ascii file points to the BI HTTPserver:

http://9.12.2.10:80/bi.html.ascii

When prompted by Type Logon , enter a valid Baan user ID such as baan0 .

When prompted by Type Password , enter the RACF password for baan0.

Note: When using Netscape on the client, you will get the following pop-upwindow message:

The application ottstpoledaemon (pid=1) is using a feature(Automation not available - Must run on MS Windows with MS VM)that is not supported by BI. Application will be killed.

However, the menu browser is then displayed and you can work with theapplication. Now you should be able to work with the Baan Internet client.

7.4 Starting the Webserver and Baan Internet ClientThe operational procedure to enable the bi client should include checking thefollowing:

The Webbaan server is running.

The BI HTTP server is running.

bi.html.ascii is in /web/baan/pub and bi.jar is in /web/baan/pub/netscape.

The AFC package is installed on the workstation.

Then, on a Netscape browser, a user should enter:

9.12.2.10:80/bi.html.ascii

A Baan user ID and password

7.5 Started ProceduresYou should set up BPX batch jobs to start the Webserver and BI HTTP server asstarted tasks.

7.5.1 Started Procedure for BI HTTP ServerFollowing is a sample procedure you can put in SYS1.PROCLIB that can be usedto start the Baan BI HTTP server from the console.

à ð//* To start Baan Web Server//BAANWEB EXEC PGM=BPXBATCH,TIME=NOLIMIT,REGION=0M,// PARM='SH /u/baanweb/java -Dfile.encoding=8859_1 BiServer -l x// bi.log -c -t 3 -p 1180 -a wtsc55oe'//STDERR DD PATH='/tmp/baanweb.stderr',// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),// PATHMODE=(SIRWXU)//STDOUT DD PATH='/tmp/baanweb.stdout',// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),// PATHMODE=(SIRWXU)

á ñ


These started tasks must be RACF-authorized and associated with the currentuser ID.

7.5.2 Started Procedure for WebserverFollowing is the procedure we used to start the Webserver:

à ð//WEBBAAN PROC P1='-p 80',// P2='-r /web/baan/httpd.conf',// P3='-B -vv',// LEPARM='ENVAR("_CEE_ENVFILE=/web/baan/httpd.envvars")'//*********************************************************************//*//* LEPARM ==> LE runtime opts//* LEPARM='ENVAR("_CEE_ENVFILE=/etc/httpd.envvars")'//*//* ICSPARM ==> Internet Connection Server parameters//* # Standalone HTTPD//* ICSPARM='-p 8080 -r /etc2/httpd.conf'//* # WLM Queue Manager//* ICSPARM='-SN WEBSN1 -p 8080 -r /etc/httpd.conf'//* # WLM ApplEnv Queue Server//* ICSPARM='-SN WEBSN1 -AE WEBHTML'//*//* Internet Connection Server Parameters://* -SN # WLM - subsystem name//* -AE # WLM - Application Environment//* -fscp nnn # File system codepage - EBCDIC//* -netcp nnn # net code page - ASCII//* -gc_only # clean cache & exit (garbage collect)//* -normalmode//* -p nnnn # use port nnn (default 80)//* -sslmode//* -sslport nnnn # use port nnn (default 443)//* -nosec # no security//* -nosmf # no smf processing on//* -smf # smf processing on//* -r /etc/httpd.conf # use rule file xxxx//* -restart//* -v # trace to stderr//* -vv # trace all to stderr//* -vc # cache trace to stderr//* -version # show version and exit//* xxxxxxx # ServerRoot xxxxxxx; Pass /*//*//*********************************************************************//WEBSRV EXEC PGM=IMWHTTPD,REGION=0K,TIME=NOLIMIT,// PARM=('&LEPARM/&P1 &P2 &P3')//STEPLIB DD DSN=IMW.SIMWMOD1,DISP=SHR//*********************************************************************//SYSIN DD DUMMY//OUTDSC OUTPUT DEST=*//SYSPRINT DD SYSOUT=*//SYSERR DD SYSOUT=*//STDOUT DD SYSOUT=*//STDERR DD SYSOUT=*//SYSOUT DD SYSOUT=*//CEEDUMP DD SYSOUT=***************************** Bottom of Data ****************************

á ñ



Chapter 8. Cloning/Customizing the HTTP Server for OS/390

Before you can start customizing the HTTP server for OS/390, you will need tomake sure you have UNIX System Services and TCP/IP customized. The Webserver runs on top of a functional UNIX System Services and TCP/IPenvironment. For more information see UNIX System Services Planning,SC28-1890.

The definitive guide for the HTTP server installation process is the IBM HTTPServer for OS/390: Planning, Installing and Using, SC31-8690. We do notduplicate that information here, but summarize some of the key steps.

1. Do the SMP/E installation of the HTTP server for OS/390.

2. Define RACF profiles, RACF groups, RACF user IDs, RACF surrogate IDs tosupport the Web server environment.

3. Install the latest Java Virtual Machine for OS/390 from:http://www.s390.ibm.com/java

4. Edit /usr/lpp/internet/sbin/setup.sh, and point JAVA_HOME to where youhave the JDK installed. For example:JAVA_HOME=${JAVA_HOME:-</usr/lpp/java/J1.1>}

5. Run /usr/lpp/internet/sbin/setup.sh. This will create httpd.conf andhttpd.envvars files in the /etc directory.

Once the installation tasks for the default HTTP server for OS/390 have beencompleted and some basic configuration done, you should clone thisenvironment before doing any more customization. We discuss how to clone in8.2.2.2, “Web Content Setup Recommendations” on page 87.

8.1 Setting Up Server Configuration FilesThe Web server configuration file (often referred to as the httpd.conf file) may belocated in any HFS directory. If you plan to run multiple servers, you will needmultiple configuration files, one per server. You can place all of these in the /etcdirectory, or you can have them located in their own managed directories, suchas /web/baan/httpd.conf and /web/server2/httpd.conf.

In managing your configuration file, you can either use the online Configurationand Administration forms (the server must be running to use these), or you canedit the configuration file manually.

We assume that you have started your server using the default IBM-suppliedconfiguration file. You can now continue using this file and customize it to yourneeds. Because of the many parameter and directive changes from release torelease, you cannot use a downlevel copy of the httpd.conf file with a new levelof the HTTP Server for OS/390.

If migrating to a new release, it is best to start out with the sample httpd.conf filefor that new release and retro-fit your local customization to it.


There are a number of IBM-supplied configuration file samples in the/usr/lpp/internet/samples/config directory:

httpd.conf is the main Web server configuration file.

httpd.envvars are the Web server environment variable definitions.

lgw_fcgi.conf is the fast CGI configuration file.

mvsds.conf is the MVS data set (MVSDS) DLL configuration file.

ics_pics.conf is the platform for the Internet Connection Selection (PICS)configuration file.

javelin.conf is the proxy server or Web Traffic Express configuration file.

socks.conf is the Socks clients configuration file.

After installation, your server has one authorized user ID that can be used toaccess the Configuration and Administration forms. By default, the authorizeduser ID is WEBADM. If you selected a different user ID during HTTP Server forOS/390 installation, you should edit the httpd.conf file and change alloccurrences of WEBADM,webadm to the user ID you selected.

8.2 Setting Up a Single ServerThis section helps you to set up the server configuration file to be used with asingle server. This server is intended to run in normal mode only (no SSLencryption). Setting up a secure server needs extra steps; see Enterprise WebServing with the Lotus Domino Go Webserver for OS/390, SG24-2074 for moreinformation on setting up a secure server.

You may configure the server using a Web browser and the remoteadministration configuration method as described in the HTTP Server, Planning,Install and Use, SC31-8690, or you may update the server configuration file usinga text editor. The HTTP Server, Planning, Install and Use section “Using theConfiguration and Administration forms” describes the steps to follow whenusing the remote server administration forms.

The following descriptions are based on the use of a text editor instead of theremote server administration forms.

8.2.1 Basic Single Server ConfigurationIf you followed the standard installation procedure for the HTTP Server forOS/390, no customization work is needed to enable the Web server to run.

Standard, in this case, means the following:

The Web server files have been installed in /usr/lpp/internet/server_root.Check if Frntpage.html exists in /usr/lpp/internet/server_root/pub.

You are using the default TCP/IP port (80) to access the Web server.

If you start up your Web server, you should be able to access it using a Webbrowser through TCP/IP. However, you will be prompted to provide a validOS/390 user ID and a password because the initial setting requires this.

The following describes some of the first changes you will probably want tomake to the IBM-supplied default configuration file.


8.2.1.1 Specify the Default Access Control User IDIf you wish to allow access to your Web server to anyone, without the need foruser verification, you might change the UserID directive from UserID %%CLIENT%%to UserID PUBLIC .

This assumes that you are using an OS/390 (RACF) user ID of PUBLIC as yourdefault access user ID.

Restarting the Web server after making this change should enable you to accessthe Web server's home page without providing a user ID.

8.2.1.2 Specify the Authorized Administrator User IDAfter installation, your server has one authorized user ID that can be used toaccess the Configuration and Administration forms. By default, the authorizeduser ID is WEBADM. If you selected a different user ID during HTTP Server forOS/390 installation, you should edit the httpd.conf file and change alloccurrences of WEBADM and webadm to the user ID you selected. Figure 40shows the default statements that you will need to update if you selected adifferent user ID. However, access to the configuration page in order to workwith the remote administration forms will still be protected. This will be enforcedby the definition shown in Figure 40.

Protection IMW_Admin {ServerId IMWEBSRV_AdministrationAuthType BasicPasswdFile %%SAF%%Mask WEBADM,webadm

}

Protect /admin-bin/* IMW_Admin WEBADMProtect /reports/* IMW_Admin WEBADMProtect /Usage* IMW_Admin WEBADM

Figure 40. Web Server Administration Protection Directives

8.2.1.3 SSL Security Customization for Non-SSL ModeIf you followed our recommendation and started with the supplied sampleconfiguration file as shipped, the configuration directives shown in Figure 41appear in your configuration file. They are related to SSL security.

SSLClientAuth offsslmode onsslport 443normalmode onkeyfile key.kdb

Figure 41. SSL Directives in IBM-Supplied Configuration File (httpd.conf)

There is no requirement to change these parameters.

Note: If you leave these parameters as they are, you will get the following errormessage, which can be seen in the httpd.errors log when starting the server:

+0500 SSL support initialization failed,server will run only in non-secure mode without listening on ssl port

Chapter 8. Cloning/Customizing the HTTP Server for OS/390 85

This message indicates that no setup has been done for SSL. However, the Webserver can still be used as a normal “non-secure” server.

You can avoid getting this error by commenting out the directives shown inFigure 41 on page 85. If you want to set up SSL, see Enterprise Web Servingwith the Lotus Domino Go Webserver for OS/390, SG24-2074 for moreinformation.

8.2.2 Locating Your Web ContentThis section shows you how and where to set up your own Web content withoutaffecting or being affected by the IBM Web content that is provided with HTTPServer for OS/390. This is important because if you place your own Web contentin the file system that IBM provides, you might find it difficult to upgrade toanother version of the Web server, or even apply maintenance.

8.2.2.1 Standard Web Content SetupThe Web server is defined to look for Web pages in/usr/lpp/internet/server_root/pub, with some exceptions for “special pages”(such as remote configuration forms). This is enforced by the definitions shownin Figure 42.

#Pass /admin-bin/webexec/* /usr/lpp/internet/server_root/admin-bin/webexec/*Exec /cgi-bin/* /usr/lpp/internet/server_root/cgi-bin/*Exec /admin-bin/* /usr/lpp/internet/server_root/admin-bin/*Exec /Docs/admin-bin/* /usr/lpp/internet/server_root/admin-bin/*

# These are the pass rules for server administration#Pass /icons/* /usr/lpp/internet/server_root/icons/*Pass /Admin/*.jpg /usr/lpp/internet/server_root/Admin/*.jpgPass /Admin/*.gif /usr/lpp/internet/server_root/Admin/*.gifPass /Admin/*.html /usr/lpp/internet/server_root/Admin/*.htmlPass /Docs/* /usr/lpp/internet/server_root/Docs/*Pass /reports/javelin/* /usr/lpp/internet/server_root/pub/reports/javelin/*Pass /reports/java/* /usr/lpp/internet/server_root/pub/reports/java/*Pass /reports/* /usr/lpp/internet/server_root/pub/reports/*Pass /img-bin/* /usr/lpp/internet/server_root/img-bin/*# *** ADD NEW PASS RULES HERE ***Pass /* /usr/lpp/internet/server_root/pub/*

Figure 42. Standard Web Content Setup Directives

These Exec and Pass statements force the Web server to search for content atparticular locations in the HFS. This approach also has the effect of hiding thestructure of your file system from users of Web browsers.

The following HTML example can be used to show how the Web server resolvesthe requests. Assume that a Web browser makes a request for the home pageof a particular site, (that home page is shown in Figure 43 on page 87).


<html><head><TITLE>IBM HTTP Server</TITLE></head><body bgcolor="#FFFFFF">

<img src="/Admin/lgmast.gif" alt="IBM HTTP Server"> . .<hr><DL><DT><a href="/admin-bin/webexec/cfgstart.html">CONFIGURATION AND ADMINISTRATIONFORMS</a><DD>To set up, configure, and administer the IBM HTTP Server.<br><font size="-1"><A HREF="tunetips.html"><b>Tune your browser first.</b></A></font><P><DT><A HREF="http://www.ics.raleigh.ibm.com/lotusgowebserver/">LOTUS DOMINOGO WEBSERVER WEB SITE</a><DD>To find useful information.<P><DT><A HREF="http://www.software.ibm.com/webservers/httpservers/doc51.html">INFORMATION TO HELP</A>

.

.

.

.

Figure 43. HTML Example - frntpage.html

This HTML file is found by the Web server and is sent to the client.

The client browser reads the file and finds the first reference statement in thisHTML file (line . . in Figure 43). This causes another GET request to be madeto the server. The request would look like this:

GET /Admin/lgmast.gif HTTP/1.0

The server receives this request, looks for a matching configuration directive,and in this case finds the following, as shown in Figure 42 on page 86.

Pass /Admin/*.gif /usr/lpp/internet/server_root/Admin/*.gif

The Web server therefore translates the request to:

/usr/lpp/internet/server_root/Admin/lgmast.gif

It is important that you understand how this example was mapped by the Webserver to actual file system locations. Each request is mapped according to theHTTP rules and to the configuration directives (in a top-to-bottom, first matchapproach).

8.2.2.2 Web Content Setup RecommendationsOur recommendations are:

1. Do not modify IBM-provided default content.

2. Do not mix IBM-provided default content with your own content.

3. Do not use the following locators assumed by IBM default content for yourown URLs:

/cgi-bin/ Used to address CGI programs./admin-bin/ Used to address CGI programs for remote

administration purposes. WEBADM passwordneeded to access.

/Docs/admin-bin/ Used to address CGI programs for documentation.


/icons/ Used to address server icons for tree views andother purposes.

/Admin/ Used for remote administration purposes./Docs/ Used for the standard documents provided with the

Web server./img-bin/ Used for clickable icons./reports/ Used to access reports generated by service tasks

from the log files./reports/javelin/ Used to access reports generated by Web Traffic

Express./reports/java/ Used to access reports generated by Java.

4. Use a separate HFS data set for your own Web content, mounted at adifferent mount point than the /usr/lpp/internet/server_root path.

8.2.3 Customizing Your Web ServerThe following procedure shows you an easy way to start with your Web serversetup:

1. You should have already run /usr/lpp/internet/sbin/setup.sh to create defaulthttpd.conf and httpd.envvars files in the /etc directory.

2. Allocate a new HFS data set for your Web content. Allocate a 20 to 25cylinder HFS (call it OMVS.systemID.WEB.yyy on the SYSPLEX andOMVS.WEByyy.HFS on the non-SYSPLEX systems). Mount it at /web/yyy,where yyy is a name that corresponds with the server you are cloning, likeapple, baan, suf or peg. Mount this HFS to a mount point such as/web/baan/, as follows:

mkdir -p /web/baan/samples/mountx /web/baan OMVS.SC04.WEBBAAN.HFS

3. Create the following directories:

/web/baan/pub Default directory containing your HTML and otherfiles.

/web/baan/pub/images Default directory containing your GIF files./web/baan/our-cgi Default directory containing your CGI programs./web/baan/reports Directory containing the server reports./web/baan/logs Directory containing the server logs.

4. Issue the following command to change the permission bit settings for all thedirectories that you have created:

chmod -R 755 /web

5. Copy /etc/httpd.conf and /etc/httpd.envvars to the /web/yyy directory.

The following assumes you are configuring a server called BAAN:

cp /etc/httpd.* /web/baan/

6. Edit the /web/baan/httpd.conf file and change the ServerRoot statement to/web/baan .

7. Change UserID %%CLIENT%%to UserID PUBLIC .

This assumes that you are using an OS/390 (RACF) user ID of PUBLIC asyour default access user ID.

8. Change the PidFile statement to /web/baan/httpd-pid .

9. Change the logging and reporting statements to the appropriate directories,as shown in Figure 44 on page 89.


AccessLog /web/baan/logs/httpd-logAgentLog /web/baan/logs/agent-logRefererLog /web/baan/logs/referer-logErrorLog /web/baan/logs/httpd-errorsCgiErrorLog /web/baan/logs/cgi-error

AccessLogArchive purgeErrorLogArchive purgeAccessLogExpire 5ErrorLogExpire 5AccessLogSizeLimit 0ErrorLogSizeLimit 0

AccessReportDoDnsLookup OffAccessReportRoot /web/baan/reports

Figure 44. Single Server - Logging and Reporting Changes to httpd.conf

10. Edit the httpd.conf file and modify the Exec and Pass statements as shown inFigure 45.

#Exec /our-cgi/* /web/baan/our-cgi/*Exec /cgi-bin/* /usr/lpp/internet/server_root/cgi-bin/*Exec /admin-bin/* /usr/lpp/internet/server_root/admin-bin/*Exec /Docs/admin-bin/* /usr/lpp/internet/server_root/admin-bin/*

# These are the pass rules for server administration#Pass /icons/* /usr/lpp/internet/server_root/icons/*Pass /Admin/*.jpg /usr/lpp/internet/server_root/Admin/*.jpgPass /Admin/*.gif /usr/lpp/internet/server_root/Admin/*.gifPass /Admin/*.html /usr/lpp/internet/server_root/Admin/*.htmlPass /Docs/* /usr/lpp/internet/server_root/Docs/*Pass /img-bin/* /usr/lpp/internet/server_root/img-bin/*Pass /images/* /web/baan/pub/images/*Pass /reports/javelin/* /usr/lpp/internet/server_root/pub/reports/javelin/*Pass /reports/java/* /usr/lpp/internet/server_root/pub/reports/java/*#Pass /reports/* /usr/lpp/internet/server_root/pub/reports/*Pass /reports/* /web/baan/reports/*#Pass /* /usr/lpp/internet/server_root/pub/*Pass /Server/* /usr/lpp/internet/server_root/pub/*Pass /* /web/baan/pub/*

Figure 45. Single Server - Modified Web Content Setup Directives

This modification will force the Web server to search in your /web/baan/pubdirectory for everything but the IBM-provided default content.

Other configuration file changes depend on the purpose and content of your Webserver. You may also need to change some parameters in order to tune theserver. For more detailed information on all valid configuration file directivessee HTTP Server, Planning, Install and Use, SC31-8690.


8.2.4 Create a Default Home Page for Your Web ServerThe HTML example in Figure 46 shows you how to set up your own home pageusing the settings shown in Figure 45 on page 89, and still be able to access theremote administration forms as before. This file should be called index.html orWelcome.html and should be placed in /web/baan/pub.

<html><head><title>BAANWEB and the HTTP Server for OS/390</title></head><body bgcolor="#FFFFFF"><img src="/images/thiswher.gif" align=left><h1>Welcome to my home page </h1>This is the HTTP Server for OS/390 serving BAANWEBpages and applets.<hr>Follow this link to access the<a href="/web/baan/pub/bi.html.ascii"> Baan Applet</a></html>

Figure 46. Single Server - HTML Example for a Home Page (index.html)

8.2.5 Create/Update a Started P rocedure for Your Web Server1. Update the started procedure to point to the new httpd.conf and

httpd.envvars files. An example follows:

//WEBBAAN PROC P1='-B',// P2='-r /web/baan/httpd.conf',// P3='-p 99 ',// LEPARM='ENVAR("_CEE_ENVFILE=/web/baan/httpd.envvars")'//*//WEBSRV EXEC PGM=IMWHTTPD,REGION=0K,TIME=NOLIMIT,// PARM=('&LEPARM/&P1 &P2 &P3')//SYSIN DD DUMMY//OUTDSC DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SYSERR DD SYSOUT=*//STDOUT DD SYSOUT=*//STDERR DD SYSOUT=*//SYSOUT DD SYSOUT=*//CEEDUMP DD SYSOUT=*

2. Define a RACF STARTED profile for this Web server, setting the associateduser ID to WEBSRV.

3. Start the Web server. You should see the following message when your Webserver is ready:

IMW3536I SA 184549402 0.0.0.0:9 9 * * READY


Chapter 9. Post-Installation Tasks

After you have completed the installation of Company 000, you must do thefollowing:

Set up the profile for user ID bsp:

You must set $BSE and $BSE_TMP. Check the file /usr/local/bin/set5

Logon to user ID bsp.

Create the DB2 files for Company 813 and Company 900.

Complete the post-installation tasks as described in the Baan manual.

Load all the dump files in $BSE/test:

/baanerp/test/tcB50_b/813/813/comp813.pre/baanerp/test/tcB50_b/900/900/PI.eis.Z/baanerp/test/tgB50_b/813/813/BAANERP-PD.Z (DONE)/baanerp/test/tgB50_b/813/813/conv.dump.Z

Go through the steps to validate the license.

9.1 JCL to Create Company 813à ð

//BERP000 JOB (999,POK),'BERP 000 ALLOCATE',NOTIFY=&SYSUID, 00010023// CLASS=A,MSGCLASS=T,TIME=1439, 00020017// MSGLEVEL=(1,1) 00030017//***//***//***/*JOBPARM SYSAFF=SC55//JOBLIB DD DSN=DB2V510D.RUNLIB.LOAD,DISP=SHR// DD DSN=DB2V510.SDSNLOAD,DISP=SHR//CREATETS EXEC PGM=IKJEFT01,DYNAMNBR=20//SYSPRINT DD SYSOUT=*//SYSTSPRT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSTSIN DD *


//SYSIN DD *


COMMIT;



COMMIT;

GRANT DBADM ON DATABASE BERP813 TO BSPGRP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP813 TO BSP WITH GRANT OPTION;

//á ñ


9.2 JCL to Create Company 900We used the same JCL to create Company 900.

à ð//BERP900 JOB (999,POK),'BERP 900 ALLOCATE',NOTIFY=&SYSUID, 00010023// CLASS=A,MSGCLASS=T,TIME=1439, 00020017// MSGLEVEL=(1,1) 00030017//***//***//***/*JOBPARM SYSAFF=SC55//JOBLIB DD DSN=DB2V510D.RUNLIB.LOAD,DISP=SHR// DD DSN=DB2V510.SDSNLOAD,DISP=SHR//CREATETS EXEC PGM=IKJEFT01,DYNAMNBR=20//SYSPRINT DD SYSOUT=*//SYSTSPRT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSTSIN DD *


//SYSIN DD *


COMMIT;



COMMIT;

GRANT DBADM ON DATABASE BERP900 TO BSPGRP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP900 TO BSP WITH GRANT OPTION;

//á ñ

9.2.1 db2_storage file for Companies 813 and 900This is the db2_storage file we used for Companies 813 and 900 that correspondsto the previous JCL and that puts everything in one database and onetablespace:

à ð*:813:T:group:01:5: ARR_SIZE 1 OPT_R OWS 5 T_SPACE BERP813.TS813*:900:T:group:01:5: ARR_SIZE 1 OPT_R OWS 5 T_SPACE BERP900.TS900*:*:I::01::STOGROUP BERPGRP PRIQTY 64 SECQTY 960 BUFFERPOOL BP3*:*:T:group:01:5: ARR_SIZE 1 OPT_ROWS 5 T_SPACE BERP000A.TS000..

á ñ

Figure 47. db2_storage File for Companies 813 and 900


Chapter 10. Enabling Process Manager on UNIX System Services

This chapter describes how we customized the Process Manager functions of theUNIX System Services Connection Scaling Kit for our installation.

10.1 Process Manager (PM) InstallationThe installation of this new OS/390 features was straightforward and is welldocumented in the Program Directory for OS/390 UNIX System ServicesConnection Scaling Kit, GI10-0635, which is shipped with the OS/390 PTF.

Note: We discovered that customization should be done through a Telnetscreen, rather than through a TSO session.

10.2 Customizing the Process ManagerThe Process Manager (PM) configuration has many options to allow you tocontrol, among many parameters, the number of prestarted address spaces andthe number of Task Control Blocks (TCBs) per address space.

We recommend that you start the installation without PM running. When youstart running the applications with several users, just start with the defaultparameters, which are the ones we used as shown in 10.2.1, “Process ManagerParameters” on page 94.

If you start having memory or address space problems, you can alter suchparameters as:

Prestarted address spaceTCBs per address space

The sample process manager configuration file needs to be copied to the/etc/bpa directory. The /etc/bpa directory was created during the installation ofthe UNIX System Services Connection Scaling Kit. The following command willcopy the file:

cp /usr/lpp/bpa/samples/bpares.cfg /etc/bpa/bpares.cfg.conf

To enable Process Manager with a basic customization, we added thestatements describing the port number to two files:

1. The services file of the client workstation

The port number has to be put in the services file of the client workstation.In our case, this was a Windows 95 PC. We had to add this to the/windows/services file on the client, as shown in Figure 48

Note: We first made the error of adding the port number to the /etc/servicesfile of UNIX System Services on the S/390.

à ðBaanRexec 6000/tcp #This port is used to contact the Process Manger Daemon

á ñFigure 48. Adding Port Number to /windows/services


2. Using vi, we added the following to the /etc/bpa/bpares.cfg file in UNIXSystem Services of OS/390, as shown in Figure 49 on page 94.

à ðIP_Address=9.12.2.14

Port=6000

á ñFigure 49. Adding the IP Address to /bpares.cfg

Note: These key words are case sensitive. For example, we received an errorwhen we entered PORT instead of Port.

We checked that our environment variable LIBPATH included the following value:/usr/lpp/bpa/lib

We checked that our environment variable PATH included the following values:/usr/lpp/bpa/bin/usr/lpp/cmx/bin

We also checked that NLSPATH included:/usr/lpp/bpa/nls/msg/%L/%N/usr/lpp/cmx/nls/msg/%L/%N

10.2.1 Process Manager ParametersFigure 50 on page 95 shows the sample Process Manager file. We recommendthe following:

Do the installation without running the Process Manager.

After installation, start running with the default values.

Tune the values in this file to adjust for your environment, based on yourexperience.

The parameters to consider changing are the number of users per addressspace and the number of associated control tasks.


à ð//------------------------------------------------------------------------------// Process Manager Configuration Template File//// Note: you must at least set the following parameters// ( see Process Manager Installation and Tuning Guide for details ) :// DAEMON“ PORT// DAEMON“ IP-Address//------------------------------------------------------------------------------

[BASE]

//------------------------------------------------------------------------------// The base path is used as prefix for any other path definitions used// by Process Manager components. It has to be specified as an absolute path.//------------------------------------------------------------------------------BasePath=/var/bpa

//------------------------------------------------------------------------------// Errorlog determines the pathname of the error log file used by the// Process Manager for Baan//------------------------------------------------------------------------------ErrorLog=/var/bpa/bpaerr.log[SYSTEM]

//------------------------------------------------------------------------------// MaxTCBPerAS determines the maximum of TCB's kept running in one address// space. If there are more TCB's to spawn then they are started// into a foreign address space.//------------------------------------------------------------------------------MaxTCBPerAS=50

[DAEMON]

//------------------------------------------------------------------------------// RestartToShutdownThreshold determines the number of restarts tried for the// TCP/IP communication threads of the Process Manager Daemon.//------------------------------------------------------------------------------RestartToShutdownThreshold=10

//------------------------------------------------------------------------------// RestartDelayTime determines the delay time in seconds used before// restarting a thread of the Process Manager daemon. See parameter// RestartToShutdownThreshold for more information.//------------------------------------------------------------------------------RestartDelayTime=60//------------------------------------------------------------------------------// IP-Address determines the host address used by the listener. This is the IP// Address of the machine this daemon is running.// It has to be specified standard dotted-decimal notation.//// Values specified in standard dotted-decimal notation take one of the// following forms://// a.b.c.d// a.b.c// a.b// a//

á ñ

Figure 50 (Part 1 of 3). Parameters for Process Manager

Chapter 10. Enabling Process Manager on UNIX System Services 95

à ð// Note:// If you specify "IP-Address=0" then the daemon will listen bound to all// network interfaces on the host.//------------------------------------------------------------------------------IP-Address=<the ip-address of your system>//------------------------------------------------------------------------------//Port (TCP) determines the port to which the Listener must bind.//------------------------------------------------------------------------------Port=<any valid port number of TCP on your system>//------------------------------------------------------------------------------// LITQueueLength determines the maximum length for the queue (eg. the// number of pending connections) for the Listener thread of// Process Manager Daemon.//------------------------------------------------------------------------------LITQueueLength=500//------------------------------------------------------------------------------// MaxThreadTasks determines the softlimit of the maximum TCBs available to// the process for concurrently running threads.//------------------------------------------------------------------------------MaxThreadTasks=1000//------------------------------------------------------------------------------// MaxThreads is the softlimit of the maximum number of threads a// process can run concurrently at a time.//------------------------------------------------------------------------------MaxThreads=1000

//------------------------------------------------------------------------------// ThreadStacksize determines the initial thread stack size// as a multiple of 1K (1024) bytes. Other stack characteristics,// like stack increment size, are inherited from the STACK runtime option.//------------------------------------------------------------------------------ThreadStackSize=10[SSPT]//------------------------------------------------------------------------------// Value specifies the maximum wait time of the login handler thread// to get a SSP returned. (Should be greater than TrimmTime)//------------------------------------------------------------------------------SSPWaitTime=600//------------------------------------------------------------------------------// Time to wait for a SSP in state STARTTING or INUSE.// The value has to be specified in seconds.//------------------------------------------------------------------------------TrimmTime=300//------------------------------------------------------------------------------// Max number of terminating SSPM with bad return code. If more SSPMs// failed in execution this case will be logged and no retry will be made// to restart the SSPM.//------------------------------------------------------------------------------MaxRestartSSPM=10//------------------------------------------------------------------------------// PrestartedAS is the number of prestarted AS (each controlled by a SSPM)// after startup of the Process Manager Daemon. Each Address Space is// controlled by an SSPM process.// PrestartedSSPPerAS is the number of SSPs, which are prestarted by any new// SSPM in the same Address Space.// MaxSSPPerAS is the maximum number of SSPs controlled by an SSPM.

á ñ



à ð//// MinFreeSSP is the minimum number of all SSPs controlled by the// Process Manager which have to be available to get new work assigned.// When this threshold is reached, a number of "StartAddSSP" new SSPs// will be started.// MaxFreeSSP is the maximum number of free SSPs controlled by the// Process Manager. When this threshold is reached for longer than// "TrimmTime", a number of "TermAddSSP" free SSPs will be stopped.// StartAddSSP is the number of SSPs to be started when MinFreeSSP// threshold was reached.// TermAddSSP is the number of SSPs to be stopped when MaxFreeSSP// threshold was reached for longer than "TrimmTime" seconds.//// MaxMemBelowPerUser is the typical max. amount of storage which is allocated// by each user below the 16Meg line. (in KByte)// MinFreeMemBelowPerAS is the percentage amount of memory below the 16Meg line// which should be left free for exceptional reasons.// (in %)//------------------------------------------------------------------------------PrestartedAS=1

// Numbers per Adress Space (AS)PrestartedSSPPerAS=2MaxSSPPerAS=15

// Total numbersMinFreeSSP=1MaxFreeSSP=4StartAddSSP=2TermAddSSP=2

// Storage usage below the lineMaxMemBelowPerUser=350MinFreeMemBelowPerAS=40

[TRACE]

Level=0BufferSize=3000 // size of trace string bufferFileRecords=500000 // maximum number of trace records in fileBufRecords=1000 // threshold of trace records the buffer should holdKeyFileName=/var/bpa/bpalogd.key // request the key to create msg queueLogFileName=/var/bpa/bpatrace.log // trace log file nameToStdout=0 // trace strings will be dumped to stdout use

// this for debugging purpose only (tail -f file)

á ñ


10.2.2 Starting and Stopping the Process ManagerTo start the Process Manager, do the following:

1. Logon as root.2. Change directory by issuing the command: cd /usr/lpp/bpa/bin3. Execute the command: s_dae

To stop PM:

1. Issue the command: p_dae

Chapter 10. Enabling Process Manager on UNIX System Services 97

These tasks are described in greater detail in UNIX System Services ConnectionScaling Reference, SA22-7305.


Chapter 11. Administration of DB2 for Baan Applications on OS/390

This chapter reviews a collection DB2 data administration topics from thefollowing sources:

Baan IVc installation experience

Interviews with customers who have installed Baan IVc to run with DB2 on aSystem/390 platform

Interviews with Baan support and development personnel

DB2 experience

Over the years, we have worked with customers who have installedapplications similar in architecture to BaanERP.

11.1 DB2/BaanERP IntroductionThere are some basic characteristics of the BaanERP implementation that mustbe presented for you to understand the reasons for many of the DB2/BaanERPrecommendations in this chapter.

11.1.1 DB2/BaanERP IndexesIndexes in BaanERP systems are on columns named HASH1, HASH2, ..., HASHn.Two indexes (one ascending and one descending) are defined on each HASHcolumn. Baan primes the HASH columns under program control. The Baan userdoes not know what is in the HASH columns.

None of the BaanERP indexes are explicitly defined as clustering. This has aprofound effect on our recommendations regarding the Reorg utility. All of theBaanERP-defined indexes are explicitly declared unique. This has a profoundeffect on our recommendations regarding the Runstats utility.

11.1.2 DB2/BaanERP User-Written QueriesIf you plan to support user-written queries against your BaanERP data, you willbe required to define indexes to support reasonable performance. The Baanindexes on the HASH columns will be of no use to your user-written queries(since you do not know what the HASH columns contain, you will not be able todefine query predicates using them).

11.1.3 Baan's Use of SQLBaan application programs pass requests for data to a Baan component, whichin turn constructs DB2 SQL statements. These statements are then passed toDB2. Baan refers to this passing of an SQL statement to DB2 on behalf of Baanapplication programs as a driver. There is a level 1 driver currentlyimplemented in the BaanERP applications, with a level 2 driver planned for afuture date.

The level 1 driver passes fundamentally simple SQL requests to DB2 (simpleSelects, Inserts, Updates, and Deletes). The planned level 2 driver will likelypass more sophisticated SQL to DB2. The implication of this is that you canexpect BaanERP to place DB2 under relatively light stress because of the simpleSQL produced by the level 1 driver. Our experience indicates that you are likely


to see the major share of resource consumption in the BaanERP environmentcome from components outside of DB2.

11.2 DB2/BaanERP Operational ObservationsIt is recommended that you plan to run BaanERP on a dedicated DB2 subsystem.This will position you to implement upcoming recommendations, specificallythose addressing point-in-time recovery.

It is important to note that if you implement some or all of theserecommendations, it will be your responsibility to insure that you carry forwardyour changes should you migrate to a later release of Baan products.

11.3 DB2/BaanERP Database and Table Space Re commendationsIf the user does not influence the BaanERP installation process, all tables for agiven company will go into one DB2 table space, which goes into one DB2database. Additionally these tables, table spaces, and indexes will have DB2default buffer pool and free space attributes.

BaanERP Company 000 contains 392 tables, and the combination of Company550 plus Company 750 contains 4598 tables.

1. It is recommended that you install BaanERP table spaces and databases asfollows:

Install no more than 100 tables per table space.

In some cases it can be beneficial to assign as few as one table to atable space. 100 should be considered a maximum.

Install 1 table space per database.

The implication of this recommendation is that you will have at least 4table spaces and databases for Company 000, and at least 46 tablespaces and databases for the combination of Company 550 and Company750.

The benefits of this recommendation are:

− The DB2 DBD (Database Descriptor) will be smaller.

The DBD must be loaded contiguously into the DB2 EnvironmentalDescriptor Manager (EDM) pool. DB2 will not load a DBD into theEDM pool that is larger than 25% of the pool size. Smaller DBDs arelikely to place less stress on the EDM pool size.

DB2 logs the necessary undo/redo information for the unit ofrecovery in which the DBD was changed. The DBD is changedduring data definition activity like Create Index. Smaller DBDs offerthe potential for less DB2 logging.

− There can be greater user concurrency of SQL Data DefinitionLanguage (DDL).

DDL, like Create Index, requires a DB2 lock on the DBD whichrestricts other users for the duration of the DDL process.

2. It is recommended that you assign to a separate table space smaller tablesthat are primarily read-only.


You will have to query the DB2 catalog to determine which tables aresmaller. To determine tables that are primarily read-only, you will have toanalyze the instrumentation reports produced by DB2PM (or your functionallyequivalent DB2 performance reporting tool). We did not attempt to identifythose tables during this effort.

These smaller primarily read-only tables can then be assigned to a separateDB2 buffer pool. You will want to evaluate a higher hiperpool allocation forthis buffer pool. DB2 will not cache to the hiperpool changed data pages, butwill attempt to cache unchanged read-only data pages.

3. It is recommended that you allocate highly volatile frequently updated tablesto a separate table space.

You will have to determine these highly volatile and frequently updatedtables in your environment by an analysis of the DB2 instrumentation data.These tables tend to be a function of the application and the requirementsplaced upon the application by the user.

Highly volatile table spaces can be assigned to one or more separate DB2buffer pools. You then can evaluate the setting of the DB2 buffer poolthresholds, the Deferred Write Threshold (DWQT) and the Vertical DeferredWrite Threshold (VDWQT), to values other than the defaults of 50% and 10%,respectively. If the virtual buffer pool is large, it is unlikely that the defaultvalues of VWQT and DVWQT will be reached. In this case there tends to bea surge of write I/O as writes are triggered by DB2 checkpoints. Loweringthe DWQT and VDWQT could improve performance by distributing the writeI/Os more evenly over time. For more information on tuning DB2 bufferpools, see “Buffer Pool Thresholds” in DB2 for OS/390 Version 5Administration Guide, Volume II, SC26-8957.

4. It is recommended that you segregate, into one or more separate tablespaces, tables against which you will run the Reorg and Runstats utilities.

The BaanERP architecture makes it unlikely that you will want to run Reorgor Runstats once your application is in production. (These utilities areaddressed more completely in 11.6, “DB2/BaanERP Reorganization andRunstats Recommendations” on page 104.) If you intend to runuser-developed queries against BaanERP tables, you should put those tablesin one or more separate table spaces. The reason is that the Reorg andRunstats utilities are invoked at the table space level.

11.4 DB2/BaanERP DSNZPARM Rec ommendationThis recommendation should be considered as a starting point. Of course, if youhave unique processing requirements, you may choose a different value for thefollowing parameter.

1. LOGLOAD

It is recommended that you set LOGLOAD to 50,000. LOGLOAD specifies thenumber of DB2 log records written between DB2 checkpoints. The higherLOGLOAD, the less frequently DB2 takes checkpoints.

This recommendation centers around two factors:

DB2 restart time

If DB2 abnormally terminates, the restart time is a function of the numberof log records that DB2 must process. At restart time, DB2 will generally

Chapter 11. Administration of DB2 for Baan Applications on OS/390 101

go back one checkpoint and then process to the end of the log. A lowerLOGLOAD means less log to process at restart, and consequently afaster restart in general. Of course, a long-running unit of recovery thattakes few or no commits could cause a greater amount of log processingat restart.

DB2 writes from buffer pools to DASD

When DB2 takes its internal checkpoint (a function of LOGLOAD), itschedules I/O for updated pages in the buffer pools to DASD. AsLOGLOAD increases, the number of pages to be written tends toincrease. With large buffer pools and a large LOGLOAD, the writeactivity can be significant (this activity is sometimes noticeable by userswho perceive periods of slower than normal performance). You cancontrol the write load with the DWQT and VDWQT threshold parametersdiscussed earlier, or as an alternative, you can minimize exposure to anexcessive write load with a smaller value for LOGLOAD.

11.5 DB2/BaanERP Buffer Pool, Free Space, and Space AllocationIf during the BaanERP installation process you do not explicitly state buffer pool,free space, and primary/secondary space allocations, your indexes and tablespaces will be defined with DB2 defaults. Specifically, accepting the DB2defaults will cause the following allocations:

The table space or index will default to the default buffer pool of thedatabase.

This is typically BP0.

For a table space, the default FREEPAGE will be 0 and the default PCTFREEwill be 5%.

For an index, the default FREEPAGE will be 0 and the default PCTFREE willbe 10%.

For a table space, the default PRIQTY (primary space allocation) is 12 Kbytes and the default SECQTY (secondary space allocation) is 12 K bytes.

For an index, the default PRIQTY (primary space allocation) is 12 K bytes andthe default SECQTY (secondary space allocation) is 12 K bytes.

11.5.1 DB2/BaanERP Buffer Pool RecommendationsIf you take no explicit action during the BaanERP installation process, you arelikely to have all of your BaanERP/DB2 objects in buffer pool 0. Since you arenot likely to know the characteristics of the table spaces at installation time, youshould accept the default and later change the buffer pool with the AlterTablespace/Index SQL statement.

The following are general recommendations regarding configuration of the DB2buffer pools in support of BaanERP. The recommendations are not based uponspecific BaanERP experience, but upon experience with applications of similararchitecture. The recommendations assume that the DB2 subsystem isdedicated to BaanERP, and are presented as percentages of the number ofbuffers you are willing to assign to the DB2 buffer pools.

BP0 - 10%. Restrict BP0 to the DB2 catalog and directory.

This is to facilitate the dynamic SQL that BaanERP executes.


BP1 - 10%. BP1 is to support large Baan tables.

The large tables will generally have a low buffer reuse. Consequently, 10%is moderate relative to the other Baan buffer pool assignments.

BP2 - 35%. BP2 is dedicated to Baan indexes.

Indexes tend to have a high buffer reuse. Consequently, we recommend ahigh buffer allocation.

BP3 - 23%. BP3 is dedicated to the smaller Baan tables.

Code tables are usually smaller and tend to experience high access. Thislarge buffer pool allocation facilitates data-in-memory processing of thefrequently accessed smaller tables.

BP4 - 20%. BP4 is dedicated to other Baan tables.

This is to provide for exceptions that do not fit neatly into the previouslypresented scheme.

BP7 - 2%. BP7 is to support DB2 temporary storage (DSNDB07).

We have not seen extensive use of the DB2 sort work files running the Baanapplications. 2% is considered a minimum “safe” allocation of buffers tosupport the use of DSNDB07. You will want to track DB2 instrumentationstatistics regarding this buffer pool. You may add some query workload oruse parts of the Baan applications that we did not test. Either of these couldcause you to increase the buffers allocated to DSNDB07.

BP32 - minimum. This is support for any 32 K buffer pool requirement.

Except for BP0, a specific buffer pool number is arbitrary. Note, however, thatDB2 requires BP0 for the catalog and directory table spaces. Obviously youmay, for example, use BP2 to support DSNDB07. The key is the conceptcentering on differentiating large tables, small tables, and indexes.

11.5.2 DB2/BaanERP Free Space Rec ommendationsBoth PCTFREE (percent of a page that is kept free at Load or Reorg time) andFREEPAGE (interval at which a page of free space is to be inserted during Loador Reorg) apply to table spaces and indexes.

BaanERP/DB2 table spaces

It is recommended that you explicitly set PCTFREE to 0. You may accept thedefault of 0 for FREEPAGE.

None of the BaanERP tables have indexes that have been explicitly definedas clustering. The implication of this is that there is no benefit to having DB2attempt to maintain the table's data in a sequence. Even if you do notexplicitly define a clustering index, DB2 will attempt to sequence the data atSQL insert time by the sequence of the first defined index. This is not likelyto be of any value during processing. Zero for PCTFREE and FREEPAGE willsave DASD.

You may be concerned about insert processing contention at the end of thetable. That is not a problem. DB2 in this case will attempt to find the “bestpage” for the insert (it will be the last page without any free space) and ifDB2 cannot get that page it will get another page “near the best page.” Ineffect, do not worry about insert contention in this recommendedno-free-space environment.


BaanERP/DB2 indexes

For indexes, the default of 10% for PCTFREE should be maintained. Anindex has the characteristics of a sequential data set. DB2 can moreefficiently maintain an index's sequence with free space.

We do not have a specific recommendation for FREEPAGE. In general, youshould consider free pages when insert activity is high against a table. Youwill have to track insert activity in your environment.

11.5.3 DB2/BaanERP Primary/Secondary AllocationsDuring the installation on Company 000, we allowed the default value of 12 K forthe primary allocation and 12 K for the secondary allocation. This proved to beinadequate with the maximum number of data set extents exceeded in somecases.

There are two requirements: getting through load (load in Baan applications isaccomplished with SQL Inserts and not the DB2 Load utility), and running inproduction. Both requirements can be met with the following techniques. Duringload, it is recommended that you default to the small primary allocation, butdefine a larger secondary allocation. We found 10,000 for the secondaryallocation to be acceptable during load.

Once you are in production, reverse the strategy discussed previously for theload environment. For table spaces and indexes that are in extents, alter to alarge primary and small secondary based on data requirements in yourenvironment. Although not necessary, it is a good idea to avoid secondaryextents in production.

11.6 DB2/BaanERP Reorganization and R unstats RecommendationsFollowing are considerations for the use of the DB2 Reorg and Runstats utilitiesin support of BaanERP data.

1. Reorg strategy

a. In general, do not Reorg BaanERP table spaces.

BaanERP tables are not defined with clustering indexes explicitly defined.The Reorg utility will not re-sequence a table that does not have aclustering index explicitly defined. The Reorg utility could reestablishfree space, but it was recommended that you define no free space onBaanERP table spaces. Given the fact that the BaanERP tables have noexplicitly defined clustering index and there will be no free space (if youelect to implement that recommendation), Reorg will be of no value.

b. If you support user-written queries against BaanERP data, evaluateReorg of the table spaces containing tables that users will query.

It will be necessary for you to define indexes to support user-writtenqueries (the Baan indexes on HASH1, HASH2, ..., and so on will not beuseful for user-written queries since the contents of the “HASHn”columns are not documented).

Given that you will define one or more indexes to support user-writtenqueries, you will have the opportunity to determine if one of your indexesshould be defined as clustering. You would do this if you determinedthat your query could benefit from having the data in the physical


sequence of the clustering index. If sequence has meaning in youruser-developed query environment, then Reorg has value inre-sequencing data periodically.

c. Evaluate the use of the online Reorg feature of DB2 V5 when youdetermine that the running of Reorg can benefit your environment.There would be benefit if you defined a clustering index to supportuser-written queries.

Online Reorg significantly reduces the impact of this planned outage.The online Reorg utility copies the table space to one or more shadowdata sets where the actual reorganization is done. The DB2 log isapplied in an iterative fashion to the shadow copy of the data tosynchronize it with the actual online table space.

After the log is applied, the shadow data replaces the unorganized datawhen the Reorg utility changes data set names. The outage is nowlimited to read-only during the final application of the DB2 log to theshadow copy of the table space, and no readers or writers are allowedduring the changing of the shadow data set names to the active tablespace data set names.

d. Reorg DB2 indexes on a periodic basis.

Since indexes have the characteristics of sequential data, there is benefitto Reorging or Re-sequencing them. There are many indexes defined inthe BaanERP applications; however, it is not necessary to Reorg themall. We recommend that as a starting point you Reorg, on a monthlybasis, indexes that are in multiple extents. You can then refine yourindex Reorg strategy based upon your experience with the BaanERPapplications.

2. Runstats strategy

a. Run Runstats on the Baan/DB2 objects one time prior to going intoproduction.

Since all BaanERP indexes are defined as unique, the one-to-one relationof index key to row will not change. Therefore, one execution ofRunstats will provide DB2 index cardinality data that cannot change overtime (that is, the one-to-one mapping cannot change).

b. Run periodic Runstats on the Baan/DB2 objects on which you havedefined a clustering index.

Based upon the characteristics of the indexes you define ( to supportuser-written query activity perhaps), Runstats can provide DB2 importantdata distribution statistics.

11.7 DB2/BaanERP Index UsageIt is recommended that you define all indexes on BaanERP tables to be type 2indexes. This will reduce locking and position you for the future when supportfor type 1 indexes will be dropped.


11.8 DB2/BaanERP Point-in-Time Recovery RecommendationsThe usual reason for a point-in-time recovery is an application programmingerror or a flawed operational procedure. Unfortunately, this exposure is alwayspresent regardless of your hardware/software configuration. Additionally, apoint-in-time recovery has the potential to be the most disruptive outage you arelikely to encounter.

The reason is that in a BaanERP environment, you may have to recover all of thetable spaces and indexes to a prior point in time. Why possibly all objects?Baan does dynamic SQL. You may not be able to determine a subset of tablesto be recovered. To play it safe, you may decide to recover all objects to a priorpoint of consistency. Your usual point-in-time recovery techniques, which youlikely regard as conventional at this time, may be insufficient in this environment.

The point-in-time recovery environment will be addressed as follows:

Point-in-time recovery preventive measures

Point-in-time recovery techniques

Point-in-time recovery recommendations

11.8.1 Point-in-Time Recovery Preventive MeasuresA failure in application development, introducing a programming defect, or inoperational procedures perhaps by running a job twice, introduces therequirement for point-in-time recovery. The available preventive measures areincreased attention to:

Change management

Problem management

Testing

Each of these disciplines is procedure-oriented and management-driven. Asattention to these disciplines is increased, the need for point-in-time recovery isusually decreased. Unfortunately, the need for point-in-time recovery is neverentirely eliminated. Consequently, you will want to make every effort to avoidhaving to do a point-in-time recovery, but you should be prepared to do one ifrequired.

11.8.2 Point-in-Time Recovery TechniquesThe concept behind point-in-time recovery is well understood. It usually involvessetting a table or group of tables to a prior point in time when data wasdetermined to be consistent. The challenge in the BaanERP environment isdetermining the set of tables that are logically related. It is possible that you willnot be able to determine a subset of the BaanERP tables to be reset. You maybe required to reset all BaanERP tables to a prior point of consistency. Thereare three generally used techniques to effect a point-in-time recovery.

Point-in-time recovery using DB2 utilities

The DB2 QUIESCE and COPY utilities are the primary tools.

Point-in-time recovery not using DB2 utilities

This is basically a dump/restore scenario.

Point-in-time recovery using user-written application programs


11.8.2.1 Point-in-Time Recovery Using DB2 UtilitiesThe scenario for a point-in-time recovery using DB2 utilities is as follows:

Determine the set of tables that are logically related.

Typically this is a subset of the tables that make up the application database.However, it may be all BaanERP table spaces and indexes.

Execute the QUIESCE utility on all of the tables that are candidates to bereset if a point-in-time recovery is required.

This establishes a point of consistency and causes the DB2 buffers for thequiesced tables to be externalized to DASD.

Execute the COPY utility on all of the table spaces that are candidates to bereset if a point-in-time recovery is required.

The obvious reason for this step is to back up the data. However, COPY willfail if it cannot externalize the DB2 buffers to DASD. That is the reason weinvoked the QUIESCE utility first (to remove one reason why COPY may fail).

For the second time, execute the QUIESCE utility on all of the tables that arecandidates to be reset if a point-in-time recovery is required.

This invocation of QUIESCE will establish a log RBA which will be the pointof consistency.

When it is necessary to recover to this point of consistency, RECOVER to theRBA established by the second invocation of the QUIESCE utility.

With the combination of the COPY and the second QUIESCE, the RECOVERTORBA will perform as efficiently as a Recover TOCOPY would perform,assuming no logging during the execution of this scenario.

When it is necessary to recover to this point of consistency, RECOVER allindexes on all of the tables that have been reset to the prior point ofconsistency. The indexes must be synchronized with the data in therecovered table spaces.

The benefits of this scenario are:

There is minimal disruption to the user in preparing for the scenario.

The user may see some slowness in response during the execution of theQUIESCE utility, but this can likely be scheduled during off-hours to minimizethe disruption.

There is no disruption to the user when COPY is run with Share-LevelChange.

COPY — Share-Level Change allows updates concurrent with utilityexecution.

The recovery of the table spaces will be efficient.

RECOVER TORBA will perform as well as RECOVER TOCOPY, assuming nologging between the execution of the COPY utility and the second executionof QUIESCE.

However, there is a significant disadvantage to this scenario: the requirement torecover potentially many indexes may make this scenario impractical.


11.8.2.2 Point-in-Time Recovery Not Using DB2 UtilitiesThis scenario will use a DB2 command and a dump/restore utility program.

Determine the set of tables that are logically related.

Typically this is a subset of the tables that make up the application database.However, in the BaanERP environment, it may be all of the tables.

Use the DB2 Stop Database command to stop all of the table spaces that arelogically related.

The Stop Database command will cause the DB2 buffers to be externalizedand the VSAM data sets that hold the DB2 data to be closed. While the tablespaces are stopped, the data will be unavailable to users.

Dump the table space and index data sets using your installation high-speeddump utility.

You may consider using SnapShot, a program product that runs with the IBMRAMAC Virtual Array. The dumped data sets represent your point ofconsistency.

When it is necessary to recover to this point of consistency, restore the datasets that were dumped in the previous step.

Because the table spaces are stopped, there will be no outstanding units ofrecovery, and the data will be consistent. The data being restored consistsof both the table spaces and the associated indexes.

This scenario is more efficient than the previous one, but preparing for it is moredisruptive to the user. The data is unavailable to the user while the table spacesare stopped and while the data is being dumped. The duration of the period thatdata is unavailable can be lessened by using SnapShot.

11.8.2.3 Point-in-Time Recovery Using User-Written ApplicationProgramsThis is a strategic direction and not a scenario. It acknowledges that data canbe corrupted due to program error. If this happens, the support staff mayattempt to correct the contaminated data with application programs. Failing theability to correct the data with application programming, a scenario such as oneof those previously described could be used as a last resort. This approach isgaining favor among users striving for high availability.

In implementing an approach like this, it is important to determine whichtransactions will make the data more corrupt or will propagate the errors. Thisinformation then can either be communicated to the end users, or the DBA canuse it to disable the dangerous transactions.

11.8.3 Point-in-Time Recovery RecommendationsYour strategy should be to avoid a point-in-time recovery if possible. If apoint-in-time recovery must be done, then choose the most efficient recoveryscenario given your environment. More specifically, the following isrecommended:

1. Point-in-time recovery using user-written application programs

This is the preferred approach among users when possible. It has thefollowing benefits:

There is little or no disruption to the user.


Data which has not been corrupted will be available to the user.However, the user may see erroneous data prior to the recovery.

There is no loss of data entered between the time the data contaminationwas introduced into the system and the time the contaminated data wascorrected.

Required processor resources are likely to be far less than using eitherof the other techniques.

Do not forget that this is an ideal and not a rigorous scenario that can bedocumented and tested. You must be prepared to reset your system bydoing the point-in-time recovery when a “programming fix” is not possible orpractical.

2. Point-in-time recovery not using DB2 utilities

The issue regarding this and the following scenario is the number of tablespaces and indexes that must be recovered to an established point ofconsistency. As the number of tables and indexes to be recovered grows,the dump-restore scenario becomes the practical alternative. Dumpingpacks and restoring data is clearly faster than a recovery-based scenario.

The major disadvantage to this scenario is that the dumping of the data isdisruptive to the user. The BaanERP system must be stopped to dump datathat is consistent. An additional disadvantage inherent in any point-in-timerecovery scenario is that work is lost when data is reset to a prior point ofconsistency.

It is recommended that you seriously consider implementing this scenariousing SnapShot on the RAMAC Virtual Array. The advantages andconsiderations of using SnapShot on the RAMAC Virtual Array are:

You must stop BaanERP in the DB2 environment to establish a point ofconsistency.

This is necessary in any point-in-time recovery scenario.

You may SnapShot the data at the volume level quickly.

Tests show that a volume can be snapped in 3 to 5 seconds.

When the snapshot is complete, the data can be made available to theuser.

Once the snapshot is complete, the data can be copied to tape as abackground task.

This DASD-to-tape process does not interfere with user access toBaanERP data.

When a point-in-time recovery is required, the data can be quicklyrestored from the tape backup.

For more information on SnapShot on the RAMAC Virtual Array, seeImplementing SnapShot, SG24-2241.

3. Point-in-time recovery using DB2 utilities

This scenario is preferred over the point-in-time recovery not using DB2utilities scenario when few table spaces and indexes are to be recovered.The benefit of this scenario is minimal-to-no disruption to the user during thedaily QUIESCE/COPY step. However, as long as there is the potential torecover a large number of table spaces and indexes, this scenario may notbe usable.



Appendix A. BPX Parameters

These are the BPX paramters we used in our installation.

MAXPROCSYS(30000) /* System will allow at most 200 00740008processes to be active 00750000concurrently. Was 300 RC */ 00760008

00770000MAXPROCUSER(30000) /* Allow each user (same UID) to 00940008

have at most 200 concurrent 00950000processes active. Was 10125 */ 00960008

00970000MAXUIDS(2000) /* Allow at most 50 OpenEdition MVS 01110008

users to be active concurrently 01120008Was 50 RC */ 01130008

MAXFILEPROC(65535) /* Allow at most 65535 open files 01320000per user (the max) */ 01330000

01340000MAXPTYS(256) /* Allow up to 256 pseudo-terminal 01480000

sessions */ 0149000001500000

MAXRTYS(256) /* Allow up to 256 remote-terminal 01640000sessions */ 01650000

01660000CTRACE(CTIBPX00) /* Parmlib member 'CTIBPX00' will 01810000

contain the initial tracing 01820000options to be used */ 01830000

01840000USERIDALIASTABLE('/etc/alias') /* HFS file /tablename will 02220003

contain the list of MVS userids 02230000and their corresponding XPG4 02240000compliant alias names. */ 02250000

02260000FILESYSTYPE TYPE(HFS) /* Type of file system to start */ 02600000

ENTRYPOINT(GFUAINIT) /* Entry Point of load module */ 02610000PARM(' ') /* Null PARM for physical file 02620000

system */ 02630000/* ASNAME(adrspc01) */ /* Name of address space for 02640000

physical file system */ 0265000002660000

/* files */ 03040000ROOT FILESYSTEM('OMVS.OS390R6.&SYSNAME..&SYSR1..ROOT') 03050000

TYPE(HFS) /* TYPE OF FILE SYSTEM */ 03060000MODE(RDWR) /* (OPTIONAL) CAN BE READ OR RDWR. 03070000

DEFAULT = RDWR */ 0308000003090000

MOUNT FILESYSTEM('OMVS.&SYSNAME..ETC') 03100000MOUNTPOINT('/etc') 03110000TYPE(HFS) MODE(RDWR) 03120000

03130000MOUNT FILESYSTEM('OMVS.&SYSNAME..USERS') 03140000

MOUNTPOINT('/u') 03150000TYPE(HFS) MODE(RDWR) 03160000

03170000MOUNT FILESYSTEM('OMVS.&SYSNAME..VAR') 03180002

MOUNTPOINT('/var') 03190002TYPE(HFS) MODE(RDWR) 03200002

03210002


FILESYSTYPE TYPE(TFS) ENTRYPOINT(BPXTFS) 03700000MOUNT FILESYSTEM('/TMP') 03710000

TYPE(TFS) MODE(RDWR) 03720000MOUNTPOINT('/tmp') 03730000PARM('-s 500') 03740000

03750000FILESYSTYPE TYPE(UDS) ENTRYPOINT(BPXTUINT) 05100000NETWORK DOMAINNAME(AF_UNIX) 05110000

DOMAINNUMBER(1) 05120000MAXSOCKETS(32000) 05130008TYPE(UDS) 05140000

05150000FILESYSTYPE TYPE(CINET) 05160000

ENTRYPOINT(BPXTCINT) 05170000NETWORK DOMAINNAME(AF_INET) 05180000

DOMAINNUMBER(2) 05190000MAXSOCKETS(32000) 05200008TYPE(CINET) 05210000INADDRANYPORT(10000) 05220000INADDRANYCOUNT(2000) 05230000

05240000SUBFILESYSTYPE NAME(TCPIPOE) 05250000

TYPE(CINET) 05260000ENTRYPOINT(EZBPFINI) 05270000DEFAULT 05280000

05290000SUBFILESYSTYPE NAME(TCPIPMVS) 05300000

TYPE(CINET) 05310000ENTRYPOINT(EZBPFINI) 05320000

05330000SUBFILESYSTYPE NAME(TCPKMT) 05340000

TYPE(CINET) 05350000ENTRYPOINT(EZBPFINI) 05360000

05370000SUBFILESYSTYPE NAME(OESTACK) 05380000

TYPE(CINET) 05390000ENTRYPOINT(BPXUIINT) 05400000

05490000FILESYSTYPE TYPE(NFS) ENTRYPOINT(GFSCINIT) 05500000

ASNAME(MVSNFSC6) 0551000105520000

MAXTHREADTASKS(1000) /* System will allow at most 10000 06330000threads tasks to be active 06340000concurrently in a single process 06350000

*/ 0636000006370000

MAXTHREADS(1000) /* System will allow at most 10000 06520000threads to be active 06530000concurrently in a single process 06540000

*/ 0655000006560000

IPCMSGNIDS (20000) 07400000IPCMSGQBYTES (262144) 07410000IPCMSGQMNUM (10000) 07420000IPCSHMNIDS (20000) 07430000IPCSHMSPAGES (2621440) 07440000IPCSHMMPAGES (25600) 07450000IPCSHMNSEGS (1000) 07460000IPCSEMNIDS (20000) 07470000


IPCSEMNSEMS (32767) 07480000IPCSEMNOPS (32767) 07490000

07500000MAXMMAPAREA(4096) /* System will allow at most 4096 07660000

pages to be used for memory 07670000mapping. 07680000

*/ 0769000007700000

MAXCORESIZE(4194304) 0821000008220000

MAXASSIZE(2147483647) 0847000008480000

MAXCPUTIME(2147483647) 0879000008800000

MAXSHAREPAGES(32768000) /* System will allow at most MAX 09110000pages of shared storage to be 09120000concurrently in use */ 09130000

09140000FORKCOPY(COPY) /* System will use copy-on-write 09400000

for fork system calls if the 09410000suppression-on-protection 09420000hardware feature is available 09430000

*/ 0944000009450000

SUPERUSER(BPXROOT) 0956000009570000

TTYGROUP(TTY) 0972000009730000

STARTUP_PROC(OMVS) 098100000982000010000000

If you want to have your Baan HFS mounted at IPL you should addthe following lines with the other mount commands:

MOUNT FILESYSTEM('BAANERP.CDROM')MOUNTPOINT('/baanerpcdrom')TYPE(HFS) MODE(RDWR)

MOUNT FILESYSTEM('BAANERP.INSTALL')MOUNTPOINT('/baanerpinstall')TYPE(HFS) MODE(RDWR)

MOUNT FILESYSTEM('BAANERP.APPL.BSE')MOUNTPOINT('/baanerp')TYPE(HFS) MODE(RDWR)

Appendix A. BPX Parameters 113


Appendix B. The vi Editor and Common UNIX Commands

During the installation of Baan applications on OS/390, much of the work is doneusing a Telnet connection to UNIX services. In this mode, the command oeditmay not be usable to perform editing. The vi editor that comes with UNIXservices is used to edit the files with EBCDIC characters. Some of the Baan filessuch as bi.html contain ASCII characters. For these files, you will need theviascii editor. The viascii editor can be downloaded from the following Web site:

:http//www.s390.ibm.com/products/oe/bpxaltoy.html

The viascii editor should be placed in the /bin directory.

The viascii editor uses iconv and vi to edit a file with ASCII characters; the file istemporarily stored in the /tmp directory. Many permission checks are in placeand this script will not update the time stamp of your file if you make nochanges. The commands are the same as for the vi editor.

The vi commands and common UNIX commands are included in B.1, “Using thevi Editor” for those not familiar with UNIX. There are several reference books onthe commands, such as Learning the vi Editor, Linda Lamb, O'Reilly &Associates, February 1986. You may also wish to consult UNIX for Dummies,John R. Levine and Margaret Levine Young, IDG Books Worldwide, 1997.

B.1 Using the vi EditorSome vi commands are single-character-oriented. One example is r; if the userenters r and then a character, the character replaces the character where thecursor is located. Other vi commands are multiple-character in nature; thosecommands cause vi to enter input mode, and input mode is ended with theescape key. An example is R; if the user enters R and then one or morecharacters, the characters replace those previously in the file. Replacementcontinues until the escape key is used.

B.1.1.1 Common vi Commands(spacebar) Move cursor forward (right) 1 character (cursor movement key)

/pattern Search forward for pattern

/ Repeat previous search (forward)

? Repeat previous search (backward)

?pattern Search backward for pattern

. Repeat last editing command

$ Move cursor to last character of current line (cursor movement key)

0 Move cursor to first character of current line (cursor movement key)

a Insert text after cursor (ended by escape key)

A Insert text at end of current line (ended by escape key)

dd Delete line (may be followed by P to put the line, effectively movingthe line)

G Move to last line of file


h Move cursor back (left) 1 character (cursor movement key)

i Insert text before cursor (ended by escape key)

I Insert text at beginning of current line (ended by escape key)

j Move cursor down (forward) 1 line (cursor movement key)

J Join two lines

k Move cursor up (backward) 1 line (cursor movement key)

l Move cursor forward (right) 1 character (cursor movement key)

n Repeat previous search (same direction)

N Repeat previous search (opposite direction)

p Put yanked or deleted text before current line

P Put yanked or deleted text before current line

r Replace a character

R Replace characters (ended by the escape key)

s Delete character and substitute text (ended by escape key)

S Delete current line and substitute text (ended by escape key)

u Undo last edit

U Undo last edit

:w Write (save) the file

:w! Write (save) the file (overriding protection)

x Delete character

X Delete character before cursor

yy Yank (copy to buffer) a line (usually followed by P)

Y Yank (copy to buffer) a line (usually followed by P)

B.1.1.2 Ending the vi SessionTo end the vi editor, use one of the following:

:q! Quit, discarding any changes

:q Quit

ZZ Write (save) the file, then quit

:x Write (save) the file, then quit

:wq Write (save) the file, then quit

B.2 Common UNIX CommandsDuring the installation, we frequently used the following commands:

cat List a file

cd Make another directory the current directory

chgrp Change file or directory group

chmod Change file or directory access permissions

chown Change file or directory ownership


cp Copy a file or directory (makes a new copy)

df Show the status and capacity of file systems

env List the environment variables

find Find the path to a file in the filesystem

grep Select lines from a file

kill Send a signal to a process (kill -9 terminates a process )

ls List the contents of a directory

mkdir Create a directory

mv Move a file or directory (re-locates, no new copy)

ps Show processes in a system

pwd Display the name of the current directory

rm Remove a file (may remove a directory with an appropriate flag)

rmdir Remove a directory

tar Creates or restores an archived version of a directory

touch Create an empty file or change the last changed date of a file

who Display logged in users

more Display a file, stopping at each logical page (screen)

head Displays the first few (default 10) lines of a file

tail Displays the last few (default 10) lines of a file

wc Counts the number of lines, words, and bytes in a file

Appendix B. The vi Editor and Common UNIX Commands 117


Appendix C. The hostname Command

The Baan db2_install6.1 script expects to be able to execute the hostnamecommand, which is not part of UNIX Systems Services. The following programwill create the hostname command for UNIX Services.

Unlike the hostname command on some other Posix superset platforms, thisversion does not support setting the hostname. Setting the hostname is specificto each AF_INET PFS.

This hostname command does not currently support binding to a specific PFS viaan environment variable or any other mechanism.

C.1 Using the hostname CommandEnter hostname to display the full hostname with domain name (if specified to thetransport driver).

Enter hostname -s to see just the host name without the domain name.

You could use your host name in your shell prompt as follows (optimized forspeed):

In your shell profile, use something like the following to set the HOSTNAMEenvironment variable:

export HOSTNAME=¦hostname -s¦export HOSTNAME=“hostname -s”

Note that the quote marks are backward quote marks, so that "hostname -s"is first executed and then HOSTNAME is set to the output of "hostname -s" .

In your shell profile, use something like the following to put the host name inyour shell prompt:

export PS1="$HOSTNAME:$LOGNAME:$PWD: >"

To build the hostname command, compile it from the shell with the c89command:

c89 -o hostname hostname.c

Note: Check that the HEAP value in the $_CEE_RUNOPTS variable does nothave any value set.

C.1.1 Source Code for the hostname CommandFollowing is the source code that you can compile to produce the hostnamecommand.


à ð#include <stdio.h>#include <string.h>

#include <unistd.h>

int main(int argc,char **argv){

char *dotpos;char hostname[2000 ];int dontPrintDomain = 0, rc = 0;

if (argc == 2 &&!strcmp(argv[1],"-s"))

dontPrintDomain = 1;else if (argc != 1){

fprintf(stderr,"Usage: %s [-s]\n""Specify \"-s\" to print the host name without\n""the domain name.\n",argv[0]);

rc = 1;}

if (!rc){

rc = gethostname(hostname,sizeof(hostname));if (rc){

perror("gethostname");rc = 1;

}else{

if (dontPrintDomain){

dotpos = strchr(hostname,'.');if (dotpos)

*dotpos = '\0';}printf("%s\n",hostname);

}}return rc;

}á ñ


Appendix D. Executing the db2_install6.2 Script

This appendix describes how we used the db2_install6.2 script to do all the DB2preparation for a Baan installation (that is, without using JCL or DDL) to set up asimple configuration to create the DB2 environment. The script db2_install6.2assists you in creating the DB2 environment so you can do the following tasks:

Perform DB2 system administration tasks:Create the DB2 STOGROUP (for the DASD)Create the DB2 DatabasesCreate tablespaces in the databaseGrant dbadm authority to the userids

Create control files required by Baan to load the data for Company 000 andthe Demo companies:

db2_groupdb2_usersdb2_storage

We used the script to create:

STOGROUP BERPGRP

Database BERP000

Tablespace TS000

Tables *

Indexes *

The * means use the default table

The following screens show the questions and answers we used to create ourdatabase, tablespace and files. We took the defaults whenever we could.

Attention

Be patient in replying to the questions, because the script will generally takea few seconds to provide a default answer. Also, do not type Yes and pressEnter, because the enter will be taken as the answer to the followingquestion. Just type y or n.

This is the first screen:


à ðDB2 Server Installation

Before invoking this script, a DB2 subsystem must have been defined

This script will do following things for the DB2 subsystem.

- Create storage group and grant privileges to use thestorage group.

- Create database and grant privileges on database.- Create tablespace and grant privileges to use the tablespace- Create group and user files.

Add initial group to group file.Add users root, bsp, ROOT, and BSP to group.

- Create storage file.Add default entries for table & index to storage file.

Note: Check db2_inst.log in the current directory for any errorRead Installation Document Carefully regarding specification

of DB2 for OS/390.O.K to continue ? Y

á ñ

D.1.1 Listing Environment V ariablesThis screen shows the environment variables.

à ðEnvironment Variables

*** db2_install6.2 Started ***

- HOST wtsc55oe

- LOGNAME root

- BSE /baanerp/bse

Press any key .

á ñ

Note: If you have not installed the hostname command as described inAppendix C, “The hostname Command” on page 119, you will get the followingerror message but it will not cause any problem:

hostname: initial_setup: db2_install6.2 1677: FSUM7351 not found:

At this point there are a series of questions to answer about the layout of yourdatabase. The order of the questions will change, depending on how youanswer these questions. Remember, do not press Enter; instead, just type y orn.


D.1.2 Storage Group CreationThese are the questions you must answer to create the STOGROUP if you wantthe Baan db2_install6.2 script to do this for you.

D.1.2.1 Creating stogroupThis how we answered the questions to create BERPGRP.

à ðStorage Group Creation

Want to create storage groups (Y?N) ? y

á ñ

D.1.2.2 Granting Use of stogroupThe first time we added user IDs bsp and root. Root cannot grant privileges toitself, so the script failed and we had to restart.

à ð

Storage Group Creation

Grant Use Of STOGROUP

Enter storage group name : BERPGRP

Enter Authorization name : PUBLIC

Granting use of storage group 'BERPGRP' ....

Granted use of storage group 'BERPGRP'

Create another storage group (Y/N) ? Ná ñ

D.1.3 Database CreationThese are the questions you must answer to have the Baan db2_install6.2 scriptcreate a database for you.

D.1.3.1 Creating a DatabaseThis how we answered the questions to create a database.

Appendix D. Executing the db2_install6.2 Script 123


Want to create a database (Y?N) ? Y

Database Name : BERP000

Storage Group Name (Not Mandatory-Default) : BERPGRP

Buffer Pool (Not Mandatory-Default) : BP3.....

Want to specify CCSID (Y/N) ? N

Create database 'BERP000' (Y/N) ? Y

Creating database 'BERP000' ....Database 'BERP000' is created

Want to grant database privileges (Y/N) ? Y

á ñ

We specified the value of CCSID in the DB2 parameters, so we did not have tospecify it here again.

D.1.3.2 Granting Privileges to DatabaseThis is how we answered the questions to grant privileges to the database.


Grant Database Privileges

Enter Privileges : DBADM

Database name : BERP000


Granting privileges to Database 'BERP000' ....Privileges granted on database 'BERP000'

Create another database (Y/N) ?

á ñ

D.1.4 Tablespace CreationThese are our answers to creating a tablespace. This creates one table spacefor Company 000.



Tablespace Name : baan

Database Name (Not Mandatory-Default) : XXX

Do you want to create tablespace?

Tablespace Name:TS000

Database Name: BERP000

Specify using-block

Using VCAT or STOGROUP ? : STOGROUP

Storage Group Name : BERPGRP

Want to specify space allocations (Y/N) ? Y

Primary Space Quantity : 1440000

Secondary Space Quantity : 144000..

Want to specify gbpcache-block (Y/N) ? N

Will this table space be segmented (Y/N) ? Y

Segment size (SEGSIZE) ? : 32

Want to specify BUFFERPOOL (Y/N) ? Y

Buffer Pool Name : BP3

Want to specify LOCKSIZE (Y/N) ? Y

Lock Size (ANY/TABLESPACE/TABLE/PAGE/ROW) : ROW.........

Want to specify MAXROWS (Y/N) ? N

Create Tablespace 'TS0000' (Y/N) ? Y

Creating Tablespace 'TS0000' ....Tablespace 'TS0000' was created successfully

Want to grant use of tablespace (Y/N) ? Yá ñ

D.1.4.1 Granting Use of TablespaceThese are our answers about granting privileges to the tablespace.



Grant Use Of Tablespace

Enter database-name.tablespace-name : BERP000.TS0000


Granting use of tablespace 'BERP000.TS0000' ....

Granted use of tablespace 'BERP000.TS0000'Want to create another tablespace (Y/N) ? N

á ñ

D.1.5 Creating DB2 Reference Files for Baan ScriptThis step creates three files that Baan install6.2 script uses to build and load thedatabase.

D.1.5.1 Group File CreationThis will create db2_groups.

à ðGroup File Creation

Want to create initial group (Y/N)? Y

á ñ

à ð

Group File Creation

Initial Group : db2berp

Group Password : db2berp

Is above data correct (Y/N) ? Y

Add group “db2berp” (Y/N) ? Y

Adding group “db2berp”Group added.

Press any key .

á ñ

D.1.5.2 Creating the User FileThe following will create db2_users.


à ð

User File Creation

Add users “root,”“bsp” , “ROOT,”“BSP” (Y/N) ? Y

á ñ

à ð

User File Creation

Add Baan user “root” to Group “db2berp” (Y/N) ? Y

DB User : root

Adding user “root” to group “db2berp”User added to group.

Press any keyá ñ

This is repeated four times, once for each user: bsp, BSP, root, and ROOT.

à ð

User File Creation

Add other users (Y/N)? N

á ñ

D.1.5.3 Creating the Storage FileThe following will create db2_storage.

Note: We did not specify any particular tables at this time for Company 000, andthe script used the defaults of * *.

à ð

Storage File Creation

Create db2_storage Entries ? Y

á ñ


à ðDo you want to specify Company Data ? N

Update Index Parameters

Company: * Table spec: *

Current Index parameters:

STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3Do you wish to modify ? N

'/baanerp/bse/lib/db2/db2_storage' updated successfulCompany: * , Table: *

á ñ

à ðFollowing lines are added to the file '/baanerp/bse/lib/db2/db2_storage'

*:*:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3*:*:T:group:01:5:ARR_SIZE 1 OPT_ROWS 5 T_SPACE BERP000.TS0000

á ñ

à ðdb2_install6.2 completedbshell6.2> exit

á ñ

D.1.6 Files Baan Will Use to Define the DatabaseAfter the script has been run, the STOGROUP, Database and Tablespace havebeen created, privileges have been granted and the following files will be indirectory /baanerp/bse/lib/db2:

à ð$ ls


This is db2_storage:


á ñ

This is db2_groups:


á ñ

This is db2_users:


à ðBSP:BSP:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:db2berpbsp:bsp:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:db2berproot:root:&l%d(43‘"Bd5g+jaj2I1/o,-0H){c3:E:db2berpROOT:ROOT:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:db2berp

á ñ

D.1.7 Adding More Users and Data LaterYou can use this script later on when you are ready to add more users or loadother Baan companies. There is also a db2_admin script. See BaanERP -Installation Guide for BaanERP on OS/390 UNIX System Services for moreinformation.



Appendix E. RAMAC Virtual Array (RVA)

This section gives the reader who is unfamiliar with the RAMAC Virtual Array(RVA) an overview of the device architecture and its unique SnapShot function.

E.1 Overview of RAMAC Virtual ArrayThe RVA is a high-performance RAID 6 storage subsystem. RAID 6 protectsagainst data loss even in the unlikely event that two disks are lost in the array.The RVA RAID implementation has automatic hot-sparing: if a disk fails, thedata on that disk is immediately recreated on a spare disk in the array, thusrestoring RAID protection. The failed disk can be nondisruptively replaced andbecomes the new spare.

The RVA RAID implementation is transparent to users and, unlike most RAID 5or RAID 6 implementations, has no adverse effect on performance thanks to theadvanced architecture of the RVA.

Traditional storage subsystems, such as the 3880, 3990, and RAMAC Array DASDfamily, use the count key data (CKD) architecture. The CKD architecture defineshow and where data is stored on the disk device. Any updates to the data arewritten directly to the same position on the physical disk from which the datawas retrieved prior to the update. This is referred to as update in place.

IBM's RVA provides a high-availability, high-performance storage solution,thanks to its revolutionary virtual disk architecture. To the host, the RVAappears as up to four traditional 3990 subsystems, with up to 1024 3380 and/or3390 volumes. These devices do not physically exist in the subsystem and arereferred to as functional devices. In reality, the subsystem containsRAID-protected arrays of fixed block architecture (FBA) disk devices. The RVAtranslates I/O requests from CKD format to FBA format.

E.2 Log Structured FileThe RAID-protected FBA disk arrays that make up the RVA's physical disk spaceare sequentially filled with data. New and updated data is placed at the end, asit is on a sequential or log file. We call this a log structured file.

Updates leave areas of data that are no longer needed in the RVA log file. Amicrocode recycle process called freespace collection ensures that these areasare removed so that there is always enough freespace for writing. (This issimilar to a reorg of the data.) You can control the freespace by observing thenet capacity load (NCL) of the RVA and using the IBM Extended FacilitiesProduct (IXFP) program. The RVA's physical disk space typically should not befilled above 75% NCL. Above that level, the freespace collection process runswith higher priority, and performance degradation may result.

The following tables are used to map the tracks of functional devices to the FBAblocks related to those tracks.

Functional device table

The functional device table (FDT) holds the information about the functionalvolumes that have been defined to the RVA.


Functional track directory

The functional track directory (FTD) is the collective name for two tables thattogether map each functional track to an area in the RVA's physical storage:

− Functional track table

The functional track table (FTT) contains the host-related, that is, thefunctional device-related track pointers of the FTD.

− Track number table

The track number table (TNT) contains the back-end data pointers of theFTD. A reference counter is also part of this table.

Although the FTD consists of two tables, we discuss it as one entity. In fact,each functional track has an entry in the FTD. If a functional track contains data,its associated FTD entry has a pointer to the FBA block where the data starts.The data of a functional track may fit on one or more FBA blocks.

If the data of a functional track is updated, the RVA puts the new data in a newplace in the log structured file, and the FTD entry points to the new data location.There is no update in place. Figure 51 shows the virtual disk architecture.

Figure 51. Virtual Disk Operation. In the first FDT box, 100 33903 stands for Volume 100of a 3390 model 3. In the FTT box, CC is cylinder 5, HH is head 4, T is track 3452.

E.3 Data Compression and CompactionBecause update in place does not occur in the log structured file, data can becompressed. In fact, all data, as soon as it enters an RVA, is compressed (to theextent possible). In addition, the gaps between the records, as they appear onthe CKD devices, are removed before the data is written to disk. This is calledcompaction. Experience shows that RVA customers can achieve an overallcompression and compaction ratio of 3.6:1.


E.3.1 Effect of Data CompressionThe effect of data compression on the RVA subsystem is that it speeds up thetransfer of data to and from the back-end disk arrays to cache and it increasesthe effectiveness of the cache memory since more data can fit in cache due toits compression. The subsystem Effective Capacity attempts to give the users asuggested guideline as to how much traditional non-compressed data will fit inthe RVA subsystem based on the current compression algorithm.

Many types of data such as documents, JCL, batch and TSO data compress verywell in the RVA. Other applications may sometimes use host compression orinternal compression software to achieve the same benefits of compressed datafor storage and transmission. This data, when placed on the RVA, will becompressed internally as is all data that enters the RVA subsystem. However,data that is very random in nature either by content or because of previouscompression will not compress as well within the RVA as non-compressed data.

Therefore, the user should understand that if the only data that is to be placedon an RVA subsystem is pre-compressed or highly random numerical data, theremay not be as good internal compression as expected and the Effective Capacityof the RVA, which is based on non-compressed data, may be inaccurate. If thecompression of the data to be placed on the RVA is known or can beapproximated, this number can be used times the physical capacity of the RVAdisk arrays to give an approximate effective capacity value for that data.

If the DA Capacity of the RVA, as shown on the Subsystem Configuration panelor Local Operator Panel of the subsystem, is 117.4 GB, then the EffectiveCapacity of that subsystem is generally thought to be 420 GB, based on a 3.6compression.

If the data to be stored on that RVA shows 3.0 compression, then the effectivecapacity would be 352 GB.

If the data to be stored only compressed 2.5 to one, then the Effective Capacity ofthe subsystem would only be 293 GB.

Note: The data compression on the HFS files has been in the range of 1.8 to onefor Baan files.

These numbers represent the amount of data that should fit in 75% NCL of theRVA subsystem. More information is available in DB2 for OS/390 and DataCompression, SG24-5261, and IBM RAMAC Virtual Array, SG24-4951.

Appendix E. RAMAC Virtual Array (RVA) 133


Appendix F. SnapShot

The RVA's virtual disk architecture enables you to produce almost instantaneouscopies of data sets and volumes. We call this function SnapShot. Snapshotproduces copies without data movement. We call making a copy with SnapShotsnapping the data. The term snap also refers to the resulting copy of the data.

Conventional methods of copying data on DASD consist of making a physicalcopy of the data on either DASD or tape. Host processors, channels, tape, andDASD controllers are involved in these conventional copy processes. Copyingmay take a lot of time, depending on the availability of system resources.

With SnapShot, copying is achieved with no data movement. Snapping can takejust seconds rather than minutes or hours, because data is not moved and thehost processor and channels are not involved in data transfer. Furthermore,additional physical disk space is not required to accommodate the snap untileither the source or the target is updated. As far as the operating system isconcerned, the snap is a real copy of the data; as far as the RVA hardware isconcerned, it is a virtual copy of the data.

F.1 How SnapShot W orksA functional device is represented by a certain number of pointers in the FTD.Every used track has a pointer to its back-end data in the FDT.

The RVA's virtual disk architecture enables you to make a copy of a data set orvolume by copying its FTD pointers. As you can imagine, this is a very fastprocess. No data movement takes place, and no additional back-end physicalspace is used. Both FTD pointers (the original and the copy) point to the samephysical data location. Figure 52 shows how SnapShot works.

Figure 52. SnapShot Operation

Only when either the original or the copied track is updated is its associated FTDpointer changed to point to the new data location. The other FTD pointerremains unchanged. Additional space is needed in this case. As long as there


is a pointer to a data block in the physical disk storage, the block cannot becomefree for the freespace collection process. A reference counter in the TrackNumber Table (TNT) prevents the block from becoming free.

On the RVA side, the execution of the SnapShot function is quite simple; on theOS/390 side, some additional operations are necessary. If a data set is snapped,a new data set name is required and given in the snap command. After the RVAperforms the snap, OS/390 must update the catalog and VTOC (as well as theVVDS, if the snap is performed on a VSAM data set).

Although the creation of the copy is a logical manipulation of pointers, the dataexists on disk, so in this sense it is not a logical copy. As far as the operatingsystem is concerned, the two copies are completely independent of each other.

When you make a copy with SnapShot, both the source and the target must bewithin the same RVA. For further information about SnapShot, see ImplementingSnapShot, SG24-2241.

F.2 What Is Virtual Concurrent CopyIn this section we describe the functions of virtual concurrent copy andDFSMSdss SnapShot. These functions combine the data duplication function ofIBM SnapShot for MVS/ESA with the flexibility and operability of DFSMSdss.

Both functions are delivered through a small programming enhancement (SPE)to DFSMSdss. Integration of SnapShot with DB2 is provided through virtualconcurrent copy.

F.2.1 DFSMSdss SnapShotDFSMSdss SnapShot enables you to take advantage of SnapShot when you arecopying data within a single RAMAC Virtual Array (RVA). When you specifyDFSMSdss COPY, and both the source and target data sets are in the sameRVA, SnapShot is automatically invoked.

There are no changes to JCL, and your copy jobs instantly benefit fromSnapShot, both in terms of the speed of the copies and the fact that SnapShotdoes not use any additional back-end space to make a copy.

F.2.2 Virtual Concurrent CopyVirtual concurrent copy extends the benefits of SnapShot to DB2 users. DB2already has integrated support for 3990 concurrent copy through theCONCURRENT keyword in a COPY utility.

When you specify the CONCURRENT keyword on a DB2 image copy, theDFSMS/MVS software can detect whether you have an RVA. If you have an RVAwith SnapShot, the virtual concurrent copy function is invoked.

Concurrent copy enables you to take a consistent copy or dump of data, usingDFSMSdss, while applications are updating the data. The logical completion ofthe point-in-time copy occurs when the source data is snapped into an interimdata set called the working space data set (WSDS). Because there is no actualmovement of data, snapping can take seconds rather than minutes or hours, andhost processor and channels are not involved in the data transfer.


The physical completion occurs when the data is moved by DFSMSdss to thetarget tape or disk data set. Once the copy is logically complete, the data canbe made available for application updates. Figure 53 on page 137 shows thevirtual concurrent copy operation.

Figure 53. Virtual Concurrent Copy Operation. One target is a copy to disk and the othertarget is a copy to a tape cartridge.

If you are already using concurrent copy, you do not have to make changes toyour JCL to use virtual concurrent copy. For further information on virtualconcurrent copy, see Implementing DFSMSdss SnapShot and Virtual ConcurrentCopy, SG24-5268.

Appendix F. SnapShot 137


Appendix G. Installation Problems We Encountered

This chapter describes the problems we encountered during installationactivities with earlier versions of the Baan Application code, as well as how werestarted the scripts after encountering the problems.

Although you should not encounter such scenarios, they are included as hintsand tips.

G.1 Problems and WorkaroundsDuring the installation process, we ran into several areas that required aworkaround. A summary of these problems and their workarounds are asfollows:

Problem

We exceeded the number of allowable VSAM extents on index files.

Workaround

We increased the secondary allocation for indexes in db2_storage. we used thealter tablespace command to increase the size then reorg the tablespace.

Alternately ,you can also rename the old index, create a new index VSAM filewith a larger primary and secondary extent, and then use the REPRO commandto copy the data over to the new larger file. Another choice is to use theDFDSCOPY utility.

However, as we had many of these errors, we restarted with the largersecondary quantity. If you use the sample db2_storage files, you should notencounter this.

Problem

While loading the demo companies, DB2 was short on storage.

Workaround

We increased the paging and CSA space to load the demo companies. Wefound sometimes it was easier to restart if we had serious problems with DB2 atthe beginning of the installation.

Problem

We were told we would run out of VTOC space when loading the democompanies because of the large number of index files.

Workaround

We increased the VTOC space on one volume to 30 cylinders.


Problem

We had a problem with ASCII mode and DB2 (we had DB2 return code 1332).

Workaround

We had to change the SSCID parameter from 1 to 37.

Problem

We had several PATH problems because $PATH and $LIBPATH were not setcorrectly.

Workaround

If you correctly set your environment variables you should not encounter thissituation. The first time it could not find db2srv61. Although the messagereferred to shared memory, we had to set LIBPATH to /baanerp/bse/bin, wheredb2srv61 resides.

Problem

We had a problem when the script spawned another process while it was settingpermissions.

Workaround

We did not have the entry BMP_SPAWN=Yes. This is now set by the install6.2script.

Problem

The database was locked.

Workaround

We had to create a different database and tablespace for Company 550. Whenwe did this we used the db2_install6.2 script, but this adds the new entry at thebottom of the file. Because the first entry is *, the specific entry for 550 willnever be reached. Therefore, we had to manually reorder the entries.

Problem

The group name db2baan was not authorized.

Workaround

We had to grant dbadm privileges to db2baan.

Problem

We received the message: installation aborted: could not find modulegloblvar .

Workaround

We had to follow the installation instructions and modify the install6.2 script tocopy the module to the correct directory.


Problem

The DB2 load library was not found.

Workaround

We had to set the value of the STEPLIB variable before starting the install6.2script by issuing the command:

export STEPLIB=DB2V510.SDSNLOAD

Problem

We could not log on as bsp using the BW Client.

Workaround

We had to copy the file ubsp to uBSP in the directory /baanerp/bse/lib/user.

You should also verify that the bsp profile is correct. To do this, telnet to OMVS,logon as bsp, then issue the env |more command to check that the settings arecorrect.

In addition, if you are using the latest version of TCP/IP, you must add the letters to the end of the following line in the /etc/inetd.conf file:

à ðexec stream tcp nowait OMVSKERN /usr/sbin/orexecd orexecd -LVs

á ñ

G.2 Restarting after Encountering ProblemsIf you try to restart the install6.2 script without clearing any active shmtimertasks, you will get the following messages:

à ðInstallation restarted: Sun Sep 20 16:51:25 EDT 1998

>INSTALLATION ABORTED!! Cannot initialize Shared Memory Manager for temporaryenvironment: Sun Sep 20 16:51:27 EDT 1998

á ñ

à ðStop shared memory for temporary environment...

>INSTALLATION ABORTED!! Couldn't start bshell with object ottiex1289: Mon

13:44:44 EDT 1998

á ñ

Therefore you must first execute the steps, described in G.2.1, “Restarting theinstall6.2 Script” on page 142, before restarting.

Appendix G. Installation Problems We Encountered 141

G.2.1 Restarting the install6.2 ScriptTo restart the install6.2 script to allow it to continue processing, you must clearthe shared memory messages and ensure the paths are set by following thesesteps:

1. Issue the command ps -ef (or ps -ef |more if it creates more than one pageof output) to look for shmtimer tasks that are active. Then issue thefollowing command to stop any active shmtimer tasks:

à ðkill -9 taskidnumber

á ñ2. To check shared memory allocation, issue:

à ðipcs

á ñIf shared memory or semaphore allocations exist, then issue the ipcrmcommand to stop them, as follows.

For shared memory, issue:

à ðipcrm -m (task ID number)

á ñFor semaphore, issue:

à ðipcrm -s (task ID number)

á ñFigure 54 shows we had two tasks to kill.

à ðShared Memory:root @ SC55:/etc>ipcs

Message Queues:T ID KEY MODE OWNER GROUP

q 4 0x00000000 ----------- ALEX SYS1q 5 0x00000000 ----------- ALEX SYS1q 6 0x00000000 ----------- ALEX SYS1

q 7 0x00000000 ----------- ALEX SYS1q 8 0x00000000 ----------- ALEX SYS1Shared Memory:T ID KEY MODE OWNER GROUP

m 3513412 0x01101fd0 --rw-rw-rw- ALEX bspSemaphores:T ID KEY MODE OWNER GROUP

s 151076 0x00000000 --ra-ra-ra- ALEX bspá ñFigure 54. Result of ipcs Command

To stop the memory task, issue:

à ðroot @ SC55:/etc>ipcrm -m 3513412

á ñ


To stop the semaphore task, issue:

à ðroot @ SC55:/etc>ipcrm -s 151076

á ñ

To check that these tasks are no longer there, issue the ipcs commandagain, as follows:

à ðroot @ SC55:/baanerpinstall/install>ipcs

Message Queues:T ID KEY MODE OWNER GROUPq 4 0x00000000 ----------- root SYS1

q 5 0x00000000 ----------- root SYS1q 6 0x00000000 ----------- root SYS1q 7 0x00000000 ----------- root SYS1q 8 0x00000000 ----------- root SYS1Shared Memory:Semaphores:

á ñSometimes the ID number for the memory still appears after you have issuedthe command. This does not cause a problem.

3. Check that all the following variables are set. They allow the script torestart. (This is needed because the script expects these to be set. If youhave been disconnected from your telnet session, these settings will havebeen lost.)

export BSE=/baanerp/bseexport BSE_TMP=$BSE/tmpexport DB2_MVS_SYNTAX=1export _BPX_SHAREAS=YESexport LIBPATH=/baanerp/bse/bin:$LIBPATHexport _BPX_SPAWN_SCRIPT=YESexport TERM=vt100

You may want to verify all your env values at this point.

Attention

A special variable needs to be set as follows when the script abortsbefore completion:

export DS_AS=bshell.inst

This should only be set during a restart, after you have started movingfiles to your temporary $BSE directories.

If you issue this by mistake, you must disconnect your telnet session andre-establish a new one to remove the variable from the system. Usingthe unset command is not sufficient.


G.2.2 Restarting install6.2 from the BeginningTo restart the script, execute the following steps:

1. Issue the command ps -ef or ps -ef |more to look for shmtimer tasks thatare active, then issue the following command to stop any active shmtimertasks.

à ðkill -9 (task ID number)

á ñ2. To check shared memory allocation, issue:

à ðipcs

á ñIf shared memory or semaphore allocations exist, then issue the ipcrmcommand to stop them.

For shared memory, issue:

à ðipcrm -m (task ID number)

á ñFor semaphores, issue:

à ðipcrm -s (task ID number)

á ñThe following shows two active tasks:

à ðShared Memory:root @ SC55:/etc>ipcs

Message Queues:T ID KEY MODE OWNER GROUP

q 4 0x00000000 ----------- ALEX SYS1q 5 0x00000000 ----------- ALEX SYS1q 6 0x00000000 ----------- ALEX SYS1

q 7 0x00000000 ----------- ALEX SYS1q 8 0x00000000 ----------- ALEX SYS1Shared Memory:T ID KEY MODE OWNER GROUP

m 3513412 0x01101fd0 --rw-rw-rw- ALEX bspSemaphores:T ID KEY MODE OWNER GROUP

s 151076 0x00000000 --ra-ra-ra- ALEX bspá ñTo stop the memory task, issue:

à ðipcrm -m 3513412

á ñTo stop the semaphore task, issue:

à ðipcrm -s 151076

á ñ


To check that these tasks are no longer there, issue the ipcs commandagain:

à ðroot @ SC55:/baanerpinstall/install>ipcs

Message Queues:T ID KEY MODE OWNER GROUPq 4 0x00000000 ----------- root SYS1

q 5 0x00000000 ----------- root SYS1q 6 0x00000000 ----------- root SYS1q 7 0x00000000 ----------- root SYS1q 8 0x00000000 ----------- root SYS1Shared Memory:Semaphores:

á ñ

3. To remove existing information in the target file and source directories,execute the following commands:

à ðcd /rm -fr /baanerp/bserm -fr /baanerpinstall/install

á ñNote: The rm command with the -r flag will remove all the data under thedirectory specified. Use this command carefully.

You will receive the following message:

à ðroot @ SC55:/baanerpinstall/install>rm -fr /baanerp/bse

rm: FSUM9196 cannot remove directory "/baanerp/bse": EDC5114Iroot @ SC55:/baanerpinstall/install>rm -fr /baanerp/installrm: FSUM9196 cannot remove directory "/baanerpinstall/install": EDC5114I

root @ SC55:/baanerpinstall/install>

á ñ

This is correct as the file systems are still mounted.

4. Drop the DB2 database as shown in this sample JCL in Figure 55 onpage 146:


à ð//BAAN JOB (999,POK),'BAAN INSTALL',NOTIFY=&SYSUID, 0// CLASS=A,MSGCLASS=T,TIME=1439, 0// REGION=5000K,MSGLEVEL=(1,1) 0//***//***//***/*JOBPARM SYSAFF=SC55//JOBLIB DD DSN=DB2V510D.RUNLIB.LOAD,DISP=SHR// DD DSN=DB2V510.SDSNLOAD,DISP=SHR//CREATETS EXEC PGM=IKJEFT01,DYNAMNBR=20//SYSPRINT DD SYSOUT=*//SYSTSPRT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSTSIN DD *


//SYSIN DD *

DROP DATABASE BERP000A;DROP STOGROUP BAANGRP;

COMMIT;á ñFigure 55. Dropping the DB2 Database

At this point go back to the step where you tar the files, as shown in 5.3.2,“Unpacking Files into Install Directories” on page 41.

G.3 Using Baan Log FilesSome log files are located in $BSE/log. After we loaded Company 000, weissued the command ls-l to view our logs, as shown in Figure 56.

à ðroot @ SC55:/baanerp/bse/log>ls -ltotal 456-rw-rw-rw- 1 bsp bsp 0 Sep 24 14:05 log.ba6.2

-rw-rw-rw- 1 bsp bsp 7170 Sep 25 06:19 log.bdbreconfig6.2-rw-rw-rw- 1 bsp bsp 6634 Sep 25 07:17 log.bshell.inst-rw-rw-rw- 1 bsp bsp 0 Sep 24 15:12 log.compress6.2

-rw-rw-rw- 1 bsp bsp 0 Sep 24 15:15 log.db2-rw-rw-rw- 1 bsp bsp 0 Sep 24 16:36 log.db2.mesg-rw-rw---- 1 bsp bsp 218 Sep 25 07:24 log.oiex1287-rw-rw---- 1 bsp bsp 76431 Sep 25 08:00 log.oiex1288

-rw-rw-rw- 1 bsp bsp 543 Sep 24 16:41 log.pdaemon6.2-rw-rw-rw- 1 bsp bsp 2754 Sep 25 08:00 log.sh_server-rw-rw-rw- 1 bsp bsp 2282 Sep 24 14:10 log.shmmanager6.2

-rw-rw-rw- 1 bsp bsp 1528 Sep 25 07:17 log.shmtimer6.2-rw-rw-rw- 1 bsp bsp 0 Sep 24 13:50 log.shmvalues6.2-rw-rw-rw- 1 bsp bsp 0 Sep 24 15:15 log.sort6.2

á ñ

Figure 56. Baan Llogs


When a problem occurs, go to this log directory and edit the log that has themost recent date and time.

G.3.1.1 Log to Track ProgressThis is a sample of log.oiex1288. The current installation processes throughline.0072.

à ðInstall Runtime Data Dictionary /baanerpinstall/install/line.0023 092598104845Install objects /baanerpinstall/install/line.0023 092598104845Install Data Dictionary /baanerpinstall/install/line.0024 092598104845Repair cpac vrc structure 092598104845

Install Data Dictionary forms /baanerpinstall/install/line.0024 092598104859Install Data Dictionary reports /baanerpinstall/install/line.0024 092598104859Install Data Dictionary scripts /baanerpinstall/install/line.0024 092598104859

Install Data Dictionary libraries /baanerpinstall/install/line.0024 092598104859Install Runtime Data Dictionary /baanerpinstall/install/line.0024 092598104859Install objects /baanerpinstall/install/line.0024 092598104859

Install Data Dictionary /baanerpinstall/install/line.0025 092598104859Repair cpac vrc structure 092598104859

á ñ

Other logs can be found in:

/baanerpinstall/install

/tmp

/etc



Appendix H. Alternate DB2 Layout

This appendix shows an alternate layout for Company 000 that puts the tablesinto more tablespaces and databases.

H.1 JCL Used to Create TablespacesThe JCL we used to create the database is shown in Figure 7 on page 30.Because we restarted several times during the loading of Company 000, weplaced the drop commands at the beginning of the job. When you are creatingthe database and tablespaces, you should also consider assigning bufferpools.This topic is covered in more detail in 11.5.1, “DB2/BaanERP Buffer PoolRecommendations” on page 102. Our JCL uses the following allocation of bufferpools:

BP4 for 60 tablespaces for Company 000BP5 for other tablespaces for Company 000BP6 for tablespaces for Company 813BP8 for tablespaces for Company 900BP10 for tablespaces for Company 999

The db2_storage file, shown in Figure 58 on page 158, has the bufferpoolallocations for indexes:

BP3 for indexes for Company 000BP2 for indexes for Company 813 and Company 900.

Attention

If you choose to use the supplied db2_install6.2 script to create the database,you do not have to run this job.


à ð//BAANDB2 JOB (999,POK),'BAAN INSTALL',NOTIFY=&SYSUID, 00010023//*********************************************************************///* NAME = BAANDDL *///* *///* DESCRIPTIVE NAME = SAMPLE DDL TO CREATE DATABASES & TABLESPACES *///* FOR BAAN ERP INSTALLATION *///* *///* STATUS = VERSION 1 *///* *///* FUNCTION = THIS JCL PERFORMS THE NECESSARY DDL TO BUILD THE *///* BAAN ERP DB2 DATABASE. THE FOLLOWING DDL MATCHES THE *///* SETUP SUPPLIED IN THE $BSE/lib/db2/db2_storage FILE. *///* *///* ANY CHANGES TO STOGROUP, DATABASE AND/OR TABLESPACE *///* NAMES REQUIRES THE CORRESPONDING CHANGE IN THE *///* $BSE/lib/db2/db2_storage FILE. *///* *///* YOU MUST UPDATE THE hlq IN THE JOBLIB. *///* *///* CHANGE ACTIVITY = *///*********************************************************************///JOBLIB DD DSN=DB2V510.SDSNLOAD,DISP=SHR//CREATDDL EXEC PGM=IKJEFT01,DYNAMNBR=20//SYSPRINT DD SYSOUT=*//SYSTSPRT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSTSIN DD *


//SYSIN DD *

CREATE STOGROUP BERPGRP

VOLUMES (BAAPK5,BAAPK6,BAAPK7) VCAT DB2V510D;

COMMIT;CREATE DATABASE BERP000A

STOGROUP BERPGRPBUFFERPOOL BP2;

CREATE DATABASE BERP000BSTOGROUP BERPGRPBUFFERPOOL BP2;


COMMIT;á ñ

Figure 57 (Part 1 of 6). JCL to Create Tablespaces with Company 000 Detailed Setup


à ð

CREATE TABLESPACE TAAD050 IN BERP000A BUFFERPOOL BP4USING STOGROUP BERPGRP






















CREATE TABLESPACE TADV002 IN BERP000A BUFFERPOOL BP4USING STOGROUP BERPGRP






á ñ


Appendix H. Alternate DB2 Layout 151

à ðCREATE TABLESPACE TADV130 IN BERP000A BUFFERPOOL BP4

USING STOGROUP BERPGRPPRIQTY 10500 SECQTY 1050

LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TADV140 IN BERP000A BUFFERPOOL BP4


























LOCKSIZE ROW SEGSIZE 32 CLOSE NO;á ñ



à ðCREATE TABLESPACE TADV997 IN BERP000A BUFFERPOOL BP4






LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTXT001 IN BERP000A BUFFERPOOL BP4






LOCKSIZE ROW SEGSIZE 32 CLOSE NO;

COMMIT;

CREATE TABLESPACE TTADV IN BERP000B BUFFERPOOL BP4USING STOGROUP BERPGRP


CREATE TABLESPACE TTAAD IN BERP000B BUFFERPOOL BP4USING STOGROUP BERPGRP


CREATE TABLESPACE TTCHM IN BERP000B BUFFERPOOL BP4USING STOGROUP BERPGRP


CREATE TABLESPACE TTCMT IN BERP000B BUFFERPOOL BP4USING STOGROUP BERPGRP


CREATE TABLESPACE TTCON IN BERP000B BUFFERPOOL BP4USING STOGROUP BERPGRP


CREATE TABLESPACE TTDBA IN BERP000B BUFFERPOOL BP4USING STOGROUP BERPGRP


á ñ



à ðCREATE TABLESPACE TTDBT IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTDDI IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTDLL IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTDSK IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTGFD IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTGUI IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTIEX IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTPCM IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTPTP IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTSEM IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTSQL IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTSTP IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTTBS IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTTLD IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;á ñ



à ðCREATE TABLESPACE TTTLS IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTTSS IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTTST IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTTTD IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTTXT IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TTUID IN BERP000B BUFFERPOOL BP4


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;CREATE TABLESPACE TOTHER IN BERP000B BUFFERPOOL BP5


LOCKSIZE ROW SEGSIZE 32 CLOSE NO;

COMMIT;

CREATE TABLESPACE T813000 IN BERP813 BUFFERPOOL BP6USING STOGROUP BERPGRP


CREATE TABLESPACE T900000 IN BERP900 BUFFERPOOL BP8USING STOGROUP BERPGRP




COMMIT;GRANT DBADM ON DATABASE BERP000A TO BSPGRP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP000B TO BSPGRP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP9999 TO BSPGRP WITH GRANT OPTION;GRANT USE OF STOGROUP BERPGRP TO BSPGRP;

GRANT USE OF ALL BUFFERPOOLS TO PUBLIC;/*//

á ñ


Note: If you have not set up DB2 secondary authid, you will have to add thesegrant statements for BSP.


à ðGRANT DBADM ON DATABASE BERP000A TO BSP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP000B TO BSP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP813 TO BSP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP900 TO BSP WITH GRANT OPTION;GRANT DBADM ON DATABASE BERP9999 TO BSP WITH GRANT OPTION;GRANT USE OF STOGROUP BERPGRP TO BSP;

á ñ

H.2 DB2 Files BaanERP UsesThere are three files that BaanERP uses to set up the loading of theirapplications to the database. You can use the sample ones that BaanERPprovides, or you can create your own using the db2_install6.2 script that isexecuted during the installation process.

It is recommended that you start with the sample files, so at the appropriate timein the installation process, you will move these to the directory/baanerp/bse/lib/db2. Then you can display them as shown by the following lscommand:

à ð$ ls


The following shows db2_groups: The group name becomes the owner ID orcreate ID and must have dbadm or sysadm privileges:


á ñ

The following shows db2_users; these unintelligible character strings areencrypted passwords that are not used for OS/390, but are used in the UNIXimplementation. These files are the same as those used in the UNIXimplementation.

à ðBSP:BSP:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:bspgrpbsp:bsp:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:bspgrproot:root:&l%d(43‘"Bd5g+jaj2I1/o,-0H){c3&colonE:bspgrpROOT:ROOT:pDOH9BNtTkv.*3e!&t#<rA{11Pw;#Moc:bspgrp

á ñ

The following shows a very simple db2_storage that puts everything in onetablespace:


á ñ


Figure 58 on page 158, is a sample db2_storage file that we used. It puts 34 ofthe larger indexes and 60 tables of Company 000 in their own tablespaces.

Attention

The entries must be in ascending sequence with the *.* last. If you use thedb2_install6.2 script, it puts the new entries at the end. Therefore, you mustmanually insert them into the correct sequence.


à ðttaad050:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad050:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD050ttaad100:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad100:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD100ttaad106:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad106:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD106ttaad110:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad110:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD110ttaad200:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad200:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD200ttaad201:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad201:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD201ttaad300:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad300:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD300ttaad305:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad305:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD305ttaad306:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad306:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD306ttaad311:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad311:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD311ttaad320:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttaad320:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TAAD320ttadv002:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv002:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV002ttadv010:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv010:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV010ttadv112:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv112:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV112ttadv130:000:I::01::STOGROUP BERPGRP PRIQTY 5000 SECQTY 960 BUFFERPOOL BP3ttadv130:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV130ttadv140:000:I::01::STOGROUP BERPGRP PRIQTY 3500 SECQTY 960 BUFFERPOOL BP3ttadv140:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV140ttadv200:000:I::01::STOGROUP BERPGRP PRIQTY 4000 SECQTY 960 BUFFERPOOL BP3ttadv200:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV200ttadv301:000:I::01::STOGROUP BERPGRP PRIQTY 14400 SECQTY 960 BUFFERPOOL BP3ttadv301:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV301ttadv330:000:I::01::STOGROUP BERPGRP PRIQTY 2000 SECQTY 960 BUFFERPOOL BP3ttadv330:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV330ttadv334:000:I::01::STOGROUP BERPGRP PRIQTY 10000 SECQTY 960 BUFFERPOOL BP3ttadv334:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV334ttadv420:000:I::01::STOGROUP BERPGRP PRIQTY 1000 SECQTY 960 BUFFERPOOL BP3ttadv420:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV420ttadv422:000:I::01::STOGROUP BERPGRP PRIQTY 2500 SECQTY 960 BUFFERPOOL BP3ttadv422:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV422ttadv450:000:I::01::STOGROUP BERPGRP PRIQTY 6000 SECQTY 960 BUFFERPOOL BP3ttadv450:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV450ttadv460:000:I::01::STOGROUP BERPGRP PRIQTY 200 SECQTY 960 BUFFERPOOL BP3ttadv460:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV460ttadv461:000:I::01::STOGROUP BERPGRP PRIQTY 300 SECQTY 960 BUFFERPOOL BP3ttadv461:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV461ttadv990:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv990:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV990

á ñ

Figure 58 (Part 1 of 2). Sample db2_storage File


à ðttadv991:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv991:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV991ttadv996:000:I::01::STOGROUP BERPGRP PRIQTY 100000 SECQTY 9600 BUFFERPOOL BP3ttadv996:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV996ttadv997:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv997:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV997ttadv998:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv998:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV998ttadv999:000:I::01::STOGROUP BERPGRP PRIQTY 5000 SECQTY 960 BUFFERPOOL BP3ttadv999:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TADV999tttxt001:000:I::01::STOGROUP BERPGRP PRIQTY 6000 SECQTY 960 BUFFERPOOL BP3tttxt001:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TTXT001tttxt002:000:I::01::STOGROUP BERPGRP PRIQTY 2200 SECQTY 960 BUFFERPOOL BP3tttxt002:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TTXT002tttxt010:000:I::01::STOGROUP BERPGRP PRIQTY 3000 SECQTY 960 BUFFERPOOL BP3tttxt010:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000A.TTXT010*:000:I::01::STOGROUP BERPGRP PRIQTY 12 SECQTY 960 BUFFERPOOL BP3ttadv:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTADVttaad:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTAADttchm:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTCHMttcmt:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTCMTttcon:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTCONttdba:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTDBAttdbt:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTDBTttddi:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTDDIttdll:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTDLLttdsk:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTDSKttgfd:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTGFDttgui:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTGUIttiex:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTIEXttpcm:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTPCMttptp:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTPTPttsem:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTSEMttsql:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTSQLttstp:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTSTPtttbs:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTTBStttld:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTTLDtttls:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTTLStttss:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTTSStttst:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTTSTttttd:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTTTDtttxt:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTTXTttuid:000:T:group:01:5: OPT_ROWS 5 T_SPACE BERP000B.TTUID*:*:I::01::STOGROUP BERPGRP PRIQTY 64 SECQTY 960 BUFFERPOOL BP3*:*:T:group:01:5: ARR_SIZE 1 OPT_ROWS 5 T_SPACE BERP9999.TS999

á ñ

Figure 58 (Part 2 of 2). Sample db2_storage File



Appendix I. Set the Environment Variables for Baan

One of the most important parts of the installation process is to have all thenecessary environment variables set correctly for each step in the installationprocess. This appendix shows the environment variables we set at each point:

Adding the Connection Manager and Process Manager paths

Preparing for the running the installation script

Setting up the profile for the user bsp

Restarting the install6.2 script

I.1.1 Setting Environment Va riables for OS/390 Connection Scaling KitImportant

Since this change to the variables will be seen system-wide you need tocheck with the OS/390 systems programmer to ensure you will not affect anyother users.

During the installation of the OS/390 UNIX System Services Connection ScalingKit, the following strings should have been added in /etc/profile.

Variable String to be includedPATH /usr/lpp/bpa/binPATH /usr/lpp/cmx/binLIBPATH /usr/lpp/bpa/libLIBPATH /usr/lpp/cmx/lib - new for the April/99 porting setNLSPATH /usr/lpp/bpa/nls/msg/C/%NNLSPATH /usr/lpp/cmx/nls/msg/C/%N

Note: IN the NLSPATH entriese, C and N must be capitalized. To verify thesetting, issue the following commands:echo $PATHecho $LIBPATHecho $NLSPATH

If they are not set, you need to modify the profile in the /etc directory.

If the following line is commented out in the /etc/profile, you need to uncommentthe line.

export _C89_INCDIRS="/usr/include"Then add /usr/lpp/cmx/include to this line:

export _C89_INCDIRS="/usr/include /usr/lpp/cmx/include"

Note: The separator between the include directories is a space character.

If the following lines are commented out in the /etc/profile, you need touncomment them.

eval "export $(typeset -x | grep "¬_C89_" | awk '{sub("_C89_","_CC_");printf "%s ",$0}')"eval "export $(typeset -x | grep "¬_C89_" | awk '{sub("_C89_","_CXX_");printf "%s ",$0}')"


If the following lines are commented out in the /etc/profile, you need touncomment them. Again, this change is seen system-wide so you need to checkwith the installation system programmer before modifying the profile.

export _C89_LIBDIRS="/lib /usr/lib"Then add /usr/lpp/cmx/lib to this line:

export _C89_LIBDIRS="/lib /usr/lib /usr/lpp/cmx/lib"

Note: The separaters between the library directories (/lib, /usr/lib, and/usr/lpp/cmx/lib) are space characters.

I.1.2 Set Environment Variables-Installation of Baan ApplicationsTo use the install6.2 script, the following variables must be set:

1. Add the HEAP parameter to _CEE_RUNOPTS.To set this up:_CEE_RUNOPTS=$_CEE_RUNOPTS' HEAP(24M)',STACK(131072,131072,ANYWHERE,KEEP),ALL31(ON),TERMTHDACT(USDUMP)'export _CEE_RUNOPTSecho $_CEE_RUNOPTS

2. TERM=vt100

3. _BPX_SHAREAS=YES

4. _BPX_SPAWN_SCRIPT=YES

5. _DB2_MVS_SYNTAX=1

6. _CMX_THREASDS=0 (new for porting set)

7. LIBPATH=$LIBPATH:/baanerp/bse/bin:/baanerpinstall/install/bse/bin

Then you must issue the following commands:

export TERMexport _BPX_SHAREASexport _BPX_SPAWN_SCRIPTexport _DB2_MVS_SYNTAXexport LIBPATH

Note: The HEAP value of 24M in the _CEE_RUNOPTS was used for ourinstallation without any problems. If the HEAP value is not set correctly, theinstall6.2 script will abort the installation with shared memory problems.

Various problems arose during our execution of the install6.2 script (it could notfind modules) which were corrected by setting the values of $PATH and$LIBPATH with new directory paths. Review the bug notes in the installationmanual and modify the install6.2 script as directed.

Note: The DSNAME for STEPLIB is installation-dependent. In our case we hadto export STEPLIB=DB2V510.SDSNLOAD . This was not the case in other installations.

To verify all variables are set correctly, enter the following command:env


Following is our list of environment variables before running install6.2:

root @ SC55:/>env_CXX_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/libMAIL=/usr/mail/rootHOSTNAME=SC55PATH=/bin:/usr/lpp/tcpip/sbin:/usr/lpp/tcpip/bin:.:/usr/lpp/bpa/bin:/usr/lpp/cmx/bin:/baanerp/bse/bin_CXX_INCDIRS=/usr/include /usr/lpp/cmx/include /usr/lpp/bpa/includeSHELL=/bin/sh

_CC_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/lib_CC_INCDIRS=/usr/include /usr/lpp/cmx/include /usr/lpp/bpa/includePS1=$LOGNAME @ $HOSTNAME:$PWD>

_CEE_RUNOPTS=$_CEE_RUNOPTS' HEAP(24M)',STACK(131072,131072,ANYWHERE,KEEP),ALL31(ON),TERMTHDACT(USDUMP)'_=/bin/env_BPXK_SETIBMOPT_TRANSPORT=TCPIPOE

LOGNAME=rootSTEPLIB=noneLANG=CLIBPATH=/lib:/usr/lib:.:/usr/lpp/bpa/lib:/baanerpinstall/install/bse/bin:/baanerp/bse/bin_C89_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/libTERM=vt100

_BPX_SHAREAS=YES_BPX_SPAWN_SCRIPT=YES_DB2_MVS_SYNTAX=1_C89_INCDIRS=/usr/include /usr/lpp/cmx/include /usr/lpp/bpa/includeHOME=/

TZ=EST5EDTMANPATH=/usr/man/%LNLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lpp/bpa/nls/msg/C/%N:/usr/lpp/cmx/nls/msg/C/%N

I.2 Setting Up the Profile for the bsp User IDAfter Company 000 was loaded, we set up the profile for user bsp by adding tothe install profile the following two variables:

export BSE=/baanerp/bse

export BSE_TMP=$BSE/tmp

After this is done, you can proceed to use the Baan Windows client and then thedemo companies.

The environment variables we set for the bsp user are shown in Figure 59 onpage 164.

Appendix I. Set the Environment Variables for Baan 163

_CXX_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/libMAIL=/usr/mail/bspHOSTNAME=SC55PATH=/bin:/usr/lpp/tcpip/sbin:/usr/lpp/tcpip/bin:.:/usr/lpp/bpa/bin:/usr/lpp/cmx/bin_CXX_INCDIRS=/usr/include /usr/lpp/cmx/includeSHELL=/bin/sh_CC_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/lib_CC_INCDIRS=/usr/include /usr/lpp/cmx/includePS1=$LOGNAME @ $HOSTNAME:$PWD>_=/bin/env_BPXK_SETIBMOPT_TRANSPORT=TCPIPOELOGNAME=bspSTEPLIB=noneLANG=CLIBPATH=/lib:/usr/lib:.:/usr/lpp/bpa/lib_C89_LIBDIRS=/lib /usr/lib /usr/lpp/cmx/lib_C89_INCDIRS=/usr/include /usr/lpp/cmx/includeHOME=/baan/bseTZ=EST5EDTMANPATH=/usr/man/%LNLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lpp/bpa/nls/msg/C/%N:/usr/lpp/cmx/nls/msg/C/%Nexport _CEE_RUNOPTS="HEAP(24M,1M,ANYWHERE,KEEP),STACK(131072,131072,ANYWHERE,KEEP),ALL31(ON),LIBSTACK(8),TERMTHDACT(UADUMP)"export TERM=vt100export DB2_MVS_SYNTAX=1export _BPX_SHAREAS=YESexport _BPX_SPAWN_SCRIPT=YESexport PATH=$PATH:/baanerp/bse/binexport LIBPATH=$LIBPATH:/baanerp/bse/binexport BSE=/baanerp/bseexport BSE_TMP=$BSE/tmp

Figure 59. Environment Variables for bsp User

I.3 Restarting the install6.2 ScriptIf for some reason you must restart the install6.2 script after you have beenlogged off, you will have lost all the settings that the installation script had made.See G.2.2, “Restarting install6.2 from the Beginning” on page 144, for moreinformation.

I.4 Default Profile Before Starting the install6.2 ScriptFigure 60 on page 165 shows the complete default profile in /etc/profile.


à ð# This is a sample profile defining system wide parameters. The# variables set here may be overridden by a user's personal .profile in# their $HOME directory.# This may be tailored to your own enterprise, and should be copied into# /etc/profile. More information on this profile may be found in the# OS/390 OpenEdition Planning Guide and the OpenEdition User's Guide.## To enable and disable lines in this profile you may remove or add '#'# to uncomment or comment the desired lines.# Improve the shell's performance for users from ISPF or with# STEPLIB data sets allocated. This performance improvement is not# applicable to non-interactive shells, for example those started with# the BPXBATCH and OSHELL utilities.if -z "$STEPLIB" “ && tty -s;then

echo " - - - - - - - - - - - - - - - - - - - - - - - - - - - "echo " - Improve performance by preventing the propagation - "echo " - of TSO/E or ISPF STEPLIBs - "echo " - - - - - - - - - - - - - - - - - - - - - - - - - - - "export STEPLIB=noneexec sh -L

fi# Set the time zone as appropriate.TZ=EST5EDT# This sets a default command path, including your current working# directory (CWD).

PATH=/bin:/usr/lpp/tcpip/sbin:/usr/lpp/tcpip/bin:.:/usr/lpp/bpa/bin:/usr/lpp/cmx/bin

# Specifies the directory to search for a DLL (Dynamic Link Library)# filename. If not set, the working directory is searched.LIBPATH=/lib:/usr/lib:.:/usr/lpp/bpa/lib# Sets the path for NLS files (message catalogs).

NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lpp/bpa/nls/msg/C/%N:/usr/lpp/cmx/nls/msg/C/%N

#C/%Nts the path for man pages (help files).MANPATH=/usr/man/%L# Sets the language# For Japanese: LANG=Ja_JPLANG=C# Sets the name of the system mail file and enables mail notification.MAIL=/usr/mail/$LOGNAME# Export the values so the system will have access to them.export TZ PATH NLSPATH MAIL LANG LIBPATH MANPATH# Set the default file creation mask - reference umask in the OpenEdition# Commands Referenceumask 022# Set the LOGNAME variable readonly so it is not accidentally modified.readonly LOGNAME

á ñ

Figure 60 (Part 1 of 3). Profile in /etc/profile


à ð# ======================================# Start of c89/cc/c++ customization section# ======================================## The following environment variables are used to provide information# to the c89/cc/c++ utilities, such as (parts of) dataset names which# are dynamically allocated.## If installation of the compiler and/or runtime library products use# different values, then the appropriate "export" lines should be# set to the correct value (and uncommented). Note that since a# VOL=SER= paramater is not supported by c89/cc/c++, all named data# sets used by c89/cc/c++ must be cataloged.# It may be necessary to override the default esoteric unit for# (unnamed) work data sets, if the c89/cc/c++ default (SYSDA) is not# defined for the installed system. A NULL ("") value may be specified# in order to allow c89/cc/c++ to use an installation defined default.## Only the c89 command variables are explicitly shown. The cc and c++# variables are set by the command line beginning with "eval" at the# end of this c89/cc/c++ section.## Note that this is not an exhaustive list of the environment# variables that affect the behavior of c89/cc/c++. It is however all# those that will normally might require customization by the system# programmer. For ease of migration, it is recommended that of these# only the variables necessary for correct operation of cc/c89/c++ be# set. Consult the "Environment Variables" section of the c89/cc/c++# command in the OS/390 OpenEdition Command Reference for complete# information about these environment variables.## High-Level Qualifier "prefixes" for data sets used by c89/cc/c++:# ======================================## C/C++ Compiler:# ----------------------------------------# export _C89_CLIB_PREFIX="CBC"## Prelinker and runtime library:# ----------------------------------------# export _C89_PLIB_PREFIX="CEE"## OS/390 system data sets:# ----------------------------------------# export _C89_SLIB_PREFIX="SYS1"

á ñ



à ð## Compile and link-edit search paths:# ===================================## Compiler include file directories:# ----------------------------------export _C89_INCDIRS="/usr/include /usr/lpp/cmx/include /usr/lpp/bpa/include"## Link-edit archive library directories:# --------------------------------------

export _C89_LIBDIRS="/lib /usr/lib /usr/lpp/cmx/lib"## Esoteric unit for data sets:# ============================## Unit for (unnamed) work data sets:# ----------------------------------------# export _C89_WORK_UNIT="SYSDA"## Commands to propogate c89 environment variables for cc and c++:# ======================================#eval "export $(typeset -x | grep "¬_C89_" | awk '{sub("_C89_","_CC_");printf "%s ",$0}')"eval "export $(typeset -x | grep "¬_C89_" | awk '{sub("_C89_","_CXX_");printf "%s ",$0}')"

## ======================================# End of c89/cc/c++ customization section# ======================================# added PS1 to know where you are, who you are, and what your# current directory isexport PS1='$LOGNAME @ $HOSTNAME:$PWD>'

á ñ




Appendix J. Using UNIX System Services for UNIX-Trained BaanSpecialist

This appendix describes the TSO and USS interfaces into a OS/390 system, froma UNIX specialist's point of view.

J.1 OverviewOS/390 is the descendant of the MVS operating system. In addition to beingMVS, it is a UNIX-branded system. That is to say, the XOPEN organization,which holds UNIX branding authority, has certified that OS/390 has implementedthe APIs and functions that define a UNIX system.

That being said, many UNIX-literate people, when they first encounter OS/390UNIX Systems Services, do not feel OS/390 is truly a UNIX system, and the usersthat do acknowledge it is a UNIX operating system often refer to themselves asbeing on the “MVS” side or on the “UNIX” side.

Both situations have a lot to do with which interfaces the user uses to work withthe system, and what commands and functions are available to them at aparticular interface.

J.2 Interface OptionsThere are two fundamental ways a user accesses the system, via logging ontoTSO or the UNIX shell (an implementation of the Korn shell). Both provide thekey function of allowing/implementing communication between the user and thesystem.

However, the implementation and presentation of this communication is done indifferent manners. For example, to view the contents of a disk, TSO (usingISPF/PDF) uses a menu system, whereas under USS, “command line”commands are used. Since the “look and feel” of the TSO menu system istraditional for MVS, one often states they are on the MVS side of OS/390.

This is compounded by the fact that, to interface with the HFS (the OS/390implementation of a UNIX journal file system) under TSO, a particular commandis entered to get to the set of menus to display HFS-related information. Again,some folks say they have just jumped to the OE (the archaic term for USS) orUNIX side. However, in reality, they have just simply triggered another set ofmenus. Of course, if a user did an rlogin to the UNIX shell, he thinks of himselfas being on the UNIX side.


Figure 61. Accessing S/390

Figure 61 portrays the entry into OS/390 by either TSO (the MVS side), orRLOGIN, (the UNIX side). What really happens is that a program is invoked(after all, TSO is just a program) which accesses system functions on behalf ofthe user. From an operating system point of view, all functions (MVS and USS)are available to all programs.

As shown in Figure 61, if a person is logged onto TSO, access to function 1 and3 are available, (that is to say, one has the “key” to that function (API)).Similarly, if one has RLOGINed into the UNIX shell, functions 1 and 2 areavailable.

Using a very simple scenario, if function 1 is printing, function 2 is the VI editorand function 3 is the ISPF editor, both “sides” can print, but TSO has not enabledthe VI editor and the UNIX shell has not enabled ISPF. You use the vi editorwhile logged into the UNIX shell, and you use ISPF when logged into TSO. Ofcourse, if you were logged onto TSO and wanted to use the vi editor, you wouldhave to RLOGIN to the UNIX shell, which to most people is going “ to the otherside.”

The point is that one could write a terminal monitor program that would have all3 keys and thus print, VI edit or ISPF under one login. You would never need tochange logins, and your sense of the system is that of a single entity.

Thus the inability to access “both sides” us not a result of the limitations ofOS/390 (including UNIX System Services) but of the constructs of the program,perhaps limitations of the complier used and of course, the level of securityallowed. For example, one may not be able to access “MVS” data sets (files)from the “UNIX side” because of a lack of authorization, not because it is


technically impossible. Some compliers may not provide verbs for all functions,hence they may be a cause of this either/or view. Presuming a complier thathas all the appropriate verbs is chosen then, whether a program uses aparticular function, is up to the designer of that program. This is the case forboth TSO and the UNIX shell; not all functions are accessible by either program,hence the need to bounce between these two terminal monitors.

While this explanation will not eliminate your need to do multiple logins, it ishoped that understanding why this is necessary, will eliminate the misconceptionthat there are “sides” to OS/390

One last point: OS/390 is often dismissed as not being a “true” UNIX systembecause it is missing a favorite shell script or command. In reality, noteveryone's favorite command or shell script is necessarily there, but it could be,it just was not ported.

Appendix J. Using UNIX System Services for UNIX-Trained Baan Specialist 171


Appendix K. DDF Customization

After establishing connectivity using TCP/IP, you can install and customize DDFon OS/390.

K.1 Installing and Customizing DRDAThe following four steps customize DDF:

1. BSDS changes.

Most DDF parameters are stored in the DSNZPARM module. We used theDSNTIJUZ member in DSN510.NEW.SDSNSAMP to update the DSNZPARMmodule. One of the steps in the DSNTIJUZ JCL is to update the BSDSinformation, using the change log inventory utility. To execute the changelog inventory, you must stop the DB2 subsystem. Figure 62 shows theDSNTIJUZ job step to update the BSDS.

à ð//DSNTLOG EXEC PGM=DSNJU003,COND=(4,LT)//STEPLIB DD DISP=SHR,DSN=DSN510.SDSNLOAD//SYSUT1 DD DISP=OLD,DSN=DSN510.BSDS01//SYSUT2 DD DISP=OLD,DSN=DSN510.BSDS02//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD *

DDF LOCATION=DB2D,LUNAME=SCPDBA1,NOPASSWD,RESPORT=33000,PORT=446

//*á ñFigure 62. DDF Parameters

2. Define DB2 DDF to VTAM in SYS1.LOCAL.VTAMLST.

To enable TCP/IP support, you must also define an APPL in VTAM. Theplace to do this is in SYS1.LOCAL.VTAMLST. The LUNAME keyword must bedefined in BSDS and the LU must be active, prior to starting DDFcommunications. Figure 63 on page 174 shows the APPL definitions inSYS1.LOCAL.VTAMLST.


à ð** **** DB2 V5 LU DEFINITION FOR DRDA **** **

VBUILD TYPE=APPL*SCPDBA1 APPL ACBNAME=SCPDBA1, X

APPC=YES, XATNLOSS=ALL, XAUTH=(ACQ), XAUTOSES=10, XDMINWNL=25, XDMINWNR=25, XDSESLIM=50, XEAS=509, XENCR=NONE, XMODETAB=ISTINCLM, XPARSESS=YES, XSECACPT=ALREADYV, XSONSCIP=NO, XSYNCLVL=SYNCPT, XVERIFY=NONE, XVPACING=2, XVTAMFRR=NO

á ñFigure 63. APPL Entries in SYS1.LOCAL.VTAMLST

3. Define DB2 DDF to RACF.

DDF uses UNIX System Services to perform TCP/IP services. Some of theUNIX System Services functions that DDF executes require an authorizeduser with certain privileges. To execute the authorized functions, the user IDassociated with the DDF started task must be defined for UNIX SystemServices as a superuser. To define a user ID as a superuser, you must setthe User Identifier (UID) parameter of the RACF user profile to zero. To setthe UID parameter for your DDF user, you can issue one of the followingRACF commands:

ADDUSER userid OMVS(UID(0)) .....

ALTUSER userid OMVS(UID(0)) .....

The ADDUSER RACF command adds a new user profile and should be usedwhen creating a new user for DDF. The ALTUSER RACF command changesthe RACF profile for the existing DDF user. To check whether your DDF userID is already correctly defined to RACF, issue the following RACF command:

LISTUSER userid OMVS

If you specify both a user ID and a group in the RACF Started ProcedureTable (ICHRIN03) for the DDF address space, the group must also have avalid UNIX System Services group ID (GID) setting. To define RACF groupsto be UNIX System Services groups, use the RACF panels or the followingcommand:

ADDGROUP groupid OMVS(GID(n)) .....

where groupid is the name of the RACF group associated with the DDFaddress space, and can be any valid unique identifier.

4. Define DB2 DDF to TCP/IP.


Part of the DDF customization process is to select port numbers whenupdating the BSDS. The DDF statement of the change log inventory hasbeen enhanced with PORT and RESPORT values. If PORT and RESPORT aredefined, DDF accepts TCP/IP connections from any client that provides validsecurity information. DB2 also allows outbound connections to other DRDAservers using TCP/IP.

To define the port numbers in TCP/IP, you must update the TCP/IP PROFILEdata set. In our case, we used SYS1.TCPPARMS member PROFILE. Youmust register the TCP/IP port numbers you have specified during DB2installation or when using the change log inventory utility. We defined twoport numbers required by our DB2 subsystem, DB2D. In the PORT statementyou must use TCP as the protocol, and the name of the UNIX SystemServices started procedure (in our case, OMVS). Because DB2 uses UNIXSystem Services to connect to TCP/IP, the DB2 ports are reserved for theUNIX System Services address space, and not for the DDF address space,xxxxDIST. The PORT definitions are shown in Figure 64.

à ðSYS1.TCPPARMS(PROFILE)

PORT23 TCP INTCLIEN ;446 TCP OMVS ; DRDA SQL PORT for DB2D33000 TCP OMVS ; DRDA SQKL resync port for DB2D33001 TCP OMVS ; DRDA SQKL resync port for DB2D

á ñFigure 64. PORT Definitions for DRDA

For more detailed information on customizing DDF, refer to WOW! DRDASupports TCP/IP: DB2 Server for OS/390 and DB2, SG24-2212.

Note: For the latest information on DRDA, refer to DB2 for OS/390 V5Installation Guide, GC26-8970.

Appendix K. DDF Customization 175


Appendix L. Special Notices

This publication is intended to help those who will be installing BaanERPApplications on OS/390 with DB2. The information in this publication is notintended as the specification of any programming interfaces that are provided byBaanERP, or DB2. See the PUBLICATIONS section of the IBM ProgrammingAnnouncement for DB2 V5.1 for more information about what publications areconsidered to be product documentation.

References in this publication to IBM products, programs or services do notimply that IBM intends to make these available in all countries in which IBMoperates. Any reference to an IBM product, program, or service is not intendedto state or imply that only IBM's product, program, or service may be used. Anyfunctionally equivalent program that does not infringe any of IBM's intellectualproperty rights may be used instead of the IBM product, program or service.

Information in this book was developed in conjunction with use of the equipmentspecified, and is limited in application to those specific hardware and softwareproducts and levels.

IBM may have patents or pending patent applications covering subject matter inthis document. The furnishing of this document does not give you any license tothese patents. You can send license inquiries, in writing, to the IBM Director ofLicensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact IBM Corporation, Dept.600A, Mail Drop 1329, Somers, NY 10589 USA.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The information contained in this document has not been submitted to anyformal IBM test and is distributed AS IS. The information about non-IBM("vendor") products in this manual has been supplied by the vendor and IBMassumes no responsibility for its accuracy or completeness. The use of thisinformation or the implementation of any of these techniques is a customerresponsibility and depends on the customer's ability to evaluate and integratethem into the customer's operational environment. While each item may havebeen reviewed by IBM for accuracy in a specific situation, there is no guaranteethat the same or similar results will be obtained elsewhere. Customersattempting to adapt these techniques to their own environments do so at theirown risk.

Any pointers in this publication to external Web sites are provided forconvenience only and do not in any manner serve as an endorsement of theseWeb sites.

This document contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples containthe names of individuals, companies, brands, and products. All of these names


are fictitious and any similarity to the names and addresses used by an actualbusiness enterprise is entirely coincidental.

Reference to PTF numbers that have not been released through the normaldistribution process does not imply general availability. The purpose ofincluding these reference numbers is to alert IBM customers to specificinformation relative to the implementation of the PTF when it becomes availableto each customer according to the normal IBM PTF distribution process.

The following terms are trademarks of the International Business MachinesCorporation in the United States and/or other countries:

The following terms are trademarks of other companies:

C-bus is a trademark of Corollary, Inc.

Java and HotJava are trademarks of Sun Microsystems, Incorporated.

Microsoft, Windows, Windows NT, and the Windows 95 logo are trademarksor registered trademarks of Microsoft Corporation.

PC Direct is a trademark of Ziff Communications Company and is usedby IBM Corporation under license.

Pentium, MMX, ProShare, LANDesk, and ActionMedia are trademarks orregistered trademarks of Intel Corporation in the U.S. and othercountries.

UNIX is a registered trademark in the United States and othercountries licensed exclusively through X/Open Company Limited.

SET and the SET logo are trademarks owned by SET Secure ElectronicTransaction LLC.

Other company, product, and service names may be trademarks orservice marks of others.

DataJoiner DB2DFSMS DFSMSdssIBM OpenEditionOS/390 RAMACS/390 SNAP/SHOTSystem/390 S/390 Parallel Enterprise Server


Appendix M. R elated Publications

The publications listed in this section are considered particularly suitable for amore detailed discussion of the topics covered in this redbook.

M.1 International Technical Support Organization PublicationsFor information on ordering these ITSO publications see “How to Get ITSORedbooks” on page 181.

Installing Baan IV Applications on OS/390, SG24-5334

Implementing DFSMSdss SnapShot and Virtual Concurrent Copy, SG24-5268

Implementing SnapShot, SG24-2241

IBM RAMAC Virtual Array, SG24-4951

DB2 for OS/390 and Data Compression, SG24-5261

WOW! DRDA Supports TCP/IP: DB2 Server for OS/390 and DB2, SG24-2212

Enterprise Web Serving with the Lotus Domino Go Webserver for OS/390,SG24-2074

M.2 Redbooks on CD-ROMsRedbooks are also available on the following CD-ROMs. Click the CD-ROMsbutton at http://www.redbooks.ibm.com/ for information about all the CD-ROMsoffered, updates and formats.

CD-ROM Title Collection KitNumber

System/390 Redbooks Collection SK2T-2177Networking and Systems Management Redbooks Collection SK2T-6022Transaction Processing and Data Management Redbooks Collection SK2T-8038Lotus Redbooks Collection SK2T-8039Tivoli Redbooks Collection SK2T-8044AS/400 Redbooks Collection SK2T-2849Netfinity Hardware and Software Redbooks Collection SK2T-8046RS/6000 Redbooks Collection (BkMgr Format) SK2T-8040RS/6000 Redbooks Collection (PDF Format) SK2T-8043Application Development Redbooks Collection SK2T-8037

M.3 Other IBM PublicationsThese publications are also relevant as further information sources:

UNIX System Services Connection Scaling Reference, SA22-7305

SnapShot for MVS/ESA Using SnapShot Version 1 Release 2, SC26-7173

SnapShot for MVS/ESA Installating and Using Version 1 Release 2, SC26-7174

SnapShot Installation Notes for MVS Version 1 Release 2, SC26-7175

UNIX System Services Planning, SC28-1890

IBM HTTP Server for OS/390: Planning, Install and Use, SC31-8690

SnapShot for MVS/ESA Implementing SnapShot for Version 1 Release 2,SC26-7176


DB2 for OS/390 V5 Administration Guide, Volumes I and II, SC26-8957

DB2 for OS/390 V5 Application Programming and SQL Guide, SC26-8958

DB2 for OS/390 V5 Call Level Interface Guide and Reference, SC26-8959

DB2 for OS/390 V5 Command Reference, SC26-8960

DB2 for OS/390 V5 Data Sharing: Planning and Administration, SC26-8961

DB2 for OS/390 V5 Installation Guide, GC26-8970

DB2 for OS/390 V5 SQL Reference, SC26-8966

DB2 for OS/390 V5 Utility Guide and Reference, SC26-8967

OS/390 eNetwork Communications Server: IP Configuration, SC31-8513

M.4 Baan PublicationsThese publications, available from Baan, are also relevant as further informationsources. For information on how to contact Baan go to: http://www.baan.com

BaanERP - Installation Guide for BaanERP on OS/390 UNIX System Services

BaanERP - DB2 Installation Guide for BaanERP

BaanERP Internet Server Installation and Configuration Guide

M.5 Other PublicationsThere are several reference books on UNIX commands, available in bookstores:

Learning the vi Editor, Linda Lamb, O'Reilly & Associates, February 1986.

UNIX for Dummies, John R. Levine and Margaret Levine Young, IDG BooksWorldwide, 1997.


How to Get ITSO Redbooks

This section explains how both customers and IBM employees can find out about ITSO redbooks, redpieces, andCD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.

Redbooks Web Site http://www.redbooks.ibm.com/

Search for, view, download, or order hardcopy/CD-ROMs redbooks from the redbooks Web site. Also readredpieces and download additional materials (code samples or diskette/CD-ROM images) from this redbookssite.

Redpieces are redbooks in progress; not all redbooks become redpieces and sometimes just a few chapterswill be published this way. The intent is to get the information out much quicker than the formal publishingprocess allows.

E-mail Orders

Send orders by e-mail including information from the redbook fax order form to:

Telephone Orders

Fax Orders

This information was current at the time of publication, but is continually subject to change. The latest informationmay be found at the redbooks Web site.

IBM Intranet for Employees

IBM employees may register for information on workshops, residencies, and redbooks by accessing the IBMIntranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materialsrepository for workshops, presentations, papers, and Web pages developed and written by the ITSO technicalprofessionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ forredbook, residency, and workshop announcements.

In United States: e-mail address: [email protected] North America: Contact information is in the "How to Order" section at this site:

http://www.elink.ibmlink.ibm.com/pbl/pbl/

United States (toll free) 1-800-879-2755Canada (toll free) 1-800-IBM-4YOUOutside North America Country coordinator phone number is in the "How to Order" section at this site:


United States (toll free) 1-800-445-9269Canada 1-403-267-4455Outside North America Fax phone number is in the "How to Order" section at this site:



IBM Redbook Fax O rder Form

Please send me the following:

Title Order Number Quantity

First name Last name

Company

Address

City Postal code Country

Telephone number Telefax number VAT number

Z Invoice to customer number

Z Credit card number

Credit card expiration date Card issued to Signature

We accept American Express, Diners, Eurocard, M aster Card, and Visa. Payment by credit card notavailable in all countries. Signature mandatory for credit card payment.


List of Abbreviations

4GL fourth generation language

AFP advanced function printing

API application program interface

ASCII American National StandardCode for InformationInterchange

ATM asynchronous transfer mode

BA Baan ASCII Client

bc Conversion

BI Baan Internet Client

BW Baan Windows Client

BX Baan Xwindows Client

BPX buffer prefix

BSE Baan Software Environment

CAF call attach facility

cf Configuration

ci Central Invoicing

CLI call level interface (X-Open,SQL interface)

CM Connection Manager

cp Constraint Planning (BaanApplication Package)

DB database

DB2 DATABASE 2 (an IBMrelational databasemanagement system)

DEM Dynamic Enterprise Modeling

dc Development Control

ec Electronic Commerce

ed Enterprise Model Data

EBCDIC extended binary codeddecimal interchange code

ERP enterprise resource planning

ESCON enterprise systemsconnection (architecture, IBMSystem/390)

FDDI fiber distributed datainterface (100 Mbit/s fiberoptic LAN)

FTP File Transfer Program

HFS hierarchical file system

IBM International BusinessMachines Corporation

ISPF Interactive SystemProductivity Facility

ITSO International TechnicalSupport Organization

LPA link pack area

OS/390 Operating System (for the)IBM System/390

PC personal computer

PCL printer control language

PM Process Manager

ps Process (Baan Application)

qm Quality Management

RAMAC Raid Architecture withMulti-Level Adaptive Cache

RDBMS relational databasemanagement system

RRS resource recovery services

RS/6000 IBM RISC System 6000

RVA RAMAC Virtual Array

S/390 IBM System/390

SNA Systems NetworkArchitecture

SQL Structured Query Language

tc Common (Baan ApplicationCommon Package)

td Distribution (BaanApplication Package)

tf Finance (Baan ApplicationPackage)

tg Orgware (Baan ApplicationPackage)

ti Manufacturing (BaanApplication Package)

tp Project (Baan ApplicationPackage)

tr Transportation (BaanApplication Package)

ts Services (Baan ApplicationPackage)

tt Tools (Baan Application Tools

tu Utilities (Baan ApplicationUtilities)

TCP/IP Transmission ControlProtocol/Internet Protocol

USS UNIX System Services (ofOS/390)


UNIX An operating systemdeveloped at BellLaboratories (trademark ofUNIX System Laboratories,licensed exclusively byX/Open Company, Ltd.)

vrc Version Release customerextension

wh Warehousing

WINNT Microsoft Windows NT


Index

Special Characters/etc/alias 17

Aabbreviations 183acronyms 183alias 17application layer 4application server 4architecture 1ASCII 3

BBaan applications that run on S/390 6Baan HTTP server 71Baan internet client 71Baan Software Alliances 8Baan Software Environment (BSE) 5BaanERP installation steps 15BAANERP.APPL.BSE 38BI Client 3, 65bibliography 179BSDS changes 173BShell 4buffer pool recommendations 102BW Client 3, 65

CCall Attach Facility (CAF) 10common vi commands 115configuration directives

Exec 86, 89keyfile 85normalmode 85Pass 86, 89Protect 85Protection IMW_Admin 85SSLClientAuth 85sslmode 85sslport 85User ID 85

Configuration fileshttpd.conf 84, 85setting up 83Single server 84

configure client connection 67connection manager 9, 33Content placement 86content setup recommendations 87

Ddata compression 132database drivers 3database layer 3database server 3, 11db2_groups 54, 128db2_storage 54, 128, 157db2_users 54, 128DDF 173DDF and RACF 174DFSMSdss SnapShot 136directives

See configuration directivesDynamic Enterprise Modeling (DEM) 8

EEBCDIC 3env variables 43, 143ERP 1Exec 86, 89executing DB2 script 49, 120expert mode 3

Ffunctional device table 131functional track directory 132functional track table 132

HHFS 37HFS file systems 3HTTP server 71

Iindex usage 105install6.2 script 43, 44, 163internet client 3, 71ipcs 142

Lload the BaanERP software from CD-ROM 18log files 146log to track progress 147

Mmanagement disciplines 106multibshell 48multibyte 48


OOS/390 11

PPass 86, 89porting set 4presentation client 2presentation layer 2problems

ASCII mode 140globlvar not found 140logging on as bsp 141problems encountered 139setting permissions 140short on storage 139STEPLIB not found 141VSAM extents 139VTOC space 139

Process Manager (PM) 10, 93Protect 85PUBLIC 85, 88

RRDBMS 3reference manuals 15reorganization and runstats recommendations 104Resource Recovery Services (RRS) 9restarting scripts 141restarting the install6.2 script 144, 164RVA 131

Sscripts

db2_install6.2 49, 120install6.2 43restarting 141

semaphores 143shared memory problem 42, 142, 162shared memory problems 141Single server

httpd.conf 84setting up 84

SnapShot 135starting the Baan application 62SYS1.LOCAL.VTAMLST 173

Uunload the Baan software from CD-ROM 40User ID 85using Baan log files 146

Vvirtual concurrent copy 136

vrc 46

WWeb client 3Windows client 3

YYear 2000 1


ITSO Redbook Evaluation

Installing BaanERP Applications on OS/390SG24-5440-00

Your feedback is very important to help us maintain the quality of ITSO redbooks. Please com plete thisquestionnaire and return it using one of the following methods:

Use the online evaluation form found at http://www.redbooks.ibm.com/Fax this form to: USA International Access Code + 1 914 432 8264Send your comments in an Internet note to [email protected]

Which of the following best describes you?__Customer __B usiness P artner __Solution Developer __IBM employee__None of the above

Please rate your overall satisfaction with this book using the scale:(1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor)

Overall Satisfaction ____________

Please answer the following questions:

Was this redbook published in time for your needs? Yes____ No____

If no, please explain:_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

What other redbooks would you like to see published?_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

Comments/Suggestions: (THANK YOU FOR YOUR FEEDBACK!)_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

_____________________________________________________________________________________________________

_____________________________________________________________________________________________________


SG24-5440-00Printed in the U.S.A.

InstallingB

aa

nE

RP

Applications

onO

S/3

90

SG

24-5440-00

Date post:	23-Nov-2014
Category:	Documents
Upload:	sergio-castaneda-vega
View:	90 times
Download:	3 times

sg245440

Documents