pm˜ F„¤Fm›˜ —z›¨˜ m'›"dd"›apm˜%˜ pmOaV - Public Support Login ...

LINC on Sequent) 

DYNIX/ptx) 

Installation and Configuration 

Guide 

July 1998 

v

!()+ 

LINC on Sequent) 

DYNIX/ptx) 

Installation and Configuration 

Guide 

Copyright ( 1998 Unisys Corporation. 

All rights reserved. 

Unisys is a registered trademark of Unisys Corporation. 

LINC is a registered trademark of Unisys Corporation. 

Griffin is a trademark of Unisys Corporation. 

Sequent is a registered trademark of Sequent Computer Systems Inc. 

DYNIX/ptx is a registered trademark of Sequent Computer Systems Inc. 

Release 16.3 July 1998 

v

The names, places, and/or events used in this publication are not intended to correspond to any 

individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, 

places, and/or events with the names of any individual living or otherwise is purely coincidental and 

unintentional. 

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product and related 

material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly 

executed Program Product License or Agreement to Purchase or Lease Equipment. The only warranties 

made by Unisys, if any, with respect to the products described in this document are set forth in such 

License or Agreement. Unisys cannot accept any financial or other responsibilities that may be the 

result of your use of this information or software material, including direct, indirect, special or 

consequential changes. 

You should be very careful to ensure that the use of this information and/or software material complies 

with the laws, rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise 

of such changes and/or additions. 

RESTRICTED. Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 

252.227-7013 and FAR 52.227-14 for commercial computer software. 

TRADEMARKS. All other terms mentioned in this book that are known to be trademarks or service marks 

have been appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this 

information. Use of a term in this book should not be regarded as affecting the validity of any trademark 

or service mark. 

Correspondence regarding this publication should be forwarded using the Business Reply Mail form at 

the back of this document to:Australian Centre for Unisys Software, 115 Wicks Road, North Ryde NSW 

2113, AUSTRALIA. Alternatively you can send an E-Mail message to: linc.pi@unisys.com 

MicroFocus is a registered trademarks of MicroFocus Ltd. 

ORACLE is a registered trademark of Oracle Corporation. 

SQL*Plus is a registered trademark of Oracle Corporation. 

UNIX is a registered trademark of X/Open Company Ltd.

Contents 

About This Document :::::::::::::::::::::::::::::::::::::::::: vii 

Section 1. Preparing for Installation of LINC Software 

Overview :::::::::::::::::::::::::::::::::::::::::: 1-1 

About Object Packaging :::::::::::::::::::::::::::::: 1-1 

Required Hardware ::::::::::::::::::::::::::::::::: 1-2 

Configuring the UNIX Kernel :::::::::::::::::::::::::: 1-3 

Required Software :::::::::::::::::::::::::::::::::: 1-5 

Section 2. Installing LINC Deployment Executables 

Overview :::::::::::::::::::::::::::::::::::::::::: 2-1 

Contents of the LINC Deployment CD-ROM ::::::::::::: 2-1 

Pre-Installation Requirements ::::::::::::::::::::::::: 2-2 

Starting the Installation of LINC Deployment Executables : 2-3 

Supplying Details for LINC Deployment Executables ::::: 2-3 

Validation Checks Performed during Installation ::::::::: 2-5 

Defining Environment Variables ::::::::::::::::::::::: 2-5 

Setting Up the LINC Tidy Up Script :::::::::::::::::::: 2-5 

Section 3. Installing LINC Generate Executables 

Overview :::::::::::::::::::::::::::::::::::::::::: 3-1 

Contents of the LINC Generate CD-ROM :::::::::::::::: 3-1 

Pre-Installation Requirements ::::::::::::::::::::::::: 3-2 

Starting the Installation of LINC Generate Executables ::: 3-3 

Supplying Details for LINC Generate Executables :::::::: 3-3 

After Installation Is Complete ::::::::::::::::::::::::: 3-6 

v iii

Contents 

Section 4. Maintaining Your LINC Environment 

Overview ::::::::::::::::::::::::::::::::::::::::::: 4-1 

Typical LINC Environments ::::::::::::::::::::::::::: 4-1 

Installing LINC Deployment Objects :::::::::::::::::::: 4-3 

Pre-Installation Requirements ::::::::::::::::::: 4-3 

Starting the Installation of LINC Deployment Objects : 4-3 

Supplying Details for LINC Deployment Objects ::::: 4-4 

Installing LINC Generate Objects :::::::::::::::::::::: 4-4 

Pre-Installation Requirements ::::::::::::::::::: 4-4 

Starting the Installation of LINC Generate Objects ::: 4-5 

Supplying Details for LINC Generate Objects :::::: 4-5 

The Product Menu Utility ::::::::::::::::::::::::::::: 4-6 

The EIF Installation Menu ::::::::::::::::::::::::::::: 4-8 

Applying EIFs ::::::::::::::::::::::::::::::::::::::: 4-9 

Applying a Validation EIF ::::::::::::::::::::::: 4-9 

Applying Other EIFs :::::::::::::::::::::::::: 4-10 

Uninstalling an EIF ::::::::::::::::::::::::::: 4-11 

Building Executables ::::::::::::::::::::::::::::::::: 4-12 

Building Executables During Installation ::::::::::: 4-12 

Building Executables with Product Menu :::::::::: 4-12 

Creating a Package for Distribution :::::::::::::::::::: 4-13 

Creating a Package :::::::::::::::::::::::::: 4-14 

Removing a Spooled Package :::::::::::::::::: 4-14 

Appendix A. Configuring and Tuning ORACLE and Griffin for 

LINC Software 

Overview ::::::::::::::::::::::::::::::::::::::::::: A-1 

Planning Your ORACLE SIDs and Griffin Universes ::::::: A-2 

Choosing the Number of ORACLE SIDs and Griffin 

Universes ::::::::::::::::::::::::::::::: A-2 

Choosing Names for ORACLE SIDs and Griffin 

Universes ::::::::::::::::::::::::::::::: A-2 

Choosing Names and Sizes of Tablespaces and 

Database Files ::::::::::::::::::::::::::: A-3 

Creating ORACLE SIDs ::::::::::::::::::::::::::::::: A-4 

Before You Start ::::::::::::::::::::::::::::: A-4 

Guidelines for Creating ORACLE SIDs :::::::::::: A-4 

Creating an ORACLE SID :::::::::::::::::::::: A-6 

Creating Griffin Universes :::::::::::::::::::::::::::: A-8 

Before You Start ::::::::::::::::::::::::::::: A-8 

Guidelines for Creating Griffin Universes :::::::::: A-8 

iv v

Glossary 

Index 

Contents 

Creating a Griffin Universe ::::::::::::::::::::: A-10 

Tuning ORACLE SIDs ::::::::::::::::::::::::::::::::: A-12 

Default Configuration of ORACLE SIDs :::::::::::: A-12 

Tuning the Configuration of ORACLE SIDs ::::::::: A-12 

Allowing for Cursors :::::::::::::::::::::::::: A-15 

Changing LINC Structures in Tablespaces ::::::::: A-16 

Tuning Griffin Universes :::::::::::::::::::::::::::::: A-17 

Tuning the Configuration of Griffin Universes ::::::: A-17 

Tuning Griffin ::::::::::::::::::::::::::::::: A-18 

Changing LINC Structures in Tablespaces ::::::::: A-21 

v v

About This Document 

Purpose 

Scope 

Audience 

This document provides information and instructions for the installation and configuration 

of LINC software on the Sequent hosts. 

This document provides step-by-step instructions for installing and configuring LINC 

software at your site. 

Additional information is contained in your LINC Administration and Operations Guide 

for the UNIX Operating System, andinLate-Breaking Changes, available from the LINC 

Support Web page at http://www.support.unisys.com/. This information must be used in 

conjunction with this document. 

The primary audience for this document consists of those responsible for the installation 

of LINC software. 

A secondary audience consists of LINC System designers who need to understand 

operational aspects of LINC Systems that may be pertinent to their design considerations. 

Prerequisites 

The primary audience is presumed to have had training in installing, implementing, and 

operating LINC Systems, and to be familiar with the operational aspects of the Sequent 

host. The secondary audience should be trained in developing LINC Systems. 

How to Use This Document 

Read section 1, which gives an overview of LINC software environments and installation, 

and lists installation prerequisites. Then read the introductory paragraphs at the start of the 

following sections to gain a basic understanding of the layout and scope of this document. 

Read sections 2 and 3 to install supplied LINC software executable packages. 

v vii


Read section 4 to install supplied LINC software object packages, to build LINC 

executables from supplied LINC software object packages, to create object and executable 

packages, and to apply Engineering Interim Fixes (EIFs). 

As part of the installation process, you must also read the Late-Breaking Changes, 

available from the LINC Support Web page at http://www.support.unisys.com/. 

Organization 

Notations 

Caution 

If you are migrating a system from a previous release of LINC, it is important that 

you refer to your LINC Release 16.3/16R3 Migration and Conversion Guide. 

This document contains four sections and an appendix. 

Section 1. Preparing for Installation of LINC Software 

This section describes the preparation required before LINC software can be installed. It 

includes configuration of the host and software requirements. 

Section 2. Installing LINC Deployment Executables 

This section describes the installation of LINC Deployment Executables. 

Section 3. Installing LINC Generate Executables 

This section describes the installation of LINC Generate executables. 

Section 4. Maintaining Your LINC Environment 

This section describes typical LINC environments, the installation of LINC software object 

packages, the building of LINC executables, the creation of LINC object and executable 

packages, and the application of Engineering Interim Fixes (EIFs). 

Appendix A. Configuring and Tuning ORACLE and Griffin for LINC Software 

This section describes the configuration of ORACLE and Griffin for use with LINC. 

In this document, and throughout the LINC documentation, ORACLE SID is used in place 

of the term database that is used in ORACLE documentation. LINC documentation uses 

database in a different context. 

viii v

Related Product Information 


The following publications contain information relevant to the definition and operation of 

a LINC System. These publications are reference sources for users who have completed 

LINC training courses. See your local Unisys representative for information on available 

LINC training courses. 

Most of these documents are published by Unisys Corporation and can be ordered through 

Plymouth Operations Software Manufacturing (POSM), or your local Unisys subsidiary. 

LINC documents without part numbers in the following list are included on the LINC 

Deployment CD. 

In addition to these documents, you may require documentation specific to your Sequent 

host to describe the operation of the related software. 

LINC Administration and Operations Guide for the UNIX Operating System 

This document describes the generation and operation of LINC Systems and Reports, and 

the general administration of LINC Systems. 

LINC Generate Operations Guide 

This document describes the use of LINC Generate to create and maintain user 

information systems. 

LINC Programming Reference Manual 

This document contains reference material for developers, such as LINC Logic commands 

and System Data items used in creating LINC Systems. 

LINC Generate Reference Manual: Painter and Editor 

This document contains reference material for LINC Generate, including LINC Editor and 

LINC Painter commands, Data commands and Data Attributes, and screens and commands 

for defining Profiles. 

LINC Programming Reference Handbook(7844 8057) 

This document contains the syntax of LINC Logic commands and System Data items and 

other commands used in LINC Generate. 

LINC Ad Hoc Inquiry Operations Guide 

This document describes the operation of LINC Ad Hoc Inquiry, which enables users to 

make inquiries against a LINC System, either interactively, or by using structured (SQL) 

statements. 

LINC Developers Guide: LCOPY 

This document provides reference material for using the LINC LCOPY Utility, which is 

used to transfer LINC Specifications between versions of LINC Generate. 

v ix


LINC Executive Overview - The Business Case (7833 2145) 

This document is an introduction to LINC for executive and general readers. 

LINC Technical Overview - The Business Case (7833 2152) 

This document is an overview of LINC features and facilities for more technically oriented 

readers. 

Griffin Data Engine Installation and Administration Guide 

This document describes the installation and administration of the Griffin database 

management system used with LINC Systems. 

ORACLE8 Server for Sun SPARC Solaris 2.x Installation Guide 

ORACLE8 Server for Sun SPARC Solaris 2.x Administrator’s Reference 

These documents describe the installation and administration of the ORACLE database 

management system used with LINC Systems. 

x v

Section 1 

Preparing for Installation of LINC 

Software 

Overview 

Before you install the LINC Software, you should perform the following tasks described in 

this section. 

$ Ensure the required hardware is installed. 

$ Ensure the required software is installed. 

Note: It is important that you study the Late-Breaking Changes, available from the 

LINC Support Web page at http://www.support.unisys.com/, before installing 

LINC software. 

About Object Packaging 

As of LINC Release 16.3/16R3, Deployment and Generate products are supplied as 

packages in two formats u ready-to-install executables and object modules. The object 

packages contain the entire product. 

You can choose to install only the executables, and you will be able to run LINC as soon as 

the installation finishes. 

You can choose to install only the object packages, and the LINC executables must be built 

from the objects before you can run LINC. If you select the build option during object 

package installation, LINC executables are built and you will be able to run LINC as soon 

as the installation finishes. Until the LINC executables are built, either during object 

package installation or afterwards, you will be unable to run LINC from this installation. If 

you install object packages with the build option, there is no need to install executables. 

Usually there is no need to install object packages unless you want to install an EIF or you 

want to use the Forms Translation Utility (FTU) to translate parts of the LINC software. 

To install LINC executable packages, see Section 2 and Section 3. 

To install LINC object packages, see Section 4. 

v 1-1

Required Hardware 

Engineering Interim Fixes (EIFs) are supplied in cpio format. From LINC Release 

16.3/16R3, EIFs are usually supplied as object modules. If the EIF contains object modules, 

a build is necessary. To build LINC executables that include the EIF, the object packages 

must be installed. 

A special type of EIF called a Validation EIF may be provided from time to time. Validation 

EIFs will allow you to build LINC with different levels of ORACLE, Griffin, Cobol, and 

Tuxedo (see the LINC Support Web page at http://www.support.unisys.com/ for availability 

of Validation EIFs). You will usually apply Validation EIFs during installation of object 

packages with the build option selected. 

You access object packaging functions through the Product Menu utility. It allows you to 

install EIFs and it also allows you to make backups of your LINC installation in executable 

package and object package formats. You should make backups after installing EIFs. 

Product Menu is described in Section 4. 

Required Hardware 

The following minimum hardware configuration is required to support the installation and 

operation of this LINC Release. 

$ Sequent DYNIX/ptx host. 

$ A CD-ROM device if you are installing from the supplied LINC executable or object 

packages. 

$ 64 Mb memory for LINC Deployment. 

$ 64 Mb memory for LINC Generate. 

$ Shared memory for ORACLE configuration. Installing LINC Software with the default 

ORACLE configuration requires 8 Mb for each ORACLE SID. 

Note: Increasing the parameters from the default ORACLE configuration 

may increase the shared memory requirements. 

$ Shared memory for Griffin configuration. Installing the LINC Software with the default 

Griffin configuration requires 8 Mb for each Griffin Universe. 

$ 70 Mb disk space for LINC Deployment executables. Approximately 30 Mb of 

additional space is required if object modules are installed. 

$ 125 Mb disk space for LINC Generate executables. Approximately 120 Mb of additional 

space is required if object modules are installed. 

$ Disk space for ORACLE SIDs and Griffin Universes. See ‘‘Creating ORACLE SIDs’’ and 

‘‘Creating Griffin Universes’’, in Appendix A. 

$ Swap space at least equal to three times the size of main memory. A more accurate 

estimate can be calculated from the sum of the following: 

v Code size of fully bound executable program. 

v For each server, add the cursor pool size times 50 Kb, plus the data size of the 

server. 

1-2 v

v For each requestor, add 300 Kb. 

Configuring the UNIX Kernel 

v Add 735 Kb. 

Determine the cursor pool size with the LINC System command :CPS. This command 

is described in your LINC Administration and Operations Guide for the UNIX 

Operating System. 

Determine the amount of swap space used with the UNIX command: 

 

Symptoms of insufficient swap space are: 

v Messages in the error log that show a fork failing. 

v Messages in the error log that show a return value of -1 from c_procstart. 

v ORACLE shadow process failing to start. 

Note: LINC is only qualified to run with an Oracle Dedicated Server and has not been 

qualified in an SQL*Net configuration. Cursor pooling has been implemented 

in LINC to reduce the considerable overheads that have been detected in 

reparsing and rebinding SQL statements. 


Before installing LINC on a Sequent DYNIX/ptx host, ensure that the kernel is configured 

with at least the minimum values. If you wish to increase these minimum values, see your 

DYNIX/ptx System Administration Guide. Your Sequent DYNIX/ptx environment should 

be configured as Commercial or Timeshare. 

The following table contains suggested minimum values for the kernel of a host running 

LINC Systems. See also the notes following the table. 

Parameter Minimum Value 

hfszlim unlimited 

maxproc 150 

maxup 150 

msgmap 1024 

msgmax (8*1024) 

msgmnb (32*1024) 

msgmni 128 

msgseg 4096 

msgssz 32 

continued 

v 1-3


hfszlim 

continued 

Parameter Minimum Value 

semmni 300 

semmns 512 

semmnu 128 

shmmax (See below) 

shmseg 10 

sfszlim unlimited 

This parameter specifies the hard limit (in bytes) for the largest file size that can be 

specified by sfszlim. The default size is unlimited. 

maxproc 

This parameter determines the maximum number of processes per user. 

For LINC, maxproc should be set to at least 150. 

msgmni 

This parameter defines the maximum number of message queues in the system. 

Each active LINC user and each server requires one message queue, so if the system has a 

large number of users, you will need to increase this value. The recommended value of 

msgmni is the number of users, plus the number of servers, plus 50 for the UNIX system 

and other applications. You can safely overestimate the required value, as the memory 

usage is only 52 bytes per message queue. 

semmni/semmns/semmnu 

The number of semaphores required is the number of processes specified for each 

ORACLE SID, plus 3 for each LINC System. See the ORACLE8 Server Administrator’s 

Guide and your ORACLE8 Server Installation Reference for advice on setting and altering 

these parameters. 

For Griffin, the number of semaphores required is the number of Griffin Clients for each 

Griffin Universe, rounded to the nearest multiple of 20. The number of Clients is specified 

when a Griffin Universe is created. See Appendix A for details. 

sfszlim 

This parameter specifies the soft limit (in bytes) for the largest file size that can be created 

by a user. The value of sfszlim cannot exceed hfszlim. The default size is unlimited. 

1-4 v

shmmax 

Required Software 

The amount of shared memory required will depend on the number of ORACLE SIDs and 

Griffin Universes that you want active simultaneously, together with the parameters used 

when initializing or altering each ORACLE SID or Griffin Universe, plus 0x6000 for each 

installed LINC System. 

Set this value to be at least 0xA00000. 


This LINC Release may be installed and run with the software configuration in the 

following table. Future Engineering Interim Fixes (EIFs) may provide support for 

additional software levels. See the LINC Support Web page at 

http://www.support.unisys.com/ and the EIF documentation for details. See also the 

comments following the table. 

DYNIX/ptx release 4.4.2 

Software 

MicroFocus COBOL/2 v4.1 PRN=OXUNY/ZZN:8a.1c.13.01 

ORACLE RDBMS 8.0.3.0 

ORACLE PL*SQL 

Griffin 4.2.2 

Support for standard UNIX character-mode terminals 

TCP/IP software 

Tuxedo ETP System 6.4 

When preparing to install LINC Software 

$ Your COBOL compiler must have been installed and configured before your LINC 

Software can be installed. To install LINC Software you need to know the COBOL 

compiler installation directory and the COBOL software level. 

$ Your ORACLE, ORACLE PL*SQL and Griffin software must have been installed and 

configured before LINC Software can be installed. To install LINC Software you need 

to know the ORACLE and Griffin installation directories, DBA usernames, and 

software levels. See Appendix A. 

Note: If you do not have a full (unrestricted) Griffin license, and you 

intend to use LINC Generate, you must install the restricted Griffin 

software from the LINC Generate CD-ROM. See your Griffin Data 

Engine Installation and Administration Guide for installation details. 

v 1-5


$ Network software is required if you intend to use PowerClient or external Automatic 

Entries to other hosts. 

$ Tuxedo is required if you intend to use On Line Transaction Processing (OLTP). To 

include OLTP support, you need to know the Tuxedo installation directory. 

1-6 v

Section 2 

Installing LINC Deployment Executables 

Overview 

This section describes how to install LINC Deployment Executables on Sequent hosts. You 

must install LINC Deployment before you set up your ORACLE SIDs and Griffin Universes, 

and before you install LINC Generate. 

This section contains the following topics: 

$ Contents of the LINC Deployment CD-ROM 

$ Pre-installation Requirements 

$ Starting the Installation of LINC Deployment Executables 

$ Supplying Details for LINC Deployment Executables 

$ Defining Environment Variables 

$ Setting Up the LINC Tidy Up Script 

Further parts of the installation process, such as configuring ORACLE SIDs and Griffin 

Universes, the installation of object packages, and the installation of LINC Generate 

software, are described in later sections of this document. 

Other considerations, such as setting up usernames and running LINC Systems, are 

described in your LINC Administration and Operations Guide for the UNIX Operating 

System. 

Contents of the LINC Deployment CD-ROM 

The LINC Deployment CD-ROM contains the following products: 

$ LINC Deployment Executables 

LINC Deployment software in executable format (approximately 70 Mb). 

$ LINC Deployment Objects 

LINC Deployment software in object format (approximately 30 Mb). See Section 4 for 

details about installing LINC Deployment Objects. 

$ LINC Documentation 

The LINC documentation library is supplied as online documentation in Acrobat and 

WinHelp format. 

v 2-1

Pre-Installation Requirements 


Before you install LINC Deployment Executables 

1. Ensure that the required hardware and software is installed and configured. See 

Section 1 for details. 

2. Back up any LINC Systems that will use the new LINC Deployment Software. 

3. Ensure that you have the following information which is requested during LINC 

installation: 

$ LINC home directory ($LINCIIDIR). 

$ COBOL installation directory ($COBDIR). 

$ ORACLE DBA username and ORACLE home ($ORACLE_HOME) directory. 

$ Griffin DBA username and Griffin home ($GRFNDIR) directory (if you intend to 

use Griffin LINC Systems, such as LINC Generate). 

$ Tuxedo installation directory ($TUXDIR) if OLTP support is required. 

Note: If the location of any of the underlying support software changes, 

or if any of these values change, you must re-install LINC. 

2-2 v

Supplying Details for LINC Deployment Executables 

Starting the Installation of LINC Deployment 

Executables 

Note: If you are installing LINC on top of existing LINC Software, first ensure that 

no LINC processes using that existing software are currently running. 

To start the installation 

1. Log in to your Sequent host as a superuser. 

2. Insert the LINC Deployment CD-ROM into the CD-ROM drive. 

3. Mount the CD-ROM file system. 

Enter the following from the shell: 

 

Where cdrom is the mount point for the CD-ROM device. 

4. Install the LINC Deployment Executables from the CD-ROM. 


 

$ cdrom is the mountpoint for the CD-ROM device. 

$ deployment is the LINC Deployment package which contains LINC Deployment 

software. 

$ l2r163 is the LINC Deployment product in executable format. 

5. The installation process commences and displays the message 

Installation in progress. Do not remove the media. 

Processing package instance from 

LINC Deployment 16.3, Release 

Version 163.ptx (Sequent) 

Unisys 


When the installation has started, you are asked a number of questions. To get help for a 

question, enter a question mark (?). 

If this package has been installed on this machine before, the system displays the following 

message: 

This appears to be an attempt to install the same architecture and version of a package 

which is already installed. This installationwill attempt to overwrite this package. 

v 2-3


It may be several minutes before the first prompt appears. In any of the following steps, 

you can 

$ Either enter the required information (for example, a directory path). Error messages 

are displayed if you enter invalid information (for example, a path that does not exist). 

$ Or enter Y or N to specify whether or not to perform the action (for example, install 

ORACLE database support). Required information is displayed (for example, required 

software levels). 

$ Press Return to accept the default value. 

$ Enter q to abort the installation. 

1. You are prompted to enter the full path of the LINC installation directory. If there is 

an existing LINC installation in this directory, it will be overwritten. 

2. You are prompted to enter the full path of the COBOL home directory. 

3. You are prompted whether or not to install ORACLE database support. 

4. You are prompted to enter the ORACLE DBA username. 

5. You are prompted to enter the full path of the ORACLE Home directory. 

6. You are prompted whether or not to install Griffin database support. 

7. You are prompted to enter the Griffin DBA username. 

8. You are prompted to enter the Griffin Home directory. 

9. You are prompted whether or not to install Tuxedo support. 

10. You are prompted to enter the Tuxedo installation directory. Tuxedo is needed only if 

you intend to use On-Line Transaction Processing (OLTP). 

11. You are prompted whether or not to install Package Creation support. Package 

creation support enables you to create LINC object or executable packages from 

your LINC installation using the Object Packaging utility. 

12. You are prompted whether or not to apply EIFs during installation of the LINC 

Deployment Executables. 

Caution 

All EIFs in the directory you specify will be applied in numeric order. You should 

read EIF installation instructions to ensure they can be applied with LINC 

Deployment Executables. Most EIFs require that LINC objects are installed and 

they cannot be applied during the installation of LINC Deployment Executables. 

Ensure that the directory you specify contains only those EIFs that can be 

applied and that you want to apply. 

13. If you specified that you wanted to apply EIFs, you are prompted to enter the full 

path of the directory containing the EIFs you want to apply. An attempt will be made 

to apply all EIFs (files with extension .eif, .EIF, .cer, .CER or additionally, 

compressed EIFs with a .Z extension) found in the directory. 

2-4 v

Setting Up the LINC Tidy Up Script 

14. You are prompted whether or not to proceed with the installation of LINC 

Deployment Executables. 

Installation then commences. 

On successful completion of the LINC Deployment Executables installation, the following 

message is displayed: 

Deployment installed on 

Installation of was successful. 

You may want to create or change the configuration of your ORACLE SIDs or Griffin 

Universes. See Appendix A for details of ORACLE and Griffin configuration. 

Validation Checks Performed during Installation 

The following are some of the validation checks performed during LINC installation: 

$ Tuxedo cannot be selected unless ORACLE is also selected. 

$ Checks are made in ORACLE, Griffin, COBOL, and Tuxedo installation directories to 

ensure that the version installed matches the expected level (executables) or the user 

entered level (objects). 

A warning is given if software levels do not match. 

$ All options, or no options, must be entered for each support software package. For 

example, an error is raised if you enter the ORACLE-DBA value but fail to enter an 

ORACLE-HOME value. 

Defining Environment Variables 

Following LINC Deployment installation, you must define or modify the following 

environment variables: 

$ LINCIIDIR 

The LINCIIDIR variable must be set to the full path name of the directory where the 

LINC Deployment software is installed (for example, /usr/linc163). 

$ PATH 

The PATH variable should include $LINCIIDIR/bin. 

Note: You must define these variables before you create ORACLE SIDs or Griffin 

Universes. 


v 2-5


The LINC Tidy Up script removes files from the $LINCIIDIR/trace directory that have not 

been accessed for three days . These files are used for diagnostic purposes, and need not 

normally be retained. 

Add the following line to the file root in the /usr/spool/cron/crontabs directory: 

 

This line sets linc16tdy to run each day at 3:00 a.m. You can change this time as required. In 

this line, $LINCIIDIR should be replaced with the actual directory in which the LINC 

Software was installed. 

For example, if the /usr/linc163 directory was used, the following entry would be made: 

 

2-6 v

Section 3 

Installing LINC Generate Executables 

Overview 

This section describes how to install LINC Generate Executables on Sequent hosts. 

Note: Before installing LINC Generate Executables, you must install LINC 

Deployment Executables. See Section 2. 

This section covers the following: 

$ Contents of the LINC Generate CD-ROM 

$ Pre-Installation Requirements 

$ Starting the Installation of LINC Generate Executables 

$ Supplying Details for LINC Generate Executables 

$ After Installation Is Complete 

Other considerations, such as setting up usernames and running LINC Systems, are 

described in your LINC Administration and Operations Guide for the UNIX Operating 

System. 

Contents of the LINC Generate CD-ROM 

The LINC Generate CD-ROM contains the following products: 

$ Restricted Griffin Software 

Database engine for LINC Generate (approximately 12 Mb), not required if you already 

have a full Griffin license. 

$ LINC Generate Executables 

LINC Generate Software in executable format (approximately 120 Mb). 

$ LINC Generate Objects 

LINC Generate software in object format (approximately 125 Mb). See Section 4 for 

details about installing LINC Generate Objects. 

v 3-1



Before you install LINC Generate Executables, 

$ Ensure that the required hardware and software is installed and configured. See 

Section 1 for details. 

$ Back up any LINC Specifications in the LINC Generate System, if it already exists. 

$ Install the restricted Griffin software if you do not have an unrestricted Griffin 

installation. See your Griffin Data Engine Installation and Administration Guide 

for installation details. 

$ Install LINC Deployment Executables. See Section 2 for details. 

Note: LINC Generate should be installed into the directory in which LINC 

Deployment was last installed on your host. If you are installing 

LINC software into multiple locations, you should first install LINC 

Deployment and then LINC Generate for each of these environments. 

$ Create the Griffin Universe if necessary, and configure it for LINC. See Appendix A for 

details. 

$ Ensure that you know which Griffin Universe is used for LINC Generate. 

$ Ensure that no LINC users are using the Griffin Universe that is to be used by LINC 

Generate. To do this, from the shell, enter: 

 

See your LINC Administration and Operations Guide for the UNIX Operating 

System for details of the linc16 command. 

$ Start the Griffin Universe to be used by LINC Generate with the LINC Griffin Database 

Management Utility (GMU): 

1. Sign on to your host using the Griffin DBA username. 

2. Enter the following from the shell: 

 

3. Select option 3, Change or Set Griffin Universe from the main GMU menu. Enter 

the name of the Griffin Universe to be used for LINC Generate. 

4. Select option 2, Perform Griffin Administration from the main GMU menu. The 

Griffin Administration Functions menu is displayed. 

5. Select option 5, Start this Griffin Universe from the Griffin Administration 

Functions menu. Enter the name of the Griffin Universe to be used by LINC 

Generate. 

The Griffin Universe will be started. 

6. Exit from GMU. 

See your LINC Administration and Operations Guide for the UNIX Operating 

System for details of the Database Management Utility for Griffin. 

3-2 v

Supplying Details for LINC Generate Executables 

Starting the Installation of LINC Generate 

Executables 

Note: Ensure that no LINC processes using the existing software are running. 

To start the installation: 

1. Log in to your Sequent host as a superuser. 

2. Insert the LINC Generate CD-ROM into the CD-ROM drive. 

3. Mount the CD-ROM file system. 


 

Where cdrom is the mount point for the CD-ROM device. 

4. Install the LINC Generate Executables from the CD-ROM. 


 

$ cdrom is the mountpoint for the CD-ROM device. 

$ generate is the LINC Generate package which contains LINC Generate product. 

$ ln2163 is the LINC Generate product in executable format. 

5. The installation process commences and displays the message 

Installation in progress. Do not remove the media. 

Processing package instance from 

LINC Generate 16.3, Release 

Version 163.ptx (Sequent) 

Unisys 


When the installation starts, you are asked a number of questions. To obtain help for a 

question, enter a question mark (?). 

If this package has been installed on this machine before, the system displays the following 

message: 

This appears to be an attempt to install the same architecture and version of a package 

which is already installed. This installation will attempt to overwrite this package. 

It may be several minutes before the first prompt appears. In any of the following steps, 

you can perform one of these actions: 

v 3-3


$ Enter the required information (for example, a directory path). Error messages are 

displayed if you enter invalid information (for example, a path that does not exist). 

$ Enter Y or N to specify whether or not to perform the action (for example, install 

ORACLE database support). Required information is displayed (for example, required 

software levels). 

$ Press Return to accept the default value. 

$ Enter q to abort the installation. 

1. You are prompted to enter the full path of the LINC installation directory. 

2. You are prompted to enter the Griffin Universe to be used by LINC Generate. 

3. You are prompted whether or not to retain LINC Specifications and LINC Security 

settings in an existing installation. 

Caution 

Before you choose to delete all existing LINC Specifications, ensure that you 

have a backup copy. 

4. You are prompted to make Reserved word host list selections. An entry for a host 

type enables reserved word checking for that host type if it is currently not selected, 

and disables reserved word checking for that host type if it is currently selected. 

UNIX is mandatory and cannot be disabled. A table showing the current status of the 

Reserved word host list selections is displayed, and redisplayed after each selection. 

For new installations, the default is to check for UNIX reserved words only. 

Note: You can also set and change target host types and Reserved word 

lists using the Supervisor mode in LINC Generate. If you opted to 

Retain the existing database then the entries you make here will 

not override your existing HOSTLIST settings and you will have to 

use the Supervisor mode Host Maintenance feature to change your 

host settings. See the LINC Generate Operations Guide for further 

details. 

5. You are prompted whether or not to load templates into shared memory when LINC 

systems are generated. Loading templates uses more memory, but will speed up the 

generate process. 

6. You are prompted whether or not to allow automatic resequencing of line numbers in 

the Editor. 

7. You are prompted whether or not to enable Change Identification for LINC Generate. 

See your LINC Generate Operations Guide for information on change control 

settings. 

8. You are prompted whether or not to enable Resource Locking for LINC Generate. See 

your LINC Generate Operations Guide for information on Resource Locking. 

3-4 v


9. If you have enabled either Change Identification or Resource Locking, you are 

prompted to enter the type of identification mode. 

Value Identification Mode 

1 Identification by Station Name 

2 Identification by LSM usercode 

3 Identification by Change Identifier 

10. You are prompted whether or not to enable Patch Identification. See your LINC 

Generate Operations Guide for details of Patch Identification. 

11. You are prompted to specify your required audit level. See your LINC Generate 

Operations Guide for details about audit levels. 

12. You are prompted whether or not to use the Specification Administration facility. 

This facility enables you to define administration tasks for your LINC Specifications. 

See your LINC Generate Operations Guide for details of the Specification 

Administration utility. 

13. You are prompted whether or not to reset Run Time Version counts when the patch 

identifier is changed. See your LINC Generate Operations Guide for details about 

runtime version counts. 

14. You are prompted whether or not to reset Report version counts each time your LINC 

System is generated. See your LINC Generate Operations Guide for details about 

Report version counts. 

15. You are prompted whether or not to propagate your configuration settings to all 

LINC Specifications (that is, use the same change control and patch identification 

settings for all LINC Specifications in LINC Generate). See your LINC Generate 

Operations Guide for details about the Propagate All Settings option. 

16. You are prompted whether or not to install Package Creation support. Package 

Creation support enables you to create LINC object or executable packages from 

your LINC installation using the Object Packaging utility. 

17. You are prompted whether or not to apply any EIFs during installation. 

Caution 

All EIFs in the directory you specify will be applied in numeric order. You should 

read EIF installation instructions to ensure they can be applied with LINC 

Generate Executables. Most EIFs require that LINC objects are installed and 

they cannot be applied during the installation of LINC Generate Executables. 

Ensure that the directory you specify contains only those EIFs that can be 

applied and that you want to apply. 

v 3-5

After Installation Is Complete 

18. If you specify that you want to apply EIFs, you are prompted to enter the full path of 

the directory containing the EIFs you want to apply. An attempt will be made to 

apply all EIFs (files with extension .eif, .EIF, .cer, .CER or additionally, compressed 

EIFs with a .Z extension) found in the directory. 

19. You are prompted whether or not to proceed with the installation of LINC Generate 

Executables. 

Installation then commences. 

On successful completion of the LINC Generate Executables installation, the following 

message is displayed: 

Generate installed on 

Installation of was successful. 

After Installation Is Complete 

After installation is complete, perform the following tasks: 

$ Enable the system with the shell command 

 

if you disabled it before installation. See your LINC Administration and Operations 

Guide for the UNIX Operating System for details of the linc16 command. 

$ Change the configuration of the Griffin Universe as required. See Appendix A for 

configuration details. 

$ Update any LINC Specifications as detailed in the output file produced by reserved 

word checking. 

3-6 v

Section 4 

Maintaining Your LINC Environment 

Overview 

This is a general guide to maintenance in your LINC environment. It is by no means 

exhaustive. You must carefully consider your own specific requirements and how you can 

best use the features of object packaging. 

Much of the process of maintaining your LINC environment is controlled on site using 

object packaging. From LINC 16.3, LINC Deployment and LINC Generate products are 

supplied as packages in two formats u ready-to-install executables, and object modules. 

The object packages contain everything needed to build the entire product and are 

required for translation and for the installation of most Engineering Interim Fixes (EIFs). 

The directory you install LINC into is defined by the environment variable LINCIIDIR. A 

LINCIIDIR that contains the LINC object packages necessary to build LINC executables is 

a buildable LINCIIDIR. The creation and maintenance of a buildable LINCIIDIR is essential 

to the use of object packaging in maintaining your LINC environment. 

As of LINC 16.3, EIFs, in cpio format, will usually be supplied as objects. If the EIF 

contains object modules, the LINC object packages will have to be installed before you 

apply the EIF. You then build your new LINC executables incorporating the EIF. 

A special type of EIF called a Validation EIF may be provided from time to time. Validation 

EIFs will allow you to build the LINC products with different levels of ORACLE, Griffin, 

COBOL, and Tuxedo (see the LINC Support Web page at http://www.support.unisys.com/ 

for availability of Validation EIFs). You will usually apply Validation EIFs during 

installation of object packages with the build option selected. 

You access object packaging functions with the Product Menu utility. It allows you to 

install EIFs and it also allows you to make backups of your LINC installation in executable 

package and object package formats. You should make backups before and after installing 

EIFs. The Product Menu utility is described later in this section. 

To install LINC executable packages, see Section 2 and Section 3. 

Typical LINC Environments 

With the availability of user controlled object packaging, you may want to reconsider your 

change control and maintenance strategy. Object packaging allows you to create and 

archive new LINC object and executable packages incrementally with each EIF. It will be 

important that you maintain version control of the packages supplied and those you build, 

to provide a complete audit trail of incremental LINC changes as implemented through the 

installation of EIFs. 

v 4-1

Typical LINC Environments 

The expected LINC environments fall into two broad types: 

$ A basic environment which would comprise a single LINCIIDIR which provides for 

both development and production activities. You will need to take your LINC 

production off-line to perform maintenance tasks with object packaging including 

installing, building, and testing. 

$ A standard environment comprising a single maintenance LINCIIDIR and one or more 

production LINCIIDIRs on the same or other machines. The other machines must be 

running identical levels of system software. All maintenance tasks involving object 

packaging are performed in the maintenance LINCIIDIR. The newly created LINC 

executables are then transferred to each production LINCIIDIR and installed. LINC 

must be shut down on each production LINCIIDIR only for the time taken to install the 

new executables. 

It is desirable to have a LINC maintenance environment which is not used for production 

work. This is because the buildable LINCIIDIR will be unavailable while EIFs are installed, 

and while LINC executables are built and tested. 

The recommended incremental maintenance cycle in your maintenance environment 

would be as follows: 

1. Initial installation 

Install LINC executable packages from CD-ROM into your production LINCIIDIR 

directory or directories. 

2. First EIF 

$ When required, download an EIF (cpio file) from the web. 

$ Install LINC object packages from CD-ROM into your maintenance environment 

LINCIIDIR directory, applying EIFs and requesting a build. 

$ Test your newly built executables in your maintenance environment LINCIIDIR 

directory. 

$ Create backup packages for objects and executables. 

$ Archive the object packages for use when installing the next EIF. 

$ Install the executable packages into your production LINCIIDIR directory or 

directories. 

3. Subsequent EIFs 

$ When required, download another EIF (cpio file) from the web. 

$ Install most recent LINC object packages from archive into your maintenance 

environment LINCIIDIR directory, applying new EIFs and requesting a build. 

$ Test your newly built executables in your maintenance environment LINCIIDIR 

directory. 

$ Create backup packages for objects and executables. 

$ Archive the object packages for use when installing the next EIF. 

4-2 v

Installing LINC Deployment Objects 

$ Install the executable packages into your production LINCIIDIR directory or 

directories. 

This strategy means you are always applying an EIF to a proven LINC build. This takes the 

shortest time to process and provides you with an immediate fallback to the most recent 

version if required. 

Note: If you can guarantee the integrity of the objects in your maintenance 

environment, you can install and build subsequent EIFs using the Product 

Menu utility instead of reinstalling object packages from archive. 

Installing LINC Deployment Objects 

To maintain your own LINC environment, you need to be able to build new LINC 

executables for installation at your site. New LINC executables are built from LINC objects 

and EIFs located in a buildable installation. A buildable installation requires the 

installation of the LINC Deployment Objects from the LINC Deployment CD-ROM or from 

an archived LINC Deployment Objects package. 

This section describes how to install LINC Deployment objects. You must install LINC 

Deployment Objects before you can install LINC Generate Objects. 

The environment variable LINCIIDIR specifies the full path of the buildable installation of 

LINC Deployment objects. A log of the installation process is written to 

LINCIIDIR/install/ProductLog in the installation LINCIIDIR. 

To create a buildable installation requires the following: 


$ Starting the Installation of LINC Deployment objects 

$ Supplying Details for LINC Deployment objects 


Pre-installation requirements for LINC Deployment Objects are similar to those described 

for LINC Deployment installation in ‘‘Pre-Installation Requirements’’. Also ensure that you 

know the ORACLE, Griffin, COBOL and Tuxedo software levels. 

Starting the Installation of LINC Deployment Objects 

Starting the installation of LINC Deployment Objects is almost identical to ‘‘Starting the 

Installation of LINC Deployment Executables’’ described in Section 2. The only difference 

is that you must choose LINC Deployment Objects (l2ro163) and not LINC Deployment 

Executables (l2r163). 


 

v 4-3

Installing LINC Generate Objects 

Supplying Details for LINC Deployment Objects 

Supplying details for LINC Deployment objects is almost identical to Supplying Details for 

LINC Deployment executables described in Section 2. The differences are that you must 

enter the following additional values. The values you enter must be in the validated list of 

software supported by LINC. 

$ COBOL level 

$ ORACLE level 

$ Griffin level 

$ Tuxedo level 

$ You are prompted whether or not to build LINC Deployment executables as part of 

this installation. 

Normally you do not build LINC Deployment if you are going to install LINC Generate 

unless you need to configure a Griffin Universe to install LINC Generate into. 

After installing LINC Deployment objects, you should configure your ORACLE SIDs or 

Griffin Universes for use with LINC. You will not be able to perform this configuration until 

you have built LINC Deployment executables. See Appendix A for details of ORACLE and 

Griffin configuration. 


A buildable installation which includes LINC Generate requires the installation of the LINC 

Generate Objects from the LINC Generate CD-ROM or from an archived LINC Generate 

Objects package. 

The environment variable LINCIIDIR specifies the full path of the buildable installation of 

LINC objects. A log of the installation process is written to 

$LINCIIDIR/install/ProductLog in the installation LINCIIDIR. 

To create a buildable installation requires the following: 


$ Starting the Installation of LINC Generate Objects 

$ Supplying Details for LINC Generate Objects 


Pre-installation requirements for LINC Generate Objects are almost identical to those 

described in ‘‘Pre-Installation Requirements’’ in Section 3. 

Additionally, you must have already installed LINC Deployment Objects. See ‘‘Installing 

LINC Deployment Objects’’ earlier in this section. 

4-4 v

Starting the Installation of LINC Generate Objects 


Starting the installation of LINC Generate Objects is almost identical to ‘‘Starting the 

Installation of LINC Generate Executables’’ described in Section 3. The only difference is 

that you must choose LINC Generate Objects (ln2o163) and not LINC Generate 

Executables (ln2163). 


 

Supplying Details for LINC Generate Objects 

Supplying Details for LINC Generate Objects is almost identical to ‘‘Supplying Details for 

LINC Generate Executables’’ described in Section 3. The difference is that you are 

prompted whether or not to build LINC Deployment executables as part of this installation. 

Do you want to build the product now (default: no) [y,n,?,q] 

Enter Y or N to specify whether or not to build LINC Generate executables from this 

installation. It is usual to build LINC executables during the LINC Generate Objects 

installation. 

Alternatively, enter q to abort the installation. 

v 4-5

The Product Menu Utility 


Product Menu is a menu driven utility for maintaining your LINC environment. You must 

be logged in as the root user to run the Product Menu utility. You start Product Menu with: 

 

 

The product menu appears with the following options: 

1 - Display Software Environment 

Use this option to display the software environment settings you have chosen for this 

installation. The Display Software Environment screen appears. 

2 - Install Package 

Use this option to install a LINC package from the original CD-ROM or from a package you 

have created into another LINCIIDIR. 

You will be prompted to enter the device name for the device (or path) containing the 

LINC package. See ‘‘Installing LINC Deployment Objects’’ or ‘‘Installing LINC Generate 

Objects’’earlier in this section, or see Section 2 or Section 3 for further details. 

Caution 

Don’t use Product Menu to install LINC Deployment into the same LINCIIDIR from 

which you are running Product Menu to avoid overwriting Product Menu with a 

changed version. 

3 - Build Executables 

Use this option to build LINC executables from a buildable LINCIIDIR (a LINCIIDIR that 

contains the LINC object packages). During the build, no users are permitted to run 

anything in the LINCIIDIR and you should ensure that there are no running processes 

using the LINCIIDIR. You are prompted to enter the build type. The build type can be one 

of the following: 

$ Normal 

The product status file is used to determine which components to build. Use this build 

type to initiate a build after installation. 

$ Timestamps 

Caution 

The product status file is LINCIIDIR/install/ProductStatus. You should never 

manually edit this file. 

4-6 v


The time and date stamps of the individual object files are compared with the existing 

executables (if they exist) to determine which files to build. Use this build type to 

initiate a build after installing an EIF. 

$ Forced 

All files and components are built regardless of their status. This build type is not 

usually required. 

You will need to build new LINC executables using the timestamps option when you have 

applied an EIF (see your EIF installation instructions). 

Check that the environment variables LINCIIDIR and PATH are set correctly and use 

1 - Display Software Environment to ensure you have the correct values for your software 

environment. 

4 - Finish Post-Install Processing 

Use this option to finish the installation processing before you attempt to run LINC. This is 

required if you initiated a build with the Product Menu utility rather than during 

installation. 

5 - Create Package 

Use this option to create an object or executable package. You can use the created 

packages for archiving or distributing to other environments for installation. 

You are prompted to specify whether you want to create a Deployment or Generate 

package, whether you want to create an Object or Executable package, and the pathname 

of the directory you want to use as a spool directory to hold the packages you create. 

You are prompted to enter a version suffix. The default suffix is the last one entered. 

Increment the version suffix if you have added EIFs since the last packages used. 

Once you have created a package, you can use 6 - Transfer Packages to Final Media, to 

move one or more packages to a device or file for archive or distribution to other 

environments. You can also choose to install LINC directly from your spool directory. 

6 - Transfer Packages to Final Media (optional) 

Use this option to transfer all object and executable packages in your spool directory to an 

installable file or mounted device. This is one way to distribute packages you have created 

to other environments for installation. 

You can also use this option to create archives of the packages you have created and 

installed, or to create a single file that contains multiple packages. 

7 - Remove Spooled Packages 

Use this option to remove packages you have created from your spool directory. 

Packages you have created using 5 - Create Package, are stored in a spool directory that 

you specify. Once you have archived and distributed your package, you can delete it from 

the spool directory to reclaim the disk space. 

v 4-7

The EIF Installation Menu 

8 - Install EIF 

You can use this option to install an EIF in your buildable LINCIIDIR and then build new 

executables for installation. However, if you cannot guarantee the integrity of the objects 

in your buildable LINCIIDIR, you should apply EIFs during installation of a recent object 

package archive and not use this option. 

Do not use this option to apply a Validation EIF. If you want the Validation EIF to take 

effect in the current installation, it must be applied during installation. For a description of 

the procedure to install an EIF using the options of this screen, see ‘‘Applying Other EIFs’’ 

later in this section. 

9-Exit 

Use this option to exit the Product Menu utility and return to the shell prompt. 

The EIF Installation Menu 

From the Product Menu screen, select 8 - Install EIF to display the EIF Installation menu. 

See ‘‘Applying EIFs’’ later in this section for details. The EIF Installation menu has the 

following options: 

1 - Select EIF to install 

Select this option to specify the EIF you want to apply, or to specify the EIF you want to 

back out. You are prompted to enter the full pathname of the cpio file containing the EIF. 

2 - Change Backup Directory 

Select this option to specify the backup directory where files that will be replaced by 

application of the EIF are to be stored. 

3 - Backup LINC product files to be replaced by EIF 

Select this option to backup LINC files that will be replaced by the EIF to the location you 

specified in 2 - Change Backup Directory. The files will be saved in a file with the same 

name as the EIF but with the extension .save. You can use these files to back out of the EIF 

installation and return the LINCIIDIR to its previous state. 

4 - Copy EIF from cpio file to $LINCIIDIR 

Specify this option to copy the files from the EIF cpio file into your defined LINCIIDIR 

directory. The files will be used with the LINC objects in LINCIIDIR to build the new LINC 

executables. 

5 - Build Executables 

Select this option to build new LINC executables from the LINC and EIF objects in your 

LINCIIDIR. The resulting executables are updated with the EIF you have applied. 

4-8 v

6 - Run installeifnnnn script 

Applying EIFs 

Select this option to run the script supplied with the EIF. This script performs additional 

actions specific to this EIF (see your EIF installation instructions for further details). 

7 - Restore LINC product files from backup 

Select this option to restore the LINC files from the .save file in the backup directory to the 

LINCIIDIR directory. This action overwrites the EIF files and enables you to rollout the 

EIF. If you did a build to apply the EIF, then you must build your LINC executables again 

to return to your LINC installation to its previous state. 

8 - Remove backup files 

Once the EIF has been installed and tested, select this option to remove the backup files 

contained in the .save file in the backup directory you specified in 2 - Change Backup 

Directory. Option 7 will then be disabled for this EIF. 

9 - Return to Main Menu 

Select this option to exit the EIF Installation menu and return to the main menu. 

Applying EIFs 

EIFs can be applied in several ways. The installation instructions accompanying an EIF 

will detail specific installation requirements. Two types of EIF are considered and 

described here: 

$ Validation EIFs 

Validation EIFs provide additional support for different versions of software which 

have been validated for use with LINC. The newly validated versions are then available 

as support software choices during LINC installation. To use a new software level, 

Validation EIFs must be applied during LINC Deployment Objects installation, and a 

build is normally required. 

$ Other EIFs 

These EIFs usually require new LINC executables to be built from a buildable 

LINCIIDIR. If you are installing LINC objects, you should apply the EIF during 

installation. Otherwise, install the EIF with Product Menu after the installation of LINC 

objects (see the EIF Installation Instructions for further details). 

Before installing an EIF, you should create backup packages of your LINC installation. See 

‘‘Creating a Package for Distribution’’, later in this section. 

Read any special instructions that come with the EIF. To apply EIFs during installation, 

the file name must be either eif or EIF followed by the EIF number. File names of 

compressed EIFs should retain the .Z suffix. 

Applying a Validation EIF 

v 4-9

Applying EIFs 

During LINC Deployment Objects installation (see ‘‘Installing LINC Deployment Objects’’ 

earlier in this section), you are prompted whether or not you want to apply EIFs. If you 

answer yes you are then prompted to enter the full pathname of the directory containing 

the Validation EIFs you want to install. 

All EIF files in the specified directory will be applied. 

You can choose the newly validated level during this installation. The new level will not 

appear in the list of valid levels, as the EIF has not yet been installed. Enter the new level 

anyway. You will be cautioned that a Validation EIF must be applied during this 

installation. 

The new level of software must already be installed. 

Object packages subsequently created from this LINCIIDIR will include the new software 

level in the list of valid levels displayed for subsequent installs. 

Applying Other EIFs 

You usually apply non Validation EIFs in one of two ways: 

1. During LINC objects installation (see ‘‘Installing LINC Deployment Objects’’ or 

‘‘Installing LINC Generate Objects’’earlier in this section), you are prompted whether 

or not you want to apply EIFs. If you answer yes you are then prompted to enter the 

full pathname of the directory containing the Validation EIFs you want to install. 

All EIF files in the specified directory will be applied. 

2. Following LINC objects installation, use the Product Menu utility to install an EIF. 

To install an EIF to an existing buildable LINC installation, 

1. Log in to your system as a superuser. 

2. Change directory to the LINCIIDIR directory containing your buildable LINC 

installation. 

3. Start Product Menu with 

 

The Product Menu screen appears. 

4. Select 8 - Install EIF. 

The EIF installation screen appears. The display-only fields at the top of the screen 

show the current settings for the LINCIIDIR directory, the EIF file and the backup 

directory. 

5. Select 1 - Select EIF to install. 

Enter the full pathname of the EIF to install. If the EIF file is compressed, be sure to 

include the .Z suffix. 

6. Select 2 - Change Backup Directory. 

4-10 v

Applying EIFs 

Enter a directory where files replaced by the EIF are backed up. 

7. Select 3 - Backup LINC product files to be replaced by EIF. 

This creates backup files in the backup directory you specified. The backup files are 

named the same as the EIF file, but with a .save suffix. 

8. Select 4 - Copy EIF from cpio file to $LINCIIDIR. 

This copies (and expands if the file is compressed) the EIF file into your buildable 

LINC installation directory. 

9. Select 5 - Build Executables. 

This builds the new executables from the LINC and EIF objects in the buildable LINC 

installation directory. 

10. If instructed in the EIF installation instructions, select 6 - Run installeifnnnn script. 

This runs the post installation script supplied with the EIF. 

If the installation failed, or if you find that you did not require the EIF you installed, you 

can restore the files you backed up before the installation. See ‘‘Uninstalling an EIF’’ later 

in this section. 

Uninstalling an EIF 

You can restore the files you backed up before the EIF installation, and rebuild LINC to its 

previous status as follows: 



installation. 


 


4. Select 8 - Install EIF. 

The EIF installation screen appears. 

5. Select 1 - Select EIF to Install. 

Enter the full pathname of the EIF you want to uninstall. 

6. Select 2 - Change Backup Directory. 

Specify the location of the backup file for the EIF you want to uninstall. 

7. Select 7 - Restore LINC product files from backup. 

The currently selected EIF is uninstalled using the specified backup file to replace 

the relevant EIF files in the selected LINCIIDIR. 


v 4-11

Building Executables 

This builds executables from the LINC objects in the buildable LINC installation 

directory. The EIF files have been overwritten by the restore action and the new 

LINC executables are created using the newly restored files. 

Building Executables 

There are two ways in which you can build executables. They are described in the 

following subsections. 

Building Executables During Installation 

Follow the instructions in ‘‘Installing LINC Deployment Objects’’ or ‘‘Installing LINC 

Generate Objects’’ earlier in this section. 

You are prompted whether or not to build LINC Deployment executables during the 

installation of LINC Objects, Deployment and Generate. 

Do you want to build the product now (default: no) [y,n,?,q] 

Enter Y to specify that you want to build LINC (Deployment or Generate) executables 

from this installation. 

The resultant LINCIIDIR will contain both executables and objects. 

If you are going to install LINC Generate Objects, usually you would not install LINC 

Deployment Objects with the build option. You would install LINC Generate Objects with 

build which would automatically build LINC Deployment executables before building 

LINC Generate Executables. 

If you build executables in this way, you can choose to apply any EIFs during the 

installation. Executables built in this way will include any EIFs in the specified EIF 

directory (see ‘‘Applying EIFs’’ earlier in this section for filename restrictions). 

Building Executables with Product Menu 

1. Log in to the system as a superuser. 


installation. 


 



The Build Executables screen appears displaying the free space in your LINCIIDIR 

and TMPDIR directories. 

4-12 v

Creating a Package for Distribution 

5. Press Return to continue. You are warned about running LINC executables in this 

LINCIIDIR. 

Ensure that no users attempt execution of LINC during the build. 

6. Press Return to continue. 

7. Enter the type of build you want and press Return. 

The build can be one of the following: 

$ Normal 

The product status file is used to determine which components to build. Use this 

type to restart a stopped build, or to initiate a build after installation. 

Caution 

The product status file is LINCIIDIR/install/ProductStatus. You should 

never manually edit this file. 

$ Timestamps 

The time and date stamps of the individual object files are compared with the 

existing executables (if they exist) to determine which files to build. Use this 

type of build after installing an EIF. 

$ Forced 

All files and components are built regardless of their status. Use this type of build 

to force a build of everything. This should not normally be required. 

The LINC executables are created in your LINCIIDIR directory. 

8. Select 4 - Finish Post-Install Processing. 

Processing is performed to finish LINC installation processing. 

Use this option to finish the installation processing before you attempt to run LINC. 

This step is only required once per release level (for example 16.3) per universe. 

Future installations of the same release level into the same universe do not require 

this step to be repeated. However, repeating the step does no harm if you are unsure. 


The Product Menu utility allows you to create a package of your LINC installation, in either 

executable or object formats. It is recommended that you create backups of both objects 

and executables. 

You can create packages with support for any validated software installed with this LINC 

installation, and all packages created will contain all EIFs applied to this LINC installation. 

v 4-13


Executable packages can only be installed into an environment with the same software 

levels as the software levels that were used to build the executables in the package. 

Software levels can only be changed during the installation of LINC Deployment Objects. 

Creating a Package 



installation. 


 


4. Select 5 - Create Package. 

The Create Package screen appears. You are prompted to specify the following: 

$ Whether to create a Deployment (Runtime) or Generate (Development) package. 

If you intend to distribute LINC Generate, then you will need to distribute LINC 

Deployment as well. 

$ Whether to create an Object or Executable package. You can only create an 

object package if you have installed the Deployment or Generate objects. 

Similarly, you can only create an executable package if you have built or installed 

the Deployment or Generate executables. 

$ The location of the spool directory where you want the packages created. 

$ The suffix to be appended to the LINC version for your information. The default 

suffix is the current version. 

You should increment the suffix if you have applied EIFs as a means of tracking 

your different packages. 

The Product Menu utility then creates the specified package in the specified spool 

directory. 

5. Select 6 - Transfer Packages to Final Media (optional). 

When the Product Menu utility has successfully created the package, this action 

creates a single file in a distribution directory or on mounted distribution media. 

You can use this distribution file or media to install the newly created package on 

your production machines. The distribution file or media will contain all packages 

that were in your specified spool directory. 

To install an executable package you have created, see Section 2 or Section 3. 

To install an object package you have created, see ‘‘Installing LINC Deployment Objects’’ or 

‘‘Installing LINC Generate Objects’’ earlier in this section. 

Removing a Spooled Package 

4-14 v


If you have created a number of packages in your spool directory, you may wish to remove 

one or more of them after you transfer a package to a file. You may also want to remove 

spooled packages once you have archived the package and have distributed the file for 

installation in your production LINCIIDIRs. 


installation. 


 


3. Select 7 - Remove Spooled Packages. 

The Remove Spooled Packages screen appears. 

4. Enter the location of the spool directory containing packages you want to remove. 

5. Enter the name of the package you want to remove from the spool directory or press 

Return to see a list of packages in the specified spool directory. 

Removing a package from the spool directory does not remove the source of the 

package in your LINCIIDIR. Once the package has been successfully removed, you 

are prompted to enter the name of the next package you want to remove. 

6. Press Ctrl-D to return to the Product Menu screen when you have finished removing 

packages from the spool directory. 

v 4-15

Appendix A 

Configuring and Tuning ORACLE and 

Griffin for LINC Software 

Overview 

ORACLE and Griffin must be configured before your LINC Software can be used, and 

before LINC Generate can be installed. You cannot configure ORACLE and Griffin until 

you have installed the LINC Deployment Executables or built them from the installed LINC 

Deployment Objects. 

This section contains the following procedures for configuring ORACLE and Griffin: 

$ Planning your ORACLE SIDs and Griffin Universes 

$ Creating ORACLE SIDs 

$ Creating Griffin Universes 

$ Tuning ORACLE SIDs 

$ Tuning Griffin Universes 

Note: In this document and throughout the LINC documentation, ORACLE SID is 

used in place of the term database that is used in ORACLE documentation. 

LINC documentation uses database in a different context. 

v A-1

Planning Your ORACLE SIDs and Griffin Universes 


In order to run LINC Systems whose databases will reside in an ORACLE SID or Griffin 

Universe, you must first plan your ORACLE SIDs and Griffin Universes by performing the 

following tasks: 

$ Choose the number of ORACLE SIDs and Griffin Universes 

$ Choose names for your ORACLE SIDs and Griffin Universes 

$ Choose Names and Sizes of Tablespaces and Database Files 

Choosing the Number of ORACLE SIDs and Griffin Universes 

Use the following guidelines when deciding how many ORACLE SIDs and Griffin 

Universes to create. 

$ You can choose to create a separate ORACLE SID or Griffin Universe for each LINC 

System, or assign all LINC Systems to a single ORACLE SID or Griffin Universe. 

$ The Griffin Universe for LINC Generate should be separate from those used for LINC 

Deployment. 

Caution 

Do not use the same ORACLE SID or Griffin Universe for multiple versions of LINC 

Software. This could corrupt data for the LINC Report Output Control System (ROC) 

and other system tables. 

You should install multiple versions of LINC Software in separate ORACLE SIDs or 

Griffin Universes. 

Choosing Names for ORACLE SIDs and Griffin Universes 

LINC is designed only for one- or two-character ORACLE SID and Griffin Universe names, 

where the first character is uppercase A through Z only, and the second character is 

uppercase A through Z, or0 through 9. 

Examples of valid and invalid names for use with LINC Software are contained in the 

following table. 

A-2 v


Valid names A C1 HB Z9 

Invalid names ABC aB Ab 1A 

Note: Do not use the same name for an ORACLE SID and a Griffin Universe. 

Choosing Names and Sizes of Tablespaces and Database Files 

Structures in the LINC Database are assigned to disk locations according to Tablespace 

name. The disk locations available to a given Tablespace are determined by the ORACLE 

or Griffin database files the Tablespace contains. 

You may want to separate files from each other for reasons of hardware failure and I/O 

load. For example, you can put audit and control files on a different physical disk unit from 

the rest of the database. You can improve performance by placing high-usage files on 

physical disk units of their own, reducing I/O contention, and placing the files in such a 

way as to reduce head movement. 

For the initial installation, most Tablespaces normally consist of a single ORACLE or 

Griffin database file, unless there is insufficient available contiguous space. More database 

files can be added subsequently to Tablespaces as required. 

v A-3

Creating ORACLE SIDs 


Before You Start 

Before you begin the process of creating an ORACLE SID, you need to gather the following 

information: 

$ Password for the ORACLE DBA username. The password is required to allow access 

to the functions and privileges of the username. 

$ Name of the new ORACLE SID. See ‘‘Choosing Names for ORACLE SIDs and Griffin 

Universes’’, earlier in this section. 

$ Configuration information for the ORACLE SID 

v Proposed location of additional control files. 

v Number of 2 KB database buffers. 

v Name of rollback segments. 

v Number and size of extents, which determine the size of the rollback segments. 

v Sizes, names, and locations of Tablespaces and ORACLE database files. You will 

be adding one database file in the SYSTEM Tablespace during the creation of the 

ORACLE SID, and adding the remaining database files later. 

v Location and size of Redo Log files. 

See ‘‘Guidelines for Creating ORACLE SIDs’’ for further details. 

In addition to the above, you must have installed LINC Deployment and set up 

environment variables. See Section 2 of this document. 

Guidelines for Creating ORACLE SIDs 

Use the following points as a guide for the minimum requirements for your ORACLE SID. 

$ Location of additional control files for the ORACLE SID 

The ORACLE Control file contains the location of database and Redo Log files, and is 

used to record information about the use of the ORACLE SID. Multiple copies of the 

Control file are recommended to ensure database reliability and recoverability. 

Additional copies of the file should be placed on different physical disk drives. 

$ Number of 2 KB database buffers 

If the ORACLE SID is to be used for small LINC systems, accept the default value of 

1000. If the ORACLE SID is to be used for large LINC systems, increase the value to 

2000. This value has a significant impact on the amount of shared memory required for 

the ORACLE SID. 

$ Name of rollback segments 

The default name is RBS_1. 

A-4 v


$ Number and size of extents which determine the size of the rollback segments 

If you do not create rollback segments for an ORACLE SID used for LINC systems, the 

SYSTEM rollback segment will be used. You can add rollback segments to any 

Tablespace later, by using the Database Management Utility (DMU). For details of 

DMU, see your LINC Administration and Operations Guide for the UNIX Operating 

System. 

See also the descriptions of the init.ora and rollback_segments parameters in the 

ORACLE8 Server Administrator’s Guide. 

Note: All rollback segments you create should be the same size. The 

SYSTEM rollback segment is created automatically, and need not be 

the same size as other rollback segments. 

$ Size and locations of Tablespaces and database files 

The initial file (SYSTEM Tablespace) should be at least 25 MB to hold ORACLE system 

tables and LINC system tables. Both sets of system tables will require space as more 

LINC Systems are generated and run. Additional space is required for LINC Report 

Output Control System (ROC16) and LINC Ad Hoc Inquiry Utility (ADHOC16) 

structures. See ‘‘Changing LINC Structures in Tablespaces’’ later in this section. 

The location of the file or files will be determined by the availability of raw disk 

partitions or space available in the UNIX file system. You must ensure that permissions 

of any raw disk or directories will allow users access to the database files. See also 

‘‘Choosing Names and Sizes of Tablespaces and Database Files’’, earlier in this section. 

$ Location and size of Redo Log files 

For the LINC Deployment ORACLE SID, two 500 KB Redo Log files may be sufficient 

for small LINC systems. Increase the size for large systems. 

The amount of space required will be affected by 

$ The size of the LINC Databases stored in an ORACLE SID for LINC Systems 

$ The size of the database for the LINC Report Output Control System (ROC) in an 

ORACLE SID 

Note: You will find that more space is required as you add data for your systems. You 

can use DMU to alter the size of your ORACLE SIDs. For details of DMU, see 

your LINC Administration and Operations Guide for the UNIX Operating System. 

Additional considerations for ORACLE SIDs are as follows: 

$ ORACLE parameter init_sql_files 

Ensure that the init_sql_files parameter includes catalog.sql, catexp.sql and 

catproc.sql, or ensure that these files are run using sqldba after creating a new 

ORACLE SID. The LINC Database Management Utility (DMU) runs these files 

automatically after creating a new ORACLE SID. 

See also the descriptions of the init.ora parameters in the ORACLE8 Server 

Administrator’s Guide. 

v A-5


$ Raw disk 

If you intend to use raw disk devices, see ‘‘Tuning ORACLE under UNIX’’ in your 

ORACLE Installation and Configuration Guide. 

Creating an ORACLE SID 

Use the LINC Database Management Utility (DMU) to create ORACLE SIDs. DMU is 

installed as part of LINC Deployment. 

To create a new ORACLE SID, 


 

The main DMU menu is displayed. 

2. Select option 3, Change or Set ORACLE_SID. You are asked for the name of an 

ORACLE SID. 

3. Enter the name of your new ORACLE SID. 

You are notified if the ORACLE SID does not exist, and asked whether you want to 

initialize it. Answer Y. The main DMU menu is redisplayed for the ORACLE SID you 

specified. 

4. Select option 2, Perform Database Administration Functions on the whole 

ORACLE_SID. The ORACLE Administration Functions menu is displayed. 

5. Select option 3, Initialize an ORACLE_SID. You are asked for the password 

associated with the ORACLE DBA username. Enter this password. 

6. Name any additional control files you want to create for the ORACLE SID. See 

‘‘Guidelines for Creating ORACLE SIDs’’, earlier in this section. 

7. Specify the number of 2 KB database buffers. See ‘‘Guidelines for Creating ORACLE 

SIDs’’, earlier in this section. 

8. Specify the name (location), size, and Tablespace name of one of the database files. 

See ‘‘Guidelines for Creating ORACLE SIDs’’, earlier in this section. Add additional 

database files and Tablespaces after the ORACLE SID has been created. 

9. Enter the name (location) and size of the Redo Log files. See ‘‘Guidelines for Creating 

ORACLE SIDs’’, earlier in this section. 

The ORACLE SID is created. 

10. Indicate whether you want to change the passwords for the SYS and SYSTEM 

ORACLE usernames. If you have a requirement to do so, enter Y and then the new 

passwords. If you do not want to change the passwords, enter N. 

The ORACLE SID is shut down and warm started. 

11. Indicate whether you want to grant privileges to the users LINC and LINCINQ. Ifthe 

ORACLE SID is to be used for LINC purposes, you must answer Y. 

12. Indicate whether you want to create rollback segments. Answer Y and name the 

rollback segment you want to create. 

A-6 v


13. Enter the size and minimum number of extents for the rollback segment. See 

‘‘Guidelines for Creating ORACLE SIDs’’, earlier in this section. 

14. Set the Optimal Size parameter to the rollback segment size. If the rollback segment 

grows larger than this size during a transaction, ORACLE will shrink it back to its 

Optimal Size when any transactions using the larger rollback segment are committed. 

15. Indicate whether you want to create LINC System tables in the ORACLE SID. Answer 

Y to create the tables. Answer N to defer this process (see your LINC 

Administration and Operations Guide for the UNIX Operating System for the use 

of DMU to create the tables). 

After the ROC, ADHOC, and other system tables are created, you are returned to the 

ORACLE Administration Menu. 

16. Indicate whether you want to change the password for the LINC and LINCINQ users. 

You must know the root password to perform this operation. 

17. Add any additional database files and Tablespaces you need. 

18. Enter 99 to exit DMU. 

v A-7

Creating Griffin Universes 


Before You Start 

Before you begin the process of creating a Griffin Universe, you need to gather the 

following information: 

$ Password for the Griffin DBA username. The password is required to allow access to 

the functions and privileges of the username. 

$ Name of the new Griffin Universe. See ‘‘Choosing Names for ORACLE SIDs and Griffin 

Universes’’, earlier in this section. 

$ Configuration information for the Griffin Universe: 

v Whether Archiving is to be used 

v Maximum number of Griffin servers 

v Number and location of Tablespaces 

v Name and size of each Tablespace 

v Number and location of Griffin database files 

v Name, size, and Tablespace name for each Griffin database file 

v Number and location of Griffin audit files 

v Name and size of each Tablespace name for each Griffin audit file 

v Number of Audit Arms 

See ‘‘Guidelines for Creating Griffin Universes’’, later in this section. 

Note: Table, Index, Audit Arm, and Tablespace names are converted to lowercase for 

use with Griffin. 

In addition to the above information, you must have installed LINC Deployment and set up 

environment variables. See Section 2. 

Guidelines for Creating Griffin Universes 

Use the following points as a guide for the minimum requirements for your Griffin 

Universe. 

$ Whether Archiving is to be used 

Choosing this function means that you are required to back up Audit Arms on a regular 

basis, so that recovery can be guaranteed. See the recovery section of your Griffin 

Data Engine Installation and Administration Guide for details and requirements of 

archiving. 

A-8 v


You should consider enabling this function for your production systems. However, you 

should be aware that Griffin does not automatically archive Audit Arms, and that when 

all Audit Arms are ready to be archived, you are required to intervene manually. 

$ Maximum number of Griffin servers 

You will need four Griffin servers (for the LINC lcp, Griffin Utility, audit daemon, and 

monitor daemon), plus one for each LINC Server, plus two if you are using the LINC 

Report Output Control System (ROC), plus one for each concurrent LINC Report that 

is to be run. 

Note: The number of Griffin servers affects the number of semaphores 

required during creation of Griffin Universes. If you specify too 

high a value, the creation of the Griffin Universe may fail. 

$ Number of Griffin database files, and the name, size, and Tablespace name for each 

Griffin database file 

Griffin database files are the names (locations) of UNIX files or raw disk partitions 

used to store data for the Griffin Universe. Tablespaces are logical groupings of Griffin 

database files. 

The number and size of your Griffin database files will depend on the amount of data 

to be stored. See your Griffin Data Engine Installation and Administration Guide 

and the following notes on space requirements for guidelines. You will need a 

minimum of 40 MB of space for Tablespaces for LINC Generate, and 8 MB of space for 

LINC System Tables. 

$ Number of Griffin audit files, and the name, size, and Tablespace name for each Griffin 

audit file 

Griffin audit files are the names (locations) of UNIX files or raw disk partitions used to 

store transactions and audit information for the Griffin Universe. See your Griffin 

Data Engine Installation and Administration Guide and the following notes on 

space requirements for guidelines. Additional space is required if LINC Report Output 

Control System (ROC16) and LINC Ad Hoc Inquiry Utility (ADHOC16) structures are 

included. See ‘‘Changing LINC Structures in Tablespaces’’ later in this section. 

$ Number of Audit Arms 

Audit Arms are used for recovery purposes. At least two Audit Arms are required, and 

four are recommended for use with LINC Systems. Four 15 MB Audit Arms are 

required for LINC Generate. At least 8 MB of space are required for LINC System 

tables in runtime Griffin Universes. These requirements will increase as LINC Systems 

are created, generated, and run. 

See also ‘‘Tuning the Configuration of Griffin Universes’’, later in this section. 

The amount of space required by a Griffin Universe will be affected by the following: 

$ Size of the LINC Databases stored in a runtime Griffin Universe 

$ Size of the database for the LINC Report Output Control System (ROC) in a Griffin 

Universe 

$ Size of data for the LINC Ad Hoc Inquiry Utility 

v A-9


$ Size of the LINC Specifications stored in a development Griffin Universe 

Note: You can use GMU to increase the size of your Griffin Universes. For details of 

GMU, see your LINC Administration and Operations Guide for the UNIX 

Operating System. 

Creating a Griffin Universe 

Use GMU to create Griffin Universes. GMU is installed as part of LINC Deployment. 

To create a new Griffin Universe 


 

The main GMU menu is displayed. 

2. Select option 3, Change or set Griffin Universe. You are asked for the name of a 

Griffin Universe. 

3. Enter the name of your new Griffin Universe. 

You are notified if the Griffin Universe does not exist and asked whether you wish to 

initialize it. Answer Y. The main GMU menu is redisplayed for the Griffin Universe 

you specified. 

4. Select option 2, Perform Griffin Administration. The Griffin Administration 

Functions menu is displayed. 

5. Select option 3, Create a Griffin Universe. You are asked for the password 

associated with the Griffin DBA username. Enter this password. 

6. Enter Y if you want Archiving to be turned on for the Griffin Universe. Enter N if you 

do not want to enable Archiving. See ‘‘Guidelines for Creating Griffin Universes’’, 

earlier in this section. 

7. Enter the maximum number of concurrent Griffin servers, in the range 5 through 500, 

and press Return. The default is 15. See ‘‘Guidelines for Creating Griffin Universes’’, 

earlier in this section. 

8. Enter the number of Griffin database files, in the range 1 through 100, and press 

Return. The default is 1. See ‘‘Guidelines for Creating Griffin Universes’’, earlier in 

this section. 

9. Ensure the default name, size, and Tablespace for each Griffin database file are 

correct. 

$ Enter N and press Return to accept the displayed values. 

$ Enter Q and press Return to cancel the definition of this Griffin Universe. 

$ Enter Y and press Return if you want to change the values. You will be asked to 

change the values for the name, size, and Tablespace. See ‘‘Guidelines for 

Creating Griffin Universes’’, earlier in this section. 

A-10 v


10. Enter the number of Griffin audit files, in the range 1 through 100, and press Return. 

The default is 1. See ‘‘Guidelines for Creating Griffin Universes’’, earlier in this 

section. 

11. Ensure the default name, size, and Tablespace for each Griffin audit file are correct. 

$ Enter N and press Return to accept the displayed values. 

$ Enter Q and press Return to cancel the definition of this Griffin Universe. 

$ Enter Y and press Return if you want to change the values. You will be asked to 

change the values for the name, size, and Tablespace. See ‘‘Guidelines for 

Creating Griffin Universes’’, earlier in this section. 

12. Enter the number of Audit Arms, in the range 2 through 100, and press Return. The 

default value is 2. See ‘‘Guidelines for Creating Griffin Universes’’, earlier in this 

section. 

13. Enter Y and press Return, if you want to check the configuration values, to repeat all 

of the previous questions. 

Enter N and press Return to accept the current values. The name of the configuration 

file is displayed. 

14. Enter Y and press Return to create the Griffin Universe. 

Enter N and press Return to abandon the creation. 

15. Enter 99 to exit GMU. 

v A-11

Tuning ORACLE SIDs 


Default Configuration of ORACLE SIDs 

The following table shows the parameter values for an ORACLE SID created by the LINC 

Database Management Utility (DMU). 

Parameter Value 

db_block_buffers 1000 

db_block_size 2048 

db_files 20 

dml_locks 300 

enqueue_resources 650 

log_buffer 32768 

open_cursors 250 

processes 25 

shared_pool_size 6000000 

sort_area_size 1024000 

Tuning the Configuration of ORACLE SIDs 

Guidelines for Configuring ORACLE SIDs 

For maximum performance, set the ORACLE parameter log_checkpoint_interval to a value 

larger than the Redo Log file size. This will trigger a checkpoint only when log file switches 

occur. 

Setting a value smaller than the Redo Log file size reduces the amount of work required in 

the event of an ORACLE failure, but causes more frequent checkpoints, resulting in greater 

runtime overheads. 

Enable Redo Log Archiving and set the ORACLE parameters log_archive_start and 

log_archive_dest if automatic Redo Log Archiving is required. 

Note: Multiple LINC Deployment Systems may coexist in the same ORACLE SID. 

Configuration of an ORACLE SID must take into account the sum of 

requirements for all LINC Systems in that ORACLE SID. 

For a discussion of Redo Log files, see your LINC Administration and Operations Guide 

for the UNIX Operating System. 

A-12 v

See also the descriptions of the init.ora parameters in the ORACLE8 Server 

Administrator’s Guide. 

db_block_buffers 

dml_locks 


The default values that are configured in the installation of LINC Software have been 

determined to be most suitable for the typical required performance of LINC Software. 

These values take block size into account, and represent a minimum of 2 MB of 

bufferspace for LINC Generate and 1 MB for LINC Deployment. 

You can choose to amend these values, but you may experience performance degradation 

if the values are decreased. 

Increasing the default values will have a significant, favorable impact on performance, but 

at the expense of extra shared memory requirements. 

If you change db_block_buffers, use the SQL*DBA monitor command to monitor the 

number of physical reads/writes compared to logical reads/writes. 

This parameter defines the maximum number of DML locks held simultaneously. Set 

dml_locks to 1 for each table modified in a concurrent transaction. 

enqueue_resources 

This parameter defines the number of resources that can be locked by lock manager. 

Set enqueue_resources to 120 percent of the sum of the maximum number of DML locks 

and the maximum number of parse locks held simultaneously. 

log_archive_dest 

Set this parameter together with log_archive_start. 

log_archive_start 

log_buffer 

This parameter invokes automatic archiving when Redo Log Archiving is enabled. 

Set this parameter together with log_archive_dest if automatic Redo Log file Archiving is 

required. See your LINC Administration and Operations Guide for the UNIX Operating 

System for a discussion of archiving Redo Log files. 

v A-13


This parameter determines the size (in bytes) of the Redo Log buffer for the ORACLE SID. 

Larger values generally reduce the number of accesses (I/O) to the log file. 

log_checkpoint_interval 

open_cursors 

processes 

For maximum performance, set the parameter log_checkpoint_interval to a value larger 

than the Redo Log file size. This triggers a checkpoint only when log file switches occur. 

Setting a value smaller than the log file size will cause more frequent checkpoints (thus 

having a greater runtime overhead) and reduce the amount of work required in the event of 

an ORACLE failure. 

Set open_cursors to a value greater than the cursor pool size plus ten. For maximum 

performance, cursor pool size should allow all the cursors used in the system and reports 

to remain open. 

The number of cursors required depends on 

$ The number of Components and Profiles used 

$ The types of database accesses used on each Profile (for example, DETERMINE; 

EVERY and DETERMINE; FROM LINC logic commands) 

$ The number of Ordinates declared for each Profile 

The maximum value of open_cursors is 255. 

LINC allocates a default cursor_pool value of 40 for LINC Systems, and 200 for LINC 

Generate. The maximum value of cursor_pool is 200. 

Note: The value 100 is used for all LINC Reports. 

The cursor pool size value can be altered dynamically in a LINC System, using the LINC 

System command :CPS. 

For more details about cursors, see ‘‘Allowing for Cursors’’, later in this section. 

Set this parameter to a value more than ten greater than the number of concurrent 

processes of your LINC System. 

The number of concurrent processes includes 

$ Six ORACLE background processes 

$ One process for each user of the LINC System (if not in LINC server mode) 

A-14 v

esource_limit 

$ One process for each server (if in LINC server mode) 


$ Two processes for every recoverable Report running against the LINC System 

$ One process for every other LINC System potentially using external Automatic Entries 

(HUB) to communicate with this LINC System 

$ One process for monitoring and recovery 

Set resource_limit to true if you want to enforce a read limit for the SQL Views feature. 

See your LINC Administration and Operations Guide for the UNIX Operating System 

for details of the SQL Views feature. 

shared_pool_size 

Set shared_pool_size to 3500000 for a small ORACLE SID, 6000000 for a medium 

ORACLE SID, and 9000000 for a large ORACLE SID. See the ‘‘Memory Structures and 

Processes’’ section of the ORACLE8 Server Administrator’s Guide for further 

information. 

Allowing for Cursors 

A cursor is a work area used by ORACLE to contain a query and its results. One cursor is 

associated with each ORACLE data manipulation statement used. 

The cursor pool size is the number of concurrently open cursors maintained by LINC. An 

open cursor remains open until the cursor pool is exhausted. At this point, the next request 

to open a cursor will result in a search for the most appropriate cursor to replace. 

Frequency of use, recent use, and cost to reopen the cursors are taken into account. 

Cursors are marked ‘‘in use’’ only when being used by an iterative data access by the 

DETERMINE; and LOOK.UP; commands. 

Size of the Cursor Pool 

Generally, each inquiry function on a Standard Component (using a LOOK.UP; command, 

for example) uses one cursor. An update function on a Standard Component (using a 

FLAG; command, for example) uses another cursor. DETERMINE; commands on Profiles 

generally use one cursor for every Profile Ordinate. Conditional Profiles use an additional 

three cursors if the contents of the Conditional Profile table are being updated (using a 

FLAG; command, for example). All Profiles over Events are Conditional Profiles. 

You can control the cursor pool size for a LINC System, by using the LINC System 

command :CPS. For more details, see your LINC Administration and Operations Guide 

for the UNIX Operating System. 

When running in LINC server mode, the setting of the cursor pool applies to the whole 

system. 

v A-15


Obtaining Maximum Performance 

For maximum performance, cursor pool size should allow all the frequently used cursors 

in LINC Systems and Reports running in the ORACLE SID to remain open. 

The cost of a large cursor pool is the use of additional memory. 

You can use the ORACLE MONITOR utility to assist you to determine the most appropriate 

number of open cursors. 

Changing LINC Structures in Tablespaces 

If you use DMU to create system tables, all LINC Ad Hoc Inquiry Utility (ADHOC16), LINC 

Report Output Control System (ROC16), and LINC global database (LINCGLB) structures 

will go to the Tablespace which is declared as the ORACLE default for the LINC usercode 

at that time. 

ADHOC16 and ROC16 can subsequently be moved to other Tablespaces using linc16cfg. 

The LINC global database cannot be moved from the default Tablespace. Since ORACLE 

does not allow dropping or reducing of the size of the SYSTEM Tablespace, to place 

ADHOC16 and ROC16 in another Tablespace, defer the creation of LINC system tables 

when you create an ORACLE SID, then set the LINC default Tablespace appropriately 

before creating system tables. The LINC default Tablespace can be changed again after the 

system tables are created. 

To change Tablespaces or populations for ADHOC16 or ROC16, 

1. Log in to your host as root. 

2. Ensure that the LINCIIDIR/bin directory is included in your path. To do this, you can 

enter the following from the shell: 

 

3. Move to the appropriate directory under $LINCIIDIR (ADHOC16 for LINC Ad Hoc 

Inquiry Utility, or ROC16 for the LINC Report Output Control System). 

4. Access the LINC Configure Utility (linc16cfg), and ensure that you are accessing the 

ORACLE version of the utilities and that you will create a new database. See your 

LINC Administration and Operations Guide for the UNIX Operating System for 

details of linc16cfg. 

5. Make Tablespace and population changes as required, and then regenerate the 

database. 

When creating subsequent ORACLE SIDs with the same $LINCIIDIR, follow the above 

procedure. However, if you used linc16cfg to move ADHOC16 and ROC16, you will not 

have to change the Tablespaces again, as linc16cfg uses the same RDML.EXT files you 

modified earlier. You must still change the retain database flag to new database, since 

linc16cfg has not previously created the database in this ORACLE SID. 

A-16 v

Tuning Griffin Universes 

Tuning the Configuration of Griffin Universes 

The main parameters affecting the use of LINC Systems are 


$ shm_size parameter 

The default value for this parameter is 60 KB. If you experience Griffin error 1005, 

increase the value of shm_size. 

$ cache_size parameter 

Increasing the value of this parameter results in increased performance, at the cost of 

increased shared memory and recovery time. A value of 8 MB is recommended for use 

with LINC Systems, provided there is no restriction on the amount of shared memory. 

$ Number of Audit Arms 

The recommended number of Audit Arms is four. If you experience shut downs of 

your Griffin Universes due to Audit Arms wraparound (while running without 

Archiving), increase the size or number of your Audit Arms. 

$ Number and size of Audit Buffers 

$ Number of Servers 

You may need to increase the number of servers if you need to increase the number of 

concurrently running LINC Reports. 

Caution 

The number of Griffin servers affects the number of semaphores required 

during creation of Griffin Universes. If you specify too high a value, the creation 

of the Griffin Universe may fail. 

$ Disk I/O 

The performance of a Griffin Universe is highly dependent on disk I/O. This includes 

the number of I/Os initiated, and the number of bytes transferred with each I/O. Griffin 

configuration parameters directly related to disk I/O are the size and number of Audit 

Arms, cache size, and number of Audit Buffers, and size of each Audit Buffer. 

Note: Disk I/O performs much better on raw disk rather than on regular 

UNIX files. All partitions in a Griffin Universe should be on raw 

disk. 

v A-17


Tuning Griffin 

Audit Arms 

Griffin Universes require at least four Audit Arms each of 15 MB or more. If you configure 

additional Audit Arms, they must be at least 15 MB in size. 

The number and size of Audit Arms that you configure depends on the number of 

concurrent servers that you are running and the amount of audit records each server 

generates. A server is any process that opens a Griffin database; for example, PGEN, SGEN 

and glcp. 

Both the number of concurrent servers and the number of audit records depend on the 

database schema and the type of server activity. 

Checking Size and Number of Audit Arms 

You can check the size and number of audit arms by executing the following Griffin (grfn) 

command: 

 

This command lists details for each Audit Arm. You can calculate the size (in bytes) of 

each Audit Arm by multiplying "num pieces" by "piece size". 

Gathering Statistics 

In order to gather cache and audit statistics, turn on the statistics parameters in the cache 

and audit sections. 

To turn on cache statistics, use the following Griffin (grfn) command: 

 

To turn on audit statistics, use the following Griffin (grfn) command: 

 

To turn on statistics you require execute permission for grfncmd or gsql. 

Cache Configuration 

The cache parameter in your Griffin configuration file is cache_size. This parameter should 

be set initially to at least 1% the size of all your database partitions (but no less than 2 MB). 

For example, if the sum of all your database partitions is 2000 MB, the cache-size should be 

set to 20 MB (2000 times 1 divided by 100). 

A-18 v

Checking the cache hit rate 


To check the cache hit rate, while servers are running execute the following Griffin (grfn) 

command: 

 

If the "normal read only" hit rate is less than 90%, 

1. Increase the cache size by 5 MB to the new size size by using the following Griffin 

(grfn) command: 

 

2. Stop and start your Griffin Universe and servers. 

3. Check whether the hit rate improves. 

4. Keep increasing the cache size by 5 MB (repeat Steps 1, 2, and 3) until the "normal 

read only" hit rate reaches 90% or until the cache size reaches 5% of the size of all 

your database partitions. 

For example, if the sum of all your database partitions is 1000 MB, do not increase 

the cache size beyond 50 MB. At this point the low hit rate could be due to 

unoptimized audit parameters. 

Audit Configuration 

In the AUDIT section of configuration file, 

$ Set the max_size parameter to 0. 

$ Set the max_buffers parameter initially to half the value of max_servers, but to at least 

4. 

$ Set the buffer_size parameter to 32 KB and the block0_writes parameter to 256. 

$ Make sure that the audit daemon is turned on by checking that the min_open 

parameter in the audit daemon section is 1 and the max_open parameter is at least 1. 

Producing statistics 

While your servers are running, execute the following Griffin (grfn) command: 

 

Check "average flushed block size" 

If the "average flushed block size" value is 90% or more, 

1. Increase the buffer_size parameter by 1 KB to the new size size by using the 

following Griffin (grfn) command: 

 

v A-19


Note: Do not increase the buffer_size parameter over 63 KB. 

2. Stop and start your Griffin Universe and servers to action the change. 

3. Check whether the "average flushed block size" value drops below 90%. 

Check "avg number of buffers daemon was behind manager" 

If the "avg number of buffers daemon was behind manager" is more than half the "number 

of buffers", 

1. Increase the max_buffers parameter by 1 to value by using the following Griffin 

(grfn) command: 

 

Note: Do not increase the max_buffers parameter above the value of the 

max_servers parameter. 

2. Increase the buffer_size parameter by 1 KB to size (unless you have already 

increased it when you checked the "average flushed block size")byusingthe 

following Griffin (grfn) command: 

 

Note: Do not increase the buffer_size parameter over 63 KB. 

3. Stop and start your Griffin Universe and servers to make the changes take effect. 

4. Check whether the value drops to less than half the number of buffers. 

Continuing checking 

Repeat your checks of the "average flushed block size" and "avg number of buffers daemon 

was behind manager" until the conditions are satisfied. 

If both these limits have been reached and your performance is still not satisfactory, then 

make sure that you have at least four Audit Arms, each at least 15 MB. 

If performance is still unsatisfactory, look at database-specific performance using GSQL. 

Section 10 of the Griffin Data Engine Installation and Administration Guide is devoted 

to performance tuning using GSQL. The two most important database-specific subsections 

are "Retrieving Statistics on Cache Memory Usage" and "Analyzing Statistics". Thereare 

SELECT statements described in those subsections that may be used to get cache 

information specific to a structure (table or index) in a database including the cache hit 

rate for that structure. 

A-20 v

About "avg number of buffers daemon was behind manager" 


The Griffin audit manager writes audit records into the audit buffers in memory. The audit 

manager writes into audit buffer memory in a circular fashion: when the audit manager 

reaches the end of the audit buffer space, it begins writing to the first audit buffer again. 

The Griffin audit daemon writes audit buffers to disk, freeing audit buffers written by the 

audit manager. If the audit manager is faster than the daemon, the daemon may be "caught" 

by the audit manager. The goal is to minimize the number of times the daemon is "caught". 

The space (in terms of number of buffers) between the buffer that the audit manager is 

currently filling and the buffer that the audit daemon is currently writing to disk varies 

with activity in the Griffin Universe. 

The "avg number of buffers daemon was behind manager" is the average number of buffers 

between the audit manager and the audit daemon during the course of the Griffin Universe 

session. 

Note: If you have not configured an audit daemon, then the "avg number of buffers 

daemon was behind manager" has no meaning. By default you will have an 

audit daemon. 

About Griffin Commands 

Griffin uses the configuration file in the $GRFNDIR/dbs/$GRFNUNI directory. All changes 

must be made to this file using the ALTER grfn command and can be made effective by 

stopping and starting the universe. You do not need to stop and start the universe after 

adding or dropping audit arms. 

Changing LINC Structures in Tablespaces 

When LINC system tables are created for a Griffin Universe, all structures are included in 

the default Tablespace. 

LINC Generate (LINC16DB), LINC Ad Hoc Inquiry Utility (ADHOC16) and LINC Report 

Output Control System (ROC16) can be moved to other Tablespaces by using linc16cfg. 

The LINC global database (LINCGLB) cannot be moved. The default Tablespace can then 

be reduced in size by using the Griffin command processor (grfn) to back up the LINCGLB 

database, drop the Tablespace, create the Tablespace with a smaller size, and restore the 

LINCGLB database. You should ensure that the default Tablespace is empty before 

dropping it. 

To change Tablespaces or populations for LINC16DB, ADHOC16, or ROC16 

1. Log in to your host as root. 

2. Ensure that the $LINCIIDIR/bin directory is included in your path. To do this, you can 

enter the following from the shell: 

 

v A-21


3. Move to the appropriate directory under $LINCIIDIR (LINC16SYS for LINC Generate, 

ADHOC16 for the LINC Ad Hoc Inquiry Utility or ROC16 for the LINC Report Output 

Control System). 

4. Access the LINC Configure Utility (linc16cfg), and make changes to the Griffin LINC 

System as required. See your LINC Administration and Operations Guide for the 

UNIX Operating System for details of linc16cfg. 

5. Use linc16cfg to regenerate the database. 

Subsequent Griffin Universes created with the same $LINCIIDIR will pick up any changes 

made to ADHOC16 and ROC16. The default Tablespace can be created with a size 

appropriate for LINCGLB. 

A-22 v

Glossary 

A 

access class 

For LINC Ad Hoc Inquiry, a particular type of user access to queries, defined by a letter (A 

through Z) or an asterisk (*, for unrestricted access). Also called query class. 

Action line 

A field that appears on most screens in LINC Generate, enabling fast-track navigation to 

required functions. Also referred to as the Action field. 

Ad Hoc Inquiry 

See LINC Ad Hoc Inquiry. 

Automaint Profile 

The Profile of a Multiple Ordinate Memo Component that provides automatic access to the 

records of that Component. See Multiple Ordinate Memo Component, Profile. 

Automatic Entry 

(1) A facility that enables an Ispec to create a record in another Ispec. (2) A facility that 

enables an Ispec to modify an existing record in a Standard Component, Table Component, 

or Multiple Ordinate Memo Component. (3) Not applicable to Copy.From Ispecs. (4) See 

also Automatic Entry buffer, external Automatic Entry, internal Automatic Entry, HUB. 

Automatic Entry buffer 

An area in memory used by the Automatic Entry facility. See Automatic Entry. 

Automatic Lookup 

A process where a Component record is automatically read into memory from the 

database. 

v Glossary-1

Glossary 

B 

banner 

A system-generated page that prints at the start of a Report and provides control 

information about that Report. 

base year 

The year upon which the DATE.CONVERT; command bases relative day numbers. The 

year is defined using the Primary Database Options screen and may be accessed through 

the System Data item GLB.BASE. See relative day number. 

Buildable LINCIIDIR 

The LINC installation directory is defined by the environment variable LINCIIDIR. A 

LINCIIDIR that contains the LINC object packages necessary to build LINC executables 

using object packaging is a buildable LINCIIDIR. A buildable LINCIIDIR is necessary to use 

object packaging to maintain your LINC environment 

Bulk Option screens 

A group of screens in LINC Generate that enable options for several Ispecs, Reports, 

Profiles, or Global Logics to be entered together. 

C 

Change Control 

A method for tracking changes to LINC Specifications in LINC Generate. 

Change identifier 

A alphanumeric value used to identify a single user or user terminal for change control 

purposes. Applies when the Change Identification option is selected for that LINC 

Specification. Contrast with Patch identifier. 

class 

See access class, security class. 

Column name 

For LINC Ad Hoc Inquiry, an SQL term equivalent to data item. 

Component 

(1) A business resource such as a customer, product or vendor. (2) A store of static data 

about a business resource. (3) Consists of a screen layout and associated logic (Pre-Screen 

logic, Pre-LINC logic, and Main logic). (4) Together with Events, Components form the 

fundamental building blocks of a LINC System. (5) See also Ispec, Standard Component, 

Table Component, Memo Component, Multiple Ordinate Memo Component. 

Component Profile 

For LINC Ad Hoc Inquiry, a Profile over one Component. (2) Contrast with Event Profile. 

Glossary-2 v

Glossary 

Component record 

For LINC Ad Hoc Inquiry, an individual database record for a Component. Equivalent in 

SQL terminology to a row. 

COMUS 

For OS 2200 based LINC Systems, a product used to build LINC Deployment before 

installation (see SOLAR). 

Copy.From Ispec 

An Ispec with a screen that has a number of identical recurring lines. Transmission of the 

whole screen produces a separate record in the database for each completed line. See also 

Ispec. 

Critical Point 

(1) A procedure used within a LINC Report to aid in recovery following a system failure. 

(2) Created by using the CRITICAL.POINT; LINC Logic command. 

D 

DAD 

See Data Display. 

Data Attribute 

An attribute of a data item. For example, LENGTH, EDIT, BRIGHT. 

Data Command 

A command that identifies or creates a data item used in a screen layout, LINC Report, or 

logic. 

Data Display (DAD) 

(1) Optional descriptive text for a data item. Used in status messages in place of the name 

of the data item. (2) Defined using the DATA.DISPLAY Data Attribute. 

Data item 

Part of a LINC Specification defined by using the DATA; command in LINC Painter. Used 

to enter, store and display data. 

data item 

The collective term for the variables used to enter, manipulate, store, and display data 

(Data items, Ordinates, Setup Data items, and so on). 

database 

See LINC Database. 

v Glossary-3

Glossary 

Database Management Utility (DMU) 

(1) A LINC Utility that enables you to maintain your LINC Database. (2) Use to perform 

such tasks as changing the amount of disk space allocated to database structures, initiate a 

full or partial database reorganizations (for MCP based LINC Systems), and creating 

ORACLE SIDs and Griffin Universes (for LINC Systems based on the UNIX operating 

system). (3) See also Griffin Database Management Utility (GMU). 

Development System 

See LINC Development and LINC Generate. 

Direct Component 

A Component type that uses a key for direct access to the dataset, saving on the number of 

Input/Output operations. It has a single numeric Ordinate with a maximum of 8 digits. See 

Component. 

Direct Report 

(1) A specific type of Report that uses the LINC Report Output Control System (ROC), and 

which sends output directly to an output device and not to the ROC database. (2) See also 

LINC Report Output Control System. (3) Contrast with Standard Report. 

Display item 

A string of descriptive information displayed on an Ispec screen layout or Report Frame, 

primarily used to inform the user which data items are which. 

DMU 

E 

Editor 

EIF 

See Database Management Utility. 

See LINC Editor. 

Engineering Interim Fixes (EIFs) are used to distribute new features, fixes, customer 

requests and newly validated versions of support software. 

Environmental Options screens 

Screens in LINC Generate that enable you to define options for your LINC Specification 

that apply to the generation on a particular host type. 

Event 

(1) An activity performed by an organization, for example a sale, purchase, or payment. (2) 

A store of data about an activity performed. (3) Consists of a screen layout and associated 

logic (Pre-Screen logic, Pre-LINC logic, and Main logic). (4) Together with Components, 

Events form the fundamental building blocks of a LINC System. (5) See also Ispec. 

Glossary-4 v

Event file 

For LINC Ad Hoc Inquiry, the file containing the Event records. 

Glossary 

Event Profile 

For LINC Ad Hoc Inquiry, a Profile over one or more Events. Contrast with Component 

Profile. 

Event record 

For LINC Ad Hoc Inquiry, an individual database record for an Event. Equivalent in SQL 

terminology to a row. 

Executables 

Executables are one of two methods of distributing LINC to customers. They are the 

compiled set of LINC files which are ready to install and run. Contrast this with Objects. 

external Automatic Entry 

An Automatic Entry to or from an external source, such as another LINC System. See 

Automatic Entry, HUB. Contrast with internal Automatic Entry. 

Extract file 

A non-database (text) file created or read by a LINC Report. 

F 

Fireup Ispec 

A particular Ispec that is displayed on your terminal when you sign on to a LINC System. 

G 

Generalized LINC Interface (GLI) 

A facility that enables a non-LINC program to initiate transactions into a LINC Information 

System. 

Generate Group 

A specified group of Reports that can be generated together. 

Generate Set 

A named set of values for generating a particular LINC System from a LINC Specification; 

for example, for a particular host type. 

GLI 

See Generalized LINC Interface. 

v Glossary-5

Glossary 

Global Data Dictionary 

(1) A data dictionary that controls the use of data items over all LINC Specifications within 

the same LINC Generate. (2) Part of GLOBAL Specification. (3) See also LINC Data 

Dictionary, Local Data Dictionary. 

Global Logic 

(1) Part of a LINC Specification that can be reused in other parts of your LINC 

Specification. (2) Inserted into Ispecs, Reports, or Global Logics by using the INSERT; 

logic command. (3) See Insertable Global Logic, Performable Global Logic. 

Global Setup Data item 

A Setup Data item that can be used by any Ispec or Report logic within a LINC 

Specification. See Setup Data item, Group Global Setup Data item. 

GMU 

See Griffin Database Management Utility. 

Griffin Database Management Utility (GMU) 

The equivalent of the Database Management Utility (DMU) for Griffin. 

Griffin 

Database Management System used as the underlying database software for LINC Systems 

based on the UNIX operating system and LINC Generate. Griffin is produced by Unisys 

Corporation. See also ORACLE. 

Griffin Universe 

A Griffin term for a logical storage area that may contain one or more LINC Databases. 

Equivalent of ORACLE SID. See also Tablespace. 

Group Global Setup Data item 

A Global Setup Data item that is a concatenation of a number of other Global Setup Data 

items. See Global Setup Data item. 

group query 

For LINC Ad Hoc Inquiry, an SQL format query whose output lines are for groups of 

related records (rather than individual records). The group is defined by including a 

GROUP BY clause, or by including group functions (such as MAX, MIN, SUM, and AVG) in 

the select list. 

Group Setup Data item 

A Setup Data item that is a concatenation of a number of other Setup Data items. See Setup 

Data Item. 

Glossary-6 v

H 

Glossary 

highlighting attribute 

An attribute of a data item or Display item that affects its appearance when displayed on a 

screen or printed in a LINC Report. For example, BRIGHT or REVERSE. 

Home position 

Top left corner of the screen. Often used as the position from which commands are 

entered. 

Home screen 

For LINC Ad Hoc Inquiry, the base screen from which the main functions are chosen. 

host list 

(1) The list of valid host types for which LINC Generate can perform reserved word 

checking and generation of LINC Systems. (2) The initial list is specified on installation. (3) 

Can be changed in the GLOBAL Specification, using the Supervisor screen. 

HUB Background Run 

For OS 2200 LINC Systems, a background run that processes external Automatic Entries. 

There is one LINC Background Run for each LINC Deployment. See also HUB. 

HUB 

I 

ICP 

The facility that controls external Automatic Entries between LINC Systems. See 

Automatic Entry, external Automatic Entry. 

See Initial Control Program (for OS 2200 based LINC Systems) and Ispec Control Program 

(for LINC Systems based on the UNIX operating system). 

Initial Control Program (ICP) 

The program that controls the generated Ispec subprograms in OS 2200 based LINC 

Systems. Contrast with Update Program (for MCP based LINC Systems) and Ispec Control 

Program (for LINC Systems based on the UNIX operating system). 

Insertable Global Logic 

A sequence of business rules (logic) and a screen layout that can be copied into any 

number of Ispecs and LINC Reports. Contrast with Performable Global Logic. 

interdatabase access 

The accessing of the database of an OS 2200 based LINC System by another OS 2200 based 

LINC System. 

v Glossary-7

Glossary 

internal Automatic Entry 

An Automatic Entry from within the same LINC System. See Automatic Entry. Contrast 

with external Automatic Entry. 

interrogation point 

For LINC Ad Hoc Inquiry, a regular interval during query execution when the status of that 

query is written to the database. 

Ispec 

(1) A collective term for Components and Events. (2) A contraction of the term Interface 

Specification. (3)See also Component, Event. 

Ispec Control Program (ICP) 

The program that controls the generated Ispec subprograms in LINC Systems based on the 

UNIX operating system. Contrast with Update Program (for MCP based LINC Systems) 

and Initial Control Program (for OS 2200 based LINC Systems). 

K 

Keyword 

A data item that has multiple data entry fields and display items. See also Keyword Term 

Item, Keyword Term Display. 

Keyword Term Display 

The Display item associated with a Keyword. See Keyword. 

Keyword Term Item 

The data item associated with a Keyword. See Keyword. 

L 

LDA 

See LINC Development. 

LDL Listing Utility 

A facility in LINC Generate used for printing a LINC Specification. 

LCOPY Utility 

(1) A utility that provides a means of backing up, maintaining and controlling LINC 

Specifications, on the same or different machines (and host types). (2) Formerly known as 

LINC Copy. 

LINC Ad Hoc Inquiry 

A facility used for making inquiries on a LINC Database. 

Glossary-8 v

Glossary 

LINC Administration Guide 

The LINC manual that contains instructions for administering and operating LINC Systems 

on a particular host type. See the front matter for details. 

LINC Background Run 

For OS 2200 LINC Systems, a background run that controls certain functions; for example 

recovery, report handling, and setting up of Common Banks. There is one LINC 

Background Run for each LINC Deployment. 

LINC Data Dictionary 

A collective name for the Local and Global data dictionaries. See Local Data Dictionary, 

Global Data Dictionary. 

LINC Database 

The database created in the generation of a LINC System. Used for storing data. 

LINC Deployment 

(1) A collective term for the software programs required to operate, control and audit a 

LINC System and its LINC Database. (2) Contrast with LINC Generate. (3) Formerly LINC 

Run Time. 

LINC Development 

(1) PC based development tool for creating and maintaining LINC Business Models (LINC 

Specifications). (2) LINC Business Models are transferred to host based LINC Generate for 

generation and deployment in LINC Deployment. (3) Formerly known as LDA III. 

LINC Development Environment 

A collective term for the tools used to design, develop and generate LINC Systems. 

Includes LINC Development, LINC Generate, and LINC utilities. 

LINC Development System 

See LINC Generate. 

LINC Development Test 

Part of LINC Development that enables testing of your LINC Business Model. 

LINC Editor 

A facility for specifying business rules (logic), expressed using LINC Logic commands and 

text. 

LINC Generate 

(1) The LINC Software used to generate LINC Specifications as LINC Systems for use in 

LINC Deployment. (2) Formerly known as LINC Development. 

LINCIIDIR 

LINCIIDIR is an environment variable specifying the LINC installation directory. 

v Glossary-9

Glossary 

LINC Installation Guide 

The LINC manual that contains instructions for installing and configuring LINC Systems on 

a particular host type. See the front matter for details. 

LINC Interactive Test Environment (LITE) 

(1) Software that enables testing and debugging of LINC Systems. (2) Interacts with LINC 

Generate and LINC Deployment. 

LINC Painter 

A facility of LINC Generate used to define an Ispec screen layout or Report Frame layout. 

LINC Report 

(1) Part of a LINC Specification, generated and used to produce output or to carry out 

specialized batch processing of a LINC Database. (2) Consists of Report Frames and 

Report Main logic, and a number of options that define the operation and output of the 

Report. (3) Many programs in LINC Generate and LINC Utilities are LINC Reports. 

LINC Report Output Control System (ROC) 

A utility that provides control over the output of a LINC Report. 

LINC Run Time 

See LINC Deployment. 

LINC Security Level 

A value from 0 through 9 that is assigned to a specific user or terminal to restrict access to 

various functions. 

LINC Security Module (LSM) 

A utility which provides security facilities for both LINC Generate and LINC Systems. 

LINC Specification 

(1) The source definition of a LINC System. LINC Specifications are stored within LINC 

Generate. (2) The result of specifying a LINC Business Model using LINC Development. (3) 

The source from which a LINC System is generated. 

LINC System 

The set of programs (and database) generated from a LINC Specification. 

LINC System command 

A command to assist in the operation of a LINC System or LINC Report. Formerly known 

as a colon command. 

LITE 

See LINC Interactive Test Environment. 

Glossary-10 v

Glossary 

local Data Dictionary 

A data dictionary that controls the use of data items within a single LINC Specification. See 

also LINC Data Dictionary, Global Data Dictionary. 

locked query 

For LINC Ad Hoc Inquiry, a query that is not available for editing or running because it is 

currently queued for execution, or its execution has terminated abnormally, or it is being 

edited. 

logically deleted 

A term used to describe the status of an Ispec record that has been deleted from a database 

as far as all processes are concerned, but is physically still present. 

LSM 

See LINC Security Module. 

LSM security 

For LINC Ad Hoc Inquiry, the security imposed by the LINC Security Module (LSM). If in 

effect, user access to queries and the limits associated with queries may be restricted. 

M 

Main Logic 

A section of user-specified Ispec logic that is executed after any Pre-LINC logic and LINC 

automatic editing and validating sequences have been executed. 

MAINT 

(1) A System Data item, stored with each record of every Standard, Table, and Multiple 

Ordinate Memo Component, that indicates whether that record is added, changed or 

deleted. (2) A screen field for every Standard, Table, and Multiple Ordinate Memo 

Component used to indicate the database maintenance action request. 

Maintenance Mode 

A Painter facility that enables an existing Ispec screen layout or Report Frame to be 

modified. 

Memo Component 

A Component type that has no Ordinate, and which is used to store data of a memorandum 

nature. See Component, Multiple Ordinate Memo Component. 

Memo Data 

Memo-type, optional Ispec data that is stored separately to the primary Ispec records to 

assist with the optimization of disk usage. Valid for MCP based LINC Systems only. See 

Ispec. 

v Glossary-11

Glossary 

Menu Assistance 

A LINC Painter facility that provides assistance when painting an Ispec screen layout or 

LINC Report Frame. 

menu format query 

A query created using the various selection screens of LINC Ad Hoc Inquiry. Contrast with 

SQL format query. 

MLA 

Module 

See Multiple Language Mode. 

LINC Specification that is a subset of a Module Master. When generated a Module 

produces a complete LINC System. See also Module Master. 

Module Master 

A complete LINC Specification that contains defined parts (Modules) that can be 

generated as separate LINC Systems. See also Module. 

multiple language facilities 

A collective term for the LINC facilities that enable a LINC System to be translated and 

used in up to fifteen different languages, from a single LINC Specification. 

Multiple Language Mode (MLA) 

An facility in a menu of LINC Generate that enables a language name or number to be 

defined. (2) See multiple language facilities. 

Multiple Ordinate Memo Component 

(1) A Memo Component with one or more Ordinates defined by a specified Profile (that is 

sometimes referred to as its Automaint Profile). (2) Similar to a Standard Component, but 

with multiple Ordinates. (3) See also Component, Standard Component and Automaint 

Profile. 

N 

NOF 

NOFORM 

See NOF. 

(1) A facility for interfacing to and from a LINC System, usually to an non-LINC System and 

terminals. (2) The interface to PowerClient uses NOF. 

Non-Formatted Input/Output (NOF) 

See NOF. 

Glossary-12 v

O 

Glossary 

Object Packaging 

Object packaging allows the creation of LINC executables from supplied LINC object files, 

the installation of LINC, the installation of LINC EIFs, and the maintenance of your LINC 

environment. It also allows the creation of new LINC object and executable packages 

which can include supplied EIFs. Packages can be created for distribution and as backups. 

Objects 

Objects are one of two methods of distributing LINC to customers. They are the set of 

LINC object files which must be built into executables on your site before LINC can be run. 

Objects files are built using Object Packaging. Contrast this with Executables 

Offline interface 

A facility for passing batches of high-volume, non-LINC transactions for a LINC System. 

OLTP 

See Online Transaction Processing. 

On Change Statistical Routine 

A statistical routine (for example, AVERAGE;) that can be performed on a data item as 

part of an ON.CHANGE; LINC Logic command. 

Online Transaction Processing (OLTP) 

A generic method for transferring transactions to other systems. 

ORACLE 

Relational Database Management System used as the underlying database software for 

LINC Systems based on the UNIX operating system. ORACLE is produced by Oracle 

Corporation. See also Griffin. 

ORACLE SID 

An ORACLE term for a logical storage area that may contain one or more LINC Databases. 

Equivalent of Griffin Universe. See also Tablespace. 

Ordinate 

The data item of a Component that acts as the unique identifier of one record from 

another. The access path to individual Component records. 

v Glossary-13

Glossary 

P 

pack 

Painter 

patch 

The location in which part of a LINC System or LINC Database is stored. For a LINC System 

based on the UNIX operating system, a pack is either a Tablespace or a UNIX pathname. 

See LINC Painter. 

A set of changes to a LINC Specification made over a period of time by users signing on to 

LINC Generate under a specific patch identifier value. 

Patch identifier 

A number used to identify and group changes to a LINC Specification by one or more 

users. Applies when the patch identification option is selected for that LINC Specification. 

Contrast with Change identifier. 

Performable Global Logic 

A sequence of business rules (logic) that can be executed by any number of Ispecs and 

LINC Reports. Contrast with Insertable Global Logic. 

Pre-LINC Logic 

A section of user-specified Ispec logic that is executed before the Ispec Main logic is 

executed. 

Pre-Screen Logic 

A section of user-specified Ispec logic that is executed before the screen layout is 

displayed on the terminal. 

Primary Database Options screen 

The screen in LINC Generate for setting basic options and parameters for a LINC System. 

The screen displayed whenever a new LINC Specification is being created. 

Product Menu Utility 

Product Menu is a menu driven utility to access object packaging features. See Object 

Packaging for details of the functions that can be performed with Product Menu. 

Profile 

(1) An index to a specified selection of records. (2) A method of providing access to just 

those records that are required to perform a specific function. (3) A functional view of the 

database. 

Profile Data 

A data item that is physically stored in a Profile as well as in its associated Ispec. See also 

Profile. 

Glossary-14 v

Glossary 

Profile Ordinate 

The data item by which a Profile accesses individual records. A Profile can have several 

Profile Ordinates. See also Profile. 

Q 

query class 

See access class. 

Query Compiler 

For LINC Ad Hoc Inquiry, the part of LINC Ad Hoc Inquiry that validates an entered query 

and transforms it to a standard internal code and format. See also Query transformation. 

Query Front End 

For LINC Ad Hoc Inquiry, the part of LINC Ad Hoc Inquiry that allows a query to be entered. 

Query Optimizer 

The part of LINC Ad Hoc Inquiry that selects the most efficient way to access the LINC 

Database for a query. 

Query Output Handler 

The part of LINC Ad Hoc Inquiry that provides facilities to manipulate query output. 

Query Processor 

The part of LINC Ad Hoc Inquiry that interprets the query code and runs the query against 

the LINC Database. 

Query Processor report 

For LINC Ad Hoc Inquiry, the program that performs the functions of the Query Processor. 

This program is a LINC Report. 

query transformation 

For LINC Ad Hoc Inquiry, the process performed by the Query Compiler to convert a 

validated query into a standard internal form. 

queued query 

For LINC Ad Hoc Inquiry, a query waiting (for resources) to begin execution. 

v Glossary-15

Glossary 

R 

relation name 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an 

Event Profile. Also called a table . 

relative day number 

A date expressed as the number of days since January 1 of the base year (which is 

accessible through the System Data item GLB.BASE). The relative day number of January 

1 of the base year is zero. See also base year. 

Report 

See LINC Report. 

Report Frame 

(1) Layout that contains display text and data items, and some associated logic that is part 

of a LINC Report. (2) The logic is executed (often to define the data items in the layout) 

and then the layout is included in the Report output. (3) Report Frames are accessed as 

single units from the logic of Report Frame or from Main logic of the Report. 

Report Initiation Program (RIP) 

An MCP based LINC utility that enables you to execute a line printer Report or terminal 

printer Report in batch mode. 

Report Output Control System (ROC) 

See LINC Report Output Control System. 

resource locking 

A facility of LINC Generate that prevents access to parts of a LINC Specification by more 

than one user at a time. 

ROC 

See LINC Report Output Control System. 

ROC Background Run 

For OS 2200 LINC Systems, a background run that identifies Report output requests and 

spools the output to the required print queue. There is one ROC Background Run for each 

LINC Deployment. 

row 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component record or an Event 

record. 

Run Time Environment 

See LINC Deployment. 

Glossary-16 v

S 

Screen Build mode 

A Painter facility that is used to specify a new Ispec screen layout. 

Glossary 

search expression 

For LINC Ad Hoc Inquiry, a logical expression used in a search list to define records to be 

included in query output. 

search list 

For LINC Ad Hoc Inquiry, the part of a query that determines whether records will be 

included in the output. 

security access 

For LINC Ad Hoc Inquiry, full access to all queries. 

security class 

For LINC Ad Hoc Inquiry, a type of user access to queries. See access class. 

select list 

For LINC Ad Hoc Inquiry, the part of a query that defines the data items to be included in 

the output. 

Setup Data item 

A data item used in memory only for data manipulation by an Ispec or LINC Report. See 

also Global Setup Data item, Group Setup Data item. 

Shadow Report 

Part of a LINC Report used to produce additional output separate from that produced by 

the primary functions of the Report. 

Sleeping Report 

A Report that, by the use of the SLEEP; LINC Logic command, stops executing for a 

predetermined number of seconds or until reactivated by your LINC System. 

SOLAR 

For OS 2200 LINC Systems, a product used to install LINC Software. 

sort expression 

For LINC Ad Hoc Inquiry, a logical expression used in a sort list to define output sort order. 

sort list 

spooler 

For LINC Ad Hoc Inquiry, the part of a query that defines the order of the output. 

See Terminal Printer Spooler. 

v Glossary-17

Glossary 

SQL format query 

AnSQLqueryenteredinfreeformatinLINCAdHocInquiry.Contrast with menu format 

query. 

Standard Component 

A Component type that requires a single Ordinate. See also Component. 

Standard Report 

A specific type of Report that uses the LINC Report Output Control System, and whose 

output is written to the database. Subsequent use of the output is determined by the user. 

See Report Output Control System. Contrast with Direct Report. 

station 

structure 

(1) General term in LINC for method used to identify users. (2) For LINC Systems based on 

the UNIX operating system, station equates to user name, while for OS 2200 based LINC 

Systems, station equates to userid. 

(1) In LINC Generate, part of a LINC Specification that can be selected (for example, for 

printing, copying, or extraction). (2) For LINC Ad Hoc Inquiry, part of a LINC Database 

that can be the subject of a query. 

structure list 

For LINC Ad Hoc Inquiry, the part of a query that defines the structures to be included. 

One of the following: 

$ Component 

$ Event Profile 

$ All Events 

Supervisor 

A facility of LINC Generate enabling administration-level functions. 

System Data item 

(1) Data item that is automatically part of your LINC Specification. (2) Used for accessing 

or setting parameter or control-type data in LINC logic. (3) Some System Data Items are 

stored automatically in your LINC Database (for example, MAINT). 

Glossary-18 v

T 

table 

Glossary 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an 

Event Profile. Also called relation name. 

Table Component 

A Component type that is used to store low-volume, frequently accessed data, such as code 

tables. See also Component. 

Tablespace 

Discrete part of an ORACLE SID or Griffin Universe. Tablespaces in the same ORACLE 

SID or Griffin Universe can be stored on different physical devices. 

Teach Screen 

A user-written screen display of information about an Ispec being used within a LINC 

System, intended to provide online help for users at run time. 

Terminal Printer Spooler (TPS) 

An MCP based LINC Utility that enables users to manipulate the output of a LINC Report 

to terminal printers. 

TPS 

Trace 

See Terminal Printer Spooler. 

(1) A facility to monitor the logic of an Ispec or Report in your LINC System. (2) Enabled in 

LINC Generate. (3) Contrast with LINC Interactive Test Environment. 

Translation Screen 

A copy of an Ispec screen that is modified to create a secondary language version. 

U 

Update program 

A generated program that contains the necessary logic for performing Ispec operations in a 

MCP based LINC System. 

Usage Input 

An Ispec attribute that enables a data item to be entered or displayed on the screen, 

accessed by logic, but not stored in the database. 

Usage Input Ispec 

An Event or Memo Component that is not output to the database, and where Data items 

default to Usage Input. (Individual data items can be set to Usage Inquiry.) 

v Glossary-19

Glossary 

Usage Input-Output 

An Ispec attribute that enables a data item to be entered or displayed on the screen, 

accessed by logic, and stored in the database. 

Usage Input-Output Ispec 

Ispec that is both Usage Input and Usage Output. 

Usage Inquiry 

An Ispec attribute that enables a data item displayed on the screen, but not to be entered 

on the screen, nor written to the database. 

Usage Output 

An Ispec attribute that enables a data item to be written to the database and accessed by 

logic, but not entered or displayed on the screen. 

Usage Output Ispec 

An Ispec that is written to the database, but does not have a screen display. 

V 

Validation EIF 

Validation EIFs are a special type of EIF which provide support for newly validated 

versions of LINC support software such as ORACLE, Griffin, COBOL, and Tuxedo. 

value expression 

For LINC Ad Hoc Inquiry, a logical expression used in an SQL format query to define a 

value, and made up of data items, literals, operators, and functions. 

value logic 

Logic associated with a Dictionary item that determines acceptable values for that item. 

version control 

A method for identifying different versions of a LINC System by version number, 

description, and generation date. 

Glossary-20 v

Index 

A 

applying an EIF, 4-9 

B 

buildable LINC Installation 

creating, 4-3, 4-4 

building executables, 4-12 

C 

creating 

LINC package, 4-13 

cursors in ORACLE 

allowing for, A-15 

cursor pool size, A-15, A-16 

D 

directory 

spool, 4-14 

disk space required, 1-2 

DMU 

for defining ORACLE SIDs, A-5, A-6, A-12 

DYNIX/ptx 

installing LINC Deployment, 2-3 

E 

EIF, 4-11 

applying, 4-9 

installation, 4-8 

validation, 4-9 

environment variables 

defining, 2-5 

executables 

building, 4-12 


extents in ORACLE, A-4 

G 

GMU 

for defining Griffin Universes, A-10 

for starting Griffin Universes, 3-2 

Griffin Universes 

changing LINC structures in Tablespaces, 

A-21 

choosing the number of, A-2 

configuring and tuning, A-1 

creating, A-8, A-10 

guidelines for configuring, A-8 

planning, A-2 

Tablespaces for, A-3 

tuning, A-17 

using GMU to define, A-10 

using GMU to start, 3-2 

H 

hardware required, 1-2 

I 

init.ora parameters for ORACLE SIDs, A-5, 

A-12 

installation 

EIF, 4-8 

validation checks, 2-5 

installing 

LINC Deployment executables, 2-3 

LINC Generate, 3-3 

preparing for, 1-1 

v Index-1

Index 

K 

kernel 

configuring, 1-3 

minimum values, 1-3 

L 

LINC 

building executables, 4-12 

creating a buildable installation, 4-3, 4-4 

creating a package, 4-13 

installing Deployment Objects, 4-3 

installing object packages, 4-4 

LINC Database Management Utility (DMU), 

A-5 

LINC Deployment 

contents of CD-ROM, 2-1 

Griffin Universe for, A-2 

installing, 2-1 

installing executables, 2-3 

ORACLE SIDs for, A-2, A-4 

LINC environment 

maintaining, 4-1 

LINC environments 

typical, 4-1 

LINC Generate 

contents of CD-ROM, 3-1 

Griffin Universe for, A-2 

installing, 3-1, 3-3 

LINC Griffin Database Management Utility 

(GMU), 3-2 

LINC tidy up script 

setting up, 2-5 

M 

memory required, 1-2 

O 

Objects 

creating a buildable LINC installation, 4-3, 

4-4 

installing, 4-3 

installing object packages, 4-4 

ORACLE Monitor, A-16 

ORACLE SIDs 

P 

changing LINC structures in Tablespaces, 

A-16 

choosing the number of, A-2 

configuring and tuning, A-1 

creating, A-4, A-6 

cursor pool size, A-16 

cursors, A-15 

db_block_buffers, A-13 

default configuration of , A-12 

dml_locks, A-13 

enqueue_resources, A-13 

guidelines for configuring, A-4, A-12 

init.ora parameters, A-5, A-12 

log_archive_dest, A-13 

log_archive_start, A-13 

log_buffer, A-13 

log_checkpoint_interval, A-14 

names for, A-2 

open_cursors, A-14 

planning, A-2 

processes, A-14 

rollback segments, A-4, A-5 

shared_pool_size, A-15 

Tablespaces for, A-3 

using DMU to define, A-5, A-6, A-12 

package 

creating a LINC package, 4-13 

removing spooled, 4-14 

spool directory, 4-14 

pre-installation requirements 

disk space, 1-2 

hardware, 1-2 

kernel configuration, 1-3 

for LINC Deployment, 2-2 

for LINC Generate, 3-2 

memory, 1-2 

software, 1-5 

swap space, 1-2 

product menu utility, 4-6 

PTX 


Index-2 v

R 

removing 

spooled packages, 4-14 

rollback segments in ORACLE, A-4, A-5 

S 

Sequent 


software required, 1-5 

space 

disk space required, 1-2 

memory required, 1-2 

swap space required, 1-2 

spooled package 

creating, 4-14 

removing, 4-14 

swap space required, 1-2 

T 

tidy up script 

setting up LINC, 2-5 

typical 

LINC environment, 4-1 

U 

uninstalling, 4-11 

uninstalling EIFs, 4-11 

UNIX kernel 

configuring, 1-3 

minimum values, 1-3 

V 

validation 

during LINC installation, 2-5 

validation EIFs, 4-9 

Index 

v Index-3

Tape 

Fold Here 

Airmail 

Unisys Australia Pty Ltd 

115-117 Wicks Rd 

North Ryde, NSW 2113 

Australia 

Cut along dashed line 

Do Not Staple 

Please Fold and Fasten 

Attention: ACUS Product Information 

Correct Airmail 

Postage Required 

Tape

Addition Deletion 

Revision Error 

Publication title 

Document number 

Comments: 

Name 

Title 

Address 

City 

Help Us To Help You 

Unisys Corporation is interested in your comments and suggestions regarding this manual. We will 

use them to improve the quality of your Product Information. Please check type of suggestion: 

Company 

Date 

Telephone number 

( ) 

State ZIP code

*-*

pm˜ F„¤Fm›˜ —z›¨˜ m'›"dd"›apm˜%˜ pmOaV - Public Support Login ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?