Runtime for ClearPath OS 2200 Installation and Configuration Guide

Unisys e-@ction 

Enterprise Application 

Runtime for ClearPath 

OS 2200 

Installation and Configuration Guide 

Copyright © 2000 Unisys Corporation. 

All rights reserved. 

Level 3R1A 

November 2000 78616323-000 

Unisys

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described 

herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or 

lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described 

in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be 

the result of your use of the information in this document or software material, including direct, special, or consequential 

damages. 

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. 

Notice to Government End Users: The software and accompanying documentation are delivered and licensed as 

“commercial computer software” and “commercial computer software documentation” as those terms are used in 48 

C.F.R. § 12.212 and 48 C.F.R. § 227.7202-1 through 227.7202-4, as applicable. The Government shall receive only those 

rights provided in the standard commercial software license, or where applicable, the restricted and limited rights 

provisions of the contract FAR or DFARS (or equivalent agency) clause. 

Correspondence regarding this publication should be forwarded to Unisys Corporation by addressing remarks to Product 

Information, Australian Centre for Unisys Software, 115 Wicks Road, North Ryde, NSW 2113, Australia. Comments about 

documentation can also be sent through e-mail to linc.pi@unisys.com. 

All terms which may be mentioned in this document 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 

document should not be regarded as affecting the validity of any trademark or service mark. 

Unisys, LINC, INFOConnect, ClearPath, and PowerClient are registered trademarks, and e-@ction and Griffin are 

trademarks of Unisys Corporation. 

EPSON is a registered trademark of Seiko Epson Corporation. 

HP and HP-UX are registered trademarks of the Hewlett-Packard Company. 

IBM, DYNIX/ptx, AIX and RS/6000 are registered trademarks of International Business Machines Corporation. 

JADE is a trademark of Aoraki Corporation Limited. 

Micro Focus and Net Express are registered trademarks of Merant International Limited. 

Microsoft, Windows, Windows NT, and Internet Explorer are either registered trademarks or trademarks of Microsoft 

Corporation in the United States and/or other countries. 

ORACLE and SQL*Plus are registered trademarks of Oracle Corporation. 

SPARC is a registered trademark of SPARC International, Inc. Products bearing SPARC trademarks are based on an 

architecture developed by Sun Microsystems, Inc. 

SQL Server is a trademark of Sybase, Inc. or its subsidiaries 

Sun, Java and Solaris are registered trademarks of Sun Microsystems, Inc. in the United States and other countries. 

UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company, Ltd. 

UnixWare is a registered trademark of The Santa Cruz Operation, Inc.

Contents 

Section 1. Introduction....................................................................... 1–1 

About This Document ....................................................................................1–1 

Purpose .......................................................................................1–1 

Audience .....................................................................................1–1 

Notation Conventions ..................................................................1–1 

Windows 2000 Compatibility .........................................................................1–2 

Unisys e-@ction Branding ...............................................................................1–2 

Enterprise Application Environment Products .............................1–3 

Graphical Interface Workbench Products ....................................1–4 

Enterprise Application Environment Product Information ...........1–4 

Windows Operating Systems ........................................................................1–6 

Section 2. Preparing for Installation of Enterprise Application 

Environment Software .................................................. 2–1 

About Enterprise Application Environment Software .....................................2–1 

Before Installing Your OS 2200 Based System ..............................................2–3 

Hardware Requirements .............................................................2–4 

Checklist for OS 2200 Based System Software .........................2–6 

Other Software Considerations ...................................................2–9 

Installing and Configuring Required OS 2200 System Software ..................2–11 

Configuring and Regenerating Your EXEC .................................2–11 

CMS 1100 and MCB Configuration ...........................................2–15 

UDS Software Configuration .....................................................2–16 

Applying System Software Changes .........................................2–17 

Section 3. Installing Enterprise Application Environment Software.. 3–1 

Installation Procedure .....................................................................................3–2 

COMUS Build Procedure ................................................................................3–3 

Registering the Release Tape with COMUS ...............................3–3 

Changing Default Configuration Parameters ...............................3–3 

Building Your Parameter Changes ...............................................3–5 

Installing Runtime ...........................................................................................3–7 

About the Runtime Release Tape ................................................3–7 

Installing with SOLAR .................................................................3–7 

Installation Modes for Setting Up HUBs ...................................3–10 

Installing Runtime with XTC .........................................................................3–12 

About XTC .................................................................................3–12 

About Shared and Local Application Groups .............................3–12 

Installing Runtime into a Shared Application Group ..................3–13 

Installing Runtime with PAEXEC ..................................................................3–14 

Before Using Runtime ..................................................................................3–15 

78616323–000 iii

Contents 

Starting Your Background Runs ................................................................... 3–18 

Reinstalling Runtime .................................................................................... 3–19 

Installing Additional Copies of Runtime ....................................................... 3–21 

Installing Host Builder .................................................................................. 3–22 

Loading Host Builder from Tape ............................................... 3–23 

Configuring and Installing Host Builder ..................................... 3–27 

Deleting Temporary Files .......................................................... 3–28 

Installing Multiple Copies of Host Builder .................................................... 3–29 

Installing ROC .............................................................................................. 3–30 

Loading ROC from the Release Tape ........................................ 3–30 

Configuring and Installing ROC ................................................. 3–31 

Deleting Temporary Files .......................................................... 3–33 

Deinstalling .................................................................................................. 3–34 

Deinstalling Runtime ................................................................. 3–34 

Deinstalling Host Builder .......................................................... 3–34 

Section 4. Migrating to Release 3R1A ................................................ 4–1 

Migration Procedure ...................................................................................... 4–1 

Using LCOPY ............................................................................. 4–2 

Generating OS 2200 Reports before Migrating .......................... 4–2 

Addressing Migration Issues ......................................................................... 4–4 

Environmental Settings ............................................................... 4–4 

Relational Database Fast Load support ...................................... 4–4 

S_T_N Records in Memory ......................................................... 4–4 

Global Setup Data Blocks ........................................................... 4–4 

Rounding from Compute Commands ......................................... 4–5 

Extract Format for Data Interchange .......................................... 4–5 

Localization ................................................................................. 4–6 

ROC Performance Improvement ................................................ 4–9 

Graphical Interface Workbench Release 3R2 ........................... 4–10 

Generating Your Systems after Migration ................................................... 4–11 

Appendix A. Files Created by Enterprise Application Environment .......A–1 

Conventions Used in This Appendix ..............................................................A–1 

Installing Runtime ..........................................................................................A–2 

File Names ..................................................................................A–2 

RDMS Storage Areas ..................................................................A–2 

Using Special Printing Attributes ................................................A–3 

Installing Host Builder ....................................................................................A–4 

Configuring and Generating Systems ............................................................A–5 

Output from Configure or Generate ...........................................A–5 

Database Files ............................................................................A–6 

Appendix B. COMUS Configuration and SOLAR Installation Parameters 

......................................................................................B–1 

COMUS Configuration Main Menu ................................................................B–3 

General Configuration Parameter Screens .....................................................B–4 

General Configuration Parameter Screen 1 ................................B–4 

iv 78616323–000

Contents 

General Configuration Parameter Screen 2 ................................ B–6 

General Configuration Parameter Screen 3 ................................ B–8 

Processor File Names Screens ................................................................... B–11 

Processor File Names Screen 1 ............................................... B–11 

Processor File Names Screen 2 ............................................... B–13 

Common Bank Attributes Screen ................................................................ B–15 

Work Queue Size ..................................................................... B–15 

Number of Slots ....................................................................... B–15 

Number of Items in the Pool .................................................... B–15 

Pool Size ................................................................................... B–15 

Maximum Number of Systems ................................................ B–15 

Additional I-Language Banks Screen ........................................................... B–17 

HUB Configuration Parameters Screens ..................................................... B–18 

HUB Configuration Parameter Screen 1 .................................. B–18 

HUB Configuration Parameter Screen 2 .................................. B–18 

OLTP Configuration Parameters Screen ...................................................... B–20 

LRSS Configuration Parameters Screen ...................................................... B–21 

COMUS Run Parameters ............................................................................ B–22 

First Build of OS 2200 Based Software ................................... B–22 

Subsequent Builds of OS 2200 Based Software ..................... B–22 

Appendix C. Terminal and Printer Support ............................................ C–1 

Supported Terminal Attributes ....................................................................... C–1 

Foreign Terminal Support .............................................................................. C–4 

Terminals Supported by Enterprise Application Environment .... C–4 

Terminals Not Supported by Enterprise Application Environment 

.................................................................................................. C–4 

How Enterprise Application Environment Determines Terminal 

Types ..................................................................................... C–4 

Customizing the Mapping of PTTYP Values ............................... C–7 

Inserting Your Own Code to Handle Foreign Terminals ............. C–8 

IBM 3270 Terminal Support ..................................................... C–10 

Appendix D. Related Product Information .............................................D–1 

Glossary 

Index 

Related Product Information ......................................................................... D–1 

78616323–000 v

Contents 

vi 78616323–000

Section 1 

Introduction 

About This Document 

Purpose 

Audience 

This document provides instructions for the installation and configuration of OS 2200 

based Enterprise Application Environment Software. 

This document provides step-by-step instructions for installing and configuring OS 2200 

Runtime and Host Builder software at your site. 

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

installation and configuration of one or more of the Enterprise Application Environment 

products. 

The primary audience is presumed to have been trained in installing and configuring 

OS 2200 based Systems, and to be familiar with the operational aspects of their 

installation. 

Notation Conventions 

Italics are used to delimit variables; for example, system. Enter an actual value in place of 

these, as instructed. Square brackets delimit optional values. 

Throughout this document, an HVTIP-imposed limit of 262K words is specified. Where 

this is mentioned, it refers to UCS. 

78616323–000 1–1

Introduction 

Windows 2000 Compatibility 

Developer software is qualified on Windows 2000 Professional, and we see no reason 

why Developer will not work on Windows 2000 Server or Advanced Server. Please note 

the following requirements: 

• Runtime for Windows Operating Systems and Builder Server for Windows Operating 

Systems require Windows 2000 Server when using the SQL Server database in a 

Windows 2000 environment. (This does not affect the ability of SQL Server database 

to operate in a Windows NT 4.0 environment.) 

• Terminal Server requires Windows 2000 Server. 

Unisys e-@ction Branding 

By the end of the year 2000 all Unisys products and services will be named or renamed in 

the Unisys e-@ction Branding schema. The purpose of this initiative is to shift the naming 

of Unisys products and services from component or system level to the solution level. 

Accordingly, the LINC range of products will now be known as the Unisys e-@ction 

Enterprise Application Environment. The PowerClient range will go under the umbrella of 

Unisys e-@ction Graphical Interface Workbench. These names will better reflect the path 

that Unisys is taking to serve the needs of enterprise wide application developers. 

The tables in the following sections identify all former products and published product 

information and map them to their new names. 

Note: The new name for MAPPER is Unisys e-@ction Business Information Server. 

1–2 78616323–000

Enterprise Application Environment Products 

Unisys e-@ction Enterprise Application 

Environment 


Developer 


Builder 

Products 

New Former 

LINC 

LINC Development 

LINC Generate 

Enterprise Application Builder for ClearPath MCP LINC Generate for MCP 

Enterprise Application Builder for ClearPath OS 2200 LINC Generate for OS 2200 

Enterprise Application Builder for the Windows 2000 

and Windows NT Operating Systems 

LINC Generate for NT 

Enterprise Application Builder for HP-UX LINC Generate for HP-UX 

Enterprise Application Builder for DYNIX/ptx LINC Generate for Sequent PTX 

Introduction 

Enterprise Application Builder for Sun SPARC Solaris LINC Generate for Sun SPARC Solaris 

Enterprise Application Builder for IBM AIX LINC Generate for IBM AIX 

Enterprise Application Builder for UnixWare LINC Generate for SCO UnixWare 


Runtime 

LINC Deployment 

Enterprise Application Runtime for ClearPath MCP LINC Deployment for MCP 

Enterprise Application Runtime for ClearPath OS 2200 LINC Deployment for OS 2200 

Enterprise Application Runtime for the Windows 2000 


LINC Deployment for NT 

Enterprise Application Runtime for HP-UX LINC Deployment for HP-UX 

Enterprise Application Runtime for DYNIX/ptx LINC Deployment for Sequent PTX 

Enterprise Application Runtime for Sun SPARC Solaris LINC Deployment for Sun SPARC 

Solaris 

Enterprise Application Runtime for IBM AIX LINC Deployment for IBM AIX 

Enterprise Application Runtime for UnixWare LINC Deployment for SCO UnixWare 

Enterprise Application Runtime Test Environment LINC Interpretive Test Environment 

Enterprise Application Component Enabler PowerClient ActiveLINC 

Enterprise Application Web Enabler PowerClient Web Agent 

78616323–000 1–3

Introduction 

Graphical Interface Workbench Products 

Product 

New Former 

Unisys e-@ction Graphical Interface Workbench PowerClient 

Graphical Interface Developer PowerClient Development 

Graphical Interface User PowerClient Runtime 

Graphical Interface Storage Facility PowerClient Central Storage Facility 

Enterprise Application Environment Product Information 

Product Information 

New Former 

Unisys e-@ction Enterprise Application Ad Hoc 

Inquiry Guide 


Programming Reference Handbook 


Programming Reference Manual 

Unisys e-@ction Enterprise Application LCOPY 

Guide 


Component Enabler Developer’s Guide 


Remote Access Guide 


Developer Installation and Configuration Guide 


Developer User Guide 


Developer Administration Guide 


Developer Version Control Guide 

Localization Instructions for Unisys e-@ction 

Enterprise Application Developer 


Developer Version Control Key Letter 

Unisys e-@ction Enterprise Application Builder 


LINC Ad Hoc Inquiry Operations Guide 

LINC Programming Reference Handbook 

LINC Programming Reference Manual 

LINC Developers Guide: LCOPY 

PowerClient ActiveLINC Developers Guide 

Remote Access to LINC Server Guide 

LINC Development Installation and 

Configuration Guide 

LINC Development and Testing Guide 

LINC Development Administration Guide 

LINC Development Version Control Guide 

Localization Instructions for LINC 

Development 

LINC Development Version Control Key Letter 

LINC Generate Guide 

1–4 78616323–000

Unisys e-@ction Enterprise Application Host 

Builder Guide 

Unisys e-@ction Enterprise Application Host 

Builder Reference Manual: Painter and Editor 

Unisys e-@ction Enterprise Application Builder 

Key Letter 


Runtime for ClearPath MCP Installation and 



Runtime for ClearPath MCP Administration 


Unisys e-@ction Enterprise Application Getting 

Started with Runtime for the Windows 2000 



Runtime for the Windows 2000 and Windows 

NT Operating Systems Administration Guide 


Runtime for the Windows 2000 and Windows 

NT Operating Systems Localization 

Instructions 


Runtime for the Unix Operating System 

Administration Guide 


Runtime for HP-UX Installation and 



Runtime for UnixWare Installation and 



Runtime for DYNIX/ptx Installation and 



Runtime for IBM RS/6000 AIX Installation and 



Runtime for Sun SPARC Solaris Installation 

and Configuration Guide 


New Former 

LINC Generate Operations Guide 

Introduction 

LINC Generate Reference Manual: Painter and 

Editor 

LINC Generate Key Letter 

MCP Based LINC Installation and 


MCP Based LINC Administration and 

Operations Guide 

LINC Deployment for Windows NT Getting 

Started 

LINC Deployment for Windows NT 

Administration and Operations Guide 

Localization Instructions for LINC Deployment 

for Windows NT 

LINC Administration and Operations Guide for 

the Unix Operating System 

LINC on HP-UX Installation & Configuration 


LINC on UnixWare Installation & Configuration 


LINC on Sequent DYNIX/ptx Installation & 


LINC on IBM RS/6000 AIX Installation & 


LINC on Sun SPARC Solaris Installation & 


78616323–000 1–5

Introduction 

Unisys e-@ction Enterprise Application Griffin 

Data Engine Installation and Administration 



Runtime for ClearPath OS 2200 Installation 

and Configuration Guide 


Runtime for ClearPath OS 2200 Administration 



Runtime Test Environment Guide 

Windows Operating Systems 

In the contents of this manual: 


New Former 

Griffin Data Engine Installation and 


OS 2200 Based LINC Installation and 


OS 2200 Based LINC Administration and 

Operations Guide 

LINC Interpretive Test Environment Operations 


• The product Unisys e-@ction Enterprise Application Builder for the Windows® 2000 

and Windows NT® Operating Systems will be referred to as Builder for Windows 

Operating Systems 

• The product Unisys e-@ction Enterprise Application Runtime for the Windows® 2000 

and Windows NT® Operating Systems will be referred to as Runtime for Windows 

Operating Systems 

Please note that no other Windows operating systems, including Windows 95 and 

Windows 98, are supported. 

1–6 78616323–000

Section 2 

Preparing for Installation of Enterprise 

Application Environment Software 

About Enterprise Application Environment Software 

Enterprise Application Environment Software is supplied on two separate release tapes. 

The basic tape contains Runtime and Report Output Control System (ROC). Host Builder 

is supplied on a separate tape. 

Throughout this document, release tape is used as a general term. The particular release 

tape is implied by the subject matter. 

The OS 2200 based System Software consists of the following products: 

• Runtime (mandatory) 

Runtime is the basic product that enables all the other products to run. Runtime 

must be installed before other Software for a release. For a list of the files on this 

tape, see “Installing Enterprise Application Environment Software” on page 3–1. 

• Host Builder 

Host Builder enables you to generate Specifications into Systems. It is itself a System 

that must run within Runtime. There is no need to install it if you plan to develop 

systems on another OS 2200 based machine (or another Runtime on the same 

machine) and transfer the runtime versions here. 

You can use Host Builder on another host and transfer your System to an OS 2200 

based Runtime. 

• Report Output Control System (ROC) 

ROC is a System that controls the output from Reports. It enables you to browse 

Report output online, schedule printing, and print to terminal or site printers. It must 

be installed after Runtime. There can only be one ROC System in a Runtime. 

Additional Information 

Before installing system software, read “Before Installing Your OS 2200 Based System” 

on page 2–3. 

To set up security privileges for your System, see your Unisys e-@ction Enterprise 

Application Runtime for ClearPath OS 2200 Administration Guide. 

Details about installing Software are in “Installing Enterprise Application Environment 

Software” on page 3–1. 

78616323–000 2–1

Preparing for Installation of Enterprise Application Environment Software 

For more information on developing Systems, see your Unisys e-@ction Enterprise 

Application Host Builder Guide. 

2–2 78616323–000


Before Installing Your OS 2200 Based System 

This subsection describes the issues you should consider before installing your OS 2200 

based System Software. 

It covers the following topics: 

• Hardware Requirements 

• Checklist for OS 2200 Based System Software 

Lists the mandatory and optional software that you should install as your first 

preinstallation task. 

• Other Software Considerations 

Covers issues you should consider if you use Intersystem Communications (HUB), 

UCS Subsystems, or OLTP. 

Note: For information on changes to system software levels, see PLE 15106301. 

78616323–000 2–3


Hardware Requirements 

The following hardware is necessary to use an OS 2200 based System. The size 

estimates are exclusive of any other existing software. 

Host 

To run Runtime or Host Builder, you require a 2200 Series machine (specifically a 2200/ 

300, 2200/500, 2200/700, or 2200/900) or a ClearPath IX machine. 

Memory 

To run Host Builder as well as your own Systems, nine to eleven million words of memory 

are required, with three to four million words reserved for TIP memory. TIP memory is 

dynamic and does not need to be configured. 

These memory requirements do not allow for other external Systems or other 

development activity. 

Disk Storage 

The basic Runtime requires a minimum of 3,000 tracks of disk storage. If you use ROC, 

you should increase this to a minimum of 10,000 tracks. Host Builder needs 

approximately 100,000 tracks when it is initially installed. 

Note: The disk storage figure for Host Builder assumes that you have selected the 

Override REM Pack Initial Reserve field when configuring your Host Builder. For 

more details about this option, see your Unisys e-@ction Enterprise Application Runtime 

for ClearPath OS 2200 Administration Guide. 

Terminals Supported 

This release supports any of the following terminal types: 

UTS 20 UTS 20L UTS 20R 

UTS 30 UTS 40 UTS 60 

UTS 60I SVT 1120 SVT 1121 

LT300 DS7 IBM 3270 group of 

terminals 

SNA3270 logical 

terminals 

PCs with UTS terminal 

emulation software 

Note: Enterprise Application Environment supports the LT300 terminal, operating in 

SVT1121-compatible mode. The LT300 is an internationalized terminal with multiple 

character set capabilities, and it supports many of the ISO 8859 8-bit character sets. 

The LT300 terminal type is recognized by the :STN colon command, and is a valid value for 

the GLB.STYLE System Data item. 

2–4 78616323–000


CMS and MCB recognize the LT300 as a supported terminal type, and identify the Coded 

Character Set (CCS) for each message from the LT300. The Coded Character Set is a oneto-one 

mapping of characters in a character set to their internal binary representation. 

Enterprise Application Environment stores the CCS identifier (CCS ID) for the input 

message in the GLB.CCS System Data item. 

Other Peripherals 

You will require a line printer and tape drive. 

78616323–000 2–5


Checklist for OS 2200 Based System Software 

This subsection details the mandatory and optional OS 2200 based System software, 

release SB8 (CP IX 4.1 or higher). You should install this software as your first 

preinstallation task. For system software installation details, see “Installing and 

Configuring Required OS 2200 System Software” on page 2–11. 

Mandatory System Software 

The following system software is mandatory: 

• EXEC 

Enterprise Application Environment supports MHTIP and PAEXEC shared/partitioned 

applications (and local applications). 

• TIP Utilities 

• CMS1100 

• UDS control (UDSC) 

• UREP and RDMS 

An OS 2200 based System requires only the UREP and RDMS subproducts. These 

are provided under UDS, but also operate with the full UREP and RDMS products. 

(Due to the use of FastPath, the RDMS STATISTICS option is not supported.) 

• IRU 

• MCB 

• SOLAR 

• ACOB 

– You must install the full ACOB Compiler and the C$DML ACOB Common Bank. 

– The ACOB compiler must be installed as non-flagging. 

– The Field data DML Common Banked library must not be used. 

If you require the Field data DML Common Banked library for existing external 

Systems, you must install a second, alternative ACOB Compiler. See your 

OS 2200 ASCII COBOL Installation Guide for information on installing alternative 

Compilers. 

– As part of the 2200/500 product deliverables, you will receive the ASCII COBOL 

compiler. This compiler must be installed. 

Caution 

Unless the ASCII COBOL compiler has been licensed, no other use for this 

compiler is authorized. In this context, other use includes compilation or 

execution of user-written externally generated programs. 

2–6 78616323–000


• UCOB 

• MAP 

• PCIOS 

• SORT 

• LINK 

• LSS 

• URTS 

• Extended Language Message System (ELMS) 

Optional System Software 

Check the following table to decide if you need to install the optional system software. 

System Software Install This Software If You … 

COMUS Are making changes to the default configuration. 

MAPPER Use a Mapper interface (you need MRI for mapper access to 

OS 2200 Databases). You will need MRI and/or IPFSQL (see 

below). 

MRI Use a Mapper interface (you need MAPPER to process Report 

Extract files in Mapper). 

IPFSQL Use a NOF interface. 

DDP-PPC Use HUB. DDP-PPC is an optional product used with external 

and interhost Automatic Entries, which use the HUB 

mechanism. See “Considerations for Intersystem 

Communications” under “Other Software Considerations” on 

page 2–9. 

PADS Use UCS applications (recommended). 

OLTP-TM2200 Use OLTP. 

OLTP-2PC Use OLTP 2PC. 

OSI-TP Use OLTP multi-host capability. 

UC Use OLTP UCS server systems. 

Relational 

Database Fast 

Load 

Requirements for the Runtime Configuration Process 

When you start to configure Runtime, you will be asked to supply replies to requests 

made by the configuration process. You need the following. (Full descriptions of these 

items are supplied later in this section.) 

• Release tape 

Use the off line utility for database reorganisation, or Fast Load 

Reports. 

78616323–000 2–7


• COMUS Database (you need to create one COMUS database if you are making 

changes to the default configuration) 

• Configuration parameters 

You may find that you can accept most of the default parameters for the configuration 

(especially if you are a new site). However, you may have established naming 

conventions for jobs and files and numbering systems for your BDIs, and so you will need 

to change the parameters. 

The complete parameter set is given in “COMUS Configuration and SOLAR Installation 

Parameters” on page B–1. You should review this appendix, to make sure that you are 

aware of the information you require for the configuration process. 

Requirements for Runtime 

To enable use of commands to control the Background Run and HUB Background Run, 

the userid for each background run must have SSCONSOLE privilege. 

For details of these commands, see your Unisys e-@ction Enterprise Application Runtime 

for ClearPath OS 2200 Administration Guide. 

Requirements for ROC 

To install the Report Output Control System (ROC), you need: 

• An installed Runtime 

• Runtime tape 

• Names used in the Runtime configuration 

– System name for your ROC System 

– Database name for your ROC System 

• VALTAB entry for ROC, containing the following information: 

– ROC Spooler transaction Id 

– TIP transaction number 

– Application group number 

– QPRIORITY node with a QMAX of zero for the ROC spooler transaction id 

You may want to use Freespace files for ROC output, which can give performance 

benefits in a high-volume printing environment. This involves an Exec configuration 

parameter, creating a TIP Freespace control file (FS$SYS) for ROC, and the use of a 

TEMP$SGS parameter for ROC. 

For more details, see “Configuring and Regenerating Your EXEC” on page 2–11 and 

“Installing ROC” on page 3–30. 

Requirements for the Host Builder 

To install multiple copies of Host Builder under your Runtime, you require: 

2–8 78616323–000


• Release tape 

• Unique System name for each copy of Host Builder 

• Unique Database name for each copy of Host Builder 

• HVTIP Library Number and TIP Transaction Number 

There are various configuration options to consider when loading the Host Builder. These 

are target host templates, reserved word lists, automatic edit resequencing, and change 

