Runtime for ClearPath MCP Installation and Configuration Guide

Unisys e-@ction 

Enterprise Application 

Runtime for ClearPath 

MCP 

Installation and Configuration Guide 

Copyright © 2000 Unisys Corporation. 

All rights reserved. 

Release 3.1A 

November 2000 78616208-001 

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 

Notations .....................................................................................1–1 

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

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. Pre-Installation .................................................................. 2–1 

Products and Terminology ..............................................................................2–1 

Host Builder ................................................................................2–1 

Runtime .......................................................................................2–2 

System Transfer ..........................................................................2–2 

Release 3.1 Media Summary .........................................................................2–3 

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

Software Requirements .................................................................................2–6 

General Software Requirements .................................................2–6 

Network Software Requirements ...............................................2–6 

Other Software Release Compatibility ........................................2–7 

Setting Up Your Host ......................................................................................2–8 

Configuring Terminal Devices for Enterprise Application Environment ..........2–9 

COMS Station Definitions ...........................................................2–9 

Configuration Settings for Terminals Qualified for Enterprise 

Application Environment ......................................................2–10 

Using IBM 3270 Terminals ........................................................2–14 

Section 3. Installing and Configuring Enterprise Application Software 

...................................................................................... 3–1 

Preparing for Installation .................................................................................3–1 

Installation Checklist .......................................................................................3–2 

General Notes About Installation ....................................................................3–3 

Existing LINC/NET Files ..............................................................3–3 

Setting Tasklimit ..........................................................................3–3 

Changing Populations in Host Builder .........................................3–3 

Checking for Duplicate LINCSUPPORT Libraries ........................3–4 

Installing Host Builder ....................................................................................3–5 

Completing Configure Screens ......................................................................3–6 

78616208–001 iii

Contents 

Getting Online Help in Configure ................................................ 3–6 

Summary of Configure Utility Screens ....................................... 3–7 

Configure Options Screen 1 ....................................................... 3–8 

Configure Options Screen 2 ..................................................... 3–10 

Target Host Generation Control Screen .................................... 3–12 

Change Control Options Screen ............................................... 3–14 

System Pack Details Screen ..................................................... 3–17 

A Series Environmental Options Screen ................................... 3–21 

A Series Environmental DMS Options Screen ......................... 3–23 

Copy Audit to Tape Details Screen ........................................... 3–27 

Select Configure Pack/Population Option Screen ..................... 3–29 

Pack Name Changes Screen .................................................... 3–31 

Event and Components Selection Screen ................................ 3–32 

Populations and Packs Screen .................................................. 3–33 

Installing Free-Standing Runtime Software ................................................. 3–34 

Configuring COMS for Systems .................................................................. 3–36 

Inhibiting or Interrupting Automatic Loading ............................ 3–36 

COMS Configuration for the SWITCH.TO; Command .............. 3–37 

COMS Configuration for the WDP Interface Program .............. 3–37 

Installing and Configuring Remote Subroutine Server ................................. 3–38 

Installation ................................................................................. 3–38 

Configuration ............................................................................ 3–38 

Operations ................................................................................ 3–40 

Monitoring ................................................................................ 3–40 

Installing the MCP Builder Server ................................................................ 3–40 

Software Requirements ............................................................ 3–40 

Installation ................................................................................. 3–41 

Section 4. Signing On to Enterprise Application Environment........... 4–1 

Section 5. Migrating to Release 3.1.................................................... 5–1 

Migration Procedure ...................................................................................... 5–1 

Using LCOPY ............................................................................. 5–2 

Updating local patches to CCsversion for MCP based hosts ..... 5–2 

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

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

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

Population Setting ....................................................................... 5–4 

CCsversion Settings ................................................................... 5–5 

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

New Database Blocksize Feature ............................................... 5–5 

Network Maintenance (NETMAINT) ........................................... 5–5 

Workstation Driver Program (WDP) Database ............................ 5–6 

Saved Transfer Parameter Processing (STPP) ............................ 5–7 

Localization ................................................................................. 5–7 

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

Graphical Interface Workbench Release 3R2 ............................. 5–9 

Generating Your Systems after Migration ................................................... 5–10 

Appendix A. Using the USS5100 Unisys Remote Data Facility ...........A–1 

iv 78616208–001

Contents 

Planned Recovery .......................................................................................... A–1 

Online Application Takeover .......................................................................... A–2 

Planned Takeover ....................................................................... A–2 

Unplanned Takeover ................................................................... A–3 

Unplanned Takeover during Reorganization or System Generation 

.................................................................................................. A–4 

Report Recovery during Unplanned Takeover ............................................... A–4 

Reports Creating Extract Files .................................................... A–4 

Reports Using ROC Flat Files ..................................................... A–4 

Reports writing directly to a printer backup ............................... A–4 

Appendix B. Related Product Information ............................................. B–1 

Glossary 

Index 

78616208–001 v

Contents 

vi 78616208–001

Section 1 

Introduction 

About This Document 

Purpose 

Audience 

Notations 

This document provides information and instructions for the installation and configuration 

of MCP based Enterprise Application Software releases. 

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

installation of MCP based software. A secondary audience consists of Enterprise 

Application Environment users who need to understand the requirements and procedures 

necessary to migrate systems from previous releases to the current release. 

Where specific operating command strings are given, italics are used to delimit 

metatokens or variables. Enter an actual value in place of these variables as instructed. 

Square brackets delimit optional values. 

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. 

78616208–001 1–1

Introduction 

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 78616208–001

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 

78616208–001 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 78616208–001

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 & 


78616208–001 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 78616208–001

Section 2 

Pre-Installation 

This section covers the following topics: 

• Products and Terminology 

• Release 3.1 Media Summary 

• Hardware Requirements 

• Software Requirements 

• Setting Up Your Host 

• Configuring Terminal Devices for Enterprise Application Environment 

Products and Terminology 

Host Builder 

This subsection gives a summary of the main Enterprise Application Software products. 

This subsection lists important terminology. Read this subsection carefully to help you 

understand how the instructions in this document relate to your particular type of 

software. 

Host Builder enables you to design, develop, modify, and generate systems. It consists of 

a definition language and an interactive compiler that checks the validity of your coding as 

you input it, and then creates the programs for the system. Runtime is supplied with Host 

Builder. 

You are guided through the different modes of data entry in Host Builder as you define 

your system and Reports. 

• For each type of activity, declare the options for your system and Reports. The mode 

of entry is by menu selection screens. 

• Design screens and Report Frame layouts by using Painter. 

• Enter logic commands, Global Setup Data items, Keywords, Dictionary text, Teach 

screens, and Profile definitions by using Editor. 

See your Unisys e-@ction Enterprise Application Host Builder Guide and Unisys e-@ction 

Enterprise Application Host Builder Reference Manual: Painter and Editor for further 

details. 

78616208–001 2–1



Runtime is the term used for the programs and utilities needed to run generated 

systems. 

Generated systems, Reports, and Networks cannot run on your host equipment until 

Runtime is installed. 

Note: Runtime is supplied with Host Builder. 

System Transfer 

The System Transfer utility enables generated systems to be transferred to and from 

other MCP environments. It consists of the following parts: 

• The Transfer functions within Host Builder. These functions are used to produce a 

magnetic tape (similar to a release tape) or a series of pack files (for BNA/Disk 

transfer), containing the files for a generated system to be configured on a different 

host. 

• The Configure utility is used to install and configure a system from a magnetic tape or 

a directory of pack files produced on a different host. 

When transferring a system generated under release 3.1 to another MCP based host, you 

must also use Runtime or Host Builder from release 3.1 on the target host. 

See your Unisys e-@ction Enterprise Application Runtime for ClearPath MCP 

Administration Guide for more details regarding transferring systems. 

2–2 78616208–001

Release 3.1 Media Summary 


Release 3.1 software products are provided on Release Media as shown in the following 

table (unless stated otherwise in your product release information). Use this as a checklist 

to ensure that you have the correct release tapes and diskettes. 

Medium Medium ID Description 

Tape/CD LN2171 Full Enterprise Application Environment, including full Host Builder 

and Runtime 

Tape/CD L2R171 Runtime 

78616208–001 2–3


Hardware Requirements 

The following hardware is necessary to use MCP based software: 

• MCP based mainframe, with a minimum of 18 Megabytes of memory. Release 3.1 is 

compatible with all MCP based platforms that are currently supported by Unisys. 

Machines that use emode beta microcode (A7, NX4200 and A2100 systems) cannot 

use DMSII Extended Edition features with release 3.1. 

• Terminals (which must be capable of displaying a 72-character status line): 

– Unisys T 27, ET 1100, level 5.0, or equivalent. 

– Unisys TD 830, or equivalent, with level 2.2 firmware or higher, and 4 KB of 

memory. 

– IBM 3270 with the appropriate configuration. 

For more details, see “Configuring Terminal Devices for Enterprise Application 

Environment” on page 2–9. 

• Line printer (optional). 

• Tape Drive (for installation). 

• CD drive (for installation). 

• Memory. The database for Host Builder is configured with an Allowed core of 

200,000 words. 

2–4 78616208–001


• Disk space. Sufficient to support the minimum disk requirements shown in the 

following table (based on release 3.1 configured with default settings and using a 

secondary audit file). 

Files Sectors Description 

LINC17/= 147000 Skeleton files and general utilities common to all 

systems 

LINC17DB/= 201000 Database for Host Builder, and control file 

LINC17SYS/= 331000 All files specific to running Host Builder 

Other Files 36000 Other database files and COMS Configuration File 

Total 715000 

In addition, the following table shows the requirements needed on DISK. These files 

are shared by all end-users on the host. 

Files Sectors Description 

LINC17/= 13000 Shared files and programs 

LINC17TP/= Site 

specific 

Terminal Printer Spooler (TPS) files 

Others 250 EXAMINER and LINCXSUPPORT files 

As disk and memory requirements vary, contact your Unisys representative for 

planning assistance. 

78616208–001 2–5


Software Requirements 

This subsection lists the required and the optional software for Enterprise Application 

Environment operations. Install the software according to the instructions included in the 

documentation for each item. 

General Software Requirements 

System Software Release level 46.1 supports all release 3.1 software, including: 

• COBOL85. (Note that COBOL74 cannot be used.) 

• DMS II 46.1 and DMSII XE 

If you will be using Extended Edition features, you must have a license for Extended 

Edition. 

• DMS/INQUIRY (optional) 

• ERGO (optional) 

• SYSTEM/CANDE 

• SYSTEM/BINDER IC 6 and above 

• COMS 

• DMALGOL 

• Multi Lingual System (MLS) 

• NEWP compiler 

• If you will be interfacing to the ADDS Dictionary, ADDS software must be installed. 

Network Software Requirements 

Caution 

Using system software facilities to manipulate message content outside of 

functionality (for example, COMS PIs) is done at your own risk. 

To support cross-host transactions, networking capability is required. 

If you do not require interhost communications, then local port capability is provided by 

LPPSUPPORT. 

If you require interhost communications, BNA V2, TCP, or OSI are required. 

If you require interhost system services (for example, file transfers), you must also install 

Distributed System Services (DSS). You need to install this if you are going to use Builder 

or the Remote Subroutine Server. 

2–6 78616208–001


If you require Developer Test to call subroutines on the host you must install the Remote 

Subroutine Server (also known as LRSS) in addition to DSS. See “Installing and 

Configuring Remote Subroutine Server” on page 3–38. 

If you intend to use DEPCON for Report printing, then you will need to install and 

configure the DEPCON software for A Series hosts. This will enable systems on the A 

Series to direct print output to the DEPCON PC Server when the default output device is 

set to DP. For details about installing and configuring DEPCON on A Series see the 

Clearpath HMP Series, A Series, and 2200 Series DEPCON Software Configuration and 

Operations Guide. 

Other Software Release Compatibility 

Graphical Interface Workbench 

Release 3.1 is compatible with Graphical Interface Workbench release 3R1. 

Developer 

Release 3.1 supports CASE Interchange File (LCIF) interchange with LDA release 2.2, 2.3, 

and 3.1. 

Runtime Test Environment 

Runtime Test Environment release 4.1 will be compatible with release 3.1. 

