Runtime for ClearPath OS 2200 Software Release Announcement

Unisys e-@ction 

Enterprise Application 

Runtime for ClearPath 

OS 2200 

Software Release Announcement for 

Release 3R1A 

Copyright © 2000 Unisys Corporation. 

All rights reserved. 

Printed in USA 

November 2000 78616414-000 

Unisys

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

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

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

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

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

damages. 

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

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

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

and/or additions. 

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

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

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

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

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

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

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

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

All terms which may be mentioned in this document that are known to be trademarks or service marks have been 

appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this information. Use of a term in this 

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

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

trademarks of Unisys Corporation. 

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

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

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

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

Corporation in the United States and/or other countries. 

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

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

architecture developed by Sun Microsystems, Inc. 

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

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

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

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

Contents 

Section 1. General Description........................................................... 1–1 

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

Enterprise Application Environment ............................................1–1 

Graphical Interface Workbench ...................................................1–3 

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

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

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

Product Overview ...........................................................................................1–3 

The OS 2200 based 3R1A Enterprise Application Environment .1–4 

Runtime 3R1A for ClearPath OS 2200 ........................................1–4 

Host Builder 3R1A for ClearPath OS 2200 ..................................1–5 

Developer 3.1A ...........................................................................1–6 

Runtime Test Environment 4R1 for ClearPath OS 2200 .............1–6 

Section 2. Product Interdependencies................................................ 2–1 

Hardware Requirements ................................................................................2–1 

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

Enterprise Application Software ..................................................2–2 

Mandatory Software ...................................................................2–2 

Optional System Software ..........................................................2–3 

Network Software .......................................................................2–3 

Requirements for Host Builder 3R1A for ClearPath OS 2200 .....2–3 

Section 3. Migration Requirements .................................................... 3–1 

Pre-Migration Tasks ........................................................................................3–1 

Migration Issues ..........................................................................3–1 

Reference Material ......................................................................3–2 

Migrating from 2200-based LINC Deployment 16R3 .....................................3–2 

Section 4. Release Functionality ........................................................ 4–1 

New Features in Runtime 3R1A for ClearPath OS 2200 ................................4–1 

Runtime Development Enhancements .......................................4–3 

Database Performance Enhancements .......................................4–6 

Component Enabler Enhancements ...........................................4–7 

Developer Security Enhancements .............................................4–8 

Reporting Enhancements ............................................................4–8 

Printing Enhancements ...............................................................4–9 

Removal of DOC .........................................................................4–9 

78616414–000 iii

Contents 

Section 5. Restrictions and Known Limitations.................................. 5–1 

System Restrictions ....................................................................................... 5–1 

New Feature Restrictions .............................................................................. 5–1 

Section 6. Support .............................................................................. 6–1 

Support Online ............................................................................................... 6–1 

Product Support ............................................................................................. 6–1 

Tech Advantage .............................................................................................. 6–2 

Notice of De-implementations ....................................................................... 6–2 

Section 7. Customer Product Information.......................................... 7–1 

3.1A Documentation CD-ROM ...................................................................... 7–1 

OS 2200 Documentation Library .................................................................... 7–2 

On-line Help ................................................................................................... 7–2 

Section 8. Ordering Procedure ........................................................... 8–1 

Product Licensing Options ............................................................................. 8–1 

Style Types .................................................................................. 8–2 

Style IDs for Runtime 3R1A for ClearPath OS 2200 ...................................... 8–2 

New Styles ................................................................................. 8–2 

Subscription Style IDs ................................................................. 8–4 

Update Style IDs ......................................................................... 8–4 

iv 78616414–000

Section 1 

General Description 

Unisys e-@ction Branding 

In 2000 all Unisys products and services have been named or renamed using the Unisys 

e-@ction Branding schema listed in the table below. The purpose of this initiative is to 

shift the naming of Unisys products and services from component or system level to the 

solution level. 

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

Application Environment, while the PowerClient range will go under the umbrella of 

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

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

Enterprise Application Environment 

The following tables identify the new names for all LINC and PowerClient products. 

New Product LINC Product 


Enterprise Application Environment 

Unisys e-@ction Enterprise Application 

Developer 


Developer Test 


Developer Security 


Developer Version Control Client 


Developer Version Control Server 


Developer Repository 


Builder 


Builder for ClearPath MCP 

78616414–000 1–1 

LINC 

LINC Development 

LINC Development Test (LDA Runtime) 

LINC Development Security 

LINC Development Version Control 

Client 

LINC Development Version Control 

Server 

LINC Development Repository 

LINC Generate 

LINC Generate for MCP


New Product LINC Product 


Host Builder for ClearPath OS 2200 


Builder for the Windows 2000 and Windows 

NT Operating Systems 


Builder for HP-UX 


Builder for DYNIX/ptx 


Builder for Sun Solaris 


Builder for IBM AIX 


Builder for UnixWare 


Runtime 


Runtime for ClearPath MCP 


Runtime for ClearPath OS 2200 


Runtime for the Windows 2000 and 

Windows NT Operating Systems 


Runtime for HP-UX 


Runtime for DYNIX/ptx 


Runtime for Sun Solaris 


Runtime for IBM AIX 


Runtime for UnixWare 


Runtime Test Environment 


Component Enabler 


Web Enabler 

LINC Generate for OS 2200 

LINC Generate for Windows NT 

LINC Generate for HP-UX 

LINC Generate for Sequent DYNIX/ptx 

LINC Generate for Sun Solaris 

LINC Generate for IBM AIX 

LINC Generate for UnixWare 

LINC Deployment 

LINC Deployment for MCP 

LINC Deployment for OS 2200 

LINC Deployment for NT 

LINC Deployment for HP-UX 

LINC Deployment for Sequent DYNIX/ptx 

LINC Deployment for Sun Solaris 

LINC Deployment for IBM AIX 

LINC Deployment for UnixWare 

LINC Interpretive Test Environment 

(LITE) 

PowerClient ActiveLINC 

PowerClient Web Agent 

1–2 78616414–000

Graphical Interface Workbench 

About This Document 

Purpose 

Audience 


This Software Release Announcement presents an overview of Enterprise Application 

Runtime 3R1A for ClearPath OS 2200 and describes its new features. It should be read in 

conjunction with other product information for Runtime 3R1A for ClearPath OS 2200. 

The primary audience for this Software Release Announcement is current LINC 

Deployment users who wish to upgrade to Enterprise Application Runtime 3R1A for 

ClearPath OS 2200. 

The secondary audience is prospective customers. 

Product Overview 

New Product Current Product 


Graphical Interface Workbench 


Graphical Interface Developer 


Graphical Interface User 


Graphical Interface Storage Facility 

PowerClient 

PowerClient Development 

PowerClient Runtime 