and resource locking. For more details, see “Installing Host Builder” on page A–4 in 

“Installing Enterprise Application Environment Software” on page 3–1. 

Other Software Considerations 

Considerations for Intersystem Communications 

The external Automatic Entry (HUB) facility provides an easy-to-use method of 

communication between Systems, which can be on the same host, or on different hosts. 

The following table describes the software requirements for HUBs, depending on the 

facilities that you want to use. 

Facility Used 

No external Automatic 

Entries and no ROC 

Active HUB 

Background Run 

Note: The Report Output Control System (ROC) uses external Automatic Entries to 

communicate header information. 

For details of this installation, see “Installation Modes for Setting Up HUBs” on 

page 3–10. 

Considerations When Using UCS Subsystems 

HUB$SGS element 

with LOCALHOST 

and Remote Host 

SGSs 

Configured HUB 

for Runtime 

No No Yes 

ROC Yes No Yes 

External Automatic 

Entries in same 


External Automatic 

Entries on same host 

Interhost external 

Automatic Entries 

Yes No Yes 

Yes No Yes 

Yes Yes Yes 

If you envisage having very large Ispec transactions in your System, you may want to 

consider setting up your System as a UCS Subsystem. The mechanism involves setting 

parameters, and is discussed in your Unisys e-@ction Enterprise Application Runtime for 

78616323–000 2–9


ClearPath OS 2200 Administration Guide. However, at the installation stage of Runtime, 

you have to consider user privileges, because your Runtime must be installed under a 

USER-ID with security attributes that allow the loading of UCS Subsystems. 

Note: UCS Subsystems are supported only on M Series hosts with memory paging 

facilities. 

Considerations When Using OLTP 

Systems may use the Open/OLTP software for the external Automatic Entry facility, 

providing distributed transaction processing across different types of machines and 

networks. 

For details on configuration issues, see your Unisys e-@ction Enterprise Application Host 

Builder Guide. 

2–10 78616323–000


Installing and Configuring Required OS 2200 

System Software 

For the latest information on configuring and installing required system software, see the 

Support web page at http://www.support.unisys.com/. 

Before you commence installing and configuring any OS 2200 based System software, it 

is important that you perform the following tasks where necessary: 

1. Configure your EXEC for the Software, and regenerate if necessary. 

2. Configure CMS 1100 and MCB to facilitate the Software. 

3. Configure UDS software. 

4. Apply any necessary system software changes. 

These tasks are described in the following subsections. 

Configuring and Regenerating Your EXEC 

Configuring EXEC: Deciding on Application Groups 

You must decide which application group or groups your Enterprise Application 

Environment Systems will run in. Consider the following points: 

• If your Systems are to run in different application groups, install Runtime into each 

application group. 

• The default application group for Runtime is UDSSRC, with an application number of 

3. 

• For information on establishing application groups, see your OS 2200 UDS Installation 

and Configuration Guide. 

• To interface with other (including external) Systems, you should install these systems 

into the same application group. If you need some guidelines on deciding whether to 

place systems in different application groups, see your OS 2200 Integrated Recovery 

System, Concepts and Facilities Manual. 

If you intend to interface with external database systems that are under the control of 

UDS, your System must be in the same application group as the external System. If 

you want to interface to a DMS 1100 system, that system must be in the same 

application group under the control of UDS, not DMS 8. 

• You may decide to install more than one Runtime in an application group (especially 

helpful for testing). 

• If you wish to run Runtime in more than one application group, the following products 

must be either configured or installed for each of these application groups: 

– EXEC (to configure extra application groups) 

– IRU 

– CMS (Application configure statements) 

78616323–000 2–11


– TELCON (XEU and DESTSSU statements) 

– MCB 

– UDS Control (UDSC) 

– RDMS (subproduct) 

– RSA 

– UREP (subproduct) 

Configuring EXEC: Creating Application Groups 

You may need to regenerate your EXEC to create an application group in which to run 

Enterprise Application Environment. If you have a General Purpose Tailored EXEC (GPTE), 

an application group already exists. For 2200/400 sites with GPTE, the application group 

number is 3. 

If you do not have an application group, the EXEC must be generated with the appropriate 

STEP control and AUDIT control SGSs to define the required application group. For more 

information and examples, see your OS 2200 EXEC Installation and Configuration Guide. 

Queue Items 

The number of Queue Items allocated for the Application defaults to 250. Since each 

active message requires a queue item, this limit may be exceeded, particularly when a 

large number of MESSAGE; requests are being delivered by the Background run. It is 

recommended that you increase the number of queue items (for example, to 1000) using 

the STEPCONTROL QNBR parameter. This will prevent the application running out of 

queue items. 

You should use a different QPRIORITY node for your Error Notification Program, and 

different ones for each System or group of Systems. 

The STEPCONTROL statement must contain at least one PRIORITY, n, 0 statement, 

where n is the QPRIORITY value. This QPRIORITY value is used when configuring the 

dummy transaction for ROC. A separate PRIORITY statement is required for each of the 

GLI, NOF, or OFFLINE interfaces that you intend to use. 

Using a TIP File to Hold Terminal Records 

If you intend to use an FCSS TIP file to hold your terminal records instead of an RDMS 

table, and the file is RECOVERABLE, you must include ROLLBACK SGS statements. 

Note: If you require the Rollback Page file, it must also be created and registered with 

TIP. For more details, see your OS 2200 EXEC Installation and Configuration Guide. 

If you install a UCS System, and you intend to use an FCSS TIP file to hold your terminal 

records instead of an RDMS table, you must ensure that you have the UCS TIP Primitives 

installed. For details about generating TIP with the required options, see the OS 2200 

Transaction Processing Installation Guide. 

2–12 78616323–000


For more details about using the FCSS TIP file, see your Unisys e-@ction Enterprise 


The required SGS statements are as follows. 

 

The a value is the Application group number, and n is the TIP file number of the Rollback 

Page file, which is used for quick-look storage when FCSS TIP files are updated. 

 

This statement specifies the name of your Rollback Page file. 

 

 

For details about how to calculate the number of words per page (n2), the number of 

memory pages (n3), and the number of file pages (n4), see your OS 2200 EXEC 

Installation and Configuration Guide. 

Calculating Page Size 

To assist in the calculation of page size, the following table shows how the size of 

GLB.WORK affects the terminal record size. The page size must be big enough to contain 

at least one terminal record. The size of GLB.WORK is defined on the Primary Database 

Options screen, and its default is 128. 

Size of GLB.WORK 

(characters) 

 

 

 

 

For full details of these parameters, see your OS 2200 EXEC System Software 

Operations Reference Manual. 

The following example shows statements for setting up a Rollback Page file. 

 

 

 

Size of Terminal Records 

(Words) 

Up to 132 56 

Up to 356 112 

Up to 804 224 

Up to 1700 448 

Up to 3492 896 

Greater than 3492 1792 

78616323–000 2–13


 

 

 

 

 

The STNUTIL program (used in conjunction with defining FCSS TIP Files) commits every 

20 records. You should consider this when calculating the STEPCONTROL ROLLBACK 

WORDS PER PAGE value and PAGES PER TRANSACTION ROLLBACK LIMIT based on 

the size of terminal records. This means that if the ROLLBACK PAGE FILE is defined as in 

the example in the previous step and the size of GLB.WORK exceeds 804 (characters) 

and there are more than 20 records to process, then errors will occur. 

This is based on 896 (words per page) divided by 448 (terminal record size) multiplied by 

10 (pages per transaction rollback limit), giving a result of 20 records. 

In this example, the error would be avoided if the pages per transaction rollback limit was 

increased by 1 to 11. An error has been found on the twentieth record as the Rollback 

page size has its own header information, forcing the twentieth record into the eleventh 

page. 

Configuring EXEC: EXPRGENVIRON Configuration Parameter 

If you are using Host Builder or generating a UCS System, you must set the EXEC 

configuration parameter EXPRGENVIRON to TRUE (the default). 

Configuring EXEC: Parameters for HVTIP 

Ensure HVTIP is turned on. You may need to perform a NEWCON EXEC generate. 

Recommended configuration parameters for HVTIP are listed in the following table. 

Note: For SB6 and above, TIP memory is dynamic and does not need to be configured. 

Parameter Recommended Value Meaning 

HVTIP 64 Number of HVTIP libraries 

TMECRL TRUE Turn on TIP memory control 

TPMEMX 31250 Maximum number of TIP memory blocks of 

64 words (see below) 

TPNRTN 7 Maximum number of nested RTN$s allowed 

For larger systems, TPMEMX will need to be greater than the value listed in this table. 

The recommended value is 31,250 blocks of 64 words, giving a total memory allocation of 

2 million words. 

For more information on HVTIP Memory Allocation, see your Unisys e-@ction Enterprise 


For more details about TIP configuration, see your OS 2200 EXEC Installation and 

Configuration Guide. 

2–14 78616323–000


Configuring EXEC: Non-OS2200 Tapes for LCOPY 

To enable LCOPY to read tapes created on non-OS 2200 hosts, set the following EXEC 

configuration TAG: 

 

This parameter can be changed dynamically. For more details, see your OS 2200 EXEC 

Installation and Configuration Guide. 

Configuring EXEC: Freespace Files 

To enable the use of Freespace files, set the FREESPACE configuration parameter to 

TRUE. (This is applicable to ROC flat files only. For more details, see “Installing ROC” on 

page 3–30.) 

Configuring EXEC: Large Files 

If you want to take advantage of the Large Files option (maximum 262,143 positions), 

set LARGEFILES to TRUE in your EXEC configuration. If you set LARGEFILES to FALSE 

(the default) your files are limited to 4095 positions. 

For details on enabling the feature, see your Unisys e-@ction Enterprise Application 

Runtime for ClearPath OS 2200 Administration Guide. 

CMS 1100 and MCB Configuration 

To configure CMS 1100 and MCB for Enterprise Application Environment: 

1. If you do not already have MCB (Message Control Bank) installed, install and 

configure it for recoverable messages. 

You must install MCB with the Extended Mode options set if either of the following 

conditions apply. 

• Your Systems are to be generated as UCS. 

• You are using Host Builder. 

For more details, see your OS 2200 MCB Installation Guide. 

2. Define the terminals that you intend to use for your Systems to CMS 1100 as TIP 

terminals in a PID configuration statement. 

3. Ensure your MCB has a User Parameter Area of 32 words or less. 

4. Set the UDBASE MCB configuration parameter to the default specified in your MCB 

System Support Reference Manual. (If UDBASE is set lower than the default, it is 

possible that the MCB DBANK will overlap with the DBANK.) 

You can modify the start address of the DBANK. For details, see your Unisys e-@ction 

Enterprise Application Runtime for ClearPath OS 2200 Administration Guide. 

78616323–000 2–15


Trigger Characters 

You can use MCB and CMS Trigger characters. However, since Enterprise Application 

Environment already uses the tilde (~) character for internal use, you should not use it as 

the trigger character for a System. 

UDS Software Configuration 

You must ensure that the MCB BDI and entry-point (as defined when you installed MCB) 

are set in the UDS configuration. If incorrect values are set in the UDS configuration, 

transactions may fail with MCB error 013 on function 2 (initialize). 

When configuring your UDS software you must: 

1. Set the UDS thread control bank to the maximum. If necessary, increase its size by 

entering the following sequence of commands in a Data Dictionary session. 

 

 

 

 

The thread bank size may be changed while your Systems are active, but before 

these changes will take effect, all threads must be stopped. The first thread that 

restarts must not be a TIP thread. 

Set your UDS DCS banks to their maximum size to prevent queuing. For more details, 

see the OS 2200 UDS Installation Guide. 

2. To increase the size of your UDS DCS bank, enter the following sequence of 

commands in a Data Dictionary session. 

 

 

 

 

The bank size may be changed while Enterprise Application Environment is active, 

but the changes will not take effect until a BEGIN THREAD is encountered after UDS 

has been idle; that is, when it has no active threads. For more details about the DCS- 

BANK-SIZE parameter, see the OS 2200 UDS Installation Guide. 

3. If your site has the Data Dictionary subproduct and not the full product, you must 

enter the following commands before installing. 

 

 

 

To determine if you are using the Data Dictionary subproduct, attempt to define an 

entity by entering: 

 

 

If you have only the subproduct, an error message is returned. If you have the full 

product, delete the entity by entering: 

 

 

2–16 78616323–000


Applying System Software Changes 

Some changes must be applied to other OS 2200 based system software before 

installing your Enterprise Application Environment Software. For the latest details, see 

your release information at http://www.support.unisys.com/. 

These changes are supplied on the Runtime Release tape. They are contained in an 

element CHANGES/SBlevel in the first file, where SBlevel is the level of SB software that 

you are currently running (for example, SB5R4). 

The following runstream copies the first file down to a disk file called file. 

 

 

 

Here reel# is the tape reel number and tape is a device that supports the release format 

(for example, U9S or HICL). 

You will need to build and install those products for which there are changes. 

Use the following ECL to load the changes into the COMUS Database, where qualifier is a 

COMUS qualifier, file is a file name, and element the element name. 

 

 

 

78616323–000 2–17


2–18 78616323–000

Section 3 

Installing Enterprise Application 

Environment Software 

This section covers the following topics: 

• Installation Procedure 

• COMUS Build Procedure 

• Installing Runtime 

• Installing Runtime with XTC 

• Installing Runtime with PAEXEC 

• Before Using Runtime 

• Starting Your Background Runs 

• Reinstalling Runtime 

• Installing Additional Copies of Runtime 

• Installing Host Builder 

• Installing ROC 

• Deinstalling 

Related Information 

For information on: 

• Migrating from previous releases, see “Migrating to Release 3R1A” on page 4–1. 

• Removing installed software, see “Deinstalling” on page 3–34. 

• COMUS parameters for installing and configuring and SOLAR Installation parameters, 

see “COMUS Configuration and SOLAR Installation Parameters” on page B–1. 

Before Installing 

Before installing, you must make sure both the Application Group and the MCB are in the 

UP state. If Enterprise Application Environment is configured to use OLTP, the OLTP 

TMSC background run must also be in the UP state. 

78616323–000 3–1

Installing Enterprise Application Environment Software 

Installation Procedure 

Runtime is the basic product that enables all other Enterprise Application Software to run. 

It must be the first product you install. 

If you wish to change the default configuration parameters, you must use COMUS to 

perform a configure and build before you install with SOLAR. If you have not previously 

used COMUS to configure or build, you first need to initialize a COMUS Database. For 

more details, see your OS 2200 COMUS End Use Reference Manual. 

When you install your OS 2200 based Runtime using SOLAR, you perform the following 

steps. (Each of these steps is described in more detail in the following subsections.) 

1. If you want to customize Enterprise Application Environment for your site and change 

the default configuration parameters, you should: 

• Register the Release tape with COMUS. 

• Change the default configuration parameter settings. Full details of the default 

parameters can be found in “COMUS Configuration and SOLAR Installation 

Parameters” on page B–1. 

• Build Runtime with COMUS. 

If you do not change the default parameters, use SOLAR to register and install 

Runtime directly from the Release tape. 

For details, see “COMUS Build Procedure” on page 3–3. 

2. Register the output tape from the build process with SOLAR. 

3. Install Runtime, by using SOLAR. 

Installing Unisys-Supplied Changes 

Unisys supplies changes by distributing EIFs (Engineering Interim Fixes). These changes 

can affect: 

• Runtime 

• Any Enterprise Application Environment component, including the Report Output 

Control System (ROC) and Host Builder 

To install an EIF, see the instructions accompanying the EIF. 

To install changes to Runtime Software, for each copy of your Runtime: 

1. Insert any Unisys-supplied source changes into the COMUS Database. 

2. Repeat the build and install process, merging the changes into the product at the 

Build stages. 

For more details about this process, see your OS 2200 COMUS End Use Reference 

Manual. 

3–2 78616323–000

COMUS Build Procedure 


Use the procedures described in this subsection to customize the installation of 

Enterprise Application Software for your site. 

Registering the Release Tape with COMUS 

To register an OS 2200 based System with COMUS, perform the following steps: 

1. Log on to DEMAND. 

2. Specify the COMUS qualifier, by entering: 

 

The qualifier value is that specified when the COMUS database was created. 

3. Initiate COMUS, by entering: 

 

4. Register with COMUS, by entering: 

 

The reelnum value is the tape identifier of the Release tape. The Release tape is 

unlabeled, and the default tape characteristics are assumed. 

COMUS assigns the tape, and waits for you to mount it. 

When COMUS completes the registration task, it displays the following message: 

 

To check the result of the register process, look at the print files produced under the runid 

that initiated the register. These print files contain information specific to this release, 

including (in the case of an Interim release) the details of all Engineering Interim Fixes 

(EIFs) patched by this release. 

Changing Default Configuration Parameters 

If you do not want to change the default parameter setting, proceed to “Installing 

Runtime” on page 3–7. For more details about the default parameters, see “COMUS 

Configuration and SOLAR Installation Parameters” on page B–1. 

If you want to change some of these parameters, you must perform both the Configure 

and Build stages. 

To change the Configuration parameters for your site, perform the following steps: 

1. To update the configuration parameters for the Runtime, start the configuration 

process by entering the following command: 

78616323–000 3–3


 

A list of the available Configuration Sets is displayed. A Configuration Set is a release 

of a product or a group of products or subproducts which are installed together. There 

may be more than one Configuration Set for a product. For example, if you wish to 

install in more than one application group, you need to create a Configuration Set for 

each application group. 

If your COMUS Database has not been used before, a message is displayed 

indicating that no Configuration Sets exist. 

2. After you have registered, you must create a Configuration Set. 

To create a Configuration Set, enter the following COPY command: 

 

The runtime value gives the Runtime name to be used in the BUILD. 

3. Following the COPY command, COMUS redisplays the Configuration Set Selection 

screen. 

Enter the number associated with the set you have just created, and transmit. 

4. A Product Selection screen is then displayed. This screen is used by Configuration 

sets containing more than one product. 

The display is: 

 

 

5. Enter 1 to select LINC 3R1. 

This displays the Configuration Process Main Menu screen. Throughout the 

configuration process, you may obtain help information by typing a question mark 

character (?) either in the top left-hand corner to obtain general information about the 

whole screen, or in column 1 of a field position to obtain information about that field. 

The Main menu has the following seven options, each of which displays additional 

screens: 

 

 

 

 

 

 

 

6. To display the current values for any of the above groups of parameters, enter the 

associated number from the Main Menu. To change a parameter, overtype its existing 

value on the particular parameter screen. 

Some of the parameters for these options are spread over more than one screen. If 

so, enter a plus sign (+) to display the next screen in the sequence, or enter a minus 

sign (-) to display the previous screen. 

7. When you have made all your changes to a particular screen, transmit to effect the 

changes. Enter BACK to return to the Main Menu to select another group of 

parameters. 

3–4 78616323–000


8. When you are satisfied with all your changes, enter PROCESS, and transmit. You can 

enter this command from any screen. 

To discard the changes you have made, enter the OMIT. The Main Menu is displayed. 

9. Enter END (or E) to terminate the configure process. 

If the configure process was unsuccessful, an error message is displayed. 

10. To terminate the current COMUS session, enter the EXIT command. 

Building Your Parameter Changes 

This task is required only if you have changed any of the defaDult settings for the 

configuration parameters. To build Runtime, perform the following actions: 

1. Start the Build process, by entering the following command during a COMUS 

session: 

 

2. The first time you build Runtime, COMUS asks for some default parameters. Enter 

your required values, or accept the defaults. For more details, see the OS 2200 End 

Use Reference Manual. 

A set of suggested values for your first build is shown in the following table. For the 

full set of parameters, including those required for subsequent builds, see “COMUS 

Configuration and SOLAR Installation Parameters” on page B–1. 

Item Suggested Value or Action 

Runtime name Enter the Runtime name you specified when configuring your 

software 

Project Id LINCBUILD 

Runid BLINC 

Run Options Transmit a space 

Run priority Transmit a space 

Tape equipment For example, U9S or HICL 

Tape assign option TJ for unlabeled 

Generation type TAPE/TAPE 

permanent SGSs Transmit a space 

Maximum 9999 

Maximum pages 99999 

3. During the Build process, the following prompt message is displayed: 

78616323–000 3–5


 

Enter the name of the Runtime you wish to build or, if you are accepting all the 

configuration defaults, simply transmit to accept the default name from the Release 

tape. The default Runtime name on the Release tape is LINC3R1, and the default 

configuration parameters are described in “COMUS Configuration and SOLAR 

Installation Parameters” on page B–1. 

Note: The maximum length of the Runtime name entered in the COMUS 

configuration screens is eight characters. 

If you enter a name, it must be the name you supplied in your General Configuration 

Parameters. 

Note: If you have created a configuration set in COMUS and used the default 

Runtime name in GENERAL LONG PARAMS, this name must be entered to accept the 

values in the COMUS database. If not, the name will be that from the tape. 

4. The Build process creates an ECL runstream. You may view this runstream before 

execution. (If you need to modify the runstream, you must exit COMUS and use an 

editor). When you are satisfied with the runstream, instruct COMUS to start the batch 

job, which generates a new (unlabeled) master tape. (Disk to disk BUILDS are not 

supported.) 

When the BUILD TASK COMPLETED message is displayed, processing is complete. 

5. To determine if the Build was successful, review the output from the batch job and 

check for errors. The output is directed to your default print queue, and the last page 

identifies any errors that have occurred. 

Most of the output is directed to the PRNTF$ file and copied onto the output tape. 

The remaining output is printed. 

3–6 78616323–000

Installing Runtime 

About the Runtime Release Tape 


The Runtime Release tape, supplied as an unlabeled 6250 bpi tape, contains the following 

files. 

Installing with SOLAR 

File File Name Description 

1 CO$UTIL COMUS utility file 

2 UTIL$ Enterprise Application Environment Utilities 

3 ALIB$ Common Bank Absolutes and subsytem object 

modules 

4 OLIB1$ Relocatables and object modules used for Build 

5 OLIB$ Relocatables 

6 OMLIB$ Extended Mode Object Modules 

7 SLIB$ Source elements 

8 PCF$ OS 2200 based System changes 

9 PRNTF$ Build print file 

10–14 ROCSYS Report Output Control (ROC) System Object files 

20 HELPDOC Help Document 

23 GLOBALST Skeletons used by generate 

24 GLOBALSG Skeletons used by generate 

25 CODES Sample CODES file 

26 U$SCRREL Utility Program Screens 

To run the SOLAR installation of Runtime, perform the following steps: 

• Register the Output Tape 

• Install from Registered Packages 

• Modify the Runstream 

• Set Up Special Installation Privileges 

• Check the Installation Verification Procedure (IVP) 

These steps are detailed in the following subsections. 

78616323–000 3–7


Register Output Tape 

To register the output tape from the build process with SOLAR: 

1. From the SOLAR Main menu, tab to the Register field and transmit. 

The Package Information screen is then displayed. 

2. Enter the source media containing the output of the COMUS Build process. For 

example, if you had an unlabeled tape 23792c, you would enter this in the Reel Ids: 

field. 

The Runstream Information screen is then displayed. 

3. Make your required changes. To start the runstream, enter Y in the Do you wish to 

start (@START) the runstream now? field. 

Installing from Registered Packages 

To install Release 3R1A from the registered packages: 

1. From the SOLAR Main menu, tab to the Software Installation: Registered 

Packages field and transmit. 

2. Locate the screen containing Enterprise Application Environment 3R1A. 

3. Move to the Enterprise Application Environment 3R1A tape that you registered and 

press the F8 key. 

4. Move to the Mode you want to install and press the F5 key. 

The Runstream Information screen is then displayed. 

5. Make your required changes. To start the runstream, enter Y in the Do you wish to 

start (@START) the runstream now? field. 

Modifying the Runstream 

If you need to modify the runstream, you must exit SOLAR and use an editor. If you are 

satisfied with the runstream, inform SOLAR to start the batch job. 

The batch job reads the product master tape created by the Build process, and installs 

Runtime. 

Setting Up Special Installation Privileges 

You need special privileges to perform the install process. For example, the MAKE- 

TABLES runstream updates the runtime*PERM$SGS file with Integrated Recovery 

Application information. The runstream therefore needs the necessary privileges in order 

to accomplish this. Check with your site security administrator. 

See the OS 2200 COMUS End Use Reference Manual for a summary of the required 

privileges. The Common Bank Reload privilege is required to install Enterprise Application 

Environment 3R1A. 

3–8 78616323–000


The userid used to install Runtime must have the necessary privileges to perform SOLAR 

installations. See Section 1 of the SOLAR End Use Reference Manual for information on 

the privileges needed. 

Also, the security environment must be set up properly for the LINC$RTS subsystem to 

function correctly. Refer to Appendix A of the OS2200 Software Products Installation 

Guide for guidelines on setting up the security environment for Object Module 

Subsystems. 

Runtime contains both chameleon and protected subsystem types. The userid of the 

owner of the ALIB$ file (which contains the subsystem definition elements) must have 

the following subsystem security attributes. -LINC- is the recommended userid. 

Parameter Value 

User-id Name -LINC- 

Record Access Semiprivate 

Attached ACR Name EXEDEL 

ACR Arguments Execute: Public 

Delete: Userid EQ SUBSYS-ADMIN 

Run Mode None 

Processor Privilege Read Execute GRS 

Access Privilige Trusted 

Sharing Level Application 

Clearance Level Minimum = 0, Maximum = 0 

Compartment Set Maximum = NULL, Default = NULL 

Trusted Privileges None 

Other Priviliges SSGAP 

ERs, CALLs None 

File ACR Name PUBRD 

File ACR Arguments Read: Public 

Checking the Installation Verification Procedure (IVP) 

The Installation process contains an Installation Verification Procedure (IVP). The IVP 

checks that Runtime has been installed successfully by checking that all files, RDMS 

tables, and Common Banks have been correctly set up. 

If the IVP fails, you can check the success of your installation procedure by reviewing the 

output from the batch job, and checking for errors. The output is directed to your default 

print queue, and the last page identifies any errors that may have occurred. 

78616323–000 3–9


The output from the installation will show that a number of elements were created in the 