DEPCON Software 

DEPCON Software release 5R2 is compatible with release 3.1. 

78616208–001 2–7


Setting Up Your Host 

Before you install and configure your software, you should perform the following tasks: 

• Set the Host Name for your system. 

• Make sure SYSTEM/BINDER, SYSTEM/DASDL, and SYSTEM/COBOL85 are 

accessible for your usercode. 

• If configuring with a Dictionary or Work pack that is the alternate family for the 

usercode under which you run the configure. Then, before the configure job is run, 

change the usercode family to: 

 

This will ensure the appropriate files are copied to the correct pack. 

• Ensure that an SL command has been performed on the library KEYEDIOIISUPPORT 

on your system. Setting the KEYEDIOII is recommended but not required. 

Note: As of release 3.1, valid MCP based pack names of up to 17 characters are 

supported in Enterprise Application Environment. Developer, 2200 based systems, and 

UNIX based systems, however, still limit pack names to ten characters only. Be aware that 

pack names longer than ten characters will be truncated when transferring files to 

Developer or when transferring systems from an MCP based platform to a different host 

platform. 

2–8 78616208–001

Configuring Terminal Devices for Enterprise 

Application Environment 

COMS Station Definitions 


COMS station definitions, as used by Enterprise Application Environment, make use of 

fields within COMS Installation Data entities. The use of these fields is shown in the 

following table. 

Notes: 

Field Usage Description 

Integer1 Station type 0 = ET/TD/T27 

1 = ET/TD/T27 

3 = IBM 3270 

4 = NOFORM interface 

8 = Graphical Interface Workbench 

terminals 

Integer2 Access level 0 = Standard 

1 = ODT 

2 = Controller 

Integer3 Privilege level 1 to 15 

String1 Associated printer Up to 17 characters 

String2 Default language Language name, up to 15 characters 

• If Integer1 is equal to 0 for a station, when Enterprise Application Environment 

receives a BYE from that station, a ?CLOSE request is sent from the station. 

• When Integer1 is equal to 1, Enterprise Application Environment will perform a 

programmatic CLOSE of the window. 

• Instead of setting Integer1 to 8 for Graphical Interface Workbench stations, you can 

run the DWLAUNCH program when Graphical Interface Workbench-capable systems 

start up. 

If you have external systems that use Installation Data entities, and these conflict with the 

way in which Enterprise Application Environment uses these entities, you should define 

your non-external entities as secondary Installation Data, and then associate this 

secondary Installation Data with the primary. 

On conversion to release 3.1, the LINC/NET file will be loaded into the COMS Utility file. 

The LINC17/MON program now has an interface to COMS/UTILITY which will allow new 

terminals to be defined. 

78616208–001 2–9


Configuration Settings for Terminals Qualified for Enterprise 

Application Environment 

See your terminal device reference material for full instructions on configuration. The 

required register settings for terminal devices are given in the following subsections (by 

device type). The convention XX XX represents a unique terminal address (in 

hexadecimal). 

General requirements 

When defining terminal devices: 

• Do not use braces as alternate forms characters. 

• Enterprise Application Environment requires terminals that are capable of displaying a 

72-character status line. 

• Where applicable, configure your terminal so that carriage returns are not visible. 

2–10 78616208–001

TD 830 and TD 830J (9600 BPS TDI) 

MT 983/5 (9600 BPS TDI), level 3 firmware 

SR-100 and SR-110 

Location Hex Settings 

0080 OA FB 01 00 17 4F 1F 1E 10 XX XX 04 09 00 04 04 

0090 00 2F 4F 17 4F FF 00 4F 17 40 00 08 03 50 0F FF 

00A0 04 


0080 OA A1 01 03 17 4F 1F 1E 10 XX XX 47 08 01 47 41 

0090 00 2F 4F 17 0F 00 00 4F 17 00 00 08 00 00 07 80 

00A0 04 

Datacomm Setting 

Databits 7 

Parity E 

Syn N 

60 Hz Y 

2 Stop Bits N 

ACK Level 0051 

XMIT #s N 

Edit Setting 

Stay in receive Y 

Forms XMIT to cursor Y 

SOH Exits Forms Y 

SOH Clears Page N 

Auto Page Adv Enable N 

DC1=Stay In RCV Y 

DC2=Toggle Forms Y 

Dcom LF->CR N 

Dcom CR->LF Y 


78616208–001 2–11


B20 MT 983 Emulator 

ETX Plant From Dcom N 

CR Plant From Kbd N 


0080 OA A1 01 03 17 4F 1F 1E 10 XX XX 47 08 01 47 41 

0090 00 2F 4F 17 0F 00 41 4F 17 00 00 08 00 00 07 80 

00A0 00 

ET 1100 and T 27 Terminal Configuration Menu 

To print on AP 1312 or AP 1314 terminal printers from an ET 1100, the PRINT GROUP 

options must be set to the default values, with the following exceptions: 

In addition, the following values must be set. 

Option Value 

LINE/PAGE 24 

CHAR/PAGE 80 

LINE/SCREEN 24 

Option Value 

BITS/CHAR 7 

AUX INPUT D 

BUSY (I/O) 1 

SPECIFY KEY A 

Option Value Required 

SCREEN 17280 (max) 

ALT FORM DELIMITERS OPEN (US) 1F 

CLOSE (RS) 1E 

Edit Setting 

PRINT AUX 2-character address of background printer 

PRINTER DCOM 2048 (min) 

PRINT BPS Must be set as relevant for particular printer 

2–12 78616208–001

TC 4000J 

On switch SW734, bits 4 through 8 (inclusive) must be closed. 

Attributes for … File Name 

BNA LINC17/1/GLOBALBNA 

NDL LINC17/1/GLOBALNDL 


78616208–001 2–13


Using IBM 3270 Terminals 

IBM 3270 terminals can be attached to a Unisys MCP based processor through an IBM 

cluster controller, and used to run generated systems. However, they cannot be used to 

run utilities, nor to perform system development using Host Builder. 

In terms of their operation with systems, IBM 3270 terminals differ from Unisys terminals 

in the following fundamental ways: 

• They operate in single page mode only. 

• The screen display is permanently in “Forms” mode. 

• Only 24 display lines are available. 

Operational Considerations 

Page 2 

Although IBM 3270 terminals operate in single page mode, the standard Page 2 screen 

(format request) can be displayed by pressing PA2, PF2, or PF14. Your original screen 

format may be recalled by pressing PA1, PF1, or PF13. 

Screen Size 

If a screen greater than 2150 characters is sent to an IBM 3270 terminal, the screen 

displayed at the terminal will be truncated to 2150 characters, and a message will be 

displayed at the console indicating that truncation has occurred. 

Video Reports 

Video reports are displayed in single, 22-line pages. In addition to the commands used 

while viewing video reports, the following pre-programmed functions are available. 

Error Messages 

Only single-line error messages and the first line of multiple line error messages are 

displayed. These messages appear on the status line (line 24). 

HOME Position and Clear Screen 

Function Key Action 

PF8 or PF20 Displays next screen 

PF9 or PF21 Displays previous screen 

PF10 or PF22 Terminates the Report 

As IBM 3270 terminals operate in permanent forms mode, a simulated out-of-forms 

mode and Home position is available. Press the CLEAR key to display a clear input 

screen, on which you can enter system commands in the upper left-hand position. 

2–14 78616208–001

List of Function Keys 

The following table gives a full list of the preprogrammed function keys. 

Use of Line 24 


Line 24 is used as the status line for system messages. All such messages will overwrite 

any displays that use this line in your systems. 

Screen Display Attributes 

The Display and Data item highlight attributes BLINK, REVERSE video and UNDERLINE, 

are not supported on IBM 3270 terminals and so are ignored by your generated systems. 

Unlike Unisys terminals, IBM 3270 terminals do not reset BRIGHT highlighting 

characteristics at the end of a line. Such characteristics continue until a data item 

delimiter or RESET character is reached. 

Data item delimiters, although present, are not displayed on IBM 3270 terminals. 

Repeat.From Displays 

Key Function 

CLEAR Clears the screen 

PA1, PF1 or PF13 Recalls the last message 

PA2, PF2 or PF14 Recalls format request screen 

PF3 or PF15 :HELP screen request 

PF4 or PF16 HI 

PF5 or PF17 :STN screen request 

PF6 or PF18 :UPD screen request 

PF7 or PF19 Clears screen and displays a colon (:) 

PF8 or PF20 Video Report NEXT screen 

PF9 or PF21 Video Report Previous (LAST) screen 

PF10 or PF22 Video Report termination 

PF12 or PF24 PF key HELP screen 

PF11 or PF23 Not used 

Only the current Repeat.From line is displayed. Each new line overwrites the previous 

line. 

ERASE INPUT and ERASE EOF 

78616208–001 2–15


Use of the ERASE INPUT and ERASE EOF keys will cause the deletion of prefilled blanks 

in the data item field where the cursor is positioned. This will cause data item length 

errors when transmitted. 

Configuration Information 

IBM 3270 terminals and controllers must support and be configured for 1920-character 

displays. Line configuration should be set for BISYNC line protocol. 

IBM 3270 terminals must be defined in the Network as type IBM3270 devices as the 

terminal type cannot be determined dynamically. 

SOURCE NDL II IBM 3270 BISYNC algorithm and editor are required. The COMS UTILITY 

Station definition for 3270 devices must have a TRANCODE position value of 7. 

Library Operation Description 

The library system /1/3270 is automatically generated for each system, and is called when 

needed for both input and output messages for an IBM 3270-type terminal. 

On input, all cursor and field address information is stripped off and the length adjusted. If 

a PF or PA key is used, a keyed response is generated. On output, a Unisys terminal 

output response is converted to the equivalent response for an IBM 3270-type terminal. 

2–16 78616208–001

Section 3 

Installing and Configuring Enterprise 

Application Software 

This subsection covers the following topics: 

• Preparing for Installation 

• Installation Checklist 

• General Notes About Installation 

• Installing Host Builder 

• Completing Configure Screens 

• Installing Free-Standing Runtime Software 

• Configuring COMS for Systems 

• Installing and Configuring Remote Subroutine Server 

• Installing the MCP Builder Server 

Preparing for Installation 

Before commencing installation, read “Pre-Installation” on page 2–1 and “Installation 

Checklist” on page 3–2. 

In addition, it is important that you read your Software Release Announcement (SRA) 

before commencing installation. You must note carefully any listed conditions or 

restrictions that may apply to you. 

78616208–001 3–1

Installing and Configuring Enterprise Application Software 

Installation Checklist 

Use this checklist when considering the issues and the steps you must take before and 

after you install your software. (Unless specifically stated otherwise, references in the 

table are to topics later in this section.) 

If you are already a user, you only need to confirm that your current pre-installation setup 

is correct before migrating to this release. 

Step Action References 

1 Review the Enterprise Application 

Environment terminology and product range. 

2 Verify that you have the correct release 

media. 

“Products and Terminology” on 

page 2–1 

“Release 3.1 Media Summary” on 

page 2–3 

3 Verify that you have the necessary hardware. “Hardware Requirements” on 

page 2–4 

4 Verify that you have the necessary software. “Software Requirements” on 

page 2–6 

5 Check your host setup. “Setting Up Your Host” on page 2–8 

6 Ensure that your terminal device 

configurations are appropriate for Enterprise 

Application Environment. 

7 If you are already a user, consider any 

relevant conversion issues and whether you 

can install with the Retain existing 

database field set to Y. 

“Configuring Terminal Devices for 

Enterprise Application Environment” 

on page 2–9 

“Migrating to Release 3.1” on 

page 5–1 

8 Installing the software. “Installing Host Builder” on page 3–5 

and “Completing Configure Screens” 

on page 3–6 

9 Verify that you have the appropriate COMS 

configuration for your site requirements. 

“Configuring COMS for Systems” on 

page 3–36 

3–2 78616208–001


General Notes About Installation 

Before initiating the installation process, you should be aware of the points outlined in the 

following subsections. 

Existing LINC/NET Files 

During installation, any existing LINC/NET file will be converted to use the COMS/UTILITY 

