clearpath os 2200 - unisys...7850 5252–018 1–1 section 1 clearpath os 2200 release overview this...

unisys

ClearPath OS 2200

Software Product Catalog

ClearPath OS 2200 Release 15.0

February 2014 7850 5252–018

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 U.S. Government End Users: This is commercial computer software or hardware documentation developed

at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard

commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract

data rights clauses.

Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries.

JBoss® is a registered trademark of Red Hat, Inc. and its subsidiaries in the U.S. and other countries.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their

respective owners.

All other brands and products referenced in this document are acknowledged to be the trademarks or registered

trademarks of their respective holders.

7850 5252–018 iii

Contents

Section 1. ClearPath OS 2200 Release Overview

1.1. About This Catalog ............................................................................. 1–1 1.1.1. Purpose ....................................................................................... 1–1

1.1.2. Scope ........................................................................................... 1–1

1.1.3. Audience ..................................................................................... 1–2

1.1.4. How to Use This Catalog ........................................................ 1–2

1.2. Documentation Updates ................................................................... 1–2 1.3. ClearPath OS 2200 Release Overview .......................................... 1–3 1.3.1. Integrated Operating Environment (IOE) and the

Unisys Operating Environment (UOE) ............................ 1–3

1.3.2. ClearPath OS 2200 Documentation ..................................... 1–4

1.4. Security.................................................................................................. 1–5

Section 2. Application Development Products

2.1. ASCII COBOL Compiler .................................................................... 2–2 2.2. ASCII FORTRAN Compiler ............................................................... 2–3 2.3. C Compiler ........................................................................................... 2–4 2.4. COBOL Compiler ................................................................................ 2–6 2.5. Collector ............................................................................................... 2–8 2.6. Common Mathematical Library ...................................................... 2–9 2.7. Display Processing System........................................................... 2–10 2.8. Eclipse IDE for OS 2200.................................................................. 2–12 2.9. FORTRAN Compiler ......................................................................... 2–15 2.10. Language Support System ............................................................ 2–16 2.11. Linking System ................................................................................. 2–17 2.12. Meta Assembler .............................................................................. 2–19 2.13. PLUS .................................................................................................... 2–20 2.14. Programmers Advanced Debugging System ........................... 2–20 2.15. Runtime System for Basic Mode Compilers ............................ 2–22 2.16. Runtime System for Extended Mode Compilers .................... 2–22 2.17. Service Library .................................................................................. 2–23 2.18. Sort/Merge ........................................................................................ 2–24 2.19. System Service Routines Library ................................................ 2–25 2.20. Universal Compiling System PLUS .............................................. 2–26

Section 3. Transaction Processing Products

3.1. Open Distributed Transaction Processing ................................... 3–1 3.2. OSI-TP High Performance Distributed Transaction

Processing for XATMI.................................................................. 3–2 3.3. WebSphere® MQ Version 7 for ClearPath OS 2200 ............... 3–3

Contents

iv 7850 5252–018

3.4. ClearPath OS 2200 QProcessor ..................................................... 3–4 3.5. ClearPath OS 2200 Interface to Microsoft Message

Queuing ........................................................................................... 3–5 3.6. High-Performance Transaction Processing

Interconnect ................................................................................... 3–6

Section 4. Communications and Networking Products

4.1. Communications Application Program Interface

(COMAPI)......................................................................................... 4–2 4.2. Communications Interface for Transaction

Applications (CITA) ....................................................................... 4–3 4.3. Communications Platform (CPComm) .......................................... 4–4 4.4. Communications Platform for Open Systems

(CPCommOS) ................................................................................. 4–5 4.5. Cryptographic Library (CryptoLib) .................................................. 4–7 4.6. Distributed Data Processing File and Job Transfer

(DDP-FJT) ........................................................................................ 4–7 4.7. Distributed Data Processing Program-to-Program

Communications (DDP-PPC) ...................................................... 4–9 4.8. FTP Services for ClearPath OS 2200 ........................................... 4–10 4.9. Message Control Bank (MCB) ....................................................... 4–11 4.10. Messaging Integration Services for ClearPath

OS 2200 ......................................................................................... 4–12 4.11. System Interface for Legacy Application Systems

(SILAS) ............................................................................................ 4–14 4.12. TCP/IP Application Services (TAS) ............................................... 4–15

Section 5. Database Management Products

5.1. ClearPath Database Extensions for PHP ..................................... 5–2 5.2. Database Inquiry ................................................................................ 5–2 5.3. Define File Processor........................................................................ 5–3 5.4. Network Database Server ............................................................... 5–4 5.5. ODBC Access for ClearPath OS 2200........................................... 5–7 5.6. Processor Common Input/Output System ................................. 5–9 5.7. Relational Database Server ........................................................... 5–10 5.8. Repository for ClearPath OS 2200 .............................................. 5–13 5.9. Shared File System .......................................................................... 5–16 5.10. UniAccess for OS 2200 Systems ................................................. 5–17 5.11. Universal Database Control........................................................... 5–19

Section 6. Fourth Generation Language (4GL) Products

6.1. Business Information Server .......................................................... 6–2 6.2. Enterprise Application Environment ............................................. 6–7

Section 7. Internet Products

7.1. ClearPath ePortal ................................................................................ 7–1

Contents

7850 5252–018 v

7.2. Distributed Transaction Integration .............................................. 7–4 7.3. Web Transaction Server for ClearPath OS 2200 ....................... 7–8

Section 8. Java and Java 2 Platform, Enterprise Edition

Products

8.1. Business Information Server Resource Adapter for

the Java™ Platform ...................................................................... 8–2 8.2. Open Distributed Transaction Processing Resource

Adapter for the Java™ Platform ............................................... 8–3 8.3. OS 2200 Transaction Resource Adapter for the

Java™ Platform ............................................................................. 8–5 8.4. JBoss Enterprise Application Platform for ClearPath

OS 2200 (JBOSS-2200) ................................................................ 8–5 8.5. Virtual Machine for the Java™ Platform on ClearPath

OS 2200 JProcessor (JPJVM) .................................................... 8–6 8.6. ClearPath OS 2200 JProcessor....................................................... 8–7 8.7. Network Database Server Resource Adapter for the

Java Platform ................................................................................. 8–8 8.8. Relational JDBC Driver for ClearPath OS 2200 .......................... 8–9

Section 9. Operating Environment Products

9.1. Checkpoint/Restart ........................................................................... 9–2 9.2. CIFS for ClearPath OS 2200 ............................................................. 9–3 9.3. Executive ............................................................................................. 9–6 9.4. Executive Separately Packaged Features ................................... 9–9 9.5. Extended Transaction Capacity .................................................... 9–13 9.6. Interactive Processing Facility ...................................................... 9–15 9.7. Open Programming Environment ................................................ 9–17 9.8. Operations Sentinel Basic Edition ............................................... 9–20 9.9. Pause Disk I/O for ClearPath OS 2200 ........................................ 9–21

Section 10. Systems Management Products

10.1. Apex Administration and Reporting ........................................... 10–2 10.2. Cipher Application Programming Interface (Cipher

API) ................................................................................................. 10–3 10.3. COMUS ............................................................................................... 10–5 10.4. Enterprise Output Manager .......................................................... 10–6 10.5. File Administration System (FAS) ................................................ 10–8 10.6. Operations Sentinel ......................................................................... 10–9 10.7. Remote System Support (RSS) ................................................... 10–11 10.8. Roll-out/Roll-back Runstream (ROLRUNS) ............................... 10–12 10.9. Security Administration for ClearPath OS 2200 ...................... 10–12 10.10. SightLine Enterprise Data Manager (EDM) ............................. 10–13 10.11. SightLine Expert Advisor/ Vision (EA/V) ................................... 10–14 10.12. SightLine Interface Agents .......................................................... 10–16 10.12.1. SightLine SIP Statistics ....................................................... 10–16

10.12.2. SightLine System Log / INSP$ Statistics ....................... 10–16

Contents

vi 7850 5252–018

10.12.3. SightLine MFD Statistics .................................................... 10–16

10.12.4. SightLine TIP KONS Statistics............................................10–17

10.12.5. SightLine UDS Statistics......................................................10–17

10.12.6. SightLine TPM / HVSTATs Statistics ................................10–17

10.12.7. SightLine Step Control / MCB Statistics .........................10–17

10.12.8. SightLine MAPPER Statistics .............................................10–17

10.12.9. SightLine CMS / SILAS Statistics ..................................... 10–18

10.12.10. SightLine DPS Statistics ..................................................... 10–18

10.13. SightLine Power Agent ................................................................ 10–18 10.14. SightLine Torch ............................................................................... 10–18 10.15. SightLine Torch Capacity Manager Interface Agents........... 10–19 10.16. Software Library Administrator (SOLAR) ................................ 10–20 10.17. Software Library Administrator Extended (SOLAR/E) ........... 10–21 10.18. TeamQuest Baseline..................................................................... 10–22 10.19. TeamQuest D-Fragger and RemD-Fragger

(D-Fragger) .................................................................................. 10–22 10.20. TeamQuest Log Analyzer (LA).................................................... 10–24 10.21. TeamQuest Mass Storage Analysis and Relocation

(MSAR) ......................................................................................... 10–26 10.22. TeamQuest Mass Storage Manager (MSManager) .............. 10–27 10.23. TeamQuest Model......................................................................... 10–28 10.24. TeamQuest Online ........................................................................ 10–29 10.25. TeamQuest Online System Activity Monitor (OSAM) ......... 10–30 10.26. TeamQuest Performance Analysis Routines (PAR) .............. 10–31 10.27. TeamQuest PMLog (PMLog) ...................................................... 10–32 10.28. TeamQuest Probes (Probes) ...................................................... 10–32 10.29. TeamQuest Site Administrator Utilities (SAUtilities) ............ 10–33 10.30. TeamQuest Site Management Complex (SIMAN) ............... 10–35 10.31. TeamQuest TIP Log Analyzer (TIP-LA) .................................... 10–36 10.32. TeamQuest View (View) .............................................................. 10–37 10.33. User Authentication ...................................................................... 10–38

Section 11. Tool and Utility Products

11.1. Console Message Redisplay.......................................................... 11–2 11.2. Disk Preparation Utility .................................................................... 11–3 11.3. Dump Analysis Processor .............................................................. 11–4 11.4. Element Processor ........................................................................... 11–5 11.5. Extended Language Message System ....................................... 11–6 11.6. Fault Location by Interpretive Testing ........................................ 11–7 11.7. File Utility Routine/Program-File Utility Routine ...................... 11–11 11.8. General Syntax Analyzer ............................................................... 11–12 11.9. Internationalization Service Library ............................................ 11–14 11.10. Interconnect ..................................................................................... 11–15 11.11. List Processor .................................................................................. 11–15 11.12. Multiple Batch Run Optimizer ..................................................... 11–16 11.13. PostMortem Dump Processor .................................................... 11–17 11.14. Procedure Definition Processor .................................................. 11–18 11.15. Program-Callable FURPUR ............................................................ 11–19 11.16. Relational Database Fast Load .................................................... 11–20 11.17. Symbolic Stream Generator ......................................................... 11–21

Contents

7850 5252–018 vii

11.18. Tape Labeling Utility for ClearPath OS 2200 ............................ 11–22 11.19. TeamQuest Cross Reference Generator ................................. 11–22 11.20. TeamQuest Interactive CULL ..................................................... 11–23 11.21. Utilization Report Utility for OS 2200 ........................................ 11–24

Section 12. Integrated Recovery

12.1. Integrated Recovery Utility ............................................................ 12–1

Appendix A. Acronyms and Abbreviations

Contents

viii 7850 5252–018

7850 5252–018 1–1

Section 1

ClearPath OS 2200 Release Overview

This section gives an overview of this ClearPath OS 2200 release, the server

environment, the software, the associated documentation, and ordering information.

1.1. About This Catalog

The following subsections describe the purpose, scope, and audience of this catalog,

and how to use this catalog.

1.1.1. Purpose

Over 100 products are available for use with your ClearPath OS 2200 system. The

ClearPath Enterprise Servers ClearPath OS 2200 Systems Software Product Catalog

contains functional descriptions for each of them. The catalog is designed to help you

answer the following types of questions:

• I’ve just received a ClearPath OS 2200 system and an assortment of

documentation. What do all of these products do?

• I have a ClearPath OS 2200 system and there is a particular task I want to perform

using this system. Which software product should I use to accomplish this task?

• I’ve heard about a particular OS 2200 software product, and it sounds like it might

be relevant to my needs. What are the general capabilities of this product, and

what documents are available that describe the product in detail?

1.1.2. Scope

This catalog contains functional descriptions of all system software and networking

products that Unisys licenses for use on ClearPath OS 2200 systems. These

descriptions help you understand what each product does and present some

particular strengths of each product. Where two products serve a similar function, this

catalog helps you distinguish between them. Each product description contains the

following information:

• Product Overview: Provides a statement of capability.

• General Features: Contains a more detailed description of technical capabilities.

• Related Product Information: Provides titles of documents that may provide

additional helpful information.


1–2 7850 5252–018

This catalog does not compare different products. Each is discussed independently of

the others. Further, it does not contain hardware product descriptions or line-of

business application descriptions that are available for use on ClearPath OS 2200

systems.

1.1.3. Audience

This catalog is of interest to analysts, application programmers, data communications

specialists, data dictionary administrators, database administrators, end users,

network administrators, security administrators, system administrators, system

programmers, system operators, members of information systems management, and

anyone else who uses or evaluates ClearPath OS 2200 system software, OS 2200

software, and networking products.

If you are a new ClearPath OS 2200 system customer, are considering acquiring a

system, or just want an introduction to OS 2200 software, you will find the information

in this catalog particularly beneficial.

1.1.4. How to Use This Catalog

You can locate product descriptions in this catalog by product name or by product

category.

1.2. Documentation Updates

This document contains all the information that was available at the time of

publication. Changes identified after release of this document are included in problem

list entry (PLE) 18956187. To obtain a copy of the PLE, contact your Unisys

representative or access the current PLE from the Unisys Product Support Web site:

http://www.support.unisys.com/all/ple/18956187

Note: If you are not logged into the Product Support site, you will be asked to do

so.

http://www.support.unisys.com/all/ple/18956187


7850 5252–018 1–3

1.3. ClearPath OS 2200 Release Overview

ClearPath OS 2200 products provide a complete software platform (including

state-of-the-art features and new products) that is installable, reliable, and

maintainable.

ClearPath OS 2200 Release 15.0 is an integrated package of software delivered as a

single system instead of independent and separate release products. This release is

tested on a product level and a system level to ensure that the system and all its

products operate together as a cohesive unit. This release supports the OS 2200

system environments and is available for use by the existing and new customers. A

forward functional progression is guaranteed for each release. This means that, for

example, the functional capabilities introduced in ClearPath OS 2200 Release 14.0 are

included in the Release 15.0 and are retained for the respective migration.

The ClearPath OS 2200 Release 15.0 is the current release and supports all

Dorado 800, Dorado 700, Dorado 4000, Dorado 4100 and Dorado 4200 servers.

1.3.1. Integrated Operating Environment (IOE) and the Unisys

Operating Environment (UOE)

A subset of the products in the ClearPath OS 2200 Release 15.0 is packaged as the

Integrated Operating Environment (IOE) and the Unisys Operating Environment (UOE).

The IOE and the UOE package for a ClearPath OS 2200 server contains the basic

system software required to operate the OS 2200 server. The IOE package is available

on nonmetered systems such as the Dorado 880 or the Dorado 4280. The UOE

package is available on metered systems such as the Dorado 890 or the Dorado 4290.

Depending on your processing needs, you can choose from the different operating

environment packages for your server. Each package is designed to support a

different type of processing workload. You can choose from the following available

packages:

• General-Purpose-Workload IOE

The standard production IOE for the ClearPath systems includes the mandatory

products that are needed to run your system besides the Exec.

• OS 2200 Software Development Kit (SDK) Package

This package includes the standard IOE products, compilers, database

management, data access, transaction integration, and Web-enabling software.

• OS 2200 Business Information Server (BIS) Package

This package includes the standard IOE products and the BIS software.

• OS 2200 Enterprise Application Environment (EAE) IOE Package

Formerly called LINC, this package includes the standard IOE products, and the

additional products required for use with EAE. Although EAE software is not

included in this package, it is necessary to license it separately.


1–4 7850 5252–018

1.3.2. ClearPath OS 2200 Documentation

Your ClearPath OS 2200 server is accompanied by hardware and software

documentation that is crucial to use the system.

The ClearPath OS 2200 Product Documentation Library (7848 4482) is available with

your order.

All documentation related to the ClearPath OS 2200 library is also available on the

Unisys Product Support Web site at http://www.support.unisys.com

http://www.support.unisys.com


7850 5252–018 1–5

1.4. Security

Dorado servers achieve a significant level of security through their hardware and

firmware architecture. The OS 2200 Executive System (Exec) includes configuration

options that take advantage of the hardware security and extend it in several ways.

The level of additional security available to your enterprise is governed at a high level

by your choice of Fundamental Security, Security level 1, or higher security options

within the OS 2200 Exec. Some OS 2200 Exec security features are configured

through system generation and others can be changed dynamically by using Security

Administration (Security-Admin), Apex, or TeamQuest® Site Management Complex

(SIMAN). Refer to the ClearPath Enterprise Servers Security Administration for

ClearPath OS 2200 Help or ClearPath OS 2200 Apex Help for more information.

Security is a design and implementation requirement for all OS 2200 software

products. Furthermore, many of the software products that run on OS 2200 include

security features directly applicable to the software function. For more information on

these features, refer to “4.3 Communications Platform (CPComm),”“4.8 FTP Services

for ClearPath OS 2200,”“5.4 Network Database Server,”“5.7 Relational Database

Server,”“6.1 Business Information Server,’’ and “9.8 Operations Sentinel Basic Edition,”

for example. However, there are certain products whose sole purpose is to provide

enhanced security. In addition to Security-Admin, Apex, and SIMAN, four software

products can provide additional security for your enterprise:

• Cipher Application Programming Interface (Cipher API)

Encryption for data at rest

• Cryptographic Library (CryptoLib)

Provides the cryptographic algorithms used by communications products and

Cipher API

• Message Integration Services for OS 2200 (NTSI)

Supports network authentication for OS 2200 in cooperation with User

Authentication. Authentication modules included with NTSI support single sign-on

using Windows and Linux security through Lightweight Directory Access Protocol

(LDAP), Kerberos, and Windows NT LAN Manager (NTLM). This includes accessing

OS 2200 servers after establishing the user identity at a workstation by using

biometrics and smart cards. Another authentication module included with NTSI

supports logging into the OS 2200 server using Windows network credentials.

• User Authentication (FLEX)

Supports additional options for enhanced user authentication, including Configured

Password Profiles, an authentication module that enforces advanced password

rules. FLEX also supports the network-related authentication options released with

Message Integration Services. This includes the use of biometrics and smart

cards.

Additional information about OS 2200 security is available in white papers in the

Unisys Web site and in the documentation section of the product support Web site

http://support.unisys.com. Select the desired ClearPath Dorado server. In the Dorado

series support site, under Support Options, click Documentation, and then click

Dorado Security White Papers.

http://support.unisys.com


1–6 7850 5252–018

7850 5252–018 2–1

Section 2 Application Development Products

The enterprise server system supports a broad range of industry-standard

programming languages. In addition, a broad range of program development tools

helps you to implement, compile, test and debug programs with the least possible

effort.

The following products are described in this section:

• ASCII COBOL Compiler

• ASCII FORTRAN Compiler

• C Compiler

• COBOL Compiler

• Collector (MAP Processor)

• Common Mathematical Library (CML)

• Display Processing System (DPS 2200)

• Eclipse IDE for OS 2200

• FORTRAN Compiler

• Language Support System

• Linking System (LINK)

• Meta Assembler (MASM)

• PLUS

• Programmers Advanced Debugging System

• Runtime System for Basic Mode Compilers

• Runtime System for Extended Mode Compilers

• Service Library (SLIB)

• Sort/Merge (SORT)

• System Service Routines Library (SYSLIB)

• Universal Compiling System PLUS (UCS PLUS)

ASCII COBOL Compiler

2–2 7850 5252–018

2.1. ASCII COBOL Compiler

ASCII COBOL Compiler (formerly called ASCII COBOL or ACOB) is a complete

implementation of the COBOL language as defined in the American National Standards

Institute (ANSI) COBOL X3.23 1974 standard.

General Features

ASCII COBOL Compiler consists of a compiler and runtime system. ASCII COBOL

Compiler complies with the highest levels of all modules of ANSI COBOL. It recognizes

ASCII characters as the standard data mode at both source and object time. Fieldata

character-handling capabilities are available as an option.

The compiler of the ASCII COBOL Compiler product is multibanked and reentrant. It

produces optimized reentrant code that can be used in a multitasking, common bank,

or transaction environment.

Additional features and extensions of the ASCII COBOL Compiler product's compiler

and runtime system include the following:

• Multiple data formats, including ASCII, Fieldata, quarter- and sixth-word multiple

binary, and single- and double-precision floating point

• Debugging features, including MONITOR, EXHIBIT, subscript range checking, and

frequency count of procedures

• ANSI standard tape and label formats with optional recording modes for

processing Information Interchange tapes

• Fieldata COBOL and IBM fixed, variable, and undefined tape formats

• Optional index-sequential file organization on mass storage

• Interface to the Shared File System

• Common Storage Section for blank common

• The ability to produce object programs with D-bank space as large as 262,000

words

Related Product Information

The following technical manuals are available for this product on the Unisys Product

Support Web site:

• ASCII COBOL Compiler Runtime Technical Reference Manual (7862 6744)

• ASCII COBOL Programming Reference Manual (7830 7709)

• ASCII COBOL Supplementary Reference Manual (UP8584)

ASCII FORTRAN Compiler

7850 5252–018 2–3

2.2. ASCII FORTRAN Compiler

ASCII FORTRAN Compiler (formerly called ASCII FORTRAN or FTN) provides the

standard FORTRAN language (FORTRAN 77) specified by the ANSI FORTRAN X3.9-

1978 standard.

General Features

ASCII FORTRAN Compiler is a high-level, mathematically-oriented language processor.

It is a reentrant, multiphase, modular compiler that uses resources efficiently,

especially in interactive multiprogramming environments.

ASCII FORTRAN Compiler provides the following language extensions that are not

included in FORTRAN 77:

• Internal subroutines

• Double-precision complex data type

• Reread capability

• ENCODE/DECODE statements (storage-to-storage capability)

• Name list I/O

• INCLUDE statement (copy external source into FORTRAN compilation)

• Debug facility interactive postmortem dump (PMD) and walk-back mechanism

• Support of FTNPMD, Supertrace, and VDA

• Data initialization on DIMENSION and TYPE statements

• Multiple targets in assignment statements

• Acceptance of comments at the end of a source line

• BITS and SUBSTR pseudo-functions

Several ASCII FORTRAN Compiler features make maximum use of the OS 2200

architecture and operating system.

• Reentrant common-banked compiler and reentrant code generation.

• Common-banked I/O routines and Common Mathematical Library (CML).

• Interlanguage communication with COBOL, FORTRAN V, and MASM.

• Handling of complete ASCII/ISO character data.

• Multiple data banks and instruction banks extending the object program size

beyond 262,000 words.

• Extensive object program optimization. A relocatable element can be produced

that has been extensively optimized by the compiler to execute more rapidly. Both

local and global forms of optimization are available.

• A virtual programming feature for software paging of large arrays. Arrays can be

as large as 32 million words.

C Compiler

2–4 7850 5252–018

• Load-and-go facility provided by the checkout mode for quick compilation and

execution of FORTRAN programs.

• Sort/Merge interface.

• Service subprograms.

• Share File System interface.


The document ASCII FORTRAN Programming Reference Manual (UP8244) is available

for this product on the Unisys Product Support Web site.

2.3. C Compiler

C Compiler (formerly called UCS C or UC) is the implementation of the C language for

OS 2200 systems. It is an implementation of the C programming language processor

as defined in the American National Standards Institute (ANSI) C X3.159-1989 standard.

It also provides numerous extensions to this standard.

General Features

The basic C library supported by C Compiler provides more than 100 library functions.

C Compiler also includes a number of features to take advantage of the OS 2200

architecture:

• Multitasking capabilities

• Support for TIP and HVTIP

• Executive request (ER) interface routines

• Interface between the C language and other UCS languages

• Interface to Relational Database Server for ClearPath OS 2200 through either

embedded SQL or interpreted SQL

• Interface to

− Message Control Bank (MCB)

− Program Callable FURPUR (PCFP)

− Repository for ClearPath OS 2200

− Contingency handling

− Test and set queuing facilities

C Compiler

7850 5252–018 2–5

C Compiler Language Components

C Compiler consists of the following components:

• C language front-end compiler

The front-end compiler is a multipass processor combining macro preprocessing,

syntax analysis, and semantic analysis. It transforms source language input into a

common intermediate text, dictionary entities, and global data structures that are

then passed to a machine-dependent back end. There are two processors that you

can use to invoke the C compiler: UC and CIFSCC

− UC

The standard C compiler using the normal OS 2200 file naming convention.

Examples

@UC athena*srcs.func2

athena*oms.func2/o

− CIFSCC

Uses the CIFS path names on the processor call, or optionally on the #include

statements.

Examples

@’CIFSCC /athena/sources/utilfuncs/func2

/athena/libraries/utils/lib1/func2

• Run-time library

The C run-time library is a visible, user-callable set of files containing the following

items:

− C source statements that are included during compilation

− Precompiled subroutines that are linked so that they can be referenced at

execution time

Compatibility with UNIX

C Compiler is highly compatible with existing UNIX independent programs written for

Open Programming Environment (OPE) C and a subset of the C library functions. It has

the following two modes:

• Default

Default mode is the implementation of the 1989 ANSI standard.

• COMPAT

COMPAT mode provides a high level of source and language compatibility with the

UNIX V.4 C compiler.

COBOL Compiler

2–6 7850 5252–018



Support Web site:

• Universal Compiling System (UCS) Evaluation Overview (7833 0792)

• Universal Compiling System (UCS) Conceptual Overview (7831 0802)

• Application Development Programming Guide (7831 4077)

• C Compiler Programming Reference Manual Volume 1: C Language and Library

(7831 0422)

• C Compiler Programming Reference Manual Volume 2: Compiler and System

Interface (7831 0430)

2.4. COBOL Compiler

COBOL Compiler (formerly called Universal Compiling System COBOL or UCOB) is an

implementation of the COBOL language as defined by the American National

Standards Institute (ANSI X3.23-1985). It also provides numerous extensions to this

standard.

The COBOL source language implemented by COBOL Compiler includes all required

features of the American National Standards Institute (ANSI) COBOL X3.23-1985 and of

the Federal Information Processing Standards Publication 21-2 (FIPS PUB 21-2).

General Features

COBOL Compiler includes numerous compatibility features that ease code migration

from ASCII COBOL or the ANSI COBOL X3.25-1974 standard. (The COBOL 85 standard

contains many new features that were not in COBOL 74 and should not have any

impact on existing programs.)

COBOL Compiler is fully reentrant and produces optimized reentrant code usable in

multibanked, common-banked, or transaction program environments.

COBOL Compiler contains the following standard language extensions:


• Element I/O

• Embedded DML commands

• IBM tape processing

• Migration tools

• Interfaces for the following:

− Kanji

− Message Control Bank (MCB)

− Programmer's Advanced Debugging System

COBOL Compiler

7850 5252–018 2–7

− Relational Database Server for ClearPath OS 2200

(through embedded commands or program callable interfaces)

− Shared File System

− TIP

− HVTIP

− HVTIP II

• Internationalization (I18N) capabilities

• Zip Files

The COBOL Compiler provides five COBOL callable routines that enable COBOL

applications to read data directly from a compressed zip file. The routines also can

compress and write data from the OS 2200 to a zip file. To compress and

decompress the data, they use the Virtual Machine for the JavaTM Platform.

• MIN-ALS keyword option for UCOB

This option eliminates ALS-overflow error occurring at runtime for some COBOL

applications.

• D$WORK-WS keyword option for UCOB

This option is for use by DMS programs. When a DMS program places the DMCA

into COMMON using the INVOKE clause, the UCS COBOL compiler normally puts

the DMS D$WORK data structure at the end of COMMON-STORAGE, after all the

user variables. If COMMON-STORAGE layout is not the same in all program units in

an executable program, user variables can overlay the D$WORK data structure

and problems can occur. The D$WORK-WS keyword option causes the compiler

to put the DMS D$WORK data structure into WORKING-STORAGE, thereby

eliminating any potential problems.



Support Web site:




• Universal Compiling System (UCS) COBOL Programming Reference Manual

Volume 1, COBOL Statements (7831 0448)

• COBOL Compiler Programming Reference Manual Volume 2: Compiler and

System Interface (7831 0455)

Collector

2–8 7850 5252–018

2.5. Collector

Collector, also known as the MAP processor, combines or collects relocatable

elements generated by the language processors with relocatable library elements to

form an executable (absolute) element.

Collector provides a direct means of collecting or combining relocatable elements to

produce an executable program. The executable program, called an absolute element,

is structured so the Exec program loader can place it in execution. Optionally, you can

use Collector to create a single relocatable element from a collection of several

relocatable elements.

Once Collector creates the absolute program by collecting the relocatable elements,

the absolute element can be saved and re-executed many times. You re-collect the

program only if the program changes.

A program execution control statement (@XQT) or processor call within the runstream

places an absolute element (program) in execution. When the Exec encounters an

@XQT or processor call statement, it retrieves the program from its mass storage file,

loads it into main storage, and executes it.



Support Web site:

• Collector Programming Reference Manual (7830 9887)

• Data Structures Programming Reference Manual (7833 3481)

Common Mathematical Library

7850 5252–018 2–9

2.6. Common Mathematical Library

Common Mathematical Library (CML) is the system standard mathematical library.

Common Mathematical Library includes the math routines normally required by the

language processors. These include, but are not limited to, trigonometric, logarithmic,

and exponentiation functions in real, double-precision, and both single- and

double-precision complexes.

General Features

Common Mathematical Library is organized with a base set of reentrant static

common banks that provide calculation of frequently used mathematical functions.

The common bank implementation is intended to replace the former relocatable

mathematical functions at the user's option. Common bank reentrancy enables several

users to reference the same mathematical functions without having them loaded in

their absolute programs.

The mathematical function routines are available in four mathematical static common

banks and as RLIB$ mathematical function routines. Functions are classified according

to their occurrence in one of the mathematical banks: RMATH$, DMATH$, CMATH$, or

CDMATH$. The functions are further divided into the following eight classifications:

• Trigonometric

• Hyperbolic

• Exponential

• Logarithmic

• Root

• Exponentiation

• Intrinsic

• Support

Examples of functions include the following:

• SIN(x)

Single-precision sine

• COS(x)

Single-precision cosine

• TAN(x)

Single-precision tangent

• COTAN(x)

Single-precision cotangent

Display Processing System

2–10 7850 5252–018

2.7. Display Processing System

Display Processing System (formerly called DPS 2200) manages display-oriented

transactions and helps you define forms (screens), user profiles, security, test

environments, and more.

With Display Processing System, you can shorten development time, reduce errors

(through automatic input error handling), standardize your user interfaces, provide

display security, and achieve device independence.

Benefits

Using Display Processing System, you can:

• Reduce program development time for programs requiring full-screen interaction

with different types of terminals (device independence)

• Reduce program development time for transaction programs

• Reduce errors (the Display Processing System automatically handles input errors)

• Standardize user interface using the repository

• Provide easy definition, update, and review of forms

• Provide form and field security without special security code in your program

• Dynamically control field display attributes like intensity, highlight, emphasis, font,

and color

• Refresh a form after accidental destruction

• Store statistical and trace information about terminals in the Transaction

Processing (TIP) environment

• Define initial default values for fields during form definition

Features

Display Processing System includes the following features:

• Interface routines

Display Processing System provides an interface between form definitions,

application programs, and Display Processing System run-time routines. Interface

routines are available for C, COBOL, FORTRAN, and MASM.

• Batch and demand

Display Processing System makes system and application definitions easier, but

can also be used in demand and batch environments. This promotes device

independence, faster program development with fewer errors, automatic handling

of input errors, and display security.

• Display Processing System and I18N

Display Processing System features I18N Delivery 2. It performs string and

character classification, comparison, and conversion through the I18N Service

Library (I18NLIB). In addition, the Display Processing System provides

transliteration of literal text in a screen from one Coded Character Set (CCS) into

another CCS through the I18NLIB routines.

Display Processing System

7850 5252–018 2–11

Capabilities

Display Processing System has the following capabilities:

• Stores the data defining a form in a form library.

• Generates working storage in the demand environment or batch mode. The output

element is compatible with the ASCII COBOL Compiler, the COBOL Compiler, the

ASCII FORTRAN Compiler, the FORTRAN Compiler, or the C Compiler.

• Completes input/output (I/O) editing within the run-time handler. It removes I/O

buffers from a program and transfers only dynamic information to a program. The

user program receives and supplies data transferred to and from the form in

internal format (for example, numeric computational).

• Generates internal error messages and displays them on a specified message line

when logical errors occur in input data.

• Supports 7-bit and 8-bit character sets.

• Generates up to 10,000 pages of output.

• Provides standard transaction/demand programs to handle LOGON/LOGOFF

sequences and to control terminal test modes that enable or disable displaying

data fields.

• Supports the Integrated Recovery environment.

• Generates working storage in the repository (COBOL Compiler and C Compiler) for

a form if the Display Processing System is configured to use the repository.

• Provides the capability for an application program to lock the keyboard while an

output message is being sent to a terminal. This capability is useful when an

application program is busy and cannot receive input from the keyboard until it

completes the current operation. It also enables an applications program to send

status messages and perform other functions.

• Provides an extended security environment that ensures that sensitive data is

protected.

• Provides the capability for Display Processing System TIP transactions to be

executed in a distributed transaction processing environment using the Heritage

Application Access feature of the Open Distributed Transaction Processing

software.

Web Enabler for Display Processing System

Using the Web Transaction Server and the Web Enabler for Display Processing

System, programmers can adapt existing Display Processing System applications to

be Web accessible without changing the transaction programs themselves.

Programmers can enhance the applications interface and use modern Web browser

capabilities such as graphics, fonts, color, multimedia, and so forth.

Eclipse IDE for OS 2200

2–12 7850 5252–018



Support Web site:

• Display Processing System (DPS 2200) Run-Time Programming Reference

Manual (7830 7840)

• Display Processing System (DPS 2200) Form Design Programming Guide

(7831 2279)

• Display Processing System (DPS 2200) Administration Guide (7831 2295)

• Web Enabler for Display Processing System User's Guide (7851 5509)

• Display Processing System (DPS 2200) Programming Quick-Reference Guide

(7831 0000)

2.8. Eclipse IDE for OS 2200

Eclipse IDE for OS 2200 is an integrated development environment (IDE) tool based on

the Eclipse IDE open source product. Unisys has prepackaged, extended, and tested

Eclipse IDE to provide a complete and easy-to-install IDE for OS 2200 application

development.

All-In-One

The All-In-One feature is a prepackaged Eclipse and set of Eclipse plug-ins appropriate

for developing Java 2 Platform, Enterprise Edition (J2EE) Java Composite Applications.

The package includes the following:

• Eclipse IDE

• WTP

• EMF-SDO-XSD SDK

• GEF

• JEM SDK

• SQL Explorer

• Unisys CA


7850 5252–018 2–13

CA Eclipse Plug-In

The CA Eclipse Plug-in simplifies the development of Java composite applications. It

extends Eclipse with an OS 2200 project framework, language editors, and Telnet

communication capabilities. The Eclipse Plug-in enables you to create, modify, build,

and integrate OS 2200 3GL programs with new or existing Java application programs.

• Projects

− OS 2200 project Wizard and Eclipse IDE perspective

− Create, update, and delete OS 2200 projects

− Shared Eclipse IDE and OS working directory

− OS 2200 CIFS directories hold program source on the OS 2200

− Add, create, and delete program file elements from an OS 2200 project

− Managed Builds enable you to control builds and deployment

− Report compilation warnings and errors

− Displays program statement associated with warnings and errors

− Automatically connects to the OS 2200 system using a Telnet plug-in

− Automatic LETS-J to Unicode character conversion for project files

− Supports builds with output in Brkpt files

− Supports interactive debugging of UCS programs

• Editors

− COBOL IDE editor using the Eclipse COBOL IDE plug-in

− C/C++ editor using the Eclipse CDT plug-in

• PLUS editor

− Common Eclipse editor capabilities (Cut, Copy, Paste, and so forth)

− Syntax color coding

− Automatic block indention

− Automatic tab and line delimiter conversion

− Source line numbers

− Preference adjustments

• Java Application Integration

− TIP/HVTIP Java Connection class generator using annotations

− Build and edit Application Server configuration files

− Define and edit connector Views

− Supports code generation for using the BIS resource adapter and the DMS

resource adapter


2–14 7850 5252–018

• Unisys Telnet Plug-In

− Create Connection wizard

− Create Session wizard

− Opening manual sessions

− Set, update, and delete connection profiles

− Set, update, and delete Host Account profiles

− Automatic login script generation

− Cancel output

− Pause output

− Kill process and output

− Toggle echo state

− Command history scrolling

− Command Copy and Paste

− Copy a session output

• Logging and Diagnostics

− Built-in diagnostic logging of plug-in processing

− Automatic packaging and export of log files

• Integrated Eclipse IDE Help



Support Web site:

• ClearPath Application Development Solutions Eclipse IDE for OS 2200

Installation Guide (4729 2107)

• ClearPath Application Development Solutions Eclipse IDE for OS 2200 PLUS Editor Help (3850 8297)

FORTRAN Compiler

7850 5252–018 2–15

2.9. FORTRAN Compiler

FORTRAN Compiler (formerly called Universal Compiling System (UCS) FORTRAN, or

UFTN) is an implementation of FORTRAN, the programming language designed

specifically for mathematical, scientific, and technological applications. It conforms to

the ANSI FORTRAN X3.9-1978 standard and provides numerous extensions to this

standard.

General Features

FORTRAN Compiler conforms to the ANSI FORTRAN X3.9-1978 standard (known as

FORTRAN 77) and to FIPS PUB 69-1 standards. It also supports most ASCII FORTRAN

extensions and some features of the ANSI FORTRAN X3.9-1990 standard, especially

for array handling features.

FORTRAN Compiler includes the following general features:

• Support of relational databases through either module SQL or interpreted SQL

• Support of network databases through embedded DML commands

• Transaction processing in TIP, HVTIP, or HVTIP II environments with interfaces to

DPS 2200 and MCB

• Multitasking capabilities

• Interface to Sort/Merge utility


• Element I/O



Support Web site:




• FORTRAN Compiler Programming Reference Manual Volume 1: FORTRAN

Statements (7831 0489)

• FORTRAN Compiler Programming Reference Manual Volume 2: Compiler and

System Interface (7830 7477)

Language Support System

2–16 7850 5252–018

2.10. Language Support System

Language Support System (formerly called Universal Compiling System (UCS)

Language Support System or UCS LSS) functions as a back end to the Universal

Compiling System compilers. It takes language-dependent compilations from any of

these compilers and generates machine-dependent object code.

Note: Language Support System must be used with a Universal Compiling System

compiler to generate code to be run on the system.

Language Support System is the common back-end processor for all Universal

Compiling System languages. The Universal Compiling System compilers consist of

processors that perform syntax analysis appropriate to the language being processed

and produce architecture-independent code. This intermediate output then passes to

Language Support System, the common back-end processor. Language Support

System generates optimized, architecture-dependent code; the output can be limited

to one or more particular hardware systems.

The final output of a compilation is an object module. This object module can be

executed immediately, or processed by the Linking System to resolve references

(calls) and produce a new object module.

General Features

Language Support System supports most high-level language features found in the

user environment. It can:

• Handle recursive and nonrecursive programs.

• Handle high-level language data types such as integer, floating point, packed

decimal, ASCII/ISO character, kanji character, file, pointer, logical, set, bit string,

and user-defined data types.

• Provide programming constructs such as assignments, IF statements, file I/O,

looping statements, CASE statements, and many other structured programming

statements.

• Create debugging tables for interactive symbolic debugging with the

Programmer's Advanced Debugging System.

• Provide interfaces to other software products such as PCIOS, Enterprise Network

Database Server for ClearPath OS 2200, Programmer's Advanced Debugging

System, and SORT.



Support Web site:




Linking System

7850 5252–018 2–17

2.11. Linking System

The Linking System is an integral component in the Universal Compiling System

(extended mode) programming environment. It provides the means for creating object

modules (separately compiled routines) and provides both dynamic and static linking

services, which enable these modules to execute as a single program. Linking System

also loads object modules to be executed.

Note: The Linking System is sometimes referred to as LINK. Do not confuse this

product with the LINC II system that is an advanced 4GL system generator.

Linking is the process of converting a program from the form produced by a compiler

or assembler into a form that the computer hardware can execute. The two biggest

tasks of linking are to

• Replace symbolic external references (calls) with the entry-point addresses

(definitions) those references represent. This usually involves combining two or

more separately compiled or assembled object modules (routines) into a new

object module or into a whole executing program.

• Adjust addresses affected by address relocation.

Programs written in assembly language or in most of the high-level languages (such as

C, FORTRAN, or COBOL) cannot be executed in their original form, because a

computer cannot execute programs in symbolic form (words). The programs must

first be translated to the operations of the computer by being encoded in a form the

computer can interpret (usually a sequence of binary numbers).

Usually compiled programs are not entirely in machine-oriented form. When routines

are compiled separately, they cannot know the addresses of other routines. When one

routine calls (makes a reference to) another, the compiler cannot generate the address

of the other; it must leave the reference in symbolic form. That is, the compiler

compiles the hypothetical statement "CALL SUBPROG" into a jump to the symbolic

name SUBPROG, rather than into a jump to an entry point address.

The Linking System is a key component in the UCS/extended mode programming

environment; it links separately compiled routines known as object modules that can

then be executed in this environment as a single program. The Linking System also

loads object modules to be executed.

In addition, the Linking System provides the means for creating extended mode

subsystems. The Linking System can manage and load subsystems. The Linking

System also provides various utilities for obtaining information about object modules,

ZOOMs, and subsystems.

To make full use of the Linking System capabilities in the UCS environment, the UCS

Support Package must be ordered.

Linking System

2–18 7850 5252–018

General Features

The Linking System can create and obtain information about these object module

types:

• Standard object modules

• Subsystem definition object modules

• Zero overhead object modules (ZOOM), which are loaded by the Exec

The Linking System provides these methods of linking object modules:

• Static (preload) linking

• Dynamic (run-time) linking

Components

Some of the Linking System components are

• LINK processor

The LINK processor links object modules together. The LINK processor can also

be used to tailor a program for a specific application. Some examples of this are

merging or moving banks, deleting definitions, producing a specific kind of object

module, or changing a reference name.

• CIFSLD processor

The CIFSLD processor is an interface to the static linker that uses CIFS path names

in its processor call and in the static linking commands.

Examples

@’CIFSLD /athena/sources/links/check-passenger-link

/athena/applications/tipzooms/chkpass

• SSDP processor

The Subsystem Definition Processor (SSDP) is used to define subsystem

attributes.

• SSInfo processor

The SSInfo Processor (subsystem information processor) displays a variety of

information about extended mode software subsystems and alternate file

common banks (AFCB) that are installed on any OS 2200 system.

• OMCR processor

The object module cross-reference processor can be used to list references and

definitions in object modules.



Support Web site:

• Linking System Subsystems Programming Guide (7830 7451)

• Linking System Programming Reference Manual (7831 0505)

Meta Assembler

7850 5252–018 2–19

2.12. Meta Assembler

Meta-Assembler (MASM) processor assembles a symbolic source element to produce

a relocatable or object module element.

Restriction: Unisys supports extended mode MASM usage only in software

written by Unisys or in interfaces written by the customer that explicitly require

assembler-produced object modules according to the documents published by

Unisys.

The MASM processor accepts both Fieldata and ASCII input and maintains character

constants in either code as specified by the user. MASM uses an internal code to

store character constants that do not have to be maintained in a specific character

code, such as names in the dictionary and some relocation information.

MASM performs specified tasks based on the interpretation of statements received

primarily using the symbolic input/output routine (SIR$); MASM then produces output

that depends on the user's request. The relocatable output routine (ROR) produces a

relocatable binary element. The object module output routine (OMOR) produces an

object module element. MASM optionally produces a printed listing of the input and

its processed form.

In addition, MASM can produce an omnibus element known as a definition mode

assembly. A definition mode assembly saves the result of processing a set of

definitions so that it can be used in several assemblies. The use of definition mode is

considerably faster since MASM is required to read the source language only once.

Another, though seldom used, capability of MASM is to produce symbolic elements

suitable for input to other processors using the symbolic input/output routine (SIR$).

MASM performs its function in two scans of the input. The first scan is known as the

summary pass, and the second is known as the generative pass. These two passes of

the source input, from the first to the last source image, are known as the main

assembly. Assemblies called within the main assembly are known as subassemblies.

MASM is not limited to generating code for a particular hardware architecture even

though the predefined OS 2200 instruction set is loaded when the MASM processor is

loaded. With the built-in directives and functions, you can define the instruction set

and useful directives for any hardware architecture, if the output of MASM (OS 2200

relocatable binary or object module format) can be converted to a form acceptable to

the operating system on the alternate architecture.



Support Web site:

• Meta-Assembler (MASM) Programming Reference Manual (7830 8269)

• Data Structures Programming Reference Manual (7833 3481)

• Exec System Software Executive Requests Programming Reference Manual

(7830 7899)

PLUS

2–20 7850 5252–018

2.13. PLUS

PLUS (an acronym for Programming Language for Unisys Systems) is a high-level

language developed by Unisys for internal use by Unisys systems programmers. It is a

Unisys proprietary language and compiler that is released to OS 2200 system sites

only as a tool for generating and maintaining Unisys software products. Any other use

of PLUS is not authorized.

PLUS was developed for use as an in-house product development language. The

benefit of having a custom-built high-level language is that it enables Unisys to

develop features without dependency on external development or standards

organizations. PLUS was developed for use on systems prior to the introduction and

general use of extended mode. (The extended mode version is called Universal

Compiling System (UCS) PLUS, and there is an extension of UCS PLUS called XPLUS.)

The following restrictions apply to PLUS:

• PLUS is available in absolute mode only.

• PLUS must be used to build only purchased Unisys software. Any other use is not

authorized.

• Unisys maintains and supports PLUS, but support is limited to problems in

compiling released Unisys software that was developed in PLUS. No support is

provided for problems in compiling software developed by individual sites.

• You can submit a User Communication Form (UCF) against Unisys software coded

in PLUS, but not against PLUS itself.

2.14. Programmers Advanced Debugging System

Programmers Advanced Debugging System (formerly called PADS) helps you debug

programs compiled by the ASCII COBOL Compiler or any of the Universal Compiling

System compilers. You can debug programs interactively as the program executes or

after the program terminates in error.

General Features

PADS eases the job of debugging. You don't need to embed debugging statements in

your source code, which can save time and reduce errors. Also, you debug programs

at a symbolic level, which shields you from the low-level details of the system

architecture.

PADS is a symbolic debugging tool that enables interactive debugging of programs

written in any of the Universal Compiling System programming languages, ASCII

COBOL Compiler, and basic mode Meta-Assembler (MASM).

During interactive PADS sessions, programmers can collect and use debugging

information about executing programs. They can

• Display or modify parts of the program

• Trace the logic flow of programs

Programmers Advanced Debugging System

7850 5252–018 2–21

• Trap faults and other events in programs

PADS provides significant advantages for debugging because it

• Requires no debugging statements in source code.

• Uses high-level addressing.

• Enables you to debug programs at a symbolic level, without having to know the

low-level details of the system architecture. PADS enables you to work with

symbolic parts of a program such as program symbolic names, variables, line

numbers, labels, paragraph names, and section names.

• Enables the programmer to perform low-level debugging; that is, work with

programs at a hardware address level.

PADS has an interactive command language. Using PADS, the programmer can

interact with a program at selected points or at any point where an error might occur.

For example, the programmer can suspend or resume execution, or examine and

modify the contents of data items.

PADS can be used with a number of programming environments because it

• Supports dynamically linked object modules, statically linked object modules, and

zero overhead object modules (ZOOM).

• Provides a common command syntax that applies to all supported high-level

languages.

• Supports interactive operation on programs running in demand mode and

supports live operations using planned scripts on programs running in batch

mode.

• Supports postmortem analysis for programs executed in batch mode, demand

mode, TIP, or HVTIP that create a DIAG$ equivalent file before termination.

• Supports the Programmer's Workbench debugging capability.

• Provides an updated Programmers Advanced Debugging System (PADS)

Quick-Reference Help available as a CHM file

The NPEER feature supported by PADS can point to the areas of inefficiency in your

applications. The NPEER feature consists of the OM DC-NPEER that is included with

your application at the static link time. The NPEER processor generates performance

reports after application execution.



Support Web site:

• Programmers Advanced Debugging System (PADS) Programming Guide

(7831 0562)

• Programmers Advanced Debugging System (PADS) Quick-Reference Help

(7831 0570)

Runtime System for Basic Mode Compilers

2–22 7850 5252–018

2.15. Runtime System for Basic Mode Compilers

Runtime System for Basic Mode Compilers (formerly called Universal Compiling

System Run Time System or UCSRTS) contains storage management and SORT

interface routines. These routines are used by the runtime library of basic mode

compiler run-time systems such as the ASCII COBOL compiler and ASCII FORTRAN

compiler.

Note: Do not confuse the Runtime System for Basic Mode Compilers with the

Runtime System for Extended Mode Compilers. The Runtime System for Extended

Mode Compilers is used with the Universal Compiling System compilers.

Runtime System for Basic Mode Compilers contains storage management routines

used by the runtime system of the ASCII COBOL Compiler and the ASCII FORTRAN

compiler. Runtime System for Basic Mode Compilers also contains SORT and MERGE

interface routines used to implement the ASCII FORTRAN Compiler Sort/Merge

interfaces. All of these routines operate in the traditional programming environment

(basic mode).

Runtime System for Basic Mode Compilers is not part of the Universal Compiling

System, which is both written in and generates code in extended mode and provides

more extensive addressing capabilities than the earlier basic mode architecture.

Runtime System for Basic Mode Compilers consists of a number of elements that

reside in the system file SYS$LIB$*UCSRTS.

• A proc element

• Relocatables required by the ASCII COBOL compiler and ASCII FORTRAN compiler

runtime library routines

Runtime System for Basic Mode Compilers should not be confused with Runtime

System for Extended Mode Compilers that resides on the system as both a set of

alternate file common banks (AFCB) and as a set of object modules that provide an

extended mode object code execution environment for the Universal Compiling

System programming languages.

2.16. Runtime System for Extended Mode Compilers

Runtime System for Extended Mode Compilers (formerly called UCS Runtime System

or URTS) resides on the system as both a set of alternate file common banks (AFCB)

and as a set of object modules that provide an extended mode object code execution

environment for the Universal Compiling System (UCS) programming languages.

Note: Do not confuse the Runtime System for Extended Mode Compilers with the

Runtime System for Basic Mode Compilers. The Runtime System for Basic Mode

Compilers is used with traditional programming environment compilers.

Service Library

7850 5252–018 2–23

Runtime System for Extended Mode Compilers provides common interfaces and

services to all Universal Compiler System (UCS) programs. These include

• Interfaces to the Universal Data System (UDS) products

• Input/output interfaces

• Data conversion routines

• Built-in math functions

• Service libraries

Runtime System for Extended Mode Compilers also performs program initialization

and termination. While previous compilers each had their own run-time system, in the

Universal Compiling System the similar tasks performed by the multiple run-time

systems have been combined into a single runtime system used by all executing

programs.

Components of Runtime System for Extended Mode Compilers include object

modules and the service library, both of which must be available at link time. The

object modules provide runtime program tables and interfaces required by Runtime

System for Extended Mode Compilers and Programmer's Advanced Debugging

System. The service library is a set of object modules that provide part of the object

code environment for Universal Compiling System compilers.



Support Web site:




2.17. Service Library

Service Library (SLIB) is a collection of services that perform common tasks for

programs written in Universal Compiling System high-level languages. These services

provide high-level interfaces to perform tasks that would otherwise require low-level

programming. SLIB services have been developed to be used repeatedly by many

users and programs. These services can reduce development time, eliminate common

errors, and promote consistency.

SLIB provides services that perform tasks typically required for processors in the

OS 2200 environment. SLIB services include

• Character Conversion Services

• Run-Condition Word Services

• Element Type Services

• Internal Format Services

Sort/Merge

2–24 7850 5252–018

• Level Identification Services

• Processor Setup Services

• System Data Format Input Services

• Storage Management Services

• Symbolic Read Services

• Symbolic Write Services

• Time and Date Services

• High-Level Language Interfaces

• High-Performance I/O Interface to the Exec

The caller of a service in SLIB can be sure that the interface does not change, except

in a controlled manner, and that the service continues to function as documented,

regardless of the level of Exec software, the processor type, or the hardware device.

SLIB is installed on OS 2200 extended mode systems as a fixed-gate shared

subsystem. A fixed-gate shared subsystem is the extended mode equivalent of basic

mode common banks. Principal advantages of this implementation are as follows:

• SLIB code banks are shared and reentrant. Only one copy of the Service Library

code needs to be loaded.

• Once loaded, SLIB remains loaded (unless specifically deactivated). Services are

constantly available to all users without the overhead of loading and reloading

called routines.


The document Service Library (SLIB) Programming Reference Manual (7830 7857) is

available for this product on the Unisys Product Support Web site.

2.18. Sort/Merge

Sort/Merge (SORT) consists of two parts:

• An independent SORT processor activated by using Executive Control Language

(ECL) and controlled by user-supplied parameters (processor mode, type of input

data, file formats).

• The callable Sort/Merge subroutines used to perform the actual sort and merge

operations requested by the SORT processor or by other languages.

SORT Processor

The SORT processor performs copying, sorting, and merging operations. You use it to

do the following:

• Sort the records in one or more files

• Change the format of the output file with the COPY operation

System Service Routines Library

7850 5252–018 2–25

• Change the format of the records by deleting and moving fields based on

character position using the SELECT parameter

• Combine the records of two or more identically sorted files

Executive Control Language (ECL) activates the SORT processor to do the following:

• Read input files from cards, mass storage, and tape

• Perform copy, estimate, merge, retrieve, or sort operations

• Create output files

Sort/Merge Subroutines

The Sort/Merge subroutines consist of a set of callable routines to perform a sort or

merge operation. The routines are implicitly called from the SORT processor, ASCII

COBOL Compiler, ASCII FORTRAN Compiler, COBOL Compiler, and FORTRAN

Compiler.

Explicit interfaces exist for basic mode Meta Assembler (MASM), C Compiler, and

Universal Compiling System PLUS Compiler.

General Feature

Sort/Merge provides the LOG message runid that identifies the run or transaction

associated with the SORT characteristics.


The document Sort/Merge Programming Guide (7831 0687) is available for this

product on the Unisys Product Support Web site.

2.19. System Service Routines Library

System Service Routines Library (SYSLIB) is a set of reusable routines for developers

of both application and system software. This standardized implementation of

commonly required services eliminates the need for detailed knowledge of the

internal system data structures, which are subject to change.

SYSLIB contains absolute, object module, omnibus, procedure, relocatable, and

symbolic elements. The SYSLIB routines can be grouped into the following functional

areas:

• System Procedures, Definitions, and Entry Points

• Collector Interface Routines

• Diagnostic and Debugging Routines

• Editing Routines

• Processor Interface Routines (PIRs)

• Utility Routines

Universal Compiling System PLUS

2–26 7850 5252–018

SYSLIB has a number of important features:

• Constant interface that functions even when software and hardware levels change

• Easier ways to develop executable programs (also known as processors) for the

system environment

• Common interfaces to system data structures that do not change even though the

underlying data structures might change

• Standardized activities throughout the system environment that improve system

performance and provide a consistent user view of the system

All the SYSLIB elements are contained in the SYS$LIB$*SYSLIB file. A subset of the

SYSLIB relocatable routines is also available in the SYSLIB common banks.


The document System Service Routines Library (SYSLIB) Programming Reference

Manual (7833 1733) is available for this product on the Unisys Product Support Web

site.

2.20. Universal Compiling System PLUS

Universal Compiling System PLUS (UCS PLUS or UPLS) is a high-level language

developed by Unisys for internal use by Unisys systems programmers. It is a Unisys

proprietary language and compiler that is released to OS 2200 system sites only as a

tool for generating and maintaining Unisys software products. Any other use of

UCS PLUS is not authorized.

UCS PLUS is an extended mode version of PLUS, which was developed for use as an

in-house product development language. The benefit of having a custom-built high-

level language is that it enables Unisys to develop features without dependency on

external development or standards organizations. (There is also an extension of

UCS PLUS called XPLUS.)

The following restrictions apply to UCS PLUS:

• UCS PLUS is available in absolute mode only.

• UCS PLUS must be used to build only purchased Unisys software. Any other use is

not authorized.

• Unisys maintains and supports UCS PLUS, but support is limited to problems in

compiling released Unisys software that was developed in UCS PLUS. No support

is provided for problems in compiling software developed by individual sites.

• You can submit a User Communication Form (UCF) against Unisys software coded

in UCS PLUS, but not against UCS PLUS itself.


7850 5252–018 2–27



Support Web site:

• Universal Compiling System (UCS) PLUS Programming Reference Manual

Volume 1, PLUS Statements (7831 0497)

• Universal Compiling System (UCS) PLUS Programming Reference Manual

Volume 2, Compiler and System Interface (7831 2287).


2–28 7850 5252–018

7850 5252–018 3–1

Section 3 Transaction Processing Products


• Open Distributed Transaction Processing

• OSI-TP High Performance Distributed Transaction Processing for XATMI

• WebSphere® MQ Version 7 for ClearPath OS 2200

• ClearPath OS 2200 QProcessor

• ClearPath OS 2200 Interface to Microsoft Message Queuing

• High-Performance Transaction Processing Interconnect (HTP/IC)

3.1. Open Distributed Transaction Processing

Open Distributed Transaction Processing (formerly called Open/OLTP) is a suite of

system software products that combines the power and reliability of traditional online

transaction processing systems with the flexibility and freedom of today's

standards-based distributed transaction solutions. With Open Distributed Transaction

Processing and related software, you can

• Link or connect isolated applications, so they collectively provide new services or

greater efficiencies.

• Perform global transactions in or across enterprises, thereby improving

coordination between departments or with business partners.

• Modernize applications and provide broader access to them by adding Web or

Java interfaces.

• Create a bridge between the traditional ClearPath environment and other

component-based software technologies. In this way, you can easily "plug in"

standard, off-the-shelf application components as they become available.

With Open Distributed Transaction Processing products, you can distribute application

program processing among heterogeneous computer systems, so that transaction

processing tasks are shared.

Open Distributed Transaction Processing software implements the Open Group

Distributed Transaction Processing (DTP) model. The DTP model is an international

standard that promotes interoperability among different computer systems.

OSI-TP High Performance Distributed Transaction Processing for XATMI

3–2 7850 5252–018



Support Web site:

• Open Distributed Transaction Processing Getting Started (7833 5007)

• Open Distributed Transaction Processing Programming Guide (7833 5049)

• Open Distributed Transaction Processing Administration Guide

− Volume 1: Installation, Configuration, and Ongoing Administration

(7833 5072)

− Volume 2: Building Applications (7833 5080)

• Open Distributed Transaction Processing XATMI Application Program Interface

Programming Guide (7833 5064)

• Open Distributed Transaction Processing TX Application Program Interface


• Open Distributed Transaction Processing Heritage Application Access

Administration and Programming Guide (7833 5098)

3.2. OSI-TP High Performance Distributed Transaction Processing for XATMI

OSI-TP High Performance Distributed Transaction Processing for XATMI (OSI-TP,

formerly called HTP/X) provides high-performance distributed transactions between

Unisys and other Unisys vendors who have implemented the ISO/IEC standard. It

facilitates communication between Windows or Java 2 Platform, Enterprise Edition

(J2EE) client programs (Web pages, Java applications and applets, Microsoft ActiveX,

.NET and DCOM clients) and Open Distributed Transaction Processing services on

ClearPath OS 2200 nodes. This makes it possible for Windows or J2EE client programs

to request OS 2200 Open Distributed Transaction Processing services and include

them in global or nonglobal transactions.

General Features

OSI-TP includes the following features:

• High-performance transaction processing architecture

• Support for ISO/IEC 10026 open standard for distributed transaction processing

• Open Distributed Transaction Processing (formerly Open/OLTP) interoperability

with other transaction processing systems such as Oracle Tuxedo, Microsoft

Transaction Server (MTS), COM+, .NET (see Distributed Transaction Integration)

and J2EE application servers

• Multiple OS 2200 nodes

• Multiple Intel

• Sample configurations for common ClearPath multinode environments

WebSphere® MQ Version 7 for ClearPath OS 2200

7850 5252–018 3–3



Support Web site:

• Open Distributed Transaction Processing XATMI Application Program Interface


• OSI-TP High-performance Transaction Processing for XATMI (HTP/x)

Implementation and Administration Guide (2750 2558)

3.3. WebSphere® MQ Version 7 for ClearPath OS 2200

WebSphere® MQ Version 7 for ClearPath OS 2200 (WebSphere MQ) is the follow-on

product to MQSeries for ClearPath OS 2200. WebSphere MQ is based on version 7.0

of the IBM product IBM® WebSphere® MQ Version 7.0 and requires an OS 2200

QProcessor. See “ClearPath OS 2200 QProcessor” for information on OS 2200

QProcessor. As this version of the product is an upgrade to MQSeries, all the

capabilities that are available in MQSeries for ClearPath OS 2200 is applicable here.

This section provides a brief description of the general high-level capabilities of the

product and some of the new features.

WebSphere MQ allows TIP/HVTIP or batch programs on ClearPath OS 2200 servers to

use message queuing to participate in message-driven processing. It provides

transactional support with WebSphere MQ acting as a XA-compliant resource

manager (RM) under Open Distributed Transaction Processing. WebSphere MQ can

operate on any platform on which a compatible version of WebSphere MQ is available

since it is based on IBM® WebSphere® MQ Version 7.0.

Capabilities

WebSphere MQ is based on a more recent version of the IBM product

IBM® WebSphere® MQ Version 7.0 than MQSeries for ClearPath OS 2200. It includes

the following additional features:

• Enhanced publish or subscribe capabilities including the queue manager's

integrated Publish/Subscribe functionality to simplify application programming

• Use of 64-bit addressing

• Enhanced channel security through the use of OpenSSL (Secure Sockets Layer)

including the use of Federal Information Processing Standards (FIPS) 140-2

compliant mode

• New and convenient Web-based administrator interface used for deployment and

administration called the OS 2200 QProcessor Administration Console

• Enhancements and changes to the administration functions of the MQSC

administration interfaces and control commands

ClearPath OS 2200 QProcessor

3–4 7850 5252–018

• The WebSphere MQ bridge for HTTP is a Java, Enterprise Environment (JEE) Web

application that allows client applications to exchange messages with WebSphere

MQ without the need to install a WebSphere MQ client. You can call WebSphere

MQ from any platform or language with HTTP capabilities. The WebSphere MQ

bridge for HTTP is not suitable for use with messages, if guaranteed delivery is

required

• MQI Client Enhancements

• New Message Queue Interface (MQI) extensions provide new capabilities

• The WebSphere MQ classes for Java Message Service (JMS) are enhanced to make

WebSphere MQ a more natural fit with the features of JMS

In addition to the new features, the following restrictions on MQSeries for ClearPath

OS 2200 were removed by Unisys:

• Queue manager clustering support

• Security Option 3 environment support

• Exec configuration parameter NPECTRL set to TRUE

• Several WebSphere MQ Explorer restrictions

• Sticking support for TIP/HVTIP OLTP servers

• Chained message headers support

• XTC and XTC 2PC remote recovery


The document WebSphere® MQ Version 7 for ClearPath OS 2200 Installation,

Administration, and Programming Guide (3843 3744) is available for this product on the Unisys Product Support Web site.

3.4. ClearPath OS 2200 QProcessor

The Unisys ClearPath OS 2200 QProcessor (OS 2200 QProcessor) is a cost-effective,

high performance, secure, and reliable environment for enterprise-class message

queuing. It is designed to enable applications running under the control of the OS 2200

operating system on a ClearPath server to utilize WebSphere MQ on ClearPath

OS 2200.

The OS 2200 QProcessor, which is tightly integrated with the ClearPath OS 2200

server, is optimized for running WebSphere MQ 7.0. This product enables OS 2200

applications (TIP/HVTIP, Open DTP, and batch) to take advantage of the high level of

performance, reliability, and security of the OS 2200 operating environment.

Capabilities

• Provides WebSphere MQ Version 7 to the ClearPath OS 2200 customers

• Enables OS 2200 applications to fully participate in message-oriented processing

• Existing MQSeries for ClearPath OS 2200 applications can use WebSphere MQ for

ClearPath OS 2200 without re-linking

ClearPath OS 2200 Interface to Microsoft Message Queuing

7850 5252–018 3–5

• Provides migration paths from MQSeries for ClearPath OS 2200 to WebSphere

MQ for ClearPath OS 2200

• Supports Queue Manager Clusters for increased availability, load balancing, and

reduced system administration

• Supports high-availability clustering for automated detection of and recovery from

common hardware and software failures

• Supports IPv6

• Supports SSL connections

• Supports publish or subscribe capabilities


The document ClearPath Specialty Engine for OS 2200 Configuration Guide (3839

3005) is available for this product on the Unisys Product Support Web site.

3.5. ClearPath OS 2200 Interface to Microsoft Message Queuing

ClearPath OS 2200 Interface to Microsoft Message Queuing (Interface for MSMQ) is a

COBOL-friendly interface to MSMQ message queues. It enables OS 2200 applications on an OS 2200 server to send to and receive messages from these queues, which in

turn enable the applications to interact asynchronously with other applications on

Windows systems, other OS 2200 servers, UNIX systems, and IBM MVS systems.

Microsoft Message Queuing (MSMQ) is a queue manager for applications that run on

Microsoft Windows servers.

ClearPath OS 2200 Interface to Microsoft Message Queuing provides a set of

application interfaces (API) for processing MSMQ queues in an enterprise network.

The APIs of the Interface for MSMQ enable an application to

• Open a queue for receiving (reading) or sending (writing) messages.

• Receive messages from a queue and remove them.

• Peek at (examine) messages on a queue without removing them.

• Send a message.

• Close a queue.

• Delete a queue.

• Create a new queue.

Agent for the Interface

The agent is the interface for the OS 2200 application programs; it is an object module

linked with the application program. The application interfaces support the COBOL and

the C compilers.

High-Performance Transaction Processing Interconnect

3–6 7850 5252–018

This agent uses the MSG_CALL_WITH_ID function of the Messaging Integration

Services product to interoperate with the companion adapter that resides on the

Windows server.

The agent is a thin client (that is, the bulk of the logic is in the server) and saves no

state. It uses only Activity Local Storage and supports OS 2200 multiple activity

programs.

Adapter for the Interface

The adapter provides the interface to the MSMQ product; it is a Messaging Integration

Services C++ Class Interface service adapter.

This adapter establishes a processing thread from a pool in the adapter program for

each open connection session on the OS 2200 server. This session is a message call

exchange.

The adapter uses the MSMQ COM interface (MSMQ object interfaces) to MSMQ to

perform its tasks.


The document ClearPath OS 2200 Interface for Microsoft Message Queuing Help

(Self-extracting Help file) (6885 2722) is available for this product on the Unisys Product Support Web site.

3.6. High-Performance Transaction Processing Interconnect

High Performance Transaction Processing Interconnect (HTP/ic) is system software

that facilitates communication between Windows or Java 2 Platform, Enterprise

Edition (J2EE) client programs (Web pages; Java applications and applets; Microsoft

ActiveX, .NET, and DCOM clients) and Open Distributed Transaction Processing

services on the OS 2200 nodes. This makes it possible for Windows or J2EE client

programs to request OS 2200 Open Distributed Transaction Processing services and include them in global or nonglobal transactions.

The HTP/ic-2200 product enables interoperability for applications using Distributed

Transaction Processing. This includes applications written for Distributed Transaction

Integration, Open Transaction Integrator, or J2EE Connector for Open DTP.

These products provide protocols and services that enable heterogeneous computers

to communicate during global transactions, using functions in the Open Group XATMI

specification.


7850 5252–018 3–7

General Features

High Performance Transaction Processing Interconnect (HTP/ic) has the following

features:

• Provides infrastructure so that Windows or J2EE applications can interoperate

with OS 2200 Open Distributed Transaction Processing applications (see Distributed Transaction Integration or J2EE Connector for Open DTP).

• OSI-TP compliant (supports protocols defined in ISO/IEC 10026).

• Provides Microsoft Transaction Server (MTS) integration so OS 2200 services can be combined with Windows resources in a global transaction using COM+ or .NET.

• Enables an administrator to configure calling IP addresses with each called IP

address to optimize routing in a complex network.

• Enables an administrator to configure remote port numbers that enable HTP/ic to

connect to hosts that listen on ports other than port 102.

• Enables an administrator to specify domain names for the calling or called IP

addresses.

• Enables an administrator to configure the Communications Platform product to

use for communications.

• Provides the ability to RESET the IP address that is used to the first IP address in

the list.

• Provides support of both link level and user level security.


3–8 7850 5252–018

7850 5252–018 4–1

Section 4 Communications and Networking Products

The communications and networking products described in this section enable you to

distribute information and share resources as well as to provide reliable transmission

of data, text, graphics, image and voice information.

The following products are described in this section.

• Communications Application Program Interface (COMAPI)

• Communications Interface for Transaction Applications (CITA)

• Communications Platform (CPComm)

• Communications Platform for Open Systems (CPCommOS)

• Cryptographic Library (CryptoLib)

• Distributed Data Processing File and Job Transfer (DDP-FJT)

• Distributed Data Processing Program-to-Program Communications (DDP-PPC)

• FTP Services for ClearPath OS 2200

• Message Control Bank (MCB)

• Messaging Integration Services for ClearPath OS 2200

• System Interface for Legacy Application Systems (SILAS)

• TCP/IP Application Services (TAS)

Communications Application Program Interface (COMAPI)

4–2 7850 5252–018

4.1. Communications Application Program

Interface (COMAPI)

Communications Application Program Interface (COMAPI) is a software product that

enables applications to access a communications network. It provides a new

environment and sockets-like interface for OS 2200 application programs that handle

both TCP and UDP connections. If you also use Communications Interface for

Transaction Applications (CITA), then network input through COMAPI can schedule

transactions using the Message Control Bank (MCB).

COMAPI consists of the following components:

• A background run that “owns” all the connections

• A fixed gate shared subsystem

• BSD/Unix sockets library code modules

COMAPI provides a set of program-callable procedures that enable applications to

access the communication services by Communications Platform. COMAPI simplifies

the task of using communication services by providing application programmers with

a basic set of commands such as LISTEN, CONNECT, SEND, RECEIVE, and

DISCONNECT.

COMAPI provides an efficient interface by decreasing the number of hand-offs

between different components in the transaction processing environment (TIP).

Instead of using position identifiers (PID) to identify TIP end users, COMAPI passes a

unique identifier, a socket ID, to the transaction. This socket ID is then used for all

subsequent communication with the peer. In addition, COMAPI provides a

conversational mode for TCP/IP connections. Instead of sending only one request for

each session, transactions can now create conversational loops using the SEND and

RECEIVE calls.

General Features

The general features include the following:

• FastDataAccess

This feature enables the application to make a single call to retrieve all outstanding

data and events for a given session. This eliminates a redundant call when looping

using the TCP QBRECEIVE, which is necessary in order to discover that all data has

been processed.

• Program Registration

This feature enables you to register for program-wide registration which is

recoverable over a restart of the background run.

• Reduced Input Path

COMAPI uses the queue bank repository feature of OS 2200 to stage network

input data so that the transfer of input data can be avoided. This eliminates the use

of the background run to transfer application data from a BGRAPI program level

queue header to an application level queue header when the application requests

the data.

Communications Interface for Transaction Applications (CITA)

7850 5252–018 4–3

• Raw dump analysis

This feature takes a raw dump of the COMAPI subsystem, analyzes the output,

and produces a printfile.

• TCP-STATUS

This feature provides the capability for a COMAPI application to retrieve the

information supplied by the CM_TCPSTATRQ and CP_TCPSTATRQ procedure calls.

• BSD Socket Library

This feature implements a BSD/UNIX sockets library. The library helps port socket

applications to ClearPath OS 2200 servers from other hardware platforms. The

socket functions conform to BSD, UNIX, or Winsock specifications.


The document Communications Application Program Interface (COMAPI) User's

Guide (7851 5749) is available for this product on the Unisys Product Support Web site.

4.2. Communications Interface for Transaction

Applications (CITA)

Communications Interface for Transaction Applications (CITA) enables remote devices

to access OS 2200 TIP applications. Communication between CITA and the remote

devices uses the industry standard TCP protocol. CITA can also use UDP input

datagrams to schedule transactions.

The TIP applications and CITA interact through the standard OS 2200 Message Control

Bank (MCB) interface. It uses MCB to store input and receive output messages to and

from the OS 2200 TIP programs. CITA can support multiple TIP applications at the

same time.

For communications services, CITA uses Communications Application Program

Interface, which in turn attaches to Communications Platform.

Connections between CITA and remote devices can be initiated either by the remote

device or by CITA. Connections of both types can exist simultaneously. Input can be

received and output can be sent over either type of connection.

CITA can provide the communication path for any device on the network that supports

industry standard TCP/IP protocols. These protocols are normally supported by

standard product platforms within Unisys and most other manufacturers' products.

User Authentication

The CITA user authentication feature enables the use of TIP Session Control (TSC) in a

TIP environment. TIP Session Control provides a level of security by validating the

userID and password when a session is established. With this feature, CITA provides

the interface to the Exec that is needed for the validation of the userID and password.


The document Communication Interface for Transaction Applications Configuration

and Operations Guide (7862 6470) is available for this product on the Unisys Product Support Web site.

Communications Platform (CPComm)

4–4 7850 5252–018

4.3. Communications Platform (CPComm)

Communications Platform (formerly called Cooperative Processing Communications

Platform or CPComm) is high-performance system communications control software.

Communications Platform is the OS 2200 communications control component. It

connects OS 2200 application programs to end users and peer applications through

TCP/IP networks, including the global Internet.

The key attributes of Communications Platform are:

• High performance

The ability to handle gigabit network input and output

• Efficiency

Reduced path length and processor use

• Large capacity

The ability to support many thousands of users

• Openness

Support of industry-standard protocols and media

• Security

The ability to secure your network communications

• Ease-of-use

Simple installation and administration

Communications Platform provides basic mode and new programming environment

(NPE) user interfaces including TCP, UDP, ICMP, Multicast, Telnet, DNR, SSL/TLS,

SNMP, and TP0/TCP interfaces.

Communications Platform can take advantage of the queuing architecture of newer

OS 2200 systems, which enables faster throughput, especially for high-volume

applications.

Features in Communications Platform

Communications Platform communicates with networks by means of network

interface cards (NICs) attached to a PCIOP. The PCIOP is a system bus attached to a

PCI bus adapter. Communications Platform supports the use of Ethernet and FDDI

NICs. The interface between Communications Platform and the PCIOP is the same as

that between Communications Platform and the NIOP on older machines.

Communications Platform supports the industry standard network data protection

protocols Secure Socket Layer (SSL) and Transport Layer Security (TLS) that provide

peer authentication and data encryption. The applications that use Communications

Platform can take advantage of SSL/TLS for TCP/IP and OSI TP0 protocols.

Communications Platform for Open Systems (CPCommOS)

7850 5252–018 4–5

Communications Platform supports both the IPv4 and IPv6 protocols. The IPv6

protocol allows for an increased address space over the IPv4 protocol, as well as

performance improvements and increased flexibility. For many existing IPv4

applications, the Communications Platform implementation of the IPv6 protocol allows

the applications to take advantage of the IPv6 network with no changes.

Link Layer Services on Servers

Communications Platform supports connections to Ethernet, Gigabit Ethernet, and

FDDI networks through Network Interface Cards (NIC) attached to a PCIOP.



Support Web site:

• Communications Platform Programming Reference Manual (7844 8446)

• Communications Platform Configuration and Operations Guide (7844 8438)

4.4. Communications Platform for Open Systems

(CPCommOS)

The Communications Platform for Open Systems (CPCommOS) runs on SAIL-based

systems, OS 2200 environments on Intel platforms. Communications Platform for

Open Systems provides access to the network for OS 2200. Communications Platform

for Open Systems is an adapted version of the Communications Platform product that

has been modified to use the Linux Sockets Application Programming Interface.

Communications Platform for Open Systems connects application programs with

terminals, workstations, and other applications in a data communications network. The

Communications Platform for Open Systems software package provides the following

key attributes:

• High reliability

• High throughput

• Low latency

• Support of open communications standards

• Security

• Ease of administration

Applications can use Communications Platform for Open Systems to connect to

TCP/IP-based Ethernet networks. The network can contain Unisys hardware and

software, as well as hardware and software products from various vendors that

conform to open systems standards.

Communications Platform for Open Systems (CPCommOS)

4–6 7850 5252–018

There are two major components required to support communications in an OS 2200

environment:

• Communications Platform for Open Systems, executing in the OS 2200

environment

• Extended NIOP (XNIOP), a shared object executing in the Linux environment

Communications Platform for Open Systems uses the Linux Sockets API; it also uses

the communication transport layer, network layer, link layer, device drivers, and NICs

supported by Linux. Consequently, there are no transport, network, or link layers in

Communications Platform for Open Systems like there are in Communications

Platform.

In addition to Communications Platform for Open Systems, which executes in the

OS 2200 environment, there is a component called Extended NIOP (XNIOP) that

executes as a shared object in the Linux environment and makes the socket calls.

Communications Platform for Open Systems uses the NIOP architecture to pass

messages between the OS 2200 and the Extended NIOP. The Extended NIOP shared

object makes socket calls on behalf of Communications Platform for Open Systems.

Although Linux supports a variety of transport and network protocols,

Communications Platform for Open Systems supports only the AF_INET address

family, TCP/IP version 4 and TCP/IP version 6 protocol stacks.

Communications Platform for Open Systems supports the industry standard network

data protection protocols Secure Socket Layer (SSL) and Transport Layer Security

(TLS) that provide peer authentication and data encryption. The applications that use

Communications Platform for Open Systems can take advantage of SSL/TLS for TCP/IP

and OSI TP0 protocols.



Support Web site:

• Communications Platform for Open Systems Configuration and Operations

Guide (3850 8032)

• Communications Platform for Open Systems Programming Reference Manual

(3839 3971)

Cryptographic Library (CryptoLib)

7850 5252–018 4–7

4.5. Cryptographic Library (CryptoLib)

Cryptographic Library (CryptoLib) is an OS 2200 system library containing

cryptographic software that has been certified to the Federal Information Processing

Standards (FIPS) 140-2 standard. Other OS 2200 software program can use the

software contained in this library. The library is currently restricted for use by Unisys

system software only.

CryptoLib is required for generation and execution of Communications Platform

(CPComm) level 6R1 and above.

Current FIPS 140-2 approved and tested algorithm types include symmetric encryption,

asymmetric encryption, message digest, and authentication. CryptoLib includes

approved and non-approved algorithms of each type. Refer to the Cryptographic

Library User’s Guide (3850 6762) for more information.


The document Cryptographic Library User’s Guide (3850 6762) is available for this


4.6. Distributed Data Processing File and Job Transfer (DDP-FJT)

Distributed Data Processing File and Job Transfer (DDP-FJT) can be used to administer

files, programs, print files and tape files in a distributed data processing network.

Distributed Data Processing File and Job Transfer (DDP-FJT) is an OS 2200 Series

software product that controls the movement of files and jobs through a distributed

data processing network.

DDP-FJT provides a number of services, including the following:

• File Transfer Services

Enable user programs or terminal operators to create, copy, and purge files on any

system in the network.

• Job Transfer Services

Enable user programs or terminal operators to submit runstreams for execution

on other servers in the network and send the output to a specified server in the

network, to interrogate job and command status, and to cancel backlogged or

previously submitted jobs.

• Print Server Services

Enable print files to be transferred between OS 2200 servers configured in the

DDP network for subsequent printing.

• Tape-to-tape transfer

Enables the transfer of tape files from one OS 2200 system to another.

Distributed Data Processing File and Job Transfer (DDP-FJT)

4–8 7850 5252–018

DDP-FJT file and job transfer services can be used through the following four

interfaces:

• IPF

A command-oriented interface that uses Interactive Processing Facility services

• Menu

A full-screen interface that uses Display Processing System services

• Program-callable

Programs developed with the ASCII COBOL Compiler or the COBOL Compiler that

call file and job transfer functions

• Batch

Executive control language (ECL) runstreams containing DDP-FJT commands

In addition to the file and job transfer commands, DDP-FJT provides a tape transfer

capability. The tape transfer processor, TXFR, is used to initiate a tape-to-tape transfer

between OS 2200 servers. TXFR has both full-screen and line-oriented user interfaces.



Support Web site:

• DDP-FJT Implementation and Administration Guide (3787 3544)

• DDP-FJT Menu Interface Operations Guide (3787 3569)

• DDP-PPC/DDP-FJT DCA Interface COBOL Programming Guide (3787 3510)

• DDP-PPC/DDP-FJT Messages Reference Manual (3787 3528)

• OSI FTAM/DDP-FJT Print and Tape Transfer Facilities Implementation and

Operations Guide (3788 9920)

• DDP-FJT IPf and Batch Interface Operations Guide (3787 3551)

Distributed Data Processing Program-to-Program Communications (DDP-PPC)

7850 5252–018 4–9

4.7. Distributed Data Processing Program-to-Program Communications

(DDP-PPC)

Distributed Data Processing Program-to-Program Communications (DDP-PPC) forms

the basis for communication and operation among servers in a distributed data

processing environment. Software programs use DDP-PPC to transfer data through a

network, to communicate with similar peer programs on the same system or other

systems, to access files, to send and receive electronic mail, and to execute programs

on other computers in the network.

The Distributed Data Processing Program-to-Program Communications (DDP-PPC) is

an OS 2200 Series software product that provides distributed data processing

capabilities.

DDP-PPC provides a distributed processing capability that connects system hosts into

Transmission Control Protocol/Internet Protocol (TCP/IP) networks. The network can

consist of Unisys or non-Unisys hosts that support Transmission Control

Protocol/Internet Protocol (TCP/IP) protocols. DDP-PPC supports IPv6 for DCA and OSI

applications when executed with CPComm levels that support IPv6.

A program can use DDP-PPC to communicate with similar peer programs on the same

system or other systems in the network. An OS 2200 software product can use

DDP-PPC to access files, send and receive electronic mail, and execute programs on

other computer systems in the network. A DDP-PPC user is a program or an OS 2200

software product that uses DDP-PPC to transfer data through a network.

A DDP-PPC network consists of two or more computer systems (called hosts) that are

connected electronically by data communication lines or devices. This enables each

host in the network to access the facilities of other hosts in the network. Each host in

a network can also function independently while remaining connected to other hosts

in the network.

DDP-PPC provides upper-layer services that other products use to distribute their

applications across the network. These same services are available for user-written

applications through an interface called program-to-program communications. This

interface enables user programs executing in batch, demand, or transaction

processing (TIP) mode to communicate with others across the network.

DDP-PPC functions also enable programs to

• Initiate or terminate a conversation and confirm a termination request

• Send or receive messages

• Replace a calling program

• Send an unsolicited response

• Release all DDP-PPC resources

FTP Services for ClearPath OS 2200

4–10 7850 5252–018

DDP-PPC provides several common services that can be accessed by other distributed

products. As a result, there is a common and centralized user interface for this

capability for all the products, which includes log and trace (recording and processing

diagnostic information) and configuration (recording and maintaining configuration

information).



Support Web site:


Implementation and Administration Guide (3787 3270)


OSI Interface C Language Programming Guide (3787 3288)

• Distributed Data Processing (DDP-PPC) OSI Interface COBOL Programming

Guide (3787 3296)

• Distributed Data Processing (DDP-PPC) DCA Interface C Language Programming

Guide (3787 3254)

• Distributed Data Processing (DDPPPC/DDP-FJT) DCA Interface COBOL


• Distributed Data Processing (DDPPPC/DDP-FJT) Messages Reference Manual

(3787 3528)

• Distributed Data Processing (DDP-PPC) TCP/IP Interface C Language


• Distributed Data Processing (DDP-PPC) TCP/IP Interface COBOL Programming

Guide (3789 6651)

• Distributed Data Processing (DDP-PPC) TCP/IP Interface FORTRAN


4.8. FTP Services for ClearPath OS 2200

FTP Services for ClearPath OS 2200 (formerly called Cooperative Processing File

Transfer Protocol or cpFTP) is an implementation of the File Transfer Protocol (FTP) for

the OS 2200 environment. Computers equipped with FTP can exchange files with

other computers across a Transmission Control Protocol/Internet Protocol (TCP/IP)

network, such as the Internet, regardless of differences in their native file systems.

FTP Services for ClearPath OS 2200 is an OS 2200 Series software product that

permits the high-speed transfer of files between OS 2200 systems and other

computer systems using the TCP/IP protocols.

It provides typical FTP functions, such as the ability to copy, delete, and rename files

on either the local or the remote system. It also provides some capabilities that are

unique to the OS 2200 environment.

Message Control Bank (MCB)

7850 5252–018 4–11

A PC or terminal user can run FTP Services for ClearPath OS 2200 directly or call it with

a batch run. In addition, program interfaces enable FTP Services for ClearPath OS 2200

functions to be called by applications written in any of the supported languages, such

as COBOL Compiler, C Compiler, and FORTRAN Compiler.


The document FTP Services for ClearPath OS 2200 User's Guide (7847 5753) is


4.9. Message Control Bank (MCB)

Message Control Bank (MCB) is the message control component of the OS 2200

Integrated Recovery system. MCB provides support for messages passed between

programs and for messages that are input from, or output to, a communications

network.

MCB is the message control component of the OS 2200 Integrated Recovery system.

MCB, used primarily in a transaction processing environment, provides support for

messages passed between programs and messages that are input from, or output to,

a communications network.

MCB is an alternative to the original communications message-buffer pool

(COMPOOL) component of the OS 2200 Exec, providing additional functions,

particularly in message recovery. In combination with related software in the System

Interface for Legacy Application Systems (SILAS) and the OS 2200 (Exec) system, MCB

supports the following message types:

• Communications network input messages

• Communications network output messages

• Internally generated program pass-off messages

• Checkpoint messages (not communications)

Transaction programs or programs connected with transaction processing (TIP) batch

or demand programs can receive input or pass-off messages, or create output or

pass-off messages. Application programs interface to the MCB through one of the

following:

• A low-level, packet-driven interface

• The Display Processing System

• A TIP primitive interface compatible with COMPOOL

• MCB supports a number of message processing activities:

• Message staging

Holds message text in main storage buffers or in message retention files on mass

storage.

• Message auditing

Enables optional logging of message traffic on a magnetic tape or mass storage

audit trail for recovery, statistical, and accounting purposes.

Messaging Integration Services for ClearPath OS 2200

4–12 7850 5252–018

• Message queuing

Gives priority sequencing to control information for orderly delivery of input and

pass-off messages to application programs and delivery of output to the network

through SILAS.

• Message recovery

Automatically requeues recoverable undelivered input, output, and pass-off

messages after system failure.

• Message recall

Recalls successfully delivered input or output from a message retention file.



Support Web site:

• Message Control Bank (MCB) Programming Reference Manual (7833 1568)

• Message Control Bank (MCB) Administration and Operations Guide (7833 1550)

4.10. Messaging Integration Services for ClearPath

OS 2200

Messaging Integration Services for ClearPath OS 2200 is a low-level, message-based

interface between programs running on the OS 2200 and Windows systems.

Message Integration Services enables application developers to develop applications

that span both OS 2200 (TIP/HVTIP) and Windows environment.

Messaging Integration Services is an infrastructure designed to support a number of

Windows interfaces and applications provided by Unisys or written by a customer.

Messaging Integration Services provides OS 2200 access to Windows applications as

long as those Windows applications have a client API or a COM/COM+ interface.

Messaging Integration Services supplies a development environment to assist

developers in writing their own applications.

Solutions Supplied by Unisys

Unisys supplies the following solutions built on Messaging Integration Services:

• Provides an interface to Microsoft Message Queuing. Refer to Section 3.5,

“ClearPath OS 2200 Interface to Microsoft Message Queuing,” for information on

message queuing.

Messaging Integration Services for ClearPath OS 2200

7850 5252–018 4–13

• If User Authentication is installed on your ClearPath Enterprise Server, the

Network Authentication feature can be used to authenticate $$OPEN TIP and

demand users. Unisys-supplied agent/adapter pairs use the Windows Security

Domain model instead of the local OS 2200 security database to authenticate

users. Network Authentication supports userID/password credentials in addition

to Windows NT LAN Manager (NTLM) tickets and Windows Kerberos tokens.

Authentications using NTLM or Kerberos also require a UTS terminal emulator that

supports these authentication types. LDAP userID/password authentication is also

supported and requires an LDAP server. OS 2200 user authorization decisions,

after authentication has passed, are still done by local OS 2200 Exec security.

How Messaging Integration Services Works

Messaging Integration Services connects service requesters called agents from a

demand, batch, or transaction program to Windows service providers called adapters.

Unisys provides adapters along with paired application interfaces (API) that enable

applications on the OS 2200 node to access applications and services that operate on

Windows.

Application Interfaces and Call Sequences

Messaging Integration Services functions on the OS 2200 system to support

synchronous service requests. For each programming language compiler supported,

there is an associated language library.

ASCII COBOL Compiler is also supported by using a mixed mode gate, which enables

a basic mode bank to call the APIs.

On the Windows system there are adapter APIs that support C and Visual Basic

programs. Messaging Integration Services provides

• A C++ class with methods for adapters that match and extend the C APIs

• A Microsoft Developer Studio class Wizard to assist in building your adapter

project


The manual Messaging Integration Services for ClearPath OS 2200 Help

(Self-extracting help file) (7851 5558) is available for this product on the Unisys Product Support Web site.

System Interface for Legacy Application Systems (SILAS)

4–14 7850 5252–018

4.11. System Interface for Legacy Application

Systems (SILAS)

System Interface for Legacy Application Systems (SILAS) provides an interface

between Communications Platform and the traditional transaction processing (TIP) and

demand environments. It enables an enterprise to migrate to Communications

Platform without impacting applications in these key existing environments.

SILAS supports both UTS emulation and Telnet clients. This level of support enables

existing terminal-sensitive applications to continue to operate when network support

is migrated to Communications Platform.

SILAS and Communications Platform

System Interface for Legacy Application Systems supports the traditional transaction

processing (TIP) and interactive demand processing using Communications Platform.

The Communications Platform application program interface (API) provides access to

the Communications Platform's TCP/IP and RFC 1006 protocol stacks.

System Interface for Legacy Application Systems plays an important role in this

high-performance communications alternative. It performs the following functions:

• Access to TIP, including Business Information Server, for COMPOOL and MCB

applications

• Access to the remote symbiont interface (RSI) complex and its interactive

(demand) processing

• System console and remote administrator access to Communications Platform

through a demand run

System Interface for Legacy Application Systems uses the services of

Communications Platform through Communications Platform's API to access the RFC

1006 TP0 and Telnet interfaces for its transport connections. SILAS supports both IPv4

and IPv6 Internet addresses. SILAS can also be configured by Communications

Platform to impose security.

The following figure shows the relationship between System Interface for Legacy

Application Systems and Communications Platform.

TCP/IP Application Services (TAS)

7850 5252–018 4–15

System Interface for Legacy Application Systems

System Interface for Legacy Application Systems uses both COMPOOL and Message

Control Bank (MCB) for TIP message handling and other TIP services. System Interface

for Legacy Application Systems supports the INT1 and DTPX protocols using the RFC

1006 TP0 protocol stack, and also supports the Telnet protocol stack.


The document System Interface for Legacy Application Systems (SILAS)

Configuration and Operations Guide (7851 5475) is available for this product on the Unisys Product Support Web site.

4.12. TCP/IP Application Services (TAS)

TCP/IP Application Services (TAS) is a software product that enables a ClearPath

enterprise server to communicate with other hosts in a network using the

Transmission Control Protocol/Internet Protocol (TCP/IP) protocols.

TCP/IP Application Services (TAS) is an OS 2200 Series system software product that

enables communication between hosts. This communication can take place using an

X.25 Public Data Network (PDN) or a Local Area Network (LAN) using the Transmission

Control Protocol/Internet Protocol (TCP/IP).

TAS components provide inter-server processing that can be homogeneous (between

OS 2200 hosts) or heterogeneous (between an OS 2200 host and a non-OS 2200 host).

TCP/IP Application Services (TAS)

4–16 7850 5252–018

TAS consists of the following components:

• TAS File Transfer Facility

Provides file transfer capabilities, based on the File Transfer Protocol (DDN,

MIL-STD-1780)

• TAS Mail Processor

Provides electronic mail processing capabilities, based on the Simple Mail Transfer

Protocol (DDN, MIL-STD-1781)

• TAS FORTRAN Programming Interface

Provides facilities for writing FORTRAN applications programs

• TAS C Language Programming Interface

Provides facilities for writing C Language applications programs

• TAS COBOL Programming Interface

Provides facilities for writing COBOL applications programs that invoke the TAS

File Transfer Facility or Mail Processor



Support Web site:

• TCP/IP Application Services (TAS) C Language Programming Guide (4173 5135)

• TCP/IP Application Services (TAS) FORTRAN Programming Guide (3787 3247)

• TCP/IP Application Services (TAS) Implementation and Administration Guide

(3787 3221)

• TCP/IP Application Services (TAS) File Transfer User Guide (3787 3213)

• TCP/IP Application Services (TAS) COBOL Programming Guide (3787 3205)

• TCP/IP Application Services (TAS) Mail Processor User Guide (3787 3239)

7850 5252–018 5–1

Section 5 Database Management Products

Enterprise servers systems support an integrated family of software products that

address the entire spectrum of data management needs, including data definition,

control, reporting, and maintenance. Enterprise server systems support three different

database management systems that are based on three different database models. All

three database management systems use a common data engine. The database

management environment includes a variety of advanced utilities for database

definition, data retrieval, data manipulation, and system operations. These products

offer both menu and command driven interfaces and facilitate the data management

tasks of both occasional and expert users. An appropriate selection of database

management products can be configured according to your specific data management

requirements.


• ClearPath Database Extensions for PHP

• Database Inquiry

• Define File Processor

• Network Database Server

• ODBC Access for ClearPath OS 2200

• Processor Common Input/Output System (PCIOS)

• Relational Database Server

• Repository for ClearPath OS 2200

• Shared File System (SFS)

• UniAccess for OS 2200 Systems

• Universal Database Control

ClearPath Database Extensions for PHP

5–2 7850 5252–018

5.1. ClearPath Database Extensions for PHP

PHP is a language widely used for Web application development. The ClearPath

Database Extensions for PHP is tested and supported on ClearPath JProcessor as well

as other deployment environments. The ClearPath Database Extensions for PHP is a

rapid application development environment that enables PHP Web applications to

access the Relational Database Server for ClearPath OS 2200 (RDMS).

The ClearPath Database Extensions for PHP is available to PHP Web applications

deployed in the Quercus environment, which is a PHP interpreter written in Java. The

Quercus environment runs in an application server, such as JBoss® Enterprise

Application Platform (JBoss EAP) and Tomcat. The database extension is available only

to PHP Web applications, and not to command-line applications. An end-user can

access a PHP application similar to a Java Web application.

The ClearPath Database Extensions for PHP is modeled after the MySQLi extension.



Support Web site:

• ClearPath Database Extensions for PHP Installation and Configuration Guide (3850

7398)

• ClearPath Database Extensions for PHP User’s Guide (3850 7406)

5.2. Database Inquiry

Database Inquiry (formerly called Query Language Processor or QLP) can select,

retrieve, update, and display or print information stored in

• Network Database Server for ClearPath OS 2200 database

• Processor Common Input/Output System (PCIOS) data files

• Relational Database Server for ClearPath OS 2200 database (on a limited basis)

Database Inquiry is a conversational, English-oriented processor that enables access

to and updating of a Network Database Server database. It also provides the existing

report definition and generation capabilities for Relational Database Server data and

includes a separately packaged feature that provides most Database Inquiry functions

for selected PCIOS files.

Database Inquiry includes global commands, report statements, procedures, requests,

and macros to

• Manipulate selected data

• Specify report formats

• Group and process report generation calls

• Define, store, and call command sequences

Define File Processor

7850 5252–018 5–3

• Expand user commands into Database Inquiry commands

• Manipulate previously saved reports, procedures, macros, formats, and requests

Separately Packaged Feature: FDP/ADP

The File Definition Processor/Application Definition Processor (FDP/ADP) enables

Database Inquiry to access selected PCIOS files.

• The FDP defines the PCIOS files and their attributes.

• The ADP binds a set of these files into one common application view.

With FDP/ADP, some Database Inquiry functions can be used with PCIOS MSAM files,

as well as with SSDF tape files and mass disk files.



Support Web site:

• Query Language Processor (QLP 2200) End Use Guide

− Volume 1: Basic Commands (7830 7493)

− Volume 2: Advanced Commands (7830 7485)

• Query Language Processor (QLP 2200) Configuration Guide (7833 4851)

• Query Language Processor (QLP 2200) File and Application Definition

Processors Administration and Programming Guide (7833 0974)

5.3. Define File Processor

Define File Processor (DFP) is a stand-alone processor that creates file information

used by Processor Common Input/Output System (PCIOS) and Shared File System.

Applications programmers use Define File Processor to produce a data file description

that is external to the programs processing the file and to provide header label

information for a tape file.

Define File Processor produces a define file block containing the data file description

and enters that block as an element in a program file. A user program processing the

data file makes implicit references to this program file. When a program opens the

data file, the language processor reads the define file block from the program file. The

information from the define file block is used to modify the program’s original data file

description. All this activity is transparent to the user.

You can use define file blocks to perform the following tasks:

• Provide data file descriptions when the language you are using has no data file

description mechanism.

• Override data file descriptions specified within the program source language.

Network Database Server

5–4 7850 5252–018

• Specify data file descriptions for elements of a partitioned data file.

A partitioned data file is actually a program file. Each element of the partitioned

data file is a symbolic element of the program file. (Therefore, File Utility

Routine/Program-file Utility Routine (FURPUR) commands can be used to

manipulate the file or its elements.) A partitioned data file can also contain

absolute and relocatable elements, but these elements cannot be processed as

partitioned data file elements.

Data elements of a partitioned data file are restricted to system data format (SDF)

sequential format.

To refer to a partitioned data file element, use element/version-name on the

Define File Processor call statement.

• Concatenate data files.

You can concatenate data files by linking their define file blocks. When a program

opens a file, the language processor checks the concatenation field of the define

file block. This field contains the file and element name for the next define file

block in the concatenation sequence. If the value in the concatenation field is

nonzero, the current file is concatenated with the specified file. If the value is zero,

concatenation stops. When the language processor encounters an end of file, it

automatically closes the current file and opens the next file. You can concatenate

only sequential files and read only in the forward direction.

• Specify header label information for an ANSI tape file.


The document Define File Processor (DFP) Administration and Programming

Reference Manual (7830 7816) is available for this product on the Unisys Product Support Web site.

5.4. Network Database Server

Network Database Server for ClearPath OS 2200 (formerly called Data Management

System or DMS) is a data manager that organizes data according to the network

database model. Network Database Server includes software components that create

the database structures, programming languages that enable access to data in the

database, and utilities that can maintain, restructure, or reorganize the database.

Network Database Server is part of the Universal Data System (UDS), a suite of data

management software components and products that form an integrated

environment for control, maintenance, and recovery of user databases.

Network Database Server is a logical data manager based on the specifications

recommended by the CODASYL committees for network database processing.

Network Database Server includes a variety of database storage structures, high-level

language interfaces, and a selection of accessing techniques, as well as several levels

of database recovery and security.

One of the characteristics of the CODASYL model is a strict separation of data

definition from data manipulation. The database administrator is responsible for data

definition: designing, monitoring, and tailoring the database. The applications

programmer is responsible for data manipulation: storing, retrieving, modifying, and

deleting data in the database.


7850 5252–018 5–5

Database Definition

The database administrator first defines the database through a schema. The schema

describes the database both physically and logically.

The physical description specifies the

• Size and organization of every file in the database

• Types of records in the database

• Characteristics of the data each record contains

The logical description specifies

• Relationships among record types, which are called set types

• Ownership, membership, linkages, and other rules for set definition and usage

The database administrator writes a source schema with COBOL-like Data Definition

Language (DDL) statements. The DDL processor then translates the source schema

into an absolute schema, which contains tables that the Network Database Server run-

time routine (the Data Management Routine, or DMR) uses to fulfill data requests.

The database administrator also defines subsets of the schema, that is, logical views

of the database. These subsets are called subschemas.

The Subschema Data Definition Language processor (SDDL) translates the source

subschema into an absolute subschema. The subschema contains tables that the

Network Database Server runtime routine accesses.

Data Manipulation

Programmers write DML applications to store, retrieve, modify, and delete the data in

a database. These programs manipulate the database through a named subschema

that defines the portion of the database available to the program.


5–6 7850 5252–018

The applications programmer embeds Data Manipulation Language (DML) statements

in one of the host language programs (ASCII COBOL Compiler, UCS COBOL Compiler,

ASCII FORTRAN Compiler, or UCS FORTRAN Compiler) to manipulate database files

defined in the subschema.

Network Database Adapter (DMS-RA), which is a standards-based Java interface. The

DMS-RA gives access to network databases from stand-alone Java applications and

Java 2 Platform, Java Enterprise Edition (JEE) application components such as

Enterprise JavaBeans (EJB) and Java Servlets. Server databases can also be accessed

by the Network Database Server Resource.



Support Web site:

• Enterprise Network Database Server for ClearPath OS 2200 Administration and

Support Guide (7830 7568)

• Enterprise Network Database Server COBOL Data Manipulation Language

Operations and Programming Reference Manual (7830 7576)

• Data Management System (DMS 2200) FORTRAN Data Manipulation Language

(FDML) Operations and Programming Reference Manual (7830 7584)

• Data Management System (DMS 2200) Schema Data Definition Language (DDL)

Administration, Operations, and Programming Guide (7831 0745)

• Enterprise Network Database Server for ClearPath OS 2200 Subschema Data

Definition Language Administration, Operations, and Programming Guide

(7831 0752)

• Network Database Server Resource Adapter for the JavaTM Platform User Guide

(3850 8362)

ODBC Access for ClearPath OS 2200

7850 5252–018 5–7

5.5. ODBC Access for ClearPath OS 2200

ODBC Access for ClearPath OS 2200 (formerly called INFOAccess) is middleware that

provides SQL and ODBC access to Enterprise Network Database Server for ClearPath

OS 2200 databases. It links Windows-based tools and applications with the data

stored in Network Database Server databases.

ODBC Access for ClearPath OS 2200 provides access to Unisys proprietary databases

from

• Windows-based tools and applications (PowerViewer, Microsoft Access, Visual

Basic, Forest & Trees, Crystal Reports, and so on)

• Web servers

• Data integration gateways (Attunity Connect (formerly called ISG Navigator),

Microsoft SQL Server 7.0, Oracle8i Generic Connectivity Services, and so on)

General Features

ODBC Access for ClearPath OS 2200 provides the following features and benefits:

• Rapid conversion of data into useful information

End users, business managers, and workgroups are empowered by the availability

of hundreds of graphical user interface (GUI) based desktop query, reporting, and

decision support tools that provide ad hoc access to enterprise data using the

Microsoft standard ODBC interface. Qualified tools include, among others,

PowerViewer, Visual Basic, and Crystal Reports.

• Rapid, lower-cost application building

Access existing information through SQL (the industry standard relational database

language) without the need to develop special programs in the legacy database

languages such as the COBOL Data Manipulation Language (CDML) or FORTRAN

Data Manipulation Language (FDML). Using SQL results in less programming,

which can significantly reduce your application backlog.

• Use your existing data resources without reengineering applications and

databases

With ODBC Access, you can develop business applications (decision support

systems, executive information systems, and management support systems,

publish Network Database Server data on the Web), while fully leveraging data

collected over the years. You can accomplish any desired reengineering at your

own pace, thus saving time and money.

• Interoperability with non-Unisys databases in the enterprise

Using products, such as ISG Navigator, Unisys and non-Unisys databases can be

seamlessly integrated, providing data location transparency to applications and

end users.

ODBC Access for ClearPath OS 2200

5–8 7850 5252–018

Components

ODBC Access for ClearPath OS 2200 systems consists of the following family of

software components:

• The Data Access Storage Server resides in the OS 2200 environment. It provides

access to the Network Database Server for ClearPath OS 2200.

• The Data Access Sockets Subsystem resides in the OS 2200 environment. It is a

standard sockets interface that is used to communicate between the Data Access

Storage Server and the Data Access SQL Server. It interfaces to Communications

Management System (CMS) or Communications Platform (formerly called

Cooperative Processing Communications Platform or CPComm).

• The Data Access SQL Server resides on a Windows Server. It performs all

necessary SQL processing and transformations between the network database

model and the relational database model.

• The Data Access Administrator resides on any Windows NT platform (including

Windows 2000). It provides remote administration of a Data Access server

environment and remote browsing of relational database definitions that were

mapped from Network Database Server definitions.

• The Data Access Modeller resides on any Windows platform except Windows CE.

It permits the easy transformation of network database definitions into relational

definitions for use by the Data Access SQL Server and provides the information

that permits the Data Access Storage Server to efficiently use the unique Network

Database Server access mechanisms.

• The ODBC Access Driver resides on any Windows platform except Windows CE.

It provides access to the Network Database Server from any ODBC compliant

application.



Support Web site:

• ODBC Access for ClearPath OS 2200 Administrator User's Guide (7862 5746)

• ODBC Access for ClearPath OS 2200 Installation and Operations Guide (7862

5753)

• ODBC Access Interactive SQL (ISQL) Reference Manual (8807 9322)

• ODBC Access Modeller User's Guide (7862 2354)

• ODBC Access SQL Reference Manual (8807 9330)

• ODBC Access Stored Procedures User's Guide (6885 2664)

Processor Common Input/Output System

7850 5252–018 5–9

5.6. Processor Common Input/Output System

Processor Common Input/Output System (PCIOS) is a basic data management system

that supports handling of files that are used by different programming language

processors. Using PCIOS, files written by an application developed in one

programming language can be read and updated by applications developed in other

languages.

The same data files can be used when writing programs using the ASCII COBOL

Compiler, ASCII FORTRAN Compiler, Information Management System, Database

Inquiry, Sort/Merge, C Compiler, COBOL Compiler, and FORTRAN Compiler.

Common Input/Output Modules

PCIOS consists of a series of common input/output modules (CIOM) that can be used

as relocatable subroutines or as reentrant common banks on an OS 2200 Executive

system. Each CIOM is responsible for the file format and reference functions (OPEN,

CLOSE, READ, WRITE, and so on) for one file type. There is one CIOM for each of the

physical data files defined for processing by PCIOS and also one for error processing.

All CIOMs are quarter-word sensitive. The CIOMs are as follows:

• C2SSDF Sequential system data format (SSDF) I/O module

SSDF files have no keys. They are read sequentially.

• C2DSDF Direct system data format (DSDF) I/O module

DSDF files have ordinal keys (record number) associated with specific addresses

on the file.

• C2ANSI American National Standards Institute (ANSI) tape I/O module

ANSI tape files can be created on one computer system and read on other

systems. For instance, they can be created on a DEC system and read on a Unisys

system.

• C2ERR Error processing for C2SSDF, C2DSDF, C2ANSI, and C2COMP.

• C2MSAM Multi-indexed sequential access method (MSAM) I/O module

MSAM files can have multiple keys.

• C2COMP IBM-compatible tape I/O module

The IBM-compatible tape module can process standard IBM-formatted tapes.

Relational Database Server

5–10 7850 5252–018

General Features

PCIOS works in conjunction with the Define File Processor (DFP), Database Inquiry, and

Shared File System. It enables

• File attributes to be specified using the stand-alone preprocessor DFP.

• Database Inquiry functions for selected PCIOS file formats are available through

PCIOS.

• Processing of some files with formats produced by PCIOS to be processed by the

Shared File System, and vice versa. Unlike the Shared File System, however,

PCIOS is not designed to enable processing of one file by several programs

simultaneously.

• Record termination character sequence identification


The document Processor Common Input/Output System (PCIOS) Administration and

Programming Reference Manual (7831 0588) is available for this product on the Unisys Product Support Web site.

5.7. Relational Database Server

Relational Database Server for ClearPath OS 2200 (formerly called Relational Data

Management System or RDMS 2200) is a database management system. It supports a

high volume of transactions against large relational databases. Relational Database

Server provides

• Continuous operation

• Data security, data recovery, large-scale database management, and support for

thousands of active users

• Interoperability with databases from other vendors and with databases that reside

on different platforms

• Ability to operate in a multiprocessor, clustered environment

Architecture

Relational Database Server is part of the Universal Data System (UDS), a suite of data

management software that forms an integrated environment for the control,

maintenance, and recovery of user databases.

Relational Database Server is one of the data models within UDS. UDS provides

services such as session control (commit and rollback), caching, and locking. UDS and

the OS 2200 Integrated Recovery mechanism automate database and message

recovery with minimal operator or administrator intervention.


7850 5252–018 5–11

Relational Database Server architecture includes an active data dictionary. The active

data dictionary is a combination of a relational catalog, a configuration control system,

and a cross referencing system. This active data dictionary keeps track of all schema

changes, configuration changes, and application changes.

SQL Standard Compliance

Relational Database Server incorporates the industry-standard Structured Query

Language (SQL) for data definition and manipulation. The National Institute of

Standards and Technology (NIST) has validated the Relational Database Server for

conformance to the FIPS 127-2 entry level, which corresponds to the entry level of the

SQL 92 standard. The Relational Database Server also contains many features from

recent versions of the standard.

Enterprise Server Attributes

The following are the enterprise server attributes:

• Availability

The Relational Database Server is designed to be available 24 hours a day, 7 days a

week, 365 days a year. To ensure continuous operation and predictable

performance, the Relational Database Server dynamically balances the database

storage structures. This means that production does not stop to reorganize a

growing database. Other features of the Relational Database Server, such as the

active data dictionary, database event logging, software partitions, and online

dynamic schema modifications, all contribute to its continuous operation

capabilities.

• Integration

The Relational Database Server, integrating with the OS 2200 operating system,

recovers transactions and messages at the same time so that you never miss a

message coming from the transaction when the transaction is committed.


5–12 7850 5252–018

• Security

The Relational Database Server employs five types of security

− System

− File

− Table

− View

− Role

• These security types control access to the hardware and software, database files,

tables in the database, and rows and columns within the tables. Relational

Database Server also supports data encryption for the safe transmission of

sensitive information.

• Scalability

The Relational Database Server handles applications and data that continually

increase in size, complexity, and volume.

• Recoverability

The recovery capabilities of the Relational Database Server include static, dynamic,

and incremental database backups, online partial file or database recovery, and

automatic restart of recovery scripts and programs whenever the operating

system restarts. In a distributed environment, the automatic recovery feature of

the Relational Database Server coordinates the recovery to a point in time among

all the hosts.

• Resiliency

The Relational Database Server takes advantage of the extended processing

architecture available for ClearPath servers. This architecture increases the

capacity of the system and provides built-in hardware and software redundancy.

Language Support

Access to the Relational Database Server is integrated into many third and fourth

generation languages, including

• COBOL, C, and FORTRAN through a program-callable interface

• COBOL and C through SQL statements embedded in the program

• Business Information Server through the MAPPER Relational Interface (MRI)

• Enterprise Application Development through the generated COBOL language

statements

Interoperability

Relational Database Server data is accessible from other platforms through Java,

Enterprise Java Beans, Tuxedo distributed transactions, Open Database Connectivity

(ODBC), Java Database Connectivity (JDBC), ActiveX Data Objects (ADO), and other

technologies.

Repository for ClearPath OS 2200

7850 5252–018 5–13

The UniAccess ODBC Server of Relational Database Server enables an enterprise to

use a variety of ODBC-compliant, Windows-based tools to access Relational Database

Server databases without any programming on the client or server. Many ODBC-

compliant tools, such as Microsoft Access, Microsoft Query, Microsoft Excel,

PowerBuilder, and so on, have been qualified for use with the UniAccess ODBC

Server.

Relational Enterprise Data is also available through the Web using languages such as

Microsoft Visual Basic, Visual C++, Java, and so on, and scripting languages such as

JavaScript and VBScript.

Binary Large Objects (BLOB)

Today's multimedia applications depend on storage of a variety of large data objects,

such as scanned documents, medical images, and audio messages. The Relational

Database Server provides the Binary Large Object (BLOB) data type and corresponding

RSM-Large Object format storage areas to handle large data efficiently.

A Binary Large Object is a data type whose contents and structure are defined by the

application that uses it. BLOBs can be relatively small (a couple thousand bytes) to

very large (up to 4 gigabytes). Typically, BLOBs store image data: pictures, finger

prints, scanned documents, and so on.



Support Web site:

• Relational Data Management System (RDMS 2200) and IPF SQL Interface End

Use Guide (7831 0778)

• Relational Database Server for ClearPath OS 2200 SQL Programming Reference

Manual (7830 8160)

• Relational Database Server for ClearPath OS 2200 Administration Guide

(7831 0760)

5.8. Repository for ClearPath OS 2200

Repository for ClearPath OS 2200 (formerly called Unisys Repository Manager or

UREP) organizes and manages information and resources used in your database

environment. Repository provides data dictionary functionality that tracks information

resources and repository functions that manage information for other products.

Repository is the focal point for the management of information resources. Like a data

dictionary, it can keep track of information resources. For example, Repository can

provide information about such things as the location of source code for a particular

program.


5–14 7850 5252–018

In addition to the data dictionary functions, Repository provides repository functions.

The main purpose of Repository is to organize information in one place, making it

easier to access and update.

• The repository manager stores information for other products and provides the

capability for other products to use that information.

• The repository database contains the information used in a database environment.

• The repository manager processes the information stored in the repository.

In addition, a repository system

• Enables the control of information by enforcing rules and standards regarding the

access to, and the use of, repository information to help ensure data integrity and

consistency.

• Increases accuracy and timeliness of the information it contains because the

repository is easier to update. It helps to eliminate duplicate storage, collection,

and maintenance of information, thereby reducing unnecessary program

development.

• Simplifies software and data conversion because you are using consistent

documentation.

• Provides flexibility by enabling you to customize and extend the type of data

stored to meet specific needs.

In addition to being an information resource dictionary, the Repository provides

documentation capabilities.

Repository Environment

The Repository operates in an environment that encompasses many products.


7850 5252–018 5–15

The following products work with the Repository in a number of ways:

• Universal Database Control directs and coordinates the operations of Universal

Data System (UDS) products. The Repository defines configurations and files for

Universal Database Control.

• The Relational Database Server for OS 2200 stores definitions of relational tables

and views in Repository. Repository uses the Relational Database Server as its

logical data manager to store information.

• Shared File System provides shared access to direct system data format (DSDF)

and multi-indexed sequential access method (MSAM) files. SFS uses the

Repository to define these files.

• The Network Database Server for ClearPath OS 2200 uses Repository to support

implementation of the CODASYL data model. Repository holds schema,

subschema, and area definitions.

• The C Compiler, COBOL Compiler, and FORTRAN Compiler can extract data

definitions from the Repository during compilation. The Repository generates

definitions for COBOL files and records and for C Compiler and FORTRAN

Compiler data. The Repository stores cross-reference information for all three

languages.

• Display Processing System manages forms for screen processing and provides an

interface to the Repository that enables the Repository to store Display

Processing System forms in the repository.

Repository Interfaces

The Repository enables you to work in the repository using any of the two interfaces

the Repository supports:

• The DDS command language is compatible with the Repository. You might prefer

to use DDS commands if you have used this language before and are familiar with

it. It also enables you to execute functions that the Information Resource

Dictionary System (IRDS) command language does not yet implement.

• The Repository includes a partial implementation of the IRDS command language

in the American National Standards Institute IRDS, X3.138. You might want to use

this interface if you plan to use this standard. The IRDS command language comes

as part of the basic Repository product. With this interface you can perform most

Universal Data System (UDS) functions, use the OPTIONS entity, and do

documentation.



Support Web site:

• Repository for ClearPath OS 2200 Administration Guide (7830 8087)

• Repository for ClearPath OS 2200 Programming Reference Manual (7830 8079)

Shared File System

5–16 7850 5252–018

5.9. Shared File System

Shared File System (formerly called SFS) is a collection of file access routines that

enable more than one application program to access a file at the same time. The

Shared File System provides this shared access to data files created and maintained

by application languages such as ASCII COBOL Compiler and ASCII FORTRAN

Compiler.

Shared File System is Universal Data System (UDS) data management software that

consists of a collection of file access routines. Shared File System provides shared

access to data files created and maintained by application languages such as ASCII

COBOL Compiler and ASCII FORTRAN Compiler. Shared access enables more than one

application program to access a file at the same time.

As a part of the Universal Data System (UDS) environment, it has the recovery and

locking features provided by Integrated Recovery Utility and the locking subsystem

(LSS) software components. You can access files concurrently and update the same

file at the same time without sacrificing data integrity. When a record is updated,

Shared File System calls the Universal Data System (UDS) locking subsystem to lock

the page until the updates are committed, which makes them permanent. When a

record is read, Shared File System calls LSS to lock the page. Shared File System calls

LSS to unlock the page as soon as the lock is no longer needed.

Shared File System provides a number of benefits:

• Increased throughput

Shared File System enables concurrent access by multiple programs to the same

multi-indexed sequential access method (MSAM) and direct system data format

(DSDF) files. This capability can increase processing throughput, saving time and

money.

• Data safeguarding

Shared File System uses the full recovery features of Universal Data System (UDS)

to provide recovery for MSAM and DSDF files. These features include program

rollback, short recovery, selective recovery, and long recovery.

• Data integrity

Shared File System uses the locking features of the Universal Data System (UDS)

to ensure data integrity when files are accessed by multiple users.

• Implementation of the Relative I/O Module and Indexed I/O Module section from

the American National Standard COBOL, X3.23-1985

This standard dictates rules for features such as language syntax and error codes.

Shared File System benefits users wanting concurrent access to data files. Shared file

usage increases processing throughput. Shared File System file-sharing features can

be used by applications that access MSAM or DSDF files through ASCII COBOL

Compiler, ASCII FORTRAN Compiler, Information Management System (IMS), COBOL

Compiler, FORTRAN Compiler, or C Compiler.

UniAccess for OS 2200 Systems

7850 5252–018 5–17


The document Shared File System (SFS 2200) Administration and Support Reference

Manual (7831 0786) is available for this product on the Unisys Product Support Web

site.

5.10. UniAccess for OS 2200 Systems

UniAccess for OS 2200 Systems implements Microsoft client/server architecture for

the OS 2200 system. It provides seamless integration among DBMSs, applications,

and hardware systems within a TCP/IP network environment. Application

development tools, end-user tools, database servers, Internet servers, or transaction

processing systems compatible with the Microsoft data access architecture can

interoperate through UniAccess with any data source or program on an OS 2200

system. Thus, UniAccess transforms OS 2200 systems into Microsoft enterprise

servers and enables the modernization of existing applications and databases to

client/server, intranet, or Internet applications.

UniAccess provides components to enable applications running under OS 2200 to

function as a client, or as a server. The OS 2200-based servers are UniAccess

Transaction Server and the UniAccess ODBC Server for RDMS 2200. They process

requests from PC-based ODBC clients and Open Clients as well as from UniAccess

Transaction Client. The UniAccess Transaction Client enables OS 2200 applications to

make requests of various servers, including SQL Servers and OS 2200 transactions. To

the client, the processes of the UniAccess servers appear the same as those of a SQL

Server. The processes of the Transaction Client, on the other hand, appear the same

as an Open Client application.

The UniAccess ODBC Server for RDMS 2200 provides a TIP transaction to access data

and stored procedures using the Relational Database Server. Programmers working in

the UniAccess Transaction Server environment generally write OS 2200 TIP

transactions that process client requests. A TIP transaction must be associated with

each client request to the UniAccess Transaction Server. Programmers working in the

UniAccess Transaction Client environment write the applications that make requests

of remote servers or local UniAccess servers.

The Integrated Operating Environment (IOE) software supports up to two concurrent

UniAccess Relational Server threads, up to two concurrent UniAccess Transaction

Server threads, and up to two concurrent UniAccess Transaction Client threads

(licenses are available for additional concurrent threads or an unlimited number of

concurrent threads).

Components

UniAccess ODBC driver executes on Windows platforms. It handles differences

between ODBC SQL and RDMS SQL and enables extensions to be passed through.

The ODBC driver also enables TIP transactions using the UniAccess Server-Library to

be called as if they were stored procedures. The ODBC driver has been tested with a

number of client applications, including Microsoft Access, Microsoft Excel, Microsoft

Internet Information Server, Microsoft Active X Data Objects (ADO), Visual Studio,

Visual Studio.Net, Impromptu, SQL Server Reporting Services, and Business Objects.

UniAccess for OS 2200 Systems

5–18 7850 5252–018

UniAccess ODBC Server provides ODBC access to the Relational Database Server.

This ODBC capability enables you to access Relational Database Server data using a

variety of Windows-based client tools and applications.

UniAccess Transaction Server enables ODBC-compliant and Open Client applications

to invoke new and existing Unisys TIP transactions on the OS 2200 system. Using the

Server-Library API, OS 2200 programmers can create transactions to access a variety

of OS 2200 data.

UniAccess Transaction Client provides client capabilities on the ClearPath OS 2200. It

enables Unisys mainframe-based applications remote access to Microsoft and Sybase

SQL Servers. In addition, transaction client applications can access ClearPath OS 2200

TIP transactions through the UniAccess ODBC Server for Relational Database Server

and UniAccess Transaction Server.

General Features

UniAccess provides the following features and benefits:

• Choice of tools

Because it implements both Microsoft and Sybase architectures and complies

with ODBC, UniAccess offers a choice of hundreds of application development,

end user, and off-the-shelf client and server products. These products are

available from Microsoft, Sybase, and hundreds of other industry-leading vendors,

such as IBM, Lotus, Powersoft, Business Objects, and Gupta.

• Choice of platforms

The Microsoft or Sybase architecture is available on all leading client platforms:

MS-DOS, Windows, Windows NT Workstation, Macintosh, and UnixWare. A single

client can interoperate with new or existing applications on ClearPath enterprise

servers as well as OS 2200 systems and most server environments, including IBM,

Hewlett-Packard, and Sun.

• Ease in application development

Use of ODBC-compliant tools with UniAccess offers point-and-click application

development with no additional programming necessary on client PCs or in the

OS 2200 environment.



Support Web site:

• UniAccess for OS 2200 Systems Read.Me (7850 5021)

• UniAccess for OS 2200 Systems Software Release Announcement (7847 5373)

Universal Database Control

7850 5252–018 5–19

5.11. Universal Database Control

Universal Database Control, the Universal Data System manager, provides a common

architecture and environment for the Universal Data System (UDS) product family. It

supports the three Universal Data System data models and manages all of their files.

Universal Database Control enables users to share files, controls access to those files,

and automatically and uniformly resolves conflicts over access to the files. It also

enables you to designate recoverable files, regardless of the data management

method used, and provides consistent file recovery.

Universal Database Control is one of the UDS suite of products and is packaged as

part of the kernel.

ClearPath Enterprise Servers Universal Database Control (formerly known as Universal

Data Systems Control, or UDS Control), the UDS online data manager, provides a

common architecture and environment for the three UDS data models:

• Relational Database Server for ClearPath OS 2200

• Network Database Server for ClearPath OS 2200

• Shared File System

All three types of databases can be accessed from within the same program or within

different programs executing concurrently. All programs use the same method to

commit or omit changes for all files.

General Features

Universal Database Control has the following features:

• Universal Database Control supports up to 16 application groups, which provide

for independent database environments. Universal Database Control can also be

installed into any one of the available application groups. You can manipulate data

in one application group without affecting data in other application groups.

• UDS Control handles main storage through its own cache manager banks. The UDS

memory can be used for general file paging or as page buffers for specific files.

Buffers can contain data from one file, part of a file, or several files. Users can

configure how much memory is available. UDS Control assigns all shared Exec

files to its own common name section, which improves overall system

performance and increases data security.

• A Universal Database Control thread is a sequence of commands from one user.

The user determines when the thread begins and ends, can partition the thread

into subsequences or steps, and then commits the thread for a successful end of

step or omits it and undoes the step including its updates to the database.

Records added or changed by a successful step become permanent entries in a

recoverable file. Conversely, records added or changed by a failed step revert to

their original state.

Universal Database Control

5–20 7850 5252–018

• Universal Database Control maintains a central lock directory for files, pages, and

records. A queue and deadlock detection system recognizes and resolves locking

conflicts. Universal Database Control detects and uniformly resolves resource

deadlocks. Universal Database Control queues threads in conflict with one another

because of a lock by a thread or another resource, and then reactivates the

threads as soon as the lock is lifted and the resource becomes available.



Support Web site:

• Repository for ClearPath OS 2200 Programming Reference Manual (7830 8079)

• Universal Data System Planning and Installation Overview (7844 8370)

• Universal Data System Configuration Guide (7844 8362)

• Universal Data System Administration and Support Reference Manual

(7831 0737)

7850 5252–018 6–1

Section 6 Fourth Generation Language (4GL) Products

The enterprise server program development strategy maximizes productivity by

emphasizing the use of fourth-generation languages and by providing a variety of

programmer productivity tools for use with third-generation languages. The Business

Information Server (formerly MAPPER), Enterprise Application Environment (formerly

LINC) and Graphical Interface Workbench (formerly PowerClient) products provide a

comprehensive software development environment for rapid software development.

Note: Business Information Server (formerly MAPPER) products are no longer

included with the release and must be ordered separately.


• Business Information Server

• Enterprise Application Environment

Business Information Server

6–2 7850 5252–018

6.1. Business Information Server

Business Information Server (formerly called MAPPER) is a decision support system

providing information access, analysis, and reporting in an open, enterprise-wide,

client/server environment.

The Business Information Server system supports both end-user ad hoc analysis and

the rapid development of sophisticated decision support applications.

Business Information Server offers these key features:

• Ability to access, analyze, and report on information throughout the enterprise

• Iterative analysis capabilities

• Access to popular relational databases

• Data view and analysis tools that operate in the way you think about the data

• Support for all client/server modes of operation

• Powerful scripting language to build sophisticated decision support applications

• Robust networking features

Business Information Server software operates on all tiers of an enterprise network,

such as the following:

• Desktop and laptop PCs

• Departmental servers from many different vendors

• Enterprise Servers from Unisys

The Business Information Server system creates a powerful and intuitive environment

for your end users at all levels of the enterprise and with various degrees of computer

skills.

Business Information Server for ClearPath provides decision support capabilities that

span both the custom and Intel nodes of a ClearPath OS 2200 server. The primary

benefits of Business Information Server for ClearPath are the following:

• Common end-user environment across both nodes.

• Common application development environment for both nodes.

• Easy application partitioning.

• Ability to run parts of applications on whichever processors are best for the job.

• Ability to leverage the processing qualities of both nodes. Combines enterprise

characteristics such as resiliency, data integrity, and high-volume transaction

processing with the flexibility and choice offered by open systems.

• Proven technology in a heterogeneous, multiprocessing environment.

Unisys offers clients the added advantage of running open applications while

protecting their investments in existing applications.


7850 5252–018 6–3

In the operating environment of a ClearPath OS 2200 server, Business Information

Server can use its powerful decision support capabilities against operational data on

the custom node while analyzing and processing data on the Intel node. This operating

environment gives you the opportunity to use the most appropriate node of a

ClearPath server to achieve the best results for your business.

A Business Information Server for ClearPath OS 2200 package includes the following:

• Business Information Server for ClearPath OS 2200

• Business Information Server for ClearPath OS 2200 separately installable features:

− Turbo MAPPER 2200

− Tape Recovery and Maintenance (TRAM)

− MRI

− MAPPER OLTP for 2200

• Business Information Server for Microsoft Windows

• Business Information Server for Microsoft Windows Client

• Graphical Interface for Business Information Server

• Business Information Server Jump Start for Programmers CBT

• Internet Commerce Enabler (formerly called Cool ICE)

As listed, this complete package of Business Information Server software is provided

with ClearPath OS 2200. All products work independently as well as together in an

integrated package. For example, you can install only the Business Information Server

for ClearPath OS 2200 and continue to execute Business Information Server

applications developed on your 2200 system. To extend the total Business Information

Server processing capability on your ClearPath OS 2200 servers, you can install

Business Information Server for UnixWare or Business Information Server for

Microsoft Windows.

Included with this Business Information Server solution package is a Business

Information Server for Microsoft Windows Client and a Graphical Interface for

Business Information Server. Business Information Server for Microsoft Windows

Client provides seamless execution of enterprise decision support applications.

Graphical Interface enables you to develop or execute graphical applications using the

Business Information Server graphical interactive commands.

The Graphical Interface is available for all Business Information Server systems. The

following optional clients are available:

• Business Information Server for Microsoft Windows Client development tools

Enables you to perform workstation-based development of Business Information

Server solutions

• Graphical Interface Workbench

Enabling integration with third-party visual development tools such as Visual Basic

and PowerBuilder.


6–4 7850 5252–018

Graphical Interface for Business Information Server runs in a Windows 2000

(Professional Edition) or Windows 98 environment. The Graphical Interface can only

access Business Information Server through a Windows Sockets interface.

Business Information Server for Microsoft Windows Client interoperates with other

Business Information Server components through a TCP/IP and Windows Sockets

interface.

The Business Information Server solution package also includes the Internet

Commerce Enabler. Internet Commerce Enabler is a rapid application development and

deployment environment that provides the framework to create, organize, and

manage dynamic Web-based business applications and services on the Microsoft

Windows server platform. It enables developers to create new business applications

that extend the capabilities of the existing databases and applications far beyond their

original intent by providing value in the following areas:

• Support for multiple clients

• Support of Microsoft Windows COM platforms

• E-business components and services

• Access to and integration of enterprise data assets

The following components are necessary for creating, organizing, and managing Web

applications using Internet Commerce Enabler:

• Active Server Page (ASP) Object

• Server Object

• Engine

• Service Handler

• Repository

• Script Editor

• Component Builder (includes the XML mapping tool)

• ICE Admin

• Gateway Configuration tool

Interoperability

The Business Information Server for ClearPath MRI, OLTP, and Business Information

Server networking components are facilitated by the interoperability aspects of the

ClearPath OS 2200 system. MRI can be used to integrate data from Oracle systems.

The OLTP capabilities of the Business Information Server for the UNIX Operating

System component can be used to integrate data with other external transaction

applications from the custom node as well as the Intel node.

Business Information Server networking capabilities are a key component to

distributing Business Information Server applications across the custom and Intel

nodes, as well as the Windows desktop.


7850 5252–018 6–5

Remote Database Access Through ODBC

Business Information Server for Microsoft Windows is capable of locally or remotely

accessing ODBC-compliant databases for a Business Information Server application

running on Windows. The MRI components of the Business Information Server for

ClearPath OS 2200 and Business Information Server for the UNIX Operating System

delivered with the ClearPath OS 2200 system include the capability to remotely access

ODBC-compliant databases. It also significantly expands the database interoperability

of the Business Information Server.



Support Web site:

ClearPath OS 2200

• Business Information Server for ClearPath OS 2200 Administration Guide

(7831 9415)

• Business Information Server for ClearPath OS 2200 Installation and Systems

Analysis Guide (7831 9332)

• Business Information Server for ClearPath OS 2200 Open Interface Guide

(7846 0243)

• Business Information Server for ClearPath OS 2200 Operations Guide

(7831 9324)

• Business Information Server for ClearPath OS 2200 SCHDLR Interface

Programming Reference Manual (7832 1122)

• Business Information Server for ClearPath OS 2200 Software Release

Announcement (7832 1106)

• Business Information Server for ClearPath OS 2200 Using an IBM 3270 Terminal

(7832 1114)

• Business Information Server for Tape Recovery and Maintenance (TRAM)

Installation and Operations Guide (7850 2408)

Microsoft Windows

• Business Information Server Application Portability Quick Reference (7832 1205)

• Business Information Server Command Reference (7832 0769-124)

• Business Information Server Developer's Guide (7850 2341-012)

• Business Information Server for Microsoft Windows Software Release


• Business Information Server User's Guide (7850 2358-011)

• MRI Administration and User's Guide (7846 0391)

• Business Information Server JavaScript Developer's Help (6891 8960)

• Business Information Server for Microsoft Windows Documentation Roadmap

(6891 8945)

• Business Information Server Standard Help Library (6885 2797)


6–6 7850 5252–018

UNIX Systems

• Business Information Server Application Portability Quick Reference (7832 1205)


• Business Information Server for the UNIX Operating System Administration

Guide (7832 0777)

• Business Information Server for the UNIX Operating System Installation Guide

(7846 0474)

• Business Information Server for the UNIX Operating System Software Release



• MRI Administration and User's Guide (7846 0391-016)


Microsoft Windows Clients



• MRI Administration and User's Guide (7846 0391)

• Business Information Server Application Portability Quick Reference

(Self-extractingEXE) (7832 1205)

• Command Reference (7832 0769-121)


• Business Information Server For Microsoft Windows Client Software Release


Linux

• Business Information Server for Linux, Red Hat® Enterprise Linux 4 Version,

Software Release Announcement (3850 8057)

• Business Information Server for Linux SUSE LINUX Enterprise Server Software

Release Announcement (4729 2131)


Internet Commerce Enabler

• Internet Commerce Enabler Software Release Announcement (7850 2507)

• Internet Commerce Enabler for Windows 2000/NT Getting Started (7850 2481)

• Internet Commerce Enabler Technical Overview (7850 2473)

• Internet Commerce Enabler Developer's Reference (7850 2465)

• ICE-RADS for Internet Commerce Enabler Software Release Announcement

(7850 2879)

Enterprise Application Environment

7850 5252–018 6–7

6.2. Enterprise Application Environment

Enterprise Application Environment (formerly called LINC) is a suite of business-

oriented software tools and a supporting methodology that helps your organization

build and deploy transaction-intensive information systems. Enterprise Application

Environment facilitates design, development, operation, and maintenance of

client/server applications and enables fast-track implementation of software changes.

With Enterprise Application Environment, you can define the information needs of

your organization in business terms, rather than in technical data processing terms.

Enterprise Application Environment provides a set of the tools that an enterprise uses

to build large-scale, host-based, client-server, and Web applications. Enterprise

Application Environment consists of the following tools:

• Enterprise Application Developer

Enterprise Application Developer (formerly called LINC Development) is a PC-

based Windows development environment that provides the capabilities to

− Define, design, develop, and test a new Enterprise Application Environment.

− Import and reengineer or enhance an existing Enterprise Application

Environment system downloaded from a host (ClearPath servers, MCP,

OS 2200, or UNIX).

− Export an Enterprise Application Environment system to another host for

generation and deployment.

• Enterprise Application Builder

Enterprise Application Builder (formerly called LINC Generate) provides the

capability to

− Create and maintain Enterprise Application Environment System

Specifications.

− Load and unload existing Enterprise Application Environment Specifications to

and from Enterprise Application Builder on ClearPath enterprise servers; MCP

based, OS 2200 based, and UNIX hosts, by using LCOPY, and to and from LDA,

by using the CASE Extract/CASE Load facility.

− Generate and install Enterprise Application Environment Systems and Reports.

− Analyze, list, and inquire on Enterprise Application Environment Specifications.

− Interface to Enterprise Application Environment Report Output Control System

(ROC).

• Enterprise Application Runtime Test Environment for ClearPath OS 2200

Enterprise Application Runtime Test Environment for ClearPath OS 2200 (formerly

called LINC Interpretive Test Environment or LITE) enables developers to test new

and changed Ispecs and Reports without requiring generation. It gathers

information directly from the Enterprise Application Environment Specification held

in Enterprise Application Builder. It then runs Enterprise Application Environment

according to this information.

Enterprise Application Environment

6–8 7850 5252–018

• Enterprise Application Runtime

Enterprise Application Runtime (formerly called LINC Deployment) consists of a

set of utility programs, common banks, and Relational Database Server tables

providing Enterprise Application Environment facilities on OS 2200 based servers

that enable you to use the following software:

− Enterprise Application Builder

− Enterprise Application Environment Report Output Control System (ROC)

− Interface to Graphical Interface Workbench

− User-generated Enterprise Application Environment Systems

LINC Systems Approach

LINC Systems Approach (LSA) is a flexible methodology for building and deploying

small to very large business applications using the tools in Enterprise Application

Environment. It presents the "best practices" of successful Enterprise Application

Environment users and provides guidelines for the analysis, design, development,

implementation, and evaluation phases of Enterprise Application Environment

software development life cycle. The purpose of LINC Systems Approach is to

produce higher quality applications.

Enterprise Application Web Enabler

Enterprise Application Web Enabler (formerly called PowerClient Web Agent) provides

the necessary link between the Microsoft Internet Information Server (IIS) and existing

Enterprise Application Environment applications on ClearPath enterprise servers and

OS 2200 systems. Using a Windows NT server, Enterprise Application Web Enabler

enables the browser user to connect with the application, using the modernized forms

developed in LDA or Graphical Interface Developer.

Enterprise Application Component Enabler

Enterprise Application Component Enabler (formerly called PowerClient ActiveLINC)

enables programmers to develop Active Server Pages, Java Server Pages, Java

applets, or Visual Basic applications that interact with your Enterprise Application

Environment application as a data source. Any application that can call a COM object

(for example, Microsoft Excel) can interact with the Enterprise Application

Environment application.


The Enterprise Application Environment Documentation Updates includes the

documentation updates for this product on the Unisys Product Support Web site.

7850 5252–018 7–1

Section 7 Internet Products

This section describes products that support access to private intranets and to the

Internet, and area of vital importance in today's business world.

Note: See the Fourth-Generation Languages section for Business Information

Server (formerly MAPPER), Internet Commerce Enabler, and Enterprise Application

Environment.


• ClearPath ePortal

• Distributed Transaction Integration (DTI)

• Web Transaction Server for ClearPath OS 2200

7.1. ClearPath ePortal

ClearPath ePortal enables application developers to automatically deploy, manage, and

secure ClearPath applications for Web, mobile device, and Web services solutions.

Using ClearPath ePortal, application developers can

• Import COBOL source data descriptions directly for the Transaction Processing

(TIP) application and the Open Distributed Transaction Processing (Open DTP)

application.

• Import View Definition file for the Open DTP environment.

• Deploy applications to

− The Web

− Mobile devices such as iPhone and smart phones.

− Web services

ClearPath ePortal automates a solution at every point: from development to

deployment.

ClearPath ePortal requires no new incremental skills and can radically reduce the cost

of creating e-business solutions, accelerating the time to market and bringing new

levels of efficiency to your ClearPath infrastructure.

ClearPath ePortal

7–2 7850 5252–018

General Features

ClearPath ePortal consists of the following main features:

• ClearPath ePortal Developer

This plug-in to Visual Studio 2008/2010 enables you to

− Modernize Open Distributed Transaction Processing (Open DTP) programs by

importing COBOL data description or View Definition file. You can capture

single data descriptions or complete COBOL programs.

− Modernize Transaction Processing (TIP) programs by capturing COBOL data

description. You can capture single data descriptions or complete COBOL

programs.

− Control the flow of data between a client and an OS 2200 application. This

capability enables you to

ο Consolidate multiple OS 2200 transactions into one Web page or Web

service method.

ο Specify client application interactions with the OS 2200 application based

on run-time conditions.

− Use the integrated source control capabilities of Visual Studio 2008/2010 with

the Unisys SURE Software Configuration Management solution, which is

compatible with the Microsoft source code control (SCC) API.

• Personality Modules

A ClearPath ePortal personality module provides a run-time environment that

enables you to

− Export your OS 2200 applications to the Web and wireless networks; for

example, iPhone and smart phones.

− Export your OS 2200 applications as Web services for use in service-oriented

architecture (SOA) environments.

• ClearPath ePortal Manager

This browser-based point-and-click management environment automates the

processes required to deploy, configure, and manage applications and solutions

residing in the personality modules. The ClearPath ePortal Manager enables you to

− Easily deploy and monitor applications in the ClearPath ePortal environment.

− Add personality modules to scale your ClearPath ePortal applications.

− Manage and monitor the health of the ClearPath ePortal system.

− Receive e-mail notifications of significant ClearPath ePortal alert events.

• Deployment

− ClearPath ePortal Business

A rack-mounted server appliance. Virtualization technology enables personality

modules and the management software to share a common hardware

environment.

ClearPath ePortal

7850 5252–018 7–3

ClearPath ePortal Developer

The following are the configuration requirements for ClearPath ePortal Developer:

• Client Workstation Hardware

A workstation capable of running Microsoft Visual Studio 2008/2010 is required.

See the Microsoft Visual Studio 2008/2010 documentation or Web site for specific

hardware requirements.

• Client Workstation Software

Microsoft Visual Studio 2008/2010 is required to install and run the ClearPath

ePortal Developer.

All Microsoft Visual Studio 2008/2010 editions are supported except the Microsoft

Visual Studio 2008/2010 Express edition.

See the Microsoft Visual Studio 2008/2010 documentation or Web site for

workstation software requirements.

ClearPath ePortal Business

The primary back-end OS 2200 server partition must have at least 300 MBs of space

for the APPLIANCES share.

The following are the network configuration requirements for ClearPath ePortal

Business:

• Back-end LAN (host LAN)

• A private, secure LAN that connects one Ethernet port on the OS 2200 server to

the ClearPath ePortal Business system is required.

• Front-end LAN (public LAN) connected to an organization intranet or the public

Internet

• Application Management LAN (AM LAN) connected to an AM LAN switch which

connects to the Operations Servers

ClearPath ePortal iPhone integration

This release incorporates the following new iPhone integration capabilities:

• iPhone integration automatically builds iPhone WebApps in ePortal. This feature

provides custom iPhone .Net controls for iPhone development

• Enhanced iPhone Support – this feature supports calling ePortal generated web

services from native iPhone applications

Ordering Information

Contact your Unisys representative to determine the proper licensing styles required

to order the software for the ClearPath ePortal personality module and for ClearPath

ePortal Manager for your particular environment.

Distributed Transaction Integration

7–4 7850 5252–018



Support Web site:

• ClearPath ePortal Manager Help (6891 9042)

• ClearPath ePortal Developer Help (3850 7869)

• ClearPath ePortal Business Configuration Wizard Help (8214 5491)

• ClearPath ePortal Business Implementation and Operations Guide (8215 9641)

• ClearPath Specialty Engine for OS 2200 Configuration Guide (3839 3005)

7.2. Distributed Transaction Integration

Distributed Transaction Integration is a multipurpose middleware product that

provides access to applications or transactions running on ClearPath systems from a

Microsoft Windows environment. It also provides access to other transaction

environments including Oracle Tuxedo and Fujitsu TPMS.

This product combines the capabilities previously provided by Transaction Integrator

(formerly WebTx) and Open Transaction Integrator (OpenTI).

Distributed Transaction Integration enables

• Internet or Intranet access to applications and transactions running on a ClearPath

OS 2200 system.

• An environment where Microsoft applications can access applications and

transactions on all supported systems and transaction environments. Access is

fully bidirectional and supports global transactions.

Distributed Transaction Integration provides both application run-time and

development environments that integrate these various middleware environments. As

a result, Distributed Transaction Integration enables developers to integrate existing

X/Open-compliant DTP services (Unisys OpenDTP, Oracle Tuxedo, Fujitsu TPMS) and

Unisys TIP/HVTIP transactions with other popular application environments such as

Microsoft and Oracle WebLogic.

Client Types

Distributed Transaction Integration supports access from the following client types:

• Simple Object Access Protocol (SOAP)-based, .NET Web services

• Enterprise JavaBeans (EJB), Java/Remote Method Invocation (RMI), Java applets,

and Java Server Pages (JSP)

• Microsoft COM+ (extension to the Component Object Model)

• Hypertext Markup Language (HTML)

• Extensible Markup Language (XML)

• Active server pages (ASP)


7850 5252–018 7–5

Enterprise Application Integration (EAI) Solutions

Distributed Transaction Integration supports integration with the Siebel eScript

enterprise application integration (EAI) solution.

Transaction Integrator Component

The Transaction Integrator (TxI) component provides access from Web-based and

non-Web clients to ClearPath MCP and ClearPath OS 2200 applications that comply

with the Open Group's Distributed Transaction Processing (DTP) model, and to

ClearPath OS 2200 TIP, HVTIP, and batch transactions. Clients and technologies include

XML, .NET, COM+, Active Server Pages, Wireless Application Protocol (WAP), and

others.

Transaction Integrator enables you to make new or existing applications running in the

OS 2200 or MCP operating environments available to clients in client/server networks

outside the legacy systems. These networks can be based on various environments,

including Web-based (that is, Internet, intranet, or extranet), Enterprise JavaBeans

(EJB), Java Remote Method Invocation (RMI), CORBA, .NET, or DCOM.

Transaction Integrator provides the following services:

• Client handling

Transaction Integrator communicates with the browser or other clients as though

it were the server, keeping communications open as expected by the target

network. Some gateways (ViewGate and JGate) have built-in client handling

features that can handle HTML clients such as Web browsers. Other gateways

(GGate and XGate) use adapters that provide client handling services. This enables

them to support a wide variety of clients.

• Data conversion

Transaction Integrator can use VIEWs or COBOL descriptions of the data on the

ClearPath system to provide data conversion between the client environment and

the ClearPath environment. It also supports data transfers where no data

conversion occurs, leaving data translation issues entirely to the clients and

services.

• Server handling and communication

Transaction Integrator communicates with the host application as though it were

the client, ensuring that all I/O is sent and received correctly from the legacy

application perspective.

OS 2200 OutBound Feature

OS 2200 OutBound is the Windows component of a solution that enables Open

Distributed Transaction Processing services and clients to make calls to Microsoft

COM servers or Enterprise JavaBeans (EJBs) running in the Oracle WebLogic Server

on a Windows system.


7–6 7850 5252–018

Open Transaction Integrator Component

The Open Transaction Integrator (OpenTI) component provides native COM+ access to

transaction monitors (TMs) and their applications that conform to the Open Group's

distributed transaction processing standard. These TMs include Oracle Tuxedo on

Windows, UnixWare, HP, AIX or SUN platforms as well as the TMs on Unisys and ICL

mainframes that use Open Distributed Transaction Processing software. The COM+

environment enables these TMs to be integrated with other TMs in the same global

transaction.

OpenTI enables COM+ Component Services to communicate with applications running

under an XATMI-compliant transaction monitor. You only need to create a client

application that can instantiate a COM+ object. This includes Visual Basic, ASPs, Visual

C++, and Java clients running on a Windows Server, Windows Workstation, Windows

95, or any other platform that supports DCOM. Running on Windows 2000,

components created by OpenTI appear as simple automation servers that developers

can easily add to their application.

OpenTI also enables client OLTP programs to access COM+ server components

written in Visual C++, or Visual Basic. These server components enable the OLTP

client to gain access to other resources controlled by COM+. Using the Bring Your

Own Transaction (BYOT) feature of COM+, OpenTI enables full bi-directional two-

phase commitment between remote OLTP systems and COM+.

Note: Starting with the ClearPath OS 2200 Release 8.0, Open Transaction Integrator

was incorporated into Distributed Transaction Integration.

Open Transaction Integrator (formerly called OpenTI) provides an application runtime

and development environment that enables full transaction integration between

applications that conform to the Open Group's distributed transaction processing

standard and COM+ applications. Open Transaction Integrator enables the enterprise

to leverage data and the business logic that controls them and extend the application

to include data controlled by COM+ applications.

Open Transaction Integrator consists of the following main features:

• Builder

A stand-alone graphical user interface (GUI) tool that enables an application

developer to automatically create Open Transaction Integrator components that

provide bi-directional communication between Open Distributed Transaction

Processing and COM+ applications.

• Runtime

A generic automation server for all Open Transaction Integrator components is

created by the Builder component. It provides connection services to remote

Distributed Transaction Processing systems using standard OSI (over TCP/IP)

protocols or enhanced TCP-IP multiplexed connections as well as data coercion

support between Windows and the Distributed Transaction Processing system.


7850 5252–018 7–7

• Management Console Snap-In

An extension snap-in for Microsoft Management Console (MMC) that enables you

to manage the remote host properties of the Open Transaction Integrator

components, maintain connections to remote Open Distributed Transaction

Processing hosts, manage security mapping credentials for inbound service

requests and manage Distributed Transaction Processing service to method

mappings.

• Open Transaction Integrator Utilities

A series of utilities, included in the Management Console snap-in, that aid in

configuration of peer Distributed Transaction Processing systems. This includes

Unisys ClearPath servers, Oracle Tuxedo and deployment utilities to enable

OpenTI and COM+ component and configuration information to be easily

transferred from test to production systems.

• Remove

A utility that helps you remove Open Transaction Integrator components from the

Windows system and registry.

The Open Transaction Integrator software enables developers to create new

Windows clients and servers for existing Open Distributed Transaction Processing

services without having to learn XATMI programming notation. The clients can be

written in any language that supports COM+ including Microsoft Visual Basic,

Microsoft Visual C/C++, Micro Focus COBOL, Sybase PowerBuilder, Microsoft .Net,

and Siebel.

Open TI provides the following services:

• Automatic client proxy

By using the robust OpenTI Builder development environment, you can create

client proxies as a back end to DTP services that include Enterprise Application

Environment (LINC), Business Information Server (MAPPER), Oracle TUXEDO, and

other DTP applications. A single COM+ method is exposed and can be called from

any programming language that supports COM+ including Microsoft Visual Basic,

Microsoft Visual C/C++, Microsoft .NET, Sybase PowerBuilder, and Micro Focus

COBOL.

• Data Conversion

OpenTI provides the conversion of data from the Windows environment to the

legacy DTP system. OpenTI supports all DTP VIEW and buffer types as well as a

conversion from XML to COBOL Working Storage Data. This enables Windows

clients and servers to seamlessly extend applications to include data controlled by

a legacy DTP application.

• Server support

OpenTI is fully bi-directional supporting global transactions for full transaction

integration from either the Windows environment or from the legacy DTP system.

A COM+ application can be extended to include data from a DTP application. An

existing DTP application can be extended to include data from a COM+ application.

Web Transaction Server for ClearPath OS 2200

7–8 7850 5252–018

Open Transaction Integrator provides:

• Internet, intranet and extranet clients with access to Open Distributed Transaction

Processing services running on the OS 2200, MCP or Oracle Tuxedo systems.

Open Transaction Integrator controls all connections, data coercion issues, and

recovery.

• Open Distributed Transaction Processing clients on the OS 2200 node or MCP

node of the ClearPath server, or Oracle Tuxedo systems clients with access to

COM-based services on the Windows node of the same ClearPath server or on

other Windows servers. This enables the legacy Distributed Transaction

Processing application to be extended to include data controlled by COM+

components within a global transaction.

• Utilities to aid the enterprise in managing the COM+ deployment, security and

configuration of a heterogeneous environment.

Open Transaction Integrator Product Suites

Open Transaction Integrator is available in two product suites:

• Open Transaction Integrator 2.1 provides full transactional support when going

from COM+/MTS to Open/OLTP, but non-transactional only when going the other

way. This version supports Windows NT and Windows 2000.

• Open Transaction Integrator 8.0, now a component of Distributed Transaction

Integrator, provides full transactional support between COM+ and Distributed

Transaction Processing applications. This version supports Windows 2000 only

and provides multiplexed connection support to other Distributed Transaction

Processing Systems.



Support Web site:

• Distributed Transaction Integration User's Guide (Self-extracting Help file)

(7850 4230)

• Open Distributed Transaction Processing Getting Started (7833 5007)

7.3. Web Transaction Server for ClearPath OS 2200

Web Transaction Server for ClearPath OS 2200 enables Web access to high-volume

OS 2200 transaction applications. It provides a modern, Web-compatible interface

directly to the ClearPath OS 2200 series large-scale transaction processing

environment.

Web Transaction Server also supports static Web pages, forms, graphics, Java

applets, and other standard Web server features to facilitate the implementation of

complete Web applications on Web Transaction Server. These Web objects can be

stored in OS 2200 program files or in Common Internet File System (CIFS) files.


7850 5252–018 7–9

Designed specifically with transaction processing in mind, the Web Transaction Server

takes full advantage of the proven performance, reliability, and security of the OS 2200

system, making it ideally suited to high-capacity intranet and Internet usage.

In addition to supporting general Web server capabilities, the Web Transaction Server

enables Web access to the high-volume transaction environment associated with

traditional mainframes. Using this capability, you can run OS 2200 transactions from

standard Web browsers, such as the Microsoft Internet Explorer, with the industrial

strength features required for business-critical applications.

Web Transaction Server is specifically designed for Web-enabling the following kinds

of applications:

• OS 2200 transaction processing (TIP) or high volume transaction processing

(HVTIP) applications

• Applications developed with the COBOL Compiler, the ASCII COBOL Compiler, or

the C Compiler using CGI (Common Gateway Interface)

• Display Processing System applications, written in any supported programming

language, via the Web Enabler for Display Processing System, a feature of the

Web Transaction Server

• OS 2200 applications that are compliant with Open Distributed Transaction

Processing, excluding applications developed with the Enterprise Application

Environment

Web Transaction Server supports secure Web access and messaging using SSL

(Secure Sockets Layer) making it ideal for applications that require a high level of

security and data protection.

Web Enabler for Display Processing System

Using the Web Transaction Server and the Web Enabler for Display Processing

System, programmers can adapt existing Display Processing System applications to

be Web accessible without changing the transaction programs themselves.

Programmers can enhance the application's interface and use modern Web-browser

capabilities such as graphics, fonts, color, multimedia, and so forth.

Web Transaction Server Strong Version

The Web Transaction Server standard version (which is part of the integrated

operating environment) provides a 40-bit data encryption method. The128-bit

encryption strength style of WebTS (IXS4000-SSU) is not supported in ClearPath

OS 2200 12.0 and in the future releases. The IXS4000-CSU style supports the 128-bit

and even stronger levels of encryption using Communications Platform and

Communications Platform for Open Systems cipher APIs instead of embedded WebTS

Cipher libraries.


7–10 7850 5252–018

Publishing Assistant

The Publishing Assistant provides Web site managers with a capability similar to

Microsoft's FrontPage Explorer for assisting with Web content management and

publication of Web Transaction Server hosted objects. This tool builds a visual

definition of the relationship between the Web Transaction Server 2200 Program Files

and the corresponding Windows directories on the Web-content manager's

workstation. Using this visual definition, the Publishing Assistant can do everything a

Web content manager needs to do. In particular:

• Display PC filenames and corresponding OS 2200 names.

• Check for conflicts between the generated OS 2200 names.

• Compare the dates of a PC file as it exists on the OS 2200 against its date as it

exists on the PC.

• Build the appropriate file transfer scripts and perform the file transfers.

• Build script files that are processed by the Web Transaction Server administrator

to update the contents of OS 2200 Web Page files while the files are in

production.

The Publishing Assistant resides on the OS 2200 server hosting the Web Transaction

Server.

Administrative Scripting

This feature enables a site to update Web pages and pack page files while the Web

Transaction Server is in production operation. It enables the running of scripts on a

one-time or repeated basis at regular intervals. The script file names and descriptions

must be configured by the Web Transaction Server administrator, but users with

script file access can alter the actual script commands as needed for their application.

Web Transaction Server and CIFS

The OS 2200 Common Internet File System (CIFS) introduced the ability to access,

create, and modify information on ClearPath OS 2200 systems from your Windows

desktop using Windows-based tools. The Web Transaction Server supports the ability

to serve OS 2200 CIFS content through standard Web browsers. And, you can use

state-of-the-art Web content tools directly on the OS 2200 data and deliver the results

with the Web Transaction Server.



Support Web site:

• Web Transaction Server for ClearPath OS 2200 Programming Guide (7850 4248)

• Web Transaction Server for ClearPath OS 2200 Administration Guide

(7850 4073)

• Web Enabler for Display Processing System User's Guide (7851 5509)

7850 5252–018 8–1

Section 8 Java and Java 2 Platform, Enterprise Edition Products

The following product is described in this section:

• Business Information Server Resource Adapter for the Java™ Platform

• Open Distributed Transaction Processing Resource Adapter for the Java™

Platform

• OS 2200 Transaction Resource Adapter for the Java™ Platform

• JBoss Enterprise Application Platform for ClearPath OS 2200 (JBOSS-2200)

• Virtual Machine for the Java™ Platform on ClearPath OS 2200 JProcessor (JPJVM)

• ClearPath OS 2200 JProcessor

• Network Database Server Resource Adapter for the Java™ Platform (DMS-RA)

• Relational JDBC Driver for ClearPath OS 2200

If you are new to Java and want a high-level understanding of the Java products, refer

to the Getting Started with Java™ Technologies (3839 3096) for more information.

Business Information Server Resource Adapter for the Java™ Platform

8–2 7850 5252–018

8.1. Business Information Server Resource Adapter for the Java™ Platform

The Business Information Server Resource Adapter for the Java™ Platform (BIS-RA) is

a standards-based Java interface into Business Information Server that opens up BIS

data and scripts to stand-alone Java applications and Java 2 Platform, Enterprise

Edition (J2EE™ ) components such as Enterprise JavaBeans (EJBs), and servlets. The Business Information Server Resource Adapter for the Java™ Platform has server and

client components.

The JBIS Server runs on the ClearPath OS 2200, Windows, or Linux platform that

contains BIS. The 2200 JBIS Server is installed as part of the BISAPI installation. The

client component is the BIS-RA. The BIS-RA implements the contracts defined in the

J2EE Connector Architecture Specification. The client component runs on your Java

platform.

General Features

• Supports SSL connections

• Passes a CLOB as input to a script

This enables you to pass large amounts of data as input to a script. A defined

parsing mechanism breaks up the input data into lines that are placed in an input

report for a script.

• Scripts can return a BLOB

A script can return a BLOB (binary report) as a result. A new method is added to

the BISScript interface that is used to determine if the result of a script contains

binary or character data.

• Inbound Messaging

This allows a JavaScript running in the BIS environment to open a connection to

the BIS-RA and then execute the Session Bean method.

• Full IPv6 support (available when executed with COMAPI and CPComm levels that

support IPv6)

Note: Changes were included in level 45R1 of BIS 2200 for ClearPath OS 2200 to

support The Business Information Server Resource Adapter for the Java™ Platform.


The document Business Information Server Resource Adapter for the Java™

Platform Developer’s Guide (3839 6529) is available for this product on the Unisys

Product Support Web site.

Open Distributed Transaction Processing Resource Adapter for the Java™ Platform

7850 5252–018 8–3

8.2. Open Distributed Transaction Processing Resource Adapter for the Java™ Platform

Open Distributed Transaction Processing Resource Adapter for the Java™ Platform is

a J2EE Resource Adapter that provides connections between J2EE platforms

(including Oracle WebLogic Server and IBM WebSphere) and Open Distributed

Transaction Processing (Open DTP) applications that exist on ClearPath NX, Windows,

or UNIX systems.


enables you to integrate Open DTP applications on a remote system with J2EE

technology. With the Open Distributed Transaction Processing Resource Adapter for

the Java™ Platform, application environments on diverse platforms can access and

interact with your Open DTP applications and data.

Using Open Distributed Transaction Processing Resource Adapter for the Java™

Platform enables your Open DTP applications to

• Participate in Java-based business-to-business or government-to-government

exchanges with other enterprises or organizations.

• Maintain database integrity across platforms without incurring system downtime

or using manual updates.

• Continue full-service business operations while implementing new methods and

systems.

• Coordinate updates to ClearPath and Windows databases with updates to Java

environment databases.

• Invoke DTP transactions and access databases from Java-based Web application

portals.

• Invoke J2EE JavaBeans (EJB) from DTP client applications.

General Features


provides the following features:

• Complies with version 1.5 of the J2EE Connector Architecture specification.

• Supports synchronous, asynchronous, and connection-oriented interactions with a

J2EE client application and an Open DTP server program.

• Supports bi-directional global exchanges so J2EE can invoke DTP services and DTP

clients can invoke J2EE services.

• Supports the XATMI call/response and conversational set of functions.

• Provides a 3GL development tool for defining data coercion and automatic

generation of coordinating java classes.

• Enables the support of other EBCDIC character sets including Latin-1, Latin 3 and

others.

Open Distributed Transaction Processing Resource Adapter for the Java™

Platform

8–4 7850 5252–018

• Provides a Web-based administration tool. As an option for Oracle WebLogic

users, it can be incorporated into the WebLogic Administrator Console as a

console extension.

• Provides optional data compression and network redundancy features.

• Enables the developer to optionally trace all data buffers for easier debugging.

• Provides a 3GL administrator tool to create and manage the resource adapter and

Web-based administrator program for deployment to the application server.

• Supports global transactions from the J2EE application server environment.

• Supports data encoding based on COBOL 01 records. COBOL data definitions can

include nested items, occurs clauses, default values, and for MCP can include

numeric types and varying arrays.

• Supports data encoding of DTP buffer types (X_Octet, String, Carray, and XML).

• Supports DTP View types (X_Common and X_C_Types, all view fields) and XATMI

encoding (TM2200, CAE, and Native_MCP).

• Provides an integrated security environment between J2EE and the peer DTP

system.



Support Web site:


Platform Studio Help (3827 9295)


Platform Administration Help (3830 8854)


Platform User’s Guide (6898 5852)

OS 2200 Transaction Resource Adapter for the Java™ Platform

7850 5252–018 8–5

8.3. OS 2200 Transaction Resource Adapter for the Java™ Platform

The OS 2200 Transaction Resource Adapter for the Java™ Platform (Resource

Adapter) provides access from application components executing under Oracle

WebLogic Server (WLS), IBM WebSphere Application Server (WAS), and JBoss

Enterprise Application Platform (including JBOSS-2200) to ClearPath TIP, HVTIP, and

batch programs. Clients and technologies include Enterprise JavaBeans (EJB),

JavaServer Pages (JSP), Java servlets, and other J2EE technologies.

The resource adapter enables you to make new or existing applications running in the

OS 2200 operating environments available to Java clients running on ClearPath

systems or others systems that are running Oracle WLS, IBM WAS, and JBoss

Enterprise Application Platform (including JBOSS-2200).

The resource adapter accepts application component connection requests for

OS 2200. Once a component connection request is granted, the component can

interact with OS 2200 TIP/HVTIP or batch programs using a request/response

paradigm.

The Java Connector Architecture (JCA) specification enables Unisys to provide a

standard connector for ClearPath Enterprise Servers (OS 2200). The resource adapter

is a system-level software that is used by a Java application to connect to an existing

system. The resource adapter plugs into an Application Server and provides

connectivity between the existing system, the Application Server, and the client

application.


The document OS 2200 Transaction Resource Adapter for JavaTM User's Guide

(4729 1992) is available for this product on the Unisys Product Support Web site.

8.4. JBoss Enterprise Application Platform for ClearPath OS 2200 (JBOSS-2200)

JBoss Enterprise Application Platform for ClearPath OS 2200 (JBOSS-2200) (formerly

known as JBoss Application Server™ for ClearPath OS 2200) is the preeminent open

source Java Enterprise Edition (Java EE) Application Server for your enterprise Java

applications.

The ClearPath architecture provides a secure mainframe environment for running your

mission-critical Java-based applications. The JBoss Enterprise Application Platform

from Unisys runs on an OS 2200 JProcesser within your OS 2200 environment. You

can take advantage of a popular open source, fully integrated JBoss Enterprise

Application Platform supported by Unisys.


The document ClearPath Enterprise Servers JBoss® Enterprise Application Platform

for ClearPath® OS 2200 Installation, Administration, and Programming Guide


Virtual Machine for the Java™ Platform on ClearPath OS 2200 JProcessor (JPJVM)

8–6 7850 5252–018

8.5. Virtual Machine for the Java™ Platform on ClearPath OS 2200 JProcessor (JPJVM)

The Virtual Machine for the JavaTM Platform on ClearPath OS 2200 JProcessor is the

follow-on product of OS 2200 JVM and contains Java SE 6 and 7. This product runs on

OS 2200 JProcessor, and provides improved throughput.

JPJVM requires an OS 2200 JProcessor Specialty Partition for execution. Java SE

levels 6.0 and 7.0 are provided in the same release DVD. They are based on Oracle

levels. Anyone who has existing Java applications will benefit immediately from the

performance and reliability in Java SE 6. This release delivers dramatic out-of-the-box

benefit without any coding changes or recompilation coupled with expanded

monitoring and diagnostics capacities built into the platform. You simply need to run

the existing Java applications on this latest release.

Application management has been enhanced by improvements made to the JMX

Monitoring API. There are many enhancements to serviceability, including making the

jconsole more user-friendly. Java SE 6 significantly enhances the ability of diagnosing

memory problems. The HotSpot VM provides the ability to request a heap dump (on

demand) from the jmap tool programmatically.

General Features

JPJVM provides the following features:

• Java 6 and 7

• Debug launchers for jps, jinfo, jmap, jstack, jdb, jstat, jstatd and jsadebugd

• Cipher Installation

Enables you to install Cipher API on the JProcessor during the JPJVM installation.

• Apache Portable Runtime Installation

Provides scripts for the automatic installation of the Apache Portable Runtime on

the JProcessor when JPJVM is installed.

• Supports LETS-J character set for Japanese customers.

• jptransfer launcher

• The new installation mode, JP$2200, performs only the OS 2200 server portion of

the JProcessor JVM installation

• New installations scripts to allow installation on a specified JProcessor.

• JProcessor Routing

• Restart Handling

• Mounting of Shares

It is no longer necessary to specify OS 2200 CIFS shares using Administration

Console or the icmount utility. The environment is created for the user when the

JPJVM is executed.

• Dtraceic Interconnect Tracing

ClearPath OS 2200 JProcessor

7850 5252–018 8–7


The document Virtual Machine for the Java Platform on ClearPath OS 2200

JProcessor User Guide (3839 3088) is available for this product on the Unisys Product

Support Web site.

8.6. ClearPath OS 2200 JProcessor

The Unisys ClearPath OS 2200 JProcessor (JProcessor) is a cost-effective environment

designed for Java applications running under OS 2200 operating system on a ClearPath

server. The Java execution is done on an embedded specialty partition that is

optimized for the Java environment.

The JProcessor supports the Java™ Platform, Standard Edition (Java SE) runtime

environment and the Java™ Platform, Enterprise Edition (Java EE). The Java capability

is provided by the JPJVM product running on the OS 2200 JProcessor. The Java SE

runtime environment provides the libraries, the Java virtual machine, and other

components to run portable applications written in Java programming language. Java

EE is an industry standard for developing portable, robust, scalable, and secure

server-side Java applications. Java EE is built on the solid foundation provided by Java

SE. The OS 2200 JProcessor is tightly integrated with the ClearPath OS 2200 server

and enables Java applications to take advantage of the high level of performance,

reliability, and security of the OS 2200 operating environment.



Support Web site:

• ClearPath OS 2200 JProcessor Administration Console Help (3839 3104)

• Business Information Server Resource Adapter for the Java Platform

Developer's Guide (3839 6529)

• CIFS for ClearPath OS 2200 User, Programmer, and Administrator Reference

Manual (7859 6137)

• ClearPath OS 2200 JProcessor Release Notes 2.0 (8207 2828)

• ClearPath Specialty Engine for OS 2200 Configuration Guide (3839 3005)

• Eclipse IDE for OS 2200 Application Development Guide for Java EE Projects

(3839 3831)

• Eclipse IDE for OS 2200 Installation Guide (4729 2107)

• Getting Started with Java Technologies (3839 3096)


Platform Studio Help (3827 9295)


Platform User’s Guide (6898 5852)

• OS 2200 Transaction Resource Adapter for JavaTM User's Guide (4729 1992)

• JBoss® Enterprise Application Platform for ClearPath® OS 2200 Installation,

Administration, and Programming Guide (3826 6425)

Network Database Server Resource Adapter for the Java Platform

8–8 7850 5252–018

• Network Database Server Resource Adapter User Guide (3850 8362)

• Open Distributed Transaction Processing Administration Guide Volume 2

Building Applications (7833 5080)

• Open Distributed Transaction Processing Programming Guide (7833 5049)

• Relational JDBC Driver for ClearPath OS 2200 User Guide (7862 7395)

• Virtual Machine for the Java Platform on ClearPath OS 2200 JProcessor User

Guide

(3839 3088)

8.7. Network Database Server Resource Adapter for the Java Platform

The Enterprise Network Database Server Resource Adapter for the Java™ Platform

(DMS-RA) software product provides a standards-based Java interface to Enterprise

Network Database Server for ClearPath OS 2200. It opens DMS data to stand-alone

Java applications and J2EE™ components such as EJBs and servlets.

Enterprise Network Database Server Resource Adapter for the Java™ Platform has

server and client components.

The server component is the JDMS Server, and it runs on the ClearPath OS 2200

platform that contains the Enterprise Network Database Server for ClearPath OS 2200

database.

The client components are the DMS-RA and the Class Builder. The DMS-RA

implements the contracts defined in the J2EE Connector Architecture Specification

and the custom class interface that an application uses to interact with DMS. The

Class Builder creates custom Java classes from the XML produced by SDDL when

HOST LANGUAGE IS JAVA is specified. The client components run on your Java

platform.

Note: Changes were included in level 20R1 of Enterprise Network Database Server

for ClearPath OS 2200 to support Network Database Server Resource Adapter for

the Java™ Platform.

General Features

DMS-RA provides the following features:

• Supports XA transaction

• Enhanced version checking

• Supports Fill character configuration property

• “How To” section of the user guide

• Supports KEEP lock method

A Java application keeps a lock on a record so that other applications cannot

update the record.

Relational JDBC Driver for ClearPath OS 2200

7850 5252–018 8–9

• Supports methods to determine max and min values for repeating items

A Java application can determine programmatically the minimum and maximum

number of occurrences allowed for a repeating item.

• Supports LETS-J and Kanji character sets for Japanese customers

• Supports IPv6 (available when executed with COMAPI and CPComm levels that

support IPv6)

• Supports MODIFY command

The MODIFY command updates the record items set by an application in the DMS

database.

• A unique thread ID is added to DMS-RA server trace displays. This helps in

matching up the threads when viewing the UDSC and DMS-RA server traces.

• Converts data in DMS records to XML.

• Determines the state of a DMS record.

• Allows access to alternate database field definitions using a REDEFINES clause in

the Java host language subschema


The document Network Database Server Resource Adapter for the Java™ Platform

User Guide (3850 8362) is available for this product on the Unisys Product Support Web site.

8.8. Relational JDBC Driver for ClearPath OS 2200

Relational JDBC Driver for ClearPath OS 2200 is a software package that enables Java

programs of all types to communicate with databases managed on ClearPath OS 2200

systems under the Relational Database Server. It provides Java™ Database

Connectivity (JDBC) access to the Relational Database Server for ClearPath OS 2200.

Relational JDBC Driver has server and client components.

The server component runs on the ClearPath OS 2200 platform that contains the

Relational Database Server database. The server is not written in the Java

programming language, and for that reason it is not necessary to have a Java Virtual

Machine running on the ClearPath platform.

When an application participates in a global transaction, the server component runs

under Open DTP, and is referred to as the JDBC XA Server. When the server

component handles local transactions, it is referred to as the JDBC Local Server.

The client component consists of the Java class files for JDBC. The client is written in

the Java programming language and uses Java Networking to communicate with the

server component of the Relational JDBC Driver.

When used in a two-tier client/server environment, the client component runs on the

platform of the Java calling program. When used in a three-tier environment, the client

component runs on the same platform as the application server.


8–10 7850 5252–018

General Features

Relational JDBC Driver for ClearPath OS 2200 provides the following features:

• Tighter RDMS integration and performance improvements including:

− JDBC Object reuse

− Get Description

− Auto-Commit

− JDBC Admitter

− New SET statement (SET SKIPGENERATED [ON|OFF])

− RDMS RS MetaData reuse

− RDMS temporary tables

− Stored procedures returning JDBC results sets (multiple result sets)

• Updated Hibernate RDMS Dialect

• Get/Set methods with calendar argument

• SSL port connections support

• Product diagnostics improvements including file cycle modification on tracing and

improved error handling

• JDBC 3.0 BLOB interface support

• JDBC XADataSource and XAConnection support

• JCA 1.5 support

• JDBC Server restart resiliency

• Multiple levels of RDMS

This feature enables the RDMS JDBC product to support multiple levels of RDMS.

Previously, you had to upgrade your RDMS level to take advantage of the features

in the latest level of the RDMS JDBC product. Now you can use the latest level of

RDMS JDBC with any recent level of RDMS. This means that you can use one

level of RDMS JDBC although you upgrade your RDMS database system to a new

level. Typically, RDMS JDBC supports the current level of RDMS and at least one

level earlier.

• Updatable cursor

• Removes restriction on Secopt-1 security

• Full IPv6 support (available when executed with COMAPI and CPComm levels that

support IPv6)

• Enhanced JDBC DataSource implementation


7850 5252–018 8–11

• Scrollable cursors

• JDBC PreparedStatement performance enhancement

This feature allows a JDBC PreparedStatement or Statement object to utilize

RDMS parsing and optimization information gained from previous SQL statement

executions, providing a performance enhancement when an SQL command is

executed repeatedly.

• JDBC XA server increased server concurrency

• JDBC XA database server transactional thread reuse

• JDBC CharSet enhancements


The document Relational JDBC Driver for ClearPath OS 2200 User Guide (7862 7395) is available for this product on the Unisys Product Support Web site.


8–12 7850 5252–018

7850 5252–018 9–1

Section 9 Operating Environment Products

This section describes the operating system as well as products that closely support

its functions and are bundled as part of the Integrated Operating Environment (IOE)

and the Operating System Group (OSG).


• Checkpoint/Restart (CKRS)

• CIFS for ClearPath OS 2200

• Executive (Exec)

• Executive Separately Packaged Features

• Extended Transaction Capacity (XTC)

• Interactive Processing Facility (IPF 1100)

• Open Programming Environment (OPE)

• Operations Sentinel Basic Edition

• Pause Disk I/O for ClearPath OS 2200

Checkpoint/Restart

9–2 7850 5252–018

9.1. Checkpoint/Restart

Checkpoint/Restart (CKRS) helps developers control the operating environment by

enabling the developer to stop and restart a program at a particular point. This is

useful, for example, to ensure that the developers have information needed to

reconstruct their environment after an interruption or to gather and retain results of

testing.

The CKRS system consists of two routines: checkpoint and restart. Checkpoint saves

information about the current operating environment of a program and/or computer

run. Restart uses this information to resume processing of the program or run at the

point it was halted by checkpoint. The two routines correspond to the checkpoint and

restart functions.

• Checkpoint

The point in a run at which processing is momentarily halted to make a magnetic

tape record of the contents of working storage, the position of input and output

tapes, and other variables. A run is checkpointed so that, if an error or malfunction

occurs, it can be restarted from the last checkpoint, instead of from the beginning

of the run.

• Restart

To return to a previous checkpoint and continue a run from there, instead of

starting over from the beginning. Runs are often restarted after an error or

malfunction occurs.

Although checkpoint and restart operate independently, each complements the other.

In addition, restart includes the restart initialization processor (RIP) that provides a

variation of the restart procedure.

CKRS was originally created when batch runs executed for extended periods of time

and when system stability was not assured. CKRS provided the means of creating

recovery points within extensive batch runs, which in turn saved both recovery time

and processing resources. While both the existence and time of batch runs has

decreased, and system stability has increased dramatically, it is still a viable tool for

use in selected processing environments.

There are several reasons to use CKRS to control an operating environment:

• To obtain information about the environment, in the event of a system failure

• To provide appropriate information to reconstruct an environment and resume

processing from the point of interruption

• To gather and retain results of testing, without having to repeat test schemas

unnecessarily

• To promote a uniform method of segmenting lengthy computations over several

time periods

• To interrupt a computation at a logical point and restart it at another logical point

CIFS for ClearPath OS 2200

7850 5252–018 9–3


The document Checkpoint/Restart (CKRS) Programming Reference Manual


9.2. CIFS for ClearPath OS 2200

The Common Internet File System (CIFS) for ClearPath OS 2200 enables access to

OS 2200 files through standard internet protocols. CIFS also includes a client capability,

enabling OS 2200 programs to directly access files on other systems that support the

SMB protocol, such as all Windows platforms and Linux systems running a Samba

server.

CIFS permits direct access from the Windows Explorer to files stored in OS 2200. This

enables you to do the following:

• Move, copy, delete, and display properties of the OS 2200 files.

• Edit files with Windows Notepad, Microsoft Word, image processors, and so on,

and save changes to the files.

• Copy or move files, using the Windows drag-and-drop feature, between your

workstation and OS 2200.

• Create, update, view, and extract zip files on the OS 2200 system.

When compared to the CIFS implementations on other platforms, CIFS for ClearPath

OS 2200 is very secure. It strictly enforces every aspect of the OS 2200 security

policy. CIFS for ClearPath OS 2200 incorporates programming practices that limit

exposure to application security vulnerabilities. This reduces undetected buffer

overflows and provides better handling of unanticipated requests.

CIFS for ClearPath OS 2200 is a standard remote file access system that enables you

to treat OS 2200 as a Windows file server. The CIFS specification was created by

Microsoft Corporation and is based on the existing Server Message Block (SMB)

protocol. SMB is a client/server request/response protocol for sharing files, printers,

serial ports, and communication abstractions.

With this implementation of CIFS on ClearPath OS 2200 servers, OS 2200 files can be

manipulated from a workstation using the standard hierarchical directory structure in

Windows Explorer. CIFS provides access to all OS 2200 files and elements through a

special directory: /os2200. During CIFS initialization, all OS 2200 files (except certain

system files) are automatically added to the /os2200 directory. CIFS monitors changes

to the OS 2200 file environment and updates the /os2200 hierarchy accordingly.


9–4 7850 5252–018

Components

CIFS includes the following components:

• CIFS Host Infrastructure (CIFSHI)

This component includes the communications layers necessary for a remote client

to use CIFS on the OS 2200, as well as the file system structure and host APIs.

The communication capabilities of CIFSHI uses SMB protocols to provide access

to existing OS 2200 files from most SMB clients, such as Windows Explorer.

• CIFS Library (CIFSLIB)

This component consists of a UC- and UCOB-callable layer of interfaces to CIFSHI

as well as I/O stream-handling functions.

• CIFS Utility (CIFSUT)

This component provides a simple command-line interface to CIFS capabilities.

• ZIPUT Processor

This command line utility enables you to create, update, view, and extract zip files

on OS 2200 systems.

CIFS interfaces with the Exec are invisible to you. You access CIFS utilities and

application program interfaces by calling them as functions from a C program.

Security Features

CIFS for ClearPath OS 2200 is not subject to several security vulnerabilities that are

common on other platforms:

• CIFS for OS 2200 is less prone to user errors that result in unprotected shares

being exposed. Instead of one layer, CIFS for ClearPath OS 2200 has two layers of

security:

− The OS 2200 security policy

− The CIFS file directory permissions (visible in Windows Explorer)

To create an unprotected share, you must create a public OS 2200 file with read

and write permissions, and a share and folder that enables public read and write

permissions. CIFS for OS 2200 defined folders and files, and OS 2200 files, are not

visible through the network unless a share point was explicitly defined.

• Folders and files created under CIFS for ClearPath OS 2200 are, by default, private,

not public as on other operating systems.

• Unlike other implementations, CIFS for ClearPath OS 2200 does not support

anonymous login or null sessions.

• Vulnerabilities caused by undetected buffer overflows are less likely because of

strict programming practices and reviews by security experts.

• CIFS for OS 2200 does not broadcast or announce the presence of the OS 2200

host or its shares to the network.

Compared to other network access methods, CIFS sessions are more secure than FTP

because a password is never sent over the network. CIFS also does not use any form

of embedded scripting, so CIFS is less vulnerable to attacks that rely upon scripts.


7850 5252–018 9–5

General Features

The following are the CIFS features.

• CIFS 24x7 operation

Continuous availability of CIFS file access.

• CIFS filecopy() API

• Automatic creation of large element program files (LEPF)

CIFS supports references to and usage of LEPF. The LEPF format can contain

symbolic and omnibus elements with text larger than 262,143 sectors.

• Automatic and manual packing of program files

• Removes the need for customers to periodically pack the underlying program files

for CIFS directories.

• Long encrypted passwords

CIFS supports up to 18-character encrypted case-sensitive and insensitive

passwords.

• Configurable wait times for rolled out and exclusively assigned files

• IPv6 support via the bump-n-the-API (available when executed with COMAPI and

CPComm levels that support IPv6)

• Supports multiple line terminator formats (LF, LF/CR, CR)

• Resilient interaction of CIFS with monitor services

• Binary file compatibility with cpFTP

• Supports CIFSUT cat command

• Multiple f-cycle removal using CIFSUT rm command

• Enhanced ZIPUT archive file naming

• Supports CIFS TRACE keyin and BRKPT keyins

• Supports CIFSUT mkfifo command

CIFS creates one or more new first-in-first-out (FIFO) files.

• Configurable file cache size limit and more efficient memory usage

• Permits change of file type

• Allows copying of files with _UNKNOWN set

• Journal file size restriction and monitor usage capability

• Full IPv6 Support (available when executed with COMAPI and CPComm levels that

support IPv6)

• Background Run Restart Notice

• Increase the CIFS inode limit

• ACR Inheritance

• NT status codes to prepare for SMB2

• User registration with CIFS

Executive

9–6 7850 5252–018

• Avoid Size Scanning


The document CIFS for ClearPath OS 2200 User, Programmer, and Administrator

Reference Manual (7859 6137) is available for this product on the Unisys Product Support Web site.

9.3. Executive

Exec (also known as the Executive, Executive System, Exec-8, or Exec) is a software

supervisor that controls the OS 2200 system operating environment. Largely resident

in memory, Exec processes user runs, controls files, manages system resources, and

performs input/output operations for you. First introduced in 1966 on the Univac 1108

as the successor to the Exec II operating system, the Exec provides the interface for

true multithread processing.

Exec is the principal interface between the user and the system as a whole. It is

responsible for such functions as time and space allocation of system resources;

first-level I/O control and interrupt answering; logging of system accounting data;

first-level debugging assistance; and protection against undesired interaction of users

with other users of the system. By presenting a relatively simple interface, it enables

the programmer to use the system easily, while relieving concern for the internal

interaction between the program and other coexistent programs.

Multiple Modes of Operation

The technical capabilities of the Exec cover a great variety of data processing

activities. Its design offers versatility to handle batch processing, demand processing,

and real-time processing; using multiprogramming and multiprocessing techniques. An

installation that is not interested in making use of the full range of capabilities can

specify component features to be eliminated at system generation.

Batch Processing

The Exec eases run preparation and submission, shortens job turn-around time, and

reduces the need for operator intervention and decisions. Batch jobs can be submitted

for processing from a variety of remote terminals, as well as from central site

equipment.

Demand Processing (Time Sharing)

The time sharing mode of operation accommodates simultaneous requests and

demands from users at numerous remote inquiry terminals operating in a demand (or

conversational) mode. All facilities available to the batch processing user are also

available in the demand mode but the Exec permits the demand user additional

flexibility in the statement and control of individual runs. For example, when an error is

made, the user simply corrects it online and proceeds rather than suffering the turn-

around cycle inherent in batch processing. The demand user can interact with the

system at various levels that include direct communications with either the Exec, a

user program, or with a conversational processor, such as BASIC.

Executive

7850 5252–018 9–7

Real-Time Processing

The Exec's efficient scheduling and interrupt processing features work together with

communications software to provide an environment for the operation of real-time

programs.

Transaction Processing Interface

Another type of remote inquiry terminal processing provided by the Executive System

is transaction processing. Selected programs can be executed on request from

remote inquiry terminals. While the types of operations performed in this processing

mode are more limited than in the demand processing mode, the number of remote

terminals and the number of inquiries per second are much greater. The types of

operations enabled are prespecified to the Executive System, either by Unisys or by

the site.

Exec contains integrated transaction monitoring capabilities, known as TIP

(Transaction Interface Package). The characteristics of the transaction processing

capabilities can be custom tailored on a site-by-site basis using system generation

parameters.

Multiprogramming and Multiprocessing

Runs can be initiated at remote and central sources. The efficient multiprogramming

and multiprocessing techniques of the Exec enable the simultaneous processing of

many different runs at different stages of activity. Input, processing, and output can all

be occurring simultaneously, thus enabling efficient operation.

Utilization of Mass Storage

The Exec ensures effective and efficient utilization of mass storage devices. This

enables sites to simplify operations, eliminating many of the errors that have

accompanied the use of large scale software systems and considerably improves

overall operating efficiency.

Permanent data files and program files are maintained on the mass storage devices,

with full facilities for modification and manipulation of these files. Security measures

are established by the Exec to ensure that files are not subject to unauthorized use.

The Exec automatically relocates infrequently used files to magnetic tape as unused

mass storage space approaches exhaustion and retrieves and restores them without

any need of user intervention when they are requested.

Functional Areas

The Exec is logically divided into a number of areas that correspond to key aspects of

functionality. These areas include the following:

• Security (SEC)

• Processor and Control (PCN)

• Input/Output (IO)

Executive

9–8 7850 5252–018

• Main Storage Management (MSM)

• File Control (FILE)

• Transaction Interface Processing (TIP)

• Miscellaneous Interface Processing (INTF)

• Exec System Capped Functionality (ESC)

These functional areas are further classified in component areas. For example, the

security function area is further broken down into the following five component areas:

• Security

• Quota

• TIP File Security

• System dynamic configuration

• Exec utilities.



Support Web site:

• Exec System Software Operations Reference Manual (7831 0281)

• System Console Messages Reference Manual (7833 3275)


(7830 7899)

• Exec System Software Installation and Configuration Guide (7830 7915)

• Exec System Software Administration Reference Manual (7831 0323)

• Exec System Software Common Banks Programming Guide (7830 7386)

• Executive Control Language (ECL) and FURPUR Reference Manual (7830 7949)

• System Log Operations and Support Reference Manual, Volume 1: Introduction

Through Error Log Type 628 (7831 0315)

• System Log Operations and Support Reference Manual, Volume 2: Error Log

Type 801 Through Type 17650 (3839 6347)

• Multi-Host File Sharing (MHFS) Planning, Installation, and Operations Guide

(7830 7469)

• Unit Duplexing Planning, Installation, and Operations Overview (7830 7592)

• Exec System Software Executive Control Language (ECL) Programming

Quick-Reference Guide (7830 9945)

• Exec System Software Executive Requests Programming Quick-Reference

Guide (7830 9952)

Executive Separately Packaged Features

7850 5252–018 9–9

9.4. Executive Separately Packaged Features

The Exec separately packaged features are distributed on a separate tape.

The following are the Exec separately packaged features:

• ARC

The Automatic Recovery of Components (ARC) provides automated recovery of

host's registered components after component failure or host failure. Components

register recovery runstreams to be executed upon host failure or loss of

component heartbeat. ARC consists of the Application Interface bank (AIB) and the

monitor run (ARC).

• CARTIS

Cartridge Tape Interface Software (CARTIS) supports the 5073/0099 cartridge tape

subsystem. It provides the basic tape functions of the standard tape handler and

added functions that use the 5073 features.

CARTIS includes the user-requested software to handle buffer operations and

new status indications from the subsystem. It also supports subsystem and tape

drive assignment configurations.

When configured, CARTIS becomes an integral part of the Exec I/O complex. It

supports 5073 I/O requests from user programs and the Exec in the same way

other I/O requests are handled.

Note: CARTIS software must be ordered for each cartridge tape controller it

supports if the device is obtained from a source outside of Unisys. This applies

whether or not the device is a Unisys model or a model from another vendor.

• CARTLIB

Cartridge Library software (CARTLIB) supports the CTS5118 (18-track) and CTS5136

(36-track) cartridge tape subsystems from StorageTek. These subsystems might

be free-standing or associated with the CLU1000 and/or CLU6000 libraries. If the

subsystems are associated with these libraries, the following software must be

used with CARTLIB:

− Client System Component (CSC), the host-based library control software

− Automated Client Server Library Software (ACSLS), the software used in the

UNIX (SUN) server

Note: CARTLIB and associated software are third-party product releases

associated with the SB release. They have separate ordering and licensing

requirements.

• DMPLIB

The Dump Analysis Library contains the DAP functions that are used to edit Exec

structures from a system dump during dump analysis. DMPLIB also contains

runstreams and SSG skeletons used to perform dump analysis, as well as utilities

used to manage dump files.

• FBCIS

Fixed Block Compatible Interface Software (FBCIS) is the implementation of the

fixed-block rotating mass storage (FBRMS) FIPS standard for mass storage

subsystems.


9–10 7850 5252–018

• MHFS

Multi-Host File Sharing (MHFS) enables multiple hosts to access files on one or

more shared disk devices. Shared access is available for both fixed and removable

disk devices. The MHFS environment includes the following capabilities:

− Shared master file directory (MFD) in addition to the local MFD.

− For ECL statements, an additional field that enables you to specify and change

implied and default directoryIDs for a filename to indicate which MFD in a

shared system contains a file.

− Keyins that enable the operator to change the MHFS configuration by bringing

hosts or shared devices up or down in the file-sharing environment.

− Keyins that send messages or unsolicited keyins to other hosts.

− Supports the following alternative communication/locking device

environments:

ο MHM (multi-host messaging) Environment (default) makes use of the

extended processor complex (XPC-L).

ο Network Environment (alternative or fallback option) makes use of the

Host LAN Controller (HLC) or Channel Adaptor (CA) devices.

• MMGR

Media Manager (MMGR) is a system interface that enables the use of a tape

management system supplied by vendors other than Unisys. MMGR is an ILES

installed with SOLAR without the need for an Exec build.

• MSCP

The Monitor Services Control Program (MSCP) enables user programs to monitor

certain system events as they occur. System events can be hardware or software

interrupts or conditions that are logged to the system log file. By interfacing with

MSCP, the user programs can receive copies of the log entries as they occur. The

entries can then be used for such activities as providing hardware diagnostic

information or monitoring console message traffic.

Note: MSCP is released as both a separately installable (SOLAR installable)

feature and as a preinstalled feature in SYS$*LIB$. Clients with Security Option

3 must use the separately installed version.

• SCSITIS

The SCSI Tape Interface Software (SCSITIS) is the handler for the 2145 and the

USR5073 tape devices.

• Security Packages

Unisys offers four security packages. These packages yield a variety of security

configurations so a site can provide the exact protection needed. The security

packages are

− Fundamental Security

− Security Option 1

− Security Option 2

− Security Option 3, which includes

ο Security Option 3 Controlled Access Protection Environment


7850 5252–018 9–11

ο Security Option 3 Trusted Environment

Each security package builds on the previous one. For example, if you order

Security Option 2, you also receive Security Option 1. Or, if you order Security

Option 3, you also receive Security Options 1 and 2.

See the Security Packages topic for more detail on the security options.

• SINCH

The Unisys Interconnect Channel Handler (SINCH) supports both the Network

Systems HYPERchannel Model Network Adapter and the Network Systems

HYPERchannel DX N220 adapter. The adapter is connected to these systems by a

block multiplexer channel (BMC). Through the use of a standard I/O interface, the

user can initialize a session, read and write data, and terminate the session. SINCH

supports three types of software-defined devices:

− The HYPNET device is defined at system generation by stream generation

statements (SGS). This type of device has its message header built by the I/O

handler on output and has the message header verified on input for a correct

FROM address. Each of these devices is either an output or input device and

has a preassigned destination (output) or sender (input).

− The OWN HEADER device can be any device other than a HYPNET device. The

OWN HEADER device controls its headers on input and output. Thus, it

constructs the header on output and verifies it on input. It can send or receive

from any adapter device in the network.

− The TEST device can be any device on that adapter. It also builds and verifies

its message headers and can send or receive from any adapter device in the

network. Only one TEST device can be active on an adapter at any given time.

• SIPIPM

The Software Instrumentation Package Internal Performance Monitor (SIPIPM)

records the raw SIP data in the system log file. This data includes the values from

the instruction counters that are used by SIP to sample system activity and collect

data on that activity.

• SPAIR

Software Product Application Initialization and Recovery (SPAIR) is the installation

identifier for the utility used by recovery runstreams to initialize, defer, or recover

TIP File Control, Step Control, and Audit Control within a runstream. SPAIR can be

executed manually or within a recovery runstream in either batch or demand

mode.

• TAVR

Tape Automatic Volume Recognition (TAVR) supports the premounting and

postmounting of tape volumes.

• TIPUTIL

Transaction Processing Utilities (TIPUTIL) are the utility programs and subroutines

of TIP, a modular extension of the Exec. Through the use of predefined transaction

programs, TIP provides a high-performance transaction management system.

• Unit Duplexing

Unit Duplexing is a hardware configuration that reduces system vulnerability to

mass storage failure by providing an associated backup disk pack for each disk

pack specified as unit-duplexed.


9–12 7850 5252–018

If a unit specified as duplex is requested to perform I/O, writes are made

automatically to both units and reads can be taken from either. The contents of

both disk packs are kept identical, bit for bit.

• Virtual Tape Handler (VTH)

The Virtual Tape Handler (VTH) simulates tape drives using mass storage (fixed or

removable packs). VTH is a separately priced Exec feature that gives you the

ability to reduce tape volume usage and operator interaction to mount tapes if you

use tapes for more than just mass storage backup and transaction auditing.

In general, programs cannot tell the difference between a virtual tape and a real

tape. However, the File Administration System (FAS) cannot use virtual tape as the

backup medium because of the problems that occur if the File Administration

System needs to use more than one media type to reload files. Also, the system

default tape type cannot be virtual tape because the system uses this tape type

for assigns that need physical tape media.

• XPCEXEC

XPCEXEC is the installation identifier for the extended processing complex—

locking (XPC-L) software that is installed in the Exec.

• XTCEXEC

XTCEXEC is the installation identifier for the Extended Transaction Capacity (XTC)

software.



Support Web site:

• Exec System Software Operations Reference Manual (7831 0281)

• System Console Messages Reference Manual (7833 3275)


(7830 7899)

• Exec System Software Installation and Configuration Guide (7830 7915)

• Exec System Software Administration Reference Manual (7831 0323)

• Exec System Software Common Banks Programming Guide (7830 7386)

• Executive Control Language (ECL) and FURPUR Reference Manual (7830 7949)

• System Log Operations and Support Reference Manual Volume 1 (7831 0315)

• Multi-Host File Sharing (MHFS) Planning, Installation, and Operations Guide

(7830 7469)

• Unit Duplexing Planning, Installation, and Operations Overview (7830 7592)

• Cartridge Library (CARTLIB) End Use Guide (7844 8701)

• Cartridge Library (CARTLIB) Technical Bulletin (7844 8719)

• Exec System Software Executive Control Language (ECL) Programming

Quick-Reference Guide (7830 9945)

• Exec System Software Executive Requests Programming Quick-Reference

Guide (7830 9952)

Extended Transaction Capacity

7850 5252–018 9–13

9.5. Extended Transaction Capacity

Extended Transaction Capacity (XTC) is a grouping of software features that provide

clustering of up to four hosts to provide increased processing capacity and increased

system resiliency through the use of an external lock manager for TIP and UDS

database environments. The XTC feature grouping consists of the following features:

• XTCEXEC

• Multi-Host File Sharing (MHFS)

• Automatic Recovery of Components (ARC)

In addition, the extended processing complex—locking (XPC-L) is required as well as

the XPCEXEC feature in Exec. These are not part of the XTC feature grouping.

Benefits of Using XTC

Basic Transaction Processing (TIP) and Universal Data System (UDS) systems use only

one host. In an XTC environment, multiple hosts can share TIP and UDS databases on

shared mass storage and these hosts can concurrently access and update the

databases. The extended processing complex—locking (XPC-L) handles the locking of

the shared files and coordination of the multiple hosts in the transaction environment.

The end result is a system that can process many more transactions per second than

a one-host system. However, in multihost environments, just as in multiprocessor

environments, there is a loss of overall efficiency, referred to as a mutihost factor, as

additional hosts are added to the configuration. The multihost factor is dependent on

many elements and is typically a 5- to 10-percent loss of efficiency.

Increased capacity, when stated as transactions per second, is dependent on the

design of the application and the data model involved. Instructions per transaction, I/O

to instruction ratio, and number of database accesses affect the single-host

transaction rate and the increase resulting from XTC. The increased capacity seen

from incorporating one, two, or three additional hosts is linear (additive). New hosts

can be added or upgraded into an existing environment.

Resiliency is increased by allowing one or more of the active hosts in an XTC

environment to leave the environment, either through a planned outage or system

failure, without impacting the remaining hosts. Standard recovery procedures are used

to return a stopped host to the XTC environment while the active hosts continue to

process transactions.

XTC provides as many choices for database management as in a single-host system,

but with greatly increased database accessibility.

A recoverable transaction environment can be maintained across XTC hosts for user

application programs and the following shared databases:

• UDS databases formatted by the Repository for ClearPath OS 2200 and maintained

by the UDS online data manager for one or more of the UDS data managers,

Enterprise Network Database Server for ClearPath OS 2200, Enterprise Relational

Database Server for ClearPath OS 2200, or Shared File System

Extended Transaction Capacity

9–14 7850 5252–018

• TIP databases managed by TIP File Control

Components

The following XTC components enable hosts to share databases safely and efficiently

during system operations:

• Multi-Host File Sharing (MHFS) lets multiple XTC hosts share the files that make up

the shared databases. MHFS is the software component that provides I/O access

from each host to the shared database. MHFS is included in the XTC feature

grouping.

• The XPC-L is a hardware device connected to all hosts in an XTC system. In an

one-host system, file and record locking is handled through software locking by

TIP File Control for TIP files, or by UDS for UDS or UDS/TIP files. In an XTC system,

the XPC-L provides hardware locking and supporting software outside the hosts to

enable access to shared databases regardless of the database type (TIP or UDS).

• XTCEXEC is a feature that enables concurrent access from multiple hosts to a

common database locked by XPC-L. This concurrency of access increases system

throughput.

− For shared TIP databases, XTCEXEC lets TIP File Control work with XPC-L to

control database access and handles the host-to-host communications

necessary for TIP file sharing and for transaction scheduling across hosts.

− For shared UDS or UDS/TIP databases, XTCEXEC lets Universal Database

Control work with XPC-L to control database access and handle the

host-to-host communications for UDS file sharing and cache memory

updating.

• ARC provides for the recovery of components such as the Message Control Bank

(MCB) and for the recovery of application groups on each host. The ARC feature

includes a monitor run and an application interface bank (AIB) that registers and

execute runstreams performing local and component recovery when needed. The

ARC feature is part of the XTC feature grouping.


The document ClearPath OS 2200 Integrated Recovery Reference and

Administration Guide for Multihost Environments (7831 0919) is available for this product on the Unisys Product Support Web site.

Interactive Processing Facility

7850 5252–018 9–15

9.6. Interactive Processing Facility

The Interactive Processing Facility (IPF 1100) is an interface to OS 2200 that makes it

easier for you to develop application programs and to use the software and databases

available on the server. The IPF 1100 interface is an easy-to-learn, keyword-oriented

command language that can be used by both novice and experienced users.

The Interactive Processing Facility (IPF 1100) is an interactive and batch processing

system that enables you to develop application programs and to use the processors

and databases already available on the system. IPF 1100 provides an interface to the

OS 2200 operating system through a keyword-oriented command language that is

designed to enable access to the computer system by all types of users, including

novice end users and experienced programmers.

The main features of IPF 1100 are the following:

• An easy-to-learn command and response language

• The ability to create command procedures using flow-of-control statements,

argument passing, and canned run streams

• Full-screen and line-by-line modes of operation

• Completion notices to reassure you that IPF 1100 has processed your request

• Online assistance with commands or error messages at any time

• An SQL interface to Relational Database Server databases

• Direct access to the entire distributed data processing network

IPF 1100 includes the following components:

• Control

Provides the environment and control structures necessary to use the other IPF

1100 components.

• Command Language

Provides the basic command services that enable IPF 1100 users to communicate

with the operating system programs, work with files, manipulate user-defined

variables, and redirect terminal input and output. The Command Language has a

consistent format, with keywords, a set of consistent abbreviations for commands

and keywords, and clear, concise, messages and command responses (known as

completion notices).

• EDIT 1100

Provides an easy-to-use text editor for making changes to the workspace while

using IPF 1100. The workspace is a temporary area into which a file is copied that

is to be worked on using IPF 1100 Command Language. When changes are

complete, the workspace must be copied back to the original file (using Command

Language). EDIT 1100 can be used to manipulate all types of programs, data, or

document text. It has both a full-screen and a general-editing (that is, line by line)

mode. The full-screen commands are powerful and very easy to use. Together

with the general-editing commands, they provide a total editing facility.

Interactive Processing Facility

9–16 7850 5252–018

• Procedures

Provides additional command language flexibility by enabling IPF 1100 users to

define and store a group of IPF 1100 commands so they can be executed as one

command. IPF 1100 Procedures enable debugging, specifying different paths to

take depending on the values of certain variables (this is known as flow of control),

and iteration (that is, repetition) of a group of commands.

• User Assistance (UA 1100)

Provides online assistance and explanations of error messages, commands,

system variables and functions. UA 1100 also includes tutorials about IPF 1100. UA

1100 can be used to perform the following tasks:

− Learn how to use the IPF 1100 commands, system functions, system variables,

and online tutorials.

− Review the new features of IPF 1100.

− Explain an error message.

− Learn the keyword parameters associated with a command.

− Learn the values associated with a system variable or system function.

− Review the error messages IPF 1100 displays during your current session.

− Build a template so you can construct a command by filling in values for the

keyword parameters.

• IPF Structured Query Language (IPF SQL)

Provides a SQL interactive ad hoc query interface to relational databases via the

IPF 1100 environment. IPF SQL can display and update relational databases

maintained by the Relational Database Server.

IPF 1100 provides distributed processing capabilities through the following OS 2200

products:

• Distributed Data Processing File and Job Transfer (DDP-FJT)

DDP-FJT controls the movement of files and jobs in a distributed network. By

entering IPF 1100 commands, users can create, copy, and delete files on other

hosts in the network, as well as submit jobs for processing.

• TCP/IP Application Services (TAS)

TAS enables OS 2200 hosts to participate in networks that use the Transmission

Control Protocol/Internet Protocol (TCP/IP) for inter-host communications. For IPF

1100 users, TAS provides mail processing, using the simple mail transfer protocol

(SMTP), and file transfer, using the file transfer protocol (FTP).



Support Web site:

• Interactive Processing Facility (IPF 1100) EDIT 1100 User's Guide (7833 3812)

• Interactive Processing Facility (IPF 1100) Command Language User's Guide

(7833 3788)

• Interactive Processing Facility (IPF 1100) Procedures User's Guide (7833 3770)

Open Programming Environment

7850 5252–018 9–17

• Interactive Processing Facility (IPF 1100) User Assistance (UA 1100) User's

Guide (7833 3762)

• Interactive Processing Facility (IPF 1100) Administration Guide (7833 3754)

• Interactive Processing Facility (IPF 1100) User's Quick-Reference Guide

(7833 3804)

• Interactive Processing Facility (IPF 1100) User's Reference Handbook

(7833 3820)

• Interactive Processing Facility (IPF 1100) Error Message Reference Manual

(7833 4018)

9.7. Open Programming Environment

The Open Programming Environment (OPE) is an operating system that enables you to

communicate with OS 2200 using commands and programming interfaces based on

UNIX and open systems standards.

The Open Programming Environment (OPE) operating system is software that

provides a UNIX-like interface between the user and the OS 2200 operating system. It

is designed to provide an uncomplicated, efficient, and flexible computing

environment.

Features

The Open Programming Environment has the following features:

• A general purpose system for performing a wide variety of jobs or applications.

• An interactive environment that enables you to communicate with OS 2200 using

commands and programming interfaces based on UNIX and open systems

standards.

• Working in concert with OS 2200, OPE provides a multi-user environment that

enables you to share the computer's resources with other users without

sacrificing productivity. OPE interacts with users on a rotating basis so quickly that

it appears to be interacting with users simultaneously.

• A multitasking environment that enables you to execute more than one program

simultaneously.

• Access to the full range of services provided by OS 2200, and conversely,

provides access to OPE services for OS 2200 applications.

• Provides industry standard commands for building applications, and includes

command-based source control.


9–18 7850 5252–018

Components

The organization of the Open Programming Environment is based on four major

components:

• Kernel

• File system

• Shell

• Commands

Kernel

The nucleus of the Open Programming Environment is called the kernel. The kernel is

an OS 2200 fixed-gate subsystem that constitutes the nucleus of the Open

Programming Environment. It requests services (I/O, resource allocation, and so on)

from OS 2200 on behalf of the user. The kernel works transparently; you do not need

to be aware of it while you are working.

By making requests to the OS 2200, the kernel controls access to the computer,

manages the computer's memory, maintains the file system, and allocates the

computer's resources among users.

File System

The file system is the cornerstone of Open Programming Environment. It provides a

method of handling data that makes it easy to store and access information. It also

provides access to both OPE files and OS 2200 SDF and program files.

The file system provides a logical method of organizing, retrieving, and managing

information. The structure of the file system is hierarchical; if you could see it, it might

look like an organizational chart or an inverted tree.

The file is the basic unit of the OPE file system and it can be any one of three types:

• Ordinary file

An ordinary file is a collection of characters that is treated as a unit by the system.

Ordinary files are used to store any information you want to save. They might

contain text for letters or reports, code for the programs you write, or commands

to run your programs. Once you have created a file, you can add material to it,

delete material from it, or remove it entirely when it is no longer needed.

• Directory

A directory is a superfile that contains a group of related files. Your home

directory is a directory assigned to you by the system administrator when you

receive a recognized login. You have control over this directory; no one else can

read or write files in it without your explicit permission, and you determine its

structure. You can create and remove files and additional directories in your home

directory as needed.


7850 5252–018 9–19

• Special Files

Special files constitute the most unusual feature of the file system. A special file

represents a physical device such as a terminal, disk drive, magnetic tape drive, or

communication link. The system reads and writes to special files in the same way

it does to ordinary files. However, the system's read and write requests do not

activate the normal file access mechanism; instead, they activate the device

handler associated with the file.

Shell

The shell is a program that serves as the command interpreter that enables you to

communicate with the operating system. It acts as a liaison between you and the

kernel, interpreting and executing your commands. Because it reads input from you

and sends you messages, it is described as interactive.

The shell reads the commands that are entered and interprets them as requests to

execute other programs, access files, or provide output. The shell is also a powerful

programming language, not unlike the C programming language, that provides

conditional execution and control flow features.

Commands

Commands are the names of programs that you request the computer to execute.

Packages of programs are called tools. The Open Programming Environment provides

tools for jobs such as creating and changing text, writing programs and developing

software tools, and exchanging information with others through the computer.

Programs that can be executed by the computer without need for translation are

called executable programs or commands. Many standard programs and tools are

available to a user of the OPE system. If the OPE system is used to write programs

and develop software, one can also draw on system calls, subroutines, and other

tools.

Commands provide a number of functions.

• Text processing

The system provides programs such as line and screen editors for creating and

changing text, a spelling checker for locating spelling errors, and optional text

formatters for producing high-quality paper copies that are suitable for publication.

• Information management

The system provides many programs that enable you to create, organize, and

remove files and directories.

• Electronic communication

Several programs, such as mail, enable you to transmit information to other users

and to other OPE systems.

• Software development

Several OPE system programs establish a friendly programming environment by

providing OPE-to-programming-language interfaces and by supplying numerous

utility programs.

Operations Sentinel Basic Edition

9–20 7850 5252–018

• File/data manipulation capabilities

OPE provides file transfer protocol (FTP), network file system (NFS), and r-

command capabilities as well as the ability to copy and translate or filter data

formats.



Support Web site:

• Open Programming Environment (OPE) User's Guide (7831 1073)

• Open Programming Environment (OPE) Programmer's Guide (7831 1040)

• Open Programming Environment (OPE) Configuration Guide (Self-extracting help

file) (7831 1032)

• Open Programming Environment (OPE) Administrator's Guide (7831 1016)

9.8. Operations Sentinel Basic Edition

Operations Sentinel Basic Edition (formerly Single Point Operations) is the default

system operations interface for OS 2200. Basic Edition enables an operator to operate

and manage the OS 2200, Windows, UNIX, and LINUX partitions as well as service

processors using an integrated graphical interface. The Operations Sentinel Basic

Edition display of the configuration provides a graphical way of monitoring the

connections and status of each constituent of the server.

Basic Edition executes on the portion of your server called the Operations server.

Operations Sentinel displays information through the Operations Sentinel workstation,

a Windows PC.

“Operations server” and “Operations Sentinel server” are used interchangeably.

Operations Sentinel provides powerful operation management functions with

value-added features designed specifically for managing a server. You can upgrade

Basic Edition to full Operations Sentinel for complete management of your enterprise

network.

If you already use Operations Sentinel, you can integrate your server into a new or

existing Operations Sentinel configuration that might include other OS 2200.

Architecture of Basic Edition

Operations Sentinel Basic Edition executes on a Microsoft Windows server called the

Operations server.

The Operations Sentinel Windows agent monitors events on each Windows partition.

It reports those events to the Operations Sentinel server. The agent receives events

from the Windows event logs and converts them to information that Operations

Sentinel Console displays in its Alerts window.

OS 2200 consoles are hosted on the Operations Sentinel server and communicate

with operators through the OS 2200 Console View application on an Operations

Sentinel workstation.

Pause Disk I/O for ClearPath OS 2200

7850 5252–018 9–21

The replicated console window of a UNIX partition is available on the Operations

Sentinel workstation through Operations Sentinel server.

The remote desktop of a Windows partition is available on the Operations Sentinel

workstation through the use of Microsoft remote desktop or Microsoft NetMeeting

utilities.

Operations Sentinel uses an autoaction database associated with each OS 2200

console (CP-AMS) or Linux or UNIX partition (SP-AMS) to identify system messages

and automatically execute actions. The OS 2200 console CP-AMS component uses the

attendance mode set by the OM keyin to tailor actions to the level of operator

availability. These actions can include alerts that are displayed in the alerts window of

Operations Sentinel Console. In addition to displaying alarms, you can create rules to

activate external paging devices when alarms are raised, acknowledged, or cleared.

Actions can also include cross-system commands sent to a Linux or UNIX partition or

another OS 2200 partition of the server.



Support Web site:

• Operations Sentinel Software Release Announcement (7862 6512)

• Operations Sentinel Administration and Configuration Guide (7862 2321)

• Operations Sentinel Autoaction Message System Administration Guide

(7862 6900)

• Operations Sentinel Event Server Application Program Interface Programming

Guide (7844 8107)

• Operations Sentinel Master Glossary (7847 4244)

• Single Point Operations MCP Installation and Configuration Guide (7844 8131)

• Single Point Operations MCP Software Release Announcement (7847 5449)

9.9. Pause Disk I/O for ClearPath OS 2200

Pause Disk I/O for ClearPath OS 2200 is a feature of the Executive that makes it faster

and easier to split off a consistent set of EMC Symmetrix TimeFinder Business

Continuance Volumes (BCV). A Business Continuance Volume is a mirror image of

active production disk volumes that can be split off from their production packs at a

point in time and used for a variety of purposes. ClearPath systems and applications

including Universal Database System, TIP FCSS, and Business Information Server fully

support EMC Symmetrix TimeFinder.

The Pause Disk I/O feature freezes I/O to your disk environment to ensure

consistency and integrity of the data set on the Business Continuance Volume at the

time of the split. When combined with Operations Sentinel, EMC Control Center (ECC),

and Operations Sentinel Professional Services, Pause Disk I/O provides an automated

procedure for managing this process with maximum efficiency.

Pause Disk I/O and EMC Symmetrix TimeFinder

Pause Disk I/O for ClearPath OS 2200

9–22 7850 5252–018

The primary purpose of the Pause Disk I/O for ClearPath OS 2200 feature is to enable

the EMC Symmetrix TimeFinder capability; however, other system management

functions are enabled without the use of TimeFinder, such as

• Performing short-term maintenance like reloading microcode in control units or

drives, replacing cables, and replacing other failed hardware items that can be

done in a couple of minutes.

• Creating a consistency point for debugging or performance analysis.

• Enabling off-line operations of the subsystems to complete.

TimeFinder creates Business Continuance Volumes (BCVs) that are mirror images of

active production disk volumes. The BCVs are a real time copy of your production data

and system disks that can be split off from their production packs at a point in time

and used for a variety of purposes. You can even configure multiple sets of BCVs in a

Symmetrix, which enables you to maintain multiple cycles of this data at different

points in time.

The potential applications for TimeFinder are as varied as the multitude of data centers

that use this innovative product. With TimeFinder, you can

• Maximize hours of online processing to increase revenue and help deal with your

24x7 availability requirements.

• Accomplish backups quickly, frequently, and without disruption.

• In concert with the Symmetrix Remote Data Facility, you can move data

seamlessly to a remote data center for disaster backup.

• Load or update data warehouses as needed, quickly and efficiently.

• Perform application testing with real production data while business continues,

and refresh this data frequently for more effective test environments.


The document Exec System Software Operations Reference Manual (7831 0281) is available for this product on the Unisys Product Support Web site.

7850 5252–018 10–1

Section 10 Systems Management Products

This section describes products that support the management of distributed,

heterogeneous networks.


• Apex Administration and Reporting

• Cipher Application Programming Interface (Cipher API)

• COMUS

• Enterprise Output Manager

• File Administration System (FAS)

• Operations Sentinel

• Remote System Support (RSS)

• Roll-out/Roll-back Runstream (ROLRUNS)

• Security Administration for ClearPath OS 2200

• SightLine Enterprise Data Manager (EDM)

• SightLine Expert Advisor/ Vision (EA/V)

• SightLine Interface Agents

• SightLine Power Agent

• SightLine Torch

• SightLine Torch Capacity Manager Interface Agents

• Software Library Administrator (SOLAR)

• Software Library Administrator Extended (SOLAR/E)

• TeamQuest Baseline®

• TeamQuest® D-Fragger and RemD-Fragger (D-Fragger)

• TeamQuest® Log Analyzer (LA)

• TeamQuest® Mass Storage Analysis and Relocation (MSAR)

• TeamQuest® Mass Storage Manager (MSManager)

• TeamQuest Model®

• TeamQuest Online®

Apex Administration and Reporting

10–2 7850 5252–018

• TeamQuest® Online System Activity Monitor (OSAM)

• TeamQuest® Performance Analysis Routines (PAR)

• TeamQuest® PMLog (PMLog)

• TeamQuest® Probes (Probes)

• TeamQuest® Site Administrator Utilities (SAUtilities)

• TeamQuest® Site Management Complex (SIMAN)

• TeamQuest® TIP Log Analyzer (TIP-LA)

• TeamQuest View® (View)

• User Authentication

10.1. Apex Administration and Reporting

Apex provides an easy-to-use, intuitive, browser-based interface for managing the

OS 2200 operating system. It consolidates the administrative tasks that have

traditionally been performed using various Unisys-provided and user-developed

utilities and processes. The ultimate goal of Apex is to enhance the administration of

the OS 2200 system such that a less experienced user can effectively manage the

system similar to open systems and Windows-based systems. This increases the

manageability of the Dorado system for new customers and customers who want to

reduce costs through less-expensive administrative resources.

Apex comprises two major components: an agent installed on the Dorado server and

a Web application installed on a Windows server that is configured to access the 2200

agent by using TCP/IP protocol and is secured with SSL. Basing the user interface on

browser technology eliminates the need for the customer to install any client

software, thereby making any device that can access the Web server a potential

system management workstation.

Apex is accessed from a client's workstation through an HTTPS link in Internet

Explorer or other supported browser to the Web server.

The administrative user can do the following:

• Examine and change user security records and account definitions.

• Examine and change Exec configuration parameters.

• Configure Configured Password Profiles, an authentication module included with

User Authentication.

• Create and save reports that assist in evaluating the state of system security and

take basic actions based on the report contents.

− Accounts Summary

− Users Summary

− New Users

− Modified Users

Cipher Application Programming Interface (Cipher API)

7850 5252–018 10–3

− Dormant Users

− Passwords (Expired, Due to Expire, Unchanged, and Not Using System

Standard Age Limits)

− Privilege Escalations (assignment of SYS$*DLOC$)

− Login Failures


The following documents are available on the Unisys Product Support Web site:

• ClearPath OS 2200 Apex Getting Started Guide (8207 4055)

• ClearPath OS 2200 Apex User's Guide (8207 4063)

• ClearPath OS 2200 Apex Help (8207 4154)

10.2. Cipher Application Programming Interface (Cipher API)

Cipher Application Programming Interface (Cipher API) gives programs running in the

OS 2200 environment access to certain industry-standard FIPS-certified cryptography

algorithms through its use of OS 2200 Cryptographic Library (CryptoLib) and an

optional hardware accelerator. Refer to the Cryptographic Library User’s Guide

(3850 6762) for more information.

Cipher API can be used from the following OS 2200 language products:

• UCS C

• UCS COBOL

• ASCII COBOL

• ASCII FORTRAN

• PLUS

• MASM

• Java

It can also be called from the OS 2200 command line.

One or more optional hardware accelerator appliances can be installed to provide

increased performance for bulk cryptographic services. Each hardware accelerator

appliance acts as an IO controller for up to 128 pairs of cryptographic devices on the

appliance.

Cipher API continues to support the interfaces introduced in level 1Rx (referred to here

as the “level 1 interfaces”) along with level 2 interfaces that provide all of the

capabilities of the level 1 interfaces along with additional capabilities.

The level 1 and level 2 API calls are supported concurrently, but any particular program

must use only one or the other set of APIs. New uses of Cipher API should use the

level 2 interfaces.

Cipher Application Programming Interface (Cipher API)

10–4 7850 5252–018

Cipher API supports the following block cipher algorithms in Cipher Block Chaining

(CBC) or Electronic Code Book (ECB) mode:

• DES (not recommended for new encryptions; not supported by hardware or level 1

interfaces)

• 3DES

• AES

Cipher API supports the RC4 stream cipher with level 2 interfaces.

Cipher API supports the following cryptographic hash algorithms for digital signature

creation and verification with level 2 interfaces:

• MD2

• MD5

• SHA1

• SHA224

• SHA256

• SHA384

• SHA512

• HmacMD5

• HmacSHA1

Notes:

• MD5 is also supported by the level 1 software interfaces.

• Cipher API does not support the use of these hash algorithms with the hardware

accelerator appliance.

Java applications can access Cipher API using the standard Java Cryptography

Architecture (JCA) classes and interfaces. Cipher API handles cryptographic requests

through the UnisysJCE Cryptographic Service Provider.

In addition to the API and Java Cryptographic Service Provider support, Cipher API

includes a command line utility for file encryption.

If a hardware accelerator appliance is installed and the API calls specify dynamic

mode, Cipher API uses either hardware or software encryption, whichever will be

faster for the given data format, data size, and encryption algorithm. To allow for

performance differences based on host hardware configuration, the crossover points

can be configured by the site if the defaults are inappropriate.

Cipher API relies on the OS 2200 security system for user authentication. No new

OS 2200 security attributes are needed.

COMUS

7850 5252–018 10–5

This product is installable by SOLAR. It also requires the OS 2200 Cryptographic Library

to be installed on the same platform.



Support Web site:

• ClearPath OS 2200 Cipher Application Programming Interface (API)

Programming Reference Manual (3826 6110)

• Cryptographic Library User’s Guide (3850 6762)

10.3. COMUS

COMUS is a system software tool that provides site administrators with standard

procedures for configuring and maintaining system software products.

COMUS is used to perform a number of functions:

• Product generation

Provides a standard way to apply changes to a software product.

• Software product configuration

Provides a way to tailor an OS 2200 software product to individual site

requirements and a standard interface for updating the values established for each

product configuration.

• Product database maintenance

Enables you to establish siteIDs, product names, and default global variables for

the products in the COMUS database. The database automatically keeps records

of the products registered, installed, generated, and configured at a site, as well as

all of the local changes applied to products.

Note: COMUS is also used to provide product installation functions, but that

capability has now been replaced by the Software Library Administrator (SOLAR)

product.


The document COMUS End Use Reference Manual (7830 7758) is available for this


Enterprise Output Manager

10–6 7850 5252–018

10.4. Enterprise Output Manager

Enterprise Output Manager is a comprehensive output-management solution for

mixed-platform networks. While running on the Windows operating system, the

primary function of the Output Manager software is to automatically process and

route print files and other application output files from any supported platform to any

supported output destination. An automated processing is based on the file name, file

size, or other file characteristics that you specify. In addition to printing, Output

Manager lets you take advantage of a variety of delivery mechanisms, such as e-mail,

Web, HTTP, FTP, CD/DVD, and fax. With each of these delivery methods, Output

Manager can reformat text documents and data into a customized and modern

appearance.

Output Manager can process output files from a variety of systems, such as Unisys

ClearPath Enterprise Systems and ES7000, IBM, Windows, Oracle, HP, UNIX, and Linux

systems. With its standards-based open architecture, you can “unfreeze” application

output files produced by various vendors, such as Oracle, PeopleSoft, and Unisys, or

by customer-written application programs, such as COBOL, and other legacy

applications. Output Manager can automatically customize and send these output files

to any of the following destination of your choice:

• File server

• Mainframe

• Desktop

• E-mail system (using SMTP or a MAPI compliant e-mail client)

• Fax

• CD/DVD

• XML file

• HTML file

• Printer

• Web site

• FTP server

• HTTP server

• Microsoft Office SharePoint Server (using HTTP PUT method)

• PDF file

• XPS file

• Customer-written programs or software application

Enterprise Output Manager

7850 5252–018 10–7

The main capabilities and benefits of Enterprise Output Manager are as follows:

• Sends and receives print files to and from printers attached to any of the

supported platforms.

• Handles a variety of file formats, including OS 2200 system data format (SDF) files,

MCP printer backup and data files, Passthru files from Windows or any other

source that are already formatted for a printer, and ASCII text files.

• Enables customization of print data by converting characters, changing fonts, using

electronic forms, and rearranging and reformatting data.

• Routes print jobs to different places or print them differently based on

characteristics such as origin of file, size of file, or who created the print job.

• Enables automatic e-mail of documents. Digitally signed and encrypted e-mails can

be sent and received.

• Provides a file viewer for simultaneous previewing of multiple files, performing file

searches, copying portions of a file to the Windows clipboard, and printing some

or all of a file.

• Posts documents to a Web server with use of the Output Manager Web

Assistant.

• Enables automatic or manual backup of files.

• Enables to perform encrypted (signed) data transfer using different protocols like

Raw TCP, HTTP, LPR/LPD, and Output Manager protocols

• Finds information quickly across multiple files through the automatic Indexing

capability.

• Supports many printers, including Postscript, Printer Control Language (PCL),

Unisys, Epson, IBM ProPrinter, and XEROX.

• Provides easy access to LPR/LPD print queues for print jobs from all Output

Manager input sources.

• Enables sharing of files with other users.

• Provides convenient operator and administrator tools.

• Provides custom header and trailer pages.

• Generates log records for cost accounting, print job tracking or statistical reports,

and provides a log viewer for formatting and displaying the entries.

Output Manager and ClearPath IOE

The ClearPath OS 2200 and ClearPath MCP Integrated Operating Environments (IOE)

include the license and media for the appropriate host agent software, and the license

and media for one copy of the Department edition. Additional components can be

purchased separately, such as the function for printing to high-speed printers, the

Web Assistant for Web publishing, Secure E-mail Add-on for sending and receiving

digitally signed and encrypted e-mails, DDA Designer Key for document reengineering,

and PDF Writer Add-on for creating PDF files.

File Administration System (FAS)

10–8 7850 5252–018


Output Manager documents are available at www.unisys.com. After registering or

logging on, you can find an online version of a Capabilities Overview, services and

training flyers, release information, white papers, and so on. Documents are also

available on the Unisys Product Support Site at http://www.support.unisys.com/.

Online Help is provided with Enterprise Output Manager.

The document Enterprise Output Manager for ClearPath OS 2200 and ClearPath

MCP Configuration and Operations Guide (7850 4362) is available for this product on

the Unisys Product Support Web site.

10.5. File Administration System (FAS)

File Administration System (FAS) enables a site administrator to plan, control, and

monitor the files and mass storage space on OS 2200 systems. In addition to ensuring

the safety and validity of the data, FAS can optimize mass storage utilization and

provide file maintenance functions.

FAS Tasks and Commands

FAS can perform many tasks, such as listing information about a file, making copies of

files, loading file text, and reestablishing files from tape volumes. Tasks are initiated

through the use of FAS commands. For example

• BACKUP

This command copies a file or files onto a backup volume. If you have the correct

privileges, the MFD is updated with the backup information.

• LOAD

If a file becomes “unloaded”, for example by an EXEC ROLOUT, then this

command loads file text from a backup volume and places it in a mass storage file.

The file might or might not be the primary backup. This command does not

recatalog the file; the file must have an MFD entry before it can be loaded.

FAS commands can be placed within runstreams for repeated execution. Although

most FAS commands and operations are intended for use by a privileged site

administrator, some commands can also be used by nonprivileged users. FAS is part

of the Integrated Operating Environment (IOE) and is installed using the Software

Library Administrator (SOLAR) processor.

General Features

File Administration System has the following features:

• Data integrity

Backup copies of files can be created on less expensive and easily expandable

storage media (such as magnetic tape). Multiple levels of backup can be retained.

http://www.unisys.com

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

Operations Sentinel

7850 5252–018 10–9

• Virtual file system management

A system can be run with less fixed mass storage. Automatic runs are used to

unload and back up files when mass storage is near capacity and to reload files

when they are needed.

• Archive management

Rarely used files can be removed from a system and still be readily retrievable.

• File management

Files can be positioned and moved to make the most efficient and cost-effective

use of the available storage media.

• Media management

Different pools can be set up simultaneously for use as backup and archive

copies. Each pool is maintained separately, and contains a set of tape volumes.

The pools protect tape volumes from being overwritten.

• Disaster recovery

FAS provides an automated way to create a duplicate set of backup volumes, and

a corresponding file directory, for offsite storage and disaster recovery purposes.

In the event the original backup volumes and directory volume are destroyed, the

duplicate volumes and corresponding file directory can be used to restore a

system in the same way the original set would have been used.


The document File Administration System (FAS) Operations Guide (7830 7972) is


10.6. Operations Sentinel

The Operations Sentinel (formerly Single Point Operations) suite of products enables

an operator to monitor and control multiple server systems from a centralized

operations workstation. With these products, you can centralize control of

heterogeneous systems scattered throughout your enterprise and automate routine

functions, reducing the potential for human error and decreasing overall operating

costs.

Operations Sentinel runs on a Windows server platform.

Operations Sentinel helps you automate many operational functions and centralize

control over the rest:

• Automation

Routine tasks are performed by the computer. This eliminates operator error and

improves service levels.

• Centralization

One operator monitors and controls the entire network of systems. This reduces

the need for operations staff and enables dark room operations.

The Operations Sentinel suite of products includes "virtual console" software and

interface software for each host system that you are monitoring.

Operations Sentinel

10–10 7850 5252–018

Operations Sentinel Console Software

The console software enables monitoring and control from a single workstation. There

are the following editions:

• Operations Sentinel Basic Edition controls one Dorado Series server. It is a

standard component of the integrated operating environment (IOE).

• Operations Sentinel Department Edition and Enterprise Edition are optional

upgrades that control multiple systems, including NX and LX systems, and Dorado

Series servers, ES7000 servers, UNIX/Linux systems, Windows 2003 systems,

Windows 2008 systems, Windows 7 systems, Windows VISTA systems and a

number of other system types. They are optional products.

Department Edition manages up to 25 Windows and UNIX/Linux systems and host

partitions. It supports management of all the MCP and OS 2200 systems and host

partitions for which you have the appropriate Operations Sentinel interface

installed.

Enterprise Edition manages any number of systems (limited only by Operations

Sentinel server capacity and performance).

Basic Edition includes a subset of the features available in the other two editions. You

can upgrade from the Operations Sentinel Basic Edition to Operations Sentinel

Department Edition or Enterprise Edition if you want to manage multiple systems and

take advantage of the many additional features.

Interface Software

For Dorado Series systems, the equivalent of the Operations Sentinel Interface

software resides on the Service Processor or Operations Server. It provides

communication between the OS 2200 partition and the virtual consoles.

Note: Similar interface software exists for MCP systems, Microsoft Windows, and

UNIX systems. If you want to connect to these systems, contact your Unisys

representative, who can help you determine the software appropriate for your use.

Dorado Series Console

Operations Sentinel includes the Dorado console software, providing the following

benefits:

• A Windows-based OS 2200 console, OS 2200 Console View

• Enhanced operator notification using Operations Sentinel capabilities

• Reduced hardware

Autoaction Database Manager

Autoaction Database Manager (ADBM) organizes automation projects using source

and database files, projects, and workspaces. ADBM enables you to build, dump,

verify, and distribute message-based automation databases.

Remote System Support (RSS)

7850 5252–018 10–11



Support Web site:

• Operations Sentinel Software Release Announcement (7862 6512)

• Operations Sentinel Administration and Configuration Guide (7862 2321)

• Operations Sentinel Autoaction Message System Administration Guide

(7862 6900)

• Operations Sentinel Event Server Application Program Interface Programming

Guide (7844 8107)

• Operations Sentinel Master Glossary (7847 4244)

• Single Point Operations MCP Installation and Configuration Guide (7844 8131)

• Single Point Operations MCP Software Release Announcement (7847 5449)

• Operations Sentinel Event Server C# Application Program Interface


10.7. Remote System Support (RSS)

Remote System Support (RSS) is a software product that maintains and processes

diagnostic and maintenance files produced on your site and transfers them between

your computer system and the Unisys Support Center.

Remote System Support (RSS) is a OS 2200 system support software product that

maintains and processes diagnostic and maintenance files and transfers them

between a customer computer system and the Unisys Support Center. Diagnostic

files and site profile data can be sent from a site to a support center, and the support

center can provide emergency information and other assistance to the site.

Files can be sent to and received from Unisys using RSS when a site has been

registered with Unisys as a SITE document with a valid NUM field. This NUM field

must match the SYSTEM-ID in the RSS Administer task that is accessed through the

RSS main menu. Please call Unisys Support if you do not have a valid SYSTEM-ID.

RSS provides access to the Unisys Support Center through TCP/IP protocol across a

DCP, HLC, or internal host communication connectivity (channel adapter), through the

Internet or dial-up connections.

RSS and Mass Storage Dumps

Mass storage dump files can be registered with RSS for future analysis by using the

RSS-REG runstream. RSS-REG takes all existing mass storage dump files and copies

their contents to RSS files. After the dump data is given to RSS, the mass storage

dump files (all SYS$*PANIC$DUMP$$ F-cycles) are deleted.

Every mass storage dump registered by RSS-REG can be analyzed by using the RSS

PROCESS task. System dump files are registered under the name EXEC.

Roll-out/Roll-back Runstream (ROLRUNS)

10–12 7850 5252–018

The following three process names are associated with each dump file:

• MICRO

This process name creates a brief synopsis of the problem, containing only

pertinent information. This summary file is registered with RSS and can be

transmitted to the Unisys Support Center.

• SHORT

This process name creates and prints a complete listing of all Exec internal

structures. The SHORT process name can be used when the support center

requests information that you cannot transmit electronically in a MICRO dump.

• TAPE

This process name creates a tape containing the unprocessed mass storage dump

data. The tape file is in @COPY,G format. The TAPE process name could be used

on the rare occasions when a SHORT dump listing is insufficient to diagnose the

problem and all dump data must be examined at the support center.


The document Remote System Support (RSS) Operations Guide (UP10302) is available

for this product on the Unisys Product Support Web site.

10.8. Roll-out/Roll-back Runstream (ROLRUNS)

The Roll-out/Roll-back Runstream (ROLRUNS) product enables OS 2200 to

automatically roll out files to tape if the system is running out of unallocated mass

storage space and to roll them back when access to a rolled-out file is needed.

ROLRUNS provides a virtual file system whose capacity is limited only by the total

capacity of both disks and tapes.

The Roll-out/Roll-back runstream (ROLRUNS) product is a collection of runstreams

used for file maintenance. ROLRUNS enables the Exec to automatically roll out files to

tape if the system is running out of unallocated mass storage space. When access to

a rolled-out file is needed, the Exec automatically rolls back (retrieves) the file from

tape.


The document Exec System Software Administration Reference Manual (7831 0323)

lowing technical manual is available for this product on the Unisys Product Support

Web site.

10.9. Security Administration for ClearPath OS 2200

Security Administration for ClearPath OS 2200 (Security-Admin) provides a modern

tool for managing OS 2200 security records. This tool contains both a graphical user

interface, the Security Client, and a batch/demand interface, SECMGR.

Security Administration is an alternative to TeamQuest® SIMAN.

SightLine Enterprise Data Manager (EDM)

7850 5252–018 10–13

Security Client

Security Client is a Java application for administering security on an OS 2200 host

system from a remote workstation.

Users who are not security officers or administrators can use the client to view their

own user records, display a list of controlled interfaces, create access control records

(ACR), and attach those ACRs to objects they own.

Security officers and administrators can use the client to do the following:

• Install userIDs and assign initial passwords

• Create and maintain security records for each userID, including those for users,

other administrators (subadministrators), and subsystems

• Enforce or unenforce privileges and interfaces that enable users or subsystems to

bypass security when needed

• Manage the Security Environment

• Create accounts and assign quotas to control system resources

• Generate security reports

The Security Client performs its operations through a security agent running on the

OS 2200 host, using the simple network management protocol (SNMP). The agent

must be running on the host for any communication and control to occur.

Optionally, end users and administrators can access the OS 2200 system directly

through a workstation or terminal and perform the same functions as through the

Security Client using the processing capabilities of SECMGR.

SECMGR

SECMGR is an OS 2200 command line utility initiated by the @SECMGR processor

command. Commands provided by SECMGR enable you to install, display, or update

large amounts of security database information as a batch job. For example, you can

install or update large numbers of userIDs or access control records (ACR) using

SECMGR commands.


The document Security Administration for ClearPath OS 2200 Help (7862 1760) is


10.10. SightLine Enterprise Data Manager (EDM)

SightLine Enterprise Data Manager (EDM) is at the center of the SightLine Software

Suite. EDM is a J2EE application comprising two components: the Data Collector

Service (DCS) and the Web-based EDM User Interface. These two components

together provide central control and management for data collection and maintenance,

agent configuration/ management, alert processing, reporting,

browser-based user interface, and more.

SightLine Expert Advisor/ Vision (EA/V)

10–14 7850 5252–018

The capabilities and benefits of EDM are as follows:

• Central administration – A single interface to aggregate information regarding all

the components within your IT infrastructure.

• Gathers SightLine performance data from hundreds or thousands of monitored

systems and data sources, both agent-less and agent based.

• Manages a data repository and archive of performance data – Data archival and

summarization are performed automatically as the data is collected. Thus, data you

need is available whenever it is required and at the granularity best suited to

answer the question.

• SightLine Agent configuration– Configuration and management for all SightLine

agent-based data collection can be performed from the Web-based EDM console.

With EDM, you do not need direct access to the system to update workload

definitions, view log files, or even restart the agent.

• Central alerting– As data is collected, user-configured alerts are evaluated and

predetermined actions are taken. You can send an e-mail, execute a command, or

send an SNMP trap to a third-party framework. The possibilities are endless.

• The correlation engine of EDM compares the behavior of your target metric to all

the other metrics on the system, and to the metrics on any other monitored

systems you are concerned about. Similar behavior is detected regardless of the

units or scale of the other metrics, and the time range can be shifted to allow

possible delays in the appearance cause-and-effect relationship between systems.

• Provides the most robust reporting capabilities available from a performance

management solution today. Reports can be customized by user and can be

automated to run at the user’s convenience.

A conversion path is available for users who have an existing implementation of the

SightLine Software Suite that is based on data collection from SightLine Expert

Advisor/Vision (EA/V). The data collected and stored by EDM is available for analysis

using EA/V. Open the trace files created by EDM. All analysis features that you have

become familiar with are available along with the centralized configuration and

administration capabilities from EDM.

10.11. SightLine Expert Advisor/ Vision (EA/V)

SightLine EA/V offloads the overhead of performance monitoring from the host to the

desktop. EA/V identifies and monitors the critical path of e-business services across

the IT infrastructure, so that problems can be detected and eliminated as they occur

before they become major performance bottlenecks.

EA/V provides a variety of different ways to view your data, all accessible at the click

of a button. You can display the data in a conventional line plot and instantly switch to

a scatter plot, or any of the 12 other views. EA/V also includes an online data dictionary

containing definitions of the metrics that are being reported.

SightLine Expert Advisor/ Vision (EA/V)

7850 5252–018 10–15

The full power of the SightLine suite is available to users through

Windows-based EA/V workstation provided by SightLine. Graphical displays of

utilization of a variety of resources (CPU, memory, storage, and so on), technical and

management reports, and more can be viewed from the console software. All

information can also be viewed through a Web browser, for ease in remote

monitoring, as well as customized information displays.

Beyond merely displaying performance information, SightLine EA/V provides

automated, intelligent analysis features, such as AutoCorrelate™, AutoAnalyze™, and

AutoInvestigate™. These features provide tuning advice, enabling you to drill down

into live or potential problem areas within your server, whether it is a Unisys ClearPath

system, UNIX, Linux, Windows, or any others.

The SightLine EA/V workstation is not limited to analysis and correlation of data from

the current system. It can be used to analyze performance and capacity information

from a wide range of components in your data processing environment. This feature

adds unique functionality such as highlighting unknown relationships between various

components of your IT infrastructure.

AutoAnalyze

AutoAnalyze uses expressions or rules to search specified data and examine certain

condition sets that suggest potential service-level impacts. When any defined

condition set becomes true, AutoAnalyze produces a group of reports describing the

activity of the host system, highlighting potential performance problems.

AutoCorrelate

AutoCorrelate is the industry's premier linear correlation engine that quickly compares

the inter-relationships of large volumes of data metrics across your entire computing

infrastructure.

It helps you analyze your systems’ data in seconds to identify problems and their

exact cause, enabling your technicians to rectify those problems immediately.

AutoInvestigate

AutoInvestigate isolates periods of time when enterprise parameters have deviated

from their normal patterns.

AutoAlert

AutoAlert examines user-defined threshold definitions based on specific events when

occurred, triggers a warning message, executes an action, or sends an e-mail

message or page. In addition, AutoThreshold takes the guesswork out of identifying

appropriate threshold levels by providing an automated way of specifying threshold

values based on their deviation from normal behavior.

AutoWeb

AutoWeb creates and serves HTML pages from the pages and plots displayed by

SightLine. Custom HTML pages can be substituted for the default environment. Thus,

you can match the look and feel of your existing Intranet styles, as well as supplement

plots with explanations and related links.

SightLine Interface Agents

10–16 7850 5252–018

Automation

Automation allows you to access the performance data that is stored in trace files and

work with it in other applications. It also provides an effective tool to customize or

automate frequent tasks you want to perform.

Trend Analyzer

Trend Analyzer helps you identify trends in your historical SightLine data and provides

the ability to summarize and profile data in ways that were previously unavailable.

10.12. SightLine Interface Agents

Interface Agents provide additional data to SightLine EDM, SightLine EA/V, and the

user and require the Power Agent to operate. The Interface Agents for the ClearPath

OS 2200 are described in the following sections.

10.12.1. SightLine SIP Statistics

The System Instrumentation Package (SIP) is a standard part of the OS 2200 operating

system. SIP monitors and collects performance statistics about the operating system,

workloads, and major pieces of hardware on the system. A comprehensive set of

statistics is supplied. SightLine provides statistics on CPU, Memory and I/O utilization,

XPC, Gate Activity, IPM, Expool, Dynamic Allocator, Dispatcher, ER activity, and

hundreds of other critical performance metrics. The SIP data source is included with

the SightLine OS 2200 Power Agent.

10.12.2. SightLine System Log / INSP$ Statistics

The System Log provides detailed TIP, demand, and batch resource usage statistics by

individual run, program, and terminal. SightLine takes advantage of data available

through INSP$ calls, so you get the information to link performance problems back to

the user and transaction. Additionally, disk errors and security violations are monitored

so that failing hardware or unauthorized usage can be detected before major system

outages occur.

10.12.3. SightLine MFD Statistics

The Master File Directory (MFD) can be queried to obtain information about the mass

storage of a system. SightLine provides statistics about the availability

(MFD K-Trks Avail) and the reliability (MFD K-NonErr Refs) of each disk drive and logical

channel. Statistics are also provided summarizing these statistics for all cache,

non-cache, fixed, removable, and for all disks. Additionally, SightLine can be configured

to produce MFD statistics by qualifier, project-id, and account number.

SightLine Interface Agents

7850 5252–018 10–17

10.12.4. SightLine TIP KONS Statistics

TIP KONS is an area of memory set aside by the Transaction Interface Processor (TIP)

to record the performance and behavior of a TIP transaction environment. The global

metrics from System KONS can be used to determine the need to look at individual

transaction statistics. There are eight areas of performance information available

within the KONS Interface Agent: Transaction Response Times, Transaction Rates,

Transactions Active, COMPOOL, Transaction Errors, FCSS, Transaction Scheduling, and

Timer Statistics.

10.12.5. SightLine UDS Statistics

The Universal Data System (UDS) measures transaction volume, queuing, and errors in

any of the databases managed under the UDS umbrella, including DMS and RDMS.

UDS data is gathered from the published UMON interface, or from the ACT, QAD, and

BST Tables within UDS. Hit rates can be determined, queuing problems can be quickly

identified and overcome, and space utilization can be optimized. SightLine collects data

for three functional areas: Transaction Activity and DMR Slot Usage, Buffer Usage plus

Rollbacks, and Queuing by queue reason.

10.12.6. SightLine TPM / HVSTATs Statistics

Transaction Performance Monitor (TPM) audit trails and High Volume Statistics

(HVSTATS) are used in place of TIP Logging at some sites. The statistics reported are

similar to those described earlier for TIP Log, with the addition of several statistics

unique to HVTIP. With SightLine, the TPM Log records can be grouped into workloads

characterized by Program Name. HVSTAT records can be grouped by Program Name

or Initial Control Program, User Word030, or LINC ISPEC.

10.12.7. SightLine Step Control / MCB Statistics

Step Control metrics record tree usage and queuing by node and priority. Message

queuing can be isolated in the input tree – queuing that will not show up directly as

increased response time. Step Control identifies transactions being queued before

they are scheduled. (System Log, TPM/HVSTATS, and UDS data identifies transactions

being queued after they have been scheduled.) SightLine collects statistics for all

configured priorities and nodes. It also displays input messages that are active and

queued, total and maximum allowed; and output messages that are active, queued,

and total.

10.12.8. SightLine MAPPER Statistics

SightLine’s MAPPER data is divided into six functional groups: Communication, Mass

Storage, Memory Pool, Report Access, User Activity, and Workload. Workload data

provides Utilization, Activity Counts, and Response Time Statistics by MAPPER

function, department, user, run, and type.

SightLine Power Agent

10–18 7850 5252–018

10.12.9. SightLine CMS / SILAS Statistics

CMS or SILAS data provides an event-by-event description of everything that goes

through the communications system. Data collection from multiple instances of CMS

is possible.

10.12.10. SightLine DPS Statistics

The Display Processing System (DPS) allows application programmers to define and

use screens for their programs, and also to separate screens from other parts of the

application. SightLine provides statistics on the DPS system including Message

Activity, Errors, I/O Rates and Utilization, and Response Time.

10.13. SightLine Power Agent

The SightLine™ Power Agent™ for Unisys ClearPath OS 2200 Systems is the

foundation of the SightLine Software Suite. The SightLine Power Agent resides on the

ClearPath host. It is easily configured to collect data on various key system

components, user-specified programs, and groups of programs as single measurable

workloads. The data is collected on a regular basis, stored on the host, and sent

through TCP/IP to the SightLine Enterprise Data Manager (EDM) or Expert

Advisor/Vision (EA/V) console for alerting, analyzing, displaying, and reporting.

Note: To use the data from a Power Agent, you must have the SightLine EDM or

EA/V console installed and properly running. SightLine EDM and EA/V are licensed

separately from other SightLine components.

10.14. SightLine Torch

Torch Capacity Manager is a historical database performance management system

used for long-term workload trend analysis and capacity planning for Unisys ClearPath

OS 2200 systems. By examining the past, the performance or capacity-planning

analyst can accurately anticipate the future. Torch combines the key performance data

from multiple sources into one comprehensive, integrated performance database.

Using Torch/Report, it can produce graphs and statistical reports that summarize and

display performance data according to specific needs, while also providing the

information necessary to make sound decisions concerning computer system

performance and capacity requirements.

The following data sources are included with the base Torch Capacity Manager:

• Torch/SIP

• Torch/MFD

• Torch/STAR

Torch/SIP

Reduces SIP data. It reads one or more SIP cycles and produces the file

SIP-INTERVAL as an output.

SightLine Torch Capacity Manager Interface Agents

7850 5252–018 10–19

Torch/MFD

Gathers statistics and produces reports related to mass storage utilization. It can also

be used to feed the MICS product of Computer Associates, Inc. At this time, the

Torch/MFD data is not integrated into the Torch performance database and cannot be

reported through Torch/Report.

Torch/STAR

Extracts and reports statistics from Star-1100 Tape Management System of Formula

Consultant. It can be used to feed the MICS product of Computer Associates, Inc. At

this time, Torch/Star data is not integrated into the Torch performance database and

cannot be reported through Torch/Report.

10.15. SightLine Torch Capacity Manager Interface Agents

The Torch Capacity Manager Interface Agents provide additional data to be integrated

into the Torch performance database. Torch Interface Agents require SightLine Torch

Capacity Manager to operate. The Interface Agents are as follows:

• Torch/IO

• Torch/Alog

• Torch/MAPPER

• Torch/TPM

Torch/IO

Reduces I/O Trace data. It reads an I/O Trace tape and produces an IOT event file,

IOT-EVENT. The IOT-EVENT file contains a detailed summary of the I/O Trace data from

which Torch/IO produces a set of I/O distribution reports.

Torch/Alog

Reduces Master Log File (MLF) or system log data. It is used to reduce the ASCII Log

cycle.

Torch/TPM

Reduces TIP Transaction Performance Monitor (TPM) audit trails and High Volume

Statistics (HVSTATS) data.

Torch/MAPPER

Reduces MAPPER data. Data from multiple MAPPER systems can be merged into the

same database.

Software Library Administrator (SOLAR)

10–20 7850 5252–018

10.16. Software Library Administrator (SOLAR)

Software Library Administrator (SOLAR) is a software tool that a site or system

administrator uses to install and maintain software products. It provides utilities that

enable software package registration, product installation and deinstallation, library

backup and restoration, reporting of library contents, and the packaging of software

products.

SOLAR is a software tool that a system administrator uses to install and maintain the

software products on an OS 2200 system. SOLAR consists of the following

components:

• SOLAR processor

• SOLAR utilities

SOLAR replaced COMUS as the principal product installation tool. COMUS is still used

to generate symbolic products.

To use SOLAR, a site administrator must have knowledge of software package tapes,

OS 2200 Exec Control Language (ECL) and runstreams.

Note: Software packaged from one MCN/partition/workload can still be installed

on any other MCN/partition/workload if product keys authorizing the target system

workload are registered.

SOLAR Utilities

SOLAR contains six independent utilities. Each utility performs one or more tasks

related to the installation or maintenance of software:

• PKGREG

Registers and unregisters software package tapes. Registers key package tapes

and removes registered keys.

• PRODLD

Installs products from a package tape or installs local products.

• PRODRV

Removes software products from a system.

• PRODRT

Creates reports based on the registered software packages, registered keys, and

installed products.

• RECON

Identifies and optionally corrects any corrupt data in SYS$*DATA$.

• PRODSV

Saves software products to a software package tape (available only with

SOLAR/E).

Software Library Administrator Extended (SOLAR/E)

7850 5252–018 10–21

SOLAR Processor

The SOLAR processor is a full-screen, menu-driven processor that creates

runstreams. Depending on the task the user selects from the main menu, SOLAR

displays a series of screens to collect the information it needs to build the runstream.

The runstream contains stream generation statements (SGS) and a call to the

appropriate SOLAR utility.

Once SOLAR has created the runstream, the user can either start (@START) it from

within SOLAR or save it to a file and element and start it at a later time. When the

runstream is started, the SOLAR utilities process the SGSs in the runstream to

complete the specified task.


The document Software Library Administrator (SOLAR) User Reference Manual


10.17. Software Library Administrator Extended (SOLAR/E)

Software Library Administrator Extended (SOLAR/E) contains all the functionality

available with SOLAR plus the ability to create software product packages with

PRODSV, the product save utility.

SOLAR/E can serve as a cornerstone in your software distribution process. With

PRODSV, you can coordinate system software at all your remote sites from a central

location. Your system administrator can customize and verify local software as well as

software received from Unisys or other vendors. Using PRODSV to create the

software package, the central site can then send it to remote sites for installation on

their systems.

PRODSV creates software packages. The user can either call the SOLAR processor to

create a runstream that automatically includes the appropriate stream generation

statements (SGS) and the call to PRODSV, or write the input SGSs and then call

PRODSV.

With the SOLAR/E PRODSV utility, the user can

• Save system software, files, and products to a software package tape.

• Save a local product to a package tape without first installing it.

• Save products from existing software package and COMUS build output tapes.

• Create software package tapes at a central OS 2200 site for distribution to remote

OS 2200 sites.


The document Software Library Administrator (SOLAR) User Reference Manual


TeamQuest Baseline

10–22 7850 5252–018

10.18. TeamQuest Baseline

TeamQuest Baseline® provides real-time monitoring, historic reporting, workload

characterization, and trend analysis. Performance data is collected and stored on the

host system, and reporting is done on a PC by using the TeamQuest View interface

software.

TeamQuest Baseline enables you to build and manage a system performance

database. It uses existing operating system instrumentation to gather measurement

data into a TeamQuest Baseline database and maintain this database on a daily basis.

You can access this data and present it in either a textual report format or a color

graphics display. You can use TeamQuest Baseline to perform the following tasks:

• Workload characterization

This feature enables you to analyze and understand workload differences in terms

of processor, memory, and I/O requirements to resolve performance issues and

predict impact if workload changes occur. Workloads can be characterized by such

identifiers as runID, userID, and Business Information Server department.

• Performance analysis

This feature enables you to identify performance bottlenecks, analyze alternative

solutions, and recommend the most cost-effective method of providing service to

the user.

• Trend analysis

This feature enables you to identify periodic oscillations (continuous growth or

decline of workload activity) for forecasting expanding activities on a system.

TeamQuest Baseline can provide workload forecasts derived from trend analysis

to predict the hardware configurations necessary to ensure expected levels of

service.



Support Web site:

• OS 2200 TeamQuest Products Installation Guide (TQ-01013)

• TeamQuest Baseline Framework and TeamQuest Online User Guide (TQ-01011)

• TeamQuest View User Guide (TQ-01401)

10.19. TeamQuest D-Fragger and RemD-Fragger (D-Fragger)

TeamQuest® D-Fragger defragments fixed mass storage, leaving disk files in

contiguous blocks. You no longer have to perform a jump key 13 boot to defragment

your fixed mass storage.

TeamQuest RemD-Fragger defragments removable mass storage, leaving disk files in

contiguous blocks. You no longer have to back up all your files on the drive, delete

them, then reload them from tape to defragment your removable mass storage.

TeamQuest D-Fragger and RemD-Fragger (D-Fragger)

7850 5252–018 10–23

D-Fragger and RemD-Fragger helps you compact mass storage by defragmenting files,

consolidating free space for future allocation, and minimizing DAD entries. It

decreases Exec time and streamlines I/Os. D-Fragger also reports disk fragmentation

on allocated and unallocated space.

Using TeamQuest D-Fragger and RemD-Fragger provides the following benefits:

• Improves job turnaround times.

• Frees up administrator and operator time.

• Increases the amount of available mass storage without purchasing disk drives.

TeamQuest D-Fragger and RemD-Fragger enables you to perform the following:

• Defragment Fixed Mass Storage (D-Fragger)

− Defragment fixed mass storage quickly and efficiently.

− Stay on-line while fixed devices defragment.

− Quit performing a jump key 13 boot.

• Defragment Removable Mass Storage (RemD-Fragger)

− Defragment removable mass storage quickly and efficiently.

− Stay on-line while removable devices defragment.

− Eliminate the cumbersome tasks of backing up all the files, deleting them, and

reloading them from tape to defragment your files.

• Consolidate Mass Storage

− Defragment files.

− Consolidate free space for future allocation.

− Speed I/Os.

− Minimize DAD entries.

− Improve access times and file allocation speed.

• Speed User Applications

− Decrease Exec time.

− Streamline I/Os.

− Improve turnaround times.

• Report Disk Fragmentation

− Prepare management reports on disk space availability.

− Investigate allocated and unallocated fragments.

TeamQuest Log Analyzer (LA)

10–24 7850 5252–018



Support Web site:

• TeamQuest Products Installation Guide (TQ-01013)

• TeamQuest D-Fragger End Use Reference Manual (TQ-01551)

• TeamQuest RemD-Fragger End Use Reference Manual (TQ-01561)

10.20. TeamQuest Log Analyzer (LA)

TeamQuest® Log Analyzer (LA) reduces the system log file into meaningful reports

that help you monitor and manage system resource usage. The reports it produces

supplement those provided by other system processors, such as TeamQuest®

Performance Analysis Routine (PAR) and the Software Instrumentation Package (SIP),

and helps you isolate software development costs, analyze user trends, and plan

system capacity.

Log Analyzer (LA) produces reports based on the data collected in the system log file

of the OS 2200 Series systems. The reports provide information on the system

resources that include programs, runs, transactions, and devices used. Log Analyzer

reports also summarize the activity of the entire system, a program, a run, or a

transaction. Log Analyzer can also produce graphs that plot the active runs, SUP

usage, backlog runs, and mass storage requirements. With these reports and graphs,

site administrators can analyze the usage of their system.

Just as the OS 2200 system log has developed and expanded over the years, LA has

grown in terms of resources and capabilities. As the number and types of system log

entries has grown, so have the capabilities of LA, so that the product currently offers a

range of log report types (see the following table). The types of reports and

combinations of reports generated are all user selection options. Both the report type

and time duration must be specified by the user. LA can be used either interactively in

demand mode, or in batch mode.

Report Type Description

Device Usage Measures the usage of peripheral devices.

Dump Provides octal, ASCII, single line, or text representation of log entries

plus identification information contained in the run initiation entry.

Entry Frequency Counts the log entries processed.

Event Provides a chronological list of run activity on the system for a

specific time interval.

Equipment Describes equipment types available on the system.

File Summarizes information on all file usage, ROLBAK and ROLOUT

activity, and detail information on all cataloged files and tape files

used.

Group Produces reports based on computer resource usage summarized

by account, projectID, userID, and original runID.

TeamQuest Log Analyzer (LA)

7850 5252–018 10–25

Report Type Description

I/O Error Summary reports the I/O errors that occurred on each type of

equipment.

LAN Activity reports on utilization of Local Area Network (LAN) devices

attached to a Host LAN Controller (HLC).

Media Usage Summarizes tape reel and disk pack usage and I/O errors that

occurred on each reel or pack.

Message Re-creates the console printer listing, lists other types of messages.

MIPS Metering The MIPS metering report summarizes the million instructions per

second (MIPS) usage on the system.

Program Produces reports based on computer resource usage broken down

by program rather than run.

Qlink Provides detailed console messages for each Qlink transaction that

is locally created by specific sites and logged with the entry type

167770/1.

Run Provides information about program aborts, lost runs, a summary of

a run's activities, and an analysis of a run.

Security Reports on security events caused by a user.

Symbiont Usage Measures the usage of symbiont devices.

System Summary Summarizes total system activity.

Terminal Reports the activity and use of each communication device.

Thread Provides a list of threads that were processed.

TIP Reports on TIP transactions.

Tuning Provides internal LA performance information to assist in using

ALLOCATE CACHE to increase LA performance.

Unsolicited Keyin

Summary Lists the type of each unsolicited keyin used.

Weekly Summarizes system performance over a seven-day period.

During normal processing of the system log file, LA reads the Audit Control Interface

(ACI) file to obtain the file names and reel numbers. If no input or selection parameters

are specified, LA searches the ACI file for files that have data from the last 24 hours.

However, the user can specify the period of time for which LA should process data.

When the time duration is specified, LA examines the ACI file to obtain data for the

specified time interval.



Support Web site:


• TeamQuest Log Analyzer (LA) Administration and End Use Reference Manual

(TQ-01081)

TeamQuest Mass Storage Analysis and Relocation (MSAR)

10–26 7850 5252–018

10.21. TeamQuest Mass Storage Analysis and Relocation (MSAR)

TeamQuest® Mass Storage Analysis and Relocation (MSAR) analyzes mass storage

files and devices. It also helps to balance file input/output activity across devices or

subsystem locations by moving files or portions of files from one physical location to

another.

MSAR is designed for customers who want to monitor their file system and improve

total system performance and program efficiency, especially in situations where

performance of the I/O subsystem is a significant factor in total system performance.

MSAR provides displays (maps) of the locations of files on mass storage devices and

gives storage allocation information. A map is a layout of the file by its device area

descriptors (DAD), which illustrates where on mass storage the file resides. MSAR has

the capability to move files or file segments from one device to another, and provides

recovery in case of system services interruptions.

MSAR functions are provided by the following processors:

• Master File Directory Reporting (MFDRPT)

A parameter-driven processor that enables you to choose many combinations of

file directory fields. Selection parameters are provided to display or report most of

the accessible file information fields of the master file directory (MFD).

Construction of MFD reports involves a simple process of entering selection

parameters and options to direct MFDRPT to create the desired reports and file

lists.

• Directory Change (DIRCHG)

Processor used to organize and maintain the master file directory (MFD). This

processor can assist in maintaining and enforcing the standards for account and

project naming. It can also provide a consistent means of placing files into

categories for billing and accounting purposes.

• File Placement (ACQ)

Processor acquires, releases, and moves files and file segments on disk devices

within the system local and shared disk configuration. Processor options and

parameters provide useful methods of manipulating files giving assurance that

data is not lost. ACQ does the file operations solely within itself without using the

FAS processor. ACQ does, however, use Program Callable FURPUR to perform

functions such as file copying.

MSAR is compatible with the Multi-Host File Sharing (MHFS) feature. Both shared

devices and files can be reported. It can be used to access either OS 2200 Executive

(Exec) or Transaction Processing (TIP) files. Information displayed about TIP files also

includes information about the Exec files in which they reside.

TeamQuest Mass Storage Manager (MSManager)

7850 5252–018 10–27



Support Web site:


• OS 2200 TeamQuest Mass Storage Analysis and Relocation (MSAR) End Use

Guide (TQ-01091)

10.22. TeamQuest Mass Storage Manager (MSManager)

TeamQuest® Mass Storage Manager (MSManager) can be used to automate the

mass storage procedures and practices at an OS 2200 site. Automating the handling of

the files on a system leads to better management of mass storage resources.

MSManager can be used to control the handling of the files on an OS 2200 system to

better manage mass storage resources. MSManager is not meant to be a replacement

for a file backup system, but rather to supplement and improve an existing facility.

MSManager provides a number of benefits:

• Improves I/O performance

• Reduces mass storage hardware costs

• Reduces ROLOUT and ROLBAK

• Enforces file-naming standards

• Reduces system administration costs

• Reduces File Administration System processing time

• Reduces the number of File Administration System tapes

MSManager consists of two components:

• File database (FDB) processor

Maintains the file and archive databases. These databases contain retention

information about the files on your system.

• PURGE processor

Removes or archives the unwanted files based upon the retention information

stored in the file database. It can also update master file directory (MFD) attributes

and can optionally pack program files to further reduce the amount of mass

storage.

The FDB and PURGE processors work together to provide the automated file purging

capabilities of MSManager. The FDB processor maintains the list of files and their

retention information that the PURGE processor uses when removing or archiving

files. The PURGE processor uses the information in the file and archive databases to

determine whether to remove or archive each file on your system.

TeamQuest Model

10–28 7850 5252–018



Support Web site:


• TeamQuest Mass Storage Manager (MSManager) End Use Reference Manual

(7833 4406)

10.23. TeamQuest Model

TeamQuest Model® can be used to build and solve a model for predicting and tuning

system performance. Data can be imported from TeamQuest Baseline or directly into

the model. Once built and calibrated, this model can be used to

• Predict the effects of changes in system workloads on system service levels

• Predict the effects of changes in workload or hardware configuration

• Tune the system without making any actual changes to the system

TeamQuest Model can build baseline models of measured periods of systems

operations with its built-in, automated model builder.

TeamQuest Model automatically calibrates or adjusts the models to represent your

system. You can control further calibration so that the predicted performance of the

model is close to the measured performance of your system. You can also build your

own queuing network models from scratch.

You can use TeamQuest Model to predict computer system performance measures,

such as response times, throughputs, queue lengths, and facility utilizations.

TeamQuest Model enables you to build a representation of either an existing or a

hypothetical system and subsequently experiment with "what if" questions. You can

answer such questions as

• When is the system likely to run out of capacity, given a set of workload growth

projections?

• What benefit is realized from adding another central processing unit (CPU)?

• What effect does doubling a specific business workload have over the next six

months while moving part of another workload to an alternative shift?

When your model has been built, TeamQuest Model solves it using one of the

following techniques:

• Analytic modeling, using heuristic iterative mean value approximation

• Discrete-event simulation

TeamQuest Online

7850 5252–018 10–29

When a model has been solved, TeamQuest Model produces detailed reports

providing information on principal results, workload and resource result statistics, and

summary statistics. You can also export the generated statistics directly into

Microsoft Excel to produce default charts and statistic database or to an ASCII

comma-delimited file for input to a commercial spreadsheet program for generating

graphs.



Support Web site:


• TeamQuest Model User Guide (TQ-01424)

• TeamQuest Model Tutorial (TQ-01425)

10.24. TeamQuest Online

TeamQuest Online® is used to monitor system performance data. Performance data

is collected and stored on the host system, and reporting is done on a PC by using the

TeamQuest View® interface software.

By using the PC as the user interface, you can view performance data from multiple

host systems in a single PC session. This function enables you to administer many

systems or to compare performance from a single location.

TeamQuest Online uses existing operating system instrumentation to gather

measurement data and present real-time monitor reports. You can view this data in

either a textual report format or a color graphics display.

TeamQuest Online includes significant features that give you the ability to

• Present reports simultaneously from multiple hosts

• Perform correlation analysis between performance statistics

• Export reports to word processors and spreadsheets

• Produce hard-copy output of reports using a printer or plotter

• Supports TeamQuest View Socket connections to OS 2200

• Streamlines the initialization process



Support Web site:


• TeamQuest Baseline Framework and TeamQuest Online User Guide (TQ-01011)

TeamQuest Online System Activity Monitor (OSAM)

10–30 7850 5252–018

10.25. TeamQuest Online System Activity Monitor (OSAM)

TeamQuest® Online System Activity Monitor (OSAM) is a comprehensive monitoring

and capacity planning program. It is the single tool that all departments can use to

monitor and manage their particular system resources.

OSAM provides instantaneous and historical access to a variety of OS 2200

information:

• Exec Software Instrumentation Package (SIP)

• Overall transaction processing (TIP) environment and individual transactions

• Batch and demand runs and programs

• Overall Universal Data System (UDS) environments and individual UDS threads

• Mass storage utilization for the fixed pool and by device

• File track usage by run

• Message Control Bank (MCB) and COMPOOL environments

• Step Control queue trees

• MIPS metering for capacity on demand (COD) systems

OSAM consists of the basic product that provides information in real time on any

full-screen demand terminal and the OSAM performance database feature that greatly

increases its capabilities. The performance database feature provides logging,

database maintenance, batch execution, replay, and report capabilities for the product.

OSAM integrates data from Exec instrumentation, the system log file, and up to 16

application groups into a single monitoring facility. The monitored information is

provided in real-time and near real-time through menu, data, threshold, and graph

screens.

An extensive threshold alerting facility is built into the product. The user can set

thresholds on all OSAM parameters and specify actions to be taken when those

thresholds are reached, such as issuing console messages, starting batch runs, or

alerting a terminal.

The monitored information can also be stored in a database with the performance

database feature. Databases can be maintained with different levels of detail for a

variety of analysis and capacity planning functions. The stored data can be reported or

replayed in text format.

TeamQuest Performance Analysis Routines (PAR)

7850 5252–018 10–31



Support Web site:


• OS 2200 TeamQuest Online System Activity Monitor (OSAM) End Use

Reference Manual (TQ-01101)

10.26. TeamQuest Performance Analysis Routines (PAR)

TeamQuest Performance Analysis Routines (PAR) package is a performance

measurement system used to analyze and generate reports from the data gathered by

the Software Instrumentation Package (SIP) and I/O trace, which are functions of the

Exec. PAR helps you identify performance bottlenecks, optimize system throughput,

and measure the performance effects of additional hardware or configuration

changes.

PAR is used to analyze and produce reports from SIP and I/O trace data files. SIP is a

system-performance data collection function of the OS 2200 Executive (Exec). The SIP

data collection function can be configured during a system generation and then

activated or deactivated by the operator at the system console by system balance

(SB) keyins. Running SIP results in data files consisting of raw performance data

recorded at user-defined intervals. Additionally, you can obtain an input/output (I/O)

trace tape file or mass storage file containing data for every I/O performed.

Because the level of analysis required by individual users varies, PAR contains

standard reports and graphs, as well as a high-level command language that lets you

develop custom reports.

The PAR processor has a programmable user interface that enables users a high

degree of control over manipulating data and creating reports. It provides a standard

set of reports with minimum input, without the need for specialized analysis and

reporting. The standard SIP reports provide statistics covering various functional areas

of the operating system and a summary report. The standard I/O trace reports range

from a full raw data report to summary reports over specific I/O requests.

The data reduction process can be controlled through the use of processor options,

processor specification fields, and the PAR standard commands. Default cases exist

for all statements, so you need not specify any input except a data file to obtain the

standard set of reports. More sophisticated users can control the reading and

processing of SIP data through user-defined commands, producing reports and graphs

tailored to the specific needs of a site.

TeamQuest PMLog (PMLog)

10–32 7850 5252–018



Support Web site:


• OS 2200 TeamQuest Performance Analysis Routines (PAR) End Use Reference

Manual (TQ-01111)

10.27. TeamQuest PMLog (PMLog)

TeamQuest® PMLog (PMLog) is a software product that gathers 2200/Extended

Processing Architecture (XPA) Performance Monitor log data for the TeamQuest

Baseline® Framework software. The TeamQuest PMLog software is installed on an

OS 2200 node and uses the TeamQuest View® software as the user interface.

TeamQuest PMLog is a tool to aid the system administrator in performing capacity

management and performance analysis tasks.

TeamQuest PMLog serves as a probe for TeamQuest Baseline, collecting the system

log data and storing that data in the TeamQuest Baseline database. The data can then

be viewed as textual or graphic reports using the TeamQuest View user interface

software that is released with TeamQuest Baseline.

TeamQuest PMLog processing consists of two phases: data collection and data

display. These phases include the various activities involved in processing, reducing,

and storing performance monitor log data in the TeamQuest Baseline database and

using that data for report generation and graphics displays. TeamQuest Baseline

controls the activities for data collection and data display processing.



Support Web site:


• TeamQuest PMLog End Use Reference Manual (TQ-01351)

10.28. TeamQuest Probes (Probes)

TeamQuest® Probes (Probes) is a software package that contains a set of programs

(known as probes) that gather measurement data for the TeamQuest Baseline

Framework or TeamQuest Online software products. This set of probes augments

the data sources supplied with TeamQuest Baseline Framework and TeamQuest

Online, giving the system administrator a better view of system performance.

TeamQuest Site Administrator Utilities (SAUtilities)

7850 5252–018 10–33

The TeamQuest Probes software consists of the following probes:


Gathers data from MCB applications.

• Mass storage probe

Gathers mass storage statistics.

• Universal Data System (UDS)

Gathers data from UDS applications.

Each of the probes in the TeamQuest Probes software acquires performance

information from its respective data source on the system. The probes use this

information to calculate various statistics that are then stored in the TeamQuest

Baseline database. These statistics can be viewed as textual or graphic reports using

the TeamQuest View interface software.

TeamQuest Probes consists of two phases:

• Data collection

This phase includes the various activities involved in processing, reducing, and

storing data in the TeamQuest Baseline database.

• Data display

This phase includes the use of the data for report generation and graphic displays.

TeamQuest Baseline or TeamQuest Online controls the activities for data storage

and data display processing. Both TeamQuest Baseline and TeamQuest Online use

the TeamQuest Baseline database for data storage and retrieval.



Support Web site:


• TeamQuest Probes End Use Reference Manual (TQ-01361)

10.29. TeamQuest Site Administrator Utilities (SAUtilities)

TeamQuest® Site Administrator Utilities (SAUtilities) is a collection of programs and

interfaces used to design site administration tools and procedures. It includes utilities

for print queue maintenance, disk file dumps, audit trail scanning, tape labeling, and

database event reporting, as well as services for character conversion, time, and log

file access.

TeamQuest Site Administrator Utilities (SAUtilities)

10–34 7850 5252–018

SAUtilities includes the following tools:

• Print Queue Maintenance Utility (PQMU)

Used to copy print files from a symbiont print queue and store them as elements

in a program file. PQMU uses information contained in the symbiont print file

header to create element names.

• Dump

A full-screen program that can be used to view and update sector-or word-

formatted disk files interactively. It can also be used to position and view tape

files.

• TLBL

A series of runstreams that perform the tape labeling functions required by your

site. The runstreams let you label new tapes, re-label used tapes, and unlabel

tapes. They also print existing tape labels on the console.

• Audit Trail Scan Utility (ATSUTL)

Provides the capability to scan a tape or mass storage audit trail and produce

reports. You can produce database activity reports from an Enterprise Network

Database Server for ClearPath OS 2200, Enterprise Relational Database Server for

ClearPath OS 2200, or a Shared File System by selecting runID, area, file, schema,

table name, record number, page number, generated runID or transactionID, date

and time period, or a summary total of all database record subtypes.

• Database Event Reporting (DBEVENT)

Interfaces with the system to turn reporting on or off. When DBEVENT reporting is

turned on, DBEVENT accepts packets of collected database event data from the

system. Selected information from these packets is written to mass storage or

tape files. The report program DBERPT can be called to read the raw data and

produce reports as requested.

SAUtilities contains a collection of service routines that perform common tasks for

programs written in Universal Compiling System (UCS) and basic mode environment

high-level languages. These services provide high-level interfaces to perform tasks

that would otherwise require low-level programming. The services have been

developed once to be used repeatedly by many users and programs. These SAUtilities

services can do the following:

• Reduce development time

• Eliminate common errors

• Promote consistency

• Assist migration from basic mode to UCS environments

The SAUtilities service routines provide the following:

• Character conversion services

Perform character string manipulations using ASCII strings, single-precision

integers and double-precision integers. These character conversion services are

adjunct to the existing conversion services in the OS 2200 Service Library.

TeamQuest Site Management Complex (SIMAN)

7850 5252–018 10–35

• Date and time services

Perform date and time manipulations, using TDATE timestamps, DWTIME

timestamps, and ASCII strings. These date and time services are adjunct to the

existing time manipulation services in the OS 2200 Service Library.

• Log File Interface (LFI) subroutines

Read log entries from the system log file. The LFI subroutines, accessed through a

Call interface, gather information to develop computer-time accounting and

performance analysis programs that process system log file data. The subroutines

can be called from programs written in COBOL, FORTRAN, C Compiler, or PLUS.



Support Web site:


• OS 2200 TeamQuest Site Administration Utilities (SAUtilities) End Use


10.30. TeamQuest Site Management Complex (SIMAN)

The TeamQuest® Site Management Complex (SIMAN) software provides an

interactive, screen-oriented, menu-driven interface for handling site administration

functions.

SIMAN is an interactive software product for creating and maintaining security and

resource control in an OS 2200 system. You can set up security for the whole system,

for a particular application, or for personal security.

SIMAN is designed for security officers, site administrators, and other users who are

responsible for security and resource control. SIMAN is also designed for users who

want to create access control records (ACR), change access lists on their files, or view

their userID security record.

By setting up the SIMAN environment on your system, you determine what kind of

tasks you can perform using SIMAN. The SIMAN environment consists of the

following functions:

• User Identification and Maintenance

• Extended Security and Access Control

• Accounting and Resource Control

TeamQuest TIP Log Analyzer (TIP-LA)

10–36 7850 5252–018



Support Web site:


• OS 2200 TeamQuest Site Management Complex (SIMAN) Administration and

End Use Reference Manual (TQ-01151)

10.31. TeamQuest TIP Log Analyzer (TIP-LA)

TeamQuest® TIP Log Analyzer (TIP-LA) provides a flexible method of obtaining

reports from the TIP Performance Monitor (TPM) audit trail file through its free-format,

keyword-oriented interface. It is designed to produce reduction reports of TPM log

records from the TPM audit trail file. With TIP-LA, you can view summary and detail

information about transaction activities. You can customize reports to fit specific

needs and export the report output to a spreadsheet or Web browser. TIP-LA also

includes a set of tools and services that enable you to write programs to read the

TPM audit trail file and produce reports that fit your system environment. These tools

and services include TPM Log File Interface (LFI) and the date and time conversion

routines.

Tools and Services

The Log File Interface does the following:

• Retrieves data from the TPM audit trail file

• Enables user software to read and process TPM records without needing the

specific TPM record format.

• Supports PLUS, UCS PLUS, COBOL, UCS COBOL, and UCS C language interfaces.

• Conversion service routines provide a set of date and time conversion service

routines that perform date and time manipulations using TDATE$ format,

DWTIME$ format and ASCII string data types

Report Types

You can view the following report types:

• View usage reports organized by transaction, input pid and HVTIP library and

subprogram numbers.

• View summary and detail reports on transaction usage of ER and CALL interfaces.

• View summary reports on transactions usage of FCSS I/O activities

• View summary reports on transaction aborts and status of the aborts

• View summary reports on transaction accessing to TIP file activities

• View summary reports on transaction with reads and writes done by UDS to both

Exec and UDS/TIP files

• View detail reports on each transaction executed

TeamQuest View (View)

7850 5252–018 10–37

Predefined and Custom Reports

The following are predefined or custom reports:

• Generate standard reports to summarize the use of the transaction resource in as

many categories as you need.

• Create ad hoc custom reports specific to your needs.

Output Files

The following are output files:

• Export the report output in element format to a file with delimiter that can be read

by spreadsheet programs.

• Export the report output to an SDF file in HTML format which is suitable for Web

browser reporting.



Support Web site:


• OS 2200 TeamQuest TIP Log Analyzer (TIP-LA) Administration and End Use


10.32. TeamQuest View (View)

TeamQuest View® provides a graphical user interface for the detailed reporting and

analysis of system performance data. TeamQuest View obtains performance data

from the TeamQuest Performance Framework (TeamQuest Baseline) for display and

analysis on your PC workstation. TeamQuest View enables a system administrator to

monitor the performance of one or more systems and to quickly drill down to the

exact cause of a problem.

TeamQuest View accesses the host system, retrieves data, and creates text and

graphical reports. Each report appears as an individual window that can be moved,

resized, and adjusted as needed.

TeamQuest View® enables you to perform the following tasks:

• Analyze and view system performance data using a real-time monitor.

• Present reports simultaneously from multiple hosts.

• Perform correlation analysis between performance statistics.

• Generate and present reports in textual or graphic format.

• Select and view reports predefined for each system platform.

• Create and maintain user-defined reports.

User Authentication

10–38 7850 5252–018

• Create and report on user-defined statistics that are derived using data collected

by the data collection probes.

• Open and save a session and its associated reports as an environment which can

be opened at a later time.

• Specify and save the default database and calendar settings for a session.

• Export reported data into a tab- or comma-delimited file format.

• Export and automatically import report data into Microsoft Excel.

• Copy charted data as a Microsoft Graph chart and paste it into other applications.

• Produce hard-copy output of reports using a printer or a plotter.

• Report detailed process or event data collected in tables.

• Drill down from a chart report to a table report.

• Drill down from a table report to another table report.

• Locate descriptions of statistics collected using online help mechanisms.

• Create a chart report based on statistics that triggered an alarm event.



Support Web site:


• TeamQuest View User Guide (TQ-01401)

10.33. User Authentication

User Authentication (FLEX) enables you to enhance the security of your systems by

implementing additional methods of authentication. In addition to the traditional Exec

passwords, you can implement advanced password requirements and take advantage

of smart cards, fingerprint identification, or any other forms of authentication that give

a user access to the network that includes the Dorado server. These additional forms

of authentication provide the convenience of a single sign-on solution or extra

protection against unauthorized system access or both.

With User Authentication, you can install authentication modules outside the Exec,

rather than building local code into the Exec or implementing authentication within an

application.

Authentication Modules (AMs) implementing any form of authentication on demand

and TIP system access can be "plugged in" to the Authentication and Session Initiation

Subsystem (ASIS). ASIS provides the infrastructure, and it links to AMs that implement

the decision-making policies.

User Authentication

7850 5252–018 10–39

User Authentication also provides a program-callable interface to allow common

authentication for server software that does not initiate a demand or a TIP session.

User Authentication supports authentication requests through the authentication API

or directly from the Exec, with or without the tokens or tickets that are required by

certain protocols.

AMs can securely store data needed to authenticate a user in an authentication data

area (ADA) associated with the user’s security database userID record. An

administrative interface to ASIS enables site-written utilities to populate and maintain

the ADA.

AMs are supplied by Unisys and can be supplied by third parties. In addition, sites can

provide their own authentication methods.

ASIS supports up to 64 AMs. Two AMs are installed as part of User Authentication.

• AM0 (traditional Exec userID/password) supports the User Authentication API that

corresponds to the traditional Exec userID/password authentication method.

• AM19 (Configured Password Profiles) supports advanced password requirements,

such as requiring a password to contain alphanumeric characters and preventing

the reuse of the previous n passwords.

Additional AMs are released with Messaging Integration Services (NTSI). These AMs

use the Windows domain security model or Linux security for authentication and the

local 2200 security database for authorization after authentication is completed

successfully.

The security profile of each OS 2200 user indicates the AM that must be used to

authenticate the user.


The document ClearPath Enterprise Servers User Authentication Administration

Guide (7850 4586) is available for this product on the Unisys Product Support Web

site.

User Authentication

10–40 7850 5252–018

7850 5252–018 11–1

Section 11 Tool and Utility Products

This section describes the tools and utilities available to support the operation of your

ClearPath server or OS 2200 Series system.


• Console Message Redisplay (CMR)

• Disk Preparation Utility (DPREP1100)

• Dump Analysis Processor (DAP)

• Element Processor (ELT)

• Extended Language Message System (ELMS)

• Fault Location by Interpretive Testing (FLIT)

• File Utility Routine/Program-file Utility Routine (FURPUR)

• General Syntax Analyzer (GSA 1100)

• Internationalization Service Library (I18NLIB)

• Interconnect

• List Processor (LIST)

• Multiple Batch Run Optimizer

• PostMortem Dump Processor (PMD)

• Procedure Definition Processor (PDP)

• Program-Callable FURPUR (PCFP)

• Relational Database Fast Load

• Symbolic Stream Generator (SSG)

• Tape Labeling Utility for ClearPath OS 2200

• TeamQuest® Cross Reference Generator (CULL)

• TeamQuest® Interactive CULL (IACULL)

• Utilization Report Utility for OS 2200 (URU)

Console Message Redisplay

11–2 7850 5252–018

11.1. Console Message Redisplay

Console Message Redisplay (CMR) captures and saves all console messages and then

redisplays them upon operator request.

CMR provides the ability to capture and save all console messages for later display

upon operator request. The SHIELD friendly console provides an easy way to scroll

back and review previously displayed console messages. For systems not using the

SHIELD friendly console, the Console Message Redisplay (CMR) function lets the

operator review previously displayed console messages.

CMR is a process (executing in a service run) providing the ability to redisplay console

messages that have scrolled off the screen. The CMR keyin can be used to request a

message redisplay. The service run (activated at system initialization time) collects

console messages as they appear and saves them for future reference in a file,

CMR*REDISPLAY$.

Note: Messages displayed before a service run is started are not available for

redisplay.

New cycles of the file are created whenever the service run is started and also at

midnight. CMR puts a limit of five cycles on CMR*REDISPLAY$ so that no more than

five cycles exist on the system at the same time. Normally, no more than three cycles

of CMR*REDISPLAY$ are cataloged at one time. Messages that are less than 24 hours

old and were saved since the current service run was started can be redisplayed.

All system consoles and users of remote consoles with console mode LIMITED or

higher can use the redisplay capabilities. The minimum console mode privileges

enabled for the remote console can be changed at execution time. CMR is a batch job

that references the System Log file, and its ability to obtain console messages is not

related to the state of the system console.

Messages that are redisplayed show their original display time (in the format

hhmm:ss) at the beginning of the message. The redisplayed copy of a message is

never redisplayed again. However, the original message can be redisplayed as often

as necessary.

Note: Asian messages that are redisplayed by the CMR capability are not checked

to prevent the 2-byte Asian characters from being truncated after the first byte. If

this happens, the character is incorrectly displayed.

The AUTO$START element in SYS$LIB$*RUN$ contains the names of runstreams that

are initiated each time the system is booted. Each product that releases runstreams

defines whether these runstreams should be included in the AUTO$START element.

COMUS and SOLAR insert an @RUN image at the beginning of the element.

Example

@RUN AUTO,730200,AUTO$START

@START SYS$LIB$*RUN$.CMR

Disk Preparation Utility

7850 5252–018 11–3

11.2. Disk Preparation Utility

Disk Preparation Utility (DPREP1100) prepares and maintains system disks.

DPREP1100 runs on OS 2200 and SUMMIT Exec.

DPREP1100 prepares disks for use with the operating system. Disk preparation

creates the Exec visible directory structures on the mass storage device, such as

• Volume header label, VOL1

• Directory track that contains information on the allocation of the directory,

information on the disk device and the hardware, and the software master bit

tables (MBT)

DPREP1100 can, however, perform a number of other related actions.

Separate prep types (1 through 8) within DPREP1100 are selected to perform specific

actions. One or more prep types might be required to prepare and maintain disks,

depending on disk types and site requirements. The specific nature of each prep type

can vary for different disk types and families.

DPREP1100 is released in the following ways:

• ClearPath Integrated Operating Environment (IOE)

• Diagnostic Software Peripheral Equipment Routines (DSPER) releases

DPREP1100 can be run in either offline or online mode. It is used in offline mode with

the SUMMIT maintenance executive if there is a need to prepare a disk so that it can

be made available for use by the OS 2200 Executive. In online mode, DPREP is initiated

either in batch mode or interactively with an OS 2200 processor (Exec control

language or ECL) call.


The following documents are available for this product on the Unisys Product Support

Web site:

• OS 2200 Exec System Software Installation and Configuration Guide (7830 7915)

• Disk Preparation (DPREP1100) Operations Guide (7831 3038)

Dump Analysis Processor

11–4 7850 5252–018

11.3. Dump Analysis Processor

Dump Analysis Processor (DAP) is a tool provided with OS 2200 System software to

assist in dump processing. It provides dump analysis for panic, batch, interactive, and

program dumps.

Dump Analysis Processor is a subset of the Fault Location by Interpretive Testing

(FLIT) processor. You can use the basic file editing capabilities to print formatted dump

files, but Dump Analysis Processor has none of the interactive simulation capabilities

of FLIT.

Dump Analysis Processor is a component of the OS 2200 Dump Library (DMPLIB). It

supports the New Programming Environment (NPE) DIAGDUMP for absolutes.

Dump Analysis Processor does not have separate documentation.

Format

LOAD$PMD(altdiag,absfn,options)

where:

altdiag specifies the DIAG$ file.

absfn specifies the program file.

options are the load options.



Support Web site:

• FLIT Programming Reference Manual Volume 1: Program Mode (7830 7998)

• FLIT Programming Reference Manual Volume 2: System Mode (7830 8004)

Element Processor

7850 5252–018 11–5

11.4. Element Processor

Element Processor (ELT) is a processor that is part of the OS 2200 operating system. It

creates, modifies, and lists elements (groupings of information) in program files.

ELT can be used to create and update symbolic elements and to create omnibus

elements from the output produced by the FURPUR @PCH, O command.

General Features

ELT provides a range of capabilities.

• Transfers content corrections to the existing element, the next cycle of an

element, or to an element of another name, leaving the content of the original

intact.

• Processes non-transparent control statements as data and inserts them into a

symbolic element. It can also update symbolic elements in a file.

• Provides a complete listing of a symbolic element when requested. The list

includes sequential line numbers for each image, cycle number of each image, and

information about deleted and added images.

The ELT processor is invoked through the use of an Exec control language (ECL)

statement. Options are provided for the ECL statement that determines the nature of

processing.

Element type options either insert images following the @ELT statement into an

omnibus element as they appear in the runstream or identify elements as symbolic

elements.

Image handling options either indicate that the symbolic input images following the

@ELT statement can include control statements that are to be transferred as element

data, eject a page whenever a slash (/) appears in column one, generate a listing of the

complete symbolic element, print (for symbolic elements only) both the input and

updated line numbers with the correction lines, or takes error exit (ERR$) upon

occurrence of an error.


The document DATA Processor and ELT Processor Operations Manual (UP13402) is


Extended Language Message System

11–6 7850 5252–018

11.5. Extended Language Message System

Extended Language Message System (ELMS) is a full-featured message system that

enables Unisys and customer program products to display messages through a single

interface in any configured language. Messages can be delivered to a console, a

standard print file, or an alternate print file.

ELMS consists of a subsystem for message delivery and several utility processors

that provide associated components (message modules and the installed-module

directory), enable message testing, and report information. An application can request

ELMS to deliver a message to a console, standard print file, or alternate print file, or it

can just receive the buffered message.

When an application uses ELMS for message processing, messages are defined,

maintained, and processed separately from the application. This gives the application

independence from its messages and the run-time environment.

I18N applications can use ELMS to define and display messages in multiple languages.

Programmers doing I18N and localization can use ELMS to

• Define and store messages in modules called message data banks (MDB), which

have multilingual delivery capabilities.

− Multiple MDBs can coexist on a system for any given application.

− MDBs can contain different subsets of the same message in different languages.

− Any MDB can be dynamically selected for delivery at each request.

− MDBs for additional languages can be created and installed separately.

• Dynamically select the language in which a message is delivered, based on a

specific profile. A system can have a system-wide default language, a system-

wide console language, and per-run user languages.

• Use the Local Language Processor (LLP) to localize MDBs.

ELMS can be used with any application running on any ClearPath enterprise server or

any OS 2200 Series system that supports extended mode.


The document Extended Language Message System (ELMS) Programming Guide


Fault Location by Interpretive Testing

7850 5252–018 11–7

11.6. Fault Location by Interpretive Testing

Fault Location by Interpretive Testing (FLIT) software simulates an OS 2200 program or

system environment within which one can run and debug any OS 2200-compatible

executable program or an OS 2200 operating system. Within a FLIT-simulated

environment, a programmer can load, execute, and examine object code, and change

it dynamically without the need for recompilation. A programmer can also use FLIT to

analyze OS 2200 files.

FLIT software provides a simulated OS 2200 system environment in which a

programmer can run and debug any OS 2200-compatible executable program.

FLIT is primarily an interactive simulator that enables programmers to control both

developmental software and the surrounding environment. It includes a virtual

processor that can simulate systems, system programs, and object modules. For

example; working within a FLIT-simulated environment, a programmer can load,

execute, and examine object code, and change it dynamically (without the need for

recompilation).

Program execution is controlled in the simulated environment with the FLIT

programming language. The FLIT programming language provides:

• Control statements for starting, stopping, and tracing program execution, and for

finding and fixing programming errors without re-assembly or recompilation

• Prewritten library functions for program debugging (You can also write your own

functions in the FLIT language.)

The simulated system contains all pseudo registers, switches, and controls needed to

represent the state of the system or program being simulated. FLIT does not require

operating system modifications or a special configuration to run.

FLIT Modes

You can use FLIT in the following modes:

• File Analysis Mode

The default mode. In this mode, a programmer can use FLIT's paging to analyze

and modify any OS 2200 file.

• Program mode

In program mode, a programmer can load and debug a program. FLIT can simulate

executables, object modules, zero overhead object modules (ZOOM), common

banks, and subsystems. FLIT can also simulate multi-activity programs. FLIT also

provides a set of functions (prefixed with D$) to enable high-level debugging.

• Postmortem dump mode

A mode of operation in which a program environment is established based on

information obtained from the diagnostic file (DIAG$) that the OS 2200 Exec

automatically writes upon termination of a program. The DIAG$ file contains the

final contents of a program's main storage at termination.


11–8 7850 5252–018

• System mode

A customized hardware environment in which you can boot, run, and debug an

operating system or control program. FLIT enters system mode automatically

upon encountering a FLIT statement for configuring a simulated hardware system

(for example, S500$SYS, S900$SYS, or S30$SYS). During the configuration and

booting of a simulated system, all FLIT capabilities are available to perform such

tasks as stopping the simulation, saving the current environment, or restoring a

previously saved environment.

• Panic dump mode

In this mode, FLIT processes panic dumps stored on either an Exec dump tape or

a dump stored on mass storage. When FLIT loads a panic dump, it creates an

environment identical to the state of the machine at the time of the dump.

WinFLIT

WinFLIT is a debugger that combines a register transfer language simulator running on

the OS 2200 (FLIT) with a symbolic debug interface running on your workstation. If you

have purchased FLIT, you can upload and use WinFLIT.

You can use WinFLIT to debug OS 2200 absolutes, object modules, ZOOMs, common

banks, and subsystems. WinFLIT supports symbolic debug. Symbolic debug enables

you to see the source code as it is being simulated. You can also view and change

symbolic variables. WinFLIT supports an INFOConnect interface. Using this interface,

you can communicate with OS 2200 full screen (@@ESC) programs. The window

interface is easy to use and uses common window menus and controls.

WinFLIT communicates with FLIT running on the OS 2200 using a TELNET connection.

The source listings are uploaded to the workstation using an FTP connection. The

optional full screen interface to simulated programs is supplied by an INFOConnect

connection. You must have a 32-bit version of INFOConnect installed.

WinFLIT is supported on Windows 95/98/00 and NT.

Format

*TRACE{,options} {id} {addr1{AT}/addr2{AT} {switch} {’fname’}

*TRACI{,options} component addr1{AT}/addr2{AT} {switch} {’fname’}

*BRKPT addr1{AT} options num {’funct’}

where addr1 and addr2 can be a 72-bit constant or a 72-bit variable.

Postmortem Dump Mode: Version 7 DIAG$ format

FLIT goes into postmortem dump mode by loading a DIAG$ and program using the

LOAD$PMD function. Using this mode, you can examine the environment of the

program at the time of the dump. FLIT supports the loading of absolutes, NPEDIAG

absolutes, object modules, and ZOOMs.

The LOAD$PMD function supports DIAG$ formats 5, 6, and 7.


7850 5252–018 11–9

Format

LOAD$PMD(altdiag,absfn,options)

where:

altdiag specifies the DIAG$ file.

absfn specifies the program file.

options are the load options.

FLIT Enhancements

FLIT includes the following enhancements:

• Enables you to specify a register on the *BRKPT statement

• Program mode supports the 2200/8040 and 2200/8050 systems

When FLIT is activated on a 2200/8040 system, the MACH predefined variable is

set to S2200$8040. When FLIT is activated on a 2200/8050 system, the MACH

predefined variable is set to S2200$8050.

• System mode supports the 2200/8040 and 2200/8050 systems

APBOOT automatically configures the S804$ and S805$ functions on a given

2200/8040 or 2200/8050 partition data bank (PDB).

• System mode supports the CUTASC tape control unit and device

APBOOT automatically configures the tape subsystem as required.

• System mode supports the LB$SIM function on an emulated system

This function enables the user to define another function that will execute when a

defined library gate is executed.

• System mode supports the MEM$ACQ$CPTR, MEM$REL$CPTR, and MEM$ALLOC

functions to aid debugging of an emulated system.

• System mode supports the DSP$AA$QBR, DSP$BD$QBR, and DSP$REAL$QBR

functions to aid debugging of a queue bank repository (QBR).

• System mode supports the DSP$TAPESTAT function to display the status of a

tape device.

Capabilities

• S803$FIC$CHN 2200/8030 FICON configuration function

• S804$ 2200/8040 configuration function

• S805$ 2200/8050 configuration function

• TASC$CU peripheral configuration function

• DSP$AA$QBR displays a queue bank repository for a given absolute address

• DSP$BD$QBR displays a queue bank repository for a given level and bank

descriptor index (LBDI)

• DSP$REAL$QBR displays a queue bank repository for a given real address


11–10 7850 5252–018

• MEM$ACQ$CPTR returns a c-pointer (real address) for a given size and optional

attribute

• MEM$REL$CPTR releases a c-pointer (real address) for a given c-pointer and size

• MEM$ALLOC displays the memory allocation entries on an emulated system

• LB$SIM sets the FLIT function to be executed when library gate is executed

• SCF$STATSAV creates a state save

• DSP$TAPESTAT displays tape device information

New Predefined Variables

• PDBMAINSESS$ points to the partition data bank (PDB) session data offset and is

used by the APBOOT$ elements to modify the PDB prior to the boot

• SESSBOOTYP$ points to the PDB session boot type offset and is used by the

APBOOT$ elements to modify the PDB prior to the boot

• S2200$8040 can be a setting for the MACH predefined variable to create a

2200/8040 program mode environment

• S2200$8050 can be a setting for the MACH predefined variable to create a

2200/8050 program mode environment



Support Web site:

• FLIT Programming Reference Manual, Volume 1: Program Mode (7830 7998)

• FLIT Programming Reference Manual, Volume 2: System Mode (7830 8004)

• OS 2200 System Services Programming Reference Manual (7833 4455)


(7830 7899)

File Utility Routine/Program-File Utility Routine

7850 5252–018 11–11

11.7. File Utility Routine/Program-File Utility

Routine

File Utility Routine/Program-File Utility Routine (FURPUR) provides a simplified method

for copying text, and updating or listing information for OS 2200 files. These tasks are

accomplished by entering FURPUR commands while logged onto an OS 2200 server

session.

FURPUR is a set of file maintenance routines that are an integral part of the OS 2200

operating system. FURPUR provides you with a simplified method of controlling and

moving data within the OS 2200 file structure, and within the general system, and

running utility routines.

The OS 2200 file structure consists of data residing on magnetic tape or mass storage.

FURPUR, which is invoked by means of runstream control statements, provides a

number of functions:

• Change file attributes (@CHG).

• Change program file element names (@CHG,AORS).

• Close magnetic tapes (@CLOSE).

• Copy magnetic tape element files to mass storage program files (@COPIN).

• Copy mass storage program files to magnetic tape element files (@COPOUT).

• Copy mass storage files to mass storage files (@COPY).

• Copy mass storage program file elements to mass storage program files

(@COPY,AORS, @COPY,P).

• Copy mass storage or magnetic tape System Data Format (SDF) files to mass

storage or magnetic tape SDF files (@COPY,F).

• Copy mass storage or magnetic tape files to mass storage program file elements

(@COPY,I).

• Copy mass storage program file elements to mass storage or magnetic tape files

(@COPY,I, @PCH).

• Copy mass storage files to magnetic tape files in several formats (@COPY).

• Copy magnetic tape files in several formats to mass storage files (@COPY).

• Copy magnetic tape files in any format to magnetic tape files (@COPY).

• Print information about and change the attributes of sets of cataloged files (F-cycle

sets) (@CYCLE).

• Delete files (@DELETE).

• Delete mass storage program file elements (@DELETE,AORS).

• Undelete mass storage program file elements (@DELETE,UAORS)

• Enable disabled files (@ENABLE).

General Syntax Analyzer

11–12 7850 5252–018

• Erase the contents of mass storage files and release unused mass storage

(@ERS).

• Locate elements in magnetic tape element files (@FIND).

• Write hardware end-of-file marks on magnetic tapes (@MARK).

• Position magnetic tapes (@MOVE, @REWIND).

• Remove deleted elements and text from mass storage program files (@PACK).

• Create mass storage program file entry point tables (@PREP).

• Print the contents of the Master File Directory (@PRT).

• Print information about specific files (@PRT,F).

• Print information about files in use by the run (@PRT,I).

• Print the table of contents of a mass storage program file (@PRT,T).

• Print the text of a mass storage program file symbolic element (@PRT,S).

FURPUR commands are issued using control statements. Control statements consist

of a set of processor call statements that the Exec interprets as calls for FURPUR.

When the Exec encounters a FURPUR control statement, it loads the FURPUR

processor. FURPUR continues to process processor call statements until signaled by

the Exec that the next statement is not a FURPUR processor call statement.


The document Executive Control Language (ECL) and FURPUR Reference Manual


11.8. General Syntax Analyzer

General Syntax Analyzer (GSA 1100) is a tool for users who create their own language

processors and scanners. It helps you construct a broad range of processors and

other applications that require the scanning of a language-type input, such as

• Compilers and assemblers

• Data management processors

• Hardware and firmware language processors

• Text editors and documentation processors

When compared with other syntax analysis methods, GSA 1100 helps you

• Reduce implementation time and cost

• Reduce errors

• More easily update language specifications

• Simplify design

• Create less code

General Syntax Analyzer

7850 5252–018 11–13

GSA 1100 is a general language-analysis tool used in the construction of processors

for several languages such as

• Data-management languages

• Hardware and firmware languages

• Text-editing and documentation languages

• Online control languages

• Simulation languages

• Specialized problem-solving languages

GSA 1100, or parts of it, are used in the MACRO processor, PLUS compiler, Subschema

Data Definition Language (SDDL), Database Inquiry, Programmer's Advanced

Debugging System, Display Processing System, Enterprise Relational Database Server

for ClearPath OS 2200, FORTRAN Compiler, COBOL Compiler, Linking System, and

numerous other products.

The GSA 1100 system has a considerable number of advantages over hand-coded

syntax analysis, which has been the mainstay for parsing in a production environment.

Some of these advantages include

• Reduced implementation time and reduced cost

• Less probability of errors

• Language specifications easily changed and updated

• Simplified design since separate specification encourages modularization

• Less code due to use of tables

These general advantages apply to most syntax-directed methods of parsing, whether

or not they are suitable methods for a production environment. The main differences

between the GSA 1100 method of parsing and other tried methods are as follows (not

all of the following differences apply when comparing the GSA 1100 method with a

different method):

• You can more easily represent a language specification.

• GSA 1100 treats error recovery as an integral and automatic aspect of parsing.

• There is a greater flexibility in semantic interaction.

GSA 1100 can function in both basic mode and extended mode.


The document General Syntax Analyzer (GSA 1100) Programming Reference Manual


Internationalization Service Library

11–14 7850 5252–018

11.9. Internationalization Service Library

Internationalization (I18N) Service Library (I18NLIB) provides the ability for applications

to sort lists of names and words according to local conventions. I18NLIB also provides

a smooth, structured, documented migration path from 7-bit character sets to the 8-

bit character sets, which are sorted and indexed according to the new conventions.

I18NLIB provides I18N capabilities for OS 2200 Series system software and

applications programs. I18NLIB contains the service routines required to process user

data according to local language conventions and to select the processing rules at run

time. I18NLIB service routines perform tasks associated with character identification,

transliteration, name-and-number transformation, uppercasing/lowercasing,

formatting, and sorting/collating. With few exceptions, all are callable from programs

written in basic and extended mode MASM, PLUS/UPLS, C Compiler, and COBOL

Compiler.

I18NLIB is released and installed as part of the integrated operating environment (IOE)

or operating system group (OSG) software release groups.

The following are terms associated with the Unisys I18NLIB implementation:

• Locale

A locale is the collection of rules and data that represent linguistic and cultural

conventions for a specific region. It consists of six parts called categories. The

locale model of processing forms the basis of I18N implementation for OS 2200

Series systems. The repository that comes with the I18NLIB product contains a

set of locales that meet current market requirements; this set can be changed as

requirements change.

• Category

A category is part of a locale. Each category contains locale-specific information

for one class of functions. The value of a category is set by the I18NLIB

SETLOCALE service routine and is applicable on an activity level. A locale definition

file contains several categories, each corresponding to an environment variable of

the same name.

• Environment Variable

An environment variable contains information that exists on a run or transaction

level. It is used to convey information between an application program and an

I18NLIB service routine. Like categories, environment variables can be used by the

service routines to execute a program based on a specific locale.



Support Web site:

• Internationalization (I18N) Assistant: An Online Help System for the I18N Service

Library Online Help (7850 5393)

• Internationalization (I18N) User Manual (7833 4588)

Interconnect

7850 5252–018 11–15

11.10. Interconnect

The Interconnect is a software product used internally by several other Unisys

products. It provides system services that enable you to use the Specialty Partitions

OS 2200 JProcessor and OS 2200 QProcessor in OS 2200 servers.

11.11. List Processor

List Processor (LIST) produces a listing of any standard elements and subtypes in an

OS 2200 mass storage program file. It can also display whole files in octal, Fieldata,

ASCII, or decimal formats.

Programmers use the LIST processor to debug software that deals with program files.

LIST provides edited element listings, including the associated element control

information not normally of interest to a user. The primary function of the LIST

processor is to debug software that deals with program files. LIST can also display

whole files in octal, Fieldata, ASCII, or decimal formats.

The LIST processor can be used in either of two modes:

• Interactive file mode

The LIST processor provides an interactive system that enables you to work with

the file on the screen, listing any area of a file in ASCII, decimal, Fieldata, or octal.

Editing commands are provided to specify the relative address and length of the

listing. Editing functions enable you to edit a file.

• Predefined element mode

The LIST processor enables you to breakpoint an entire element to a file. This file

can be used to print a hard copy of the element or to make changes to it using a

text editor. In this mode, the output of the LIST processor is generally larger than

screen size.

LIST produces an edited listing of any standard element existing in an OS 2200 mass

storage program file including the associated element control information. LIST dumps

(lists) standard element types:

• Symbolic

• Relocatable

• Absolute

• Omnibus

The LIST processor is invoked through the use of an Exec control language (ECL)

statement.


The document LIST Processor End Use Guide (7831 3384) is available for this product on the Unisys Product Support Web site.

Multiple Batch Run Optimizer

11–16 7850 5252–018

11.12. Multiple Batch Run Optimizer

Multiple Batch Run Optimizer (formerly called ExPipe) is a workflow management tool

that can significantly reduce elapsed wall clock time for OS 2200 batch jobs that

execute sequentially.

With Multiple Batch Run Optimizer, the initial output of the first job is used by the

second job before the first job is complete, so the two runs can execute in parallel and

I/O overhead is reduced. Therefore, the execution time is reduced significantly,

sometimes up to 50 percent. In most cases, you can use the Multiple Batch Run

Optimizer without changing any program code. You simply modify the control

language to invoke it.

Multiple Batch Run Optimizer provides an interrun first-in first-out (FIFO) file capability

for application programs developed using the ASCII COBOL Compiler or the COBOL

Compiler as well as the Sort/Merge processor (SORT). The Multiple Batch Run

Optimizer increases the concurrency of execution steps and decreases the I/O

overhead and the amount of time required to execute specific batch programs.

No changes are required to your COBOL programs or SORT processor parameters if

they use Processor Common Input/Output System (PCIOS) sequential SDF files.

Otherwise, some changes are required.

As a batch run writes records to a FIFO file (also called a pipe), the Multiple Batch Run

Optimizer transfers them to up to three other concurrently executing batch runs. The

batch runs read the records from the FIFO file in the order they were written. Since I/O

to mass storage is eliminated, the batch run sequence is accelerated.

The execution of the batch runs is accelerated because of the Multiple Batch Run

Optimizer FIFO file implementation, which has the following characteristics:

• For each FIFO file, the Multiple Batch Run Optimizer allocates one shared

(application-level) bank that is divided into buffers to store blocks of records.

• Multiple Batch Run Optimizer does not assign mass storage back-up for FIFO files.

• Each FIFO file is transferred between runs using the buffers without the need for

I/O to mass storage.

• Since access to the FIFO file is sequential, as soon as all the succeeding runs finish

reading a block in a buffer, the Multiple Batch Run Optimizer discards the block

and prepares the buffer for reuse by another block.


The document Expipe User Guide (7846 7024) is available for this product on the Unisys Product Support Web site.

PostMortem Dump Processor

7850 5252–018 11–17

11.13. PostMortem Dump Processor

The PostMortem Dump (PMD) processor is used to dump basic mode programs from

main storage when the program terminates.

The PostMortem Dump (PMD) processor, called by the @PMD Exec Control Language

statement, is an OS 2200 Series system processor that creates a printout (dump) of

the main storage a program occupied when it terminated. At program termination, the

final contents of a program's main storage areas are written to the run's diagnostic file

by the Exec. The information is made available to be edited and printed by the PMD

processor. Postmortem dumps can be taken of

• Overlay segments

• Elements

• Banks

• Any portion of the terminated program as long as the segments, elements, or

banks are active at termination time

PMD is the historical low-level tool used to provide edited data to be used in

diagnosing and debugging programs. It has, to a large extent, been superseded by

more intuitive products that provide greater analytical capabilities and insights for the

user.

The nature of PMD processing is determined by call line options and parameters.

Options and parameters can be used to define when and if a dump is to be created,

what components are to be dumped, at which address dumping is to begin, the

number of words to be dumped, etc.

Options are referred to as being general or special.

General Options

The general options are

• C

Dumps the words that were changed during the execution of the allocated

program area of main storage specified in the @PMD statement.

• E

Processes @PMD control statement only if the previous program terminates in

error.

• P

Causes an octal dump of the program control table (PCT) blocks used by the run to

be printed preceding the dump of the program.

Procedure Definition Processor

11–18 7850 5252–018

Special Options

The special options are

• A

Produces a dump of the specified main storage area of each named element or

segment.

• D

Produces a dump of the data bank portion of each named element or segment.

• I

Produces a dump of the instruction portion of each named element or segment.

• L

Dumps the active library elements.

• X

Used in conjunction with the A, I, or D options. Dumps all active elements except

those named in the control statement and those belonging to the segments

named in the control statement.

PMD output is provided in edited numeric (octal) dump format, which is only useful to

people who are able to decode numeric dumps. For example

122727242705 222411125305 053136251244

is 6-bit fieldata for

"ERROR MODE: TYPE=".


The document Postmortem Dump (PMD) Programming Reference Manual


11.14. Procedure Definition Processor

Procedure Definition Processor (PDP) accepts symbolic input that defines a procedure

and builds a procedure element and associated procedure table entries in a

user-specified file. These procedures can subsequently be referred to by a language

processor during a compilation or assembly.

PDP accepts symbolic input that defines assembler (MASM) and high-level language

procedures and builds a procedure element and associated procedure table entries in

a user-specified file.

A MASM procedure, or PROC, is a predefined set of symbolic program logic that

carries out predefined operations on data specified by parameters. A procedure can

be called from anywhere within a program, with each call providing different input

parameters. For high-level languages, a PROC is a set of source language statements

that can be inserted into source language with an INCLUDE statement for FORTRAN

programs and with a COPY statement for COBOL programs.

Program-Callable FURPUR

7850 5252–018 11–19

The symbolic output of PDP consists of an unmodified copy of the symbolic input or

an updated copy of the symbolic input. The symbolic input can be updated by

specifying a source output procedure element on the PDP control statement and

entering correction images in the runstream following the PDP control statement,

followed by an end-of-file (@EOF) or other control statement.

PDP generates a procedure table entry in the source output file for each valid

procedure coded within the symbolic input. This entry contains information about the

symbolic entry point to the PDP procedure that can be referenced later by the

respective language processors. All procedure table entries generated by one

execution of PDP apply to the same procedure table (in other words, only one type of

procedure table is updated per execution of PDP).

The symbolic output is placed in a program file symbolic procedure element specified

by the symbolic output field on the @PDP statement. The element cycle of this

symbolic element is always zero (in other words, no "updating" of the symbolic input

element to a higher element cycle can be performed using PDP). Symbolic output is

the same character code as the symbolic input.

The symbolic output that PDP generates is accessible to you through other system

processors such as @ELT, @ED, and @CTS.


The document Procedure Definition Processor (PDP) Operations Reference Manual

(UP10070) is available for this product on the Unisys Product Support Web site.

11.15. Program-Callable FURPUR

Program-Callable FURPUR (PCFP) supports many of the file and element handling

capabilities of the FURPUR processor. It also provides file and element handling

capabilities that are not available in FURPUR.

Using PCFP, a programmer can perform FURPUR-like functions at run time in

applications written using the C Compiler, FORTRAN Compiler, and COBOL Compiler.

Results are returned to the program through the function packet and through returned

data structures.

PCFP can be called repeatedly from within a program. Some PCFP functions operate

on a single file; some functions operate on all members of a File cycle (F-cycle) set;

some functions operate on a source file and a destination file. PCFP can also be called

simultaneously from multiple activities running in the same program.

PCFP functions operate on two types of files:

• Random access files (RAF), also referred to as mass storage files. A number of

PCFP functions operate on a special type of RAF called a program file.

• Sequential access files (SAF), also referred to as tape files.

Relational Database Fast Load

11–20 7850 5252–018

PCFP functions can be performed in five steps:

1. Include the appropriate data definition elements in the program. These data definition elements are part of the PCFP product release.

2. Initialize the parameter packets.

3. Set values to indicate the precise operation to perform.

4. Call PCFP to perform the operation.

5. Check the returned status for successful completion.


The document Program-Callable FURPUR (PCFP) Programming Reference Manual


11.16. Relational Database Fast Load

Relational Database Fast Load (formerly called XRLOAD) is a utility that loads files into

a Relational Database Server for ClearPath OS 2200 database three times faster than

similar utility loaders. With this fast loading capability, it becomes feasible to maintain

and access large archived databases to support strategic queries. With the decrease

in elapsed time to load a database, you can rapidly modernize an environment to take

advantage of Relational Database Server capabilities.

The Relational Database Fast Load utility processor implements fast initial offline

loading of a large amount of data into a Relational Database Server database.

Relational Database Fast Load is a standalone utility. It does not access the Relational

Database Server.

Relational Database Fast Load includes its own storage manager, JETLOAD, to build

Relational Database Server B-trees.

Relational Database Fast Load uses the SORT processor to sort records for loading

• Into secondary index and unique constraint B-trees

• From a file that is not sorted in the table's primary key order

Comparison with the RDMUTL Processor

Relational Database Fast Load loads data faster than the RDMUTL processor's LOAD

command and is noticeably more effective if the database contains many secondary

indexes and unique constraints. JETLOAD always reads presorted record sets during

the loading process; it does not insert data randomly into secondary index and unique

constraint B-trees.

Relational Database Fast Load processes one LOAD command per call, while RDMUTL

enabless multiple LOAD commands per call. Relational Database Fast Load processes

one table per LOAD command, while RDMUTL enables multiple tables per LOAD

command.

Symbolic Stream Generator

7850 5252–018 11–21

The LOAD command for the Relational Database Fast Load and RDMUTL processors

are syntactically similar.


The document Relational Database Fast Load User Guide (7847 4889) is available for this product on the Unisys Product Support Web site.

11.17. Symbolic Stream Generator

Symbolic Stream Generator (SSG) is a general purpose interpreter that creates and

maintains many types of symbolic streams. Of particular importance are the symbolic

streams that generate, maintain, and update the system configuration for OS 2200

processors and libraries.

Symbolic Stream Generator (SSG) creates and controls a symbolic environment. It

directs and manipulates one or more symbolic input streams and creates one or more

symbolic output streams. Directions to build stream images are given to SSG through

a skeleton (program) written in Symstream language, an interpreted language.

Resulting symbolic output streams can be directed to files or elements and listed or

dynamically added (@ADD) before termination.

Symstream language statements control how the SSG processor operates. These

language statements make up a program, commonly called a skeleton. A skeleton is

one of many possible input streams to the SSG processor.

SSG can maintain the corrections to be applied to symbolic elements in program files.

These symbolic streams are the permanent correction file (PCF) and the temporary

correction file (TCF). SSG can merge correction streams with other correction streams,

list and place them in the generated output stream, and insert them into their original

files.

When SSG terminates, it dynamically adds (@ADD) the generated output to the

runstream. Optionally, SSG can direct the output to a file for subsequent examination

or use.

One of the main uses for SSG is generating the OS 2200 Exec, processors, and

libraries. SSG maintains and updates permanent corrections (PCF streams) by applying

input derived from temporary corrections (TCF streams), and skeleton-generated

corrections. It creates the appropriate runstream images to generate the proper

system configuration under the control of one or more skeletons.

An Exec control language (ECL) statement invokes the SSG processor. Processor

options determine the nature of processing.


The document Symbolic Stream Generator (SSG) Programming Reference Manual


Tape Labeling Utility for ClearPath OS 2200

11–22 7850 5252–018

11.18. Tape Labeling Utility for ClearPath OS 2200

Tape Labeling Utility for ClearPath OS 2200 is a site administration utility. It enables an

operator to

• Initialize new tapes (prelabel)

• Display existing tape labels

• Relabel existing tapes

• Erase old tape labels

The Tape Labeling Utility is an alternative to the TeamQuest® SAUtilities.

Tape Labeling Utility is an interactive program that can be run in batch mode or in

demand mode.

Tape Formats Supported

The Tape Labeling Utility supports all of the standard formats of tapes:

• ANSI X3.27-1987 (R1998)

• Unisys ASCII labeled tapes

• IBM EBCDIC labeled tapes

Tape Equipment

The Tape Labeling Utility supports all Unisys tape equipment including free-standing

drives, free-standing drives with auto-loaders, and tapes and drives in an ACS robotic

library.

11.19. TeamQuest Cross Reference Generator

TeamQuest® Cross Reference Generator (CULL) is a OS 2200 Series system software

product. It scans symbolic elements and generates a listing of the symbols that it finds

in the elements. The listing cross references the symbol to the line number and

element name in which it occurs. Each line number in the listing is a separate

occurrence of the symbol.

Programmers and system analysts use CULL to develop and maintain software.

CULL scans a specified set of symbolic elements and produces an alphabetical listing

of the symbols found in those elements, cross-referenced to the line numbers and

element names in which they occur.

CULL processes program files made up of one or more element subtypes by

1. Searching the table of contents of the file

2. Scanning each symbolic element using the scanner for that element subtype

3. Flagging the references according to how the symbol is used in the element

TeamQuest Interactive CULL

7850 5252–018 11–23

For example, CULL flags a reference with the letter "Q" if the symbol associated with

that reference appears in single quotation marks (' '). These flags vary depending on

the type of element being scanned.

Scanners

CULL uses the following types of scanners when scanning for the following symbols:

Assembler CTS LINK PL/I SSG

C Data Map PLUS/DCL SSDP

COBOL FORTRAN Pascal

CULL uses the scanner that corresponds to the element subtype you specify on the

processor call statement. For example, if you specify element subtype PAS in the

processor call statement, CULL uses the Pascal scanner to scan for symbols in all

elements with the PAS element subtype.

Symbol Table

Programmers have the option of using a special symbol table with CULL. The symbol

table is a series of character strings separated by blanks. The strings are the symbols

the programmer wants to either include in or exclude from the cross-reference listing.

The symbol table enables the programmer to tailor the cross-reference listing to a

specific set of symbols.



Support Web site:


• TeamQuest® CULL Operations Reference Manual (TQ-01061.7)

11.20. TeamQuest Interactive CULL

TeamQuest® Interactive CULL (IACULL) is a separately packaged feature of the Cross

Reference Generator (CULL). It enables programmers to interactively examine how a

symbol is used and to view the source code surrounding a symbol. As an option,

IACULL can produce a cross-reference listing similar to the one produced by CULL.

Like CULL, IACULL helps programmers and system analysts develop and maintain

software.

CULL shows programmers and system analysts where a symbol is referenced by

element name and line number. IACULL displays the actual lines of code where the

symbol is referenced. It also enables programmers to trace subroutine call references

interactively in either direction.

Utilization Report Utility for OS 2200

11–24 7850 5252–018

Intermediate File

IACULL needs an intermediate file produced by CULL. To create this file, a

programmer selects the elements or files to be processed and executes CULL with

the F option. The intermediate file contains pointers into the source code that was the

symbolic input scanned and sorted by CULL. Each time the source code changes the

programmer creates a new intermediate file.

IACULL Window

Upon command, IACULL displays a cross-reference listing of the desired symbol or

prints the lines of code that surround the symbol. IACULL maintains a window that is

placed over the symbolic input. The dimensions of the window and the line for cursor

return are variable. Also, the insert point is a variable. The insert point is the line on the

screen that displays the source code containing the reference of the symbol that CULL

has located.



Support Web site:


• TeamQuest® CULL Operations Reference Manual (TQ-01061.7)

11.21. Utilization Report Utility for OS 2200

The Utilization Report Utility (URU) is a reporting utility that is used to collect millions

of instructions per second (MIPS) usage data from the OS 2200 partition and generate

MIPS usage reports that are primarily used for billing purposes. However,

administrators can generate reports for informational purposes as well.

System Requirements

The URU Windows component can be installed on any workstation or server running

the following Microsoft Windows versions:

• Windows Server 2003

• Windows Vista


• Windows Server 2008 R2 (64-bit)

• Windows 7 (32-bit and 64-bit)

• Windows 8 (32-bit and 64-bit)

• Windows 8.1 (32-bit and 64-bit)


• Windows Server 2012 R2


7850 5252–018 11–25

Functions

The main function of the URU is to collect MIPS Metering data and generate MIPS

Utilization reports.


The document ClearPath Enterprise Servers Utilization Report Utility Help for OS

2200 (3826 6441) is available for this product on the Unisys Product Support Web site.


11–26 7850 5252–018

7850 5252–018 12–1

Section 12 Integrated Recovery

Integrated Recovery is a combination of OS 2200 software products (such as database

management, transaction processing, message handling, and Exec capabilities) that

are described elsewhere in this document. The Integrated Recovery Utility supports

the recovery and integrity of the component products.

This section describes the Integrated Recovery Utility (IRU).

12.1. Integrated Recovery Utility

Integrated Recovery Utility (formerly called IRU) combines and uses information

available from other Integrated Recovery components to recover and ensure the

integrity of files, databases, transaction messages, and queue items.

Integrated Recovery Utility is command-driven software that uses information

provided by the other Integrated Recovery components to protect and restore data

and messages according to your site's needs. Integrated Recovery Utility provides

standard recovery procedures used by Transaction Processing (TIP)/FCSS and

Universal Data System (UDS) database environments, and message control bank

(MCB) message environments. Using Integrated Recovery Utility commands, you can

form various layers of protection for your database files, transaction messages, and

system processing.

Integrated Recovery Utility is used to

• Perform regular backups to prevent loss of data.

• Recover corrupted or lost data to its original state.

• Aid recovery management.

• Decrease the chance of disk failure.

• Monitor the condition of files.

• Archive a mass storage audit trail file to tape.

• Dump (back up) files, reload files, collect and dump changes made since the last

full database dump.

Integrated Recovery Utility

12–2 7850 5252–018

IRU commands are used to perform the following types of recovery:

• Short recovery (SHORT RECOVER command)

• Medium recovery (MEDIUM RECOVER command)

• Long recovery (RECOVER command)

• Remote Recovery (RECOVER REMOTE command)

The components of an Integrated Recovery system are

• Exec Step Control, Exec Audit Control

• Transaction Processing (TIP) File Control (TFC)


• Integrated Recovery Utility

• Universal Data System (UDS)



Support Web site:

• Integrated Recovery Conceptual Overview (7830 8186)

• Integrated Recovery Utility Administration Guide (7833 1576)

• Integrated Recovery Utility Operations Guide (7830 8194)

• ClearPath OS 2200 Integrated Recovery Reference and Administration Guide

(3826 4842)

• ClearPath OS 2200 Integrated Recovery Reference and Administration Guide for

Multihost Environments (7831 0919)

7850 5252–018 A–1

Appendix A Acronyms and Abbreviations

This appendix defines the acronyms and abbreviations used in this overview and

related Unisys documentation.

A

ACI Audit Control Interface (file)

ACOB ASCII COBOL Compiler

ACR access control record

ACS Automatic Cartridge System

ACSLS Automatic Client Server Library Software

ADP Application Definition Processor

ADT application definition table

AFCB alternate file common bank

ALAU ASCII Log Analysis Utility

AM authentication modules

AMS Autoaction Message System

ANSI American National Standards Institute

ARC Automatic Recovery of Components

ASCII American Standard Code for Information Interchange

ASIS Authentication and Session Initiation Subsystem

ATM asynchronous transfer mode

ATMCA Asynchronous Transfer Mode Channel Adapter

B

BDI bank descriptor index

BIF Built-in function

BIS Business Information Server

BMC block multiplexer channel

Acronyms and Abbreviations

A–2 7850 5252–018

C

CA channel adapter

CADIS Cache/Disk Interface Software

CAM channel adapter microcode

CARTIS Cartridge Tape Interface Software

CARTLIB Cartridge Library

CBD common bank descriptor

CCS coded character sets

CD Communications Delivery

CEC central electronics complex

CER Customer Engineering Request

CHG Change document (formerly PCR)

CIFS Common Internet File System

CIOP Communications I/O processor for Ethernet connections

CIPHER-API Cipher Application Programming Interface

CITA Communications Interface for Transaction Applications

CKRS Checkpoint/Restart

CLU cartridge library unit

CMF Capacity Management Facility

CML Common Mathematical Library

CMR Console Message Redisplay

CMSR Customized Media Summary Report

COMAPI Communications Application Program Interface

COMPOOL communications message-buffer pool

COMUS COMUS

CPComm Communications Platform

CPCommOS Communications Platform for Open Systems

cpFTP FTP Services for ClearPath OS 2200

CSC Client System Component

CSIOP Compatible channel I/O processor

CSS Client Support Services

CTL Cartridge Tape Library

CULL TeamQuest® Cross Reference Generator

CWP Client Workstation PCI


7850 5252–018 A–3

D

DAD Device Area Descriptor

DAP Dump Analysis Procedures

DATAEXTRACTOR Data Extractor

DCA Distributed Communications Architecture

DCP Distributed Communications Processor

DDA Data Dependent Attribute

DDN 1100 Defense Data Network software

DDP Distributed Data Processing

DDP-FJT Distributed Data Processing File and Job Transfer

DDP-PPC Distributed Data Processing Program-to-Program Communications

DEPCON Enterprise Output Manager (Windows software)

DEPCON-2200 Enterprise Output Manager for ClearPath OS 2200 (host software)

DFP Define File Processor

DML data manipulation language

DMPLIB Dump Library

DMS Enterprise Network Database Server for ClearPath OS 2200

DMS-RA Network Database Server Resource Adapter for the JavaTM Platform

DMU Data Management Utility

DPREP1100 Disk Preparation Utility

DPS Display Processing System

DROC data reduction

DRS disk resident system

DRU Data Reorganization Utility

DSPER Diagnostic Software Peripheral Equipment Routines

DSR dynamic system reconfiguration

DSS Display System Services

DTI Distributed Transaction Integration

DTP Distributed Transaction Processing


A–4 7850 5252–018

E

EBRS Enterprise Backup and Restore

ECL Executive Control Language

ECLIPSE-2200 Eclipse IDE for OS 2200

ED OS 2200 Text Editor

EDRC Enhanced Data Recording Capability

ELMS Extended Language Message System

ELT Element Processor

EM Extended Mode

EPORTAL-2200 ClearPath ePortal for OS 2200

ER Executive request

ESQL embedded SQL

ESS Electronic Support Services

EUR encryption user routine

EXEC OS 2200 Executive

EXPIPE Multiple Batch Run Optimizer

EXPOOL Exec buffer pool

F

FAS File Administration System

FBCIS Fixed Block Compatible Interface Software

FC-AL Fibre Channel Arbitrated Loop

FCSS file control superstructure

FDP File Definition Processor

FDT file description table

FGSS fixed-gate shared subsystems

FIPS Federal Information Processing Standards

FJT File and Job Transfer

FLEX User Authentication

FLIT Fault Location by Interpretive Testing

FLSS Fast Load Subsystem

FREIPS Freespace Integrated Processing System

FSAH Free Standing Audit Handler

FTA Fast Tape Access

FTN ASCII FORTRAN compiler


7850 5252–018 A–5

FTP File Transfer Protocol

FURPUR File Utility Routines/Program Utility Routines

G

GIN Graphics Input

GRS general register set

GSA General Syntax Analyzer

H

HLC Host LAN Controller

HMP Heterogeneous multiprocessing

HVTIP High-Volume Transaction Processing

I

I18NLIB Internationalization Service Routine Library

I18NLIB Assistant Online help for Internationalization Service Routine Library

IACULL TeamQuest® Interactive Cross Reference Generator

INFOACCESS ODBC Access for ClearPath OS 2200

Interconnect Interconnect

IOE Integrated Operating Environment

IOCQ I/O command queuing

IP instruction processor

IPCC interprocessor channel coupler

IPF Interactive Processing Facility

IPF SQL IPF 1100 Structured Query Language

IRU Integrated Recovery Utility

IS Information Services

IVP installation verification procedure

J

J2EE Java 2 Platform, Enterprise Edition

J2EE-CON-OS2200 OS 2200 Transaction Resource Adapter for the Java™ Platform

J2EE-CON-OpenDTP Open Distributed Transaction Processing Resource Adapter for the

JavaTM Platform

JBOSS-2200 JBoss Enterprise Application Platform for ClearPath OS 2200


A–6 7850 5252–018

JDBC Java DataBase Connectivity

JNI Java Native Interface

JPJVM Virtual Machine for the Java™ Platform on ClearPath OS 2200

JProcessor

L

LA TeamQuest® Log Analyzer

LAN local area network

LBDI Level and bank descriptor

LDAT Logical Device Address Table

LEPF Large element program file

LFI Log File Interface

LINC Logic and Information Network Compiler

LINK Linking System

LIST List Processor

LPF large program file

LSS Language Support System

LTO Linear Tape Open

M

MAP Collector

MAPPER Business Information Server for ClearPath OS 2200

MASM Meta-Assembler

MCB Message Control Bank

MCN Manufacturing Control Number

MFAS Mini-FAS

MFD master file directory

MHFS Multi-Host File Sharing

MMGR Media Manager

MPE Modular Processor EISA-Bus

MSAR TeamQuest® Mass Storage Analysis and Relocation processor

MSB Monitor Services Bank

MSCP Monitor Services Control Program

MSMANAGER TeamQuest® Mass Storage Manager


7850 5252–018 A–7

N

NIC network interface card

NIOP network input output processor

NTLM Windows NT LAN Manager

NTSI Messaging Integration Services

O

OADE Programmer’s Workbench for ClearPath OS 2200

ODTP Open Distributed Transaction Processing

OLE-DB-OS2200 Network Database OLE DB Data Provider for ClearPath OS 2200

OLTP online transaction processing

OPE Open Programming Environment

OPE-TP Open Programming Environment

OPENTI Open Transaction Integrator

OSAM TeamQuest Online System Activity Monitor

OSG Operating System Group

OSI Open Systems Interconnection

OSI-TP Open Systems Interconnection Transaction Processing

P

PADS Programmers Advanced Debugging System

PAR TeamQuest® Performance Analysis Routines

PBD page bank descriptor

PCF permanent correction file

PCFP Program-Callable FURPUR

PCIOP peripheral component interconnect input output processor

PCIOS Processor Common Input/Output System

PCR program control and registration

PCT program control table

PDP Procedure Definition Processor

PFP Program File Package

PLE problem list entry

PLUS Programming Language for Unisys Systems


A–8 7850 5252–018

PMD PostMortem Dump

PPC Program-to-Program Communications

Q

QBR Queue Bank Repository

QLP Query Language Processor

R

RDMS Unisys Enterprise Relational Database Server for ClearPath OS 2200

RDMS-JDBC RDMS-JDBC is required to access Relational Database Server data from

JBoss applications.

RDT relational table definition

RLP record lock processor

RMI/IIOP Remote Method Invocation/Internet Inter-ORB Protocol

ROLRUNS Roll-out/Roll-back Runstream

RQA Relational Query Accelerator

RSA Relational Syntax Analyzer

RSS Remote System Support

S

SAUTILITIES TeamQuest® Site Administrator Utilities

SAS Sentinel Alert Service

SBCON Single-byte command code set connection

SBF system boot file

SCF System Control Facility

SCIOP Standard channel I/O processor

SCMS Site Configuration Management System

SCN Software Control Number

SCP Software Controlled Performance

SCSI small computer system interface

SCSITIS SCSI Tape Interface Software

SCSS self-contained shared subsystem

SDD symbolic debugging dictionary

SDDL Subschema Data Definition Language

SDF Site Data Facility (also – system data format)

SECOPT Security Level (Option)

SECURITY-ADMIN Security Administration for ClearPath OS 2200


7850 5252–018 A–9

SFS Shared File System

SGS stream generation statement

SHA SCSI host adaptor

SILAS System Interface for Legacy Applications Systems

SIMAN TeamQuest® Site Management Complex

SINCH Interconnect Channel Handler

SIOP Storage I/O processor

SIP Software Instrumentation Package

SIPIPM SIP Internal Performance Monitor

SLAR System Log Analysis and reports

SLIB Service Library

SLRR System Log Read Routines

SNA Systems Network Architecture

SNMP-AGX2200 SNMP Agent for ClearPath OS 2200

SOLAR Software Library Administrator

SOLAR/E Software Library Administrator/Extended

SORT Sort/Merge

SPAIR Software Product Application Initialization and Recovery

SPEF Separately Packaged Exec Features

SP-OPERATIONS Operations Sentinel, formerly known as Single Point Operations.

SQL Structured Query Language

SSAM Site Specific Authentication Modules

SSDP Subsystem Definition Processor

SSG Symbolic Stream Generator

SSL/TLS Secure Sockets Layer/Transport Layer Security

SUP standard unit of processing

SYSLIB System Service Routines Library

T

TAS TCP/IP Application Services

TAVR Tape Automatic Volume Recognition

TCDBF TIP Common Data Bank File

TCP/IP transmission control protocol/Internet protocol

TIF Tape Inventory File

TIP Transaction Processing

TPM TIP Performance Monitor


A–10 7850 5252–018

TQ-BASELINE TeamQuest Baseline®

TQ-DFRAGGER TeamQuest® D-Fragger defragments fixed mass storage.

TQ-MODEL TeamQuest Model®

TQ-ONLINE TeamQuest Online®

TQ-PMLOG TeamQuest® PMLog

TQ-PROBES TeamQuest® Probes

TQ-REMDFRAGGER TeamQuest® RemD-Fragger defragments removable mass storage.

TQ-TIP-LA TeamQuest® TIP Log Analyzer

TSAM Transport Service Access Method

TS/TN termination system/transport network

TSU transport service user

TUTIL Tape Labeling Utility

U

UC C Compiler

UCF User Communication Form

UCOB COBOL Compiler

UCPP C++ Compiler

UCS Universal Compiling System

UCSRTS Runtime System for Basic Mode Compilers

UDLS universal data link control

UDS Universal Data System

UDSC Universal Data System Control

UFTN FORTRAN Compiler

UNIACCESS-ODBC UniAccess for OS 2200 Systems

UOE Unisys Operating Environment

UOFACU Unattended Operations Facilities Automated Control Unit

UOFAPC Automated Power Control

UPLS UCS PLUS

UREP Repository for ClearPath OS 2200

URTS Runtime System for Extended Mode Compilers

URU-OS2200 Utilization Report Utility for OS 2200

UTS universal terminal system


7850 5252–018 A–11

V

VALTAB validation table

W

WAD Word addressable file

WEBTS Unisys Web Transaction Server for ClearPath OS 2200

WEBTX Transaction Integrator

WMQ2200 WebSphere® MQ Version 7 for ClearPath OS 2200

X

XIOP eXtended I/O Processor for connection to the XPC-L

XML Extensible Markup Language

XMLPROVIDER XML Provider for ClearPath OS 2200

XPC Extended Processing Complex

XPC-L Extended Processing Complex-Locking

XRF XPC resident file

XRLOAD Relational Database Fast Load

XTC Extended Transaction Capacity

XTCEXEC Exec Component of XTC Software

XTP Extended Transaction Processing

XTPA Extended Transaction Processing Architecture

Z

ZOOM zero overhead object module


A–12 7850 5252–018