SOLAR*DIAGNOSTIC file. 

1. Check if there were any errors encountered during the installation. If a problem 

existed, inspect the PL-DIAGINFO/timestamp element with an editor to determine 

the cause of the problem. 

2. Ensure that the complete environment is functioning correctly (including EXEC, MCB, 

and HVTIP) by installing and logging on to the Report Output Control System (ROC). 

Installation of ROC is described later in this section. 

Log on to ROC by entering the ROC transaction name from a TIP terminal. The ROC 

transaction name is specified when Runtime is installed. For more details, see 

“COMUS Configuration and SOLAR Installation Parameters” on page B–1. 

If the ROC Home screen is displayed, Enterprise Application Environment has been 

installed correctly and the IVP is complete. If you cannot display the ROC Home 

screen, contact your local Unisys representative. 

Installation Modes for Setting Up HUBs 

The HUB feature handles external Automatic Entries, including those between hosts. A 

HUB is defined by the LINC$HUB BDI and the HUB identifier in the COMUS 

Configuration Set. One HUB may comprise multiple Runtimes. 

Use the MODE parameter in the SOLAR installation of your Runtime to define which 

Runtime you are installing. 

• If you are planning interhost communication, this procedure must be followed on 

each host; that is, there must be a HUB Common Bank for each host. 

• For interhost Automatic Entries, you are required to supply an element (HUB$SGS) 

containing SGS parameters that define your network host names and addresses. 

This is a post-installation procedure. Full details are provided in your Unisys e-@ction 


One Runtime is nominated as the controller of the HUB. Install this environment first. 

Select the HUB mode on the SOLAR installation screen. 

When additional Runtimes are installed into the same HUB (that is, in the same 

intersystem communication network), select the LINC mode field on the SOLAR 

installation screen. The Runtimes within a HUB are linked by having the same HUB id and 

HUB common bank BDI during your COMUS configuration. 

The default mode is HUB. 

Note the following points: 

• All Runtimes must belong to a HUB. As a result, for the first Runtime you install, you 

must select the HUB mode, even though it may be the only environment to be used. 

3–10 78616323–000


• If you are performing external Automatic Entries between a Release 16.3 (or earlier) 

System and your Release 3R1A System, Release 3R1A Runtime must be used as 

your HUB controller. 

Reinstalling or Switching the Controller 

You may reinstall or switch your controlling Runtime, by performing the following steps: 

1. Ensure that all Background Runs for the HUB are down during this procedure (they all 

share the same common bank). 

2. Install the intended controlling environment. Select the HUB mode. During this 

process, the old controller will be deinstalled if the same BDI value for the LINC$HUB 

common name is used. 

3. When this switch is complete, the old controller must be reinstalled. Select the LINC 

mode. 

78616323–000 3–11


Installing Runtime with XTC 

About XTC 

XTC Systems consist of two or more 2200 Series hosts, special interhost 

communications links such as Host LAN Controllers (HLCs), shared mass storage 

subsystems, and a Record Lock Processor (RLP). The RLP keeps track of what current 

resources are in use. XTC uses the RLP to coordinate shared database operations across 

all hosts. 

XTC TIP 

XTC TIP, through the use of shared application groups, enables you to share TIP and 

HVTIP applications across multiple hosts. This functionality is controlled by the EXEC 

configuration tag MHTIP. Within a shared application, XTC TIP enables you to share 

access to transactions and databases between multiple hosts. 

XTC UDS 

XTC UDS is a facility of Universal Data Systems that permits the sharing of DMS, SFS, 

and RDMS databases across the hosts of an information hub. XTC UDS also uses the RLP 

to track resource usage across all hosts. 

About Shared and Local Application Groups 

Valid OS 2200 based application groups on XTC systems are: 

• Local 

• Shared 

You can install your copy of Runtime into local or shared application groups. When 

configuring the copy of Runtime, specify the application group in which it will run. If the 

application group type is local, Systems that are part of that copy of Runtime will be 

confined to a single host. If the application group is shared, the Systems will be available 

on all hosts. 

Local Application Groups 

Systems in local application groups operate normally, with one exception. 

If your host has MHTIP (XTC TIP) configured, all HVTIP library files must be cataloged on 

shared mass storage, and registered in the shared directory; even if the HVTIP system 

itself operates in a local application group. 

For Enterprise Application Environment Systems, this means that for hosts with MHTIP 

configured, all HVTIP libraries are cataloged on shared mass storage. 

3–12 78616323–000


For Systems in a local application group, it means that the OBJECT PACK specification 

will not be honored for the HVTIP library. Instead, the HVTIP library will be cataloged on 

fixed shared mass storage. This is because the removable disks specified for use in a 

local System are local removable disks. Because of the MHTIP requirement, the HVTIP 

library cannot be cataloged on the same disks as the other object files for the system. 

Shared Application Groups 

When your Enterprise Application Environment System is installed in a shared application 

group, all files (and any defined packs) are cataloged as shared on shared mass-storage, 

and are registered in the shared directory. While your System is operating, XTC UDS uses 

the XPC/RLP to coordinate updates and locks on all hosts. 

Enterprise Application Environment handles all of the details associated with shared 

systems. A shared application group is selected automatically by running in the 

appropriate Runtime. 

Installing Runtime into a Shared Application Group 

In an XTC environment, use SOLAR to install a copy of the Runtime into the same shared 

application group on each host. 

Follow the COMUS configure and build, and SOLAR installation procedures for the first 

host. This first installation creates the RDMS tables for the total environment, on shared 

mass storage. 

The output from the configure/build on your first host is date/time stamped. You should 

install the same output tape on all hosts in the XTC environment. 

When you install it on another host, the system detects from this date/time stamp that 

you are installing the same shared Runtime, and the RDMS tables are not created again. 

If the date/time stamp does not match that for the existing shared environment, then 

RDMS tables are built for a new Runtime. In this case, before you install, you must stop 

all Background Runs on all hosts. 

78616323–000 3–13


Installing Runtime with PAEXEC 

Partitioned applications can be switched between hosts in a PAEXEC environment, 

although an application can only be running on one host at a time. 

You must install Runtime on both of the hosts in the PA EXEC configuration. 

During installation of Runtime, RDMS tables for applications that can be switched are 

catalogued on mass-storage. 

You must ensure that a shared mass-storage device is used in the COMUS configuration, 

if removable packs are used on your hosts. 

3–14 78616323–000

Before Using Runtime 


After installing Runtime, you must perform the tasks outlined in the following subsection 

before it can be used. 

Turn on TIP Transaction Processing 

Use the FB command to ensure that the FB OP$MAIN parameter is on. This effectively 

turns TIP transaction processing ON. For more details, see your OS 2200 TIP Installation 

Guide. 

Create TIP Memory Groups 

TIP memory groups are automatically created within the total available TIP memory, as 

specified in the TPMEMX parameter. You may choose to use the automatically created 

groups, or to change them. There is an overhead if the available TIP memory groups do 

not match the requirements of your Systems. 

Note: For SB6 (and above), TIP memory is dynamic and does not need to be configured. 

Manually changing the TIP memory groups may improve performance, but requires a 

good knowledge of TIP. It is advisable to use the automatically created group, unless you 

have previous experience of tuning TIP memory. 

Changing TIP Memory Groups 

If you decide to change the TIP memory allocation group, ensure that all unwanted 

groups are deleted. 

To establish the TIP memory requirements for your Systems, use the TMINIT Utility to 

monitor current TIP memory group usage. 

Note: Before changing your TIP memory groups, it is advisable to switch transaction 

scheduling off, and wait until all active transactions have been completed. To switch 

scheduling off, enter the following from a system console: FB OFF SCHEDULE. 

The automatic TIP memory group allocation should be used for TIP environments running 

Enterprise Application Environment. However, you may wish to modify TIP memory 

groups to improve utilization of TIP memory. The following discussion provides details 

about memory usage that may help you establish TIP memory requirements. 

There are two important considerations about TIP memory allocation: 

• There must be a memory group allocation big enough to accommodate your largest 

IBANK plus its associated relocatable (RSEG) DBANK. The TIP memory group 

acquired by your ICP has to accommodate not only the DBANK for the ICP, but also 

the DBANKS of any subprograms it uses. As Ispecs are subprograms, a TIP memory 

group must exist that is large enough to accommodate the DBANK for the ICP plus 

the DBANK of your largest Ispec. 

78616323–000 3–15


• There must be sufficient TIP memory, both in terms of total allocation and in the 

number of individual allocations. All Ispecs use TIP memory, and any Reports that use 

external Automatic Entries may also use TIP memory to schedule the resulting 

transaction. 

The exact allocation depends upon the size, complexity, and use of your system. The 

current use of TIP memory can be displayed using TMINIT. For more details, see your 

OS 2200 TIP Installation Guide. 

If your largest non-PCT bank allocated is not large enough, TPUR fails while loading the 

program library. If your DBANK is larger than any non-PCT bank allocated, the first attempt 

to execute the transaction causes an error. 

To decide which TIP memory groups to set up, you will need to know the size of the 

IBANKS and DBANKS of your ICP and Ispecs. This information can be found in the output 

from the @MAP (TPE) or @LINK (UCS) for each Ispec when your System is installed using 

the Generate option of Host Builder, or using the Configure Utility. 

An element exists for each Ispec, each separately compiled Global Logic, and for your 

ICP. The ICP element has the same name as your system transaction id. 

When executing TPUR against your HVTIP library, the LIST option also provides 

information on the bank sizes of your Ispecs. Enter the following ECL to list your HVTIP 

library: 

 

 

The nn value represents your HVTIP library number. By default the TIPRUN$ file tiprun$file 

is named TIP$*TIPRUN$. 

Reload TIP Library and TIP Memory Groups 

If you are already running TIP, you may have a runstream in SYS$LIB$*RUN$ that reloads 

HVTIP libraries after a system reboot. Add to this runstream a reload of the TIP library 

associated with each of your Systems, and a runstream to reset the TIP memory groups, 

as mentioned in “Changing TIP Memory Group”. 

Enter the following ECL to load or reload an HVTIP library: 

 

 

The nn value represents your HVTIP library number. 

If you have the Application Recovery Feature (ARF) turned on (by using the TIP ON 

system keyin), then the reloading of HVTIP libraries and the reestablishing of TIP memory 

allocations are automatic. 

A runstream is available with Runtime to reestablish a System TIP environment. Enter the 

following from a Demand session: 

 

3–16 78616323–000


A message is displayed, prompting you for your system name. Enter the correct system 

name, and its TIP environment will then be recovered. 

Note: If you perform a valtab build or jump key 7 or 13 boot, you need to reestablish your 

TIP environment by running recovery for all your Systems. 

Define a TIP Error Handling Program 

TIP requires an error handling program to receive recoverable messages that cannot be 

successfully processed. The STEPCONTROL EXEC SGS defines the QPRIORITY of the 

error handling program. 

If an error handling program is not created and the STEPCONTROL SGS defines the same 

QPRIORITY for the nonexistent error handling program as for your system, a transaction 

error may stop your entire system. 

A sample of an error handling program is provided in the COMUS file (file1) on the 

Release tape. A sample ECL to map the error handling program is also provided in this 

file. The element names are MCBSE1 and MCBSE1 / MAP. 

To copy file 1 from the Release tape to a file file, where reel is the reel number and type is 

the tape equipment type, execute the following ECL: 

 

 

 

For more details of error handling programs, see your OS 2200 MCB System Support 

Reference Manual. 

Set Default Page Size 

The default page size (MAX-PAGE-SIZE) parameter for the Integrated Recovery Utility 

(IRU) should be set to at least 7168, to allow IRU to back up all the RDMS tables. For 

details of this parameter and how to change it, see your OS 2200 UDS Installation Guide. 

78616323–000 3–17


Starting Your Background Runs 

The Background Run and the HUB Background Run should be active before you install 

and use the other Enterprise Application Environment products. 

To start a runstream, from the system console, enter the following command: 

 

Depending on your software configuration, you may be able to abbreviate the command 

as follows: 

 

The name of the runstream that starts the Background Runs is defined when your 

Runtime software is installed. By default it is LINCBR. This runstream is placed in 

SYS$LIB$*RUN$. For more information, see “COMUS Configuration and SOLAR 

Installation Parameters” on page B–1. 

3–18 78616323–000

Reinstalling Runtime 


You may need to reinstall Runtime for the following reasons: 

• Updating to a new release of Enterprise Application Environment 

• After upgrading your operating system (recommended) 

Procedure for Reinstalling 

To reinstall Runtime: 

1. Ensure that no one is using Runtime while you are reinstalling the product. 

2. Close down all Systems by executing the CLOSEDOWN program, as follows. 

 

3. Terminate the HUB Background Run by entering the following command from a 

operator console: 

 

Here id is the HUB identifier that was specified when configuring Runtime. 

Terminate the Background Run by entering the following: 

 

Here runtime is the Runtime name. 

RDMS Tables 

Caution 

If a new version of Runtime is installed, install Host Builder again, and use the 

Configure from Disk Transfer option. This is described later in this 

subsection. 

The RDMS tables described in the following table are saved at the beginning of the install 

process, and restored on completion. 

Table Contains Details of … Saved As 

runtime_SCHEMA.LSYS All Systems configured 

within Runtime 

runtime_SCHEMA.SECURITY Security that you have 

loaded for all Systems 

within Runtime 

runtime_SCHEMA.SECURINT Security that you have 

loaded for your Host 

Builder 

runtime*SAVE-LSYS 

runtime*SAVE-SEC 

runtime*SAVE-SECINT 

78616323–000 3–19


Table Contains Details of … Saved As 

runtime_SCHEMA.PIDRANGES TIP Stations runtime*SAVE-RANGES 

runtime_SCHEMA.CONFIG COMUS Parameters runtime*SAVE-CONFIG 

runtime_SCHEMA.STNDEFAULT Initial setup information 

for station records 

runtime_SCHEMA.SERVICES Relationships between 

OLTP service names 

and the Systems they 

are part of 

If saved files are found to exist at the beginning of an install, it is assumed that an earlier 

install had failed. The current install will issue a detailed message, and stop. You should 

check the save files. If they are empty, delete them and restart the install. If they contain 

valid data and your system tables are empty, perform the following: 

 

 

Handling Unsaved RDMS Tables 

The data in the following tables is not saved and restored when reinstalling Runtime. 

• runtime_SCHEMA.ACCEPTS 

• runtime_SCHEMA.REPORTINFO 

• runtime_SCHEMA.REPORTSRUN 

• runtime 

runtime*SAVE-STNDEF 

runtime*SAVE-SRVCES 

There can be implications in the fact that these tables are not saved when reinstalling 

Runtime. If you had a Report that went into extended report recovery immediately prior to 

the reinstall, you would lose this Report information when the Report recovered under 

the new Runtime. 

For further information on the tables, see “Files Created by Enterprise Application 

Environment” on page A–1. 

3–20 78616323–000


Installing Additional Copies of Runtime 

You may want to install more than one copy of Runtime. For example, you may wish to 

run Enterprise Application Environment in more than one application group. 

To install an additional copy of Runtime: 

1. Create a new Configuration Set, specifying a different Runtime name and 

Configuration Set name. 

2. Complete the remaining steps for configuring a Runtime (as described earlier in this 

subsection), followed by the Build and Install tasks. 

3. The Runtime name, Common Bank BDIs, and the Background Run id must be unique 

for each Runtime. If you are installing into a different application group, the application 

name and application number must be changed, as well as the Library file names for 

MCB, and RDMS. 

4. If your additional Runtime is to be part of an existing HUB network, remember to 

install selecting the LINC mode. 

78616323–000 3–21


Installing Host Builder 

The Host Builder provides all the necessary tools to specify and generate user Systems. 

For details of the facilities of Host Builder, see your Unisys e-@ction Enterprise 

Application Host Builder Guide. 

To install Host Builder, perform the following steps: 

1. Ensure that Runtime is installed. 

2. Load Host Builder from its Release tape by using the LOAD option of the LRU utility. 

You can change various configuration parameters if required. 

3. Configure and install Host Builder by using the Configure utility. 

4. Ensure files are secured. For a full list of files, see “Files Created by Enterprise 

Application Environment” on page A–1. 

5. Delete temporary files no longer required. 

6. Start your Host Builder as a final check. 

Each of these steps is described in more detail in the following subsections. 

Note: To install Unisys-supplied changes to Host Builder, see the instructions 

accompanying the EIF (Engineering Interim Fix). 

Files on the Host Builder Release Tape 

The OS 2200 based Host Builder Release tape contains the following files. 


1 CONTROL$ Control file 

2 SYSLIB System Control file 

3 TRXREL Transaction relocatables 

4 SCRSYM Source of screen images 

5 SCRREL Relocatables for screens 

6 REPREL Report relocatables 

7 GLOBALSP Skeletons and templates 

8 GLOBALSR Skeletons and templates 

9 GLOBALCO Skeletons and templates 

10 GLOBALSC Skeletons and templates 

11 LIBRARYR Skeletons and templates 

12 SLDACCEPT Skeletons and templates 

13 RELOAD Skeletons and templates 

3–22 78616323–000

Loading Host Builder from Tape 


Load Host Builder from its Release tape by executing the load program, using the 

following ECL format: 

 

The LOAD Utility prompts are displayed one at a time. These prompts and your required 

responses are displayed in the following table. (Default prompt responses are shown in 

angle brackets in the prompt messages.) 

Are Changes Required? 

During the LOAD procedure, the default or current Host Builder configuration is shown. 

You will be prompted: 

 

If you answer Y, you are presented with another set of prompts regarding the following 

features: 

• Target Host Templates 

• Reserved Word Lists 

14 ILANGUAGE Skeletons and templates 

15 START$ ECL for CMP Report 

LOAD Utility Prompt Required Response 

What would you like to 

load? 

Are Changes Required ? 

Y//E(xit) 

Enter 3. 

Enter Y to change options regarding Target Host 

Templates, Reserved Word Lists, Auto Edit 

Resequencing, Change Identification and Resource 

locking Identification, as described following the table. 

Enter N to bypass the prompts associated with these 

options. 

Enter E to terminate. 

Enter the tape reel number Enter the reel number to be used to request loading of 

the Release tape. 

Enter Tape equipment 

Type 


Enter the media type, for example U9S (as the Release 

tape is 6250 bpi). 

Labelled tape Enter N (as Release tapes are unlabeled). 

What System name shall it 

be loaded as? 

Enter the System name for your Host Builder. This may 

be changed later, by using the Configure Utility. 

78616323–000 3–23


• Auto Edit Resequencing 

• Change Control Options 

Additional information on change control settings is contained in your Unisys e-@ction 

Enterprise Application Host Builder Guide. 

Pairs of the angle brackets (< >) contain the default or currently enforced values (except 

for the Change/Resource Control parameters, which default to N). Currently enforced 

values will be shown within angle brackets if the SLDACCEPT file already exists for your 

Runtime; for example, if a Host Builder has already been installed. 

Details about each prompt are given in the following subsections. 

Target Host Templates 

You are asked which target host templates you wish to load. The options are OS 1100, 

ASeries, or UNIX, or an acceptable abbreviation (for example, 1, A, or U). 

Only one set of templates may be loaded. This means that you can only generate 

Systems that target one type of host. 

You can set up the templates for UNIX or MCP based Systems in the OS 2200 based 

environment, if you want to use LCOPY to transfer a Specification to that type of host at a 

later date. 

Note: Once your Host Builder is operational you can change these settings with the 

SUPERVISOR (SUP) command. If you are configuring with Retain Existing Database, 

then the entries you make on this screen 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 your Unisys e-@ction Enterprise Application Host Builder Guide for 

further details. 

Reserved Word Lists 

Reserved Words are loaded for the host you have nominated for Target Templates. You 

can also select one or more of the other available architectures, including Developer. 

You are prompted for each available host type in turn. 

Your reserved word lists are stored in a Common Bank, and therefore the more reserved 

word lists you select, the larger the corresponding memory usage. 

Note: Once your Host Builder is operational you can change these settings with the 

SUPERVISOR (SUP) command. If you are configuring with Retain Existing Database, 

then the entries you make on this screen 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 Unisys e-@ction Enterprise Application Host Builder Guide for 

further details. 

The full list of reserved words is contained in your Unisys e-@ction Enterprise Application 

Developer User Guide. 

3–24 78616323–000

Auto Editor Resequencing 


To allow automatic line resequencing in Editor, respond to this prompt by entering Y. This 

is the default. 

To inhibit automatic Editor resequencing, respond by entering N. 

Once set, this option applies to all Specifications in Host Builder. 

If you turn off automatic Editor resequencing, it will be the responsibility of your 

programmers to manually resequence any lines of code that may require it. If 

resequencing becomes necessary, and you have turned off automatic Editor 

resequencing, an appropriate message is displayed requesting manual resequencing of 

the necessary lines. 

Note: This feature has nothing to do with the RESEQ; command. It applies only to 

automatic line resequencing in Editor. This would usually occur when programmers 

attempt to insert lines at a point where the sequence would have to be changed to 

accommodate these extra lines. 

This facility is most appropriate when a Specification is required to undergo LCOPY 

Create Patch and Merge Patch operations. 

An LDL listing will show the current state of your Auto Editor Resequencing field. 

Change Identification 

Enter Y in this field if you want Change Identification to be enabled for your Host Builder. 

This will identify all changes by your selected Identification Mode. 

Resource Locking 

Caution 

If you answer N to this field, resequencing becomes a manual operation, and 

therefore your responsibility. An Insufficient space for INSERT message is 

issued if lines are inserted that would normally force an automatic resequence. 

This parameter can be changed from the Environmental Options screen once 

your Host Builder is operational, however you would need to reconfigure your 

Host Builder for the change to take place. 

Enter Y in this field if you want Resource Locking to be enabled for your Host Builder. This 

will enable structures to be explicitly locked by users, and remain locked until they are 

specifically unlocked. 

For details of the methods that you can select to identify users when Resource Locking is 

in force, see the Identification Mode field. 

78616323–000 3–25


Identification Mode 

Enter the Identification mode that you wish to use for your Host Builder. This setting is 

only relevant if you have entered Y in either or both the Change Identification or 

Resource Locking fields. 

Enter a value that specifies the method of identifying users of your Host Builder when 

Change Control or Resource Locking is in effect. Values are contained in the following 

table. 

If you specify U, an identifier of LINC will be automatically established for initial access. 

It is expected that your user identifiers will be set up during this initial access by the 

administrator for your Host Builder. 

Patch Identification 

Enter Y in this field if you want Patch Identification to be enabled for your Host Builder. 

This will identify and store all changes under a unique patch identification number, with 

the date and time of the change. 

Audit level 

Enter the level of auditing to be performed for your Host Builder, as shown in the 

following table. 

Specification Administration 

Value Method of Identification 

L Security Module Usercode/Password 

S Station identifier (PID) (default) 

U User defined identifier 

Level Type of Audit performed 

0 No auditing 

1 Audit deletions only 

2 Audit changes. For user logic changes, discard any intermediate changes 

3 Audit all changes 

4 Audit all changes. Include a full image for all structure deletions 

Enter Y in this field if you want auditing to be enabled for your Host Builder administration 

tasks. This will create an audit trail for such activities as generates, Supervisor command 

usage, and LCOPY runs. 

3–26 78616323–000


Reset all Version counts On id change 

Enter Y in this field to automatically reset all System and Report generate counts 

whenever the Version Identifier for the System is changed. For details regarding the use 

of the (optional) Version Identifier, see the Change Control Options screen as described in 

your Unisys e-@ction Enterprise Application Host Builder Guide. 

Reset report version counts on system gen 

Enter Y in this field to automatically reset all Report generate counts whenever your 

System is generated. 

Propagate change control settings 

Enter Y in this field if you have specified Configure with Retain and you want the current 

Change Control options to be used to set up every Specification in the Host Builder. 

Otherwise, the current settings will be used to set up only the GLOBAL Specification. 

Configuring and Installing Host Builder 

To configure and install Host Builder, execute the Configure Utility by performing the 

following steps. For a full description of the Configure Utility, see your Unisys e-@ction 


1. Ensure that the Background Run for your Runtime is active. 

2. From a Demand terminal, enter: 

 

3. Select the Configure from disk transfer option from the first screen, and enter 

the name specified for the LOAD function in the System as Loaded field, and the 

name required for your Host Builder in the New System Name field. 

After transmitting this screen, the configuration parameters are displayed. 

Note: You may execute a Host Builder over the top of an existing Host Builder. 

However, since the install will require the SYS$LIB file exclusively for some of its 

installation processing, other user's system generates will queue waiting for the 

SYS$LIB file to become available. 

4. Change the configuration parameters and the pack and population specifications, as 

required. 

5. The following files contain database storage areas for the Host Builder, and are used 

extensively. You may consider placing these separately, for performance reasons. 

 

 

 

 

 

Note: It is advisable to monitor the usage of all database storage areas, to identify 

candidates for special placement. 

78616323–000 3–27


6. The Configure utility records any errors and stores them in various files. Use the 

LRUGENSTATUS command to report on errors. 

For more information, see your Unisys e-@ction Enterprise Application Runtime for 

ClearPath OS 2200 Administration Guide. 

7. The SLD and MOD reports are executed as part of the installation process. These 

reports load data into the Host Builder database if you are reconfiguring an existing 

Host Builder and retaining its existing database. It is advisable to check the SLD 

Report output, as it lists any reserved words used in Specifications. 

Note: You cannot use Host Builder from an IBM 3270 or a PCE terminal. 

Deleting Temporary Files 

The LRU LOAD facility creates certain files during its processing. These files are all 

qualified by T$system. LRU LOAD also creates a runstream file that you can use to 

remove these files, once you are satisfied that your load and configure have been 

successful. 

Enter the following command to delete these files upon completion of a successful load 

and configure, if required: 

 

The system value is the name you entered when you were prompted by the LRU LOAD 

facility with the following message: 

 

3–28 78616323–000


Installing Multiple Copies of Host Builder 

You can install multiple copies of Host Builder in the same Runtime, providing they are all 

at the same release level, and that the following values are unique: 

• System name 

• Database name 

• Transaction id and VALTAB Number 