implementation. Once converted, the LINC/NET file is not required by release 3.1. 

Setting Tasklimit 

When configuring software, the Configuration WFL job may terminate because the 

number of spooled tasks exceeds the Tasklimit for the queue. You can avoid this 

happening by submitting the Configuration WFL to a queue that does not have the 

Tasklimit attribute set. The maximum value of the Tasklimit is 31. 

Changing Populations in Host Builder 

If the defined populations for the structures within Host Builder are of insufficient size for 

the Specifications you want to load, you can increase the sizes by one of the following 

means (which may cause a reorganization of the structures that are increased): 

• Increase the population size on the A Series Population & Family Changes screen of 

the Configure Utility. 

• Run the Database Management Utility (DMU) against the relevant structures after the 

installation process has completed. For more details, see your Unisys e-@ction 

Enterprise Application Runtime for ClearPath MCP Administration Guide. 

The following files are copied to DISK (or the alternate family pack), provided that the 

version being installed is higher than the version currently in place. (If it is not, the files are 

not copied from the Dictionary pack specified during installation, and a message is 

displayed.) 

 

 

 

 

 

 

 

 

 

 

 

 

 

78616208–001 3–3


Checking for Duplicate LINCSUPPORT Libraries 

If you install a new version of the LINCSUPPORT library without first shutting down your 

system, you may encounter problems with your system. Generate and Configure WFLs 

will force a system to be shut down if a new LINCSUPPORT library is being installed. 

Since you can also manually install this library, a checking mechanism in the 

LINCSUPPORT library warns you if there is more than one copy of this library running. 

There are two methods used to check this: 

• If LINCSUPPORT cannot exclusively open the file system/UNIQUE/SAVE, the library 

will hang waiting for this file. The message CHECK FOR DUPLICATE LINCSUPPORT 

is displayed. 

• If a COMSTP program starts up and is using a copy of LINCSUPPORT that is not 

linked to System Supervisor (LSS), then a separate task will be initiated. This will 

show in the waiting entries. The message CHECK FOR DUPLICATE LINCSUPPORT is 

displayed. 

If you have more than one LINCSUPPORT running, your system must be taken down. It 

should not be restarted until you have checked that there are no duplicate copies of 

LINCSUPPORT still running. 

3–4 78616208–001

Installing Host Builder 

To install Host Builder: 


1. Mount the release media labeled LN2171. 

2. If your machine has Security Administrator status enforced (by enabling the 

SECADMIN option), and you have access to a usercode with SECADMIN status, log 

on to CANDE under that usercode or under a privileged usercode. 

3. Run SYSTEM/COPY to load down the Configure Utility: 

 

where media is either TAPE or CD. 

4. Run the Configure Utility by entering: 

 

5. Complete the various Configure Utility screens. See “Completing Configure Screens” 

on page 3–6. 

6. Set up the required Support Libraries (SLs). If your host has Security Administrator 

(SECADMIN) status enforced, sign on to MARC with a SECADMIN status usercode. 

(Only a user/task/job with SECADMIN status may issue SL commands when 

SECADMIN status is enforced.) 

From MARC, enter: 

 

 

The altpack value gives the alternate pack for the family of the usercode under which 

you are running Host Builder. For example, your usercode family may be specified as 

follows: 

 

In this case, enter SYSPACK as your altpack value. 

7. If your host has Security Administrator status enforced, you may also wish to enter 

certain Mark Program (MP) commands to confer Security Administrator status upon 

various programs required for Host Builder (for example, LINC17SYS/UPD, system/ 

COMS_LINC_TP, LINC17/CEL, LINC17/CFG, and so on). Otherwise, running these 

programs may result in security violation entries that appear in the SUMLOG. 

Note: To obtain a complete list to check for privileged programs, use the LFILES 

command from CANDE. 

Sign on to MARC using a SECADMIN usercode. For each program file that has 

caused a security violation entry in SUMLOG, enter: 

 

8. You can optionally override the COMS configurations that were automatically set up 

by the configuration process. For more details, see “Configuring COMS for Systems” 


78616208–001 3–5


Completing Configure Screens 

This subsection describes the Configure Utility screens that you use to configure Host 

Builder as part of the installation process. The screens you use to configure other 

software (except Runtime) are based on the same screens. Not all fields apply to each 

type of software being installed. 

Getting Online Help in Configure 

During your Configuration run, you can receive online help by entering a command from 

the following table in an Action field on any of the screens in the Configure Utility. 

Command Description 

HELP Introduction and explanation of how you can get further information 

specific to any field 

HELP field Displays help for field. Valid values of field are displayed on the 

introductory help screen 

Help information is always displayed on the Page 2 screen of your terminal. 

3–6 78616208–001


Summary of Configure Utility Screens 

The following table lists the screens in the Configure Utility in the order in which they will 

be displayed, and describes how to access them. Further details of each screen are given 

in the following subsections. 

Screen Optional? How to Access the Screen 

Configure Options 1 No 

Configure Options 2 No 

Target Host Generation Control Yes Enter Y in the target hosts field on 

the Configure Options Screen 2 

Change Control Options Yes Enter Y in the version control field 

on the Configure Options Screen 2 

System Pack Details No 

Report Extract Pack Details Yes Reports/transferred file contains valid 

entries 

A Series Environmental Options No 

A Series Environmental DMS Options No 

Access External Databases Yes Not valid for an interactive 

configuration 

Copy Audit to Tape Details Yes Enter U in the Copy audit to tape 

field on the A Series Environmental 

Options screen 

Select Configure Pack/Population 

Options 

No 

Pack Name Changes Yes Enter Y in the Pack changes by 

family field on the Select Configure 

Pack/Population Options screen 

Event and Component Yes Enter Y in the Pack and Population 

Changes field on the Select 

Configure Pack/Population Options 

screen 

Pack and Population Yes Always displayed after the Event and 

Component screen 

Online Help (first) Yes Enter HELP in the Action field 

Online Help (specific) Yes Use HELP item command in the 

Action field 

78616208–001 3–7


Configure Options Screen 1 

The Configure Options Screen 1 enables you to enter the major details of your 

configuration. The screen which follows this screen is Configure Options Screen 2. 

Retain existing database 

Use this field to retain or remove you existing database. Enter Y or N. The results of these 

choices are explained under the following headings. 

Enter HELP or HELP RETAIN for online help. 

Entering Y 

Before entering Y, consider the following points: 

• You would normally enter Y if you are upgrading for a patch release. This will retain 

any existing (or Network) Specifications. Your migration information will specify 

whether an entry of Y is valid for the specific upgrade you are performing. 

• If you enter Y when it is not valid, the Configure Utility will return an error. 

• If you enter Y when it is valid, a partial load is invoked that will not destroy any of your 

existing Specifications. Only skeleton and error files are changed, but not your 

underlying database, so that all your existing Specifications are retained. 

Entering N 

• You would normally enter N if you did not have an existing release. You may also 

enter N when installing a major release upgrade over an existing earlier release. 

• If you enter N, and you are installing over an existing Host Builder, any existing 

Specifications are automatically removed during installation, as the process creates a 

new database for Host Builder. If you want to save any existing Specifications, use 

LCOPY to back up your existing Specifications before starting the Configure Utility. 

• If a DMS II database control file already exists and you have not selected the Retain 

Existing Database field, a message occurs requiring your response: 

 

To overwrite the old database, enter: 

 

System name 

This field displays the system name for the software being configured, and cannot be 

changed. 

Enter HELP SYSTEM for online help. 

Database name 

This field contains the name of the database for the software you are configuring. The 

value will be LINC17DB for Host Builder. 

3–8 78616208–001


Enter HELP DATABASE for online help. 

System Usercode / Password 

Use these fields to enter the usercode and password that the programs and source files 

will reside under for the software you are currently configuring. 

You do not need to enter an asterisk (*) for the usercode. Host Builder can generate 

systems under other usercodes. 

Enter HELP SYSTEM or HELP USERCODE for online help. 

Accesscode / Password 

Use these fields to enter the accesscode and password for your system usercode (if it 

has an associated accesscode). 

Enter HELP USERCODE for online help. 

Chargecode / Password 

Use these fields to enter the chargecode and password for your system usercode (if it 

has an associated chargecode). 

Enter HELP USERCODE for online help. 

Coms Window 

Use this field to enter the COMS window name that users will use to sign on to Host 

Builder. This is the same name as the COMS database name. 

The default is LINC17 for Host Builder. 

Enter HELP COMS for online help. 

Language 

Use this field to enter the language that is to be used with the software you are currently 

configuring. The default is ENGLISH. 

The language you enter becomes the default language for the LINC17/MLSLIBRARY. You 

can change this later by altering the LANGUAGE task attribute of the MLSLIBRARY. 

Enter HELP LANGUAGE for online help. 

Configure job 

This field displays the name of the Configure WFL job that is included on your release 

media. 

The LINC17/WFL/CONFIGURE file is automatically copied from your release media by the 

Configure Utility, and the WFL job is started by the Configure program when all the user 

details are entered. This WFL job performs all the tasks for your software configuration. 

78616208–001 3–9


Enter HELP CONFIGURE for online help. 

Media type 

The media type can be TAPE or CD. 


Media Name 

This field displays the name of your release media. This value is preset to the name of the 

release media corresponding to the Configure Utility you have initiated. 


Configure Options Screen 2 

The next screen to be displayed depends on your entries in the Target Host and 

Version Control fields, as shown in the following table. 

Dictionary family 

Use this field to specify the dictionary pack for your system family. 

Enter HELP DICTIONARY for online help. 

Work family 

Use this field to specify the pack family for any work files used during your Configuration 

process. These files are removed during or at the end of the run. 

Enter HELP WORK for online help. 

Target Hosts 

Target Hosts Version Control Next Screen Displayed 

Y Y or N Target Host Generation Control 

N Y Change Control Options 

N N System Pack Details 

Use this field to specify the host types that may be used to run the systems created in 

Host Builder, and the host Reserved Word lists and Templates you wish to apply to Host 

Builder. This field applies only if you are configuring the full Host Builder. 

If you enter Y, a screen is displayed that lists host types. For more details, see “Target 

Host Generation Control Screen” on page 3–12. 

Enter HELP TARGET or HELP HOSTS for online help. 

3–10 78616208–001

Version control 


Use this field to specify the change control options you require. This field applies only if 

you are configuring the full Host Builder. 

Enter Y to display a screen that lists your change control options. See “Change Control 

Options Screen” on page 3–14. 

For more details about change control, see your Unisys e-@ction Enterprise Application 

Host Builder Guide. 

Enter HELP CHANGE for online help. 

78616208–001 3–11


Target Host Generation Control Screen 

Use this screen to select the host types you want to include for reserved word checking 

and code preparation, if you intend to target other hosts, or transfer Specifications to 

Developer. It is displayed if you entered Y in the Target hosts field on the Configure 

Options Screen 2. 

For the purpose of code generation, UNIX and Windows operating systems reserved 

words and templates are identical. Therefore, if you are generating a Specification in MCP 

based Host Builder, and the target host is Windows, you must select the UNIX options on 

this screen. 

If you do not want to target other host types, you can save generation time by not 

selecting these options. 

Note: You can also set and change target host types and reserved word lists by using 

Supervisor mode in Host Builder. 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 to change your host settings. For further 

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

The fields on this screen are described in the following subsections. 

Next Screen 

The next screen displayed depends on options you selected on the Configure Options 

Screen 2. 

• If you entered Y in the Version control field on the Configure Options Screen 2, the 

Change Control Options screen will be displayed next. 

• If you entered N in the Version control field on the Configure Options Screen 2, 

the System Pack Details screen will be displayed next. 

Reserved Words 

Use these fields to select the host reserved words that you want to apply to Host Builder. 

Any name used or added to a Specification within Host Builder is checked against your 

selected reserved word lists. 

If templates are chosen for a host, the reserved words for that host must also be 

selected. Enter HELP TARGET for online help. 

Templates 

This field only applies to configuration of a full Host Builder. 

Use these fields to specify which host types may be used to run the systems created in 

Host Builder. This controls which reserved words are loaded into Host Builder, and which 

templates are loaded. Templates will be loaded into memory if you also select the LSO 

