Runtime for ClearPath OS 2200 Installation and Configuration Guide
Runtime for ClearPath OS 2200 Installation and Configuration Guide
Runtime for ClearPath OS 2200 Installation and Configuration Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Unisys e-@ction<br />
Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong><br />
<strong>OS</strong> <strong>2200</strong><br />
<strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong><br />
Copyright © 2000 Unisys Corporation.<br />
All rights reserved.<br />
Level 3R1A<br />
November 2000 78616323-000<br />
Unisys
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related in<strong>for</strong>mation described<br />
herein is only furnished pursuant <strong>and</strong> subject to the terms <strong>and</strong> conditions of a duly executed agreement to purchase or<br />
lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described<br />
in this document are set <strong>for</strong>th in such agreement. Unisys cannot accept any financial or other responsibility that may be<br />
the result of your use of the in<strong>for</strong>mation in this document or software material, including direct, special, or consequential<br />
damages.<br />
You should be very careful to ensure that the use of this in<strong>for</strong>mation <strong>and</strong>/or software material complies with the laws, rules,<br />
<strong>and</strong> regulations of the jurisdictions with respect to which it is used.<br />
The in<strong>for</strong>mation contained herein is subject to change without notice. Revisions may be issued to advise of such changes<br />
<strong>and</strong>/or additions.<br />
Notice to Government End Users: The software <strong>and</strong> accompanying documentation are delivered <strong>and</strong> licensed as<br />
“commercial computer software” <strong>and</strong> “commercial computer software documentation” as those terms are used in 48<br />
C.F.R. § 12.212 <strong>and</strong> 48 C.F.R. § 227.7202-1 through 227.7202-4, as applicable. The Government shall receive only those<br />
rights provided in the st<strong>and</strong>ard commercial software license, or where applicable, the restricted <strong>and</strong> limited rights<br />
provisions of the contract FAR or DFARS (or equivalent agency) clause.<br />
Correspondence regarding this publication should be <strong>for</strong>warded to Unisys Corporation by addressing remarks to Product<br />
In<strong>for</strong>mation, Australian Centre <strong>for</strong> Unisys Software, 115 Wicks Road, North Ryde, NSW 2113, Australia. Comments about<br />
documentation can also be sent through e-mail to linc.pi@unisys.com.<br />
All terms which may be mentioned in this document that are known to be trademarks or service marks have been<br />
appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this in<strong>for</strong>mation. Use of a term in this<br />
document should not be regarded as affecting the validity of any trademark or service mark.<br />
Unisys, LINC, INFOConnect, <strong>ClearPath</strong>, <strong>and</strong> PowerClient are registered trademarks, <strong>and</strong> e-@ction <strong>and</strong> Griffin are<br />
trademarks of Unisys Corporation.<br />
EPSON is a registered trademark of Seiko Epson Corporation.<br />
HP <strong>and</strong> HP-UX are registered trademarks of the Hewlett-Packard Company.<br />
IBM, DYNIX/ptx, AIX <strong>and</strong> RS/6000 are registered trademarks of International Business Machines Corporation.<br />
JADE is a trademark of Aoraki Corporation Limited.<br />
Micro Focus <strong>and</strong> Net Express are registered trademarks of Merant International Limited.<br />
Microsoft, Windows, Windows NT, <strong>and</strong> Internet Explorer are either registered trademarks or trademarks of Microsoft<br />
Corporation in the United States <strong>and</strong>/or other countries.<br />
ORACLE <strong>and</strong> SQL*Plus are registered trademarks of Oracle Corporation.<br />
SPARC is a registered trademark of SPARC International, Inc. Products bearing SPARC trademarks are based on an<br />
architecture developed by Sun Microsystems, Inc.<br />
SQL Server is a trademark of Sybase, Inc. or its subsidiaries<br />
Sun, Java <strong>and</strong> Solaris are registered trademarks of Sun Microsystems, Inc. in the United States <strong>and</strong> other countries.<br />
UNIX is a registered trademark in the U.S. <strong>and</strong> other countries, licensed exclusively through X/Open Company, Ltd.<br />
UnixWare is a registered trademark of The Santa Cruz Operation, Inc.
Contents<br />
Section 1. Introduction....................................................................... 1–1<br />
About This Document ....................................................................................1–1<br />
Purpose .......................................................................................1–1<br />
Audience .....................................................................................1–1<br />
Notation Conventions ..................................................................1–1<br />
Windows 2000 Compatibility .........................................................................1–2<br />
Unisys e-@ction Br<strong>and</strong>ing ...............................................................................1–2<br />
Enterprise Application Environment Products .............................1–3<br />
Graphical Interface Workbench Products ....................................1–4<br />
Enterprise Application Environment Product In<strong>for</strong>mation ...........1–4<br />
Windows Operating Systems ........................................................................1–6<br />
Section 2. Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application<br />
Environment Software .................................................. 2–1<br />
About Enterprise Application Environment Software .....................................2–1<br />
Be<strong>for</strong>e Installing Your <strong>OS</strong> <strong>2200</strong> Based System ..............................................2–3<br />
Hardware Requirements .............................................................2–4<br />
Checklist <strong>for</strong> <strong>OS</strong> <strong>2200</strong> Based System Software .........................2–6<br />
Other Software Considerations ...................................................2–9<br />
Installing <strong>and</strong> Configuring Required <strong>OS</strong> <strong>2200</strong> System Software ..................2–11<br />
Configuring <strong>and</strong> Regenerating Your EXEC .................................2–11<br />
CMS 1100 <strong>and</strong> MCB <strong>Configuration</strong> ...........................................2–15<br />
UDS Software <strong>Configuration</strong> .....................................................2–16<br />
Applying System Software Changes .........................................2–17<br />
Section 3. Installing Enterprise Application Environment Software.. 3–1<br />
<strong>Installation</strong> Procedure .....................................................................................3–2<br />
COMUS Build Procedure ................................................................................3–3<br />
Registering the Release Tape with COMUS ...............................3–3<br />
Changing Default <strong>Configuration</strong> Parameters ...............................3–3<br />
Building Your Parameter Changes ...............................................3–5<br />
Installing <strong>Runtime</strong> ...........................................................................................3–7<br />
About the <strong>Runtime</strong> Release Tape ................................................3–7<br />
Installing with SOLAR .................................................................3–7<br />
<strong>Installation</strong> Modes <strong>for</strong> Setting Up HUBs ...................................3–10<br />
Installing <strong>Runtime</strong> with XTC .........................................................................3–12<br />
About XTC .................................................................................3–12<br />
About Shared <strong>and</strong> Local Application Groups .............................3–12<br />
Installing <strong>Runtime</strong> into a Shared Application Group ..................3–13<br />
Installing <strong>Runtime</strong> with PAEXEC ..................................................................3–14<br />
Be<strong>for</strong>e Using <strong>Runtime</strong> ..................................................................................3–15<br />
78616323–000 iii
Contents<br />
Starting Your Background Runs ................................................................... 3–18<br />
Reinstalling <strong>Runtime</strong> .................................................................................... 3–19<br />
Installing Additional Copies of <strong>Runtime</strong> ....................................................... 3–21<br />
Installing Host Builder .................................................................................. 3–22<br />
Loading Host Builder from Tape ............................................... 3–23<br />
Configuring <strong>and</strong> Installing Host Builder ..................................... 3–27<br />
Deleting Temporary Files .......................................................... 3–28<br />
Installing Multiple Copies of Host Builder .................................................... 3–29<br />
Installing ROC .............................................................................................. 3–30<br />
Loading ROC from the Release Tape ........................................ 3–30<br />
Configuring <strong>and</strong> Installing ROC ................................................. 3–31<br />
Deleting Temporary Files .......................................................... 3–33<br />
Deinstalling .................................................................................................. 3–34<br />
Deinstalling <strong>Runtime</strong> ................................................................. 3–34<br />
Deinstalling Host Builder .......................................................... 3–34<br />
Section 4. Migrating to Release 3R1A ................................................ 4–1<br />
Migration Procedure ...................................................................................... 4–1<br />
Using LCOPY ............................................................................. 4–2<br />
Generating <strong>OS</strong> <strong>2200</strong> Reports be<strong>for</strong>e Migrating .......................... 4–2<br />
Addressing Migration Issues ......................................................................... 4–4<br />
Environmental Settings ............................................................... 4–4<br />
Relational Database Fast Load support ...................................... 4–4<br />
S_T_N Records in Memory ......................................................... 4–4<br />
Global Setup Data Blocks ........................................................... 4–4<br />
Rounding from Compute Comm<strong>and</strong>s ......................................... 4–5<br />
Extract Format <strong>for</strong> Data Interchange .......................................... 4–5<br />
Localization ................................................................................. 4–6<br />
ROC Per<strong>for</strong>mance Improvement ................................................ 4–9<br />
Graphical Interface Workbench Release 3R2 ........................... 4–10<br />
Generating Your Systems after Migration ................................................... 4–11<br />
Appendix A. Files Created by Enterprise Application Environment .......A–1<br />
Conventions Used in This Appendix ..............................................................A–1<br />
Installing <strong>Runtime</strong> ..........................................................................................A–2<br />
File Names ..................................................................................A–2<br />
RDMS Storage Areas ..................................................................A–2<br />
Using Special Printing Attributes ................................................A–3<br />
Installing Host Builder ....................................................................................A–4<br />
Configuring <strong>and</strong> Generating Systems ............................................................A–5<br />
Output from Configure or Generate ...........................................A–5<br />
Database Files ............................................................................A–6<br />
Appendix B. COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
......................................................................................B–1<br />
COMUS <strong>Configuration</strong> Main Menu ................................................................B–3<br />
General <strong>Configuration</strong> Parameter Screens .....................................................B–4<br />
General <strong>Configuration</strong> Parameter Screen 1 ................................B–4<br />
iv 78616323–000
Contents<br />
General <strong>Configuration</strong> Parameter Screen 2 ................................ B–6<br />
General <strong>Configuration</strong> Parameter Screen 3 ................................ B–8<br />
Processor File Names Screens ................................................................... B–11<br />
Processor File Names Screen 1 ............................................... B–11<br />
Processor File Names Screen 2 ............................................... B–13<br />
Common Bank Attributes Screen ................................................................ B–15<br />
Work Queue Size ..................................................................... B–15<br />
Number of Slots ....................................................................... B–15<br />
Number of Items in the Pool .................................................... B–15<br />
Pool Size ................................................................................... B–15<br />
Maximum Number of Systems ................................................ B–15<br />
Additional I-Language Banks Screen ........................................................... B–17<br />
HUB <strong>Configuration</strong> Parameters Screens ..................................................... B–18<br />
HUB <strong>Configuration</strong> Parameter Screen 1 .................................. B–18<br />
HUB <strong>Configuration</strong> Parameter Screen 2 .................................. B–18<br />
OLTP <strong>Configuration</strong> Parameters Screen ...................................................... B–20<br />
LRSS <strong>Configuration</strong> Parameters Screen ...................................................... B–21<br />
COMUS Run Parameters ............................................................................ B–22<br />
First Build of <strong>OS</strong> <strong>2200</strong> Based Software ................................... B–22<br />
Subsequent Builds of <strong>OS</strong> <strong>2200</strong> Based Software ..................... B–22<br />
Appendix C. Terminal <strong>and</strong> Printer Support ............................................ C–1<br />
Supported Terminal Attributes ....................................................................... C–1<br />
Foreign Terminal Support .............................................................................. C–4<br />
Terminals Supported by Enterprise Application Environment .... C–4<br />
Terminals Not Supported by Enterprise Application Environment<br />
.................................................................................................. C–4<br />
How Enterprise Application Environment Determines Terminal<br />
Types ..................................................................................... C–4<br />
Customizing the Mapping of PTTYP Values ............................... C–7<br />
Inserting Your Own Code to H<strong>and</strong>le Foreign Terminals ............. C–8<br />
IBM 3270 Terminal Support ..................................................... C–10<br />
Appendix D. Related Product In<strong>for</strong>mation .............................................D–1<br />
Glossary<br />
Index<br />
Related Product In<strong>for</strong>mation ......................................................................... D–1<br />
78616323–000 v
Contents<br />
vi 78616323–000
Section 1<br />
Introduction<br />
About This Document<br />
Purpose<br />
Audience<br />
This document provides instructions <strong>for</strong> the installation <strong>and</strong> configuration of <strong>OS</strong> <strong>2200</strong><br />
based Enterprise Application Environment Software.<br />
This document provides step-by-step instructions <strong>for</strong> installing <strong>and</strong> configuring <strong>OS</strong> <strong>2200</strong><br />
<strong>Runtime</strong> <strong>and</strong> Host Builder software at your site.<br />
The primary audience <strong>for</strong> this document consists of those responsible <strong>for</strong> the successful<br />
installation <strong>and</strong> configuration of one or more of the Enterprise Application Environment<br />
products.<br />
The primary audience is presumed to have been trained in installing <strong>and</strong> configuring<br />
<strong>OS</strong> <strong>2200</strong> based Systems, <strong>and</strong> to be familiar with the operational aspects of their<br />
installation.<br />
Notation Conventions<br />
Italics are used to delimit variables; <strong>for</strong> example, system. Enter an actual value in place of<br />
these, as instructed. Square brackets delimit optional values.<br />
Throughout this document, an HVTIP-imposed limit of 262K words is specified. Where<br />
this is mentioned, it refers to UCS.<br />
78616323–000 1–1
Introduction<br />
Windows 2000 Compatibility<br />
Developer software is qualified on Windows 2000 Professional, <strong>and</strong> we see no reason<br />
why Developer will not work on Windows 2000 Server or Advanced Server. Please note<br />
the following requirements:<br />
• <strong>Runtime</strong> <strong>for</strong> Windows Operating Systems <strong>and</strong> Builder Server <strong>for</strong> Windows Operating<br />
Systems require Windows 2000 Server when using the SQL Server database in a<br />
Windows 2000 environment. (This does not affect the ability of SQL Server database<br />
to operate in a Windows NT 4.0 environment.)<br />
• Terminal Server requires Windows 2000 Server.<br />
Unisys e-@ction Br<strong>and</strong>ing<br />
By the end of the year 2000 all Unisys products <strong>and</strong> services will be named or renamed in<br />
the Unisys e-@ction Br<strong>and</strong>ing schema. The purpose of this initiative is to shift the naming<br />
of Unisys products <strong>and</strong> services from component or system level to the solution level.<br />
Accordingly, the LINC range of products will now be known as the Unisys e-@ction<br />
Enterprise Application Environment. The PowerClient range will go under the umbrella of<br />
Unisys e-@ction Graphical Interface Workbench. These names will better reflect the path<br />
that Unisys is taking to serve the needs of enterprise wide application developers.<br />
The tables in the following sections identify all <strong>for</strong>mer products <strong>and</strong> published product<br />
in<strong>for</strong>mation <strong>and</strong> map them to their new names.<br />
Note: The new name <strong>for</strong> MAPPER is Unisys e-@ction Business In<strong>for</strong>mation Server.<br />
1–2 78616323–000
Enterprise Application Environment Products<br />
Unisys e-@ction Enterprise Application<br />
Environment<br />
Unisys e-@ction Enterprise Application<br />
Developer<br />
Unisys e-@ction Enterprise Application<br />
Builder<br />
Products<br />
New Former<br />
LINC<br />
LINC Development<br />
LINC Generate<br />
Enterprise Application Builder <strong>for</strong> <strong>ClearPath</strong> MCP LINC Generate <strong>for</strong> MCP<br />
Enterprise Application Builder <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> LINC Generate <strong>for</strong> <strong>OS</strong> <strong>2200</strong><br />
Enterprise Application Builder <strong>for</strong> the Windows 2000<br />
<strong>and</strong> Windows NT Operating Systems<br />
LINC Generate <strong>for</strong> NT<br />
Enterprise Application Builder <strong>for</strong> HP-UX LINC Generate <strong>for</strong> HP-UX<br />
Enterprise Application Builder <strong>for</strong> DYNIX/ptx LINC Generate <strong>for</strong> Sequent PTX<br />
Introduction<br />
Enterprise Application Builder <strong>for</strong> Sun SPARC Solaris LINC Generate <strong>for</strong> Sun SPARC Solaris<br />
Enterprise Application Builder <strong>for</strong> IBM AIX LINC Generate <strong>for</strong> IBM AIX<br />
Enterprise Application Builder <strong>for</strong> UnixWare LINC Generate <strong>for</strong> SCO UnixWare<br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong><br />
LINC Deployment<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> MCP LINC Deployment <strong>for</strong> MCP<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> LINC Deployment <strong>for</strong> <strong>OS</strong> <strong>2200</strong><br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> the Windows 2000<br />
<strong>and</strong> Windows NT Operating Systems<br />
LINC Deployment <strong>for</strong> NT<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> HP-UX LINC Deployment <strong>for</strong> HP-UX<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> DYNIX/ptx LINC Deployment <strong>for</strong> Sequent PTX<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> Sun SPARC Solaris LINC Deployment <strong>for</strong> Sun SPARC<br />
Solaris<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> IBM AIX LINC Deployment <strong>for</strong> IBM AIX<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> UnixWare LINC Deployment <strong>for</strong> SCO UnixWare<br />
Enterprise Application <strong>Runtime</strong> Test Environment LINC Interpretive Test Environment<br />
Enterprise Application Component Enabler PowerClient ActiveLINC<br />
Enterprise Application Web Enabler PowerClient Web Agent<br />
78616323–000 1–3
Introduction<br />
Graphical Interface Workbench Products<br />
Product<br />
New Former<br />
Unisys e-@ction Graphical Interface Workbench PowerClient<br />
Graphical Interface Developer PowerClient Development<br />
Graphical Interface User PowerClient <strong>Runtime</strong><br />
Graphical Interface Storage Facility PowerClient Central Storage Facility<br />
Enterprise Application Environment Product In<strong>for</strong>mation<br />
Product In<strong>for</strong>mation<br />
New Former<br />
Unisys e-@ction Enterprise Application Ad Hoc<br />
Inquiry <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
Programming Reference H<strong>and</strong>book<br />
Unisys e-@ction Enterprise Application<br />
Programming Reference Manual<br />
Unisys e-@ction Enterprise Application LCOPY<br />
<strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
Component Enabler Developer’s <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
Remote Access <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
Developer <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
Developer User <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
Developer Administration <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
Developer Version Control <strong>Guide</strong><br />
Localization Instructions <strong>for</strong> Unisys e-@ction<br />
Enterprise Application Developer<br />
Unisys e-@ction Enterprise Application<br />
Developer Version Control Key Letter<br />
Unisys e-@ction Enterprise Application Builder<br />
<strong>Guide</strong><br />
LINC Ad Hoc Inquiry Operations <strong>Guide</strong><br />
LINC Programming Reference H<strong>and</strong>book<br />
LINC Programming Reference Manual<br />
LINC Developers <strong>Guide</strong>: LCOPY<br />
PowerClient ActiveLINC Developers <strong>Guide</strong><br />
Remote Access to LINC Server <strong>Guide</strong><br />
LINC Development <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
LINC Development <strong>and</strong> Testing <strong>Guide</strong><br />
LINC Development Administration <strong>Guide</strong><br />
LINC Development Version Control <strong>Guide</strong><br />
Localization Instructions <strong>for</strong> LINC<br />
Development<br />
LINC Development Version Control Key Letter<br />
LINC Generate <strong>Guide</strong><br />
1–4 78616323–000
Unisys e-@ction Enterprise Application Host<br />
Builder <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application Host<br />
Builder Reference Manual: Painter <strong>and</strong> Editor<br />
Unisys e-@ction Enterprise Application Builder<br />
Key Letter<br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> MCP <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> MCP Administration<br />
<strong>Guide</strong><br />
Unisys e-@ction Enterprise Application Getting<br />
Started with <strong>Runtime</strong> <strong>for</strong> the Windows 2000<br />
<strong>and</strong> Windows NT Operating Systems<br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> the Windows 2000 <strong>and</strong> Windows<br />
NT Operating Systems Administration <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> the Windows 2000 <strong>and</strong> Windows<br />
NT Operating Systems Localization<br />
Instructions<br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> the Unix Operating System<br />
Administration <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> HP-UX <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> UnixWare <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> DYNIX/ptx <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> IBM RS/6000 AIX <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> Sun SPARC Solaris <strong>Installation</strong><br />
<strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong><br />
Product In<strong>for</strong>mation<br />
New Former<br />
LINC Generate Operations <strong>Guide</strong><br />
Introduction<br />
LINC Generate Reference Manual: Painter <strong>and</strong><br />
Editor<br />
LINC Generate Key Letter<br />
MCP Based LINC <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
MCP Based LINC Administration <strong>and</strong><br />
Operations <strong>Guide</strong><br />
LINC Deployment <strong>for</strong> Windows NT Getting<br />
Started<br />
LINC Deployment <strong>for</strong> Windows NT<br />
Administration <strong>and</strong> Operations <strong>Guide</strong><br />
Localization Instructions <strong>for</strong> LINC Deployment<br />
<strong>for</strong> Windows NT<br />
LINC Administration <strong>and</strong> Operations <strong>Guide</strong> <strong>for</strong><br />
the Unix Operating System<br />
LINC on HP-UX <strong>Installation</strong> & <strong>Configuration</strong><br />
<strong>Guide</strong><br />
LINC on UnixWare <strong>Installation</strong> & <strong>Configuration</strong><br />
<strong>Guide</strong><br />
LINC on Sequent DYNIX/ptx <strong>Installation</strong> &<br />
<strong>Configuration</strong> <strong>Guide</strong><br />
LINC on IBM RS/6000 AIX <strong>Installation</strong> &<br />
<strong>Configuration</strong> <strong>Guide</strong><br />
LINC on Sun SPARC Solaris <strong>Installation</strong> &<br />
<strong>Configuration</strong> <strong>Guide</strong><br />
78616323–000 1–5
Introduction<br />
Unisys e-@ction Enterprise Application Griffin<br />
Data Engine <strong>Installation</strong> <strong>and</strong> Administration<br />
<strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Installation</strong><br />
<strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration<br />
<strong>Guide</strong><br />
Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> Test Environment <strong>Guide</strong><br />
Windows Operating Systems<br />
In the contents of this manual:<br />
Product In<strong>for</strong>mation<br />
New Former<br />
Griffin Data Engine <strong>Installation</strong> <strong>and</strong><br />
Administration <strong>Guide</strong><br />
<strong>OS</strong> <strong>2200</strong> Based LINC <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
<strong>OS</strong> <strong>2200</strong> Based LINC Administration <strong>and</strong><br />
Operations <strong>Guide</strong><br />
LINC Interpretive Test Environment Operations<br />
<strong>Guide</strong><br />
• The product Unisys e-@ction Enterprise Application Builder <strong>for</strong> the Windows® 2000<br />
<strong>and</strong> Windows NT® Operating Systems will be referred to as Builder <strong>for</strong> Windows<br />
Operating Systems<br />
• The product Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong> the Windows® 2000<br />
<strong>and</strong> Windows NT® Operating Systems will be referred to as <strong>Runtime</strong> <strong>for</strong> Windows<br />
Operating Systems<br />
Please note that no other Windows operating systems, including Windows 95 <strong>and</strong><br />
Windows 98, are supported.<br />
1–6 78616323–000
Section 2<br />
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise<br />
Application Environment Software<br />
About Enterprise Application Environment Software<br />
Enterprise Application Environment Software is supplied on two separate release tapes.<br />
The basic tape contains <strong>Runtime</strong> <strong>and</strong> Report Output Control System (ROC). Host Builder<br />
is supplied on a separate tape.<br />
Throughout this document, release tape is used as a general term. The particular release<br />
tape is implied by the subject matter.<br />
The <strong>OS</strong> <strong>2200</strong> based System Software consists of the following products:<br />
• <strong>Runtime</strong> (m<strong>and</strong>atory)<br />
<strong>Runtime</strong> is the basic product that enables all the other products to run. <strong>Runtime</strong><br />
must be installed be<strong>for</strong>e other Software <strong>for</strong> a release. For a list of the files on this<br />
tape, see “Installing Enterprise Application Environment Software” on page 3–1.<br />
• Host Builder<br />
Host Builder enables you to generate Specifications into Systems. It is itself a System<br />
that must run within <strong>Runtime</strong>. There is no need to install it if you plan to develop<br />
systems on another <strong>OS</strong> <strong>2200</strong> based machine (or another <strong>Runtime</strong> on the same<br />
machine) <strong>and</strong> transfer the runtime versions here.<br />
You can use Host Builder on another host <strong>and</strong> transfer your System to an <strong>OS</strong> <strong>2200</strong><br />
based <strong>Runtime</strong>.<br />
• Report Output Control System (ROC)<br />
ROC is a System that controls the output from Reports. It enables you to browse<br />
Report output online, schedule printing, <strong>and</strong> print to terminal or site printers. It must<br />
be installed after <strong>Runtime</strong>. There can only be one ROC System in a <strong>Runtime</strong>.<br />
Additional In<strong>for</strong>mation<br />
Be<strong>for</strong>e installing system software, read “Be<strong>for</strong>e Installing Your <strong>OS</strong> <strong>2200</strong> Based System”<br />
on page 2–3.<br />
To set up security privileges <strong>for</strong> your System, see your Unisys e-@ction Enterprise<br />
Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
Details about installing Software are in “Installing Enterprise Application Environment<br />
Software” on page 3–1.<br />
78616323–000 2–1
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
For more in<strong>for</strong>mation on developing Systems, see your Unisys e-@ction Enterprise<br />
Application Host Builder <strong>Guide</strong>.<br />
2–2 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
Be<strong>for</strong>e Installing Your <strong>OS</strong> <strong>2200</strong> Based System<br />
This subsection describes the issues you should consider be<strong>for</strong>e installing your <strong>OS</strong> <strong>2200</strong><br />
based System Software.<br />
It covers the following topics:<br />
• Hardware Requirements<br />
• Checklist <strong>for</strong> <strong>OS</strong> <strong>2200</strong> Based System Software<br />
Lists the m<strong>and</strong>atory <strong>and</strong> optional software that you should install as your first<br />
preinstallation task.<br />
• Other Software Considerations<br />
Covers issues you should consider if you use Intersystem Communications (HUB),<br />
UCS Subsystems, or OLTP.<br />
Note: For in<strong>for</strong>mation on changes to system software levels, see PLE 15106301.<br />
78616323–000 2–3
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
Hardware Requirements<br />
The following hardware is necessary to use an <strong>OS</strong> <strong>2200</strong> based System. The size<br />
estimates are exclusive of any other existing software.<br />
Host<br />
To run <strong>Runtime</strong> or Host Builder, you require a <strong>2200</strong> Series machine (specifically a <strong>2200</strong>/<br />
300, <strong>2200</strong>/500, <strong>2200</strong>/700, or <strong>2200</strong>/900) or a <strong>ClearPath</strong> IX machine.<br />
Memory<br />
To run Host Builder as well as your own Systems, nine to eleven million words of memory<br />
are required, with three to four million words reserved <strong>for</strong> TIP memory. TIP memory is<br />
dynamic <strong>and</strong> does not need to be configured.<br />
These memory requirements do not allow <strong>for</strong> other external Systems or other<br />
development activity.<br />
Disk Storage<br />
The basic <strong>Runtime</strong> requires a minimum of 3,000 tracks of disk storage. If you use ROC,<br />
you should increase this to a minimum of 10,000 tracks. Host Builder needs<br />
approximately 100,000 tracks when it is initially installed.<br />
Note: The disk storage figure <strong>for</strong> Host Builder assumes that you have selected the<br />
Override REM Pack Initial Reserve field when configuring your Host Builder. For<br />
more details about this option, see your Unisys e-@ction Enterprise Application <strong>Runtime</strong><br />
<strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
Terminals Supported<br />
This release supports any of the following terminal types:<br />
UTS 20 UTS 20L UTS 20R<br />
UTS 30 UTS 40 UTS 60<br />
UTS 60I SVT 1120 SVT 1121<br />
LT300 DS7 IBM 3270 group of<br />
terminals<br />
SNA3270 logical<br />
terminals<br />
PCs with UTS terminal<br />
emulation software<br />
Note: Enterprise Application Environment supports the LT300 terminal, operating in<br />
SVT1121-compatible mode. The LT300 is an internationalized terminal with multiple<br />
character set capabilities, <strong>and</strong> it supports many of the ISO 8859 8-bit character sets.<br />
The LT300 terminal type is recognized by the :STN colon comm<strong>and</strong>, <strong>and</strong> is a valid value <strong>for</strong><br />
the GLB.STYLE System Data item.<br />
2–4 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
CMS <strong>and</strong> MCB recognize the LT300 as a supported terminal type, <strong>and</strong> identify the Coded<br />
Character Set (CCS) <strong>for</strong> each message from the LT300. The Coded Character Set is a oneto-one<br />
mapping of characters in a character set to their internal binary representation.<br />
Enterprise Application Environment stores the CCS identifier (CCS ID) <strong>for</strong> the input<br />
message in the GLB.CCS System Data item.<br />
Other Peripherals<br />
You will require a line printer <strong>and</strong> tape drive.<br />
78616323–000 2–5
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
Checklist <strong>for</strong> <strong>OS</strong> <strong>2200</strong> Based System Software<br />
This subsection details the m<strong>and</strong>atory <strong>and</strong> optional <strong>OS</strong> <strong>2200</strong> based System software,<br />
release SB8 (CP IX 4.1 or higher). You should install this software as your first<br />
preinstallation task. For system software installation details, see “Installing <strong>and</strong><br />
Configuring Required <strong>OS</strong> <strong>2200</strong> System Software” on page 2–11.<br />
M<strong>and</strong>atory System Software<br />
The following system software is m<strong>and</strong>atory:<br />
• EXEC<br />
Enterprise Application Environment supports MHTIP <strong>and</strong> PAEXEC shared/partitioned<br />
applications (<strong>and</strong> local applications).<br />
• TIP Utilities<br />
• CMS1100<br />
• UDS control (UDSC)<br />
• UREP <strong>and</strong> RDMS<br />
An <strong>OS</strong> <strong>2200</strong> based System requires only the UREP <strong>and</strong> RDMS subproducts. These<br />
are provided under UDS, but also operate with the full UREP <strong>and</strong> RDMS products.<br />
(Due to the use of FastPath, the RDMS STATISTICS option is not supported.)<br />
• IRU<br />
• MCB<br />
• SOLAR<br />
• ACOB<br />
– You must install the full ACOB Compiler <strong>and</strong> the C$DML ACOB Common Bank.<br />
– The ACOB compiler must be installed as non-flagging.<br />
– The Field data DML Common Banked library must not be used.<br />
If you require the Field data DML Common Banked library <strong>for</strong> existing external<br />
Systems, you must install a second, alternative ACOB Compiler. See your<br />
<strong>OS</strong> <strong>2200</strong> ASCII COBOL <strong>Installation</strong> <strong>Guide</strong> <strong>for</strong> in<strong>for</strong>mation on installing alternative<br />
Compilers.<br />
– As part of the <strong>2200</strong>/500 product deliverables, you will receive the ASCII COBOL<br />
compiler. This compiler must be installed.<br />
Caution<br />
Unless the ASCII COBOL compiler has been licensed, no other use <strong>for</strong> this<br />
compiler is authorized. In this context, other use includes compilation or<br />
execution of user-written externally generated programs.<br />
2–6 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
• UCOB<br />
• MAP<br />
• PCI<strong>OS</strong><br />
• SORT<br />
• LINK<br />
• LSS<br />
• URTS<br />
• Extended Language Message System (ELMS)<br />
Optional System Software<br />
Check the following table to decide if you need to install the optional system software.<br />
System Software Install This Software If You …<br />
COMUS Are making changes to the default configuration.<br />
MAPPER Use a Mapper interface (you need MRI <strong>for</strong> mapper access to<br />
<strong>OS</strong> <strong>2200</strong> Databases). You will need MRI <strong>and</strong>/or IPFSQL (see<br />
below).<br />
MRI Use a Mapper interface (you need MAPPER to process Report<br />
Extract files in Mapper).<br />
IPFSQL Use a NOF interface.<br />
DDP-PPC Use HUB. DDP-PPC is an optional product used with external<br />
<strong>and</strong> interhost Automatic Entries, which use the HUB<br />
mechanism. See “Considerations <strong>for</strong> Intersystem<br />
Communications” under “Other Software Considerations” on<br />
page 2–9.<br />
PADS Use UCS applications (recommended).<br />
OLTP-TM<strong>2200</strong> Use OLTP.<br />
OLTP-2PC Use OLTP 2PC.<br />
<strong>OS</strong>I-TP Use OLTP multi-host capability.<br />
UC Use OLTP UCS server systems.<br />
Relational<br />
Database Fast<br />
Load<br />
Requirements <strong>for</strong> the <strong>Runtime</strong> <strong>Configuration</strong> Process<br />
When you start to configure <strong>Runtime</strong>, you will be asked to supply replies to requests<br />
made by the configuration process. You need the following. (Full descriptions of these<br />
items are supplied later in this section.)<br />
• Release tape<br />
Use the off line utility <strong>for</strong> database reorganisation, or Fast Load<br />
Reports.<br />
78616323–000 2–7
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
• COMUS Database (you need to create one COMUS database if you are making<br />
changes to the default configuration)<br />
• <strong>Configuration</strong> parameters<br />
You may find that you can accept most of the default parameters <strong>for</strong> the configuration<br />
(especially if you are a new site). However, you may have established naming<br />
conventions <strong>for</strong> jobs <strong>and</strong> files <strong>and</strong> numbering systems <strong>for</strong> your BDIs, <strong>and</strong> so you will need<br />
to change the parameters.<br />
The complete parameter set is given in “COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong><br />
Parameters” on page B–1. You should review this appendix, to make sure that you are<br />
aware of the in<strong>for</strong>mation you require <strong>for</strong> the configuration process.<br />
Requirements <strong>for</strong> <strong>Runtime</strong><br />
To enable use of comm<strong>and</strong>s to control the Background Run <strong>and</strong> HUB Background Run,<br />
the userid <strong>for</strong> each background run must have SSCONSOLE privilege.<br />
For details of these comm<strong>and</strong>s, see your Unisys e-@ction Enterprise Application <strong>Runtime</strong><br />
<strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
Requirements <strong>for</strong> ROC<br />
To install the Report Output Control System (ROC), you need:<br />
• An installed <strong>Runtime</strong><br />
• <strong>Runtime</strong> tape<br />
• Names used in the <strong>Runtime</strong> configuration<br />
– System name <strong>for</strong> your ROC System<br />
– Database name <strong>for</strong> your ROC System<br />
• VALTAB entry <strong>for</strong> ROC, containing the following in<strong>for</strong>mation:<br />
– ROC Spooler transaction Id<br />
– TIP transaction number<br />
– Application group number<br />
– QPRIORITY node with a QMAX of zero <strong>for</strong> the ROC spooler transaction id<br />
You may want to use Freespace files <strong>for</strong> ROC output, which can give per<strong>for</strong>mance<br />
benefits in a high-volume printing environment. This involves an Exec configuration<br />
parameter, creating a TIP Freespace control file (FS$SYS) <strong>for</strong> ROC, <strong>and</strong> the use of a<br />
TEMP$SGS parameter <strong>for</strong> ROC.<br />
For more details, see “Configuring <strong>and</strong> Regenerating Your EXEC” on page 2–11 <strong>and</strong><br />
“Installing ROC” on page 3–30.<br />
Requirements <strong>for</strong> the Host Builder<br />
To install multiple copies of Host Builder under your <strong>Runtime</strong>, you require:<br />
2–8 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
• Release tape<br />
• Unique System name <strong>for</strong> each copy of Host Builder<br />
• Unique Database name <strong>for</strong> each copy of Host Builder<br />
• HVTIP Library Number <strong>and</strong> TIP Transaction Number<br />
There are various configuration options to consider when loading the Host Builder. These<br />
are target host templates, reserved word lists, automatic edit resequencing, <strong>and</strong> change<br />
<strong>and</strong> resource locking. For more details, see “Installing Host Builder” on page A–4 in<br />
“Installing Enterprise Application Environment Software” on page 3–1.<br />
Other Software Considerations<br />
Considerations <strong>for</strong> Intersystem Communications<br />
The external Automatic Entry (HUB) facility provides an easy-to-use method of<br />
communication between Systems, which can be on the same host, or on different hosts.<br />
The following table describes the software requirements <strong>for</strong> HUBs, depending on the<br />
facilities that you want to use.<br />
Facility Used<br />
No external Automatic<br />
Entries <strong>and</strong> no ROC<br />
Active HUB<br />
Background Run<br />
Note: The Report Output Control System (ROC) uses external Automatic Entries to<br />
communicate header in<strong>for</strong>mation.<br />
For details of this installation, see “<strong>Installation</strong> Modes <strong>for</strong> Setting Up HUBs” on<br />
page 3–10.<br />
Considerations When Using UCS Subsystems<br />
HUB$SGS element<br />
with LOCALH<strong>OS</strong>T<br />
<strong>and</strong> Remote Host<br />
SGSs<br />
Configured HUB<br />
<strong>for</strong> <strong>Runtime</strong><br />
No No Yes<br />
ROC Yes No Yes<br />
External Automatic<br />
Entries in same<br />
<strong>Runtime</strong><br />
External Automatic<br />
Entries on same host<br />
Interhost external<br />
Automatic Entries<br />
Yes No Yes<br />
Yes No Yes<br />
Yes Yes Yes<br />
If you envisage having very large Ispec transactions in your System, you may want to<br />
consider setting up your System as a UCS Subsystem. The mechanism involves setting<br />
parameters, <strong>and</strong> is discussed in your Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong><br />
78616323–000 2–9
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>. However, at the installation stage of <strong>Runtime</strong>,<br />
you have to consider user privileges, because your <strong>Runtime</strong> must be installed under a<br />
USER-ID with security attributes that allow the loading of UCS Subsystems.<br />
Note: UCS Subsystems are supported only on M Series hosts with memory paging<br />
facilities.<br />
Considerations When Using OLTP<br />
Systems may use the Open/OLTP software <strong>for</strong> the external Automatic Entry facility,<br />
providing distributed transaction processing across different types of machines <strong>and</strong><br />
networks.<br />
For details on configuration issues, see your Unisys e-@ction Enterprise Application Host<br />
Builder <strong>Guide</strong>.<br />
2–10 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
Installing <strong>and</strong> Configuring Required <strong>OS</strong> <strong>2200</strong><br />
System Software<br />
For the latest in<strong>for</strong>mation on configuring <strong>and</strong> installing required system software, see the<br />
Support web page at http://www.support.unisys.com/.<br />
Be<strong>for</strong>e you commence installing <strong>and</strong> configuring any <strong>OS</strong> <strong>2200</strong> based System software, it<br />
is important that you per<strong>for</strong>m the following tasks where necessary:<br />
1. Configure your EXEC <strong>for</strong> the Software, <strong>and</strong> regenerate if necessary.<br />
2. Configure CMS 1100 <strong>and</strong> MCB to facilitate the Software.<br />
3. Configure UDS software.<br />
4. Apply any necessary system software changes.<br />
These tasks are described in the following subsections.<br />
Configuring <strong>and</strong> Regenerating Your EXEC<br />
Configuring EXEC: Deciding on Application Groups<br />
You must decide which application group or groups your Enterprise Application<br />
Environment Systems will run in. Consider the following points:<br />
• If your Systems are to run in different application groups, install <strong>Runtime</strong> into each<br />
application group.<br />
• The default application group <strong>for</strong> <strong>Runtime</strong> is UDSSRC, with an application number of<br />
3.<br />
• For in<strong>for</strong>mation on establishing application groups, see your <strong>OS</strong> <strong>2200</strong> UDS <strong>Installation</strong><br />
<strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong>.<br />
• To interface with other (including external) Systems, you should install these systems<br />
into the same application group. If you need some guidelines on deciding whether to<br />
place systems in different application groups, see your <strong>OS</strong> <strong>2200</strong> Integrated Recovery<br />
System, Concepts <strong>and</strong> Facilities Manual.<br />
If you intend to interface with external database systems that are under the control of<br />
UDS, your System must be in the same application group as the external System. If<br />
you want to interface to a DMS 1100 system, that system must be in the same<br />
application group under the control of UDS, not DMS 8.<br />
• You may decide to install more than one <strong>Runtime</strong> in an application group (especially<br />
helpful <strong>for</strong> testing).<br />
• If you wish to run <strong>Runtime</strong> in more than one application group, the following products<br />
must be either configured or installed <strong>for</strong> each of these application groups:<br />
– EXEC (to configure extra application groups)<br />
– IRU<br />
– CMS (Application configure statements)<br />
78616323–000 2–11
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
– TELCON (XEU <strong>and</strong> DESTSSU statements)<br />
– MCB<br />
– UDS Control (UDSC)<br />
– RDMS (subproduct)<br />
– RSA<br />
– UREP (subproduct)<br />
Configuring EXEC: Creating Application Groups<br />
You may need to regenerate your EXEC to create an application group in which to run<br />
Enterprise Application Environment. If you have a General Purpose Tailored EXEC (GPTE),<br />
an application group already exists. For <strong>2200</strong>/400 sites with GPTE, the application group<br />
number is 3.<br />
If you do not have an application group, the EXEC must be generated with the appropriate<br />
STEP control <strong>and</strong> AUDIT control SGSs to define the required application group. For more<br />
in<strong>for</strong>mation <strong>and</strong> examples, see your <strong>OS</strong> <strong>2200</strong> EXEC <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong>.<br />
Queue Items<br />
The number of Queue Items allocated <strong>for</strong> the Application defaults to 250. Since each<br />
active message requires a queue item, this limit may be exceeded, particularly when a<br />
large number of MESSAGE; requests are being delivered by the Background run. It is<br />
recommended that you increase the number of queue items (<strong>for</strong> example, to 1000) using<br />
the STEPCONTROL QNBR parameter. This will prevent the application running out of<br />
queue items.<br />
You should use a different QPRIORITY node <strong>for</strong> your Error Notification Program, <strong>and</strong><br />
different ones <strong>for</strong> each System or group of Systems.<br />
The STEPCONTROL statement must contain at least one PRIORITY, n, 0 statement,<br />
where n is the QPRIORITY value. This QPRIORITY value is used when configuring the<br />
dummy transaction <strong>for</strong> ROC. A separate PRIORITY statement is required <strong>for</strong> each of the<br />
GLI, NOF, or OFFLINE interfaces that you intend to use.<br />
Using a TIP File to Hold Terminal Records<br />
If you intend to use an FCSS TIP file to hold your terminal records instead of an RDMS<br />
table, <strong>and</strong> the file is RECOVERABLE, you must include ROLLBACK SGS statements.<br />
Note: If you require the Rollback Page file, it must also be created <strong>and</strong> registered with<br />
TIP. For more details, see your <strong>OS</strong> <strong>2200</strong> EXEC <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong>.<br />
If you install a UCS System, <strong>and</strong> you intend to use an FCSS TIP file to hold your terminal<br />
records instead of an RDMS table, you must ensure that you have the UCS TIP Primitives<br />
installed. For details about generating TIP with the required options, see the <strong>OS</strong> <strong>2200</strong><br />
Transaction Processing <strong>Installation</strong> <strong>Guide</strong>.<br />
2–12 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
For more details about using the FCSS TIP file, see your Unisys e-@ction Enterprise<br />
Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
The required SGS statements are as follows.<br />
<br />
The a value is the Application group number, <strong>and</strong> n is the TIP file number of the Rollback<br />
Page file, which is used <strong>for</strong> quick-look storage when FCSS TIP files are updated.<br />
<br />
This statement specifies the name of your Rollback Page file.<br />
<br />
<br />
For details about how to calculate the number of words per page (n2), the number of<br />
memory pages (n3), <strong>and</strong> the number of file pages (n4), see your <strong>OS</strong> <strong>2200</strong> EXEC<br />
<strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong>.<br />
Calculating Page Size<br />
To assist in the calculation of page size, the following table shows how the size of<br />
GLB.WORK affects the terminal record size. The page size must be big enough to contain<br />
at least one terminal record. The size of GLB.WORK is defined on the Primary Database<br />
Options screen, <strong>and</strong> its default is 128.<br />
Size of GLB.WORK<br />
(characters)<br />
<br />
<br />
<br />
<br />
For full details of these parameters, see your <strong>OS</strong> <strong>2200</strong> EXEC System Software<br />
Operations Reference Manual.<br />
The following example shows statements <strong>for</strong> setting up a Rollback Page file.<br />
<br />
<br />
<br />
Size of Terminal Records<br />
(Words)<br />
Up to 132 56<br />
Up to 356 112<br />
Up to 804 224<br />
Up to 1700 448<br />
Up to 3492 896<br />
Greater than 3492 1792<br />
78616323–000 2–13
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
<br />
<br />
<br />
<br />
<br />
The STNUTIL program (used in conjunction with defining FCSS TIP Files) commits every<br />
20 records. You should consider this when calculating the STEPCONTROL ROLLBACK<br />
WORDS PER PAGE value <strong>and</strong> PAGES PER TRANSACTION ROLLBACK LIMIT based on<br />
the size of terminal records. This means that if the ROLLBACK PAGE FILE is defined as in<br />
the example in the previous step <strong>and</strong> the size of GLB.WORK exceeds 804 (characters)<br />
<strong>and</strong> there are more than 20 records to process, then errors will occur.<br />
This is based on 896 (words per page) divided by 448 (terminal record size) multiplied by<br />
10 (pages per transaction rollback limit), giving a result of 20 records.<br />
In this example, the error would be avoided if the pages per transaction rollback limit was<br />
increased by 1 to 11. An error has been found on the twentieth record as the Rollback<br />
page size has its own header in<strong>for</strong>mation, <strong>for</strong>cing the twentieth record into the eleventh<br />
page.<br />
Configuring EXEC: EXPRGENVIRON <strong>Configuration</strong> Parameter<br />
If you are using Host Builder or generating a UCS System, you must set the EXEC<br />
configuration parameter EXPRGENVIRON to TRUE (the default).<br />
Configuring EXEC: Parameters <strong>for</strong> HVTIP<br />
Ensure HVTIP is turned on. You may need to per<strong>for</strong>m a NEWCON EXEC generate.<br />
Recommended configuration parameters <strong>for</strong> HVTIP are listed in the following table.<br />
Note: For SB6 <strong>and</strong> above, TIP memory is dynamic <strong>and</strong> does not need to be configured.<br />
Parameter Recommended Value Meaning<br />
HVTIP 64 Number of HVTIP libraries<br />
TMECRL TRUE Turn on TIP memory control<br />
TPMEMX 31250 Maximum number of TIP memory blocks of<br />
64 words (see below)<br />
TPNRTN 7 Maximum number of nested RTN$s allowed<br />
For larger systems, TPMEMX will need to be greater than the value listed in this table.<br />
The recommended value is 31,250 blocks of 64 words, giving a total memory allocation of<br />
2 million words.<br />
For more in<strong>for</strong>mation on HVTIP Memory Allocation, see your Unisys e-@ction Enterprise<br />
Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
For more details about TIP configuration, see your <strong>OS</strong> <strong>2200</strong> EXEC <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong>.<br />
2–14 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
Configuring EXEC: Non-<strong>OS</strong><strong>2200</strong> Tapes <strong>for</strong> LCOPY<br />
To enable LCOPY to read tapes created on non-<strong>OS</strong> <strong>2200</strong> hosts, set the following EXEC<br />
configuration TAG:<br />
<br />
This parameter can be changed dynamically. For more details, see your <strong>OS</strong> <strong>2200</strong> EXEC<br />
<strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> <strong>Guide</strong>.<br />
Configuring EXEC: Freespace Files<br />
To enable the use of Freespace files, set the FREESPACE configuration parameter to<br />
TRUE. (This is applicable to ROC flat files only. For more details, see “Installing ROC” on<br />
page 3–30.)<br />
Configuring EXEC: Large Files<br />
If you want to take advantage of the Large Files option (maximum 262,143 positions),<br />
set LARGEFILES to TRUE in your EXEC configuration. If you set LARGEFILES to FALSE<br />
(the default) your files are limited to 4095 positions.<br />
For details on enabling the feature, see your Unisys e-@ction Enterprise Application<br />
<strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
CMS 1100 <strong>and</strong> MCB <strong>Configuration</strong><br />
To configure CMS 1100 <strong>and</strong> MCB <strong>for</strong> Enterprise Application Environment:<br />
1. If you do not already have MCB (Message Control Bank) installed, install <strong>and</strong><br />
configure it <strong>for</strong> recoverable messages.<br />
You must install MCB with the Extended Mode options set if either of the following<br />
conditions apply.<br />
• Your Systems are to be generated as UCS.<br />
• You are using Host Builder.<br />
For more details, see your <strong>OS</strong> <strong>2200</strong> MCB <strong>Installation</strong> <strong>Guide</strong>.<br />
2. Define the terminals that you intend to use <strong>for</strong> your Systems to CMS 1100 as TIP<br />
terminals in a PID configuration statement.<br />
3. Ensure your MCB has a User Parameter Area of 32 words or less.<br />
4. Set the UDBASE MCB configuration parameter to the default specified in your MCB<br />
System Support Reference Manual. (If UDBASE is set lower than the default, it is<br />
possible that the MCB DBANK will overlap with the DBANK.)<br />
You can modify the start address of the DBANK. For details, see your Unisys e-@ction<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
78616323–000 2–15
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
Trigger Characters<br />
You can use MCB <strong>and</strong> CMS Trigger characters. However, since Enterprise Application<br />
Environment already uses the tilde (~) character <strong>for</strong> internal use, you should not use it as<br />
the trigger character <strong>for</strong> a System.<br />
UDS Software <strong>Configuration</strong><br />
You must ensure that the MCB BDI <strong>and</strong> entry-point (as defined when you installed MCB)<br />
are set in the UDS configuration. If incorrect values are set in the UDS configuration,<br />
transactions may fail with MCB error 013 on function 2 (initialize).<br />
When configuring your UDS software you must:<br />
1. Set the UDS thread control bank to the maximum. If necessary, increase its size by<br />
entering the following sequence of comm<strong>and</strong>s in a Data Dictionary session.<br />
<br />
<br />
<br />
<br />
The thread bank size may be changed while your Systems are active, but be<strong>for</strong>e<br />
these changes will take effect, all threads must be stopped. The first thread that<br />
restarts must not be a TIP thread.<br />
Set your UDS DCS banks to their maximum size to prevent queuing. For more details,<br />
see the <strong>OS</strong> <strong>2200</strong> UDS <strong>Installation</strong> <strong>Guide</strong>.<br />
2. To increase the size of your UDS DCS bank, enter the following sequence of<br />
comm<strong>and</strong>s in a Data Dictionary session.<br />
<br />
<br />
<br />
<br />
The bank size may be changed while Enterprise Application Environment is active,<br />
but the changes will not take effect until a BEGIN THREAD is encountered after UDS<br />
has been idle; that is, when it has no active threads. For more details about the DCS-<br />
BANK-SIZE parameter, see the <strong>OS</strong> <strong>2200</strong> UDS <strong>Installation</strong> <strong>Guide</strong>.<br />
3. If your site has the Data Dictionary subproduct <strong>and</strong> not the full product, you must<br />
enter the following comm<strong>and</strong>s be<strong>for</strong>e installing.<br />
<br />
<br />
<br />
To determine if you are using the Data Dictionary subproduct, attempt to define an<br />
entity by entering:<br />
<br />
<br />
If you have only the subproduct, an error message is returned. If you have the full<br />
product, delete the entity by entering:<br />
<br />
<br />
2–16 78616323–000
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
Applying System Software Changes<br />
Some changes must be applied to other <strong>OS</strong> <strong>2200</strong> based system software be<strong>for</strong>e<br />
installing your Enterprise Application Environment Software. For the latest details, see<br />
your release in<strong>for</strong>mation at http://www.support.unisys.com/.<br />
These changes are supplied on the <strong>Runtime</strong> Release tape. They are contained in an<br />
element CHANGES/SBlevel in the first file, where SBlevel is the level of SB software that<br />
you are currently running (<strong>for</strong> example, SB5R4).<br />
The following runstream copies the first file down to a disk file called file.<br />
<br />
<br />
<br />
Here reel# is the tape reel number <strong>and</strong> tape is a device that supports the release <strong>for</strong>mat<br />
(<strong>for</strong> example, U9S or HICL).<br />
You will need to build <strong>and</strong> install those products <strong>for</strong> which there are changes.<br />
Use the following ECL to load the changes into the COMUS Database, where qualifier is a<br />
COMUS qualifier, file is a file name, <strong>and</strong> element the element name.<br />
<br />
<br />
<br />
78616323–000 2–17
Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application Environment Software<br />
2–18 78616323–000
Section 3<br />
Installing Enterprise Application<br />
Environment Software<br />
This section covers the following topics:<br />
• <strong>Installation</strong> Procedure<br />
• COMUS Build Procedure<br />
• Installing <strong>Runtime</strong><br />
• Installing <strong>Runtime</strong> with XTC<br />
• Installing <strong>Runtime</strong> with PAEXEC<br />
• Be<strong>for</strong>e Using <strong>Runtime</strong><br />
• Starting Your Background Runs<br />
• Reinstalling <strong>Runtime</strong><br />
• Installing Additional Copies of <strong>Runtime</strong><br />
• Installing Host Builder<br />
• Installing ROC<br />
• Deinstalling<br />
Related In<strong>for</strong>mation<br />
For in<strong>for</strong>mation on:<br />
• Migrating from previous releases, see “Migrating to Release 3R1A” on page 4–1.<br />
• Removing installed software, see “Deinstalling” on page 3–34.<br />
• COMUS parameters <strong>for</strong> installing <strong>and</strong> configuring <strong>and</strong> SOLAR <strong>Installation</strong> parameters,<br />
see “COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters” on page B–1.<br />
Be<strong>for</strong>e Installing<br />
Be<strong>for</strong>e installing, you must make sure both the Application Group <strong>and</strong> the MCB are in the<br />
UP state. If Enterprise Application Environment is configured to use OLTP, the OLTP<br />
TMSC background run must also be in the UP state.<br />
78616323–000 3–1
Installing Enterprise Application Environment Software<br />
<strong>Installation</strong> Procedure<br />
<strong>Runtime</strong> is the basic product that enables all other Enterprise Application Software to run.<br />
It must be the first product you install.<br />
If you wish to change the default configuration parameters, you must use COMUS to<br />
per<strong>for</strong>m a configure <strong>and</strong> build be<strong>for</strong>e you install with SOLAR. If you have not previously<br />
used COMUS to configure or build, you first need to initialize a COMUS Database. For<br />
more details, see your <strong>OS</strong> <strong>2200</strong> COMUS End Use Reference Manual.<br />
When you install your <strong>OS</strong> <strong>2200</strong> based <strong>Runtime</strong> using SOLAR, you per<strong>for</strong>m the following<br />
steps. (Each of these steps is described in more detail in the following subsections.)<br />
1. If you want to customize Enterprise Application Environment <strong>for</strong> your site <strong>and</strong> change<br />
the default configuration parameters, you should:<br />
• Register the Release tape with COMUS.<br />
• Change the default configuration parameter settings. Full details of the default<br />
parameters can be found in “COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong><br />
Parameters” on page B–1.<br />
• Build <strong>Runtime</strong> with COMUS.<br />
If you do not change the default parameters, use SOLAR to register <strong>and</strong> install<br />
<strong>Runtime</strong> directly from the Release tape.<br />
For details, see “COMUS Build Procedure” on page 3–3.<br />
2. Register the output tape from the build process with SOLAR.<br />
3. Install <strong>Runtime</strong>, by using SOLAR.<br />
Installing Unisys-Supplied Changes<br />
Unisys supplies changes by distributing EIFs (Engineering Interim Fixes). These changes<br />
can affect:<br />
• <strong>Runtime</strong><br />
• Any Enterprise Application Environment component, including the Report Output<br />
Control System (ROC) <strong>and</strong> Host Builder<br />
To install an EIF, see the instructions accompanying the EIF.<br />
To install changes to <strong>Runtime</strong> Software, <strong>for</strong> each copy of your <strong>Runtime</strong>:<br />
1. Insert any Unisys-supplied source changes into the COMUS Database.<br />
2. Repeat the build <strong>and</strong> install process, merging the changes into the product at the<br />
Build stages.<br />
For more details about this process, see your <strong>OS</strong> <strong>2200</strong> COMUS End Use Reference<br />
Manual.<br />
3–2 78616323–000
COMUS Build Procedure<br />
Installing Enterprise Application Environment Software<br />
Use the procedures described in this subsection to customize the installation of<br />
Enterprise Application Software <strong>for</strong> your site.<br />
Registering the Release Tape with COMUS<br />
To register an <strong>OS</strong> <strong>2200</strong> based System with COMUS, per<strong>for</strong>m the following steps:<br />
1. Log on to DEMAND.<br />
2. Specify the COMUS qualifier, by entering:<br />
<br />
The qualifier value is that specified when the COMUS database was created.<br />
3. Initiate COMUS, by entering:<br />
<br />
4. Register with COMUS, by entering:<br />
<br />
The reelnum value is the tape identifier of the Release tape. The Release tape is<br />
unlabeled, <strong>and</strong> the default tape characteristics are assumed.<br />
COMUS assigns the tape, <strong>and</strong> waits <strong>for</strong> you to mount it.<br />
When COMUS completes the registration task, it displays the following message:<br />
<br />
To check the result of the register process, look at the print files produced under the runid<br />
that initiated the register. These print files contain in<strong>for</strong>mation specific to this release,<br />
including (in the case of an Interim release) the details of all Engineering Interim Fixes<br />
(EIFs) patched by this release.<br />
Changing Default <strong>Configuration</strong> Parameters<br />
If you do not want to change the default parameter setting, proceed to “Installing<br />
<strong>Runtime</strong>” on page 3–7. For more details about the default parameters, see “COMUS<br />
<strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters” on page B–1.<br />
If you want to change some of these parameters, you must per<strong>for</strong>m both the Configure<br />
<strong>and</strong> Build stages.<br />
To change the <strong>Configuration</strong> parameters <strong>for</strong> your site, per<strong>for</strong>m the following steps:<br />
1. To update the configuration parameters <strong>for</strong> the <strong>Runtime</strong>, start the configuration<br />
process by entering the following comm<strong>and</strong>:<br />
78616323–000 3–3
Installing Enterprise Application Environment Software<br />
<br />
A list of the available <strong>Configuration</strong> Sets is displayed. A <strong>Configuration</strong> Set is a release<br />
of a product or a group of products or subproducts which are installed together. There<br />
may be more than one <strong>Configuration</strong> Set <strong>for</strong> a product. For example, if you wish to<br />
install in more than one application group, you need to create a <strong>Configuration</strong> Set <strong>for</strong><br />
each application group.<br />
If your COMUS Database has not been used be<strong>for</strong>e, a message is displayed<br />
indicating that no <strong>Configuration</strong> Sets exist.<br />
2. After you have registered, you must create a <strong>Configuration</strong> Set.<br />
To create a <strong>Configuration</strong> Set, enter the following COPY comm<strong>and</strong>:<br />
<br />
The runtime value gives the <strong>Runtime</strong> name to be used in the BUILD.<br />
3. Following the COPY comm<strong>and</strong>, COMUS redisplays the <strong>Configuration</strong> Set Selection<br />
screen.<br />
Enter the number associated with the set you have just created, <strong>and</strong> transmit.<br />
4. A Product Selection screen is then displayed. This screen is used by <strong>Configuration</strong><br />
sets containing more than one product.<br />
The display is:<br />
<br />
<br />
5. Enter 1 to select LINC 3R1.<br />
This displays the <strong>Configuration</strong> Process Main Menu screen. Throughout the<br />
configuration process, you may obtain help in<strong>for</strong>mation by typing a question mark<br />
character (?) either in the top left-h<strong>and</strong> corner to obtain general in<strong>for</strong>mation about the<br />
whole screen, or in column 1 of a field position to obtain in<strong>for</strong>mation about that field.<br />
The Main menu has the following seven options, each of which displays additional<br />
screens:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
6. To display the current values <strong>for</strong> any of the above groups of parameters, enter the<br />
associated number from the Main Menu. To change a parameter, overtype its existing<br />
value on the particular parameter screen.<br />
Some of the parameters <strong>for</strong> these options are spread over more than one screen. If<br />
so, enter a plus sign (+) to display the next screen in the sequence, or enter a minus<br />
sign (-) to display the previous screen.<br />
7. When you have made all your changes to a particular screen, transmit to effect the<br />
changes. Enter BACK to return to the Main Menu to select another group of<br />
parameters.<br />
3–4 78616323–000
Installing Enterprise Application Environment Software<br />
8. When you are satisfied with all your changes, enter PROCESS, <strong>and</strong> transmit. You can<br />
enter this comm<strong>and</strong> from any screen.<br />
To discard the changes you have made, enter the OMIT. The Main Menu is displayed.<br />
9. Enter END (or E) to terminate the configure process.<br />
If the configure process was unsuccessful, an error message is displayed.<br />
10. To terminate the current COMUS session, enter the EXIT comm<strong>and</strong>.<br />
Building Your Parameter Changes<br />
This task is required only if you have changed any of the defaDult settings <strong>for</strong> the<br />
configuration parameters. To build <strong>Runtime</strong>, per<strong>for</strong>m the following actions:<br />
1. Start the Build process, by entering the following comm<strong>and</strong> during a COMUS<br />
session:<br />
<br />
2. The first time you build <strong>Runtime</strong>, COMUS asks <strong>for</strong> some default parameters. Enter<br />
your required values, or accept the defaults. For more details, see the <strong>OS</strong> <strong>2200</strong> End<br />
Use Reference Manual.<br />
A set of suggested values <strong>for</strong> your first build is shown in the following table. For the<br />
full set of parameters, including those required <strong>for</strong> subsequent builds, see “COMUS<br />
<strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters” on page B–1.<br />
Item Suggested Value or Action<br />
<strong>Runtime</strong> name Enter the <strong>Runtime</strong> name you specified when configuring your<br />
software<br />
Project Id LINCBUILD<br />
Runid BLINC<br />
Run Options Transmit a space<br />
Run priority Transmit a space<br />
Tape equipment For example, U9S or HICL<br />
Tape assign option TJ <strong>for</strong> unlabeled<br />
Generation type TAPE/TAPE<br />
permanent SGSs Transmit a space<br />
Maximum 9999<br />
Maximum pages 99999<br />
3. During the Build process, the following prompt message is displayed:<br />
78616323–000 3–5
Installing Enterprise Application Environment Software<br />
<br />
Enter the name of the <strong>Runtime</strong> you wish to build or, if you are accepting all the<br />
configuration defaults, simply transmit to accept the default name from the Release<br />
tape. The default <strong>Runtime</strong> name on the Release tape is LINC3R1, <strong>and</strong> the default<br />
configuration parameters are described in “COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR<br />
<strong>Installation</strong> Parameters” on page B–1.<br />
Note: The maximum length of the <strong>Runtime</strong> name entered in the COMUS<br />
configuration screens is eight characters.<br />
If you enter a name, it must be the name you supplied in your General <strong>Configuration</strong><br />
Parameters.<br />
Note: If you have created a configuration set in COMUS <strong>and</strong> used the default<br />
<strong>Runtime</strong> name in GENERAL LONG PARAMS, this name must be entered to accept the<br />
values in the COMUS database. If not, the name will be that from the tape.<br />
4. The Build process creates an ECL runstream. You may view this runstream be<strong>for</strong>e<br />
execution. (If you need to modify the runstream, you must exit COMUS <strong>and</strong> use an<br />
editor). When you are satisfied with the runstream, instruct COMUS to start the batch<br />
job, which generates a new (unlabeled) master tape. (Disk to disk BUILDS are not<br />
supported.)<br />
When the BUILD TASK COMPLETED message is displayed, processing is complete.<br />
5. To determine if the Build was successful, review the output from the batch job <strong>and</strong><br />
check <strong>for</strong> errors. The output is directed to your default print queue, <strong>and</strong> the last page<br />
identifies any errors that have occurred.<br />
Most of the output is directed to the PRNTF$ file <strong>and</strong> copied onto the output tape.<br />
The remaining output is printed.<br />
3–6 78616323–000
Installing <strong>Runtime</strong><br />
About the <strong>Runtime</strong> Release Tape<br />
Installing Enterprise Application Environment Software<br />
The <strong>Runtime</strong> Release tape, supplied as an unlabeled 6250 bpi tape, contains the following<br />
files.<br />
Installing with SOLAR<br />
File File Name Description<br />
1 CO$UTIL COMUS utility file<br />
2 UTIL$ Enterprise Application Environment Utilities<br />
3 ALIB$ Common Bank Absolutes <strong>and</strong> subsytem object<br />
modules<br />
4 OLIB1$ Relocatables <strong>and</strong> object modules used <strong>for</strong> Build<br />
5 OLIB$ Relocatables<br />
6 OMLIB$ Extended Mode Object Modules<br />
7 SLIB$ Source elements<br />
8 PCF$ <strong>OS</strong> <strong>2200</strong> based System changes<br />
9 PRNTF$ Build print file<br />
10–14 ROCSYS Report Output Control (ROC) System Object files<br />
20 HELPDOC Help Document<br />
23 GLOBALST Skeletons used by generate<br />
24 GLOBALSG Skeletons used by generate<br />
25 CODES Sample CODES file<br />
26 U$SCRREL Utility Program Screens<br />
To run the SOLAR installation of <strong>Runtime</strong>, per<strong>for</strong>m the following steps:<br />
• Register the Output Tape<br />
• Install from Registered Packages<br />
• Modify the Runstream<br />
• Set Up Special <strong>Installation</strong> Privileges<br />
• Check the <strong>Installation</strong> Verification Procedure (IVP)<br />
These steps are detailed in the following subsections.<br />
78616323–000 3–7
Installing Enterprise Application Environment Software<br />
Register Output Tape<br />
To register the output tape from the build process with SOLAR:<br />
1. From the SOLAR Main menu, tab to the Register field <strong>and</strong> transmit.<br />
The Package In<strong>for</strong>mation screen is then displayed.<br />
2. Enter the source media containing the output of the COMUS Build process. For<br />
example, if you had an unlabeled tape 23792c, you would enter this in the Reel Ids:<br />
field.<br />
The Runstream In<strong>for</strong>mation screen is then displayed.<br />
3. Make your required changes. To start the runstream, enter Y in the Do you wish to<br />
start (@START) the runstream now? field.<br />
Installing from Registered Packages<br />
To install Release 3R1A from the registered packages:<br />
1. From the SOLAR Main menu, tab to the Software <strong>Installation</strong>: Registered<br />
Packages field <strong>and</strong> transmit.<br />
2. Locate the screen containing Enterprise Application Environment 3R1A.<br />
3. Move to the Enterprise Application Environment 3R1A tape that you registered <strong>and</strong><br />
press the F8 key.<br />
4. Move to the Mode you want to install <strong>and</strong> press the F5 key.<br />
The Runstream In<strong>for</strong>mation screen is then displayed.<br />
5. Make your required changes. To start the runstream, enter Y in the Do you wish to<br />
start (@START) the runstream now? field.<br />
Modifying the Runstream<br />
If you need to modify the runstream, you must exit SOLAR <strong>and</strong> use an editor. If you are<br />
satisfied with the runstream, in<strong>for</strong>m SOLAR to start the batch job.<br />
The batch job reads the product master tape created by the Build process, <strong>and</strong> installs<br />
<strong>Runtime</strong>.<br />
Setting Up Special <strong>Installation</strong> Privileges<br />
You need special privileges to per<strong>for</strong>m the install process. For example, the MAKE-<br />
TABLES runstream updates the runtime*PERM$SGS file with Integrated Recovery<br />
Application in<strong>for</strong>mation. The runstream there<strong>for</strong>e needs the necessary privileges in order<br />
to accomplish this. Check with your site security administrator.<br />
See the <strong>OS</strong> <strong>2200</strong> COMUS End Use Reference Manual <strong>for</strong> a summary of the required<br />
privileges. The Common Bank Reload privilege is required to install Enterprise Application<br />
Environment 3R1A.<br />
3–8 78616323–000
Installing Enterprise Application Environment Software<br />
The userid used to install <strong>Runtime</strong> must have the necessary privileges to per<strong>for</strong>m SOLAR<br />
installations. See Section 1 of the SOLAR End Use Reference Manual <strong>for</strong> in<strong>for</strong>mation on<br />
the privileges needed.<br />
Also, the security environment must be set up properly <strong>for</strong> the LINC$RTS subsystem to<br />
function correctly. Refer to Appendix A of the <strong>OS</strong><strong>2200</strong> Software Products <strong>Installation</strong><br />
<strong>Guide</strong> <strong>for</strong> guidelines on setting up the security environment <strong>for</strong> Object Module<br />
Subsystems.<br />
<strong>Runtime</strong> contains both chameleon <strong>and</strong> protected subsystem types. The userid of the<br />
owner of the ALIB$ file (which contains the subsystem definition elements) must have<br />
the following subsystem security attributes. -LINC- is the recommended userid.<br />
Parameter Value<br />
User-id Name -LINC-<br />
Record Access Semiprivate<br />
Attached ACR Name EXEDEL<br />
ACR Arguments Execute: Public<br />
Delete: Userid EQ SUBSYS-ADMIN<br />
Run Mode None<br />
Processor Privilege Read Execute GRS<br />
Access Privilige Trusted<br />
Sharing Level Application<br />
Clearance Level Minimum = 0, Maximum = 0<br />
Compartment Set Maximum = NULL, Default = NULL<br />
Trusted Privileges None<br />
Other Priviliges SSGAP<br />
ERs, CALLs None<br />
File ACR Name PUBRD<br />
File ACR Arguments Read: Public<br />
Checking the <strong>Installation</strong> Verification Procedure (IVP)<br />
The <strong>Installation</strong> process contains an <strong>Installation</strong> Verification Procedure (IVP). The IVP<br />
checks that <strong>Runtime</strong> has been installed successfully by checking that all files, RDMS<br />
tables, <strong>and</strong> Common Banks have been correctly set up.<br />
If the IVP fails, you can check the success of your installation procedure by reviewing the<br />
output from the batch job, <strong>and</strong> checking <strong>for</strong> errors. The output is directed to your default<br />
print queue, <strong>and</strong> the last page identifies any errors that may have occurred.<br />
78616323–000 3–9
Installing Enterprise Application Environment Software<br />
The output from the installation will show that a number of elements were created in the<br />
SOLAR*DIAGN<strong>OS</strong>TIC file.<br />
1. Check if there were any errors encountered during the installation. If a problem<br />
existed, inspect the PL-DIAGINFO/timestamp element with an editor to determine<br />
the cause of the problem.<br />
2. Ensure that the complete environment is functioning correctly (including EXEC, MCB,<br />
<strong>and</strong> HVTIP) by installing <strong>and</strong> logging on to the Report Output Control System (ROC).<br />
<strong>Installation</strong> of ROC is described later in this section.<br />
Log on to ROC by entering the ROC transaction name from a TIP terminal. The ROC<br />
transaction name is specified when <strong>Runtime</strong> is installed. For more details, see<br />
“COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters” on page B–1.<br />
If the ROC Home screen is displayed, Enterprise Application Environment has been<br />
installed correctly <strong>and</strong> the IVP is complete. If you cannot display the ROC Home<br />
screen, contact your local Unisys representative.<br />
<strong>Installation</strong> Modes <strong>for</strong> Setting Up HUBs<br />
The HUB feature h<strong>and</strong>les external Automatic Entries, including those between hosts. A<br />
HUB is defined by the LINC$HUB BDI <strong>and</strong> the HUB identifier in the COMUS<br />
<strong>Configuration</strong> Set. One HUB may comprise multiple <strong>Runtime</strong>s.<br />
Use the MODE parameter in the SOLAR installation of your <strong>Runtime</strong> to define which<br />
<strong>Runtime</strong> you are installing.<br />
• If you are planning interhost communication, this procedure must be followed on<br />
each host; that is, there must be a HUB Common Bank <strong>for</strong> each host.<br />
• For interhost Automatic Entries, you are required to supply an element (HUB$SGS)<br />
containing SGS parameters that define your network host names <strong>and</strong> addresses.<br />
This is a post-installation procedure. Full details are provided in your Unisys e-@ction<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
One <strong>Runtime</strong> is nominated as the controller of the HUB. Install this environment first.<br />
Select the HUB mode on the SOLAR installation screen.<br />
When additional <strong>Runtime</strong>s are installed into the same HUB (that is, in the same<br />
intersystem communication network), select the LINC mode field on the SOLAR<br />
installation screen. The <strong>Runtime</strong>s within a HUB are linked by having the same HUB id <strong>and</strong><br />
HUB common bank BDI during your COMUS configuration.<br />
The default mode is HUB.<br />
Note the following points:<br />
• All <strong>Runtime</strong>s must belong to a HUB. As a result, <strong>for</strong> the first <strong>Runtime</strong> you install, you<br />
must select the HUB mode, even though it may be the only environment to be used.<br />
3–10 78616323–000
Installing Enterprise Application Environment Software<br />
• If you are per<strong>for</strong>ming external Automatic Entries between a Release 16.3 (or earlier)<br />
System <strong>and</strong> your Release 3R1A System, Release 3R1A <strong>Runtime</strong> must be used as<br />
your HUB controller.<br />
Reinstalling or Switching the Controller<br />
You may reinstall or switch your controlling <strong>Runtime</strong>, by per<strong>for</strong>ming the following steps:<br />
1. Ensure that all Background Runs <strong>for</strong> the HUB are down during this procedure (they all<br />
share the same common bank).<br />
2. Install the intended controlling environment. Select the HUB mode. During this<br />
process, the old controller will be deinstalled if the same BDI value <strong>for</strong> the LINC$HUB<br />
common name is used.<br />
3. When this switch is complete, the old controller must be reinstalled. Select the LINC<br />
mode.<br />
78616323–000 3–11
Installing Enterprise Application Environment Software<br />
Installing <strong>Runtime</strong> with XTC<br />
About XTC<br />
XTC Systems consist of two or more <strong>2200</strong> Series hosts, special interhost<br />
communications links such as Host LAN Controllers (HLCs), shared mass storage<br />
subsystems, <strong>and</strong> a Record Lock Processor (RLP). The RLP keeps track of what current<br />
resources are in use. XTC uses the RLP to coordinate shared database operations across<br />
all hosts.<br />
XTC TIP<br />
XTC TIP, through the use of shared application groups, enables you to share TIP <strong>and</strong><br />
HVTIP applications across multiple hosts. This functionality is controlled by the EXEC<br />
configuration tag MHTIP. Within a shared application, XTC TIP enables you to share<br />
access to transactions <strong>and</strong> databases between multiple hosts.<br />
XTC UDS<br />
XTC UDS is a facility of Universal Data Systems that permits the sharing of DMS, SFS,<br />
<strong>and</strong> RDMS databases across the hosts of an in<strong>for</strong>mation hub. XTC UDS also uses the RLP<br />
to track resource usage across all hosts.<br />
About Shared <strong>and</strong> Local Application Groups<br />
Valid <strong>OS</strong> <strong>2200</strong> based application groups on XTC systems are:<br />
• Local<br />
• Shared<br />
You can install your copy of <strong>Runtime</strong> into local or shared application groups. When<br />
configuring the copy of <strong>Runtime</strong>, specify the application group in which it will run. If the<br />
application group type is local, Systems that are part of that copy of <strong>Runtime</strong> will be<br />
confined to a single host. If the application group is shared, the Systems will be available<br />
on all hosts.<br />
Local Application Groups<br />
Systems in local application groups operate normally, with one exception.<br />
If your host has MHTIP (XTC TIP) configured, all HVTIP library files must be cataloged on<br />
shared mass storage, <strong>and</strong> registered in the shared directory; even if the HVTIP system<br />
itself operates in a local application group.<br />
For Enterprise Application Environment Systems, this means that <strong>for</strong> hosts with MHTIP<br />
configured, all HVTIP libraries are cataloged on shared mass storage.<br />
3–12 78616323–000
Installing Enterprise Application Environment Software<br />
For Systems in a local application group, it means that the OBJECT PACK specification<br />
will not be honored <strong>for</strong> the HVTIP library. Instead, the HVTIP library will be cataloged on<br />
fixed shared mass storage. This is because the removable disks specified <strong>for</strong> use in a<br />
local System are local removable disks. Because of the MHTIP requirement, the HVTIP<br />
library cannot be cataloged on the same disks as the other object files <strong>for</strong> the system.<br />
Shared Application Groups<br />
When your Enterprise Application Environment System is installed in a shared application<br />
group, all files (<strong>and</strong> any defined packs) are cataloged as shared on shared mass-storage,<br />
<strong>and</strong> are registered in the shared directory. While your System is operating, XTC UDS uses<br />
the XPC/RLP to coordinate updates <strong>and</strong> locks on all hosts.<br />
Enterprise Application Environment h<strong>and</strong>les all of the details associated with shared<br />
systems. A shared application group is selected automatically by running in the<br />
appropriate <strong>Runtime</strong>.<br />
Installing <strong>Runtime</strong> into a Shared Application Group<br />
In an XTC environment, use SOLAR to install a copy of the <strong>Runtime</strong> into the same shared<br />
application group on each host.<br />
Follow the COMUS configure <strong>and</strong> build, <strong>and</strong> SOLAR installation procedures <strong>for</strong> the first<br />
host. This first installation creates the RDMS tables <strong>for</strong> the total environment, on shared<br />
mass storage.<br />
The output from the configure/build on your first host is date/time stamped. You should<br />
install the same output tape on all hosts in the XTC environment.<br />
When you install it on another host, the system detects from this date/time stamp that<br />
you are installing the same shared <strong>Runtime</strong>, <strong>and</strong> the RDMS tables are not created again.<br />
If the date/time stamp does not match that <strong>for</strong> the existing shared environment, then<br />
RDMS tables are built <strong>for</strong> a new <strong>Runtime</strong>. In this case, be<strong>for</strong>e you install, you must stop<br />
all Background Runs on all hosts.<br />
78616323–000 3–13
Installing Enterprise Application Environment Software<br />
Installing <strong>Runtime</strong> with PAEXEC<br />
Partitioned applications can be switched between hosts in a PAEXEC environment,<br />
although an application can only be running on one host at a time.<br />
You must install <strong>Runtime</strong> on both of the hosts in the PA EXEC configuration.<br />
During installation of <strong>Runtime</strong>, RDMS tables <strong>for</strong> applications that can be switched are<br />
catalogued on mass-storage.<br />
You must ensure that a shared mass-storage device is used in the COMUS configuration,<br />
if removable packs are used on your hosts.<br />
3–14 78616323–000
Be<strong>for</strong>e Using <strong>Runtime</strong><br />
Installing Enterprise Application Environment Software<br />
After installing <strong>Runtime</strong>, you must per<strong>for</strong>m the tasks outlined in the following subsection<br />
be<strong>for</strong>e it can be used.<br />
Turn on TIP Transaction Processing<br />
Use the FB comm<strong>and</strong> to ensure that the FB OP$MAIN parameter is on. This effectively<br />
turns TIP transaction processing ON. For more details, see your <strong>OS</strong> <strong>2200</strong> TIP <strong>Installation</strong><br />
<strong>Guide</strong>.<br />
Create TIP Memory Groups<br />
TIP memory groups are automatically created within the total available TIP memory, as<br />
specified in the TPMEMX parameter. You may choose to use the automatically created<br />
groups, or to change them. There is an overhead if the available TIP memory groups do<br />
not match the requirements of your Systems.<br />
Note: For SB6 (<strong>and</strong> above), TIP memory is dynamic <strong>and</strong> does not need to be configured.<br />
Manually changing the TIP memory groups may improve per<strong>for</strong>mance, but requires a<br />
good knowledge of TIP. It is advisable to use the automatically created group, unless you<br />
have previous experience of tuning TIP memory.<br />
Changing TIP Memory Groups<br />
If you decide to change the TIP memory allocation group, ensure that all unwanted<br />
groups are deleted.<br />
To establish the TIP memory requirements <strong>for</strong> your Systems, use the TMINIT Utility to<br />
monitor current TIP memory group usage.<br />
Note: Be<strong>for</strong>e changing your TIP memory groups, it is advisable to switch transaction<br />
scheduling off, <strong>and</strong> wait until all active transactions have been completed. To switch<br />
scheduling off, enter the following from a system console: FB OFF SCHEDULE.<br />
The automatic TIP memory group allocation should be used <strong>for</strong> TIP environments running<br />
Enterprise Application Environment. However, you may wish to modify TIP memory<br />
groups to improve utilization of TIP memory. The following discussion provides details<br />
about memory usage that may help you establish TIP memory requirements.<br />
There are two important considerations about TIP memory allocation:<br />
• There must be a memory group allocation big enough to accommodate your largest<br />
IBANK plus its associated relocatable (RSEG) DBANK. The TIP memory group<br />
acquired by your ICP has to accommodate not only the DBANK <strong>for</strong> the ICP, but also<br />
the DBANKS of any subprograms it uses. As Ispecs are subprograms, a TIP memory<br />
group must exist that is large enough to accommodate the DBANK <strong>for</strong> the ICP plus<br />
the DBANK of your largest Ispec.<br />
78616323–000 3–15
Installing Enterprise Application Environment Software<br />
• There must be sufficient TIP memory, both in terms of total allocation <strong>and</strong> in the<br />
number of individual allocations. All Ispecs use TIP memory, <strong>and</strong> any Reports that use<br />
external Automatic Entries may also use TIP memory to schedule the resulting<br />
transaction.<br />
The exact allocation depends upon the size, complexity, <strong>and</strong> use of your system. The<br />
current use of TIP memory can be displayed using TMINIT. For more details, see your<br />
<strong>OS</strong> <strong>2200</strong> TIP <strong>Installation</strong> <strong>Guide</strong>.<br />
If your largest non-PCT bank allocated is not large enough, TPUR fails while loading the<br />
program library. If your DBANK is larger than any non-PCT bank allocated, the first attempt<br />
to execute the transaction causes an error.<br />
To decide which TIP memory groups to set up, you will need to know the size of the<br />
IBANKS <strong>and</strong> DBANKS of your ICP <strong>and</strong> Ispecs. This in<strong>for</strong>mation can be found in the output<br />
from the @MAP (TPE) or @LINK (UCS) <strong>for</strong> each Ispec when your System is installed using<br />
the Generate option of Host Builder, or using the Configure Utility.<br />
An element exists <strong>for</strong> each Ispec, each separately compiled Global Logic, <strong>and</strong> <strong>for</strong> your<br />
ICP. The ICP element has the same name as your system transaction id.<br />
When executing TPUR against your HVTIP library, the LIST option also provides<br />
in<strong>for</strong>mation on the bank sizes of your Ispecs. Enter the following ECL to list your HVTIP<br />
library:<br />
<br />
<br />
The nn value represents your HVTIP library number. By default the TIPRUN$ file tiprun$file<br />
is named TIP$*TIPRUN$.<br />
Reload TIP Library <strong>and</strong> TIP Memory Groups<br />
If you are already running TIP, you may have a runstream in SYS$LIB$*RUN$ that reloads<br />
HVTIP libraries after a system reboot. Add to this runstream a reload of the TIP library<br />
associated with each of your Systems, <strong>and</strong> a runstream to reset the TIP memory groups,<br />
as mentioned in “Changing TIP Memory Group”.<br />
Enter the following ECL to load or reload an HVTIP library:<br />
<br />
<br />
The nn value represents your HVTIP library number.<br />
If you have the Application Recovery Feature (ARF) turned on (by using the TIP ON<br />
system keyin), then the reloading of HVTIP libraries <strong>and</strong> the reestablishing of TIP memory<br />
allocations are automatic.<br />
A runstream is available with <strong>Runtime</strong> to reestablish a System TIP environment. Enter the<br />
following from a Dem<strong>and</strong> session:<br />
<br />
3–16 78616323–000
Installing Enterprise Application Environment Software<br />
A message is displayed, prompting you <strong>for</strong> your system name. Enter the correct system<br />
name, <strong>and</strong> its TIP environment will then be recovered.<br />
Note: If you per<strong>for</strong>m a valtab build or jump key 7 or 13 boot, you need to reestablish your<br />
TIP environment by running recovery <strong>for</strong> all your Systems.<br />
Define a TIP Error H<strong>and</strong>ling Program<br />
TIP requires an error h<strong>and</strong>ling program to receive recoverable messages that cannot be<br />
successfully processed. The STEPCONTROL EXEC SGS defines the QPRIORITY of the<br />
error h<strong>and</strong>ling program.<br />
If an error h<strong>and</strong>ling program is not created <strong>and</strong> the STEPCONTROL SGS defines the same<br />
QPRIORITY <strong>for</strong> the nonexistent error h<strong>and</strong>ling program as <strong>for</strong> your system, a transaction<br />
error may stop your entire system.<br />
A sample of an error h<strong>and</strong>ling program is provided in the COMUS file (file1) on the<br />
Release tape. A sample ECL to map the error h<strong>and</strong>ling program is also provided in this<br />
file. The element names are MCBSE1 <strong>and</strong> MCBSE1 / MAP.<br />
To copy file 1 from the Release tape to a file file, where reel is the reel number <strong>and</strong> type is<br />
the tape equipment type, execute the following ECL:<br />
<br />
<br />
<br />
For more details of error h<strong>and</strong>ling programs, see your <strong>OS</strong> <strong>2200</strong> MCB System Support<br />
Reference Manual.<br />
Set Default Page Size<br />
The default page size (MAX-PAGE-SIZE) parameter <strong>for</strong> the Integrated Recovery Utility<br />
(IRU) should be set to at least 7168, to allow IRU to back up all the RDMS tables. For<br />
details of this parameter <strong>and</strong> how to change it, see your <strong>OS</strong> <strong>2200</strong> UDS <strong>Installation</strong> <strong>Guide</strong>.<br />
78616323–000 3–17
Installing Enterprise Application Environment Software<br />
Starting Your Background Runs<br />
The Background Run <strong>and</strong> the HUB Background Run should be active be<strong>for</strong>e you install<br />
<strong>and</strong> use the other Enterprise Application Environment products.<br />
To start a runstream, from the system console, enter the following comm<strong>and</strong>:<br />
<br />
Depending on your software configuration, you may be able to abbreviate the comm<strong>and</strong><br />
as follows:<br />
<br />
The name of the runstream that starts the Background Runs is defined when your<br />
<strong>Runtime</strong> software is installed. By default it is LINCBR. This runstream is placed in<br />
SYS$LIB$*RUN$. For more in<strong>for</strong>mation, see “COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR<br />
<strong>Installation</strong> Parameters” on page B–1.<br />
3–18 78616323–000
Reinstalling <strong>Runtime</strong><br />
Installing Enterprise Application Environment Software<br />
You may need to reinstall <strong>Runtime</strong> <strong>for</strong> the following reasons:<br />
• Updating to a new release of Enterprise Application Environment<br />
• After upgrading your operating system (recommended)<br />
Procedure <strong>for</strong> Reinstalling<br />
To reinstall <strong>Runtime</strong>:<br />
1. Ensure that no one is using <strong>Runtime</strong> while you are reinstalling the product.<br />
2. Close down all Systems by executing the CL<strong>OS</strong>EDOWN program, as follows.<br />
<br />
3. Terminate the HUB Background Run by entering the following comm<strong>and</strong> from a<br />
operator console:<br />
<br />
Here id is the HUB identifier that was specified when configuring <strong>Runtime</strong>.<br />
Terminate the Background Run by entering the following:<br />
<br />
Here runtime is the <strong>Runtime</strong> name.<br />
RDMS Tables<br />
Caution<br />
If a new version of <strong>Runtime</strong> is installed, install Host Builder again, <strong>and</strong> use the<br />
Configure from Disk Transfer option. This is described later in this<br />
subsection.<br />
The RDMS tables described in the following table are saved at the beginning of the install<br />
process, <strong>and</strong> restored on completion.<br />
Table Contains Details of … Saved As<br />
runtime_SCHEMA.LSYS All Systems configured<br />
within <strong>Runtime</strong><br />
runtime_SCHEMA.SECURITY Security that you have<br />
loaded <strong>for</strong> all Systems<br />
within <strong>Runtime</strong><br />
runtime_SCHEMA.SECURINT Security that you have<br />
loaded <strong>for</strong> your Host<br />
Builder<br />
runtime*SAVE-LSYS<br />
runtime*SAVE-SEC<br />
runtime*SAVE-SECINT<br />
78616323–000 3–19
Installing Enterprise Application Environment Software<br />
Table Contains Details of … Saved As<br />
runtime_SCHEMA.PIDRANGES TIP Stations runtime*SAVE-RANGES<br />
runtime_SCHEMA.CONFIG COMUS Parameters runtime*SAVE-CONFIG<br />
runtime_SCHEMA.STNDEFAULT Initial setup in<strong>for</strong>mation<br />
<strong>for</strong> station records<br />
runtime_SCHEMA.SERVICES Relationships between<br />
OLTP service names<br />
<strong>and</strong> the Systems they<br />
are part of<br />
If saved files are found to exist at the beginning of an install, it is assumed that an earlier<br />
install had failed. The current install will issue a detailed message, <strong>and</strong> stop. You should<br />
check the save files. If they are empty, delete them <strong>and</strong> restart the install. If they contain<br />
valid data <strong>and</strong> your system tables are empty, per<strong>for</strong>m the following:<br />
<br />
<br />
H<strong>and</strong>ling Unsaved RDMS Tables<br />
The data in the following tables is not saved <strong>and</strong> restored when reinstalling <strong>Runtime</strong>.<br />
• runtime_SCHEMA.ACCEPTS<br />
• runtime_SCHEMA.REPORTINFO<br />
• runtime_SCHEMA.REPORTSRUN<br />
• runtime<br />
runtime*SAVE-STNDEF<br />
runtime*SAVE-SRVCES<br />
There can be implications in the fact that these tables are not saved when reinstalling<br />
<strong>Runtime</strong>. If you had a Report that went into extended report recovery immediately prior to<br />
the reinstall, you would lose this Report in<strong>for</strong>mation when the Report recovered under<br />
the new <strong>Runtime</strong>.<br />
For further in<strong>for</strong>mation on the tables, see “Files Created by Enterprise Application<br />
Environment” on page A–1.<br />
3–20 78616323–000
Installing Enterprise Application Environment Software<br />
Installing Additional Copies of <strong>Runtime</strong><br />
You may want to install more than one copy of <strong>Runtime</strong>. For example, you may wish to<br />
run Enterprise Application Environment in more than one application group.<br />
To install an additional copy of <strong>Runtime</strong>:<br />
1. Create a new <strong>Configuration</strong> Set, specifying a different <strong>Runtime</strong> name <strong>and</strong><br />
<strong>Configuration</strong> Set name.<br />
2. Complete the remaining steps <strong>for</strong> configuring a <strong>Runtime</strong> (as described earlier in this<br />
subsection), followed by the Build <strong>and</strong> Install tasks.<br />
3. The <strong>Runtime</strong> name, Common Bank BDIs, <strong>and</strong> the Background Run id must be unique<br />
<strong>for</strong> each <strong>Runtime</strong>. If you are installing into a different application group, the application<br />
name <strong>and</strong> application number must be changed, as well as the Library file names <strong>for</strong><br />
MCB, <strong>and</strong> RDMS.<br />
4. If your additional <strong>Runtime</strong> is to be part of an existing HUB network, remember to<br />
install selecting the LINC mode.<br />
78616323–000 3–21
Installing Enterprise Application Environment Software<br />
Installing Host Builder<br />
The Host Builder provides all the necessary tools to specify <strong>and</strong> generate user Systems.<br />
For details of the facilities of Host Builder, see your Unisys e-@ction Enterprise<br />
Application Host Builder <strong>Guide</strong>.<br />
To install Host Builder, per<strong>for</strong>m the following steps:<br />
1. Ensure that <strong>Runtime</strong> is installed.<br />
2. Load Host Builder from its Release tape by using the LOAD option of the LRU utility.<br />
You can change various configuration parameters if required.<br />
3. Configure <strong>and</strong> install Host Builder by using the Configure utility.<br />
4. Ensure files are secured. For a full list of files, see “Files Created by Enterprise<br />
Application Environment” on page A–1.<br />
5. Delete temporary files no longer required.<br />
6. Start your Host Builder as a final check.<br />
Each of these steps is described in more detail in the following subsections.<br />
Note: To install Unisys-supplied changes to Host Builder, see the instructions<br />
accompanying the EIF (Engineering Interim Fix).<br />
Files on the Host Builder Release Tape<br />
The <strong>OS</strong> <strong>2200</strong> based Host Builder Release tape contains the following files.<br />
File File Name Description<br />
1 CONTROL$ Control file<br />
2 SYSLIB System Control file<br />
3 TRXREL Transaction relocatables<br />
4 SCRSYM Source of screen images<br />
5 SCRREL Relocatables <strong>for</strong> screens<br />
6 REPREL Report relocatables<br />
7 GLOBALSP Skeletons <strong>and</strong> templates<br />
8 GLOBALSR Skeletons <strong>and</strong> templates<br />
9 GLOBALCO Skeletons <strong>and</strong> templates<br />
10 GLOBALSC Skeletons <strong>and</strong> templates<br />
11 LIBRARYR Skeletons <strong>and</strong> templates<br />
12 SLDACCEPT Skeletons <strong>and</strong> templates<br />
13 RELOAD Skeletons <strong>and</strong> templates<br />
3–22 78616323–000
Loading Host Builder from Tape<br />
Installing Enterprise Application Environment Software<br />
Load Host Builder from its Release tape by executing the load program, using the<br />
following ECL <strong>for</strong>mat:<br />
<br />
The LOAD Utility prompts are displayed one at a time. These prompts <strong>and</strong> your required<br />
responses are displayed in the following table. (Default prompt responses are shown in<br />
angle brackets in the prompt messages.)<br />
Are Changes Required?<br />
During the LOAD procedure, the default or current Host Builder configuration is shown.<br />
You will be prompted:<br />
<br />
If you answer Y, you are presented with another set of prompts regarding the following<br />
features:<br />
• Target Host Templates<br />
• Reserved Word Lists<br />
14 ILANGUAGE Skeletons <strong>and</strong> templates<br />
15 START$ ECL <strong>for</strong> CMP Report<br />
LOAD Utility Prompt Required Response<br />
What would you like to<br />
load?<br />
Are Changes Required ?<br />
Y//E(xit)<br />
Enter 3.<br />
Enter Y to change options regarding Target Host<br />
Templates, Reserved Word Lists, Auto Edit<br />
Resequencing, Change Identification <strong>and</strong> Resource<br />
locking Identification, as described following the table.<br />
Enter N to bypass the prompts associated with these<br />
options.<br />
Enter E to terminate.<br />
Enter the tape reel number Enter the reel number to be used to request loading of<br />
the Release tape.<br />
Enter Tape equipment<br />
Type<br />
File File Name Description<br />
Enter the media type, <strong>for</strong> example U9S (as the Release<br />
tape is 6250 bpi).<br />
Labelled tape Enter N (as Release tapes are unlabeled).<br />
What System name shall it<br />
be loaded as?<br />
Enter the System name <strong>for</strong> your Host Builder. This may<br />
be changed later, by using the Configure Utility.<br />
78616323–000 3–23
Installing Enterprise Application Environment Software<br />
• Auto Edit Resequencing<br />
• Change Control Options<br />
Additional in<strong>for</strong>mation on change control settings is contained in your Unisys e-@ction<br />
Enterprise Application Host Builder <strong>Guide</strong>.<br />
Pairs of the angle brackets (< >) contain the default or currently en<strong>for</strong>ced values (except<br />
<strong>for</strong> the Change/Resource Control parameters, which default to N). Currently en<strong>for</strong>ced<br />
values will be shown within angle brackets if the SLDACCEPT file already exists <strong>for</strong> your<br />
<strong>Runtime</strong>; <strong>for</strong> example, if a Host Builder has already been installed.<br />
Details about each prompt are given in the following subsections.<br />
Target Host Templates<br />
You are asked which target host templates you wish to load. The options are <strong>OS</strong> 1100,<br />
ASeries, or UNIX, or an acceptable abbreviation (<strong>for</strong> example, 1, A, or U).<br />
Only one set of templates may be loaded. This means that you can only generate<br />
Systems that target one type of host.<br />
You can set up the templates <strong>for</strong> UNIX or MCP based Systems in the <strong>OS</strong> <strong>2200</strong> based<br />
environment, if you want to use LCOPY to transfer a Specification to that type of host at a<br />
later date.<br />
Note: Once your Host Builder is operational you can change these settings with the<br />
SUPERVISOR (SUP) comm<strong>and</strong>. If you are configuring with Retain Existing Database,<br />
then the entries you make on this screen will not override your existing H<strong>OS</strong>TLIST settings<br />
<strong>and</strong> you will have to use the Supervisor mode Host Maintenance feature to change your<br />
host settings. See your Unisys e-@ction Enterprise Application Host Builder <strong>Guide</strong> <strong>for</strong><br />
further details.<br />
Reserved Word Lists<br />
Reserved Words are loaded <strong>for</strong> the host you have nominated <strong>for</strong> Target Templates. You<br />
can also select one or more of the other available architectures, including Developer.<br />
You are prompted <strong>for</strong> each available host type in turn.<br />
Your reserved word lists are stored in a Common Bank, <strong>and</strong> there<strong>for</strong>e the more reserved<br />
word lists you select, the larger the corresponding memory usage.<br />
Note: Once your Host Builder is operational you can change these settings with the<br />
SUPERVISOR (SUP) comm<strong>and</strong>. If you are configuring with Retain Existing Database,<br />
then the entries you make on this screen will not override your existing H<strong>OS</strong>TLIST settings<br />
<strong>and</strong> you will have to use the Supervisor mode Host Maintenance feature to change your<br />
host settings. See the Unisys e-@ction Enterprise Application Host Builder <strong>Guide</strong> <strong>for</strong><br />
further details.<br />
The full list of reserved words is contained in your Unisys e-@ction Enterprise Application<br />
Developer User <strong>Guide</strong>.<br />
3–24 78616323–000
Auto Editor Resequencing<br />
Installing Enterprise Application Environment Software<br />
To allow automatic line resequencing in Editor, respond to this prompt by entering Y. This<br />
is the default.<br />
To inhibit automatic Editor resequencing, respond by entering N.<br />
Once set, this option applies to all Specifications in Host Builder.<br />
If you turn off automatic Editor resequencing, it will be the responsibility of your<br />
programmers to manually resequence any lines of code that may require it. If<br />
resequencing becomes necessary, <strong>and</strong> you have turned off automatic Editor<br />
resequencing, an appropriate message is displayed requesting manual resequencing of<br />
the necessary lines.<br />
Note: This feature has nothing to do with the RESEQ; comm<strong>and</strong>. It applies only to<br />
automatic line resequencing in Editor. This would usually occur when programmers<br />
attempt to insert lines at a point where the sequence would have to be changed to<br />
accommodate these extra lines.<br />
This facility is most appropriate when a Specification is required to undergo LCOPY<br />
Create Patch <strong>and</strong> Merge Patch operations.<br />
An LDL listing will show the current state of your Auto Editor Resequencing field.<br />
Change Identification<br />
Enter Y in this field if you want Change Identification to be enabled <strong>for</strong> your Host Builder.<br />
This will identify all changes by your selected Identification Mode.<br />
Resource Locking<br />
Caution<br />
If you answer N to this field, resequencing becomes a manual operation, <strong>and</strong><br />
there<strong>for</strong>e your responsibility. An Insufficient space <strong>for</strong> INSERT message is<br />
issued if lines are inserted that would normally <strong>for</strong>ce an automatic resequence.<br />
This parameter can be changed from the Environmental Options screen once<br />
your Host Builder is operational, however you would need to reconfigure your<br />
Host Builder <strong>for</strong> the change to take place.<br />
Enter Y in this field if you want Resource Locking to be enabled <strong>for</strong> your Host Builder. This<br />
will enable structures to be explicitly locked by users, <strong>and</strong> remain locked until they are<br />
specifically unlocked.<br />
For details of the methods that you can select to identify users when Resource Locking is<br />
in <strong>for</strong>ce, see the Identification Mode field.<br />
78616323–000 3–25
Installing Enterprise Application Environment Software<br />
Identification Mode<br />
Enter the Identification mode that you wish to use <strong>for</strong> your Host Builder. This setting is<br />
only relevant if you have entered Y in either or both the Change Identification or<br />
Resource Locking fields.<br />
Enter a value that specifies the method of identifying users of your Host Builder when<br />
Change Control or Resource Locking is in effect. Values are contained in the following<br />
table.<br />
If you specify U, an identifier of LINC will be automatically established <strong>for</strong> initial access.<br />
It is expected that your user identifiers will be set up during this initial access by the<br />
administrator <strong>for</strong> your Host Builder.<br />
Patch Identification<br />
Enter Y in this field if you want Patch Identification to be enabled <strong>for</strong> your Host Builder.<br />
This will identify <strong>and</strong> store all changes under a unique patch identification number, with<br />
the date <strong>and</strong> time of the change.<br />
Audit level<br />
Enter the level of auditing to be per<strong>for</strong>med <strong>for</strong> your Host Builder, as shown in the<br />
following table.<br />
Specification Administration<br />
Value Method of Identification<br />
L Security Module Usercode/Password<br />
S Station identifier (PID) (default)<br />
U User defined identifier<br />
Level Type of Audit per<strong>for</strong>med<br />
0 No auditing<br />
1 Audit deletions only<br />
2 Audit changes. For user logic changes, discard any intermediate changes<br />
3 Audit all changes<br />
4 Audit all changes. Include a full image <strong>for</strong> all structure deletions<br />
Enter Y in this field if you want auditing to be enabled <strong>for</strong> your Host Builder administration<br />
tasks. This will create an audit trail <strong>for</strong> such activities as generates, Supervisor comm<strong>and</strong><br />
usage, <strong>and</strong> LCOPY runs.<br />
3–26 78616323–000
Installing Enterprise Application Environment Software<br />
Reset all Version counts On id change<br />
Enter Y in this field to automatically reset all System <strong>and</strong> Report generate counts<br />
whenever the Version Identifier <strong>for</strong> the System is changed. For details regarding the use<br />
of the (optional) Version Identifier, see the Change Control Options screen as described in<br />
your Unisys e-@ction Enterprise Application Host Builder <strong>Guide</strong>.<br />
Reset report version counts on system gen<br />
Enter Y in this field to automatically reset all Report generate counts whenever your<br />
System is generated.<br />
Propagate change control settings<br />
Enter Y in this field if you have specified Configure with Retain <strong>and</strong> you want the current<br />
Change Control options to be used to set up every Specification in the Host Builder.<br />
Otherwise, the current settings will be used to set up only the GLOBAL Specification.<br />
Configuring <strong>and</strong> Installing Host Builder<br />
To configure <strong>and</strong> install Host Builder, execute the Configure Utility by per<strong>for</strong>ming the<br />
following steps. For a full description of the Configure Utility, see your Unisys e-@ction<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
1. Ensure that the Background Run <strong>for</strong> your <strong>Runtime</strong> is active.<br />
2. From a Dem<strong>and</strong> terminal, enter:<br />
<br />
3. Select the Configure from disk transfer option from the first screen, <strong>and</strong> enter<br />
the name specified <strong>for</strong> the LOAD function in the System as Loaded field, <strong>and</strong> the<br />
name required <strong>for</strong> your Host Builder in the New System Name field.<br />
After transmitting this screen, the configuration parameters are displayed.<br />
Note: You may execute a Host Builder over the top of an existing Host Builder.<br />
However, since the install will require the SYS$LIB file exclusively <strong>for</strong> some of its<br />
installation processing, other user's system generates will queue waiting <strong>for</strong> the<br />
SYS$LIB file to become available.<br />
4. Change the configuration parameters <strong>and</strong> the pack <strong>and</strong> population specifications, as<br />
required.<br />
5. The following files contain database storage areas <strong>for</strong> the Host Builder, <strong>and</strong> are used<br />
extensively. You may consider placing these separately, <strong>for</strong> per<strong>for</strong>mance reasons.<br />
<br />
<br />
<br />
<br />
<br />
Note: It is advisable to monitor the usage of all database storage areas, to identify<br />
c<strong>and</strong>idates <strong>for</strong> special placement.<br />
78616323–000 3–27
Installing Enterprise Application Environment Software<br />
6. The Configure utility records any errors <strong>and</strong> stores them in various files. Use the<br />
LRUGENSTATUS comm<strong>and</strong> to report on errors.<br />
For more in<strong>for</strong>mation, see your Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong><br />
<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
7. The SLD <strong>and</strong> MOD reports are executed as part of the installation process. These<br />
reports load data into the Host Builder database if you are reconfiguring an existing<br />
Host Builder <strong>and</strong> retaining its existing database. It is advisable to check the SLD<br />
Report output, as it lists any reserved words used in Specifications.<br />
Note: You cannot use Host Builder from an IBM 3270 or a PCE terminal.<br />
Deleting Temporary Files<br />
The LRU LOAD facility creates certain files during its processing. These files are all<br />
qualified by T$system. LRU LOAD also creates a runstream file that you can use to<br />
remove these files, once you are satisfied that your load <strong>and</strong> configure have been<br />
successful.<br />
Enter the following comm<strong>and</strong> to delete these files upon completion of a successful load<br />
<strong>and</strong> configure, if required:<br />
<br />
The system value is the name you entered when you were prompted by the LRU LOAD<br />
facility with the following message:<br />
<br />
3–28 78616323–000
Installing Enterprise Application Environment Software<br />
Installing Multiple Copies of Host Builder<br />
You can install multiple copies of Host Builder in the same <strong>Runtime</strong>, providing they are all<br />
at the same release level, <strong>and</strong> that the following values are unique:<br />
• System name<br />
• Database name<br />
• Transaction id <strong>and</strong> VALTAB Number<br />
• HVTIP Library Number<br />
Caution<br />
If you are installing multiple Host Builders in the same <strong>Runtime</strong>, all activity on<br />
all Host Builders should be stopped while any of the new Host Builders are<br />
being configured.<br />
78616323–000 3–29
Installing Enterprise Application Environment Software<br />
Installing ROC<br />
The Report Output Control System (ROC) is an Enterprise Application System that<br />
manages Report output <strong>for</strong> all Systems in <strong>Runtime</strong>. ROC is included on the Release tape.<br />
You must install ROC be<strong>for</strong>e any Report output (other than output from Direct Reports)<br />
can be printed.<br />
To install ROC:<br />
1. Load ROC from the Release tape to disk.<br />
2. Configure <strong>and</strong> install ROC.<br />
3. Delete temporary files.<br />
These procedures are described in the following subsections. For more in<strong>for</strong>mation on<br />
the <strong>Runtime</strong> Utility, see your Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong><br />
<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
Note: To install Unisys-supplied changes to your ROC System, see the instructions<br />
accompanying the EIF (Engineering Interim Fix).<br />
Loading ROC from the Release Tape<br />
To load ROC, read the Release tape (or the output tape from the COMUS Build process),<br />
by executing the LRU facility. Enter the following ECL:<br />
<br />
The load is initiated. Its prompts are displayed one at a time. These prompts <strong>and</strong> your<br />
required responses are described in the following table.<br />
LOAD prompt Required Response<br />
What would you like to load? Enter 1 to load the ROC System.<br />
Enter the tape reel number Enter the reel number to be used.<br />
Enter tape equipment type Enter media type, <strong>for</strong> example U9S (as the Release<br />
tape is 6250bpi).<br />
Labeled tape Y/ N: Enter Y if tape is labeled. (N is the default.)<br />
Equipment type <strong>for</strong> loaded files Enter the pack id(s) <strong>for</strong> the disk(s) pack to be used.<br />
Default is F (fixed mass storage). See Note.<br />
What system name shall it be loaded<br />
as?<br />
Enter the System name to be used <strong>for</strong> ROC.<br />
Note: If you enter any value other than F (Fixed mass storage), the Disk/pack id(s) <strong>for</strong><br />
loaded files prompt is displayed. Enter the pack names separated by a slash (/) character.<br />
3–30 78616323–000
Installing Enterprise Application Environment Software<br />
The load checks the validity of the pack ids, <strong>and</strong> if it cannot validate the name, it prompts<br />
you to retype the pack ids. If the pack ids validate, it will display a summary of how much<br />
space is required <strong>for</strong> the product you are loading. You can then confirm that you want to<br />
continue.<br />
Configuring <strong>and</strong> Installing ROC<br />
To configure <strong>and</strong> install ROC, per<strong>for</strong>m the following steps:<br />
1. If you are using FREESPACE, ensure that the relevant SGS that specifies the<br />
FREESPACE file is included.<br />
2. Initiate the Configure Utility program, by entering the following from a Dem<strong>and</strong><br />
terminal:<br />
<br />
3. Select the Configure from disk transfer option.<br />
4. Enter the name used by the Load Utility in the System as Loaded field, <strong>and</strong> enter<br />
the name you want to use in the New System Name field.<br />
Following this screen, all of the configuration parameters are displayed. You can<br />
change these if required. For a description of each parameter, see your Unisys e-<br />
@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
Note: Ensure that the transaction name <strong>and</strong> database name are the same as those<br />
specified in COMUS when your <strong>Runtime</strong> was installed. For more details, see<br />
“COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters” on page B–1.<br />
5. Having made any necessary changes to the <strong>Configuration</strong> parameters, you can now<br />
place individual ROC RDMS tables onto specific packs, <strong>and</strong> change their populations.<br />
To access the Pack <strong>and</strong> Population screen, enter a character in the Then: ISPEC<br />
packs <strong>and</strong> populations field. For more details, see your Unisys e-@ction<br />
Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
The following table lists some of the tables in ROC, <strong>and</strong> their use.<br />
Ispec /<br />
Table Contains<br />
HEADR One header record <strong>for</strong> each Report output in the ROC database<br />
OHEAD A record <strong>for</strong> each output request<br />
S_T_N A record <strong>for</strong> each terminal which has accessed the ROC System<br />
TXBLK Data records<br />
6. Having changed the location <strong>and</strong> size of the tables where appropriate, <strong>and</strong> confirmed<br />
the changes, a screen is then displayed that requests run details about the configure<br />
program. Specify the run details <strong>and</strong> transmit the screen.<br />
7. The Configure program then installs ROC.<br />
78616323–000 3–31
Installing Enterprise Application Environment Software<br />
8. Create an additional VALTAB entry <strong>for</strong> ROC to enable your Reports to interface with<br />
ROC. The QMAX parameter in the EXEC configuration <strong>for</strong> the QPRIORITY you specify<br />
in this VALTAB entry must be set to zero. The options <strong>for</strong> the REC parameter in the<br />
VALTAB entry must be set to LMNRSTZ.<br />
The following example shows the <strong>for</strong>mat of this VALTAB entry.<br />
<br />
<br />
<br />
<br />
<br />
Variable values used in this example are explained in the following table.<br />
Parameter Value<br />
file TIPRUN$ file<br />
ttttt ROC Spooler transaction id, as specified in the COMUS configuration <strong>for</strong><br />
this <strong>Runtime</strong><br />
nn TIP transaction number<br />
x Application group number<br />
q QPRIORITY <strong>for</strong> the ROC spooler transaction id<br />
9. Execute VTBUTL from your TIPRUN$ file. By default, this file is named<br />
TIP$*TIPRUN$.<br />
10. The Background Run <strong>and</strong> the HUB Background Run should be active be<strong>for</strong>e<br />
accessing ROC. For more details, see “Starting Your Background Runs” on<br />
page 3–18.<br />
11. Initiate the ROC Background Run <strong>for</strong> your Report Output Control System roc-system,<br />
as follows.<br />
<br />
Note: For XTC systems, you should start the ROC Background Run separately on<br />
each host.<br />
From Release 16R1, a new naming convention has been introduced <strong>for</strong> queued ROC<br />
files. For more details, see your Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong><br />
<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>. You can retain the old naming convention<br />
(as used in releases prior to 16R1) by adding the following line to the RC1 jobstream,<br />
anywhere between the @XQT <strong>and</strong> the @EOF:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
12. Enter the RC1 Background Run is active, by entering the following (where ROC is the<br />
name of the ROC System you installed):<br />
3–32 78616323–000
Installing Enterprise Application Environment Software<br />
However, if you want to stop RC1 in an orderly manner, enter the following from a TIP<br />
terminal (where id is the ROC spooler transaction id):<br />
<br />
You could also enter the following from an operator console. For in<strong>for</strong>mation about<br />
operator console comm<strong>and</strong>s, see Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong><br />
<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
<br />
13. If you are using FREESPACE, check that the Background Run has the correct setting.<br />
If you want to change the ROC spooler Qpriority Node, first change it by using the<br />
Configure utility. You will need to:<br />
1. Change the ROC spooler Qpriority Node in the COMUS configure <strong>for</strong> your <strong>Runtime</strong>.<br />
2. Rebuild <strong>and</strong> install your <strong>Runtime</strong>.<br />
3. Reconfigure the ROC Database.<br />
Deleting Temporary Files<br />
The LRU LOAD facility creates certain files during its processing. These files are all<br />
qualified by T$system. LRU LOAD creates a runstream file that you can use to remove<br />
these files once you are satisfied that your load <strong>and</strong> configure have been successful. To<br />
do this, enter the following comm<strong>and</strong>:<br />
<br />
The system value is the name you entered when you were prompted by the LRU LOAD<br />
facility with the following message:<br />
<br />
78616323–000 3–33
Installing Enterprise Application Environment Software<br />
Deinstalling<br />
Deinstalling <strong>Runtime</strong><br />
To deinstall an <strong>OS</strong> <strong>2200</strong> based <strong>Runtime</strong>, per<strong>for</strong>m the following steps:<br />
1. Remove all active Systems (including ROC <strong>and</strong> Host Builder) within <strong>Runtime</strong> by using<br />
the REMOVESYS option of the <strong>Runtime</strong> Utility (LRU).<br />
Use the LRU SYSCHECK$ALL comm<strong>and</strong> to obtain a list of all installed Systems. For<br />
more details about LRU, see your Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong><br />
<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
2. Terminate the Background Run, by entering the following from an operator console:<br />
<br />
Here runtime is the name of your <strong>Runtime</strong>.<br />
3. Remove <strong>Runtime</strong> schema details from Meta Services Engine/RDMS. To do this, enter<br />
the following comm<strong>and</strong>s from a Dem<strong>and</strong> session.<br />
<br />
<br />
4. To remove the rest of <strong>Runtime</strong>, use SOLAR.<br />
Select the REMOVE PRODUCTS option from the main menu. You can ensure you<br />
are removing the desired <strong>Runtime</strong> by pressing the F10 key from the Product<br />
Selection screen.<br />
Note: For PAEXEC Systems, you will need to per<strong>for</strong>m this step <strong>for</strong> each of your<br />
switchable application groups.<br />
Deinstalling Host Builder<br />
Host Builder is an Enterprise Application System. To deinstall it, use the same procedure<br />
as you would <strong>for</strong> your user Systems. This procedure is described in “Deinstalling<br />
<strong>Runtime</strong>” on page 3–34.<br />
Note: There will be a number of files remaining that were created when you installed<br />
your Host Builder. These files were inherited by <strong>Runtime</strong>, <strong>and</strong> you have to manually delete<br />
them. Check all files that are prefixed by the name of your Host Builder.<br />
3–34 78616323–000
Section 4<br />
Migrating to Release 3R1A<br />
Migration Procedure<br />
Use the following procedure to migrate your Enterprise Application Environment<br />
Systems:<br />
Note: Prior to the release of 3R1A you had the choice of generating either Universal<br />
Compiling System (UCS) COBOL code, or Traditional Programming Environment (TPE)<br />
COBOL code. UCS was previously known as NPE (New Programming Environment).<br />
From Release 3R1A this choice, <strong>and</strong> associated option settings, no longer exists <strong>and</strong> only<br />
UCS COBOL code can be generated.<br />
It is recommended that you migrate existing TPE systems created in Release 16R3, or<br />
earlier, directly to Release 3R1A.<br />
If your systems use external (non Enterprise Application Environment) subroutines in TPE,<br />
these will have to be re-written using a UCS compiler.<br />
1. Take note of the various migration issues outlined in “Addressing Migration Issues”<br />
on page 4–4. It is important that you underst<strong>and</strong> the implications of each new feature.<br />
2. Ensure that your existing Systems <strong>and</strong> Specifications are backed up.<br />
3. It is recommended that you per<strong>for</strong>m a syntax-only generate of your System.<br />
4. Ensure that the appropriate system software is installed. See “Checklist <strong>for</strong> <strong>OS</strong> <strong>2200</strong><br />
Based System Software” on page 2–6.<br />
5. Use one of the following procedures to migrate from release 16R3 to release 3R1A:<br />
• Use LCOPY to extract your Specifications from release 16R3 <strong>and</strong> load them into<br />
release 3R1A. See “Using LCOPY” on page 4–2.<br />
• You can also use CASE LOAD, but this will take longer than LCOPY.<br />
6. After using LCOPY to copy your Specification to release 3R1A, it is recommended<br />
that you per<strong>for</strong>m a syntax-only generate of your System be<strong>for</strong>e you generate the new<br />
System.<br />
7. Generate your Systems. See “Generating Your Systems after Migration” on<br />
page 4–11.<br />
78616323–000 4–1
Migrating to Release 3R1A<br />
Using LCOPY<br />
The following table shows whether you can use LCOPY to migrate your Specifications,<br />
depending on your Host Builder release level.<br />
Using LCOPY to migrate to release 3R1A<br />
Use the following procedure to migrate from release 16R3 to release 3R1A:<br />
1. Unload your existing Specifications (including GLOBAL) from your Developer System,<br />
by using LCOPY.<br />
2. Install release 3R1A.<br />
3. Load your Specifications into your new Host Builder, by using LCOPY.<br />
4. Generate your Systems, as described in “Generating Your Systems after Migration”<br />
on page 4–11.<br />
LCOPY is documented in Unisys e-@ction Enterprise Application LCOPY <strong>Guide</strong>.<br />
Loading into earlier releases<br />
From To 15 To 16<br />
15 Y Y Y<br />
16 – Y Y<br />
3R1A – – Y<br />
You cannot use LCOPY to load Specifications created in (or migrated to) release 3R1A into<br />
release 16.<br />
Using LCOPY Compare across major releases<br />
To<br />
3R1A<br />
Between major releases of Host Builder (<strong>for</strong> example, release 16 <strong>and</strong> release 3R1A),<br />
there are often differences in how Specifications are stored.<br />
You cannot use the LCOPY Compare function to compare Specifications across major<br />
releases.<br />
Generating <strong>OS</strong> <strong>2200</strong> Reports be<strong>for</strong>e Migrating<br />
The N execution option <strong>for</strong> Reports causes your generated Direct Reports to initialize<br />
with the MCB, be<strong>for</strong>e the call to USERPRT.<br />
To use this feature, you must per<strong>for</strong>m one of the following:<br />
• Add the N option to the @XQT report statement in the system*REP$RUN.report<br />
element.<br />
4–2 78616323–000
Migrating to Release 3R1A<br />
• Manually add the N option to the @XQT report statement when running the Direct<br />
Report from Dem<strong>and</strong> mode.<br />
You must regenerate Reports in your current release be<strong>for</strong>e migrating to Release 3R1A.<br />
78616323–000 4–3
Migrating to Release 3R1A<br />
Addressing Migration Issues<br />
Environmental Settings<br />
You may wish to check the environmental settings <strong>for</strong> each Specification. Examples of<br />
possible changes are: pack allocations, integrity settings, log settings, subsystem<br />
allocations, <strong>and</strong> whether audit files are to be copied to tape. However, be<strong>for</strong>e you make<br />
any such changes, first check that the migration in<strong>for</strong>mation (both in this section <strong>and</strong> in<br />
your release in<strong>for</strong>mation) does not specifically exclude that type of change.<br />
Do not, <strong>for</strong> example, change any data items or logic.<br />
Relational Database Fast Load support<br />
A storage area needs several more pages if Relational Database Fast Load level 4R2 is<br />
used <strong>for</strong> loading data into it. The extra number depends on the page size <strong>and</strong> varies from<br />
9 pages (page size = 7168 words) to 102 pages (page size = 224 words).<br />
In Release 3R1A generations, these extra pages will be added to the page number<br />
calculation done in the generate <strong>and</strong> will cause minor UREP Data Dictionary UPDATE<br />
work to be done on the first generate to increase the number of pages accordingly.<br />
Note: Relational Database Fast Load level 4R3 does not have this requirement.<br />
S_T_N Records in Memory<br />
LCOPY <strong>and</strong> CASELOAD will <strong>for</strong>ce the Preserve Session Data setting to "Y". The Preserve<br />
Session Data field had no meaning <strong>for</strong> prior releases on <strong>OS</strong><strong>2200</strong> plat<strong>for</strong>ms. For crossplat<strong>for</strong>m<br />
compatibility reasons, the setting to "Y" equates to using the RDMS/FCSS<br />
method of storing station records, <strong>and</strong> the setting to "N" will turn on the Station Records<br />
In Memory feature<br />
Global Setup Data Blocks<br />
Release 3R1A introduces the ability to define Global Setup Data (GSD) items in multiple<br />
logic blocks, which can be defined in named code blocks, similarly to the naming of Global<br />
Logics, Ispecs <strong>and</strong> Reports.<br />
Existing GSDs will automatically become a GSD block named GLB-SDS <strong>and</strong> any existing<br />
GLB Work GSD item or group will automatically become another GSD block named GLB-<br />
WORK-BLOCK.<br />
Migration from a previous release to this release will require minimal user intervention<br />
with regards to the GSDBLOCKS feature modification. A conversion utility, which will<br />
per<strong>for</strong>m the following, is provided:<br />
4–4 78616323–000
Migrating to Release 3R1A<br />
• Existing GSDs will automatically become a GSD block named GLB-SDS (as this is<br />
their internal “Ispec” name) with an internal number of 1, so that a description <strong>and</strong><br />
text can now be entered <strong>for</strong> them <strong>and</strong> they become a named GSD block.<br />
• Any existing Global Work name GSD item or group will be automatically removed<br />
from this block into a separate block named GLB-WORK-BLOCK. If this name is<br />
already used, then a number from 1 up is suffixed until a unique name is reached <strong>and</strong><br />
this is used. If the existing GLB Work item or group is itself within a group, it is still<br />
converted but with a warning printed in the CPY report output that this has happened.<br />
Both CPY <strong>and</strong> CLD will convert GSDs from pre-release 3R1A input files.<br />
Rounding from Compute Comm<strong>and</strong>s<br />
In release 3R1A the syntax <strong>for</strong> the COMPUTE <strong>and</strong> the COMPUTE.FROM comm<strong>and</strong>s has<br />
been extended to make use of the COBOL ROUNDED option, which <strong>for</strong>ces rounding of<br />
the final result. This is similar to the ADD, DIVIDE, MULTIPLY <strong>and</strong> SUBTRACT options.<br />
Existing specifications will continue to truncate the result of a COMPUTE or<br />
COMPUTE.FROM unless ROUNDED is added.<br />
Extract Format <strong>for</strong> Data Interchange<br />
Release 3R1A provides the ability to create <strong>and</strong> read extract files in a <strong>for</strong>mat that is<br />
compatible with all plat<strong>for</strong>m versions of Enterprise Application Environment. This new<br />
<strong>for</strong>mat is in addition to the existing extract file <strong>for</strong>mats that are user defined <strong>and</strong> internal.<br />
Use LCOPY to load existing Reports into the release 3R1A System. No changes are<br />
required to the Reports. If you want to use this feature:<br />
1. Complete the Report Choices Screen <strong>and</strong> select the Extract File Option (EX).<br />
Alternatively, you can enter the following in any Action field:<br />
<br />
2. Enter the details of the extract files on the Extract File Options screen.<br />
3. Enter the style of the extract data <strong>for</strong> Ispecs in the Ispec Format field. The default<br />
value of the field is the current internal style.<br />
Valid input values are:<br />
• I <strong>for</strong> Internal record <strong>for</strong>mat (default)<br />
• G <strong>for</strong> Generic record <strong>for</strong>mat<br />
The Ispec Format field is unique by Generate Set within a Report.<br />
Note: Print frame extracts, including Mapper extracts, <strong>and</strong> existing Ispec extracts are not<br />
affected by this feature.<br />
The Report can then be generated as normal.<br />
78616323–000 4–5
Migrating to Release 3R1A<br />
Localization<br />
In release 3R1A, all translatable messages displayed by <strong>Runtime</strong> programs use the<br />
st<strong>and</strong>ard <strong>OS</strong> <strong>2200</strong> based Extended Language Message System (ELMS) software to<br />
translate runtime messages from ELMS message files instead of the LLANGUAGE file,<br />
as was previously the means of supplying the translated messages.<br />
You will need to re<strong>for</strong>mat any translated versions of the LLANGUAGE file. The<br />
runtime*UTIL$.convert-ELMS utility is provided to automatically convert the existing<br />
versions of the LLANGUAGE file <strong>and</strong> create the runstreams <strong>and</strong> ELMS SGS statements<br />
required <strong>for</strong> conversion.<br />
Migrating to Release 3R1A <strong>for</strong> LLANGUAGE<br />
The default message file ENG-BASE is included with Enterprise Application Environment<br />
in runtime*UTIL$.<br />
The ELMS messages are installed as a SOLAR local product called LINCELMS, as mode<br />
runtime, in file runtime*LINCELMS.<br />
A new local product is installed the first time each <strong>Runtime</strong> 3R1A is installed. After the<br />
first install, it is your responsibility to maintain it.<br />
If you only use the default language (English), you will not need to do anything.<br />
If you use languages other than English, you will need to translate <strong>and</strong> install them. The<br />
utility runtime*UTIL$.CONVERT-ELMS helps you convert from previous versions of<br />
LLANGUAGE to the new ELMS message file.<br />
The procedure is as follows:<br />
1. Compare your existing LLANGUAGE file versions with runtime*UTIL$.LLANGUAGE<br />
Note: runtime*UTIL$.LLANGUAGE is only used to compare <strong>for</strong> 3R1A conversion.<br />
2. Copy your old LLANGUAGE file to runtime*LLANGUAGE <strong>and</strong> edit it with the results<br />
of the step 1.<br />
3. Enter one of the following comm<strong>and</strong>s:<br />
or<br />
<br />
<br />
4. Enter the following comm<strong>and</strong>:<br />
<br />
5. Using a text editor, add message numbers from 5001 to end of ENG-BASE to your<br />
message file runtime*LINCELMS.ELMScomponent-id/lang.<br />
lang is a three-letter language code, <strong>for</strong> example, FRA. This must match the first three<br />
characters used in GLB.LANGUAGE.<br />
6. Run the element runtime*LINCELMS.SYNTAX/CHECK <strong>and</strong> study the results.<br />
4–6 78616323–000
Migrating to Release 3R1A<br />
7. Edit <strong>and</strong> correct the message file LINCELMS.ELMScomponent-id/lang<br />
Note that the original message from the LLANGUAGE file is included as a comment<br />
to help you.<br />
ELMS will concatenate multiple spaces, so replace these with the ELMS keyword<br />
spacen.<br />
ELMS does not accept characters such as ‘
Migrating to Release 3R1A<br />
Also, old cycles of the file runtime*LINCELMS. can be left behind. You should check <strong>and</strong><br />
delete the runtime*LINCELMS file.<br />
The following table shows the messages you can translate.<br />
Messages used in Message numbers<br />
Same as old LLANGUAGE 3 through 1500<br />
CONFIGURE 5064, 5077, 5529, 5595, 5845, 5846, 5847, 5848, 5872, 6237,<br />
6238, 6239, 6240, 6241, 6242, 6243, 6244, 6245, 6246, 6247,<br />
6248, 6249, 6250, 6251, 6252, 6253, 6254, 6255, 6256, 6257,<br />
6258, 6259, 6260, 6261, 6262, 6263, 6264, 6265, 6266, 6267,<br />
6268, 6269, 6271, 6272, 6273, 6274, 6275, 6276, 6277, 6278,<br />
6279, 6280, 6281, 6282, 6283, 6284, 6285, 6286, 6287, 6288,<br />
6289, 6290, 6291, 6292, 6293, 6294, 6295, 6296, 6297, 6298,<br />
6299, 6300, 6301, 6302, 6303, 6304, 6305, 6306, 6307, 6308,<br />
6308, 6309, 6310, 6311, 6312, 6313, 6314, 6315, 6316, 6317,<br />
6318, 6319, 6320, 6321, 6322, 6323, 6324, 6325, 6326, 6327,<br />
6328, 6329, 6330, 6331, 6332, 6333, 6334, 6335, 6336, 6337,<br />
6338, 6340, 6341, 6342, 6343, 6344, 6345, 6346, 6347, 6348,<br />
6349, 6350, 6351, 6352, 6353, 6354, 6355, 6356, 6357, 6358,<br />
6359, 6360, 6361, 6362, 6363, 6365, 6366, 6367, 6368, 6369,<br />
6370, 6371, 6371, 6372, 6373, 6374, 6375, 6376, 6377, 6378,<br />
6379, 6380, 6381, 6382, 6383, 6384, 6385, 6386, 6387, 6388,<br />
6389, 6390, 6391, 6392, 6393, 6394, 6395, 6396, 6397, 6398,<br />
6399, 6401, 6402, 6403, 6404, 6405, 6407, 6408, 6583, 6584<br />
CONFIGURE LRU 6406<br />
GLOBALCO 5140, 5398, 5438, 5500, 5501, 5522, 5636, 5829, 5835, 6119<br />
GLOBALSP 5462<br />
GLOBALSR 5025, 5031, 5094, 5123, 5125, 5126, 5160, 5161, 5747, 5963,<br />
6050, 6585, 6586, 6587, 6588, 6589, 6590, 6591, 6592, 6593,<br />
6594, 6595<br />
LIBRARYR 5440, 5518, 5624, 5625, 5626, 5628, 5632, 5633, 5750, 5823,<br />
5889, 5983, 6057<br />
4–8 78616323–000
Messages used in Message numbers<br />
ROC Per<strong>for</strong>mance Improvement<br />
Migrating to Release 3R1A<br />
LRU 5013, 5016, 5017, 5023, 5024, 5028, 5038, 5069, 5093, 5095,<br />
5097, 5099, 5102, 5105, 5116, 5107, 5136, 5137, 5138, 5139,<br />
5141, 5144, 5145, 5149, 5158, 5162, 5163, 5164, 5165, 5166,<br />
5167, 5186, 5351, 5357, 5359, 5360, 5364, 5373, 5374, 5376,<br />
5380, 5383, 5384, 5385, 5386, 5387, 5388, 5389, 5390, 5399,<br />
5406, 5408, 5415, 5421, 5427, 5442, 5447, 5448, 5463, 5473,<br />
5475, 5476, 5496, 5513, 5517, 5528, 5532, 5533, 5534, 5535,<br />
5545, 5550, 5554, 5557, 5558, 5558, 5560, 5561, 5575, 5657,<br />
5658, 5686, 5753, 5754, 5772, 5773, 5780, 5798, 5820, 5825,<br />
5830, 5831, 5834, 5832, 5836, 5839, 5850, 5851, 5863, 5866,<br />
5869, 5887, 5943, 5949, 5973, 5974, 5975, 5976, 5993, 5994,<br />
5995, 5996, 6007, 6024, 6028, 6062, 6064, 6072, 6078, 6080,<br />
6081, 6083, 6086, 6103, 6113, 6120, 6127, 6128, 6144, 6527,<br />
6528, 6529, 6530, 6531, 6532, 6533, 6534, 6535, 6536, 6537,<br />
6538, 6539, 6540, 6541, 6542, 6543, 6544, 6545, 6546, 6547,<br />
6548, 6549, 6550, 6551, 6552, 6553, 6554, 6555, 6556, 6557,<br />
6558, 6559, 6560, 6561, 6562, 6563, 6564, 6565, 6566, 6567,<br />
6568, 6569, 6570, 6571, 6572, 6573, 6574, 6575, 6576, 6577,<br />
6578, 6579, 6580, 6581, 6582, 6582, 6597<br />
STNUTIL 5538, 6270, 6406, 6409, 6410, 6411, 6412, 6413, 6414, 6415,<br />
6416, 6417, 6418, 6419, 6420, 6421, 6422, 6423, 6424, 6425,<br />
6425, 6426, 6427, 6428, 6429, 6430, 6431, 6432, 6433, 6434,<br />
6435, 6436, 6437, 6438, 6439, 6440, 6441, 6442, 6443, 6444,<br />
6445, 6446, 6447, 6448, 6449, 6450, 6451, 6452, 6453, 6454,<br />
6455, 6456, 6457, 6458, 6459, 6460, 6461, 6462, 6463, 6464,<br />
6465, 6466, 6467, 6468, 6469, 6470, 6471, 6472, 6473, 6474,<br />
6475, 6476, 6477, 6478, 6479, 6480, 6481, 6482, 6483, 6484,<br />
6485, 6486, 6488, 6489, 6490, 6491, 6492, 6493, 6494, 6495,<br />
6496, 6497, 6498, 6499, 6500, 6501, 6502, 6503, 6504, 6505,<br />
6506, 6507, 6508, 6509, 6510, 6511, 6512, 6513, 6514, 6515,<br />
6516, 6517, 6518, 6519, 6520, 6521, 6522, 6523, 6524, 6525,<br />
6526<br />
The per<strong>for</strong>mance <strong>and</strong> functionality of the ROC (Report Output Control) system on<br />
<strong>OS</strong> <strong>2200</strong> has been enhanced. The new implementation reduces competing access to the<br />
ROC database.<br />
To help you migrate to ROC release 3R1A, two Migration Reports are provided:<br />
• ROCEXT is provided as an EIF. Run ROCEXT against LINC release 16R3 to extract<br />
some or all of your ROC database to extract files.<br />
• ROCLOAD is provided on the Enterprise Application Environment release 3R1A<br />
media. When you have installed ROC release 3R1A, run ROCLOAD to load the<br />
extract files into the new ROC database.<br />
78616323–000 4–9
Migrating to Release 3R1A<br />
Graphical Interface Workbench Release 3R2<br />
Updating Graphical Interface Workbench Scripts<br />
Be<strong>for</strong>e running any Graphical Interface Workbench-capable Systems that have been<br />
migrated from a release prior to release 16R3, change your existing master scripts to use<br />
the WDP16 window rather than running the WDPSTATIONS program.<br />
If you have migrated your System from release 16 to release 3R1A, you can continue to<br />
use your existing scripts. You require new scripts if your host does not have a WDP16<br />
window defined. These scripts are available in the latest Interim Corrections (ICs) <strong>for</strong><br />
released versions of PCE.<br />
Using Graphical Interface Workbench<br />
If you do not wish to use Graphical Interface Workbench, set the DW capable system<br />
field on the System Environmental Options screen to N.<br />
If you intend to use Graphical Interface Workbench, be<strong>for</strong>e generating any migrated<br />
Graphical Interface Workbench-capable system, use the Designer Workbench Options<br />
screens to enter values corresponding to the in<strong>for</strong>mation in your existing WDPMAP file.<br />
Migrating existing Graphical Interface Workbench screens<br />
Release 3R1A supports Graphical Interface Workbench release 3R2. By using Graphical<br />
Interface Workbench release 3R2, you can make many <strong>for</strong>m changes at your PC without<br />
causing the screen layouts to be downloaded from the host.<br />
Caution<br />
If you make changes, you are responsible <strong>for</strong> ensuring that the data item<br />
definitions in the <strong>for</strong>ms match those defined in your System.<br />
4–10 78616323–000
Generating Your Systems after Migration<br />
Note: Release 3R1A will only generate UCS COBOL code.<br />
Migrating to Release 3R1A<br />
To generate your migrated Specifications, per<strong>for</strong>m the following procedure:<br />
1. Sign on to Host Builder <strong>for</strong> release 3R1A.<br />
2. Log on to a migrated Specification.<br />
Note: For Modules, you must complete a syntax-only generate of the Module<br />
Master (including all Reports) be<strong>for</strong>e you generate any Modules.<br />
3. Access the Generate screen. Enter N in the Stop on first error field, <strong>and</strong> Y in the<br />
Syntax only field, <strong>and</strong> generate the System.<br />
The first System generate following migration may take longer than at other times.<br />
4. Correct any errors found.<br />
Note: If your Specification contains nested Per<strong>for</strong>mable Global Logics that bring data<br />
into memory, errors may be reported where an Ispec manipulates data read in by a<br />
Per<strong>for</strong>mable Global Logic. The error can be resolved by including a dummy read, or by<br />
repositioning the logic that per<strong>for</strong>ms the read.<br />
5. At this point, you may wish to run the CONVINIT <strong>and</strong> CONVDATE reports, so that you<br />
can take advantage of release 3R1A features. See “Addressing Migration Issues” on<br />
page 4–4.<br />
6. Access the Generate screen again. Enter Y in the Stop on first error field, <strong>and</strong> N in<br />
the Syntax only field, <strong>and</strong> generate the System.<br />
7. When your system generation <strong>and</strong> reorganization are complete, generate all Reports.<br />
8. If you are using System Transfer <strong>and</strong> Configure <strong>for</strong> your Systems, per<strong>for</strong>m the<br />
transfer <strong>and</strong> configure now.<br />
Caution<br />
Do not start up your System until the generation process has been fully<br />
completed.<br />
78616323–000 4–11
Migrating to Release 3R1A<br />
4–12 78616323–000
Appendix A<br />
Files Created by Enterprise Application<br />
Environment<br />
This appendix contains the following in<strong>for</strong>mation on the files created by Enterprise<br />
Application Environment:<br />
• Conventions Used in This Appendix<br />
• Installing <strong>Runtime</strong><br />
• Installing Host Builder<br />
• Configuring <strong>and</strong> Generating Systems<br />
Conventions Used in This Appendix<br />
The following conventions are used in this appendix.<br />
The runtime parameter indicates the name of the <strong>Runtime</strong>.<br />
The system parameter indicates the name of the Enterprise Application Environment<br />
System, whether it is a generated System, or Unisys-supplied software (<strong>for</strong> example,<br />
Host Builder).<br />
78616323–000 A–1
Files Created by Enterprise Application Environment<br />
Installing <strong>Runtime</strong><br />
File Names<br />
The following files are created when installing <strong>Runtime</strong>:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
The PERM$SGS file is created when <strong>Runtime</strong> is installed. The parameters in this file<br />
describe the system settings, <strong>and</strong> you can add additional SGSs after them. Do not delete<br />
these SGSs. For a description of SGS parameters, see your Unisys e-@ction Enterprise<br />
Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
The LINC$GLADTR$ file is created on all <strong>OS</strong> <strong>2200</strong> based hosts, but is used primarily on<br />
XTC systems.<br />
RDMS Storage Areas<br />
A number of RDMS storage areas are created that contain the RDMS tables listed in the<br />
following table.<br />
Storage Area<br />
File Name Table Name Description<br />
SA$ CONFIG COMUS details<br />
LSYS Details of all <strong>OS</strong> <strong>2200</strong> based Systems in<br />
current <strong>Runtime</strong><br />
PIDRANGES Ranges of valid PIDs<br />
SERVICES OLTP Service Names<br />
STNDEFAULT Initial station record info.<br />
SA$RI REPORTINFO Active Reports<br />
SA$RII Index <strong>for</strong> SA$RI<br />
SA$RR REPORTSRUN Completed Reports used in recovery<br />
SA$SI SECURINT Development System Security In<strong>for</strong>mation<br />
SA$SII Index <strong>for</strong> SA$SI<br />
A–2 78616323–000
Files Created by Enterprise Application Environment<br />
Storage Area<br />
File Name Table Name Description<br />
SA$SU SECURITY Security in<strong>for</strong>mation<br />
SA$SUI Index <strong>for</strong> SA$SU<br />
SA$ACC ACCEPTS SA$ACC<br />
SA$ACCI Index <strong>for</strong> SA$ACC<br />
SA$APID ACTIVEPIDS Clears PIDs during background run recovery<br />
BCAST$ BCAST Flags <strong>for</strong> recovery of AUTOs<br />
BCAST$PRO BCAST_PRO Critical point data <strong>for</strong> Reports<br />
Note: The BCAST <strong>and</strong> BCAST_PRO tables are only created <strong>for</strong> shared application groups<br />
on XTC hosts.<br />
Using Special Printing Attributes<br />
The following files are created as sample files that must be modified if you wish to use<br />
special printing attributes. For more in<strong>for</strong>mation, see your Unisys e-@ction Enterprise<br />
Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
<br />
<br />
78616323–000 A–3
Files Created by Enterprise Application Environment<br />
Installing Host Builder<br />
When you install Host Builder, files from the Release tape are copied to mass storage.<br />
The following files need to be secured:<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
These files are cataloged on mass storage with the V option (ineligible <strong>for</strong> rollout).<br />
A–4 78616323–000
Files Created by Enterprise Application Environment<br />
Configuring <strong>and</strong> Generating Systems<br />
The following files are created when configuring <strong>and</strong> generating a System.<br />
File Description<br />
system*SYS$LIB. System configuration in<strong>for</strong>mation plus some ECL (<strong>for</strong> example,<br />
LINC$CNTL, RDML$EXT, COPY$ECL)<br />
system*TRX$SYM. Ispec logic symbolics<br />
system*TRX$REL. Ispec logic relocatables<br />
system*TRX$ABS. Ispec logic absolutes<br />
system*SCR$SYM. Ispec Screen subprogram symbolics<br />
system*SCR$REL. Ispec Screen subprogram relocatables<br />
system*GEN$RUN. System generation runstreams <strong>for</strong> BATCH processing, serial or split<br />
runs<br />
system*PDP$LIB. Common database access code<br />
system*REP$SYM. Report symbolics (if Reports exist)<br />
system*REP$REL. Report relocatables (if Reports exist)<br />
system*REP$ABS. Report absolutes (if Reports exist)<br />
system*REP$RUN. Report runstreams (if Reports exist)<br />
runtime*systemP$. HVTIP library containing subprogram banks (ICP <strong>and</strong> Ispecs) of the<br />
System. For UCS Subsystems, it is a SUPUR library containing the<br />
st<strong>and</strong>ard TIP ICP used to access the Subsystem.<br />
system*TRX$SSDP. UCS Subsystem definition, registered with the operating system<br />
during SOLAR PRODLD. Exclusively assigned to the Exec until the<br />
Subsystem is deactivated. (It is not created <strong>for</strong> HVTIP Systems).<br />
runtime*systemS$. Subsystem library of object modules. Exclusively assigned to the<br />
Exec until the Subsystem is deactivated. (It is not created <strong>for</strong> HVTIP<br />
Systems).<br />
Note: The runtime*systemP$. file is only valid if you are not using HVTIP shared libraries.<br />
If your default duplex pack is specified then your HVTIP library will be duplexed <strong>and</strong> the file<br />
will be runtime*system$2P$.<br />
Output from Configure or Generate<br />
The P$ file is cycled, enabling you to access previous runs. Each Report Batch generate<br />
<strong>and</strong> Individual Report generates use one cycle of the P$ file.<br />
If you choose to split runs <strong>for</strong> your generate or configure, the following files are created.<br />
• For PGEN phase:<br />
78616323–000 A–5
Files Created by Enterprise Application Environment<br />
<br />
• For compile phase:<br />
<br />
• For maps phase:<br />
<br />
Possible n values range from 2 to the number of splits specified.<br />
Database Files<br />
The following database files are created when configuring or generating a System.<br />
The tip value is the TIP number. Valid length <strong>for</strong> the TIP number is six digits, <strong>for</strong> example,<br />
000230. The database value is the name of your database, ispec is an Ispec name, <strong>and</strong><br />
profile is a Profile name.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
A–6 78616323–000
Appendix B<br />
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR<br />
<strong>Installation</strong> Parameters<br />
This appendix lists the parameters required <strong>for</strong> each stage of COMUS configuration <strong>and</strong><br />
SOLAR installation of your Enterprise Application Environment Software. Instructions <strong>for</strong><br />
these stages are given in “Installing Enterprise Application Environment Software” on<br />
page 3–1. This appendix covers the following topics:<br />
• COMUS <strong>Configuration</strong> Main Menu<br />
• General <strong>Configuration</strong> Parameter Screens<br />
• Processor File Names Screens<br />
• Common Bank Attributes Screen<br />
• Additional I-Language Banks Screen<br />
• HUB <strong>Configuration</strong> Parameters Screens<br />
• OLTP <strong>Configuration</strong> Parameters Screen<br />
• LRSS <strong>Configuration</strong> Parameters Screen<br />
• COMUS Run Parameters<br />
<strong>Configuration</strong> parameters <strong>and</strong> defaults <strong>for</strong> installing a System that will communicate with<br />
the OLTP environment are described in your Unisys e-@ction Enterprise Application Host<br />
Builder <strong>Guide</strong>.<br />
Stages of the <strong>Configuration</strong> <strong>and</strong> <strong>Installation</strong> Process<br />
The stages of the COMUS configuration <strong>and</strong> SOLAR installation process are listed in the<br />
following table.<br />
Stage Process Description<br />
1 Register (COMUS) Register the Release tape with COMUS.<br />
2 Configure Set the configuration parameters to customize <strong>for</strong> your site.<br />
3 Build Build a copy of <strong>Runtime</strong> (if you have altered the parameters).<br />
4 Register (SOLAR) Register the output of the <strong>Runtime</strong> with SOLAR.<br />
5 Install Install a copy of <strong>Runtime</strong>.<br />
If you do not change any parameters, that is you accept all of the default values on your<br />
first install, you do not need to run the Build step.<br />
78616323–000 B–1
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Any time after <strong>Runtime</strong> is installed, you may change your configuration, <strong>and</strong> rebuild/<br />
reinstall with new parameters.<br />
B–2 78616323–000
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
COMUS <strong>Configuration</strong> Main Menu<br />
The COMUS <strong>Configuration</strong> Main Menu enables you to navigate to seven other<br />
configuration screens.<br />
• General <strong>Configuration</strong> Parameter Screens<br />
• Processor File Names Screens<br />
• Common Bank Attributes Screen<br />
• Additional I-Language Banks Screen<br />
• HUB <strong>Configuration</strong> Parameters Screens<br />
• OLTP <strong>Configuration</strong> Parameters Screen<br />
• LRSS <strong>Configuration</strong> Parameters Screen<br />
From the Home position, enter the number <strong>for</strong> the group of configuration parameters you<br />
want to access <strong>and</strong> transmit. The screens <strong>and</strong> individual parameters <strong>for</strong> each of the seven<br />
possible groups are described in the following subsections.<br />
Hints on Navigating <strong>and</strong> Online Help<br />
The <strong>Configuration</strong> parameter screens are accessed from the <strong>Configuration</strong> Main Menu<br />
screen.<br />
For online help, enter a question mark (?) at the top of the screen <strong>and</strong> transmit.<br />
Some of these screens have continuation screens. To display a continuation screen, enter<br />
a plus sign (+) at the Home position. To return to a previous screen from a continuation<br />
screen, enter a minus sign (-) at the Home position.<br />
To return to the <strong>Configuration</strong> Main Menu, enter b in the Home position of any screen.<br />
To return to a previous screen from a continuation screen, enter a minus sign (-) at the<br />
Home position.<br />
78616323–000 B–3
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
General <strong>Configuration</strong> Parameter Screens<br />
Use the General <strong>Configuration</strong> Parameter screens to enter the basic parameters <strong>for</strong><br />
<strong>Runtime</strong>. The various screens are described in the following subsections.<br />
General <strong>Configuration</strong> Parameter Screen 1<br />
This subsection describes the fields on General <strong>Configuration</strong> Parameter Screen 1.<br />
<strong>Runtime</strong> Name<br />
Enter the name <strong>for</strong> the <strong>Runtime</strong> you are configuring. You may want to install more than<br />
one copy of <strong>Runtime</strong>. The default name is LINC3R1.<br />
Each <strong>Runtime</strong> name must be unique <strong>and</strong> may contain up to eight characters, the first of<br />
which must be alphabetic. The <strong>Runtime</strong> name is used as a qualifier <strong>for</strong> your <strong>OS</strong> <strong>2200</strong><br />
based production files, <strong>and</strong> is the name you use with the BUILD comm<strong>and</strong>. The<br />
maximum length is eight characters to prevent the runtime$Lxx <strong>and</strong> runtime$Rxx<br />
Common Bank names from exceeding the maximum length of 12 characters.<br />
It is advisable to use the same name as you specified <strong>for</strong> your COMUS Config Set Name.<br />
Background Run RUNID<br />
Enter the name of the runstream created in SYS$LIB$*RUN$ to start the Background<br />
Run. The value that you enter is the run id of that run. This name must be a unique run id<br />
of up to six characters in length.<br />
It is advisable to use your <strong>Runtime</strong> name <strong>for</strong> your Background Run id.<br />
The default value is L3R1.<br />
<strong>Configuration</strong> Description<br />
Use these three fields to enter an optional description of this particular configuration. Up<br />
to three lines of text are available.<br />
Each description line may be up to 32 characters long.<br />
The default is spaces.<br />
Application Name<br />
Use this field to enter the name of the Application Group in which you wish to install<br />
<strong>OS</strong> <strong>2200</strong> based <strong>Runtime</strong>. The default is UDSSRC.<br />
The Application Name identifies a recoverable element to the operating system, the<br />
recovery system (IRU), <strong>and</strong> the data manager (UDS).<br />
B–4 78616323–000
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Application group names have an associated Application Number, which is also a<br />
configuration parameter. The Application Number you specify must relate to the<br />
application name that you enter. Consult your Site Administrator about the choice of<br />
Application Group.<br />
Real Application Names are required, as aliases are not valid.<br />
Application Number<br />
Enter the number of the Application Group in which you wish to install <strong>OS</strong> <strong>2200</strong> based<br />
Enterprise Application Environment. The valid range is 1 through 16. The default value is<br />
3.<br />
The Application Number you specify must relate to the Application Name. For more<br />
details, see the Application Name parameter.<br />
HVTIP Base Library Number<br />
Enter the base TIP file number <strong>for</strong> your HVTIP libraries. This number may contain up to<br />
four characters, <strong>and</strong> it must match the value of the TPLIB operating system configuration<br />
parameter in your EXEC generation. The default is 17.<br />
Consult your Site Administrator about the base TIP file number <strong>for</strong> your installation.<br />
System Files Equipment<br />
Each copy of <strong>Runtime</strong> maintains control in<strong>for</strong>mation in RDMS tables. Use this field to<br />
enter the equipment type of the unit where the associated RDMS storage area is to be<br />
located. The default is F, which locates the files on fixed mass storage.<br />
Note: Several environment files are created external to COMUS, <strong>and</strong> these files are also<br />
created on the specified equipment type.<br />
You may enter up to eight characters. For related in<strong>for</strong>mation, see the System Files<br />
Packids parameter.<br />
System Files Packids<br />
If you leave this parameter blank (the default), the storage area is placed on fixed mass<br />
storage. The maximum length of this field is 32 characters.<br />
Enter the packid of the unit where your Control storage area <strong>and</strong> other associated files are<br />
to be located.<br />
If multiple packids are required, enter them consecutively, separating them with a slash<br />
character (/), as shown in the following example.<br />
<br />
The packs specified have the same equipment type that you specify in the System Files<br />
Equipment parameter.<br />
78616323–000 B–5
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
System Files ACR Name<br />
Control in<strong>for</strong>mation <strong>for</strong> <strong>Runtime</strong> is maintained in RDMS tables. Use this field to enter the<br />
ACR name to be used when cataloguing the file containing these tables.<br />
You may enter up to six characters. Additional equipment files also have this ACR on their<br />
catalogue. For more details, see your <strong>OS</strong> <strong>2200</strong> SIMAN User Reference Manual.<br />
Note: Security <strong>for</strong> RDMS tables should be established with care, as all transactions have<br />
to pass this ACR.<br />
General <strong>Configuration</strong> Parameter Screen 2<br />
This subsection describes the fields on General <strong>Configuration</strong> Parameter Screen 2.<br />
Common Bank BDI Parameters<br />
Common Bank BDI parameters <strong>for</strong> the Configure stage are described as follows.<br />
LINC$TABLES BDI<br />
Enter the BDI <strong>for</strong> the LINC$TABLES Common Bank. You must enter all seven characters,<br />
including the leading zero. The LINC$TABLES Common Bank contains data structures<br />
that are used to coordinate the operation of <strong>Runtime</strong>.<br />
Each copy of <strong>Runtime</strong> must have a separate set of Common Banks. It is advisable that<br />
LINC$TABLES <strong>and</strong> LINC$SUBS use consecutive BDIs; <strong>for</strong> example, 0402676 <strong>and</strong><br />
0402677.<br />
The default value is 0402676.<br />
LINC$SUBS BDI<br />
Enter the BDI <strong>for</strong> the LINC$SUBS Common Bank. You must enter all seven characters,<br />
including the leading zero. The LINC$SUBS Common Bank contains subroutines used in<br />
the execution of your Systems.<br />
Be<strong>for</strong>e entering these BDIs, check that they are not already in use. These numbers are<br />
shown as a sample set in your UDS <strong>Installation</strong> <strong>Guide</strong>, <strong>for</strong> application group 8. Consult<br />
your Site Administrator about the choice of BDIs.<br />
See also the LINC$TABLES BDI parameter.<br />
The default is 0402677.<br />
LINC$EMCB BDI<br />
Use this field to enter the BDI <strong>for</strong> the LINC$EMCB Common Bank. You must enter all<br />
seven characters, including the leading zero. The LINC$EMCB Common Bank contains<br />
subroutines used in the execution of your UCS Systems.<br />
The default is 0404615.<br />
B–6 78616323–000
See also the other BDI parameters.<br />
LINC$SRCEC BDI<br />
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Enter the BDI <strong>for</strong> the LINC$SRCEC Common Bank. You must enter all seven characters,<br />
including the leading zero. The LINC$SRCEC Common Bank contains COBOL templates<br />
used by Host Builder.<br />
See also the other BDI parameters.<br />
The default is 0404616.<br />
LINC$STN BDI<br />
Enter the BDI <strong>for</strong> the LINC$STN Common Bank. You must enter all seven characters,<br />
including the leading zero, in extended mode <strong>for</strong>mat e.g. 020xxxx. The LINC$STN<br />
Common Bank contains the subsystem used to store station data associated with<br />
GLB.WORK in memory. Other S_T_N station data will continue to use RDMS Table or<br />
FCSS file.<br />
The default is 0205110.<br />
LINC$VLOG BDI<br />
Enter the BDI <strong>for</strong> the LINC$VLOG Common Bank. You must enter all seven characters,<br />
including the leading zero. See also the other BDI parameters. The LINC$VLOG Common<br />
Bank contains templates used <strong>for</strong> the editing facilities within Host Builder.<br />
The default is 0404617.<br />
LINC$RTS BDI<br />
Enter the BDI <strong>for</strong> the LINC$RTS Common Bank. You must enter all seven characters,<br />
including the leading zero, in extended mode <strong>for</strong>mat e.g. 020xxxx.<br />
The LINC$RTS Common Bank contains UCS support routines created as a chameleon<br />
fast-load self-contained subsystem (FLSS), a shared subsystem which provides <strong>for</strong> fast<br />
loading of local unshared data<br />
The default is 0205471<br />
LINC$L01 BDI<br />
Enter the BDI <strong>for</strong> the Common Bank into which the ILANGUAGE file containing message<br />
texts <strong>for</strong> Host Builder will be loaded. The default is 0404645. You must enter all seven<br />
characters, including the leading zero.<br />
This is the Common Bank BDI <strong>for</strong> the primary language only. If you have a multiple<br />
language Host Builder, select the Additional I-Language Banks (ILANGUAGE) set of<br />
parameters to specify your LINC$L02 to LINC$L15 BDIs.<br />
78616323–000 B–7
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
General <strong>Configuration</strong> Parameter Screen 3<br />
This subsection describes the fields on General <strong>Configuration</strong> Parameter Screen 3.<br />
EIS Capable Host<br />
Enter Y to specify that <strong>Runtime</strong> is to run on an Extended Instruction Set (EIS) machine.<br />
EIS is a hardware feature which gives faster character h<strong>and</strong>ling, <strong>and</strong> is available on all<br />
<strong>OS</strong> <strong>2200</strong> based machines.<br />
Enter N if EIS does not apply. The default is Y.<br />
Print Queue <strong>for</strong> Error Dumps<br />
Enter the print queue in which you wish any TIP printed output or post mortem dumps to<br />
be placed. You may enter up to four characters. The default is PR. This value applies to all<br />
<strong>OS</strong> <strong>2200</strong> based Systems within <strong>Runtime</strong>, but it can be overridden at system level.<br />
Network Host ID <strong>for</strong> this System<br />
Enter the Host id <strong>for</strong> the machine your <strong>Runtime</strong> runs on, as defined to your TELCON<br />
software. This is used in the global host parameters, enabling <strong>OS</strong> <strong>2200</strong> based Systems<br />
running on other hosts to access your <strong>OS</strong> <strong>2200</strong> based System.<br />
You can enter up to six alphanumeric characters. The value entered is automatically<br />
stored in the System Data item GLB.SELFH<strong>OS</strong>T, <strong>and</strong> is automatically moved to<br />
GLB.ORIGINH<strong>OS</strong>T when an external Automatic Entry is per<strong>for</strong>med.<br />
The default value is six space characters, which provides no host ID. That is, your System<br />
is not accessible to <strong>OS</strong> <strong>2200</strong> based Systems running on other hosts.<br />
On XTC systems, select one Network Host id to represent all the closely coupled hosts.<br />
For example, if your system consists of hosts with network ids NY01, NY02, NY03, <strong>and</strong><br />
NY04, you can select NY01 to represent the entire system. This causes the entire XTC<br />
system to be treated as a single host.<br />
ROC Transaction ID<br />
Enter the TIP transaction id to be used to sign on to your Report Output Control System<br />
(ROC).<br />
Up to six alphanumeric characters may be used. The default is RT3R1.<br />
ROC Database Name<br />
Enter the database name to be used <strong>for</strong> your Report Output Control System (ROC). The<br />
name is used as a qualifier <strong>for</strong> the ROC database files. The name must not exceed seven<br />
alphanumeric characters. The default is RD3R1.<br />
ROC Spooler Transaction ID<br />
Enter the TIP transaction id to be used by the ROC spooler to receive transaction input.<br />
B–8 78616323–000
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
You can enter up to six alphanumeric characters. The default is RQ3R1.<br />
ROC Environment Name<br />
You can use a ROC System which runs in a different copy of <strong>Runtime</strong> to the <strong>Runtime</strong> you<br />
are installing. Use this field to enter the name of the <strong>Runtime</strong> in which ROC is to run.<br />
You may enter up to ten characters. The default is spaces, which is the <strong>Runtime</strong> you are<br />
currently installing.<br />
ROC Spooler Queuing Node<br />
Enter the Queue Priority node used by the ROC Spooler to receive transaction input.<br />
Node numbers can be in the range from 1 through 99999. The node used must already<br />
have been defined in an EXEC gen, with a QMAX parameter of zero. This node must not<br />
be in current use.<br />
The default is 10.<br />
Maximum Number of PIDs<br />
Enter the maximum number of terminals that can be simultaneously connected to<br />
Systems within the current copy of <strong>Runtime</strong>. Enter up to five numeric characters.<br />
This parameter controls the size of the ACTIVEPIDS Table in the LINC$TABLES Common<br />
Bank, which is used to scan <strong>for</strong> terminals that may be timed out.<br />
The default is 1000.<br />
Idle Terminal Timeout (min)<br />
Enter the time (in minutes) that a terminal is to remain in idle status. Enter up to four<br />
numeric characters. After this time, a BYE will be automatically issued by the Background<br />
Run, to sign the terminal off the System.<br />
Multiple PIDs on the same physical terminal are monitored separately.<br />
The default value is 30.<br />
Timeout Check Interval (sec)<br />
Enter the time interval (in seconds) between checks <strong>for</strong> idle terminals. This value<br />
specifies how often the Background Run scans through the ACTIVEPIDS table.<br />
The default value is 60.<br />
Unsuitable values <strong>for</strong> this parameter may affect per<strong>for</strong>mance.<br />
Clear AUX area in MCB packet<br />
Enter Y if you have an XIS/AIS environment. This in<strong>for</strong>ms MCB not to call its error<br />
h<strong>and</strong>ling routine.<br />
78616323–000 B–9
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
The default is N.<br />
B–10 78616323–000
Processor File Names Screens<br />
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Use the Processor File Names screens to name the various software packages used to<br />
operate or build your copy of <strong>Runtime</strong>.<br />
Entering Parameters<br />
All parameters have a maximum length of twenty-five alphanumeric characters.<br />
Processor File Names Screen 1<br />
This subsection describes the fields on Processor File Names Screen 1.<br />
COBOL Compiler (@ACOB)<br />
Enter the name of the COBOL compiler file. Do not enter a trailing period after the file<br />
name.<br />
The default is SYS$LIB$*ACOB.<br />
UCOB UCS COBOL Compiler<br />
Enter the name of the UCOB COBOL Compiler file.<br />
Do not enter a trailing period after the file name. The default is SYS$LIB$*UCOB.<br />
Note: If a UCOB compiler file is specified, the U---U Ispec is always compiled with the<br />
UCOB compiler in addition to ACOB. This allows UCS Reports to link correctly.<br />
Collector (@MAP)<br />
Enter the name of the Collector processor file. Do not enter a trailing period after the file<br />
name.<br />
The default is SYS$LIB$*MAP.<br />
Data Dictionary (@DD)<br />
Enter the name of the Data Dictionary processor file. Do not enter a trailing period after<br />
the file name.<br />
The default is SYS$LIB$*UREP.<br />
ACOB TIP Library<br />
Enter the name of the ACOB TIP library file. Do not enter a trailing period after the file<br />
name.<br />
The default is SYS$LIB$*ACOB-TIPLIB.<br />
78616323–000 B–11
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
File Containing ACOB CBEP$<br />
Enter the name of the file containing the COBOL Common Bank entry point table. Ensure<br />
that the CBEP$ file you specify matches the COBOL compiler you have specified. Do not<br />
enter a trailing period after the file name.<br />
The default is SYS$LIB$*ACOB-DML.<br />
ACOB Library<br />
Enter the name of the ACOB library file. Do not enter a trailing period after the file name.<br />
The default is SYS$LIB$*ACOB.<br />
TIP RUN$ File<br />
Enter the name of the TIP RUN$ file. Do not enter a trailing period after the file name.<br />
The default is TIP$*TIPRUN$.<br />
TIP LIB$ File (<strong>for</strong> MCB)<br />
Enter the name of the TIP library file containing the MCB interface routines <strong>for</strong> the<br />
application group within which your <strong>OS</strong> <strong>2200</strong> based System runs. Do not enter a trailing<br />
period after the file name.<br />
The TIP LIB$ file contains TIP primitive subroutines <strong>and</strong> the MCB interface routines. The<br />
MCB interface routines may be specific to each application group, depending on the<br />
method used when they were installed. For more details, see the <strong>OS</strong> <strong>2200</strong> TIP<br />
<strong>Installation</strong> <strong>Guide</strong>.<br />
The default is TIP$*TIPLIB$.<br />
File Containing CBEP$$MCB<br />
Enter the file name containing the CBEP$$MCB relocatable element <strong>for</strong> the application<br />
group previously specified <strong>for</strong> this configure. Do not enter a trailing period after the file<br />
name.<br />
The relocatable element CBEP$$MCB is used during the collection of an <strong>OS</strong> <strong>2200</strong> based<br />
System to identify the MCB Common Banks. The MCB Common Bank is different <strong>for</strong><br />
each application group.<br />
The default is MCB3*MCB$.<br />
UC UCS C Compiler<br />
Enter the name of the UC C Compiler file (commonly named SYS$LIB$*UC). Do not enter<br />
a trailing period after the file name.<br />
UC is required <strong>for</strong> the generation of OLTP UCS server systems.<br />
The default is *NONE*.<br />
B–12 78616323–000
Processor File Names Screen 2<br />
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
This subsection describes the fields on Processor File Names Screen 2.<br />
RSA Relational Syntax Analyzer<br />
Enter the name of the RSA library file associated with the application group within which<br />
your <strong>OS</strong> <strong>2200</strong> based System runs. Do not enter a trailing period after the file name.<br />
The default is SYS$LIB$*RSA.<br />
RSA Extended Mode Interface<br />
Enter the name of the RSA library file <strong>for</strong> the extended mode interface. If you do not<br />
intend using UCS mode, enter *NONE* in the UCOB UCS COBOL Compiler fields.<br />
Do not enter a trailing period after the file name.<br />
This is no longer a separate file, <strong>and</strong> it is included in the RSA file. If applicable, enter the<br />
same file name that you enter in the RSA Relational Syntax Analyzer field,<br />
described earlier in this subsection.<br />
If you are installing Host Builder, you must have installed LINK <strong>and</strong> the RSA Extended<br />
Mode Interface. Enter the processor file names in the appropriate fields.<br />
RDMS Relational Data Manager<br />
Enter the name of the RDMS library file associated with the application group within<br />
which your <strong>OS</strong> <strong>2200</strong> based System runs. Do not enter a trailing period after the file name.<br />
The default is SYS$LIB$*RDMS.<br />
ASSEMBLER (@MASM)<br />
Enter the name of the MASM processor file. Do not enter a trailing period after the file<br />
name.<br />
The default is SYS$LIB$*MASM.<br />
PDP Processor (@PDP)<br />
Enter the name of the file containing the PDP processor. Do not enter a trailing period<br />
after the file name.<br />
The default is SYS$LIB$*PDP.<br />
DDP Relocatable File Name<br />
The default is SYS$LIB$*DDP-PPC-1. If you intend to use Automatic Entries between<br />
hosts, SYS$LIB$*DDP-PPC-1 is the usual file name.<br />
78616323–000 B–13
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Enterprise Application Environment may use the DDP-PPC DCA interface <strong>for</strong> Automatic<br />
Entries between hosts. Use this field to identify the file containing the DDP-PPC DCA<br />
relocatable elements. This is used to create the HUBDDP server program.<br />
DDN Relocatable File Name<br />
Enter the file containing the DDP-PPC TCP/IP relocatable elements. This value is used in<br />
creating the HUBDDN program. (Enterprise Application Environment may use the DDP-<br />
PPC TCP/IP interface <strong>for</strong> Automatic Entries between hosts.)<br />
The default is SYS$LIB$*DDP-PPC-4. If you intend to use Automatic Entries between<br />
hosts, this is the usual file name.<br />
LINK Program Linker<br />
Enter the name of the LINK program linker. Do not enter a trailing period after the file<br />
name.<br />
LINK is part of the operating system, <strong>and</strong> is required in the <strong>Runtime</strong> build.<br />
The default is SYS$LIB$*LINK.<br />
IRU Integrated Recovery Utility<br />
Enter the name of the file containing the IRU processor. Do not enter a trailing period after<br />
the file name.<br />
The default is SYS$LIB$*IRU.<br />
ARC File name<br />
Enter the name of the file containing the CBEP$$ARC relocatable if you require Automatic<br />
Recovery (ARC). ARC recovery is specifically <strong>for</strong> the Background Run. SYS$LIB*ARC is<br />
the usual name <strong>for</strong> the ARC file. If you do not require this feature, choose the default<br />
value of *NONE*.<br />
If a file is specified in this field, the Background Run is built so that it registers with ARC<br />
<strong>for</strong> software component recovery. ARC restarts the Background Run if an error causes<br />
termination.<br />
B–14 78616323–000
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Common Bank Attributes Screen<br />
Use this screen to change the parameters controlling the data structures in the<br />
LINC$TABLES Common Bank.<br />
These parameters control the data structures in the LINC$TABLES Common Bank.<br />
Note: You would not usually change the default settings without specific instructions<br />
from your Unisys Support Center.<br />
Work Queue Size<br />
Enter a value in the range 1 through 999 is valid. The default is 200.<br />
A work queue entry is made in the tables Common Bank <strong>for</strong> some of the requests to the<br />
Background Run. The logic comm<strong>and</strong>s SLEEP;, MSG;, ACCEPT;, RUN;, <strong>and</strong> STOP;<br />
generate work queue entries. The work queue must be big enough to hold all of the<br />
requests that can be active or pending at any one time.<br />
Number of Slots<br />
Enter a value from 1 through 999. The default is 250.<br />
Data structures called slots exist in the LINC$TABLES Common Bank. A slot is allocated<br />
<strong>for</strong> each request being serviced by the Background Run. A request could be a SLEEP;,<br />
MESSAGE;, SEND.MESSAGE;, ACCEPT;, or RUN; logic comm<strong>and</strong> or a :RUN System<br />
comm<strong>and</strong>.<br />
Number of Items in the Pool<br />
Pool Size<br />
Under normal circumstances, the default of 50 should be used.<br />
The Pool is an area of memory used to hold database records. This field determines how<br />
many database records can be h<strong>and</strong>led by the pool at any one time.<br />
Under normal circumstances, the default of 10,000 should be used.<br />
The Pool is an area of memory used to hold database records. This field defines the size<br />
of the Pool (in words).<br />
Maximum Number of Systems<br />
Enter a number in the range 1 through 999. The default is 64.<br />
78616323–000 B–15
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
This field contains the maximum number of Enterprise Application Environment Systems<br />
that you want to run simultaneously under this <strong>Runtime</strong>.<br />
B–16 78616323–000
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Additional I-Language Banks Screen<br />
The BDI <strong>for</strong> the ILANGUAGE Common Bank <strong>for</strong> your Primary language is entered on the<br />
General <strong>Configuration</strong> Parameters screen, described earlier in this feature.<br />
If you intend having Host Builder messages translated, you must specify Common Bank<br />
BDIs <strong>for</strong> your secondary languages on the Additional I-Language Banks screen. Up to<br />
fourteen secondary languages may be specified.<br />
Additional I-Language Banks<br />
If you intend to have a multiple language Host Builder, you need to enter BDIs <strong>for</strong> the<br />
Common Banks into which your translated Host Builder messages will be loaded.<br />
The BDI <strong>for</strong> your primary language BDI is entered on the General <strong>Configuration</strong><br />
Parameters screen. You can also make BDI entries <strong>for</strong> languages two through fifteen on<br />
this screen.<br />
The fields are labeled LINC$L02 BDI through LINC$L15 BDI.<br />
Enter up to fourteen BDIs <strong>for</strong> your secondary languages; that is, languages 2 through 15.<br />
The default value <strong>for</strong> each field is zero (0).<br />
78616323–000 B–17
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
HUB <strong>Configuration</strong> Parameters Screens<br />
Use the HUB <strong>Configuration</strong> Parameters screens to change the parameters controlling the<br />
data structures in the LINC$HUB Common Bank. The LINC$HUB Common Bank controls<br />
external Automatic Entries within multiple copies of <strong>Runtime</strong> that have the same BDI <strong>and</strong><br />
HUB identifier.<br />
The two HUB <strong>Configuration</strong> Parameter screens are described in the following<br />
subsections.<br />
HUB <strong>Configuration</strong> Parameter Screen 1<br />
This subsection describes the fields on the first HUB <strong>Configuration</strong> Parameter screens.<br />
LINC$HUB BDI<br />
Enter the BDI of the HUB Common Bank to be used by this configuration set.<br />
The default is 0404642.<br />
HUB <strong>Configuration</strong> Identifier<br />
Enter the single-character identifier <strong>for</strong> the HUB <strong>Configuration</strong> to be used by this<br />
environment. This character is used to <strong>for</strong>m the runid of the HUB Background Run<br />
controlling this configuration, as follows.<br />
<br />
Under normal circumstances, there would be only one HUB configuration <strong>for</strong> each host,<br />
but others may be defined <strong>for</strong> testing purposes. If so, you should also change the<br />
LINC$HUB BDI value. You must also make sure that the single-character identifier is<br />
unique on all hosts.<br />
The default is A.<br />
HUB <strong>Configuration</strong> Parameter Screen 2<br />
This subsection describes the fields on the second HUB <strong>Configuration</strong> Parameter screen.<br />
Work Queue Size<br />
Use this field to set the HUB work queue size. Enter a value in the range 1 through 999.<br />
The default is 200.<br />
A work queue entry is made <strong>for</strong> every Automatic Entry request made to the HUB<br />
Background Run. The work queue must be big enough to record all concurrent requests.<br />
B–18 78616323–000
Number of Slots<br />
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Data structures called slots exist in the LINC$HUB Common Bank. A slot is allocated <strong>for</strong><br />
each Auto request being serviced by the HUB Background Run.<br />
Use this field to specify the number of slots that may be used. Typically, the number of<br />
slots should be approximately 25 percent more than the sum of the number of work<br />
queue items <strong>and</strong> the number of items in the pool.<br />
Enter a value in the range 1 through 999. The default is 250.<br />
Number of Items in the Pool<br />
The Pool is an area of memory used to hold the database records being transferred to<br />
another System using an external Automatic Entry.<br />
Use this field to determine how many database records can be transferred at any one<br />
time. Enter a value in the range through 999.<br />
The default is 200.<br />
Pool Size<br />
The Pool size should be the product of the average size of database records being<br />
transferred using <strong>and</strong> external Automatic Entry, <strong>and</strong> the number of items in the Pool.<br />
Use this field to define the size of the Pool (in words). Enter a value in the range 1 through<br />
30,000.<br />
The default is 10,000.<br />
Maximum Number of Systems<br />
Use this field to specify the maximum number of Systems that you want to run<br />
simultaneously under this HUB. Enter a number in the range 1 through 999.<br />
The default is 64.<br />
Maximum Number of Hosts<br />
Use this field to control the number of independent hosts which can be connected to the<br />
HUB at one time.<br />
The default is 35.<br />
Maximum Environments / Host<br />
Use this field value to control the maximum number of copies of <strong>Runtime</strong> which can be<br />
defined in this HUB configuration. Enter a number in the range 1 through 64.<br />
The default is 4.<br />
78616323–000 B–19
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
Maximum No. of DDN Programs<br />
Use this field to control the maximum number of DDN (DDP-PPC TCP/IP) service<br />
programs associated with the HUB Background Run. Enter a number in the range 1<br />
through 64. Batch runs with the following runid will be started to service requests.<br />
<br />
The default is 4.<br />
Maximum No. of DDP Programs<br />
Use this field to control the maximum number of DDP (DDP-PPC DCA) service programs<br />
associated with the HUB Background Run. Enter a number in the range 1 through 64.<br />
Batch runs with the following runid will be started to service requests.<br />
<br />
The default is 4.<br />
Service Program Capacity<br />
Use this field to control the volume of requests each service program (DDN or DDP) may<br />
process be<strong>for</strong>e the HUB Background Run starts another service program to deal with the<br />
excess. The default is 64.<br />
OLTP <strong>Configuration</strong> Parameters Screen<br />
The OLTP <strong>Configuration</strong> Parameters screen contains two fields:<br />
• $OLTP-TM<strong>2200</strong> Qualifier<br />
• $APP-GROUP-ID<br />
Use OLTP-TM<strong>2200</strong> Qualifier to enter the name of the qualifier <strong>for</strong> the OLTP-TM<strong>2200</strong><br />
installed product filenames.<br />
Use APP-GROUP-ID to enter the name of the UDS resource manager application group.<br />
You need this entry to use the Two Phase Commit option with your System. For further<br />
details about OLTP, see your Unisys e-@ction Enterprise Application Host Builder <strong>Guide</strong>.<br />
B–20 78616323–000
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
LRSS <strong>Configuration</strong> Parameters Screen<br />
Use the LRSS <strong>Configuration</strong> Parameters screen to change the parameters controlling the<br />
Remote Subroutine Server (LRSS).<br />
This subsection describes the fields on the LRSS <strong>Configuration</strong> Parameters screen.<br />
LINC$LRSS BDI<br />
Enter the BDI of the LRSS gate bank that is used to provide access to the TSU<br />
Subsystem <strong>for</strong> communication between Developer clients <strong>and</strong> the host. This BDI must<br />
be specified as an Application Level Extended Mode BDI. Application Level Extended<br />
Mode BDIs begin with 02 whereas Basic Mode BDIs begin with 04.<br />
The subsystem is installed by using MODE LRSS or MODE ALL at SOLAR install time.<br />
The default is 0205466.<br />
LRSS <strong>Configuration</strong> Identifier<br />
Enter the single-character identifier <strong>for</strong> the LRSS configuration to be used. This parameter<br />
identifies the LRSS TSU name to be used by this <strong>Runtime</strong>, so that A represents TSU<br />
Name LNCARS, B represents TSU Name LNCBRS, <strong>and</strong> so on.<br />
It is also used to <strong>for</strong>m the runid of the TCP/IP server, as follows:<br />
<br />
The default is A.<br />
Notes:<br />
• Under normal circumstances, there would be only one LRSS configuration <strong>for</strong> each<br />
host, but you may want to nominate another <strong>for</strong> testing purposes. If so, you should<br />
also change the LINC$LRSS BDI value. You must also make sure that the singlecharacter<br />
LRSS configuration identifier is unique on all hosts.<br />
• The configuration file is referenced by the name TSUname*TSUname, <strong>and</strong> the<br />
element name is CONFIG. So if you enter A <strong>for</strong> the configuration identifier, the<br />
configuration file will be referenced by LNCARS*LNCARS.CONFIG. For details of the<br />
configuration file, see the section on Interfacing to Other Systems in your Unisys<br />
e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
The LRSS installation process creates the two dummy elements CONFIG <strong>and</strong> FILES/<br />
6009 <strong>for</strong> reference <strong>and</strong> editing. The version (6009) is the port number specified in the<br />
configuration file. If you use another port number, you should also create a<br />
corresponding FILES/port-number element. In the FILES/port-number element you<br />
should specify, in SGS <strong>for</strong>mat, the files to be searched <strong>for</strong> the Object Modules that you<br />
want to call.<br />
• The TSU must be defined in the CMS1100.<br />
78616323–000 B–21
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
COMUS Run Parameters<br />
This subsection contains in<strong>for</strong>mation on COMUS run parameters that are requested <strong>for</strong><br />
the following tasks:<br />
• First Build of <strong>OS</strong> <strong>2200</strong> Based Software<br />
• Subsequent Builds of <strong>OS</strong> <strong>2200</strong> Based Software<br />
First Build of <strong>OS</strong> <strong>2200</strong> Based Software<br />
For the first BUILD of <strong>OS</strong> <strong>2200</strong> based Software, the COMUS parameters listed in the<br />
following table are requested. You may need to set up some of the COMUS parameters<br />
detailed under “Subsequent Builds of <strong>OS</strong> <strong>2200</strong> Based Software” on page B–22.<br />
Parameter Suggested Value or Action<br />
Project id LINCBUILD<br />
Runid BLINC<br />
Run options Transmit a space<br />
Run priority Transmit <strong>for</strong> default<br />
Tape equipment For example, U9Sor HICL<br />
Tape assign options TJ (unlabeled) or TF (labeled)<br />
Generation type TAPE/TAPE<br />
Permanent SGSs Transmit a space<br />
Maximum runtime 9999<br />
Maximum pages 99999<br />
Note: If more than one build of <strong>Runtime</strong> is currently running, the Project id must not<br />
duplicate the name of an active build of <strong>Runtime</strong>.<br />
Subsequent Builds of <strong>OS</strong> <strong>2200</strong> Based Software<br />
For each subsequent BUILD of <strong>OS</strong> <strong>2200</strong> based Software, the following COMUS<br />
parameters are requested. You may need to set up some of the COMUS parameters<br />
detailed under “First Build of <strong>OS</strong> <strong>2200</strong> Based Software” on page B–22.<br />
Parameter Suggested Value<br />
MASTER reel Reel number of the Release tape or the previous BUILD<br />
output tape (see comments following the table)<br />
NEWMASTER reel Reel number of the output tape (see comments following<br />
the table)<br />
B–22 78616323–000
Reel Numbers<br />
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
The Master <strong>and</strong> Newmaster reel numbers have additional options, as follows:<br />
<br />
The options value indicates st<strong>and</strong>ard tape assign options, type is the equipment type, <strong>and</strong><br />
expiry is the number of days from the current date.<br />
Optionally, include RING or NORING to indicate whether the tape is to be loaded with or<br />
without a Write ring, respectively.<br />
For example:<br />
Parameter Suggested Value<br />
Generation id 01, 02, <strong>and</strong> so on. The generation id is displayed on the<br />
sign-on line after the version value. Do not use the<br />
apostrophe character ('). Site specific. 12 characters.<br />
Heading Optional text <strong>for</strong> your reference.<br />
Reason Optional text <strong>for</strong> your reference.<br />
New change number Transmit a space. (If installing a Unisys-supplied EIF or<br />
site-local code, enter the change number.)<br />
Type of generation UPDATE.<br />
Additional SGSs Transmit a space.<br />
<strong>Runtime</strong> name Name as used <strong>for</strong> the <strong>Runtime</strong> name on the General<br />
<strong>Configuration</strong> Parameters screen.<br />
<br />
78616323–000 B–23
COMUS <strong>Configuration</strong> <strong>and</strong> SOLAR <strong>Installation</strong> Parameters<br />
B–24 78616323–000
Appendix C<br />
Terminal <strong>and</strong> Printer Support<br />
This appendix covers:<br />
• Supported Terminal Attributes<br />
• Foreign Terminal Support<br />
Supported Terminal Attributes<br />
Data attributes that are supported by different terminal types are indicated by an x in the<br />
following table.<br />
Attribute UTS20<br />
SVT1120<br />
UTS30<br />
UTS40 UTS60 DS7<br />
BLINK x x x x<br />
BRIGHT – – – –<br />
RESET x x x x<br />
REVERSE x x x x<br />
SECURE – x x x<br />
UNDER – x x x<br />
DIM x x – x<br />
LEFTBAR – – – x<br />
RIGHTBAR – – – x<br />
UPPERSCORE – – – x<br />
UNDERSCORE – – – x<br />
KEISEN – – – x<br />
BOX – – – x<br />
Kanji (ED ;K) – – – x<br />
Mixed Data (Kanji) – – – x<br />
COLOR – – x x<br />
78616323–000 C–1
Terminal <strong>and</strong> Printer Support<br />
Implementation of Highlighting<br />
Further points to consider are:<br />
• UTS20 supports either DIM or REVERSE (but not both), depending on Control Page<br />
setting (AB/LI, AB/RV).<br />
<br />
<br />
• DIM on DS7 terminals always causes the field to be displayed in YELLOW.<br />
• On PC-emulation, Low Intensity (DIM) is configurable by the user <strong>and</strong> may actually<br />
appear as BRIGHT.<br />
• The DIM attribute may affect the color displayed on UTS60s, as shown in the<br />
following table.<br />
Color Dim Normal<br />
Ebony BLACK BLACK<br />
Blue BLUE BLUE<br />
Magenta MAGENTA HOT PINK<br />
Red RED ORANGE<br />
Green GREEN LIME<br />
Cyan CYAN CYAN<br />
Yellow BROWN YELLOW<br />
White GREY WHITE<br />
For the older Step-Board versions, low-intensity colors <strong>and</strong> normal colors are inverted.<br />
If this is the case, use the :STN System comm<strong>and</strong> to set up your terminal as type<br />
UTS60I. For more details, see “Preparing <strong>for</strong> <strong>Installation</strong> of Enterprise Application<br />
Environment Software” on page 2–1.<br />
• On PCs, the background color can only be the DIM color (that is, a yellow background<br />
will always be brown on PCs).<br />
• The only effect the BRIGHT attribute has is to override the DIM attribute. BRIGHT will<br />
carry through to REVERSE, BLINK, <strong>and</strong> so on.<br />
• When using the following attributes, every character to which they apply has to be<br />
transmitted to the screen (that is, an underlined line always results in 80 characters<br />
being sent). Normally, the suppression of trailing spaces applies, but use of the<br />
following attributes inhibit this process.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
• Underlining does not work on PCs using terminal emulation.<br />
C–2 78616323–000
Terminal <strong>and</strong> Printer Support<br />
• Although underlining does not work on PCs, Enterprise Application Environment<br />
cannot distinguish between true terminals <strong>and</strong> PC emulators, <strong>and</strong> sends the underline<br />
sequences regardless.<br />
• Delimiters are always shown as DIM, with no other attributes (except on DS7, where<br />
UPPERSCORE, UNDERLINE, <strong>and</strong> UNDERSCORE apply to the delimiters).<br />
Note: If you enter N in the Show Delimiters field on the 1100 Series System<br />
Environmental Options screen, the delimiters are spaces.<br />
Compatibility with MCP Based Systems<br />
Highlighting attributes are h<strong>and</strong>led differently in MCP based <strong>and</strong> <strong>OS</strong> <strong>2200</strong> based<br />
Systems. For MCP based Systems, a highlighting attribute is turned on by a control<br />
character that occupies the character immediately be<strong>for</strong>e a data or Display item.<br />
For <strong>OS</strong> <strong>2200</strong> based Systems, the attribute is turned on by an FCC that is contained in the<br />
first character of the data or Display item. For compatibility with MCP based Systems, a<br />
data or Display item with highlighting attributes should not start in column one.<br />
78616323–000 C–3
Terminal <strong>and</strong> Printer Support<br />
Foreign Terminal Support<br />
This subsection provides in<strong>for</strong>mation <strong>for</strong> the following tasks:<br />
• Associating a type of terminal (as identified by st<strong>and</strong>ard <strong>OS</strong> <strong>2200</strong> based<br />
communication software) with a terminal type supported by Enterprise Application<br />
Environment.<br />
• Inserting local code into Enterprise Application Environment to h<strong>and</strong>le nonst<strong>and</strong>ard<br />
terminals.<br />
Terminals Supported by Enterprise Application Environment<br />
Enterprise Application Environment supports st<strong>and</strong>ard Uniscope terminals (SVT1120,<br />
UTS20, UTS40, UTS60), Kanji-capable DS7 terminals, <strong>and</strong> IBM 3270-style terminals.<br />
Terminals Not Supported by Enterprise Application Environment<br />
Terminals not supported by Enterprise Application Environment can be dealt with in one<br />
of the following ways:<br />
• Map the unsupported terminal type to a supported terminal type. Whenever a<br />
terminal of the unsupported terminal type uses a System, Enterprise Application<br />
Environment will apply screen h<strong>and</strong>ling as <strong>for</strong> the supported terminal type.<br />
• Insert your own screen h<strong>and</strong>ling code into Enterprise Application Environment, using<br />
st<strong>and</strong>ard software hooks that are described in “Inserting Your Own Code to H<strong>and</strong>le<br />
Foreign Terminals” on page C–8. This code is associated with a special terminal type,<br />
<strong>and</strong> the mapping with the external terminal type is also required.<br />
Note: Screen h<strong>and</strong>ling code refers to the conversion of data items, Display items, <strong>and</strong><br />
Data Attributes into a series of characters <strong>and</strong> control code sequences suitable <strong>for</strong> sending<br />
to the terminal in order to display an Ispec screen (<strong>and</strong> the reverse process to h<strong>and</strong>le input).<br />
How Enterprise Application Environment Determines Terminal<br />
Types<br />
The first time a terminal is used to sign on to a System, Enterprise Application<br />
Environment determines the terminal type <strong>and</strong> stores it in the S_T_N record. This value<br />
may subsequently be changed by using the :STN System comm<strong>and</strong>, or by modifying the<br />
S_T_N record directly (<strong>for</strong> example, by using IPFSQL).<br />
Internally, Enterprise Application Environment uses a single character to define each<br />
terminal type stored in the S_T_N record. When a transaction starts, this character is read,<br />
<strong>and</strong> uses is used to insert a descriptive terminal type into GLB.STYLE <strong>and</strong> to determine<br />
which screen h<strong>and</strong>ler to use.<br />
Note: The value of GLB.STYLE must be used with the :STN comm<strong>and</strong>.<br />
C–4 78616323–000
Terminal <strong>and</strong> Printer Support<br />
The following table lists terminal types <strong>and</strong> corresponding GLB.STYLE values.<br />
Type GLB.STYLE Description<br />
3 SNA3270 IBM terminal using SNANET Uniscope emulation<br />
5 UTS20L UTS20 with Alternate Brightness = LOW<br />
6 UTS20R UTS20 with Alternate Brightness = REVERSE<br />
7 DS7<br />
8 UTS60I UTS60 with color intensities reversed<br />
A SVT1120<br />
B UTS40<br />
C UTS60<br />
D UTS20<br />
E UTS30<br />
F IBM3270 IBM terminal using native mode<br />
G IBM3178<br />
H IBM3278<br />
I IBM3279<br />
J LT300<br />
K NOFORM<br />
L NOFORM<br />
M ActiveLINC<br />
N ActiveLINC<br />
a FOREIGN Unsupported Foreign terminal type (see comment<br />
following table)<br />
b FOREIGN2 Unsupported Foreign terminal type<br />
c FOREIGN3 Unsupported Foreign terminal type<br />
d FOREIGN4 Unsupported Foreign terminal type<br />
0 Not<br />
determined<br />
4 NOF terminal<br />
9 NOF passoff<br />
(see comment following table)<br />
78616323–000 C–5
Terminal <strong>and</strong> Printer Support<br />
Type a, b, c, d<br />
A lowercase alpha terminal type value (a, b, c, or d) represents <strong>for</strong>eign terminals which<br />
are not directly supported by Enterprise Application Environment, but may be supported<br />
by the addition of your own local code, as described later in this appendix.<br />
Type 0<br />
A value of 0 indicates that the terminal type is not yet known. When a transaction is<br />
initiated from such a terminal, Enterprise Application Environment will examine the value<br />
of PTTYP in the AUX Area of the incoming MCB Packet, in order to determine the<br />
terminal type.<br />
Note: For Kanji-capable Systems, the System Data item GLB.MFLAG is set to Y. This<br />
item is used in determining the terminal type from the PTTYP value. For example, PTTYP<br />
22 is a UTS60 terminal if GLB.MFLAG is N, but a DS7 terminal (UTS60 with Kanji capability)<br />
if GLB.MFLAG is Y<br />
The following table lists the PTTYP values <strong>and</strong> the internal terminal type codes they<br />
generate.<br />
Value of PTTYP St<strong>and</strong>ard Terminal Codes Kanji-capable Terminal Codes<br />
5 3 (SNA3270) 7 (DS7)<br />
14 D (UTS20)<br />
15 B (UTS40)<br />
21 E (UTS30)<br />
22 C (UTS60) 7 (DS7)<br />
23 F (IBM3270)<br />
34 D (UTS20) 7 (DS7)<br />
(other) D (UTS20) a (FOREIGN)<br />
Points to Note<br />
• Enterprise Application Environment does not support UTS400 terminals. Any<br />
terminal, configured as a UTS400 terminal, will be regarded as an IBM3270 terminal<br />
that uses SNA/NET software Uniscope emulation.<br />
• Terminals configured as UTS60 that are Kanji-capable are regarded as DS7 terminals.<br />
• If Enterprise Application Environment is unable to determine the terminal type, it<br />
defaults to UTS20, or to FOREIGN if Kanji-capable.<br />
• The :STN System comm<strong>and</strong> enables you to change the terminal type to any of the<br />
recognized values. When the :STN comm<strong>and</strong> is used to set the terminal back to the<br />
default type, Enterprise Application Environment determines the terminal type again,<br />
as in the previous table.<br />
C–6 78616323–000
Customizing the Mapping of PTTYP Values<br />
Terminal <strong>and</strong> Printer Support<br />
You can use the following ways to customize the mapping of PTTYP values onto terminal<br />
types.<br />
• Modify the internal translation table, GET$STYLE<br />
• Use PERM$SGS statements<br />
You can skip the process in which the terminal type is assessed from PTTYP, by using the<br />
following methods:<br />
• Preallocate S_T_N records<br />
• Use STNUTIL to predefine default terminal types<br />
These methods enable you to predefine what type particular terminals should be, so that<br />
Enterprise Application Environment does not need to use PTTYP to determine the type.<br />
These methods are described in “Inserting Your Own Code to H<strong>and</strong>le Foreign Terminals”<br />
on page C–8.<br />
Modifying the Table<br />
The GET$STYLE element contains the table (TERMTABLE) that is used to translate<br />
PTTYP values to terminal types. To add extra entries to the TERMTABLE, use COMUS,<br />
<strong>and</strong> then rebuild <strong>and</strong> reinstall.<br />
The <strong>for</strong>mat of the entries in TERMTABLE is:<br />
<br />
The parameters in this <strong>for</strong>mat are described in the following table.<br />
Field Contents<br />
pttyp Decimal PTTYP value<br />
type1 Character identifying the terminal type when not Kanji-capable<br />
type2 Character identifying the terminal type when Kanji-capable<br />
To establish the line number at which to insert your new entry, you may list the<br />
GET$STYLE element, which is contained in the SLIB$ file on your Release tape.<br />
The advantage of this method is that the changes apply immediately to all Systems within<br />
your copy of <strong>Runtime</strong>.<br />
Using PERM$SGS Statements<br />
This method of providing <strong>for</strong> additional PTTYP values cannot be applied in the following<br />
cases, as there is no ICP source available.<br />
• Systems installed using Object-Only transfer<br />
78616323–000 C–7
Terminal <strong>and</strong> Printer Support<br />
• Host Builder<br />
• Report Output Control System (ROC)<br />
Note: Where the ROC.MODE; logic comm<strong>and</strong> or ROC_I Ispec is used to enter ROC, the<br />
terminal type is correctly transferred into ROC.<br />
The advantage in using the PERM$SGS mechanism is that it does not require your copy<br />
of <strong>Runtime</strong> to be rebuilt.<br />
Extra PTTYP values can be configured by using SGSs within the PERM$SGS file <strong>for</strong> your<br />
copy of <strong>Runtime</strong> (the PERM$SGS file with your <strong>Runtime</strong> name as its qualifier). This will<br />
be used by all your Systems within that environment.<br />
The <strong>for</strong>mat of these SGSs is<br />
<br />
The field value parameters in this <strong>for</strong>mat are described in the following table.<br />
Field Contents<br />
pttype Decimal PTTYP value<br />
type Character terminal type<br />
value Y, YES, or ON (Kanji-capable)<br />
N, NO, or OFF (Not Kanji-capable)<br />
The MFLAG <strong>and</strong> the value fields are optional. If not present, then the PTTYP value<br />
corresponds to the specified terminal type, whether your System is Kanji-capable or not.<br />
If it is present, then the PTTYP value only corresponds to the specified terminal type if<br />
GLB-MFLAG has the appropriate value.<br />
For example, with an SGS of TERMINAL 29,D Enterprise Application Environment<br />
interprets terminals with a PTTYP value of 29 as type D (UTS20).<br />
With an SGS of TERMINAL 29,7 MFLAG,Y Enterprise Application Environment only<br />
interprets terminals with a PTTYP value of 29 as type 7 (DS7) if GLB.MFLAG is set to Y.<br />
These PERM$SGS statements cause the appropriate lines to be inserted into your<br />
System ICP when the System is installed or reconfigured. There<strong>for</strong>e, when PERM$SGS<br />
statements are added or changed, each of your Systems will need to be regenerated,<br />
reinstalled, or reconfigured.<br />
Inserting Your Own Code to H<strong>and</strong>le Foreign Terminals<br />
To provide support <strong>for</strong> additional <strong>for</strong>eign terminal types, per<strong>for</strong>m the following steps:<br />
1. Define the terminal type in the table of valid types <strong>and</strong> styles within the GET$STYLE<br />
element, as described in “Modifying the Table” under “Customizing the Mapping of<br />
PTTYP Values” on page C–7.<br />
C–8 78616323–000
Terminal <strong>and</strong> Printer Support<br />
2. Insert local code into the various routines that Enterprise Application Environment<br />
executes <strong>for</strong> <strong>for</strong>eign terminal screen h<strong>and</strong>ling.<br />
3. Create a COMUS PCF to make the changes <strong>for</strong> steps 1 <strong>and</strong> 2.<br />
4. Apply the PCF, rebuild, <strong>and</strong> reinstall.<br />
Defining Foreign Terminal Types<br />
If a terminal has an internal one-character type code that is lowercase alphabetic (a, b, c,<br />
or d), Enterprise Application Environment regards it as a <strong>for</strong>eign terminal, <strong>and</strong> will use the<br />
<strong>for</strong>eign terminal routines in preference to the st<strong>and</strong>ard screen h<strong>and</strong>ling routines.<br />
By default, Enterprise Application Environment defines the following <strong>for</strong>eign terminal<br />
types:<br />
<br />
<br />
<br />
<br />
Although these types are defined <strong>and</strong> can be specified in the S_T_N record or with the<br />
:STN comm<strong>and</strong>, Enterprise Application Environment does not provide any code to h<strong>and</strong>le<br />
these terminal types.<br />
To use these <strong>for</strong>eign terminal types or to add new ones, alter the TERMTABLE table in<br />
the GET$STYLE element. Each entry in this table is three words long (12 bytes), <strong>and</strong><br />
contains the GLB.STYLE name <strong>for</strong> the terminal. Only the first ten characters of the name<br />
are used. Each entry is indexed using the terminal type value, that is, the first entry is <strong>for</strong><br />
0, the second <strong>for</strong> 1, <strong>and</strong> so on, in ascending ASCII sequence. Unused letters have dummy<br />
entries to reserve their positions. These dummy entries are indicated by question marks.<br />
The four entries, (FOREIGN, FOREIGN2, FOREIGN3, <strong>and</strong> FOREIGN4) can be changed to<br />
have any GLB.STYLE name desired, by using a COMUS PCF to patch the table. Additional<br />
GLB.STYLE names can be associated with the other lowercase alphabetic types. Once<br />
this TERMTABLE Table is changed, you can use the GLB.STYLE values in :STN System<br />
comm<strong>and</strong>s <strong>and</strong> in the STNUTIL program.<br />
Inserting Your Own Screen H<strong>and</strong>ling Code<br />
At various points during a transaction, screen-specific text sequences are created to be<br />
sent to terminals. In all such cases, the terminal type is checked <strong>and</strong> if it is a <strong>for</strong>eign<br />
terminal, then an alternative routine is used.<br />
Local screen h<strong>and</strong>ling code is required in the routines listed in the following table.<br />
Element Routine(s) Function<br />
X-BUILDS X$BUILDS Creates Ispec output screens.<br />
X-DSUB X$DLNCBR Translates text <strong>for</strong> MESSAGE; comm<strong>and</strong>s.<br />
Called from the Background Run.<br />
78616323–000 C–9
Terminal <strong>and</strong> Printer Support<br />
Element Routine(s) Function<br />
You should assemble your code, insert it into the OMLIB$ file on the Release tape, <strong>and</strong><br />
then rebuild <strong>and</strong> reinstall.<br />
IBM 3270 Terminal Support<br />
General In<strong>for</strong>mation <strong>for</strong> IBM 3270 Users<br />
Terminal Operating Modes<br />
Operating modes through SNANET:<br />
X$DLSS Translates output in response to System<br />
comm<strong>and</strong>s. Called from LINC17LSS.<br />
X$DRCBR Translates output from the ROC Background<br />
Run. Called from RC1.<br />
X-GETDATA X$GETDATA Interprets Ispec input.<br />
X-QUICKSCAN X$QUICKSCAN Examines terminal input, returning text with<br />
control sequences removed.<br />
X-SPECIALS X$AUTOXMIT Creates a sequence to position the cursor on<br />
the @ sign, <strong>and</strong> then to retransmit the<br />
screen.<br />
X$BLNKSCREEN Sends a sequence to clear the screen.<br />
X$ENDMSG Creates the text <strong>for</strong> the Unisys sign-off logo.<br />
X$SIMFNK Simulates a function key by analyzing the<br />
terminal input, <strong>and</strong> inserting a value into the<br />
MCB Packet PKEY field.<br />
X$XMITCHAN Creates a XMIT VAR control page sequence.<br />
• Uniscope Emulation mode<br />
• ASCII Native mode<br />
Enterprise Application Environment sends <strong>and</strong> receives ASCII characters in IBM 3270<br />
Datastream <strong>for</strong>mat, with SNANET per<strong>for</strong>ming the conversion to <strong>and</strong> from EBCDIC <strong>for</strong><br />
communication with IBM terminals.<br />
C–10 78616323–000
Terminal <strong>and</strong> Printer Support<br />
• EBCDIC Pass-Through mode<br />
Enterprise Application Environment sends <strong>and</strong> receives EBCDIC characters in IBM<br />
Datastream <strong>for</strong>mat. Enterprise Application Environment itself does the EBCDIC to<br />
ASCII conversion; that is, SNANET can pass the messages directly to <strong>and</strong> from the<br />
IBM terminals. This mode enables the extended highlighting features of IBM<br />
terminals to be used. The following table lists the IBM terminal types supported.<br />
Terminal Type Functionality SNANET Operating Mode<br />
SNA3270 Basic Uniscope Emulation<br />
IBM3270 Basic ASCII Native 3270 Datastream<br />
IBM3178 Basic EBCDIC Native 3270 Datastream<br />
IBM3278 Extended Highlighting EBCDIC Native 3270 Datastream<br />
IBM3279 Extended Highlighting <strong>and</strong><br />
Color<br />
Screen Field Attributes<br />
EBCDIC Native 3270 Datastream<br />
• Basic Functionality<br />
The following basic screen field attributes are provided:<br />
– Protection<br />
– Numeric-only<br />
– Security (Video off)<br />
– Two levels of brightness<br />
• Extended Highlighting<br />
Extended highlighting provides you with the following additional attributes:<br />
– Blinking<br />
– Reverse Video<br />
– Underlining<br />
If your terminal has Extended Highlighting functionality, only one of the attributes can<br />
be shown on any one field at a time. That is, if more than one of these attributes<br />
applies to a field, only one will take affect. For example, the BLINK attribute overrides<br />
REVERSE VIDEO <strong>and</strong> UNDERLINE, while REVERSE VIDEO overrides UNDERLINE.<br />
Only IBM 3279 terminals are color-capable, <strong>and</strong> you may specify <strong>for</strong>eground (text)<br />
colors <strong>for</strong> your Ispec fields on these terminals. These terminals do not support the<br />
use of background colors. However, when you use color with the REVERSE VIDEO<br />
78616323–000 C–11
Terminal <strong>and</strong> Printer Support<br />
attribute, the <strong>for</strong>eground color becomes the background color, <strong>and</strong> the text appears in<br />
black. Colors that you specify in your field definition are mapped to IBM terminal<br />
colors, as shown in the following table.<br />
The Status line always appears in Reverse Video Turquoise.<br />
The BRIGHT attribute has no effect on IBM 3279 terminals. Vary the color to achieve<br />
a similar effect.<br />
Host Builder Restriction<br />
You cannot use Host Builder from an IBM 3270 terminal.<br />
IBM Printers<br />
This feature does not apply to IBM printers. Enterprise Application Environment continues<br />
to use Uniscope Emulation mode when sending report output to IBM printers. To send<br />
output to an IBM 3270 printer, in the LNET file define the PID as an IBM 3270 type<br />
device. The default is that the output is in UTS Pass-through mode.<br />
For more in<strong>for</strong>mation on supported printers, see your Unisys e-@ction Enterprise<br />
Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration <strong>Guide</strong>.<br />
<strong>Installation</strong> Notes <strong>for</strong> IBM 3270 Terminal<br />
Be<strong>for</strong>e using EBCDIC Pass-through mode in your system, you must apply changes to<br />
both SNA/NET <strong>and</strong> CMS1100 to enable EBCDIC data to be sent through SNANET. For<br />
details of these PCRs, contact your Unisys Support Center.<br />
If you wish to use EBCDIC Pass-through mode, you will need to apply these PCRs, <strong>and</strong><br />
include the following SGS card in your PERM$SGS file:<br />
<br />
Color Specified Color on IBM Terminal<br />
Ebony Neutral<br />
Red Red<br />
Yellow Yellow<br />
Blue Blue<br />
Magenta Pink<br />
Cyan Turquoise<br />
White Neutral<br />
The level parameter is the level number of SNANET (<strong>for</strong> example, 3R1E). This is currently<br />
ignored.<br />
C–12 78616323–000
Terminal <strong>and</strong> Printer Support<br />
Without this PERM$SGS statement, you cannot use the IBM3178, 3278, <strong>and</strong> 3279<br />
terminal types, <strong>and</strong> all IBM terminals will operate in ASCII Native mode or Uniscope<br />
Emulation mode. Any attempt to change a terminal to one of these types using the :STN<br />
System comm<strong>and</strong> will lead to the following error message:<br />
<br />
It is recommended that you include this SGS card in the PERM$SGS file of <strong>Runtime</strong>.<br />
Note: To correctly align numeric fields on the new IBM terminal types, you must reedit<br />
<strong>and</strong> regenerate your existing Systems.<br />
Technical Notes <strong>for</strong> IBM 3270 Terminals<br />
How Enterprise Application Environment Sends Screens to an IBM 3270<br />
When building up a Native-mode 3270 Datastream sequence to be sent to an IBM3270<br />
terminal, Enterprise Application Environment per<strong>for</strong>ms the following operations:<br />
• All data items (including Usage Inquiry <strong>and</strong> protected) have the modified data tag<br />
(MDT) bit set.<br />
• Display items do not have the MDT bit set.<br />
• Enterprise Application Environment uses SBA (Set Buffer Address) or RA (Repeat to<br />
Address) sequences where possible to reduce the number of characters to be sent.<br />
• Null characters are used instead of spaces, except <strong>for</strong> embedded spaces in data item<br />
text.<br />
• Trailing spaces on data items are replaced by null characters not sent when an Ispec<br />
is initially displayed.<br />
• Enterprise Application Environment places an Start Field (SF) or an Start Field<br />
Extended (SFE) at the beginning <strong>and</strong> end of each data item, <strong>and</strong> wherever an attribute<br />
is to change (<strong>for</strong> example, at the end of a line to turn off Reverse Video).<br />
• If two items are joined together on the screen, or one item ends in column 80 <strong>and</strong><br />
another starts in column one of the next line, the last character of the first item will be<br />
overwritten by the SF (or SFE) character unless the two items have the same<br />
attributes. This includes a Display item immediately followed by a data item.<br />
• When you press PDl-5 or CLEAR, Enterprise Application Environment effectively<br />
clears the screen by filling it with null characters, except <strong>for</strong> the status line. The status<br />
line contains the system name <strong>and</strong> an unprotected SF character at Row 24 Column<br />
80, enabling data entry from Row 1 Column 1.<br />
• When Enterprise Application Environment sends text to the status line only (<strong>for</strong><br />
example, an error message), columns 78, 79, <strong>and</strong> 80 do not change. These columns<br />
usually contain the SF <strong>for</strong> the @ sign, the @ sign itself, <strong>and</strong> an SF character in column<br />
80.<br />
• When an Ispec that is to be sent is already on display at the destination terminal,<br />
Enterprise Application Environment sends only the Status line text <strong>and</strong> data item<br />
values. It does not send SF characters of Display items.<br />
78616323–000 C–13
Terminal <strong>and</strong> Printer Support<br />
• Signed numeric items (other than Usage Inquiry items) have an SF (or SFE) character<br />
inserted between the value <strong>and</strong> sign parts. This has the effect of separating the value<br />
<strong>and</strong> sign with one space character. This applies whether or not delimiters are being<br />
used.<br />
• The scrolling action of Repeat.From screens is not supported <strong>for</strong> IBM 3270 terminals.<br />
A Repeat.From Ispec will there<strong>for</strong>e behave as though it is not a Repeat.From Ispec.<br />
How Enterprise Application Environment Receives Screens from an IBM<br />
3270<br />
SNANET always per<strong>for</strong>ms a Read Modified operation to receive input from an IBM 3270<br />
terminal, so that it only receives text <strong>for</strong> fields that have the Modified Data Tag (MDT) bit<br />
set. Enterprise Application Environment sets the MDT bit <strong>for</strong> all data items be<strong>for</strong>e<br />
sending the screen, <strong>for</strong>cing text <strong>for</strong> every data item to be retained. For more details, see<br />
“How Enterprise Application Environment Sends Screens to an IBM 3270", earlier in this<br />
appendix.<br />
The Read Modified operation also ignores any null characters, <strong>and</strong> since Enterprise<br />
Application Environment uses null characters instead of spaces where possible, the total<br />
number of characters sent on input is minimized.<br />
Terminal Operating Modes<br />
IBM 3270 terminals operate in one of the following modes over SNANET.<br />
• Uniscope Emulation (INT-1)<br />
• ASCII Native<br />
• EBCDIC Pass-through<br />
Enterprise Application Environment uses the terminal type field in the S_T_N table to<br />
keep track of the SNANET mode under which a terminal is currently operating. The<br />
following table shows the possible values of this one-character field.<br />
S_T_N Value Terminal Type SNANET Mode<br />
3 SNA3270 Uniscope Emulation<br />
F IBM3270 ASCII Native Mode<br />
G IBM3178 EBCDIC Pass-through<br />
H IBM3278 EBCDIC Pass-through<br />
I IBM3279 EBCDIC Pass-through<br />
C–14 78616323–000
Terminal <strong>and</strong> Printer Support<br />
When Enterprise Application Environment receives input from a terminal, it uses the<br />
S_T_N terminal type field to set the fields relating to the terminal type in the MCB<br />
packet. SNANET then drives the terminal in the appropriate mode. There<strong>for</strong>e, when the<br />
current mode being used by SNANET differs from that stored in the S_T_N table, a<br />
change of SNANET operating mode occurs.<br />
Note: Without the SNANET EBCDIC PERM$SGS statement, Enterprise Application<br />
Environment regards S_T_N values G, H, <strong>and</strong> I as equivalent to F. That is, it only operates<br />
the terminal in ASCII Native mode.<br />
The MCB fields used to determine the current operating mode of a terminal are PTTYP<br />
<strong>and</strong> PRTYP. The value of the S_T_N field relates to the values of PTTYP <strong>and</strong> PRTYP as<br />
shown in the following table.<br />
PRTYP PTTYP S_T_N Value<br />
23 5 3<br />
23 23 F<br />
23 31 G<br />
23 31 H<br />
23 31 I<br />
78616323–000 C–15
Terminal <strong>and</strong> Printer Support<br />
C–16 78616323–000
Appendix D<br />
Related Product In<strong>for</strong>mation<br />
The following publications are used as reference sources <strong>for</strong> <strong>OS</strong> <strong>2200</strong> based System<br />
users who have completed training courses. They are not intended as self-teach<br />
documents. See your local Unisys representative <strong>for</strong> in<strong>for</strong>mation on available training<br />
courses.<br />
Unisys e-@ction Enterprise Application <strong>Runtime</strong> <strong>for</strong> <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong><br />
Administration <strong>Guide</strong><br />
This document describes the generation <strong>and</strong> operation of Systems <strong>and</strong> Reports, <strong>and</strong> the<br />
general administration of Systems <strong>for</strong> <strong>OS</strong> <strong>2200</strong> based hosts.<br />
Unisys e-@ction Enterprise Application Programming Reference Manual<br />
This document contains reference material <strong>for</strong> developers, such as Logic comm<strong>and</strong>s <strong>and</strong><br />
System Data items used in creating Systems.<br />
Unisys e-@ction Enterprise Application Executive Overview - The Business<br />
Case (7833 2145)<br />
This document is an introduction to Enterprise Application Environment <strong>for</strong> executive <strong>and</strong><br />
general readers.<br />
Unisys e-@ction Enterprise Application Technical Overview - The Business<br />
Case (7833 2152)<br />
This document is an overview of Enterprise Application Environment features <strong>and</strong><br />
facilities <strong>for</strong> more technically oriented readers.<br />
Unisys e-@ction Enterprise Application Host Builder <strong>Guide</strong><br />
This document describes the use of Host Builder to create <strong>and</strong> maintain user in<strong>for</strong>mation<br />
systems.<br />
Unisys e-@ction Enterprise Application Programming Reference H<strong>and</strong>book<br />
(7861 6067-001)<br />
This document contains the syntax of Logic comm<strong>and</strong>s <strong>and</strong> System Data items <strong>and</strong> other<br />
comm<strong>and</strong>s used in Host Builder.<br />
78616323–000 D–1
Related Product In<strong>for</strong>mation<br />
Unisys e-@ction Enterprise Application Developer <strong>Installation</strong> <strong>and</strong><br />
<strong>Configuration</strong> <strong>Guide</strong><br />
This document describes the installation of Developer in st<strong>and</strong>alone or multiuser<br />
environments <strong>and</strong> the administration of the Developer working environment, including<br />
repository administration, backup procedures, security <strong>and</strong> other issues.<br />
Extended Transaction Capacity (XTC) Conceptual Overview<br />
This overview discusses the various components <strong>and</strong> processes that constitute an XTC<br />
system <strong>and</strong> provides in<strong>for</strong>mation to help in the planning of an XTC system.<br />
D–2 78616323–000
Glossary<br />
A<br />
access class<br />
For Ad Hoc Inquiry, a particular type of user access to queries, defined by a letter (A<br />
through Z) or an asterisk (*, <strong>for</strong> unrestricted access). Also called query class.<br />
Action line<br />
A field that appears on most screens in mainframe Enterprise Application Systems,<br />
enabling fast-track navigation to required functions. Also referred to as the Action field.<br />
Activity<br />
A group of Objects which together per<strong>for</strong>m a business function.<br />
Ad Hoc Inquiry<br />
A mainframe facility used <strong>for</strong> making inquiries on an Enterprise Application Database.<br />
Administration Client<br />
A tool <strong>for</strong> administering Enterprise Application user systems <strong>and</strong> their associated<br />
databases. The Administration Client can be used on a remote workstation or on the<br />
runtime server. The Administration Client communicates with the Administration Services<br />
using Remote Procedure Call (RPC) to per<strong>for</strong>m the requested operations.<br />
Administration group<br />
A group of user accounts within a Windows domain <strong>for</strong> people who have privileges to<br />
administer systems, <strong>for</strong> example, to add a new database to an Enterprise Application<br />
environment. The Administrator is a separate role from the Windows Administrator,<br />
although the two roles may be per<strong>for</strong>med by the same person. Most administration<br />
functions are per<strong>for</strong>med from the Administration Client interface.<br />
Administration <strong>Guide</strong><br />
The manual that contains instructions <strong>for</strong> administering <strong>and</strong> operating Enterprise<br />
Application Systems on a particular host type.<br />
Administration Services<br />
The set of Windows services on the runtime server that communicates with<br />
Administration Clients using RPC. These services per<strong>for</strong>m various administrative functions<br />
on behalf of the Administration Clients.<br />
Administrator<br />
Person responsible <strong>for</strong> administration of a computing environment.<br />
78616323–000 Glossary–1
Glossary<br />
archive<br />
Copy files to a directory as protection against accidental loss, deletion, or damage.<br />
Audit Archive File<br />
An archive file of audit records.<br />
Audit Domain<br />
An Audit Domain defines the scope of audit activity <strong>for</strong> Developer. An Audit Domain can<br />
be a Model or a Business Segment.<br />
auditing<br />
Auditing records events that occur in the Developer <strong>and</strong> Developer Security environments,<br />
providing a history of changes made to the Developer Repository.<br />
Audit Store<br />
The Audit Store holds audit records. Because the function of auditing is to record<br />
operations that affect a Developer Repository, there is one Audit Store <strong>for</strong> each Repository.<br />
Automaint Profile<br />
The Profile of a Multiple Ordinate Memo Component that provides automatic access to the<br />
records of that Component. See Multiple Ordinate Memo Component, Profile.<br />
Automatic Entry<br />
(1) A facility that enables an Ispec to create a record in another Ispec. (2) A facility that<br />
enables an Ispec to modify an existing record in a St<strong>and</strong>ard Component, Table Component,<br />
or Multiple Ordinate Memo Component. Not applicable to Copy.From Ispecs. See also<br />
Automatic Entry buffer, external Automatic Entry, internal Automatic Entry, HUB.<br />
Automatic Entry buffer<br />
An area in memory used by the Automatic Entry facility. See Automatic Entry.<br />
Automatic Lookup<br />
A process where a Component record is automatically read into memory from the<br />
database.<br />
Automatic Profile<br />
The Profile created by Developer <strong>for</strong> a Component with an Ordinate. This Profile cannot be<br />
seen in the Model Directory, but can be viewed as part of a System in the Systems<br />
Directory.<br />
B<br />
Background Run<br />
For <strong>OS</strong> <strong>2200</strong> Systems, a background run that controls certain functions; <strong>for</strong> example<br />
recovery, report h<strong>and</strong>ling, <strong>and</strong> setting up of Common Banks. There is one Background Run<br />
<strong>for</strong> each <strong>Runtime</strong>.<br />
Glossary–2 78616323–000
Glossary<br />
Background window<br />
The window behind the first window you see when Developer is initiated. The Background<br />
window provides access to the various functions of Developer.<br />
backup<br />
banner<br />
Make a copy of a database or subset of a database.<br />
A system-generated page that prints at the start of a Report <strong>and</strong> provides control<br />
in<strong>for</strong>mation about that Report.<br />
base year<br />
The year upon which the DATE.CONVERT; comm<strong>and</strong> bases relative day numbers. Base<br />
year is defined using the Primary Database Options screen in Host Builder <strong>and</strong> using the<br />
Business Segment Options dialog box in Developer. It may be accessed through the<br />
System Data item GLB.BASE. See relative day number.<br />
binary<br />
bind<br />
Object files that may be .int, .gnt, .exe, or .dll files. A runtime transfer using export or<br />
import transfers the runtime files, not the source COBOL files.<br />
The task of coupling object files with executable files <strong>for</strong> dynamically linked program code.<br />
Ensures that externally referenced procedures or subprograms are available to a main<br />
program.<br />
breakpoint<br />
A feature of the Developer Test Debugger that stops logic execution in response to a<br />
certain state of the system.<br />
buildable LINCIIDIR<br />
The Enterprise Application installation directory is defined by the environment variable<br />
LINCIIDIR. A LINCIIDIR that contains the object packages necessary to build executables<br />
using object packaging is a buildable LINCIIDIR. A buildable LINCIIDIR is necessary to use<br />
object packaging to maintain your Enterprise Application environment.<br />
Builder<br />
The software used to generate Specifications (Business Models) as applications.<br />
Generation is the process of generating a complete set of source files <strong>and</strong> then compiling<br />
<strong>and</strong> linking those files to create a set of executables. Through Builder, a Developer<br />
workstation can generate an application to a target host runtime environment.<br />
Builder Client<br />
The Builder Client runs on the workstation that initiates the generate process <strong>and</strong> controls<br />
the generation of the system according to its specified elements <strong>and</strong> options. It also<br />
includes the Generate Client/Server interface to the Builder Server.<br />
78616323–000 Glossary–3
Glossary<br />
Builder Server<br />
The Builder Server runs on the host to which the Builder Client is connected. It compiles<br />
the Enterprise Application System generated by the client <strong>and</strong> provides the runtime<br />
environment <strong>for</strong> the application.<br />
Bulk Option screens<br />
A group of screens in Host Builder that enable options <strong>for</strong> several Ispecs, Reports, Profiles,<br />
or Global Logics to be entered together.<br />
Business Model<br />
Repository containing details of Business Segments (Specifications) held by Developer.<br />
Business Rules<br />
In<strong>for</strong>mation entered as text which supports an Element.<br />
Business Segment<br />
Part of a Model that provides the definition <strong>for</strong> an Enterprise Application System in<br />
Developer. Equivalent to a Specification in Host Builder.<br />
C<br />
Change control<br />
A method <strong>for</strong> tracking changes to Specifications.<br />
Change identifier<br />
A alphanumeric value used to identify a single user or user terminal <strong>for</strong> change control<br />
purposes. Applies when the Change Identification option is selected <strong>for</strong> that Specification.<br />
Contrast with Patch identifier.<br />
class<br />
client<br />
See access class, security class.<br />
A Windows program, typically running on a workstation, that works cooperatively with one<br />
or more programs or services running on a server computer. In some cases, the client<br />
program may reside on the server computer, but uses the network interfaces to<br />
communicate with the server program or service. In <strong>Runtime</strong> <strong>for</strong> the Windows 2000 <strong>and</strong><br />
Windows NT operating systems, there are two distinct types of client:<br />
1. An operational tool, such as the Administration Client, which deploys, manages, <strong>and</strong><br />
maintains user systems.<br />
2. An end-user client, such as Graphical Interface Workbench, that provides workstation<br />
users access to Enterprise Application user systems. This class of client includes<br />
user-written clients developed in languages such as C++ <strong>and</strong> Visual Basic.<br />
Client Listener<br />
This service listens <strong>for</strong> <strong>and</strong> accepts connection requests from the Administration Client.<br />
Glossary–4 78616323–000
Glossary<br />
client/server<br />
A distributed architecture in which client workstations communicate with servers through<br />
a network. For instance, a client typically provides initial processing, data gathering<br />
functionality <strong>and</strong> the user interface. It then communicates the data <strong>and</strong> requests to a<br />
server <strong>for</strong> further processing.<br />
Column name<br />
For Ad Hoc Inquiry, an SQL term equivalent to Data Item.<br />
compile<br />
To create object files from source files.<br />
Component<br />
(1) A business resource such as a customer, product or vendor. (2) A store of static data<br />
about a business resource. Consists of a screen layout <strong>and</strong> associated logic (Pre-Screen<br />
logic, Pre-LINC logic, <strong>and</strong> Main logic). Together with Events, Components <strong>for</strong>m the<br />
fundamental building blocks of a System. See also Ispec, St<strong>and</strong>ard Component, Table<br />
Component, Memo Component, Multiple Ordinate Memo Component.<br />
Component Enabler<br />
The product with which users can build their own GUI interfaces, or Views, to Systems.<br />
These Component Enabler applications use the Remote Access Server to communicate<br />
with Systems on the host environment. Component Enabler allows applications to current<br />
Web technology <strong>and</strong> the Enterprise NT world. See also Remote Access to Enterprise<br />
Application.<br />
Component Profile<br />
For Ad Hoc Inquiry, a Profile over one Component. Contrast with Event Profile.<br />
Component record<br />
For Ad Hoc Inquiry, an individual database record <strong>for</strong> a Component. Equivalent in SQL<br />
terminology to a row.<br />
COMSTP Program<br />
A pre-compiled program that contains the necessary logic <strong>for</strong> routing of user transactions<br />
in a MCP based System.<br />
COMUS<br />
For <strong>OS</strong> <strong>2200</strong> based Systems, a product used to build <strong>Runtime</strong> be<strong>for</strong>e installation. See<br />
SOLAR.<br />
Control tables<br />
Tables created <strong>for</strong> the control of an environment within each Oracle database (SID)<br />
associated with the environment. Examples are PROCTAB <strong>and</strong> LSYS.<br />
78616323–000 Glossary–5
Glossary<br />
Copy.From Ispec<br />
An Ispec with a screen that has a number of identical recurring lines. Transmission of the<br />
whole screen produces a separate record in the database <strong>for</strong> each completed line. See<br />
also Ispec.<br />
Critical Point<br />
A user-specified recovery point within a Report. In the event of a failure, recovery will<br />
restore the environment to the last successful Critical Point, then resume execution at the<br />
location of the Critical Point.<br />
D<br />
DAD<br />
See Data Display.<br />
Data Attribute<br />
An attribute of a Data Item. For example, LENGTH, EDIT, BRIGHT.<br />
Data Comm<strong>and</strong><br />
A comm<strong>and</strong> that identifies or creates a Data Item used in a screen layout, Report, or logic.<br />
Data Dictionary<br />
A collective name <strong>for</strong> the Local <strong>and</strong> Global data dictionaries. See Local Data Dictionary,<br />
Global Data Dictionary.<br />
Data Display (DAD)<br />
Optional descriptive text <strong>for</strong> a Data Item, used in status messages in place of the name of<br />
the Data Item. Defined using the DATA.DISPLAY Data Attribute.<br />
Data Item<br />
The variable used to enter, manipulate, store, <strong>and</strong> display data. For example, Ordinates,<br />
Setup Data items.<br />
Database ID<br />
The two-character identifier <strong>for</strong> either an ORACLE or SQL Server database. This identifier<br />
was previously referred as the ORACLE SID. See ORACLE SID.<br />
Database Management Utility (DMU)<br />
A utility that enables you to maintain your Enterprise Application Database. Use DMU to<br />
per<strong>for</strong>m such tasks as changing the amount of disk space allocated to database structures,<br />
initiate a full or partial database reorganizations (<strong>for</strong> MCP based Systems), <strong>and</strong> creating<br />
ORACLE SIDs (<strong>for</strong> Systems based on the UNIX operating system). See also Griffin<br />
Database Management Utility (GMU).<br />
debug settings<br />
A set of breakpoint, watch, <strong>and</strong> debug options that can be saved to a file <strong>and</strong> loaded into<br />
a Developer Test Debugger session as needed.<br />
Glossary–6 78616323–000
Glossary<br />
DEPCON<br />
The Unisys DEPCON software application is a comprehensive print-management <strong>and</strong> file<br />
distribution solution <strong>for</strong> mixed-plat<strong>for</strong>m networks. Coupling the Enterprise Application<br />
Environment with DEPCON increases the design possibilities <strong>and</strong> flexibility of Reports.<br />
See the DEPCON Software <strong>Configuration</strong> <strong>and</strong> Operations <strong>Guide</strong> <strong>and</strong> “Using DEPCON<br />
Reports” in the Unisys e-@ction Enterprise Application Developer User <strong>Guide</strong>.<br />
deploy<br />
To implement a set of Enterprise Application executables <strong>and</strong> a database on a host<br />
machine. The result of deployment is the creation of an application on the host.<br />
Deployment Server<br />
The Windows server on which an application is installed <strong>and</strong> executed. Does not have<br />
Micro Focus COBOL installed.<br />
Deployment Services<br />
Windows programs installed with <strong>Runtime</strong> <strong>for</strong> the Windows 2000 <strong>and</strong> Windows NT<br />
operating systems to per<strong>for</strong>m specific functions, such as listening <strong>for</strong> <strong>and</strong> accepting<br />
connection requests on behalf of an environment. A collective term <strong>for</strong> the Administration<br />
<strong>and</strong> Generation services.<br />
Design Audit<br />
Analyzes a Business Segment, Functional Area, or Activity, <strong>and</strong> lists any items that may<br />
indicate poor design that will impact per<strong>for</strong>mance in a generated system.<br />
Developer<br />
Workstation based development tool <strong>for</strong> creating <strong>and</strong> maintaining Business Models<br />
(Specifications). From Developer, Business Models are transferred to host based Builder<br />
<strong>for</strong> generation <strong>and</strong> deployment, or generated directly to a target host. Formerly known as<br />
LDA III or LINC Development.<br />
Developer Test<br />
A workstation testing environment <strong>for</strong> Developer which includes a logic Debugger.<br />
Formerly known as LINC Development <strong>Runtime</strong>.<br />
Development Environment<br />
A collective term <strong>for</strong> the tools used to design, develop, <strong>and</strong> generate Enterprise Application<br />
Systems. Includes Developer, Builder, <strong>and</strong> utilities.<br />
Development System<br />
See Developer <strong>and</strong> Builder.<br />
Direct Component<br />
A Component type that uses a key <strong>for</strong> direct access to the dataset, saving on the number<br />
of Input/Output operations. It has a single numeric Ordinate with a maximum of 8 digits.<br />
See Component.<br />
78616323–000 Glossary–7
Glossary<br />
Direct Report<br />
A Report that uses the Report Output Control System (ROC), <strong>and</strong> which sends output<br />
directly to an output device <strong>and</strong> not to the ROC database. See also Report Output Control<br />
System. Contrast with St<strong>and</strong>ard Report.<br />
Display item<br />
A string of descriptive in<strong>for</strong>mation displayed on an Ispec screen layout or Report Frame.<br />
DLL<br />
DMU<br />
E<br />
Editor<br />
EIF<br />
Dynamic Link Library, contains one or more functions that are compiled, linked, <strong>and</strong> stored<br />
separately from the processes using them.<br />
See Database Management Utility.<br />
An Enterprise Application facility <strong>for</strong> specifying logic <strong>for</strong> Ispec <strong>and</strong> Report processing.<br />
Engineering Interim Fixes (EIFs) are used to distribute new features, fixes, customer<br />
requests <strong>and</strong> newly validated versions of support software.<br />
Element<br />
Collective term <strong>for</strong> the individual parts of the Business Model. An Element may be any of<br />
the following: Activity, Functional Area, Language, Object, or Wildcard.<br />
Enterprise Application Database<br />
The database created in the generation of an Enterprise Application System. Used <strong>for</strong><br />
storing data.<br />
Environment<br />
The operating environment <strong>and</strong> supporting services <strong>for</strong> applications on a Windows server.<br />
Each environment is created by a separate installation of <strong>Runtime</strong> <strong>for</strong> the Windows 2000<br />
<strong>and</strong> Windows NT operating systems. There may be multiple environments on a single<br />
Windows server. Each environment includes one or more databases. Each database may<br />
contain zero or more user systems.<br />
Environment database<br />
The database associated with an environment that contains control tables. These tables<br />
control the environment <strong>for</strong> all the user systems in the environment. Synonymous with<br />
control tables.<br />
Environmental Options screens<br />
Screens in Host Builder that enable you to define generate options <strong>for</strong> your Specification.<br />
Glossary–8 78616323–000
Event<br />
Glossary<br />
(1) An activity per<strong>for</strong>med by an organization, <strong>for</strong> example a sale, purchase, or payment. (2)<br />
A store of data about an activity per<strong>for</strong>med. An Event consists of a screen layout <strong>and</strong><br />
associated logic (Pre-Screen logic, Pre-LINC logic, <strong>and</strong> Main logic). Together with<br />
Components, Events <strong>for</strong>m the fundamental building blocks of a System. See also Ispec.<br />
Event file<br />
For Ad Hoc Inquiry, the file containing the Event records.<br />
Event Profile<br />
For Ad Hoc Inquiry, a Profile over one or more Events. Contrast with Component Profile.<br />
Event record<br />
For Ad Hoc Inquiry, an individual database record <strong>for</strong> an Event. Equivalent in SQL<br />
terminology to a row.<br />
Executables<br />
Executables are one of two methods of distributing applications to customers. They are<br />
the compiled set of application files which are ready to install <strong>and</strong> run. Contrast this with<br />
Objects.<br />
EXE file<br />
export<br />
A Windows native executable file.<br />
To copy an Enterprise Application System to a file <strong>for</strong> transfer to another environment.<br />
Extended Language Message System (ELMS)<br />
An <strong>OS</strong> <strong>2200</strong> based facility that provides translatable versions of messages used by<br />
software.<br />
extent<br />
A contiguous block of disk space assigned by Oracle. Extents are used in data segments<br />
(table data storage), index segments, rollback segments, <strong>and</strong> temporary segments. An<br />
extent is a unit of database storage space allocation. When an extent is used up, Oracle<br />
allocates a new one.<br />
External Automatic Entry<br />
An Automatic Entry to or from an external source, such as another System. See Automatic<br />
Entry, HUB. Contrast with internal Automatic Entry.<br />
Extract file<br />
A non-database (text) file created or read by a Report.<br />
78616323–000 Glossary–9
Glossary<br />
F<br />
Filegroup<br />
A discrete part of an SQL Server database. Filegroups in the same database can be stored<br />
on different physical devices. See tablespace.<br />
Fireup Ispec<br />
The Ispec that is displayed on your terminal when you sign on to an Enterprise Application<br />
System.<br />
Forms Translation Utility (FTU)<br />
A utility that enables you to modify screen layouts, Teach screens, Data Displays, <strong>and</strong><br />
translatable Global Setup Data items of your System without regeneration. FTU can also<br />
be used to modify Enterprise Application Software.<br />
Frame<br />
A number of Report lines containing display text <strong>and</strong> Data Items that is output as a single<br />
unit when the Frame is invoked by Report logic.<br />
Function Point Analysis<br />
A technique <strong>for</strong> estimating the size of an existing or future in<strong>for</strong>mation system, using a unit<br />
of measurement called a Function Point.<br />
Functional Area<br />
(1) A group of Activities. (2) A concept used to group Activities <strong>for</strong> the purpose of loading<br />
into Builder.<br />
G<br />
garbage collection<br />
An Administration Client function that aids the compacting of Oracle database tables.<br />
Generalized Interface (GLI)<br />
A facility that enables a external program to initiate transactions into an Enterprise<br />
Application user system.<br />
generate<br />
Per<strong>for</strong>m the tasks necessary to create an Enterprise Application System on a host,<br />
including:<br />
• Importing Enterprise Application user system files from the development<br />
environment or another server<br />
• Deploying a runtime system <strong>and</strong> a database<br />
Generate Group<br />
A specified group of Reports that can be generated together.<br />
Glossary–10 78616323–000
Glossary<br />
Generate Set<br />
A named set of values <strong>for</strong> generating a particular System from a Specification; <strong>for</strong> example,<br />
<strong>for</strong> a particular host type.<br />
Generate Threads<br />
A number of parallel generate tasks that can be initiated on the workstation.<br />
GLI<br />
See Generalized Interface.<br />
Global Data Dictionary<br />
(1) A data dictionary that controls the use of Data Items over all Specifications (<strong>for</strong> Host<br />
Builder) or Business Segments (<strong>for</strong> Developer). (2) Part of GLOBAL Specification. (3) See<br />
also Data Dictionary, Local Data Dictionary.<br />
Global Logic<br />
Part of a Specification that can be reused in more than one part of your Specification or<br />
Business Segment. Inserted into Ispecs, Reports, or Global Logics by using the INSERT;<br />
logic comm<strong>and</strong>. See Insertable Global Logic, Per<strong>for</strong>mable Global Logic.<br />
Global Setup Data Block<br />
An internal logic block used to group Global Setup Data Items. Grouping Global Setup Data<br />
Items <strong>for</strong> example, by Ispec would mean that when you recompiled that Ispec <strong>for</strong> generate<br />
purposes, only those Global Setup Data Items grouped in that Block would be recompiled,<br />
rather than all of them. Global Setup Data Items can only be defined within Global Setup<br />
Data Blocks.<br />
Global Setup Data item<br />
A type of Setup Data item that can be used by any Ispec or Report logic within a<br />
Specification or Business Segment. Global Setup Items can only be defined within Global<br />
Setup Data Blocks. See Setup Data item, Group Global Setup Data item.<br />
GMU<br />
GNT<br />
graph<br />
See Griffin Database Management Utility.<br />
The file extension <strong>for</strong> Micro Focus "generated" (native instruction set) COBOL code. Files<br />
in this <strong>for</strong>mat have intermediate compilation <strong>and</strong> execution times. Contrast with INT.<br />
Pictorial representation of a number of Elements <strong>and</strong> the relationships between the<br />
Elements. Provides access to all in<strong>for</strong>mation supporting the represented Elements.<br />
Graphical Interface Workbench<br />
The workstation software that makes it possible <strong>for</strong> end users to access a deployed user<br />
system through a graphical user interface. Formerly known as PowerClient.<br />
78616323–000 Glossary–11
Glossary<br />
Griffin<br />
Database Management System used as the underlying database software <strong>for</strong> Builder <strong>for</strong><br />
the UNIX operating system. See also ORACLE.<br />
Griffin Database Management Utility (GMU)<br />
The equivalent of the Database Management Utility (DMU) <strong>for</strong> Griffin.<br />
Griffin Universe<br />
A Griffin term <strong>for</strong> a logical storage area that may contain one or more databases.<br />
Equivalent of ORACLE SID. See also tablespace.<br />
Group Global Setup Data item<br />
A Global Setup Data item that is a concatenation of a number of other Global Setup Data<br />
items. See Global Setup Data item.<br />
group query<br />
For Ad Hoc Inquiry, an SQL <strong>for</strong>mat query whose output lines are <strong>for</strong> groups of related<br />
records rather than individual records. The group is defined by including a GROUP BY<br />
clause, or by including group functions such as MAX, MIN, SUM, <strong>and</strong> AVG in the select list.<br />
Group Setup Data item<br />
A Setup Data item that is a concatenation of a number of other Setup Data items. See<br />
Setup Data item.<br />
H<br />
Home position<br />
Top left corner of a character-based screen. Often used as the position from which<br />
comm<strong>and</strong>s are entered.<br />
Home screen<br />
For Ad Hoc Inquiry, the base screen from which the main functions are chosen.<br />
host<br />
Computer on which an Enterprise Application Environment application is running.<br />
Host List<br />
(1) In the host environment, the list of valid host types <strong>for</strong> which Builder can per<strong>for</strong>m<br />
reserved word checking <strong>and</strong> generation of applications. (2) In Developer, a list of valid host<br />
computers that can be used by a Generate Set.<br />
Host Name<br />
The name of the specific host to be used <strong>for</strong> a function.<br />
Glossary–12 78616323–000
Glossary<br />
Host Specification<br />
The name of the target host to be used <strong>for</strong> the process, its TCP/IP or network address, <strong>and</strong><br />
host type. See Host Name.<br />
HUB<br />
The facility that controls external Automatic Entries between Enterprise Application<br />
Systems. See Automatic Entry, external Automatic Entry.<br />
HUB Background Run<br />
For <strong>OS</strong> <strong>2200</strong> Systems, a background run that processes external Automatic Entries. There<br />
is one Background Run <strong>for</strong> each <strong>Runtime</strong>. See also HUB.<br />
HUB Listener<br />
This service listens <strong>for</strong> <strong>and</strong> accepts HUB connection requests from other Enterprise<br />
Application user systems.<br />
I<br />
ICP<br />
import<br />
See Initial Control Program (<strong>for</strong> <strong>OS</strong> <strong>2200</strong> based Systems) <strong>and</strong> Ispec Control Program (<strong>for</strong><br />
Unix based Systems).<br />
To copy application files into the directory where they will be deployed. When importing<br />
files from another Windows server, the import operation also decompresses the export file<br />
into its constituent application files.<br />
Initial Control Program (ICP)<br />
The program that controls the generated Ispec subprograms in <strong>OS</strong> <strong>2200</strong> based Systems.<br />
Contrast with COMSTP Program (<strong>for</strong> MCP based Systems) <strong>and</strong> Ispec Control Program (<strong>for</strong><br />
Unix based Systems).<br />
Insertable Global Logic<br />
A logic sequence <strong>and</strong>/or a screen layout that can be copied into any number of Ispecs <strong>and</strong><br />
Reports. Contrast with Per<strong>for</strong>mable Global Logic.<br />
<strong>Installation</strong> <strong>Guide</strong><br />
The manual that contains instructions <strong>for</strong> installing <strong>and</strong> configuring Enterprise Application<br />
Systems on a particular host type.<br />
INT<br />
The file extension <strong>for</strong> a file in Micro Focus interpretive code <strong>for</strong>mat. Files in this <strong>for</strong>mat<br />
compile quickly, but are slow to execute. Contrast with GNT.<br />
interdatabase access<br />
The accessing of the database of an <strong>OS</strong> <strong>2200</strong> based System by another <strong>OS</strong> <strong>2200</strong> based<br />
System.<br />
78616323–000 Glossary–13
Glossary<br />
internal Automatic Entry<br />
An Automatic Entry from within the same Enterprise Application System. See Automatic<br />
Entry. Contrast with external Automatic Entry.<br />
interrogation point<br />
For Ad Hoc Inquiry, a regular interval during query execution when the status of that query<br />
is written to the database.<br />
Ispec<br />
(1) A collective term <strong>for</strong> Components <strong>and</strong> Events. In the Enterprise Application<br />
Environment, an Ispec models an entity or activity in the real world. An Ispec also specifies<br />
the user interface, the processing rules, <strong>and</strong> the database structure to be used to represent<br />
it in the deployed user system. (2) A contraction of the term Interface Specification. (3)<br />
See also Component, Event.<br />
Ispec Control Program (ICP)<br />
The program that controls the generated Ispec subprograms in Enterprise Application Unix<br />
based Systems. Contrast with COMSTP Program (<strong>for</strong> MCP based Systems) <strong>and</strong> Initial<br />
Control Program (<strong>for</strong> <strong>OS</strong> <strong>2200</strong> based Systems).<br />
K<br />
Keyword<br />
A Data Item that has multiple data entry fields <strong>and</strong> Display items. See also Keyword Term<br />
Item, Keyword Term Display.<br />
Keyword Term Display<br />
The Display item associated with a Keyword. See Keyword.<br />
Keyword Term Item<br />
The Data Item associated with a Keyword. See Keyword.<br />
L<br />
language<br />
A natural language in which text components of the system can appear. The default<br />
language is usually English, but can be any language you chose. An application can have<br />
up to 14 languages concurrently installed. Users, or the software itself, can choose to<br />
display screens, Reports, or prompts in any one of the installed languages.<br />
LCOPY Utility<br />
A utility that provides a means of backing up, maintaining <strong>and</strong> controlling Specifications, on<br />
the same or different machines.<br />
LDL Listing Utility<br />
A facility in Host Builder used <strong>for</strong> printing a Specification.<br />
Glossary–14 78616323–000
Glossary<br />
LINCTEMP<br />
The temporary directory. Its location is defined by the environment variable LINCTEMP <strong>and</strong><br />
defaults to \bin.<br />
LINQINQ<br />
A user account with read-only privileges used to per<strong>for</strong>m inquiries against Enterprise<br />
Application Control <strong>and</strong> User tables.<br />
literal<br />
A literal is a value used directly by a system, without requiring any named storage area. A<br />
literal may also be used in many logic comm<strong>and</strong>s in place of Data Items, <strong>and</strong> to define the<br />
characteristics of Setup Data items.<br />
Local Data Dictionary<br />
A data dictionary that controls the use of Data Items within a single Specification. See also<br />
Data Dictionary, Global Data Dictionary.<br />
lock<br />
Inhibit other users from reading <strong>and</strong>/or updating a specific record or window. Developer<br />
has three <strong>for</strong>ms of locking:<br />
• An automatic soft lock that is set up whenever you attempt to modify an Object. This<br />
lock is released when the transaction ends or you cancel the operation.<br />
• A manual lock that emulates the behavior of the the host environment resource<br />
locking.<br />
• If Version Control is installed, a Version lock that is set when an Object is checked out<br />
of the Version Control Bank.<br />
locked query<br />
For Ad Hoc Inquiry, a query that is not available <strong>for</strong> editing or running because it is currently<br />
queued <strong>for</strong> execution, or its execution has terminated abnormally, or it is being edited.<br />
logic<br />
Series of comm<strong>and</strong>s defined using the Editor that can be executed by an Object such as<br />
a Component or an Element.<br />
logical printer<br />
A logical printer is a printer name specified in a Report. You must map a logical printer to a<br />
physical printer be<strong>for</strong>e printing.<br />
logical reorganization<br />
Trans<strong>for</strong>ms the data from the existing physical database schema into the <strong>for</strong>mat of the<br />
newly developed logical schema in memory each time the data is accessed. File <strong>for</strong>mats<br />
are not altered. Allows a new database schema to be run against the existing old database<br />
schema prior to a physical reorganization.<br />
78616323–000 Glossary–15
Glossary<br />
logically deleted<br />
A term used to describe the status of an Ispec record that has been deleted from a<br />
database as far as all processes are concerned, but is physically still present.<br />
Long name<br />
Long names of Objects are up to 30 characters <strong>and</strong> allow double-byte characters, such as<br />
Kanji, to be used <strong>for</strong> an Object's name. They also allow you to give Objects more<br />
meaningful names. Long names must be used in conjunction with shorter names which<br />
can be used by the host environment.<br />
LSM<br />
M<br />
See Security Module.<br />
Main Logic<br />
User-specified Ispec logic that is executed after any Pre-LINC logic <strong>and</strong> automatic editing<br />
<strong>and</strong> validating sequences have been executed.<br />
MAINT<br />
(1) A System Data item, stored with each record of every St<strong>and</strong>ard, Table, <strong>and</strong> Multiple<br />
Ordinate Memo Component, that indicates whether that record is added, changed or<br />
deleted. (2) In mainframe Systems, a screen field <strong>for</strong> every St<strong>and</strong>ard, Table, <strong>and</strong> Multiple<br />
Ordinate Memo Component used to indicate the database maintenance action request.<br />
MCP environment<br />
The component of the A Series or <strong>ClearPath</strong> HMP NX machine that runs the MCP<br />
operating system.<br />
Memo Component<br />
A Component type that has no Ordinate, <strong>and</strong> which is used to store data of a memor<strong>and</strong>um<br />
nature. See Component, Multiple Ordinate Memo Component.<br />
Memo Data<br />
Memo-type, optional Ispec data that is stored separately to the primary Ispec records to<br />
assist with the optimization of disk usage. Valid <strong>for</strong> MCP based Systems only. See Ispec.<br />
Menu Assistance<br />
A mainframe Painter facility that provides assistance when painting an Ispec screen layout<br />
or Report Frame.<br />
menu <strong>for</strong>mat query<br />
A query created using the various selection screens of Ad Hoc Inquiry. Contrast with SQL<br />
<strong>for</strong>mat query.<br />
Glossary–16 78616323–000
Message Translation Utility (MSGTRANS)<br />
A part of the Multilingual System (MLS) that co-ordinates the output of translated<br />
messages.<br />
MLA<br />
Model<br />
See Multiple Language Mode.<br />
Glossary<br />
Database containing details of Business Segments (Specifications) held by Developer. A<br />
synonym <strong>for</strong> Repository.<br />
Model Directory<br />
A graphical representation of the hierarchical structure of the Business Model. An essential<br />
part of the Developer navigation facilities.<br />
Module<br />
Specification that is a subset of a Module Master. When generated a Module produces a<br />
complete Enterprise Application System. See also Module Master.<br />
Module Master<br />
A complete Specification that contains defined parts (Modules) that can be generated as<br />
separate Enterprise Application Systems. See also Module.<br />
Multilingual System (MLS)<br />
An MCP based facility that provides data structures <strong>and</strong> associated access methods to<br />
store <strong>and</strong> retrieve the translatable text used by software. See also Message Translation<br />
Utility.<br />
multiple language facilities<br />
A collective term <strong>for</strong> the facilities that enable an Enterprise Application System to be<br />
translated <strong>and</strong> used in up to fifteen different languages, from a single Specification.<br />
Multiple Language Mode (MLA)<br />
A facility in mainframe Enterprise Application Environment that enables a language name<br />
or number to be defined. See multiple language facilities.<br />
Multiple Ordinate Memo Component<br />
A Memo Component with one or more Ordinates defined by a specified Profile (that is<br />
sometimes referred to as its Automaint Profile). See also Component, St<strong>and</strong>ard<br />
Component <strong>and</strong> Automaint Profile.<br />
N<br />
navigation tree<br />
In the Administration GUI, a depiction of the Windows domains, servers, environments,<br />
databases, <strong>and</strong> systems. The navigation tree is updated as the user makes changes to the<br />
environment.<br />
78616323–000 Glossary–17
Glossary<br />
NOF<br />
NOFORM<br />
See NOF.<br />
A facility <strong>for</strong> interfacing to <strong>and</strong> from an Enterprise Application System using Non-Formatted<br />
Input/Output, a message-oriented interface between an Enterprise Application user<br />
system, <strong>and</strong> usually, an external system <strong>and</strong> terminal. The interface to Graphical Interface<br />
Workbench uses NOF.<br />
Non-Formatted Input/Output (NOF)<br />
See NOF.<br />
O<br />
OBJ<br />
Object<br />
The file extension <strong>for</strong> a file in st<strong>and</strong>ard object code <strong>for</strong>mat. Files in this <strong>for</strong>mat compile<br />
slowly, but execute quickly. Files in .obj <strong>for</strong>mat cannot be executed unless bound.<br />
Collective term <strong>for</strong> a Component, Event, Inquiry, Report, Global Logic, or Profile.<br />
object files<br />
In <strong>Runtime</strong> <strong>for</strong> the Windows 2000 <strong>and</strong> Windows NT operating systems, the .obj files that<br />
result from compiling source files. Object files usually require linking to other program<br />
modules be<strong>for</strong>e they can be executed.<br />
Object Packaging<br />
Object Packaging allows the creation of executables from supplied Enterprise Application<br />
object files, the installation of Enterprise Application software, the installation of EIFs, <strong>and</strong><br />
the maintenance of your Enterprise Application environment. It also allows the creation of<br />
new object <strong>and</strong> executable packages which can include supplied EIFs. Packages can be<br />
created <strong>for</strong> distribution <strong>and</strong> as backups.<br />
Objects<br />
(1) Objects are one of two methods of distributing Enterprise Application software to<br />
customers. They are the set of object files which must be built into executables on your<br />
site be<strong>for</strong>e Enterprise Application Environment can be run. Object files are built using<br />
Object Packaging. Contrast this with Executables. (2) In <strong>Runtime</strong> <strong>for</strong> the Windows 2000<br />
<strong>and</strong> Windows NT Operating Systems Administration Client, anything that appears in the<br />
navigation tree, including servers, client machines, environments, databases, <strong>and</strong> user<br />
systems.<br />
Offline interface<br />
A facility <strong>for</strong> passing batches of high-volume transactions from external systems into an<br />
Enterprise Application user system.<br />
Glossary–18 78616323–000
OLTP<br />
See Online Transaction Processing.<br />
Glossary<br />
OLTP Buffer Definition file<br />
An OLTP Buffer Definition file holds the data <strong>for</strong>mat <strong>for</strong> communicating with external OLTP<br />
Servers.<br />
OLTP View Ispec<br />
In the host environment, an OLTP View Ispec (OVI) is used to store an OLTP View<br />
Description file. This file holds the data <strong>for</strong>mat <strong>for</strong> communicating with external OLTP<br />
Servers.<br />
On Change Statistical Routine<br />
A statistical routine (<strong>for</strong> example, AVERAGE;) that can be per<strong>for</strong>med on a Data Item as part<br />
of an ON.CHANGE; logic comm<strong>and</strong>.<br />
Online Transaction Processing (OLTP)<br />
A generic method <strong>for</strong> transferring transactions between systems.<br />
ORACLE<br />
Relational database management system used as the underlying database software <strong>for</strong><br />
Enterprise Application Systems based on the UNIX or Windows operating systems.<br />
ORACLE is produced by Oracle Corporation. See also Griffin.<br />
ORACLE Hints<br />
A facility that allows users to add in<strong>for</strong>mation to SQL SELECT statements. Correct use may<br />
improve database per<strong>for</strong>mance, but incorrect use may reduce database per<strong>for</strong>mance.<br />
Using Oracle Hints in an SQL statement overrides the Oracle Optimizer. Users are able to<br />
specify:<br />
• Which index is used in the database access operation<br />
• Whether the index should be read in reverse order<br />
ORACLE SID<br />
An occurrence or instance of an Oracle database. The Oracle SID is a 1- or 2- character<br />
identifier. An ORACLE term <strong>for</strong> a logical storage area that houses user systems <strong>and</strong> control<br />
tables <strong>and</strong> may contain one or more databases. The SID identifies a particular database<br />
occurrence. Equivalent of Griffin Universe. See also tablespace.<br />
ORACLE tablespace<br />
A discrete part of an Oracle SID. Tablespaces in the same Oracle SID can be stored on<br />
different physical devices.<br />
Ordinate<br />
The Data Item of a Component that acts as the unique identifier <strong>for</strong> a record. The access<br />
path to individual Component records.<br />
78616323–000 Glossary–19
Glossary<br />
P<br />
pack<br />
A definition within Enterprise Application of the location where part of a user system or an<br />
environment database is stored. This may be either a tablespace or a directory path.<br />
Pack Association<br />
The Pack Association specifies the location in which the files of the generated system will<br />
be stored on the target host computer.<br />
Pack View<br />
The Pack View in Developer lists all the packs used in the Systems options of the currently<br />
open Model. This specifies the Pack associations, or the location in which that part of the<br />
System or database is stored. See Pack.<br />
Painter<br />
patch<br />
A facility of Enterprise Application Environment used to define an Ispec screen layout or<br />
Report Frame layout.<br />
A set of changes to a Specification made over a period of time by users signing on to<br />
Enterprise Application Environment under a specific Patch identifier value.<br />
Patch identifier<br />
A number used to identify <strong>and</strong> group changes to a Specification by one or more users.<br />
Applies when the Patch identification option is selected <strong>for</strong> that Specification. Contrast<br />
with Change identifier.<br />
Per<strong>for</strong>mable Global Logic<br />
Logic that can be executed by any number of Ispecs <strong>and</strong> Reports. Contrast with Insertable<br />
Global Logic.<br />
physical delete<br />
Removal of a record from a database or repository.<br />
physical reorganization<br />
Copies <strong>and</strong> trans<strong>for</strong>ms the physical data from the existing database into a <strong>for</strong>m which<br />
matches the new database schema.<br />
population<br />
Also called Expected Number. The maximum number of records expected to be stored in<br />
the database <strong>for</strong> an Ispec.<br />
Pre-LINC Logic<br />
User-specified Ispec logic that is executed be<strong>for</strong>e the Ispec Main logic.<br />
Glossary–20 78616323–000
Pre-Screen Logic<br />
A section of user-specified Ispec logic that is executed be<strong>for</strong>e the screen layout is<br />
displayed on the terminal.<br />
Glossary<br />
Primary Database Options screen<br />
The screen in Host Builder <strong>for</strong> setting basic options <strong>and</strong> parameters <strong>for</strong> an Enterprise<br />
Application System. The screen is displayed whenever a new Specification is created.<br />
Product Menu Utility<br />
Product Menu is a menu-driven utility to access Object Packaging features. See Object<br />
Packaging <strong>for</strong> details of the functions that can be per<strong>for</strong>med with Product Menu.<br />
Profile<br />
(1) An index to a specified selection of records. (2) A method of providing access to just<br />
those records that are required to per<strong>for</strong>m a specific function. (3) A functional view of the<br />
database.<br />
Profile Data<br />
A Data Item that is physically stored in a Profile as well as in its associated Ispec. See also<br />
Profile.<br />
Profile Ordinate<br />
The Data Item by which a Profile accesses individual records. A Profile can have several<br />
Profile Ordinates. See also Profile.<br />
Q<br />
query class<br />
See access class.<br />
Query Compiler<br />
The Ad Hoc Inquiry facility that validates an entered query <strong>and</strong> trans<strong>for</strong>ms it into a st<strong>and</strong>ard<br />
internal code <strong>and</strong> <strong>for</strong>mat. See also query trans<strong>for</strong>mation.<br />
Query Front End<br />
The Ad Hoc Inquiry user interface that allows a query to be entered.<br />
Query Optimizer<br />
The Ad Hoc Inquiry facility that selects the most efficient way to access the database <strong>for</strong><br />
a query.<br />
Query Output H<strong>and</strong>ler<br />
The Ad Hoc Inquiry facility that enables users to manipulate query output.<br />
78616323–000 Glossary–21
Glossary<br />
Query Processor<br />
The Ad Hoc Inquiry facility that interprets the query code <strong>and</strong> runs the query against the<br />
database.<br />
Query Processor report<br />
For Ad Hoc Inquiry, the program that per<strong>for</strong>ms the functions of the Query Processor.<br />
query trans<strong>for</strong>mation<br />
For Ad Hoc Inquiry, the process per<strong>for</strong>med by the Query Compiler to convert a validated<br />
query into a st<strong>and</strong>ard internal <strong>for</strong>m.<br />
queued query<br />
For Ad Hoc Inquiry, a query waiting <strong>for</strong> resources to begin execution.<br />
R<br />
recovery<br />
The process of restoring database files from a backup <strong>and</strong> per<strong>for</strong>ming roll-<strong>for</strong>ward recovery<br />
from a current transaction log file. Failed Reports must be restarted manually, as they are<br />
not automatically restarted by the recovery process.<br />
relation name<br />
For Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an Event<br />
Profile. Also called a table.<br />
relationship<br />
An association between two Elements. Relationships may be a result of design (<strong>for</strong><br />
example, added using a graph) or logic (<strong>for</strong> example, adding a FLAG; comm<strong>and</strong> to an<br />
Ispec).<br />
relative day number<br />
A date expressed as the number of days since January 1 of the base year. The relative day<br />
number of January 1 of the base year is zero. See also base year.<br />
Remote Access to Enterprise Application<br />
The Remote Access server resides on the <strong>Runtime</strong> host <strong>and</strong> provides the basis <strong>for</strong><br />
communication between user Views <strong>and</strong> Enterprise Application Systems. Can be used<br />
with Graphical Interface Workbench as well as Component Enabler Viewer applications. It<br />
per<strong>for</strong>ms services previously provided by WDP. Formerly known as RATL Server. See<br />
Component Enabler, Graphical Interface Workbench, Workstation Driver Program (WDP).<br />
reorganization<br />
The process by which the physical database <strong>for</strong> a System is updated to match the logical<br />
definition held in the Repository. See also logical reorganization <strong>and</strong> physical<br />
reorganization.<br />
Glossary–22 78616323–000
Report<br />
Glossary<br />
Part of a Specification generated <strong>and</strong> used to produce output or to carry out specialized<br />
batch processing of a database. Consists of Report Frames <strong>and</strong> Report Main logic, <strong>and</strong> a<br />
number of options that define the operation <strong>and</strong> output of the Report.<br />
Report Frame<br />
Layout that contains display text <strong>and</strong> Data Items, <strong>and</strong> some associated logic that is part of<br />
a Report. The logic is executed (often to define the Data Items in the layout) <strong>and</strong> then the<br />
layout is included in the Report output. Report Frames are accessed as single units from<br />
the logic of Report Frame or from Main logic of the Report.<br />
Report Group<br />
A set of Reports that are generated as a group. All the Reports assigned to the group are<br />
generated by selecting the Report Group <strong>for</strong> generation.<br />
Report Initiation Program (RIP)<br />
An MCP based utility that enables you to execute a line printer Report or terminal printer<br />
Report in batch mode.<br />
Report Output Control System (ROC)<br />
A utility that provides control over the output of a Report.<br />
Repository<br />
Database containing details of Business Segments (Specifications) held by Developer. A<br />
synonym <strong>for</strong> Model.<br />
reserved words<br />
Words reserved <strong>for</strong> system use. Each architecture has its own set of reserved words.<br />
resource locking<br />
A facility of the host environment that prevents access to parts of a Specification by more<br />
than one user at a time.<br />
ROC Background Run<br />
For <strong>OS</strong> <strong>2200</strong> Systems, a background run that identifies Report output requests <strong>and</strong> spools<br />
the output to the required print queue. There is one ROC Background Run <strong>for</strong> each<br />
<strong>Runtime</strong>.<br />
rollback segment<br />
In Oracle, a segment that contains an image of data be<strong>for</strong>e committing to a transaction.<br />
Used <strong>for</strong> rolling back uncommitted transactions, read consistency, <strong>and</strong> recovery.<br />
row<br />
For Ad Hoc Inquiry, an SQL term equivalent to a Component record or an Event record.<br />
78616323–000 Glossary–23
Glossary<br />
RPC<br />
Remote Procedure Call, a Windows protocol that runs background services that are<br />
necessary <strong>for</strong> the operation of the Administration Client <strong>and</strong> <strong>Runtime</strong> <strong>for</strong> the<br />
Windows 2000 <strong>and</strong> Windows NT operating systems.<br />
<strong>Runtime</strong><br />
A collective term <strong>for</strong> the software programs required to operate, control <strong>and</strong> audit an<br />
Enterprise Application System <strong>and</strong> its Database.<br />
<strong>Runtime</strong> plat<strong>for</strong>ms<br />
The plat<strong>for</strong>ms on which applications developed <strong>and</strong> built using Enterprise Application<br />
software runs: Windows 2000, Windows NT, <strong>OS</strong> <strong>2200</strong>, MCP, <strong>and</strong> the UNIX Operating<br />
System.<br />
<strong>Runtime</strong> Test Environment<br />
Software that enables testing <strong>and</strong> debugging of Enterprise Application Systems on<br />
mainframe hosts.<br />
S<br />
schema<br />
screen<br />
Database structure.<br />
In Developer, a screen is a means of entering a transaction. Screens are usually designed<br />
<strong>for</strong> a single purpose <strong>and</strong> so each System function will usually have a specific screen.<br />
Screens may have associated logic.<br />
Screen Build mode<br />
A host environment Painter facility that is used to specify a new Ispec screen layout.<br />
search expression<br />
For Ad Hoc Inquiry, a logical expression used in a search list to define records to be<br />
included in query output.<br />
search list<br />
For Ad Hoc Inquiry, the part of a query that determines whether records will be included in<br />
the output.<br />
security access<br />
For Ad Hoc Inquiry, full access to all queries.<br />
security class<br />
For Ad Hoc Inquiry, a type of user access to queries. See access class.<br />
Glossary–24 78616323–000
Glossary<br />
security level<br />
A value from 0 through 9 that is assigned to a specific user or terminal to restrict access<br />
to functions.<br />
Security Module (LSM)<br />
A utility which provides security facilities <strong>for</strong> Enterprise Application environments.<br />
select list<br />
For Ad Hoc Inquiry, the part of a query that defines the Data Items to be included in the<br />
output.<br />
Setup Data Array or Global Setup Data Array<br />
Use a Setup Data array or Global Setup Data array to store multiple values. An individual<br />
value is accessed by specifying values <strong>for</strong> the indexes of the array. Indexes are numeric<br />
Setup Data items or Global Setup Data items.<br />
Setup Data item<br />
A Data Item used in memory only <strong>for</strong> data manipulation by an Ispec or Report. See also<br />
Global Setup Data item, Group Setup Data item.<br />
Shadow Report<br />
Part of a Report used to produce additional output separate from that produced by the<br />
primary functions of the Report.<br />
SID<br />
The two-character identifier of an Oracle database. In <strong>Runtime</strong> <strong>for</strong> the Windows 2000 <strong>and</strong><br />
Windows NT operating systems, database, Database ID <strong>and</strong> Oracle SID are synonymous.<br />
Sleeping Report<br />
A Report that, by the use of the SLEEP; logic comm<strong>and</strong>, stops executing <strong>for</strong> a<br />
predetermined number of seconds or until reactivated by your runtime System.<br />
SOLAR<br />
For <strong>OS</strong> <strong>2200</strong> Systems, a product used to install Enterprise Application Software.<br />
sort expression<br />
For Ad Hoc Inquiry, a logical expression used in a sort list to define output sort order.<br />
sort list<br />
For Ad Hoc Inquiry, the part of a query that defines the order of the output.<br />
Specification<br />
(1) The source definition of an Enterprise Application System. Specifications consist of<br />
screen definitions, database definitions, <strong>and</strong> processing logic. (2) The result of specifying<br />
a Business Model using Developer. (3) The source from which an Enterprise Application<br />
System is generated.<br />
78616323–000 Glossary–25
Glossary<br />
spooler<br />
See Terminal Printer Spooler.<br />
SQL <strong>for</strong>mat query<br />
An SQL query entered in free <strong>for</strong>mat in Ad Hoc Inquiry. Contrast with menu <strong>for</strong>mat query.<br />
SQL Server<br />
A relational database management system that is optionally used as the database software<br />
<strong>for</strong> Enterprise Application Systems based on Windows operating systems. SQL Server 7.0<br />
is a product of Microsoft Corporation. See also ORACLE.<br />
St<strong>and</strong>ard Component<br />
A Component type that requires a single Ordinate. See also Component.<br />
St<strong>and</strong>ard Report<br />
A specific type of Report that uses the Report Output Control (ROC) System, <strong>and</strong> whose<br />
output is written to the database. Subsequent use of the output is determined by the user.<br />
See Report Output Control System. Contrast with Direct Report.<br />
station<br />
(1) In Enterprise Application terminology, a general term <strong>for</strong> a method used to identify<br />
users. (2) For UNIX based Systems, station equates to user name, while <strong>for</strong> <strong>OS</strong> <strong>2200</strong><br />
based Systems, station equates to userid.<br />
status line<br />
A line on a screen <strong>for</strong> the display of system messages.<br />
structure<br />
(1) In the host environment, part of a Specification that can be selected (<strong>for</strong> example, <strong>for</strong><br />
printing, copying, or extraction). (2) For Ad Hoc Inquiry, part of an Enterprise Application<br />
Database that can be the subject of a query.<br />
structure list<br />
For Ad Hoc Inquiry, the part of a query that defines the structures to be included.<br />
Sub Items<br />
A Global Setup Data item that has been defined <strong>for</strong> a Group Global Setup Data item or a<br />
Setup Data item that has been defined <strong>for</strong> a Group Setup Data item.<br />
Sub Scripts<br />
A Data Item that has been defined as an index <strong>for</strong> either a Global Setup Data Array or a<br />
Setup Data Array.<br />
Supervisor<br />
A facility of the host environment enabling administration-level functions.<br />
Glossary–26 78616323–000
System<br />
Glossary<br />
In Builder each System consists of a configuration of elements <strong>and</strong> the options assigned<br />
to these elements. The options define the generation options <strong>for</strong> the host-based<br />
environment on which the system will be deployed.<br />
System comm<strong>and</strong><br />
A comm<strong>and</strong> to assist in the operation of a System or Report. Formerly known as a colon<br />
comm<strong>and</strong>.<br />
System Data item<br />
Data Item that is automatically part of your Specification. Used <strong>for</strong> accessing or setting<br />
parameter or control-type data in logic. Some System Data items are stored automatically<br />
in your Enterprise Application Database (<strong>for</strong> example, MAINT).<br />
System Directory<br />
A graphical representation of the hierarchical structure each System configured <strong>for</strong> a<br />
Business Model. It lists the current <strong>and</strong> previous configurations <strong>for</strong> each System, showing<br />
the Elements assigned to the system <strong>and</strong> the processing options defined <strong>for</strong> them. The<br />
System Directory provides the basis <strong>for</strong> the build process.<br />
System Element<br />
Collective term <strong>for</strong> the individual parts of the System. An Element may be any of the<br />
following: Business Segment, Bundle, Ispec, Global Logic, Profile, Report Group, or<br />
Report.<br />
System Specification<br />
A specification that represents the configuration of Elements within a deployed host<br />
system, <strong>and</strong> the generation options required to generate a set of executables <strong>for</strong> the<br />
specified host environment. See Generate Set.<br />
T<br />
table<br />
For Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an Event<br />
Profile. Also called relation name.<br />
Table Component<br />
A Component type that is used to store low-volume, frequently accessed data, such as<br />
code tables. See also Component.<br />
tablespace<br />
Discrete part of an ORACLE SID or Griffin Universe. Tablespaces in the same ORACLE SID<br />
or Griffin Universe can be stored on different physical devices.<br />
target host<br />
The name of the specific host on which a generated Enterprise Application System will be<br />
deployed. See also Host Specification.<br />
78616323–000 Glossary–27
Glossary<br />
Teach screen<br />
A user-written screen display of in<strong>for</strong>mation about an Ispec, intended to provide online help<br />
<strong>for</strong> end users at runtime.<br />
Terminal Printer Spooler (TPS)<br />
An MCP based Enterprise Application Utility that enables users to manipulate the output<br />
of a Report to terminal printers.<br />
TPS<br />
Trace<br />
See Terminal Printer Spooler.<br />
A facility to monitor the execution of logic of an Ispec or Report in your Enterprise<br />
Application System. Contrast with <strong>Runtime</strong> Test Environment.<br />
transaction log file<br />
File to which be<strong>for</strong>e <strong>and</strong> after images of all Developer transactions are written <strong>for</strong> recovery<br />
<strong>and</strong> restart purposes.<br />
Translation Screen<br />
A copy of an Ispec screen that is modified to create a secondary language version.<br />
U<br />
Usage Input<br />
An Ispec attribute that enables a Data Item to be entered or displayed on the screen,<br />
accessed by logic, but not stored in the database.<br />
Usage Input Ispec<br />
An Event or Memo Component that is not output to the database, <strong>and</strong> where Data Items<br />
default to Usage Input. (Individual Data Items can be set to Usage Inquiry.)<br />
Usage Input-Output<br />
An Ispec attribute that enables a Data Item to be entered or displayed on the screen,<br />
accessed by logic, <strong>and</strong> stored in the database.<br />
Usage Input-Output Ispec<br />
Ispec that is both Usage Input <strong>and</strong> Usage Output.<br />
Usage Inquiry<br />
An Ispec attribute that enables a Data Item displayed on the screen, but not to be entered<br />
on the screen, nor written to the database.<br />
Usage Output<br />
An Ispec attribute that enables a Data Item to be written to the database <strong>and</strong> accessed by<br />
logic, but not entered or displayed on the screen.<br />
Glossary–28 78616323–000
Usage Output Ispec<br />
An Ispec that is written to the database, but does not have a screen display.<br />
Glossary<br />
user system<br />
An instance of a Specification. Generally refers to a generated <strong>and</strong> deployed Enterprise<br />
Application user system.<br />
user system tables<br />
Tables that contain end user data (Ispec data) of a specific Enterprise Application user<br />
system.<br />
V<br />
Validation EIF<br />
Validation EIFs are a special type of EIF which provide support <strong>for</strong> newly validated versions<br />
of Enterprise Application Environment support software such as ORACLE, Griffin, COBOL,<br />
<strong>and</strong> Tuxedo. See EIF.<br />
value expression<br />
For Ad Hoc Inquiry, a logical expression used in an SQL <strong>for</strong>mat query to define a value, <strong>and</strong><br />
made up of Data Items, literals, operators, <strong>and</strong> functions.<br />
value logic<br />
Logic associated with a dictionary item that determines acceptable values <strong>for</strong> that item.<br />
version control<br />
A method <strong>for</strong> identifying different versions of an Enterprise Application System by version<br />
number, description, <strong>and</strong> generation date.<br />
Version Control<br />
An optional feature of Developer that provides source control of versionable Enterprise<br />
Application objects such as Model definitions, data dictionary items, Ispecs, Profiles, <strong>and</strong><br />
Reports.<br />
W<br />
watch<br />
A feature of the Developer Test Debugger that monitors, or 'watches', the state of a Data<br />
Item. When logic execution is stopped during debugging, the value of the watch item is<br />
displayed in the Watch Window.<br />
Wildcard<br />
Represents relationships with objects outside the Business Segment, or outside the<br />
Model. For example, a flat file that is read or extracted, or an external system called by the<br />
Enterprise Application System.<br />
78616323–000 Glossary–29
Glossary<br />
Workstation<br />
In a client-server environment, a PC or workstation that is connected to a server, usually<br />
by a network. The workstation runs the client portion of client-server software.<br />
Workstation Driver Program (WDP)<br />
A server-resident component of <strong>Runtime</strong> <strong>for</strong> the Windows 2000 <strong>and</strong> Windows NT<br />
operating systems. Its function is to pass data between the Graphical Interface<br />
Workbench workstation <strong>and</strong> the application on the runtime host. It also converts screen<br />
definition files during the direct generation of an application.<br />
Workstation Driver Program (WDP) listener<br />
This service listens <strong>for</strong> <strong>and</strong> accepts connection requests from Graphical Interface<br />
Workbench clients.<br />
Workstation listener port<br />
A Windows TCP/IP port assigned to the Workstation Driver Program (WDP) listener or a<br />
particular environment. This value must be changed to a unique number <strong>for</strong> each user<br />
system environment during installation.<br />
Glossary–30 78616323–000
Index<br />
A<br />
ALIB$ file<br />
security attributes, 3–9<br />
application groups<br />
allocating queue items, 2–12<br />
configuring EXEC with, 2–11<br />
local, 3–12<br />
<strong>Runtime</strong>, 2–11<br />
shared, 3–12, 3–13<br />
XTC System, 3–12<br />
Application Recovery Feature (ARF), 3–16<br />
attributes<br />
supported IBM 3270, C–11<br />
supported terminal, C–3<br />
B<br />
background runs<br />
starting, 3–18<br />
C<br />
change control<br />
installation options <strong>for</strong>, 3–25<br />
CL<strong>OS</strong>EDOWN program, 3–19<br />
CMS 1100<br />
configuration of, 2–15<br />
COMUS<br />
Common Bank Attributes screen, B–15<br />
General Parameter screens, B–4<br />
Processor File Names screens, B–11, B–13<br />
COMUS parameters<br />
additional I-Language bank, B–17<br />
Common Bank attribute, B–15<br />
Common Bank BDI, B–6<br />
configure, B–1<br />
HUB configuration, B–18<br />
LRSS server configuration, B–21<br />
OLTP configuration, B–1<br />
preview of, B–1<br />
Remote Subroutine Server configuration,<br />
B–21<br />
run, B–22<br />
Software build, B–22<br />
<strong>Configuration</strong> Process Main Menu screen, 3–4<br />
configuration sets<br />
creating, 3–4<br />
configure<br />
changing defaults <strong>for</strong>, 3–3<br />
COMUS parameters <strong>for</strong>, B–1<br />
files created during, A–5<br />
78616323–000 Index–1<br />
D<br />
databases<br />
files created when generating, A–6<br />
deinstalling<br />
Host Builder, 3–34<br />
<strong>Runtime</strong>, 3–34<br />
Deployment<br />
XTC with, 3–13<br />
DIM attribute<br />
terminals supporting, C–2<br />
disk storage<br />
requirements <strong>for</strong>, 2–4<br />
E<br />
EXEC<br />
application groups <strong>for</strong>, 2–12<br />
configuration of non-<strong>OS</strong><strong>2200</strong> LCOPY tapes,<br />
2–15<br />
configuring application groups <strong>for</strong>, 2–11<br />
configuring freespace files <strong>for</strong>, 2–15<br />
configuring parameters <strong>for</strong> HVTIP, 2–14<br />
EXPRGENVIRON configuration parameter,<br />
2–14<br />
large files configuration of, 2–15<br />
EXPRGENVIRON<br />
configuring EXEC <strong>for</strong>, 2–14
Index<br />
F<br />
FCC<br />
terminal attributes in, C–3<br />
files<br />
Enterprise Application-created, A–1<br />
generated database, A–6<br />
loading Host Builder, A–4<br />
System generated, A–5<br />
<strong>for</strong>eign terminals<br />
inserting code to h<strong>and</strong>le, C–8<br />
supported, C–4<br />
freespace files<br />
configuring <strong>for</strong> EXEC, 2–15<br />
G<br />
generate<br />
files created during, A–5, A–6<br />
generating a migrated System, 4–11<br />
GLB.MFLAG, C–6<br />
GLB.STYLE, C–4<br />
GLB.WORK, 2–13<br />
Graphical Interface Workbench, 4–10<br />
migrating Systems using, 4–10<br />
non-use of, 4–10<br />
support <strong>for</strong>, 4–10<br />
H<br />
hardware requirements, 2–4<br />
highlighting attributes<br />
IBM 3270 terminal support of, C–11<br />
supported terminal, C–3<br />
Host Builder<br />
configuring, 3–27<br />
deinstalling, 3–34<br />
identification mode <strong>for</strong>, 3–26<br />
installing, 3–22, 3–27<br />
loading files <strong>for</strong>, A–4<br />
loading from Release tape, 3–23<br />
multiple copies of, 3–29<br />
overview of, 2–1<br />
requirements <strong>for</strong>, 2–8<br />
Host Builder messages<br />
translation of, B–17<br />
HUB<br />
<strong>Configuration</strong> Parameter screens, B–18<br />
considerations <strong>for</strong>, 2–9<br />
installation modes <strong>for</strong>, 3–10<br />
HVTIP<br />
library <strong>for</strong> XTC System, 3–13<br />
HVTIP parameters <strong>for</strong><br />
EXEC, 2–14<br />
Index–2 78616323–000<br />
I<br />
IBM 3270 terminals<br />
modified data tag (MDT), C–13<br />
installation<br />
COMUS parameters <strong>for</strong>, B–1<br />
HUB, 3–10<br />
<strong>Runtime</strong>, 3–2<br />
XTC Deployment, 3–13<br />
<strong>Installation</strong> Verification Procedure (IVP), 3–9<br />
installing<br />
Host Builder, 3–22<br />
registered packages from, 3–8<br />
registering output tape, 3–8<br />
runstream modifying, 3–8<br />
<strong>Runtime</strong> copies, 3–21<br />
Unisys-supplied changes, 3–2<br />
intersystem communications (see HUB), 2–9<br />
K<br />
Kanji<br />
support of, C–6<br />
L<br />
LCOPY<br />
compatibility with Host Builder releases,<br />
4–2<br />
loading Specifications, 4–2<br />
migration, 4–2<br />
line resequencing<br />
inhibiting, 3–25<br />
locking<br />
resource, 3–25<br />
LRSS server<br />
<strong>Configuration</strong> Parameter screens, B–21<br />
lt300 terminal support, 2–4
M<br />
MCB<br />
configuration of, 2–15<br />
MCB/CMS<br />
trigger characters <strong>for</strong>, 2–16<br />
memory<br />
requirements <strong>for</strong>, 2–4<br />
Message Control Bank (see MCB), 2–15<br />
migration<br />
environmental settings, 4–4<br />
extract <strong>for</strong>mat <strong>for</strong> data interchange, 4–5<br />
first generation after, 4–11<br />
Global Setup Data blocks, 4–4<br />
Graphical Interface Workbench, 4–10<br />
localization, 4–6<br />
procedure, 4–1<br />
rounding from COMPUTE comm<strong>and</strong>s, 4–5<br />
using LCOPY, 4–2<br />
modified data tag (MDT)<br />
<strong>for</strong> IBM 3270 terminals, C–13<br />
O<br />
OLTP<br />
considerations <strong>for</strong>, 2–10<br />
online help<br />
<strong>Configuration</strong> Parameter screen, B–3<br />
<strong>OS</strong> <strong>2200</strong> based software (see System software),<br />
2–6<br />
output tape<br />
SOLAR registration of, 3–8<br />
P<br />
PAEXEC<br />
installing <strong>Runtime</strong> with, 3–14<br />
switching between hosts in, 3–14<br />
page size<br />
calculating, 2–13<br />
setting default <strong>for</strong>, 3–17<br />
STNUTIP calculating <strong>for</strong>, 2–14<br />
parameter changes<br />
building, 3–5<br />
PTTYP values<br />
mapping terminal types to, C–7<br />
providing <strong>for</strong> additional, C–7<br />
terminal types in, C–6<br />
Index<br />
78616323–000 Index–3<br />
R<br />
RDMS<br />
table storage area, A–2<br />
RDMS tables<br />
details of, 3–19<br />
unsaved of, 3–20<br />
reinstalling<br />
<strong>Runtime</strong>, 3–19<br />
Release tape<br />
COMUS registration of, 3–3<br />
files on Host Builder, 3–22<br />
<strong>Runtime</strong>, 3–7<br />
Remote Subroutine Server<br />
<strong>Configuration</strong> Parameter screens, B–21<br />
Report Output Control System (ROC)<br />
installing, 3–30<br />
overview of, 2–1<br />
requirements <strong>for</strong>, 2–8<br />
reserved words<br />
loading of, 3–24<br />
target host, 3–24<br />
resource locking<br />
installation options <strong>for</strong>, 3–25<br />
REVERSE attribute<br />
terminals supporting, C–2<br />
ROC<br />
configuring, 3–31<br />
installing, 3–30<br />
loading from Release tape, 3–30<br />
requirements <strong>for</strong>, 2–8<br />
runstream<br />
modifying when installing, 3–8<br />
<strong>Runtime</strong><br />
be<strong>for</strong>e using, 3–15<br />
configuration process <strong>for</strong>, 2–7<br />
deinstalling, 3–34<br />
files created when installing, A–2<br />
installing, 3–2<br />
installing copies of, 3–21<br />
overview of, 2–1<br />
PAEXEC with, 3–14<br />
reinstalling, 3–11, 3–19<br />
release tape <strong>for</strong>, 3–7<br />
requirements <strong>for</strong>, 2–8<br />
SOLAR installation of, 3–7<br />
switching control of, 3–11
Index<br />
S<br />
screen h<strong>and</strong>ling code<br />
inserting your own, C–4, C–9<br />
local, C–9<br />
SGS statements<br />
terminal type, C–7<br />
SNA3270 terminals<br />
support of, C–10<br />
Software<br />
about, 2–1<br />
products of, 2–1<br />
software requirements, 2–6<br />
SOLAR<br />
installing <strong>Runtime</strong>, 3–9<br />
special privileges<br />
set up of, 3–8<br />
Specifications, 4–2<br />
generating after migration, 4–11<br />
loading using LCOPY, 4–2<br />
station details<br />
STN System comm<strong>and</strong>, C–4<br />
STN System comm<strong>and</strong><br />
station details, C–6<br />
STNUTIL program<br />
commits by, 2–14<br />
System software<br />
applying changes to, 2–17<br />
installing required, 2–11<br />
m<strong>and</strong>atory requirements, 2–6<br />
optional, 2–7<br />
pre-installation tasks <strong>for</strong>, 2–11<br />
requirements <strong>for</strong>, 2–6<br />
Systems<br />
files created when generating, A–5<br />
setting maximum number of, B–16<br />
S_T_N records<br />
terminal type in, C–4<br />
T<br />
templates<br />
target host, 3–24<br />
temporary files<br />
deleting, 3–33<br />
deleting installation, 3–28<br />
terminal records<br />
TIP files holding, 2–12<br />
terminal type<br />
lowercase alpha value of, C–6<br />
terminals<br />
attributes supported <strong>for</strong>, C–3<br />
default types of, C–7<br />
<strong>for</strong>eign, C–4, C–8, C–9<br />
supported, 2–4, C–1, C–4<br />
types of, C–4, C–5, C–6, C–7<br />
unsupported, C–4<br />
TERMTABLE<br />
terminal type in, C–7<br />
TIP Error H<strong>and</strong>ling Program<br />
defining, 3–17<br />
TIP file<br />
holding terminal records with, 2–12<br />
TIP Library<br />
reloading, 3–16<br />
TIP memory<br />
allocation of, 3–15<br />
TIP memory groups<br />
changing, 3–15<br />
creating, 3–15<br />
reloading, 3–16<br />
translation<br />
Host Builder messages, B–17<br />
trigger characters, 2–16<br />
Index–4 78616323–000<br />
U<br />
UCS Subsystems<br />
considerations <strong>for</strong>, 2–10<br />
UDS software<br />
configuration of, 2–16<br />
Unisys-supplied changes<br />
installing, 3–2<br />
Universal Data Systems (see UDS), 2–16<br />
X<br />
XTC<br />
application groups with, 3–12<br />
COMUS configuring <strong>for</strong>, 3–13<br />
HVTIP library with, 3–13<br />
installing Deployment with, 3–13<br />
SOLAR installing <strong>for</strong>, 3–13<br />
UDS facility <strong>for</strong>, 3–12<br />
Z<br />
:STN comm<strong>and</strong> (station details), C–4, C–6
Unisys<br />
*78616323-000*<br />
78616323-000