• HVTIP Library Number 

Caution 

If you are installing multiple Host Builders in the same Runtime, all activity on 

all Host Builders should be stopped while any of the new Host Builders are 

being configured. 

78616323–000 3–29


Installing ROC 

The Report Output Control System (ROC) is an Enterprise Application System that 

manages Report output for all Systems in Runtime. ROC is included on the Release tape. 

You must install ROC before any Report output (other than output from Direct Reports) 

can be printed. 

To install ROC: 

1. Load ROC from the Release tape to disk. 

2. Configure and install ROC. 

3. Delete temporary files. 

These procedures are described in the following subsections. For more information on 

the Runtime Utility, see your Unisys e-@ction Enterprise Application Runtime for 


Note: To install Unisys-supplied changes to your ROC System, see the instructions 

accompanying the EIF (Engineering Interim Fix). 

Loading ROC from the Release Tape 

To load ROC, read the Release tape (or the output tape from the COMUS Build process), 

by executing the LRU facility. Enter the following ECL: 

 

The load is initiated. Its prompts are displayed one at a time. These prompts and your 

required responses are described in the following table. 

LOAD prompt Required Response 

What would you like to load? Enter 1 to load the ROC System. 

Enter the tape reel number Enter the reel number to be used. 

Enter tape equipment type Enter media type, for example U9S (as the Release 

tape is 6250bpi). 

Labeled tape Y/ N: Enter Y if tape is labeled. (N is the default.) 

Equipment type for loaded files Enter the pack id(s) for the disk(s) pack to be used. 

Default is F (fixed mass storage). See Note. 

What system name shall it be loaded 

as? 

Enter the System name to be used for ROC. 

Note: If you enter any value other than F (Fixed mass storage), the Disk/pack id(s) for 

loaded files prompt is displayed. Enter the pack names separated by a slash (/) character. 

3–30 78616323–000


The load checks the validity of the pack ids, and if it cannot validate the name, it prompts 

you to retype the pack ids. If the pack ids validate, it will display a summary of how much 

space is required for the product you are loading. You can then confirm that you want to 

continue. 

Configuring and Installing ROC 

To configure and install ROC, perform the following steps: 

1. If you are using FREESPACE, ensure that the relevant SGS that specifies the 

FREESPACE file is included. 

2. Initiate the Configure Utility program, by entering the following from a Demand 

terminal: 

 

3. Select the Configure from disk transfer option. 

4. Enter the name used by the Load Utility in the System as Loaded field, and enter 

the name you want to use in the New System Name field. 

Following this screen, all of the configuration parameters are displayed. You can 

change these if required. For a description of each parameter, see your Unisys e- 

@ction Enterprise Application Runtime for ClearPath OS 2200 Administration Guide. 

Note: Ensure that the transaction name and database name are the same as those 

specified in COMUS when your Runtime was installed. For more details, see 

“COMUS Configuration and SOLAR Installation Parameters” on page B–1. 

5. Having made any necessary changes to the Configuration parameters, you can now 

place individual ROC RDMS tables onto specific packs, and change their populations. 

To access the Pack and Population screen, enter a character in the Then: ISPEC 

packs and populations field. For more details, see your Unisys e-@ction 


The following table lists some of the tables in ROC, and their use. 

Ispec / 

Table Contains 

HEADR One header record for each Report output in the ROC database 

OHEAD A record for each output request 

S_T_N A record for each terminal which has accessed the ROC System 

TXBLK Data records 

6. Having changed the location and size of the tables where appropriate, and confirmed 

the changes, a screen is then displayed that requests run details about the configure 

program. Specify the run details and transmit the screen. 

7. The Configure program then installs ROC. 

78616323–000 3–31


8. Create an additional VALTAB entry for ROC to enable your Reports to interface with 

ROC. The QMAX parameter in the EXEC configuration for the QPRIORITY you specify 

in this VALTAB entry must be set to zero. The options for the REC parameter in the 

VALTAB entry must be set to LMNRSTZ. 

The following example shows the format of this VALTAB entry. 

 

 

 

 

 

Variable values used in this example are explained in the following table. 

Parameter Value 

file TIPRUN$ file 

ttttt ROC Spooler transaction id, as specified in the COMUS configuration for 

this Runtime 

nn TIP transaction number 

x Application group number 

q QPRIORITY for the ROC spooler transaction id 

9. Execute VTBUTL from your TIPRUN$ file. By default, this file is named 

TIP$*TIPRUN$. 

10. The Background Run and the HUB Background Run should be active before 

accessing ROC. For more details, see “Starting Your Background Runs” on 

page 3–18. 

11. Initiate the ROC Background Run for your Report Output Control System roc-system, 

as follows. 

 

Note: For XTC systems, you should start the ROC Background Run separately on 

each host. 

From Release 16R1, a new naming convention has been introduced for queued ROC 

files. For more details, see your Unisys e-@ction Enterprise Application Runtime for 

ClearPath OS 2200 Administration Guide. You can retain the old naming convention 

(as used in releases prior to 16R1) by adding the following line to the RC1 jobstream, 

anywhere between the @XQT and the @EOF: 

 

 

 

 

 

 

 

12. Enter the RC1 Background Run is active, by entering the following (where ROC is the 

name of the ROC System you installed): 

3–32 78616323–000


However, if you want to stop RC1 in an orderly manner, enter the following from a TIP 

terminal (where id is the ROC spooler transaction id): 

 

You could also enter the following from an operator console. For information about 

operator console commands, see Unisys e-@ction Enterprise Application Runtime for 


 

13. If you are using FREESPACE, check that the Background Run has the correct setting. 

If you want to change the ROC spooler Qpriority Node, first change it by using the 

Configure utility. You will need to: 

1. Change the ROC spooler Qpriority Node in the COMUS configure for your Runtime. 

2. Rebuild and install your Runtime. 

3. Reconfigure the ROC Database. 

Deleting Temporary Files 

The LRU LOAD facility creates certain files during its processing. These files are all 

qualified by T$system. LRU LOAD creates a runstream file that you can use to remove 

these files once you are satisfied that your load and configure have been successful. To 

do this, enter the following command: 

 

The system value is the name you entered when you were prompted by the LRU LOAD 

facility with the following message: 

 

78616323–000 3–33


Deinstalling 

Deinstalling Runtime 

To deinstall an OS 2200 based Runtime, perform the following steps: 

1. Remove all active Systems (including ROC and Host Builder) within Runtime by using 

the REMOVESYS option of the Runtime Utility (LRU). 

Use the LRU SYSCHECK$ALL command to obtain a list of all installed Systems. For 

more details about LRU, see your Unisys e-@ction Enterprise Application Runtime for 


2. Terminate the Background Run, by entering the following from an operator console: 

 

Here runtime is the name of your Runtime. 

3. Remove Runtime schema details from Meta Services Engine/RDMS. To do this, enter 

the following commands from a Demand session. 

 

 

4. To remove the rest of Runtime, use SOLAR. 

Select the REMOVE PRODUCTS option from the main menu. You can ensure you 

are removing the desired Runtime by pressing the F10 key from the Product 

Selection screen. 

Note: For PAEXEC Systems, you will need to perform this step for each of your 

switchable application groups. 

Deinstalling Host Builder 

Host Builder is an Enterprise Application System. To deinstall it, use the same procedure 

as you would for your user Systems. This procedure is described in “Deinstalling 

Runtime” on page 3–34. 

Note: There will be a number of files remaining that were created when you installed 

your Host Builder. These files were inherited by Runtime, and you have to manually delete 

them. Check all files that are prefixed by the name of your Host Builder. 

3–34 78616323–000

Section 4 

Migrating to Release 3R1A 

Migration Procedure 

Use the following procedure to migrate your Enterprise Application Environment 

Systems: 

Note: Prior to the release of 3R1A you had the choice of generating either Universal 

Compiling System (UCS) COBOL code, or Traditional Programming Environment (TPE) 

COBOL code. UCS was previously known as NPE (New Programming Environment). 

From Release 3R1A this choice, and associated option settings, no longer exists and only 

UCS COBOL code can be generated. 

It is recommended that you migrate existing TPE systems created in Release 16R3, or 

earlier, directly to Release 3R1A. 

If your systems use external (non Enterprise Application Environment) subroutines in TPE, 

these will have to be re-written using a UCS compiler. 

1. Take note of the various migration issues outlined in “Addressing Migration Issues” 

on page 4–4. It is important that you understand the implications of each new feature. 

2. Ensure that your existing Systems and Specifications are backed up. 

3. It is recommended that you perform a syntax-only generate of your System. 

4. Ensure that the appropriate system software is installed. See “Checklist for OS 2200 

Based System Software” on page 2–6. 

5. Use one of the following procedures to migrate from release 16R3 to release 3R1A: 

• Use LCOPY to extract your Specifications from release 16R3 and load them into 

release 3R1A. See “Using LCOPY” on page 4–2. 

• You can also use CASE LOAD, but this will take longer than LCOPY. 

6. After using LCOPY to copy your Specification to release 3R1A, it is recommended 

that you perform a syntax-only generate of your System before you generate the new 

System. 

7. Generate your Systems. See “Generating Your Systems after Migration” on 

page 4–11. 

78616323–000 4–1


Using LCOPY 

The following table shows whether you can use LCOPY to migrate your Specifications, 

depending on your Host Builder release level. 

Using LCOPY to migrate to release 3R1A 

Use the following procedure to migrate from release 16R3 to release 3R1A: 

1. Unload your existing Specifications (including GLOBAL) from your Developer System, 

by using LCOPY. 

2. Install release 3R1A. 

3. Load your Specifications into your new Host Builder, by using LCOPY. 

4. Generate your Systems, as described in “Generating Your Systems after Migration” 

on page 4–11. 

LCOPY is documented in Unisys e-@ction Enterprise Application LCOPY Guide. 

Loading into earlier releases 

From To 15 To 16 

15 Y Y Y 

16 – Y Y 

3R1A – – Y 

You cannot use LCOPY to load Specifications created in (or migrated to) release 3R1A into 

release 16. 

Using LCOPY Compare across major releases 

To 

3R1A 

Between major releases of Host Builder (for example, release 16 and release 3R1A), 

there are often differences in how Specifications are stored. 

You cannot use the LCOPY Compare function to compare Specifications across major 

releases. 

Generating OS 2200 Reports before Migrating 

The N execution option for Reports causes your generated Direct Reports to initialize 

with the MCB, before the call to USERPRT. 

To use this feature, you must perform one of the following: 

• Add the N option to the @XQT report statement in the system*REP$RUN.report 

element. 

4–2 78616323–000


• Manually add the N option to the @XQT report statement when running the Direct 

Report from Demand mode. 

You must regenerate Reports in your current release before migrating to Release 3R1A. 

78616323–000 4–3


Addressing Migration Issues 

Environmental Settings 

You may wish to check the environmental settings for each Specification. Examples of 

possible changes are: pack allocations, integrity settings, log settings, subsystem 

allocations, and whether audit files are to be copied to tape. However, before you make 

any such changes, first check that the migration information (both in this section and in 

your release information) does not specifically exclude that type of change. 

Do not, for example, change any data items or logic. 

Relational Database Fast Load support 

A storage area needs several more pages if Relational Database Fast Load level 4R2 is 

used for loading data into it. The extra number depends on the page size and varies from 

9 pages (page size = 7168 words) to 102 pages (page size = 224 words). 

In Release 3R1A generations, these extra pages will be added to the page number 

calculation done in the generate and will cause minor UREP Data Dictionary UPDATE 

work to be done on the first generate to increase the number of pages accordingly. 

Note: Relational Database Fast Load level 4R3 does not have this requirement. 

S_T_N Records in Memory 

LCOPY and CASELOAD will force the Preserve Session Data setting to "Y". The Preserve 

Session Data field had no meaning for prior releases on OS2200 platforms. For crossplatform 

compatibility reasons, the setting to "Y" equates to using the RDMS/FCSS 

method of storing station records, and the setting to "N" will turn on the Station Records 

In Memory feature 

Global Setup Data Blocks 

Release 3R1A introduces the ability to define Global Setup Data (GSD) items in multiple 

logic blocks, which can be defined in named code blocks, similarly to the naming of Global 

Logics, Ispecs and Reports. 

Existing GSDs will automatically become a GSD block named GLB-SDS and any existing 

GLB Work GSD item or group will automatically become another GSD block named GLB- 

WORK-BLOCK. 

Migration from a previous release to this release will require minimal user intervention 

with regards to the GSDBLOCKS feature modification. A conversion utility, which will 

perform the following, is provided: 

4–4 78616323–000


• Existing GSDs will automatically become a GSD block named GLB-SDS (as this is 

their internal “Ispec” name) with an internal number of 1, so that a description and 

text can now be entered for them and they become a named GSD block. 

• Any existing Global Work name GSD item or group will be automatically removed 

from this block into a separate block named GLB-WORK-BLOCK. If this name is 

already used, then a number from 1 up is suffixed until a unique name is reached and 

this is used. If the existing GLB Work item or group is itself within a group, it is still 

converted but with a warning printed in the CPY report output that this has happened. 

Both CPY and CLD will convert GSDs from pre-release 3R1A input files. 

Rounding from Compute Commands 

In release 3R1A the syntax for the COMPUTE and the COMPUTE.FROM commands has 

been extended to make use of the COBOL ROUNDED option, which forces rounding of 

the final result. This is similar to the ADD, DIVIDE, MULTIPLY and SUBTRACT options. 

Existing specifications will continue to truncate the result of a COMPUTE or 

COMPUTE.FROM unless ROUNDED is added. 

Extract Format for Data Interchange 

Release 3R1A provides the ability to create and read extract files in a format that is 

compatible with all platform versions of Enterprise Application Environment. This new 

format is in addition to the existing extract file formats that are user defined and internal. 

Use LCOPY to load existing Reports into the release 3R1A System. No changes are 

required to the Reports. If you want to use this feature: 

1. Complete the Report Choices Screen and select the Extract File Option (EX). 

Alternatively, you can enter the following in any Action field: 

 

2. Enter the details of the extract files on the Extract File Options screen. 

3. Enter the style of the extract data for Ispecs in the Ispec Format field. The default 

value of the field is the current internal style. 

Valid input values are: 

• I for Internal record format (default) 

• G for Generic record format 

The Ispec Format field is unique by Generate Set within a Report. 

Note: Print frame extracts, including Mapper extracts, and existing Ispec extracts are not 

affected by this feature. 

The Report can then be generated as normal. 

78616323–000 4–5


Localization 

In release 3R1A, all translatable messages displayed by Runtime programs use the 

standard OS 2200 based Extended Language Message System (ELMS) software to 

translate runtime messages from ELMS message files instead of the LLANGUAGE file, 

as was previously the means of supplying the translated messages. 

You will need to reformat any translated versions of the LLANGUAGE file. The 

runtime*UTIL$.convert-ELMS utility is provided to automatically convert the existing 

versions of the LLANGUAGE file and create the runstreams and ELMS SGS statements 

required for conversion. 

Migrating to Release 3R1A for LLANGUAGE 

The default message file ENG-BASE is included with Enterprise Application Environment 

in runtime*UTIL$. 

The ELMS messages are installed as a SOLAR local product called LINCELMS, as mode 

runtime, in file runtime*LINCELMS. 

A new local product is installed the first time each Runtime 3R1A is installed. After the 

first install, it is your responsibility to maintain it. 

If you only use the default language (English), you will not need to do anything. 

If you use languages other than English, you will need to translate and install them. The 

utility runtime*UTIL$.CONVERT-ELMS helps you convert from previous versions of 

LLANGUAGE to the new ELMS message file. 

The procedure is as follows: 

1. Compare your existing LLANGUAGE file versions with runtime*UTIL$.LLANGUAGE 

Note: runtime*UTIL$.LLANGUAGE is only used to compare for 3R1A conversion. 

2. Copy your old LLANGUAGE file to runtime*LLANGUAGE and edit it with the results 

of the step 1. 

3. Enter one of the following commands: 

or 

 

 

4. Enter the following command: 

 

5. Using a text editor, add message numbers from 5001 to end of ENG-BASE to your 

message file runtime*LINCELMS.ELMScomponent-id/lang. 

lang is a three-letter language code, for example, FRA. This must match the first three 

characters used in GLB.LANGUAGE. 

6. Run the element runtime*LINCELMS.SYNTAX/CHECK and study the results. 

4–6 78616323–000


7. Edit and correct the message file LINCELMS.ELMScomponent-id/lang 

Note that the original message from the LLANGUAGE file is included as a comment 

to help you. 

ELMS will concatenate multiple spaces, so replace these with the ELMS keyword 

spacen. 

ELMS does not accept characters such as ‘


Also, old cycles of the file runtime*LINCELMS. can be left behind. You should check and 

delete the runtime*LINCELMS file. 

The following table shows the messages you can translate. 

Messages used in Message numbers 

Same as old LLANGUAGE 3 through 1500 

CONFIGURE 5064, 5077, 5529, 5595, 5845, 5846, 5847, 5848, 5872, 6237, 

6238, 6239, 6240, 6241, 6242, 6243, 6244, 6245, 6246, 6247, 

6248, 6249, 6250, 6251, 6252, 6253, 6254, 6255, 6256, 6257, 

6258, 6259, 6260, 6261, 6262, 6263, 6264, 6265, 6266, 6267, 

6268, 6269, 6271, 6272, 6273, 6274, 6275, 6276, 6277, 6278, 

6279, 6280, 6281, 6282, 6283, 6284, 6285, 6286, 6287, 6288, 

6289, 6290, 6291, 6292, 6293, 6294, 6295, 6296, 6297, 6298, 

6299, 6300, 6301, 6302, 6303, 6304, 6305, 6306, 6307, 6308, 

6308, 6309, 6310, 6311, 6312, 6313, 6314, 6315, 6316, 6317, 

6318, 6319, 6320, 6321, 6322, 6323, 6324, 6325, 6326, 6327, 

6328, 6329, 6330, 6331, 6332, 6333, 6334, 6335, 6336, 6337, 

6338, 6340, 6341, 6342, 6343, 6344, 6345, 6346, 6347, 6348, 

6349, 6350, 6351, 6352, 6353, 6354, 6355, 6356, 6357, 6358, 

6359, 6360, 6361, 6362, 6363, 6365, 6366, 6367, 6368, 6369, 

6370, 6371, 6371, 6372, 6373, 6374, 6375, 6376, 6377, 6378, 

6379, 6380, 6381, 6382, 6383, 6384, 6385, 6386, 6387, 6388, 

6389, 6390, 6391, 6392, 6393, 6394, 6395, 6396, 6397, 6398, 

6399, 6401, 6402, 6403, 6404, 6405, 6407, 6408, 6583, 6584 

CONFIGURE LRU 6406 

GLOBALCO 5140, 5398, 5438, 5500, 5501, 5522, 5636, 5829, 5835, 6119 

GLOBALSP 5462 

GLOBALSR 5025, 5031, 5094, 5123, 5125, 5126, 5160, 5161, 5747, 5963, 

6050, 6585, 6586, 6587, 6588, 6589, 6590, 6591, 6592, 6593, 

6594, 6595 

LIBRARYR 5440, 5518, 5624, 5625, 5626, 5628, 5632, 5633, 5750, 5823, 

5889, 5983, 6057 

4–8 78616323–000

Messages used in Message numbers 

ROC Performance Improvement 


LRU 5013, 5016, 5017, 5023, 5024, 5028, 5038, 5069, 5093, 5095, 

5097, 5099, 5102, 5105, 5116, 5107, 5136, 5137, 5138, 5139, 

5141, 5144, 5145, 5149, 5158, 5162, 5163, 5164, 5165, 5166, 

5167, 5186, 5351, 5357, 5359, 5360, 5364, 5373, 5374, 5376, 

5380, 5383, 5384, 5385, 5386, 5387, 5388, 5389, 5390, 5399, 

5406, 5408, 5415, 5421, 5427, 5442, 5447, 5448, 5463, 5473, 

5475, 5476, 5496, 5513, 5517, 5528, 5532, 5533, 5534, 5535, 

5545, 5550, 5554, 5557, 5558, 5558, 5560, 5561, 5575, 5657, 

5658, 5686, 5753, 5754, 5772, 5773, 5780, 5798, 5820, 5825, 

5830, 5831, 5834, 5832, 5836, 5839, 5850, 5851, 5863, 5866, 

5869, 5887, 5943, 5949, 5973, 5974, 5975, 5976, 5993, 5994, 

5995, 5996, 6007, 6024, 6028, 6062, 6064, 6072, 6078, 6080, 

6081, 6083, 6086, 6103, 6113, 6120, 6127, 6128, 6144, 6527, 

6528, 6529, 6530, 6531, 6532, 6533, 6534, 6535, 6536, 6537, 

6538, 6539, 6540, 6541, 6542, 6543, 6544, 6545, 6546, 6547, 

6548, 6549, 6550, 6551, 6552, 6553, 6554, 6555, 6556, 6557, 

6558, 6559, 6560, 6561, 6562, 6563, 6564, 6565, 6566, 6567, 

6568, 6569, 6570, 6571, 6572, 6573, 6574, 6575, 6576, 6577, 

6578, 6579, 6580, 6581, 6582, 6582, 6597 

STNUTIL 5538, 6270, 6406, 6409, 6410, 6411, 6412, 6413, 6414, 6415, 

6416, 6417, 6418, 6419, 6420, 6421, 6422, 6423, 6424, 6425, 

6425, 6426, 6427, 6428, 6429, 6430, 6431, 6432, 6433, 6434, 

6435, 6436, 6437, 6438, 6439, 6440, 6441, 6442, 6443, 6444, 

6445, 6446, 6447, 6448, 6449, 6450, 6451, 6452, 6453, 6454, 

6455, 6456, 6457, 6458, 6459, 6460, 6461, 6462, 6463, 6464, 

6465, 6466, 6467, 6468, 6469, 6470, 6471, 6472, 6473, 6474, 

6475, 6476, 6477, 6478, 6479, 6480, 6481, 6482, 6483, 6484, 

6485, 6486, 6488, 6489, 6490, 6491, 6492, 6493, 6494, 6495, 

6496, 6497, 6498, 6499, 6500, 6501, 6502, 6503, 6504, 6505, 

6506, 6507, 6508, 6509, 6510, 6511, 6512, 6513, 6514, 6515, 

6516, 6517, 6518, 6519, 6520, 6521, 6522, 6523, 6524, 6525, 

6526 

The performance and functionality of the ROC (Report Output Control) system on 

OS 2200 has been enhanced. The new implementation reduces competing access to the 

ROC database. 

To help you migrate to ROC release 3R1A, two Migration Reports are provided: 

• ROCEXT is provided as an EIF. Run ROCEXT against LINC release 16R3 to extract 

some or all of your ROC database to extract files. 

• ROCLOAD is provided on the Enterprise Application Environment release 3R1A 

media. When you have installed ROC release 3R1A, run ROCLOAD to load the 

extract files into the new ROC database. 

78616323–000 4–9


Graphical Interface Workbench Release 3R2 

Updating Graphical Interface Workbench Scripts 

Before running any Graphical Interface Workbench-capable Systems that have been 

migrated from a release prior to release 16R3, change your existing master scripts to use 

the WDP16 window rather than running the WDPSTATIONS program. 

If you have migrated your System from release 16 to release 3R1A, you can continue to 

use your existing scripts. You require new scripts if your host does not have a WDP16 

window defined. These scripts are available in the latest Interim Corrections (ICs) for 

released versions of PCE. 

Using Graphical Interface Workbench 

If you do not wish to use Graphical Interface Workbench, set the DW capable system 

field on the System Environmental Options screen to N. 

If you intend to use Graphical Interface Workbench, before generating any migrated 

Graphical Interface Workbench-capable system, use the Designer Workbench Options 

screens to enter values corresponding to the information in your existing WDPMAP file. 

Migrating existing Graphical Interface Workbench screens 

Release 3R1A supports Graphical Interface Workbench release 3R2. By using Graphical 

Interface Workbench release 3R2, you can make many form changes at your PC without 

causing the screen layouts to be downloaded from the host. 

Caution 

If you make changes, you are responsible for ensuring that the data item 

definitions in the forms match those defined in your System. 

4–10 78616323–000

Generating Your Systems after Migration 

Note: Release 3R1A will only generate UCS COBOL code. 


To generate your migrated Specifications, perform the following procedure: 

1. Sign on to Host Builder for release 3R1A. 

2. Log on to a migrated Specification. 

Note: For Modules, you must complete a syntax-only generate of the Module 

Master (including all Reports) before you generate any Modules. 

3. Access the Generate screen. Enter N in the Stop on first error field, and Y in the 

Syntax only field, and generate the System. 

The first System generate following migration may take longer than at other times. 

4. Correct any errors found. 

Note: If your Specification contains nested Performable Global Logics that bring data 

into memory, errors may be reported where an Ispec manipulates data read in by a 

Performable Global Logic. The error can be resolved by including a dummy read, or by 

repositioning the logic that performs the read. 

5. At this point, you may wish to run the CONVINIT and CONVDATE reports, so that you 

can take advantage of release 3R1A features. See “Addressing Migration Issues” on 

page 4–4. 

6. Access the Generate screen again. Enter Y in the Stop on first error field, and N in 

the Syntax only field, and generate the System. 

7. When your system generation and reorganization are complete, generate all Reports. 

8. If you are using System Transfer and Configure for your Systems, perform the 

transfer and configure now. 

Caution 

Do not start up your System until the generation process has been fully 

completed. 

78616323–000 4–11


4–12 78616323–000

Appendix A 

Files Created by Enterprise Application 

Environment 

This appendix contains the following information on the files created by Enterprise 

Application Environment: 

• Conventions Used in This Appendix 

• Installing Runtime 

• Installing Host Builder 

• Configuring and Generating Systems 

Conventions Used in This Appendix 

The following conventions are used in this appendix. 

The runtime parameter indicates the name of the Runtime. 

The system parameter indicates the name of the Enterprise Application Environment 

System, whether it is a generated System, or Unisys-supplied software (for example, 

Host Builder). 

78616323–000 A–1

Files Created by Enterprise Application Environment 