Stored in Memory field on the Environmental Options screen. 

3–12 78616208–001


If you select templates for a particular host, the reserved words for that host must also be 

selected. 

Do not select templates that you do not require, as this will cause unnecessary code to 

be produced and stored in the database. 

Base your selection on the hosts that can receive an LCOPY tape from this Host Builder. 

Enter HELP TARGET or HELP HOSTS for online help. 

78616208–001 3–13


Change Control Options Screen 

The Change Control Options screen enables you to select Change Control and Resource 

Locking options for Host Builder. For more details about Change Control and Resource 

Locking, see Sections 2, 3, and 5 of your Unisys e-@ction Enterprise Application Host 

Builder Guide. 

This screen is displayed if you entered Y in the Version Control field on the Configure 

Options Screen 2. 

The fields on the Change Control Options screen are described in the following 

subsections. 

Note: Although your system administrator can later change these settings in Host 

Builder, it is recommended that you make accurate selections at this stage, as they affect 

your overall Host Builder security, user access control, and ability to track changes. 

Next Screen 

The System Pack Details screen will be displayed following this screen. 

Change Identification 

If you want Change Identification to be enabled for Host Builder, enter Y in this field. This 

will identify all changes by your selected Identification Mode. 


Resource Locking 

Use this field to enable Resource Locking for Host Builder. Enter Y in this field to 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. 


Identification Mode 

Use this field to enter the Identification mode that you wish to use for Host Builder. This 

setting is only relevant if you have entered Y in either (or both) of the Change 

Identification or Resource Locking fields. 

The values that you can enter in this field give the method that will identify users of Host 

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

following table. 

Value Method of Identification 

L Security Module Usercode/Password 

S Station identifier (default) 

3–14 78616208–001


The administrator of your Host Builder should have already set up your user identifiers. 


Patch Identification 

Use this field to enable Patch Identification for 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 

Use this field to specific the level of auditing to be performed for Host Builder. The levels 

of auditing available are shown in the following table. 


Specification Admin 

Use this field to enable auditing of Host Builder administration tasks. This will create an 

audit trail for such activities as generates, Supervisor command usage, and LCOPY runs. 


On id change 

Value Method of Identification 

Use this field to automatically reset all system and Report generate counts whenever the 

runtime version identifier for the system is changed. For details regarding the use of the 

(optional) runtime version identifier, see the Change Control Options screen in your 

Unisys e-@ction Enterprise Application Host Builder Guide. 


U User defined identifier (an identifier of LINC is 

established automatically for initial access) 

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 

78616208–001 3–15


Reports on sys gen 

Use this field to automatically reset all Report generate counts whenever your system is 

generated. 


Propagate all settings 

Use this field if you have chosen to retain the existing database (you entered Y in the 

Retain Existing Database field), to use the current Change Control options to set up 

every Specification in Host Builder. Otherwise, the current settings will be used to set up 

only the GLOBAL Specification. 


3–16 78616208–001

System Pack Details Screen 


The System Pack Details screen enables you to enter pack names for Host Builder. 

Fields contain default values of the appropriate pack names from the Configure Options 

Screen 1. The fields on the System Pack Details screen are described in the following 

subsections. 

Note: The Rocdb pack, Rocfile pack and Adhoc pack fields are ignored, as the 

Report Output Control System (ROC) and Ad Hoc Inquiry are not available for Host Builder. 

Next Screen 

The A Series Environmental Options screen is displayed after you transmit this screen. 

Default Pack 

Use this field to specify the default pack for other pack fields. Defaults apply only when a 

pack field is blank. Some packs default to other pack names, as shown in the following 

table. 

Enter HELP DEFAULT for online help. 

Event Pack 

Use this field to enter the pack family on which all Event structures will be located unless 

structures are specifically directed to other pack families (by selecting the Pack and 

Population Changes field on the Select Configure Pack/Population Option screen). If 

you do not enter a value in this field, the Database pack (if entered) is used, otherwise the 

Default pack is used. 

Enter HELP EVENT for online help. 

Pack Defaults to … 

Adhoc Pack Database Pack 

Audit Pack Dictionary Pack 

Database Pack Dictionary Pack 

Dictionary Pack Default Pack 

Extract Pack Dictionary Pack 

Log Pack Audit Pack 

Object Pack Dictionary Pack 

Rocdb Pack Database Pack 

Rocfile Pack Database Pack 

Station Pack Database Pack 

78616208–001 3–17


Dictionary Pack 

Use this field to specify the Dictionary pack for the software you are currently configuring. 

Files that will be located on your specified Dictionary Pack are described in the following 

table. 

Dictionary Pack Files 

In each case, the Database Control file is renamed during the configuration process. 

If you do not enter a value in the Dictionary Pack field, the Default pack is used. 

Enter HELP DICTIONARY for online help. 

Object Pack 

Use this field to enter the pack for the system code files and DMS code files for the 

software you are currently configuring. This pack will also be used as a work pack and for 

storage of Report source code files. 

Enter HELP OBJECT for online help. 

Log Pack 

Use this field to enter the pack on which log files are to reside. If you do not enter a value, 

the Audit pack is used. 

Note: If a Log backup program/job is present, it must be on the Object Pack. 

Enter HELP LOG for online help. 

Station Pack 

File name/Directory Description 

LINC17SYS/CODES Output Control Codes 

DESCRIPTION/LINC17DB Database DESCRIPTION file 

LINC17SYS/SOURCE/DMS DMS source file 

LINC17DB/CONTROL Database CONTROL file 

LINC17SYS/LINCCNTL Control file 

LINC17SYS/LINCFORM Forms file 

LINC17SYS/LINCGLI GLI format file 

LINC17/= Other files 

Use this field to enter the pack family that will be used to store the structures holding 

information on the terminals accessing the software you are currently configuring. These 

are high-activity structures, and having them on a separate pack family could improve 

your throughput. If you do not enter a value in this field, the Database pack is used. 

3–18 78616208–001


Enter HELP STATION for online help. 

Audit Pack 

Use this field to specify the pack on which your DMS audit files are to reside. If you do 

not specify an Audit pack, the Dictionary pack is used. 

The entry in this field is ignored for audit purposes if you enter U in the Copy audit to 

tape field on the A Series Environmental Options screen. However, the pack you enter in 

the Audit pack field is always used to hold the secondary copy of the GLB.UNIQUE file. 

Enter HELP AUDIT for online help. 

2nd Audit Pack 

Use this field to specify the Secondary Audit Pack for Host Builder. If no pack is entered, 

secondary audit files are not created. 

The entry in this field is ignored for audit purposes if you enter U in the Copy audit to 

tape field on the A Series Environmental Options screen. 

Enter HELP AUDIT for online help. 

Reorg Pack 

Use this field to enter the name of that pack family if you have selected the Retain 

Existing Database field, and you want to use a separate pack for the interim structures 

created by the database reorganization. 

Enter HELP REORG for online help. 

Database Pack 

Use this field to specify a pack for your Database structures. The Database pack specified 

here will not apply to Database structures for which you have separately defined a pack. If 

you do not specify a pack in this field, the Dictionary pack is used. 

If you intend using the Pack Mirroring feature, it is essential that you use this field to 

define one pack for all your Database structures. 

Rocdb Pack 

This field is not used for Host Builder, and cannot be entered. 

Rocfile Pack 


Adhoc Pack 


78616208–001 3–19


Station Alias file 

Use this field to enter the pack (not family) for the alias file for your reference station 

library. If you have previously installed the alias file, enter the current location if you wish 

to retain the definitions in the current file. If a file is not found on the specified pack, a 

new file is created (any existing reference station name definitions will be lost). 

See Unisys e-@ction Enterprise Application Runtime for ClearPath MCP Administration 

Guide for details of the reference station library. 


Dup Stn Alias 

Use this field to enter a pack on which a copy of the alias file for the reference station 

library is to be maintained. The pack must be different from the pack in the Station 

Alias file field. Make no entry if no copy of the file is to be maintained. 

See Unisys e-@ction Enterprise Application Runtime for ClearPath MCP Administration 

Guide for details of the reference station library. 


Extract Pack 

Use this field to enter the pack family on which all Extract files from Host Builder will be 

located unless they are specifically directed to other families. If you do not enter a value in 

this field, it defaults to the Dictionary pack, which in turn defaults to the Default pack. 

Enter HELP EXTRACT for online help. 

3–20 78616208–001


A Series Environmental Options Screen 

The A Series Environmental Options screen enables you to enter your specific 

environmental options for your MCP environment. 

The fields on the A Series Environmental Options screen are described in the following 

subsections. 

Next Screen 

The A Series Environmental DMS Options screen is displayed after you transmit this 

screen. 

Log activities 

Enter Y in this field to specify that details of non-transaction activities are to be written to 

a Log file as the default setting for systems generated out of Host Builder. The default is 

N. 

Enter HELP LOGACT for online help. 

Log transactions 

Enter Y in this field to specify that details of all activities are to be written to a Log file as a 

default for systems generated out of Host Builder. The default is N. 

Enter HELP LOGTRANS for online help. 

Log file size (blocks) 

Use this field to specify the size for Log files, in blocks (and in records, as the records are 

BLOCKED 1). 

The minimum size you can enter is 1000. The maximum size you can enter is 999999. 

The default is 4000. 

Enter HELP LOG for online help. 

Expected TPH (x 1000) 

Use this field to enter the expected number of thousands of transactions per hour that is 

used by COMS to calculate the Input queue memory size. If you do not enter a value, a 

default of 5 (5000 tph) is used. 

Enter HELP TPH for online help. 

Protected input 

When configuring Host Builder, this field is set to N, and cannot be changed. 

78616208–001 3–21


When generating or configuring systems, if you enter Y in this field, COMS will save all 

input before it is processed by the software you are currently configuring. This will ensure 

that any input is not lost due to a HALT/LOAD. The default is N. 

Enter HELP PROINPUT for online help. 

Protected output file name 

Use this field to enter the name of a Protected Output File to be used by COMS to 

manage the recovery of output messages to user terminals from your configured 

software. The default file name is the relevant system name. 

Enter NONE if you do not require protected output. 

Enter HELP POF for online help. 

POF family 

Use this field to enter the pack family for the Protected Output File. The default is the 

Default pack. 

Enter HELP POFFAMILY for online help. 

Duplicate POF family name 

If you enter a valid pack family name in this field, a duplicate copy of the Protected Output 

file will be created for the software you are currently configuring. If you do not enter a 

value in this field, the duplicate Protected Output file is not created. 

This field cannot be changed when configuring Host Builder. 

Enter HELP DUPPOF for online help. 

LSO Stored In Memory 

Enter Y in this field to specify that the LSO Templates are stored in a memory buffer 

rather than in the database (at the expense of memory). This will result in performance 

improvements during generates. The default is Y. 

The LSO Templates are used in the generate process to convert logic commands to 

COBOL. 

Enter HELP LSO for online help. 

Allow Editor reseq 

Enter Y in this field to select automatic resequencing within Editor. 

Automatic resequencing can occur due to Editor MOVE and COPY commands, and the 

insertion of new lines. Enter N to disallow automatic resequencing in the Editor. The 

default entry is Y. 

Note: The Editor RESEQ command itself is not affected by this field. 

3–22 78616208–001


To change this field, you must reconfigure Host Builder with either Y or N as your Retain 

Existing Database field. 

Enter HELP EDITRESQ for online help. 

WFL family 

Use this field to specify the pack family where your system and system software files 

reside. 

This field requires an entry if either of the following situations apply: 

• The system software required during the installation, (for example, the compilers), is 

not resident on either the primary or alternate pack family of the WFL usercode's 

family, but is resident on pack. 

To address this situation, enter the statement: 

 

Or, to ensure all work files are kept on your primary family primary, enter the 

statement: 

 

• You are placing some or all of the installed software onto a pack family called DISK. 

To address this situation, enter the statement: 

 

Or, if the system software is not on the pack family called DISK, then enter: 

 

Enter HELP FAMILY for online help. 

A Series Environmental DMS Options Screen 

Next Screen 

The Select Configure Pack/Population Option screen is displayed after you transmit this 

