MFGPRO SysAdminReferenceGuide ProgressDatabase WindowsNTServer IG v09

System Administration Reference Guide
PROGRESS DATABASE ON WINDOWS NT SERVER
78-0460A MFG/PRO Version 9.0 Printed in the U.S.A. March 1999
This document contains proprietary information that is protected by copyright. No part of this document may be photocopied, reproduced, or translated without the prior written consent of QAD Inc. The information contained in this document is subject to change without notice. QAD Inc. provides this material as is and makes no warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. QAD Inc. shall not be liable for errors contained herein or for incidental or consequential damages (including lost profits) in connection with the furnishing, performance, or use of this material whether based on warranty, contract, or other legal theory. Some states do not allow the exclusion of implied warranties or the limitation or exclusion of liability for incidental or consequential damages, so the above limitations and exclusion may not be applicable. PROGRESS is a registered trademark of Progress Software Corporation. Windows is a trademark of Microsoft Corporation. MFG/PRO is a registered trademark of QAD Inc. Copyright 1999 by QAD Inc. 78-0460A QAD Inc. 6450 Via Real Carpinteria, California 93013 Phone (805) 684-6614 Fax (805) 684-1890
Contents
PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 MFG/PRO Manager Functions Information . . . . . . . . . . . . . . . . . . . . . . 2 Configuration and Sizing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
CHAPTER 1
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
System Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 PROGRESS Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 PROGRESS Version Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 PROGRESS Executables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 PROGRESS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 PROGRESS Database Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 MFG/PRO Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 MFG/PRO Version Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 MFG/PRO Compiled and Source Code . . . . . . . . . . . . . . . . . . . . . . . . 10 Empty Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Main MFG/PRO Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Help, User Interface (GUI), and Configurator Databases . . . . . . . . . . . 12 Database Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Multiple and Custom Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
IV
MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT
CHAPTER 2
DATABASE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Large Scale Data Movements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Types of Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 PROGRESS Backup Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Validating the Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Offsite Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Delete/Archive and Database Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Dump and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Reasons for Dumping and Loading Data . . . . . . . . . . . . . . . . . . . . . . . . 21 Normal Dump/Load Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 About PROGRESS Bulk Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Dumping Through MFG/PRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Dumping Through PROGRESS Data Administration Tool . . . . . . . . . . . . . . . . 24 Limited Disk Space Dump Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Preparing an Empty Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Bulk Load: Creating the Bulk Loader Description File . . . . . . . . . . . . . . . . . . . 25 Bulk Loading the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Bulk Load: Rebuilding the Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Loading Through Progress Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Post Dump/Load Sequence Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
CHAPTER 3
PERFORMANCE TUNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Start-Up Parameters and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Parameter Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Parameters Affecting Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Relocation of the Before-Image File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 PROGRESS Performance Aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Before-Image Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 After-Image Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Asynchronous Page Writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Performance Aid Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 PROMON PROGRESS Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CONTENTS
User Control (PROMON Item 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locking and Waiting Statistics (PROMON Item 2) . . . . . . . . . . . . . . . Block Access (PROMON Item 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Record Locking Table (PROMON Item 4) . . . . . . . . . . . . . . . . . . . . . . Activity (PROMON Item 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared Resources (PROMON Item 6) . . . . . . . . . . . . . . . . . . . . . . . . . Database Status (PROMON Item 7) . . . . . . . . . . . . . . . . . . . . . . . . . . . Shut Down Database (PROMON Item 8) . . . . . . . . . . . . . . . . . . . . . . .
37 37 38 39 39 39 40 40
CHAPTER 4
MULTI-VOLUME DATABASE . . . . . . . . . . . . . . . . . . . . . . . . . 43
44 45 45 46 47 47 48 49 49 51 52 53 53
Multi-Volume Database Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi-Volume Database Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . Multi-Volume Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi-Volume Set-Up Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the Allocation Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the Structure Description File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting the Extent Size to Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . Example Structure File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before-Image Extents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Void Multi-Volume Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Schema and Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi-Volume Database Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Extents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHAPTER 5
SPLIT SCHEMA DATABASE . . . . . . . . . . . . . . . . . . . . . . . . . . 55

56 56 56 57 57 58 59 59 60
Reasons for Splitting Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhance Database Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . Increase Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Common Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining How to Split the Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Split for ECommerce . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical Disk Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VI
Creating a Split Schema Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Administering the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
CHAPTER 6
GENERAL ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . 63
Maintaining MFG/PRO Scripts and Database Sets . . . . . . . . . . . . . . . . . . . . . . 64 Setting Up Training Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Setting Up the Training Database Server . . . . . . . . . . . . . . . . . . . . . . . . 65 Setting Up the Training Database Client . . . . . . . . . . . . . . . . . . . . . . . . 66 Compiling Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Using MFG/UTIL to Compile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Non-English Language Compile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Compiling Character Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Compiling Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Batch Processes with PROGRESS Prowin32 Batch Client . . . . . . . . . . . . . . . . 74 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Editing the Batch Program and Input Control File . . . . . . . . . . . . . . . . 75 Copying and Editing the progress.ini File . . . . . . . . . . . . . . . . . . . . . . . 76 Modifying the batch.pf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Creating Unique Batch Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Defining Batch IDs for MRP and Hotbatch . . . . . . . . . . . . . . . . . . . . . . 79 Submitting Batch Jobs in MFG/PRO . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Scheduling Batch Jobs in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . 82
CHAPTER 7
USING PROGRESS RESULTS WITH MFG/PRO . . . . . . . . 87
About RESULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 RESULTS Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Setting Up RESULTS to Start from a MFG/PRO Menu . . . . . . . . . . . . . . . . . . 88
CHAPTER 8
MFG/UTIL REFERENCE INFORMATION . . . . . . . . . . . . . . . . . 91
Database Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Create Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Load Data File into Existing Database . . . . . . . . . . . . . . . . . . . . . . . . . 93 Update Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Split Database Schema File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
CONTENTS
VII
Connect to a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Create Dump/Load Procs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Load Translated Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Program Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Compile Procedure Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 DataServer Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Generate Oracle Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Change Oracle Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 99 Scripts Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Generate Server Startup and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . 99 Generate User Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Configure Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 DLC and PROPATH Variables (Set MFG/PRO Paths) . . . . . . . . . . . 100 Company Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Any Database Set (Database Set Configuration) . . . . . . . . . . . . . . . . 101 Database Set Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Client View of Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Server View of Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 103 Sections in mfgutil.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Summary of Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 ClientSetup Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Compile Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 OracleValues Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 ServerSetup Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 DBSET Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 General Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 HasRun Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Paths Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Site Section (mfgutil.ini) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
CHAPTER 9
MODIFIED BROWSE PROGRAM NAMES . . . . . . . . . . . . . . . . 111
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
VIII
Preface
Using This Guide Organization 3 3 2
Document Conventions
Using This Guide

Use this guide for background and reference information on MFG/PRO system administration, especially database management and related tasks.
Audience
These instructions are for the MFG/PRO system administrator who manages the MFG/PRO database and is familiar with Microsoft Windows NT and networking.
MFG/PRO Manager Functions Information

Although it is involved with system administration, this guide does not include documentation for the MFG/PRO Manager Functions (menu 36). For that information, refer to User Guide Volume 11: Manager Functions. However, because this guide discusses various dump/load methods, it also covers the MFG/PRO dump/load programs found on the Manager Functions menu.
Configuration and Sizing Information

Refer to your MFG/PRO installation guide for the following types of information:
Configuration overview Minimum system requirements Hardware sizing recommendations
PREFACE
Organization
This guide is organized as follows.
1 2 3 4 5 6 Introduction Database Management Performance Tuning Multi-Volume Database Split Schema Database General Administration Explains the basic concepts of PROGRESS and the MFG/PRO system. Explains the common database management tasks, along with some step-by-step instructions. Offers advice on how to boost system performance. Explains how to set up a multi-volume database, which is recommended for best performance. Explains the reasons and procedure for splitting the MFG/PRO production database. Covers various tasks that support the MFG/PRO application, particularly how to schedule and process batch jobs. Explains how to set up the custom reporting tool RESULTS. Provides MFG/UTIL reference information. Lists the old and current names for MFG/PRO browse programs.
7 8 9
Using PROGRESS RESULTS with MFG/PRO MFG/UTIL Reference Information Modified Browse Program Names
Document Conventions
Command prompts use the conventions listed in the following table.
If you see: monospaced text It means: A command or file name.
italicized Italicized monospaced text indicates a variable name for a monospaced text value you enter as part of an operating system command. For example, YourCDROMDir.
indented command line A long command that you enter as one line (although it appears in the text as two lines).
CHAPTER 1
Introduction
This chapter presents general information you need to know for successful system administration. The topics in this chapter are: System Administration Tasks PROGRESS Basics MFG/PRO Basics 9 6 6
System Administration Tasks

The following table summarizes the major tasks involved with system administration, along with how often they typically occur.
Table 1.1
System Administration Tasks
Task System Backup Batch processing setup Client setup Performance monitoring Delete/Archive Dump/Load
Frequency Daily During implementation and as needed During implementation and as needed Weekly or as needed After financial close (yearly or as needed) After delete/archive (to alleviate disk fragmentation)
PROGRESS Basics
PROGRESS is both a relation database management system (RDBMS) and a fourth-generation (4GL) programming language. It is installed by default in the DLC directory. (DLC stands for Data Language Corporation, the previous name for PROGRESS, Inc.)
PROGRESS Version Number

To find the PROGRESS version number, use a text editor to open a file called version, located in the main PROGRESS installation directory. A single line appears in this file, listing the version number and a revision letter. For example:
PROGRESS version 8.3A as of Mon Mar 8 1999
Another important file is PROGRESS.cfg, located in the PROGRESS installation directory. This file is a text file containing the serial numbers and other details about the installed PROGRESS products. To open it, double-click the file name in Explorer or File Manager.
Note To determine which PROGRESS version is required for a given
MFG/PRO release, refer to the MFG/PRO Installation Guide .
INTRODUCTION
PROGRESS Executables
As you maintain start-up scripts and other parts of the system, keep in mind the various PROGRESS executables that perform tasks such as starting application sessions and database servers. These executables are located in sub-directories of the PROGRESS installation directory and typically have an underscore ( _ ) in the first character of the name. For example, the PROGRESS executable that starts multiuser database servers is called _mprosrv.exe, located in the bin sub-directory. MFG/PRO runs PROGRESS executables as needed; you normally do not need to run them directly. To start _mprosrv.exe, MFG/PRO uses the following command, where PROGRESSInstallDir is your PROGRESS installation directory and DbName is the name of an existing database.
ProgressInstallDir\bin\_mprosrv DbName
PROGRESS Parameters
A PROGRESS parameter is a setting that instructs the RDBMS how to handle hardware factors such as memory and I/O resources. Parameters pass to the RDBMS when a PROGRESS executable starts or when connecting to a database. You specify parameters after the PROGRESS executable command statement. For example, you can type the -B parameter (database buffer memory) in the following command line to allocate 8MB of memory as a database buffer:
ProgressInstallDir\bin\_mprosrv DbName -B 2000
When you use parameters, keep in mind the following tips.

Each parameter works with a particular PROGRESS executable. For
example, the -B parameter does not work with the executable _prowin32.exe.
Each parameter takes affect at a specific point, such as program
startup or database connection.

You cannot specify parameters when running a PROGRESS script,
such as procopy.
For a complete listing of PROGRESS startup parameters, refer to the PROGRESS system administration manuals. Also refer to for information on the main parameters: -B, -g, -L, -s, -H, -N, -S, and mmax.
PROGRESS Database Architecture

In its simplest form, a PROGRESS database is a single physical file on the computer. The file extension is .db. There are also related files, such as the before-image file (extension .bi). Like any RDBMS system, PROGRESS databases have a structure, called a schema, that defines how data is stored and accessed. The schema consists of:
Tables (also called files): logical groupings of data, such as customer
information.
Fields (known as columns in other systems): the data elements within
tables, such as address.

Indexes: a map of the fields within tables. Before-Image (.bi) File
PROGRESS employs a mandatory recovery technique called rollbackward recovery. Any time a transaction is called against a database, a snapshot of the data is recorded prior to alteration. The snapshot is held in the .bi file. If a transaction is aborted, PROGRESS resets the database record to the .bi file snapshot. The .bi file incurs heavy use during I/O operations. Relocating this file to a different drive from the database file (.db, also an I/O intensive file) allows for less contention. Refer to Chapter 3, Performance Tuning, for more information on relocating the .bi file.
INTRODUCTION
Related Database Files
Some of the main files involved with building and running a PROGRESS database are:
Empty Database (empty.db): Included with every PROGRESS
release, this database has some version-specific header information, but is otherwise empty. By making a copy of empty.db and loading a database definition file, you create a working PROGRESS database.
Database Definition (extension .df): An ASCII text file with
descriptions of the tables and fields used to create the schema. Before MFG/PRO is shipped, database definitions are loaded into a copy of empty.db in order to create a given MFG/PRO database.
Data files (extension .d): ASCII text files containing database records
to be dumped from or loaded into a database.

Bulkload definition file (extension .fd): Like the database definition
file, this file lists all tables and fields in the schema. However, its purpose is to define how to insert records from data files into the database during a bulkload process.
Lock file (extension .lk): A file created when you start a PROGRESS
session against a database. If your database was shut down abnormally (such as a system failure), you may need to delete the lock file in order to connect to the database.
Log file (extension .lg): A file containing a database event history,
such as startup, shutdown, and errors.
MFG/PRO Basics
MFG/PRO is a global supply chain management software package offered by QAD Inc. MFG/PRO programs are written in the PROGRESS 4GL programming language and the MFG/PRO databases run on the PROGRESS RDBMS. MFG/PRO is dependent on the installation of PROGRESS to function.
10
MFG/PRO Version Number

Because MFG/PRO is supported on certain versions of PROGRESS, you must know how to identify the software version. To find the MFG/PRO version number, use a text editor to open a file called version.mfg, located in the main MFG/PRO installation directory. Like PROGRESS, the version number includes a revision letter. In some cases, it also includes an enhancement code at the end. For example:
"Release 9.0 02 as of Mar 8 1999"
MFG/PRO Compiled and Source Code

The MFG/PRO programs are delivered as compiled code (also called object code). The file extension is .r and it is sometimes called r-code. The programs are grouped into modules, so your installation contains only those programs needed for the modules you purchased. In addition to compiled code, the system includes source code (file extension .p). Source code is the high-level 4GL programming syntax. You may need to use source code to recompile MFG/PRO or make programming customizations.
Note You can also run directly from source code, in which case
PROGRESS creates the compiled code in system memory at run time. However, running from source code is significantly slower. There are two versions of source programs:
Encrypted Code: This source code is passed through an encoder to
prevent custom programming; however, you can use it to recompile MFG/PRO. It is provided for all modules purchased.
Non-Encrypted Code: If you plan to customize MFG/PRO programs,
you can purchase the non-encrypted source code. When purchased, the source code is provided for all modules.
INTRODUCTION
11
Empty Databases
The sources for all MFG/PRO databases are called empty databases because they only contain the schema and not any data. You can use these empty databases in case one of the standard databases is damaged and you need to replace it.
Table 1.2
mfgempty hlpempty guiempty cfempty
Source database for mfg, mfgdemo, and mfgtrain. Source database for mfghelp. Source database for gui. Source database for cfg.
Empty Databases
The data that are loaded into standard databases are kept in subdirectories under the MFG/PRO installation directory. The directory names correspond to the name of the standard database. For example, directory mfg contains data (.d files) for the mfg.db database.
Fig. 1.1
Empty Database: mfgempty +
Data Directory: /qad/mfg/*.d
Built Database: mfg
Empty and Built Databases
hlpempty
/qad/mfghelp/*.d
mfghelp
guiempty
/qad/gui/*.d
gui
cfempty
/qad/cfg/*.d
cfg
12
Main MFG/PRO Databases

For Windows NT, the MFG/PRO databases come pre-built from the CD-ROM. A pre-built database means the schema is loaded, as well as any default data. The bulk of MFG/PRO tables appear in one database. The source version of this database is called mfgempty. Copies of mfgempty are made to support different types of data: demonstration, training, and your production data.
Table 1.3
Main MFG/PRO Databases
Database Name mfg YourProductionDB mfgdemo mfgtrain
Description Source database used to make the production database. Contains only default menus, messages, and system codes. A copy of mfg to be used as your production database. The production database name is determined during installation. A copy of mfgempty with demonstration MFG/PRO data loaded. A copy of mfgempty with training MFG/PRO data loaded.
Help, User Interface (GUI), and Configurator Databases

In addition to the main database, MFG/PRO also uses the databases listed in Table 1.4.
Table 1.4
Help, User Interface, and Configurator Databases
Database Name mfghelp gui cfg
Description Contains all data for the system help feature. It is therefore mostly read-only information. Contains data used to create the MFG/PRO user interface, including the interface for MFG/PRO object programs. Contains the data from the Component Configurator Maintenance programs. This module enables you to customize MFG/PRO object programs.
INTRODUCTION
13
Fig. 1.2
Database:
Related Application Item:
The cfg, gui, and mfghelp Databases
cfg: (object components)

)LHOG+HOS(PSOR\HH
gui: (browses,
user interface)
%URZVH
mfghelp
(online help)
Database Sequences
Sequences are a data structure in PROGRESS Version 7 and higher. Sequences generate a sequential stream of values for records that must be uniquely identified, such as the Inventory Transaction History file (tr_hist). Starting with MFG/PRO Version 8.5, several control file numbering fields were replaced by sequences, which are faster, require less error checking, and reduce the amount of time MFG/PRO spends validating uniqueness. In general, sequences are self-maintained. However, you may need to update sequence values when you perform a delete/archive. The sequencing functionality in MFG/PRO helps you maintain sequence values both manually and through the CIM interface.
Multiple and Custom Databases

From the clients perspective, the existence of multiple databases and custom (side) databases merely requires that the client connects to additional databases at client start-up time, using the script or start-up icon and configuration files. The creation of the multiple databases and custom (side) databases occurs on the database server. This overview explains why a system administrator might be required to connect to these additional databases.
14
Multiple Database
To operate multiple inventory sites while consolidating financial information, you must set up a multiple database environment. Use the Multiple Database module to set up and operate the multiple database environment. Multiple Database functions retrieve and update data in other databases. Database connections can be either automatic, manual, or scripted. Database connection information is accessed for all multiple database functions: central sales orders, distributed purchase orders, and DRP. When these functions are called, MFG/PRO accesses the database connected to the site specified on the transaction. As long as the network connection is operating, the connection is invisible to the user.
Custom (Side) Databases
If you customize MFG/PRO and the standard user fields provided for each file are not adequate, you can create custom (side) databases. These databases should be created and used to hold the new table and field definitions required for the custom programs. The standard MFG/PRO schema should never be modified to add new tables and fields, since this could complicate subsequent updates. Instead, a copy of the PROGRESS empty database should be modified to create the tables and fields required by the custom programs. When a client runs the custom code, the client must connect to the custom (side) database to ensure that the custom code will execute.
CHAPTER 2
Database Management
Topics in this chapter: Large Scale Data Movements Database Backup 16 19 16
Delete/Archive and Database Fragmentation Dump and Load 20 23
Dumping Through MFG/PRO
Dumping Through PROGRESS Data Administration Tool Limited Disk Space Dump Procedure Preparing an Empty Database 25 25 24
24
Bulk Load: Creating the Bulk Loader Description File Bulk Loading the Data 26 27 27
Bulk Load: Rebuilding the Indexes
Loading Through Progress Data Dictionary Post Dump/Load Sequence Initialization 28
16
Large Scale Data Movements

There are three types of large scale data movements, described in Table 2.1.
Table 2.1
Types of Data Movement
Method Backup Delete/Archive Dump/Load
When Regularly When data is no longer needed After delete and archive
What Makes exact copy of database or of changes. Frees space by removing records. Copies data from the database into ASCII files. No data is deleted.
Database Backup
Regular database backups are crucial to ensure against data loss. You should back up as often as practical, at least every day. Whatever your schedule, consistency is important. Database backup involves transferring the database file (single-volume) or files (multi-volume) to media such as tape. Also, you must back up all related database files, including:
Before-image (.bi) file because it is time-stamped to the database After-image (.ai) files, if after-imaging is enabled
However, if you truncate the before-image file, you do not need to back it up. When you truncate the .bi file, PROGRESS updates the database with pertinent before-image information and then empties the .bi file to its minimum length. PROGRESS recreates the .bi file at the next server startup. Truncating is recommended to save time and space during the backup, but it requires you to shut down the database, which may not be feasible if you must operate 24 hours per day, 7 days per week. The command for truncating the database is:
ProgressDir\bin\_proutil.exe YourDbName -C truncate bi
DATABASE MANAGEMENT
17
Types of Backup
There are various types of backup.
Off-line backup means the database is shut down. This method
ensures database integrity.

On-line backup means the database is still running during the backup.
It is about 99.9 percent accurate. This method is only available with the PROGRESS backup utility.
Full backup includes all records and can be time consuming. Incremental backup includes only the differences since the date of the
last full or incremental backup. For this reason, it is faster.

Backup Schemes
When you choose your type of backup, you must also plan for how you will restore the data. In the simplest case, you perform a daily full backup and, in the event of a failure, restore the whole database. If you choose incremental backups, you must choose whether to back up the changes for each day or to back up the cumulative changes since the last full backup. Table 2.2 presents two examples.
Table 2.2
Day Friday Monday Tuesday Restore
Daily Incremental Full backup Backup changes since Friday Backup changes since Monday Friday, Monday, Tuesday backups
Cumulative Incremental Full backup Backup changes since Friday Backup changes since Friday Friday and Tuesday backups
Backup Scheme Examples
PROGRESS Backup Utilities

You can perform the backup with various third-party utilities or with the PROGRESS utilities. If you run your database 24-hours, 7 days a week, then you must do your backups online. In this case, the only option is to use the PROGRESS backup utility probkup.
18
With probkup and its counterpart, prorest (for restoration), you can:
Back up online (servers up) or offline (servers down) Perform incremental backups
It is also advantageous to use probkup if you are running after-imaging. After-imaging is an optional type of recovery known as roll forward recovery. It requires a separate disk drive. It can be used without probkup, but some RFUTIL commands will need to be started.
Validating the Backup

Validate the ability to back up and restore your database at least once a month, if not once a week. Use the production database if space is available. Otherwise, use a test database or the default mfg database.
Reliability Test Procedure
You can use this procedure to validate your ability to back up and restore your database.
1 2 3 4 5
Shut down the database with the standard MFG/PRO shut-down icon. Truncate the .bi file using the PROGRESS proutil utility. Back up the database. Restore the database to a different directory. Run MFG/PRO against the restored database, or you can compare the two databases.
Note Use PROGRESS cmpdb for single-volume databases.
DATABASE MANAGEMENT
19
Offsite Storage
It is a good idea to regularly rotate your backups to an offsite storage area. This provides you with greater security. There are numerous service providers who will assist you with this. Check your yellow pages under Data Storage. An alternative is to rent a bank safety deposit box and store backups there. Offsite storage is less a matter of theft prevention than security should your site burn down or be subject to a natural disaster. Offsite storage should be, if possible, at least 10 miles away.
Delete/Archive and Database Fragmentation

When you perform a delete/archive, the actual database records are deleted, fragmenting your logical database file. Whenever a deletion occurs within the database, the storage area occupied by that data record becomes available to the database to reuse. (The space is not available to the operating system; the .db file size does not decrease.) Quite possibly the deleted record was stored in a larger storage area that held many similar type records. For example, you have deleted a group of work orders. The storage area they resided in becomes available for use. The RDBMS uses this area within the database file the next time someone enters any type of record(s) that can physically fit in the vacated storage area. For the purpose of this example, a sales quote is the next record entered, and it is placed in the newly vacated area. Due to the way an indexed database retrieves records, both the work order and sales quote retrieval process will now be more complex. Both these files are fragmented, and so are their indexes. For the system to retrieve a particular record within these files (work order and sales quote), it starts searching the disk at some point and reads a part of the entire file. It then needs to reposition the physical disk read/write head, and recommence the read process.
20
Fig. 2.1
Database Fragmentation
When you delete/archive records... Record 1 Record 2 Record 3 Record 4 Record 5 Record 6
...Database searches are no longer contiguous
Obviously the more fragmented any file becomes the more inefficient the search becomes. For this reason it is best to perform all sub-function delete/archive processes during one particular period, and then defragment your database by performing a dump and load.
Dump and Load

A database dump replicates all data records from selected database tables into ASCII files. The dump does not delete any data from the database. The ASCII files are named after their source tables and have a .d extension. For example, if you dump the menu detail table (mnd_det), the resulting file would be: mnd_det.d. The logic for a MFG/PRO dump, or load, is supplied using the programs contained in the dmpprocs (dump procedures) or ldprocs (load procedures) sub-directories. These sub-directories are found off the main MFG/PRO install directory. If any errors occur during the dump/load, PROGRESS creates an error file (.e extension) in the dump/load directory.
Note Since the MFG/PRO application could produce several related file
records during any single transaction, loading of single files into populated databases could result in loss of integrity between files and needed related files. For this reason, a database should be dumped as a whole, and loaded as a whole.
DATABASE MANAGEMENT
21
Reasons for Dumping and Loading Data

The main reasons for a full dump/load of a database data are:
Resolve database fragmentation, especially after a delete/archive Convert from one MFG/PRO version to another
A dump/load reduces the database fragmentation because records that were once scattered within the database are reloaded from the ASCII files in sequential order, creating one continuous logical file order in the database.
Normal Dump/Load Procedure

These are the general steps to follow for a dump/load. Before you perform these steps on a production database, you should perform a test dump/load on a non-production database in order to estimate the amount of time your machine will take. To help estimate the time, you can run Database File Size Report (36.16.2) and chose a representative 5-10% of the files (in terms of size). Dump and load these files and time the process.
1
Check the primary indexes using Database File Size Report (36.16.2). The primary indexes must be all right. If not, you need to rebuild the indexes using the proutil idxbuild command. Create a dump directory on the server. Check for adequate disk space. You will need about 75% of the database size in free space. If you do not have enough space, it is possible to perform a series of partial dumps. Refer to Limited Disk Space Dump Procedure on page 24. Make sure all users are logged off. Choose one of the following dump methods:
From MFG/PRO, use Database File Dump/Load w/Batch
2 3
4 5
(36.16.4).
From PROGRESS, use the Data Administration Dump/Load. 6
When the dump is complete, shut down the database you dumped and back it up.
22
7 8
Prepare a copy of the empty MFG/PRO database (mfgempty) to load the dumped data. Load the dumped data using one of the following methods:
Run the Bulk Loader option of the PROGRESS PROUTIL utility
(recommended)
Use the PROGRESS Data Administration Dump/Load
Note Although you can use Database File Dump/Load w/ Batch to load
data, it is not recommended for loading an entire database because of the performance impact on the network.
9
Once the data is loaded, initialize sequences with Database Sequence Initialization (36.16.17).
10 Back up the database.
Note In general, you should perform all dump and loads on your server
machine. However, on DEC Alpha Windows NT machines, you cannot complete dump and loads on the server because ProVISION, which is required, is not available for DEC Alpha on Windows NT. In this case, you must install ProVISION on a client machine and build the .fd file using the clients Database Dictionary Admin Menu. You then transfer this file to the server using ftp, or another applicable file transfer method. You should always use ftp in binary mode.
About PROGRESS Bulk Loader

The PROGRESS Bulk Loader utility is the fastest load method because it is the only method that does not maintain the indexes at load time. It discards them. This requires a separate index rebuild, but it is still faster than other methods, which reproduce indexes during the load. The overall tasks for performing a bulk load are:
Create a bulk loader description file from the PROGRESS Data
Administration tool. This file maps all of the tables and fields so that PROGRESS can place the data from the .d files.
Run the proutil utility, bulkload option. Run the proutil utility, index rebuild option.
DATABASE MANAGEMENT
23
Dumping Through MFG/PRO

Prerequisites:
Your dump directory must be created on the server. If you have not done so, you must build the dump/load procedures for
the Windows client PC. (Dump/load procedures are delivered prebuilt with the server media, but they are only used for dumping through a non-interactive batch process.) To create the dump/load procedures, run utmkdl from any MFG/PRO menu. This step takes several minutes.
1
In an MFG/PRO session against your training database, start Batch ID Maintenance (36.14.1). Create two batch IDs called Dump and Load. Select Database File Dump/Load w/Batch (36.16.4), and enter the following
Field Database Name Dumpfile Directory Dump/Load File Name To Allow Errors, Log file Output Batch ID Enter Defaults to physical name of primary database. YourDumpDir Dump Leave blank to include all fields. Leave blank to include all fields. These fields are display only. Leave this field blank. Dump
3 4
Choose Go when ready. Process the dump batch job with one of the following methods.
Run Batch Request Processor (36.14.13). Type Dump in the
Batch IDs field. This method works for a small number of tables, but is not recommended when dumping the whole database.
If you are dumping an entire database, run a non-interactive batch
process on the database server. Refer to Batch Processes with PROGRESS Prowin32 Batch Client on page 74 for instructions on setting up non-interactive batch processes.
24
Dumping Through PROGRESS Data Administration Tool

As an alternative to dumping through MFG/PRO, you can use the tools from PROGRESS.
1 2
If you have not already done so, create a dump directory. From an MFG/PRO session, start the PROGRESS Data Administration tool using the following substeps.
a b
From any menu, select the User Menu and choose PROGRESS Editor. In the PROGRESS Procedure Editor, select the Tools menu and choose Data Administration.
3 4 5
When the Data Administration tool starts, select the Admin menu, choose Dump Data and Definitions, and choose Table Contents. In the Select Tables window, select all or some of the tables and choose OK. In the next dialog, specify your dump directory in the Output File field. In the Code Page field, accept the default. Choose OK to continue. Once the process is complete, you can find the .d file in the dump directory and view it using any text editor.
Limited Disk Space Dump Procedure

If you do not have 75% of the database size in free disk space, you could perform partial dumps (for example, files a-g) into limited disk space. Then run these files to tape, delete them from the disk, and restart the dump/load, selecting files h-x, and so on. Of course, you absolutely must have at least as much space as your single largest logical database file, typically tr_hist (plus an additional 10% as a safety factor). You can determine these file sizes by running the Database File Size Report (36.16.2).
DATABASE MANAGEMENT
25
Preparing an Empty Database

Always load your dumped data into a copy of the mfgempty database, located in your MFG/PRO installation directory. Use the PROGRESS prodb command and give the new database a meaningful name. Type the following DOS prompt command from the MFG/PRO installation directory.
ProgressDir\prodb NewProdDb.db mfgempty
If you plan to set up a multi-volume database (which is recommended), you can do so before loading the data. Refer to Chapter 4, Multi-Volume Database, on page 43 for further instructions.
Bulk Load: Creating the Bulk Loader Description File

If you are using the bulk load method, you must create a bulk loader description file of the database.
1
From an MFG/PRO session, start the PROGRESS Data Administration tool using the following steps.
a b
From any menu, select the User Menu and choose PROGRESS Editor. In the PROGRESS Procedure Editor, select the Tools menu and choose Data Administration.
2 3 4
When Data Administration starts, select the Admin menu and choose Create Bulk Loader Description File. In the Select Tables window, select all or some of the tables and choose OK. In the next dialog, specify your dump directory in the Output File field. In the Code Page field, accept the default. Choose OK to continue. Choose OK when informed of completion.
26
6 7
You can find the .fd file in the dump directory. You can also open it in a text editor to view the results. Exit Data Administration.
Bulk Loading the Data

Bulk loading data is the recommended method because it is the fastest. Prerequisite: Complete the instructions Preparing an Empty Database on page 25 and Bulk Load: Creating the Bulk Loader Description File on page 25.
1
Verify no server is running against the database using one of the following methods.
Look in the database directory for the database lock file (.lk). Use the Windows NT Task Manager to look for the
_mprosrv.exe process. If a server is running, shut it down by choosing the Shut Down icon.
2 3 4
Open a DOS window. Change to your dump directory. From the dump directory, type the PROUTIL Bulk Loader command.
YourPROGRESSDir\bin\_proutil YourDBDir\NewProdDb.db -C bulkload *.fd
The system proceeds to deactivate all the indexes, then load the .d files, as directed by the .fd file.
DATABASE MANAGEMENT
27
Bulk Load: Rebuilding the Indexes

Upon completion of a Bulk Loader process, you must run an index rebuild. This task is required because the Bulk Loader does not construct indexes at load time. Since a relational database is useless without indexes, they must be rebuilt.
1
To run the index rebuild, enter the following:

YourPROGRESSDir\bin\_proutil YourDBDir\NewProdDb.db -C idxbuild -TM 30 -TB 30
The TM parameter controls the sort speed, and the TB parameter controls blocking sizes.
2
At the following prompt, enter A (all) or S (some).

Select one of the following All - Rebuild all of the indexes Some - Rebuild only some of the indexes
If rebuilding only some indexes, enter the appropriate table and index names one at a time. When you have entered the last table and index, enter: ! If the data is correct, answer Yes at the confirmation prompt. Answer Yes at the system prompt Do you have enough disk space for index sorting? The index sort requires about 75% of the total size of the database.
4 5
Loading Through Progress Data Dictionary

As an option, you can perform this type of load instead of a bulk load. Prerequisite: Complete the instructions Preparing an Empty Database on page 25.
1 2
Start a Progress Procedure Editor session, and connect to your empty target database. Open the Data Administration tool from the Tools menu.
28
3 4 5
In the Data Administration tool, select the Admin menu, choose Load Data and Definitions, and choose Table Contents. In the Select Tables window, select all or some of the tables and choose OK. In the next dialog, specify your dump directory in the Output File field. In the Code Page field, accept the default. Choose OK to continue.
Post Dump/Load Sequence Initialization

After a dump and load, you must initialize the database sequences. Sequences are mechanisms used to obtain system-generated sequential numbers. Start an MFG/PRO session, and choose Database Sequence Initialization (36.16.17) or type utsequp.p at any menu.
CHAPTER 3
Performance Tuning
This chapter summarizes some of steps you can take to tune the database performance. For further details, refer to the PROGRESS System Administration Guide, Managing PROGRESS Performance. Topics in this chapter: Start-Up Parameters and Performance Parameters Affecting Performance Relocation of the Before-Image File PROGRESS Performance Aids PROMON PROGRESS Monitor 34 36 31 33 30
30
Start-Up Parameters and Performance

There are several PROGRESS parameters available to make the system perform better and be more stable. You specify the parameters as part of the command statement that starts a certain PROGRESS task. For example, the following command starts a database server with the database buffer parameter (-B), which allots a specified amount of memory to the database.
ProgressDir\bin\_mprosrv.exe \Path\YourProd.db -B 8000
Typically, you specify parameters within a .bat file script. Parameters can also be specified in a separate parameter file (.pf). You cannot specify parameters at the time you invoke the script unless the script was set up with variables. For example, in the following .bat file script, there is a variable (%1) that acts as a placeholder for the database name.
set DLC = \usr\dlc set PROMSGS = %DLC%\promsgs set PROTERMCAP = %DLC%\protermcap %DLC%\bin\_mprosrv.exe %1
You use this script by entering the script name (for example, startdb), followed by the database name.
startdb mfgtrain.db
However, if you type the script name, followed by the -B parameter, it would have no effect because the script startup has no provisions to accept the B parameter input. You have to edit the command line of the script to read:
%DLC%\bin\_mprosrv.exe %1 -B 8000
Parameter Applicability
Keep in mind that parameters apply to specific PROGRESS executables. In the above example, the -B parameter was passed to the _mprosrv.exe (multiuser PROGRESS server) task. The -B parameter does not apply to the user session task, _prowin32.exe. Also, some parameters apply at the execution of a program while others apply at the time you connect to a database.
PERFORMANCE TUNING
31
Parameters Affecting Performance

This section discusses some of the more commonly used PROGRESS startup parameters. For a more comprehensive list and explanation, refer to PROGRESS System Administration Reference.
Table 3.1
Option -1
Effect Single User
Where To Set End User (prowin32)
Notes Identifies the database is connected without using a server in a single-user mode. Not an option for client/server connections. Allocates a specified amount of system memory into which you can read and manipulate database records. It is much faster to manipulate a record in memory rather than through the I/O channel. This is a critical setting for system performance, and is set while using the PROGRESS Monitor (see Block Access (PROMON Item 3) on page 38 for details). Specifies how many records from the database can be locked at any one time cumulatively between all the users. May be useful for CIM load. Specifies how many users can access the database at any given time. The system adds one to this number and reserves it for the PROGRESS Monitor. Typically, at the start of a MFG/PRO session, the user connects to several databases. The lowest -n inhibits the users from connecting.
Performance Parameters
-B
Database Buffers
Server Start (_mprosrv)
-L
Lock Table
-n
# of Users
32
Option -g
Effect BeforeImage File Name
Where To Set Everywhere
Notes Used by _mprosrv if the database is accessed using a server. It is passed to _progres if needed during single-user access, as well as to PROUTIL or other PROGRESS tasks connecting single users. Its purpose is to direct the system to the location of the .bi file if it has been moved anywhere other than the database directory. NOTE: PROGRESS recommends not using this parameter and instead relocating the .bi file through a multivolume structure.
-mmax
Maximum Memory
Client Start (prowin32)
Specifies an allocation of memory for the end user. This memory is where compiled procedures can reside in memory, and scratch-pad work can be done. Specifies the length of the users directory tables; i.e., the number of files a user can have open at any given point. Same as -g, but pertains to the .ai file, which is optional. If you use roll forward recovery, the server, or the users session, needs to know where the .ai file is. This specifies where to find the file. PROGRESS creates temp files, and sort files are created in the directory MFG/PRO was started from. You can redirect these files by using the -T followed by the directory. PROGRESS allocates a certain size to temporary files. When this size is exceeded, system operation halts, and then reallocates a new size. By using -TB, you can specify a larger block size for temporary files so that the system does not have to stop and reallocate as often. This parameter is particularly helpful during an index build.
-D
Directory Entries
-a
After-Image Everywhere File Location
-T
Temp Files
-TB
Temp File Block Size
Client Start (prowin32) IDXBUILD
PERFORMANCE TUNING
33
Option -TM -by
Effect Sort Speed Bypass
Where To Set IDXBUILD Server Shut (_mprshut)
Notes Increases the speed at which the idxbuild sort is performed. When the database is shut down, you are given a four-selection menu. Using -by bypasses this menu for unattended shutdown operations.
Relocation of the Before-Image File

One of the biggest factors contributing to poor system performance is I/O contention. In a multiuser system, you have several users simultaneously reading or writing to the database file. If there is only one physical I/O channel to the database, all users must wait their turn. In addition, with each potential record update operation, PROGRESS writes to the beforeimage (.bi) file. This additional file has an excessive amount of I/O. By default, both the database and before-image files reside on the same physical disk drive (I/O channel), together creating severe I/O contention. For this reason, you can make your system more efficient by relocating the .bi file to a separate I/O channel and disk drive. When you relocate the before-image file, you must specify to the system where it is. You can use one of the following methods.
Set up a multi-volume database with .bi extents specified for a
separate disk drive. This is the recommended method.

If you do not set up a multi-volume database, you can move the .bi
file with standard operating system commands and use the -g parameter in your start-up scripts and other operations. Also, the system needs the -g parameter incorporated into any PROUTIL, DBUTIL, or RFUTIL command, whether called using a script, an icon, or on the command line.
34
PROGRESS Performance Aids

There are several other performance aids available for use. Among these are:
Before-Image Writers After-Image Writers Asynchronous Page Writers Watchdog PROMON
Before-Image Writers
The before-image writer (BIW) queues up the before-image data in a memory cache area and actually performs the write at one time, after an entire block has been accumulated. You can start only one BIW per database. To start the BIW use:
ProgressDir\bin\probiw dbpath\dbname
After-Image Writers
The after-image writer (AIW) is similar to the before-image writer, except it deals with writes to the after-image file, if you enacted the roll-forward recovery feature. To start the AIW, use:
ProgressDir\bin\proaiw dbpath\dbname
Asynchronous Page Writers

Similar to the before-image and after-image writers, an Asynchronous Page Writer (APW) queues up database writes, waiting for an entire page of data to be accumulated prior to performing the write. You can start as many APWs as needed per database; however, we recommend no more than two. Using PROMON (PROGRESS Monitor) you can determine how many writes are being performed by the APW, and determine when starting another may be needed.
PERFORMANCE TUNING
35
To start an APW enter:

ProgressDir\bin\proapw dbpath\dbname
Watchdog
Watchdog is a PROGRESS task that monitors the system for abandoned processes, such as an end-users session still connected to a database whose server has been shut down. This situation can occur when a user fails to log off. Watchdog kills the end-user session after a predetermined length of time. It is advisable to use this task on your production database. To start Watchdog enter:
ProgressDir\bin\prowdog dbpath\dbname
Performance Aid Summary

You should modify your server startup script or batch file to start up one BIW, one APW, WATCHDOG, and one AIW (if using after imaging) at production database startup time. At this point, you should be able to set up an advantageous client/server environment, coupled with efficiently defined startup parameters, to achieve a well-performing database system.
36
PROMON PROGRESS Monitor

PROGRESS offers a monitor utility, PROMON, that can be started against any multiuser database. It can be used to monitor your database setup to determine efficiency or problem areas. PROMON gives you some insight into current users, locked records, system resource settings, and so forth. You start PROMON by typing:
ProgressDir\bin\promon dbpath\dbname
You receive the following menu:

PROGRESS MONITOR Version 8 Database: QAD\mfgpro\mfgtrain
1. 2. 3. 4. 5. 6. 7. 8.
User Control Locking and Waiting Statistics Block Access Record Locking Table Activity Shared Resources Database Status Shut Down Database
T. Transactions Control L. Resolve Limbo Transactions C. Coordinator Information M. Modify Defaults Q. Quit
Selections 1-4 present you with a secondary menu with the following options:
1. 2. 3. 4. Display Match a Match a Match a all entries user number range of user numbers record id (only on 4-Record Locking Table)
Q. Return to Main Menu
PERFORMANCE TUNING
37
The following sections discuss some of the more commonly used features of the monitor. The remainder of the PROMON utility is to be used in distributed database environment only, or to modify the defaults of the PROMON utility itself. For more information, refer to the PROGRESS System Administration Reference manual.
User Control (PROMON Item 1)

This selection shows you all/specific users logged on to the database. You see the user number (as referred to by PROMON), login name, Type (broker, monitor, self-service user, server, etc.), previous and current transactions, process identifier, semaphores, server used, login date and time.
8VHU 1DPH 7\SH URRW %52. VMWUDLQ 6(/) VMWUDLQ 021 :DLW 7UDQV 3,' 6HP 659 /RJLQ 7LPH
Locking and Waiting Statistics (PROMON Item 2)

This selection shows you all/specific users that are holding, or have held (during this database session), any record locks, or are currently waiting for specific records. The statistics are shown individually and cumulatively. This also shows completed transactions and schema changes.
7\SH /RFN :DLW /RFN :DLW /RFN :DLW 8VU 1DPH 727$/ 727$/ URRW URRW VMWUDLQ VMWUDLQ 5HFRUG 7UDQV 6FKHPD
38
Block Access (PROMON Item 3)

This selection shows the number of database requests users have made, along with total requests. It also breaks down the requests into database writes and database reads from the .db, .bi, and .ai files.
7\SH 8VU 1DPH '%5HTVW '%5HDG '%:ULWHV %,5HDGV %,:ULWHV $,5HDGV $,:ULWHV
$&& $&& $&&

727$/ URRW VMWUDLQ

The number of database reads vs the number of database requests is a critical measurement when determining the -B (database buffers) parameter setting. As shown, we requested data from the database 804590 times. Of those requests, we had to go to the database through the relatively slow I/O channel 72152 times. This means that the other 732438 times we were able to retrieve database records directly from relatively fast buffer memory. This equates to a buffer hit percentage of 91% (732438 804590 x 100). This is how you determine the setting for the -B parameter. During peak transaction volume, monitor this selection and selection 5, Activity, which shows buffers hits as a percentage. After monitoring for one to two weeks, do the following.
Shut down the database server Modify the startup script with a higher -B Restart the server Monitor again during peak load
Your buffer hits should increase. Continue this process until at some point the buffer hits percentage drops off. This is due to the system going into swapping. Revert the -B parameter to your previous setting, or split the difference and monitor again. You will zero in on the most optimal buffer hits percentage, ideally 85% or greater. This selection can also aid in determining when to start additional APWs since the writes are shown here. If the APW writes account for 50% or less, start another one.
PERFORMANCE TUNING
39
Record Locking Table (PROMON Item 4)

This selection shows you the exact record ID and the chain number of each record a user currently has locked. It also shows the type of lock the user is holding (exclusive, shared, etc.).
8VU 1DPH VMWUDLQ VMWUDLQ VMWUDLQ &KDLQ 5(& 5(& 5(& 5HFLG /RFN 6+5 6+5 (;&/ )ODJV
Activity (PROMON Item 5)

This selection has a large amount of data and is useful when trying to calculate the -B parameter because it shows the buffer hits as a percentage. Also use this selection to determine when to start APWs, BIWs, and AIWs.
Shared Resources (PROMON Item 6)

This selection shows the setting of the current system parameters. It also shows other information, such as whether a BIW is running, an AIW, Watchdog, how many APWs, how many monitors, etc.
6KDUHG 5HVRXUFHV $IWHULPDJH ILOH QDPH D 1XPEHU RI GDWDEDVH EXIIHUV % 1XPEHU RI EHIRUHLPDJH EXIIHUV ELEXIV 1XPEHU RI DIWHULPDJH EXIIHUV DLEXIV %HIRUH LPDJH ILOH QDPH J &XUUHQW VL]H RI ORFNLQJ WDEOH / 0D[LPXP QXPEHU RI XVHUV Q

40
Database Status (PROMON Item 7)

This selection gives physical characteristics about the database, the version number, whether it is open, whether it is damaged, total number of blocks, last transaction number, character set, last two open date and times, last two times the .bi file was opened, schema time stamp, last backup time, last bi truncation, etc.
Shut Down Database (PROMON Item 8)

This selection gives you the same menu you get if you run the _mprshut task without using the -by (bypass menu) option. Using this, you could shut down the database and disconnect users. This is how you could shutdown an APW, BIW, Watchdog, AIW, or disconnect a certain user.
8VU SLG WLPH RI ORJLQ )UL 'HF 7KX 'HF XVHU LG DSZ VMWUDLQ
The following submenu appears.

1 Disconnect a User 2 Unconditional Shutdown 3 Emergency Shutdown x Exit Enter Choice >
Disconnect a User. This option lets you disconnect a user. Selecting 1 results in a prompt asking for the user to be disconnected. If you wanted to stop the APW, choose User 1, and this would disconnect/stop the user. Unconditional Shutdown. This option is a gracious shutdown. Any pending transactions are rolled backward from the .bi file as the users are disconnected.
PERFORMANCE TUNING
41
Emergency Shutdown. This option kills all user processes. This is not a gracious shutdown, since the pending transactions are not rolled back from the .bi file. At next server startup, this condition is detected, and the transactions cleaned up at that point. Of course, you are vulnerable to any damage that occurs to your .bi file in this interim. Exit. This option exits without disconnecting anything.
42
CHAPTER 4
Multi-Volume Database
This chapter summarizes the PROGRESS multi-volume database feature, which is recommended for better performance. For full details on multi-volume databases, refer to the PROGRESS System Administration Guide. Topics in this chapter: Multi-Volume Database Overview Multi-Volume Components Multi-Volume Set-Up Steps 45 46 47 47 51 44
Determining the Allocation Sizes
Creating the Structure Description File Creating a Void Multi-Volume Database Load Schema and Data 52
Multi-Volume Database Administration
53
44
Multi-Volume Database Overview

By default, PROGRESS databasesincluding the MFG/PRO databasesare single-volume, meaning the database equates to a single physical file on disk. Reading and writing to a single physical file often causes input and output (I/O) contention. To alleviate this problem and others, PROGRESS offers a multi-volume database configuration. With a multi-volume database, one logical database is comprised of many physical files. These physical files have a pre-allocated size and directory location, usually scattered across many physical disks, I/O channels, or both. All these physical files together constitute the database.
Note Some operating systems offer a similar feature, called disk striping,
that packages several physical disks into one logical disk volume. You can use striping in addition to the multi-volume database feature.
Fig. 4.1
Multi-Volume Database Feature
Translates a single logical database to many physical files (extents) Physical files can be distributed across disk volumes and file systems Can be used in addition to operating system striping
Logical Database
Physical Files (extents)
MULTI-VOLUME DATABASE
45
Multi-Volume Database Advantages

In general, a multi-volume database configuration:
Improves performance by avoiding disk channel I/O contention: With
the physical files scattered across your disk drives, simultaneous read and write requests process more efficiently.
Overcomes problems with operating system file size limits: For
example, if your database was 5 gigabyte (GB) in size, but your operating system had a file size limitation of 2GB, you could create a multi-volume database using 25 200MB extents.
Multi-Volume Components
The components of a multi-volume database are:
Structure description file (extension .st): a text file used during the
creation of the multi-volume database. It defines the number, location, and size of each extent.
Database structure extent (extension .db): the main database extent
that defines the location of all other extents. The physical .db file contains no data.
Database extents (extension .dn): the files that contain database
records.
Before-image (BI) extents (extension .bn): the files containing
before-image records.
Note A multi-volume database can also include after-image (AI) extents,
if you implement the after-imaging feature. Since after-imaging is an optional feature, this chapter does not discuss it.
46
Fig. 4.2
Components of a Multi-Volume Database
Database Structure Extent (.db)
Structure Description File (.st)
Database Extent 1 (.d1)
Database Extent 2 (.d2)
...
Before Image Extent 1 (.b1)
...
Multi-Volume Set-Up Steps

The general set-up steps are:
1 2 3
Determine the number and size of extents. Create a structure description file (.st extension) to identify the extents, sizes, and locations. Run the PROSTRCT CREATE utility against the structure description file. This utility creates a void multi-volume database with no schema or data. Load data definitions and, if applicable, data. Typically, you do this by copying an existing database to the multi-volume database structure.
Determine Determinethe thenumber numberand and size sizeof ofthe theextents. extents. Run Runthe theprostrct prostrctutility. utility.Creates Creates a avoid voidmulti-volume multi-volumedatabase. database.
Create Createthe thestructure structure description descriptionfile. file.
Load Loaddatabase databasedefinitions definitionsand and data data(you (youcan cancopy copyan anexisting existing database). database).
47
Determining the Allocation Sizes

To set up the multi-volume structure, you must decide how much space to allocate for the database, including the size and number of extents. There is no exact science for this task, but you can follow these guidelines:
Target a total database size that allows for at least a years growth. If
your database has grown from 1GB to 2GB over the past year, and you foresee the same approximate growth rate, target at least a 3GB multi-volume structure.
For a new installation, start off with a 2GB total database size at a
minimum.
Make no single extent greater than 500MB. The preferred extent size
is 200MB.
Limit your database to 20 fixed extents, unless this exceeds the
500MB size. The maximum is 256 extents.

Pay attention to the operating system limits on the maximum number
of open files or file handles per user. Because each extent is a separate file, they may add to this operating system limitation. Example size allocations: A 2GB database should have 10 extents, 200MB each. A 6GB database should have 20 extents, 300MB each. A 10GB database should have 20 extents, 500MB each. A 20GB database should have 40 extents, 500MB each.
Creating the Structure Description File

Once you have determined the allocation sizes, you must describe this data to the PROGRESS system. This is done by creating a structure description file in a text editor. A line from a structure file looks like:
d /DatabaseDir/DBName.d1 f
blocksize
The components of this line are explained in Table 4.1.
48
Table 4.1
Structure Description File Components
Component d
Explanation Indicates a data type extent (b would indicate a .bi extent). Indicates a fixed extent, which means the extent has a permanent, pre-allocated size. Otherwise, the extent is considered a variable length and continually grows in size. Size of the fixed extent. The size is measured in 1024 byte blocks and must be a multiple of 32. For example, if you specify 128 as the block size (divisible by 32), then 128 x 1024 = 131072 bytes.
/DatabaseDir/DBName.d1 The path and name of the database extent. f
blocksize
Converting the Extent Size to Blocks

Use the following to determine the block size for each extent in the structure description file.
Table 4.2
Extent Block Size 1 2 3 4 5
Step Start with the extent size Divide by 1024 (bytes in each block) Divide by 32 Round up if necessary
Example 200MB = 200,000,000 bytes 200,000,000 1024 = 195312.5 195312.5 32 = 6103.515625 6104
Multiply by 32 and use as the block size 6104 x 32 = 195328
The example block size195,328yields an extent size of 200,015,872 (195328 x 1024). This is as close to the 200MB target as you can get.
49
Example Structure File

Assuming you have three data areas (data1, data2, data3) to stripe your database across, the structure file looks like:
d d d d d d d d d d d x:\data1\database.d1 x:\data2\database.d2 x:\data3\database.d3 x:\data1\database.d4 x:\data2\database.d5 x:\data3\database.d6 x:\data1\database.d7 x:\data2\database.d8 x:\data3\database.d9 x:\data1\database.d10 x:\data1\database.d11 f f f f f f f f f f 195328 193528 193528 193528 193528 193528 193528 193528 193528 193528
Notice how each extent carries a .dx extension where x indicates the extent number. Also notice the striping of the extents across the three data areas. Notice in the last extent (.d11) that there is no file size specification (f). The last extent should always be created as a variable extent (no f or size specification). This extent is allocated as one operating system block size. It remains the same size until all the fixed extents are full. Then, the system starts writing to the overflow variable extent. This extent will grow until it fills the available disk space or until you take some action. The action to take is to enlarge the database; refer to Adding Extents on page 53.
Before-Image Extents
As an option, you can add before-image extents to the multi-volume database. Having .bi extents is optional because it is unlike the database. The database has many logical files (tables) within it, such as ad_mstr, cm_mstr, and mnd_det. The .bi file, however, is made up of only one logical file. The system writes to it sequentially and reads back from near
50
the bottom of the file. Therefore, multiple access channels do not offer as much I/O gain as with the database. However, .bi extents offer some I/O advantage because the .bi file uses index keys, maintained in master blocks. These blocks are written to and read from often, just like the body of the file. Separating the master blocks from the body of the file eliminates some contention. Also, by defining a .bi extent, you can hard code the .bi files location, alleviating the need to ever use the -g parameter. Keep in mind the following recommendations.
For the fixed-length .bi extent, the total .bi file size depends largely
on how often you shut the server down and truncate the .bi file. If you shut down weekly, set your .bi file fixed extent to 2040% of the total database size.
You should also define a variable-length .bi extent because the .bi file
may jump in size. PROGRESS shuts down if you run out of .bi space.
Assign the .bi files to a separate disk or disks from the database.
The completed structure file could look like:

d d d d d d d d d d d b b b \data1\database.d1 \data2\database.d2 \data3\database.d3 \data1\database.d4 \data2\database.d5 \data3\database.d6 \data1\database.d7 \data2\database.d8 \data3\database.d9 \data1\database.d10 \data1\database.d11 \bi1\database.b1 \bi2\database.b2 \bi1\database.b3 f f 195328 195328 f f f f f f f f f f 195328 193528 193528 193528 193528 193528 193528 193528 193528 193528
51
Creating a Void Multi-Volume Database

You use the PROGRESS PROSTRCT utility to create and manage the multi-volume database. The command to start the utility enables you to specify from various options, including Create, Add, List, Statistics, and Repair. The syntax for the PROSTRCT command is:
DLC\bin\prostrct option dbpath\dbname stpath\stname
The components of this command are explained in Table 4.3.

Table 4.3
Syntax Item DLC prostrct option dbpath/dbname stpath/stname
Explanation
PROGRESS install directory.

The .bat file that starts the prostrct utility. The prostrct option to use. Options include: create, add, list, statistics, and repair. The path and name of the actual .db file to create. Path/name of structure file used for extent definitions.
PROSTRCT Command Components.
The resulting database is void. It has no schema and no data. You can see the extents in their specified directories, but they are empty files. In addition to creating the extents listed in the structure file (extension .d1, .d2, etc.), the PROSTRCT utility also creates the database structure extent (extension .db). The database structure extent contains no schema, data, or indexes. It simply contains the map of where each extent is located, as specified in the structure file. All PROGRESS commands should refer to the database structure extent as if it were a single-volume database file. PROGRESS resolves the actual location of database extents, which contain the data.
Note This could be a time-consuming step, depending on the size of the
database and extents.
52
Load Schema and Data

Since the newly created multi-volume database is void (no schema or data), you cannot start up an MFG/PRO session. You must first load a schema and, optionally, data. To perform the load you can either:
Use the PROGRESS Data Dictionary or any other standard load
method.
Use a PROGRESS copy utility called PROCOPY.
You can use PROCOPY for either an empty database (such as mfgempty) or a working database. With an empty database, only a schema loads. With a working database, both the schema and the data load. The procopy method is recommend if you want to convert a single-volume database to a multi-volume database. The syntax for the command is:
$DLC\bin\procopy path\source.db path\target.db
Figure 4.3 summarizes how the prostrct and procopy commands work together.
Fig. 4.3
Converting SingleVolume to MultiVolume
Multi-Volume Structure Structure Description Description File File (.st) (.st) prostrct
.db .d1 ... .dx
(creates a void multi-volume database)
Single-Volume
.db
procopy
.bi
(copies schema and data from single volume)
.bi
53
Multi-Volume Database Administration

To set up and maintain a multi-volume database, PROGRESS provides the PROSTRCT utility. For details on maintenance tasks, refer to the PROGRESS System Administration Guide. One of the administration tasks commonly performed is adding extents.
Adding Extents
If your variable extent is growing too large, you need to enlarge the database by adding more extents. This is done by creating another structure file (for example, add.st) in the same format as the original, except you do not include the extents already used. Using the example on page 49, the new add.st file would begin with .d12. The same rules apply to this structure file. When ready, you run the PROSTRCT add command and specify your new structure file. When this procedure is run, extent .d11 (variable extent) is locked in as a fixed extent at its current size, rounded to a size expressible as a multiple of 32 (to be multiplied by the 1024 block size). Once this procedure is run, you have two applicable structure files that together constitute the entire current database structure. For housekeeping reasons, you should concatenate these two files. You could do this using an editor tool, or the PROSTRCT utility has a List option that reads the database structure and creates a current structure file for you. PROSTRCT also has a Statistics option that reports total database size, current database usage, last backup time, and so forth.
54
CHAPTER 5
Split Schema Database

The reasons and procedure for splitting the MFG/PRO production database are described in this chapter. Reasons for Splitting Database Schema Determining How to Split the Schema System Requirements 59 60 56 57
Creating a Split Schema Database Administering the Database 62
56
Reasons for Splitting Database Schema

The reasons for splitting the MFG/PRO production database schema include the following:
Database becomes too large to efficiently administer Performance has slowed and is difficult to control Set of common files is beneficial
Splitting the database may solve these situations, as described in the following sections.
Enhance Database Administration

If the MFG/PRO database has become too large (more than eight gigabytes), administrative tasks such as a Dump/Load or Index Rebuild require too much time and effort. For example, a Dump/Load or Index Rebuild may be required to recover from database corruption. This activity may take many days to accomplish. Two or more days downtime for a dump/load is unacceptable to most companies.
Increase Performance
Another reason to split the schema is improved performance. With a single-schema production database, you cannot control the locations on disk of individual tables in the database. In addition, you cannot control the memory allotment for individual tables. For example, if a process (such as a long-running report) heavily engages a certain table (such as TR_HIST), you cannot dedicate any extra memory to the use of that table or tables. Both these conditions cause poor performance because of either a lack of I/O balance or a lack of memory buffer balance. This issue is particularly critical for a large number of concurrent users (200 or more).
SPLIT SCHEMA DATABASE
57
Can You Split Across Multiple Machines?
QAD does not recommend that customers put their split databases onto separate machines. In this scenario, there are several machines that host different portions of the database and they are connected through client/server PROGRESS to create the complete schema of MFG/PRO. If the customer chooses to follow this scenario, they must run two-phase commit and after-imaging to ensure database integrity. The reason a customer may want to follow this design is that it can be used to balance the CPU activity of machines. It can also be used to maintain common files without using replication.
Create Common Files

Splitting the schema also lets you create a set of common files that can be shared by multiple databases, such as CM_MSTR, AD_MSTR, IN_MSTR, and PT_MSTR.
Note Using a split schema in conjunction with multiple production
databases, commonly called Central Order Processing with Multiple Databases, is not explained in this document. It involves making custom programming modification to MFG/PRO.
Determining How to Split the Schema

Once you have made the business decision to split the MFG/PRO schema, you must make additional business decisions to determine where to split the schema. Use the examples shown in Table 5.1.
Table 5.1
Tables in DB1 Example 1: All tables not in DB2 and DB3. Must include required files. All tables not in DB2, DB3, and DB4. Must include required files.
Tables in DB2 TR_HIST
Tables in DB3 GLTR_HIST
Tables in DB4
Suggested Splits
Example 2:
QAD_WKFL TRGL_DET
TR_HIST
GLTR_HIST
58
Recommended Split for ECommerce

If you have the ECommerce Gateway implemented, QAD recommends that you split the following tables and sequences into a second database to improve performance.
Recommended ECommerce Tables edc_ctrl edmfdd_det edmfd_det edmfrd_det edmfr_mstr edmfsdd_det edmfsd_det edmfs_mstr edmf_mstr edmidd_det edmid_det edmi_mstr edmsg_mstr edrrx_ref edmfs_sq01 edc_sq02 edsdd_det edsd_det edss_mstr edsxx_ref edtadm_mstr edtarf_mstr edtar_mstr edta_mstr edtg_mstr edtmx_ref edtpd_det edtpparm_mstr edtp_mstr edtrd_det edxfs_sq01 edtrf_mstr edtrp_mstr edtrv_mstr edtr_mstr edval_mstr edxfdd_det edxfd_det edxfsdd_det edxfsd_det edxfs_mstr edxf_mstr edxrd_det edxref_mstr edxr_mstr edc_sq01
Recommended ECommerce Sequences
59
System Requirements
Physical disk and memory considerations are the primary requirements for setting up a system for splitting schema. These requirements are described in the following sections.
Physical Disk Requirements

Configuring the physical disks is the most important factor when splitting the schema. Many people mistakenly think about the number of gigabytes (raw storage). Instead, they should think of the number of separate physical disks (spindles). Twelve 4-gigabyte drives provide a much better load balance than six 8-gigabyte drives. A greater number of drives (even smaller drives) provide more efficient splits because you can more effectively spread out the databases, before-image files, and after-image files among more disks. Remember that the standard rule of keeping the before-image file on a separate disk still applies. The after-image files must also reside on a separate physical disk, preferably a separate controller from the database and before-image files, to ensure its integrity if the disk or controller containing the database or before-image file crashes. This technique is also required to balance I/O across disks because the after-image and the before-image files are single-threaded and must be written before any work can be performed on the database.
Example As an example, consider a 12-gigabyte database, with a
See Relocation of the Before-Image File on page 33
multi-volume structure spread across less than 13 fast and wide SCSI disks. Are there enough disks? If before the split you need five gigabytes for the GLTR_HIST table, there are probably not enough disks. The general rule in this case is one gigabyte of data per physical disk and one gigabyte of data per before-image file. This rule can be expanded for EMC disks so that no more than 50 percent of the disk is used for data and the before-image file is on a separate disk.
60
Memory Requirements
Another important requirement is your amount of memory and the system parameters that control memory. If the database is large, the buffer pool is likely to be several hundred megabytes or larger. In this case, reapportion memory so that virtually the same amount of memory is used for multiple databases instead of one large database. As part of the memory requirements, you may need to tune several kernel parameters, such as MAXPROC, NFILE, SHMSMAX, SHMSEG, and MAXFILES. Because there are more files that must be opened to start a session, the MAXFILES and NFILE parameters most likely require tuning.
Creating a Split Schema Database

This section outlines the overall steps for creating a split schema database. It does require having a 4GL version of PROGRESS and familiarity with the PROGRESS Data Dictionary. These instructions assume you are connecting to only one cumulative MFG/PRO schema. It does not support setting up a split schema and also connecting to multiple MFG/PRO production databases (commonly called Central Order Processing with Multiple Databases). If you want that functionality, you need to modify several programs in MFG/PRO so that, when the database alias is changed, the split schema databases are moved as a set. If the programs are not modified, transaction data will be placed in the wrong database. Prerequisites:
Make sure you have analyzed all tables to decide which tables you
want to centralize and which you want to localize.

Back up your databases. 1 2
Make a copy of the mfgempty database located in the standard QAD directory. This becomes a working copy of the database. Connect in single user mode to the database:
ProgressDir/bin/pro /qad/split
61
3 4 5
Run the Data Dictionary using either the Menu/Tools or the command dict. Select Admin/Dump Data and Definitions/Data Definitions. Select the database tables to separate (i.e. TR_HIST, GLTR_HIST, etc.) one at a time. This creates separate .df files that contain the database definitions for the individual files. Select Utilities/Freeze Unfreeze from the Dictionary Menu. Set frozen to NO for all the dumped file definitions. Select Schema/Delete from the Dictionary menu and delete all the File Definitions for all the files to be separated. Select Admin/Dump Data and Definitions/Data Definitions and dump the schema for the rest of the tables in the database. database per the design chosen. Be sure to delete all but the last trailer record in the individual .df files so that the schema load will load all the tables.
6 7 8 9
10 Link together all the .df files together that are supposed to be in one
11 Make a copy of the PROGRESS Empty database for each of the new
databases to be created.
12 Connect to each of the databases in turn, and load the schemas created
using the Dictionary/Admin/Load Data and Definitions/Data Definitions. You have now created the default databases in the split. These should be used at compile time and to make copies for the creation of new databases only.
13 Create a new compile database set in MFG/UTIL that contains all the
databases in the split with the first database containing the files noted above and a logical set of qaddb.
14 Recompile all the MFG/PRO programs as given by the original file
called utcompil.wrk. After splitting the database, modify all scripts and parameter files to connect the new databases with the logical database names specified in the compile script or set.
62
Administering the Database

Administration of the database is an important aspect of splitting the schema. Treat all databases in the split as one set. If one database crashes or becomes inoperative, all databases must be treated as if they are down. Also, if one database must be restored from backup, all the databases must be restored. This must be done to maintain the integrity of the data since a transaction may now span multiple databases. In addition, it is strongly recommended that after imaging be turned on for all databases. It is also imperative that all the databases are brought down together for backups so that data integrity can be maintained.
CHAPTER 6
General Administration
Topics in this chapter: Maintaining MFG/PRO Scripts and Database Sets Setting Up Training Databases Compiling Programs 68 74 64 64
Batch Processes with PROGRESS Prowin32 Batch Client
64
Maintaining MFG/PRO Scripts and Database Sets

To modify the MFG/PRO start-up and shut-down scripts and icons, you can use the MFG/UTIL utility. The scripts and icons are based on database sets. A database set defines the connection parameters for a group of databases.
1 2 3
From the MFG/UTIL Configure menu, choose Any Database Set and complete the Database Set Configuration window. To save your changes to the start-up scripts, choose one of the generate options from the Scripts menu. If you added a new database name, set it up in the hosts and services files on both the server and client PCs. For detailed instructions, refer to the MFG/PRO installation guide. Remember to make your changes on both the server and, if applicable, Windows clients. There is one version of MFG/UTIL on the server and another on the Windows client.
Setting Up Training Databases

Starting with MFG/PRO Version 8.6E, additional training databases are available for specific business environments. MFG/PRO 9.0 provides enhanced multiple currency capabilities to support the eurothe single European currency being introduced by the European Monetary Union (EMU). The standard MFG/PRO training database (mfgtrain) does not contain multi-currency instruction appropriate to this new business environment. To provide this instruction, QAD has created the Triangulation training database (tritrain). To enable a business specific training database, you must complete the following tasks.
Setting Up the Training Database Server Setting Up the Training Database Client
GENERAL ADMINISTRATION
65
Setting Up the Training Database Server

Follow these instructions to create a specialized training database server.
1 2 3 4
Start MFG/UTIL from the database server program group. Select the Configure menu, and choose Any Database Set. In the Database Set Configuration window, choose New Set. In the Database Sets window, select the Set Name field and type the name you will use for your new training database set. For example, tritrain.
5 6
Set the Active field to Yes, and accept the default in all other fields. Choose OK. Add database servers to your training database set by choosing New Server and completing the Database Parameters window for each database. Use the following table and graphic as an example. For this example, the tritrain database is used. Your training database may be different.
Physical tritrain mfghelp gui cfg
Description Triangulation Train Help Database Gui Database Configurator Database
Service tritrain mfghelp gui cfg
Path InstallDir\ InstallDir\us InstallDir\us InstallDir\us
66
7 8 9
Once the database set is complete, choose OK in the Database Set Configuration window. At the MFG/UTIL window, select the Scripts menu and choose Generate Server Startup and Shutdown... At the Server Script Creation window, select the your training database and choose OK.
MFG/UTIL will generate database server start-up and shutdown icons for your training database.
See the MFG/PRO Installation Guide PROGRESS on Windows NT, for instructions. See the MFG/PRO Installation Guide PROGRESS on Windows NT, for instructions.
Note QAD highly recommends that you use the PROGESS ProControl
utility to run your MFG/PRO databases as registered Windows NT services.
Setting Up the Training Database Client

Follow these instructions to create specialized training database clients. These instructions assume that you have already set up MFG/PRO GUI clients.
1 2 3
From an MFG/PRO client PC, start MFG/UTIL. Select the Configure menu, and choose Any Database Set. In the Database Set Configuration window, choose New Set.
67
In the Database Sets window, select the Set Name field and type the name you will use for your new training database set. For example, tritrain. Set the Active field to Yes, and accept the default in all other fields. Choose OK. Add database clients to your training database set by choosing New Client and completing the Client View of Database Parameters window for each database.
a b c
5 6
In the Connection Type field, choose ClientServer for each database client. In the Host field, enter the name of your MFG/PRO 9.0 database server machine. Use the following table as an example for the remaining fields. For this example the tritrain database is used. Your new training database may be different.
Physical tritrain mfghelp gui cfg Logical Leave blank qadhelp qadgui qadcf Service tritrain mfghelp gui cfg
Database Training Help Gui Configurator
7 8 9
Once the database set is complete, choose OK in the Database Set Configuration window. At the MFG/UTIL window, select the Scripts menu and choose Generate User Startup... At the Server Script Creation window, select your training database and choose OK.
MFG/UTIL will generate a client icon for your training database. Test your training environment by double-clicking the new training client icon.
68
Compiling Programs
Sometimes you may need to compile a custom program, or recompile an existing program. Do this using MFG/UTIL. You must have the source file you want to compile. Once the source file is compiled, an object file with the same name and a .r extension is created. By default, MFG/UTIL saves the .r program in a sub-directory using the first two letters of the program name. This subdirectory is located under the two-letter language directory, below the main MFG/PRO installation directory. For example, the program somstr.p would be saved in: InstallDir/us/so. Keep in mind that you have two sets of code to maintain: the Windows character programs on the server and the Windows client programs on the file server. (The Windows client source code is optional at MFG/PRO client installation.)
Using MFG/UTIL to Compile

MFG/UTIL provides a compile function that lets you compile against an active database. Use the following instructions to compile.
Important Before using MFG/UTIL to compile MFG/PRO code,
additional steps must be taken if you are planing to compile under one of the following circumstances.
You are performing a non-English language compile. You are compiling character code.
Non-English Language Compile

If you are compiling for a non-English language, you must first create a compile database set. Refer to the instructions in your installation guide, Multiple Language Setup chapter.
69
Compiling Character Code

Compiled character code is not completely portable across platforms. Differences exist between character r-code compiled on Windows character client machines and UNIX machines.
Important Because many MFG/PRO programs reference, or share, the
same program frame layout, run-time errors occur when character code compiled on different machines is mixed. QAD compiles all MFG/PRO character code on UNIX. The compiled character code (.r extension, referred to as r-code) is initially portable across platforms because all the program frames have the same layout. A problem arises when users compile programs at their sites, for custom programs or patch implementation. The recompiled programs reference frame layouts specific to the machine where they were compiled. For example, programs compiled on Windows character clients reference Windows frame layouts and can no longer reference the existing UNIX character code frames. When incompatible code is run, the following PROGRESS error occurs. In this example, ProgramName refers to the recompiled program name, and FrameName refers to the shared frame the program uses.
ProgramName Shared frame layouts do not match for frame FrameName. (683)
Solution
To solve this problem, choose one of the following options.

Recompile all character programs on a single machine and perform
all future compiles on the same machine. For example, recompile all character code on a Windows character client and perform all future compiles on a Windows character client.
Note This option does not require any additional setup or software.
Recompile all character programs using the PROGRESS 8.3 portableframes start-up parameter. Perform all future compiles
using this parameter. Use the instructions in Compiling with the portableframes Parameter on page 70 to implement this option.
70
Compiling with the portableframes Parameter
The portableframes parameter enables you to compile on either UNIX or Windows machines. Use the following instructions to implement this solution. Beginning with PROGRESS Version 8.3A03 for Windows, the portableframes start-up parameter is provided to enable the creation of portable character code from either Windows character clients or UNIX machines.
Important Once this parameter is set, all character code must be
compiled using it. Run-time errors occur if you mix character code compiled with the
portableframes parameter and character code compiled without it. If you choose to use the portableframes start-up parameter, you must
recompile all MFG/PRO character code with it. Future compiles can be performed on either UNIX or Windows character client machines, but must have the portableframes parameter set. To implement the portableframes start-up parameter, use the following instructions.
Important QAD recommends that you recompile all programs during
installation. If not, you must recompile all MFG/PRO programs when you compile your first patch or custom program.
1 2 3 4 5
Right click the Start menu button. Select Open All Users and the Start program group is displayed. Double click on the Programs icon. The individual programs are displayed. Double click the MFG/PRO program folder. Edit the properties of the MFG/UTIL icon by performing the following:
a b
Right click the MFG_UTIL icon and select Properties. From the Properties window, select the Shortcut folder tab. Add the portableframes parameter to the end of the Target field.
71
c 6
Click the Apply button to save your changes
When using PROGRESS Version 8.3 and MFG/UTIL to compile allor a large number ofMFG/PRO programs, you may receive the following error.
Error: Insufficient disk space or write access denied (291).
To avoid this error, add the following start-up parameters to the target field after the -d and -yy parameters and before the -ininame parameter.
-D 50 -TM 31 -TB 31 -B 100
Perform all MFG/PRO compiles using this MFG/UTIL icon.
Compiling Code
1
Start an MFG/UTIL session on either the server or a Windows client PC. This session must run against a copy of PROGRESS ProVISION or 4GL. From the MFG/UTIL main menu, select Program, then Compile Procedures. In the Source Directory field, enter the source directory where the .p and other source files are located. Using the two radio buttons, you can compile all of the files in the source directory or point to a work file that contains a list of the files to be compiled. If you select the Files listed in the work file option, another input field displays. Enter the full path name of the work file in this field.
2 3
72
Indicate if you want the new .r files saved. If you are performing test compiles, leave this box unchecked until you are ready to do your final compile. In the Destination directory field, enter the full path name of the destination directory. If you choose to save the compiled files, do the following substeps.
a
Enter or accept the default for the two-letter language code in the Language field. It is appended to the end of the directory you specify in the Destination directory field depending on your choice in the next step. Choose the MFG/PRO default option or the flat destination option. With the default option, your compiled .r code is placed in a series of two-letter sub-directories based on the first two letters of the program name. Also, if you compile triggers, they appear under a .\triggers sub-directory. With the flat destination option, all .r code is placed directly under the destination directory, with no language code directory appended.
73
The compile process must connect to an active database. In the Use this database set field, select a database set to run the compile against. If you have configured a compile database set, you should select that set; otherwise, select any database set that already has database servers started for it. Choose Compile. During the compile, an Installation Log Window displays the current status.
7 8
When the compile ends, choose Print or Close.
Note MFG/UTIL saves the settings you entered in the Compile
Procedures Files window so that you can reuse or modify them for the next compile.
74
Batch Processes with PROGRESS Prowin32 Batch Client

In an MFG/PRO for Windows NT Version 9.0 environment, you can significantly improve performance of certain functions by using the PROGRESS Prowin32 Batch Client. This client can be used to process long-running batch jobs such as regenerative MRP or provide continuous Hotbatch processing for background operations such as printing large reports. The examples in this section illustrate how to set up batch processing to run a regenerative MRP against the mfgdemo database and set up Hotbatch processing.
Overview
Setting up the batch process consists of implementing a pre-compiled batch.p program to be called by Prowin32. The following is an overview of the activities required to create this program.
Editing the Batch Program and Input Control File
To meet your specific requirements, you must modify the sample batch program and the input control file provided in this release.
Copying and Editing the progress.ini File
The progress.ini file, which you rename progress.bch, controls your batch processing environment variables, such as the PROPATH.
Modifying the batch.pf File
This file must point to your production database.

Creating Unique Batch Directories
Instructions on setting up batch directories for different batch jobs.

Defining Batch IDs for MRP and Hotbatch
An example MRP batch ID is explained, as well as a Hotbatch batch ID for running continuous batch processes.
75
Submitting Batch Jobs in MFG/PRO
Once you define the batch IDs, you can schedule items in MFG/PRO.
Scheduling Batch Jobs in Windows NT
You can schedule the batch jobs using an icon, the Windows NT AT command, or the Windows NT Resource Kit scheduler.
Note If you are using ProControl to start your databases, it is critical for
batch processes that you set up the ProControl environment setting ACCESS=all.
Editing the Batch Program and Input Control File

MFG/PRO for Windows NT Version 9.0 includes a pre-compiled batch control program. Below is a listing of that batch.r control program. The batch.r program is in the InstallDir\BATCH directory.
Statements in batch.p Program INPUT from batchin.inp. OUTPUT to batchout.out. PAUSE 0 BEFORE-HIDE. RUN MF.P. INPUT CLOSE. OUTPUT CLOSE. Comments Defines the input control file. Defines an output file for MFG/PRO screens. This can be very useful for debugging. Standard programming convention. Calls the MFG/PRO main program. Cleanup. Cleanup.
For details, see Installation Guide PROGRESS Database on Windows NT Server.
There are two sample batch input control files in the sub-directory InstallDir\batch:
mrpbatch.inp: Intended for MRP batch processes. hotbatch.inp: Intended for continuous background processing.
76
To use either of these sample files, you must first copy or rename the selected file to batchin.inp.
Statements in mrpbatch.inp Input Control File "" "mgbatch.p" "mrp" . . "Y" Comments Positional field. Call the mgbatch program. Call the MRP Batch ID. Escape. Escape. Log off confirmation.
Statements in hotbatch.inp Input Control File Comments "" "mgbatch.p" "hotbatch" - - - - - - - - - "yes" "30" Positional field. Call the mgbatch program. Schedule the hotbatch Batch ID.
If you choose to set up both hotbatch and mrpbatch, you must put each batch input control file, along with all other batch processing files, in unique directories. You need a unique directory for each input control file because the control file name, batchin.inp, is the same in all cases.
Note The minimum files required in each batch directory are: batch.pf, batch.r, batchin.inp, and progress.bch.
Copying and Editing the progress.ini File

1 2 3
Copy the DLC\bin\progress.ini file to InstallDir\batch\progress.ini. Rename the extension of the copied file to progress.bch. Open the copy of the progress.bch file in a text editor.
77
In the [Startup] section, modify the PROPATH entry to point to your InstallDir directory and the InstallDir\triggers directory.
Example Original PROPATH.

PROPATH=.,c:\DLC\PROBUILD\EUCAPP,C:\DLC\PROBUILD\ EUAPP\EUC.PL
Example Modified PROPATH. In the following, mfgntsvr is the
MFG/PRO database server installation directory.

PROPATH=.,d:\mfgntsvr,d:\mfgntsvr\triggers
This sets the batch PROPATH to point to the MFG/PRO Windows NT 9.0 character code on your database server.
5
Save your changes.
Modifying the batch.pf File

In this section, you will modify a copy of the standard batch.pf file to use as the batch start-up parameter file. This file is used during batch processing to point to your production database and to set certain PROGRESS environment variables. You will find the batch.pf file in the InstallDir\batch sub-directory.
1
Open batch.pf in a text editor. Sample File:

-db your-production-database -mmax 8192 -l 4096 -T yourtemp-drive
Change -db your-production-database to point to the location of your production database. Use the full path. Example:
-db d:\mfgntsvr\mfgdemo.db
Change -T your-temp-drive to point to a temp file location. Example:

-T c:\temp
78
Specify the location of your gui database using the following line.
-db your-gui-database -ld qadgui
Example:
-db d:\mfgntsvr\gui.db -ld qadgui
Add the -cpinternal, -cpcoll, and -cprcodein database connection parameters. Use the settings appropriate for your language. The following example applies to most Western European language systems.
-cpinternal iso8859-1 -cpcoll basic -cprcodein iso8859-1
Save the batch.pf file.
Note If you change the location of your databases, make sure the batch.pf file is also changed to reflect the new database locations.
Creating Unique Batch Directories

As an example of creating batch processes for various batch jobs, you will create unique directories for your Hotbatch and MRP batch jobs. Depending on your business, other batch directories might be set up for daily, weekly, and monthly batch processes.
1
With Windows NT Explorer or File Manager, create Hotbatch and MRP directories under InstallDir\batch.
InstallDir\batch\mrp InstallDir\batch\hotbatch
2 3 4
Copy the InstallDir\batch\hotbatch.inp file to your Hotbatch directory, and rename it batchin.inp. In your Hotbatch directory, open the batchin.inp file in a text editor. Change the last variable in the final line from 30 to 300.
"hotbatch" - - - - - - - - - "yes" "300"
The batch ID hotbatch will now be run every 300 seconds.
79
5 6
Copy the InstallDir\batch\mrpbatch.inp file to your MRP directory, and rename it batchin.inp. Copy the remaining batch files into both directories.
Batch Process Files
batch.pf batch.r progress.bch
Both your Hotbatch and MRP directories should now contain the required batch files: batchin.inp, batch.pf, batch.r, progress.bch.
Defining Batch IDs for MRP and Hotbatch

Use the following steps to define the MRP batch job.
1 2 3
Start an MFG/PRO client session against your production database. In this example, we are using mfgdemo as the production database. Log in and select menu item Batch ID Maintenance (36.14.1). In Batch ID Maintenance, do the following steps:
a b
Create a Batch ID called MRP. Enter the MRP Batch ID name, and press Enter. Enter the Permanent and Priority fields.
80
Note In this example, the Permanent field is set No and the Priority field is set to 10. This is the priority that this Batch ID runs in relationship to concurrent batch processes. Priority 10 is the highest.
Use the following steps to define the Hotbatch batch job.

1
In Batch ID Maintenance (36.14.1), complete the following steps to add a new Batch ID record.
a
Create a Batch ID for a Hotbatch batch job.
Set the Permanent field to No. If the Permanent field is set to Yes for hotbatch jobs, they will run continuously at the rate specified in the batchin.inp filefor example, every 300 seconds.
Note To shut down a continuous batch process without shutting down
the associated databases, use the Windows NT Task Manager (Ctrl + Shift + Esc) to End Task the PROGRESS application.
c 2
Press F2 to add the new Batch ID record.
When the process is completed, press Esc.
81
Submitting Batch Jobs in MFG/PRO

These steps explain how to submit batch jobs using the examples of Regenerate Materials Plan (MRP batch ID) and Control File Report (Hotbatch batch ID).
1 2 3
From the main menu, select Regenerate Materials Plan (23.2). At the Regenerate Materials Plan window, enter a site range of 1000 to 5000, then choose Print. At the Print Options window, select your output device, select the MRP Batch ID, and choose OK.
Exit from Regenerate Materials Plan. The MRP request is now queued for batch processing.
82
Hotbatch Batch ID Example 1 2
Select any report; for example, Control Files Report (36.17.6). In the Control Files Report window, select your output device, select the Hotbatch batch ID, and press F2.
Your Report is now scheduled for background printing under control of the batch processor.
3
You can check the status of your batch requests by selecting Batch Request Detail Maintenance (36.14.3).
Scheduling Batch Jobs in Windows NT

To schedule a batch job, it is recommended you use a .bat (batch) file. Once you set up this file, you can use either or both of the example techniques shown in this section:
Using an icon (launches the process on demand) Using the AT command (launches the process at a scheduled time)
You can also use the Microsoft NT Resource Kit to schedule batch processing. See that products documentation for details.
Set Up .bat File
These steps are required whether you use the icon or AT command method of scheduling.
83
In a text editor, create a .BAT (batch) file for each batch directory. For example, this chapter created MRP and Hotbatch directories. Use the following text.
ProgressDir\bin\prowin32.exe -b -p batch.p -ininame progress.bch -pf batch.pf
Use any name for the .BAT file. The subsequent steps see this file as BATFileName.bat.
Using an Icon
Use these steps if you choose to set up a shortcut icon that launches MFG/PRO batch processing on demand.
1
Create a new batch client shortcut with the following properties in the Shortcut tab.
Target: Start In:
InstallDir\batch\BATFileName.bat InstallDir\batch
You can now call the Batch Process by clicking the new Batch icon. To track the process, use the Window NT Task Manager, Applications tab.
84
Using the AT Command
Use these steps if you choose to set up MFG/PRO batch processing on a scheduled basis.
1
From the Control Panel, select Services.
From the Services window, highlight Schedule and choose the Startup... button.
85
In the Service window, do the following.

a b
Select Automatic under the Startup Type so that the service is always running. Select Allow Service to Interact with Desktop (the box should be checked). This setting is required for the batch program to run. Choose OK.
When the Services window reappears, make sure Schedule is still highlighted and choose Start. The following window appears as this service starts.
Verify that Started appears in the Schedule status and choose Close.
86
To schedule the batch job with the AT command, open the DOS Command Prompt window and enter the appropriate AT syntax. Use the following examples as guidelines. For more information on the Windows NT AT command, see Microsofts Windows NT documentation or online help. To run the batch job every weekday at 7 pm, type the following as one command line:
at 19:00 /interactive /every:M,T,W,Th,F BatchDir/BATFileName.bat
To run the batch job once at 6 pm the same day, type the following:
at 18:00 /interactive BatchDir/BATFileName.bat
To view the schedule of batch jobs, type:

at
CHAPTER 7
Using PROGRESS RESULTS with MFG/PRO

This chapter explains how to set up the RESULTS reporting tool for use with MFG/PRO. For details on using this tool to produce reports, refer to the PROGRESS documentation. About RESULTS 88 88 88
RESULTS Setup Overview
Setting Up RESULTS to Start from a MFG/PRO Menu
88
About RESULTS
RESULTS is a PROGRESS ad-hoc reporting tool available for UNIXbased character clients, 16-bit Windows clients, or 32-bit Windows clients.
RESULTS Setup Overview

This section explains how to set up RESULTS to run from the MFG/PRO menu. If you run RESULTS from an MFG/PRO menu, you must make some programming changes to ensure that the F2 and F6 function keys operate correctly for both MFG/PRO and RESULTS. The way MFG/PRO defines these function keys differs from PROGRESS, which can create errors if you do not correct for this situation.
Setting Up RESULTS to Start from a MFG/PRO Menu

Follow these steps to run RESULTS from an MFG/PRO menu.
1 2
Make certain that your PATH contains $DLC/bin. So that RESULTS starts correctly, make sure the RESULTS installation directory is part of the PROPATH system variable and that it is listed after the MFG/PRO installation directory. Copy the MFG/PRO RESULTS files to your production database directory using the source directory:
MfgProInstallDir\results\v2
4 5
In a MFG/PRO session, start Menu System Maintenance (36.4.4). In Menu System Maintenance, complete the fields according to the following table. After you complete the line item entry, press End.
USING PROGRESS RESULTS WITH MFG/PRO
89
Language ID
Accept the default language code or another, if appropriate. For example, the language code for English is us. Menu number where RESULTS selection item appears. Selection item that starts RESULTS. Type PROGRESS Results. Type results. For a UNIX server, type results1.p. For a Windows NT server, type results.p. Leave this field blank.
Menu Sel (selection) Selection Label Name Exec File Help File
90
CHAPTER 8
MFG/UTIL Reference Information

This chapter describes the MFG/UTIL functions, along with other reference information. MFG/UTIL is the installation and system management tool for MFG/PRO. There are two instances of MFG/UTIL: one on the server and one on each client PC. Depending on your administration task, you may need to run one or the other or both. Database Menu Program Menu DataServer Menu Scripts Menu Configure Menu 99 100 103 92 97 99
Sections in mfgutil.ini
92
Database Menu
Create Database
Select this option from the Database menu to choose a data definition file and create a new PROGRESS database or schema holder. Once you have completed the information, choose OK to begin the database creation.
Data Definition File The data definition file contains all the schema definitions for your database. You can also choose Browse .df File to browse your directories for the path and file name. You can load schema using one of the standard .df files or a .df file you have created. MFG/UTIL will load the schema specified in this .df file, using the dfloadx program. Enter the physical name of the database to create. Include the full path name. MFG/UTIL currently installs the PROGRESS database type. Reserved for future use. To create the database and load the data from a set of files (.d), choose this option. MFG/UTIL uses the mgdload program to load the data into the new database. Enter the database name where you want to load the data. The new database name defaults to this field, but you can enter another database name if you want, for example, to create an empty database called mfgempty.db, and at the same time load data to another database called mfg.db. Enter the path to the directory that contains the data files (.d files). The program then loads all .d files in this directory with a corresponding table name in the destination database. Opened from the Database menu, this option enables you to load data from a set of data files (.d) into a new or existing database. MFG/UTIL uses the mgdload program to load the data into the specified database. For MFG/PRO on ORACLE, loading into a new database is not available. Also, after this dialog, you must complete the Connect to a Database dialog. Enter the full path to the directory that contains the data files (.d files). The program then loads all .d files in this directory with a corresponding table name in the destination database.
Database Name Database Type Database ID Load Data
To this Database Name
From this Directory
Load Data from Directory
From this Directory
MFG/UTIL REFERENCE INFORMATION
93
From this Empty Database
If you want to load data into a new database, first specify which empty database you want to use as the basis of the new database. Enter the full path and physical name. For example, to load into a new copy of the main MFG/PRO database, specify mfgempty. For MFG/PRO on ORACLE, simply enter the path and name of the oraempty schema holder. Enter the new or existing database name where you want to load the data. For MFG/PRO on ORACLE, enter the schema holder used to connect to your existing ORACLE database.
To this Database Name
Load Data File into Existing Database

Use this option to load a data file (extension .d) into an existing database. You can load only one data file at a time. MFG/UTIL first opens the Connect to a Database window, and then displays the following fields.
Choose a table to load Allow Errors During Load Input File Select the target database table. By selecting this option, the load will continue even if an error is encountered. Type the name of the data file (.d). Include the directory path if it is not within the current working directory.
Update Schema
Select this option from the Database menu to update the schema for an existing database. Be sure you have a complete backup of any database before you begin an update. Once you have completed the information, choose OK to begin the database update.
Update this Database File Using this Data Definition File Allow CRC Changes Enter the database file to update. Choose Browse .db File to choose the path and file name. Enter the data definition file that contains the new schema definitions. Choose Browse .df File to choose the path and file name of the data definition file. Check this box to allow for CRC changes to the database during the update. Choosing this option might also require you to recompile programs before you can use them with the updated database.
94
Split Database Schema File

For more information, see Split Schema Database on page 55.
This option enables you to split a single database schema file, such as mfgempty.df, into multiple database definition files. You can then use these .df files to create multiple databases in a split schema installation. Split schemas are generally used to enhance system performance or to maintain different information at different physical locations. To use this feature, select Split Database Schema File from the Database menu.
Note MFG/UTIL provides a tool only for splitting the schema definition file. Since setting up a split schema installation involves additional considerations and requirements, it should be attempted only by an experienced system administrator.
Processing Logic
MFG/UTIL reads two files, the split schema definition file and the master .df input file. It produces a default .df output file plus one schema definition file for each section defined in the split schema definition file. The split schema definition file has a syntax similar to a standard .ini file, but uses a .spl extension, by default. All other files use the syntax of a standard PROGRESS database definition file and have the .df extension. When splitting the schema, MFG/UTIL reads each line from the master .df input file and determines where to write it: in each .df file, in a specific .df file, or in the default .df file. The following logic is used:
If a line contains a comment, the comment is included in all files
defined in the split schema definition file, plus the default .df output file.
If a line refers to a database table, it searches the split schema
definition file to see if the table is referenced there; if so, the program writes the line to the .df file associated with the table.
If a line does not refer to a table referenced in the split schema
definition file, the line is written only to the default .df output file.
95
Example Split Schema Definition File
An split schema definition file (extension .spl) might include these sections:
[Common] Description= Table=cah_hist [Dynamic] Description= Table=tr_hist Table=gl_hist [Service] Description=All tables from a specific module Table=bic_ctrl Table=cac_ctrl Table=caq_mstr Table=cas_mstr Table=ca_mstr Table=ccd_mstr [GL] Table=gl_mstr
The result of this example split schema definition file would be four .df files: common.df, dynamic.df, service.df, and gl.df.
Connect to a Database
This dialog is opened automatically when you choose the following Database menu commands:
Load Data from Directory Load DataFile into Existing Database Create Dump and Load Procedures Load Translated Labels All of these options require that you connect
to a database by completing the connection parameters and choosing OK

.
Physical Database Enter the physical database name of the database. For Name (-db) MFG/PRO on ORACLE, enter the PROGRESS schema holder name. Client/Server Network Connection To connect in a client/server environment using PROGRESS networking, choose this option and enter the host and service name.
Host Server Name Enter the name of the remote machine for this connection. (-H) Service Name(-S) Enter the service name to be used for this connection.
96
Local Host Connection Single-User Connection Database Path Additional (Startup) Parameters
For a local host connection (meaning the database is on the same machine as your PROGRESS session), select this option and complete the following fields. Select this option to connect to the database in single-user mode (-1 parameter). Turn off this option to connect in multiuser mode. Enter the directory path to the database or schema holder specified in the Physical Database Name field. You can enter any additional server startup parameters in this field. For example, to connect to an ORACLE database, you would need the following parameters: -ld YourSchemaHolder -RO -db ORACLEDbName -ld ORACLE_SID -dt ORACLE -U userid -P password NOTE: Append the user ID (-U) and password (-P) with "@<ORACLE_SID>" if you want to connect using SQL*Net.
Create Dump/Load Procs

Choose this option to create the dump/load procedures for the MFG/PRO database. Standard dump/load procedures come with MFG/PRO, but you may want to recreate them if you have made changes to the database schema.
Load Translated Labels

If you are compiling for a non-English language, you must load the translated schema labels into the empty MFG/PRO databases before compiling. When you choose this option, you must first complete the database connect window. Connect to one of the empty databases, such as mfgempty.db. After a connection is made, complete the following field with the path and name of the xdc_mstr table.
Update This Database File: MfgInstallDir\LanguageDir \xdc_mstr
97
Program Menu
Compile Procedure Files
Use this dialog box to select procedures based on file and directory names. You can perform a multi-tasking compile and choose the following options:
Compile an entire directory and build a list file. Compile from a list file. Resume compiling where a previous compile was interrupted. Monitor the number of files compiled and remaining. Review the number of files with errors. Log all errors. Save all database connections. Save the PROPATH used during compiles. Compile a single file or an entire directory. Include files based on whether a compiled file (.r-code) currently
exists in the database. At compile time, MFG/UTIL reads your database names and environment variables from the mfgutil.ini file. This information is stored in a temporary database while the programs are compiled. The logical database names and CRC values are compiled in the .r code. The compile PROPATH variable and other changes are written out to the mfgutil.ini file once the compile is complete.
Note Compiles must be run using a screen resolution of 800x600 or
lower.
Files in source directory Files listed in work file Source Directory Select this option to compile all source code in a given directory. Select this option to compile all source code listed in a work file. Specify the directory containing the source code you want to compile. Use the Choose... button to browse for a directory or file. The standard MFG/PRO source code directory is /src and the standard encrypted source directory is /xrc.
98
Save new .r-code
To run a test compile, leave the option to save new files unchecked. You can then view the results of the compile before actually saving the compiled programs.
Resume Previous Compile This check box is available only if a previous compile was interrupted. You can restart a compile that was canceled or aborted by the system, without starting at the beginning. MFG/UTIL reads the log file to determine where to resume the compile. Language If you are saving the .r code, specify or accept the default for your language code directory (for example, us is the directory for English). MFG/UTIL appends this directory to the end of the directory you specify in the Destination directory field, provided you choose the option: r-code to MFG/PRO default. If you are saving the .r code, choose this option to save the programs in the default directory structure. In the default structure, the programs are contained in two-letter subdirectories corresponding to the first two letters of the program name. If you are saving the .r code, choose this option to save the programs in a single, flat directory, as specified in the Desination directory field. If you run the compile and choose the save option, you can enter a destination directory in this field. If you leave this field blank, the compiled programs are saved in the same directory from where you selected them. The database sets you defined are displayed in this drop down list. You must choose one of these sets against which to compile your procedures. After using this feature the first time, the database set defaults to the last set used for a compile. The path name you enter here determines the PROGRESS version against which the selected files will be compiled.
r-code to MFG/PRO default
r-code to flat dest dir
Destination directory
Use this database set
Compile Propath
99
DataServer Menu
Generate Oracle Database Scripts
This option changes the settings in the SQL scripts, which you run to create the ORACLE database. You must answer various prompts, including the directory locations for control files, dump directories, system data files, logfiles, and more. This information affects the scripts:
crdb1<ORACLE_SID>.sql crdb1<ORACLE_SID>.sql init<ORACLE_SID>.ora config.<ORACLE_SID>
(where <ORACLE_SID> is your ORACLE system ID).
Change Oracle Connection Parameters

This option alters an existing schema holder to connect to a different ORACLE database.
Scripts Menu
Generate Server Startup and Shutdown
Select this option from the Scripts menu to generate server startup and shutdown scripts (in UNIX) or icons (in Windows NT). The start-up scripts or icons are based on the database sets you configured in the Database Set Configuration window. The program first prompts you to select a database set. To generate scripts, the program uses these parameters and one of the template scripts located in your MFG/UTIL directory.
100
Generate User Startup

Select this option from the Scripts menu to generate or regenerate user startup scripts (in UNIX) or icons (in Windows). The start-up scripts or icons are based on the database sets you configured in the Database Set Configuration window. Specify which database set you want. If the script or icon already exists for that database set, MFG/UTIL overwrites it, but warns you first.
Configure Menu
DLC and PROPATH Variables (Set MFG/PRO Paths)
Since MFG/UTIL uses various PROGRESS programs to complete the installation, you may need to specify the path name where PROGRESS is installed. Enter the root path name where the PROGRESS executable files are installed. Your changes update the initialization file mfgutil.ini; they do not affect the MFG/PRO start-up scripts or icons.
Company Information
The first time you use MFG/UTIL to set up your MFG/PRO system, this dialog box automatically appears and prompts you to enter the needed information. This information is for reference only. From the File menu, you can also print this company information along with company database names, path names, and other default information. To change existing company information, select this option from the Configure menu.
101
Any Database Set (Database Set Configuration)

The purpose of this window is to display the parameters and databases within the database set. You enter or modify the parameter information in related windows, which appear depending on the buttons you choose.
Select Database Set Edit Set, New Set In the top frame, you choose the database set you want to configure. Choose one of these buttons to access the parameters for a database set. The Database Set Parameters window opens; it contains overall parameters for all the databases within the set. In the bottom frame, you choose one of the databases within the database set. Choose one of these buttons to access the connection parameters related to starting an MFG/PRO client session. These buttons appear if you are configuring the database server start-up scripts or icons. Choose one of these buttons to access the connection parameters related to starting the database server.
Selected Set Overview Edit Client, New Client Edit Server, New Server
Database Set Parameters

This window controls overall parameters for the database set. It opens when you choose Edit Set or New Set from the Database Set Configuration window. The parameters you specify will be used to create startup scripts or icons.
Set Name Set Description Start Parms Accept the default. Enter a different description if you want. Defaults to the standard client start-up parameters, but can be changed as needed. The start-up parameters will be used by all clients that connect to this database set. When the database set is active (set to Yes), MFG/UTIL generates start-up scripts or icons for it as part of the installation. When the database set is not active (set to No), MFG/UTIL does not generate start-up scripts or icons for the database set.
Active
102
Client View of Database Parameters

This window contains the parameters that control how MFG/PRO client sessions will connect to the chosen database in the database set. It opens when you choose Edit Client or New Client from the Database Set Configuration window. The parameters you specify will be used to create start-up scripts or icons.
Physical (-db) Logical (-ld) Enter the physical database name of your database; accept the default if there is one. Enter the logical database name for the database; accept the default if there is one. For the main MFG/PRO database, always leave this field blank. Change the description if you want; it is for future reference. Enter any PROGRESS connection parameters you want that apply specifically to client connections to this database. To configure a database set for either a host mode or client/server connection, refer to the information below. For a Client/Server connection type, enter the name of the remote machine to which this client should connect at startup. This host name populates both the mfgutil.ini file and MFG/PRO parameter file. For a Client/Server connection type, enter the service name affiliated with the host. The name must correspond to an entry in your services files. (For the entries in your client service file, you must make the entries with a text editor; MFG/UTIL does not change this file.) For a Local connection type, enter the full path to the directory containing this database.
Description Connection Parms Connection Type Host
Service
Path
103
Server View of Database Parameters

The information you enter here configures the server startup. It opens when you choose Edit Server or New Server from the Database Set Configuration window. The parameters you specify will be used to create start-up scripts or icons.
Description Path Server Parms Enter a description of the database. You can accept the default description for one of the pre- defined databases or overwrite it. For a local host connection, simply enter the database path. Enter any additional server startup parameters in this field. The PROGRESS startup parameters help you manage memory and performance on the server. Also enter your network protocol parameters in this field.
Sections in mfgutil.ini
MFG/UTIL uses an initialization file, mfgutil.ini, to configure most of its operations. This allows you to review and modify the MFG/UTIL configuration and operation with any standard text editor. The mfgutil.ini file functions as the initialization file on both character and Windows platforms. The mfgutil.ini file follows the standard Windows convention and contains sections, line items, and comments. A section is a group of related information, with the section name enclosed in brackets (for example, [Compile]). The line item format is Item Name=Item Value (for example, SaveFiles=NO). Values can be text, numeric, logical, or one item from a list of choices. The logical values Yes and No are allowed. There is no case-sensitivity.
104
Summary of Sections
The following table lists the sections of the mfgutil.ini file and their description.
ClientSetup Compile DBSET General Various settings for running MFG/PRO for the current client. Controls the compile process. Stores the definition for a client database set. Contains general status information. For example, whether or not the current copy of MFG/UTIL is installed as part of a client or server release. Tracks which procedures the current client has already run. Stores information needed to install the Oracle database. Stores various paths used by MFG/UTIL. For example, a startup scripts PROPATH variable. Stores the definition for a server database set. Stores the current clients site information. For example, the company name and contact.
HasRun OracleValues Paths ServerSetup Site
ClientSetup Section (mfgutil.ini)

This section is populated by setup.exe at client setup time. These line items are used to build the mfgpro.pf file and program icons.
ClientAdminDirectory Client administration directory, where all the client r-code is stored. Refers to the original directory where the client CD was installed. The screen resolution chosen by this client for MFG/PRO. The home directory for this client when running MFG/PRO. In Microsoft Windows, this value is stored as the Working Directory for MFG/PRO. To view this value in Windows, highlight the MFG/PRO icon in Program Manager and select File- Properties. A logical value that determines whether the program prompts you to save the current clients configuration on the server as a default available to other clients.
ClientResolution ClientWorkingDirectory
FirstClient
105
Compile Section (mfgutil.ini)

This section describes the compile environment. Most settings are saved from the specifications entered from the previous compile. These settings are then the defaults used when you compile again.
DataBaseSet DestDir MultiTask The database set used with the previous compile. This will always show a database set defined in mfgutil.ini. The destination directory for any r-code files saved from the compile. The PROGRESS attribute, SESSION:MULTITASKING- INTERVAL, to use during the compile. This attribute determines how often PROGRESS internally filters events (messages) between itself and other Windows applications. The value stored in mfgutil.ini is set at the beginning of the compile and reset when the compile is finished. For more information on this attribute, refer to the PROGRESS on-line help. The PROPATH variable to use during the compile. A logical value set to YES to save r-code files to disk, or NO to perform syntax checking only. The directory where the source (.p, .w, .v) files reside. The name of the file which contains a list of files to compile.
ProPath SaveFiles SourceDir WorkFile
OracleValues Section (mfgutil.ini)

This section stores the values needed to install MFG/PRO with the Oracle DataServer.
OracleSID The Oracle environment variable that determines which instance you will access from PROGRESS. This is entered as the Database ID. The path to the Oracle database.
OracleHome
106
ServerSetup Section (mfgutil.ini)

This section stores the following information about your server setup, which is entered in the Database Set Configure window.
Description ServerHostName Path Service A text description of this database. The host name for this server. Equivalent to the PROGRESS -H parameter. The databases physical path. Used only for local host connections. The name given to the port for this database, also entered in the servers SERVICES file. (Clients will connect to this service name.) Equivalent to the PROGRESS -S parameter. The server startup parameters for this database set. The directory where your MFG/PRO installation files reside.
StartParms ServerAdmin Directory
DBSET Section (mfgutil.ini)

The DBSET or Database Set section has a slightly more complicated structure than other sections of mfguti.ini. The Section Name DBSET is always followed by a dash (-) and a database name. For example, DBSETPRODUCTION is a production database section name. Most items found in this section apply to only one database in the database set. The exceptions are SetDescription and SetParms, which apply to the database set. Any items that apply to only one database in a set are preceded by a database number prefix. This prefix is in the form DB-#, where # represents a number. The number corresponds to individual databases in the database set. For example, DB1- Physical=mfgempty shows that the physical name for database number 1 in this set is mfgempty.
107
A complete entry in this section might resemble this example:

[DBSET-Production] DB1-Physical=mfgdemo DB1-ConnectParms= DB1-Description=Main MFG/PRO Database DB1-Logical=qaddb DB1-ConnectionType=Local DB1-Host=cohs05 DB1-Service=jeffs-server DB2-Physical=mfghelp DB2-Description=Help Database DB2-Logical=qadhelp DB2-Host=cohs05 DB2-Service=old70-server StartParms=cpinternal ibm850 -cpcoll basic -p mf.p
The following table describes each database set entry.

ConnectionType Type of connection for this database. The legal values are Local or Client/Server. With Local, the Path value will be used to locate the database. With Client/Server, the Host and Service name will be used to make the database connection. Various connection parameters that can be entered by the user and are not covered in any other items within this section. A text description of this database. The server parameters for this database. The host (or server) name for a client/server connection. Equivalent to the PROGRESS -H parameter. The logical name for this database. Equivalent to the PROGRESS ld parameter. The databases physical path. Used only for local host connections. The physical name is appended on to the path when the connection command is issued. The physical file name for this connection. The name given to the port used for the connection. This value must be entered in a SERVICES file on the client and must match a value in the SERVICES file on the server. Equivalent to the PROGRESS S parameter. A text description for the entire database set. The startup parameters used when writing a client startup parameter file (.pf) using this database set. A logical value that determines whether this database set is active for a specific client.
ConnectParms Description ServerParms Host Logical Path
Physical Service
SetDescription StartParms Active
108
General Section (mfgutil.ini)

A general section to hold settings not applicable elsewhere.
ClientServer A logical value set to YES if this client uses client/server connections for its production environment. Set to NO if the client uses a host connection. Determines what type of process the system walks you through. Values are GUIClient, UnixServer, NTServer, or OracleDataServer. A logical value set to YES to run the programs in the background. Set to NO to display the processes in a DOS Window and monitor the associated messages and possible errors.
InstallType RunSilent
HasRun Section (mfgutil.ini)

This section tracks the tasks that have run in this copy of MFG/UTIL.
InitialSetup Determines whether the user has run the initial setup. If set to YES, MFG/UTIL will open at its Main Window. If set to NO, MFG/UTIL will display a Welcome screen and walk you through a client or server installation.
Paths Section (mfgutil.ini)

Stores the paths needed by MFG/UTIL to create scripts of find PROGRESS.
ScriptDLC CompileProPath InstallDir DefaultDatabasePath The DLC variable used when looking for PROGRESS or when generating scripts. The \xrc or \src directory used for compiling. The directory where MFG/PRO is installed. The directory where production databases are located.
109
Site Section (mfgutil.ini)

This section is populated by setup.exe at server setup time. These line items are used to build general information about a given site. This will be completed when setting up for server installations.
Company ContactName Location ContactPhone ContactFax ContactEmail The user-defined company name. The user-defined name of the technical support contact at this site. Might also be the name of the person performing the installation. Company site name. The user-defined phone number. The user-defined fax number. The user-defined email address.
110
CHAPTER 9
Modified Browse Program Names

The browse program names changed after MFG/PRO 8.3/8.4. Use this table if you need to know the current name; for example, you may need to update drill down records.
Version 8.3/8.4 Program Name abs1br.p abs2br.p abs3br.p abs4br.p acmbr.p adcnbrty.p adcobr.p adcsbr.p adcsbrbk.p adctbr.p adctbr01.p adctbry.p adcubrst.p addcbr.p addkbr.p addrbr.p adembr.p Current Program Name gpbr001.p gpbr002.p gpbr003.p gpbr004.p gpbr005.p gpbr006.p gpbr007.p adbr001.p adbr002.p adbr003.p adbr004.p gpbr008.p gpbr009.p gpbr010.p adbr005.p gpbr011.p adbr006.p Description Containers Browse Unallocated Containers Shippers Browse Shippers/Containers Average Cost Method Browse County Code Browse Company Address Master Customer Browse Customer/Supplier Banks Credit Term Browse Detail Credit Terms City Code Browse Address Master Customers Dock Codes Browse Dock Code Browse Address Master Browse Employee Master Browse
Modified Browse Program Names (1 of 19)
112
Version 8.3/8.4 Program Name adeubr.p adglbr.p adlsbr.p adnmbr.p adpsbr.p adrtbr.p adshbr.p adspbr.p adspbr01.p adstbr.p adsubrpp.p adtxbr.p adtybr.p advdbr.p allobr.p almbr.p altrbr02.p altrbro1.p ancdbr.p ancdbrl.p ancdbrt.p ancobrde.p ancubrst.p anpabrrt.p apbkbr.p appabr.p aprfbr.p apvobr.p apvobr2.p arbr.p arblbr.p
Current Program Name adbr007.p gpbr012.p adbr008.p gpbr013.p gpbr014.p adbr009.p gpbr015.p adbr010.p adbr011.p adbr012.p gpbr016.p adbr013.p gpbr017.p adbr014.p gpbr018.p gpbr019.p gpbr020.p gpbr021.p gpbr022.p gpbr023.p gpbr024.p gpbr025.p gpbr026.p gpbr027.p apbr001.p apbr002.p gpbr028.p gpbr029.p gpbr030.p gpbr031.p arbr001.p
Description End User Addresses Cust Ship-To Addresses Address List Browse Address Master (Name) Address Master (PO Ship) Supplier Remit-To Browse Ship-To Address Browse Salesperson Browse Salesperson Commissions Customer Ship-To Browse Address Master Suppliers U.S. Sales Tax Browse Address Master Browse Supplier Browse Allocation Master Auto Lot Master Browse Alternate Routings Alternate Routings Report Writer Analysis Codes Analysis Codes Browse Report Analysis Codes Browse Analysis Code Master Browse Analysis Code Master Browse Analysis Code Master Browse Bank Browse Payment Browse AP Master Browse Open AP Vouchers Open AP Vouchers AR Browse Customer Balances
MODIFIED BROWSE PROGRAM NAMES
113
Version 8.3/8.4 Program Name arbtbr.p arcsbr.p ardrbrm.p arglbr.p arivbr.p armbbr.p armpbr.p arsnbr.p asbr.p asnbr.p bcbr.p bmecbr.p bmmabr.p bombr.p bom1br.p bom2br.p bomabr.p btbr.p budcbrd.p cactbr.p cainbr.p cal2br.p callbr.p carsbr.p casbr.p casrbr.p cassbr.p casvbr.p catybr.p cctrbr.p cdrfbr.p
Current Program Name gpbr032.p gpbr033.p gpbr034.p gpbr035.p gpbr036.p gpbr037.p gpbr038.p gpbr039.p gpbr040.p gpbr041.p gpbr042.p bmbr001.p bmbr002.p gpbr043.p gpbr044.p gpbr045.p gpbr046.p gpbr047.p gpbr048.p gpbr049.p gpbr050.p gpbr051.p gpbr052.p gpbr053.p gpbr054.p gpbr055.p gpbr056.p gpbr057.p gpbr058.p gpbr059.p gpbr060.p
Description Unapplied Payments Open AR Browse Accounts Receivable AR GL Browse Invoices For Customers Receivables Browse AR Payments Browse Adjustment Reason Codes Asset Master Browse ASN Browse Batch Control Master ECO Browse Product Structure Browse Product Structures Formula Codes Browse BOM Codes Alternate BOM Browse Deduction Base Types Budget Codes Browse Call Categories Browse Call Work Codes Browse Open Calls Browse Open Call Browse Resolution Code Browse Call Status (Type C) Problem/Skills Browse Call Status (Type S) Severity Codes Browse Call Types Browse GL Cost Center Master Master Comments Browse
114
Version 8.3/8.4 Program Name chmbr.p citybr.p ckbtbr.p ckdtbr.p clatbr.p clbabr.p clctbrc.p clctbrs.p clltbr.p clsbr.p cmcfbr.p cmstbr.p cmtybr.p cntybr.p codebr.p colgbrp.p combr.p cpbr.p csbr.p csabr.p csbabrnk.p csbkbr1.p cscbr.p cscabrth.p csctbrrl.p cscubrst.p csplbr.p cssabrth.p cssibr01.p cssibr02.p cssibrte.p
Current Program Name fsbr001.p gpbr062.p gpbr063.p apbr003.p clbr001.p clbr002.p clbr003.p clbr004.p clbr005.p fabr001.p cmbr001.p gpbr069.p gpbr070.p gpbr071.p gpbr072.p gpbr073.p txbr003.p gpbr075.p csbr001.p gpbr076.p gpbr077.p gpbr078.p gpbr079.p gpbr080.p gpbr081.p gpbr082.p csbr002.p gpbr083.p csbr003.p csbr004.p gpbr084.p
Description Service Call History Tax Master Browse AP ChecksBatch Browse Check Detail Browse Work Order Attribute Browse Work Order Batch Browse Controlled Customer Browse Controlled Site Browse Lot Master Browse Class Codes Browse Cash FlowMisc Browse CustomersSort Name CustomersType Browse Tax Master by County Code Master Browse Column Group Browse Commodity Code Browse Customer Items Browse Cost Set Master Browse Authority Master Browse Bank Addresses Browse Bank Addresses by Name Controlled Sub Cust Mstr Browse Controlling Authority Browse Item Control Numbers Browse Controlled Customer Num Browse Cost Plan by Site Browse Controlling Authority Browse Site by Cost Set Browse Cost Set by Site Browse Controlled Sites Browse
115
Version 8.3/8.4 Program Name cssmbr.p cssnbr.p csstbr.p cstbr.p cstdbr.p ctrybr.p ctrybr1.p cueubr.p dedbr.p desdbr.p desdbrm.p devtbr.p dmbr.p dm1br.p dnftbr.p dnssbr.p dnssbr02.p dntmbr.p drdobr11.p drllbr.p drmpbr02.p drsnbr.p dsclbrst.p dsddbr.p dsdmbr.p dsdmbr01.p dsdmbr03.p dsdobr.p earnbr.p ecapbrcd.p ecapbrdt.p
Current Program Name gpbr085.p gpbr086.p gpbr087.p gpbr088.p gpbr089.p gpbr090.p adbr015.p gpbr091.p gpbr092.p txbr004.p gpbr094.p txbr005.p gpbr096.p gpbr097.p dnbr001.p dnbr002.p dnbr003.p dnbr004.p drbr001.p mgbr001.p drbr002.p gpbr098.p gpbr099.p drbr003.p dsbr001.p dsbr002.p dsbr003.p dsbr004.p gpbr100.p gpbr101.p gpbr102.p
Description Cost Set Master Browse Cost Set Master Browse Customer/Ship-To Browse Custodian Codes Browse Address Master Browse Country Code Browse Country Codes Browse End User Filtered Browse Deduction Master Browse Port Browse Intersite Demand Request Delivery Terms Browse AR Drafts Browse AR Unapproved Drafts Freight Rate Tables Network Code Browse Transportation Networks Transportation Modes Planned Intersite Reqs Drill Master Browse Order Action Messages Down Time Reason Codes Discount Tables Browse DRP Requistion Detail Intersite Request Browse Intersite Demand Browse Orders In Transit Browse Distribution Orders Earnings Master Browse Approval Codes Browse ECN Approval Detail
116
Version 8.3/8.4 Program Name ecapbrst.p ecapbrtd.p eccobrde.p ecdrbref.p ecgrbr10.p ecgrbr20.p ecgrbr30.p ecgrbrp.p ecgrbrp1.p ecgrbrp2.p ecmbr.p ecm0br1.p ecm0br3.p ecm0br4.p ecm0br5.p ecrebrv.p ectybrpe.p ecusbrr.p ecusbrr1.p elmtbr.p elmtbr1.p empbr.p empsbr.p engbr.p engcbr.p esbr.p eshbr.p essbr.p eubr.p eud2br.p eudtbr.p
Current Program Name ecbr001.p ecbr002.p ecbr003.p gpbr103.p ecbr004.p ecbr005.p ecbr006.p gpbr104.p gpbr105.p gpbr106.p gpbr107.p gpbr108.p gpbr109.p gpbr110.p gpbr111.p ecbr007.p ecbr008.p gpbr112.p gpbr113.p gpbr114.p gpbr115.p gpbr116.p gpbr117.p gpbr118.p gpbr119.p gpbr120.p gpbr121.p gpbr122.p gpbr123.p gpbr124.p gpbr125.p
Description ECN Status Browse ECN Detail Approval ECN Approval Code Browse ECN Text Comments Distribution Groups Approval Group Browse Design Group Browse ECN Type Master ECL Groups (All Types) Design Groups Browse ECM Master Browse ECN Master Browse ECN Master Browse ECN Master Browse ECN Master Browse Item Revision History ECN Type Master Browse User Master Browse Approval Group Browse Cost Element by Category Cost Elements by Element Employee Master Browse Employee Master Browse Engineer Master Browse Engineer Code Browse Escalation Browse Schedule Master Browse Work Schedule Browse End User Browse End Users Contacts (Name) End User Detail Browse
117
Version 8.3/8.4 Program Name exbr.p facobr.p facubr.p fadbbr01.p falobr.p famebr.p famxbr.p famxbr01.p fatybr.p fatybr01.p fcfcbr.p fcrfbr.p ffcmbrrg.p ffgrbrp.p ffidbr.p fflobrad.p ffmtbrhd.p fftybrpe.p flcbbr.p fmmabr.p fosobrb.p fosqbrb.p frclbr.p frlsbr.p frtmbr.p frzbr.p fsbobrm.p fsbobrm1.p fscqbr.p fscsbr.p fsesbr.p
Current Program Name gpbr126.p fabr002.p fabr003.p fabr004.p fabr005.p fabr006.p fabr007.p fabr008.p gpbr127.p fabr009.p fcbr001.p gpbr128.p gpbr129.p gpbr130.p gpbr131.p gpbr132.p gpbr133.p gpbr134.p mgbr002.p fmbr001.p fobr001.p fobr002.p sobr001.p sobr002.p sobr003.p gpbr135.p fsbr002.p gpbr136.p fsbr003.p fsbr004.p fsbr005.p
Description Currency Exchange Browse Convention Browse FA Custodian Browse Book Browse FA Location Browse Depreciation Methods Maximum Amount Browse Maximum Amt Table Browse Type Codes Browse Fixed Asset Type Browse Seasonal Build Browse Forecast Reference Customer Regions Browse Item Group Browse Forecast Master Browse Loading Method Browse Forecast Method Browse Item Type Browse Field Combo-Box Browse Formula Code Browse Sales Order Bill Browse Sales Quote Bill Browse Freight Class Codes Freight Terms Master Freight Terms Types Freight Zones Browse Repair/PM BOM Codes Bills of Material Browse Call Queue Code Browse Call Status Code Browse Call Escalation Browse
118
Version 8.3/8.4 Program Name fsfsbrhe.p fshabr.p fsmnbrp.p fsmnbrpv.p fsocbrm.p fsopbrm.p fspgbrh.p fsptbr.p fsrmbra.p fsrobr.p fssabr.p fsscbra.p fssrbr.p fssrbrs.p fssvbrar.p fssvbrs.p fssvbrw.p fswcbr.p glacbr.p glbgbr.p glcabr.p glccbr.p glccbr01.p glcrbr.p glcrbr1.p glcrbr2.p glcrbrd.p glenbr.p glfmbr.p glpjbr.p glsbbr.p
Current Program Name fsbr006.p fsbr007.p fsbr008.p fsbr009.p fsbr010.p fsbr011.p fsbr012.p fsbr013.p fsbr014.p fsbr015.p fsbr016.p fsbr017.p fsbr018.p fsbr019.p fsbr020.p fsbr021.p fsbr022.p fsbr023.p glbr001.p glbr002.p glbr003.p glbr004.p glbr005.p glbr006.p glbr007.p glbr008.p glbr009.p glbr010.p glbr011.p glbr012.p glbr013.p
Description Holiday Coverage Browse Area Service Holidays Custom Program Insertion Custom Program Entries On-Call Schedule Browse Repair/PM Standard Oper Paging Browse Service Item Browse RMA Browse Repair/PM Routing Browse Service Contract Browse Service Type Browse Service Request Browse Serv Req Status Codes Area Structure Browse Service Contract Browse Warranty Code Browse Repair/PM Work Centers Account Code Browse Budget Browse GL Calendar Browse Cost Center Code Browse Cost Center Code Detail Custom Report Browse Custom Report Fmt Browse Custom Report Accounts Custom Report Accounts Entity Code Browse Format Position Browse Project Code Browse Sub-Acct Code Browse
119
Version 8.3/8.4 Program Name glsbbr01.p grrpbrid.p grrpbrt.p iclobr.p iclobr01.p iclobr02.p iclobr03.p icltbr.p icmabr.p icptbr01.p icsibr.p icstbr.p icstbr01.p ictrbr01.p ictrbr02.p iecobrm.p iecobrm2.p ieflbrow.p iemobrt.p ienobrt.p iepobrrt.p ierebrg.p iespbr.p ietobrd.p ihbr.p ihadbr.p ipdbr.p isb1br.p isb6br.p isbpbrt.p isbpbrt3.p
Current Program Name glbr014.p gpbr137.p gpbr138.p icbr001.p icbr002.p icbr003.p icbr004.p icbr005.p icbr006.p icbr007.p icbr008.p icbr009.p icbr010.p icbr011.p icbr012.p gpbr139.p iebr001.p iebr002.p iebr003.p iebr004.p iebr005.p iebr006.p iebr007.p iebr008.p gpbr148.p gpbr149.p gpbr150.p gpbr151.p gpbr152.p gpbr153.p gpbr154.p
Description Sub-Acct Valid Accounts Report Run IDs Browse Report Codes Browse Location Master Browse Inventory Master Browse Inventory Detail Browse Site Inventory Detail Lot Transactions Browse Mirror Table Browse Stock Available Browse Site Browse Inventory Status Codes Inventory Status Detail Inventory Trans Browse Lot Transactions by Tran Commodity Master Browse Commodity Code Browse Flow Indicator Browse Mode of Transportation Browse Nature of Transportation Browse Ports Browse Regions Browse Statistical Procedures Browse Terms of Delivery Browse Invoice History Master Invoice History Browse Test Results Detail Installed Base Parts Installed Base Parts Installed Base Items Installed Base Items
120
Version 8.3/8.4 Program Name isbpbrt7.p ladbr.p langbr.p ldbr.p lda1br.p lda3br.p ldavbrl2.p ldo3br.p ldohbr.p lnbr.p lnddbr.p lngdbr.p locbr.p loc1br.p lotbr.p mcexbr.p mdtrbr.p mgbrbr01.p mgcobr.p mgfhbr.p mgmsbr.p mgrnbr.p mgufbr.p mgupbr.p mgurbr.p mgutbr.p mgvubr.p mncrbr.p mnpvbr.p
Current Program Name gpbr155.p gpbr156.p gpbr157.p gpbr158.p gpbr159.p gpbr160.p gpbr161.p gpbr162.p gpbr163.p gpbr164.p gpbr165.p gpbr166.p gpbr167.p gpbr168.p gpbr169.p gpbr170.p mcbr001.p txbr006.p mgbr003.p mgbr004.p mgbr005.p mgbr006.p mgbr007.p mgbr008.p mgbr009.p mgbr010.p mgbr011.p mgbr012.p gpbr172.p mgbr013.p gpbr173.p
Description Installed Base Items Installed Base Parts Location Allocation Num. Language Master Browse Item Lot/Serial Qty O/H Available to Allocate Available to Allocate Avail to Detail Allocate Item Location Detail O/H Item Location Qty O/H Line Master Browse Line Schedule Detail Cost Category Language Location Master Browse Location Master Item Lot/Serial Browse Exchange Rate Browse Transportation Modes Browse Master Browse Generalized Codes Browse Window Help Browse Message Browse Reason Codes Browse User Function Browse Printer Default Browse User Browse User Tool Browse View Detail Browse Insertion Descriptions Menu Substitution Browse Custom Program Exits
121
Version 8.3/8.4 Program Name mntdbr.p mpbr.p mpcabr.p mpmpbr.p mpmpbr01.p mpmpbr02.p mrpbr.p mrwobr11.p msmsbr02.p natrbr.p ntwkbr.p oacdbr.p opmtbr.p opnibrnv.p pc2br.p pilibrst.p pimabrn.p pobr.p poacbr.p poacbr01.p poblbr.p pocrbr.p polnbr.p popobr01.p popobr02.p popqbr.p poprbr.p porqbr.p poscbr.p postbrby.p potrbr01.p
Current Program Name mgbr014.p gpbr174.p mpbr001.p mpbr002.p mpbr003.p mpbr004.p gpbr175.p mrbr001.p msbr001.p txbr007.p gpbr177.p gpbr178.p gpbr179.p gpbr180.p gpbr181.p gpbr182.p gpbr183.p gpbr184.p pobr001.p pobr002.p pobr003.p gpbr185.p gpbr186.p pobr004.p pobr005.p pobr006.p pobr007.p gpbr187.p gpbr188.p gpbr189.p pobr008.p
Description Menu Translation Browse Master Specifications Test Results Browse Master Spec Detail Where UsedSpecs Item Specifications Order Browse Planned Order Browse Master Schedule Orders Nature of Transaction Network Master Action Codes Browse Standard Operation Tools Open Invoices Browse Price List Browse Price List Master Price List Master Purchase Order Master Purchase Approvals Purchase Approval Limits Blanket Order Browse PO Ship-Via Carriers Purchase Order Detail Receipt Transactions Purchase Receipt Browse Purchase Order Browse Purchase Reqs Browse Purchase Order Master Scheduled Purchase Order Sort by Browse Receipt Transactions
122
Version 8.3/8.4 Program Name ppcpbr.p ppcsbr.p pppcbr.p pppcbra.p pppcbrb.p ppplbr.p ppplbr01.p ppplbr02.p ppplbr03.p ppplbr04.p ppplbrd.p ppplbrs.p ppptbr.p ppptbr01.p ppptbr02.p ppptbr03.p ppptbr05.p ppptbr11.p ppptbr12.p ppstbr.p ppumbr.p ppvpbr.p prbr.p prbnbr.p prbtbr.p prckbrrq.p prclbrst.p prdbr.p prdebrd.p prdpbrt.p preabr.p
Current Program Name ppbr001.p ppbr002.p ppbr003.p ppbr004.p ppbr005.p ppbr006.p ppbr007.p ppbr008.p ppbr009.p ppbr010.p ppbr011.p ppbr012.p ppbr013.p ppbr014.p ppbr015.p ppbr016.p ppbr017.p ppbr018.p ppbr019.p ppbr020.p ppbr021.p ppbr022.p gpbr307.p gpbr302.p prbr001.p prbr002.p gpbr190.p gpbr191.p prbr003.p prbr004.p prbr005.p
Description Customer Item Browse Item Cost Set Browse Price List Browse Price List Min Qty 610 Price List Min Qty 1115 Product Line Browse Product Line Inv Browse Product Line Sale Browse Product Line Purc Browse Product Line WO Browse PL Inventory Detail PL Sales Detail Browse Item Master Data Browse Item Inventory Data Browse Item Planning Browse Item Cur Cost Summary Cost Element Browse Item Site Inv Browse Item Site Plan Browse Item St Code Browse Unit of Measure Browse Supplier Item Browse Printer Master Browse Payroll Bank Browse Deduction Base Types Paycheck Request Browse Price Tables (Type L) Printer Detail Browse Other Deductions Browse Department Detail Browse Earnings Code Browse
123
Version 8.3/8.4 Program Name predbr.p prffbr.p prhrbr.p prhsbr.p probbr.p prshbrft.p prstbr.p psbr.p ps1br.p ptdebrsc.p ptpdbr.p ptstbr.p pttybr.p pwcdbr.p pwcmbr.p qcbr.p qcdobrc.p qcprbroc.p qcrobrut.p qcspbr.p qctebrs.p qctsbr.p qcwcbrtr.p qcwobr.p qobr.p qocrbr.p qoshbr.p qpsbr.p rbd2br.p rbmbr.p
Current Program Name prbr006.p prbr007.p gpbr192.p gpbr193.p gpbr194.p prbr008.p prbr009.p gpbr195.p gpbr196.p gpbr197.p ptbr001.p gpbr198.p ptbr002.p gpbr199.p mgbr015.p mgbr016.p gpbr200.p gpbr201.p gpbr202.p gpbr203.p qcbr001.p gpbr204.p qcbr003.p gpbr205.p qcbr004.p gpbr206.p gpbr207.p gpbr208.p gpbr209.p gpbr210.p gpbr211.p
Description Deductions Browse FICA/FUTA/Medicare Brws Receivers Browse Packing Slips Browse Problem/Skills Browse Shift Differential Brows State W/H, SUI, SDI Product Structure Master Product Structure Master Item Descriptions Browse Item Planning Detail Item Status Master Item Substitution Browse Item Master Browse Program Window Detail Pgm Window Config Master Quality Order Browse Documents Available Procedures Browse Routing/Procedure Browse Sampling Pattern Browse Procedure Test Steps Procedure Browse Work Center & Machine Quality Order Browse Sales Quote Master Quote Ship-Via Carriers Quote Master Browse Inspection Components Invoice History Browse Retrobill Master Browse
124
Version 8.3/8.4 Program Name rcccbr.p rcccbr1.p rcccbr2.p rccpbrc.p rcsdbr.p rcsobr.p rechbr.p regbr.p relnbr.p relnbr01.p repkbr.p resbr.p resqbr.p rewobr.p rmdbr.p rmdrbr.p rmihbr.p rndbr.p robr.p roabr.p rowgbrp.p rppqbr.p rprrbr.p rprsbr.p rrsnbr.p rscbr.p rsnbr.p rspobr01.p rspobr02.p rspobr03.p rspobr04.p
Current Program Name rcbr001.p rcbr002.p rcbr003.p rcbr004.p gpbr212.p gpbr213.p rebr001.p fsbr024.p rebr002.p rebr003.p gpbr214.p gpbr215.p rebr004.p rebr005.p gpbr216.p gpbr217.p gpbr218.p gpbr219.p gpbr220.p gpbr221.p gpbr222.p rpbr001.p rpbr002.p rpbr003.p gpbr223.p gpbr224.p gpbr225.p rsbr001.p rsbr002.p rsbr003.p rsbr004.p
Description Customer Calendar Browse Operating Hrs Exceptions Shop Calendar Holidays Customer Order Periods Ship/Delivery Patterns Scheduled Sales Orders Line Changeover Browse Region/Area Browse Production Line Browse Production Line Detail Repetitive Pick List Resource Master Line Schedule Browse Cumulative Order Browse Open RMA Lines Browse RMA Receipt Lines Browse Shipped Items Browse Rounding Method Codes Routing Detail Browse Alternate Routings Row Group Browse PL Resource Bill Browse Item Resource Bills Resource Detail Browse Reject Reason Codes Reason Code Browse Reason Code Browse Scheduled Order Browse Sched OrderLine Items Sched OrdLine Items(2) Sched Order MRP % Browse
125
Version 8.3/8.4 Program Name rsscbr.p rsscbr01.p rsscbr02.p rsscbrx1.p rtsbr.p rwarbr.p rwdpbr.p rwopbr.p rwrobr04.p rwwcbr.p rwwrbr.p sabsbr1.p sabsbr2.p sabsbr3.p sabsbr4.p sapbr.p saqobr.p sasabr.p sasabr03.p sasabr04.p sasabr05.p sasabr5a.p satrbr03.p satrbr05.p sbcbr.p sc03br.p sc04br.p scabr.p sccebr.p sccebr01.p scx2br.p
Current Program Name rsbr005.p rsbr006.p mgbr017.p gpbr226.p gpbr227.p rwbr001.p prbr010.p rwbr002.p rwbr003.p rwbr004.p rwbr005.p gpbr228.p gpbr229.p gpbr230.p gpbr231.p gpbr232.p gpbr233.p gpbr234.p sabr001.p sabr002.p sabr003.p sabr004.p sabr005.p sabr006.p gpbr235.p scbr001.p scbr002.p gpbr236.p scbr003.p scbr004.p gpbr237.p
Description Supplier Calendar Browse Supplier Cal Detail Holiday Browse Scheduled Order Items Return to Supplier Order Alternate Routing Browse Department Browse Standard Oper Browse Operation Cost Browse Work Center Browse Work Center/Routing Stds Containers Browse Unallocated Containers Shippers Browse Shippers/Containers Contract PM Sched Dates Service Quotes Browse Service Contracts Browse Customer Sales Browse Items Sales Browse Salesperson Sales Browse Slsprsn Monthly Browse Customer Tran Det Browse Slspsn Trans Det Browse Service Billing Cycles Simul Work Center Rates Simul Subcontract Costs Contract Options Browse Simulation Cost Elements Cost Element Browse Scheduled Order Item POs
126
Version 8.3/8.4 Program Name sfopbr11.p shmbr.p sobr.p socrbr.p sodlbr.p sofcbr.p sofzbr.p soivbr.p solnbr.p sopobr.p soqobr.p sosdbr.p soshbr.p sosobr.p sotlbr.p sotrbr03.p sotrbr04.p sotrbr05.p sotrbr4a.p spbr.p spambr.p spedbri.p sphhbr.p sphsbr01.p sppsbr.p spsbr.p spsmbr.p sptrbr.p sqqobr.p srbr.p srobr.p
Current Program Name sfbr001.p gpbr238.p gpbr239.p sobr004.p gpbr240.p sobr005.p sobr006.p sobr007.p gpbr241.p gpbr242.p gpbr243.p sobr008.p gpbr244.p sobr009.p sobr010.p sobr011.p sobr012.p sobr013.p sobr014.p gpbr245.p spbr001.p spbr002.p mgbr018.p spbr003.p spbr004.p gpbr246.p spbr005.p gpbr247.p sqbr001.p gpbr248.p gpbr249.p
Description Operation Trans Browse Transportation Network Sales Order Master Sales Order Credits Sales Order Line Items Freight Charges Browse Freight Zone Browse Invoice History Browse S/O Detail Browse Sales Order Master (PO) Sales Order Quote Browse Volume Discount Browse Sales Order Ship-Tos Sales Order Browse Trailer Code Browse Booking Trans Browse Shipment Trans Browse Sales Order Trans Browse Shipment GL Trans Browse Salesperson Master Alternate Matrix Browse Marketing/Product Data Salesperson Quota Browse Salesperson History Family Resource Bill Salesperson Master Source Matrix Browse Salesperson Territories Sales Quote Browse SR Master Browse Customer Service System
127
Version 8.3/8.4 Program Name sro1br.p sro2br.p sro3br.p sro4br.p sro5br.p sro6br.p sro7br.p sro8br.p srotbr.p srsnbr.p srsvbr.p srtybr.p stbr.p statbre.p stprbr.p stprbrsw.p svbr.p svddbr.p svsbr.p svwbr.p sx2br.p taxcbra.p taxsbrt.p tmbr.p trlbr.p trlpbr.p trnbbr.p tx2br.p txbbr.p txebr.p txmebrth.p
Current Program Name srbr001.p srbr002.p srbr003.p srbr004.p srbr005.p srbr006.p srbr007.p srbr008.p gpbr250.p gpbr251.p gpbr252.p gpbr253.p gpbr254.p gpbr255.p prbr011.p gpbr256.p gpbr257.p gpbr258.p gpbr259.p gpbr260.p gpbr261.p txbr008.p gpbr263.p gpbr264.p gpbr265.p gpbr266.p gpbr267.p gpbr268.p gpbr269.p txbr009.p gpbr271.p
Description SRO Status Browse SRO Failure Browse SRO Assigned Browse SRO Date Browse SRO Item Browse SRO Type Browse SRO Dispositions Browse SRO Customer Browse Customer Service Browse Scrap Reason Codes Severity Codes Browse Call Types Browse State Code Browse State Codes Browse State Taxes Browse Statistical Procedures Contract/Warranty Types Service Contract Detail Service Contract Types Service Warranty Types Scheduled Order Item POs Tax Class Codes Browse Tax Master States Transportation Master Trailer Codes Browse Trailer Project Browse Transaction Numbers Tax Codes/Tax Types Tax Base Codes Browse Tax Environment Codes Tax Method Codes Browse
128
Version 8.3/8.4 Program Name txptbrv.p txtbr.p txubr.p txzbr.p txz1br.p umstbrr1.p unitbr.p uom2br.p updbr.p utfibrl.p utflbrd.p vdapbr.p vdpubr.p vdsbr.p vobtbr.p voenbr.p voivbr.p vopjbr.p vorfbr.p voshbr.p vpbr.p vpmpbr.p vpmrbr.p vpvdbr.p vtbr.p vtesbr.p vtevbr.p wcbr.p wcmcbrh.p wkbr.p wkcbr.p
Current Program Name txbr001.p txbr010.p txbr011.p txbr012.p gpbr275.p gpbr276.p gpbr277.p gpbr278.p gpbr279.p utbr001.p utbr002.p gpbr280.p gpbr281.p gpbr282.p gpbr283.p gpbr284.p gpbr285.p gpbr286.p gpbr287.p gpbr288.p gpbr289.p gpbr290.p gpbr291.p gpbr292.p ctbr001.p gpbr293.p gpbr294.p gpbr295.p gpbr296.p prbr012.p prbr013.p
Description Item Statistical Value Tax Type Codes Tax Usage Codes Tax Zones Browse Tax Zone Descriptions Unit of Measure Browse Reporting Unit Codes Alternate UOM Browse Menu Browse Database File Browse Database Field Browse Supplier Master Contacts Supplier Master Contacts Supplier Master Browse Vouchers by A/P Batch Voucher Detail Browse Voucher MasterInvoice Voucher Detail Browse Voucher Master Browse Voucher Ship-To Browse Supplier Item Master Supplier Item Browse Supplier Item Master Supplier Item Master VAT/GST Class Master Ship-To Address Browse Supplier Master Browse Work Centers by Machine Work Center Master Work Location Browse Worker's Compensation
129
Version 8.3/8.4 Program Name wobr.p wodbr.p woltbr.p woopbr.p wopbr.p wosobr.p wowabr.p wowobr.p wrbr.p wr2br.p wrltbr.p wrsnbr.p zpbr.p
Current Program Name gpbr297.p gpbr298.p gpbr299.p wobr001.p gpbr300.p gpbr301.p wobr002.p wobr003.p gpbr308.p gpbr303.p gpbr304.p gpbr305.p gpbr306.p
Description Work Order Master Work Order Operation BOM Work Order Master Work Order Routings Work Order Projects Work Order Master Work Order Bill Browse Work Order Browse Work Order Routings Work Order Routings Work Order Routings Rework Reason Codes Zip Code Browse
130
Index
A Actuate defined 88 administration tasks 6 after-image backup 16, 17 parameter 31 after-image writers 34 asynchronous page writers 34 AT command 84 B backup overview 16 validation 18 batch .ini file 76 .pf file 77 batch.r program 75 batchin.inp file 75 ID 79 process 74 program 75 progress.bch file 76 scheduling in MFG/PRO 81 scheduling in Windows NT 82 before-image backup 16 extents 49 overview 8 relocation of file 33 before-image writers 34 block size for extents 48 bulk load overview 22 performing 26 rebuilding indexes 27 bulk load description file 25 C cfempty database 11 cfg database 12 compiled code 10 compiling code 68 custom side database 14 D database file extensions 9 fragmentation 19 overview 8 database sets 64 delete/archive and fragmentation 19 description file for bulk load 25 dump through MFG/PRO 23 through PROGRESS 24 dump/load overview 20 reasons 21 E empty databases 11 encrypted code 10 extents adding 53 before-image 49 defined 45 sizing 47 F fragmented database 19 full backup 17 G gui database 12 guiempty database 11
132
H hardware sizing 2 hlpempty database 11 Hotbatch 79 I incremental backup 17 index rebuild 27 initialization file for MFG/UTIL 103 input control file 75 L load bulk loading 26 creating bulk load description file 25 for multi-volume database 52 index rebuild 27 through Data Dictionary 27 M manager functions 2 mfg database 12 MFG/UTIL compile 68, 97 Configure menu 100 database menu 92 database sets 64, 101, 106 DataServer menu 99 initialization file 103 Program menu 97 Scripts menu 99 mfgempty and dump/load 25 mfgempty database 11 mfgutil.ini file 103 MRP batch ID 79 multi-volume advantages 45 components 45 overview 44 void database 51 workflow 46 O object code, defined 10 off-line backup 17 on-line backup 17 P parameters
effect on performance 30 list 31 overview 7 probkup utility 17 procopy utility 52 PROGRESS monitor 36 progress.ini file 76 promon utility 36 prorest utility 17 prostrct command 51 proutil bulk load 26 index rebuild 27 Prowin32 batch client 74 R RESULTS defined 88 starting from MFG/PRO 88 S sequences initialization after dump/load 28 overview 13 side database 14 source code, compile 68 source code, defined 10 split schema administration 62 determining splits 57 reasons 56 requirements 59 steps 60 Splitting MFG/PRO Schema 55 start-up scripts and icons 64 striping 44 structure description file creating 47 defined 45 example 49 V version number MFG/PRO 10 PROGRESS 6 void database 51 W watchdog 35

MFGPRO SysAdminReferenceGuide ProgressDatabase WindowsNTServer IG v09

Uploaded by

Copyright:

Available Formats

MFGPRO SysAdminReferenceGuide ProgressDatabase WindowsNTServer IG v09

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MFGPRO SysAdminReferenceGuide ProgressDatabase WindowsNTServer IG v09

Uploaded by

Copyright:

Available Formats

What are some of the main tasks of a system administrator?

What are some of the main tasks of a system administrator?

What are the basics of the PROGRESS database architecture?

What are the basics of the PROGRESS database architecture?

System Administration Reference Guide

PROGRESS DATABASE ON WINDOWS NT SERVER

78-0460A MFG/PRO Version 9.0 Printed in the U.S.A. March 1999

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

SPLIT SCHEMA DATABASE . . . . . . . . . . . . . . . . . . . . . . . . . . 55

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

Creating a Split Schema Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Administering the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

USING PROGRESS RESULTS WITH MFG/PRO . . . . . . . . 87

MFG/UTIL REFERENCE INFORMATION . . . . . . . . . . . . . . . . . 91

MODIFIED BROWSE PROGRAM NAMES . . . . . . . . . . . . . . . . 111

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

Using This Guide

MFG/PRO Manager Functions Information

Configuration and Sizing Information

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

System Administration Tasks

System Administration Tasks

PROGRESS Version Number

MFG/PRO release, refer to the MFG/PRO Installation Guide .

When you use parameters, keep in mind the following tips.

startup or database connection.

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

PROGRESS Database Architecture

tables, such as address.

Related Database Files

to be dumped from or loaded into a database.

such as startup, shutdown, and errors.

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

MFG/PRO Version Number

MFG/PRO Compiled and Source Code

mfgempty hlpempty guiempty cfempty

Empty Database: mfgempty +

Data Directory: /qad/mfg/*.d

Built Database: mfg

Empty and Built Databases

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

Main MFG/PRO Databases

Main MFG/PRO Databases

Database Name mfg YourProductionDB mfgdemo mfgtrain

Help, User Interface (GUI), and Configurator Databases

Help, User Interface, and Configurator Databases

Database Name mfghelp gui cfg

Related Application Item:

The cfg, gui, and mfghelp Databases

cfg: (object components)

Multiple and Custom Databases

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

Delete/Archive and Database Fragmentation Dump and Load 20 23

Dumping Through MFG/PRO

Bulk Load: Rebuilding the Indexes

Loading Through Progress Data Dictionary Post Dump/Load Sequence Initialization 28

MFG/PRO SYSTEM ADMINISTRATION REFERENCEPROGRESS ON WINDOWS NT

Large Scale Data Movements

Types of Data Movement

727$/ URRW VMWUDLQ