Installing Runtime 

File Names 

The following files are created when installing Runtime: 

 

 

 

 

 

 

 

 

 

 

 

 

The PERM$SGS file is created when Runtime is installed. The parameters in this file 

describe the system settings, and you can add additional SGSs after them. Do not delete 

these SGSs. For a description of SGS parameters, see your Unisys e-@ction Enterprise 


The LINC$GLADTR$ file is created on all OS 2200 based hosts, but is used primarily on 

XTC systems. 

RDMS Storage Areas 

A number of RDMS storage areas are created that contain the RDMS tables listed in the 


Storage Area 

File Name Table Name Description 

SA$ CONFIG COMUS details 

LSYS Details of all OS 2200 based Systems in 

current Runtime 

PIDRANGES Ranges of valid PIDs 

SERVICES OLTP Service Names 

STNDEFAULT Initial station record info. 

SA$RI REPORTINFO Active Reports 

SA$RII Index for SA$RI 

SA$RR REPORTSRUN Completed Reports used in recovery 

SA$SI SECURINT Development System Security Information 

SA$SII Index for SA$SI 

A–2 78616323–000


Storage Area 

File Name Table Name Description 

SA$SU SECURITY Security information 

SA$SUI Index for SA$SU 

SA$ACC ACCEPTS SA$ACC 

SA$ACCI Index for SA$ACC 

SA$APID ACTIVEPIDS Clears PIDs during background run recovery 

BCAST$ BCAST Flags for recovery of AUTOs 

BCAST$PRO BCAST_PRO Critical point data for Reports 

Note: The BCAST and BCAST_PRO tables are only created for shared application groups 

on XTC hosts. 

Using Special Printing Attributes 

The following files are created as sample files that must be modified if you wish to use 

special printing attributes. For more information, see your Unisys e-@ction Enterprise 


 

 

78616323–000 A–3


Installing Host Builder 

When you install Host Builder, files from the Release tape are copied to mass storage. 

The following files need to be secured: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

These files are cataloged on mass storage with the V option (ineligible for rollout). 

A–4 78616323–000


Configuring and Generating Systems 

The following files are created when configuring and generating a System. 

File Description 

system*SYS$LIB. System configuration information plus some ECL (for example, 

LINC$CNTL, RDML$EXT, COPY$ECL) 

system*TRX$SYM. Ispec logic symbolics 

system*TRX$REL. Ispec logic relocatables 

system*TRX$ABS. Ispec logic absolutes 

system*SCR$SYM. Ispec Screen subprogram symbolics 

system*SCR$REL. Ispec Screen subprogram relocatables 

system*GEN$RUN. System generation runstreams for BATCH processing, serial or split 

runs 

system*PDP$LIB. Common database access code 

system*REP$SYM. Report symbolics (if Reports exist) 

system*REP$REL. Report relocatables (if Reports exist) 

system*REP$ABS. Report absolutes (if Reports exist) 

system*REP$RUN. Report runstreams (if Reports exist) 

runtime*systemP$. HVTIP library containing subprogram banks (ICP and Ispecs) of the 

System. For UCS Subsystems, it is a SUPUR library containing the 

standard TIP ICP used to access the Subsystem. 

system*TRX$SSDP. UCS Subsystem definition, registered with the operating system 

during SOLAR PRODLD. Exclusively assigned to the Exec until the 

Subsystem is deactivated. (It is not created for HVTIP Systems). 

runtime*systemS$. Subsystem library of object modules. Exclusively assigned to the 

Exec until the Subsystem is deactivated. (It is not created for HVTIP 

Systems). 

Note: The runtime*systemP$. file is only valid if you are not using HVTIP shared libraries. 

If your default duplex pack is specified then your HVTIP library will be duplexed and the file 

will be runtime*system$2P$. 

Output from Configure or Generate 

The P$ file is cycled, enabling you to access previous runs. Each Report Batch generate 

and Individual Report generates use one cycle of the P$ file. 

If you choose to split runs for your generate or configure, the following files are created. 

• For PGEN phase: 

78616323–000 A–5


 

• For compile phase: 

 

• For maps phase: 

 

Possible n values range from 2 to the number of splits specified. 

Database Files 

The following database files are created when configuring or generating a System. 

The tip value is the TIP number. Valid length for the TIP number is six digits, for example, 

000230. The database value is the name of your database, ispec is an Ispec name, and 

profile is a Profile name. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

A–6 78616323–000

Appendix B 

COMUS Configuration and SOLAR 

Installation Parameters 

This appendix lists the parameters required for each stage of COMUS configuration and 

SOLAR installation of your Enterprise Application Environment Software. Instructions for 

these stages are given in “Installing Enterprise Application Environment Software” on 

page 3–1. This appendix covers the following topics: 

• COMUS Configuration Main Menu 

• General Configuration Parameter Screens 

• Processor File Names Screens 

• Common Bank Attributes Screen 

• Additional I-Language Banks Screen 

• HUB Configuration Parameters Screens 

• OLTP Configuration Parameters Screen 

• LRSS Configuration Parameters Screen 

• COMUS Run Parameters 

Configuration parameters and defaults for installing a System that will communicate with 

the OLTP environment are described in your Unisys e-@ction Enterprise Application Host 

Builder Guide. 

Stages of the Configuration and Installation Process 

The stages of the COMUS configuration and SOLAR installation process are listed in the 


Stage Process Description 

1 Register (COMUS) Register the Release tape with COMUS. 

2 Configure Set the configuration parameters to customize for your site. 

3 Build Build a copy of Runtime (if you have altered the parameters). 

4 Register (SOLAR) Register the output of the Runtime with SOLAR. 

5 Install Install a copy of Runtime. 

If you do not change any parameters, that is you accept all of the default values on your 

first install, you do not need to run the Build step. 

78616323–000 B–1

COMUS Configuration and SOLAR Installation Parameters 

Any time after Runtime is installed, you may change your configuration, and rebuild/ 

reinstall with new parameters. 

B–2 78616323–000


COMUS Configuration Main Menu 

The COMUS Configuration Main Menu enables you to navigate to seven other 

configuration screens. 

• General Configuration Parameter Screens 

• Processor File Names Screens 

• Common Bank Attributes Screen 

• Additional I-Language Banks Screen 

• HUB Configuration Parameters Screens 

• OLTP Configuration Parameters Screen 

• LRSS Configuration Parameters Screen 

From the Home position, enter the number for the group of configuration parameters you 

want to access and transmit. The screens and individual parameters for each of the seven 

possible groups are described in the following subsections. 

Hints on Navigating and Online Help 

The Configuration parameter screens are accessed from the Configuration Main Menu 

screen. 

For online help, enter a question mark (?) at the top of the screen and transmit. 

Some of these screens have continuation screens. To display a continuation screen, enter 

a plus sign (+) at the Home position. To return to a previous screen from a continuation 

screen, enter a minus sign (-) at the Home position. 

To return to the Configuration Main Menu, enter b in the Home position of any screen. 

To return to a previous screen from a continuation screen, enter a minus sign (-) at the 

Home position. 

78616323–000 B–3


General Configuration Parameter Screens 

Use the General Configuration Parameter screens to enter the basic parameters for 

Runtime. The various screens are described in the following subsections. 

General Configuration Parameter Screen 1 

This subsection describes the fields on General Configuration Parameter Screen 1. 

Runtime Name 

Enter the name for the Runtime you are configuring. You may want to install more than 

one copy of Runtime. The default name is LINC3R1. 

Each Runtime name must be unique and may contain up to eight characters, the first of 

which must be alphabetic. The Runtime name is used as a qualifier for your OS 2200 

based production files, and is the name you use with the BUILD command. The 

maximum length is eight characters to prevent the runtime$Lxx and runtime$Rxx 

Common Bank names from exceeding the maximum length of 12 characters. 

It is advisable to use the same name as you specified for your COMUS Config Set Name. 

Background Run RUNID 

Enter the name of the runstream created in SYS$LIB$*RUN$ to start the Background 

Run. The value that you enter is the run id of that run. This name must be a unique run id 

of up to six characters in length. 

It is advisable to use your Runtime name for your Background Run id. 

The default value is L3R1. 

Configuration Description 

Use these three fields to enter an optional description of this particular configuration. Up 

to three lines of text are available. 

Each description line may be up to 32 characters long. 

The default is spaces. 

Application Name 

Use this field to enter the name of the Application Group in which you wish to install 

OS 2200 based Runtime. The default is UDSSRC. 

The Application Name identifies a recoverable element to the operating system, the 

recovery system (IRU), and the data manager (UDS). 

B–4 78616323–000


Application group names have an associated Application Number, which is also a 

configuration parameter. The Application Number you specify must relate to the 

application name that you enter. Consult your Site Administrator about the choice of 

Application Group. 

Real Application Names are required, as aliases are not valid. 

Application Number 

Enter the number of the Application Group in which you wish to install OS 2200 based 

Enterprise Application Environment. The valid range is 1 through 16. The default value is 

3. 

The Application Number you specify must relate to the Application Name. For more 

details, see the Application Name parameter. 

HVTIP Base Library Number 

Enter the base TIP file number for your HVTIP libraries. This number may contain up to 

four characters, and it must match the value of the TPLIB operating system configuration 

parameter in your EXEC generation. The default is 17. 

Consult your Site Administrator about the base TIP file number for your installation. 

System Files Equipment 

Each copy of Runtime maintains control information in RDMS tables. Use this field to 

enter the equipment type of the unit where the associated RDMS storage area is to be 

located. The default is F, which locates the files on fixed mass storage. 

Note: Several environment files are created external to COMUS, and these files are also 

created on the specified equipment type. 

You may enter up to eight characters. For related information, see the System Files 

Packids parameter. 

System Files Packids 

If you leave this parameter blank (the default), the storage area is placed on fixed mass 

storage. The maximum length of this field is 32 characters. 

Enter the packid of the unit where your Control storage area and other associated files are 

to be located. 

If multiple packids are required, enter them consecutively, separating them with a slash 

character (/), as shown in the following example. 

 

The packs specified have the same equipment type that you specify in the System Files 

Equipment parameter. 

78616323–000 B–5


System Files ACR Name 

Control information for Runtime is maintained in RDMS tables. Use this field to enter the 

ACR name to be used when cataloguing the file containing these tables. 

You may enter up to six characters. Additional equipment files also have this ACR on their 

catalogue. For more details, see your OS 2200 SIMAN User Reference Manual. 

Note: Security for RDMS tables should be established with care, as all transactions have 

to pass this ACR. 



Common Bank BDI Parameters 

Common Bank BDI parameters for the Configure stage are described as follows. 

LINC$TABLES BDI 

Enter the BDI for the LINC$TABLES Common Bank. You must enter all seven characters, 

including the leading zero. The LINC$TABLES Common Bank contains data structures 

that are used to coordinate the operation of Runtime. 

Each copy of Runtime must have a separate set of Common Banks. It is advisable that 

LINC$TABLES and LINC$SUBS use consecutive BDIs; for example, 0402676 and 

0402677. 

The default value is 0402676. 

LINC$SUBS BDI 

Enter the BDI for the LINC$SUBS Common Bank. You must enter all seven characters, 

including the leading zero. The LINC$SUBS Common Bank contains subroutines used in 

the execution of your Systems. 

Before entering these BDIs, check that they are not already in use. These numbers are 

shown as a sample set in your UDS Installation Guide, for application group 8. Consult 

your Site Administrator about the choice of BDIs. 

See also the LINC$TABLES BDI parameter. 

The default is 0402677. 

LINC$EMCB BDI 

Use this field to enter the BDI for the LINC$EMCB Common Bank. You must enter all 

seven characters, including the leading zero. The LINC$EMCB Common Bank contains 

subroutines used in the execution of your UCS Systems. 


B–6 78616323–000

See also the other BDI parameters. 

LINC$SRCEC BDI 


Enter the BDI for the LINC$SRCEC Common Bank. You must enter all seven characters, 

including the leading zero. The LINC$SRCEC Common Bank contains COBOL templates 

used by Host Builder. 

See also the other BDI parameters. 


LINC$STN BDI 

Enter the BDI for the LINC$STN Common Bank. You must enter all seven characters, 

including the leading zero, in extended mode format e.g. 020xxxx. The LINC$STN 

Common Bank contains the subsystem used to store station data associated with 

GLB.WORK in memory. Other S_T_N station data will continue to use RDMS Table or 

FCSS file. 


LINC$VLOG BDI 

Enter the BDI for the LINC$VLOG Common Bank. You must enter all seven characters, 

including the leading zero. See also the other BDI parameters. The LINC$VLOG Common 

Bank contains templates used for the editing facilities within Host Builder. 


LINC$RTS BDI 

Enter the BDI for the LINC$RTS Common Bank. You must enter all seven characters, 

including the leading zero, in extended mode format e.g. 020xxxx. 

The LINC$RTS Common Bank contains UCS support routines created as a chameleon 

fast-load self-contained subsystem (FLSS), a shared subsystem which provides for fast 

loading of local unshared data 

The default is 0205471 

LINC$L01 BDI 

Enter the BDI for the Common Bank into which the ILANGUAGE file containing message 

texts for Host Builder will be loaded. The default is 0404645. You must enter all seven 

characters, including the leading zero. 

This is the Common Bank BDI for the primary language only. If you have a multiple 

language Host Builder, select the Additional I-Language Banks (ILANGUAGE) set of 

parameters to specify your LINC$L02 to LINC$L15 BDIs. 

78616323–000 B–7




EIS Capable Host 

Enter Y to specify that Runtime is to run on an Extended Instruction Set (EIS) machine. 

EIS is a hardware feature which gives faster character handling, and is available on all 

OS 2200 based machines. 

Enter N if EIS does not apply. The default is Y. 

Print Queue for Error Dumps 

Enter the print queue in which you wish any TIP printed output or post mortem dumps to 

be placed. You may enter up to four characters. The default is PR. This value applies to all 

OS 2200 based Systems within Runtime, but it can be overridden at system level. 

Network Host ID for this System 

Enter the Host id for the machine your Runtime runs on, as defined to your TELCON 

software. This is used in the global host parameters, enabling OS 2200 based Systems 

running on other hosts to access your OS 2200 based System. 

You can enter up to six alphanumeric characters. The value entered is automatically 

stored in the System Data item GLB.SELFHOST, and is automatically moved to 

GLB.ORIGINHOST when an external Automatic Entry is performed. 

The default value is six space characters, which provides no host ID. That is, your System 

is not accessible to OS 2200 based Systems running on other hosts. 

On XTC systems, select one Network Host id to represent all the closely coupled hosts. 

For example, if your system consists of hosts with network ids NY01, NY02, NY03, and 

NY04, you can select NY01 to represent the entire system. This causes the entire XTC 

system to be treated as a single host. 

ROC Transaction ID 

Enter the TIP transaction id to be used to sign on to your Report Output Control System 

(ROC). 

Up to six alphanumeric characters may be used. The default is RT3R1. 

ROC Database Name 

Enter the database name to be used for your Report Output Control System (ROC). The 

name is used as a qualifier for the ROC database files. The name must not exceed seven 

alphanumeric characters. The default is RD3R1. 

ROC Spooler Transaction ID 

Enter the TIP transaction id to be used by the ROC spooler to receive transaction input. 

B–8 78616323–000


You can enter up to six alphanumeric characters. The default is RQ3R1. 

ROC Environment Name 

You can use a ROC System which runs in a different copy of Runtime to the Runtime you 

are installing. Use this field to enter the name of the Runtime in which ROC is to run. 

You may enter up to ten characters. The default is spaces, which is the Runtime you are 

currently installing. 

ROC Spooler Queuing Node 

Enter the Queue Priority node used by the ROC Spooler to receive transaction input. 

Node numbers can be in the range from 1 through 99999. The node used must already 

have been defined in an EXEC gen, with a QMAX parameter of zero. This node must not 

be in current use. 


Maximum Number of PIDs 

Enter the maximum number of terminals that can be simultaneously connected to 

Systems within the current copy of Runtime. Enter up to five numeric characters. 

This parameter controls the size of the ACTIVEPIDS Table in the LINC$TABLES Common 

Bank, which is used to scan for terminals that may be timed out. 


Idle Terminal Timeout (min) 

Enter the time (in minutes) that a terminal is to remain in idle status. Enter up to four 

numeric characters. After this time, a BYE will be automatically issued by the Background 

Run, to sign the terminal off the System. 

Multiple PIDs on the same physical terminal are monitored separately. 


Timeout Check Interval (sec) 

Enter the time interval (in seconds) between checks for idle terminals. This value 

specifies how often the Background Run scans through the ACTIVEPIDS table. 


Unsuitable values for this parameter may affect performance. 

Clear AUX area in MCB packet 

Enter Y if you have an XIS/AIS environment. This informs MCB not to call its error 

handling routine. 

78616323–000 B–9


The default is N. 

B–10 78616323–000

Processor File Names Screens 


Use the Processor File Names screens to name the various software packages used to 

operate or build your copy of Runtime. 

Entering Parameters 

All parameters have a maximum length of twenty-five alphanumeric characters. 

Processor File Names Screen 1 

This subsection describes the fields on Processor File Names Screen 1. 

COBOL Compiler (@ACOB) 

Enter the name of the COBOL compiler file. Do not enter a trailing period after the file 

name. 

The default is SYS$LIB$*ACOB. 

UCOB UCS COBOL Compiler 

Enter the name of the UCOB COBOL Compiler file. 

Do not enter a trailing period after the file name. The default is SYS$LIB$*UCOB. 

Note: If a UCOB compiler file is specified, the U---U Ispec is always compiled with the 

UCOB compiler in addition to ACOB. This allows UCS Reports to link correctly. 

Collector (@MAP) 

Enter the name of the Collector processor file. Do not enter a trailing period after the file 

name. 

The default is SYS$LIB$*MAP. 

Data Dictionary (@DD) 

Enter the name of the Data Dictionary processor file. Do not enter a trailing period after 

the file name. 

The default is SYS$LIB$*UREP. 

ACOB TIP Library 

Enter the name of the ACOB TIP library file. Do not enter a trailing period after the file 

name. 

The default is SYS$LIB$*ACOB-TIPLIB. 

78616323–000 B–11


File Containing ACOB CBEP$ 

Enter the name of the file containing the COBOL Common Bank entry point table. Ensure 

that the CBEP$ file you specify matches the COBOL compiler you have specified. Do not 

enter a trailing period after the file name. 

The default is SYS$LIB$*ACOB-DML. 

ACOB Library 

Enter the name of the ACOB library file. Do not enter a trailing period after the file name. 

The default is SYS$LIB$*ACOB. 

TIP RUN$ File 

Enter the name of the TIP RUN$ file. Do not enter a trailing period after the file name. 

The default is TIP$*TIPRUN$. 

TIP LIB$ File (for MCB) 

Enter the name of the TIP library file containing the MCB interface routines for the 

application group within which your OS 2200 based System runs. Do not enter a trailing 

period after the file name. 

The TIP LIB$ file contains TIP primitive subroutines and the MCB interface routines. The 

MCB interface routines may be specific to each application group, depending on the 

method used when they were installed. For more details, see the OS 2200 TIP 

Installation Guide. 

The default is TIP$*TIPLIB$. 

File Containing CBEP$$MCB 

Enter the file name containing the CBEP$$MCB relocatable element for the application 

group previously specified for this configure. Do not enter a trailing period after the file 

name. 

The relocatable element CBEP$$MCB is used during the collection of an OS 2200 based 

System to identify the MCB Common Banks. The MCB Common Bank is different for 

each application group. 

The default is MCB3*MCB$. 

UC UCS C Compiler 

Enter the name of the UC C Compiler file (commonly named SYS$LIB$*UC). Do not enter 

a trailing period after the file name. 

UC is required for the generation of OLTP UCS server systems. 

The default is *NONE*. 

B–12 78616323–000

Processor File Names Screen 2 


This subsection describes the fields on Processor File Names Screen 2. 

RSA Relational Syntax Analyzer 

Enter the name of the RSA library file associated with the application group within which 

your OS 2200 based System runs. Do not enter a trailing period after the file name. 

The default is SYS$LIB$*RSA. 

RSA Extended Mode Interface 

Enter the name of the RSA library file for the extended mode interface. If you do not 

intend using UCS mode, enter *NONE* in the UCOB UCS COBOL Compiler fields. 

Do not enter a trailing period after the file name. 

This is no longer a separate file, and it is included in the RSA file. If applicable, enter the 

same file name that you enter in the RSA Relational Syntax Analyzer field, 

described earlier in this subsection. 

If you are installing Host Builder, you must have installed LINK and the RSA Extended 

Mode Interface. Enter the processor file names in the appropriate fields. 

RDMS Relational Data Manager 

Enter the name of the RDMS library file associated with the application group within 

which your OS 2200 based System runs. Do not enter a trailing period after the file name. 

The default is SYS$LIB$*RDMS. 

ASSEMBLER (@MASM) 

Enter the name of the MASM processor file. Do not enter a trailing period after the file 

name. 

The default is SYS$LIB$*MASM. 

PDP Processor (@PDP) 

Enter the name of the file containing the PDP processor. Do not enter a trailing period 

after the file name. 

The default is SYS$LIB$*PDP. 

DDP Relocatable File Name 

The default is SYS$LIB$*DDP-PPC-1. If you intend to use Automatic Entries between 

hosts, SYS$LIB$*DDP-PPC-1 is the usual file name. 

78616323–000 B–13


Enterprise Application Environment may use the DDP-PPC DCA interface for Automatic 

Entries between hosts. Use this field to identify the file containing the DDP-PPC DCA 

relocatable elements. This is used to create the HUBDDP server program. 

DDN Relocatable File Name 

Enter the file containing the DDP-PPC TCP/IP relocatable elements. This value is used in 

creating the HUBDDN program. (Enterprise Application Environment may use the DDP- 

PPC TCP/IP interface for Automatic Entries between hosts.) 

The default is SYS$LIB$*DDP-PPC-4. If you intend to use Automatic Entries between 

hosts, this is the usual file name. 

LINK Program Linker 

Enter the name of the LINK program linker. Do not enter a trailing period after the file 

name. 

LINK is part of the operating system, and is required in the Runtime build. 

The default is SYS$LIB$*LINK. 

IRU Integrated Recovery Utility 

Enter the name of the file containing the IRU processor. Do not enter a trailing period after 

the file name. 

The default is SYS$LIB$*IRU. 

ARC File name 

Enter the name of the file containing the CBEP$$ARC relocatable if you require Automatic 

Recovery (ARC). ARC recovery is specifically for the Background Run. SYS$LIB*ARC is 

the usual name for the ARC file. If you do not require this feature, choose the default 

value of *NONE*. 

If a file is specified in this field, the Background Run is built so that it registers with ARC 

for software component recovery. ARC restarts the Background Run if an error causes 

termination. 

B–14 78616323–000


Common Bank Attributes Screen 

Use this screen to change the parameters controlling the data structures in the 

LINC$TABLES Common Bank. 

These parameters control the data structures in the LINC$TABLES Common Bank. 

Note: You would not usually change the default settings without specific instructions 

from your Unisys Support Center. 

Work Queue Size 

Enter a value in the range 1 through 999 is valid. The default is 200. 

A work queue entry is made in the tables Common Bank for some of the requests to the 

Background Run. The logic commands SLEEP;, MSG;, ACCEPT;, RUN;, and STOP; 

generate work queue entries. The work queue must be big enough to hold all of the 

requests that can be active or pending at any one time. 

Number of Slots 

Enter a value from 1 through 999. The default is 250. 

Data structures called slots exist in the LINC$TABLES Common Bank. A slot is allocated 

for each request being serviced by the Background Run. A request could be a SLEEP;, 

MESSAGE;, SEND.MESSAGE;, ACCEPT;, or RUN; logic command or a :RUN System 

command. 

Number of Items in the Pool 

Pool Size 

Under normal circumstances, the default of 50 should be used. 

The Pool is an area of memory used to hold database records. This field determines how 

many database records can be handled by the pool at any one time. 

Under normal circumstances, the default of 10,000 should be used. 

The Pool is an area of memory used to hold database records. This field defines the size 

of the Pool (in words). 

Maximum Number of Systems 

Enter a number in the range 1 through 999. The default is 64. 

78616323–000 B–15


This field contains the maximum number of Enterprise Application Environment Systems 

that you want to run simultaneously under this Runtime. 

B–16 78616323–000


Additional I-Language Banks Screen 

The BDI for the ILANGUAGE Common Bank for your Primary language is entered on the 

General Configuration Parameters screen, described earlier in this feature. 

If you intend having Host Builder messages translated, you must specify Common Bank 

BDIs for your secondary languages on the Additional I-Language Banks screen. Up to 

fourteen secondary languages may be specified. 

Additional I-Language Banks 

If you intend to have a multiple language Host Builder, you need to enter BDIs for the 

Common Banks into which your translated Host Builder messages will be loaded. 

The BDI for your primary language BDI is entered on the General Configuration 

Parameters screen. You can also make BDI entries for languages two through fifteen on 

this screen. 

The fields are labeled LINC$L02 BDI through LINC$L15 BDI. 

Enter up to fourteen BDIs for your secondary languages; that is, languages 2 through 15. 

The default value for each field is zero (0). 

78616323–000 B–17


HUB Configuration Parameters Screens 

Use the HUB Configuration Parameters screens to change the parameters controlling the 

data structures in the LINC$HUB Common Bank. The LINC$HUB Common Bank controls 

external Automatic Entries within multiple copies of Runtime that have the same BDI and 

HUB identifier. 

The two HUB Configuration Parameter screens are described in the following 

subsections. 

HUB Configuration Parameter Screen 1 

This subsection describes the fields on the first HUB Configuration Parameter screens. 

LINC$HUB BDI 

Enter the BDI of the HUB Common Bank to be used by this configuration set. 


HUB Configuration Identifier 

Enter the single-character identifier for the HUB Configuration to be used by this 

environment. This character is used to form the runid of the HUB Background Run 

controlling this configuration, as follows. 

 

Under normal circumstances, there would be only one HUB configuration for each host, 

but others may be defined for testing purposes. If so, you should also change the 