screen. 

Copy Audit to tape 

Use this field to automatically save Audit files for Host Builder when they are closed. It 

also enables you to specify the type of reel or cartridge tape media that the Audit files will 

be copied to. 

If you enter a non-space value in this field, a WFL job will be initiated to back up and 

remove DMS Audit trails when they are closed and a new Audit file is commenced. This 

WFL may be modified. 

78616208–001 3–23


Valid entries for this field are given in the following table. 

Enter HELP COPYAUDIT for online help. 

D Entry 

If you enter D, you can define your own media by modifying the skeleton in the LINC17/1/ 

LGLBDDLXP file. If there are no media defined in the skeleton, the media defaults to 

TAPE. 

U Entry 

If you enter U in this field, the Copy Audit to Tape Details screen will be displayed for you 

to enter in free format any required audit attributes. Examples of the attributes you can 

set are: 

• Density 

• Length 

• Blocksize 

• Areasize 

• Scratchpool details 

• Name of the copy job 

For further details, see “Copy Audit to Tape Details Screen” on page 3–27. 

DMS User 

Value Media Description 

C TAPE 1250 BPI QIC tape 

D TAPE (see comments following the table) 

G GCRTAPE 6250 BPI (2400 ft) (length generated is 2200 ft) 

H GCRTAPE 6250 BPI (3600 ft) (length generated is 3200 ft) 

K HS8500 (BPI11000) 8mm cartridge tape TAPE 

L TAPE 38000 BPI (1/2 inch cartridge) 

Y TAPE 1600 BPI (2400 ft) (length generated is 2200 ft) 

U User-defined details entered on the Copy Audit to Tape 

Details screen (see comments following the table) 

other PE TAPE (2400 ft) (length generated is 2200 ft) 

N or space Audit files are not to be copied when they are closed 

Use this field to specify the usercode for the DMS II software if you intend to configure 

your system using an alternative version of DMS II. This value is used to locate the 

required files. 

3–24 78616208–001


Enter HELP DMSVER for online help. 

DMS Pack 

Use this field to specify the pack for the DMS II software if you intend to configure your 

system using an alternative version of DMS II. This value is used to locate the required 

files. 

Enter HELP DMSVER for online help. 

No of Reorg Tasks 

Use this field to enter the maximum number of concurrent Host Builder reorganization 

tasks that can be active simultaneously. 

Reorganization will only occur if you increase Host Builder structure populations to a size 

that cannot be handled by a DMS II Update only. 

The default is 1; that is, DMS II will run reorganization tasks serially. 

Enter HELP REORG for online help. 

Sort sets on reorg 

Use this field to select the DMS II option to sort database sets in the event of a 

reorganization. 

Reorganization will occur only if you increase Host Builder structure populations to a size 

that cannot be handled by a DMS II Update only. 

Enter Y for sets to be sorted during reorganization. The default is N. 

For further details on using Sort Sets, see your Unisys e-@ction Enterprise Application 

Runtime for ClearPath MCP Administration Guide. 

Enter HELP SORTSETS for online help. 

Norestart/Offline reorg 

Enter Y in this field if you do not want reorganizations to be audited, but to use the DMS II 

OFFLINE or NORESTART feature (depending on your level of DMS software). 

Enter N to use audited reorganizations. 

For a discussion of the issues involved in this choice, see your Unisys e-@ction Enterprise 

Application Runtime for ClearPath MCP Administration Guide. 

RDB 

If you are using the Remote Database (RDB) facility with this system, you will have to 

reclone if you enter Y in this field. For further details on RDB, see your Unisys e-@ction 


78616208–001 3–25


Reorg allowedcore (Kwords) 

Use this field to change the default setting of ALLOWEDCORE. The value you enter 

becomes the default for all Generate Sets in all Specifications. 

If you enter a value greater than the memory you have available, your value will be 

changed to 80 percent of the available memory (to ensure that the reorganization will not 

fail). 

Population Increase 

Use this field to enable the population of the database to be increased automatically 

when it exceeds the current limit. A setting of 0 means that the population will not be 

automatically increased. Any other value will enable the population to be increased 

automatically by up to that percentage, until it reaches the system limit of 1000 areas. 

The valid range is 0 through 100. 


Population Warning 

Enter a value in this field to cause the system to issue a warning message when the 

population reaches a percentage of the limit. The valid range is 0 through 99. 


Display Warning Y/N 

To suppress the population warning message, enter N in this field. 

The default is Y. 

Access External DB's 

Enter Y to enter Access external database specifications. This field is not valid for host 

Builder release 3.1. 

3–26 78616208–001

Copy Audit to Tape Details Screen 


Use this screen to specify valid attributes for audit files for your systems. Examples of the 

attributes you may wish to set are: 

• Density 

• Length 

• Blocksize 

• Areasize 

• Scratchpool details 

• Name of the copy job 

This screen enables you to make use of the growing combination of new options and 

new drives as they become available. You are also able to make your own optimizations 

with regard to performance, memory requirements, and disk usage. 

Accessing the Screen 

The screen is displayed when you enter U in the Copy audit to tape field on the 

A Series Environmental Options Screen. The previous audit details will be extracted from 

the DMS II source and presented as the default details on the screen. 

Completing the Screen 

Enter the complete characteristics of the primary and duplicated audit files in the screen 

field. Up to 660 characters (10 screen lines each of 66 characters) can be entered. Your 

entry is included in your DASDL, enclosed within the parentheses following the AUDIT 

TRAIL declaration. 

You must include all necessary primary and secondary audit file details, including the audit 

pack location details, as your entries in the Audit and Duplicate audit fields on the 

Pack Allocation screen are ignored for audit purposes if U is entered in the Copy audit 

to tape field on the A Series Environmental Options screen. 

To remove any previously entered information, blank out the audit information displayed 

on the screen. 

Note: The details you enter on the Copy Audit to Tape Details screen are only included 

in your DASDL if you have entered U in the Copy audit to tape field on the A Series 

Environmental Options screen. 

It is your responsibility to ensure that the details are complete and syntactically correct, as 

syntax checking is not performed, and any errors may result in DASDL compilation or 

runtime failures. 

For further details on valid DMS II audit file attributes and details, see your DMS DASDL 

manual. 

Example 

78616208–001 3–27


The following examples show the sort of attributes you may wish to enter on this screen. 

 

 

 

 

 

 

 

 

 

3–28 78616208–001


Select Configure Pack/Population Option Screen 

The Select Configure Pack/Population Option screen enables you to select one or more of 

the following options for proceeding: 

• Proceed directly with the configure without any further changes. If you choose this 

action, the other two option values are ignored. 

• Change packs and populations on a Ispec/Profile basis. 

• Change your existing pack allocations on a pack basis. 

The fields on the Select Configure Pack/Population Option screen are described in the 

following subsections. 

Next Screen 

When this screen is transmitted, the message COPYING SOME FILES FROM TAPE is 

displayed, and there will be a short delay while the copying process completes. 

• If you chose the Proceed with configure field, the remainder of the Configure 

process will start immediately, and no further screens are displayed. 

• If you chose the Pack changes by family field, the Pack Name Changes screen 

will be displayed next. 

• If you chose the Pack and population changes field, the Event and Components 

selection screen will be displayed next. 

Only one of the Pack changes by family and the Pack and population changes 

fields can be chosen. 

Proceed With Configure 

Enter Y in this field to proceed directly with the Configure (rather than make any further 

pack and population changes). 

Enter HELP OPTIONS for online help. 

Pack and Population Changes 

Enter Y in this field if you want to make changes to pack names or populations for 

individual structures in the software you are configuring. For example, select this option if 

you know that the size of the database files are smaller than required in your installation. 

Further screens are displayed for you to select and change packs and structures that you 

want to modify. 


Pack Changes By Family 

Enter Y in this field if you want to change the packs, by family, when the Retain 

Existing Database field is set to Y. 

78616208–001 3–29



3–30 78616208–001

Pack Name Changes Screen 


The Pack Name Changes screen enables you to map packs on a pack-by-pack basis. This 

is an alternative to changing pack names on an Ispec/Profile basis. This screen is 

displayed if you entered Y in the Pack changes by family field on the Select 

Configure Pack/Population Option screen. 

The fields on the Pack Name Changes screen are described in the following subsections. 

Next Screen 

When you transmit this screen, the message CHANGING DASDL FILE is displayed, and 

there will be a short delay while the process of updating your DASDL file completes. 

If you chose the Pack and population changes field on the Select Configure Pack/ 

Population Option screen, the Event and Components Selection screen is displayed when 

you transmit this screen. 

If you did not choose the Pack and population changes field on the Select Configure 

Pack/Population Option screen, the remainder of the Configure process will start 

immediately, and no further screens will be displayed. 

78616208–001 3–31


Event and Components Selection Screen 

The Event and Components selection screen enables you to select the Event set or 

individual Components for reviewing current populations or pack locations. It is displayed 

if you entered Y in the Pack and population changes field on the Select Configure 

Pack/Population Option screen. 

The displayed structures are those for Host Builder itself, and relate to stored details of 

your Specifications (not generated systems and databases). 

For selected structures, you can also make population or pack changes for their Profiles. 

You can make similar changes after Host Builder is configured by using the Database 

Management Utility (DMU). For more details of DMU, see your Unisys e-@ction 


Next Screen 

When you transmit this screen: 

• If you do not select any Components or the Event set, the remainder of the Configure 

process will start immediately, and no further screens will be displayed. 

• If you select any Components or the Event set, the Populations and Packs screen will 

be displayed for the Event set, or for the first Component that you selected. 

3–32 78616208–001

Populations and Packs Screen 


The Populations and Packs screen enables you to alter the pack locations and the 

populations of the structures (and their Profiles) that you selected on the Event and 

Components selection screen. 

Your selected structures are displayed one at a time for you to make the required 

changes. 

Next Screen 

When you transmit this screen, your next selected structure is displayed (if any). 

After your last selected structure, the message CHANGING DASDL FILE is displayed, and 

there is a short delay while your DASDL file is updated. The remainder of the Configure 

process then starts, and no further screens are displayed. 

78616208–001 3–33


Installing Free-Standing Runtime Software 

Use these instructions to install free-standing Runtime Software. 

Note: This is not required if you are installing and configuring Host Builder as Runtime is 

installed as part of that process. 

To install free-standing Runtime software in an MCP environment, perform the following 

steps. 

Note: All parameters for LINC17/WFL/RUNTIME must be entered in upper case. 

1. Mount the media labeled L2R171. 

2. If your machine has Security Administrator status enforced (by enabling the 

SECADMIN option), and you have access to a usercode with SECADMIN status, 

then, log on to CANDE under that usercode or under a privileged usercode. 

3. Run SYSTEM/COPY to load down the configure WFL: 

 

4. Set your family statement for running the configure WFL, as follows: 

 

5. Run the Configure WFL, by entering: 

 

The pack value gives the required pack name, which may be DISK. 

The aliaspack value is the pack for your station alias file. See Unisys e-@ction 

Enterprise Application Runtime for ClearPath MCP Administration Guide for details of 

station aliases. 

The usercode value is your required usercode, which may be an asterisk (*). If you 

enter a usercode other than an asterisk (*), you must be logged on to CANDE under 

that usercode for both the SYSTEM/COPY and the START WFL. 

For example: 

• If you are copying all files as * to DISK, enter: 

 

• If you are copying all files to usercode USER1 and to pack PACK1, enter: 

 

No additional parameters are required for the installation of Runtime (that is, you are 

not required to complete any screen in the Configure Utility). 

6. Set up the required Support Libraries (SLs). If your host has Security Administrator 

(SECADMIN) status enforced, sign on to MARC with a SECADMIN status usercode. 

(Only a user/task/job with SECADMIN status may issue SL commands when 

SECADMIN status is enforced.) 

From MARC, enter: 

 

3–34 78616208–001


 

The altpack gives the alternate pack for the family of the usercode under which you 

are running Runtime. For example, your usercode family may be specified as follows: 

 

If so, enter SYSPACK as your altpack value. 

Configuration of Runtime is complete. For your next required step, see “Configuring 

COMS for Systems” on page 3–36. 