PowerClient Central Storage Facility 

The main objective of the new Unisys e-@ction Enterprise Application Environment is to 

provide improved support for transferring from host-based development to workstationbased 

Enterprise Application development. The intention is also to provide synergy with a 

more contemporary approach to technology. 

The main objective of the new Runtime 3R1A for ClearPath OS 2200 product within the 

Enterprise Application Environment is to provide new support for workstation-based 

development while continuing to provide support for host-based development and 

generates. 

Developing Enterprise Application systems in an entirely workstation-based environment 

is the objective of Runtime 3R1B, scheduled to be released next year. Thus developing 

Enterprise Application systems in the host environment, will not be enhanced beyond this 

release. 

78616414–000 1–3


You will need to refer to the separate Software Release Announcement for Developer/ 

Builder 3.1A for the full range of new Enterprise Application Environment features for 

developing and generating all runtime systems, and contact your local Unisys consultant 

to assist you with any migration concerns you may have after reading “Migration 

Requirements” on page 3–1. 

The OS 2200 based 3R1A Enterprise Application Environment 

The components of Enterprise Application Environment 3R1A that support the OS 2200 

based environment include: 

• Developer 3.1A (workstation development) 

• Host Builder 3R1A for ClearPath OS 2200 (host development and generation) 

• Runtime 3R1A for ClearPath OS 2200 (host run time) 

• Report Output Control System (ROC comes with Runtime 3R1A) 

• Runtime Test Environment 4R1 for ClearPath OS 2200 (host test run time) 

The tight integration of these components means that: 

• Host Builder 3R1A for ClearPath OS 2200 is required to be installed with Runtime 

3R1A for ClearPath OS 2200. 

• You cannot use Builder 3R1A for ClearPath OS 2200 to generate an Enterprise 

Application system for any earlier versions of LINC Deployment. 

• While Developer 3.1A and Runtime Test Environment4R1 are optional modules to 

include in your Enterprise Application Environment, only these versions can be 

installed if you wish to run them with Runtime 3R1A for ClearPath OS 2200. 

Runtime 3R1A for ClearPath OS 2200 

Runtime 3R1A for ClearPath OS 2200 consists of a set of utility programs, common 

banks, and RDMS tables providing runtime facilities on OS 2200 based machines that 

enable you to use the following software: 

• Host Builder 3.1A 

• Report Output Control System (ROC) 

• Graphical Interface Workbench 3R2 

• User-generated Enterprise Application Systems 

These programs and routines are not separately installable. Runtime 3R1A must be 

installed before Builder. It can then be used to support Enterprise Application Systems 

generated from Builder on the same or different OS 2200 based machines. Runtime 

3R1A is SOLAR-installable. 

For details on the major features of this release, see “Release Functionality” on 

page 4–1. 

1–4 78616414–000

Report Output Control System (ROC) 


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

with Runtime 3R1A for ClearPath OS 2200, that provides the capability to: 

• Store Enterprise Application Report output. 

• Save Report output for extended periods of time. 

• Direct Report output to terminals or printers. 

• Browse Report output at a terminal. 

• Delete Report output. 

• Direct output to disk as a standard Extract file, or in a flat file format. 

Graphical Interface Workbench 3R2 

Graphical Interface Workbench 3R2 provides the capability to: 

• Build true client applications for your host systems 

• Enhance or create client solutions for Enterprise Application Environment Systems 

• Keep forms and client applications current 

• Gain World Wide Web support through Enterprise Application Web Enabler 

• Integrate with third-party client-builders, PowerBuilder and Visual Basic. 

Host Builder 3R1A for ClearPath OS 2200 

Host Builder 3R1A for ClearPath OS 2200 provides the capability to: 

• Create and maintain Enterprise Application Environment specifications 

• Load and unload existing Enterprise Application Environment specifications to and 

from: 

– Builder on ClearPath HMP Servers, MCP based, OS 2200 based, and UNIX hosts, 

by using LCOPY 

– Developer, by using the CASE Extract/CASE Load facility 

• Generate and install Enterprise Application Systems and Reports 

• Analyze, list, and inquire on Enterprise Application Environment specifications 

• Interface with the Report Output Control System (ROC) 

Host Builder 3R1A for ClearPath OS 2200 requires that Runtime 3R1A for ClearPath OS 

2200 be installed first. 

When generating a system for ClearPath OS 2200, you deploy the system on a RDMS 

database. 

For details on ordering Host Builder 3R1A, you will need to refer to the separate Software 

Release Announcement for Developer/Builder 3.1A. 

78616414–000 1–5


Developer 3.1A 

Ordered separately from Runtime 3R1A for ClearPath OS 2200, Developer 3.1A is a 

generic PC-based Windows development environment providing the capability to: 

• Define, design, develop, and test a new Enterprise Application System. 

• Import and re-engineer or enhance an existing Enterprise Application System 

downloaded from a Runtime host (OS 2200, MCP, ClearPath HMP Servers or UNIX). 

• Export an Enterprise Application System for uploading to another Runtime host for 

generation and deployment. 

For details on ordering Developer, you will need to refer to the separate Software Release 

Announcement for Developer/Builder 3.1A. 

Runtime Test Environment 4R1 for ClearPath OS 2200 

Runtime Test Environment 4R1 runs on Unisys’ platform, ClearPath OS 2200. It runs 

against Runtime 3R1A for ClearPath OS 2200 and Host Builder 3R1A for ClearPath OS 

2200. 

The Runtime Test Environment enables developers to test new and changed Ispecs and 

Reports without requiring generates. This is because Runtime Test Environment gathers 

information directly from the Specification held in Enterprise Application Builder. It then 

runs the System according to this information. 

For details on ordering Runtime Test Environment 4R1, you will need to refer to the 

separate Software Release Announcement for this product. 

1–6 78616414–000

Section 2 

Product Interdependencies 

This section covers hardware and software requirements for Enterprise Application 

Runtime 3R1A for ClearPath OS 2200. 

All components of the OS 2200 based 3R1A Enterprise Application Environment require 

system software at the minimum release level of HMP IX 5.0. 

Hardware Requirements 

The OS 2200 3R1A Enterprise Application products require an OS 2200 system, using the 

Extended Mode capabilities of these machines. Hardware required in an OS 2200 based 

3R1A Enterprise Application System includes: 

• Host – either: 

– 2200 M Series operating systems 

– ClearPath IX operating systems 

• Terminals – any of the following terminal types: 

– UTS 20, UTS 20L, UTS 20R, UTS 30, UTS 40, UTS 60, UTS 60I 

– SVT 1120, SVT 1121, LT300, DS7 

– IBM 3270 group of terminals or SNA 3270 group of terminals 

– PCs with UTS terminal emulation software 

• Disk Space: 