LINC$HUB BDI value. You must also make sure that the single-character identifier is 

unique on all hosts. 

The default is A. 

HUB Configuration Parameter Screen 2 

This subsection describes the fields on the second HUB Configuration Parameter screen. 

Work Queue Size 

Use this field to set the HUB work queue size. Enter a value in the range 1 through 999. 


A work queue entry is made for every Automatic Entry request made to the HUB 

Background Run. The work queue must be big enough to record all concurrent requests. 

B–18 78616323–000

Number of Slots 


Data structures called slots exist in the LINC$HUB Common Bank. A slot is allocated for 

each Auto request being serviced by the HUB Background Run. 

Use this field to specify the number of slots that may be used. Typically, the number of 

slots should be approximately 25 percent more than the sum of the number of work 

queue items and the number of items in the pool. 

Enter a value in the range 1 through 999. The default is 250. 

Number of Items in the Pool 

The Pool is an area of memory used to hold the database records being transferred to 

another System using an external Automatic Entry. 

Use this field to determine how many database records can be transferred at any one 

time. Enter a value in the range through 999. 


Pool Size 

The Pool size should be the product of the average size of database records being 

transferred using and external Automatic Entry, and the number of items in the Pool. 

Use this field to define the size of the Pool (in words). Enter a value in the range 1 through 

30,000. 

The default is 10,000. 

Maximum Number of Systems 

Use this field to specify the maximum number of Systems that you want to run 

simultaneously under this HUB. Enter a number in the range 1 through 999. 


Maximum Number of Hosts 

Use this field to control the number of independent hosts which can be connected to the 

HUB at one time. 


Maximum Environments / Host 

Use this field value to control the maximum number of copies of Runtime which can be 

defined in this HUB configuration. Enter a number in the range 1 through 64. 


78616323–000 B–19


Maximum No. of DDN Programs 

Use this field to control the maximum number of DDN (DDP-PPC TCP/IP) service 

programs associated with the HUB Background Run. Enter a number in the range 1 

through 64. Batch runs with the following runid will be started to service requests. 

 


Maximum No. of DDP Programs 

Use this field to control the maximum number of DDP (DDP-PPC DCA) service programs 

associated with the HUB Background Run. Enter a number in the range 1 through 64. 

Batch runs with the following runid will be started to service requests. 

 


Service Program Capacity 

Use this field to control the volume of requests each service program (DDN or DDP) may 

process before the HUB Background Run starts another service program to deal with the 

excess. The default is 64. 

OLTP Configuration Parameters Screen 

The OLTP Configuration Parameters screen contains two fields: 

• $OLTP-TM2200 Qualifier 

• $APP-GROUP-ID 

Use OLTP-TM2200 Qualifier to enter the name of the qualifier for the OLTP-TM2200 

installed product filenames. 

Use APP-GROUP-ID to enter the name of the UDS resource manager application group. 

You need this entry to use the Two Phase Commit option with your System. For further 

details about OLTP, see your Unisys e-@ction Enterprise Application Host Builder Guide. 

B–20 78616323–000


LRSS Configuration Parameters Screen 

Use the LRSS Configuration Parameters screen to change the parameters controlling the 

Remote Subroutine Server (LRSS). 

This subsection describes the fields on the LRSS Configuration Parameters screen. 

LINC$LRSS BDI 

Enter the BDI of the LRSS gate bank that is used to provide access to the TSU 

Subsystem for communication between Developer clients and the host. This BDI must 

be specified as an Application Level Extended Mode BDI. Application Level Extended 

Mode BDIs begin with 02 whereas Basic Mode BDIs begin with 04. 

The subsystem is installed by using MODE LRSS or MODE ALL at SOLAR install time. 


LRSS Configuration Identifier 

Enter the single-character identifier for the LRSS configuration to be used. This parameter 

identifies the LRSS TSU name to be used by this Runtime, so that A represents TSU 

Name LNCARS, B represents TSU Name LNCBRS, and so on. 

It is also used to form the runid of the TCP/IP server, as follows: 

 

The default is A. 

Notes: 

• Under normal circumstances, there would be only one LRSS configuration for each 

host, but you may want to nominate another for testing purposes. If so, you should 

also change the LINC$LRSS BDI value. You must also make sure that the singlecharacter 

LRSS configuration identifier is unique on all hosts. 

• The configuration file is referenced by the name TSUname*TSUname, and the 

element name is CONFIG. So if you enter A for the configuration identifier, the 

configuration file will be referenced by LNCARS*LNCARS.CONFIG. For details of the 

configuration file, see the section on Interfacing to Other Systems in your Unisys 

e-@ction Enterprise Application Runtime for ClearPath OS 2200 Administration Guide. 

The LRSS installation process creates the two dummy elements CONFIG and FILES/ 

6009 for reference and editing. The version (6009) is the port number specified in the 

configuration file. If you use another port number, you should also create a 

corresponding FILES/port-number element. In the FILES/port-number element you 

should specify, in SGS format, the files to be searched for the Object Modules that you 

want to call. 

• The TSU must be defined in the CMS1100. 

78616323–000 B–21


COMUS Run Parameters 

This subsection contains information on COMUS run parameters that are requested for 

the following tasks: 

• First Build of OS 2200 Based Software 

• Subsequent Builds of OS 2200 Based Software 

First Build of OS 2200 Based Software 

For the first BUILD of OS 2200 based Software, the COMUS parameters listed in the 

following table are requested. You may need to set up some of the COMUS parameters 

detailed under “Subsequent Builds of OS 2200 Based Software” on page B–22. 

Parameter Suggested Value or Action 

Project id LINCBUILD 

Runid BLINC 

Run options Transmit a space 

Run priority Transmit for default 

Tape equipment For example, U9Sor HICL 

Tape assign options TJ (unlabeled) or TF (labeled) 

Generation type TAPE/TAPE 

Permanent SGSs Transmit a space 

Maximum runtime 9999 

Maximum pages 99999 

Note: If more than one build of Runtime is currently running, the Project id must not 

duplicate the name of an active build of Runtime. 

Subsequent Builds of OS 2200 Based Software 

For each subsequent BUILD of OS 2200 based Software, the following COMUS 

parameters are requested. You may need to set up some of the COMUS parameters 

detailed under “First Build of OS 2200 Based Software” on page B–22. 

Parameter Suggested Value 

MASTER reel Reel number of the Release tape or the previous BUILD 

output tape (see comments following the table) 

NEWMASTER reel Reel number of the output tape (see comments following 

the table) 

B–22 78616323–000

Reel Numbers 


The Master and Newmaster reel numbers have additional options, as follows: 

 

The options value indicates standard tape assign options, type is the equipment type, and 

expiry is the number of days from the current date. 

Optionally, include RING or NORING to indicate whether the tape is to be loaded with or 

without a Write ring, respectively. 

For example: 

Parameter Suggested Value 

Generation id 01, 02, and so on. The generation id is displayed on the 

sign-on line after the version value. Do not use the 

apostrophe character ('). Site specific. 12 characters. 

Heading Optional text for your reference. 

Reason Optional text for your reference. 

New change number Transmit a space. (If installing a Unisys-supplied EIF or 

site-local code, enter the change number.) 

Type of generation UPDATE. 

Additional SGSs Transmit a space. 

Runtime name Name as used for the Runtime name on the General 

Configuration Parameters screen. 

 

78616323–000 B–23


B–24 78616323–000

Appendix C 

Terminal and Printer Support 

This appendix covers: 

• Supported Terminal Attributes 

• Foreign Terminal Support 

Supported Terminal Attributes 

Data attributes that are supported by different terminal types are indicated by an x in the 


Attribute UTS20 

SVT1120 

UTS30 

UTS40 UTS60 DS7 

BLINK x x x x 

BRIGHT – – – – 

RESET x x x x 

REVERSE x x x x 

SECURE – x x x 

UNDER – x x x 

DIM x x – x 

LEFTBAR – – – x 

RIGHTBAR – – – x 

UPPERSCORE – – – x 

UNDERSCORE – – – x 

KEISEN – – – x 

BOX – – – x 

Kanji (ED ;K) – – – x 

Mixed Data (Kanji) – – – x 

COLOR – – x x 

78616323–000 C–1


Implementation of Highlighting 

Further points to consider are: 

• UTS20 supports either DIM or REVERSE (but not both), depending on Control Page 

setting (AB/LI, AB/RV). 

 

 

• DIM on DS7 terminals always causes the field to be displayed in YELLOW. 

• On PC-emulation, Low Intensity (DIM) is configurable by the user and may actually 

appear as BRIGHT. 

• The DIM attribute may affect the color displayed on UTS60s, as shown in the 


Color Dim Normal 

Ebony BLACK BLACK 

Blue BLUE BLUE 

Magenta MAGENTA HOT PINK 

Red RED ORANGE 

Green GREEN LIME 

Cyan CYAN CYAN 

Yellow BROWN YELLOW 

White GREY WHITE 

For the older Step-Board versions, low-intensity colors and normal colors are inverted. 

If this is the case, use the :STN System command to set up your terminal as type 

UTS60I. For more details, see “Preparing for Installation of Enterprise Application 

Environment Software” on page 2–1. 

• On PCs, the background color can only be the DIM color (that is, a yellow background 

will always be brown on PCs). 

• The only effect the BRIGHT attribute has is to override the DIM attribute. BRIGHT will 

carry through to REVERSE, BLINK, and so on. 

• When using the following attributes, every character to which they apply has to be 

transmitted to the screen (that is, an underlined line always results in 80 characters 

being sent). Normally, the suppression of trailing spaces applies, but use of the 

following attributes inhibit this process. 

 

 

 

 

 

 

 

• Underlining does not work on PCs using terminal emulation. 

C–2 78616323–000


• Although underlining does not work on PCs, Enterprise Application Environment 

cannot distinguish between true terminals and PC emulators, and sends the underline 

sequences regardless. 

• Delimiters are always shown as DIM, with no other attributes (except on DS7, where 

UPPERSCORE, UNDERLINE, and UNDERSCORE apply to the delimiters). 

Note: If you enter N in the Show Delimiters field on the 1100 Series System 

Environmental Options screen, the delimiters are spaces. 

Compatibility with MCP Based Systems 

Highlighting attributes are handled differently in MCP based and OS 2200 based 

Systems. For MCP based Systems, a highlighting attribute is turned on by a control 

character that occupies the character immediately before a data or Display item. 

For OS 2200 based Systems, the attribute is turned on by an FCC that is contained in the 

first character of the data or Display item. For compatibility with MCP based Systems, a 

data or Display item with highlighting attributes should not start in column one. 

78616323–000 C–3


Foreign Terminal Support 

This subsection provides information for the following tasks: 

• Associating a type of terminal (as identified by standard OS 2200 based 

communication software) with a terminal type supported by Enterprise Application 

Environment. 

• Inserting local code into Enterprise Application Environment to handle nonstandard 

terminals. 

Terminals Supported by Enterprise Application Environment 

Enterprise Application Environment supports standard Uniscope terminals (SVT1120, 

UTS20, UTS40, UTS60), Kanji-capable DS7 terminals, and IBM 3270-style terminals. 

Terminals Not Supported by Enterprise Application Environment 

Terminals not supported by Enterprise Application Environment can be dealt with in one 

of the following ways: 

• Map the unsupported terminal type to a supported terminal type. Whenever a 

terminal of the unsupported terminal type uses a System, Enterprise Application 

Environment will apply screen handling as for the supported terminal type. 

• Insert your own screen handling code into Enterprise Application Environment, using 

standard software hooks that are described in “Inserting Your Own Code to Handle 

Foreign Terminals” on page C–8. This code is associated with a special terminal type, 

and the mapping with the external terminal type is also required. 

Note: Screen handling code refers to the conversion of data items, Display items, and 

Data Attributes into a series of characters and control code sequences suitable for sending 

to the terminal in order to display an Ispec screen (and the reverse process to handle input). 

How Enterprise Application Environment Determines Terminal 

Types 

The first time a terminal is used to sign on to a System, Enterprise Application 

Environment determines the terminal type and stores it in the S_T_N record. This value 

may subsequently be changed by using the :STN System command, or by modifying the 

S_T_N record directly (for example, by using IPFSQL). 

Internally, Enterprise Application Environment uses a single character to define each 

terminal type stored in the S_T_N record. When a transaction starts, this character is read, 

and uses is used to insert a descriptive terminal type into GLB.STYLE and to determine 

which screen handler to use. 

Note: The value of GLB.STYLE must be used with the :STN command. 

C–4 78616323–000


The following table lists terminal types and corresponding GLB.STYLE values. 

Type GLB.STYLE Description 

3 SNA3270 IBM terminal using SNANET Uniscope emulation 

5 UTS20L UTS20 with Alternate Brightness = LOW 

6 UTS20R UTS20 with Alternate Brightness = REVERSE 

7 DS7 

8 UTS60I UTS60 with color intensities reversed 

A SVT1120 

B UTS40 

C UTS60 

D UTS20 

E UTS30 

F IBM3270 IBM terminal using native mode 

G IBM3178 

H IBM3278 

I IBM3279 

J LT300 

K NOFORM 

L NOFORM 

M ActiveLINC 

N ActiveLINC 

a FOREIGN Unsupported Foreign terminal type (see comment 

following table) 

b FOREIGN2 Unsupported Foreign terminal type 

c FOREIGN3 Unsupported Foreign terminal type 

d FOREIGN4 Unsupported Foreign terminal type 

0 Not 

determined 

4 NOF terminal 

9 NOF passoff 

(see comment following table) 

78616323–000 C–5


Type a, b, c, d 

A lowercase alpha terminal type value (a, b, c, or d) represents foreign terminals which 

are not directly supported by Enterprise Application Environment, but may be supported 

by the addition of your own local code, as described later in this appendix. 

Type 0 

A value of 0 indicates that the terminal type is not yet known. When a transaction is 

initiated from such a terminal, Enterprise Application Environment will examine the value 

of PTTYP in the AUX Area of the incoming MCB Packet, in order to determine the 

terminal type. 

Note: For Kanji-capable Systems, the System Data item GLB.MFLAG is set to Y. This 

item is used in determining the terminal type from the PTTYP value. For example, PTTYP 

22 is a UTS60 terminal if GLB.MFLAG is N, but a DS7 terminal (UTS60 with Kanji capability) 

if GLB.MFLAG is Y 

The following table lists the PTTYP values and the internal terminal type codes they 

generate. 

Value of PTTYP Standard Terminal Codes Kanji-capable Terminal Codes 

5 3 (SNA3270) 7 (DS7) 

14 D (UTS20) 

15 B (UTS40) 

21 E (UTS30) 

22 C (UTS60) 7 (DS7) 

23 F (IBM3270) 

34 D (UTS20) 7 (DS7) 

(other) D (UTS20) a (FOREIGN) 

Points to Note 

• Enterprise Application Environment does not support UTS400 terminals. Any 

terminal, configured as a UTS400 terminal, will be regarded as an IBM3270 terminal 

that uses SNA/NET software Uniscope emulation. 

• Terminals configured as UTS60 that are Kanji-capable are regarded as DS7 terminals. 

• If Enterprise Application Environment is unable to determine the terminal type, it 

defaults to UTS20, or to FOREIGN if Kanji-capable. 

• The :STN System command enables you to change the terminal type to any of the 

recognized values. When the :STN command is used to set the terminal back to the 

default type, Enterprise Application Environment determines the terminal type again, 

as in the previous table. 

C–6 78616323–000

Customizing the Mapping of PTTYP Values 


You can use the following ways to customize the mapping of PTTYP values onto terminal 

types. 

• Modify the internal translation table, GET$STYLE 

• Use PERM$SGS statements 

You can skip the process in which the terminal type is assessed from PTTYP, by using the 

following methods: 

• Preallocate S_T_N records 

• Use STNUTIL to predefine default terminal types 

These methods enable you to predefine what type particular terminals should be, so that 

Enterprise Application Environment does not need to use PTTYP to determine the type. 

These methods are described in “Inserting Your Own Code to Handle Foreign Terminals” 

on page C–8. 

Modifying the Table 

The GET$STYLE element contains the table (TERMTABLE) that is used to translate 

PTTYP values to terminal types. To add extra entries to the TERMTABLE, use COMUS, 

and then rebuild and reinstall. 

The format of the entries in TERMTABLE is: 

 

The parameters in this format are described in the following table. 

Field Contents 

pttyp Decimal PTTYP value 

type1 Character identifying the terminal type when not Kanji-capable 

type2 Character identifying the terminal type when Kanji-capable 

To establish the line number at which to insert your new entry, you may list the 

GET$STYLE element, which is contained in the SLIB$ file on your Release tape. 

The advantage of this method is that the changes apply immediately to all Systems within 

your copy of Runtime. 

Using PERM$SGS Statements 

This method of providing for additional PTTYP values cannot be applied in the following 

cases, as there is no ICP source available. 

• Systems installed using Object-Only transfer 

78616323–000 C–7


• Host Builder 

• Report Output Control System (ROC) 

Note: Where the ROC.MODE; logic command or ROC_I Ispec is used to enter ROC, the 

terminal type is correctly transferred into ROC. 

The advantage in using the PERM$SGS mechanism is that it does not require your copy 

of Runtime to be rebuilt. 

Extra PTTYP values can be configured by using SGSs within the PERM$SGS file for your 

copy of Runtime (the PERM$SGS file with your Runtime name as its qualifier). This will 

be used by all your Systems within that environment. 

The format of these SGSs is 

 

The field value parameters in this format are described in the following table. 

Field Contents 

pttype Decimal PTTYP value 

type Character terminal type 

value Y, YES, or ON (Kanji-capable) 

N, NO, or OFF (Not Kanji-capable) 

The MFLAG and the value fields are optional. If not present, then the PTTYP value 

corresponds to the specified terminal type, whether your System is Kanji-capable or not. 

If it is present, then the PTTYP value only corresponds to the specified terminal type if 

GLB-MFLAG has the appropriate value. 

For example, with an SGS of TERMINAL 29,D Enterprise Application Environment 

interprets terminals with a PTTYP value of 29 as type D (UTS20). 

With an SGS of TERMINAL 29,7 MFLAG,Y Enterprise Application Environment only 

interprets terminals with a PTTYP value of 29 as type 7 (DS7) if GLB.MFLAG is set to Y. 

These PERM$SGS statements cause the appropriate lines to be inserted into your 

System ICP when the System is installed or reconfigured. Therefore, when PERM$SGS 

statements are added or changed, each of your Systems will need to be regenerated, 

reinstalled, or reconfigured. 

Inserting Your Own Code to Handle Foreign Terminals 

To provide support for additional foreign terminal types, perform the following steps: 

1. Define the terminal type in the table of valid types and styles within the GET$STYLE 

element, as described in “Modifying the Table” under “Customizing the Mapping of 

PTTYP Values” on page C–7. 

C–8 78616323–000


2. Insert local code into the various routines that Enterprise Application Environment 

executes for foreign terminal screen handling. 

3. Create a COMUS PCF to make the changes for steps 1 and 2. 

4. Apply the PCF, rebuild, and reinstall. 

Defining Foreign Terminal Types 

If a terminal has an internal one-character type code that is lowercase alphabetic (a, b, c, 

or d), Enterprise Application Environment regards it as a foreign terminal, and will use the 

foreign terminal routines in preference to the standard screen handling routines. 

By default, Enterprise Application Environment defines the following foreign terminal 

types: 

 

 

 

 

Although these types are defined and can be specified in the S_T_N record or with the 

:STN command, Enterprise Application Environment does not provide any code to handle 

these terminal types. 

To use these foreign terminal types or to add new ones, alter the TERMTABLE table in 

the GET$STYLE element. Each entry in this table is three words long (12 bytes), and 

contains the GLB.STYLE name for the terminal. Only the first ten characters of the name 

are used. Each entry is indexed using the terminal type value, that is, the first entry is for 

0, the second for 1, and so on, in ascending ASCII sequence. Unused letters have dummy 

entries to reserve their positions. These dummy entries are indicated by question marks. 

The four entries, (FOREIGN, FOREIGN2, FOREIGN3, and FOREIGN4) can be changed to 

have any GLB.STYLE name desired, by using a COMUS PCF to patch the table. Additional 

GLB.STYLE names can be associated with the other lowercase alphabetic types. Once 

this TERMTABLE Table is changed, you can use the GLB.STYLE values in :STN System 

commands and in the STNUTIL program. 

Inserting Your Own Screen Handling Code 

At various points during a transaction, screen-specific text sequences are created to be 

sent to terminals. In all such cases, the terminal type is checked and if it is a foreign 

terminal, then an alternative routine is used. 

Local screen handling code is required in the routines listed in the following table. 

Element Routine(s) Function 

X-BUILDS X$BUILDS Creates Ispec output screens. 

X-DSUB X$DLNCBR Translates text for MESSAGE; commands. 

Called from the Background Run. 

78616323–000 C–9


Element Routine(s) Function 

You should assemble your code, insert it into the OMLIB$ file on the Release tape, and 

then rebuild and reinstall. 

IBM 3270 Terminal Support 

General Information for IBM 3270 Users 

Terminal Operating Modes 

Operating modes through SNANET: 

X$DLSS Translates output in response to System 

commands. Called from LINC17LSS. 

X$DRCBR Translates output from the ROC Background 

Run. Called from RC1. 

X-GETDATA X$GETDATA Interprets Ispec input. 

X-QUICKSCAN X$QUICKSCAN Examines terminal input, returning text with 

control sequences removed. 

X-SPECIALS X$AUTOXMIT Creates a sequence to position the cursor on 

the @ sign, and then to retransmit the 

screen. 

X$BLNKSCREEN Sends a sequence to clear the screen. 

X$ENDMSG Creates the text for the Unisys sign-off logo. 

X$SIMFNK Simulates a function key by analyzing the 

terminal input, and inserting a value into the 

MCB Packet PKEY field. 

X$XMITCHAN Creates a XMIT VAR control page sequence. 

• Uniscope Emulation mode 

• ASCII Native mode 

Enterprise Application Environment sends and receives ASCII characters in IBM 3270 

Datastream format, with SNANET performing the conversion to and from EBCDIC for 

communication with IBM terminals. 

C–10 78616323–000


• EBCDIC Pass-Through mode 

Enterprise Application Environment sends and receives EBCDIC characters in IBM 

Datastream format. Enterprise Application Environment itself does the EBCDIC to 

ASCII conversion; that is, SNANET can pass the messages directly to and from the 

IBM terminals. This mode enables the extended highlighting features of IBM 

terminals to be used. The following table lists the IBM terminal types supported. 

Terminal Type Functionality SNANET Operating Mode 

SNA3270 Basic Uniscope Emulation 

IBM3270 Basic ASCII Native 3270 Datastream 

IBM3178 Basic EBCDIC Native 3270 Datastream 

IBM3278 Extended Highlighting EBCDIC Native 3270 Datastream 

IBM3279 Extended Highlighting and 

Color 

Screen Field Attributes 

EBCDIC Native 3270 Datastream 

• Basic Functionality 

The following basic screen field attributes are provided: 

– Protection 

– Numeric-only 

– Security (Video off) 

– Two levels of brightness 

• Extended Highlighting 

Extended highlighting provides you with the following additional attributes: 

– Blinking 

– Reverse Video 

– Underlining 

If your terminal has Extended Highlighting functionality, only one of the attributes can 

be shown on any one field at a time. That is, if more than one of these attributes 

applies to a field, only one will take affect. For example, the BLINK attribute overrides 

REVERSE VIDEO and UNDERLINE, while REVERSE VIDEO overrides UNDERLINE. 

Only IBM 3279 terminals are color-capable, and you may specify foreground (text) 

colors for your Ispec fields on these terminals. These terminals do not support the 

use of background colors. However, when you use color with the REVERSE VIDEO 

78616323–000 C–11


attribute, the foreground color becomes the background color, and the text appears in 

black. Colors that you specify in your field definition are mapped to IBM terminal 

colors, as shown in the following table. 

The Status line always appears in Reverse Video Turquoise. 

The BRIGHT attribute has no effect on IBM 3279 terminals. Vary the color to achieve 

a similar effect. 

Host Builder Restriction 

You cannot use Host Builder from an IBM 3270 terminal. 

IBM Printers 

This feature does not apply to IBM printers. Enterprise Application Environment continues 

to use Uniscope Emulation mode when sending report output to IBM printers. To send 

output to an IBM 3270 printer, in the LNET file define the PID as an IBM 3270 type 

device. The default is that the output is in UTS Pass-through mode. 

For more information on supported printers, see your Unisys e-@ction Enterprise 


Installation Notes for IBM 3270 Terminal 

Before using EBCDIC Pass-through mode in your system, you must apply changes to 

both SNA/NET and CMS1100 to enable EBCDIC data to be sent through SNANET. For 

details of these PCRs, contact your Unisys Support Center. 

If you wish to use EBCDIC Pass-through mode, you will need to apply these PCRs, and 

include the following SGS card in your PERM$SGS file: 

 

Color Specified Color on IBM Terminal 

Ebony Neutral 

Red Red 

Yellow Yellow 

Blue Blue 

Magenta Pink 

Cyan Turquoise 

White Neutral 

The level parameter is the level number of SNANET (for example, 3R1E). This is currently 

ignored. 

C–12 78616323–000


Without this PERM$SGS statement, you cannot use the IBM3178, 3278, and 3279 

terminal types, and all IBM terminals will operate in ASCII Native mode or Uniscope 

Emulation mode. Any attempt to change a terminal to one of these types using the :STN 

System command will lead to the following error message: 

 

It is recommended that you include this SGS card in the PERM$SGS file of Runtime. 

Note: To correctly align numeric fields on the new IBM terminal types, you must reedit 

and regenerate your existing Systems. 

Technical Notes for IBM 3270 Terminals 

How Enterprise Application Environment Sends Screens to an IBM 3270 

When building up a Native-mode 3270 Datastream sequence to be sent to an IBM3270 

terminal, Enterprise Application Environment performs the following operations: 

• All data items (including Usage Inquiry and protected) have the modified data tag 

(MDT) bit set. 

• Display items do not have the MDT bit set. 

• Enterprise Application Environment uses SBA (Set Buffer Address) or RA (Repeat to 

Address) sequences where possible to reduce the number of characters to be sent. 

• Null characters are used instead of spaces, except for embedded spaces in data item 

text. 

• Trailing spaces on data items are replaced by null characters not sent when an Ispec 

is initially displayed. 

• Enterprise Application Environment places an Start Field (SF) or an Start Field 

Extended (SFE) at the beginning and end of each data item, and wherever an attribute 

is to change (for example, at the end of a line to turn off Reverse Video). 

• If two items are joined together on the screen, or one item ends in column 80 and 

another starts in column one of the next line, the last character of the first item will be 

overwritten by the SF (or SFE) character unless the two items have the same 

attributes. This includes a Display item immediately followed by a data item. 

• When you press PDl-5 or CLEAR, Enterprise Application Environment effectively 

clears the screen by filling it with null characters, except for the status line. The status 

line contains the system name and an unprotected SF character at Row 24 Column 

80, enabling data entry from Row 1 Column 1. 

• When Enterprise Application Environment sends text to the status line only (for 

example, an error message), columns 78, 79, and 80 do not change. These columns 

usually contain the SF for the @ sign, the @ sign itself, and an SF character in column 

80. 

• When an Ispec that is to be sent is already on display at the destination terminal, 

Enterprise Application Environment sends only the Status line text and data item 

values. It does not send SF characters of Display items. 

78616323–000 C–13


• Signed numeric items (other than Usage Inquiry items) have an SF (or SFE) character 

inserted between the value and sign parts. This has the effect of separating the value 

and sign with one space character. This applies whether or not delimiters are being 

used. 

• The scrolling action of Repeat.From screens is not supported for IBM 3270 terminals. 

A Repeat.From Ispec will therefore behave as though it is not a Repeat.From Ispec. 

How Enterprise Application Environment Receives Screens from an IBM 

3270 

SNANET always performs a Read Modified operation to receive input from an IBM 3270 

terminal, so that it only receives text for fields that have the Modified Data Tag (MDT) bit 

set. Enterprise Application Environment sets the MDT bit for all data items before 

sending the screen, forcing text for every data item to be retained. For more details, see 

“How Enterprise Application Environment Sends Screens to an IBM 3270", earlier in this 

appendix. 

The Read Modified operation also ignores any null characters, and since Enterprise 

Application Environment uses null characters instead of spaces where possible, the total 

number of characters sent on input is minimized. 

Terminal Operating Modes 

IBM 3270 terminals operate in one of the following modes over SNANET. 

• Uniscope Emulation (INT-1) 

• ASCII Native 

• EBCDIC Pass-through 

Enterprise Application Environment uses the terminal type field in the S_T_N table to 

keep track of the SNANET mode under which a terminal is currently operating. The 

following table shows the possible values of this one-character field. 

S_T_N Value Terminal Type SNANET Mode 

3 SNA3270 Uniscope Emulation 

F IBM3270 ASCII Native Mode 

G IBM3178 EBCDIC Pass-through 

H IBM3278 EBCDIC Pass-through 

I IBM3279 EBCDIC Pass-through 

C–14 78616323–000


When Enterprise Application Environment receives input from a terminal, it uses the 

S_T_N terminal type field to set the fields relating to the terminal type in the MCB 

packet. SNANET then drives the terminal in the appropriate mode. Therefore, when the 

current mode being used by SNANET differs from that stored in the S_T_N table, a 

change of SNANET operating mode occurs. 

Note: Without the SNANET EBCDIC PERM$SGS statement, Enterprise Application 

Environment regards S_T_N values G, H, and I as equivalent to F. That is, it only operates 

the terminal in ASCII Native mode. 

The MCB fields used to determine the current operating mode of a terminal are PTTYP 

and PRTYP. The value of the S_T_N field relates to the values of PTTYP and PRTYP as 

shown in the following table. 

PRTYP PTTYP S_T_N Value 

23 5 3 

23 23 F 

23 31 G 

23 31 H 

23 31 I 

78616323–000 C–15


C–16 78616323–000

Appendix D 

Related Product Information 

The following publications are used as reference sources for OS 2200 based System 

users who have completed training courses. They are not intended as self-teach 

documents. See your local Unisys representative for information on available training 

courses. 

Unisys e-@ction Enterprise Application Runtime for ClearPath OS 2200 


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

general administration of Systems for OS 2200 based hosts. 

Unisys e-@ction Enterprise Application Programming Reference Manual 

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

System Data items used in creating Systems. 

Unisys e-@ction Enterprise Application Executive Overview - The Business 

Case (7833 2145) 

This document is an introduction to Enterprise Application Environment for executive and 

general readers. 

Unisys e-@ction Enterprise Application Technical Overview - The Business 

Case (7833 2152) 

This document is an overview of Enterprise Application Environment features and 

facilities for more technically oriented readers. 

Unisys e-@ction Enterprise Application Host Builder Guide 

This document describes the use of Host Builder to create and maintain user information 

systems. 

Unisys e-@ction Enterprise Application Programming Reference Handbook 

(7861 6067-001) 

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

commands used in Host Builder. 

78616323–000 D–1

Related Product Information 

Unisys e-@ction Enterprise Application Developer Installation and 


This document describes the installation of Developer in standalone or multiuser 

environments and the administration of the Developer working environment, including 

repository administration, backup procedures, security and other issues. 

Extended Transaction Capacity (XTC) Conceptual Overview 

This overview discusses the various components and processes that constitute an XTC 

system and provides information to help in the planning of an XTC system. 

D–2 78616323–000

Glossary 

A 

access class 

For 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 mainframe Enterprise Application Systems, 

enabling fast-track navigation to required functions. Also referred to as the Action field. 

Activity 

A group of Objects which together perform a business function. 

Ad Hoc Inquiry 

A mainframe facility used for making inquiries on an Enterprise Application Database. 

Administration Client 

A tool for administering Enterprise Application user systems and their associated 

databases. The Administration Client can be used on a remote workstation or on the 

runtime server. The Administration Client communicates with the Administration Services 

using Remote Procedure Call (RPC) to perform the requested operations. 

Administration group 

A group of user accounts within a Windows domain for people who have privileges to 

administer systems, for example, to add a new database to an Enterprise Application 

environment. The Administrator is a separate role from the Windows Administrator, 

although the two roles may be performed by the same person. Most administration 

functions are performed from the Administration Client interface. 


The manual that contains instructions for administering and operating Enterprise 

Application Systems on a particular host type. 

Administration Services 

The set of Windows services on the runtime server that communicates with 

Administration Clients using RPC. These services perform various administrative functions 

on behalf of the Administration Clients. 

Administrator 

Person responsible for administration of a computing environment. 

78616323–000 Glossary–1

Glossary 

archive 

Copy files to a directory as protection against accidental loss, deletion, or damage. 

Audit Archive File 

An archive file of audit records. 

Audit Domain 

An Audit Domain defines the scope of audit activity for Developer. An Audit Domain can 

be a Model or a Business Segment. 

auditing 

Auditing records events that occur in the Developer and Developer Security environments, 

providing a history of changes made to the Developer Repository. 

Audit Store 

The Audit Store holds audit records. Because the function of auditing is to record 

operations that affect a Developer Repository, there is one Audit Store for each Repository. 

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. Not applicable to Copy.From Ispecs. 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. 

Automatic Profile 

The Profile created by Developer for a Component with an Ordinate. This Profile cannot be 

seen in the Model Directory, but can be viewed as part of a System in the Systems 

Directory. 

B 

Background Run 

For OS 2200 Systems, a background run that controls certain functions; for example 

recovery, report handling, and setting up of Common Banks. There is one Background Run 

for each Runtime. 

Glossary–2 78616323–000

Glossary 

Background window 

The window behind the first window you see when Developer is initiated. The Background 

window provides access to the various functions of Developer. 

backup 

banner 

Make a copy of a database or subset of a database. 

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. Base 

year is defined using the Primary Database Options screen in Host Builder and using the 

Business Segment Options dialog box in Developer. It may be accessed through the 

System Data item GLB.BASE. See relative day number. 

binary 

bind 

Object files that may be .int, .gnt, .exe, or .dll files. A runtime transfer using export or 

import transfers the runtime files, not the source COBOL files. 

The task of coupling object files with executable files for dynamically linked program code. 

Ensures that externally referenced procedures or subprograms are available to a main 

program. 

breakpoint 

A feature of the Developer Test Debugger that stops logic execution in response to a 

certain state of the system. 

buildable LINCIIDIR 

The Enterprise Application installation directory is defined by the environment variable 

LINCIIDIR. A LINCIIDIR that contains the object packages necessary to build executables 

using object packaging is a buildable LINCIIDIR. A buildable LINCIIDIR is necessary to use 

object packaging to maintain your Enterprise Application environment. 

Builder 

The software used to generate Specifications (Business Models) as applications. 

Generation is the process of generating a complete set of source files and then compiling 

and linking those files to create a set of executables. Through Builder, a Developer 

workstation can generate an application to a target host runtime environment. 

Builder Client 

The Builder Client runs on the workstation that initiates the generate process and controls 

the generation of the system according to its specified elements and options. It also 

includes the Generate Client/Server interface to the Builder Server. 

78616323–000 Glossary–3

Glossary 

Builder Server 

The Builder Server runs on the host to which the Builder Client is connected. It compiles 

the Enterprise Application System generated by the client and provides the runtime 

environment for the application. 

Bulk Option screens 

A group of screens in Host Builder that enable options for several Ispecs, Reports, Profiles, 

or Global Logics to be entered together. 

Business Model 

Repository containing details of Business Segments (Specifications) held by Developer. 

Business Rules 

Information entered as text which supports an Element. 

Business Segment 

Part of a Model that provides the definition for an Enterprise Application System in 

Developer. Equivalent to a Specification in Host Builder. 

C 

Change control 

A method for tracking changes to Specifications. 

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 Specification. 

Contrast with Patch identifier. 

class 

client 

See access class, security class. 

A Windows program, typically running on a workstation, that works cooperatively with one 

or more programs or services running on a server computer. In some cases, the client 

program may reside on the server computer, but uses the network interfaces to 

communicate with the server program or service. In Runtime for the Windows 2000 and 

Windows NT operating systems, there are two distinct types of client: 

1. An operational tool, such as the Administration Client, which deploys, manages, and 

maintains user systems. 

2. An end-user client, such as Graphical Interface Workbench, that provides workstation 

users access to Enterprise Application user systems. This class of client includes 

user-written clients developed in languages such as C++ and Visual Basic. 

Client Listener 

This service listens for and accepts connection requests from the Administration Client. 

Glossary–4 78616323–000

Glossary 

client/server 

A distributed architecture in which client workstations communicate with servers through 

a network. For instance, a client typically provides initial processing, data gathering 

functionality and the user interface. It then communicates the data and requests to a 

server for further processing. 

Column name 

For Ad Hoc Inquiry, an SQL term equivalent to Data Item. 

compile 

To create object files from source files. 

Component 

(1) A business resource such as a customer, product or vendor. (2) A store of static data 

about a business resource. Consists of a screen layout and associated logic (Pre-Screen 

logic, Pre-LINC logic, and Main logic). Together with Events, Components form the 

fundamental building blocks of a System. See also Ispec, Standard Component, Table 

Component, Memo Component, Multiple Ordinate Memo Component. 

Component Enabler 

The product with which users can build their own GUI interfaces, or Views, to Systems. 

These Component Enabler applications use the Remote Access Server to communicate 

with Systems on the host environment. Component Enabler allows applications to current 

Web technology and the Enterprise NT world. See also Remote Access to Enterprise 

Application. 

Component Profile 

For Ad Hoc Inquiry, a Profile over one Component. Contrast with Event Profile. 

Component record 

For Ad Hoc Inquiry, an individual database record for a Component. Equivalent in SQL 

terminology to a row. 

COMSTP Program 

A pre-compiled program that contains the necessary logic for routing of user transactions 

in a MCP based System. 

COMUS 

For OS 2200 based Systems, a product used to build Runtime before installation. See 

SOLAR. 

Control tables 

Tables created for the control of an environment within each Oracle database (SID) 

associated with the environment. Examples are PROCTAB and LSYS. 

78616323–000 Glossary–5

Glossary 

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 

A user-specified recovery point within a Report. In the event of a failure, recovery will 

restore the environment to the last successful Critical Point, then resume execution at the 

location of the Critical Point. 

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, Report, or logic. 

Data Dictionary 

A collective name for the Local and Global data dictionaries. See Local Data Dictionary, 

Global Data Dictionary. 

Data Display (DAD) 

Optional descriptive text for a Data Item, used in status messages in place of the name of 

the Data Item. Defined using the DATA.DISPLAY Data Attribute. 

Data Item 

The variable used to enter, manipulate, store, and display data. For example, Ordinates, 

Setup Data items. 

Database ID 

The two-character identifier for either an ORACLE or SQL Server database. This identifier 

was previously referred as the ORACLE SID. See ORACLE SID. 

Database Management Utility (DMU) 

A utility that enables you to maintain your Enterprise Application Database. Use DMU 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 Systems), and creating 