78616208–001 3–35


Configuring COMS for Systems 

The Configure Utility automatically loads the COMS Configuration file for your software 

into COMS. You may override this automatic load by supplying a user-coded library, as 

described later in this subsection. 

This automatic load does not apply to the COMS Stations file for new or changed 

Networks. 

You must manually load the COMS Configuration for NOF if required. 

Note: The COMS UTILITY window must be configured to support multiple active users, 

as the Auto-load process takes up one user slot. If the Maximum Users value is 

exceeded, the automatic load will fail. 

Inhibiting or Interrupting Automatic Loading 

The Configure Utility calls an entry point in a user-supplied library, and passes the COMS 

Configuration file name as a parameter. The library can programmatically verify and/or 

modify the parameter to allow or disallow the automatic loading. 

Library file 

The library file must be accessible under the file search path for the usercode under 

which you configured Enterprise Application Environment. The file is titled: 

 

If the library file is not found, or the library linkage fails, automatic loading proceeds. 

Entry point 

The entry-point is COMSVERIFY, defined as: 

 

 

The COMS_LOAD_FILE_TITLE parameter contains the title of the COMS Configuration 

file to be loaded. This file may be changed or replaced by a privileged process. 

Return values 

The COMSVERIFY procedure should return one of the following values: 

• The value 1 if the file is to be loaded. 

• The value 0 if the file is not to be loaded. 

3–36 78616208–001

Example 


The following ALGOL procedure inhibits the automatic for a usercoded system whose 

COMS Configuration file name begins with XX. Non-user-coded systems have COMS 

after the first slash (/) character. 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

COMS Configuration for the SWITCH.TO; Command 

The SWITCH.TO; command requires a COMS processing item such as TPTOMARC, to be 

installed for the MARCINPUT agenda in the COMS configuration data. 

The TPTOMARC processing item is provided on your release media in the sample file: 

 

For further details, see the example of the TPTOMARC processing item in your ClearPath 

HMP NX and A Series COMS Programming Guide. 

COMS Configuration for the WDP Interface Program 

The WDP interface program (LINC/WDPLAUNCH) requires a COMS processing item such 

as TPTOMARC, to be installed for the MARCINPUT agenda in the COMS configuration 

data. 

The TPTOMARC processing item is provided on your release media in the sample file: 

 

78616208–001 3–37


For further details, see the example of the TPTOMARC processing item in your ClearPath 

HMP NX and A Series COMS Programming Guide. 

Installing and Configuring Remote Subroutine 

Server 

Installation 

The Remote Subroutine Server (also known as LRSS) enables Developer Test to call 

subroutines from host Runtime platforms. 

To automatically install the Remote Subroutine Server enter the following. 

 

The location of the files will be based on the current directory. A Usercode and Pack name 

may also be provided as optional parameters to the install job. 

The following tasks are performed by the install: 

• Register the Remote Subroutine Server as a Distributed System Services (DSS) 

provider 

• Map the Support Library (SL) function names for Remote Subroutine Server 

Alternatively, the installation can be performed manually. Use the following commands 

from the system console or a suitably privileged station: 

1. To register Remote Subroutine Server as a DSS provider enter: 

 

2. To map Support Library (SL) function names for Remote Subroutine Server enter: 

 

 

Note: Usercode and Pack names may need to be inserted into the above commands as 

applicable. 

Configuration 

To configure Remote Subroutine Server you need to set the options in the configuration 

file that is read at startup. The file is at LRSS/CONFIG and all options have default 

settings, so users only need to change them if the need arises. 

The options are: 

 

 

 

 

3–38 78616208–001


 

 

 

These options are explained below: 

PORT 

The Port is the TCP/IP communications service number used to establish incoming 

connections from prospective clients. 

CONNECTIONS 

Connections is used to limit the total number of concurrent sessions available. 

MAXOFFER 

MaxOffer controls the number of listening port subfiles that are available. The range is 

either 1 through 99, or 1 through the number of connections allowed (if less than 99). 

INACTIVITY 

Inactivity is the interval of time between when TCP/IP “keep alive” packets are 

exchanged with the client. The inactivity value is mapped to the port file attribute 

DialogCheckInterval. 

TIMEOUT 

Timeout is the duration for which TCP/IP “keep alive” packets can continue to be sent 

before a connection is closed. The range is as applicable for the port file attribute 

BlockedTimeout. 

ERRORS 

The Errors option locates the filename for any configuration problems found. Messages 

are logged to the error file with a reference to the problem line in the configuration file. 

TRACE 

Trace is available for observing Remote Subroutine Server behavior or diagnosing 

problems. Tracing can be turned on or off, and the title of the trace file can also be set. 

The default value is off and the default title is LRSS/TRACE/#, where # is a numerator 

starting at zero. Each time the server starts, the trace file name's numerator restarts at 

zero. 

Comments 

Comments can be placed anywhere in the text stream and are terminated by the end of 

each line. A comment is denoted by the presence of either a percent or an asterisk 

character in the text stream except when enclosed by quotation marks. Syntax: 

 

 

78616208–001 3–39


Operations 

Monitoring 

Remote Subroutine Server can be controlled through the Network Application (NA) 

interface. You can start, stop, show status or change trace options. These commands are: 

When the RELEASE option is used on the trace command, the existing trace file is closed 

and a new trace file is opened with an increment to the numerator portion of the trace file 

title. 

If Remote Subroutine Server is not running, it will start automatically when an incoming 

connection is attempted on the port service number registered through DSS for Remote 

Subroutine Server. 

A facility exists in Remote Subroutine Server to monitor remote procedure calls made 

from its clients. The monitor facility is programmatically interfaced and provision is given 

to veto any remote procedure calls at hand. 

The monitor CALL; is made depending on an entry point within a user written application. 

For the monitor to work a Support Library (SL) named LRSSMONITOR must exist. This SL 

is checked for at startup. 

The entry point is described, and an example given, in the sample source file . 

Installing the MCP Builder Server 

Software Requirements 

Action Command 

Start NA LRSS + 

Stop NA LRSS - 

Show Status NA LRSS STATUS 

Trace NA LRSS TRACE [ON | OFF | RELEASE] 

The MCP-based Builder program requires the following software: 

• ClearPath NX HMP 3.0 or A Series SSR 44.2 or later 

• COMS installed and configured 

The release level required depends on the system type: 

– For ClearPath HMP systems, release levels 44.2A.30, 45.1A.12, or later can be 

used. 

– For A Series systems, release level 45.1A.12 or later is required. 

3–40 78616208–001

Installation 


– To login with either an Accesscode or a Chargecode, release level 46.1 is 

required. 

• Enterprise Application Environment or Runtime at release level 3.1 or above 

• Developer software at release level 3.1 or above 

These instructions are additional to any installation instructions for Enterprise Application 

Environment or Runtime. 

You can install Builder manually or via the supplied WFL job LINC17/WFL/BUILDER. 

For either installation method: 

• EAE-usercode is the usercode for the Enterprise Application Environment 

• CPA-familyname is the familyname for the Builder CPA file 

• logfile-familyname is the familyname for the Builder log file 

• usercode is the user selected usercode 

• EAE-object is the Object pack for the Enterprise Application Environment 

• EAE-dictionary is the Dictionary pack for the Enterprise Application Environment 

• pack is the user selected pack 

• EAE-alternate-pack is the alternate pack for the Enterprise Application Environment 

usercode 

• Entries within braces {...} are optional, with DISK being the default familyname 

Installing the Builder Codefile via the WFL 

The supplied WFL performs the MODIFY and COPY of the codefile, the SL definition and 

DSS configure, using the LINC17/SAMPLE/APPL_BUILD_31/LOAD file. 

To use the WFL, enter the following command. You must supply the EAE-usercode, EAEdictionary, 

and EAE-object parameters. To choose an alternate pack for the Enterprise 

Application Environment usercode, you must also supply the EAE-alternate-pack 

parameter. If you omit this parameter, the job will default to the current usercode's family 

substitution. 

 

 

Installing the Builder Codefile Manually 

Modify, and then copy, the Builder codefile from the Enterprise Application Environment 

onto a user selected pack using the following commands: 

78616208–001 3–41


 

 

 

 

 

 

Defining SL entry 

If Builder has been previously installed, use the following system commands to close 

down the current Builder and break the current SL: 

 

 

Use the following system command to establish the new SL: 

Here: 

 

• usercode is the user selected usercode 

• pack is the user selected pack 

Configuring the DSS 

Builder is installed as a DSS (Distributed System Server) that communicates to the 

Developer client via a port file interface using socket 7770. 

A sample LOAD file is included on the release media, LINC17/SAMPLE/APPL_BLD_31/ 

LOAD. You must not alter the names provided in the load file. Note that the inclusion of 

the current Builder release level in the name is to allow multi release level Builders to coexist 

on the one MCP host. 

Setting up FTP 

Set up FTP to allow access to the usercode from Builder. Use the following SYSTEM/ 

MAKEUSER +RU commands: 

 

 

Where nnn[.nnn[.nnn[.nnn]]] contains the required IP address nodes. 

3–42 78616208–001

Section 4 

Signing On to Enterprise Application 

Environment 

To sign on to your Enterprise Application Software, perform the following steps: 

1. Sign on to the COMS window that has been set up for your Enterprise Application 

Software (for example, LINC17). 

 

If the COMS window, program, and database are not correctly set up and all enabled, 

you will receive a COMS error message at your terminal. You may have to contact 

your systems administrator or operations supervisor before proceeding. 

If the COMS window, program, and database are correctly set up and enabled, the 

LSS program and at least one copy of the COMSTP program is then initiated. Any 

other COMSTP programs with a non-zero value of MINCOPIES are also initiated. 

Otherwise, the message INITIALIZATION COMPLETE is then displayed at the 

Operator Display Terminal, and after a short interval, the Welcome screen is displayed 

at your terminal. 

Note: Further copies of the general COMSTP programs will be initiated as required, 

up to a maximum number set in MAXCOPIES. The Utility Subsystem and the Generate 

Subsystem will be initiated whenever a terminal selects a utility function or a 

Generate, respectively. 

If you want introductory information about signing on, transmit HE or HELP from the 

Action field on line 2. (All screens that have an Action field may use this method to 

obtain brief information about the procedures relevant to that screen.) 

The Help information for signing on to Enterprise Application Environment is then 

displayed on Page 2. You may switch back to Page 1 to continue. 

2. Enter a Specification name and session language. If Change Control is invoked, you 

will also have to enter your Change Identifier. For more details, see Section 1 of your 

Unisys e-@ction Enterprise Application Host Builder Guide. 

You may now use your software. 

Note By using the log, it is possible to report on all user transactions against Host 

Builder. For more details, see your Unisys e-@ction Enterprise Application Runtime for 

ClearPath MCP Administration Guide. 

78616208–001 4–1

Signing On to Enterprise Application Environment 

4–2 78616208–001

Section 5 

Migrating to Release 3.1 

Migration Procedure 

Use the following procedure to migrate your systems: 

1. Take note of the various migration issues outlined in “Addressing Migration Issues” 

on page 5–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 “Software 

Requirements” on page 2–6. 

5. Use one of the following procedures to migrate from release 16.3 to release 3.1: 

• Use LCOPY to extract your Specifications from release 16.3 and load them into 

release 3.1. See “Using LCOPY” on page 5–2. 

• You can also use CASE LOAD, but this will take longer than LCOPY. 

6. Run the Report C85PCHECK, which is included in your Release Media. Examine the 

Report output and take any corrective action required. 

7. After using LCOPY to copy your specification to release 3.1, it is recommended that 

you perform a syntax-only generate of your system before you generate the new 

system. 

8. Generate your systems. See “Generating Your Systems after Migration” on 

page 5–10. 

78616208–001 5–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 3.1 

Use the following procedure to migrate from release 16.2 to release 3.1: 

1. Unload your existing Specifications (including GLOBAL) from your Developer system, 

by using LCOPY. 

2. Install release 3.1. 

3. Load your Specifications into your new Host Builder, by using LCOPY. 

4. Generate your systems, as described in “Generating Your Systems after Migration” 