– Minimum of 65,000 tracks for Runtime with ROC, if used 

– Approximately 75,000 tracks for Host Builder software, (100,000 during builds) 

• Peripherals: 

– Tape Drive 

– Line Printer 

The recommended minimum system memory is 6 million words for Runtime 3R1A 

including TIP memory, and 9 million words if Host Builder 3R1A is also to be be installed. 

Note: Size estimates are exclusive of other existing software. For details, refer to the 

Unisys e-@ction Enterprise Application Runtime for ClearPath OS 2200 Installation and 

Configuration Guide. 

78616414–000 2–1


Software Requirements 

Enterprise Application Software 

As already stated, due to the tight inter-relationships between the components of the 

Enterprise Application Environment, the following software is required to be installed 

concurrently with Runtime 3R1A for ClearPath OS 2200: 

• Host Builder 3R1A for ClearPath OS 2200 

• Developer 3.1A 

Mandatory Software 

Mandatory software for running Runtime 3R1A for ClearPath OS 2200 includes: 

• Operating System Host Software – one of the following: 

– HMP IX 5.0 (qualified) 

– HMP IX 5.1 (supported) 

– HMP IX 6.0 (supported*) 

• Compilers: 

– UCS COBOL (UCOB) 9R1 

– UCS C (UC) 7R1 

– ASCII COBOL (ACOB) 7R3A 

• Database – RDMS 2200 9R3 

• Comms Protocol – CMS 1100 8R4A 

* TPM may not be fully supported in Runtime 3R1A, but will be fully supported in 3R1B. 

Standard HMP IX System Software 

The following software comes as part of the standard HMP IX package: 

• COMUS – for making changes to the default configuration. 

• IPFSQL – for using a NOF interface. 

• DDP-PPC – for using HUB. DDP-PPC in connection with external and interhost 

Automatic Entries, which use the HUB mechanism. 

• PADS – for using Programmer’s Advanced Debugging System to use C++ Compiler 

applications (recommended) 

• OLTP-TM2200 – for using Online Transaction Processing. 

• OSI-TP– for using OLTP multi-host capability. 

2–2 78616414–000

Optional System Software 


The following items can be installed as supplementary software with Runtime 3R1A for 

ClearPath OS 2200: 

• XRLOAD (Relational Database Fast Load) 

• e-@ction Business Information Server – if you are using a Business Information 

Server interface to process Enterprise. (You need MRI for mapper access to OS 2200 

Runtime Databases). You will also need MRI and/or IPFSQL (see below). 

• MRI – for Mapper (or Business Information Server) access to OS 2200 Runtime 

Databases. 

• Open/OLTP (an optional part of the Runtime 3R1A installation) 

• Remote Access Server (an optional part of the Runtime 3R1A installation) 

• DEPCON Host Agent for 2200 5R1 or higher 

• Component Enabler 3R1 – for Remote Access Server connectivity. 

• Graphical Interface Workbench 3R2 – for testing and viewing the application. 

• Web Enabler 3.1 – to view your applications on the internet 

• Runtime Test Environment 4R1 for ClearPath OS 2200 – for testing Ispecs and 

Reports without generates. 

The last five items comprise the full complement of Unisys e-@ction Enterprise 

Application Environment software to be installed with Runtime 3R1A. 

For details of these optional software requirements, refer to the Unisys e-@ction 

Enterprise Application Runtime for ClearPath OS 2200 Installation and Configuration 

Guide. 

Network Software 

Further to networking requirements: 

• If you require inter-host system services (for example, file transfers), you must install 

Distributed System Services (DSS). 

• If you require Developer Test to call subroutines on the host, in addition to DSS, you 

need the Remote Subroutine Server (also known as LRSS), which is automatically 

installed as part of the standard runtime installation. 

• OLTP is one software option, if you want interhost communications. 

Requirements for Host Builder 3R1A for ClearPath OS 2200 

To install multiple copies of Host Builder 3R1A for ClearPath OS 2200 under your 

Runtime, you require: 

• Release tape 

• A unique System name for each copy of Host Builder 3R1A for ClearPath OS 2200 

• A unique Database name for each copy of Host Builder 3R1A for ClearPath OS 2200 

• A HVTIP Library Number and a TIP Transaction Number 

There are various configuration options to consider when loading Host Builder 3R1A for 

ClearPath OS 2200, which include target host templates, reserved word lists, automatic 

edit resequencing, and change and resource locking. For more details, see the Installation 

and Configuration Guide. 

78616414–000 2–3


2–4 78616414–000

Section 3 

Migration Requirements 

This section gives an overview of the migration process from OS 2200 based LINC 

Deployment 16R3, also known as LINC II, to Runtime 3R1A for ClearPath OS 2200. 

Pre-Migration Tasks 

Before you begin any migration task, you should ensure you do the following: 

1. Install all the necessary software, which includes: 

• Runtime 3R1A for ClearPath OS 2200 

• RDMS 2200 9R3 software on your OS 2200-based server, as required. 