ORACLE SIDs (for Systems based on the UNIX operating system). See also Griffin 

Database Management Utility (GMU). 

debug settings 

A set of breakpoint, watch, and debug options that can be saved to a file and loaded into 

a Developer Test Debugger session as needed. 

Glossary–6 78616323–000

Glossary 

DEPCON 

The Unisys DEPCON software application is a comprehensive print-management and file 

distribution solution for mixed-platform networks. Coupling the Enterprise Application 

Environment with DEPCON increases the design possibilities and flexibility of Reports. 

See the DEPCON Software Configuration and Operations Guide and “Using DEPCON 

Reports” in the Unisys e-@ction Enterprise Application Developer User Guide. 

deploy 

To implement a set of Enterprise Application executables and a database on a host 

machine. The result of deployment is the creation of an application on the host. 

Deployment Server 

The Windows server on which an application is installed and executed. Does not have 

Micro Focus COBOL installed. 

Deployment Services 

Windows programs installed with Runtime for the Windows 2000 and Windows NT 

operating systems to perform specific functions, such as listening for and accepting 

connection requests on behalf of an environment. A collective term for the Administration 

and Generation services. 

Design Audit 

Analyzes a Business Segment, Functional Area, or Activity, and lists any items that may 

indicate poor design that will impact performance in a generated system. 

Developer 

Workstation based development tool for creating and maintaining Business Models 

(Specifications). From Developer, Business Models are transferred to host based Builder 

for generation and deployment, or generated directly to a target host. Formerly known as 

LDA III or LINC Development. 

Developer Test 

A workstation testing environment for Developer which includes a logic Debugger. 

Formerly known as LINC Development Runtime. 

Development Environment 

A collective term for the tools used to design, develop, and generate Enterprise Application 

Systems. Includes Developer, Builder, and utilities. 

Development System 

See Developer and Builder. 

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. 

78616323–000 Glossary–7

Glossary 

Direct Report 

A Report that uses the Report Output Control System (ROC), and which sends output 

directly to an output device and not to the ROC database. See also Report Output Control 

System. Contrast with Standard Report. 

Display item 

A string of descriptive information displayed on an Ispec screen layout or Report Frame. 

DLL 

DMU 

E 

Editor 

EIF 

Dynamic Link Library, contains one or more functions that are compiled, linked, and stored 

separately from the processes using them. 

See Database Management Utility. 

An Enterprise Application facility for specifying logic for Ispec and Report processing. 

Engineering Interim Fixes (EIFs) are used to distribute new features, fixes, customer 

requests and newly validated versions of support software. 

Element 

Collective term for the individual parts of the Business Model. An Element may be any of 

the following: Activity, Functional Area, Language, Object, or Wildcard. 

Enterprise Application Database 

The database created in the generation of an Enterprise Application System. Used for 

storing data. 

Environment 

The operating environment and supporting services for applications on a Windows server. 

Each environment is created by a separate installation of Runtime for the Windows 2000 

and Windows NT operating systems. There may be multiple environments on a single 

Windows server. Each environment includes one or more databases. Each database may 

contain zero or more user systems. 

Environment database 

The database associated with an environment that contains control tables. These tables 

control the environment for all the user systems in the environment. Synonymous with 

control tables. 

Environmental Options screens 

Screens in Host Builder that enable you to define generate options for your Specification. 

Glossary–8 78616323–000

Event 

Glossary 

(1) An activity performed by an organization, for example a sale, purchase, or payment. (2) 

A store of data about an activity performed. An Event consists of a screen layout and 

associated logic (Pre-Screen logic, Pre-LINC logic, and Main logic). Together with 

Components, Events form the fundamental building blocks of a System. See also Ispec. 

Event file 

For Ad Hoc Inquiry, the file containing the Event records. 

Event Profile 

For Ad Hoc Inquiry, a Profile over one or more Events. Contrast with Component Profile. 

Event record 

For 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 applications to customers. They are 

the compiled set of application files which are ready to install and run. Contrast this with 

Objects. 

EXE file 

export 

A Windows native executable file. 

To copy an Enterprise Application System to a file for transfer to another environment. 

Extended Language Message System (ELMS) 

An OS 2200 based facility that provides translatable versions of messages used by 

software. 

extent 

A contiguous block of disk space assigned by Oracle. Extents are used in data segments 

(table data storage), index segments, rollback segments, and temporary segments. An 

extent is a unit of database storage space allocation. When an extent is used up, Oracle 

allocates a new one. 

External Automatic Entry 

An Automatic Entry to or from an external source, such as another System. See Automatic 

Entry, HUB. Contrast with internal Automatic Entry. 

Extract file 

A non-database (text) file created or read by a Report. 

78616323–000 Glossary–9

Glossary 

F 

Filegroup 

A discrete part of an SQL Server database. Filegroups in the same database can be stored 

on different physical devices. See tablespace. 

Fireup Ispec 

The Ispec that is displayed on your terminal when you sign on to an Enterprise Application 

System. 

Forms Translation Utility (FTU) 

A utility that enables you to modify screen layouts, Teach screens, Data Displays, and 

translatable Global Setup Data items of your System without regeneration. FTU can also 

be used to modify Enterprise Application Software. 

Frame 

A number of Report lines containing display text and Data Items that is output as a single 

unit when the Frame is invoked by Report logic. 

Function Point Analysis 

A technique for estimating the size of an existing or future information system, using a unit 

of measurement called a Function Point. 

Functional Area 

(1) A group of Activities. (2) A concept used to group Activities for the purpose of loading 

into Builder. 

G 

garbage collection 

An Administration Client function that aids the compacting of Oracle database tables. 

Generalized Interface (GLI) 

A facility that enables a external program to initiate transactions into an Enterprise 

Application user system. 

generate 

Perform the tasks necessary to create an Enterprise Application System on a host, 

including: 

• Importing Enterprise Application user system files from the development 

environment or another server 

• Deploying a runtime system and a database 

Generate Group 

A specified group of Reports that can be generated together. 

Glossary–10 78616323–000

Glossary 

Generate Set 

A named set of values for generating a particular System from a Specification; for example, 

for a particular host type. 

Generate Threads 

A number of parallel generate tasks that can be initiated on the workstation. 

GLI 

See Generalized Interface. 

Global Data Dictionary 

(1) A data dictionary that controls the use of Data Items over all Specifications (for Host 

Builder) or Business Segments (for Developer). (2) Part of GLOBAL Specification. (3) See 

also Data Dictionary, Local Data Dictionary. 

Global Logic 

Part of a Specification that can be reused in more than one part of your Specification or 

Business Segment. Inserted into Ispecs, Reports, or Global Logics by using the INSERT; 

logic command. See Insertable Global Logic, Performable Global Logic. 

Global Setup Data Block 

An internal logic block used to group Global Setup Data Items. Grouping Global Setup Data 

Items for example, by Ispec would mean that when you recompiled that Ispec for generate 

purposes, only those Global Setup Data Items grouped in that Block would be recompiled, 

rather than all of them. Global Setup Data Items can only be defined within Global Setup 

Data Blocks. 

Global Setup Data item 

A type of Setup Data item that can be used by any Ispec or Report logic within a 

Specification or Business Segment. Global Setup Items can only be defined within Global 

Setup Data Blocks. See Setup Data item, Group Global Setup Data item. 

GMU 

GNT 

graph 

See Griffin Database Management Utility. 

The file extension for Micro Focus "generated" (native instruction set) COBOL code. Files 

in this format have intermediate compilation and execution times. Contrast with INT. 

Pictorial representation of a number of Elements and the relationships between the 

Elements. Provides access to all information supporting the represented Elements. 

Graphical Interface Workbench 

The workstation software that makes it possible for end users to access a deployed user 

system through a graphical user interface. Formerly known as PowerClient. 

78616323–000 Glossary–11

Glossary 

Griffin 

Database Management System used as the underlying database software for Builder for 

the UNIX operating system. See also ORACLE. 

Griffin Database Management Utility (GMU) 

The equivalent of the Database Management Utility (DMU) for Griffin. 

Griffin Universe 

A Griffin term for a logical storage area that may contain one or more 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 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. 

H 

Home position 

Top left corner of a character-based screen. Often used as the position from which 

commands are entered. 

Home screen 

For Ad Hoc Inquiry, the base screen from which the main functions are chosen. 

host 

Computer on which an Enterprise Application Environment application is running. 

Host List 

(1) In the host environment, the list of valid host types for which Builder can perform 

reserved word checking and generation of applications. (2) In Developer, a list of valid host 

computers that can be used by a Generate Set. 

Host Name 

The name of the specific host to be used for a function. 

Glossary–12 78616323–000

Glossary 

Host Specification 

The name of the target host to be used for the process, its TCP/IP or network address, and 

host type. See Host Name. 

HUB 

The facility that controls external Automatic Entries between Enterprise Application 

Systems. See Automatic Entry, external Automatic Entry. 

HUB Background Run 

For OS 2200 Systems, a background run that processes external Automatic Entries. There 

is one Background Run for each Runtime. See also HUB. 

HUB Listener 

This service listens for and accepts HUB connection requests from other Enterprise 

Application user systems. 

I 

ICP 

import 

See Initial Control Program (for OS 2200 based Systems) and Ispec Control Program (for 

Unix based Systems). 

To copy application files into the directory where they will be deployed. When importing 

files from another Windows server, the import operation also decompresses the export file 

into its constituent application files. 

Initial Control Program (ICP) 

The program that controls the generated Ispec subprograms in OS 2200 based Systems. 

Contrast with COMSTP Program (for MCP based Systems) and Ispec Control Program (for 

Unix based Systems). 

Insertable Global Logic 

A logic sequence and/or a screen layout that can be copied into any number of Ispecs and 

Reports. Contrast with Performable Global Logic. 

Installation Guide 

The manual that contains instructions for installing and configuring Enterprise Application 

Systems on a particular host type. 

INT 

The file extension for a file in Micro Focus interpretive code format. Files in this format 

compile quickly, but are slow to execute. Contrast with GNT. 

interdatabase access 

The accessing of the database of an OS 2200 based System by another OS 2200 based 

System. 

78616323–000 Glossary–13

Glossary 

internal Automatic Entry 

An Automatic Entry from within the same Enterprise Application System. See Automatic 

Entry. Contrast with external Automatic Entry. 

interrogation point 

For 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. In the Enterprise Application 

Environment, an Ispec models an entity or activity in the real world. An Ispec also specifies 

the user interface, the processing rules, and the database structure to be used to represent 