LCOPY is documented in Unisys e-@ction Enterprise Application LCOPY Guide. 

Loading into earlier releases 

From To 15 To 16 To 3.1 

15 Y Y Y 

16 – Y Y 

3.1 – – Y 

Using LCOPY, you can load Specifications created in (or migrated to) release 3.1 into 

release 16. You may encounter syntax errors if the Specification includes features 

specific to release 3.1. 

When you load a Specification in this way, all logic lines are marked for re-edit. 

Using LCOPY Compare across major releases 

Between major releases of Host Builder (for example, release 16 and release 3.1), there 

are often differences in how Specifications are stored. 

You cannot use the LCOPY Compare function to compare Specifications across major 

releases. 

Updating local patches to CCsversion for MCP based hosts 

If you are migrating from release 15 to release 3.1, and you have applied a local patch to 

set CCsversion in the DASDL, COMSTP programs, and Reports, you must ensure that 

the correct CCsversion is applied in the DASDL Defaults screen before your first generate 

your systems under release 3.1. 

5–2 78616208–001


This removes the need for any unnecessary reorganizations, and marks all of the Ispecs 

and Reports for extraction and compilation. 

Notes: 

• As the PROGRAM COLLATING SEQUENCE is defined in COMSTP programs and 

Reports, changes in functionality may occur in your system. 

• As COMSTP programs and Reports automatically use the same CCsversion defined 

for the database, some performance degradation may be noticed. 

78616208–001 5–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. 

Global Setup Data Blocks 

Release 3.1 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: 

• 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 3.1 input files. 

Population Setting 

Release 3.1 allows for population, population increases, warning percentages, and pack 

information to be set from within Host Builder for internal structures, Adhoc, ROC, and 

Graphical Interface Workbench (PCE) structures. 

On migration from 16.x to 3.1, the current value of any population and pack settings will 

be available using this option from within Host Builder. 

5–4 78616208–001

CCsversion Settings 


If you are migrating from release 16 to release 3.1, all EDIT; A painted data items, SDs, 

and GSDs will have the DEF.NATIONAL.ITEM; attribute set, except for the following 

items, which have the NO.NATIONAL.ITEM; attribute: 

• Painted Dictionary items 

• Painted qualified data items 

• Data items, SDs, or GSDs that are defined SAME.AS a dictionary item or a qualified 

data item 

If you have set CCsversion in the DASDL, Update programs, and Reports, you will need 

to set the Use 2 Bytes/I18N field to C, and choose whether to set the National Item 

default to Y for the Specification, Component, Report or Dictionary items. 

Rounding from Compute Commands 

In release 3.1 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. 

New Database Blocksize Feature 

This feature will allow Enterprise Application Environment and user systems to take 

advantage of performance improvements when using 512-byte sector disks. 

For migration to release 3.1, the value of Optimize Blocksize to VSS-2 for existing 

gensets and components is set automatically to: 

• D for all Ispecs and Events 

• N for all Generate Sets 

Once the system is migrated, you can set Optimize Blocksize to VSS-2 to Y from 

the Global DASDL Defaults screen if the new BLOCKSIZE feature is required for all Ispecs 

and Events. 

When the blocksize is changed, this may cause the database to reorganize. 

Network Maintenance (NETMAINT) 

Following the de-implementation of the Network Configuration System (NETCON) in 

release 3.1 there is still a requirement to maintain details of terminals, printers, and hosts 

previously stored in the NETCON database. NETMAINT provides a replacement for the 

NETCON features used to define host and device information. 

78616208–001 5–5


Migration from a previous release to this release will require minimal user intervention 

with regards to the NETMAINT feature modification. A conversion utility is provided that 

converts LINCNET files from previous releases. This produces a file in COMS load format 

(to be subsequently loaded via CEL), which will: 

• Add model information to the station Installation Data records for user defined 

terminal types. 

• Add host Installation Data records. 

• Add or modify Installation Data records for printers. 

Installation Data records are created or modified for all printers, to add model information. 

The records for terminals is not modified unless the terminal type cannot be determined 

using Integer1 (that is, it is not a T27 or one of the other defined types). 

Although there are changes to the format of COMS Installation Data records, these are 

compatible with previous releases, and should not affect co-existence of releases 16 and 

3.1 on the same host. 

LINCNET file (from previous releases) 

Conversion (GEN) (LINC17GEN "NET") 

COMS.CONFIG 

definitions 

NET17/COMS/STATIONS 

COMS Utility 

(manual load) 

NETCON Conversion Process 

(LOad format) 

COMS Configuration 

file 

Workstation Driver Program (WDP) Database 

In release 3.1, the WDP ISAM files are moved into the database to improve locking and 

resizing, and availability of updated Graphical Interface Workbench (PCE) information on 

Remote Database (RDB) secondary takeover. 

To convert the pre-3.1 ISAM files to flat files, perform the following steps before you 

migrate from 16.x to 3.1: 

5–6 78616208–001


1. Logon to a CANDE session with the user code of the system. 

2. Run the conversion utility WDPCONVERT from CANDE against your system. The file 

equation of WDPCONVERT'S WCF-FILE is used to specify where the existing ISAM 

WDP files reside. For example: 

 

 

WDPCONVERT produces a report on the minimal populations required in the GLB-WDP 

database structures. The information in this report may be used to set populations in the 

specification before the conversion generate to release 3.1. 

During the migration generate, WDP runs to load the flat files into the database 

structures. 

Saved Transfer Parameter Processing (STPP) 

Localization 

In release 3.1, the Transfer Parameter Selection screen is removed from the Interactive 

Development Environment and the Transfer and Configure WFL are maintained in WFL 

Include files instead. A sequence range in the Include file corresponds to each of the 

parameters from the Transfer Parameter Selection screen. 

The process of converting LDL from release 15/16 to release 3.1 happens automatically 

as described below. No user intervention is required. 

• LCOPY detects and writes the Saved Transfer Parameters to WFL Include files when 

Specifications are loaded to release 3.1. The flat files will reside on the dictionary 

pack of the Interactive. The filenames will be system/INCLUDE/saved transfer 

parameter, where system is the specification being loaded, and saved transfer 

parameter is the name of the Saved Transfer Parameter. 

• The Include files are created automatically by a report zipped from LCOPY when a 

specification into the Host Builder 3.1 from a LINC 15/16 CPY file application, 

including logic from the saved parameter files. 

Note: WFL does not allow nested Include files. If your saved transfer parameters are in 

the form of nested files, you will need to move the contents of the nested file into its 

parent Include file. 

In release 3.1, all translatable messages displayed by programs now use the MCP based 

MLS software to translate runtime messages from a MLSLIBRARY file instead of the 

LLANGUAGE file, as was previously the means of supplying the translated messages. 

The new library is copied to the alternate pack of the FAMILY attribute of the installation 

job – to the same pack as the LINCxx/1/LIBRARY library. 

The new library has a FILENAME of LINCxx/MLSLIBRARY and is installed as a system 

library with a FUNCTIONNAME of LINCxxMLSSUPPORT. 

78616208–001 5–7


The default installation language specified on the HOME screen of the installation 

CONFIGURE program is assumed to be the default language within the MLSLibrary. This 

default language may later be altered by modifying the LANGUAGE task attribute of the 

LINCxx/MLSLIBRARY library. 

Program Initializaton 

Within its initialization, the program attempts to locate a library with the name: 

LINCxx/MLSLIBRARY (no usercode or pack family specified) 

If this library is located, the program will link to it, BYTITLE, to obtain its required 

messages. 

If the library cannot be located, the program will modify the library attributes, and link to 

the global system library, BYFUNCTION, to obtain its required messages. 

Initialization of Library 

If the LANGUAGE task attribute has not been specified, the host environment is 

interrogated for the host default language. The language determined from this, or from 

the LANGUAGE task attribute, is validated with the languages contained within the library. 

If the determined language is not available, a default language is determined by the MLS 

software (usually the first language found). 

Translator Information 

Enterprise Application Environment provides a translator's comment associated with 

each message, containing the message-text length of the originally provided message. 

This is immediately available to the translator when the associated message is accessed 

for translation. 

Extract Format for Data Interchange 

Release 3.1 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 3.1 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) 

5–8 78616208–001

• G for Generic record format 

The Ispec Format field is unique by genset 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. 

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 16.2, 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 3.1, 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 3.1 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. 

78616208–001 5–9


Generating Your Systems after Migration 

Procedure 

To generate your migrated Specifications, perform the following procedure: 

1. Sign on to Host Builder for release 3.1 

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 3.1 features. See “Addressing Migration Issues” on 

page 5–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. 

5–10 78616208–001

Appendix A 

Using the USS5100 Unisys Remote 

Data Facility 

The USS5100 Unisys Remote Data Facility (URDF) is a disk mirroring system that can be 

used to provide a remote copy of an application for disaster recovery backup purposes. 

The following issues should be considered when using the URDF with systems: 

• Capabilities within MCP based software in order to optimize data recovery 

• Minimize system downtime in the event a switch to the remote system becomes 

necessary 

Planned Recovery 

Planned recovery indicates that the application has been successfully taken to EOJ the 

source host. 

The following table shows the non DMSII files that require mirroring: 

File Family 

Linccntl Dictpack 

Linclog Logpack 

Unique/Save Dictpack 

Extract files Extrackpack 

Roc Data Files Rocpack 

If the application is Graphical Interface Workbench (PCE) capable, the following files also 

require mirroring: 

File Family 

Lincbuf Dictpack 

Lincbdf Dictpack 

Lincscl Dictpack 

Lincsdf Dictpack 

78616208–001 A–1

Using the USS5100 Unisys Remote Data Facility 

Note: These files may have different extensions depending on the host system using 

KEYEDIO or KEYEDIOII. 

There are a number of files that must be synchronized between hosts, based on the 

assumption that the alternate family (DISK) or the backup family (PACK) will not be 

mirrored across hosts. 

These files and disk families are shown in the following table. 

In addition, the development or runtime environments must also be present on both 

hosts. Having this software loaded ensures the system-wide runtime libraries will always 

be available. 

Online Application Takeover 

Planned Takeover 

Lincwcf Dictpack 

Lincwdf Dictpack 

Wcf/Lincbuf Dictpack 

File Family 

*Coms/Cfile Disk 

*Lincsys/Codes Disk 

*Linc/Stn/Alias Disk 

*Linc17/Wdp/Applications 

(PCE capable applications only) 

File Family 

In the case of a planned takeover, before you attempt to log into the application on the 

secondary host, perform the following steps: 

1. Ensure that the latest system/COMS/CONFIG/FULL file details are contained in the 

*COMS/CFILE. 

If you are unsure, load this file (located on the dictionary pack) via the COMS batch 

load facility on the Utility window. 

2. If the system has COMS Protected Output and Protected Input enabled, as a 

precaution, you can disable COMS recovery. To do this: 

• Go to the DRC window of the COMS Utility. 

• Set Create New file to Y. 

• Set RDS pointer to end to Y. 

A–2 78616208–001


3. Log into the application. The normal system startup should proceed. 

During the takeover, if you log back into the application with a different terminal id, then a 

new Glb-Dialoginfo record is created. If this occurs, you might want to maintain the same 

Installation Data across the Configuration files on both hosts. This will ensure that when a 

user logs in to either host, the same privileges are granted by both hosts. 

Unplanned Takeover 

In the case of an unplanned takeover, before you attempt to log into to the application 

window on the secondary host, perform the following steps: 

1. Ensure the latest system/COMS/CONFIG/FULL file details are contained in the 

*COMS/CFILE. 

If you are unsure, load this file (located on the dictionary pack) via the COMS batch 

load facility on the Utility window. 

2. If the system has COMS Protected Output and Protected Input enabled, as a 

precaution, you can disable COMS recovery. To do this: 

• Go to the DRC window of the COMS Utility. 

• Set Create New file to Y. 

• Set RDS pointer to end to Y. 

3. Log into the application. At this stage *SYSTEM/DMRECOVERY will be started to 

recover the database. If there are any DMSII recovery issues, refer to your ClearPath 

HMP NX and A Series DMSII Utilities Operations Guide. 

Notes: 