• The latest Interim Correction of Developer 3.1A (see the Unisys support web site 

at http://www.support.unisys.com for the latest IC information) 

2. Back up both your application and its data. 

3. Consider all migration issues. See below. 

Migration Issues 

When migrating to Runtime 3R1A for ClearPath OS 2200, you need to consider the 

following: 

Reserved Words 

If you are installing the new release of Host Builder 3R1A for ClearPath OS 2200, and plan 

to migrate existing LINC Specifications, some of your existing item names could conflict 

with new reserved words. It is important that you run the new Reserved Words utility 

(see “Runtime Development Enhancements” on page 4–4) and check the list of potential 

reserved word conflicts in the SLD report from the installation process. 

Prior to performing any generates, address any reserved word conflicts by changing item 

names through the Dictionary Maintenance facility within Host Builder 3R1A. If conflicts 

are not addressed, you may receive errors during later generates. 

Use of KEYONLY; Commands 

KEYONLY; commands in LINC Deployment 16R3 were ignored, but migrating to Runtime 

3R1A may alter the processing of any Ispecs containing these commands. 

78616414–000 3–1

Migration Requirements 

Preserve Session Data 

The option to “Preserve Session Data” is no longer ignored when migrating data to 

Runtime 31RA, as this option controls the S_T_N Records in Memory feature. 

Consequently LINC 16R3 session data may be lost in migration. See “Runtime 

Development Enhancements” on page 4–5. 

Reference Material 

Refer to the following documentation for more detailed information: 

• Unisys e-@ction Enterprise Application Runtime for ClearPath OS 2200 Installation 

and Configuration Guide for complete procedures on migrating your OS 2200 based 

LINC 16R3 applications and application data.The various migration issues are outlined 

in “Addressing Migration Issues”in this guide. 

• Unisys e-@ction Enterprise Application Developer Installation and Configuration Guide 

for information on extracting your 3R1A Application Model. 

• Unisys e-@ction Enterprise Application Developer 3.1A Administration Guide, for 

information on loading your Enterprise Application Model. 

• RDMS documentation for detailed information about the RDMS utilities. 

Migrating from 2200-based LINC Deployment 16R3 

Having completed all pre-migration tasks, migrating your application and data from the 

16R3 environment to the new 3R1A environment, involves the following steps: 

1. Extract and Load 

To extract your Specifications from release 16R3 and load them into release 3R1A, 

use either: 

• LCOPY 

or 

• CASE LOAD, but this will take longer than LCOPY. 

2. Syntax-only and System Generate 

After copying your Specification to release 3R1A, it is recommended that you: 

• Perform a syntax-only generate of your System, with “Stop on first error” set to 

N, before you generate the new System. 

• When the database environment has been set up, use Host Builder 3R1A for 

ClearPath OS 2200 to generate and deploy your Systems to the Runtime 3R1A 

for ClearPath OS 2200 host. 

If you wish to migrate LINC 16R2, you will first have to migrate to LINC 16R3 first. 

3–2 78616414–000

Section 4 

Release Functionality 

As already stated in the General Description, the main objective of the new Unisys e- 

@ction Enterprise Application Environment products is to provide improved support for 

transferring from host-based development to workstation-based Enterprise Application 

Development. 

Runtime 3R1A for ClearPath OS 2200 provides the following reasons for migrating to an 

Enterprise Application Environment: 

• Reduced application downtime 

• Shorter incremental generate 

• Improved scalability 

• Tighter integration with system software 

• Improved Runtime transfer 

New Features in Runtime 3R1A for ClearPath OS 2200 

The individual new features that contribute towards the improvements stated above, are 

introduced under the following headings: 

• Runtime development enhancements 

– Runtime Test Environment 4R1 for ClearPath OS 2200 

– UCS Runtime Subsystem 

– Generic extract format for System data interchange 

– Remote Subroutine Server (LRSS) 

– Local (language) message system 

– Definition of Global Setup Data Blocks 

– Standardized SERIAL; command behavior 

– COMPUTE; command supports the LDL ROUNDED clause 

– Reserved words utility 

– Population and Pack Information 

– Improved performance for storing terminal-related information 

– Use of the @CHG,N command to make pack changes 

– Support for the EURO currency symbol 

78616414–000 4–1


• Database performance enhancements 

– Direct specification of RDMS database options and attributes 

– Multi-thread installation/reorganization 

– Support for the RDMS XRLOAD (Relational Database Fast Load) Utility 

– Support for the KEYONLY; command 

• Integration of Component Enabler, with: 

– Remote Access Server recognition 

– Active Server Page Generator 

– SetNOF Interface 

– Change Report 

– Automation of installation Setup Tasks 

– Class Reference summary lists 

– Integration with Developer Test 

• Developer Security enhancements 

– Change Identifier can be empty during Logon 

– Password modification on expiry 

• Reporting enchancements 

– ROC performance 

– Automatic Report Batch Generate after a system generate 

– Stage reports during generates 

• Printing enhancements through DEPCON Support 

• De-implementation of DOC 

Each of these features for Runtime 3R1A for ClearPath OS 2200 is outlined in the 

following subsections. A summary of these changes is listed in the InfoPack 3.1 on 

http://www.support.unisys.com. 

For details of the effects of changes when you are migrating from an earlier LINC release, 

see your Unisys e-@ction Enterprise Application Runtime for ClearPath OS 2200 

Installation and Configuration Guide, as well as summary details in “Migration 

Requirements” on page 3–1. 

4–2 78616414–000

Runtime Development Enhancements 

Runtime for ClearPath OS 2200 has its own Test Environment 


Runtime 3R1A for ClearPath OS 2200 is supported by its own Test Environment. Runtime 

Test Environment 4R1 for ClearPath OS 2200 enables developers to test new and 

changed Ispecs and Reports without requiring generates. This is because Runtime Test 

Environment 4R1 gathers information directly from the Specification held in Host Builder 

3R1A for ClearPath OS 2200 and then runs the System according to that information. For 

full details, please refer to the Unisys e-@ction Enterprise Application Runtime Test 

Environment 4R1 for ClearPath OS 2200 Software Release Announcement. 

UCS Runtime Subsystem 

To remove runtime restrictions, the basic mode infrastructure has been replaced by an 

UCS subsystem infrastructure. The runtime UCS support routines are packaged as a fastload 

self-contained shared subsystem, so allowing a single copy of the support routines 

to be shared by all Runtime programs. This subsystem creates smaller UCS object 

modules, including more address space available for HVTIP. 

Generic Extract Format for all System Programs 

A new generic data interchange format creates and reads extract files across all platform 

versions of the Enterprise Application Environment. Provided as an option to existing 

user-defined and internal extract file formats, the use of this command is as simple as 

specifying which Ispec to extract and the type of format indicator. 

This new common extract format can be used by macro report utilities such as 

DXREPGEN which automatically create Enterprise Application unload/load reports for 

host Runtime and Developer Test. These reports can then be generated to allow data to 

be moved and exchanged from one architecture to any other easily. A new extract option 

means there is no impact to existing report LDL code. 

LRSS Runtime Host Subroutine Server 

The Enterprise Application Environment Remote Subroutine Server (LRSS) installed on 

the Runtime host enables remote subroutines on the host to be called, so making more 

accurate System testing possible. Developers can now call subroutines that the System 

is designed to use on the host platform or from a DLL on the Developer machine. 

Each LDL “Call” directive sends “Call” Requests across the network to the Remote Host 

on the connection. The Developer Test CALL; extension establishes a remote session, 

using information in an .INI file, and sends requests to, and receives replies from, the 

proxy server. The proxy server carries out actions on the remote machine and can, if 

required, return a result. The caller server protocol includes “Connect”, “Make call to 

routine” and “Disconnect” actions. 

78616414–000 4–3


Local (Language) Message System 

All translatable messages displayed by Enterprise Application programs use the standard 

OS 2200-based software to translate runtime console messages from ELMS message 

files instead of the LLANGUAGE file. ELMS was chosen as the new message delivery 

system because it is standard, supported Unisys OS 2200 software, is easy to tailor and 

maintain, and supports Kanji and other character sets. 

GSDs defined in named Global Setup Data Blocks 

Global Setup Data Items (GSDs) can now be defined in multiple GSD Blocks and then 

defined in named code blocks, similar to the naming of Global Logics, Ispecs, and 

Reports. Once a block is defined, GSDs can be added, and made available for reference in 

Logic. Both GSD Blocks and individual GSDs are supported as versionable objects. 

GSD Blocks allow a way of partitioning GSDs, both logically within the specification, and 

physically within the generated source files. When you recompile, grouping GSDs means 

saving time as it is only necessary to recompile and link, for example, Ispecs that are 

referenced by the changed GSD blocks rather than all Ispecs. 

When migrating to this release, existing GSDs are moved into one of two default GSD 

Blocks: GLB-WORK-BLOCK, for global work GSDs; and GLB-SDS, for all others. 

Standardized SERIAL; Command Behavior 

Runtime for OS 2200-based Systems will no longer fail if a DETERMINE; SERIAL or 

LOOK.UP; SERIAL command is first performed when GLB.COPY is greater than one. This 

change makes the behavior of the SERIAL; command option for OS 2200-based Systems 

consistent with that of the MCP and UNIX based Systems. 

Note, however, that failing to execute a DETERMINE; SERIAL or LOOK.UP; SERIAL 

command with GLB.COPY set to one in the first cycle of logic will cause unpredictable 

results on all platforms. 

Support for the LDL ‘ROUNDED’ Clause 

Syntax for the COMPUTE and the COMPUTE.FROM commands has been extended to 

make use of the LDL ‘ROUNDED’ option, which forces rounding of the final result. Thus 0 

– 4 inclusive are rounded down, while 5 – 9 inclusive are rounded up. This brings it into 

line with the ADD;, DIVIDE;, MULTIPLY;, and SUBTRACT; options. 

Reserved Words Utility 

This feature enables users to create a list of the reserved words on the OS 2200-based 

Runtime host rather than referring to the list in the Enterprise Application Environment 

documentation. Users can generate the list for any or all of the available platforms. The 

list of reserved words produced by this feature maintains a more accurate and up-to-date 

list of reserved words than the previous hardcopy listing in the documentation. 

4–4 78616414–000

Population and Pack Information 


OS 2200 system users define populations, packs, and tip numbers for internal data 

structures and Graphical Interface Workbench on a new Internal Populations screen 

instead of on the Pack screen. The population and pack options are stored by the 

Generate Set. 

Storing Terminal-related Information 

The transaction performance for storing terminal related information has improved by 

holding station data in memory within a data Common Bank, thereby reducing the I/O 

required and the associated path length for a transaction. It also reduces the code size of 

Ispecs and allows more user code to fit within the HVTIP 262KW bank limit. 

In existing systems the methods for storing terminal related information required I/O to 

the structure itself and to the system audit trail, as S_T_N and FCSS are recoverable and 

audited. By storing the station related information in memory during normal processing 

this I/O overhead can be significantly reduced. 

Additionally by reading and locking S_T_N records in an FCSS tip file, (through the option 

to “Preserve Session Data”), the existing FCSS storage technique has been improved for 

cases where recovery and auditing of station data is required, further improving 

performance of a system. 

Use of the @CHG,N Command to make Pack Changes 

The use of the @CHG,N command, a feature of FURPUR, allows a file to be renamed 

without requiring it to be copied. By eliminating the need for copying via intermediate files 

considerable time and resources are saved, and no user intervention is required. Using 

the @CHG,N command means faster Object Pack Changes and improved reorganization 

performance of database packs. 

Support for the EURO Currency Symbol 

Runtime 3R1A supports the EURO currency symbol, . 

78616414–000 4–5


Database Performance Enhancements 

Direct Specification of RDMS Storage Attributes 

You can directly specify RDMS storage attributes controlling the allocation of space for 

structures in runtime systems through Developer 3.1A, which has new Advanced RDMS 

Options pages added to the Ispec and Profile Options dialog box. Frequently tuned 

storage parameters can be altered for Ispecs, Conditional Profiles, Profiles, Named 

Partitions, Ispec AutoIndexes and Conditional Profile AutoIndexes. Additionally, packs and 

populations can be entered for AutoIndexes. 

Users now have the option of directly specifying the maximum number of pages to be 

used for a storage area, as well as the page size for that storage area. Previously, this 

number was automatically calculated based on population and page size. 

Multi-thread Installation/Reorganization 

The install phase of a system generate can now be split into multiple streams, where you 

can nominate the number of parallel batch jobs for its database reorganization phase. The 

Multireorg feature enables OS2200 RDMS database reorganizations to run in multithread 

mode, i.e. more than one split run can be started up for the database reorganization 

phase. Through an option set in host Builder to use this feature, you can now specify a 

number of parallel reorganization activities within a generate, in the same way that the 

compile and link phases can be multi threaded. You may also spread the work among the 

split runs. 

Previously, if a number of structures in an OS2200 RDMS database were affected by a 

generate, the previous logic would single-thread the reorganization process. This process 

was time intensive if the structures involved a lot of data, increasing system down time. 

Thus, this feature reduces the database reorganization time for long runs and so reduces 

system down time. 

Support for RDMS XRLOAD Utility (Relational Database Fast Load) 

XRLOAD (Relational Database Fast Load) has been developed as an offline utility for 

speedy loading of data. It allows RDMS database reorganization performance to be an 

order of magnitude faster than the alternative of using RDMSMUTL, especially when very 

large tables and Fastload reports are involved. 

While XRLOAD does not use RDMS, UDS or Integrated Recovery, and Fastload Reports 

do not support multi-table Ispecs, XRLOAD does construct database pages directly in the 

proper UDS and RDMS format. 

Support for KEYONLY; Commands 

Using KEYONLY; commands avoids accessing a whole table when only the profile 

ordinates are required. Doing so reduces I/O and therefore increases performance. 

4–6 78616414–000

Component Enabler Enhancements 


The following enhancements to Component Enabler are available with the release of 

Graphical Interface Workbench 3R2. 

Remote Access Server Recognition 

GLB.STYLE and GLB.GUI are sensitive to Component Enabler clients. This feature 

provides anonymous user login; multiple users can login with the same user ID, so that 

Component Enabler is recognized by the Remote Access Server. 

Active Server Page Generator 

The ASP Generator for Component Enabler generates Active Server Pages that can be 

run on a server, using the graphical forms defined in Enterprise Application Developer or 

Graphical Interface Developer. The ASP Generator produces the painted screens in 

HTML4 and DHTML, and is an optional, separately-priced product for Component Enabler. 

SetNOF Interface 

Limited support is now available to allow direct access to the NOF buffers in Component 

Enabler. This functionality is provided to assist existing LINC customers to migrate their 

applications to Component Enabler. It is expected these customers will, as soon as is 

practical, move to using the field-based data access. 

Automation of Installation Setup Tasks 

The installation program has enhancements to further automate the setup tasks. 

Automated functions include: locating the Microsoft Java SDK or Microsoft Visual C++ 

binaries, updating ALGAE.INI with compiler settings, updating the CLASSPATH settings 

for the Component Enabler Java Archive files, and providing a confirmation dialog to 

check selected options before completing installation. 

Change Report 

The Component Enabler Generator produces a Change Report outlining all changes since 

the previous generate that can affect the client front-end of a system. Changes reported 

include: new Ispec, deleted Ispec, new field on Ispec, deleted field on Ispec, changed 

length of field, changed edit of a field, and other changed attributes of a field. 

Class Reference Summary 

In Acrobat PDF format, the Class Reference summary lists common functions called 

when logging onto a system or when retrieving data using Component Enabler. The 

summary lists functions, describes instructions for completing them, common response 

codes they evoke, and includes information on how to Register Component Enabler as a 

COM object. Functions included are: Connecting/Disconnecting, Transactions, Listboxes 

and Console. 

Integration with Developer Test 

Developer can now generate Component Enabler Bundles and Environment Options for 

testing in Developer Test. 

78616414–000 4–7


Developer Security Enhancements 

At Logon, Change Identifier can be empty 

For sites using virtual station addresses that are user-defined, the Change Identifier and 

Patch Number on the logon screen, that used to be automatically filled by previously used 

fields, can now be deliberately left empty when logging in. 

Password Modification on Expiry 

A System option that can be dynamically enabled/disabled for network connections to the 

Remote Access Server, this feature determines whether the system should force users 

to change their password when it expires. 

Reporting Enhancements 

Automatic Report Batch Generate after System Generate 

You can initiate a Report Batch Generate automatically when a System Generate has 

completed. Unattended generates are now more streamlined as the user does not need 

to wait until the end of a System Generate in order to initiate the Report Batch Generate. 

For large Systems this is a considerable improvement as you can make all the generate 

option selections up front, and generate both the System and Reports in the one process. 

ROC Performance Improvement 

Performance and functionality of the ROC (Report Output Control) system on OS 2200 

platforms has been enhanced. The new implementation reduces competing for access to 

the ROC database. Other enchancements include: 

• Unique record keys for Reports are kept in memory. 

• Report output is automatically deleted from the ROC database after printing. 

• A new HEADR profile shows the expiration date of the Report. 

Stage Reports during Generates 

The system no longer has to be generated and installed before Reports can be generated. 

This release allows a Generate without Install” for Reports, and means that Reports that 

access a changing database structure can be generated and run successfully. It means 

developers now have the option to generate reports without copying report executables 

into the production files, and to stage the installation of generated reports so that they 

can generate their system and reports without impacting their online system. 

4–8 78616414–000

Printing Enhancements 


Definition of DEPCON Electronic Forms through a DEPCON Wizard 

Support of DEPCON with its electronic forms enhances the printing capabilities of 

System Reports. Developers are able to define these electronic forms as a Windows 

metafile, and then use the DEPCON DFFU utility to define the data fields for the Report. 

The Developer then imports the form into Developer, to generate the basic Report, using 

the new DEPCON wizard. These new DEPCON Reports are defined as “DP” Reports and 

are treated similarly to direct “DI” Reports. 

After the “DP” Report has been created the user needs to manually complete the Report 

logic in the usual manner to enhance the logic generated by the DEPCON wizard. There is 

no further restriction on what the developer decides to include in the logic. 

Printing Enhancements 

DEPCON Reports can be created and started from all host platforms, including the 

ClearPath OS 2200-based platform. Printing enhancements for all platforms include: 

• Top and bottom margin for every Report 

• Lines per inch setting for every Report 

• Characters per inch setting for each Report, Frame, and Data Item 

• Point size of characters can be set for each Report, Frame, and Data Item 

• Detailed edit attributes such as supported by the COBOL picture statement 

• Multiple fonts and styles 

• Scalable character sizes 

• Landscape or portrait orientation 

• Inclusion of graphics (logos, etc.) 

The ROC system has been upgraded to support new printer connect mechanisms and 

allow for user selection of defaults. 

Removal of DOC 

DOC functionality has been removed from Runtime 3R1A for ClearPath OS 2200, which 

means the Runtime objects/executables will take less time to install, and the time to build 

executables will be reduced. 

78616414–000 4–9


4–10 78616414–000

Section 5 

Restrictions and Known Limitations 

Restrictions on the use of Runtime 3R1A for ClearPath OS 2200 are listed in this section. 

System Restrictions 

Only Enterprise Application Systems generated using Host Builder 3R1A for ClearPath OS 

2200 can be deployed on Runtime 3R1A for ClearPath OS 2200. A user using Developer 

3.1A and Host Builder 3R1A for ClearPath OS 2200 cannot generate until Runtime 3R1A 

for ClearPath OS 2200 is also installed. Therefore: 

• Runtime 3R1A for ClearPath OS 2200 requires Host Builder 3R1A for ClearPath OS 

2200. 

• Host Builder 3R1A for ClearPath OS 2200 cannot support LINC 16R2 or 16R3 

Environments. The LINC Environments can, however, coexist on the same ClearPath 

OS 2200 server, but Developer 3.1A cannot generate and deploy to the old LINC 

16R2 or 16R3 Environments. 

New Feature Restrictions 

Restrictions on XRLOAD (Relational Database Fast Load) 4R2 Support 

• XRLOAD 4R2 cannot be used for reloading data into a LINC Ispec when it is split into 

two or more tables (multi-table). It is an XRLOAD requirement that in such a case, 

RDMUTL would continue to be used. Before using XRLOAD 4R2, it is recommended 

that you read the XRLOAD User Guide. 

• XRLOAD 4R2 requires the use of between 9 and 102 extra pages in the storage-area. 

The extra number depends on page size. These extra pages are added to the page 

number calculation done in host Builder generations. To use XRLOAD 4R2 

successfully, you may have to increase the population to force the creation of extra 

pages. 

As XRLOAD (Relational Database Fast Load) is an optional product, it is recommended, 

that you use XRLOAD 4R3 (or higher), which has no requirement for addition al pages. 

Restriction on the MULTREORG Feature 

When many small tables are being reorganized, there may be problems with using the 

multi-thread reorg feature. 

78616414–000 5–1


Restriction on S_T_N Records in Memory 

The feature is only active for the most common use of the S_T_N structure, namely the 

storing of the record associated with GLB.WORK. It is not used for the storage of error 

screens, Ispec data or PCE switch information as each of these cases should be low 

frequency occurrence. To reserve memory for each of these S_T_N structures would use 

a lot more memory and would be inconsistent with the current implementation, which 

uses RDMS S_T_N/FCSS for these structures. 

KEYONLY; Restrictions 

The following points should be noted about use of the KEYONLY; command: 

• The KEYONLY; command option must be included on the same line as the 

DETERMINE; or LOOK.UP; command. 

• LOOK.UP; retrievals can use the KEYONLY; command option only on Standard 

Components. 

• KEYONLY; is ignored for: 

– Integrity systems 

– Ispecs that require multiple RDMS tables 

(FLAG commands to an Ispec (or EVENT) which are successfully read with 

KEYONLY; will update the record retrieved with the KEYONLY.) 

• If you reference a non-key data item it will contain high-values. The contents of nonkey 

numeric data items may vary depending on the machine type. Therefore, access 

to non-key data items, while syntactically valid, may produce unwanted and 

unpredictable results. 

• Runtime Test Environment 4R1 for ClearPath OS 2200 does not support KEYONLY; 

on the 2200 platform. 

LRSS Restrictions 

A couple of points to note about use of the Remote Subroutine Server: 

• Each LRSS Server can have up to a maximum of 10 concurrent activities servicing a 

connection. 

• The target subroutines cannot be in HVTIP libraries nor can they be Basic Mode 

Routines. 

• Dynamic Linking from a Bound Object Module places certain constraints on the 

LRSS: 

– Once the LRSS has associated itself with a particular file, subsequent calls 

always search that file. 

– The inability to unload Object Modules after a connection had been terminated 

and, as a consequence, the LRSS server has to terminate after each connection 

and be restarted. If this is not done, the size of each LRSS activity continues to 

grow until the Exec detects a bounding violation. 

5–2 78616414–000

Stage Reports Restrictions 

A couple of points to note about Staging Reports: 


• After a system install, GEN$STATUS should be checked for any problems in copying 

individual staged reports. 

• After staging a report, the unsupported LRU function, REBUILDREP, will compile the 

new version of the report. 

Decommitment of TPE Environments 

The OS 2200 Based LINC Software Release Announcement for Release 16R3, 

announced LINC 16R3 was be the last release to support TPE generated LINC Systems 

due to restrictions imposed by the TPE environment. Thus Runtime 3R1A for ClearPath 

OS 2200 now requires all Specifications to be generated using the UCS Software 

environment only. This may increase memory and disk requirements for existing TPE 

user-generated systems. 

78616414–000 5–3


5–4 78616414–000

Section 6 

Support 

Classified as new Category 1 software, Runtime 3R1A for ClearPath OS 2200 will be fully 

supported by the Unisys Customer Support Centers until mid 2004. 

This software supersedes prior releases of OS 2200 based LINC, also known as LINC II. 

Support issues related to this product can be logged in the normal manner against its 

Product-Level, LINC-3R1AIX. The Product-Level value for all Enterprise Application 

products is 3R1AXX, where XX is the platform. 

Support Online 

If you have any questions or problems with a Unisys product, your first source of 

information is Support Online, an online technical resource available to all Unisys clients 

with a service agreement. Support Online provides an interface with experts at the 

Unisys Client Support centers. This information is available through the World Wide Web. 

Your maintenance contract entitles you to access Support Online at the following address: 

http://www.service.unisys.com. 

Support Requests can be entered and tracked via Support Online, and are used to: 

1. Send a Technical Assistance Request. 

2. Report a defect on a Unisys product. 

3. Submit a New Feature Suggestion on a Unisys product. 

This technical resource is available 24 hours a day, 7 days a week. It offers a wealth of 

information about Unisys hardware and software systems. Take some time to explore 

Support Online and discover the services available to you. 

Product Support 

The product support web site is at: http://www.support.unisys.com. 

Comments, inquiries, and trouble reports should be submitted to the engineering plant on 

the User Communications Form (UCF) (#3027057). These should be directed to your local 

Unisys Support center. 

USA and Canadian customers may contact the Customer Support Center on this toll free 

number: 800 328 0440 followed by prompt 4. All non-USA UCFs should be sent to your 

local Unisys Support center. 

78616414–000 6–1

Support 

UCFs should be submitted as per the UCF Submission Requirements which are 

documented in the "LINC" PVP. UCFs and their attachments can be submitted by e-mail or 

ftp server as follows: 

1. By e-mail to acus.support@unisys.com. 

Materials can be mailed to this address putting the UCF/Contact ID in the subject 

field. 

2. By FTP Server within Unisys to ftp.acus.unisys.com (192.146.252.110). 

Using Login name “acussupport” and Password "supportacus”, materials can be sent 

from within Unisys by efts, and placed in the “incoming”directory, within another 

directory or zip-file whose filename incorporates the UCF or Contact ID. 

Tech Advantage 

Tech Advantage is a suite of technical services offered by Unisys Client Support Centers. 

For more information, look up the Web site, http://www.service.unisys.com, or contact 

your local Client Support Center. 

Notice of De-implementations 

Support for OS 2200-based LINC 16R3 is scheduled to terminate on March 31, 2002. 

However, for current date information it is best to consult the Enterprise Application 

Environment Release and Support Plan on the Unisys web site at: 

http://www.support.unisys.com/ind/txt/lin-releases?pla=lin. 

Support for all releases prior to OS 2200 based LINC 16R3 has ceased, and their product 

information may no longer be ordered. 

Thus, for sites still using OS 2200 based LINC 16R3, migration to Runtime 3R1A for 

ClearPath OS 2200 should be considered a high priority. 

6–2 78616414–000

Section 7 

Customer Product Information 

All Enterprise Application Environment product documentation for Release 3.1A is 

included on the following CD-ROMs: 

• Unisys e-@ction Enterprise Application Environment 3.1A Documentation CD-ROM 

• Unisys e-@ction Enterprise Application Runtime 3.1A for UNIX CD-ROM 

Your purchase of Runtime 3R1A for ClearPath OS 2200 software includes the first 

documentation CD-ROM. You use Acrobat Reader, provided on the CD-ROM, to read the 

product documentation. Instructions are in the CD-ROM insert booklet. See “Ordering 

Procedure” on page 8–1 for details on ordering the software. 

Ordering procedures for software are described in the next section. 

3.1A Documentation CD-ROM 

Dedicated to documentation only, the Unisys e-@ction Enterprise Application 

Environment 3.1A Documentation CD-ROM is delivered to all Enterprise Application 

Environment customers. It includes documentation for the entire set of Release 3.1A 

products, which include: 

• Developer 3.1A 

• Workstation Builder 3.1A for Windows 2000, Windows NT, ClearPath MCP, and UNIX 

• Host Builder 3.1A for ClearPath MCP and UNIX, and 3R1A for ClearPath OS 2200 

• Runtime 3.1A for Windows 2000, Windows NT, ClearPath MCP, and UNIX, 

and 3R1A for ClearPath OS 2200 

• Runtime Test Environment 4.1 for ClearPath MCP, and 4R1 for ClearPath OS 2200 

You can also order this CD-ROM separately on Part Number 7861 6513-001. 

78616414–000 7–1

Customer Product Information 

OS 2200 Documentation Library 

The following table lists all documentation available for Runtime 3R1A for ClearPath OS 

2200 and where to find it. 

Note: Product documentation specific to Developer and Host Builder 3R1A for ClearPath 

OS 2200 is listed in the Unisys e-@ction Enterprise Application Developer and Builder 

Release 3.1A Software Release Announcement. 

http://www.support.unisys.com 

All documentation on CD-ROM is also available on the Unisys Support Web. All Software 

Release Announcements can also be found on this site. 

http://www.bookstore.unisys.com 

Hard copies of all Software Release Announcements and the Programming Reference 

Handbook can be ordered from the Unisys Electronic Bookstore. 

On-line Help 

Document Title Part Number Media 


Runtime for ClearPath OS 2200 Installation and 

Configuration Guide 


Runtime for ClearPath OS 2200 Administration Guide 


LCOPY Guide 


Programming Reference Manual 


Host Builder Guide 


Host Builder Reference Manual: Painter and Editor 


Environment InfoPack 3.1A 


Runtime for ClearPath OS 2200 Release 3R1A Software 

Release Announcement (this document) 


Programming Reference Handbook 

7861 6323-000 CD-ROM + Web 

7861 6331-000 CD-ROM + Web 

7861 6083-001 CD-ROM + Web 

7861 6075-001 CD-ROM + Web 

7861 6190-001 CD-ROM + Web 

7861 6174-001 CD-ROM + Web 

7861 6596-001 CD-ROM + Web 

7861 6414-000 Web + Hard 

Copy 

7861 6067-001 Hard Copy only 

In addition to product information in manual format, some of Runtime 3R1A’s utilities 

have context-sensitive online help. 

7–2 78616414–000

Section 8 

Ordering Procedure 

Runtime 3R1A for ClearPath OS 2200 can be ordered through the normal Unisys channels 

using the style IDs listed in this section. 

For all sites in the United States and Canada, Unisys provides a software ordering 

procedure that is quick and easy to use. You can fax or mail new or update orders for 

Unisys e-@ction Enterprise Application Environment software. Alternatively, you can 

telephone Software Order Express (1-800-829-1313, prompt 2). 

For all sites outside of the United States, you can request new or update orders by 

contacting your local Unisys representative or authorized Unisys Value Added Reseller for 

more information, or by contacting the the Unisys Support Organization at: 

http://www.service.unisys.com 

Product Licensing Options 

The Runtime product consists of software released on tape and documentation released 

on CD-ROM. On ordering Runtime 3R1A for ClearPath OS 2200, you receive the Unisys 

e-@ction Enterprise Application Runtime 3R1A for ClearPath OS 2200 tape, which also 

contains the software for its standard attached module: Report Output Control System 

(ROC). See “Customer Product Information” on page 7–1 for information on the 

documentation available with this release. 

Runtime 3R1A for ClearPath OS 2200 is licensed on a per user basis, through these 

licensing options: 

• Minimum User license for an initial concurrent eight users (or less) 

• Additional User license for each additional, concurrent user, above the initial eight 

users 

• Unlimited User license according to the performance group of the system 

The customer is required to notify Unisys in writing if the number of users or the 

performance group is to be expanded beyond those licenses initially purchased. Then, 

user expansion is subject to Unisys conditions and charges current at the time of 

purchase. 

Licenses can be purchased with or without a Selected Software Update (SSU) 

subscription and maintenance agreement. 

78616414–000 8–1


Style Types 

Product licenses are identified by their Style IDs, as follows: 

New Styles for: 

• Completely new users of Enterprise Application Environment software. 

• Existing users wanting to increase the number of developer licenses. 

Update Styles for: 

• Existing users of pre-Release 3.1 software wanting to upgrade to Release 3.1A of 

Enterprise Application Environment software, whereby: 

– Customers with a valid Selected Software Update (SSU) license and maintenance 

agreement are entitled to receive the update style at no additional charge. 

– Customers without an SSU license for a product will be charged an update fee 

associated with each update style. 

Note: Existing users of Release 3.1 Enterprise Application Environment software with a 

valid maintenance agreement are entitled to received the upgrade to Release 3.1A 

versions at no additional cost. 

For details on how to order new or update styles in either the United States or outside the 

U.S., see the beginning of this section. 

To order Host Builder 3R1A for ClearPath OS 2200, see the Unisys e-@ction Enterprise 

Application Developer and Builder Release 3.1A Software Release Announcement. 

Style IDs for Runtime 3R1A for ClearPath OS 2200 

New Styles 

New Styles for Runtime on ClearPath OS 2200 

New IDs Description 

Enterprise Application Runtime 3R1A for ClearPath 2200, for... 

EAR999-22 ... an initial 8 users 

EAR999-X22 ... 1 additional user 

EAR5-X2C ... unlimited users on a Group 5 system 








8–2 78616414–000

New Styles for Runtime on ClearPath IX with NT 


New Styles for Runtime on ClearPath IX with UnixWare 


EAR999-IXN 

Enterprise Application Runtime 3R1A for ClearPath IX with NT, for... 

... an initial 8 users 

EAR999-XIN ... 1 additional user 

EAR5-INC ... unlimited users on a Group 5 system 















Enterprise Application Runtime 3R1A for ClearPath IX with UnixWare, for... 

EAR999-IXW ... an initial 8 users 

EAR999-XIW ... 1 additional user 

EAR5-IWC ... unlimited users on a Group 5 system 














78616414–000 8–3


Subscription Style IDs 

Subscription Styles for Runtime 3R1A 

Update Style IDs 

Update IDs Description 

Enterprise Application Environment Software Update subscription for 

Runtime 3R1A for ClearPath IX with NT, ClearPath IX with Unixware and 

2200, for ... 

EAR5-SUB ... unlimited users on all Group 5 systems 














Update Styles for Runtime on ClearPath OS 2200 


Enterprise Application Environment one-time individual license to update 

from LINC Deployment 16Rx to Runtime on ClearPath OS 2200 for ... 

EAR16231-22 ... an initial 8 users 

EAR16221-X22 ... 1 additional user 









8–4 78616414–000

Update Styles for Runtime on ClearPath IX with NT 


Update Styles for Runtime on ClearPath IX with UnixWare 


EAR16231-IXN 


from LINC Deployment 16Rx to Runtime 3R1A for ClearPath IX with NT, for 

... 

... an initial 8 users 

EAR16231-XIN ... 1 additional user 

















from LINC Deployment 16Rx to Runtime 3R1A for ClearPath IX with 

UnixWare, for ... 

EAR16231-IXW ... an initial 8 users 

EAR16231-XIW ... 1 additional user 















78616414–000 8–5


8–6 78616414–000

*78616414-000* 

78616414-000

Runtime for ClearPath OS 2200 Software Release Announcement

Create successful ePaper yourself

Delete template?

Save as template?