it in the deployed user system. (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 Enterprise Application Unix 

based Systems. Contrast with COMSTP Program (for MCP based Systems) and Initial 

Control Program (for OS 2200 based 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 

language 

A natural language in which text components of the system can appear. The default 

language is usually English, but can be any language you chose. An application can have 

up to 14 languages concurrently installed. Users, or the software itself, can choose to 

display screens, Reports, or prompts in any one of the installed languages. 

LCOPY Utility 

A utility that provides a means of backing up, maintaining and controlling Specifications, on 

the same or different machines. 

LDL Listing Utility 

A facility in Host Builder used for printing a Specification. 

Glossary–14 78616323–000

Glossary 

LINCTEMP 

The temporary directory. Its location is defined by the environment variable LINCTEMP and 

defaults to \bin. 

LINQINQ 

A user account with read-only privileges used to perform inquiries against Enterprise 

Application Control and User tables. 

literal 

A literal is a value used directly by a system, without requiring any named storage area. A 

literal may also be used in many logic commands in place of Data Items, and to define the 

characteristics of Setup Data items. 

Local Data Dictionary 

A data dictionary that controls the use of Data Items within a single Specification. See also 

Data Dictionary, Global Data Dictionary. 

lock 

Inhibit other users from reading and/or updating a specific record or window. Developer 

has three forms of locking: 

• An automatic soft lock that is set up whenever you attempt to modify an Object. This 

lock is released when the transaction ends or you cancel the operation. 

• A manual lock that emulates the behavior of the the host environment resource 

locking. 

• If Version Control is installed, a Version lock that is set when an Object is checked out 

of the Version Control Bank. 

locked query 

For 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. 

logic 

Series of commands defined using the Editor that can be executed by an Object such as 

a Component or an Element. 

logical printer 

A logical printer is a printer name specified in a Report. You must map a logical printer to a 

physical printer before printing. 

logical reorganization 

Transforms the data from the existing physical database schema into the format of the 

newly developed logical schema in memory each time the data is accessed. File formats 

are not altered. Allows a new database schema to be run against the existing old database 

schema prior to a physical reorganization. 

78616323–000 Glossary–15

Glossary 

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. 

Long name 

Long names of Objects are up to 30 characters and allow double-byte characters, such as 

Kanji, to be used for an Object's name. They also allow you to give Objects more 

meaningful names. Long names must be used in conjunction with shorter names which 

can be used by the host environment. 

LSM 

M 

See Security Module. 

Main Logic 

User-specified Ispec logic that is executed after any Pre-LINC logic and 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) In mainframe Systems, a screen field for every Standard, Table, and Multiple 

Ordinate Memo Component used to indicate the database maintenance action request. 

MCP environment 

The component of the A Series or ClearPath HMP NX machine that runs the MCP 

operating system. 

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 Systems only. See Ispec. 

Menu Assistance 

A mainframe Painter facility that provides assistance when painting an Ispec screen layout 

or Report Frame. 

menu format query 

A query created using the various selection screens of Ad Hoc Inquiry. Contrast with SQL 

format query. 

Glossary–16 78616323–000

Message Translation Utility (MSGTRANS) 

A part of the Multilingual System (MLS) that co-ordinates the output of translated 

messages. 

MLA 

Model 

See Multiple Language Mode. 

Glossary 

Database containing details of Business Segments (Specifications) held by Developer. A 

synonym for Repository. 

Model Directory 

A graphical representation of the hierarchical structure of the Business Model. An essential 

part of the Developer navigation facilities. 

Module 

Specification that is a subset of a Module Master. When generated a Module produces a 

complete Enterprise Application System. See also Module Master. 

Module Master 

A complete Specification that contains defined parts (Modules) that can be generated as 

separate Enterprise Application Systems. See also Module. 

Multilingual System (MLS) 

An MCP based facility that provides data structures and associated access methods to 

store and retrieve the translatable text used by software. See also Message Translation 

Utility. 

multiple language facilities 

A collective term for the facilities that enable an Enterprise Application System to be 

translated and used in up to fifteen different languages, from a single Specification. 

Multiple Language Mode (MLA) 

A facility in mainframe Enterprise Application Environment that enables a language name 

or number to be defined. See multiple language facilities. 

Multiple Ordinate Memo Component 

A Memo Component with one or more Ordinates defined by a specified Profile (that is 

sometimes referred to as its Automaint Profile). See also Component, Standard 

Component and Automaint Profile. 

N 

navigation tree 

In the Administration GUI, a depiction of the Windows domains, servers, environments, 

databases, and systems. The navigation tree is updated as the user makes changes to the 

environment. 

78616323–000 Glossary–17

Glossary 

NOF 

NOFORM 

See NOF. 

A facility for interfacing to and from an Enterprise Application System using Non-Formatted 

Input/Output, a message-oriented interface between an Enterprise Application user 

system, and usually, an external system and terminal. The interface to Graphical Interface 

Workbench uses NOF. 

Non-Formatted Input/Output (NOF) 

See NOF. 

O 

OBJ 

Object 

The file extension for a file in standard object code format. Files in this format compile 

slowly, but execute quickly. Files in .obj format cannot be executed unless bound. 

Collective term for a Component, Event, Inquiry, Report, Global Logic, or Profile. 

object files 

In Runtime for the Windows 2000 and Windows NT operating systems, the .obj files that 

result from compiling source files. Object files usually require linking to other program 

modules before they can be executed. 

Object Packaging 

Object Packaging allows the creation of executables from supplied Enterprise Application 

object files, the installation of Enterprise Application software, the installation of EIFs, and 

the maintenance of your Enterprise Application environment. It also allows the creation of 

new object and executable packages which can include supplied EIFs. Packages can be 

created for distribution and as backups. 

Objects 

(1) Objects are one of two methods of distributing Enterprise Application software to 

customers. They are the set of object files which must be built into executables on your 

site before Enterprise Application Environment can be run. Object files are built using 

Object Packaging. Contrast this with Executables. (2) In Runtime for the Windows 2000 

and Windows NT Operating Systems Administration Client, anything that appears in the 

navigation tree, including servers, client machines, environments, databases, and user 

systems. 

Offline interface 

A facility for passing batches of high-volume transactions from external systems into an 

Enterprise Application user system. 

Glossary–18 78616323–000

OLTP 

See Online Transaction Processing. 

Glossary 

OLTP Buffer Definition file 

An OLTP Buffer Definition file holds the data format for communicating with external OLTP 

Servers. 

OLTP View Ispec 

In the host environment, an OLTP View Ispec (OVI) is used to store an OLTP View 

Description file. This file holds the data format for communicating with external OLTP 

Servers. 

On Change Statistical Routine 

A statistical routine (for example, AVERAGE;) that can be performed on a Data Item as part 

of an ON.CHANGE; logic command. 

Online Transaction Processing (OLTP) 

A generic method for transferring transactions between systems. 

ORACLE 

Relational database management system used as the underlying database software for 

Enterprise Application Systems based on the UNIX or Windows operating systems. 

ORACLE is produced by Oracle Corporation. See also Griffin. 

ORACLE Hints 

A facility that allows users to add information to SQL SELECT statements. Correct use may 

improve database performance, but incorrect use may reduce database performance. 

Using Oracle Hints in an SQL statement overrides the Oracle Optimizer. Users are able to 

specify: 

• Which index is used in the database access operation 

• Whether the index should be read in reverse order 

ORACLE SID 

An occurrence or instance of an Oracle database. The Oracle SID is a 1- or 2- character 

identifier. An ORACLE term for a logical storage area that houses user systems and control 

tables and may contain one or more databases. The SID identifies a particular database 

occurrence. Equivalent of Griffin Universe. See also tablespace. 

ORACLE tablespace 

A discrete part of an Oracle SID. Tablespaces in the same Oracle SID can be stored on 

different physical devices. 

Ordinate 

The Data Item of a Component that acts as the unique identifier for a record. The access 

path to individual Component records. 

78616323–000 Glossary–19

Glossary 

P 

pack 

A definition within Enterprise Application of the location where part of a user system or an 

environment database is stored. This may be either a tablespace or a directory path. 

Pack Association 

The Pack Association specifies the location in which the files of the generated system will 

be stored on the target host computer. 

Pack View 

The Pack View in Developer lists all the packs used in the Systems options of the currently 

open Model. This specifies the Pack associations, or the location in which that part of the 

System or database is stored. See Pack. 

Painter 

patch 

A facility of Enterprise Application Environment used to define an Ispec screen layout or 

Report Frame layout. 

A set of changes to a Specification made over a period of time by users signing on to 

Enterprise Application Environment under a specific Patch identifier value. 

Patch identifier 

A number used to identify and group changes to a Specification by one or more users. 

Applies when the Patch identification option is selected for that Specification. Contrast 

with Change identifier. 

Performable Global Logic 

Logic that can be executed by any number of Ispecs and Reports. Contrast with Insertable 

Global Logic. 

physical delete 

Removal of a record from a database or repository. 

physical reorganization 

Copies and transforms the physical data from the existing database into a form which 

matches the new database schema. 

population 

Also called Expected Number. The maximum number of records expected to be stored in 

the database for an Ispec. 

Pre-LINC Logic 

User-specified Ispec logic that is executed before the Ispec Main logic. 

Glossary–20 78616323–000

Pre-Screen Logic 

A section of user-specified Ispec logic that is executed before the screen layout is 

displayed on the terminal. 

Glossary 

Primary Database Options screen 

The screen in Host Builder for setting basic options and parameters for an Enterprise 

Application System. The screen is displayed whenever a new Specification is 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. 

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 

The Ad Hoc Inquiry facility that validates an entered query and transforms it into a standard 

internal code and format. See also query transformation. 

Query Front End 

The Ad Hoc Inquiry user interface that allows a query to be entered. 

Query Optimizer 

The Ad Hoc Inquiry facility that selects the most efficient way to access the database for 

a query. 

Query Output Handler 

The Ad Hoc Inquiry facility that enables users to manipulate query output. 

78616323–000 Glossary–21

Glossary 

Query Processor 

The Ad Hoc Inquiry facility that interprets the query code and runs the query against the 

database. 

Query Processor report 

For Ad Hoc Inquiry, the program that performs the functions of the Query Processor. 

query transformation 

For Ad Hoc Inquiry, the process performed by the Query Compiler to convert a validated 

query into a standard internal form. 

queued query 

For Ad Hoc Inquiry, a query waiting for resources to begin execution. 

R 

recovery 

The process of restoring database files from a backup and performing roll-forward recovery 

from a current transaction log file. Failed Reports must be restarted manually, as they are 

not automatically restarted by the recovery process. 

relation name 

For Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an Event 

Profile. Also called a table. 

relationship 

An association between two Elements. Relationships may be a result of design (for 

example, added using a graph) or logic (for example, adding a FLAG; command to an 

Ispec). 

relative day number 

A date expressed as the number of days since January 1 of the base year. The relative day 

number of January 1 of the base year is zero. See also base year. 

Remote Access to Enterprise Application 

The Remote Access server resides on the Runtime host and provides the basis for 

communication between user Views and Enterprise Application Systems. Can be used 

with Graphical Interface Workbench as well as Component Enabler Viewer applications. It 

performs services previously provided by WDP. Formerly known as RATL Server. See 

Component Enabler, Graphical Interface Workbench, Workstation Driver Program (WDP). 

reorganization 

The process by which the physical database for a System is updated to match the logical 

definition held in the Repository. See also logical reorganization and physical 

reorganization. 

Glossary–22 78616323–000

Report 

Glossary 

Part of a Specification generated and used to produce output or to carry out specialized 

batch processing of a database. Consists of Report Frames and Report Main logic, and a 

number of options that define the operation and output of the Report. 

Report Frame 

Layout that contains display text and Data Items, and some associated logic that is part of 

a Report. The logic is executed (often to define the Data Items in the layout) and then the 

layout is included in the Report output. Report Frames are accessed as single units from 

the logic of Report Frame or from Main logic of the Report. 

Report Group 

A set of Reports that are generated as a group. All the Reports assigned to the group are 

generated by selecting the Report Group for generation. 

Report Initiation Program (RIP) 

An MCP based utility that enables you to execute a line printer Report or terminal printer 

Report in batch mode. 

Report Output Control System (ROC) 

A utility that provides control over the output of a Report. 

Repository 

Database containing details of Business Segments (Specifications) held by Developer. A 

synonym for Model. 

reserved words 

Words reserved for system use. Each architecture has its own set of reserved words. 

resource locking 

A facility of the host environment that prevents access to parts of a Specification by more 

than one user at a time. 

ROC Background Run 

For OS 2200 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 

Runtime. 

rollback segment 

In Oracle, a segment that contains an image of data before committing to a transaction. 

Used for rolling back uncommitted transactions, read consistency, and recovery. 

row 

For Ad Hoc Inquiry, an SQL term equivalent to a Component record or an Event record. 

78616323–000 Glossary–23

Glossary 

RPC 

Remote Procedure Call, a Windows protocol that runs background services that are 

necessary for the operation of the Administration Client and Runtime for the 

Windows 2000 and Windows NT operating systems. 


A collective term for the software programs required to operate, control and audit an 

Enterprise Application System and its Database. 

Runtime platforms 

The platforms on which applications developed and built using Enterprise Application 

software runs: Windows 2000, Windows NT, OS 2200, MCP, and the UNIX Operating 

System. 

Runtime Test Environment 

Software that enables testing and debugging of Enterprise Application Systems on 

mainframe hosts. 

S 

schema 

screen 

Database structure. 

In Developer, a screen is a means of entering a transaction. Screens are usually designed 

for a single purpose and so each System function will usually have a specific screen. 

Screens may have associated logic. 

Screen Build mode 

A host environment Painter facility that is used to specify a new Ispec screen layout. 

search expression 

For Ad Hoc Inquiry, a logical expression used in a search list to define records to be 

included in query output. 

search list 

For Ad Hoc Inquiry, the part of a query that determines whether records will be included in 

the output. 

security access 

For Ad Hoc Inquiry, full access to all queries. 

security class 

For Ad Hoc Inquiry, a type of user access to queries. See access class. 

Glossary–24 78616323–000

Glossary 

security level 

A value from 0 through 9 that is assigned to a specific user or terminal to restrict access 

to functions. 

Security Module (LSM) 

A utility which provides security facilities for Enterprise Application environments. 

select list 

For Ad Hoc Inquiry, the part of a query that defines the Data Items to be included in the 

output. 

Setup Data Array or Global Setup Data Array 

Use a Setup Data array or Global Setup Data array to store multiple values. An individual 

value is accessed by specifying values for the indexes of the array. Indexes are numeric 

Setup Data items or Global Setup Data items. 

Setup Data item 

A Data Item used in memory only for data manipulation by an Ispec or Report. See also 

Global Setup Data item, Group Setup Data item. 

Shadow Report 

Part of a Report used to produce additional output separate from that produced by the 

primary functions of the Report. 

SID 

The two-character identifier of an Oracle database. In Runtime for the Windows 2000 and 

Windows NT operating systems, database, Database ID and Oracle SID are synonymous. 

Sleeping Report 

A Report that, by the use of the SLEEP; logic command, stops executing for a 

predetermined number of seconds or until reactivated by your runtime System. 

SOLAR 

For OS 2200 Systems, a product used to install Enterprise Application Software. 

sort expression 

For Ad Hoc Inquiry, a logical expression used in a sort list to define output sort order. 

sort list 

For Ad Hoc Inquiry, the part of a query that defines the order of the output. 

Specification 

(1) The source definition of an Enterprise Application System. Specifications consist of 

screen definitions, database definitions, and processing logic. (2) The result of specifying 

a Business Model using Developer. (3) The source from which an Enterprise Application 

System is generated. 

78616323–000 Glossary–25

Glossary 

spooler 

See Terminal Printer Spooler. 

SQL format query 

An SQL query entered in free format in Ad Hoc Inquiry. Contrast with menu format query. 

SQL Server 

A relational database management system that is optionally used as the database software 

for Enterprise Application Systems based on Windows operating systems. SQL Server 7.0 

is a product of Microsoft Corporation. See also ORACLE. 

Standard Component 

A Component type that requires a single Ordinate. See also Component. 

Standard Report 

A specific type of Report that uses the Report Output Control (ROC) 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 

(1) In Enterprise Application terminology, a general term for a method used to identify 

users. (2) For UNIX based Systems, station equates to user name, while for OS 2200 

based Systems, station equates to userid. 

status line 

A line on a screen for the display of system messages. 

structure 

(1) In the host environment, part of a Specification that can be selected (for example, for 

printing, copying, or extraction). (2) For Ad Hoc Inquiry, part of an Enterprise Application 

Database that can be the subject of a query. 

structure list 

For Ad Hoc Inquiry, the part of a query that defines the structures to be included. 

Sub Items 

A Global Setup Data item that has been defined for a Group Global Setup Data item or a 

Setup Data item that has been defined for a Group Setup Data item. 

Sub Scripts 

A Data Item that has been defined as an index for either a Global Setup Data Array or a 

Setup Data Array. 

Supervisor 

A facility of the host environment enabling administration-level functions. 

Glossary–26 78616323–000

System 

Glossary 

In Builder each System consists of a configuration of elements and the options assigned 

to these elements. The options define the generation options for the host-based 

environment on which the system will be deployed. 

System command 

A command to assist in the operation of a System or Report. Formerly known as a colon 

command. 

System Data item 

Data Item that is automatically part of your Specification. Used for accessing or setting 

parameter or control-type data in logic. Some System Data items are stored automatically 

in your Enterprise Application Database (for example, MAINT). 

System Directory 

A graphical representation of the hierarchical structure each System configured for a 

Business Model. It lists the current and previous configurations for each System, showing 

the Elements assigned to the system and the processing options defined for them. The 

System Directory provides the basis for the build process. 

System Element 

Collective term for the individual parts of the System. An Element may be any of the 

following: Business Segment, Bundle, Ispec, Global Logic, Profile, Report Group, or 

Report. 

System Specification 

A specification that represents the configuration of Elements within a deployed host 

system, and the generation options required to generate a set of executables for the 

specified host environment. See Generate Set. 

T 

table 

For 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. 

target host 

The name of the specific host on which a generated Enterprise Application System will be 

deployed. See also Host Specification. 

78616323–000 Glossary–27

Glossary 

Teach screen 

A user-written screen display of information about an Ispec, intended to provide online help 

for end users at runtime. 

Terminal Printer Spooler (TPS) 

An MCP based Enterprise Application Utility that enables users to manipulate the output 

of a Report to terminal printers. 

TPS 

Trace 

See Terminal Printer Spooler. 

A facility to monitor the execution of logic of an Ispec or Report in your Enterprise 

Application System. Contrast with Runtime Test Environment. 

transaction log file 

File to which before and after images of all Developer transactions are written for recovery 

and restart purposes. 

Translation Screen 

A copy of an Ispec screen that is modified to create a secondary language version. 

U 

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.) 

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. 

Glossary–28 78616323–000

Usage Output Ispec 

An Ispec that is written to the database, but does not have a screen display. 

Glossary 

user system 

An instance of a Specification. Generally refers to a generated and deployed Enterprise 

Application user system. 

user system tables 

Tables that contain end user data (Ispec data) of a specific Enterprise Application user 

system. 

V 

Validation EIF 

Validation EIFs are a special type of EIF which provide support for newly validated versions 

of Enterprise Application Environment support software such as ORACLE, Griffin, COBOL, 

and Tuxedo. See EIF. 

value expression 

For 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 an Enterprise Application System by version 

number, description, and generation date. 

Version Control 

An optional feature of Developer that provides source control of versionable Enterprise 

Application objects such as Model definitions, data dictionary items, Ispecs, Profiles, and 

Reports. 

W 

watch 

A feature of the Developer Test Debugger that monitors, or 'watches', the state of a Data 

Item. When logic execution is stopped during debugging, the value of the watch item is 

displayed in the Watch Window. 

Wildcard 

Represents relationships with objects outside the Business Segment, or outside the 

Model. For example, a flat file that is read or extracted, or an external system called by the 

Enterprise Application System. 

78616323–000 Glossary–29

Glossary 

Workstation 

In a client-server environment, a PC or workstation that is connected to a server, usually 

by a network. The workstation runs the client portion of client-server software. 

Workstation Driver Program (WDP) 

A server-resident component of Runtime for the Windows 2000 and Windows NT 

operating systems. Its function is to pass data between the Graphical Interface 

Workbench workstation and the application on the runtime host. It also converts screen 

definition files during the direct generation of an application. 

Workstation Driver Program (WDP) listener 

This service listens for and accepts connection requests from Graphical Interface 

Workbench clients. 

Workstation listener port 

A Windows TCP/IP port assigned to the Workstation Driver Program (WDP) listener or a 

particular environment. This value must be changed to a unique number for each user 

system environment during installation. 

Glossary–30 78616323–000

Index 

A 

ALIB$ file 

security attributes, 3–9 

application groups 

allocating queue items, 2–12 

configuring EXEC with, 2–11 

local, 3–12 

Runtime, 2–11 

shared, 3–12, 3–13 

XTC System, 3–12 

Application Recovery Feature (ARF), 3–16 

attributes 

supported IBM 3270, C–11 

supported terminal, C–3 

B 

background runs 

starting, 3–18 

C 

change control 

installation options for, 3–25 

CLOSEDOWN program, 3–19 

CMS 1100 

configuration of, 2–15 

COMUS 

Common Bank Attributes screen, B–15 

General Parameter screens, B–4 

Processor File Names screens, B–11, B–13 

COMUS parameters 

additional I-Language bank, B–17 

Common Bank attribute, B–15 

Common Bank BDI, B–6 

configure, B–1 

HUB configuration, B–18 

LRSS server configuration, B–21 

OLTP configuration, B–1 

preview of, B–1 

Remote Subroutine Server configuration, 

B–21 

run, B–22 

Software build, B–22 

Configuration Process Main Menu screen, 3–4 

configuration sets 

creating, 3–4 

configure 

changing defaults for, 3–3 

COMUS parameters for, B–1 

files created during, A–5 

78616323–000 Index–1 

D 

databases 

files created when generating, A–6 

deinstalling 

Host Builder, 3–34 


Deployment 

XTC with, 3–13 

DIM attribute 

terminals supporting, C–2 

disk storage 

requirements for, 2–4 

E 

EXEC 

application groups for, 2–12 

configuration of non-OS2200 LCOPY tapes, 

2–15 

configuring application groups for, 2–11 

configuring freespace files for, 2–15 

configuring parameters for HVTIP, 2–14 

EXPRGENVIRON configuration parameter, 

2–14 

large files configuration of, 2–15 

EXPRGENVIRON 

configuring EXEC for, 2–14

Index 

F 

FCC 

terminal attributes in, C–3 

files 

Enterprise Application-created, A–1 

generated database, A–6 

loading Host Builder, A–4 

System generated, A–5 

foreign terminals 

inserting code to handle, C–8 

supported, C–4 

freespace files 

configuring for EXEC, 2–15 

G 

generate 

files created during, A–5, A–6 

generating a migrated System, 4–11 

GLB.MFLAG, C–6 

GLB.STYLE, C–4 

GLB.WORK, 2–13 

Graphical Interface Workbench, 4–10 

migrating Systems using, 4–10 

non-use of, 4–10 

support for, 4–10 

H 

hardware requirements, 2–4 

highlighting attributes 

IBM 3270 terminal support of, C–11 

supported terminal, C–3 

Host Builder 

configuring, 3–27 

deinstalling, 3–34 

identification mode for, 3–26 

installing, 3–22, 3–27 

loading files for, A–4 

loading from Release tape, 3–23 

multiple copies of, 3–29 

overview of, 2–1 


Host Builder messages 

translation of, B–17 

HUB 

Configuration Parameter screens, B–18 

considerations for, 2–9 

installation modes for, 3–10 

HVTIP 

library for XTC System, 3–13 

HVTIP parameters for 

EXEC, 2–14 

Index–2 78616323–000 

I 

IBM 3270 terminals 

modified data tag (MDT), C–13 

installation 

COMUS parameters for, B–1 

HUB, 3–10 


XTC Deployment, 3–13 

Installation Verification Procedure (IVP), 3–9 

installing 

Host Builder, 3–22 

registered packages from, 3–8 

registering output tape, 3–8 

runstream modifying, 3–8 

Runtime copies, 3–21 

Unisys-supplied changes, 3–2 

intersystem communications (see HUB), 2–9 

K 

Kanji 

support of, C–6 

L 

LCOPY 

compatibility with Host Builder releases, 

4–2 

loading Specifications, 4–2 

migration, 4–2 

line resequencing 

inhibiting, 3–25 

locking 

resource, 3–25 

LRSS server 


lt300 terminal support, 2–4

M 

MCB 


MCB/CMS 

trigger characters for, 2–16 

memory 


Message Control Bank (see MCB), 2–15 

migration 

environmental settings, 4–4 

extract format for data interchange, 4–5 

first generation after, 4–11 

Global Setup Data blocks, 4–4 

Graphical Interface Workbench, 4–10 

localization, 4–6 

procedure, 4–1 

rounding from COMPUTE commands, 4–5 

using LCOPY, 4–2 

modified data tag (MDT) 

for IBM 3270 terminals, C–13 

O 

OLTP 


online help 

Configuration Parameter screen, B–3 

OS 2200 based software (see System software), 

2–6 

output tape 

SOLAR registration of, 3–8 

P 

PAEXEC 

installing Runtime with, 3–14 

switching between hosts in, 3–14 

page size 

calculating, 2–13 

setting default for, 3–17 

STNUTIP calculating for, 2–14 

parameter changes 

building, 3–5 

PTTYP values 

mapping terminal types to, C–7 

providing for additional, C–7 

terminal types in, C–6 

Index 

78616323–000 Index–3 

R 

RDMS 

table storage area, A–2 

RDMS tables 

details of, 3–19 

unsaved of, 3–20 

reinstalling 


Release tape 

COMUS registration of, 3–3 

files on Host Builder, 3–22 


Remote Subroutine Server 


Report Output Control System (ROC) 

installing, 3–30 



reserved words 

loading of, 3–24 

target host, 3–24 

resource locking 

installation options for, 3–25 

REVERSE attribute 

terminals supporting, C–2 

ROC 

configuring, 3–31 


loading from Release tape, 3–30 


runstream 

modifying when installing, 3–8 


before using, 3–15 

configuration process for, 2–7 

deinstalling, 3–34 

files created when installing, A–2 


installing copies of, 3–21 


PAEXEC with, 3–14 

reinstalling, 3–11, 3–19 

release tape for, 3–7 


SOLAR installation of, 3–7 

switching control of, 3–11

Index 

S 

screen handling code 

inserting your own, C–4, C–9 

local, C–9 

SGS statements 

terminal type, C–7 

SNA3270 terminals 

support of, C–10 

Software 

about, 2–1 

products of, 2–1 

software requirements, 2–6 

SOLAR 

installing Runtime, 3–9 

special privileges 

set up of, 3–8 

Specifications, 4–2 

generating after migration, 4–11 

loading using LCOPY, 4–2 

station details 

STN System command, C–4 

STN System command 

station details, C–6 

STNUTIL program 

commits by, 2–14 

System software 

applying changes to, 2–17 

installing required, 2–11 

mandatory requirements, 2–6 

optional, 2–7 

pre-installation tasks for, 2–11 


Systems 

files created when generating, A–5 

setting maximum number of, B–16 

S_T_N records 

terminal type in, C–4 

T 

templates 

target host, 3–24 

temporary files 

deleting, 3–33 

deleting installation, 3–28 

terminal records 

TIP files holding, 2–12 

terminal type 

lowercase alpha value of, C–6 

terminals 

attributes supported for, C–3 

default types of, C–7 

foreign, C–4, C–8, C–9 

supported, 2–4, C–1, C–4 

types of, C–4, C–5, C–6, C–7 

unsupported, C–4 

TERMTABLE 

terminal type in, C–7 

TIP Error Handling Program 

defining, 3–17 

TIP file 

holding terminal records with, 2–12 

TIP Library 

reloading, 3–16 

TIP memory 

allocation of, 3–15 

TIP memory groups 

changing, 3–15 

creating, 3–15 

reloading, 3–16 

translation 

Host Builder messages, B–17 

trigger characters, 2–16 

Index–4 78616323–000 

U 

UCS Subsystems 


UDS software 


Unisys-supplied changes 


Universal Data Systems (see UDS), 2–16 

X 

XTC 

application groups with, 3–12 

COMUS configuring for, 3–13 

HVTIP library with, 3–13 

installing Deployment with, 3–13 

SOLAR installing for, 3–13 

UDS facility for, 3–12 

Z 

:STN command (station details), C–4, C–6

Unisys 

*78616323-000* 

78616323-000

Runtime for ClearPath OS 2200 Installation and Configuration Guide

Create successful ePaper yourself

Delete template?

Save as template?