• Once DMRECOVERY is complete, LSS will restart any Reports that were running at 

the time of the takeover. See the “Report Recovery during Unplanned Takeover” on 

page A–4 for details on this phase of recovery. 

• The system data item GLB.UNIQUE value will increased by 2,500 from the value 

contained on the source host before the takeover. 

• The LINCLOG will have lost a number of records, depending upon when the log buffer 

was last flushed. If the LINCLOG is critical to your application, it may be necessary to 

implement procedures where the LINCLOG is regularly released to minimize the 

impact of losing any records. 

During the takeover, if a user logs back in to the application with a different terminal id, a 

new Glb-Dialoginfo record will be created. If this is the case, it would be good practice to 

ensure the same Installation Data is maintained across both hosts’ Confguration files. 

This will ensure that when the user logs on to either host, the same privileges are 

granted. 

If the user logs back with a different terminal id, the last screen may not be able to be 

recalled, and the following error is displayed: 

 

78616208–001 A–3


This will also indicate that the last instance of GLB.WORK is no longer available. 

Unplanned Takeover during Reorganization or System 

Generation 

If an unplanned takeover occurs during a reorganization or a system generate, it will be 

necessary to: 

• Reload the application from the latest backups. 

• Start the reorganization or generation from the beginning. 

Report Recovery during Unplanned Takeover 

Reports will be restarted by LSS when the SYSTEM/DMRECOVERY completes on the 

secondary system. 

In the following two cases, the Reports were all restarted with Critical Points. If any 

Reports that do not contain Critical Points are restarted, then those Reports will be run 

from the beginning. Consequently, all Report output will be started from the beginning. 

Reports Creating Extract Files 

The Report will restart from the last Critical Point, and if the Extract pack is mirrored, the 

Extract file will continue writing records from the last record written at the Critical Point. 

Reports Using ROC Flat Files 

The Report will restart from the last Critical Point, and if the ROC data pack is mirrored, 

the Report will continue writing records from the last record written at the Critical Point. 

You should take care when the Report completes, or the Report is released for printing, 

because the ROC sleeping Report will attempt to route the Report back to the source 

host for printing. At this stage, the source host might not be available. 

It may be necessary to set ROC to 0, and when the Report completes, send it to a new 

destination using the ROC Inquiry screens. This only applies to restarted Reports. 

Reports writing directly to a printer backup 

The Report will restart from the last Critical Point. It is unlikely that the backup family will 

be mirrored, in which case the Report output completed at the last Critical Point will be on 

the backup family of the primary host, which may not now be available. All new output 

from this restarted Report will be written to the backup family on the secondary host. 

A–4 78616208–001

Appendix B 

Related Product Information 

The following documents contain information relevant to the definition and operation of a 

system. These publications are intended as reference sources for users who have 

completed training courses, and do not replace these courses. See your local Unisys 

representative for information on available training courses. 

These documents are published by Unisys Corporation and are available on the Internet at 

http://www.support.unisys.com. Order hardcopy documents through the Electronic 

Bookstore at http://www.bookstore.unisys.com. 

Unisys e-@ction Enterprise Application Runtime for ClearPath MCP 


This document describes the generation and operation of systems and Reports, and the 

general administration of systems for MCP based hosts. 

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 Manual 

This document contains reference material for users, such as logic commands and 

System Data items used in creating systems. 

Unisys e-@ction Enterprise Application Host Builder Reference Manual: 

Painter and Editor 

This document contains reference material for Host Builder, including Editor and Painter 

commands, Data commands and Data Attributes, and screens and commands for 

defining Profiles. 

Unisys e-@ction Enterprise Application LCOPY Guide 

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

transfer Specifications between versions of Builder. 

ClearPath HMP NX and A Series Communications Management System 

(COMS) Programming Guide (8600 0650) 

This document describes the use of the WDP interface program (LINC/WDPLAUNCH) 

and the required COMS processing item, TPTOMARC. 

78616208–001 B–1

Related Product Information 

B–2 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

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. 

78616208–001 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 78616208–001

Index 

A 

Access external DB specifications, 3–26 

accesscodes 

installed Enterprise Application Software, 

3–9 

Allow Editor Resequence option, 3–22 

audit files 

copy to tape option for, 3–23 

pack for, 3–19 

secondary, 3–19 

audit level 

installation option for, 3–15 

Audit pack, 3–19 

auditing, reorganization, 3–25 

auto-load 

inhibiting COMS, 3–36 

B 

Builder 

installing, 3–41 

setting up FTP, 3–42 

software required for, 3–40 

Builder codefile 

installing manually, 3–41 

installing via WFL, 3–41 

C 

CCsversion migration issues, 5–2 

change control 

enabling, 3–14 

identification mode for, 3–14 

installation options for, 3–11, 3–14 

chargecode 


3–9 

command 

processing item for, 3–37 

Components 

reviewing packs and populations for, 3–32, 

3–33 

COMS 

configuring, 3–36 

inhibiting auto-load for, 3–36 

station definitions for, 2–9 

SWITCH.TO command handling by, 3–37 

WDP program handling by, 3–37 

window name, 3–9, 4–1 

configuration parameters 

entering, 3–6 

Configure Utility, 3–5 

installing with, 3–6 

online help in, 3–6 

options screen, 3–8 

Configure utility screens, 3–7 

Configure WFL 

job name of, 3–9 

setting Tasklimit for, 3–3 

configuring DSS for Builder, 3–42 

Copy Audit To Tape 

installation option, 3–23 

installation screen, 3–27 

78616208–001 Index–1 

D 

database 

configured Enterprise Application Software, 

3–8 

not retaining an existing, 3–8 

retaining an existing, 3–8 

Database Management Utility (see DMU), 3–3 

Database pack, 3–19 

Default pack, 3–17 

DEPCON installation, 2–7 

Developer 

installation options for transfer to, 3–12 

Dictionary pack, 3–18 

dictionary pack for system family, 3–10 

disaster recovery 

remote copy of DMSII database, A–1 

disk space requirements, 2–5 

Distributed System Server configuration for 

Builder, 3–42

Index 

DMS II 

options for level of, 3–24 

remote copy of database, A–1 

specifying pack for, 3–25 

specifying usercode for, 3–24 

DSS configuration for Builder, 3–42 

duplicate LINCSUPPORT libraries, 3–4 

E 

Editor 

specifying resequence option for, 3–22 

Enterprise Application Environment 

signing on to, 4–1 

environmental DMS options, configuration, 

3–23 

environmental options, configuration, 3–21 

Event pack, 3–17 

Event set 

reviewing packs and populations for, 3–32, 

3–33 

External DB 

Access specifications, 3–26 

Extract pack, 3–20 

F 

files copied during installation, 3–3 

FTP setup for Builder, 3–42 

G 

generating a migrated System, 5–10 

Graphical Interface Workbench, 5–9 

files that require remote mirroring, A–1 

migrating Systems using, 5–9 

non-use of, 5–9 

processing item for WDP interface, 3–37 

stations for, 2–9 

support for, 5–9 

H 

hardware requirements, 2–4 

Host 

Updating CCsversion for MCP, 5–2 

Host Builder 

Change Control options for, 3–14 

changing populations in, 3–3 


product summary of, 2–1 

signing on to, 4–1 

host setup procedure, 2–8 

Index–2 78616208–001 

I 

IBM 3270 terminals 

using Runtime on, 2–14 

identification mode 

enabling, 3–14 

installation 

Builder, 3–41 

Builder codefile, 3–41 

Host Builder, 3–5 

online help for, 3–6 

preparing for, 3–2 

L 

language 


3–9 

LCOPY 

compatibility with Host Builder releases, 

5–2 

loading Specifications, 5–2 

migration, 5–2 

Library operation description, 2–16 

LINCSUPPORT library 

checking for duplicate, 3–4 

LINC/NET file conversion, 3–3 

locking 

resource, 3–14 

log file 

specifying size of, 3–21 

Log pack, 3–18 

logging options, 3–21 

LRSS, 3–38 



monitoring, 3–40 

operations, 3–40 

LSS program initiation, 4–1

M 

MCP 

Updating CCsversion, 5–2 

media summary, Release 3.1, 2–3 

migration, 5–2 

CCsversion settings, 5–5 

environmental settings, 5–4 

extract format for data interchange, 5–8 

first generation after, 5–10 

Global Setup Data blocks, 5–4 

Graphical Interface Workbench, 5–9 

localization, 5–7 

network maintenance, 5–5 

optimize blocksize to VSS-2, 5–5 

population settings, 5–4 

procedure, 5–1 

rounding from COMPUTE commands, 5–5 

saved transfer parameter processing, 5–7 

using LCOPY, 5–2 

Workstation Driver Program (WDP) database, 

5–6 

N 

networks 

software required for cross-host transactions, 

2–6 

O 

Object pack, 3–18 

online help installation, 3–6 

P 

packs 

changing details of, 3–29 

changing Event and Component, 3–32, 

3–33 

changing names of, 3–31 

configuring system, 3–17 

specifying DMS II, 3–25 

patch identification installation option, 3–15 

planned recovery using remote mirroring, A–1 

planned takeover, A–2 

planned takeover using remote mirroring, A–2 

Index 

POF family 

specifying, 3–22 

specifying duplicate, 3–22 

POF file name 


populations 

changing pack, 3–29 


reviewing Event and Component, 3–32, 

3–33 

preinstallation checklist, 3–2 

product summary 

Enterprise Application Environment, 2–1 

protected input 


Protected Output File (see POF), 3–22 

78616208–001 Index–3 

R 

recovery 

planned, using remote mirroring, A–1 

release media, 2–3 

name of, 3–10 

type of, 3–10 

remote copy of DMSII database, A–1 

remote mirroring, A–1 

planned takeover, A–2 

Report recovery, A–4 

unplanned takeover, A–3 

Remote Subroutine Server, 3–38 



monitoring, 3–40 

operations, 3–40 

Reorg pack, 3–19 

reorganization 

Configure Utility options for, 3–25 

norestart, 3–25 

offline, 3–25 

sort sets, 3–25 

Report recovery 

remote mirroring, A–4 

resequencing Editor option, 3–22 

reserved words 

installation options for, 3–12 

setting target hosts for, 3–12 

resource locking installation option, 3–14 

Retain Existing Database configuration option, 

3–8 

Runtime software

Index 

installing freestanding, 3–34 

product summary of, 2–2 

runtime version installation options, 3–15, 

3–16 

S 

Secondary Audit pack, 3–19 

security 


Security Administrator status, 3–5, 3–34 

setup procedure for host, 2–8 

sign-on 


online help about, 4–1 

software compatibility, 2–7 

software requirements, 2–6 

Builder, 3–40 

sort sets 

reorganization, 3–25 

Specification administration 

installation option for, 3–15 

Specifications, 5–2 

generating after migration, 5–10 

loading using LCOPY, 5–2 

Station pack, 3–18 

SWITCH.TO, 3–37 

system family 

dictionary, 3–10 

system name 

configured Enterprise Application Software, 

3–8 

system packs 


system software requirements, 2–6 

System Transfer, 2–2 

T 

takeover 

planned, using remote mirroring, A–2 

unplanned, using remote mirroring, A–3 

target hosts, installation options, 3–10, 3–12 

Tasklimit 

Configure WFL, 3–3 

templates 

option for LSO, 3–22 

setting host types for, 3–12 

terminals 

COMS station definitions for, 2–9 

configuration settings for, 2–10 

IBM 3270, 2–14 

supported, 2–4 

terminology, 2–1 

Index–4 78616208–001 

U 

unplanned takeover using remote mirroring, 

A–3 

Update programs 

initiation of, 4–1 

usercode 


3–9 

specifying DMS II, 3–24 

USS5100 Unisys Remote Data Facility (URDF), 

A–1 

W 

WDP program 

Graphical Interface Workbench, processing 

item for, 3–37 

Welcome screen 


WFL family 


window 


3–9 

signing on to Enterprise Application Environment, 

4–1 

work files pack for Configure Utility, 3–10

Unisys 

*78616208-001* 

78616208-001

Runtime for ClearPath MCP Installation and Configuration Guide

Create successful ePaper yourself

Delete template?

Save as template?