ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 

Software Planning and Migration Overview 

for Release 13.2 

ClearPath OS 2200 Release 13.2 

October 2012 7831 0349–043 

unisys

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

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

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

products described in this document are set forth in such agreement. Unisys cannot accept any financial or other 

responsibility that may be the result of your use of the information in this document or software material, including 

direct, special, or consequential damages. 

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

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

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

changes and/or additions. 

Notice to 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. 

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

be trademarks of their respective owners. 

Java EE and Java SE are trademarks of Oracle in the U.S. and other countries. 

JBoss® is a registered trademark and JBoss Application Server is a trademark of Red Hat, 

Inc. and its subsidiaries in the U.S. and other countries. 

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

trademarks or registered trademarks of their respective holders.

Contents 

Section 1. Introducing ClearPath OS 2200 Release 13.2 

1.1. Highlights for ClearPath OS 2200 Release 13.2 ...................... 1–3 

1.1.1. New Major Capabilities ................................................... 1–3 

1.1.2. OS 2200 Master Glossary ............................................... 1–3 

1.2. Software Delivery on CD/DVD Media ...................................... 1–4 

1.3. Product Status Summary ......................................................... 1–4 

1.4. Separately Packaged Exec Features (SPEF) .......................... 1–10 

1.5. Support................................................................................... 1–11 

1.6. Locating Terms Using CDLib Manager Search ...................... 1–12 

1.6.1. Installing and Opening CDLib Manager ........................ 1–12 

1.6.2. Performing a Search ...................................................... 1–13 

1.6.3. Setting the Viewer Path ................................................ 1–13 

1.6.4. For More Information .................................................... 1–14 

Section 2. New Products and Updated Features 

2.1. DAP Level 14R2 ....................................................................... 2–1 

2.2. Exec Level 48R8A .................................................................... 2–2 

2.3. FLIT Level 14R2 ....................................................................... 2–3 

2.4. TQ-BASELINE Level 7R4F ....................................................... 2–3 

2.5. TQ-MODEL Level CP13.2 ........................................................ 2–3 

2.6. TQ-ONLINE Level 7R4F ........................................................... 2–3 

Section 3. Software Considerations, Management, and 

Delivery 

3.1. Considerations ......................................................................... 3–1 

3.2. Internet Protocol Version 6 (IPv6) Support ............................ 3–11 

3.3. Discontinued Products ........................................................... 3–14 

3.4. Future Considerations ............................................................ 3–15 

3.4.1. Notice of Intent to Remove Software ........................... 3–15 

3.4.2. Notice of Intent to Remove Hardware .......................... 3–15 

3.5. Software License Management ............................................ 3–16 

3.5.1. Definitions ..................................................................... 3–16 

3.5.2. Software License Management .................................... 3–18 

3.5.3. Ordering ClearPath OS 2200 Software ......................... 3–19 

3.5.4. System Upgrade Information ........................................ 3–19 

3.5.5. Registering Your Software Product Keys ...................... 3–20 

3.5.6. Frequently Asked Questions ......................................... 3–21 

3.6. Software License Management and 

LIBSAVE/LIBLOAD ............................................................ 3–23 

3.6.1. LIBSAVE/LIBLOAD Examples ....................................... 3–23 

7831 0349–043 iii

Contents 

3.6.2. Example 1: Performing a LIBLOAD onto 

System B ................................................................... 3–25 

3.6.3. Example 2: Performing a LIBLOAD onto 

System C ................................................................... 3–27 

3.7. Keyed Tape Delivery ............................................................... 3–29 

3.7.1. Nonkeyed Products ........................................................ 3–31 

3.7.2. Key Package Registration .............................................. 3–32 

3.8. License Keys for TeamQuest Products .................................. 3–32 

3.8.1. Updating Keys ................................................................ 3–33 

3.8.2. Product License Registration for Your OS 2200 

Host ........................................................................... 3–35 

3.8.3. Product License Registration for your PC 

(TeamQuest Model Only) .......................................... 3–35 

3.8.4. Obtaining a Registered Product License Key ................ 3–36 

3.9. Build Option ............................................................................ 3–36 

3.10. Dorado 400, 4000, 4100, and 4200 Server Systems 

Terminology Overview ....................................................... 3–37 

3.10.1. Administration and Operation Components .................. 3–38 

3.11. Dorado 300 and 700/800 Server Systems Terminology 

Overview ............................................................................ 3–39 

3.12. ClearPath and Plateau Interdependencies .............................. 3–41 

3.13. ClearPath Specialty Engines Interdependencies .................... 3–44 

3.13.1. OS 2200 JProcessor ...................................................... 3–44 

3.13.2. OS 2200 QProcessor ..................................................... 3–47 

3.14. Microcode Requirements for CTS5236 and T9840A 

Tape Drives ........................................................................ 3–48 

3.15. Supported Peripheral Products ............................................... 3–48 

Section 4. Exec Software Compatibility and Migration 

Considerations 

4.1. General Exec Considerations .................................................... 4–2 

4.1.1. ClearPath OS 2200 Release 13.1 ..................................... 4–2 




4.1.5. LIBSAVE/LIBLOAD Scenario............................................ 4–6 

4.1.6. I/O COMMAND QUEUING (IOCQ) .................................. 4–6 

4.2. SGS and Configuration Parameters .......................................... 4–8 

4.2.1. MODEL_TYPE Statement ................................................ 4–8 

4.3. Migrating from a Nonmetered System to a Metered 

System ................................................................................. 4–9 

4.4. Log Entry Changes ................................................................... 4–9 

4.5. XPC-L ...................................................................................... 4–10 

4.6. Tape and DVD ......................................................................... 4–10 

4.6.1. Tape ............................................................................... 4–10 

4.6.2. Tape Drive Encryption .................................................... 4–12 

4.6.3. 36-Track Tape Subsystems ............................................ 4–14 

4.6.4. DLT 7000 and DLT 8000 Tape Subsystems .................. 4–18 

4.6.5. Linear Tape Open Ultrium LTO3-HP Tape Drives .......... 4–21 

4.6.6. Linear Tape Open Ultrium LTO4-HP Tape Drives .......... 4–22 

iv 7831 0349–043

Contents 

4.6.7. T9840A Tape Subsystem .............................................. 4–23 

4.6.8. T9840C Tape Subsystem .............................................. 4–26 

4.6.9. T9840D Tape Subsystem .............................................. 4–28 

4.6.10. T10000A Tape Subsystem ............................................ 4–31 

4.6.11. T9840D and T10000A Applicable .................................. 4–32 

4.6.12. T9940B Tape Subsystem .............................................. 4–33 

4.6.13. CSC, ACSLS, and CARTLIB ........................................... 4–36 

4.6.14. Software Delivery on DVD Media ................................. 4–36 

4.6.15. Virtual Tapes .................................................................. 4–37 

4.7. TIP .......................................................................................... 4–37 

4.7.1. General .......................................................................... 4–37 

4.7.2. ClearPath OS 2200 Release 13.2 .................................. 4–38 

4.7.3. ClearPath OS 2200 Release 13.1 .................................. 4–38 




4.8. Software Controlled Performance (SCP) ............................... 4–40 

4.8.1. Manufacturing Control Number Expansion ................... 4–41 

4.8.2. PDB_MFG_CONTROL_NUMBER ER CONFIG$ 

Changes .................................................................... 4–41 

4.9. POSTOEXMSTR ..................................................................... 4–42 

Section 5. OS 2200 Software Compatibility and Migration 


5.1. Summary of Considerations..................................................... 5–1 

5.2. Business Information Server (BIS or MAPPER) ....................... 5–1 

5.3. CIFS .......................................................................................... 5–2 

5.4. Cipher API ................................................................................ 5–2 

5.5. Checkpoint/Restart (CKRS) ...................................................... 5–4 

5.6. COMAPI ................................................................................... 5–4 

5.7. Communications Platform (CPComm) ..................................... 5–6 

5.8. Communications Platform for Open Systems 

(CPCommOS) ...................................................................... 5–6 

5.8.1. CPCommOS Example IPv4/IPv6 Configuration ............ 5–11 

5.9. COMUS .................................................................................. 5–13 

5.10. cpFTP ..................................................................................... 5–15 

5.11. DMS-RA ................................................................................. 5–16 

5.12. DPS ........................................................................................ 5–17 

5.13. Distributed Data Processing File and Job Transfer 

(DDP-FJT) ........................................................................... 5–17 

5.14. Distributed Data Processing Program-to-Program 

Communications (DDP-PPC) ............................................. 5–18 

5.15. ECLIPSE-2200 ........................................................................ 5–19 

5.16. ELMS ..................................................................................... 5–20 

5.17. Enterprise Output Manager (EOM) ........................................ 5–20 

5.18. Enterprise Network Database Server (DMS) ......................... 5–22 

5.19. Enterprise Relational Database Server (RDMS) ..................... 5–23 

5.20. FURPUR ................................................................................. 5–25 

5.21. HTPIC-2200 ............................................................................ 5–26 

5.22. Integrated Recovery Utility (IRU) ........................................... 5–26 

7831 0349–043 v

Contents 

5.23. Interactive Processing Facility (IPF) ........................................ 5–30 

5.24. Internationalization Library (I18NLIB) ...................................... 5–30 

5.25. OS 2200 Transaction Resource Adapter for the Java 

Platform (J2EE-CON-OS2200) ............................................ 5–30 

5.26. Language Support System (LSS) ............................................ 5–31 

5.27. Linking System (LINK) ............................................................ 5–31 

5.28. Message Control Bank (MCB) ................................................ 5–32 

5.29. MSMQI ................................................................................... 5–32 

5.30. Messaging Integration Services (NTSI) .................................. 5–33 

5.31. MQSeries for ClearPath OS 2200 (MQS2200) ....................... 5–33 

5.32. ODBC Data Access (INFOAccess) ......................................... 5–34 

5.33. Open Distributed Transaction Processing (Open DTP) 

(OLTP-TM2200) .................................................................. 5–35 

5.34. Open Programming Environment (OPE) ................................ 5–35 

5.35. Operations Sentinel Basic Edition (Formerly Single 

Point Operations) ................................................................ 5–40 

5.36. OSI-TP ..................................................................................... 5–41 

5.37. RDMS-JDBC ........................................................................... 5–41 

5.38. Remote System Support (RSS) .............................................. 5–42 

5.38.1. Configuration Requirements .......................................... 5–42 

5.38.2. RSS Operations Considerations ..................................... 5–43 

5.39. Repository for ClearPath OS 2200 (UREP) ............................. 5–43 

5.40. Runtime System for Extended Mode Compilers 

(URTS) ................................................................................ 5–45 

5.41. Security-Admin ....................................................................... 5–46 

5.42. SLIB ........................................................................................ 5–46 

5.43. SOLAR and SOLAR/E ............................................................. 5–46 

5.44. Sort/Merge (SORT) ................................................................. 5–49 

5.45. SSG ......................................................................................... 5–49 

5.46. SYSLIB .................................................................................... 5–50 

5.47. Tape Labeling Utility for ClearPath OS 2200 (TUTIL) .............. 5–52 

5.48. TCP/IP Application Services (TAS) .......................................... 5–52 

5.49. TeamQuest Products .............................................................. 5–53 

5.49.1. TeamQuest Model ......................................................... 5–53 

5.49.2. TeamQuest OSAM ........................................................ 5–53 

5.49.3. TeamQuest PAR ............................................................ 5–53 

5.49.4. TeamQuest SAUtilities ................................................... 5–54 

5.49.5. TeamQuest SIMAN (SIMAN) ......................................... 5–54 

5.49.6. TeamQuest TIP-LA ......................................................... 5–56 

5.50. UniAccess-ODBC.................................................................... 5–56 

5.51. Universal Database Control (UDSC) ....................................... 5–56 

5.52. Utilization Report Utility for OS 2200 (URU-OS2200) ............. 5–57 

5.53. Virtual Machine for Java Platform (JVM) ................................ 5–59 

5.54. Virtual Machine for the Java Platform on ClearPath 

OS 2200 JProcessor (JPJVM) ............................................ 5–60 

5.55. Web Transaction Server (WEBTS) .......................................... 5–61 

5.56. WebSphere® MQ Version 7 for ClearPath OS 2200 

(WMQ2200) ........................................................................ 5–61 

vi 7831 0349–043

Section 6. Workstation-Based Software Considerations 

Contents 

6.1. ClearPath OS 2200 Release 13.2 ............................................. 6–1 

6.1.1. Enterprise Output Manager Workstation 

Requirements ............................................................. 6–1 

6.1.2. TeamQuest Model (TQ-MODEL) .................................... 6–1 

6.1.3. TeamQuest View (TQ-VIEW) ........................................... 6–1 

6.1.4. Web Transaction Server .................................................. 6–2 

6.2. Windows-Based Software Considerations .............................. 6–2 

6.2.1. Enterprise Output Manager (EOM) ................................. 6–2 

6.2.2. Operations Sentinel (SPO) .............................................. 6–2 

Section 7. Installing ClearPath OS 2200 Release 13.2 Software 

7.1. Migration Planning Checklist.................................................... 7–2 

7.2. Installation Considerations ....................................................... 7–3 

7.3. Other Considerations ............................................................... 7–3 

7.4. Description of Fast-Load Tapes ............................................... 7–5 

7.5. Migration Sequences ............................................................... 7–5 

7.6. Installing from Fast-Load Tapes ............................................... 7–6 

7.7. Installing from Package Tapes ............................................... 7–15 

7.8. Initializing an Existing System (I-Boot) ................................... 7–26 

7.9. Migration for Existing Dorado 4000 Customers .................... 7–35 

7.10. Migration for Existing Dorado 400 Customers ...................... 7–37 

7.11. Migration for Existing Dorado 4100 Customers .................... 7–38 

Section 8. Operations Sentinel (Formerly Single Point 

Operations) 

Appendix A. Media Contents 

A.1. Software Packaging ................................................................. A–1 

A.2. Dorado Models 800, 700, and 300 Workload IOE 

Package ............................................................................... A–3 

A.3. Dorado Models 800, 700, and 300 Workload UOE 

Package ............................................................................... A–9 

A.4. ClearPath Dorado Model 400, 4000, 4100, and 4200 

Workload Image IOE Basic Package ................................. A–16 

A.5. ClearPath Dorado Model 400, 4000, 4100, and 4200 

UOE Basic Package Software ........................................... A–22 

Appendix B. Product Interdependencies 

Appendix C. Fast Load and Package Tape Contents 

C.1. Logical Package Tape Definition .............................................. C–1 

C.2. Products on Fast-Load Tapes .................................................. C–2 

C.2.1. Fast-Load Tapes CP-FLD/CP-FLD400.............................. C–2 

C.2.2. Fast-Load Tape CP-OE1A ................................................ C–3 

7831 0349–043 vii

Contents 

C.2.3. Fast-Load Tape CP-OE1B................................................ C–3 

C.2.4. Fast-Load Tape CP-OE2 .................................................. C–5 

C.3. Products on Package Tapes .................................................... C–5 

Appendix D. BDI Allocation 

D.1. BDI Types ................................................................................ D–1 

D.1.1. Fixed BDI......................................................................... D–1 

D.1.2. Dynamic BDI ................................................................... D–1 

D.2. BDI System Generation Parameters ....................................... D–2 

D.2.1. MAXBDI .......................................................................... D–2 

D.2.2. Basic Mode BDIs ............................................................ D–2 

D.3. BDI Groups .............................................................................. D–3 

D.4. Customer BDIs ........................................................................ D–4 

D.5. BDI Allocation Listing .............................................................. D–5 

Appendix E. Acronyms and Abbreviations 

Glossary ............................................................................................. 1 

Index ............................................................................................. 1 

viii 7831 0349–043

Tables 

1–1. Product Status Summary ................................................................................... 1–5 

3–1. IPv6 Product Support Status ............................................................................ 3–12 

3–2. Products that use IP addresses but do not currently support IPv6 ................. 3–13 

3–3. Software Products and Features Not Supported in ClearPath OS 2200 

Release 13.2 ................................................................................................ 3–14 

3–4. Dorado 300/700/800 and 400/4000/4100/4200 Systems Terminology 

Comparison .................................................................................................. 3–37 

3–5. Dorado 300/700/800 and 400/4000/4100/4200 Systems IOPs 

Comparison .................................................................................................. 3–37 

3–6. 300/700/800 Server Systems Terminology ...................................................... 3–39 

3–7. Dorado 300/700/800 Server Systems IOPs ..................................................... 3–40 

3–8. ClearPath Dorado Plateau Interdependencies Without XPC-L Support ........... 3–41 

3–9. ClearPath Dorado Plateau Interdependencies with XPC-L Support ................. 3–42 

3–10. CPCommOS Plateau Component Requirements ............................................ 3–43 

4–1. Tape Assign Mnemonics ................................................................................. 4–11 

4–2. Capabilities Supported by the Exec ................................................................. 4–19 

4–3. SCSI and SBCON Compatibility Matrix ............................................................ 4–25 

4–4. Cartridge Read/Write Capability ....................................................................... 4–30 

4–5. T9840D and T10000A Summary of Features .................................................. 4–32 

4–6. DVD Assign Mnemonics .................................................................................. 4–37 

5–1. Summary of Considerations ............................................................................... 5–1 

7–1. Migration Requirements for Fast-Load Tapes ................................................... 7–8 

7–2. Migration Requirements for Package Tapes .................................................... 7–17 

7–3. Dorado 4000 Plateau and ClearPath Release Interdependencies ................... 7–36 

7–4. CP-FLD400 Logical Package Tape Contents for Dorado 400 .......................... 7–37 

7–5. Dorado 400 Plateau and ClearPath Release Interdependencies ..................... 7–38 

A–1. Dorado Models 800, 700, and 300 Workload IOE Software ............................. A–4 

A–2. Dorado Models 800, 700, and 300 Workload UOE Software .......................... A–10 

A–3. ClearPath Dorado Model 400, 4000, 4100, and 4200 IOE Software ............... A–16 

A–4. ClearPath Dorado Model 400, 4000, 4100, and 4200 UOE Basic 

Package Software ........................................................................................ A–22 

B–1. Products Interdependency Matrix ...................................................................... B–2 

B–2. Optional Product Interdependency Notes ....................................................... B–10 

C–1. Tape CP-FLD Fast-Load Tape Contents ............................................................. C–2 

C–2. Tape CP-OE1A Fast-Load Tape Contents .......................................................... C–3 

C–3. Tape CP-OE1B Fast-Load Tape Contents .......................................................... C–3 

7831 0349–043 ix

Tables 

C–4. Tape CP-OE2 Fast-Load Tape Contents ............................................................ C–5 

C–5. DVD Package Tape Contents............................................................................. C–5 

D–1. BDI Allocation .................................................................................................... D–5 

x 7831 0349–043

Section 1 

Introducing ClearPath OS 2200 Release 

13.2 

This ClearPath OS 2200 Release is an integrated package of software products that 

continues support for existing ClearPath Dorado servers. 

Following is a list of hardware systems supported in this release. 

Nonmetered Systems Metered Systems 

Dorado 320 Dorado 330 












Dorado 4270 

Dorado 4290 

Dorado 850 

Dorado 870 

Dorado 890 

This release was tested on a product level and system level to ensure that the system 

and all of its products operate as one cohesive unit. This release includes all the currently 

supported functional capabilities introduced in previous levels. 

This overview provides essential information required for sites moving from an earlier 

release to the current ClearPath OS 2200 Release. Installation and generation issues, 

compatibility considerations, and other technical considerations are described in detail. 

7831 0349–043 1–1

Highlights for ClearPath OS 2200 Release 13.2 

Updated Terminology 

ClearPath documents are being updated to include the terminology that defines the 

ClearPath OS 2200 systems, based on the technical architectures of their system types, 

as follows: 

• Complementary Metal-Oxide Semiconductor (CMOS) is the 2200 instruction 

processor implementation technology in the associated system types. CMOS 

systems include Dorado 300/700/800 systems. 

• System Architecture Interface Layer (SAIL) is the software environment in which the 

soft 2200 instruction processor executes in the associated system types. 

SAIL-based systems include Dorado 400/4000/4100/4200 systems and Cloud 

systems. 

• The general reference is to ClearPath OS 2200 systems if no architecture-based 

distinction is necessary. 

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) 18895005. To obtain a copy of the PLE, contact your Unisys service 

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

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

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

Software Release Updates 

Software changes identified after release are included in problem list entry (PLE) 

18881454. To obtain a copy of the PLE, contact your Unisys service representative or 

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

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

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

The following subsections identify highlights and other important aspects of this release. 

A table lists the product levels and status of each product in this release. Another table 

describes new and updated features for each product. Separately packaged Exec 

features are also identified. Certain products and features that are no longer supported 

are listed later in this overview. 

1–2 7831 0349–043

Highlights for ClearPath OS 2200 Release 13.2 

1.1. Highlights for ClearPath OS 2200 Release 13.2 

ClearPath OS 2200 continues to build on mission critical leadership in performance, 

scaling, availability, recovery, security, application agility, and integration. The following 

are the new major capabilities for the 13.2 release. 

1.1.1. New Major Capabilities 

The ClearPath OS 2200 Release 13.2 is the latest Unisys Integrated Software Stack that 

is developed, integrated, and tested for the ClearPath Dorado systems. 

With 112 Unisys software products, OS 2200 Release 13.2 is built on the successes of 

OS 2200 Release 13.1 to deliver stability updates for the new Dorado 4200 Series. The 

Dorado 4200 system is the third generation of Intel-based servers released for the 

OS 2200 operating environment. These new platforms provide a single image 

performance of approximately 300 MIPS with a combined system performance to 2,300 

MIPS. This translates into a single image processor performance increase of 44 percent. 

The Dorado 4200 system features an enhanced IO Manager, integrated specialty 

engines, and the ability to run dual partitioned systems within a single cabinet. 

The OS 2200 operating environment is comprised of enterprise system software, 

spanning the operating system, databases, transaction management, development, and 

many other software elements for enterprise-class solutions. 

1.1.2. OS 2200 Master Glossary 

The ClearPath OS 2200 Master Glossary contains terms and definitions that pertain to 

the ClearPath OS 2200 products. The OS 2200 Master Glossary is a compilation of the 

individual glossaries from all OS 2200 documents. 

Accessing the Master Glossary 

You can access the OS 2200 Master Glossary from 

• The ClearPath OS 2200 product release library on the CD or the Product Support 

Web site 

The OS 2200 Master Glossary is in the Release Information category. 

• The bookmarks of an individual document that you are viewing online 

Click Master Glossary in the bookmarks pane of the document viewer to open the 

glossary and locate the desired term. 

7831 0349–043 1–3

Software Delivery on CD/DVD Media 

1.2. Software Delivery on CD/DVD Media 

For ClearPath OS 2200 Release 13.2, release software is on a set of DVDs. The DVDs 

are processed by the Exec as read-only simulated tapes. The Exec Boot DVD is 

unlabeled and is used to boot the system. 

Dorado 300, 400, 700, 800, 4000, 4100, and 4200 Server systems are each delivered 

with one DVD reader per cell. Since a cell is the minimum size for a partition, for many 

sites a cell is one partition. Larger sites with multiple cells per partition have multiple 

DVD readers. A DVD reader is accessible only by the partition in which it is installed. To 

copy a DVD to a tape that is accessible in a tape library system, use the following 

FURPUR statements: 

@ASG,TJ DVDFILE.,DVDTP,DVDxxx 

@ASG,TJ TAPE.,MNEMONIC,REEL 

Use the following FURPUR statement to copy the DVD media to tape: 

@COPY,M DVDFILE.,TAPE.,999999 

1.3. Product Status Summary 

Table 1–1 provides the following information about each product in the current release: 

• The first column lists the installation and support name of each product and is sorted 

alphabetically. 

• The second column lists the full name of each product. 

• The third column lists the level of each product. 

• The fourth column lists the operating system. 

• The last column lists the status of each product. Status can be New Product, New 

Feature (new feature for an existing product), Feature Update (updated feature for an 

existing product), Stability Update, or No Change (no change in this release). 

Section 2 summarizes new products and updated features to existing products in this 

release. 

Note: To determine the version of Windows that is supported for a product, refer to 

the specific product documentation. 

1–4 7831 0349–043

Installation and 

Support Name 

Table 1–1. Product Status Summary 

Product Name 

Level 

Product Status Summary 

Operating 

System 

Status 

ACOB ASCII COBOL Compiler 7R3K OS 2200 No change 

CIFS CIFS 7R3 OS 2200 No change 

CIPHER-API CIPHER API 2R2 OS 2200 No change 

CITA Communications Interface 

for Transaction Applications 

2R3 OS 2200 No change 

CKRS CKRS 7R8A OS 2200 No Change 

CML CML 1R1J OS 2200 No Change 

CMR CMR 2R6 OS 2200 No Change 

COMAPI Communications Application 

Program Interface 

7R3A OS 2200 Stability Update 

COMUS COMUS 6R9A OS 2200 No Change 

CPComm Communications Platform 6R2 OS 2200 No Change 

CPCommOS Communications Platform 

for Open Systems 

cpFTP FTP Services for ClearPath 

OS 2200 

4R2A OS 2200 Stability Update 

3R5A OS 2200 No Change 

CryptoLib Cryptographic Library 1R1 OS 2200 No Change 

CULL TeamQuest® CULL 5R1A OS 2200 No Change 

DAP DAP 14R2 OS 2200 Feature Update 

DDP-FJT DDP-FJT 5R5I OS 2200 No Change 

DDP-PPC DDP-PPC 7R3A OS 2200 No Change 

DEPCON-SERVER Enterprise Output Manager 9.1 Windows No Change 

DEPCON-2200 Enterprise Output Manager 

for ClearPath OS 2200 

9.1 OS 2200 No Change 

DFP Define File Processor 2R2C OS 2200 No Change 

DMS Enterprise Network 

Database Server 

21R2 OS 2200 No Change 

DMS-RA DMS-RA 4.0 OS 2200 No Change 

DPREP1100 DPREP1100 10R7E OS 2200 Stability Update 

DPS Display Processing System 6R5A OS 2200 No Change 

DTI Distributed Transaction 

Integration 

11.2 Windows No Change 

ECLIPSE-2200 ECLIPSE 2200 3.7 OS 2200 No Change 

7831 0349–043 1–5



Support Name 


Product Name 

Level 

Operating 

System 

Status 

ELMS ELMS 3R1B OS 2200 No Change 

ELT ELT 8R3C OS 2200 No Change 

EPORTAL-2200 1.3 No Change 

EXEC Exec 48R8A OS 2200 Feature Update 

EXPIPE Multiple Batch Run 

Optimizer 

2R2B OS 2200 No Change 

FAS FAS 10R5A OS 2200 No Change 

FLEX User Authentication 4R3 OS 2200 No Change 

FLIT FLIT 14R2 OS 2200 Feature Update 

FTN ASCII FORTRAN Compiler 11R2X OS 2200 No Change 

FURPUR FURPUR 32R5B OS 2200 No Change 

GSA GSA 6R2D OS 2200 No Change 

HTPIC-2200 HTPIC-2200 9R1H OS 2200 No Change 

I18NLIB I18NLIB 2R2 OS 2200 No Change 

INFOACCESS ODBC Data Access 9R2E OS 2200 No Change 

INTERCONNECT INTERCONNECT 1R3 OS 2200 No Change 

IPF Interactive Processing 

Facility 

7R1D OS 2200 No Change 

IRU Integrated Recovery Utility 20R2 OS 2200 No Change 

J2EE-CON- 

OPENDTP 

J2EE-CON- 

OS2200 

Open Distributed 

Transaction Processing 

Resource Adapter for the 

Java Platform 

OS 2200 Transaction 

Resource Adapter for the 

Java Platform 

JBOSS-2200 JBoss Application Server for 


JPJVM Virtual Machine for the 

Javaî Platform on ClearPath 

OS 2200 JProcessor 

JVM 

Virtual Machine for the 

Javaî Platform on ClearPath 




5.1A OS 2200 No Change 



LA TeamQuest LA 7R6A OS 2200 No Change 

1–6 7831 0349–043


Support Name 


Product Name 

Level 


Operating 

System 

Status 

LINK Linking System 12R2B OS 2200 No Change 

LSS Language Support System 14R3A OS 2200 No Change 

LST LIST 4R1J OS 2200 No Change 

MAP Collector 33R1M OS 2200 No Change 

MASM MASM 6R3J OS 2200 No Change 

MCB MCB 8R3G OS 2200 No Change 

MQS2200 MQSeries for OS 2200 2R5D OS 2200 No Change 

MSAR TeamQuest MSAR 7R7B OS 2200 No Change 

MSMANAGER TeamQuest MSManager 5R7F OS 2200 No Change 

MSMQI MSMQ Interface 2R1B OS 2200 or 

Windows 

NTSI Messaging Integration 

Services 

OLTP-TM2200 Open Distributed 

Transaction Processing 

(Open DTP) 

OPE Open Programming 

Environment 

Operations 

Sentinel (See 

SP-OPERATION) 

7R3A OS 2200 

(other 

components of 

NTSI are 

installed on 

the ClearPath 

Windows node 

and Windows 

workstations) 

No Change 

No Change 

12R1C OS 2200 No Change 

4R1R OS 2200 No Change 

OSAM TeamQuest OSAM 7R5 OS 2200 No Change 

OSI-TP OSI-TP 9R1H OS 2200 No Change 

PADS Programmer’s Advanced 

Debugging System 

13R3C OS 2200 No Change 

PAR TeamQuest PAR 9R2 OS 2200 No Change 

PCFP PCFP 3R3A OS 2200 No Change 

PCIOS PCIOS 7R1B OS 2200 No Change 

PDP PDP 13R2D OS 2200 No Change 

7831 0349–043 1–7



Support Name 


Product Name 

Level 

Operating 

System 

Status 

PHP-CLEARPATH PHP-CLEARPATH 1.0 OS 2200 No Change 

PLUS PLUS 8R2O OS 2200 No Change 

PMD PMD 32R2F OS 2200 No Change 

QLP QLP 7R3B OS 2200 No Change 

RDMS Enterprise Relational 



RDMS-JDBC Relational JDBC Driver 2.7 OS 2200 No Change 

ROLRUNS ROLRUNS 4R3 OS 2200 No Change 

RSS Remote System Support 3R2N OS 2200 No Change 

SAUTILITIES TeamQuest SAUtilities 6R6 OS 2200 No Change 

Security-Admin Security-Admin 4R3 OS 2200 No Change 

SFS Shared File System 4R1 OS 2200 No Change 

SILAS SILAS 3R2B OS 2200 No Change 

SIMAN TeamQuest SIMAN 6R6 OS 2200 No Change 

SLIB SLIB 1R5I OS 2200 No Change 

SOLAR SOLAR 4R7A OS 2200 No Change 

SOLAR/E SOLAR/E 4R7A OS 2200 No Change 

SORT Sort/Merge 22R2D OS 2200 No Change 

SP-OPERATION Operations Sentinel 12.1 Windows No Change 

SP-OPERATION Operations Sentinel 

Basic Edition 

12.1CP 

Windows No Change 

SSG SSG 24R2A OS 2200 No Change 

SYSLIB SYSLIB 76R4 OS 2200 No Change 

TAS TAS 6R2I OS 2200 No Change 

TQ-BASELINE TeamQuest Baseline® 7R4F OS 2200 Feature Update 

TQD-FRAGGER TeamQuest D-Fragger 4R1D OS 2200 No Change 

TQ-MODEL TeamQuest Model® CP13.2 Windows 

workstation 

Feature Update 

TQ-ONLINE TeamQuest Online® 7R4F OS 2200 Feature Update 

TQ-PMLOG TeamQuest PMLog 7R4B OS 2200 No Change 

TQ-PROBES TeamQuest Probes 7R4D OS 2200 No Change 

1–8 7831 0349–043


Support Name 


Product Name 

Level 


Operating 

System 

Status 

TQ-TIP-LA TeamQuest TIP-LA 1R4E OS 2200 No Change 

TQRDFRAGGER TeamQuest 

RemD-Fragger 


TUTIL Tape Labeling Utility 1R1B OS 2200 No Change 

UC C Compiler 10R3A OS 2200 No Change 

UCOB COBOL Compiler 12R1F OS 2200 No Change 

UCSRTS Runtime System for Basic 

Mode Compilers 

1R1M OS 2200 No Change 

UDSC Universal Database Control 17R2 OS 2200 No Change 

UFTN FORTRAN Compiler 11R1B OS 2200 No Change 

UNIACCESS- 

ODBC 

UniAccess-ODBC 10R3-4 OS 2200 No Change 

UPLS UPLS 8R1D OS 2200 No Change 

UREP Repository for ClearPath 


URTS Runtime System for 

Extended Mode Compilers 

URU-OS2200 Utilization Report Utility for 



13R3A OS 2200 No Change 

5.1 OS 2200 and 

Windows 

No Change 

WEBTS Web Transaction Server 5R9 OS 2200 No Change 

WMQ2200 WebSphere MQ version 7 

for ClearPath Dorado 

Servers 

XRLOAD Relational Database Fast 

Load 



7831 0349–043 1–9

Separately Packaged Exec Features (SPEF) 

1.4. Separately Packaged Exec Features (SPEF) 

The following list shows ClearPath OS 2200 Release 13.2 levels for separately packaged 

Exec features. 

Feature Level 

ARC 5R6 

CARTIS 48R1 

CARTLIB 48R1 

DMPLIB 8R9 

FBCIS 48R1 

MHFS 48R1 

MMGR 48R8A 

MSCP 3R8D 

PAEXEC 48R1 

SCSITIS 48R1 

SECOPT1 48R8A 

Feature Level 

SECOPT2 48R1 

SECOPT3 48R1 

SINCH 48R1 

SIPIPM 48R1 

TAVR 48R1 

TIPUTIL 48R8A 

UDUPLEX 48R1 

VTH 48R1 

XPCEXEC 48R1 

XTCEXEC 48R1 

• The IOPUTIL runstream is included in the RUN$ file on the Exec boot tape. 

• The SPAIR and DCOPY utilities (absolutes) are released as standard software in 

SYS$*LIB$. 

• PASSGEN-DES is included in the Exec Release Master, and PASSGEN-TRAN no 

longer exists. 

• Your Exec features (installed through system generation) are delivered on keyed 

stacked tapes in a SOLAR-installable format. The following are not installed through 

a system generation: ARC, DMPLIB, MMGR, MSCP, and TIPUTIL. Refer to the Exec 

System Software Installation and Configuration Guide for installation information. 

• The SCPRBPLE feature is not normally required nor is it delivered on stacked tapes 

with other features. Two relocatables are part of SPEF: PCNSCP/RB and 

SDCSCPCTRL/RB. The PCNSCP and SDCSCPCTRL relocatables are always present 

in the RO file and are updated only when the SCPRBPLE SPEF is installed for a PLE 

resolution. Any fixes to SCP converted routines for existing releases will be supplied 

in relocatable form through the SCPRBPLE SPEF. The SCPRBPLE SPEF does not 

have to be installed, unless a PLE fix is required. 

• Monitor Services Control Program (MSCP) is released on a package tape. It is also in 

the LIB$ file on the Exec release master tape. Refer to “General EXEC 

Considerations” in Section 4 for information about how the MSCP runstreams and 

installation procedures have changed for ClearPath OS 2200 Release 12.1 and 

beyond. 

1–10 7831 0349–043

1.5. Support 

Support 

One of your key system requirements is long-term support that allows you to 

concentrate on your primary goal: filling the information processing needs of your users. 

ClearPath OS 2200 releases provide that long-term support in these ways: 

• Reduced migration interruption 

You can move to a single software system rather than changing your software 

whenever a new release of a product occurs. 

• Periodic issues of new software releases 

These releases allow you to more effectively take advantage of new software and 

system functions. The next software release is announced in advance so you can 

plan your site’s needs. 

• ClearPath OS 2200 Release 13.2 will be supported until 08/31/2014. 

Contact your Unisys Support Center for information about resolving problems and 

submitting User Communication Forms (UCF). 

The Unisys Product Support Web site contains support plans for ClearPath Plus and 

ClearPath servers. It is updated regularly, and you can access this Web site at 

http://www.support.unisys.com 

Note: Security management products provide the primary means of controlling and 

administering OS 2200 security. They are used by site administrators and by end users. 

While other products provide various security capabilities, they are not grouped with the 

term “security management product.” 

In this manual, the term “security management product” is a simplified means of 

referring to one of the following products: 

• Security Administration for ClearPath OS 2200 

• TeamQuest Site Management Complex (SIMAN) 

7831 0349–043 1–11

Locating Terms Using CDLib Manager Search 

1.6. Locating Terms Using CDLib Manager Search 

The CDLib Manager software offers a search capability that uses the Adobe Reader 

viewer. You can use the search capability in conjunction with the Master Glossary to 

locate terms, definitions, and context. 

The results of a CDLib Manager search provide the following information from the 

searched documents: 

• A list of documents that contain the search term, in order from the most 

occurrences of the term to the least 

• Hover help boxes that display the filename, title, and number of each document 

• A list of all occurrences in each document, showing the term in context 

Note: Expand a title to display the occurrences in that document. 

• The ability to open the document to see the larger context of an occurrence 

Note: Click an occurrence to open the document at the cited page. 

1.6.1. Installing and Opening CDLib Manager 

To use the search capability, install the CDLib Manager and documents on your 

workstation in one of the following ways: 

• From the ClearPath OS 2200 product documentation library CD that is delivered with 

every system order 

• From the documentation page for the desired release on the Product Support Web 

site (http://public.support.unisys.com) 

Notes: 

− Click the link that follows the list of document categories to download the 

release product documentation library ISO image. 

− The Product Support Web site also offers a search capability, but it is not as 

comprehensive as the CDLib Manager capability. 

To open CDLib Manager 

1. Expand the Unisys CD-ROM Library group in the list of installed programs that is 

displayed from the Windows Start menu. 

2. Click CD-ROM Library. 

CDLib Manager opens and displays the categories and lists of document titles in the 

installed release. 

1–12 7831 0349–043

1.6.2. Performing a Search 

To perform a CDLib Manager search 


1. Open any PDF document from the CDLib Manager interface. 

The document opens in the Adobe Reader viewer. 

2. Click Search on the Edit menu of the Adobe Reader viewer. 

The Search dialog box opens and offers basic search options. 

3. Select the set of documents to search: 

Note: The third option is the default and searches all OS 2200 documents in the 

release. 

• The current PDF document 

• All PDF documents in the location selected in the attached list. 

• In the index named 00_home.pdx (the library on the CD-ROM); 

4. Type a search term or phrase in the What word or phrase would you like to 

search for box. 

5. Select any or none of the following options to modify the search: 

• Whole words only 

• Case-Sensitive 

• Include Bookmarks 

• Include Comments 

6. Click Search. 

The search results appear in the Results portion of the Search dialog box. 

1.6.3. Setting the Viewer Path 

The CDLib Manager software assumes your default system viewer for PDF files is 

Adobe Reader. Other viewers are not supported at this time. If your default viewer is 

different, you can set the path in the CDLib Manager software to point to Adobe Reader, 

as follows: 

1. Click Viewer Launch on the Options menu. 

2. Set the location of the desired viewer in the Adobe Acrobat Reader box by 

browsing to the executable file, usually something like 

C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe 

3. Click OK. 

7831 0349–043 1–13


1.6.4. For More Information 

To view the online CDLib Manager Help, do one of the following: 

• Click Help on the CDLib Manager toolbar. 

• Click How To in the Unisys CD-ROM Library group in the list of installed 

programs that are displayed from the Windows Start menu. 

Read any topic on a desired subject for more information. 

The preceding procedures are available in help topics. The Searching PDF 

Documents book provides additional search options. 

1–14 7831 0349–043

Section 2 

New Products and Updated Features 

This section summarizes new products and updated features to existing products. 

Notes: 

• For more detailed information about a specific product, refer to the documentation 

for that product. 

• For Exec software migration and compatibility considerations, see Section 4. For 

OS 2200 software products migration and compatibility considerations, see 

Section 5. 

2.1. DAP Level 14R2 

• Supports the dump processing of the Dorado 4200 

• TDATE$ Date formatting [!DATA2] - YYYY-MM-DD 

• TDATE$ Date formatting [!DATA3] - YYYY-MM-DD (with 18 bit shift) 

• DWTIME$ Date formatting [!DWDATE] - MM/DD/YY 

• DWTIME$ Date formatting [!DWDATE1] - YYYY-MM-DD 

• DWTIME$ Time formatting [!DWTIMEn] - HH:MM:SS[.fffffffff] 

• SWTIME Date formatting [!SWDATE] - MM/DD/YY 

• SWTIME Date formatting [!SWDATE1] - YYYY-MM-DD 

• SWTIME Time formatting [!SWTIME] - HH:MM:SS 

• SYS$TIME Date formatting [!SYSDATE] - MM/DD/YY 

• SYS$TIME Date formatting [!SYSDATE1] - YYYY-MM-DD 

• SYS$TIME Time formatting [!SYSTIMEn] - HH:MM:SS[.fffffffff] zzzz 

• SYS$TIME Seasonal Shift formatting [!SYSOFF] - +|-HH:MM:SS 

• SYS$TIME Time Zone Shift formatting [!SYSOFF1] - +|-HH:MM:SS 

• SYS$TIME Time Zone mnemonic formatting [!SYSZONE] 

• FLIT will recognize PMD version 8 

7831 0349–043 2–1

Exec Level 48R8A 

2.2. Exec Level 48R8A 

Exec Support Product Level Summary: 

ARC 5R6 5.12 

DMPLIB 8R9 

E$ORMSG 6.12 

MILES 1R4 1.15 

MMGR 48R8A 43.62 

MSCP 3R8D 3.18 

PASSGEN 2R2 2.2 

RLIB$ 1.84 

TIPUTIL 48R8A 48.42.1 

VIPR 1R3D 1.7 

This release of the Exec supports the Dorado 4200 platform with increased 

stability and new functionality. 

FCSS Deadlock TPM Record 

Customer Solution/Benefit: 

A new TPM (TIP Performance Monitor) log entry is defined which, if enabled, 

will result in information about TPM FCSS deadlock errors which occur on a 

system being logged to the selected TPM log trail. 

Detailed Description: 

The new TPM log entry (type 015, subtype 011) contains the TIP FCSS file and 

record numbers involved in an FCSS deadlock condition along their associated 

RUNIDs (and HOSTID in an XTC environment). A TPM FCSS deadlock log entry is 

created if an FCSS deadlock condition occurs on a system and the new L$DLCK 

TPM selection bit has been enabled (for shared FCSS deadlock information to 

be collected and logged in an XTC environment, the TIP FLAGBOX bit SDEADLOCK 

must also be enabled). 

See Exec PLE 18853639 for comprehensive details and the documentation updates 

regarding this new functionality. 

PATHS Keyin 

Customer Solution/Benefit: 

Provide a method for the operator or hardware engineer to find all paths and 

states of paths to a device. It is very time consuming for operations to 

find the states of all paths as a result of the many components and paths to 

a device. 

Detailed Description: 

Adds capability to display paths to devices along with the state of the 

paths. 

2–2 7831 0349–043

Exec FS-Keyin Enhancements 

FLIT Level 14R2 

Several new FS-keyin options and enhancements have been requested by customers. 

New FS-keyin options are added for consistency and ease of use. For disk and tape 

options, both the plural or singular options are allowed for consistency. New FS-keyins 

are added for OS2200 Virtual Tape Handler (VTH) and communication devices (COM). 

See Exec PLE 18880270 for comprehensive details and the documentation updates 

regarding this new functionality. 

2.3. FLIT Level 14R2 

• Supports the simulation for the Dorado 4200 

• Program Mode emulation of the REG4CGY$/REG4CGYXD$ retrieve sub-function 

• Program mode emulation of the ER SYS$TIME call 

• TDATE$ Date formatting [!DATA2] - YYYY-MM-DD 

• TDATE$ Date formatting [!DATA3] - YYYY-MM-DD (with 18 bit shift) 

• DWTIME$ Date formatting [!DWDATE] - MM/DD/YY 

• DWTIME$ Date formatting [!DWDATE1] - YYYY-MM-DD 

• DWTIME$ Time formatting [!DWTIMEn] - HH:MM:SS[.fffffffff] 

• SWTIME Date formatting [!SWDATE] - MM/DD/YY 

• SWTIME Date formatting [!SWDATE1] - YYYY-MM-DD 

• SWTIME Time formatting [!SWTIME] - HH:MM:SS 

• SYS$TIME Date formatting [!SYSDATE] - MM/DD/YY 

• SYS$TIME Date formatting [!SYSDATE1] - YYYY-MM-DD 

• SYS$TIME Time formatting [!SYSTIMEn] - HH:MM:SS[.fffffffff] zzzz 

• SYS$TIME Seasonal Shift formatting [!SYSOFF] - +|-HH:MM:SS 

• SYS$TIME Time Zone Shift formatting [!SYSOFF1] - +|-HH:MM:SS 

• SYS$TIME Time Zone mnemonic formatting [!SYSZONE] 

• FLIT will recognize PMD version 8 

2.4. TQ-BASELINE Level 7R4F 

This release adds support for the Dorado 4200. 

2.5. TQ-MODEL Level CP13.2 


2.6. TQ-ONLINE Level 7R4F 


7831 0349–043 2–3

TQ-ONLINE Level 7R4F 

2–4 7831 0349–043

Section 3 

Software Considerations, Management, 

and Delivery 

3.1. Considerations 

This subsection lists several considerations that you should be aware of when you 

migrate. These considerations are grouped by release. 

Note: Please read and understand the considerations in this subsection. If you do not, 

the migration and installation sequences described in Section 7 might fail. 


• The System Release Profile (SRP) identifier for this release is CP-OS-2200-13.2 

• UCFs pertaining to general release issues should be submitted against product 

OS-2200-SBR level 13.2. 

• For SAIL-based systems beginning with the ClearPath OS 2200 Release 13.1, the 

XNIOP software is released on the CPCommOS release tape. When installing 

CPCommOS, ensure that you install CPCommOS mode XNIOP to install the 

ClearPath OS 2200 Release 13.2 version of XNIOP. On initialization, CPCommOS 

automatically loads the new version of XNIOP. Refer to the Communications 

Platform for Open Systems Configuration and Operations Guide for more information 

on loading the XNIOP software. 

ClearPath OS 2200 Release 13.1 

• The System Release Profile (SRP) identifier for this release is CP-OS-2200-13.1 


OS-2200-SBR level 13.1. 

• Cipher API Considerations 

Cipher API has a new install mode, Mode B. Use this mode rather than Mode A if 

you have a Dorado 800 with CIP2001-PCE hardware accelerator appliance configured 

in I/O Manager or if you might add the CIP2001-PCE in the future. If no encryption 

card is installed, the choice of Mode A or Mode B makes no difference, but it is 

recommended to use Mode B on systems such as the Dorado 800 that support I/O 

Manager because installing in Mode B supports adding a CIP2001-PCE card without 

having to change the Cipher API configuration file. 

7831 0349–043 3–1


• COMAPI Considerations 

− COMAPI has added two additional install modes: C and D. These additional 

modes offer the same functionality as modes A and B and give the user more 

flexibility for testing or running different system environments. 

− If your application is designed to use socket function calls, you must include the 

library element SYS$LIB$*COMAPI$LIB.SOCKET$LIB in the link of your 

application. Refer to the COMAPI User Guide for more information. 

If you use a newer level of the socket library in your application and 

subsequently try to run on an older level of COMAPI, it will not work. You must 

re-link with the socket library that is installed for that level of COMAPI. 

Note: You can use old socket libraries with newer levels of COMAPI. 

• Dorado 4000 and 4100 

Dorado 4000 and 4100 systems require a plateau upgrade. See 3.12. 

• CPCommOS Considerations 

CPCommOS has added two additional install modes: XNIOP and XNIOPTEST that 

are used to install the XNIOP software for the XNIOP Loading feature, see 2.6. This 

feature requires the ClearPath 13.1 Dorado 4000 Compatibility Package 

(2.3-CP13.1-4000-COMPATIBILITY.sup) for Dorado 4000 customers. See table 3-10 

for more information. Refer to the Software Products Installation Guide for more 

information on these new installation modes. 

• SLIB Considerations 

In the previous releases, the SLIB product could be installed in mode SS (the default) 

or mode NONSS. Neither of these old mode names exists in this release. Mode 

NONSS has been eliminated entirely and the name of the default mode has been 

changed from SS to A. SLIB must now always be installed using mode A. 

• URU Considerations 

URU can now be installed in mode A or B. The URU mode you require will depend 

on the audit trail configuration of your system and how you have installed your IRU 

FSAH subsystem. See section 5.52 for further details before installing URU. 

• DCOPY 

The DCOPY tool is used to create a tape from a DVD formatted image file or create a 

DVD formatted image file from a tape. The DCOPY tool is delivered in the LIB$ file of 

the Exec 48R3 (and higher) master tape. For information on how to use this tool, 

refer to the ClearPath OS 2200 Exec System Software Administration Reference 

Manual. 





3–2 7831 0349–043


• The information contained in the ClearPath OS 2200 13.0 Software Planning and 

Migration Overview document pertains to clients moving from the supported 

ClearPath OS 2200 12.x releases. If you are migrating from a ClearPath OS 2200 

11.x release, please refer to the ClearPath OS 2200 12.1 Software Planning and 

Migration Overview (7831 0349-040) document for information that is no longer 

included in this document. 

• COMAPI 

Beginning with COMAPI Level 7R2, the LOG parameter on the ADMIN statement in 

the COMAPI configuration has been removed. Two new configuration statements 

have been created, the ENTITY statement and the LOG statement. See the COMAPI 

User’s Guide for more details on COMAPI configuration. 

• CryptoLib 

CPComm 6R1 and Cipher-API 2R1 require the new CryptoLib 1R1 product. The 

CryptoLib product is included in the IOE for all systems. If CryptoLib is not installed 

on your CP 13.0 system, CPComm and CipherAPI terminate in error at initialization. 

The CPComm build requires CryptoLib to be installed. 

• CPCommOS Considerations 

CPCommOS mode A no longer installs mode AFCB automatically. Refer to the 

Communications Platform for Open Systems Configuration and Operations Guide for 

more information. 

• DDP-PPC Considerations 

The CPMODE keyword in the OSITSU and TASTSU records must have the same 

value if the TASTSU and DDP processes will be run concurrently. 

The default value for the CPMODE keyword has changed from CMSA to 

CPCOMMA. This means that current CMS users who do not have the CPMODE 

keyword set will have to set it to CMSA to continue using CMS. 

DDP-PPC 7R3 requires the CPComm level to be 6R1 or higher. 

DDP-PPC 7R3 requires the CPCommOS level to be 4R1 or higher. 

• Discontinued Products 

Beginning with ClearPath OS 2200 13.0 release the following products are no longer 

included in the ClearPath OS 2200 release 

− DATAEXTRACTOR 

− OADE-WIN 

− OLE-DB-OS2200 

− SLAR 

− UCPP 

− XMLPROVIDER 

7831 0349–043 3–3


• Dorado 400 Considerations 

The DDP-PPC 7R3 product delivered in the ClearPath OS 2200 Release 13.0 will not 

function on a Dorado 400 system that is running CPCommOS level 2R2. To avoid 

this issue, you can either run DDP-PPC level 7R2E or make configuration changes to 

DDP-PPC level 7R3. 

The migration scenarios documented in Section 7 of this document install 

DDP-PPC 7R3 from either the CP-OE1B fast-load tape or the CP10 package tape. 

Once the DDP-PPC 7R3 product is installed, the following configuration change must 

be applied: 

• EOM 9.0 

The CPMODE keyword in the OSITSU and TASTSU records of the DDP-PPC 

configuration file must be set to CMSA (CPMODE=CMSA). 

If you are using the EOM SSL feature with a CPComm level prior to the ClearPath 

OS 2200 13.0 Release (CPComm 6R1) you must apply CPComm PLEs 18746921 

and 18753995. CPComm 6R1 does not require a PLE. 

• JBOSS-2200 

Two versions of JBOSS-2200 are supported with the ClearPath OS 2200 13.0 

release. 

• OSAM 

− JBoss 4.3A (runs on OS 2200 natively and JProcessor) 

− JBoss 5.1A (requires JProcessor) 

OSAM Level 7R4 is required with Exec 48R7 and UDSC 17R1. Previous levels of 

OSAM do not recognize ER SYS$TIME and version 8 of the UMON interface. 

• SILAS 

Migration of SILAS from one level to another requires the SILAS word-addressable 

configuration file to be rebuilt. This can be accomplished by either using SILAS,G to 

manually create a new WAD file or starting the delivered SILAS runstream with the 

,1 option: ST STSILAS-A,1. 

• SOLAR and SOLAR/E 4R7 

The Dot-Format Level Enhancement introduces a migration consideration. You must 

build and boot your current Exec to integrate the changes in PLE 18756811. These 

fixes are required in order for the Exec to recognize the new enhanced version of the 

system key table written by SOLAR level 4R7 or higher. FURPUR level 32R5A or 

higher is also required. A SOLAR level 4R7 or higher KEYGEN-created key can only 

be used on an Exec that recognizes the new key table version. When SOLAR level 

4R7 or higher is first used to register any key, the SYS$*DATA$.KEYTABLE$ is 

written in the new format which is not recognized by previous levels of SOLAR or 

the Exec. 

All previous product installation, feature, and Exec image enabler model-based, 

MIPS-based, and MIPS metered keys are compatible with SOLAR level 4R7 or 

higher. 

3–4 7831 0349–043

• Media Distribution Changes 


The ClearPath OS 2200 13.0 Release software is distributed on DVD media only. 

The tape media (36-track, DLT and 9840) are not available for media distribution with 

this release. Systems that used tape media for their software distribution are no 

longer supported on ClearPath OS 2200 13.0. 

• Software Packaging Changes 

Several packaging changes are introduced in this release. 

CryptoLib is added to the CP-FLD, CP-FLD400 and CPCommSuite packages. 

CP-FLD/ 

CP-FLD400 

COMUS 

*CPComm 

*CPCommOS 

*CPCommOS 

CryptoLib 

FURPUR 

PCFP 

ROLRUNS 

SILAS 

SOLAR 

SYSLIB 

6R9A 

6R1 

4R1 

2R2 

1R1 

32R5A 

3R3 

4R3 

3R2A 

4R7 

76R3E 

*CP-FLD CPCOMM 6R1 for CMOS Systems 

*CP-FLD CPCommOS 4R1 for Dorado 4000/4100 Systems only 

*CP-FLD400 CPCommOS 2R2 for Dorado 400 Systems only 

CP-COMMSUITE 

COMAPI 7R2 

*CPComm 6R1 

*CPCommOS 4R1 

CryptoLib 1R1 

SILAS 3R2A 

DATAEXTRACTOR (DATAEXT and DATAEXTCDC), SLAR, and UCPP have been 

removed from the CP16, CP05, and CP07 package tapes. 

• UDSC 

Exec 48R7 is required to use the new UDSC features Shared Unit Duplexed 

Recoverable Performance Improvement. 

7831 0349–043 3–5






• This release includes the changes associated with EXEC PLE 18730588. The solution 

implemented by this PLE introduces a potential compatibility issue for sites using 

both SENTRY_CONTROL and Run-level Quota enforcement (EXEC configuration 

parameter ACCTON set to 4). Users on those systems who were formerly able to 

create G-option files may in some cases no longer be allowed to do so. Sites using 

Fundamental Security or those with EXEC configuration parameter ACCTON set to 

any value less than 4 are not affected. A further explanation of this issue can be 

found in “General Exec Considerations” in Section 4. 

• Exec Level 48R6 

The Exec level 48R5 was delivered with the ClearPath OS 2200 12.0 Plus release. 

The Exec level 48R6 is delivered with the ClearPath OS 2200 12.1 Release. 

• Dorado 4000 plateau requirement 

With ClearPath Release 12.1, the Dorado 4000 systems require Plateau 2.1 and an 

additional Compatibility Package due to dependencies with the CPCommOS 3R1A 

product. Refer to “Migration for Dorado 4000” in Section 7 for Dorado 4000 

migration information and “3.12 ClearPath and Plateau Interdependencies” for 

additional plateau information. 

• Dorado 400 considerations 

The CPCommOS 3R1A product delivered in the CleaPath OS 2200 Release 12.1 will 

not run on a Dorado 400 system. Do not use the ClearPath OS 2200 Release 12.1 

CP-FLD fast load tape or the CPCommOS 3R1A product that is delivered on the 

package tape CP-COMMSUITE. 

The Dorado 400 systems must use the CPCommOS 2R2 product that was delivered 

in ClearPath OS 2200 Release 12.0. For your convenience, Unisys has created a new 

CP-FLD400 fast load tape that contains the CPCommOS 2R2 level instead of 

CPCommOS 3R1A. 

• CPCommOS considerations 

Configuring network interfaces is moved from SAILCC to CPCommOS. Refer to 

”Communications Platform for Open Systems (CPCommOS)”in Section 5 for a 

detailed description on migrating to CPCommOS 3R1A prior to installing ClearPath 

OS 2200 Release 12.1. 

Additional CMS 1100 to CPCommOS migration modes are added. In addition, mode 

A no longer installs mode CMSA-CPCA automatically. Refer to the Communications 

Platform for Open Systems Configuration and Operations Guide for more 

information. 

• Internet Protocol Version 6 (IPv6) support 

The implementation of the IPv6 standard is introduced in the ClearPath OS 2200 

Release 12.1. Many products have updated to support this new feature. Refer to 

“3.2 Internet Protocol Version 6 (IPv6) Support” for additional product details. 

3–6 7831 0349–043

• MSCP considerations 


MSCP has made changes to the MSCP runstreams delivered in the ClearPath 

OS 2200 12.1 release. Refer to “General Exec considerations” in Section 4 for 

additional information. 

• Software Logical Package change 

A new logical package CP-FLD400 fast-load tape is created for use by the Dorado 

400 systems. This package is distributed only to the Dorado 400 and Dorado 4000 

client. 

Following is the new packaging structure for 36-track Logical Packages, DLT 

Packages and DVD packages. 

CPHD-01 12.1 

CP-EXEC-MSTR 

CP-EXEC-SYM 

CP-FLD 

CP-FLD400 

CP-OE1A 

CP-OE1B 

CP-OE2 

CP-SPF 

CP-TRN 

CPHD-02 12.1 

CP-COMMSUITE 

CP-OPE 

CPHD-03 12.1 

CP01 

CP02 

CP03 

CP04 

CP05 

CP06 

CP07 

CPHD-04 12.1 

CP08 

CP09 

CP10 

CP11 

CP12 

• Next Generation Dorado Servers Definition 

CPHD-05 12.1 

CP13 

CP14 

CP15 

CP16 

CP17 

CP18 

Unisys ClearPath Next Generation Dorado Servers combine a specially configured 

Unisys Intel® processing platform with Unisys enterprise class I/O. Throughout this 

document, the use of “Next Generation Dorado servers” refers to the Dorado 400 

and 4000 systems. 




OS-2200-SBR level 12.0 

• Cipher API considerations 

Beginning with ClearPath Release 12.0, the Cipher API product is now included in all 

the IOE packages. For new system orders, the Cipher API product will be included in 

the software order automatically. If you have an existing system that did not 

originally include the Cipher API product in the IOE and you would like to receive it 

now, contact your Unisys Sales Representative to order the no-charge CSW 20-ENC 

product. 

7831 0349–043 3–7


• COMAPI considerations 

The KEYIN statement in the COMAPI configuration no longer exists. The information 

which used to be supplied on the KEYIN statement has been moved to the ADMIN 

statement. See 5.6 for additional information. 

• cpFTP considerations 

cpFTP 3R4 now requires that the owner user ID associated with the Fixed Gate 

Subsystem for cpFTP (usually -FTP-SUBSYS-) be updated to have the 

SUBSYS$DEACT security interface. 

• Discontinued products 

Beginning with ClearPath OS 2200 Release 12.0 the following products are no longer 

included in the ClearPath OS 2200 Release. 

− ADOI 

− APP-DEFENDER 

− DB-EVENT-ANALYZR 

− JDBC-FOR-OLEDB 

− OPE-TP 

− PERFEV 

− SMART (see PLE 18626268 for additional information) 

− SNMP-AGX2200 

− TeamQuest TPAS 

Note: The TeamQuest TPAS functionality is included in TeamQuest TIP-LA. 

− UOSS (see PLE 18626276 for additional information) 


The Plateau 1.1 or higher must be installed on the Dorado 4000 systems before 

installing the ClearPath Release 12.0 software products. CPCommOS 2R2 requires 

new XNIOP code that is delivered in the plateau. 


The Plateau 1.1IC005 or higher must be installed on the Dorado 400 systems before 

installing the ClearPath Release 12.0 software products. CPCommOS 2R2 requires 

new XNIOP code that is delivered in the plateau. 

• Internet Protocol Version 6 (IPv6) 

IPv6 is not supported in ClearPath Release 12.0. 

• JBoss considerations 

In a change from the previously released version of JBOSS-2200, it is now necessary 

to purchase a support agreement for JBOSS-2200 in order to receive the product. 

Prior to this version, it was possible to freely obtain the product with or without 

obtaining a support agreement. Contact your Unisys Sales Representative to 

purchase a support agreement if you haven’t done so already. 

3–8 7831 0349–043


Beginning with ClearPath OS 2200 Release 12.0, if you are entitled to the JBoss 

product, you will not receive the JBoss software product key with your ClearPath 

Release 12.0 delivery. To acquire the JBoss software product key, you will be 

instructed to access a web page where you will be asked to accept an End User 

License Agreement (EULA) and request the key. 

• Software Logical Package changes 

A new Logical package CPHD-05 has been created to allow room to distribute the 

ClearPath Release 12.0 products. With the introduction of this new package, the 

contents of several of the package tapes have been changed. 

Following is the new packaging structure for 36-track Logical Packages, DLT 

Packages, and DVD packages. 

CPHD-01 12.0 

CP-EXEC-MSTR 

CP-EXEC-SYM 

CP-FLD 

CP-OE1A 

CP-OE1B 

CP-OE2 

CP-SPF 

CP-TRN 

CPHD-02 12.0 

CP-COMMSUITE 

CP-OPE 

• Software Packaging changes 

CPHD-03 12.0 

CP01 

CP02 

CP03 

CP04 

CP05 

CP06 

CP07 

CPHD-04 12.0 

CP08 

CP09 

CP10 

CP11 

CP12 

CPHD-05 12.0 

CP13 

CP14 

CP15 

CP16 

CP17 

CP18 

− Cipher API was previously delivered as a non-keyed, stand-alone product. It was 

keyed and included on the CP17 package tape. 

− JBoss is delivered as both a CD-ROM and a keyed, SOLAR installable product. 

The SOLAR installable portion of the product was delivered on the CP12 

package tape. 

− IC2200 (Interconnect) was delivered on the CP12 package tape in the ClearPath 

12.0 Release. 

− CPComm, CPCommOS, COMAPI, and SILAS previously delivered on CP04 are 

delivered on the new CP-COMMSUITE package in the ClearPath 12.0 Release. 

For additional packaging information, see the ClearPath OS 2200 36-track, 9840, DLT and 

DVD Media Quick Reference Card (7862 2032). 

7831 0349–043 3–9


• SOLAR and SOLAR/E considerations 

With SOLAR level 4R6A, Unisys continues support of the Software License 

Management program. Software License Management ensures that software is 

installed and executed on the system and workload for which it was purchased by 

using Software Control Numbers (SCN). The SCN on a product's installation or 

feature key must match the SCN on the registered image enabler key for the product 

to be compliant with your software license. 

SOLAR level 4R6A does not prevent product key registration or corresponding 

software installation if the registered Exec image enabler key already contains a 

different SCN. Instead, SOLAR writes a warning message to the diagnostic file and if 

executed in batch, displays a console message indicating that a noncompliance has 

occurred. 

• TeamQuest Key changes 

A new key is required to execute the TeamQuest products in ClearPath OS 2200 

Release 12.0. 

− Each system site-id requires a different permanent key. That permanent key 

includes all licensed TeamQuest products. 

− This new key will expire according to the terms of your ETP license agreement. 

The expiration date will be specified when the key is provided. 

− One month before the key expires, a warning message will display when the 

product is executed. This message will indicate that your key will expire soon. 

− This new key will work with the next release of the same set of products, 

provided that the key has not expired. 

− TeamQuest Model requires a second key for the workstation. 

See section “3.8 License Keys for TeamQuest Products” for additional information. 

• UDSC considerations 

Problems could occur after a site moves up to UDSC 16R1. At that point, if the 

customer is running on CP11.2 EXEC level or higher, the customer could use UDSC 

16R1 to create some of the new type nine QITEMs. Then, if they drop back to a 

CP11.1 EXEC or prior, they would need to have the cross-boot PLE (18390396) 

applied to their CP11.0 (or prior) EXEC level. The CP11.1 (or higher) EXEC will 

recognize the type nine QITEMs but the CP11.0 EXEC will not unless the PLE is 

added. 

• WEBTS-5R6 considerations 

The CPComm and CPCommOS encryption libraries support higher levels of 

encryption than the embedded WebTS encryption libraries. This enables WebTS to 

be shipped without including 40-bit or 128-bit strength encryption/cipher libraries; 

enables WebTS to use the 256-bit cipher strength CPComm and CPCommOS 

support; and enables high speed encryption when operating with CPCommOS on a 

ClearPath/Dorado 4000 series. 

Effective with the ClearPath 12.0 release, the Web Transaction Server (WebTS) will 

exist in only one style. 

3–10 7831 0349–043

Internet Protocol Version 6 (IPv6) Support 

The IXS4000-CSU style, which previously denoted the 40 bit encryption strength, will 

remain and will continue to be included in the ClearPath IOE. 

The IXS4000-CSU style utilizes the CPComm encryption libraries (which were 

released with ClearPath 11.0); therefore WebTS will support the full range of 

encryption strength without having the embedded (in WebTS) encryption libraries. 

The 128-bit encryption strength style of WebTS is no longer be valid beginning with 

ClearPath 12.0, because the IXS4000-CSU style will support (using CPComm) the 

128 and even stronger levels of encryption. 

3.2. Internet Protocol Version 6 (IPv6) Support 

The implementation of the IPv6 standard is introduced in the ClearPath OS 2200 Release 

12.1. The ClearPath OS 2200 13.0 release extended IPv6 support for the Dorado 4000 

and 4100 systems. There are two ways for a product to adapt to support the IPv6 

networks; they can either use the Bump-in-the-API feature or use the IPv6 APIs. 

IPv6/IPv4 Address Translation (Bump-in-the-API feature) 

Existing ClearPath OS 2200 IPv4 applications can operate over an IPv6 network by using 

the feature Bump-in-the-API in Communications Platform. This feature translates IPv6 

addresses to arbitrary private IPv4 addresses. The private IPv4 addresses are passed to 

the ClearPath OS 2200 IPv4 application instead of the real IPv6 addresses. 

IPv6 APIs 

ClearPath OS 2200 applications can operate over an IPv6 network and use real IPv6 

addresses within Communications Platform applications by revising the applications to 

use new Communications Platform IPv6 procedure calls. 

For more information on Internet Protocol Version 6 (IPv6) support, refer to the 

Communications Platform Configuration and Operations Guide and the Communications 

Platform Programming Reference Manual. 

ClearPath OS 2200 Products that Support IPv6 

CPCommOS, DDP-PPC, and ECLIPSE-2200 have updated in the ClearPath OS 2200 13.0 

release to include support of the IPv6 feature. CIFS, JVM, and WebTS are updated to 

fully support IPv6 using the IPv6 APIs. The following table lists all of the ClearPath 

OS 2200 products that support the IPv6 feature. 

7831 0349–043 3–11


Table 3–1. IPv6 Product Support Status 

OS 2200 Product 

Product Uses the 

Bump-in-the-API to 

Work with IPv6 

Networks 

BIS Initial support BIS 46R1 

Product Uses the 

IPv6 APIs 

CIFS Initial support 12.1 Initial Support 13.0 

CITA Initial support 12.1 

COMAPI Initial support 12.1 

CPComm Initial support 12.1 

CPCommOS Initial Support 13.0 

cpFTP Initial support 12.1 

DDP-FJT Takes advantage of 

DDP-PPC IPv6 support 

DDP-PPC Initial support for DCA 

and OSI in 13.0 

DEPCON Initial support 12.1 

DMS-RA Initial support 12.1 

ECLIPSE-2200 Initial Support 13.0 

FLEX Initial support 12.1 

JPJVM Initial support 

JProcessor 1.2 

JVM Initial support 12.1 Initial Support 13.0 

RDMS-JDBC Initial support 12.1 

SILAS Initial support 12.1 

TQ-BASELINE Initial support 12.1 

TQ-ONLINE Initial support 12.1 

TQ-VIEW Initial support 12.1 

UNIACCESS-ODBC Initial support 12.1 

WEBTS Initial support 12.1 Initial Support 13.0 

3–12 7831 0349–043


Clearpath OS 2200 Products that use IP addresses but do not currently 

support IPv6 

The ClearPath OS 2200 products listed in Table 3–2 are products that use the IP address, 

but do not currently support the IPv6 feature. 

DTI 

Table 3–2. Products that use IP 

addresses but do not currently 

support IPv6 

HTPIC-2200 

INFOACCESS 

IPF 

J2EE-CON-OPENDTP 

JBOSS-2200 

MQS2200 

MSMQI 

NTSI 

OPE 

OLTP-TM2200 

OSI-TP 

SP-OPERATION 

TAS 

URU-OS2200 

OS 2200 Product 

7831 0349–043 3–13

Discontinued Products 

3.3. Discontinued Products 

OS 2200 ClearPath Product Support Web sites display support plans. See 1.5 for 

additional information describing support for OS 2200 systems. 

Table 3–3 lists the software products and features that are not supported, and cannot be 

ordered as part of ClearPath OS 2200 Release 13.2. The Support Discontinued In column 

identifies the software release in which the product or feature was discontinued. 

Table 3–3. Software Products and Features Not Supported in 


Product or Feature Support Discontinued In Replaced By 

ADOI ClearPath OS 2200 Release 12.0 

APP-DEFENDER ClearPath OS 2200 Release 12.0 

DB-EVENT-ANALYZER ClearPath OS 2200 Release 12.0 

JDBC-FOR-OLEDB ClearPath OS 2200 Release 12.0 

OPE-TP ClearPath OS 2200 Release 12.0 

PERFEV ClearPath OS 2200 Release 12.0 

SMART ClearPath OS 2200 Release 12.0 

SNMP-AGX2200 ClearPath OS 2200 Release 12.0 

TeamQuest TPAS ClearPath OS 2200 Release 12.0 TeamQuest TIP-LA 

UOSS ClearPath OS 2200 Release 12.0 

WEB TS STRONG Included in WEB TS 

products 

DATAEXTRACTOR ClearPath OS 2200 Release 13.0 

OADE-WIN ClearPath OS 2200 Release 13.0 

OLE-DB-OS2200 ClearPath OS 2200 Release 13.0 

SLAR ClearPath OS 2200 Release 13.0 

UCPP ClearPath OS 2200 Release 13.0 

XMLPROVIDER ClearPath OS 2200 Release 13.0 

3–14 7831 0349–043

3.4. Future Considerations 

Future Considerations 

Future OS 2200 releases have planned features or changes that might affect customers. 

Audit and Step Control Considerations 

In a future release, the format of various audit and step control structures and audit 

records is changing. For all audit trail types (log, step control, TPM, and COD), the audit 

control records in the audit trail files will change. The ACI file structure and ACI 

configuration statements will also change. The audit block header format and size are 

changing as well as the following audit control records: media header, media trailer, 

reboot start, and reboot continue. 

Any programs that read the audit trail and do not use IRU’s FSAH (Free Standing Audit 

Handler) must change to handle the new audit control record and block header formats. 

Programs that read the audit trails through FSAH will need to include or use IRU’s new 

version of FSAH. The new IRU FSAH is able to read both the old and the new audit trail 

formats. If your program reads audit trails and does not use FSAH, you should evaluate 

adapting your program to use FSAH. If your program reads audit trails and uses FSAH, 

you may continue to use the previous TDATE$ format interfaces or you may convert to 

use the new UTC DWTIME$ format interfaces. 

For step control, the step ID is changing from a two-word TDATE$ plus uniqueness bits 

format to a two-word unique identifier based on a UTC DWTIME. This will be seen in all 

interfaces which supply or return the step ID and all audit records that include the step 

ID. The new step ID format will still allow time to be extrapolated (and at a finer 

granularity), however, any program that currently retrieves time from the step ID or 

displays the step ID needs to be updated. Also, the following other step control audit 

records are changing: periodic save and application restart audit record. 

For TPM audit trail audit records, all DWTIMEs will change from local time to UTC time. 

XPC 

The XPC has not been tested with the ClearPath OS 2200 Release 12.0 or higher and is 

not supported with this release. Phase 1 support of the XPC terminated on October 31, 

2007. Some portions of the EXEC code that formerly supported XPC caching have been 

removed or modified in releases beyond ClearPath 12.0. Support of XPC-L continues and 

XPC-L has been qualified with all currently supported releases. 

3.4.1. Notice of Intent to Remove Software 

This section identifies software, functions, support, and so forth that will be removed in 

a future release. 

3.4.2. Notice of Intent to Remove Hardware 

Dorado 400 Systems will not be supported beginning in the next major release, 14.0. 

7831 0349–043 3–15

Software License Management 

3.5. Software License Management 

Software License Management is a consistent process for installing and enabling the 

use of software products. Its purpose is to ensure that products are properly licensed for 

use on a given system. This process was initially deployed in ClearPath OS 2200 

Release 10.0. Full enforcement functionality will be implemented in a future release. 

This process is an extension of previous technologies that use keys to validate and 

enable capabilities, such as the Software Controlled Performance key and software 

product keys. 

3.5.1. Definitions 

This subsection defines several terms and concepts used with the Software License 

Management functionality. 

Manufacturing Control Number (MCN) 

MCN uniquely identifies a Unisys ClearPath system. Each hardware system is assigned a 

unique MCN when the system is built. The MCN remains the same for the life of the 

system. Use the MODELNUM keyin to determine the system MCN. 

Software Control Number (SCN) 

SCN is a seven-digit number assigned when the system software is purchased. This 

number uniquely identifies the software that is licensed to the system, including: 

• Software IOE products 

• Optional products 

• Software performance levels (Image Enabler Key) 

A system can have multiple SCNs, one for each licensed software group. 

Note: Software keys before ClearPath OS 2200 Release 10.0 are displayed as a 12-digit 

SCN (000000000000). The Master SCN is a 12-digit SCN (999999999999). 

SCN can change during the life of a system. Initially, an SCN is created when the 

system software is purchased. A new SCN will be created for an existing system when 

the system is upgraded to a new performance level and the software is relicensed. Use 

the MODELNUM keyin to determine the system SCN. 

Pre-10.0 Release SCN 

The pre-10.0 release SCN value is 000000000000. Beginning with ClearPath OS 2200 

Release 10.0, SOLAR level 4R4 automatically attaches this SCN value to any pre-10.0 

release software product key in the system key table. This allows registration of the 

product key tape and installation of software products from releases prior to ClearPath 

OS 2200 Release 10.0. 

3–16 7831 0349–043

Master SCN 


The Master SCN value is 999999999999. A software product key with a master SCN is 

authorized for registration and installation of its corresponding product on any system. A 

master SCN on the Exec Image Enabler key authorizes a product key for any licensed 

software group to be registered and its corresponding product installed. 

Licensed Software Group 

A licensed software group is a set of software authorized for a system. Unisys offers 

several different licensed software group packages for production and development 

environments. 

• ClearPath Plus General Purpose IOE 

• ClearPath Plus OS 2200 Software Development Kit (SDK) Package 

• ClearPath Plus OS 2200 Business Information Server (BIS) Package 

• ClearPath Plus OS 2200 Enterprise Application Environment (EAE) IOE Package 

When a licensed software group is purchased, it is assigned a unique SCN. A hardware 

system can have multiple licensed software groups. 

Software Product Key 

A software product key tape is included with each ClearPath OS 2200 software release 

order. The software product key tape contains the set of software product keys for the 

products purchased for the licensed software group. 

Previously, the software product key contained a product name, product level, and 

style-id. Beginning with ClearPath OS 2200 Release 10.0, each software product key also 

includes the SCN. 

Image Enabler Key 

An Image Enabler key is also known as a Software Control Performance (SCP) Exec key 

tape or file. The Exec uses an Image Enabler key to regulate the system performance 

level on ClearPath Plus systems. 

Image Enabler keys are delivered when you purchase a system or upgrade a system 

with a new performance level. Updating your system with a new ClearPath OS 2200 

software release level is not considered a system upgrade and a new Image Enabler key 

is not issued. 

The previous Image Enabler keys contained the MCN. The format of the new Image 

Enabler key contains an SCN in addition to the MCN. The new format is used with 

metered systems, and any new or upgraded systems delivered with ClearPath OS 2200 

Release 10.0 or higher. 

Compliance 

The software product key’s SCN must match the SCN on the currently registered Exec 

Image Enabler key in order to comply with the software license agreement. All software 

product keys issued prior to ClearPath OS 2200 Release 10.0 are considered to be in 

compliance. See the Pre-10.0 Release SCN definition for more information. 

7831 0349–043 3–17


Conditioned Software Package Tape 

This is a software package tape delivered by Unisys containing keyed product files that 

can be copied or installed only if the corresponding key authorizing the product is 

registered. 

Keyed Product 

This is a product on a conditioned software package tape, or originating from a 

conditioned software package tape. A keyed product is software license compliant only 

when it’s corresponding key SCN that matches the Exec image enabler key SCN is 

registered. 

3.5.2. Software License Management 

Software License Management ensures that software is installed and executed on the 

system and workload for which it was purchased. This is accomplished with the use of 

Software Control Numbers (SCN) on product keys and image enabler keys. The SCN on 

a product's installation or feature key must match the SCN on the registered image 

enabler key for the product to be compliant with your software license agreement. 

SOLAR does not prevent product key registration or corresponding software product 

installation if the registered Exec image enabler key contains a different SCN. Instead, 

SOLAR writes a warning message to its diagnostic file and registers the keys or installs 

the product. If executed in batch, SOLAR also displays a console message indicating that 

a noncompliance has occurred. 

Compliance validation applies to products installed from the keyed software package 

tape received from Unisys and to products originating from, but not installed directly 

from the package tape. For example, COMUS BUILD output and UNSTACK tapes, 

SOLAR/E created software packages, and LIBSAVE/LIBLOAD tapes. 

Software Product Key 

Software Product keys are created with a unique SCN value for a licensed software 

group. A separate software order must be placed for each SCN that is authorized for a 

system. Each software key tape is customized with the SCN information and should only 

be registered on the system where the SCN is authorized. 

When registering software product keys, SOLAR checks to verify that the SCN on the 

software product key tape complies with the current value of the SCN in the Exec Image 

Enabler key on the system. 

• If the system currently does not have an SCN value in the Exec Image Enabler key, 

the SCN value from the software product key tape is loaded into the Exec Image 

Enabler key after registering the software product key tape. 

• If the system currently has an SCN value in the Exec Image Enabler key and it does 

not match the SCN value on the software product key tape, software product keys 

will be registered although the system is not in compliance. In this case, SOLAR will 

generate a warning message. 

3–18 7831 0349–043

3.5.3. Ordering ClearPath OS 2200 Software 


An update order must be placed for every SCN authorized for a system. A ClearPath 

OS 2200 order includes new software products along with a software products key tape 

containing the set of software product keys that are customized by the SCN profile. 

The SCN number is located on the label of the software product key DVD received with 

the ClearPath OS 2200 software release. The following figure shows an example of a 

software product key DVD label. 

3.5.4. System Upgrade Information 

Image Enabler Information 

When a system is upgraded (new hardware is purchased or the performance level is 

changed), a new Image Enabler key is issued. The Image Enabler key includes the 

system’s MCN, SCN, and defines the Software Controlled Performance (SCP) level of 

the system. The SCN included on the new Exec Image Enabler key is a new SCN 

created when the software products authorized for use on the upgraded system are 

relicensed. 

Software Product Key Information 

A new SCN is also created for an existing system when it is upgraded to a new 

performance level and the software is relicensed. The upgraded software product keys 

are customized with the new SCN information. Once the upgraded Exec Image Enabler 

key is registered on the system, the new software product key tape must also be 

registered in order to comply with the new Image Enabler key information (see 3.5.5). 

The software products do not need to be reinstalled. 

7831 0349–043 3–19


3.5.5. Registering Your Software Product Keys 

For ClearPath OS 2200 Release 10.0 and higher, use SOLAR to register software 

product keys. When the keys are registered, SOLAR verifies that the SCN on the 

software product key tape complies with the value of the SCN in the Exec Image Enabler 

key. 

There are two scenarios, depending on the format of the Image Enabler key. 

• Old format Image Enabler key 

The Image Enabler key is in the old format if it does not contain an SCN value. In this 

case, the SCN value from the software product key tape is loaded into the Exec 

Image Enabler key when the ClearPath OS 2200 software product key tape is 

registered and the system is in compliance. 

• New format Image Enabler key 

The Image Enabler key is in the new format when it contains an SCN value. 

− When the SCN value on the software product key matches the SCN value on the 

Image Enabler key, the system is in compliance. 

− When the SCN value on the software product key does not match the SCN value 

on the Image Enabler key, the system is not in compliance. 

If you are running in batch mode, a console message is displayed informing you 

that a noncompliance has occurred and that there are informational messages in 

the diagnostic file. To become compliant, you must register the proper software 

product key tape. Find the SCN value displayed on the label of your software 

product key tape. Register the software product key tape that matches the SCN 

displayed when you use the MODELNUM keyin. After registration, your partition 

will be in compliance. 

Note: To determine the SCN and MCN values on your Image Enabler key that 

have been registered, use the MODELNUM keyin. Exec level 47R5 or higher 

shows both values. Earlier Exec levels show only the MCN. 

3–20 7831 0349–043

3.5.6. Frequently Asked Questions 


Is the Manufacturing Control Number (MCN) unique to a system? 

Yes, each hardware system is assigned a unique MCN when the system is built. 

For Intel based Next Generation OS 2200 systems, such as the Dorado 400 or Dorado 

4000, the 1 to 16 character MCN is derived from the manufacturing tag number or UUID. 

These MCN values are unique for all systems. 

Is the Software Control Number (SCN) unique to a specific MCN? 

Yes, the SCN is the software profile that is entitled to a specific hardware system MCN. 

A hardware system can have multiple SCNs, one for each workload. For example, 

MCN 1 can have a general IOE (SCN 0000001) and an SDK IOE (SCN 0000002) 

registered. These SCN profiles cannot be registered on another system, for example 

MCN 2. MCN 2 has its own unique SCNs, for example general IOE (SCN 0000003) and a 

Business Information Server (BIS) IOE (SCN 0000004). 

What is the difference between a software upgrade order and a software 

update order? 

A software upgrade occurs when a hardware change is made that requires the software 

to be relicensed. For example, if the performance level of a system is upgraded to a new 

level, the software must also be licensed at the new performance level. This order 

creates a new SCN. 

A software update order is created when the latest available software release is 

requested. This order does not create a new SCN. 

Is a specific SCN locked to an MCN for the life of the MCN? 

If a system is never upgraded, the original SCN will be the same for the life of the 

system. If the system is upgraded, a new SCN is issued. 

What happens if a ClearPath OS 2200 product key tape is accidentally 

registered on the wrong system? 

Find and register the software product key tape with the SCN on its label that matches 

the SCN on the registered image enabler key. If that does not correct the problem, 

contact the Unisys Support Center for assistance. Once the correct keys are registered, 

you should use SOLAR to unregister the keys with the wrong SCN. 

Can multiple software product key tapes be registered with multiple 

SCNs on a ClearPath OS 2200 Release 10.0 and higher system? 

Yes, each licensed software group has its own SCN and it is registered on a system. 

There can be multiple SCNs registered on a single MCN, depending on how many 

licensed software groups the system is authorized to run. Each licensed software group 

has a unique SCN, and a unique Exec Image Enabler key. 

7831 0349–043 3–21


How does this feature affect MIPS Image Enabler key partitioned systems 

and metered systems? 

Software License Management does not affect the partitionable Image Enabler keys. 

Note: All other Image Enabler keys are model-based, nonpartitionable keys. 

How does this feature affect package tapes created with SOLAR/E? 

With Software License Management Phase II, products on package tapes created by 

SOLAR/E are keyed, but not conditioned. Registered product keys are not required to 

install products from the package tape, but a product key with an SCN matching the 

Exec image enabler key SCN must be registered in order for the product to be software 

license compliant. 

Software License Management Phase I does not affect package tapes created by 

SOLAR/E. Output of SOLAR/E package tapes is in a nonkeyed format. 

Do not install software from a SOLAR/E package tape on a workload type for which it 

was not purchased. In future releases, SOLAR will prevent you from installing software 

from a SOLAR/E package tape unless a software license compliant product key is 

registered. 

How does this feature affect builds and installations on multiple systems? 

With Software License Management Phase II, products on build output tapes are keyed, 

but not conditioned. A registered product key is not required to install a product from a 

build output tape on another system or workload, but a product key with an SCN 

matching the Exec image enabler key SCN must be registered in order for the product to 

be software license compliant. 

Software License Management Phase I does not affect package tapes created by 

SOLAR/E. With Software License Management Phase I, output of a build is not keyed. 

Do not install software from a build output on a workload type for which it was not 

purchased. In future releases, SOLAR will prevent you from installing software from a 

build output unless a software license compliant product key is registered. 

How does this feature affect TeamQuest execution keys? 

Software License Management does not affect TeamQuest execution keys. TeamQuest 

execution keys are not created with SOLAR. As in the past, both installation and 

execution keys are required to execute your TeamQuest products. 

3–22 7831 0349–043

Software License Management and LIBSAVE/LIBLOAD 

Do Software License Management and SCNs lock software to a particular 

MCN? 

No, the SCN is not tied to a product. It is tied only to the product key. This allows 

software to be moved to another system provided that the target system has registered 

product keys containing a SCN matching the Image Enabler Key SCN. This allows you to 

distribute COMUS BUILD output and UNSTACK tapes, LIBSAVE/LIBLOAD, and 

SOLAR/E created packages to other systems. 

For example, products on MCN1 with SCN1 can be moved to MCN2 with SCN2 

provided corresponding product keys with SCN2 are registered on MCN2. Software on 

the target system MCN2 is in compliance. 

Notes: 

• If using LIBSAVE/LIBLOAD, the software product keys containing SCN2 must be 

reregistered on MCN2. 

• Software product keys do not need to be reregistered on the MCN2 system 

when using COMUS BUILD output and UNSTACK tapes, or SOLAR/E created 

packages. 

3.6. Software License Management and 

LIBSAVE/LIBLOAD 

LIBSAVE/LIBLOAD processes are used to save and restore an instance of the software 

libraries on a specific system or partition. These processes can also be used to save an 

instance of the software libraries and deploy it on another system or partition. 

LIBSAVE/LIBLOAD capabilities are available with Software License Management. 

However, additional steps are now required to perform these processes. To be in 

compliance, the Software Product key tape and the Image Enabler key tape 

corresponding to the LIBLOAD system must be registered on the LIBLOAD system 

once the LIBLOAD is complete. The following subsections identify the steps required to 

properly use LIBSAVE/LIBLOAD functions to save and restore the software products, 

software product keys, and Image Enabler keys. 

3.6.1. LIBSAVE/LIBLOAD Examples 

Examples in 3.6.2 and 3.6.3 show how Software License Management affects the 

LIBSAVE/LIBLOAD scenario. In the examples, a LIBSAVE is performed on System A. 

System A is running ClearPath OS 2200 Release 10.0 or higher product levels. A 

LIBLOAD is performed on two separate systems (System B and System C). 

The examples show a LIBLOAD on two different systems. There is a slightly different 

process depending on whether the LIBLOAD system fits into the System B category or 

the System C category. At the end of each example, each system is running ClearPath 

OS 2200 Release 10.0 or higher products and each system complies with the software 

license agreement. 

Performing the steps in the examples ensures that the proper Image Enabler key and 

software product keys are registered on the LIBLOAD system. 

7831 0349–043 3–23


You must perform these steps with the proper Image Enabler key and ClearPath 

OS 2200 Release 10.0 or higher software product keys for each system. 

Notes: 

• The Image Enabler key for new systems delivered in ClearPath OS 2200 Release 

10.0 and higher and all metering systems contain both a Manufacturing Control 

Number (MCN) and a Software Control Number (SCN). All other Image Enabler keys 

contain only an MCN. 

• Beginning with ClearPath OS 2200 Release 10.0, software product keys include an 

SCN. 

• For each workload that a LIBLOAD is performed on, ClearPath OS 2200 software 

product keys for that workload must be registered. 

Following are the parameters associated with each system: 

• System A at the time of the LIBSAVE 

− ClearPath OS 2200 Release 10.0 or higher is installed. 

− Image Enabler key contains MCN1 and SCN1. 

− Software product keys contain the SCN value of SCN1. 

• System B prior to LIBLOAD 

− The System B category is determined by the format of its Image Enabler key. 

The Image Enabler key is the new format and contains both MCN and SCN 

information. 

Systems with this format are either metering systems or new hardware systems 

delivered with ClearPath OS 2200 products. 

Note: A new nonmetered hardware system delivered with ClearPath OS 2200 

Release 9.1 or lower-level products is in the System C category. 

− Image Enabler key contains MCN2 and SCN2. 

− Software product keys contain the SCN value of SCN2. 

• System C prior to LIBLOAD 

− The System C category is determined by the format of its Image Enabler key. 

The Image Enabler key is the old format and contains only MCN information. 

These systems do not fit into any category defined for System B. 

Systems in category C are nonmetered systems that were delivered with 

software products prior to ClearPath OS 2200 Release 10.0. 

− Image Enabler key contains an MCN value of MCN3. No SCN information is 

available. 

− Software product keys are from before ClearPath OS 2200 Release 10.0. No 

SCN information is contained in these keys. 

If your system is in the same category as System B, see 3.6.2. Otherwise, see 3.6.3. 

3–24 7831 0349–043


3.6.2. Example 1: Performing a LIBLOAD onto System B 

This example is for LIBLOAD systems in the System B category. The system’s Image 

Enabler key contains SCN information. 

Note: In each step of this example, the table shows the status of the Image Enabler 

keys for each system after the action is performed. The table also shows whether the 

Image Enabler key is in compliance. 

Perform the following steps: 

1. Perform LIBSAVE from System A to save DATA$ information from System A. 

Image Enabler 

Keys 

System A System B 

Product 

Key 

Image Enabler 

Keys 

Product 

Key 

MCN1 SCN1 SCN1 MCN2 SCN2 SCN2 Yes. 

In Compliance 

Product key SCN matches new 

format Image Enabler key SCN. 

2. Perform LIBLOAD onto System B to load DATA$ information from System A onto 

System B and replace System B key values with System A key values. 

Image Enabler 

Keys 


Product 

Key 

Image Enabler 

Keys 

Product 

Key 

MCN1 SCN1 SCN1 MCN1 SCN1 SCN1 No. 

WARNING 

In Compliance 

Image Enabler key MCN does 

not match hardware MCN. 

Once the system’s Image Enabler key has been removed from the system, 

you have 30 minutes to reregister the key. Warning messages will be 

displayed on the system console. 

7831 0349–043 3–25


3. Register System B Image Enabler key tape values MCN2 and SCN2 onto System B. 

Image Enabler 

Keys 


Product 

Key 

Image Enabler 

Keys 

Product 

Key 


In Compliance 

Product key SCN does not 

match Image Enabler key SCN. 

4. Register System B ClearPath OS 2200 software product tape with the value of 

SCN2. 

Image Enabler 

Keys 


Product 

Key 

Image Enabler 

Keys 

Product 

Key 


In Compliance 

Image Enabler key and SCN 

key information is in 

compliance on System B. 

5. Use SOLAR to run the PRODRT installed product report to verify the system’s 

software license compliance. 

• All products authorized with System B product keys tape have SCN2 associated 

with them. 

• If a product authorized on System A does not have a corresponding product key 

with SCN2 registered on System B, the product, and its key with SCN1 are not 

in compliance and should be removed from System B using SOLAR. 

3–26 7831 0349–043


3.6.3. Example 2: Performing a LIBLOAD onto System C 

This example is for LIBLOAD systems in the C category. The system’s Image Enabler 

key does not contain SCN information. 

Note: In each step of this example, the table shows the status of the Image Enabler 

keys for each system after the action is performed. The table also shows whether the 

Image Enabler key is in compliance. 

Perform the following steps: 

1. Perform LIBSAVE from System A to save DATA$ information from System A. 

Image Enabler 

Keys 

System A System C 

Product 

Key 

Image Enabler 

Keys 

Product 

Key 

MCN1 SCN1 SCN1 MCN3 None None Yes. 

In Compliance 

2. Perform a LIBLOAD onto System C to load DATA$ information from System A onto 

System C and replace System C key values with System A key values. 

Image Enabler 

Keys 


Product 

Key 

Image Enabler 

Keys 

Product 

Key 


WARNING 

In Compliance 

Image Enabler key MCN does 

not match hardware MCN. 

Once the system’s Image Enabler key has been removed from the system, 

you have 30 minutes to reregister the key. Warning messages will be 

displayed on the system console. 

3. Use SOLAR to remove Image Enabler key for System C. 

Image Enabler 

Keys 


Product 

Key 

Image Enabler 

Keys 

Product 

Key 

MCN1 SCN1 SCN1 - SCN1 No. 

In Compliance 

Image Enabler key is no longer 

registered. 

7831 0349–043 3–27


4. Register the System C Image Enabler key tape value of MCN3 onto System C. 

There is no SCN value. 

Image Enabler 

Keys 


Product 

Key 

Image Enabler 

Keys 

Product 

Key 

MCN1 SCN1 SCN1 MCN3 None SCN1 No. 

In Compliance 

Product key contains an SCN 

value and Image Enabler key 

does not. 

5. Register System C software product tape value of SCN3 onto System C. 

Image Enabler 

Keys 


Product 

Key 

Image Enabler 

Keys 

Product 

Key 


In Compliance 

Product key SCN matches 

Image Enabler key SCN. 

6. Use SOLAR to run the PRODRT installed product report to verify the system’s 

software license compliance. 

• All products authorized with System C product keys tape have SCN3 associated 

with them. 

• If SCN1 authorizes more products than are authorized with SCN3, SCN1 product 

keys and their corresponding products are not in compliance and should be 

removed from System C using SOLAR. 

3–28 7831 0349–043

3.7. Keyed Tape Delivery 

Keyed Tape Delivery 

Unisys distributes its OS 2200 software products on software package tapes, which are 

installed with SOLAR. A software package tape is a tape that contains one or more 

OS 2200 software products. Unisys uses the PRODSV utility in SOLAR/E to create 

software package tapes. 

You receive two types of keyed distribution media: conditioned package tapes and key 

tapes. There are also products that are not keyed. 

A key tape is a tape containing product authorizations for a particular site. A key tape is 

registered through SOLAR (full-screen interface, calling PKGREG directly, or 

REGISTERPKG). This results in product authorizations being added to the system key 

table. PKGREG produces a summary report that lists all new product authorizations 

contained on each key tape registered. 

The following is an example of a key tape registration summary report: 

PKGREG 4R7A * Summary Report * 2012-02-24 1932:01 

************************************************************************* 

The New KEYTABLE$ Version is : 8 

The New System Identifier is: None 

The following key package(s) have been registered: 

Reel(s): DVD123 

Assign Options: TF 

Tape Type: DVDTP 

Expiration: 0 

Media Manager: none 

The following new product authorizations have been added to the key table: 

Name Level Style ID/ Concurrency Start Register Expiration Hard Exp Key Type SCN Release 

Key ID 

------ ------ -------- ------------- -------- -------- ---------- -------- -------- --------- -------- 

COMUS 6R9A 6371-00 - - 20120224 - - MIXED 0123456 13.1 

- 19:32:01 

- - - - - 

- 

SOLAR 4R7A 9894-25 - - 20120224 - - ABSOLUTE 0123456 13.1 

- 19:32:01 

- - - - - 

- 

Before you can install a product (or copy a product file from a conditioned package tape 

to mass storage), verification is made against the system key table to ensure that your 

site is authorized for the product or the file. 

7831 0349–043 3–29


Be aware of the following considerations: 

• For reference purposes, the key tape has a symbolic KEYTABLE$ element that 

contains a list of the keys on the tape. 

• The summary report from a registration of a key tape only displays all new product 

authorizations added to the system key table. Product authorizations are on a 

feature-level basis. A new product authorization is a key for a product previously not 

authorized or a key for a new feature release of a product. A key for a new feature 

release of a product also authorizes all stability update releases to the new feature 

release (for example, the key for 2R2 also authorizes stability updates 2R2A, 2R2B, 

and so on). Any duplicate entries are not inserted or displayed. You can use the 

summary report to determine new products that need to be installed. 

• A symbolic KEYTABLE$ element is generated by PKGREG in the system library file 

SYS$*DATA$. This element contains a list of current authorizations sorted by 

product. You can use the SOLAR full-screen interface to view currently registered 

keys. 

• Registered key tapes are not viewable for selection through the SOLAR full screen 

interface. There are no products on key tapes. Therefore, SOLAR performs no 

action, other than initial registration, with these tapes. 

• All products contained on a conditioned package tape are displayed through the 

SOLAR full-screen interface. You are only able to select products for installation that 

are authorized for your system. If you select an unauthorized product, SOLAR 

displays an appropriate error message and positions the cursor at the unauthorized 

selection. You can determine system installation authorization status by using the 

F10 function key to view product specific information. Authorization status 

(authorized/unauthorized) and software license compliance status are displayed for 

the product. 

• You can access utility file PRODSAVE$*UTILITY$ located at the beginning of each 

package tape to determine the location of each product on that tape. The element 

(TFD) contained in this file lists the products, product files, and their positions on the 

tape. 

• For information on the contents of the package tapes, see Appendix C. 

• If you try to install an unauthorized product, PRODLD errors with the following 

message: 

ERROR PRODLD 27626 

The product, XXXX, was specified to be installed. 

The installation site is not authorized for the 

product above. It cannot be installed. 

It is possible to receive several other error messages with the installation of 

unauthorized products. These include messages indicating no system key table 

exists and invalid key table message. However, the previous message is the 

standard unauthorized product installation message. 

3–30 7831 0349–043


• You need FURPUR to perform direct file copies (@COPY,G) or COMUS builds. 

– If desired, you can directly copy (using the FURPUR COPY,G command) any 

authorized product files from conditioned package tapes. In order for a product 

or file to be authorized, the appropriate key must be contained within the system 

key table. You must use FURPUR level 32R1B (or higher) to perform the copy. 

If you attempt to copy an unauthorized product file directly, with the FURPUR 

COPY,G command, the following error message is displayed: 

*ERROR PRA002216: The source tape file is a conditioned file. 

The site is not authorized to access the file. 

This error also occurs if you use the COPY,G command with a pre-32R1B level 

of FURPUR. 

– You must install FURPUR level 32R5A (or higher) before attempting to perform 

COMUS builds from conditioned package tapes. This occurs automatically if you 

follow the standard Unisys-supplied installation steps. 

If you attempt to perform a COMUS BUILD of a product that you are not 

authorized for, or you are only authorized for the absolute portion of the product, 

the COMUS build fails when you attempt to copy files from the input 

conditioned package tape. The following FURPUR error message is displayed: 

*ERROR PRA002216: The source tape file is a conditioned file. 

The site is not authorized to access the file. 

This error also occurs if you attempt to COMUS BUILD an authorized product 

with a pre-32R1B level of FURPUR. 

• When you receive a new key tape, register that tape with SOLAR to dynamically 

activate the corresponding products on the conditioned package tape. 

3.7.1. Nonkeyed Products 

The following products are delivered without SOLAR keys: 

• CP-FLD 

• CP-FLD400 

• CP-OE2 

• Exec boot tape 

• Exec release master / Symbolics 

• Enterprise Output Manager (EOM) for ClearPath OS 2200 (DEPCON) 

• MQSeries for ClearPath OS 2200 (MQS2200) 

• ODBC Data Access 

Note: ODBC Data Access requires a Product Capability Key, which varies 

depending on the system type and number of licensed users of ODBC Data Access. 

• Software Controlled Performance (SCP) key tape or file 

• SOLAR 

7831 0349–043 3–31

License Keys for TeamQuest Products 

• Virtual Machine for the Java Platform on ClearPath OS 2200 JProcessor (JPJVM) 

• WebSphere® MQ Version 7 for ClearPath OS 2200 (WMQ2200) 

3.7.2. Key Package Registration 

The following rules apply across all key types and supersede any specific key type rules: 

• When a product or feature key containing a key identifier is registered on a system, a 

matching key can be registered only if it contains the same key identifier or no key 

identifier. 

• The Software Control Number (SCN) on a product or feature key must match the 

SCN on the currently registered Exec Image Enabler key, contain the master SCN 

value, or contain the prerelease SCN value. 

• Unisys currently does not use the key identifier field on product keys. 

• Unisys currently does not enforce SCNs. They will be enforced in a future release. 

3.8. License Keys for TeamQuest Products 

The following TeamQuest products are released as keyed products requiring a license 

key to function correctly after installation: 

• TeamQuest Baseline (TQ-BASELINE) 

• TeamQuest CULL (CULL) 

• TeamQuest D-Fragger (TQD-FRAGGER) 

• TeamQuest IACULL (IACULL) 

• TeamQuest LA (LA) 

• TeamQuest Model (TQ-MODEL) (tqgetm program and PC program) 

• TeamQuest MSAR (MSAR) 

• TeamQuest MSManager (MSMANAGER) 

• TeamQuest Online (TQ-ONLINE) 

• TeamQuest OSAM (OSAM) 

• TeamQuest PAR (PAR) 

• TeamQuest PMLog (TQ-PMLOG) 

• TeamQuest Probes (TQ-PROBES) 

• TeamQuest RemD-Fragger (TQRDFRAGGER) 

• TeamQuest SAUtilities (SAUTILITIES) 

• TeamQuest SIMAN (SIMAN) 

• TeamQuest TIP-LA (TIP-LA) 

3–32 7831 0349–043


Your distribution package should contain the Product Installation Information Bulletin 

(PIIB) document for TeamQuest products. The product license key provided in the PIIB 

allows TeamQuest software to run for a short period. The PIIB document contains 

instructions on how to register your products with TeamQuest Corporation. 

Each system site-id requires a different product license key, which includes all licensed 

TeamQuest products. TeamQuest Model requires a second key for the workstation. 

A new product license key is not required if you are migrating from ClearPath OS 2200 

Release 12.0 or higher. 

A new product license key is required for all TeamQuest products if you are migrating 

from a release prior to ClearPath OS 2200 Release 12.0. 

This new product license key will expire according to the terms of your ETP license 

agreement. The expiration date will be specified when the key is provided. 

• One month before the product license key expires, a warning message will display 

when the product is executed. This message will indicate that your product license 

key will expire soon. 

• This new product license key will work with the next release of the same set of 

products, provided that the product license key has not expired. 

• You must obtain a new product license key whenever your system type changes, 

site-id changes, or if additional TeamQuest products are purchased. 

Note: If migrating to TeamQuest Model Level ClearPath 12.0 from a level previous to 

ClearPath 11.3, a new key is also required for the workstation. 

3.8.1. Updating Keys 

You need to update the SOFTWARE-KEY element to include a valid product license key. 

All TeamQuest license keys can be entered in the SOFTWARE-KEY element within the 

file SYS$LIB$*TEAMQUEST. If you wish to use this file, you must first verify that the file 

is cataloged and secured on your system. Use of this file is optional. 

If you do not use SYS$LIB$*TEAMQUEST, you need to update the SOFTWARE-KEY 

element in the installation file to include a valid key. TeamQuest keyed products will first 

search for the SOFTWARE-KEY element in SYS$LIB$*TEAMQUEST before searching 

the installation file. If SYS$LIB$*TEAMQUEST does not exist or it exists but does not 

contain a SOFTWARE-KEY element, software will search for the SOFTWARE-KEY 

element in the installation file. 

One advantage of placing your product license keys in SYS$LIB$*TEAMQUEST is that 

the information only needs to be updated once. If you keep your product license keys in 

individual installation files, each subsequent installation of a new level of that product 

wipes out that information. An administrator must then reenter that information before 

the product can be used. SYS$LIB$*TEAMQUEST is never affected by the installation 

of any product. Thus, if your site’s product license keys are kept in this master file, each 

product is immediately ready for use as soon as the installation completes. 

7831 0349–043 3–33


Use an editor to update the appropriate SOFTWARE-KEY element with the entire 

product license key line that was supplied to you. Multiple product license key lines are 

permitted. The format of the key line follows: 

name key comments 

where: 

name 

key 

is the site-id for the system or the keyword DEMO_KEY (for product license keys 

used before products are registered). 

is the 29-character product license key. This product license key must be inserted 

exactly as received. It is preferable that the product license key be put in the 

element using a copy/paste function. 

comments 

are any notes about the product license key that you want to make. This field is not 

required and is ignored. You may want to put in the expiration date of the product 

license key. 

Following are examples of a SOFTWARE-KEY element. The first example shows an 

element with the product license key delivered with the release. The second example 

shows an element with a registered product license key line in it. 

Example 1 

DEMO_KEY 9ABDFLAHJHF@BAJNHBFLDEAJHGD@6 key expires 11/2010 

Example 2 

CL01 9ABDFLAHJHF@BAJNHBFLDEAJHGD@6 

Note: Depending on the security that is placed on the installation file, you may need to 

be privileged to update the SOFTWARE-KEY element in the installation file. 

When updating the SOFTWARE-KEY element, add the line at the top of the element and 

remove any previous product license key lines. If you would like to keep older product 

license key lines, you should make these lines as comment lines by placing a number 

sign (#) in the first column. 

3–34 7831 0349–043


3.8.2. Product License Registration for Your OS 2200 Host 

You will be asked to supply some additional information to register your product. A utility 

called keyinfo is installed in the product installation file. This keyinfo utility must be used 

to gather the product license key information. Execute the keyinfo utility to obtain the 

permanent key information. The utility creates a report that you should send to your 

TeamQuest software distributor as described in the TeamQuest Product Installation 

Information Bulletin. 

You can execute the keyinfo utility as follows: 

@add installation-filename.keyinfo 

where installation-filename is the file into which the TeamQuest product was installed 

(for example, SYS$LIB$*OSAM). 

Example of Keyinfo Utility Report 

An example of the utility is as follows: 

>@add sys$lib$*osam.keyinfo 

> 

>The following information should be sent to your distributor 

>for creating a TeamQuest key: 

> 

>-------------------------------------------------------------- 

> KeyInfo 2R1A generated on 07/17/11 13:21:56 

> 

> 12345678901234567890 

> Exec Level : 48R7 

> Siteid : CL01 

> System Type : 2200/8030 

> MCN : 00112233 

> SCN : 1234567 

> Expiration : 2011/12/15 

3.8.3. Product License Registration for your PC (TeamQuest 

Model Only) 

To obtain your registered product license key, you will need to supply the report output 

from the keyinfo utility. The keyinfo utility is installed in the product installation file and is 

used to gather the permanent product license key information. The utility creates a 

report that you should send to your TeamQuest software distributor as described in the 

TeamQuest Product Installation Information Bulletin. 

The keyinfo utility can be run as follows: 

TQDIR\model\keyinfo 

where TQDIR is the path to the directory where TeamQuest Model is installed. 

7831 0349–043 3–35

Build Option 

3.8.4. Obtaining a Registered Product License Key 

To obtain a registered product license key, an electronic form is located at the following 

location, which can then be sent by e-mail. 

http://www.support.unisys.com/public/TQ-Key/38507364.pdf 

If you cannot send the electronic form by e-mail, provide all information as listed in the 

TeamQuest Product Installation Information Bulletin. 

United States customers, call 1-888-866-7265 prompt #1, Monday through Friday 7:00 

am to 4:00 p.m. PST. 

International customers can contact your local Unisys customer support center. 

3.9. Build Option 

A build option that provides absolute keys for several products with the core media set is 

available for ClearPath sites. These products are used for customized builds before 

installation. The style of the build option for ClearPath Plus OS 2200 server sites is 

CSW20-BLD. You can order this style separately. 

Note: TIPUTIL requires C Compiler (UC) and ASCII FORTRAN Compiler (FTN) to build. 

C Compiler is supplied to ClearPath sites as part of their IOE. ASCII FORTRAN Compiler 

is available by ordering this build option. 

ClearPath OS 2200 Series System Build Keys 

If you order this build option, you receive absolute keys for the following products: 

• ASCII COBOL Compiler (ACOB) 

• ASCII FORTRAN Compiler (FTN) 

• C Compiler (UC) 

• COBOL Compiler (UCOB) 

• FORTRAN Compiler (UFTN) 

3–36 7831 0349–043

Dorado 400, 4000, 4100, and 4200 Server Systems Terminology Overview 

3.10. Dorado 400, 4000, 4100, and 4200 Server 

Systems Terminology Overview 

When new platforms are introduced, new components and new names are sometimes 

used. Table 3–4 compares the names of components on Dorado 300 and 700/800 Server 

systems with the names on the Dorado 400 and 4000/4100/4200 Server systems that 

are the closest match. 

Table 3–4. Dorado 300/700/800 and 400/4000/4100/4200 

Systems Terminology Comparison 

Hardware 

Component 

Dorado 300/700/800 

Server 

System Platforms 

Processors IP Cell Intel ® 

Cell 

Memory IP Cell Intel ® 

Cell 

Dorado 

400/4000/4100/4200 

Server 

I/O Module I/O Module I/O Expansion Module 

I/O Processor IOP IOP 

I/O Card Rack PCI Expansion Rack PCI Channel Module 

I/O Cards HBAs and NICs HBAs and NICs 

Table 3–5 lists the names of IOPs used with the Dorado 400, 4000, 4100, and 4200 

Server systems and compares them with IOP names for Dorado 300 and 700/800 Server 

systems. 

Table 3–5. Dorado 300/700/800 and 

400/4000/4100/4200 Systems IOPs Comparison 

Dorado 300/700/800 Server Dorado 400/4000/4100/4200 

Server 

SIOP, CIOP, and XIOP SIOP 

XIOP (4000/4100/4200 only) 

Dorado 400, 4000, 4100, and 4200 Server systems I/O are based on PCI standards. IOPs 

from Dorado 100 and 200 Server platforms are not compatible with the new system 

architecture. 

For further information on any of the topics in this subsection, see the ClearPath Dorado 

400 Server Operations Guide (3850 8016), the ClearPath Dorado 4000 Server Operations 

Guide (3826 5179), the ClearPath Dorado 4100 Server Operations Guide (3850 7109), or 

the ClearPath Dorado 4200 Server Operations Guide (8207 3982). 

7831 0349–043 3–37

Dorado 400, 4000, 4100, and 4200 Server Systems Terminology Overview 

A System Architecture Interface Layer (SAIL) provides the interface between the Intel 

hardware and the OS 2200 Integrated Operating Environment (IOE, for nonmetered 

systems) or Unisys Operating Environment (UOE, for metered systems), which is the 

foundation of the ClearPath enterprise server software model. SAIL also provides 

console and peripheral connectivity for the Dorado 400, 4000, 4100, and 4200 Server 

system. 

Internal I/O Cell 

SAIL software is installed at the customer site onto an external redundant array of 

independent disks (RAID) (Dorado 400/4000 only) or onto the integrated disks of the 

lower cost base system (Dorado 400/4000/4100/4200). 

Remote I/O Cell 

A Dorado 400 Server system can have a remote I/O cell; a Procnode cell is required to 

connect the remote I/O cell to the internal I/O cell. 

The remote I/O cell provides SIOPs for the attachment of OS 2200 storage peripherals. 

I/O Expansion Module 

A Dorado 4000/4100 Server system will have a minimum of one I/O Expansion Module. 

Each IOP in the I/O Expansion Module connects to its own PCI Channel Module. 

3.10.1. Administration and Operation Components 

The administration and operation of the Dorado 400, 4000, 4100, or 4200 Server system 

is provided by Server Sentinel, Operations Sentinel, OS 2200 Server Management 

Control (SMC), and the SAIL Control Center. 

Service Processor, Server Sentinel, and OS 2200 Server Management 

Control 

Release 1 of Dorado 400 Server systems only supports embedded Service Processors. 

The embedded Service Processor is housed in the Control Module within the cells. The 

Service Processor attaches to both the hardware LAN and the maintenance LAN, which 

are virtual networks on the Server Sentinel LAN. 

Release 1 uses only the Server Sentinel features included in the firmware release, 

including Call Home and remote services software; it does not use the Server Sentinel 

Management components. Server Sentinel does not manage the OS 2200 environment; 

it manages the underlying hardware and firmware platform. A new software component 

called OS 2200 Server Management Control manages the OS 2200 environment. 

Through Server Sentinel, the system looks like a standard hardware platform, except the 

operating system type for the Dorado 400 Series partition is shown in the Server 

Sentinel user interface as OS 2200 for IA32 Processor Family with 64-bit Extensions. 

Server Sentinel server software runs on the embedded Service Processor and can be 

accessed from any Server Sentinel workstation configured on the maintenance LAN. 

3–38 7831 0349–043

Dorado 300 and 700/800 Server Systems Terminology Overview 

Operations Server, Operations Sentinel, and Operations Workstation 

The Operations Server runs Operations Sentinel and OS 2200 Server Management 

Control. Redundant Operations Servers can be configured. Operations Servers are 

attached to the maintenance LAN. Operations Server can be accessed from any 

Operations Workstation configured on the maintenance LAN. Also, serial connections 

between the Dorado 400 and 4000 Series partition cells and the Operations Servers 

carry SAIL Console traffic. 

OS 2200 Server Management Control 

The OS 2200 Server Management Control manages the OS 2200 environment. This 

includes partitioning, power management, initializing, booting, and maintaining the 

OS 2200 environment. OS 2200 Server Management Control server software runs on 

the Operations Server and can be accessed from any Operations Workstation configured 

on the maintenance LAN. 

The SMC also provides the power management and call home functions for Specialty 

Engines connected to Dorado 300 and 700/800 servers. 

SAIL Control Center 

The SAIL Control Center provides utilities for configuration and administration of SAIL. 

The SAIL Control Center is hosted by a web server running on SAIL and can be accessed 

from any Operations Workstation configured on the maintenance LAN. 

3.11. Dorado 300 and 700/800 Server Systems 

Terminology Overview 

When new platforms are introduced, new components and new names are sometimes 

used. Table 3–6 details the names of components on the Dorado 300 and 700/800 

servers. 

Hardware Component 

Table 3–6. 300/700/800 Server Systems Terminology 

Processors IP Cell 

Memory IP Cell 

I/O Module I/O Module 

I/O Processor IOP 

I/O Card Rack PCI Expansion Rack 

I/O Cards HBAs and NICs 

System Platforms 

Dorado 300/700/800 Server 

7831 0349–043 3–39

Dorado 300 and 700/800 Server Systems Terminology Overview 

Table 3–7 lists the names of new IOPs introduced with the Dorado 300 and 700/800 

Server systems. 

Table 3–7. Dorado 300/700/800 Server Systems IOPs 

Dorado 100 and 200 

Series 

Dorado 300 

Server 

CSIOP SIOP, CIOP, and 

XIOP 

Dorado 700 

Server 

SIOP-E, CIOP-E, 

and XIOP-E 

SCIOP SIOP SIOP-E SIOP-M 

PCIOP CIOP CIOP-E CIOP-M 

XIOP XIOP XIOP-E XIOP-M 

Following is a definition of the acronyms used in this table: 

CIOP – Communications I/O Processor for Ethernet connections 

CSIOP – Compatible channel I/O processor 

PCIOP – Peripheral component interconnect input output processor 

SCIOP – Standard channel I/O processor 

SIOP – Storage I/O Processor for tapes and disks 

XIOP – eXtended I/O Processor for connection to the XPC-L 

Dorado 800 

Server 

SIOP-M, CIOP-M, 

and XIOP-M 

Dorado 100 and 200 Series systems have CSIOPs that support both peripherals and 

network connections. Equivalent functionality on Dorado 300 and 700/800 Server 

systems requires the SIOP, CIOP, and XIOP. 

Dorado 300 and 700/800 Server systems I/O are based on PCI standards. IOPs from 

Dorado 100 and 200 Series platforms are not compatible with the new system 

architecture. The ClearPath 300/700/800 I/0 processors are not compatible with each 

other. 

3–40 7831 0349–043

ClearPath and Plateau Interdependencies 

3.12. ClearPath and Plateau Interdependencies 

Plateau media must be ordered and installed by your Unisys service representative. 

ClearPath OS 2200 Release 13.2 was tested as an integrated package on ClearPath. 

Table 3–8 and Table 3–9 list the Initial Plateau Release level for a system, the current 

supported plateau release level, and plateau levels that are required to support the latest 

release. 

Note: Refer to the appropriate system plateau customer reference manual for detailed 

information. 

Table 3–8. ClearPath Dorado Plateau Interdependencies Without XPC-L 

Support 

Dorado System 

(without XPC-L 

support) 

Dorado 320, 330, 340, 

350, 380,390 

System Plateau Release 

Level 

Initial Current 

Release 13.2 Dependency 

Requires New Plateau 

1.0 3.0 No specific dependency 

Dorado 400 1.0 1.1 SAIL IC = SAIL-1.1.A* or higher 

Dorado 4050, 4080, 

4090 

Dorado 4150, 4170, 

4180, 4190 

Dorado 4250, 4270, 

4280, 4290 

1.0 2.3 Requires Dorado 4000 Plateau 2.3 

and ClearPath 13.1 Dorado 4000 

Compatibility Package ** 

1.0 1.2 Requires Dorado 4100 Plateau 1.2 


Dorado 740, 750 2.0 3.0 No specific dependency 

Dorado 780, 790 1.0 3.0 No specific dependency 

Dorado 840, 850, 860, 

870, 880, 890 


7831 0349–043 3–41


Table 3–9. ClearPath Dorado Plateau Interdependencies with XPC-L Support 

Dorado System (with 

XPC-L support) 

XPC-L support on Dorado 

320, 330, 340, 350, 

380,390 

XPC-L Support on Dorado 

4080, 4090 

XPC-L Support on Dorado 

4180, 4190 


780, 790 


860, 870, 880, 890 

Notes: 

System and XPC-L Plateau 

Release Level 

Initial Current 

Release 13.2 Dependency 

Requires New Plateau 

Dorado Plateau No specific dependency 

2.1 3.0 

XPC-L Plateau 

XPC-L-2 2.0 2.2 

XPC-L-3 3 .0 3.0 

Dorado Plateau Requires Dorado 4000 Plateau 2.3 

2.0 2.3 

and ClearPath 13.1 Dorado 4000 

Compatibility Package ** 

XPC-L Plateau 

XPC-L-2 2.2 2.2 

XPC-L-3 3.0 3.0 

Dorado Plateau Requires Dorado 4100 Plateau 1.2 

1.1 1.2 

XPC-L Plateau 

XPC-L-2 2.2 2.2 

XPC-L-3 3.0 3.0 


2.0 3.0 

XPC-L Plateau 

XPC-L-2 2.1 2.2 

XPC-L-3 3.0 3.0 


3.1 3.1 

XPC-L Plateau 

XPC-L-3 3.0 3.0 

• *CPCommOS levels higher than 2R2 are not supported on Dorado 400 systems. 

CPCommOS 2R2 is required for use on the Dorado 400 systems. 

• ** The ClearPath 13.1 Dorado 4000 Compatibility Package also applies to ClearPath 

13.2. For additional information on the ClearPath 13.1 Dorado 4000 Compatibility 

Package, see section 7.9. 

3–42 7831 0349–043


• For current system plateau information, see the releases section of your specific 

hardware on www.support.unisys.com 

The CPCommOS product has direct dependencies with several plateau products. 

Table 3–10 details the requirements by product level. 

Product/Level 

Table 3–10. CPCommOS Plateau Component Requirements 

CPCommOS 2R2 ClearPath 

OS 2200 12.0 

CPCommOS 2R2A ClearPath 


Plus 








OS 2200 13.2 

Release Dorado 400 

Dependency 

XNIOP 4.61.11 

or higher 

Released in 

SAIL- 1.1.A IC 

Dorado 4000 

Dependency 

XNIOP 4.61.12 or 

higher 

Released in 1.1 

Not supported XNIOP 4.61.12 or 

higher 

Released in IC 

SAIL-1.7.7 or 

higher 

Not supported Plateau 2.3 and 

additionally the 

ClearPath 12.1 

Compatibility 

Package 




Compatibility 

Package 




Dorado 4000 

Compatibility 

Package 




Dorado 4000 

Compatibility 

Package 

Dorado 4100 

Dependency 

Dorado 4200 

Dependency 

Not supported Not supported 



Plateau 1.2 Not supported 

Plateau 1.2 Not supported 

Plateau 1.2 Plateau 1.0 

7831 0349–043 3–43

ClearPath Specialty Engines Interdependencies 

3.13. ClearPath Specialty Engines 

Interdependencies 

ClearPath OS 2200 Release 13.2 supports the following three specialty engines: 

• OS 2200 JProcessor 

• OS 2200 QProcessor 

• ePortal for OS 2200 

The JProcessor and the QProcessor require additional supporting software not released 

with ClearPath OS 2200 Release 13.2. Additional supporting software is not required for 

ePortal. 

If you move up to ClearPath OS 2200 Release 13.2, you should also move JProcessor to 

release 2.1 and QProcessor to release 2.1. The following table shows the software 

dependencies. 

Specialty Engine ClearPath OS 2200 13.2 Product Levels 

JProcessor 2.1 JPJVM 7.0 

INTERCONNECT 1R3 

QProcessor 2.1 WMQ2200 7R0 

INTERCONNECT 1R3 

If you do not wish to move to the latest levels of JProcessor or QProcessor, refer to 

sections 3.13.1 and 3.13.2. 

3.13.1. OS 2200 JProcessor 

Release Contents 

The OS 2200 JProcessor release includes the following products that support Java on 

the JProcessor. The Support Name column in the following table identifies the short 

name for each product on the Unisys Product Support Web site. Refer to the 

JProcessor-2.0 System Release Profile (SRP) on the Unisys Product Support Web site. 

The SRP lists download information for each of the products in the OS 2200 JProcessor 

2.0 release. 

The following table identifies the contents of OS 2200 JProcessor 2.1. 

Product Component Level Support Name 

OS 2200 JProcessor 2.1 JProcessor 

Linux 2.1 JProcessor 

Admin-Console 2.1 JProcessor 

3–44 7831 0349–043


The following table identifies additional products being updated to support OS 2200 

JProcessor 2.1. 

Product Level Support Name 

Interconnect (IC2200) 1R3 INTERCONNECT 

JBoss Application ServerTM for ClearPath OS 2200 5.1A JBOSS-2200 

Virtual Machine for the JavaTM Platform on ClearPath 

OS 2200 JProcessor 

The following configurations are supported. 

7.0 JPJVM 

Product-Level Combination JProcessor 1.2 JProcessor 2.0/2.1 

JPJVM 6.3/ IC2200 1R2 Supported Not supported 

JPJVM 7.0/ IC2200 1R2 Supported Not supported 

JPJVM 6.3/ IC2200 1R3 Supported Supported (old mount points) 

JPJVM 7.0/ IC2200 1R3 Not supported Supported (new mount points) 

The following ClearPath Release 13.2 products can be used with JProcessor 2.1. 


Included in Business Information Server Release 11.1 and 47R1 

Business Information Server Resource Adapter for the JavaTM 

Platform 

Included in ClearPath OS 2200 Release 13.2 

Common Internet File System 

Note: It is recommended to always install the latest level of CIFS. 

2.0 BIS-RA 

7R3 CIFS 

Eclipse IDE for OS 2200 3.7 ECLIPSE-2200 

Java TM 

2 Platform, Enterprise Edition (J2EE) Java TM 

Resource Adapter 

for Open DTP (DTP-RA) 

Network Database Server Resource Adapter for the Java TM 

Platform 

(DMS-RA) 

13.0 J2EE-CONOPENDTP 

4.0 DMS-RA 

Open Distributed Transaction Processing 12R1C OLTP-TM2200 

OS 2200 Transaction Resource Adapter for the Java TM 

Platform 13.1 J2EE-CON-OS2200 

Relational JDBC Driver for ClearPath OS 2200 (RDMS-JDBC) 2.7 RDMS-JDBC 

7831 0349–043 3–45


The following ClearPath Release 13.1 products can be used with JProcessor 2.1. 



Business Information Server Resource Adapter for the JavaTM 

Platform 

Included in ClearPath OS 2200 Release 13.1 



2.0 BIS-RA 

7R3 CIFS 


Java TM 


Resource Adapter 

for Open DTP (DTP-RA) 


Platform 

(DMS-RA) 


4.0 DMS-RA 

Open Distributed Transaction Processing 12R1C OLTP-TM2200 







Business Information Server Resource Adapter for the Java TM 

Platform 



Note: It is recommended to always install the latest level of 

CIFS. 

2.0 BIS-RA 

7R2 CIFS 


Java TM 


Resource 

Adapter for Open DTP (DTP-RA) 


Platform (DMS-RA) 


3.1 DMS-RA 

Open Distributed Transaction Processing 12R1B OLTP-TM2200 




3–46 7831 0349–043





Business Information Server Resource Adapter for the Java TM 

Platform 




2.0 BIS-RA 

7R1 CIFS 


Java TM 


Resource 

Adapter for Open DTP (DTP-RA) 


Platform (DMS-RA) 


3.0 DMS-RA 

Open Distributed Transaction Processing 12R1A OLTP-TM2200 




3.13.2. OS 2200 QProcessor 

ClearPath OS 2200 Release 13.2 includes WebSphere MQ 7R0 and INTERCONNECT 

1R3 which are supported only on the QProcessor 2.1. 

The ClearPath OS 2200 Release 13.2 allows previously released QProcessor product 

levels (1.5) and their corresponding WMQ2200 and INTERCONNECT levels to run. 

The following configurations are supported. 

Product-Level 

Combination QProcessor 1.5 QProcessor 2.0 QProcessor 2.1 

WMQ2200 6R1/ 

IC2200 1R1C 


IC2200 1R2* 


IC2200 1R3 

Supported Not supported Not Supported 

Not Supported Not Supported Not Supported 

Not Supported Not Supported Supported 

Further information about QProcessor releases and compatibility considerations can be 

found in the QProcessor Product Validation Profile (PVP) and System Release Profiles 

(SRPs). These documents are available on the Unisys Product Support Web site. 

7831 0349–043 3–47

Microcode Requirements for CTS5236 and T9840A Tape Drives 

3.14. Microcode Requirements for CTS5236 and 

T9840A Tape Drives 

A CTS5236 or a T9840A tape drive on any channel type requires the following microcode 

levels: 

• SCSI CTS5236 MCODE 8.6 or higher 

• SBCON CTS5236 MCODE 8.7 or higher 

• T9840A MCODE 1.35.112 or higher 

• T9840B MCODE 1.35.312 or higher 

• T9840C MCODE 1.43.506 or higher 

• T9840D MCODE 1.43.706 

3.15. Supported Peripheral Products 

See Appendix A, “Supported Peripherals,” in the ClearPath Dorado 

300/400/700/800/4000/4100/4200 Server I/O Planning Guide (3839 6586). This appendix 

identifies the supported tape and disk products, discontinued products previously 

supported, and miscellaneous products. 

3–48 7831 0349–043

Section 4 

Exec Software Compatibility and 

Migration Considerations 

This section describes compatibility and migration considerations for the Exec software 

when migrating to ClearPath OS 2200 Release 13.2. 

• General Exec Considerations, grouped by release levels (Section 4.1) 

• SGS and Configuration Parameters (Section 4.2) 

• Migrating to Metered Systems (Section 4.3) 

• Log Entry Changes (Section 4.4) 

• XPC-L Considerations (Section 4.5) 

• Tape and DVD Considerations (Section 4.6) 

• TIP Considerations (Section 4.7) 

• Software Controlled Performance (SCP) Considerations (Section 4.8) 

• POSTOEXMSTR (Section 4.9) 

In addition to the General Exec Considerations grouped by release level in 4.1, be sure to 

review the migration and compatibility considerations in all other areas of concern. 

7831 0349–043 4–1

General Exec Considerations 

4.1. General Exec Considerations 

This subsection identifies general Exec migration and compatibility considerations by 

software release level. 

Software Release Subsection 

ClearPath OS 2200 Release 13.1 4.1.1 




Review the considerations for all releases higher than the release from which you are 

migrating. 

4.1.1. ClearPath OS 2200 Release 13.1 

The Exec "IT" keyin is enhanced and modified to mini mize the customer confusion 

caused by incomplete documentation and inadequate console message descriptions. 

See PLE 18828324 for more specific details. 

1. Modifies the IT,TIMER logic to use the keyword "CLEAR" to clear the current 

disk timer values and set the system logic to use the default disk timer values. 

The keyin format is: 

"IT,TIMER CLEAR" and the response to this keyin is: 

DISK TIMER VALUES RESET TO DEFAULTS 

DISK IOP TIMEOUT VALUE IS 4 SECONDS. 

DISK HOST TIMEOUT VALUE IS 6 TO 13 SECONDS. 

2. The IT,TAPTIM keyin is changed to echo the value entered if it is in the 

range of 12 through 300. If the value is a non-zero value less than 12, 12 

seconds is used. If the value is greater than 300, 300 seconds is used. The value 

of zero is not legal. CLEAR is used to reset the realtime values back to the 

default non-realtime values. 

3. The IT keyin to enable/disable the SCIOP internal traces is being modified to 

accept the ON, OFF, and STATUS options as defined for the original IT trace 

keyins. 

4–2 7831 0349–043


KEYTABLE$ Migration Code 


The SOLAR 4R7 Dot-Format Level enhancement introduces an Exec migration 

consideration. You must build and boot your current Exec to integrate the changes in 

PLE 18756811. These fixes are required in order for the Exec to recognize the new 

enhanced version of the system key table written by SOLAR level 4R7 or higher. You 

must update and boot your current EXEC to include this KEYTABLE$ migration code 

before installing SOLAR level 4R7. FURPUR level 32R5A or higher is also required. 

A SOLAR level 4R7 or higher KEYGEN-created key can only be used on an Exec that 

recognizes the new key table version. When SOLAR level 4R7 or higher is first used to 

register any key, the SYS$*DATA$.KEYTABLE$ is written in the new format which is not 

recognized by previous levels of SOLAR or the Exec. All previous product installation, 

feature, and Exec image enabler model-based, MIPS-based, and MIPS metered keys are 

compatible with SOLAR level 4R7 or higher. 

Cross-boot consideration for Dorado 400 and Dorado 4000 systems 

A known problem may prevent existing Dorado 400 or Dorado 4000 systems from being 

able to boot ClearPath OS 2200 Release 13.0 EXEC level 48R7. This issue can only arise 

if the EXEC level you are currently running is 48R4 (ClearPath OS 2200 Release 12.0). 

EXEC levels 48R5 and 48R6 already contain the necessary change. If you are a Dorado 

400 or Dorado 4000 customer and are running EXEC level 48R4, you must build and boot 

PLE 18691159 before you make any attempt to boot EXEC level 48R7. 


SIP Real Memory Utilization Statistics 

With the incorporation of PLE 18683962 into ClearPath OS 2200 12.1, some of the SIP 

Real Memory Utilization (RMU) statistics may no longer be zero for Dorado 400 and 

Dorado 4000 systems. Beginning with ClearPath OS 2200 12.1, Exec maintains values 

for the RMU time-product that indicates the amount of memory that is in use (Active) 

over time. It reflects the aggregate physical memory usage on the system by both Exec 

and SAIL and can be used to track overall system memory usage. The existing Absolute 

Memory statistics remain unchanged. 

RUN$ Runstream Changes 

The following products have changed their RUN$ runstream RunIDs for this release. 

Product Eltname 

Old 

RunID 

New 

RunID 

MSCP MSCP MSCP MSCP 

MSCP MSCPRT (new run) MSCPRT 

MSCP MSCP/RT MSCPRT MSCPRT 

IRU IRU IRU IRUREC 

7831 0349–043 4–3


EXEC 

(Run$) 

TAPECOPY TPCOPY TAPCPY 

A short summary of other changes to the runstreams in RUN$: 

• IRU runstream is changed to breakpoint (BRKPT) the run output to a file and delete 

the print. Perform the command @ASG,AZ on the IRU installation file to make sure it 

is present. The options on the IRU call are changed to EPX. 

• MSCP runstream is changed to breakpoint (BRKPT) the run output to a file and 

delete the print. 

Compatibility Issue for SENTRY_CONTROL and Run-level Quota systems 

This release includes the changes associated with EXEC PLE 18730588. This PLE 

corrects a problem but may also introduce a potential compatibility issue for sites using 

both SENTRY_CONTROL and Run-level Quota enforcement (EXEC configuration 

parameter ACCTON set to 4). 

On systems using Run-level Quota enforcement, one of the privilege flags located in 

every user's Quota Set indicates whether or not that user has the capability of creating 

files with the “V” and “G” options. On Fundamental Security systems, the presence or 

absence of that Quota privilege has always correctly controlled whether “V” and “G” 

option files could be created. On systems with SENTRY_CONTROL, however, that 

Quota privilege flag has only been regulating a user's ability to create “V” option files. In 

prior releases, any user on a SENTRY_CONTROL system has been allowed to create 

“G” option files, even when the privilege flag in their Quota Set should have been 

preventing this. The changes implemented by PLE 18730588 in ClearPath OS 2200 

Release 12.1 now enforce the value found in the privilege flag of the Quota Set. Users 

who have this Quota privilege flag enabled will continue to be able to create “G” option 

files but users without this Quota privilege who try to create any “G” option files will 

now receive an error. This correction creates the small potential that some existing 

runstreams or utilities which worked on previous releases may now encounter an error. 

If failures occur in these environments when trying to create files with the “G” option, 

either create the files without the “G” option or else have your Security Administrator 

set the privilege flag in the Quota Set of the user receiving the error to grant them the 

capability of creating files with the “V” and “G” options. 

4–4 7831 0349–043

MSCP Changes 

When you install MSCP, the following runstreams are added: 

• MSCP (Run-id is MSCP) 

• MSCPRT (Run-id is MSCPRT) 

• MSCP/RT (Run-id is MSCPRT) 


If you choose to do a SOLAR installation of the separate MSCP product, the MSCP 

program must first be terminated using the E keyin. The MSCP product is always 

installed in the file SYS$LIB$*MSCP. The default install for MSCP is MODE A, which will 

insert an @START,A/X of the realtime MSCPRT runstream into the AUTO$START 

element in SYS$LIB$*RUN$. The customer can choose to SOLAR-install the nonrealtime 

version of MSCP by specifying MODE B, which will insert an @START,A/X of 

the non-realtime MSCP runstream into the AUTO$START element in SYS$LIB$*RUN$. 

MSCP runstreams include MSCP, MSCPRT, and MSCP/RT. The runstreams MSCPRT 

and MSCP/RT are identical and perform real-time enforcement of your monitor 

programs. 

The @START image for MSCP or MSCPRT is contained in element AUTO$START in 

SYS$*RUN$ or SYS$LIB$*RUN$. The image should be updated with a site-acceptable 

account number and quota set to let the MSCPRT run in the real-time environment. 

By default, SYS$*RUN$.AUTO$START automatically starts the real-time version of the 

MSCP product. If you choose to SOLAR-install this product, SOLAR creates a new entry 

in SYS$LIB$*RUN$.AUTO$START to start the MSCP product. If @START statements for 

MSCP exist in both of your AUTO$START elements, two different instances of the 

MSCP background run will become active during every system reboot. Therefore, if you 

choose to SOLAR-install this product, you should remove the @START statement for 

MSCP/RT from SYS$*RUN$.AUTO$START so that the @START statement in 

SYS$LIB$*RUN$.AUTO$START is the only one which gets used. 

Refer to the Exec Administration Reference Manual for additional information. 


This subsection describes the Exec migration and compatibility considerations that apply 

to Exec level 48R4. 

• Problems could occur after a site moves up to UDSC 16R1. At that point, if the 

customer is running on CP11.2 EXEC level or higher, the customer could use UDSC 

16R1 to create some of the new type nine QITEMs. Then, if they drop back to a 

CP11.0 EXEC or earlier, they would need to have the cross-boot PLE (18390396) 

applied to their CP11.0 or earlier EXEC level. The CP11.1 or higher EXEC will 

recognize the type nine QITEMs but the CP11.0 EXEC will not unless the PLE is 

added. 

7831 0349–043 4–5


• The Audit Trail Descriptor (ATD) version has been increased to 021 due to 

reformatting changes in the ATD. This version change will force ALL audit trails on 

the system to be closed on the initial crossboot to this EXEC level. The following 

message will be displayed for each configured audit trail: 

AT n *VERSION MISMATCH: ARF – 0xx EXEC – 021* 

where n is the trail number and xx is the version number recovered from the ARF 

(from the previous EXEC level). These audit trails will then be recovered from the 

MCT to a closed state. This will force all Stepcontrol applications to do an SUTIL 

recovery (PANIC and REBUILD recovery options will not be possible). 

4.1.5. LIBSAVE/LIBLOAD Scenario 

Communications Platform for Open Systems (CPCommOS) is a new communications 

product introduced with ClearPath Dorado 400 and 4000/4100/4200 Server systems. 

Dorado 300, 700, and 800 Server systems continue to use the CPComm 

communications product. 

To perform a LIBLOAD between a Dorado 300, 700, or 800 Server system and a 

ClearPath Dorado 400, 4000, 4100, or 4200 Server system, the correct communications 

product must be installed after the LIBLOAD is completed. See PLE 18483131 for 

required CPComm changes. 

To install the applicable communications product, perform the following steps: 

1. Perform LIBSAVE on system A. 

2. Perform LIBLOAD on system B. 

3. Use SOLAR to register the system B software product key tape. 

4. Install the correct communications product on system B. 

• CPComm for Dorado 300, 700, and 800 systems is on package tape 

CP-COMMSUITE. 

• CPCommOS for Dorado 400, 4000, 4100, and 4200 Server systems is on 

package tape CP-COMMSUITE. 

Note: The communications configuration file is not included in the LIBSAV. 

4.1.6. I/O COMMAND QUEUING (IOCQ) 

I/O Command Queuing (IOCQ) can greatly improve disk performance. IOCQ allows 

multiple I/Os to be performed on the same logical disk at the same time. This can reduce 

the amount of queuing and the time needed to complete I/Os, which reduces the I/O 

existence time, and potentially, overall transaction existence time. 

Prior to IOCQ, the OS 2200 allowed only one I/O to be active to a logical disk. If an I/O 

was active to a logical disk, any subsequent I/Os were queued in OS 2200 until the 

active I/O completed. 

4–6 7831 0349–043


With IOCQ, OS 2200 does not queue I/Os that are for the same disk. The I/Os are issued 

and the EMC microcode determines if any queuing is required. If the request can be 

satisfied in cache (cache hit), the I/O is performed. If a previous I/O is accessing the 

physical disk (cache miss) and a subsequent I/O needs to access that same physical 

disk, the subsequent I/O is queued until the previous one completes. 

IOCQ is available on all Dorado platforms. 

• For Dorado 300 Series systems, all qualifying disk subsystems automatically use 

IOCQ. 

• For earlier Dorado platforms, it is enabled for any system partition that contains one 

or more standard channel I/O processors (SCIOP). If there are compatible channel 

I/O processors (CSIOP) in a system partition containing one or more SCIOPs, IOCQ 

is also enabled for any qualifying CSIOP-attached disk subsystems in that partition. 

• IOCQ is available separately for CSIOP-only system partitions as a CER request, and 

can be obtained through Unisys Technical Consulting Services. 

Beginning with ClearPath OS 2200 Release 10.1, the IOCQ feature is integrated into the 

operating system. System partitions with qualifying configurations always have the 

required IOPCMQ relocatable element available to use command queuing. The IOPCMQ 

relocatable element is in the RO file on the Exec release master tape. 

The source for the IOPCMQ element is not released. If a CHG to the IOPCMQ element 

is required, a new relocatable element is released in a PLE. 

For a disk subsystem to qualify for IOCQ, all of the following conditions must be met: 

• The subsystem must be an EMC Symmetrix or DMX model. 

• The EMC functional microcode level must be 56.68.xx.yy or higher and include 

Symmetrix 5.0, 5.5, and DMX models, but exclude Symmetrix 4.8 and earlier 

models. 

• All logical controllers in the subsystem must be configured as single-port 

(single-path) in the partition in which they exist. 

If these conditions are met, the Exec drives the subsystem in IOCQ mode. You cannot 

disable IOCQ, either statically or dynamically if the subsystem meets the conditions. 

Note that there are no restrictions on channel types as long as the conditions are met. In 

addition, a qualifying IOCQ disk can also participate in multihost file sharing. 

A separate IOPCMQ relocatable element is released under CER control for sites that 

need IO Command Queuing on CSIOP-only partitions. The CER request is available 

through Unisys Technical Consulting Services. 

Use the following commands to install the IOPCMQ SPEF relocatable element released 

to the site for CSIOP: 

INSTALL IOPCMQ FEATURE FROM QUALIFIER*FILENAME 

CO$GENTYPE NEWCON 

7831 0349–043 4–7

SGS and Configuration Parameters 

4.2. SGS and Configuration Parameters 

The migration considerations pertaining to SGS or configuration parameters are as 

follows. 

General Considerations 

During system generation, all SGS configuration labels in the CO$CONFIG element are 

compared to a list of valid configuration SGSs. If an invalid SGS is detected, the following 

error occurs and system generation stops. 

ERROR - CO$CONFIG SGS LABEL "name" 

IS NOT VALID BECAUSE IT IS MISSPELLED, IS OBSOLETE, OR 

HAS AN IMBEDDED SEMICOLON. VERIFY THE SPELLING, REMOVE 

OBSOLETE SGS(S), OR CORRECT THE IMBEDDED SEMICOLON! 

ALL '*. COMMENT' OR '". COMMENT' LINES MUST USE THE 

RECOMMENDED '. COMMENT' FORMAT! 

4.2.1. MODEL_TYPE Statement 

The MODEL_TYPE SGS defines the machine system type. The valid choices are as 

follows: 

• VERSION3E – All SAIL-based systems. 

• 2200/XPA – All CMOS systems. 

Format 

MODEL_TYPE 2200/XPA 

MODEL_TYPE VERSION3E 

An architecture change requires a full generation to change all architecture dependent 

(2200/XPA or VERSION3E) elements. For example, a 2200/XPA master tape can 

generate a 2200/XPA system with a configuration generation, but a full generation is 

required to change the architecture type to a VERSION3E system. 

A 2200/XPA boot tape will not boot on a VERSION3E system and a VERSION3E boot 

tape will not boot on other Dorado systems. 

During all builds, the following PRESCAN/SKEL error message is displayed if a 

MODEL_TYPE SGS is not found in the CO$CONFIG element: 

ERROR: No required MODEL_TYPE SGS for a 2200/XPA or VERSION 3E! 

4–8 7831 0349–043

Migrating from a Nonmetered System to a Metered System 

During all builds, the following note is displayed if more than one MODEL_TYPE SGS is 

found in the CO$CONFIG element. The first MODEL_TYPE SGS created by COMUS is 

used. 

Note: A MODEL_TYPE [MODEL_TYPE,1,1,1] system is being built. If more than one 

MODEL_TYPE SGS is found, the first is used. 

4.3. Migrating from a Nonmetered System to a 

Metered System 

A system to be metered requires a new metered Image Enabler key, registration of new 

software product keys, and URU-OS2200. 

Perform the following steps to migrate from a nonmetered system to a metered system: 

1. Install the workstation component of URU-OS2200. This allows you to set up the 

URU client in advance. After the OS 2200 component of URU is installed in step 4, 

the URU client should connect to it immediately and begin collecting metering data. 

2. Register the new metered image enabler key. This key loads the system with new 

metering settings and a new system SCN. 

3. Register the new software product key tape. This step ensures that the software 

product keys match the SCN registered on the system. 

Note: You do not need to reinstall any of the system software. 

4. Immediately after the new software product keys are registered, install the OS 2200 

component of URU. Verify that a valid connection can be made between the URU 

client and the OS 2200 metered partition. 

This installation order ensures that no metering information is lost. 

4.4. Log Entry Changes 

See the System Log Operations and Support Reference Manual for a detailed description 

of all log entries. 


Exec Level 48R8 

Log entry type 16005 is defined to allow the logging of commands processed by the TIP 

utility SUPUR. For more information about SUPUR command logging and the format of 

the type 16005 log entry, see PLE 18769981. 

7831 0349–043 4–9

XPC-L 

4.5. XPC-L 

The XPC-L (Extended Processing Complex-Locking) is the next generation of XPC. 

XPC-L is a total replacement for XPC and it carries forward the database locking 

functions provided by XPC. System performance levels achieved using system-level-file 

caching functions of XPC can be achieved without XPC, so those functions are not 

provided by XPC-L. As a result, XPC-L is used only in multihost environments. 

4.6. Tape and DVD 

4.6.1. Tape 

This subsection provides information about the following: 

• Tape (4.6.1) 

• Tape Drive Encryption (see 4.6.2) 

• 36-track tape subsystems (see 4.6.3) 

• DLT 7000 and DLT 8000 tape subsystems (see 4.6.4) 

• Linear Tape Open Ultrium (LTO3-HP) Tape Drives (see 4.6.5) 

• Linear Tape Open Ultrium (LTO4-HP) Tape Drives (see 4.6.6) 

• T9840A tape subsystem (see 4.6.7) 

• T9840C tape subsystem (see 4.6.8) 

• T9840D tape subsystem (see 4.6.9) 

• T10000A tape subsystem (see 4.6.10) 

• T9840D and T10000A applicable (see 4.6.11) 

• T9940B tape subsystem (see 4.6.12) 

• CSC, ACSLS, and CARTLIB (see 4.6.13) 

• DVD (see 4.6.14) 

• Virtual Tapes (see 4.6.15) 

This subsection provides information on enhancements to the assign mnemonics, 

coexistence with other cartridge tape subsystems, and fast tape access. 

4–10 7831 0349–043

Tape Mnemonics 

Table 4–1 describes the assign mnemonics. 

Tape and DVD 

Note: The U47, U47L, U47NL, U47M, U47LM, LCART, NLCART assign mnemonics 

have not changed with this release. All assign mnemonics are described in the Executive 

Control Language (ECL) and FURPUR Reference Manual. 

Assign Mnemonic 

Table 4–1. Tape Assign Mnemonics 

CONV EQUATE 

Drive Allocated 

T All tapes Any available drives on system, 

regardless of format 

HIC All 18-track or 36-track 

1/2-inch cartridge tapes 

HICL All 18-track 1/2-inch 

cartridge tapes 

HICM All 36-track 1/2-inch 

cartridge tapes 

DLT70 All DLT 7000 cartridge 

tapes 

Any available 18-track or 36-track drive 

(for example 5073, CTS5236) 

Any available 18-track drive (for 

example, 5073) 

Any available 36-track drive (for 

example, CTS5136, CTS5236, 

OST4890) 

Any available DLT 7000 tape drive 

HIS98 All HIS98 cartridge tapes Any available HIS98 tape drive 

HIS98C All HIS98C cartridge tapes Any available HIS98C tape drive 

HIS98D All HIS98D cartridge tapes Any available HIS98D tape drive 

HIS99B All HIS99B cartridge tapes Any available HIS99B tape drive 

T10KA All T10000A cartridge tapes 

UT10KA 

LTO 

LTO3 

LTO4 

ULTO3, ULTO4 

ULTO3 

ULTO4 

Any available T10000A cartridge tapes 

Any LTO tape drive 

VTH All virtual tapes Appropriate tape drives 

Notes: 

• Be aware that when you use general assign mnemonics (T and HIC), you should 

determine the exact device type that was allocated so that later reassignments 

use the required assign mnemonic to read the tape. For example, if you begin 

with “HIC” and are allocated a 36-track device, you must use HICM, HIC51, 

HIC52, or U47M to reassign a 36-track device in order to read the tape. 

• Using the pool name “NONCTL” with the mnemonic U47 will force the 

assignment to a freestanding U47 drive. 

7831 0349–043 4–11


Maximum Transfer Length for Cartridge Tape Drives 

Normally, the Exec enforces the maximum transfer length of 256KB if a cartridge tape 

drive supports the expanded buffer capability (that is, EBCOPT); otherwise, the 

maximum transfer length of 131 KB is allowed. If, however, a CT0899 or a SCTAPE tape 

drive is assigned with EDRC data compression (that is, CMPEON) specified, then the 

maximum transfer length of 131 KB is enforced even if the drive is capable of supporting 

EBCOPT. An I/O request with a transfer length greater than the above maximum block 

size is rejected by the Exec with an error status of 06. 

Fast Tape Access 

The capability of using the LOCATE BLOCK ID and READ BLOCK ID hardware 

commands through user ER IO$ functions is currently available for all 1/2-inch cartridge 

and DLT tape drives. The following functions are provided: 

• Read block ID before write (RBIDW$) 

• Read block ID (RBKID$) 

• Locate block (LBLK$) 

These functions were introduced to use the high-speed search functions of the cartridge 

drive, allowing the drive to rapidly position a cartridge tape for access. 

Refer to PLE 16970158 for more information on performance with Fast Tape Access. 

4.6.2. Tape Drive Encryption 

Encryption is one of the most effective ways to achieve data security today. OS 2200 

supports tape drive encryption and the Sun/StorageTek Crypto Key Management 

Solution (KMS) Version 2.0 (KMS v2.0). Encryption functionality is built directly into the 

tape drive so the Operating System is not involved in the encryption processing. Sun’s 

encryption solution utilizes a standard AES-256 cipher algorithm. 

A successful data encryption strategy must address proper key management and make 

sure that the keys to unlock data are never lost. The Sun Crypto Key Management 

System provides safe, robust key management. It includes of a number of components: 

• Clustered Key Management Appliances (KMA) are dedicated appliances for creating, 

managing and storing encryption keys. 

• KMA Manager Software provides for the setup and administration of the encryption 

system, the interface is using a GUI management program. 

• The encryption agents are hardware and software embedded in the tape drives 

themselves. 

With this initial release of encryption on OS 2200, the encryption process is totally 

transparent to OS 2200. Once a tape device has been enrolled into the Key Management 

System all cartridges created on that device will be encrypted. 

4–12 7831 0349–043


An encrypting tape device can also read unencrypted cartridges, but you cannot write to 

an unencrypted cartridge unless you are at the beginning of tape (load point) and the 

cartridge would become encrypted. A tape cartridge currently cannot contain a mixture 

of encrypted data and unencrypted data; either the entire cartridge is encrypted or the 

entire cartridge is not encrypted. 

Tape Drives Supporting Encryption 

Encryption is fully supported on the following: 

• Sun/StorageTek T10000A 

• Sun/StorageTek T9840D 

• Sun/StorageTek LTO4-HP 

Restrictions 

Since the tape drive encryption process is totally transparent to the Operating System it 

is recommended that all drives be configured for encryption or all drives configured for 

no encryption. This release of encryption does not include any encryption subfield(s) on 

ECL or through program interfaces (ERs and CALLs). Future ClearPath releases will 

include enhancements to standard ECL statements to include encryption specifications. 

Encryption is not supported on the DSI LTO4-HP drive at this time. 

Operator Messages 

There are several I/O error messages that may be displayed on the operator 

console. These error messages can be found in the System Console Messages 

Reference Manual. The three new messages will be displayed for these events: 

• If an encrypted tape cartridge is inserted into a drive that does not have the 

encryption feature, the Operating System will prevent inadvertent overwrite of the 

encrypted cartridge and the operator will be notified. 

• If an unencrypted cartridge is mounted on a drive that has encryption enabled, you 

will not be able to append to that cartridge and the operator will be notified. 

• If an encrypted cartridge is mounted on an encryption enabled drive but the KMS 

system does not have the correct decryption key, you will not be able to read or 

write the tape and the operator will be notified. 

Related Documentation – Sun/StorageTek Crypto Key Management 

System 2.0 

• KMS 2.0 Systems Assurance Guide 

• KMS 2.0 Installation and Service Manual 

• KMS 2.0 Administration Guide 

• KMS 2.0 Engineer White Papers 

These documents can be accessed from the Sun Microsystems Web site. 

7831 0349–043 4–13


4.6.3. 36-Track Tape Subsystems 

The 36-track tape technology provides for double density and longer tape lengths. The 

Exec provides unique equipment mnemonics for configuring 36-track tape subsystems 

and unique file/tape assignment mnemonics for assigning tape files to this type of 

medium. 

This subsection provides the following information: 

• General considerations for 36-track tape subsystems 

• Specific considerations by subsystem 

− CTS5136 

− OST5136 

− CTS5236 

− OST4890 

• General tape mnemonic enhancements 

• Coexistence with other cartridge tape subsystems 

• Fast tape access 

General Considerations for 36-Track Tape Subsystems 

Consider the following when migrating to 36-track capability: 

• The 36-track tape drives use a new tape format to record more data than 18-track 

tapes. Eighteen tracks are written in one direction, and then another 18 tracks are 

written from the end to the beginning of the tape. Therefore, twice as much data can 

be recorded on 540-foot cartridge tapes. 

• Extended cartridge tapes (called E-tapes) are available for use in 36-track drives. 

E-tapes are 1,100 feet long—about two times longer than current cartridge tapes. 

Therefore, E-tapes can hold up to four times as much data as current 18-track tapes. 

Note: E-tapes should not be inserted in 18-track drives. Damage to the device or 

tape might occur. 

• Rewind time is virtually eliminated when a full tape is written in 36-track format 

because the tape has been written from the beginning to the end and back to the 

beginning. 

• The Exec returns an I/O error status 6 when a write of an I/O block greater than 256K 

bytes is attempted to a 36-track device. 

• All 36-track tapes are interchangeable between 36-track tape devices. 

• For most 36-track tape subsystems, read backwards I/O functions are not supported 

and are terminated with an I/O error status 024. However, this is not the case for 

CTS5136 tape subsystems. For these subsystems, the Exec returns an I/O error 

status 6 when a read backward of a partial or nonintegral EDRC block is attempted. 

4–14 7831 0349–043

• The following are compatibility considerations with 18-track tapes: 


− The 18-track tapes can be read by 36-track drives, but tapes written on 36-track 

cannot be read by 18-track drives. If you attempt this read, you will receive a 

data validity check error. 

Note: A labeled cartridge tape written in 36-track format will appear as an 

unlabeled cartridge tape when mounted on an 18-track cartridge drive. 

Therefore, use caution when answering the console message: “IS TAPE 

LABELED? Y,N”. Answering this message with “N” will allow the tape to be 

rewritten. 

− 36-track devices might read 18-track formatted tapes written with or without 

EDRC data compression. 36-track devices cannot read tapes created with Unisys 

compression. 

• Assign mnemonics are changed. The letter M is added to designate the 36-track 

density. 

U47M assigns a stand-alone 36-track drive (CTS5136) 

U47LM assigns an ACS 36-track drive (CTS5136) 

HIC51 assigns a SCSI 36-track drive (OST5136 and OST4890) 

HIC52 assigns a SCSI or SBCON 36-track drive (CTS5236) 

HICM assigns any available 36-track drive 

Note: The HIC51 and HIC52 assign mnemonics are handled differently for STK 

libraries than previous mnemonics. Refer to the Executive Control Language (ECL) 

and FURPUR Reference Manual for more information. 

• The following are considerations for placing 36-track tapes in Automatic Cartridge 

Systems (ACS): 

− When 36-track tapes are placed in an ACS, all tape drives in one ACS must be 

36-track. 

− Assignment of 36-track tapes in an ACS is accomplished with U47LM, HIC51, 

and HIC52. 

• Using ACS names as assign mnemonics is not supported for 36-track tape 

subsystems. If an ACS name is specified in a tape assignment statement, the Exec 

attempts to assign any 18-track tape device available in the ACS. 

Specific Considerations by Subsystem 

This subsection describes the specific considerations pertaining to the following 36-track 

tape subsystems: 

• CTS5136 

• OST5136 

• CTS5236 

• OST4890 

7831 0349–043 4–15


CTS5136 

CTS5136 is a 36-track tape subsystem that is attached through BMC or SBCON 

channels. 

Due to the device equipment mnemonics and file assignment mnemonics introduced by 

this feature, products that are sensitive to these mnemonics are affected. 

OST5136 

OST5136 is a 36-track tape subsystem that is attached through SCSI-2 channels 

(SCSI-2N and SCSI-2W). 

Note: You need to install SCSITIS if your site is configured with an OST5136 

subsystem. 

Considerations for the OST5136 tape subsystem are as follows: 

• Due to device equipment mnemonics and file assignment mnemonics introduced by 


• Currently, all existing OST5136 customers use freestanding drives. The OST4890 

tape subsystem has been specifically designed by StorageTek to configure in a 

single-size 9710 ACS library managed by ACSLS software. If your site has both 

OST5136 freestanding drives and OST4890 ACS drives, the following potential 

compatibility issues might exist when using the HIC51 mnemonic: 

− Drive allocation will be based on the location of the volume. If the library has the 

volume-id, an OST4890 drive will be selected. If the library does not have the 

volume-id, a freestanding OST5136 drive will be selected. 

− In case you want to force the assignment to an OST5136, you may use the pool 

of NONCTL to force a drive allocation outside of the library. 

You can always use absolute device assignments. 

CTS5236 

CTS5236 is a 36-track tape subsystem that is attached through SBCON or SCSI-2W 

channels. 

Note: You need to install CARTLIB if your site is configured with a CTS5236 subsystem 

that connects to SBCON channels. You also need to install SCSITIS if your site is 

configured with a CTS5236 subsystem that connects to SCSI channels. 

Considerations for the CTS5236 tape subsystem are as follows: 

• Due to a hardware limitation, the operator’s tape cleaning message is not supported 

for the SCSI CTS5236 tape subsystem by the Exec. The cleaning indicator light on 

the SCSI CTS5236 tape unit maintenance panel is displayed when the unit needs 

cleaning. 

• Due to device equipment mnemonics and file assignment mnemonics introduced by 


4–16 7831 0349–043

OST4890 


OST4890 is a 36-track tape subsystem that is attached to ClearPath systems through 

SCSI-2W channels. 

The OST4890 is a functionally compatible tape subsystem as compared to the existing 

OST5136 tape subsystem; as such, the Exec provides a unique control unit mnemonic 

for configuring this subsystem but no new assignment mnemonic and thus no new 

device equipment mnemonic is created. The existing OST5136 device assignment 

mnemonic, HIC51, is used for assigning tape files for the OST4890. The existing 

OST5136 device equipment mnemonic, U5136, is also used for configuring the OST4890 

devices. 

Note: You need to install SCSITIS if your site is configured with an OST4890 

subsystem. 

Considerations for the OST4890 tape subsystem are as follows: 

• Due to the new control unit equipment mnemonic introduced by this feature, 

products that are sensitive to this mnemonic are affected. 

• Currently, all existing OST5136 customers use freestanding drives. The OST4890 

tape subsystem has been specifically designed by StorageTek to configure in a 

single-size 9710 ACS library managed by ACSLS software. If your site has both 

OST5136 freestanding drives and OST4890 ACS drives, the following potential 

compatibility issues might exist when using the HIC51 mnemonic: 

− Drive allocation will be based on the location of the volume. If the library has the 

volume-id, an OST4890 drive will be selected. If the library does not have the 

volume-id, a freestanding OST5136 drive will be selected. 

− In case you want to force the assignment to an OST5136, you may use the pool 

of NONCTL to force a drive allocation outside of the library. 

You can always use absolute device assignments. 

• If your site uses the 9710 library, and eventually migrates to a larger library (for 

example, CLU6000), you will need to change all HIC51 assign mnemonics. If you are 

planning to migrate to a larger library, use HICM for the OST4890 usage to avoid 

potential mnemonic changes. However, if you use HICM for the OST4890 drives, 

and then add a larger library (for example, CLU6000), you could have two competing 

libraries. In this case, the query/polls would assign a drive in the correct library based 

on the location of the volume-id. If you add the freestanding U47M instead, the drive 

allocation will be purely based on whether the library software (that is, ACSLS) 

returns a positive-poll for a specified volume-id. If the library has the volume-id, an 

OST4890 drive will be selected. If the library does not have the volume-id, a 

freestanding U47M drive will be selected. 

7831 0349–043 4–17


4.6.4. DLT 7000 and DLT 8000 Tape Subsystems 

Note: DLT 8000 tape subsystems are supported only in the 35-GB mode configured as 

the DLT 7000. All information in this subsection applies to both DLT 7000 and DLT 8000 

tape subsystems. 

The DLT 7000 tape subsystem connects through SCSI-2W channels. The DLT 7000 tape 

subsystem will not work on SCSI narrow channels. 

DLT 7000 tape subsystems provide a maximum capacity per cartridge of 35 GB of 

uncompressed data (up to 70 GB of compressed data) and a sustained data transfer rate 

of 5 MB per second. Tape subsystems use the LZ1 data compression technique. 

Tape cartridges use half-inch tape. These cartridges are not interchangeable with 

cartridges used with 9-, 18-, and 36-track tape drives. 

The Exec provides unique equipment mnemonics for configuring the subsystem and a 

unique specific assign mnemonic for assigning tape files. Other than the generic assign 

mnemonic T, existing assign mnemonics used to assign half-inch cartridge tapes cannot 

be used to assign DLT 7000 tape drives. 

The Exec supports DLT 7000 tape subsystems as boot devices and system dump 

devices. They can also be used for checkpoint/restart. Checkpoint can assign DLT 7000 

tape devices with the new assign mnemonic DLT70, or the more generic assign 

mnemonic T. Restart can assign DLT 7000 tape devices with the new assign mnemonic, 

DLT70. 

Considerations for the DLT 7000 tape subsystem are as follows: 

• Read backward I/O functions are not supported. If a read backward is attempted, it is 

terminated with an I/O error status of 024 (octal). 

• DLT 7000 tape drives are not compatible with any other OS 2200 tape device. 

• The LED display is not supported by the Exec due to a DLT 7000 hardware limitation; 

therefore, the Exec does not display either system-ID or reel-ID on the drive. 

• The Exec does not support all densities or write capabilities that the DLT 7000 

hardware supports. Table 4–2 lists the capabilities that are supported and those that 

are not supported by the Exec. 

4–18 7831 0349–043

Table 4–2. Capabilities Supported by the Exec 


Tape Type Densities Tape Read Tape Write 

DLT III 2.6 GB No No 

6.0 GB No No 

10 GB (uncompressed) Yes No 

20 GB (compressed) Yes No 

DLT IIIxt 15 GB (uncompressed) Yes No 

30 GB (compressed) Yes No 

DLT-IV 35 GB (uncompressed) Yes Yes 

70 GB (compressed—actual 

capacity depends on data) 

Yes Yes 

DLT III and DLT IIIxt type tapes can only be read by DLT 7000 tape subsystems. 

They cannot be used as blank or scratch tapes. 

Caution 

All DLT 7000 cartridge tapes contain header blocks that are written at the 

factory. Therefore, the tapes must never be degaussed because any attempt 

to read or write a degaussed DLT 7000 tape can produce unpredictable I/O 

errors (for example, timeout or data check). 

• DLT 7000 tape subsystems cannot read traditional 9-, 18-, or 36-track formatted 

tapes. To read these tapes and transfer the data to a DLT 7000 tape subsystem, you 

must have a tape device on the host system that can read the 9-, 18-, or 36-track 

formatted tapes. You can then transfer the data to the DLT 7000 tape subsystem. 

• The function of the general assign mnemonic T is expanded so that it can be used 

with DLT 7000 tape subsystem. You must be aware of tape drive allocation while 

using this mnemonic in case the general assign mnemonic T is configured via 

SERVO TYPE SGS or as a standard system tape device. In this case, the assigned 

DLT 7000 tape drive will be freed (@FREE) by the system and, if there is other tape 

drives available, you are given an option to choose another type. If the only tape 

drives available are DLT 7000 tape drives, you may have to reconfigure the system 

for mass storage audit trail devices. 

• Using ACS names as assign mnemonics is not supported for DLT 7000 tape 

subsystems. You should use other means (for example, absolute device 

assignments when assigning DLT 7000 tape drives). If an ACS name is specified in a 

tape assignment statement, the Exec attempts to assign only half-inch cartridge tape 

drives (for example, HIC, HICL) available in ACS. 

7831 0349–043 4–19


• Audit trails cannot be configured to use DLT 7000 tape subsystems. You must be 

aware of tape drive allocation while using the general assign mnemonic T in case it is 

configured through SERVO TYPE SGS or as a standard system tape device. In this 

case, the assigned DLT 7000 tape drive will be freed (@FREE) by the system and, if 

there are other tape drives available, you are given an option to choose another type. 

If the only tape drives available are DLT 7000 tape drives, you may have to 

reconfigure the system for mass storage audit trail devices. 

• The operator clean message to the system console is not supported for the DLT 

7000 because the drive does not report ANSI standard requests for cleaning. 

However, the DLT 7000 has an LED indicator that is lit when the drive needs 

cleaning or the tape is bad. When DLT 7000 tape subsystems are part of a tape 

library, the Automated Cartridge System Library Software (ACSLS) should be set to 

the autocleaning-enabled mode. This enables the ACSLS and the library to perform 

the cleaning. 

• The SCSITIS separately packaged Exec feature must be installed in order to 

configure DLT 7000 tape drives. 

• Business Information Server (previously MAPPER) level 41R1 (or higher) and 

TeamQuest LA level 6R3 (or higher) are required to support the DLT 7000 tape 

subsystem. 

• MMGR level 46R2 (HMP IX 5.0) or higher is required to support DLT 7000 tape 

subsystems. 

• Sort/Merge consideration—A tape volume for DLT 7000 tape subsystems can store 

up to 70 GB of compressed data. In the past, unless a NUMREC parameter was 

specified or scratch file were explicitly assigned, the SORT processor assumed that 

tape files would fill tape volumes associated with the file. Based on that assumption, 

the SORT processor would assign appropriately sized scratch files. 

Because of the size of tape volumes for DLT7CT tape subsystems, the SORT 

processor no longer makes that assumption. Now, the SORT processor assumes 

that the last tape volume associated with each input file assigned to a DLT7CT tape 

device contains 2 GB. If the last tape volume of a file contains more than 2 GB, you 

must assign appropriately sized scratch files before calling the SORT processor or 

passing a NUMREC or RECORD parameter to the SORT processor runstream. 

• FAS consideration—DLT 7000 tape subsystems are not included in the Locate Block 

Performance and FAS Usage Scenarios discussions under Performance 

Considerations in the FAS Operations Guide because DLT 7000 tape subsystems do 

not experience the same performance problems. However, tests indicate that 

performance of this tape subsystem does not improve significantly until you access 

files larger than 500,000 tracks. 

4–20 7831 0349–043

4.6.5. Linear Tape Open Ultrium LTO3-HP Tape Drives 

The LTO3-HP is configured as a LTO3-SUBSYS tape subsystem. 

Caution 


Unisys supports LTO tape drives for audit devices. However, before 

configuring a Step Control type audit trail to use either the LTO3-HP or 

LTO4-HP drives, you should consider the potential impact on the application’s 

recovery time. Application recovery times can be significantly impacted 

depending upon the location (on the tape) of the recovery start point and the 

number of LBLK$ operations required to position the tape during recovery. 

Application programs, thread duration, audit volume, AOR action, and TCDBF 

checkpoints will affect tape positioning and could push the combined Exec 

and IRU short recovery times beyond fifteen minutes. 

The LTO3-HP tape subsystem can be used either in a library or in a freestanding 

environment. The subsystem supports both SCSI (Ultra 320) and fibre channel 

connections to the host; however, OS 2200 systems only support the fibre channel. The 

LTO3-HP subsystem can write to Ultrium 2 and Ultrium 3 cartridge media. A Generation 

3 subsystem can read Ultrium 1 cartridges, but cannot write to them. 

The Ultrium 2 media has an uncompressed capacity of 200 GB and a compressed 

capacity of 400 GB. The Ultrium 3 media has an uncompressed capacity of 400 GB and a 

compressed capacity of 800 GB. 

The Generation 3 subsystem uses the LTO-DC data compression format, which is based 

on ALDC. The subsystem does not compress data that is already compressed. 

The Ultrium 3 device transfers uncompressed data at 80 MB per second and 

compressed data at 160 MB per second. The actual transfer rate is limited by the 

channel connection and IOP type. 

There are no density options. The Generation 3 subsystem writes at the density that is 

appropriate for the media type being used. 

Electronic partitioning (EP) is supported for the HP Ultrium 3 device. 

The Generation 3 subsystem supports buffering, and Ultrium 3 devices include a 128-MB 

cache buffer. Both Tape Mark Buffering Phase I (BUFFIL) and Tape Mark Buffering 

Phase II (BUFTAP) are supported. 

The LTO specification requires that a device can read and write the current generation 

format (Ultrium 3) and one previous format (Ultrium 2). For the Generation 3 subsystem, 

if an Ultrium 3 cartridge or Ultrium 2 cartridge is mounted, it can be read and written. The 

Generation 3 subsystem cannot write to an Ultrium1 cartridge, but it can read from it. 

7831 0349–043 4–21


4.6.6. Linear Tape Open Ultrium LTO4-HP Tape Drives 

The LTO4-HP is configured as a LTO4-SUBSYS tape subsystem. 

Caution 

Unisys supports LTO tape drives for audit devices. However, before 

configuring a Step Control type audit trail to use either the LTO3-HP or 

LTO4-HP drives, you should consider the potential impact on the application’s 

recovery time. Application recovery times can be significantly impacted 

depending upon the location (on the tape) of the recovery start point and the 

number of LBLK$ operations required to position the tape during recovery. 

Application programs, thread duration, audit volume, AOR action, and TCDBF 

checkpoints will affect tape positioning and could push the combined Exec 

and IRU short recovery times beyond fifteen minutes. 

The LTO4-HP tape subsystem can be used either in a library or in a freestanding 

environment. The subsystem supports both SCSI (Ultra 320) and fibre channel 

connections to the host; however, OS 2200 systems only support the fibre channel. The 

LTO4-HP subsystem can write to Ultrium 3 and Ultrium 4 cartridge media. A Generation 

4 subsystem can read Ultrium 2 cartridges, but cannot write to them. 

The Ultrium 3 media has an uncompressed capacity of 400 GB and a compressed 

capacity of 800 GB. The Ultrium 4 media has an uncompressed capacity of 800 GB and a 

compressed capacity of 1600 GB. 

The Generation 4 subsystem uses the LTO-DC data compression format, which is based 

on ALDC. The subsystem does not compress data that is already compressed. 

The Ultrium 4 device transfers uncompressed data at 120 MB per second and 

compressed data at 240 MB per second. The actual transfer rate is limited by the 

channel connection and IOP type. 

There are no density options. The Generation 4 subsystem writes at the density that is 

appropriate for the media type being used. 

Electronic partitioning (EP) is supported for the HP Ultrium 4 device. 

The Generation 4 subsystem supports buffering, and Ultrium 4 devices include a 128-MB 

cache buffer. Both Tape Mark Buffering Phase I (BUFFIL) and Tape Mark Buffering 

Phase II (BUFTAP) are supported. 

The LTO specification requires that a device can read and write the current generation 

format (Ultrium 4) and one previous format (Ultrium 3). For the Generation 4 subsystem, 

if an Ultrium 4 cartridge or Ultrium 3 cartridge is mounted, it can be read and written. The 

Generation 4 subsystem cannot write to an Ultrium 2 cartridge, but it can read from it. 

4–22 7831 0349–043

Restrictions 

• Encryption is restricted with the DSI ALP64 device (LTO4-HP). 


• Sort/Merge consideration – A tape volume for LTO4-HP tape subsystems can store 

up to 1600 GB or more of compressed data. In the past, unless a NUMREC 

parameter was specified or scratch files were explicitly assigned, the SORT 

processor assumed that tape files would fill the tape volumes associated with the 

file. Based on that assumption, the SORT processor would assign appropriately sized 

scratch files. 

Because of the size of tape volumes for LTO4-HP tape subsystems, the SORT 


that the last tape volume associated with each input file assigned to a tape device 

contains 2 GB. If the last tape volume of a file contains more than 2 GB, you must 

assign appropriately sized scratch files before calling the SORT processor or pass a 

NUMREC or RECORD parameter to the SORT processor runstream. 

• Performance consideration – The tape repositioning (stop/start) characteristics of the 

LTO4-HP directly impact the write performance (elapsed time) when writing multiple 

files sequentially to tape, as is typically the case when using FAS and FURPUR. This 

impact can be particularly severe when many small files are written to tape. 

Write performance can be optimized by eliminating tape repositioning whenever 

possible. To accomplish this always specify the BUFTAP buffered-write mode on the 

tape assignment. Also note that PLE 18393956 documents a related tape 

repositioning impact when compression mode (CMPON) is specified for labeled 

tapes. Until the PLE documents that a fix is available, do not specify CMPON on the 

labeled tape assignment. 

To illustrate these performance impacts, a FAS BACKUP of 20 1,000-track files to a 

labeled LTO4-HP tape with BUFON/CMPON took nearly 6 minutes, but with 

BUFTAP/CMPOFF took less than 10 seconds. 

4.6.7. T9840A Tape Subsystem 

T9840A tape subsystems connect to the ClearPath systems server channels through 

single-byte command code set connection (SBCON), small computer system interface 

(SCSI-2W or SCSI-ULTRA), or Fibre Channel (FC) SCSI channels. The T9840A can be 

included in STK tape libraries or in a stand-alone environment. 

The T9840A uses the existing Client System Component (CSC) library feature when it is 

included in tape libraries (this version of CSC still uses the STK$ Executive request). The 

tape device driver is supported within the Exec through the SCSITIS separately packaged 

Exec feature when the T9840A attaches to the host through SCSI-2W, SCSI-ULTRA, or 

FCSCSI channels, and the CARTLIB separately packaged Exec feature when the T9840A 

attaches to the host through SBCON channels. 

Note: Throughout this subsection, wherever SCSI T9840A is mentioned, FCSCSI 

T9840A also applies. 

7831 0349–043 4–23


T9840A tape subsystems provide a maximum capacity per cartridge of 20 GB of 

uncompressed data. The tape subsystems use the LZ1 data compression algorithm that 

can improve capacity by factors of 2 and greater. However, individual results might vary 

depending on the characteristics of the data and other variables. 

The tape cartridges use half-inch tape. These cartridges are not interchangeable with 

cartridges used with 18-track, 36-track, or DLT tape drives. 


unique specific assign mnemonic for assigning tape files. Other than generic assign 

mnemonic T, existing assign mnemonics used to assign 1/2-inch cartridge tapes cannot 

be used to assign T9840A tape drives. 

The Exec supports T9840A tape subsystems as boot devices, system dump devices, for 

audit trails, and for checkpoint/restart. Checkpoint can assign T9840A tape devices with 

the new assign mnemonic HIS98, or the more generic assign mnemonic T. Restart can 

assign T9840A tape devices with the new assign mnemonic, HIS98. 

Considerations for using the T9840A tape subsystem are as follows: 

• The T9840A tape used by the T9840A has a native capacity of 20 GB. This is 12.5 

times the capacity of an E-cart 1100-foot cartridge written in 36-track format. 

Cautions 

• Do not degauss T9840A tapes. Servo tracks are written on the tape at the 

factory. When these tracks are mistakenly erased, the tape cartridge 

must be discarded. 

• If you drop a T9840A tape cartridge from a height of less than 1 meter, 

the cartridge is warranted to continue to read and write new data, but the 

media life might be shortened. Therefore, Unisys recommends that you 

copy data from a dropped cartridge to another cartridge and retire the 

dropped cartridge. Because the compressed capacity could be 40 GB per 

cartridge or greater, the importance of protecting cartridges from being 

dropped cannot be overstated. 



• T9840A tapes are not compatible with any other ClearPath IX system tape device. 

4–24 7831 0349–043

Tape 

Format 

IBM 9840 

(32-bit 

Block ID) 

Unisys 

9840 

(22-bit 

Block ID) 

Unisys 

9840 

(32-bit 

Block ID) 


Table 4–3 shows the incompatibilities that can exist between the three different types of 

tapes that can be created on T9840A/3590 subsystems. 

Table 4–3. SCSI and SBCON Compatibility Matrix 

IBM 

9840/SBCON “3590 

Mode” 

(32-bit capable) 

Read 

Append 

Unisys 

9840/SBCON 

(with feature) 


Read 

Device Types 

Append 

Unisys 

9840/SBCON 

(without feature) 


Unisys 

9840/SCSI or 

FCSCSI 


7831 0349–043 4–25 

Read 

Append 

Read 

OK OK OK OK Error 1 Error 2 OK OK 

OK up 

to 22 

bit 

OK up 

to 22 

bit 

Error OK OK OK OK OK OK 

Error OK OK OK up 

to 22 

bit 3 

OK up to 

22 bit 3 

OK OK 

Append 

1 LBLK operation will result in I/O error 03. For read, an existing operator error message “DEVERR” and 

an I/O error status 012 is returned to the user with fault symptom code (FSC) in sense data = 33E7. 

2 LBLK operation will result in I/O error 03. For read, an existing operator error message “DEVERR” and 

an I/O error status 012 is returned to the user with fault symptom code (FSC) in sense data = 33E8. 

3 LBLK operation beyond 22-bit addressing will result in I/O error 03. For read, an existing operator error 

message “DEVERR” and an I/O error status 012 is returned to the user. Fault symptom code (FSC) in 

sense data = 338A. 

• T9840A tape subsystems cannot read traditional 9-track, 18-track, 36-track, or DLT 

formatted tapes. To read these tapes and transfer data to a T9840A tape subsystem, 

you must have a tape device on the host system that can read 9-track, 18-track, 

36-track, or DLT formatted tapes. You can then transfer the data to the T9840A tape 

subsystem. 

• The function of the general assign mnemonic T is expanded so that it can be used 

with T9840A tape subsystems. 

• Using ACS names as assign mnemonics is not supported for T9840A tape 

subsystems. You should use assign mnemonic HIS98 (or absolute device assign) 

when assigning T9840A tape drives. If an ACS name is specified in a tape 

assignment statement, the Exec attempts to assign only 1/2-inch cartridge tape 

drives (for example, HIC, HICL) available in ACS.


• An LED indicator on a tape device lights when the drive needs cleaning or the tape is 

bad. The operator clean message to the system console is also supported for the 

T9840A. When T9840A tape subsystems are part of a tape library, the Automated 

Cartridge System Library Software (ACSLS) should be set to the 

autocleaning-enabled mode. This enables the ACSLS and the library to perform the 

cleaning. 

• The following products or features are required to support T9840A tape subsystems: 

− The Client System Component (CSC) library product supports the library 

configuration for T9840A tape subsystems. 

− The SCSITIS and /or the CARTLIB separately packaged Exec features must be 

installed in order to configure T9840A tape drives. 

− TeamQuest MSAR level 6R1D (or higher) and TeamQuest LA level 6R4 (or 

higher) are required to support T9840A tape subsystems. 

• Sort/Merge consideration – A tape volume for T9840A tape subsystems can store up 

to 40 GB or more of compressed data. In the past, unless a NUMREC parameter 

was specified or scratch files were explicitly assigned, the SORT processor assumed 

that tape files would fill the tape volumes associated with the file. Based on that 

assumption, the SORT processor would assign appropriately sized scratch files. 

Because of the size of tape volumes for T9840A tape subsystems, the SORT 




assign appropriately sized scratch files before calling the SORT processor or passing 

a NUMREC or RECORD parameter to the SORT processor runstream. 

4.6.8. T9840C Tape Subsystem 

T9840C tape subsystems connect to ClearPath systems server channels through Fibre 

Channel (FC) SCSI and SBCON channels. T9840C tape subsystems can be used in STK 

tape libraries. 

T9840C tape subsystems use the existing Client System Component (CSC) library 

feature when it is included in tape libraries (this version of CSC still uses the STK$ 

Executive request). The tape device driver is supported within the Exec through the 

SCSITIS separately packaged Exec feature when the T9840C attaches to the host 

through FCSCSI channels. 

T9840C tape subsystems provide a maximum capacity per cartridge of 40 GB of 

uncompressed data. Tape subsystems use the LZ1 data compression algorithm, which 

can improve capacity by a factor of 2 and greater. However, individual results might vary 

depending on characteristics of the data and other variables. 

The tape cartridges use half-inch tape. These cartridges are not interchangeable with the 

cartridges used with 18-track, 36-track, DLT, or CTS9940B tape drives. 

4–26 7831 0349–043


The Exec provides the unique equipment mnemonic U9840C for the device and the 

existing control unit mnemonic CU98SC (SCSI) or CU98SB (SBCON) for configuring the 

subsystem and the unique specific assign mnemonic HIS98C for assigning tape files. 

Other than generic assign mnemonic T, existing assign mnemonics used to assign ½ -inch 

cartridge tapes cannot be used to assign T9840C tape drives. 

The Exec supports T9840C tape subsystems as boot devices, system dump devices, 

and for checkpoint/restart. Checkpoint can assign tape devices with new assign 

mnemonic HIS98C, or the more generic assign mnemonic T. Restart can assign T9840C 

tape devices with new assign mnemonic, HIS98C. 

Considerations for using T9840C tape subsystems are as follows: 

• Tape used by the T9840C has a native capacity of 40 GB. 

Caution 

If you drop a 9840C tape cartridge from a height of less than 1 meter, the 

cartridge is warranted to continue to read and write new data, but the media 

life might be shortened. Therefore, Unisys recommends that you copy data 

from a dropped cartridge to another cartridge and retire the dropped 

cartridge. Because the compressed capacity could be 80 GB per cartridge or 

greater, the importance of protecting cartridges from being dropped cannot 

be overstated. 

• In order to crossboot to previous Exec levels that do not support a new device type, 

you must use a partitioned data bank (PDB) that does not contain the new device 

type. Products that are sensitive to the new device equipment mnemonics and file 

assignment mnemonics can be affected. 



• T9840C tape subsystems cannot read traditional 9-track, 18-track, 36-track, DLT, or 

CTS9940B formatted tapes. To read these tapes and to transfer data to a T9840C 

tape subsystem, you must have a tape device on the host system that can read the 

9-track, 18-track, 36-track, DLT, or CTS9940B formatted tapes. You can then transfer 

the data to the T9840C tape subsystem. 

• The function of general assign mnemonic T is expanded so that it can be used with 

T9840C tape subsystems. 

• Using ACS names as assign mnemonics is not supported for T9840C tape 

subsystems. You should use assign mnemonic HIS98C (or absolute device assign) 

when assigning T9840C tape drives. If an ACS name is specified in a tape 



• T9840C tape subsystems can read 9840A/9840B tape media, but cannot write to the 

media. 

7831 0349–043 4–27



bad. The operator clean message to the system console is also supported for 

T9840C tape subsystems. When T9840C tape subsystems are part of a tape library, 

the Automated Cartridge System Library Software (ACSLS) should be set to the 

autocleaning-enabled mode. This enables the ACSLS and library to perform the 

cleaning. 

• The following products or features are required to support T9840C tape subsystems: 

− Client System Component (CSC) library product supports the library 

configuration for T9840C tape subsystems. 

− SCSITIS separately packaged Exec feature must be installed in order to 

configure T9840C tape drives. 

− TeamQuest MSAR level 7R2A (or higher) and TeamQuest LA level 7R2 (or 

higher) are required to support the T9840C tape subsystem. 

• Sort/Merge consideration—A tape volume for T9840C tape subsystems can store up 



that tape files would fill the tape volumes associated with the file. Based on that 


Because of the size of tape volumes for T9840C tape subsystems, the SORT 




assign appropriately sized scratch files before calling the SORT processor or pass a 

NUMREC or RECORD parameter to the SORT processor runstream. 

4.6.9. T9840D Tape Subsystem 

The T9840D tape technology provides for higher density compared to 18 and 36-track 

tapes and almost twice the capacity of the T9840C. The maximum data capacity per 

cartridge supported by the T9840D is 75GB uncompressed compared to 40GB for the 

T9840C. The high density T9840D writes 576 tracks on a tape. The T9840D is three 

times faster that the T9840A, 1.6 times faster than the T9840B, and as fast as the 

T9840C. The new drive accepts the same medium as the T9840A, T9840B and T9840C. 

4–28 7831 0349–043


The T9840D tape subsystem attaches to the ClearPath OS 2200 series systems using a 

SCSI Fibre (SCSI) channel interface. The T9840D tape subsystem can either be included 

in the STK tape libraries or in a standalone environment. Although the T9840D drive uses 

a half-inch cartridge tape, the T9840D tape is not interchangeable with the cartridge tape 

used by 18-track, 36-track, U9940, T10000A, DLT, or LTO3-HP/LTO4-HP tape drives or 

vice versa. The Exec provides unique equipment mnemonics for configuring the 

subsystem T9840D and a unique specific assignment mnemonic ‘HIS98D’ for assigning 

tape files. Due to media incompatibility, any of the existing file assignment mnemonics 

that are available today for the half-inch cartridge tape assignment, except ‘T’ mnemonic, 

should not be used to assign a T9840D tape drive. 

The T9840D uses the existing CSC (Client System Component) library feature when 

included in the tape libraries. The tape device driver is supported within the Exec using 

the same handlers as its predecessors. Other features provided by the T9840D that are 

supported by the Exec include LED display, operator tape cleaning message, LZ1 data 

compression, fast tape access, and extended buffer mode. The T9840D is supported by 

the Exec as a boot device and system dump device. The T9840D may also be used for 

checkpoint and restart and may be used as an Audit Trail device. 

Checkpoint can assign the T9840D tape device via the new file assignment mnemonic 

‘HIS98D’ or via the generic file assignment mnemonic, ‘T’. Restart can assign the 

T9840D tape devices via the new file assignment mnemonic ‘HIS98D’. 

Mixed Media Management (from Sun/StorageTek 95739, Rev YA) 

The T9840A, T9840B, T9840C, and T9840D drives use the same 9840 standard data 

cartridge. Therefore, you must take extra media management measures in the following 

situations: 

• T9840C drives co-exist in the same library system with T9840A/B drives 

• T9840D drives co-exist in the same library system with T9840A/B/C drives 

The extra measures essentially involve creation and management of separate media 

pools or sub pools for the following: 

• T9840A/B formatted/written data cartridges 

• T9840C formatted/written data cartridges 

• T9840D formatted/written data cartridges 

7831 0349–043 4–29


Compatibility 

Read a cartridge 

formatted by 

Write or append data 

to a cartridge 

formatted by 

Table 4–4. Cartridge Read/Write Capability 

Drive Model 

T9840A T9840B T9840C T9840D 

T9840A and 

T9840B 


T9840B 


T9840B 


T9840B 

T9840A, 

T9840B, and 

T9840C 

T9840A, 

T9840B, 

T9840C, and 

T9840D 

T9840C T9840D 

T9840A and T9840B tape drives cannot read from a data cartridge written by either 

T9840C or T9840D tape drive because of the higher-density formats. They must have 

the following appropriate drive firmware level to identify the higher-density data 

cartridges: 

• T9840A 

− R1.33.103 or higher to identify a T9840C written cartridge 

− R1.42.107 or higher to identify a T9840D written cartridge 

• T9840B 

− R1.33.303 or higher to identify a T9840C written cartridge 

− R1.42.307 or higher to identify a T9840D written cartridge 

• T9840C 

− RP.42.507 or higher to identify a T9840D written cartridge 

Without the appropriate drive firmware level, a T9840A or T9840B drive considers a 

higher-density formatted cartridge as blank and available for scratch. Therefore, attempts 

to read data from an identified higher-density data cartridge fails. 

The T9840C or T9840D tape drive can read data from a tape cartridge written by a 

T9840A or T9840B tape drive in the low-density format, but does not append data to that 

cartridge. An attempt to append a low-density data cartridge on a T9840C or T9840D 

drive fails, and sense byte data indicates an error (similar to that of a file-protected data 

cartridge). 

4–30 7831 0349–043

4.6.10. T10000A Tape Subsystem 


The T10000A (T10K) new capacity tape technology is an extension to the current 

StorageTek T9940B tape drives (single spool, serpentine cartridge) of Sun and 2.5 times 

the capacity of the T9940B. The maximum data capacity per cartridge supported by the 

T10000A is 500GB uncompressed compared to 200GB for the T9940B. (There is also a 

Sport cartridge available with 120GB, but currently there is no way to internally 

determine which is mounted on the drive.) The low density T10000A writes 768 tracks 

on a tape. The T10000A is four times faster than the T9940B. The new drive is designed 

to accept only a unique 2,805-foot half-inch cartridge tape (for standard T10000A) that 

contains T10000A specific servo information. Therefore, the tape should never be 

degaussed; it cannot be used once it has been degaussed unless the servo information 

is restored at the factory. 

The T10000A tape subsystem attaches to the ClearPath OS 2200 series systems using a 

SCSI Fibre (SCSI) channel interface. The T10000A tape subsystem can either be included 

in the STK tape libraries or in a standalone environment. Although the T10000A drive 

uses a half-inch cartridge tape, the T10000A tape is not interchangeable with the 

cartridge tape used by 18-track, 36-track, U9840, U9940, DLT, or LT03-HP/LTO4-HP tape 

drives or vice versa. The Exec provides unique equipment mnemonics for configuring the 

subsystem T10000A and a unique specific assignment mnemonic ‘T10KA’ for assigning 

tape files. Due to media incompatibility, any of the existing file assignment mnemonics 

that are available today for the half-inch cartridge tape assignment, except ‘T’ mnemonic, 

should not be used to assign a T10000A tape drive. 

The T10000A uses the existing CSC (Client System Component) library feature when 

included in the tape libraries. The tape device driver is supported within the Exec via the 

same handlers as its predecessors. Other features provided by the T10000A that are 

supported by the Exec include operator tape cleaning message, LZ1 data compression, 

fast tape access, and extended buffer mode. The T10000A is supported by the Exec as a 

boot device and system dump device. The T10000A can also be used for checkpoint and 

restart and may be used as an Audit Trail device. 

Checkpoint can assign the T10000A tape device using the new file assignment 

mnemonic ‘T10KA’ or using the generic file assignment mnemonic, ‘T’. Restart can 

assign the T10000A tape devices using the new file assignment mnemonic ‘T10KA’. 

LED display for the T10000A is not supported by the Exec due to the hardware 

limitation. The T10000A drive itself does not have an LED. However if you order a 

rack-mount device, the rack itself does include a display. There is no display for library 

drives; you must use Virtual Operator Panel (VOP) software to control the drive. 

7831 0349–043 4–31


4.6.11. T9840D and T10000A Applicable 

The T9840D and T10000A support AES256 encryption supported by the SUN Crypto Key 

Management Station (KMS). Currently all devices of a particular type must be encryption 

capable or have encryption disabled. 

The T9840D and T10000A tape devices are supported by all Dorado systems. 

BUFFIL (buffering of tape file marks) is supported by T9840D and T10000A. 

BUFTAP (Tape Mark Buffering Phase II) is supported by T9840D and T10000A . 

The Media Manager ILES (MMGR) and the Exec Media Manager code are modified to 

support the T9840D and T10000A tape devices. New bits are added in the TIF record 

and MMI work buffer to represent the T9840D and T10000A devices and the new 

density values. With the addition of the T9840D and T10000A, these devices make up 

the eighth and ninth media types (these types are, open-reel, 18/36-track, DLT, 

LTO3-HP/LTO4-HP, T9840A, CTS9940, U9840C, T9840D, and T10000A cartridge). The 

existing media is represented by open-reel, half-inch cartridge, T9840A, CTS9940B, 

U9840C, T9840D, DLT, LTO3-HP/LTO4-HP, and T10000A cartridge. This design 

addresses nine media types by having MMGR return different statuses for each media 

type when a media incompatibility is found. 

Table 4–5 provides a summary of the features that are supported within the Exec for 

T9840D and T10000A tape devices (Y=yes, the feature/capability is supported; N=no, 

the feature/capability is not supported; NA=not applicable, the feature/capability does not 

apply because it’s not supported by the vendor) 

Table 4–5. T9840D and T10000A Summary of Features 

Features/Capabilities Supported by the Exec Fibre T9840D Fibre T10000A 

LZ1 data compression y y 

Fast Tape Access y y 

Enhanced Statistical Information (ESI) logging (1) 

y (1216 log entry) y (1216 log entry) 

Expanded Buffer (256K bytes maximum) y y 

Enabling/Disabling buffered mode y y 

Audit Trail capable y y 

Auto-loader in AUTO mode na na 

Auto-loader in MANUAL mode na na 

Auto-loader in SYSTEM mode na na 

ACS library support y y 

Electrical Partitioning y y 

LED display y n 

Tape Mark Buffering (BUFFIL) y y 

4–32 7831 0349–043

Table 4–5. T9840D and T10000A Summary of Features 


Features/Capabilities Supported by the Exec Fibre T9840D Fibre T10000A 

Tape Mark Buffering Phase II (BUFTAP) y y 

Operator clean message y y 

Media manager support y y 

CKRS support y y 

1 Tape Alert Log Sense page is saved in the ESI log entry. 

4.6.12. T9940B Tape Subsystem 

T9940B tape subsystems connect to ClearPath systems server channels through Fibre 

Channel (FC) SCSI channels. T9940B tape subsystems are used in STK tape libraries. 

The T9940B uses the existing Client System Component (CSC) library feature when it is 

included in tape libraries (this version of CSC still uses the STK$ Executive request). The 

tape device driver is supported within the Exec through the SCSITIS separately packaged 

Exec feature when the T9940B attaches to the host through FCSCSI channels. 

T9940B tape subsystems provide a maximum capacity per cartridge of 200 GB of 

uncompressed data. The tape subsystems use the LZ1 data compression algorithm that 

can improve capacity by factors of 2 and greater. However, individual results might vary 

depending on characteristics of the data and other variables. 

The tape cartridges use half-inch tape. These cartridges are not interchangeable with 

cartridges used with 18-track, 36-track, DLT, T9840A, T9840B, or T9840C tape drives. 


unique specific assign mnemonic for assigning tape files. Other than generic assign 

mnemonic T, existing assign mnemonics used to assign 1/2-inch cartridge tapes cannot 

be used to assign T9940B tape drives. 

The Exec supports T9940B tape subsystems as boot devices, system dump devices, 

audit trail devices, and for checkpoint/restart. Checkpoint can assign T9940B tape 

devices with the new assign mnemonic HIS99B, or the more generic assign mnemonic 

T. Restart can assign T9940B tape devices with the new assign mnemonic, HIS99B. 

7831 0349–043 4–33


Considerations for using the T9940B tape subsystem are as follows: 

• Tape used by the T9940B has a native capacity of 200 GB. This is 120.5 times the 

capacity of an E-cart 1100-foot cartridge written in 36-track format. 

Cautions 

• Do not degauss 9940B tapes. Servo tracks are written on the tape at the 

factory. When these tracks are mistakenly erased, the tape cartridge 

must be discarded. 

• If you drop a 9940B tape cartridge from a height of less than 1 meter, the 

cartridge is warranted to continue to read and write new data, but the 

media life might be shortened. Therefore, Unisys recommends that you 

copy data from a dropped cartridge to another cartridge and retire the 

dropped cartridge. Because the compressed capacity could be 400 GB 

per cartridge or greater, the importance of protecting cartridges from 

being dropped cannot be overstated. 

• In order to crossboot to previous Exec levels that do not support a new device type, 

you must use a partitioned data bank (PDB) that does not contain the new device 

type. Products that are sensitive to new device equipment mnemonics and file 

assignment mnemonics can be affected. 



• T9940B tapes are not compatible with any other ClearPath system tape device. 

• T9940B tape subsystems cannot read traditional 9-track, 18-track, 36-track, DLT, or 

T9840A formatted tapes. To read these tapes and transfer the data to a T9940B tape 

subsystem, you must have a tape device on the host system that can read 9-track, 

18-track, 36-track, DLT, or T9840A/B formatted tapes. You can then transfer the data 

to the T9940B tape subsystem. 

• The function of general assign mnemonic T is expanded so that it can be used with 

T9940B tape subsystems. 

• Using ACS names as assign mnemonics is not supported for T9940B tape 

subsystems. You should use assign mnemonic HIS99B (or absolute device assign) 

when assigning T9940B tape drives. If an ACS name is specified in a tape 




bad. The operator clean message on the system console is also supported for the 

T9940B. When T9940B tape subsystems are part of a tape library, the Automated 

Cartridge System Library Software (ACSLS) should be set to autocleaning-enabled 

mode. This enables ACSLS and the library to perform the cleaning. 

4–34 7831 0349–043


• The following products or features are required to support T9940B tape subsystems: 

− Client System Component (CSC) library product supports the library 

configuration for T9940B tape subsystems. 

− SCSITIS separately packaged Exec feature must be installed in order to 

configure T9940B tape drives. 

− TeamQuest MSAR level 7R1A (or higher) and TeamQuest LA level 7R1 (or 

higher) are required to support the T9940B tape subsystem. 

• Sort/Merge consideration – A tape volume for T9940B tape subsystems can store up 



that tape files would fill tape volumes associated with the file. Based on that 


Because of the size of tape volumes for T9940B tape subsystems, the SORT 




assign appropriately sized scratch files before calling the SORT processor or passing 

a NUMREC or RECORD parameter to the SORT processor runstream. 

• Audit device consideration – There are no technical restrictions on using the T9940B 

tape subsystem as audit devices. However, there are some practical considerations. 

These devices have a much larger capacity than any current audit device. They will 

take a lot longer to fill than previous tapes. If filled, they will take a lot longer to read. 

Some recovery mechanisms are able to use block-ids of the fast tape access feature 

to reach the recovery start point in a reasonable timeframe. Other recovery 

mechanisms cannot use block-ids, and must read all the data on the tape to perform 

the recovery. If the tape is full, this might take more than a reasonable amount of 

time. 

Use the following considerations to minimize recovery time when using T9940B tape 

subsystems as audit devices: 

− Always set the IRU configuration parameter USE-LOCATE-BLOCK to TRUE. 

− Make sure the run-id executing recovery has Fast Tape Access privileges. 

− Remember that a long recovery from a TBSN or point in time will read each 

block from the beginning of the tape looking for the start point. A history file 

directed recovery following a reload is a recovery from a point in time. 

− Consider swapping tapes before they are full. You will have to balance the desire 

for most efficient use of tape (generally filling each tape) with the desire for 

speedy recoveries (which will be faster if you can skip reading data that is not 

required for recovery, but happens to reside on the same tape as the start point) 

to find the best solution for your application. 

7831 0349–043 4–35


4.6.13. CSC, ACSLS, and CARTLIB 

CSC and ACSLS Oracle, Inc. software products are orderable through your Unisys 

Representative. For information on how to download the CSC updates from the 

SunSolve web page, see PLE 18598086. 

CARTLIB is provided as a separately packaged keyed Exec feature. CARTLIB is included 

in the Integrated Operating Environment (IOE). 

You should review the CARTLIB User Guide and the CARTLIB Technical Bulletin 

distributed with the software release for details of any changes made to the software 

and the installation procedures. 

Operator Keyins 

The RC and FS keyins provide the following additional status concerning operations of 

the ACS: 

• The RC operator keyin returns an informational message when a run is temporarily 

held in an ACS query. 

• The FS,ATAPES and the FS,TAPES operator keyins show an ACS controlled tape 

drive status. 

Refer to the Exec Operations Reference Manual for more information. 

4.6.14. Software Delivery on DVD Media 

Capacity 

The ClearPath OS 2200 software for the Dorado Server systems is delivered on DVD 

media. 

A DVD is a high-capacity media used as a software release media. For example, a single 

sided DVD-R disc can store up to 3.95 GB or 4.7 GB of high-density data. Information on 

the DVD media is permanently recorded and cannot be altered or erased. 

The implementation emulates DVD as a tape device by using Windows 2000 file I/O to 

access DVD devices. The DVD is supported by the Exec as a single device/single control 

unit subsystem. DVDs are processed by the Exec as read-only simulated tapes. DVDs 

are supported as read-only devices and can be used to boot the system. 

Capacity of the DVD is 3.95 GB or 4.7 GB per disc, but due to the DVD mastering 

process, current DVD capacity is limited to 448,000,000 words (250,000 tracks) or 

approximately 2 GB per disc. 

4–36 7831 0349–043

Operator Interfaces 

The console keyins (UP, DN, RV, FS, and SU) that are available for current tape devices 

and that do not attempt write functions are available for the DVD. Since the DVD is 

supported as read-only media, console keyins that attempt to write to the DVD should 

not be used. Examples are SV, SB SBDEV, and SB IODEV where the device specified is 

a DVD. Errors can occur before a write is attempted to the DVD. 

DVD Mnemonics 

Table 4–6 describes the DVD assign mnemonics. The media type is 79. 

4.6.15. Virtual Tapes 

4.7. TIP 

Table 4–6. DVD Assign Mnemonics 

Assign Mnemonic CONV EQUATE Drive Allocated 

DVDTP None DVD 

Audit trails cannot be configured to use virtual tapes. VTH tapes exist in normal mass 

storage files that can be candidates for rollout. If these files get unloaded, the only valid 

copy of the data is on a physical tape. However, you cannot access the virtual tape 

directly from the physical tape on which it resides. To access the files, you must restore 

(in other words, ROLBAK) the virtual tape to mass storage. Be aware that if these virtual 

tapes contain backups such as IRU move or dump information, this increases the time it 

takes to recover an application group or file. When performance of a recovery or 

restoration is critical, the need to restore virtual tapes can cause an undesirable delay. 

This subsection describes TIP considerations. 

4.7.1. General 

• You should install the TIPUTIL level that corresponds with the target Exec level. 

Previous levels of TIPUTIL might not be compatible with the target Exec level. 

7831 0349–043 4–37 

TIP 

• TIPUTIL generations require the RLIB$ file which corresponds to the target Exec 

level. If you generate your TIPUTIL on the target Exec level, it will include the correct 

RLIB$ file. To prebuild your TIPUTIL system on your current system before migration 

to the target Exec level, use the RLIB$ SGS to specify the location of the target 

Exec’s RLIB$ file. For details on using the RLIB$ SGS, see “TIPUTIL Generation 

Control Statements” in the Exec System Software Installation and Configuration 

Guide.

TIP 

4.7.2. ClearPath OS 2200 Release 13.2 

A new TPM selection bit named “L$DLCK” is defined which, if enabled, will result in a 

new TPM log entry (type 015, subtype 011) being created if an FCSS deadlock condition 

occurs on the system. For more information regarding the FCSS Deadlock TPM Record, 

see Exec PLE 18853639. 


A new TIP FLAGBOX bit named “SUPURLOG” is defined which, if enabled, will result in 

commands processed by the TIP utility SUPUR being logged to the system log trail (log 

entry type 16005). The new log entries will identify the run (userid) that performed the 

SUPUR command, the SUPUR command and TIP/SUPUR file involved, the completion 

status of the SUPUR command, and SUPUR command output text. For more information 

about SUPUR command logging, see PLEs 18769981 and 18769999. 

The TIP utility FREIPS can now be used to identify (select and display) TIP files which 

have been designated by UDS as UDS controlled (UDSC) files. For more information 

about UDS controlled files, see PLEs 18784432 and 18785528. 

A new TIP Freespace dynamic configuration tag named “RLAUTO” is defined which, if 

enabled, will cause the period of time between Freespace deferred release processing 

executions (specified by the Freespace configuration tag “RLFQ”) to vary based on the 

volume of deferred releases being generated on the system. For more information about 

the Freespace “RLAUTO” configuration tag, see PLEs 18787288 and 18789698. 

TIP console (“TP”) keyins that display information based on transaction codes or names 

now allow the specification of an optional step control application group number. This 

limits the amount of system console output generated when information about a specific 

application group is desired. For more information about the new “TP” keyin field and its 

use, see PLE 18809371. 


A new TIP Freespace file attribute called FCL (FCode Locking) is defined. This attribute 

can be specified when a Freespace file is created (FREIPS CRE command) or 

dynamically via the FREIPS change (CHA) command. The default value of the FCL 

attribute is permitted (FCL=P) which causes FCSS locking of Freespace records to be 

performed as part of a released recoverable Freespace record’s FCODE (as was always 

done in previous EXEC levels). If the FCL attribute of a Freespace file is set to inhibited 

(FCL=I), no FCSS locking is done for recoverable Freespace records as part of the 

FCODE performed during deferred release processing. In XTC environments this avoids 

two trips to the XPC-L (lock/unlock) for each Freespace record FCODE which can 

substantially reduce the time and overhead required for Freespace deferred release 

processing on a system. 

For more information about the TIP Freespace file FCL attribute see PLE 18746573. 

4–38 7831 0349–043

7831 0349–043 4–39 

TIP 

A new TPM (TIP Performance Monitor) log entry is defined with a TPM collection 

bit/name of L$FSRL. If the L$FSRL collection bit is enabled on a system with TPM 

logging enabled, a new TPM system record type 015 subtype 010 is generated as part of 

Freespace deferred release processing. The L$FSRL TPM record contains information 

regarding the number of Freespace records processed and the amount of time required 

by the Freespace deferred release processing activity on the system. 

For more information about the TPM L$FSRL log entry see PLE 18755882. 


A new TIP VALTAB parameter is defined. The new optional TIME (TIM) TIP VALTAB 

parameter indicates the maximum wall clock time of a TIP transaction in seconds. If a 

nonzero VALTAB TIME parameter is specified for a TIP transaction and a copy of the 

transaction remains active on the system for more than the specified number of 

seconds, the default action is to display the following read-and-reply system console 

message: 

*TIP* Runid *xxxxxx (zzzzzz) exceeds maximum wall clock time. Abort? Y/N/D 

where 

*xxxxxx 

zzzzzz 

is the RUNID of the transaction 

is the corresponding transaction code 

The actions for the valid responses of “Y” (Yes), “N” (No) and “D” (Dump) are as 

follows: 

Y An “E” keyin will be performed to abort the transaction. 

N No attempt will be made to abort the transaction. No further 

checking/selection of this transaction copy will be performed. 

D An “E” keyin will be performed to abort the transaction. An attempt to 

obtain TIP diagnostic information will be made regardless of the current 

setting of the TIP FLAGBOX bit TIPTRACE on the system.

Software Controlled Performance (SCP) 

The following two new TIP FLAGBOX bits are defined that can be used to alter the 

default maximum wall clock time action described earlier: 

• MAXTIMENQ (bit 19) – If set, and a transaction copy exceeds its specified maximum 

wall clock time, an “E” keyin is immediately performed to abort the transaction. No 

read-and-reply (query) console message is generated. 

• MAXTIMEDP (bit 18) – If set, an EXEC dynamic online dump is generated prior to the 

aborting of a transaction copy that has exceeded its specified maximum wall clock 

time. The resulting EXEC online dump can provide additional diagnostic information 

(from a system view) to help determine the reason that the transaction copy 

exceeded its specified maximum wall clock time. 

For more information regarding the setting and operation of the VALTAB TIME 

parameter see PLEs 18646846 and 18675773. 


A new TIP VALTAB indicator option is defined to specify that a transaction is Java 

enabled. When this “V” indicator is defined (IND,V) it enables Java transactions to be 

loaded as RTPS and be successfully deactivated on an INITIAL call. 

The following restrictions apply: 

• Only the first or main Java user activity can be active at the time an INITAL call is 

made. 

• Only the first or main Java user activity can start a step. 

This option is not supported for non-Java TIP transactions. JVM Level 4R2 or higher 

must be installed to use this option. For more information on Java enabled TIP 

transactions, refer to EXEC PLE 18561590. 

4.8. Software Controlled Performance (SCP) 

The OS 2200 Software Controlled Performance (SCP) feature controls system 

performance for all supported systems for this release (see Section 1). All Instruction 

Processors in a reduced speed model are subjected to a forced idle loop delay that is 

spread evenly across all IPs. It might vary slightly for each IP, but it is accurate on a 

system-wide basis. All IPs populating the partition run at the same performance level. 

Note: For more information on SCP, refer to the Exec Administration Reference 

Manual. 

An Image Enabler is an SCP Exec key tape or file used for activating a performance 

image on a ClearPath server. 

4–40 7831 0349–043

MIPS-Based Image Enabler Key 


MIPS-based keys are for Dorado servers and specify the number of production MIPS 

partitionable between all partitions. The performance level for each partition is 

determined by the specific IPs used to provide the MIPS requested. The MIPS can be 

designated to a partition or moved between partitions. All normal keys are partitionable 

with a unique key-id so that the key can be used in more than one partition at the same 

time. 

MIPS-Metered Image Enabler Key 

MIPS-metered key support includes Dorado 330, 350, 390, 430, 750, 790, 850, 870, 890, 

4050, 4090, 4150, 4170, 4190, 4250, 4270, and 4290 servers. The pay-for-use “Prepaid 

Performance” key specifies baseline MIPS, ceiling MIPS, contract ID, recording period, 

and reporting period. Metering software monitors and reports MIPS use on a system 

image basis. 

4.8.1. Manufacturing Control Number Expansion 

On OS 2200 Systems, the Manufacturing Control Number (MCN) is used to identify and, 

optionally, control hardware and software belonging to or participating in a Unisys 

system. The MCN content changed to handle up to 16 characters. The MCN container is 

defined as 4 ASCII words, left justified and space filled. 

• For Dorado 4000, 4100, and 4200 Series systems, the MCN is the seven-character 

Dell Service tag. 

• For Dorado 300, 400, 700, and 800, Series systems, the MCN is the 9-digit Cell 0 

System Serial Number (SSN), left justified and space filled. 

4.8.2. PDB_MFG_CONTROL_NUMBER ER CONFIG$ Changes 

User programs can use ER CONFIG$ to read the expanded PDB MCN number from the 

dynamic parameter PDB_MFG_CONTROL_NUMBER. Word 3,,H2 of the ER CONFIG$ 

packet indicates how many words of data the Exec is requested to return (should be 4 

words). 

If a read request specifies a word count less than 4, the number of words requested is 

returned and the status of the request is 1. The value returned contains either 8 or 9 

digits followed by spaces. User programs should be written so that they do not fail if 

there is a warning status. A status greater than 0400000 is an error status. 

7831 0349–043 4–41

POSTOEXMSTR 

4.9. POSTOEXMSTR 

The POSTOEXMSTR utility is provided to position the package tape to the first file of the 

Exec release master files. This utility is included in the SOLAR installation file 

SYS$LIB$*SOLAR and in the LIB$ file on both the Exec Boot and Exec release master. 

The POSTOEXMSTR utility can be added to any runstream or process that needs to 

access the Exec release master files. 

To use the utility, place the name of a preassigned tape containing the Exec release 

master files on the utility call line, for example: 

or 

@ASG,TJ tape-file.,type,reel-num 

@SYS$LIB$*SOLAR.POSTOEXMSTR tape-file. 

@SYS$*LIB$.POSTOEXMSTR tape-file. 

Refer to the Exec System Software Installation and Configuration Guide for the Exec 

release master and the Exec symbolics format. 

4–42 7831 0349–043

Section 5 

OS 2200 Software Compatibility and 

Migration Considerations 

This section describes compatibility and migration considerations for OS 2200 software 

products. The products are listed in alphabetical order by product name. For your 

convenience, the product installation or support name is included in parentheses. 

If you are migrating from ClearPath OS 2200 13.1, refer to Table 5–1 for a summary of 

products in this release that introduce compatibility or migration issues. 

If you are migrating from ClearPath OS 2200 12.0, 12.1, or 13.0, please review this entire 

section carefully for information on compatibility and migration issues that may affect 

you. 

If you are migrating from a ClearPath OS 2200 11.x release, please refer to the ClearPath 

OS 2200 12.1 Software Planning and Migration Overview (7831 0349-040) document for 

information that is no longer included in this document. 

5.1. Summary of Considerations 

Table 5–1 summarizes the compatibility and migration consideration for sites migrating 

from ClearPath OS 2200 Release 13.1 to Release 13.2 and references the subsection 

that contains more information. 

Table 5–1. Summary of Considerations 

Installation and Support Name Type of Consideration Subsection 

CPCommOS Migration 5.8 

5.2. Business Information Server (BIS or MAPPER) 

Business Information Server (BIS) for ClearPath OS 2200 products continue to be 

available for ClearPath systems but are not released with the ClearPath system releases. 

Business Information Server Update Server Request (USR) letters will continue to be 

released announcing product content and availability dates for new releases. The current 

release information is available on the BIS corporate Web site: 

http://www.support.unisys.com/common/welcome.aspx?pla=MAP&nav=MAP 

7831 0349–043 5–1

CIFS 

5.3. CIFS 


Backward migration to a previous CIFS level is not recommended. 


CIFS Level 7R3 

Compatibility 

CIFS operation on Windows 7 without Service Pack 1 is unreliable; it is strongly 

recommended that SP1 be installed on any Windows 7 systems used in conjunction 

with 2200 CIFS. 


CIFS Level 7R1 

Migration 

The 24x7 feature consumes more disk space for the journaling files. The amount of 

increase is entirely site-dependent. Monitor on first use and plan accordingly. 

5.4. Cipher API 


Cipher API establishes the necessary internal control structures to manage cryptography 

services through the background run SYS$LIB$*RUN$.CIPHER. This run initializes the 

Cipher subsystem before the first application call, including detecting the presence of a 

hardware accelerator. 

If the Cipher subsystem is terminated, run SYS$LIB$*RUN$.CIPHER before using 

Cipher API again. If you are running a Fundamental Security system, you might receive 

the following error message: 

*ERROR* Security violation. Caller does not have 

sufficient privileges to deactivate the subsystem. 

In such a case, you can modify the runstream to assign SYS$*DLOC$ with the correct 

read and write keys before the following line: 

@SYS$LIB$*SOLAR.DEACT SYS$LIB$*CIPHER-API.SSDEF$CIPHER 

This gives the started run the necessary privilege that is required to make the 

Subsystem Deactivate call (SUBSYS$DEACT). 

5–2 7831 0349–043


Cipher API Level 2R2 

Compatibility 

Cipher API 

Cipher API 2R2 is fully compatible with data encrypted by previous levels. The FIPScertified 

algorithms used by Cipher API 2R2 are fully compatible with APIs supported in 

previous levels, so previously-encrypted data can be safely and accurately decrypted 

using this level of Cipher API. 

Cipher API encryption calls that use dynamic mode will use either hardware or software, 

whichever is faster for the specified algorithm, data format, and data size. The 

CIP2001-PCE encryption card available on the Dorado 800 through I/O Manager has 

different latency and speed compared with the CIP1001-PCX encryption card attached to 

an SIOP or SCIOP on other Dorado servers. Therefore, the ranges in which Cipher API 

uses hardware versus software encryption are different for the two cards. To derive 

maximum efficiency from Cipher API, the correct configuration file must be loaded. Use 

the new installation Mode B for servers having I/O Manager; using this mode 

automatically loads the correct configuration file for use with the CIP2001-PCE 

encryption card. If no encryption card is installed, the choice of Mode A or Mode B 

makes no difference, but by using Mode B on systems such as the Dorado 800 that 

support I/O Manager, you are prepared for adding a CIP2001-PCE card later without 

having to change the Cipher API configuration file. 

Migration 

The OS 2200 Cryptographic Library (CryptoLib) must be installed for Cipher API to run. 

Levels of Cipher API prior to 2R1 did not require CryptoLib. 


Cipher API Level 2R1 

Compatibility 

Cipher API 2R1 is fully compatible with data encrypted by previous levels. The 

FIPS-certified algorithms used by Cipher API 2R1 are fully compatible with the previous 

APIs, so previously-encrypted data can be safely and accurately decrypted using this 

level of Cipher API. 

The Initialization Vector (IV) that can be specified on the command line call in Cipher API 

2R1 is optional. Runstreams using the Cipher API 1R3A version of the command line will 

continue to work correctly with Cipher API 2R1. 

The new ("level 2") and old ("level 1") API calls are supported concurrently. But any 

particular program must use only one or the other set of APIs. Users of the new API calls 

are cautioned that if they provide their own Initialization Vector, they will not be able to 

decrypt the data using the older APIs. 

The OS 2200 Cryptographic Library (CryptoLib) must be installed for Cipher API 2R1 to 

run, even if the level 1 APIs are used. 

7831 0349–043 5–3

Checkpoint/Restart (CKRS) 

Migration 

The OS 2200 Cryptographic Library (CryptoLib) must be installed for Cipher API to run. 

Previous levels of Cipher API did not require CryptoLib. 


Java applications can access Cipher API by using the standard Java Cryptography 

Architecture (JCA) classes and interfaces. Cipher API handles cryptographic requests 

through a cryptographic service provider called UnisysJCE. 

In addition to the API and Java Cryptographic Service Provider support, Cipher API 

includes a command line utility for file encryption. 

5.5. Checkpoint/Restart (CKRS) 


• Because CKRS saves a particular environment and then restores that exact saved 

environment, any changes to the hardware or software environment (such as a 

change in mass storage device or installation of a new product level) between the 

taking of the checkpoint and the attempted restart might prevent successful restart. 

• For a successful restart, the Exec and CKRS product levels must be compatible 

(specifically, they must be from the same system release level). 

• A checkpoint and subsequent restart will be unpredictable if you change addresses 

or data in a common bank between the checkpoint and the restart. The linked 

(resolved) references in the program are no longer valid and the restarted program 

would refer to incorrect addresses and data. Also, a checkpoint request is not 

fulfilled and a fatal checkpoint error results if any write-enabled common banks are 

based at the time a checkpoint request is made. 

5.6. COMAPI 


• The security attributes for subsystem User-id, ACRs, and files are changed. The 

following attributes are required: 

− The clearance level attributes for COMAPI are minimum=0 and maximum=63. 

− The compartment set applies only to Security Level 2 or higher. 

− The value is access to ALL compartments, even if no compartments are defined. 

− Trusted privileges are SSBAFC, SSBYCOMP, SSBYPASSOWNR, and SSCCL. 

• If your application is designed to use socket function calls, you must include the 

library element SYS$LIB$*COMAPI$LIB.SOCKET$LIB in the link of your application. 

Refer to the COMAPI User Guide for more information. 

If you use a newer level of the socket library in your application and subsequently try 

to run on an older level of COMAPI, it will not work. You must re-link with the socket 

library that is installed for that level of COMAPI. 

Note: You can use old socket libraries with newer levels of COMAPI. 

5–4 7831 0349–043


COMAPI Level 7R3 

Migration 

COMAPI 

Beginning with ClearPath Release 13.1, COMAPI has two additional install modes: C and 

D. These additional modes offer the same functionality as modes A and B and give the 

user more flexibility for testing or running different system environments. 



Beginning with ClearPath Release 13.0, the LOG parameter on the ADMIN statement in 

the COMAPI configuration has been removed. Two new configuration statements have 

been created, the ENTITY statement and the LOG statement. See the COMAPI User’s 

Guide for more details on COMAPI configuration. 



Beginning with ClearPath Release 12.0, the KEYIN statement in the COMAPI 

configuration no longer exists. The information that used to be supplied on the KEYIN 

statement has been moved to the ADMIN statement. COMAPI 6R2 will reject a 

configuration element that still contains an old KEYIN statement. 

The ADMIN statement looks as follows: 

ADMIN [KEYIN,keyin-name] ; 

[LOG,{OFF | LOW | MEDIUM | HIGH}] ; 

[VERIFY-TERM-COMMANDS,{YES | NO}] 

The name of the COMAPI execution element has changed from BGRAPI to COMAPI. To 

execute COMAPI enter the following: 

@SYS$LIB$*COMAPI.COMAPI,options configuration-file.[element] 

The program Communications Application Server (CAS) was included with COMAPI 

5R5B and earlier releases but is no longer delivered with COMAPI. The same capabilities 

supplied by CAS are available with CITA. It is recommended that you use CITA as the 

replacement for CAS. Refer to the CITA Configuration and Operations Guide and PLE 

18572567 for information on configuring CITA to serve as the replacement for CAS. 

7831 0349–043 5–5

Communications Platform (CPComm) 

5.7. Communications Platform (CPComm) 


CPComm is not compatible with CPCommOS. CPComm contains code that removes 

CPCommOS, if it is found on a system, when CPComm is installed with SOLAR. 

• A ClearPath system must include supported communications hardware. 

• Microcode associated with all installed communications hardware must be installed 

with SOLAR before initializing CPComm. 

For several releases, it has been documented that the Runtime System for Extended 

Mode Compilers (URTS) should be installed when background products for other runs 

are not active. The Software Products Installation Guide contains product-specific 

considerations for various products, and this item is mentioned in association with URTS. 

Be aware that when you install a new level of URTS, it will affect all demand users and 

you will have to restart the background runs for CPComm and SILAS. 


CPComm Level 6R1 

Migration 

CPComm requires the new product CryptoLib. The CPComm build requires CryptoLib to 

be installed. If CryptoLib is not installed on your CP 13.0 system, CPComm terminates in 

error at initialization. 

5.8. Communications Platform for Open Systems 

(CPCommOS) 


CPCommOS is not compatible with either CPComm or CMS 1100. CPCommOS contains 

code that removes CPComm and CMS 1100, if they are found on a system, when 

CPCommOS is installed with SOLAR. 


If you have a Dorado 4200 system, there are no migration considerations for 

CPCommOS. If you have a Dorado 4100 or a Dorado 4000 system, ensure that you 

follow the considerations in the ClearPath OS 2200 Release 13.1 for CPCommOS as 

follows. 


If you have a Dorado 4100 system you must install Dorado 4100 Plateau 1.2 when 

migrating to the ClearPath OS 2200 13.1 release. See Table 3–8 for more information on 

the ClearPath 13.1 Dorado 4100 plateau dependencies. 

5–6 7831 0349–043

Communications Platform for Open Systems (CPCommOS) 

If you have a Dorado 4000 system and have moved to configuring your network 

interfaces in CPCommOS, you must install the Dorado 4000 Plateau 2.3 and ClearPath 

13.1 Dorado 4000 Compatibility Package when migrating to the ClearPath OS 2200 13.1 

release. See section 7.9 for more information on the ClearPath 13.1 Dorado 4000 

Compatibility Package. 

If you have a Dorado 4000 system and are migrating from ClearPath 12.0 or ClearPath 

12.1 and you have not yet moved to configuring your network interfaces in CPCommOS, 

perform the following migration steps: 

1. Prior to installing the ClearPath 13.1 OS 2200 software, Dorado 4000 Plateau 2.3 and 

the ClearPath 13.1 Dorado 4000 Compatibility Package, the following is 

recommended: 

a. Create your CPCommOS 4R2 configuration in an OS 2200 file. Refer to the 

Communications Platform for Open Systems Configuration and Operations 

Guide for a description of the new CPCommOS configuration statements. Refer 

to section 5.8.1 for a CPCommOS configuration example. This example is also 

provided in the second file of the CPCommOS release tape – element 

CONFIGSOURCE. For now, ignore the references to SLOT, DEVICE, and 

FUNCTION until you get to step 2. To determine what is currently configured on 

your system, go to the SAIL Control Center configuration and choose network 

and then network interfaces. You can look at the configuration you have 

previously supplied through SAIL Control Center if you want to create the same 

network configuration for CPCommOS 4R2. 

b. Select each network name (eth2, eth3, and so on) and copy this information to a 

spreadsheet or take a screenshot of each network interface parameter (Ctrl-Print 

Screen) and save to a text editor like Notepad. 

c. Delete all the CPCommOS interfaces using SAIL Control Center. 

2. From the OS 2200 Console View screen, set Jump Key 3 and $! the Partition. On the 

Server Management Control, deactivate the partition. 

3. Install Dorado 4000 Plateau 2.3 and the ClearPath 13.1 Dorado 4000 Compatibility 

Package (2.3-CP13.1-4000-COMPATIBILITY.sup). See Section 7.9 for more 

information on the ClearPath 13.1 Dorado 4000 Compatibility Package. You will 

notice in the SAIL Control Center that the first two icons under Network 

Configuration are different from the previous level. The icon, System Control LAN, 

allows you to establish a resilient bond of ETH0. The icon, OS2200 Interfaces, is 

helpful when creating your CPCommOS configuration. You must supply a SLOT, 

DEVICE, and FUNCTION for each configured network interface. Refer to the 

Communications Platform for Open System Configuration and Operations Guide for 

a description of the SLOT, DEVICE, and FUNCTION parameters on the 

NIC-INTERFACE configuration statement. 

a. Use this information to finish creating the CPCommOS configuration that was 

started in step 1(a). 

b. SAIL Control Center is still used to configure a resilient backup for the System 

Control LAN, configure DNS, and configure the SSL/TLS files. Perform this step, 

if it is applicable. 

4. On the Server Management Control, activate and start the partition. 

7831 0349–043 5–7


5. Install the ClearPath 13.1 OS 2200 software or in particular, CPCommOS 4R2 if you 

have not done so. Use the configuration that you created in the previous steps to 

initialize CPCommOS. 

Refer to Table 7–3 for more information on plateau dependencies. 

Migration 

CPCommOS Level 4R2 

A new installation mode for Communications Platform for Open Systems now updates 

the XNIOP software. Your system partition no longer needs to be restarted to use new 

XNIOP software. New XNIOP software is loaded into the SAIL environment using 

Communication Platform for Open Systems, where an automatic restart of XNIOP is 

initiated. You network is not available during the load. 


Beginning with ClearPath 13.0, you can no longer configure your network interfaces 

using SAIL Control Center. Network interfaces are configured as part of the CPCommOS 

configuration process. 

If you have a Dorado 4000 system and have moved to configuring your network 

interfaces in CPCommOS, you need to install the CP13.0COMPATIBILITY.sup when 

migrating to the ClearPath OS 2200 13.0 release. 

If you have a Dorado 4000 system and you did not move to configuring your network 

interfaces in CPCommOS in ClearPath 12.1, or you are migrating from ClearPath 12.0, 

perform the following migration steps: 

1. Prior to installing the CP13.0 OS 2200 software and the CP13.0COMPATIBILITY.sup, 

the following is recommended: 

a. Create your CPCommOS 4R1 configuration in an OS 2200 file. Refer to the 

Communications Platform for Open Systems Configuration and Operations 

Guide 3850 8032-004 for a description of the new CPCommOS configuration 

statements. Refer to section 5.8.1 for a CPCommOS configuration example. 

This example is also provided in the second file of the CPCommOS release 

tape – element CONFIGSOURCE. For now, ignore the references to SLOT, 

DEVICE and FUNCTION until you get to step 2. To determine what is currently 

configured on your system, go to the SAIL Control Center configuration and 

choose network and then network interfaces. You can look at the configuration 

you have previously supplied through SAIL Control Center if you want to create 

the same network configuration for CPCommOS 4R1. 

b. Select each network name (eth2, eth3, and so forth) and copy this information to 

a spreadsheet or take a screenshot of each network interface parameter 

(Ctrl-Print Screen) and save to a text editor like Note Pad. 

c. Delete all the CPCommOS interfaces using SAIL Control Center. 

5–8 7831 0349–043


2. Install the CP13.0COMPATIBILITY.sup. You will notice in the SAIL Control Center 

that the first two icons under Network Configuration are different from the previous 

level. The icon, System Control LAN, allows you to establish a resilient bond of 

ETH0. The icon, OS2200 Interfaces, is helpful when creating your CPCommOS 

configuration. You need to supply a SLOT, DEVICE and FUNCTION for each 

configured network interface. Refer to the Communications Platform for Open 

System Configuration and Operations Guide for a description of the SLOT, DEVICE, 

and FUNCTION parameters on the NIC-INTERFACE configuration statement. 



b. SAIL Control Center is still used to configure a resilient backup for the System 

Control LAN, configure DNS, and configure the SSL/TLS files. Perform this step, 

if it is applicable. 

3. From OS 2200 Console View screen, set Jump Key 3 and $! the Partition. On the 

Server Management Control, deactivate, activate, and start the partition. 

4. Install the CP 13.0 OS 2200 software or in particular, CPCommOS 4R1 if you have 

not done so. Use the configuration that you created in the previous steps to initialize 

CPCommOS. 

Refer to Table 7–3 for more information on plateau dependencies. 

CPCommOS Level 4R1 

Migration 

CPCommOS mode A no longer installs mode AFCB automatically. Refer to the 

Communications Platform for Open Systems Configuration and Operations Guide for 



CPCommOS Level 3R1A 

Migration 

Configuring the CPCommOS network interfaces is moved from SAIL Control Center 

Network to CPCommOS 3R1A in CP 12.1. Perform the following steps when migrating 

to ClearPath Release12.1 CPCommOS 3R1A: 

7831 0349–043 5–9


1. Prior to installing the optional portion of the Compatibility Package - 

2.1-CP12.1SAILCC-NET.sup, the following is recommended: 

a. Create your CPCommOS 3R1A configuration in an OS 2200 file. Refer to the 

Communications Platform for Open System Configuration and Operations Guide 

for a description of the new CPCommOS configuration statements. A 

configuration example is also provided in the second file of the CPCommOS 

release tape, element CONFIGSOURCE. For now, ignore the references to 

SLOT, DEVICE, and FUNCTION until you get to step 2. To determine what is 

currently configured on your system, go to SAILCC configuration and choose 

network and then network interfaces. You can look at the configuration you have 

previously supplied through SAILCC if you want to create the same network 

configuration for CPCommOS 3R1A. 

b. Select each network name (eth2, eth3, and so forth) and copy this information to 

a spreadsheet or take a screenshot of each network interface parameter 

(Ctrl+Print Screen) and save to a text editor like Note Pad. 

c. Delete all the CPCommOS interfaces using SAILCC. 

2. Install the optional portion of the Compatibility Package- 2.1-CP12.1SAILCC-NET.sup. 

Refer to “Migration for Dorado 4000” in Section 7 for more information on the 

Compatibility Package. You will notice that the first two icons are different from the 

previous level. The icon, System Control LAN, allows you to establish a resilient 

bond of ETH0. The icon, OS2200 Interfaces, is helpful when creating your 

CPCommOS configuration. You need to supply a SLOT, DEVICE, and FUNCTION for 

each configured network interface. Refer to the Communications Platform for Open 

System Configuration and Operations Guide for a description of the SLOT, DEVICE, 

and FUNCTION parameters on the NIC-INTERFACE configuration statement. 



b. SAILCC-NET is still used to configure a resilient backup for the System Control 

LAN, configure DNS, and configure the SSL/TLS files. Perform this step, if it is 

applicable. 

3. From OS 2200 Console View screen, set Jump Key 3 and $! the Partition. On the 

Server Management Control, deactivate, activate, and start the partition. 

4. Install the ClearPath OS 2200 12.1 software or in particular, CPCommOS 3R1A. Use 

the configuration that you created in the previous steps to initialize CPCommOS. 

You can choose to delay migrating to the new configuration process in CPCommOS 

3R1A and still upgrade your CPCommOS to 3R1A. In this case, you need to remain on 

the existing version of SAILCC-NET, that is, do not install the optional portion of the 

Compatibility Package - 2.1-CP12.1SAILCC-NET.sup. Continue to configure your network 

interfaces through SAILCC-NET and DO NOT configure these network interfaces in the 

CPCommOS configuration. You must be using the new CPCommOS configuration 

process to configure your network interfaces by CP 13.0. 

5–10 7831 0349–043

Installation Considerations 


Prior to ClearPath OS 2200 Release 12.1, CPCommOS provided one CMS to 

CPCommOS migration mode (CMSA-CPCA), which was automatically installed with 

CPCommOS mode A. CPCommOS now provides the same CMS to CPCommOS 

migration modes as CPComm; CMSA-CPCA, CMSA-CPCB, CMSA-CPCC, CMSA-CPCD, 

CMSA-CPCE, CMSA-CPCF, CMSA-CPCG, CMSA-CPCH, CMSTEST-CPCA, 

CMSTEST-CPCB, CMSTEST-CPCC, CMSTEST-CPCD, CMSTEST-CPCE, 

CMSTEST-CPCF, CMSTEST-CPCG, CMSTEST-CPCH. If a product you use requires a 

CMS to CPCommOS migration mode, you must install that CPCommOS mode in 

addition to Mode A of CPCommOS. 

5.8.1. CPCommOS Example IPv4/IPv6 Configuration 

This CPCommOS configuration is an example and must be edited to add your site 

specific configuration information. The example contains both IPv4 and IPv6 addresses. 

Refer to the Communications Platform for Open Systems Configuration and Operations 

Guide for more information on the configuration statements. 

You must change - 

1. The IP address on the ADMIN statement DEFAULT-IP-ADDRESSES parameter to 

your IP address. 

2. The SLOT, DEVICE and FUNCTION parameters on the NIC-INTERFACE statement. 

This information is obtained from the SAILCC-NET OS2200 Interfaces page. 

3. The IP address on the IPV4-ADDRESS statement to your IP address. 

4. The IP address on the IPV4-ROUTER statement to your router IP address. 

5. The ID field on the IPV6 statement to your IP address id. The IPV6 statement is only 

specified when using IPv6 addresses. 

6. The PREFIX field on the ZONE-INFO statement to your IP address prefix. In most 

cases the prefix is acquired dynamically from an IPv6 router and a ZONE-INFO 

statement is not needed. The PREFIX statement is only specified when using IPv6 

addresses. 

7831 0349–043 5–11


7. The IPV6 and V6-INHERIT-V4 fields on the PROCESS statement are only specified 

when using IPv6 addresses. 

ADMIN CONFIG-NAME,CPCOMM1 ; 

PRIVILEGED-USERIDS,EVERYONE ; 

TRACE,MEDIUM ; 

VERIFY-TERM-COMMANDS,NO ; 

DEFAULT-IP-ADDRESSES,10.1.1.1 ; (1) 

DEFAULT-LOOPBACK-ADDRESSES,127.0.0.1 ; 

KEYIN-NAME,CPCOMM 

CA,N00000 

NIC-INTERFACE,ETH2 SLOT,0 ; (2) 

DEVICE,0 ; (2) 

FUNCTION,0 ; (2) 

IPV4-ADDRESS,ADR1 ; 

IPV4-ROUTER,RTR1 

IPV4-ADDRESS,ADR1 IP-ADDRESSES,10.1.1.1 (3) 

IPV4-ROUTER,RTR1 IP-ADDRESSES,10.1.1.2 (4) 

IPV6,ADR2 NIC-INTERFACE,ETH2 ; (5) 

ID,::0.16.0.16 

ZONE-INFO,ZONE1 NIC-INTERFACE,ETH2 ; (6) 

PREFIX,1234:: 

PROCESS,CPFTP PASSWORD,CPFTP IPV6,ADR2 V6-INHERIT-V4,YES (7) 

PROCESS,COMAPI PASSWORD,COMAPI IPV6,ADR2 V6-INHERIT-V4,YES 

PROCESS,SECOM PASSWORD,SNMP IPV6,ADR2 V6-INHERIT-V4,YES 

PROCESS,WEBTSCPC PASSWORD,WECTSCPC IPV6,ADR2 V6-INHERIT-V4,YES 

****** Silas process statements ********* 

PROCESS,TP0TIP PASSWORD,TIP T-SELECTORS,’TP0TIP’,’TIPCSU’ ; 

IPV6,ADR2 V6-INHERIT-V4,YES 

PROCESS,TP0RSI PASSWORD,RSI T-SELECTORS,’TP0RSI’,’RSDCSU’ ; 


PROCESS,TP0CSA PASSWORD,CSA T-SELECTORS,’TP0CSA’ ; 


PROCESS,TELTIP PASSWORD,TIP IPV6,ADR2 V6-INHERIT-V4,YES 

PROCESS,TELRSI PASSWORD,RSI IPV6,ADR2 V6-INHERIT-V4,YES 

5–12 7831 0349–043

5.9. COMUS 

COMUS 

COMUS is used to build products. Although COMUS installation functionality is still 

supported in the current release, SOLAR has replaced COMUS as the installation tool for 

all products. 


• COMUS supports keyed product generation and keyed product installation. 

• COMUS supports compressed and uncompressed 1/2-inch cartridge tapes. The 

COMUS commands that accept and support 1/2-inch tape compression values are 

INSTALL, REGISTER, and BUILD. 

• Products installed with SOLAR do not update the COMUS database. Be sure to use 

SOLAR reports to list the installed levels of these products, rather than the COMUS 

system installation logs. 

• Continue to use COMUS to build all symbolic products. Build information for 

products installed with SOLAR is contained in an ASCII file for each product on the 

package tape for that product. 

• The LIBSAVE and LIBLOAD runstreams are no longer released with COMUS. The 

runstreams are included with SOLAR, and will continue to be released in 

SYS$*RUN$ on the Exec boot tape. 

• The use of large program files (LPF) to build products is restricted. 

• Do not specify the maintenance update levels of products in BUILD commands (for 

example, use xR1 instead of xR1A). 

• If you have any local or third-party products that are COMUS installable, consider the 

following: 

− COMUS does not support initiation of installation runstreams in demand mode 

with the @ADD statement. You can either start the runstream during the install 

session or enter the @START statement to initiate the runstreams. 

− If there is a cycle limit on SYS$*DATA$, SYS$LIB$*RUN$, or 

SYS$LIB$*PROC$, your installation might fail. COMUS and SOLAR create a +1 

cycle of these files, which could cause a mass storage hold (M-hold) if the cycle 

number tries to exceed the maximum. You are advised not to use cycle limits for 

these files. 

Refer to the COMUS End Use Reference Manual for detailed information regarding 

product generation with COMUS. 


COMUS Level 6R9 

Compatibility 

The following products either use the standard build routine (CB$STD$BUILD) provided 

by COMUS and standard build skeletons (SKL-LDSVCTRL and SKL-LOADSAVE) or have 

updated their product-specific build routines and skeletons in Release 12.0. These 

products fully support the COMUS buffered-write and pool-id feature for the BUILD 

command. 

7831 0349–043 5–13

COMUS 

ACOB IRU PADS SIMAN UCOB 

COMUS LA PAR SORT UDSC 

CULL LINK PCIOS SSG UREP 

DMS LSS QLP TIPUTIL URTS 

Exec MSAR RDMS UC 

The following products have their own product-specific build routine which has not been 

updated in release 12.0, but they do call COMUS-provided standard build subroutines 

(CB$OPTTAPE, CB$REQTAPE, CB$SGS, CB$LDSVCTRL, and CB$SAVE) to solicit for 

tape input and assign tapes. These products support the COMUS buffered-write and 

pool-id feature for the BUILD command, provided the tape assign image produced does 

not exceed 80 characters and the SGS image produced does not exceed 96 characters. 

CKRS DFP FURPUR MASM PMD 

CMR DMPLIB HTPIC-2200 MRI* RSS 

CPFTP ELMS IPF OSAM SFS 

DDP-FJT ELT LIST OSI-TP TAS 

DDP-PPC FAS MAP PDP UCSRTS 

Note: For temporary tapes and cataloged input tapes, COMUS appends “. ASG 

IMAGE” to the tape assign image which counts towards the image length. 

The following products have their own product-specific build routine that either solicit for 

or build their own, mostly print, tape assign images. These products have not updated 

their build routine for release 12.0 and, therefore, do not support the COMUS bufferedwrite 

and pool-id feature for the BUILD command. 

CITA CPComm DPS MCB SYSLIB 

CML CPCommOS FTN MAPPER* TRAM* 

COMAPI CSC* GSA SILAS UFTN 

Notes: 

• Except CML and CSC which create their own NEWMASTER tape assign image, 

buffered-write and pool-id parameters can be specified for the output master tape for 

these products provided the assign image produced does not exceed 80 characters 

and the SGS image produced does not exceed 96 characters. 

• See PLE 18462915 for methods of specifying unsupported tape assignment 

parameters during the BUILD command for these products. 

• All other OS 2200 products are released in nonsymbolic format and do not use the 

COMUS BUILD command. 

• *Denotes asynchronously released products not included in release 12.0. 

5–14 7831 0349–043

5.10. cpFTP 


cpFTP 

When you install cpFTP, the cpFTP master runstream is overwritten during installation. 

If you change the original runstream, you should reapply it after installation 


cpFTP Level 3R5A 

Compatibility 

cpFTP 3R5A refuses the PORT command that specifies IP address different from the 

client. The purpose of this is to avoid the vulnerability. Therefore, the following 

commands may become an error: 

• proxy put filea fileb (The client might be a client of the other party) 

• proxy get filea fileb (The client might be a client of the other party) 

• transfer hosta::filea,hostb::fileb (Proxy transfer between remote hosts) 

See PLE 18852608 for additional information. 


cpFTP Level 3R5 

Compatibility 

The record format of cpFTP transfer history log is changed. If you have a program that 

reads cpFTP transfer history log directly, it should be modified. 


cpFTP Level 3R4 

Compatibility 

• The default TSU mode is changed to CPComm mode A from CMS mode A when 

TSUNAME and CPTSUNAME are not specified to the cpFTP background run. The 

default TSU mode of the previous version was CMS mode A. Therefore, the 

TSUNAME parameter should be specified when CMS mode A is used. 

• The message format of LIST console command is changed. 

• The edited transfer history list format of the CPFTPLOG program is changed. 

• A user program that uses the cpFTP API should be re-linked. 

• cpFTP 3R4 now requires that the owner user ID associated with the Fixed Gate 

Subsystem for cpFTP (usually -FTP-SUBSYS-) be updated to have the 

SUBSYS$DEACT security interface. 

7831 0349–043 5–15

DMS-RA 

5.11. DMS-RA 


DMS-RA Level 4.0 

Compatibility 

DMS-RA 4.0 requires use of a Java 1.5 (Java 5) or higher Runtime Environment. 

A subschema that is used to provide Java access to DMS data must be processed with 

the ClearPath 12.0 version of the SDDL processor, DMS 20R2, or above, to be 

compatible with DMS Resource Adapter 3.1. 



Compatibility 

DMS-RA 3.1 requires use of a Java 1.5 (Java 5) or higher Runtime Environment. 


the ClearPath 12.0 version of the SDDL processor, DMS 20R2, or above, to be 

compatible with DMS Resource Adapter 3.1. 



Compatibility 

DMS-RA 3.0 requires use of a 1.5 (Java 5) or higher Runtime Environment. 


the ClearPath 12.0 version of the SDDL processor, DMS 20R2 or higher to be compatible 

with DMS Resource Adapter 3.0. Custom classes generated with a previous version of 

the Class Builder utility are not compatible with DMS Resource Adapter 3.0. 



Compatibility 

DMS-RA 2.0 requires the ClearPath12.0 levels of OpenDTP and JBoss. 

Migration 

Java subschemas must be recompiled and the custom classes rebuilt as a result of the 

enhanced version checking feature. 

5–16 7831 0349–043

5.12. DPS 


DPS Level 6R5A 

Compatibility 

DPS 

When using a version of DPS 6R5A, users must generate new CONNECTER working 

storage/message format for every DPS screen previously generated and used with DPS 

6R5, and import the resulting COBOL structures into their ePortal Developer projects 

using the import wizard. Otherwise, a mismatch with the message/record format results 

in the DPS run-time system generating errors on transaction input, or ePortal receiving 

unrecognizable data on transaction output. 

CONNECTOR working storage/message format for DPS 6R5A now contains data fields 

for DPS screen number, DPS screen name, DPS form library filename, CONNECTOR 

working storage version number (1), and selected DPS screen control information. 


DPS Level 6R5 

Compatibility 

For DPS Level 6R5, when you define or use a field for use with ePortal/TIP Connector 

terminal type, only the A, C, I, L, N, O, X, and S minor field types are supported. The B, 

D, and R minor field types are restricted. Using B, D, and R minor field types in your DPS 

form for use with ePortal/TIP Connector yields unpredictable results. 

For DPS Level 6R5, the messages transmitted between ePortal and the TIP/DPS 

transactions have an additional 8-character field preceding the entire message. This field 

contains the DPS screen name, which is used by ePortal as the discriminator field. 

Transactions or Initial Control Programs (ICPs) which may intercept the transaction input 

message prior to being processed by the DPS run-time system must be cognizant of the 

new field. 

5.13. Distributed Data Processing File and Job 

Transfer (DDP-FJT) 


• You must install DDP-PPC before you build or execute DDP-FJT. 

• You must install I18NLIB to execute DDP-FJT. This is necessary because DDP-FJT 

uses ELMS, which, in turn, requires I18NLIB. 

• The Print Driver and Print Manager components of DDP-FJT are no longer supported 

because PERCON has been discontinued. 

• DDP-FJT background runs error on a system running Fundamental Security 

(SENTRY=0). 

• DDP-FJT requires that IRU be installed with mode FSAH or ALTFSAH. 

7831 0349–043 5–17

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

Refer to the SYS$LIB$*DDP-FJT-3.README element for additional release 

documentation. 

5.14. Distributed Data Processing 

Program-to-Program Communications 

(DDP-PPC) 

This subsection describes the considerations for DDP-PPC. Refer to the DDP-PPC 

Implementation and Administration Guide before installing DDP-PPC. 


You must install I18NLIB before you execute DDP-PPC. This is necessary because 

DDP-PPC uses ELMS, which in turn, requires I18NLIB. 

DDP-PPC starts a run named BNKLST when the PPCMASTER detects that the DDP-PPC 

subsystem has been deactivated since the last execution of the PPCMASTER. This run 

is used to obtain BDI information for the current execution of the PPCMASTER 

subsystem. It writes the information into a file named SYS$LIB$*DDP$BNKLIST. Once 

the information is obtained, the run terminates, usually after about 5 minutes. The dump 

routines then read this file whenever a DDP-PPC dump is taken. You should make sure 

the SYS$LIB$*DDP$BNKLIST file is secured. 

Because DDP-PPC executes as a fixed-gate subsystem, the files containing the 

subsystem (SYS$LIB$*PPC$$GATES) must be owned by a user-id that has fixed-gate 

subsystem privileges at shell level and can deactivate the subsystem. 

You can change the file ownership through the security management product after 

completing the DDP-PPC installation. Refer to the DDP-PPC Implementation and 

Administration Guide for more information about user-id requirements for running 

DDP-PPC. 

The SYS$LIB$*PPC$$GATES.SSD element determines the security (ring level) of the 

DDP-PPC subsystem. For Fundamental Security environments it executes at the 

TRUSTED level, for all others it executes at the SHELL level. 

DDP-PPC determines the security level of the system during the SOLAR installation 

process and loads the appropriate version of the SSD element. If you change security 

levels after installing DDP-PPC, you can either reinstall DDP-PPC or copy the appropriate 

SSD element with the following commands: 

• To go from a FUNDAMENTAL level to a SECOPT 1, 2, or 3 level, enter 

@COPY,A SYS$LIB$*PPC$$GATES.SSD/SHELL,SYS$LIB$*PPC$$GATES.SSD 

• To go from a SECOPT 1, 2, or 3 level to a FUNDAMENTAL level, enter 

@COPY,A SYS$LIB$*PPC$$GATES.SSD/TRUSTED,SYS$LIB$*PPC$$GATES.SSD 

5–18 7831 0349–043

ECLIPSE-2200 

• If you are running Fundamental Security and you are installing DDP-PPC from a 

Fast-Load tape, you must enter 

@COPY,A SYS$LIB$*PPC$$GATES.SSD/TRUSTED,SYS$LIB$*PPC$$GATES.SSD 

To perform the copy commands, you must have read and write privileges for the 

SYS$LIB$*PPC$$GATES file. 


Compatibility 

• IPV6 addresses are not supported with CMS 

• The CPMODE keyword in the OSITSU and TASTSU records must have the same 


• The default value for the CPMODE keyword has changed from CMSA to 



• DDP-PPC 7R3 requires the CPComm level to be 6R1 or higher. 

• DDP-PPC 7R3 requires the CPCommOS level to be 4R1 or higher. 

Migration 

• The CPMODE keyword in the OSITSU and TASTSU records must have the same 


• The default value for the CPMODE keyword has changed from CMSA to 



• DDP-PPC 7R3 requires the CPComm level to be 6R1 or higher. 

• DDP-PPC 7R3 requires the CPCommOS level to be 4R1 or higher. 

5.15. ECLIPSE-2200 


ECLIPSE Level 3.6 

Compatibility 

Projects created with the previous level will work with the new level with no 

modifications. 


ECLIPSE Level 3.5 

Compatibility 

The new version of the PADS library that comes with the ClearPath OS 2200 12.1 will 

need to be installed along with the new version of ECLIPSE-2200. 

7831 0349–043 5–19

ELMS 

5.16. ELMS 

The consideration for ELMS is that you must install I18NLIB before you attempt to use 

ELMS. 

5.17. Enterprise Output Manager (EOM) 


EOM Level 9.1 

Compatibility 

The fixes identified by the following PLEs have to be applied for configuring SSL/TLS 

with OS 2200 Output Manager component on OS 2200 releases prior to ClearPath 13.0 

(CPComm 6R1): 

• PLE 18746921 

• PLE 18753995 

Migration 

A continuation of Enterprise Output Manager 9.0; all prior levels of Output Manager can 

be migrated to Output Manager 9.1. 


EOM Level 9.0 

Compatibility 

OS 2200 Output Manager level 7.0 and higher are compatible with the Windows Output 

Manager level 9.0 component. Similarly, the Windows Output Manager level 7.0 and 

higher is compatible with the OS 2200 Output Manager level 9.0 component. Refer to 

the Enterprise Output Manager Help for specific details relating to OS 2200 operations. 

This release of Windows Enterprise Output Manager is a feature release and additionally 

includes fixes to problems reported since release level 8.1. 

For configuring SSL/TLS with OS 2200 Output Manager component on OS 2200 

releases prior to ClearPath 13.0 (CPComm 6R1), the fixes identified by following PLEs 

have to be applied: 

• PLE 18746921 

• PLE 18753995 

Migration 

This is a continuation of Enterprise Output Manager 8.1. All prior levels of Output 

Manager can be migrated to Output Manager 9.0; however, level 9.0 will automatically 

upgrade only levels 8.1, 8.0, 7.1, and 7.0. To migrate Output Manager 6.1 and earlier 

levels to 9.0, you must use the configuration import functionality to complete the 

migration. 

5–20 7831 0349–043


EOM Level 8.1 

Compatibility 

Enterprise Output Manager (EOM) 

There are no changes to the OS 2200 Output Manger Component. OS 2200 Output 

Manager level 7.0 and higher are compatible with the Windows Output Manager level 

8.1 component. Similarly, the Windows Output Manager level 7.0 and higher are 

compatible with the OS 2200 Output Manager level 8.1 component. Refer to the 

Enterprise Output Manager Help for specific details relating to OS 2200 operations. 


includes fixes to problems reported since release level 8.0. 

Migration 



upgrade only levels 8.0, 7.1, and 7.0. To migrate Output Manager 6.1 and earlier levels to 

8.1, you must use the configuration import functionality to complete the migration. 


EOM Level 8.0 

Compatibility 

There are minor changes to the OS 2200 Output Manager component. OS 2200 Output 

Manager level 7.0 and higher are compatible with the Windows Output Manager level 

8.0 component. Similarly, Windows Output Manager level 7.0 and higher are compatible 

with the OS 2200 Output Manager component. Refer to the Enterprise Output Manager 

Help for specific details relating to OS 2200 operations. 


includes fixes to problems reported since Release 7.1. 

Migration 



upgrade only levels 7.1, 7.0, 6.1 and 6.0. To migrate Output Manager levels 5R2 and 

older to level 8.0, you must use the configuration import functionality to complete the 

migration. 


The OS 2200 absolute-only boot tapes contain new required Station Local statements 

that define print queues for DEPCON. 

7831 0349–043 5–21

Enterprise Network Database Server (DMS) 

5.18. Enterprise Network Database Server (DMS) 


Existing lower level DML program absolutes do not need to be modified, compiled, or 

recollected/relinked. Databases do not require any modification or unloading/reloading. 


DMS Level 21R1 

Compatibility 

URTS 13R1B, 13R2, or greater must be installed before executing UCS DMS programs. 

Migration 

Code in the UDS$DMRICR that was capable of supporting access to UCS DMS 

programs is no longer included. Each application group must now have the appropriate 

UDS$DMRSHELL and UDS$DMRICR for the particular level being used. 



Compatibility 

Previously, code from the DMRTRACE procedure was controlled by a switch and was 

turned on by doing a DMS build. Output from the DMRTRACE was written to the print 

file for the run. The DMRTRACE procedure is removed from the DMR and replaced with 

the UDSC trace mechanism. 



Migration 

Java subschemas need to be recompiled, and the custom classes rebuilt as a result of 

the enhanced version checking feature. 

5–22 7831 0349–043

Enterprise Relational Database Server (RDMS) 

5.19. Enterprise Relational Database Server (RDMS) 


RDMS Level 17R2 

Migration 

The format of the section (the internal data structure that represents the SQL statement) 

was enhanced in RDMS 16R2 (CP12.1). Programs compiled on earlier levels will execute 

on RDMS level 16R2 and later levels, however, extra CPU is required to convert from the 

old format to the new format. For best performance: 

• Recompile all COBOL and C programs that contain static Embedded SQL. 

• Recreate all Stored Procedures and triggers. 

This performance consideration was not documented in the ClearPath Software Planning 

and Migration Overview in Releases 12.1 or 13.0, so some sites may not have 

recompiled their programs nor recreated their stored procedures and triggers after the 

installation of RDMS levels 16R2 or 17R1. Such sites may wish to perform that action 

after the installation of RDMS 17R2. 


• Lower level Relational Database Server databases are upwardly compatible with 

higher-level databases. You do not have to recompile or recollect user programs to 

modify the database or to unload or load data. 

• Most existing user programs run without modification. The main exception to this 

principle is the addition of certain reserved words. (Refer to the items in this section 

that discuss reserved words.) 

• The RSA component of Relational Database Server software is tightly coupled with 

the rest of Relational Database Server software. The level of the RSA component 

must match the Relational Database Server level. For example, RSA level 17R1 must 

be used with Relational Database Server level 17R1. (The RSA component is 

installed in a separate file from the rest of Relational Database Server. You can use 

the RSA for any application group to connect with a Relational Database Server in a 

different application group as long as this rule is strictly observed.) 



Migration 

If you fall back to an earlier level of RDMS: 

• Tables containing in-record BLOBs will not be accessible 

• Programs containing the new multi-column predicates will not execute. 

7831 0349–043 5–23

Enterprise Relational Database Server (RDMS) 



Migration 

Programs that contain static or dynamic ESQL, and are compiled with RDMS level 16R2 

cannot be executed by earlier levels of RDMS. Programs compiled with earlier levels of 

RDMS can be executed by RDMS level 16R2. 



Compatibility 

DEFAULT, an RDMS keyword, becomes an RDMS reserved word. This means that 

DEFAULT can no longer be used as a column or table name. Programs that reference 

DEFAULT as a table or column name must be changed to reference that table or column 

as “DEFAULT”. Alternatively, the column can be renamed using the ALTER TABLE 

RENAME COLUMN statement. EXPRESSION - columns by name EXPRESSION cannot 

be dropped unless they are presented as delimited identifiers. IDENTITY - columns by 

name IDENTITY cannot be dropped unless they are presented as delimited identifiers. 

With prior levels, when the GATHER STATISTICS command of the RDMUTL processor 

was executed, the statistics gathered by that command immediately replaced any 

existing statistics being used by RDMS. In this new level, new statistics will not be used 

until there are no threads accessing the table involved (informational message 3020 will 

be issued). In the RDMS.STATS system table, the column avg_rec_size is no longer 

maintained by the RUN STATISTICS command of the RDMUTL processor. Query 

optimization does not use this column. 

Column pct_page_full now contains the number of pages in the corresponding index 

when statistics are gathered with this level or later. 

Statistics can no longer be collected for columns which have a character set with a 

collation specification. Attempting to do this results in RDM error 27140. 

Programs explicitly referencing AUTHTABLE, to determine whether or not a given user is 

authorized to access tables, will not return the "correct" result once the site begins to use 

role security. References to AUTHTABLE should be replaced with references to one of 

the RDMS catalog views. 

Migration 

When using IDENTITY or GENERATED expression RDMS attempts to precondition the 

data and index pages to improve concurrency and reduce deadlocks. During 

preconditioning, when RDMS potentially creates new data and/or index pages or uses 

existing pages from the free chain there may be an additional requirement for page bank 

space. You should consider increasing page bank space so that all new/existing pages 

used during preconditioning can be accommodated in memory; otherwise, 

preconditioning may not be effective or possible. 

5–24 7831 0349–043

FURPUR 

Two new RDMS system tables are created within the schema RDMS. These tables are 

ROLEMEMBERSHIP and ROLES. If the site has tables by this name, those tables will 

need to be renamed before the RDMS install. 

Grants performed with RDMS 2R1 will no longer be effective. Execution by a user who 

was granted privileges in RDMS 2R1 will fail with a security violation. The granter must 

reissue the GRANT statement in order to enable access. 

5.20. FURPUR 


FURPUR Level 32R5 

Compatibility 

If the N option was included on the @PRT,T statement for FURPUR 32R4 and previous 

levels it was ignored with no user notification. @PRT,TN produced the normal long 

format element listing for batch runs and the normal short format element listing for 

demand runs. 

With FURPUR 32R5 the N option now specifies that only summary information should 

be produced. No element information is output when the N option is specified. 

The following deleted summary information lines produced by the @PRT,T statement for 

FURPUR 32R4 and previous levels have been modified. 

*THIS FILE CONTAINS DELETED TEXT TOTALING TRACKS 

*PLEASE PACK FILE 

If you use a text editing tool to search print files for these messages, they will no longer 

be found with FURPUR 32R5. For the new format of these messages, refer to Deleted 

Element Summary Information in Section 7.48.3 of the ClearPath OS 2200 Executive 

Control Language (ECL) and FURPUR Reference Manual (7830 7949). 

7831 0349–043 5–25


5.21. HTPIC-2200 

HTPIC-2200 is an absolute-only version of OS 2200 OSI-TP (HTP/x) and supports 

communications with DTI and the resource adapter for Java (J2EE-CON-OPENDTP). 

Interoperability 

HTPIC-2200 can send and receive messages to DTI and the resource adapter for Java 

(J2EE-CON-OPENDTP). If communication with BEA eLink OSI TP running on UnixWare 

or Windows is required, then OS 2200 OSI-TP (HTP/x) must be used. 

The following chart shows interoperability. 


OS 2200 OSI-TP 

(HTP/x) 

OSI-TP for 

UnixWare/NT DTI 

HTPIC-2200 √ 

OS 2200 OSI-TP (HTP/x) √ √ √ 

BEA eLink OSI TP for 

UnixWare/ Windows 

√ √ √ 

DTI √ √ √ √ 

Installation Issues 

As the previous table indicates, OS 2200 OSI-TP supports interoperability with all 

platforms supporting OSI-TP, whereas HTPIC-2200 supports only the Windows platform 

running DTI. If you need to support access to OS 2200 Open Distributed Transaction 

Processing services from Tuxedo clients, you must install OS 2200 OSI-TP (HTP/x). 

HTPIC-2200 and OS 2200 OSI-TP (HTP/x) use the same BDI. Keep in mind that if you 

have OS 2200 OSI-TP installed, there is no need to also install HTPIC-2200. However, if 

your environment dictates that both products are added on the same system, you must 

build one with mode TEST. This creates an alternate with a different BDI. Also, you must 

build OLTP/TM2200 in TEST mode for the second installation. 

5.22. Integrated Recovery Utility (IRU) 


IRU Level 20R1 

Compatibility 

Timestamps and versions throughout IRU are changing with this feature, causing a 

variety of compatibility issues. 

Previous IRU levels are not compatible with new IR structures. Previous levels of IRU 

cannot read history files, key files, move tapes or dump tapes created by this IRU level. 

5–26 7831 0349–043

Integrated Recovery Utility (IRU) 

This level of IRU supports both previous and current versions of the following IRU 

structures: 

• Dump tapes 

• Move tapes 

• FSAH packets (versions 4 and 5 - version 3 is no longer supported) 

FSAH applications must be able to handle new formats for records they expect to 

encounter. FSAH converts packet fields to their appropriate format, but returns audit 

records to the caller in whatever format exists on the audit trail being read. Note that 

TDATE values in version packets are interpreted as local times on input and converted to 

local times on output. 

These local times use the current system offsets to generate TIMEB internally and to 

convert TIMEB to TDATE if needed. 

Users must initialize or Migrate history files The new IRU level handles only new format 

history files. Users who wish to save existing history file information must execute the 

migration utility to populate the new history files. 

Users who currently have local code to alter the number of MHF entries (tapes) retained 

can no longer use that method; they should change the value of MHF-MIN-TAPES 

instead. 

Time Specification 

IRU time management mechanisms now let you choose how times are entered and 

displayed, as either local time or UTC. The new configuration parameter TIMES-ARE- 

LOCAL controls the base of displayed and entered times; local offsets are based on the 

system time at IRU execution. 

When you provide a start or end time to read an audit trail, TIMES-ARE-LOCAL must be 

set to the appropriate value for the time you enter and the current offsets. 

Note that times generated by previous IRU levels and other Integrated Recovery 

products are TDATE based. IRU displays these times without offsets, using the 

mnemonic "", without regard to the TIMES-ARE-LOCAL setting. These TDATE$ 

based times are assumed to be local times. In general, IRU tries to display a timestamp 

in the same format and offset in which it expects to receive the time input. This means 

that some local times for events that took place during a different offset period are 

displayed using the current offsets; even when IRU knows the correct offsets for that 

historical time. 

BUILD and REPORT CONFIG changes 

Configuration parameter changes in this level alter the IRU BUILD routine, introducing 

several new configuration parameters. In addition, DHF-BLK-SIZE parameter was 

removed; the DHF block size is no longer configurable. 

REPORT CONFIG output is also altered. 

7831 0349–043 5–27


ABSOLUTE DEVICE replaced by TAPE-TYPE-OVERRIDE 

The new configuration parameter TAPE-TYPE-OVERRIDE replaces the ABSOLUTE- 

DEVICE parameter in this level. The ASSUME command still accepts ABSOLUTE- 

DEVICE in this release as an alias for TAPE-TYPE-OVERRIDE. IRU will eventually 

remove ABSOLUTE-DEVICE entirely, so we recommend using the new parameter. 

MOVE LEG in MHF 

When you use the LEG clause in the MOVE command, previous levels of IRU 

considered this a non-history file move. IRU now accepts LEG specification for history 

file moves as long as other specifications do not contradict history file use. Each leg is 

recorded in separate chains in the move history file - enabling duplex history file entries 

for a moved audit trail. 

FSAH Packet Changes 

This level of IRU supports a new set of FSAH packets (packet level 5). Version 4 packets 

are still supported, but version 3 packets are not. Version 5 packets accept and return 

TIMEB formatted timestamps instead of the TDATE times used in previous packets. 

FSAH setup fields FSUP-ALAT-PLACEMENT and FSUP-TPM-PLACEMENT are no longer 

available; they are still supported in version 4 packets. These fields were superseded 

several releases ago with the single standard field FSUP-TRAIL-PLACEMENT, which is 

the only supported trail placement field in version 5 packets. 

Migration 

The format of the key file is changed. If you have a key file, you must reinitialize it 

before you can use the COLLECT, DUMP CHANGES, or REPORT KEY FILE commands 

in this level of IRU. 

The format of the dump history file is changed. If you have a dump history file, you must 

reinitialize or migrate it before you can use the DUMP, DUMP CHANGES, RELOAD, 

REPORT, or RECOVER commands. 

In addition to the format changes: 

• The default block size is changed. You might require a larger dump history file to 

accommodate the larger blocks. 

• New SET chains and GROUPs require additional space. You might require a larger 

dump history file to accomodate these items. Note that SETs and GROUPs are 

optional, so you might not need this space. 

• If you are using a TIP history file, you must re-register the file with the new record 

size. 

The format of the move history file is changed. If you have a move history file, you must 

reinitialize or migrate it before you can use the MOVE or REPORT AUDIT commands or 

access MHF audit information from the FSAH interface or the COLLECT, RECOVER, or 

VERIFY commands. 

5–28 7831 0349–043

In addition to the format changes: 


• The default block size is changed. You might require a larger move history file to 

accommodate the larger blocks. 

• New Leg 2 and SET chains take additional space. You might require a a larger move 

history file to accommodate these items. Note that, while SETs are optional, IRU 

always allocates space for leg 2 data. 

• If you are using a TIP history file, you must re-register the file with the new record 

size. 

This IRU level includes several configuration parameter changes to the IRU build 

process. You must change any automated runstreams to account for these new and 

altered parameters. 

This level of IRU includes a new FSAH packet (version 5). This packet uses TIMEB 

timestamps instead of the TDATE$ timestamps used in previous versions. 

IRU still supports version 4 packets, but no longer supports version 3 packets. If you are 

still using version 3 FSAH packets, you must upgrade your FSAH utilities before installing 

the new FSAH. 


IRU Level 19R1 

Compatibility 

VERIFY and FSAH calls to read audit F-cycles using a relative F-cycle start point now 

return or display the absolute F-cycle as the read F-cycle. End point processing is also 

adjusted to absolute F-cycles to avoid missing an F-cycle when the audit trail swaps - or 

possibly getting into an infinite swap/can't read last F-cycle loop. 

IRU allows specification of UDS/TIP files using the TIP syntax and TIP file numbers. 

While this is occasionally useful (e.g. using the LIST command to see DAD structures), it 

can result in misleading or harmful results. Previous levels of IRU did not recognize or 

prevent such actions. Starting in this level, IRU will identify UDS/TIP files specified as TIP 

files with either a warning or error. 

ALLOCATE, REALLOCATE, RELEASE, CLEAR, SET, COMPARE, RELOAD, RELOAD 

ALTERNATE, REPLACE, and static COPY and DUMP commands of TIP files that are 

registered as UDS/TIP will result in a warning. IRU will proceed with processing for these 

commands, but you should be aware that the actions are being taken from a TIP 

perspective without interaction with UDS. 

COLLECT, DUMP CHANGES, RECOVER, and dynamic COPY and DUMP commands of 

TIP files that are registered as UDS/TIP will result in errors. The COPY, DUMP, and 

DUMP CHANGES commands will continue processing the remaining files in the 

command if you’ve specified ON ERROR CONTINUE. COLLECT and RECOVER 

command processing will not proceed after encountering this error. 

7831 0349–043 5–29

Interactive Processing Facility (IPF) 

5.23. Interactive Processing Facility (IPF) 

The IPFSQL interface within IPF 1100 does not support Enterprise Relational Database 

Server (RDMS) stored procedures and any attempt to use them will cause errors. 

5.24. Internationalization Library (I18NLIB) 


I18NLIB 2R2 

Compatibility 

Due to the enhancement to the strftime service routine the value for a year can now be 

less than 0 or greater than 9999. In addition, if a minimum field width is not specified, 

the minimum length is assumed to be two bytes for the %C conversion specification 

and four bytes for the %Y conversion specification. These changes might cause some 

different date / time strings to be created or allow a string to be created when an error 

would have been returned previously. 

Due to the enhancement to the strptime service routine, the value for a year can now be 

less than 0 or greater than 9999. These changes might cause some date / time strings to 

be parsed differently or allow a string to be parsed when previously an error would have 

been returned. Also, due to the implicit maximum field width being defined for many 

conversion specifications, different results or an error could be returned. The different 

results would occur only if the actual field width is greater than the defined implicit 

maximum field width. 

5.25. OS 2200 Transaction Resource Adapter for 

the Java Platform (J2EE-CON-OS2200) 


J2EE-CON-OS2200 Level 13.0 

Compatibility 

• A new OS2200Record subclass, OS2200Xoctet, is introduced. This record allows a 

byte array to be stored and retrieved as the data attribute of the subclass. OS 2200 

TIP Connector inbound communication target EJBs now require OS2200Record 

implementations (OS2200Request and OS2200Xoctet) as the data containers. 

• OS2200EjbRemoteObject objects and OS2200EjbReturnData objects use 

OS2200Record as data objects instead of Strings. EJB samples which use these 

classes can be found in the ExampleInbound\EJB installation directory. 

• The OS2200Header class has changed. The new header version "2" format is defined 

in the OS2200Header class API. OS 2200 programs which invoke EJBs with inbound 

communications must precede the EJB data with this new 72-byte header version. 

COBOL and C definitions for the header can also be found in the 

ExampleInbound\Client installation directory. 

5–30 7831 0349–043

Language Support System (LSS) 

• The EJB response message read by inbound communication clients no longer have 

the format such that the error code and the data are separated by four ampersand 

characters (&). Prior to this 13.0 release, if the returned error code is "3" and the 

returned data text is "Hello", "3&&&&Hello" was returned to the client data portion. In 

this release 13.0, "003" is returned in the status field of the OS2200Header 72-byte 

header, and "Hello" is returned in the data portion of the message. 


J2EE-CON-OS2200 Level 12.0 

Compatibility 

A new version of the OS 2200 TIP Connector configuration file (ra.xml) must be used 

with release 12.0. Configuration files from previous releases are incompatible with 

release 12.0. 

5.26. Language Support System (LSS) 


The following products must be installed and executed with LSS to compile the desired 

program types: 

• The COBOL Compiler (UCOB) to compile COBOL programs 

• The C Compiler to compile C programs 

• The FORTRAN Compiler (UFTN) to compile FORTRAN programs 

• SFS is required if the user wishes to have shared access to data files with locking 

and recovery features. 

The level of LSS is tightly coupled with the corresponding release levels of C Compiler, 

UCOB, and UFTN and therefore must be installed as a set. 

5.27. Linking System (LINK) 


• You must deactivate all active subsystems that require ongoing Linking System 

services whenever the Linking System is replaced. To do this, you can either 

explicitly deactivate the subsystems, or you can do an autorecovery through a $! 

keyin after installing the new Linking System. 

This is necessary because the Linking System data structures that are associated 

with a given subsystem are created at the time the subsystem is initially loaded. A 

new level of the Linking System will not be compatible with those data structures. 

This incompatibility affects any subsystem that requires ongoing support from the 

Linking System after it has been initially loaded. 

7831 0349–043 5–31

Message Control Bank (MCB) 

When following the migration steps, all subsystems are implicitly deactivated due to 

the autorecovery of the system and no further action is required on your part. If the 

$! keyin is not used, it is necessary to deactivate those subsystems that require 

ongoing support from the Linking System. Refer to Appendix B of the Software 

Products Installation Guide for a list of the affected products and specific steps to 

deactivate/reload those subsystems. 

An attempt to deactivate a subsystem that is currently not active on the system 

does not create a problem. In that case, as in the following example, a simple 

“*WARNING* Subsystem was not found” message is returned by the SOLAR 

DEACT processor. 

@sys$lib$*solar.deact sys$lib$*lss.ucs$ssdef 

. 

. 

******************************************************************** 

*WARNING* Subsystem was not found. 

END DEACT 

You can use the SSINFO processor to determine which subsystems are active: 

@SSINFO,STP 

• The Linking System requires the Runtime System for Extended Mode Compilers 

(URTS), SYSLIB, and SLIB. When you are migrating to the current release, the 

version of URTS, SYSLIB, and SLIB associated with the software release previously 

installed will suffice. When URTS, SYSLIB, and SLIB have not previously been 

installed, you must install the current levels of URTS, SYSLIB, and SLIB before you 

install the current level of the Linking System. Do not deinstall (PRODRV) LINK, 

URTS, SYSLIB or SLIB before installing new levels. If you do, you might get errors 

during PREPs of files invoked by PRODLD. 

5.28. Message Control Bank (MCB) 


If you configure multiple SLOT banks, MCB enforces the documented requirement that a 

basic-mode calling program’s data bank not overlap MCB’s instruction bank. This 

requirement has not been enforced if the data of interest within the caller’s bank 

occupies addresses higher than MCB’s instruction bank. If multiple SLOT banks are 

configured, the address range of the caller’s entire data bank must be above the address 

range of the MCB’s instruction bank and SLOT banks. Refer to the MCB Administration 

and Operations Guide and MCB Programming Reference Manual for more information. 

5.29. MSMQI 


MSMQI Level 2R1B 

Compatibility 

Must use NTSI 7R3A on the 2200 and on Windows. 

5–32 7831 0349–043

Messaging Integration Services (NTSI) 

5.30. Messaging Integration Services (NTSI) 


NTSI Level 7R3A 

Migration 

If you wish to install and use MSMQI 2R1B, you must first install NTSI 7R3A. 


• Requires Communications Application Program Interface (COMAPI). 

• The MSI attachment feature requires cpFTP. 

• The Network Authentication features require User Authentication (FLEX) and 

Security Administration. 

5.31. MQSeries for ClearPath OS 2200 (MQS2200) 


The performance of IOW$ (IO with wait) requests was improved with Exec level 48R6. 

This exposed an incorrect coding sequence used by MQLOAD. This was fixed in 

MQS2200 level 2R5B, which was included in the ClearPath OS 2200 Release 12.1 

system software. If you use or plan to use the MQSAVE and MQLOAD utilities, you 

need to install MQS2200 2R5B when you upgrade to this ClearPath release. Refer to 

PLE 18762692 for additional information. 

If you are installing a replacement version of MQS2200 and you want to reinitialize your 

System Services file system (start with a new empty file system), proceed with the 

standard set of post-installation steps in Section 2 of the MQSeries for ClearPath 

OS 2200 Installation, Administration, and Programming Guide to reinitialize your System 

Services file system. 

If you are installing a replacement version of MQS2200 and you wish to retain your 

current MQS2200 System Services file system (containing your MQSeries object 

definitions, objects, and data), you need to perform an alternate set of steps in place of 

steps that you would normally use to initialize your file system. To successfully retain 

your current System Services file system while upgrading to any new level of MQS2200, 

you must follow the steps in Section 2 of the MQSeries for ClearPath OS 2200 

Installation, Administration, and Programming Guide. 

Regardless of whether you are reinitializing or retaining your Systems Services file 

system, you must add the INIT/RUN addstream provided in the file mqs$run. You are 

queried to determine if you are migrating your System Services files to a new level. 

Enter n if you want to reinitialize and start with a new empty file system. 

7831 0349–043 5–33

ODBC Data Access (INFOAccess) 

When you install a replacement version of MQS2200 and you reinitialize or retain your 

System Services file system, you must first 

• Terminate all MQS2200 batch runs. 

• Terminate all user applications that use the MQS API. 

• Ensure that none of the MQS2200 files installed with SOLAR is assigned. 

Specifically, check the mqs$*mqs$exe file. 

5.32. ODBC Data Access (INFOAccess) 


INFOAccess Level 9R2E 

Compatibility 

The Administrator and SQL Server components may not be installed on the same 

system as any prior version. Multiple versions of the ODBC driver or ISQL may co-exist 

on the same system. All supported versions are cross compatible with any OS 

components provided the default TCP/IP port numbers are adjusted. 

Migration 

If a prior version of the ODBC driver is to be updated, the DSNs created should be 

deleted prior to uninstall. 


INFOAccess Level 9R2D 

Compatibility 

The Administrator and SQL Server components may not be installed on the same 

system as any prior version. Multiple versions of the ODBC Driver or ISQL may co-exist 

on the same system. All supported versions are cross compatible with any OS 

components provided the default TCP/IP port numbers are adjusted. 

Migration 

If a prior version of the ODBC Driver is to be updated, the DSNs created should be 

deleted prior to uninstall. 

5–34 7831 0349–043

Open Distributed Transaction Processing (Open DTP) (OLTP-TM2200) 

5.33. Open Distributed Transaction Processing 

(Open DTP) (OLTP-TM2200) 


• Open DTP is delivered on both DVD and CD-ROM media. The DVD media is to be 

installed on the OS 2200 server, the CD-ROM is installed on the PC workstation. 

− On the ClearPath OS 2200 server, use the Software Library Administrator 

(SOLAR) to perform the standard (default) installation of the Open DTP system. 

You can also perform additional installation tailored to your application 

requirements. 

− On the PC workstation, you may install the optional software features of 

Transaction Wrapper (Twrap) and the Java TMAPI library. 

• To run with user authentication level security, OSI-TP level 7R1 or greater must be 

installed. 

Refer to the Open Distributed Transaction Processing Administration Guide Volume 1 for 

installation instructions. 

5.34. Open Programming Environment (OPE) 

The OPE component IXS5000-OPE is removed from all IOE (Standard) and UOE 

packages (Metered). 

For those customers who have been ordering the C++ package CSP20nnn-CPP (Dorado 

100 or older) or CSP21nnn-CPP (Dorado 200 and 300), where nnn is the software group 

number, the OPE component is added to the packages at no additional charge. 

For customers who want to re-license or order OPE, but do not require C++, no-charge 

set of package styles CSP21nnn-OPE (Dorado 200 and 300), where nnn is the software 

group number, should be ordered. 

Note: Group packages are required to ensure proper royalty payments. 

For international customers entitled to OPE updates or to the C++ package and desire an 

update, the update style CSW21-OPU and CSP21nnn-CPP should be ordered. The order 

should be marked as an update order. This will not create a royalty payment. Domestic 

customers can get updates by having their software entitlement profile records scanned 

for the OPE product. 


On Dorado 400 Series systems, OPE level OPE-4R1P.IC2 is required to use OPE. 

Beginning with level 4R1J, OPE can be configured to use Communications Platform 

(CPComm) level 4R1 or higher. However, the method might vary depending on the level. 

7831 0349–043 5–35

Open Programming Environment (OPE) 

OPE and CPComm Functionality Notes 

• OPE’s local address cache may contain loopback addresses. CPComm must be 

configured for loopback and OPE. A local loopback address must be chosen for OPE. 

This address is not user visible to OPE user programs or commands. 

• Possible candidates for the local address are 127.0.0.2, 127.0.0.3, and so forth. 

• Each OPE system must have a unique local loopback address configured in 

CPComm, which is not used by any other product in the CPComm configuration file. 

• If you had three modes of OPE, called sxtsaa, sxtsab, and sxtsac, add the following 

to the CPComm configuration file: 

ip,internal link,loopback ip-address,127.0.0.1 ; **this default must now 

be expressly defined** 

ip-address,127.0.0.2,sxtsaa ; **because of the addition of 

ip-address,127.0.0.3,sxtsab ; 

ip-address,127.0.0.4,sxtsac . 

these local addresses** 

sxtsaa, sxtsab, and sxtsac are the TSAM_NAME parameters in the ope KRNL-CONFIG 

file. 

Note: The loopback lb localhost entry in your /etc/hosts file should not reflect the 

changes in the CPComm configuration; it should remain 127.0.0.1. 

OPE Daylight Savings time Considerations for the USA and CANADA 

Because of amendments to the Uniform Time Act of 1966, starting March 11, 2007, 

OPE systems observing daylight savings time will no longer have the correct local time 

during the periods between: the second Sunday of March and the first Sunday of April 

AND the last Sunday of October and the first Sunday of November 

Elements written by the U-Driver, and files within OPE will have their timestamps set 

one hour slow. Events triggered by CRON will happen one hour late. This problem will 

go away once the former time that was the start of daylight time has passed, and will 

appear once again in the fall when the former end of daylight time is reached. 

Kernel 

The TCPMAP value default was increased from 500 to 700.and in /etc/inet/inetd.conf). 

The new recommended value is 700. The maximum is now 52400. This corresponds to 

the total number of TCP connections plus the total number of possible queued 

connections. 

For inetd, the total number of possible queued connections is the number of TCP 

services * 50. If the number of TCPMAP structures is inadequate, the connection or 

service will not be established, and a notice will be logged in the ALTPRT file: TCPMAP 

full. Consider increasing the TCPMAP kernel configuration 

5–36 7831 0349–043


The TZONE configuration variable in OPE is the default time zone for all OPE users. This 

configuration variable does not follow the POSIX standard. Because of this, it must be 

updated every year to specify that year's correct daylight savings time values. The 

default value for time zone is CST6CDT. This will lead to incorrect local time during the 

transition between the beginning and end the new DST and the old DST. 

The kernel time zone value, TZONE, is described on your online OPE pages at the 

location, http://YourOPESystem/opeconfig/WebHelp/kernelpm.htm Refer to the 

ClearPath OS 2200 Open Programming Environment (OPE) Configuration Guide for more 

details on kernel for TZONE. 

To configure your OPE system properly, the days of the year for daylight time transitions 

must be added to the time zone variable. These values are described in the following 

table. 

Year US Central Time US Eastern Time US Pacific Time 

US Mountain 

Time 

2010 CST6CDT,72,310 EST5EDT,72,310 PST8PDT,72,310 MST7MDT,72,310 









Edit or add the TZONE variable to your krnl-config element in am$?*ampriv. An example 

of the correct setting for the default TZONE setting for the year 2007 follows: 

TZONE 'CST6CDT' OLD default variable 

change to 

TZONE 'CST6CDT,69,307' 

The next time your OPE system is rebooted, it will reflect the above change. You may 

configure this parameter for the following year as soon as the observance of Daylight 

Saving Time has ended for your current year. 

7831 0349–043 5–37


OPE Level 4R1H or Higher 

Migration and Compatibility Considerations 

The UCARD parameter is no longer required, but it is included for backward 

compatibility. If there is a UCARD entry, that OS 2200 user-id/password is used for the 

background run that supports the OPE communications and chronological tasks (CRON 

RUN). Otherwise, the user-id of the user initiating the OPE boot is used for the 

background run. The user-id/password can contain characters from the set (A through Z, 

0 through 9, /, and *). This user-id must have real-time capabilities. 

The UCARD changes also affect user commands demand(1) and submit(1). With 

demand and submit, the user-id of the current run is used when a UCARD is not present. 

Submitl and demandl no longer require that the user-id/password be present in the 

submit and demand files as long as the first line in the file starts with @run. Consult the 

OPE online man pages for more details. 

Mail Considerations 

Considerations for setting up Mail and Domain Name Resolver in OPE are as follows: 

Mail Setup 

The mail system is a port of UnixWare mail. Setting up mail involves the following steps: 

1. Before upgrading to OPE level 4R1H or higher, run 

/usr/lib/mail/surrcmd/smtpsched 

This processes any messages queued in the SMTP mail queue /var/spool/smtpq. 

In UnixWare mail, the mail queue is /var/spool/mailq and the 

/usr/lib/mail/surrcmd/smtpsched program no longer exists. 

2. After replacing the /etc/passwd, /etc/shadow, and /etc/group files with your saved 

copies, modify them so there is a mail user-id and the home directory for smtp is 

/var/spool/mailq and not /var/spool/smtpq. Make the following changes: 

• /etc/passwd: 

Replace the lines for uucp, nuucp, and smtp as follows: 

uucp:x:5:5:0000-uucp(0000):/usr/lib/uucp: 

nuucp:x:10:10:0000-uucp(0000):/usr/spool/uucppublic:/usr/lib/uucp/uucico 

smtp:x:55:6:SMTP Processes:/var/spool/mailq:/usr/bin/sh 

Add the following line for the mail uid immediately after the line for the uucp uid: 

mail:x:6:6:Mail Processes:/etc/mail: 

5–38 7831 0349–043

• /etc/shadow: 

Add the following line after the line for uucp: 

mail:NP:6445: 

• /etc/group: 

Replace the lines for other and nuucp with the following: 

other:pw:1:root 

nuucp:pw:10:root,nuucp 

Add the following line after the uucp line: 

mail:pw:6:root 


3. In the /etc/mail/mailcnfg file, set DOMAIN to your domain name and set 

SMARTERHOST to the name of a gateway machine, and check that this machine’s 

IP address has been added to the /etc/hosts file. 

4. The /etc/mail/mailsurr file no longer needs to be modified. 

/usr/lib/mail/surrcmd/createSurr is run during boot (/etc/rc3.d/S88smtp) to 

auto-discover the machine configuration so that it can create a suitable 

/etc/mail/mailsurr file. The system configuration that createSurr generates is stored 

in /etc/mail/mailflgs. 

If there is an /etc/resolv.conf file on the system, the DNS flag is added to 

/etc/mail/mailflgs which causes createSurr to remove the “-N” option from smtpqer 

in Part 3 of the mailsurr file. See the subsection on Domain Name Resolver Setup 

below for instructions on how to set up the /etc/resolv.conf file. 

If you want to turn on logging of mail through the system, add the “-l on” option to 

the line containing /usr/lib/mail/surrcmd/createSurr in /etc/rc3.d/S88smtp. This 

causes the LOG flag to be added to /etc/mail/mailflgs and logging commands to be 

added to Part 4 of the mailsurr file. The logs generated will be stored in /var/mail/:log 

and /var/mail/:errors. 

If you need to customize the mailsurr file, you need to make the changes to the 

/usr/lib/mail/mailsurr.proto file in order to make them permanent. Then rerun the 

createSurr command. 

Daily logs for smtp delivery are kept in the directory /var/spool/mailq/Logs. 

Note: It is also required that the user-id in the UCARD entry of the krnl-config element 

have real-time capabilities. 

7831 0349–043 5–39

Operations Sentinel Basic Edition (Formerly Single Point Operations) 

5.35. Operations Sentinel Basic Edition (Formerly 

Single Point Operations) 

For detailed considerations, see Section 8. 

Note: Single Point Operations is now called Operations Sentinel. Throughout this 

document, however, the former product name, Single Point Operations, is used in some 

cases when referring to old levels of the product. 


Compatibility 

Operations Sentinel level 10.x and previous releases are not compatible with Operations 

Sentinel level 12.1. Configurations developed under 10.x and previous releases must be 

manually recreated to be used with the new Operations Sentinel 12.1 data model 

structures. Backward compatibility is not supported either, in that Operations Sentinel 

level 12.1 configurations cannot be used by the Operations Sentinel level 10.x and 

previous levels. 

The installation of Operations Sentinel 12.1 provides an opportunity to carry forward and 

convert the 11.x configuration to the 12.1 structure. This is available at the installer's 

choice. 

Migration 

Migration from Operations Sentinel level 10.x and previous releases requires manual 

recreation of the configuration to the Operations Sentinel level 12.1 data model. 


Compatibility 

Operations Sentinel level 10.x and previous releases are not compatible with Operations 

Sentinel level 12.0. Configurations developed under 10.x and previous releases must be 

manually recreated to be used with the new Operations Sentinel 12.0 data model 

structures. Backward compatibility is not supported either, in that Operations Sentinel 

level 12.0 configurations cannot be used by the Operations Sentinel level 10.x and 

previous levels. 

The installation of Operations Sentinel 12.0 provides an opportunity to carry forward and 

convert the 11.x configuration to the 12.0 structure. This is available at the installer's 

choice. 

Migration 

Migration from Operations Sentinel level 10.x and previous releases requires manual 

recreation of the configuration to the Operations Sentinel level 12.0 data model. 


Compatibility 

Operations Sentinel 11.1 is a stability update to Operations Sentinel 11.0. Similar to 11.0, 

11.1 is also not compatible with previous levels (10.x and earlier). 

5–40 7831 0349–043

Migration 


The installation of Operations Sentinel 11.1 server examines the server environment for 

11.0 installation. If one is found, the installer is offered the option of having the 11.0 data 

copied to the 11.1 data folder with corrections for problems identified in 11.0 merged 

into the folder. This preserves the 11.0 configuration and eliminates the need to 

manually redefine it as is required when installing Operations Sentinel 11.0. 

5.36. OSI-TP 

Refer to the SYS$LIB$*XTP$$UTIL.README element for additional release 

documentation, including information about how to use new features. 

5.37. RDMS-JDBC 


RDMS-JDBC Level 2.7 

Compatibility 

RDMS-JDBC 2.6 requires use of a Java 1.5 (Java 5) or higher Runtime Environment. 

Both the RDMS JDBC client and server components must be updated and used 

together. 



Compatibility 

RDMS-JDBC 2.6 requires use of a Java 1.5 (Java 5) or higher Runtime Environment. 



Compatibility 

RDMS-JDBC 2.5 requires use of a 1.5 (Java 5) or higher Runtime Environment. 

Migration 

When migrating to a new level of the RDMS-JDBC product, the new client component 

(RDMSDriver.jar), must be distributed or deployed to any application that is using the 

new JDBC Server or Service. The old version of the RDMSDriver.jar will not work with 

the new version of the JDBC Server or Service. The JDBC Server/Service detects and 

reports the mis-matched levels. The new version of the RDMSDriver.jar is in the installed 

location of the program file *JDBC$Client. (for example, 

UDS$$SRC*JDBC$Client.RDMSDriver.jar). The level of the RDMSDriver.jar can be found 

by looking at the "Manifest.mf" inside of the RDMSDriver.jar. You can also install and run 

multiple copies of the JDBC Server/Service on the same host using different port 

numbers. See the User Guide for details. This allows you to have multiple product levels 

running to support your migration efforts. 

7831 0349–043 5–41

Remote System Support (RSS) 



Compatibility 

RDMS-JDBC 2.4 requires the CP12 level of RDMS, OpenDTP, and JBoss. 

5.38. Remote System Support (RSS) 

RSS allows clients to electronically exchange information with Unisys support via the 

Internet. RSS uses the services of DDP-PPC and CPComm to connect to the Unisys 

Support Center. The TSAM subsystem interface is available with one of the CMSxCPCy 

CPComm installation modes. Clients are encouraged to use the CPComm-API interface 

as configured in the DDP-PPC configuration file. 

5.38.1. Configuration Requirements 

Use the following guidelines to configure DDP-PPC and CPComm. 

DDP-PPC 

HOST NAME= 

TYPE=LOCAL ; 

HOST NAME=RSC 

TYPE=OS1100 

INTERNET-ADR=192.61.61.76 

T-SEL=DDP$$RSC 

TRANSPORT-CLASS=TP0/TCPIP ; 

PPCMASTER OSITSU=UP ; 

OSITSU PROCESS= 

PASSWORD= 

CPMODE= ; 

where x is the mode. See SYS$LIB$*DDP-PPC-2.README for additional details. 

CPComm 

PROCESS, PASSWORD, ; 

T-SELECTORS,X,’DDP$$’ 

CA, 

LINK, CA, ; 

{ETHERNET|FDDI|ETHERNET-LAN,{LAN-0|LAN-1}} 

[IP-INFO ...] 

IP, LINK, ; 

IP-ADDRESS,[,] 

5–42 7831 0349–043

Repository for ClearPath OS 2200 (UREP) 

Note: If is specified on the IP-ADDRESS parameter of the IP 

statement, then the process can use only that specified ip-address. This might be helpful 

for sites with firewall considerations. 

5.38.2. RSS Operations Considerations 

Use @RSS,T to call RSS. The T option prevents RSS from advising the operator to make 

and hang up a telephone connection for the transfer operation. 

5.39. Repository for ClearPath OS 2200 (UREP) 


UREP 13R2 

Compatibility 

The UREP 13R2 build requires SYSLIB 76R4 or later. 


UREP 12R1 

Compatibility 

The default value of the RDMS-LEVEL attribute on the OPTIONS RDMS entity has 

changed from PARTIAL to COMPLETE. Unless you set the RDMS-LEVEL attribute to 

PARTIAL, RDMS will now store complete information (table, user-id, column, index, and 

partition entities) in the repository when you define an RDMS table. 

Migration 

The new RDMS STATISTICS enhancement has migration consequences. There are two 

new RDMS system tables - STATS_COMBINATIONS and STATS_HISTOGRAM - in the 

APPLQUAL*STATS$FILE. The size of the APPLQUAL*STATS$FILE. has changed from 

2,000 trks to 10,000 trks. These changes take effect upon the UREP INSTALL. 

The new RDMS Role Security feature has migration consequences. There are two new 

RDMS system tables - ROLES and ROLEMEMBERSHIP - in the 

APPLQUAL*AUTH$FILE. The UREP INSTALL creates the tables and RDMS Catalog 

views over the tables. For the tables and views to be created successfully, the 

RDMS_CATALOG.RELATIONS view must exist. Before you do a migration UREP 

INSTALL (Mode A) to UREP 12R1 on an existing application group, check for the 

existence of the RDMS_CATALOG.RELATIONS view. 

7831 0349–043 5–43


Example 

@SYS$LIB$*UREP.DD ,,UDSSRC 

REPORT INCLUDE ATTR NONE VIEW RELATIONS FOR SCHEMA RDMS_CATALOG. 

**DESCRIPTION REPORT** 

VIEW RELATIONS ddf 

SCHEMA RDMS_CATALOG 

EXIT. 

If the RDMS_CATALOG.RELATIONS view does not exist, then sign on under the UREP 

Installer's userid and create it. The CREATE VIEW syntax can be found in 

UREP*UTILITY.RDMS-CATALOG. 

Example 

@XQT,E SYS$LIB$*RSA.RSAC-COIVP 

BEGIN THREAD FOR UDSSRC; 

USE DEFAULT QUALIFIER UREP; 

CREATE VIEW RDMS_Catalog.Relations 

( Schema_name, Relation_name, 

Table_or_View, 

UDS_timestamp, 

Creator, 

Data_control ) 

AS 

SELECT QENr.Level1_QE_name, QENr.Level2_QE_Name, 

QENr.Level2_QE_type, 

Apts.Value, 

ENo.Entity_name, 

Adac.Value 

FROM Qualifying_entity_names QENr, 

Entities Er, 

Unsequenced_Relationships URo, 

Entity_names ENo, 

Entity_Attributes Adac, Entity_attributes Apts 

WHERE 

( QENr.Level1_QE_Type='SCHEMA' 

AND (QENr.Level2_QE_type='TABLE' OR QENr.Level2_QE_type='VIEW') 

AND QENr.Number_of_levels=2 ) 

AND ( Er.Entity_identifier=QENr.Qualification_identifier 

AND Er.Created_by_SW='DDF' ) 

AND ( URo.Source_entity_identifier=Er.Entity_identifier 

AND URo.Source_entity_variation=Er.Entity_variation 

AND URo.Source_entity_revision=Er.Entity_revision 

AND ( URo.Relationship_type_name='TABLE-TO-USERID' 

OR URo.Relationship_type_name='VIEW-TO-USERID' ) 

AND ENo.Name_identifier=URo.Target_entity_identifier ) 

AND ( Adac.Entity_identifier=Er.Entity_identifier 

AND Adac.Entity_variation=Er.Entity_variation 

AND Adac.Entity_revision=Er.Entity_revision 

AND Adac.Attribute_type='DATA-ACCESS-CONTROL' ) 

AND ( Apts.Entity_identifier=Er.Entity_identifier 

AND Apts.Entity_variation=Er.Entity_variation 

AND Apts.Entity_revision=Er.Entity_revision 

AND Apts.Attribute_type='DD-PROCESS-TIME-STAMP' ) 

5–44 7831 0349–043

WITH ACCESS CONTROL 

; 

COMMIT THREAD; 

EXIT; 

Runtime System for Extended Mode Compilers (URTS) 

5.40. Runtime System for Extended Mode 

Compilers (URTS) 


New levels of URTS must be installed when background runs for other products are not 

active. If any background runs are active and are written in high-level UCS languages, 

installation of a new level of URTS might cause them to abort. Background runs that 

might be affected by installation of URTS should be terminated through normal 

procedures before installing URTS and then restarted after the installation has 

completed. 

If you are running any application programs that use CPComm, CPComm will be affected 

by the reinstallation of URTS. The following is a list of known products that call 

CPComm: 

• Business Information Server (BIS) 

• COMAPI 

• DDP-PPC 

• OUTPUT-MGR 

• FTP Services for ClearPath OS 2200 (cpFTP) 

• ODBC Data Access (INFOAccess) 

• OPE 

• Open Distributed Transaction Processing (Open DTP) 

• SILAS 

• TCP/IP Application Services (TAS) 

• UNIACCESS-ODBC 

• Web Transaction Server 

Note: If you have additional background runs that are not included in this list, you must 

determine if that product was written in a high-level UCS language. This list will increase 

as products migrate or new products are developed in high-level UCS languages. 

7831 0349–043 5–45

Security-Admin 

5.41. Security-Admin 

5.42. SLIB 


The Security-Admin product includes the following: 

• Security-Admin client 3R4 

• Security-Admin agent 4R2 

• SECMGR command line utility 4R2 


SLIB Level 1R5I 

Migration 

In the previous releases, the SLIB product could be installed in mode SS (the default) or 

mode NONSS. Neither of these old mode names exists in this release. Mode NONSS 

has been eliminated entirely and the name of the default mode has been changed from 

SS to A. SLIB must now always be installed using mode A. 

5.43. SOLAR and SOLAR/E 

The Software Library Administrator (SOLAR) has replaced COMUS as the installation tool 

for all products. You still use COMUS to build products. 

Keep the following considerations in mind when planning your installation for this 

release. 


Note: When a new level of SOLAR is installed, register an Exec or product key as soon 

as possible to convert SYS$*DATA$.KEYTABLE$ to the new extended key table version. 

• You should perform a LIBSAVE before beginning any migration steps. 

• For reference purposes, the key tape has a symbolic KEYTABLE$ element that 

contains a list of the keys on the tape. 

• SOLAR provides an integral part of the Exec Software Controlled Performance (SCP) 

feature by supporting Exec key registration for all supported ClearPath system types. 

An Exec key is registered either through the SOLAR full-screen interface under the 

main menu item “Software Package Registration” or by executing the PKGREG 

utility or through the REGISTERPKG runstream. When an Exec key is registered, it is 

validated and the Exec notified of the key registration. 

• All IOE and OSG software products (System Control Software and mandatory 

software), except for the Exec and PC Console software, are installed using SOLAR. 

• Installation documentation for products that use SOLAR is contained in the Software 

Products Installation Guide. 

5–46 7831 0349–043

SOLAR and SOLAR/E 

• Continue to use COMUS to build all symbolic products. Build information for 

products installed with SOLAR is contained in an ASCII file on the package tape for 

each product. 

• Products installed with SOLAR do not have automatic installation verification 

procedures (IVP). 

• Products installed with SOLAR do not update the COMUS database. Be sure to use 

SOLAR reports to list the installed levels of these products, rather than the COMUS 

system installation logs. 

• Although SOLAR does not require additional privileges beyond those that COMUS 

requires to install and load products, SOLAR checks for and enforces these 

privileges. If you do not have the correct privileges, SOLAR advises you of this 

during your initial session. 

• If there is a cycle limit on either SYS$*DATA$, SYS$LIB$*RUN$, or 

SYS$LIB$*PROC$, your installation might fail. SOLAR creates a +1 cycle of these 

files, which could cause a mass storage hold (M-hold) if the cycle number tries to 

exceed the maximum. Unisys recommends that you not use cycle limits for these 

files. 

• All SOLAR utilities produce a console message when running in batch mode if an 

error or warning occurs. The console message will state that an error or warning 

occurred and that the diagnostic file should be checked for specific details. The 

console message can be suppressed with the N-option on the utility’s call line. 

• You should not restrict general read access to SYS$LIB$*SOLAR and 

SYS$LIB$*SOLAR-GDEF through ACRs or any other means. The file 

SYS$LIB$*SOLAR is included in the Collector (MAP) library search chain to allow 

basic mode products to easily map in the Feature Key Verification (FKEY) utility entry 

points. The file SYS$LIB$*SOLAR-GDEF is included in the Linking System 

subsystem search chain to allow extended mode products to easily link in the FKEY 

utility entry points. A user-id must have read access to these files to perform a MAP 

or LINK. 


SOLAR Level 4R7 

Compatibility 

The Dot-Format Level Enhancement feature introduces a new key table version (8): 

• Exec levels prior to 48R7 require that you apply the changes in PLE 18756811 in 

order to read the new key table version. Without it, the system reverts to its default 

performance level within 30 minutes after registering any key with SOLAR level 4R7. 

• FURPUR 32R5A is required to read the new key table version. Without FURPUR 

level 32R5A 

− You cannot perform a copy (COPY,G command). 

− You cannot perform a COMUS unstack, build, or configure command. 

− You cannot perform a COMUS installation of products from ClearPath OS 2200 

Release 13.0 keyed software packages. 

7831 0349–043 5–47

SOLAR and SOLAR/E 

Note: FURPUR is not required when you use SOLAR to install software from a 

keyed software package. 

• After you use SOLAR level 4R7 to register a key, if you need to revert to a level of 

SOLAR or FURPUR prior to ClearPath OS 2200 Release 13.0, Unisys recommends 

that you perform a LIBLOAD or LIBLOAD/FAS from the library save created before 

you started migration. 

• If you have not registered a key tape, using SOLAR level 4R7 

− You can revert to previous level of SOLAR simply by installing that level. 

− You can revert to a previous level of FURPUR by installing that level along with 

the corresponding level of SOLAR. 

Migration 

To migrate to ClearPath OS 2200 Release 13.0, perform the following steps: 

1. Apply the changes in PLE 18756811 to your existing Exec level and boot. See a 

description of Exec key migration and crossboot requirements in Section 7. 

2. Install SOLAR level 4R7 and FURPUR level 32R5A from the CP-FLD tape. See 

Section 7 for the procedure to install the first install tape (CP-FLD). 

3. Register the ClearPath OS 2200 Release 13.0 product key tape. See Section 7 for 

the procedure to register the key tape. 

The new format for the software product keys includes the release level. 

A registered product/feature key and its corresponding installed products are in 

compliance with the software license only when the Software Control Number (SCN) 

attached to the key matches the registered Exec image enabler key SCN or active 

Primary SCN. 

SOLAR level 4R7 does not prevent product key registration or corresponding software 

installation if the registered Exec image enabler key already contains a different SCN. 

Instead, SOLAR writes a warning message to the diagnostic file and, if executed in 

batch, displays a console message indicating that a noncompliance has occurred. 

Verify that the SCN listed on the product key tape label corresponds to the 

system/partition workload before registering it. If necessary, take corrective action to 

comply with your software license agreement, as follows: 

• If the Exec image enabler key contains the correct SCN, simply locate the correct 

product key tape and register it. 

• If the Exec image enabler key was populated with an incorrect SCN while migrating 

to ClearPath OS 2200 Release 13.0, use LIBLOAD to go back to the system state 

that existed prior to registering the incorrect product key tape and register the 

correct product key tape. 

• If the Exec image enabler key was populated with an incorrect SCN while migrating 

to ClearPath OS 2200 Release 13.0 or earlier, contact your Unisys Support Center for 

assistance. 

5–48 7831 0349–043

Sort/Merge (SORT) 

Refer to the SOLAR End Use Reference Manual for detailed information on how to use 

SOLAR and SOLAR/E. 


SOLAR Level 4R6A 

Software packages created on 18-track, 36-track, DVD, or associated virtual tape (MAS 

or VSM) with Fast Tape Access ON can be copied to 9840 and higher capacity half-inch 

cartridge tape or associated virtual tape (DSIVTL or VTLPLUS) and remain Fast Tape 

Access compatible. 

5.44. Sort/Merge (SORT) 


Sort/Merge Level 22R2A 

Compatibility 

5.45. SSG 

The SORT subroutines can issue LOG messages about the SORT characteristics, if 

requested. The default configuration is to issue LOG messages. These messages are 

also visible in the batch and demand tailsheet. 

The LOG message runid feature modifies one of these messages, moving the CORE and 

TOURNAMENT number fields and inserting the ORIGINAL RUNID and the RUNID fields. 

If a site has a program that analyzes the LOG file and processes the LOG for this SORT 

LOG entry, the movement of these fields and the insertion of the new fields might cause 

the LOG analysis program to either no longer find this message or to pick up the fields 

incorrectly. The LOG analysis program must be modified to handle the new format of 

this message. SORT 22R2A issues the new format of the message; however, both 

forms of the message can be issued on a system. If a program or product is collected 

with the SORT subroutines included as a relocatable library, the level of SORT used to 

collect the program or product determines the format of the message issued, regardless 

of the installed SORT level. 


SSG Level 24R2 

Compatibility 

The following reserved global variables are implemented in SSG level 24R2. There are 

compatibility considerations if you have user-defined global or local variables with the 

names of these new reserved global variables. 

• CASECHAR$ – If you have a user-defined global or local variable with this name the 

operation of the ASTR$, BSTR$ and MSTR$ references may be affected. 

• UNS_CONTROL$ – If you have a user-defined variable with this name unsolicited 

input may change the value from 0 to 1. 

7831 0349–043 5–49

SYSLIB 

• UNS_INPUT$ – If you have a user-defined variable with this name your skeleton will 

not operate correctly and will produce warning messages whenever you attempt to 

modify the variable. 

Note: Unisys recommends that you do not define global or local variable names that 

end with a dollar sign ($). 

5.46. SYSLIB 


SYSLIB Level 76R4 

Migration 

The “Extend SYSLIB Date/Time Services” feature increased the size of several SYSLIB 

relocatable elements and the SYSLIB$1 common bank. This is the first significant size 

change for these elements in many years. @MAP errors can occur for user program 

collections that have operated error-free for years. This can occur if the increased 

SYSLIB element size causes banks to exceed the Basic Mode addressing window size 

limits. 

The following relocatable elements have significant element size increases in SYSLIB 

76R4. Their sizes are shown in octal words: 

| 76R3E | 76R4 

---------- +----------+----------- 

AEDIT$SFDT | 0273 | 01004 * 

AEDIT$T | 0240 | 0772 * 

EDIT$T | 0207 | 0760 

ID$ | 0512 ** | 0461 ** 

SFDT$ | 0425 | 01213 * 

TIMESUBR$ | n/a | 0207 

* Causes inclusion of new element TIMESUBR$ 

** Causes inclusion of SFDT$ 

The SYSLIB$1 common bank address range is shown in octal: 

| 76R3E | 76R4 

---------+----------------+---------------- 

SYSLIB$1 | 01000 - 011662 | 01000 - 014253 

**************************************************************************** 

The "Extend SYSLIB Date/Time Services" feature added new parameters to many 

SYSLIB AEDIT$, EDIT$ and SFDT$ procedures. Assembly (@MASM) of user programs 

that included extra, previously ignored parameters on the procedure calls can now result 

in error messages and MASM E (error) flags. 

The modified procedures are listed below. 

5–50 7831 0349–043

For AEDIT$: 

A$EDATn (n = 1 - 5) 

A$EDAYn (n = 1 - 5) 

A$ESFDT 

A$ETD 

A$ETIME 

For EDIT$: 

E$DATn (n = 1 - 5) 

E$DAYn (n = 1 - 5) 

E$TD 

E$TIME 

For SFDT$: 

S$FDT$ 

S$FDTPKT 

*************************************************************************** 

SYSLIB 

If you DO NOT use the A$EDITPKT procedure to generate the 17-word AEDIT$ 

packet, the SYSLIB Programming Reference Manual (7833 1733), section 4.1.2, states in 

the second paragraph and in the "Note" at the end that you should set the packet version 

(S1 of word 11) to a value of 1. However, the version was not previously validated unless 

you called the AESFDT$ routine. 

Since the 'Extend SYSLIB Date/Time Services' feature implements a new 18-word 

version 2 AEDIT$ packet, it is now necessary to validate the packet version on the initial 

call to the AEDIT$ routine. The AEDIT$ routine is documented in section 4.2.1, Table 4-1, 

A$EDIT row. If the packet version is invalid (not 1 or 2), then previously defined error 

code 02 will be loaded in A1 and an ERR$ will be performed. 

If you DO use the A$EDITPKT procedure the above packet version validation is not a 

concern, since the procedure generates a valid version. If you reassemble your program 

with SYSLIB 76R4 the new 18-word version 2 packet will be generated. 

Also note that the S$FDTPKT procedure to generate the SFDT$ packet has implemented 

a new 8-word version 2 packet. Previous packet version validation is expanded to accept 

either the 5-word version 1 packet or the new version 2 packet. 


SYSLIB Level 76R3D 

Compatibility 

The following compatibility consideration applies ONLY if you have not integrated CHG 

1079 into a level of SYSLIB prior to 76R3D. 

The AEDIT$ procedures A$EPKT, A$EPKTF, A$EPKTSFDT and A$EDITPKT and the 

EDIT$ procedures E$PKT and E$PKTF allow optional parameters with the format 

'name',value when generating packets. SYSLIB 76R3D adds parameter validation to the 

procedures. 

7831 0349–043 5–51

Tape Labeling Utility for ClearPath OS 2200 (TUTIL) 

Existing programs with parameter name errors that previously assembled without error 

will now result in an error message and a MASM E (error) flag. This validation has been 

added to assure that all of the optional parameters that are specified are either 

processed as intended or are reported as being in error. This assures that a misspelled 

parameter name will be detected during program build rather than not detected at all or 

detected during program test or production usage. 

5.47. Tape Labeling Utility for ClearPath OS 2200 

(TUTIL) 


If TeamQuest SAUTILITIES is installed (TLABEL or TLBL), you must deinstall it before 

you install TUTIL (with the default INSTALL, mode A). Any user runstreams must be 

updated to call @TUTIL if they previously called @TLABEL or @TLBL. 

TUTIL provides an installation mode named TEST. This mode allows TUTIL to be 

installed coexistent with a previous version of TUTIL, or with the TeamQuest 

SAUTILITIES (TLABEL or TLBL). The runstreams all have a version name matching the 

release level, and are installed in the file SYS$LIB$*TUTILTST (not the normal alternate 

RUN$ file). The following runstreams are installed: INLBL/1R1B, EINLBL/1R1B, 

BKLBL/1R1B, EBKLBL/1R1B, RELBL/1R1B, ERELBL/1R1B, UNLBL/1R1B, PRLBL/1R1B, 

and PRLBLS/1R1B. 

The TUTIL program is also installed in the file SYS$LIB$*TUTILTST. When installed in 

this mode, TUTIL is not registered as a standard processor, so the full filename must be 

specified when called. 

5.48. TCP/IP Application Services (TAS) 


• After TAS is installed, the background runs error on a system running Fundamental 

Security (SENTRY=0). See 5.14 (DDP-PPC) for more information. 

• You must install DDP-PPC before you build or execute TAS. 

• You must install I18NLIB before you execute TAS. This is necessary because TAS 

uses ELMS, which in turn, requires I18NLIB. 

Refer to the SYS$LIB$*TAS-2.README element for additional release documentation. 

5–52 7831 0349–043

5.49. TeamQuest Products 

TeamQuest Products 

Note: See 3.8 for important information about license keys for TeamQuest products. 


When running TeamQuest Baseline, TeamQuest Online, TeamQuest PMLog, or 

TeamQuest Probes on your system, you should ensure that the base levels of the 

products are the same. The result of mixing base product levels could be database 

corruption. For example, you can run a level 7R4 product with a level 7R4A product, but 

it is incorrect to run a level 6R4 product with a level 7R4 or 7R4A product. 

Notes: 

• TeamQuest Baseline Framework and TeamQuest Online are mutually exclusive 

products. 

• TeamQuest View is part of TeamQuest Baseline Framework and TeamQuest Online. 

5.49.1. TeamQuest Model 


Compatibility 

TeamQuest Model running on Microsoft Vista cannot save to the Program Files directory 

unless the user is logged in as administrator. 

5.49.2. TeamQuest OSAM 


OSAM Level 7R4 

Migration 

OSAM Level 7R4 is required with Exec 48R7 and UDSC 17R1. 

5.49.3. TeamQuest PAR 


PAR Level 9R1 

Migration 

PAR 8R9C or 9R1 is needed if more than 8 control units are configured. 

7831 0349–043 5–53


5.49.4. TeamQuest SAUtilities 


SAUTILITIES Level 6R6 

Compatibility 

When turning on DBEvent, additional questions will be presented to the user due to the 

value-based logging feature. Runstreams may need to be updated to answer these 

questions. Refer to the SAUtilities End Use Reference Manual for details. 

5.49.5. TeamQuest SIMAN (SIMAN) 


TeamQuest SIMAN Level 6R5 

Compatibility 

Beginning with TeamQuest SIMAN 6R5, log entry types 12001, 12002, 12003 and 12004 

are no longer written to the system logfile. Instead, all information previously held in 

these deleted log entries is contained within the newly created type 12005 "TeamQuest 

SIMAN Utilization Trace" log entry. 

TeamQuest Log Analyzer (LA) will continue to support the 12001 - 12004 log entries, 

while providing new support for SIMAN's 12005 log entry via the LA DUMP report using 

single_line format. 


TeamQuest SIMAN Level 6R4 

Compatibility 

• New menu options for summary reports 

SIMAN now provides an option to exclude the user IDs from the summary reports. 

When account usage is restricted to specified user IDs, options 6 and 8 from the 

Account Maintenance menu (below) are available. 

Account Maintenance 

Enter the index of the desired function 

1 Display Account 

2 Install Account 

3 Update Account 

4 Delete Account 

5 Generate Account Summary 

6 Generate Account Summary w/o User-ids 

7 Generate Account/Quota Set Summary 

8 Generate Account/Quota Set Summary w/o User-ids 

9 Clear Account 

10 Change Master Account 

M Master Menu 

X Exit 

5–54 7831 0349–043

• Change in summary reports 


The output from most of the summary reports has changed slightly. Following are 

examples of reports as they exist in SIMAN 6R4. 

Note: For reports that include user IDs, the account number is preceded by “>”to 

assist in traversing the report when accounts have many user IDs. 

Account Summary: 

1 2 3 

123456789012345678901234567890 

ACCOUNTS USERIDS 

-------- ------- 

>ABC 

>ACCT 

TMS1 

TMS10 

Account Summary w/o User-ids: 

1 2 3 

123456789012345678901234567890 

ACCOUNTS 

-------- 

ABC 

ACCT 

ACNTA 

ACNT01 

AMICUS 

BA1 

Account/Quota Set Summary: 

1 2 3 4 

1234567890123456789012345678901234567890123456 

ACCOUNTS USERIDS QUOTA SETS 

-------- ------- ---------- 

>ABC SYSTEM 

>ACCT SYSTEM 

TMS1 SYSTEM 

TMS10 SYSTEM 

Account/Quota Set Summary w/o User-ids: 

1 2 3 

123456789012345678901234567890 

ACCOUNTS QUOTA SETS 

-------- ---------- 

ABC SYSTEM 

ACCT SYSTEM 

ACNTA SYSTEM 

ACNT01 SYSTEM 

AMICUS SYSTEM 

BA1 SYSTEM 

7831 0349–043 5–55

UniAccess-ODBC 

5.49.6. TeamQuest TIP-LA 


TQ-TIP-LA Level 1R4E 

Compatibility 

Queue Time was being calculated incorrectly. That has been corrected so the value will 

be significantly smaller than before. See PLE 18826551 for additional information. 

5.50. UniAccess-ODBC 

Refer to the UNIACCESS READ.ME file for product release notes. For example, the 

UNIACCESS READ.ME file contains: 

• General information, including the list of new features and fixes. 

• Information concerning additional fixes that might be required for your system. 

• Detailed information on compatibility and migration from previous UniAccess-ODBC 

releases. 

• Known problems and limitations. 

• Details of how to obtain the product key. 

5.51. Universal Database Control (UDSC) 


• If the UDSC system file (SYS-FILE) format changes in a new software release, you 

need to reprocess existing configuration definitions in order to use them. Refer to 

the UDSC section of the Universal Database Control Configuration Guide for 

additional information about handling the SYS-FILE during a migration installation. 

• When installing a new UDSC level standard application group over an existing level 

of UDSC, the UP/DOWN status of each file is not transferred to the new SYS-FILE. 

If you cannot place files in an UP state before the migration installation, use the IRU 

LIST ALL DOWN PAGES command to list all the files with a DOWN (inactive) status 

before installation. After the installation, use the IRU DOWN FILE command to bring 

down these files. 


UDSC Level 16R1 

Compatibility 

Usage of the RDMS Dynamic B-Tree Preconditioning (IDENTITY column, GENERATED 

expression, and SET SKIPGENERATED) feature requires the Exec feature UDS Nested 

Steps, available in Exec level 48R2 (CP-OS-2200-11.2) or later. 

5–56 7831 0349–043

Utilization Report Utility for OS 2200 (URU-OS2200) 

5.52. Utilization Report Utility for OS 2200 

(URU-OS2200) 


URU-OS2200 should be installed soon after OS 2200 metered system is ready for use. 

This includes installing the Windows components of URU-OS2200—the URU Windows 

Interface and the URU Windows Service, installing the OS 2200 component of 

URU-OS2200 and starting the URU Background Run. The URU Background Run allows 

the URU Windows Service running on the workstation to connect using a TCP/IP 

connection to the OS 2200 metering partition using CPComm. 

Before you install Windows components of URU-OS2200, you must determine which 

workstation can provide the connectivity and availability required. The workstation 

selected to execute URU-OS2200 for the site must be available to run the URU 

Windows Service as necessary to ensure collection of the COD usage data. Capacity on 

Demand (COD) data is recorded in the OS 2200 COD audit trail and the system log file. 

The URU Windows Service running on the workstation retrieves or harvests the COD 

data from the COD audit trail or system log file periodically. The URU Windows Service 

must be running in order for the COD data to be harvested. It is imperative that the COD 

log data be harvested from the OS 2200 system before the file cycles containing the 

data are overwritten or deleted. 

Unisys strongly recommends that the URU Windows Service be up and running 24 by 7. 

If the URU Windows Service is not running continuously, file management must be done 

by the OS 2200 system administrator to ensure that the COD audit trail and system log 

file cycles are not deleted or overwritten before the COD log data is retrieved. The 

methods available to manage the COD audit trail files are the same as those methods 

available for other Exec audit trails: step control, system log and TPM. See the IRU 

Administration Manual and IRU Operations Guide for additional information. 


URU-OS2200 Level 5.1 

Migration 

This release of URU has two modes of installation: Mode A and Mode B. Mode A URU 

contains a standard version of IRU’s Free Standing Audit Handler (FSAH) subsystem. 

This mode is used when the COD and system log audit trails’ configuration is the 

standard configuration released with the Exec. 

The IRU FSAH level included in URU 5.1 Mode A is IRU level 20R2 released with 

ClearPath OS 2200 13.1. 

Mode B URU does not contain an IRU FSAH subsystem but instead uses the IRU FSAH 

subsystem that is installed on the system. Mode B must be used when the COD and/or 

system log audit trails’ configuration differs from the standard configuration released 

with the Exec. URU requires that IRU be installed with mode FSAH, when you install 

using Mode B. 

7831 0349–043 5–57

Utilization Report Utility for OS 2200 (URU-OS2200) 

With this release, you must also use Mode B to obtain IRU FSAH level 19R1 or any 

earlier FSAH levels. The IRU Move history file (MHF) format changed with IRU 20R1. If 

you used an IRU 19R1or earlier level to move the COD or system log audit trail files to 

tape, then you will need to use IRU Mode B with the appropriate IRU FSAH installed to 

access the tapes via the IRU MHF. 



Migration 

This release of URU still has two modes of installation: Mode A and Mode B. 

Mode A URU contains a standard version of IRU’s Free Standing Audit Handler (FSAH) 

subsystem. This mode is used when the COD and system log audit trails’ configuration 

is the standard configuration released with the Exec. 

Mode B URU does not contain an IRU FSAH subsystem but instead uses the IRU FSAH 

subsystem that is installed on the system. Mode B must be used when the COD and/or 

system log audit trails’ configuration differs from the standard configuration released 

with the Exec. URU requires that IRU be installed with mode FSAH, when you install 

using Mode B. 

With this release, you must also use Mode B to obtain the new IRU level 20R1 released 

in CP 13.0. 

For CP 13.0 and IRU 20R1, the IRU Move history file (MHF) format is changed. IRU’s 

FSAH for CP 13.0 is not compatible with the IRU MHF produced by the IRU 19R1 (CP 

12.1) and vice versa. 

Therefore, for URU 5.0, the FSAH subsystem included in the mode A release is the 

subsystem from IRU 19R1. This allows compatibility with any IRU MHFs produced using 

IRU 19R1. 

To use the IRU 20R1, you must install URU as mode B and have the IRU installed on 

your system using MODE FSAH. 



Migration 

This release will continue to run on previously supported Windows platforms. When 

migrating to URU 4.0, the URU Windows components must be updated before the URU 

Background Run on metered OS2200 partitions. As with previous releases, the URU 4.0 

Windows Service will be able to connect to previous levels of the URU Background Run. 

However, previous levels of the URU Windows Service should not be used to collect 

utilization data from a URU 4.0 Background Run. 

Since previous levels of URU cannot execute on a Windows Vista platform, specific 

steps are required in order to transfer and upgrade existing URU utilization data from an 

existing platform. 

5–58 7831 0349–043

Virtual Machine for Java Platform (JVM) 

The following steps must be completed in order to retain utilization data on a "new" 

Windows Vista platform: 

1. Verify that Database Management is configured in the URU User Interface on the 

current Windows platform. The deletion of data should be enabled to retain only the 

data necessary to transfer. 

2. Stop the URU Service on the current Windows platform. If the URU Service is not 

running, start it and then stop it to ensure that the data that meets the data deletion 

criteria will be purged from the current URU database. 

3. Create the appropriate folder hierarchy on the Windows Vista platform. Some of the 

higher level folders may already exist. The default installation location is: 

Program Files\Unisys\Utilization Report Utility 

In which, the 'Data' folder must be created to store the utilization data. An alternate 

installation location can be setup; however, be sure to indicate this alternate location 

during the installation process so that any existing data can be upgraded 

appropriately. 

The full folder path must be setup on the Windows Vista platform: 

\Data 

4. Copy the URU.MDB file from the 'Data' folder on the current Windows platform to 

the 'Data' folder on the Windows Vista platform. 

5. Install URU 4.0 using the delivered CD. Again, be sure to change the default 

installation path to match the folder path setup in step 3, if it is not the default 

installation path. The upgrade process will be initiated as part of the installation, and 

any data in the transferred URU.MDB file will be upgraded. 

Note: If no data transfer is necessary, simply install URU 4.0 without any initial 

setup required. 

5.53. Virtual Machine for Java Platform (JVM) 


• You must install CIFS before you install JVM. This is necessary because the Java 

core classes are copied into the CIFS directory /java/jre/lib during installation. CIFS 

must also be available during execution of any Java program. 

• If you still have an old UPAS front end installed, you must remove it before you 

install JVM; otherwise you will get a PRODLD error indicating a BDI conflict. 

• Since the JVM product files that reside in CIFS files are not restored by LIBLOAD, an 

addstream has been provided in SYS$LIB$*JVM$LIB.MAKELIB to restore JVM on 

ClearPath OS 2200 product files into CIFS files after a LIBLOAD. However, there is 

one JVM product file, /java/jre/lib/security/cacerts that might have been modified 

since it was installed. For this file, you should make a copy before doing a LIBSAVE 

and restore it after doing the LIBLOAD and adding MAKELIB. If you don't do this 

save and restore, MAKELIB will restore /java/jre/lib/security/cacerts to its original 

version. 

• For information on requirements for JVM sockets and net functionality, refer to the 

Virtual Machine for the Java Platform User Guide. 

7831 0349–043 5–59

Virtual Machine for the Java Platform on ClearPath OS 2200 JProcessor (JPJVM) 


JVM Level 4R2A 

Migration 

The following statement in quotes from section 3.2 Environment Variables in the JVM 

user guide for ClearPath OS 2200 Release 12.0 is no longer valid and is removed from 

the JVM user guide for ClearPath OS 2200 Release 12.1: “The FILE.ENCODING value 

should be added only if the default coded character set (CCS) does not correspond to the 

CCS associated with the default locale or the locale in force when the JVM on OS 2200 

is initiated.” Setting the system property to anything other than one of the Sun provided 

standard character sets is dangerous. It can cause JVM initialization failures in Java SE 

1.5. Sun added a new java.nio charset mechanism in Java J2SE 1.4. Sun left the old 

deprecated converter mechanism in place, but its usefulness has eroded over time. The 

new java.nio charset mechanism should be used for Unisys provided charsets. 


JVM Level 4R2 

Compatibility 

JVM 4R2 requires CIFS 6R3 or higher. 

5.54. Virtual Machine for the Java Platform on 

ClearPath OS 2200 JProcessor (JPJVM) 


JPJVM Level 6.1 

Migration 

The following statement in quotes from section 3.2 Environment Variables in the CP12.0 

JPJVM user guide is no longer valid and is removed from the CP12.1 JPJVM user guide. 

“The FILE.ENCODING value should be added only if the default coded character set 

(CCS) does not correspond to the CCS associated with the default locale or the locale in 

force when the JVM on OS 2200 is initiated.” Setting the system property to anything 

other than one of the Sun provided standard character sets can cause JVM initialization 

failures in Java SE 1.5. In Java SE 1.6, it is silently ignored and UTF-8 is used instead of 

what was specified. Sun Microsystems added a new java.nio charset mechanism in Java 

J2SE 1.4. Sun Microsystems left the old deprecated converter mechanism in place, but 

its usefulness has eroded over time. The ClearPath OS 2200 JProcessor JVM only 

supports the new java.nio charset mechanism for Unisys provided charsets. 


JPJVM Level 6.0 

Compatibility 

The CIFS utility, ZIPUT, requires use of the OS 2200 JVM which can be installed 

concurrently with JPJVM. The I18N proprietary classes have been removed. 

5–60 7831 0349–043

5.55. Web Transaction Server (WEBTS) 


Web Transaction Server (WEBTS) 

• The first time Web Transaction Server is started, it automatically updates 

configuration files to the new format if their format differs. It is strongly 

recommended that you make a backup copy of the configuration file and any other 

WebTS associated files prior to installation. 

Note: Refer to the Web Transaction Server for ClearPath OS 2200 Administration 

Guide for complete information and procedures for migrating from previous levels of 

Web Transaction Server to the current level of Web Transaction Server. 

• The Web Transaction Server is included in the Integrated Operating Environment 

(IOE). 

• Refer to the Web Transaction Server for ClearPath OS 2200 Administration Guide for 

information on Web Transaction Server dependencies on OS 2200 software levels. 

5.56. WebSphere® MQ Version 7 for ClearPath 

OS 2200 (WMQ2200) 


Migrating from MQS2200 to WMQ2200 

Migration is no longer done with the *mqs$run.init/run addstream. Several migration 

scenarios exist for upgrading from MQS2200 to WMQ2200. Existing MQS2200 users 

have the following options: 

• Replacement – Remove all existing queue manager data by uninstalling the existing 

MQS2200 product and then installing WMQ2200. 

• Co-install – Retain your existing MQS2200 installation alongside your new 

WMQ2200 installation by generating and installing an alternate BDI version of 

WMQ2200. 

• Migration – Retain your existing queue manager data by following the migration 

procedure. 

Refer to the WebSphere® MQ Version 7 for ClearPath OS 2200 Installation, 

Administration, and Programming Guide for more information on these options. 

Upgrading from a Previous Level of WMQ2200 

Installing a new level of WMQ2200 first removes the MQS subsystem as well as the 

previously installed WebSphere MQ RPM on the OS 2200 QProcessor. Installing a new 

level of WMQ2200 does not affect your queue manager objects or queue data. In other 

words, the content of /var/mqm is not removed. 

You can choose one of the two procedures depending upon whether you are upgrading 

a High Availability environment. Refer to the WebSphere® MQ Version 7 for ClearPath 

OS 2200 Installation, Administration, and Programming Guide for more information. 

7831 0349–043 5–61

WebSphere® MQ Version 7 for ClearPath OS 2200 (WMQ2200) 

If you are also updating your Linux System Software image, make sure to use one of the 

following options to save your queue manager objects and data before updating your 

image and your WMQ2200 level: 

• Option 1: Backup and restore your queue manager objects and data using unx shell 

commands 

1. Backup your queue manager objects and data using the mqsave unx shell 

command. 

2. Update the Linux System Software image 

3. Install new level of WMQ2200 

4. Restore your queue manager objects using the mqload unx shell command 

• Option 2: Use the OS 2200 Administration Console Filesystem Backup feature 

1. Use the OS 2200 Administration Console Filesystem Backup module to backup a 

profile that includes your /var/mqm directory to the OS 2200 or an external disk 

2. Update the Linux System Software 

3. Install new level of WMQ2200 

4. Restore your queue manager objects using the Filesystem Backup module 

Refer to the WebSphere® MQ Version 7 for ClearPath OS 2200 Installation, 

Administration, and Programming Guide for more information. 


WMQ2200 Level 7R0 

Compatibility 

WMQ2200 is based on IBM® WebSphere MQ Version 7.0 and is a compatible follow-on 

to IBM MQSeries Version 5.2 (MQS2200). Where specific differences exist, they are 

documented in the user documentation provided. Refer to the WebSphere MQ Version 7 

for ClearPath OS 2200 Installation, Administration, and Programming Guide for more 

information. 

WMQ2200 7R0 is paired with QProcessor 2.0. Using WMQ2200 7R0 on any QProcessor 

version earlier than 2.0, or using QProcessor 2.0 with any WMQ2200 version earlier than 

7R0 is not supported. 

Please refer to the System Release Profile (SRP) for QProcessor-2.0 on the support 

Website for WMQ2200 ordering information. 

Migration 

Migration scenarios exist for customers migrating from MQSeries for ClearPath OS 2200 

(MQS2200) to IBM WebSphere MQ Version 7.0 (WMQ2200). 

Upgrading from a previous level of WMQ2200 to WMQ2200 Version 7.0 is also 

supported. To do this it is required that you install the QProcessor 2.0 image on your 

QProcessor specialty engine before installing WMQ2200 7R0. 

5–62 7831 0349–043


Refer to the WebSphere MQ Version 7 for ClearPath OS 2200 Installation, 

Administration, and Programming Guide for more information on these migration 

scenarios. 


WMQ2200 Level 6R0A 

Migration 

In a change from the previously released version of WMQ2200, the installation process 

now uses different SOLAR installation modes to install either on the OS 2200 or an 

OS 2200 QProcessor. The default mode, WMQ$A, is used to install to the OS 2200 only. 

Modes Q$1 through Q$8 are used to install to the eight possible OS 2200 QProcessors. 

This will typically be Q$1. A complete installation of the product is done by selecting one 

OS 2200 installation mode and at least one OS 2200 QProcessor installation mode to 

perform software installation on both the OS 2200 and the OS 2200 QProcessor. 

WMQ2200 Considerations 

If WMQ2200 is being installed using the INSTALLPKG runstream, a specific mode must 

be selected instead of choosing to install the default mode. A separate runstream must 

be created for the OS 2200 install and each OS 2200 QProcessor install. 

The OS 2200 QProcessor Administration Console is a browser based administration tool 

to configure, manage, and diagnose hardware and software issues with the OS 2200 

QProcessor. It provides the following capabilities for the WMQ2200 user: 

• System Health to track and configure the disk subsystem. 

• Manage User Mappings to configure and manage OS 2200 and other remote user 

mappings to OS 2200 QProcessor users and groups. 

• Manage MQ Log Policy to configure and manage the archival of MQ log files. 

• Manage MQ to allow users to view, edit configuration, start, and stop queue 

managers. The root user must be mapped to the local mqm group to enable this 

capability. 

• Collect MQ Trace and Dumps to collect files and download the contents. 

• View System Logs to view or download system error logs including queue manager 

logs, system logs, and installation logs among others. 

• Filesystem Backup to backup and restore any data stored on the OS 2200 

QProcessor. 

• Manage External Disks to configure and manage optional external disk subsystems. 

7831 0349–043 5–63


Refer to the following documents for more information on using the OS 2200 

QProcessor Administration Console: 

• ClearPath Specialty Engine for OS 2200 Installation and Servicing Guide 

• ClearPath Specialty Engine for OS 2200 Configuration Guide 

• ClearPath OS 2200 QProcessor Administration Console Help 

• WebSphere® MQ Version 6 for ClearPath OS 2200 Installation, Administration, and 

Programming Guide 

5–64 7831 0349–043

Section 6 

Workstation-Based Software 


This section covers the migration and compatibility considerations for the 

workstation-based software products. 

6.1. ClearPath OS 2200 Release 13.2 

Products are listed in alphabetical order. 

6.1.1. Enterprise Output Manager Workstation Requirements 

Sites must provide a workstation on which to run Enterprise Output Manager software. 

Requirements for running Enterprise Output Manager software are as follows: 

• Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista 

(Business, Ultimate, and Enterprise Editions) and Windows XP Professional. 

• Windows .NET Framework 3.5. 

• A system that meets the minimum requirements of the Windows operating system. 

• A hard disk with a minimum of 100 MB available for the Enterprise Output Manager 

software, plus enough space for the files that you want Enterprise Output Manager 

to process. 

• A CD-ROM drive. 

• A network interface card to receive files from other systems through TCP 

communications. 

Refer to the Enterprise Output Manager Help for detailed information. 

6.1.2. TeamQuest Model (TQ-MODEL) 

See 3.8 for important information about license keys for TeamQuest products. 

6.1.3. TeamQuest View (TQ-VIEW) 

The following is the consideration for TeamQuest View (TQ-VIEW): 

TeamQuest View for Microsoft Windows XP, Vista, and 7 is automatically included in the 

TeamQuest Baseline package. 

7831 0349–043 6–1

Workstation-Based Software Considerations 

6.1.4. Web Transaction Server 

The considerations for the Web Transaction Server PC-based components are as 

follows: 

• Form Assistant (Web Enabler for Display Processing System (formerly JavaClient for 

DPS) transactions) and Web Transaction Server Administrator (WebTSA) have been 

installed and run on Windows XP and Windows 2000. 

• Refer to “Hardware and Software Requirements” in the Web Transaction Server for 

ClearPath OS 2200 Administration Guide for more dependencies. 

6.2. Windows-Based Software Considerations 

Sections 6.2.1and 6.2.2 cover the migration and compatibility considerations impacting 

Windows products. 

6.2.1. Enterprise Output Manager (EOM) 

Enterprise Output Manager is supported on Windows Server 2008, Windows Server 

2003, Windows Vista (Business, Ultimate, and Enterprise Editions) and Windows XP 

Professional. 

6.2.2. Operations Sentinel (SPO) 

Operations Sentinel server is supported on Windows Server 2008/R2, Windows Server 

2008 (Standard Edition and above), and Windows 2003. Operations Sentinel server is 

also supported on Windows XP Professional only on the Dorado 110 Service Processor. 

Operations Sentinel workstation is supported on all the above server platforms, 

Windows 7 (Professional and above), Windows VISTA (Business Edition and above) and 

Windows XP Professional. Operations Sentinel workstation is supported on both 32-bit 

and 64-bit versions of the workstation operating systems. 

6–2 7831 0349–043

Section 7 

Installing ClearPath OS 2200 Release 

13.2 Software 

This section provides the following information to assist you in installing the ClearPath 

OS 2200 Release 13.2 products on your system: 

• A migration planning checklist (Section 7.1) 

• Installation considerations (Section 7.2) 

• Other considerations (Section 7.3) 

• Description of fast-load tapes (Section 7.4) 

• Migration sequences (Section 7.5)—alternative procedures for migrating products as 

follows: 

− Installing products from fast-load tapes (Section 7.6) 

− Installing products from package tapes (Section 7.7) 

• Procedure for initializing an existing system (I-boot) (Section 7.8) 

• Migration for existing Dorado 4000 customers (Section 7.9) 

• Migration for existing Dorado 400 customers(Section 7.10) 

• Migration for existing Dorado 4100 customers (Section 7.11) 

This information is designed to help plan and carry out migration from an earlier release 

to this release. It also provides information about initializing an existing ClearPath 

OS 2200 server. 

These procedures apply to all supported systems for this release as listed in Section 1. 

Note: The migration sequence described in this section assumes that you are already 

running ClearPath OS 2200 Release 12.0 or higher. If you are migrating to this release 

from a release prior to 12.0 there may be important considerations that are no longer 

documented here. To perform a migration from a release prior to 12.0 you may need to 

consult the Planning and Migration Overview document associated with release 12.0 and 

possibly prior releases to ensure that any migration issues introduced by all of the 

intervening releases have been identified. 

7831 0349–043 7–1

Migration Planning Checklist 

7.1. Migration Planning Checklist 

Use the following checklist to help plan your migration strategy. Depending on the 

configuration of your site, you may have additional issues to consider. 

• If you are migrating an existing Dorado 400, Dorado 4000, or Dorado 4100 system to 

this release from a prior release, there are critical interdependencies involving 

CPCommOS, various plateau components, and the installation order for certain 

products (including the EXEC). Refer to sections “7.9 Migration for Dorado 4000” 

“7.10 Migration for Dorado 400” or “7.11 Migration for Existing Dorado 4100 

Customers” for details. 

• Perform an audit of all Unisys software levels that you currently have installed. 

• Perform an audit of the local code that you have installed, and plan for its migration. 

If you have a significant amount of local code and plan to carry it forward to this 

release, you should estimate the complexity of this task. This estimate should 

include the number of programming hours required to relocate the code, the amount 

of testing needed, and the environment required for recertification. 

• Perform an audit of all PLEs applied to the current levels of standard software. 

Verify that these PLEs are already integrated into levels for this release. If not, 

generate the levels for this release with PLEs. 

• Plan your installation sequence. Know which products you will be installing and in 

what order. See Appendix C for the tape name of each product. 

• You will receive a product key tape that provides access to the authorized products 

for your site. You must register that key tape using the SOLAR level received with 

this release before installation. 

• After registering the key tape, print and save the SOLAR PKGREG Key Package 

Summary Report. This report identifies the products that you are authorized for. 

• Plan a training strategy for programmers, operators, and end users. 

• Arrange system time for installation and testing. 

• Arrange for additional technical assistance. Estimate the amount and type of work 

and dedicate appropriate personnel to specific tasks. 

• Plan for a fallback position in case you have to crossboot back to your previous 

environment. 

• Back up your current software and data files. 

• Do not make site program changes until you have the new release up and running. 

• Before upgrading to use new capabilities, be sure your existing production system is 

stable. 

• Make sure that you have the corresponding product documentation available and 

study it ahead of time for preparation. 

• If a document refers to a problem list entry (PLE), obtain a listing of that PLE from 

the Unisys Product Support Center. 

• Update your in-house documentation (of site-specific procedures). 

7–2 7831 0349–043

Installation Considerations 

• If this is the first time you are using TeamQuest products or you are migrating from a 

release prior to ClearPath 12.0, you need to obtain a registered product license key. 

This is documented in the TeamQuest Product Installation Information Bulletin 

(78515194). Refer to “License Keys for TeamQuest Products” in Section 3 for more 

information. If you already obtained TeamQuest license keys valid for ClearPath 

OS 2200 Release 12.0 or higher, there are no changes required for this release. 

7.2. Installation Considerations 

Caution 

See 3.1 for installation and other considerations that might affect or impact 

your installation. This information is grouped by release. 

Failure to read and apply the installation considerations described in 3.1 might 

cause the migration and installation sequences described in this section to 

fail. 

If there are no installation dependencies or conflicts, you can select products in different 

logical packages on the same physical package for installation from the same 

runstream. Refer to the SOLAR User Reference Manual for detailed information about 

using the F12 function key from the Product selection screen. 

With one exception, installation considerations when installing products from fast-load 

tapes are exactly the same as when installing products from package tapes or when 

installing with an initial boot. The exception is as follows: If you install DDP-PPC from a 

fast-load tape, and you will be running DDP-PPC in a Fundamental security environment, 

you must replace the installed version of the DDP-PPC SSD element, which supports 

Security Level 1 or higher, with the TRUSTED version that supports Fundamental 

security. See 5.14 for additional information. 

Note: Several installation runstreams are referenced in this section. If you choose to 

use these runstreams, for detailed information concerning the use of these runstreams, 

please reference Appendix B (Runstreams) in the Software Library Administrator 

(SOLAR) User Reference Manual. 

7.3. Other Considerations 

• Fast-load tapes CP-OE1A and CP-OE1B containing the Integrated Operating 

Environment (IOE) products are keyed. You must install keys first before products 

can be installed. 

• Software releases are delivered on DVD media, refer to the ClearPath OS 2200 DVD 

Media Quick Reference Card or C.1 for more information on logical package tape 

definition. 

• After installing a product, you must be sure to free the product’s SYS$LIB$*product 

file before using the product. If this is not done, the product might not work properly. 

7831 0349–043 7–3

Other Considerations 

• CPComm 6R1 (in the ClearPath OS 2200 13.0 release) and later now requires the 

CryptoLib product to be installed. If you are already running the ClearPath OS 2200 

13.0 release then you have already installed CryptoLib. If you are currently running a 

ClearPath OS 2200 release prior to 13.0 and want to build CPComm 6R2 before 

beginning the rest of your migration to the ClearPath OS 2200 13.2 release, you 

must perform the following steps: 

1. Build and boot your current Exec with PLE 18756811 

2. Install SOLAR 4R7A from the CP01 package tape 

3. Register your ClearPath OS 2200 Release 13.2 Software Product keys 

4. Install FURPUR 32R5B from the CP01 Package tape 

5. Install CryptoLib 1R1 from the CP-COMMSUITE package tape 

Your environment is now ready to build CPComm 6R2. 

• You must install and activate CIFS before installing JVM. This is necessary because 

the Java core classes are copied into the CIFS directory /java/jre/lib during 

installation. CIFS must also be available during execution of any Java program. 

• TeamQuest products have the following installation considerations: 

− TeamQuest Baseline and TeamQuest Online are mutually exclusive. 

− See 3.8 for information on license keys for TeamQuest products. 

• You should establish the Software Controlled Performance (SCP) contracted 

performance level as soon as possible. See “Software Controlled Performance” in 

Section 4. 

During bootstrap, the system runs at 100-percent performance until after SYS FIN to 

speed recovery. The system then runs at the previously registered SCP value from 

either the SYS$*DATA$ file or the DRS device. Otherwise, 100-percent performance 

is used up to 30 minutes after the SYS$*DATA$ file is established by the SOLAR 

installation, LIBLOAD, LIBLOAD/FAS, and so on. Then the default performance level 

is used until the Exec key is registered. 

Register the Exec key tape (labeled “Software Control Performance”) included in the 

system packaging using the SOLAR level received with this release. The process for 

registering the Exec key tape is the same as registering a product key tape. 

7–4 7831 0349–043

7.4. Description of Fast-Load Tapes 

Description of Fast-Load Tapes 

To support faster installation of the ClearPath Integrated Operating Environment (IOE) 

products, Unisys has created the following fast-load tapes: 

• The CP-FLD and CP-FLD400 (“first-load”) tapes contain products that must be 

installed on your current system before migrating to the new Exec. The products on 

this tape are nonkeyed, nonbuildable, and are installed in their default mode. 

• The following fast-load tapes are keyed. You must install keys first before products 

can be installed from these tapes: 

− The CP-OE1A tape is included to ease installation of new levels of the security 

management products, which are required to administer security following a 

migration installation. Products on the tape are DAP, DMPLIB, Open DTP, 

Security-Admin, and SIMAN. 

− The CP-OE1B tape contains IOE products that typically can be installed in default 

mode without change at a site. 

• The CP-OE2 tape contains products (TIPUTIL, MCB, and DPS 2200) that might or 

might not need to be configured to your particular needs. If you do not need to 

reconfigure them, use the INSTALLPKG runstream to install those products in 

default mode. The products on this tape are nonkeyed, nonbuildable, and are 

installed in their default mode. 

Note: See Appendix C for detailed information about tape packaging of products. 

7.5. Migration Sequences 

This subsection describes two migration sequences you can choose from to install your 

ClearPath OS 2200 Release 13.2 products. Because of the many product and feature 

interdependencies, do not randomly install ClearPath OS 2200 Release 13.2 software. 

Although some flexibility is allowed, the recommended migration order presented in 

these sequences should be observed as closely as possible. 

The migration sequences are as follows: 

• Installing products from fast-load tapes (7.6) 

• Installing products from package tapes (7.7) 

Notes: 




products (including the EXEC). Refer to sections “7.9 Migration for Dorado 4000” 

and “7.10 Migration for Dorado 400” for details. 

7831 0349–043 7–5

Installing from Fast-Load Tapes 

• If you encounter any difficulties while following these installation sequences, contact 

your Unisys Product Support Center. 

• Software levels in ClearPath OS 2200 Release 13.2 have been tested for stability and 

compatibility as part of an integrated system. Products having lower levels than 

those in ClearPath OS 2200 Release 13.2 might function correctly, but Unisys 

recommends that your site develop a migration plan to use only ClearPath OS 2200 

Release 13.2 levels. 

7.6. Installing from Fast-Load Tapes 

This sequence describes how to migrate to the current release by using fast-load tapes 

to speed up installation of the Integrated Operating Environment (IOE) on a ClearPath 

server. In this sequence, the following fast-load tapes are used: CP-FLD, CP-FLD400, 

CP-OE1A, CP-OE1B, and CP-OE2 (see 7.4). 

With this sequence, you install the CP-FLD or the CP-FLD400 first-load tape before 

building and booting the Exec. While building your ClearPath OS 2200 Release 13.2 

Exec, you must install any separately packaged Exec features that your site has ordered 

from the CP-SPF tape. 

The products on fast-load tapes are the released version of the products. Interim 

corrections are not available on those tapes. If you have installed any interim corrections 

or have fixes in products beyond the released version, you must perform one of the 

following steps to ensure that your site's version remains installed. 

• Install all of the products on the fast-load tape and then reinstall the interim 

correction or site-updated products. 

• Selectively install the products off the fast-load tape and do not install interim 

correction or site-updated products. 

You could choose to not use the fast-load tape but instead install products from package 

tapes (see 7.7). One product that is often affected in this manner is Enterprise Output 

Manager (EOM). 

Notes: 

• This installation sequence uses the logical package name. See C.1 for more 

information. 

• Once IOE products have been installed from the fast-load tape, they need not be 

reinstalled from a package tape unless your site wishes to customize the installation. 

• Since every user database configuration can differ, it is strongly suggested that you 

read the appropriate overview, planning, installation and configuration guides that 

apply to your own environment. This installation suggests only the order the 

products need to be installed. 




products (including the EXEC). Refer to sections “7.9 Migration for Dorado 4000”, 



7–6 7831 0349–043

Following are the recommended steps: 


1. There are three migration issues that may affect cross-booting between EXEC 

48R8A and older EXEC levels. These issues may require that PLEs be generated 

into your older EXEC level and booted before you move up to EXEC 48R8A. If you 

drop back from EXEC 48R8A to your older EXEC level, you must always drop back to 

an EXEC level that includes these PLEs. See Table 7–1 for the required migration 

information. A check mark in the table indicates that an action must be taken. 

Note: If you are migrating to this release from a release prior to 12.0 there may be 

other important cross-boot considerations that are no longer documented here. To 

perform a migration from a release prior to 12.0 you should consult the Planning and 

Migration Overview documentation associated with release 12.0 and possibly 

additional prior releases to ensure that any migration issues introduced by all of the 


There are no cross-boot or migration issues between Exec 48R8 (ClearPath OS 2200 

Release 13.1) and Exec 48R8A (ClearPath OS 2200 Release 13.2). Exec 48R7 already 

includes all the necessary PLEs. Systems running Exec levels prior to 48R7 should 

add the necessary PLEs before booting Exec 48R8. 

a. KEYTABLE$ Migration Code 


consideration. You must build and boot your current Exec to integrate the 

changes in PLE 18756811. These fixes are required in order for the Exec to 

recognize the new enhanced version of the system key table written by SOLAR 

level 4R7 or higher. You must update and boot your current EXEC to include this 

KEYTABLE$ migration code before installing SOLAR level 4R7A. FURPUR level 

32R5B must also be installed. 

A SOLAR level 4R7 or higher KEYGEN-created key can only be used on an Exec 

that recognizes the new key table version. When SOLAR level 4R7 or higher is 

first used to register any key, the SYS$*DATA$.KEYTABLE$ is written in the 

new format which is not recognized by previous levels of SOLAR or the Exec. 



higher. 

b. Cross-boot consideration for Dorado 400 and Dorado 4000 

systems 

A known problem may prevent existing Dorado 400 or Dorado 4000 systems 

from being able to boot ClearPath OS 2200 Release 13.2 EXEC level 48R8A. 

This issue can only arise if the EXEC level you are currently running is 48R4 

(ClearPath OS 2200 Release 12.0). EXEC levels 48R5 and above already contain 

the necessary change. If you are a Dorado 400 or Dorado 4000 customer and are 

running EXEC level 48R4, you must build and boot PLE 18691159 before you 

make any attempt to boot EXEC level 48R8. 

7831 0349–043 7–7


Table 7–1. Migration Requirements for Fast-Load Tapes 

Required Action Release 12.0 

(Exec 48R4) 

KEYTABLE$ Migration 

code PLE 18756811 

Cross-boot consideration 

for Dorado 400 and Dorado 

4000 systems 

Migrating to Release 13.2 (EXEC 48R8A) From… 

Release 12.0 Plus 

(Exec 48R5) 

Release 12.1 

(Exec 48R6) 


(Exec 48R7) 

√ √ √ No action 

required 

√ No action required No action 

required 

No action 

required 

2. Perform a LIBSAVE of your current system. See 5.43 (SOLAR considerations) for 


3. Beginning with ClearPath OS 2200 Release 12.1 a new fast-load tape is provided for 

the Dorado 400 systems. Dorado 400 sites must use the CP-FLD400 fast-load tape. 

All other systems continue to use the CP-FLD fast-load tape. 

Install the products contained on the first-load (CP-FLD or CP-FLD400) fast-load tape 

(refer to the following table). 

If you are a non-Dorado 400 site, install these products quickly by using the ST 

INSTALLFLD command. 

If you have a Dorado 400 system, you must use the ST INSTALLPKG runstream to 

install the CP-FLD400 fast-load tape. Additional input is required with this runstream 

for installing the CP-FLD400 tape. You will be prompted to provide the Logical 

Package name, CP-FLD400 and the Package Level, 13.2. 

The SOLAR full-screen interface can also be used to register and install these 

products. 

Note: If you use the full-screen interface for installing CP-FLD, CP-FLD400, or CP01 

products, sign off from your demand terminal and wait until the batch install 

runstream finishes. Then, reenter the full-screen interface and continue with your 

installation. 

7–8 7831 0349–043 


(Exec 48R8) 

No action 

required 

No action 

required

Installation 

and Support 

Name 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 


Notes 

COMUS 6R9A CP-FLD A COMUS is needed to generate the Exec 

CPComm 

Note: 

CPComm is 

used only with 

Dorado 300, 

700 and 800 


systems. 

CPCommOS 

Note: 


2R2 is used 

only with 

Dorado 400 

systems. 


Note: 


4R2A is used 

only with 

Dorado 

4000/4100 and 

4200 Series 

systems. 

CryptoLib 

Note: 

CPComm 6R2 

does not build 

or run unless 

CryptoLib is 

installed. 

6R2 CP-FLD A 

AFCB 

CMSA-CPCA 

2R2 CP- 

FLD400 

A 

4R2A CP-FLD A 

AFCB 

CMSA-CPCA 

XNIOP 

If you use CPComm and installation modes other than 

A, AFCB, and CMSA-CPCA delivered on fast-load tape 

CP-FLD, install CPComm for the other installation 

modes from package tape CP-COMMSUITE, after the 

product key tape has been registered (step 4). 

The ClearPath OS 2200 13.2 level of CPCommOS 

4R2A is incompatible with the Plateau that is available 

on the Dorado 400 systems. Those systems must 

continue to use the CPCommOS 2R2 level. The 

CPCommOS 2R2 product is included on the 

CP-FLD400 fast-load tape for installation. See section 

“7.10 Migration for Existing Dorado 400 Customers” 

for additional Dorado 400 specific migration 

considerations. 

The ClearPath OS 2200 13.2 Release introduces 

migration dependencies for the Dorado 4000 and 4100 

systems. Before beginning migration, refer to the 

following sections for migration considerations: 

• 3.12 ClearPath and Plateau Interdependencies 

• 7.9 Migration for Existing Dorado 4000 Customers 

• 7.11 Migration for Existing Dorado 4100 

Customers 

If you use CPCommOS and installation modes other 

than A, AFCB, CMSA-CPCA and XNIOP delivered on 

fast-load tape CP-FLD, install CPCommOS for the 

other installation modes from package tape CP- 

COMMSUITE, after the product key tape has been 

registered (step 4). 

1R1 CP-FLD LIB The CryptoLib product is required by CPComm 6R2 

and Cipher-API 2R2 for installation. If CryptoLib is not 

installed on your ClearPath 13.2 system, CPComm and 

Cipher-API terminate in error at initialization. 

FURPUR 32R5B CP-FLD A 

PCFP 3R3A CP-FLD A 

Note: CPCommOS does not require CryptoLib. 

ROLRUNS 4R3 CP-FLD A ROLRUNS is needed to ensure the Exec can be placed 

on the DRS device. 

SILAS 3R2B CP-FLD A CPComm requires SILAS for the demand connection. 

7831 0349–043 7–9


Installation 


Name 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

Notes 

SOLAR 4R7A CP-FLD A SOLAR is needed to register the product key tape. 

SYSLIB 76R4 CP-FLD A 

4. Start the REGISTERPKG runstream to register the ClearPath OS 2200 Release 13.2 

product key tape using the SOLAR level received with this release. A key tape is 

registered using the same steps as registration for a package tape. The registration 

summary report will display all new product authorizations added to the system. See 

the file SOLAR*DIAGNOSTIC! 

Note: When SOLAR 4R7 or above is first used and any key is registered (software 

product key or Exec key), the SYS$*DATA$ KEYTABLE$ format is extended to 

version 8 and is not recognized by previous levels of SOLAR or Exec levels that do 

not have PLE 18756811 applied. The ability to use SOLAR 4R7A on previous Exec 

levels is required for crossbooting. 

Use of a SOLAR 4R7 or above KEYGEN created Exec key can only be used on an 

Exec which recognizes the new SOLAR keytable version 8 expanded definitions. 

5. For metering-based systems 

First install the Windows component of URU-OS2200. This installation converts the 

URU database to the new format. When the Windows installation is complete, install 

the OS 2200 component of URU-OS2200 (CP05). 

After URU-OS2200 level 5.1 is installed, you cannot revert back to a pre-URU-2200 

4.0 level. URU-OS2200 level 5.1 can collect previous COD log data entries created 

by previous levels of the Exec, if it is necessary to revert back to a previous Exec. 

6. Prepare the ClearPath OS 2200 Release 13.2 versions of the five library files: 

MCODE$, LIB$, RUN$, RLIB$, and PRINTER$. All five files are required for system 

generation, regardless of system type. Either copy the files from the release master 

tape to another tape or catalog five mass storage files and copy the library files into 

them (one library file per mass storage file). Refer to the Exec System Software 

Installation and Configuration Guide for the specific runstreams to use. 

Notes: 

• You can use the POSTOEXMSTR utility to position the package tape to the first 

file of the Exec Release Master files. 

• The MCODE$ file is empty. This file is still needed, however. 

• The Exec level 48.0 base symbolic tape has three files: Utility, Base Symbolics, 

and the last 47-level PCF file. The PCF file on the base symbolic tape is needed 

to upgrade 47-level local code. The file name EXEC48-PCF47*PCF$. 

distinguishes the 48R1 PCF file from the 47-level PCF file. 

7. Install the separately packaged Exec features that your site has ordered from the 

CP-SPF tape. See Appendix C for a listing of the Exec features on the CP-SPF tape. 

7–10 7831 0349–043

Caution 


Unisys recommends that you perform an INSPECT generation before a FULL 

or CONFIGURATION generation. The INSPECT generation allows you to 

simulate an actual system generation to ensure that there are no syntactical 

errors. The INSPECT generation checks all the skeletons for errors without 

stopping in a skeleton that contains a fatal error. This process detects more 

errors using fewer trial-and-error passes. 

8. Generate Exec level 48R8A (ClearPath OS 2200 Release 13.2). During system 

generation, all SGS configuration labels found in the CO$CONFIG element are 

compared to a list of valid configuration SGSs. See 4.2 for a listing of any obsolete 

SGS configuration labels that should be removed. 

If an invalid SGS is detected, the following error occurs and the system generation 

stops: 

ERROR - CO$CONFIG SGS LABEL name 



THE OBSOLETE SGS(S), OR CORRECT THE IMBEDDED SEMICOLON! 

See 4.2.1 for more information about generating boot tapes for the correct system 

type. 

9. If your site requires a customized TIPUTIL, build the level of TIPUTIL that 

corresponds to the target Exec level using the CP-TRN tape. 

Notes: 

• TIPUTIL generations require the RLIB$ file that corresponds to the target Exec 

level. If you generate your TIPUTIL on the target Exec level, it includes the 

correct RLIB$ file. To prebuild your TIPUTIL system on your current system 

before migration to the target Exec level (as in this migration scenario), use the 

RLIB$ SGS to specify the location of the target Exec’s RLIB$ file. For details on 

using the RLIB$ SGS, see Configuring TIP in the Exec System Software 

Installation and Configuration Guide. 

• TIPUTIL requires ASCII FORTRAN Compiler (FTN) and C Compiler (UC) to build. 

ASCII FORTRAN Compiler is delivered with the CSW20-BLD style. See 3.9 for 

more information. C Compiler is part of the IOE. 

10. Boot the Exec. When you boot the system, you are loading the Exec from the boot 

tape and then initializing the system. 

Unisys recommends that all sites use jump key 4 to reload libraries. 

For additional information on booting the Exec, refer to the Exec System Software 


7831 0349–043 7–11


11. Install the products contained on fast-load tape CP-OE1A using the INSTALLPKG 

runstream. Products on the tape are DAP, DMPLIB, OLTP-TM2200, Security-Admin, 

and SIMAN. 

Install FLIT Mode A from tape CP07. 

Note: EXEC dumps taken on any level should always be processed with the levels 

of DAP and DMPLIB corresponding to that release. Older levels of DAP and 

DMPLIB may not recognize changes made in newer EXEC levels. 

12. Install TIPUTIL. If you have created a customized TIPUTIL tape, install it. 

Otherwise, install the default mode of TIPUTIL, MCB, and DPS from the CP-OE2 

tape using the INSTALLPKG runstream. 

Note: You should install the TIPUTIL level that corresponds with the target Exec 

level. Previous levels of TIPUTIL might not be compatible with the target Exec level. 

13. Install CIFS. 

14. Install the products contained on the fast-load tape CP-OE1B using the 

INSTALLIOE runstream. See Appendix C for the contents of this tape. 

Notes: 

• The CP-OE1B tape includes the linking system (LINK). It is important that you 

deactivate all active subsystems that require ongoing LINK services whenever 

LINK is replaced. To do this, you can either explicitly deactivate the subsystems, 

or you can do an autorecovery through a $! keyin after installing the new level of 

LINK. See 5.27 for more information. 

• When you install a new level of LINK, ELMS must be installed at the same time 

to ensure that the ELMS subsystem is loaded by the new LINK. 

• Check the IPF 1100 Administration Guide for configuration considerations when 

installing IPF-compatible products (for example, DDP-FJT or TAS). 

• DDP-PPC must be properly conditioned for the system security environment. 

See 5.14. 

• DDP-PPC 7R3A requires the following configuration changes be applied to run 

on a Dorado 400 system with CPCommOS 2R2: 



15. Install, configure, and boot OPE. 

16. Install the remainder of the products, including optional products, from package 

tapes using the order of product installation identified in the following steps. 

The following steps describe the installation of product sets. You can select either of 

two methods to install these products. 

• Use the INSTALLPKG runstream to install the default mode of all authorized 

products from any package tape. 

7–12 7831 0349–043

Installation 


Name 


• Use the SOLAR full-screen interface to register and install specific products and 

modes from each registered package tape. Start SILAS and CPComm to activate 

a demand terminal. 

17. Install the following set of products. 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

CKRS 7R8A CP05 COMMON 

BANK 

FLEX 4R3 CP05 NOAUTO 

Notes 

TUTIL 1R1B CP05 A If you currently have SAUTILITIES installed and you 

want to install TUTIL, you must remove 

SAUTILITIES using the PRODRV utility, or install 

TUTIL in mode TEST. For more TUTIL information, 

refer to “Tape Labeling Utility for ClearPath 

OS 2200 (TUTIL)” in Section 5. 

UFTN 11R1B CP08 A 

UCOB 12R1F CP08 A 

ACOB 7R3K CP09 D 

FTN 11R2X CP09 AFCB 

Installation 


Name 

18. Install the following set of products. Before you install these products, the 

associated background runs should be terminated. After successful installation and 

adjustments, the associated background runs can be restarted. 

Note: The installation of tapes CP10 and CP11 might report PRODLD warnings. 

This occurs due to the relation between IPF and DDP-FJT and IPF and TAS. A 

COMUS CONFIG of IPF is required. See the IPF 1100 Administration Guide. 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

DDP-FJT 5R5I CP10 A 

cpFTP 3R5A CP11 A 

Notes 

TAS 6R2I CP11 B TAS may require a post-installation procedure 

before it functions correctly. See the TCP/IP 

Application Services (TAS) Implementation and 

Administration Guide. 

DPS 6R5A CP11 A If you already installed the CP-OE2 tape, you do not 

need to reinstall DPS. 

19. If you have not already installed MCB, install MCB from the CP-TRN tape into 

APPL3. 

7831 0349–043 7–13


Installation 


Name 


Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

Notes 

UDSC 17R2 CP13 AP3 You must have APP 3 up and IRU short recovered. 

For important additional considerations regarding the 

Universal Data System suite of products, refer to the 

Universal Data System Planning and Installation 

Overview and the Universal Data System 

Configuration Guide. 

RDMSKEY 17R2 CP15 A If you already installed the CP-OE1B tape, you do not 

need to reinstall RDMSKEY. 

RDMS 17R2 CP15 A 

DMSKEY 21R2 CP14 A 

DMS 21R2 CP14 NOREGISTER 

DMS-RA 4.0 CP14 A 

UREPKEY 13R2 CP16 A 

UREP 13R2 CP16 A The installation user-id must be the same as the UREP 

security officer. 

RDMS-JDBC 2.7 CP15 A 

QLP 7R3B CP16 AFCB-DMS-P 

SFS 4R1 CP16 COLLECTOR 

Installation 


Name 

Application group 3 must be up and recovered before 

you install UREP. 

21. Install the products for which you are authorized from the following set. 

Note: If you are authorized for TeamQuest Baseline, do not use the INSTALLPKG 

runstream to install CP18. TeamQuest Baseline and TeamQuest Online are mutually 

exclusive. 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

MSAR 7R7B CP18 A 

CULL 5R1A CP18 A 

IACULL 5R1A CP18 A 

Notes 

SAUTILITIES 6R6 CP18 A If you currently have SLRR or TUTIL installed and you 

want to install SAUTILITIES, you must remove SLRR 

and TUTIL using the PRODRV utility. For more TUTIL 

information, refer to“Tape Labeling Utility for ClearPath 

OS 2200 (TUTIL)” in Section 5. 

MSMANAGER 5R7F CP18 A 

7–14 7831 0349–043

Installation 


Name 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

LA 7R6A CP18 A 

OSAM 7R5 CP18 A 

PAR 9R2 CP18 A 

Installing from Package Tapes 

Notes 

TQ-BASELINE 7R4F CP18 A TQ-ONLINE and TQ-BASELINE are mutually exclusive. 

TQ-ONLINE 7R4F CP18 A TQ-ONLINE and TQ-BASELINE are mutually exclusive. 

TQD-FRAGGER 4R1D CP18 A 

TQRDFRAGGER 4R1D CP18 A 

TIP-LA 1R4E CP18 A 

TQ-PMLOG 7R4B CP18 A 

TQ-PROBES 7R4D CP18 A 

22. Install your remaining products. 

Notes: 

• Use the SOLAR PKGREG Key Package Summary Report produced when the key 

tape was registered to determine which products remain. 

• See Appendix C for the tape names of these products. 

7.7. Installing from Package Tapes 

The following sequence is intended for those sites that are moving from ClearPath 

OS 2200 Release 12.0 or higher to ClearPath OS 2200 Release 13.2 and choose to install 

the products from package tapes. If you install the products in the exact order presented 

here, you will avoid possible interdependency conflicts. 

With this sequence, you install the first-load (CP-FLD) tape before building and booting 

the Exec. While building your ClearPath OS 2200 Release 13.2 Exec, you must install any 

separately packaged Exec features that your site has ordered from the CP-SPF tape. 

Notes: 

• This installation sequence uses the logical package name. See C.1 for more 

information. 





7831 0349–043 7–15





products (including the EXEC). Refer to sections “7.9 Migration for Dorado 4000”, 



Following are the recommended steps: 

1. There are three migration issues that may affect cross-booting between EXEC 48R8 

and older EXEC levels. These issues may require that PLEs be generated into your 

older EXEC level and booted before you move up to EXEC 48R8. If you drop back 

from EXEC 48R8 to your older EXEC level, you must always drop back to an EXEC 

level that includes these PLEs. See Table 7–2 for the required migration information. 

A check mark in the table indicates that an action must be taken. 

Note: If you are migrating to this release from a release prior to 12.0 there may be 

other important cross-boot considerations that are no longer documented here. To 

perform a migration from a release prior to 12.0 you should consult the Planning and 

Migration Overview documentation associated with release 12.0 and possibly 

additional prior releases to ensure that any migration issues introduced by all of the 


There are no cross-boot or migration issues between Exec 48R8 (ClearPath OS 2200 

Release 13.1) and Exec 48R8A (ClearPath OS 2200 Release 13.2). Exec 48R7 already 

includes all the necessary PLEs. Systems running Exec levels prior to 48R7 should 

add the necessary PLEs before booting Exec 48R8. 

a. KEYTABLE$ Migration Code 


consideration. You must build and boot your current Exec to integrate the 

changes in PLE 18756811. These fixes are required in order for the Exec to 

recognize the new enhanced version of the system key table written by SOLAR 

level 4R7 or higher. You must update and boot your current EXEC to include this 

KEYTABLE$ migration code before installing SOLAR level 4R7A. FURPUR level 

32R5B must also be installed. 

A SOLAR level 4R7 or higher KEYGEN-created key can only be used on an Exec 

that recognizes the new key table version. When SOLAR level 4R7 or higher is 

first used to register any key, the SYS$*DATA$.KEYTABLE$ is written in the 

new format which is not recognized by previous levels of SOLAR or the Exec. 



higher. 

7–16 7831 0349–043


b. Cross-boot consideration for Dorado 400 and Dorado 4000 

systems 

A known problem may prevent existing Dorado 400 or Dorado 4000 systems 

from being able to boot ClearPath OS 2200 Release 13.2 EXEC level 48R8A. This 

issue can only arise if the EXEC level you are currently running is 48R4 

(ClearPath OS 2200 Release 12.0). EXEC levels 48R5 and above already contain 

the necessary change. If you are a Dorado 400 or Dorado 4000 customer and are 

running EXEC level 48R4, you must build and boot PLE 18691159 before you 

make any attempt to boot EXEC level 48R8. 

Table 7–2. Migration Requirements for Package Tapes 

Migrating to Release 13.2 (EXEC 48R8A) From… 

Required Action Release 12.0 

(Exec 48R4) 

KEYTABLE$ Migration 

code PLE 18756811 

Cross-boot 

consideration for 

Dorado 400 and 

Dorado 4000 systems 


Plus (Exec 

48R5) 


(Exec 48R6) 


(Exec 48R7) 

√ √ √ No action 

required 

√ No action 

required 

No action 

required 

No action 

required 

Release 

13.1 (Exec 

48R8) 

No action 

required 

No action 

required 

2. Perform a LIBSAVE of your current system. See 5.43 (SOLAR considerations) for 














products. 

Note: If you use the full-screen interface for installing CP-FLD, CP-FLD400 or CP01 

products, sign off from your demand terminal and wait until the batch install runstream 

finishes. Then, reenter the full-screen interface and continue with your installation. 

7831 0349–043 7–17



Support Name 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

Notes 

COMUS 6R9A CP-FLD A COMUS is needed to generate the Exec 

CPComm 

Note: 

CPComm is 

used only with 

Dorado 300, 700, 

and 800 Series 

systems. 


Note: 


2R2 is used only 

with Dorado 

400 systems. 


Note: 


4R2 is used only 

with Dorado 

4000/4100 and 


systems. 

CryptoLib 

Note: CPComm 

6R2 does not 

build or run 

unless CryptoLib 

is installed. 

6R2 CP-FLD A 

AFCB 

CMSA-CPCA 

2R2 CP- 

FLD400 

4R2A CP-FLD A 

AFCB 

CMSA-CPCA 

XNIOP 

A 

If you use CPComm and installation modes other than A, 

AFCB, and CMSA-CPCA delivered on fast-load tape CP- 

FLD, install CPComm for the other installation modes 

from package tape CP-COMMSUITE, after the product 

key tape has been registered (step 4). 

The ClearPath OS 2200 13.2 level of CPCommOS 4R2A 

is incompatible with the Plateau that is available on the 

Dorado 400 systems. Those systems must continue to 

use the CPCommOS 2R2 level. The CPCommOS 2R2 

product is included on the CP-FLD400 fast-load tape for 

installation. See section “7.10 Migration for Existing 

Dorado 400 Customers” for additional Dorado 400 

specific migration considerations. 








If you use CPCommOS and installation modes other than 

A, AFCB, CMSA-CPCA and XNIOP delivered on fast-load 

tape CP-FLD, install CPCommOS for the other installation 



1R1 CP-FLD LIB The CryptoLib product is required by CPComm 6R2 and 

Cipher-API 2R2 for installation. If CryptoLib is not installed 

on your CP 13.2 system, CPComm and Cipher-API 

terminate in error at initialization. 




ROLRUNS 4R3 CP-FLD A ROLRUNS is needed to ensure the Exec can be placed 

on the DRS device. 

SILAS 3R2B CP-FLD A CPComm requires SILAS for the demand connection. 



7–18 7831 0349–043



product key tape using the SOLAR level received with this release. A key tape is 

registered using the same steps as registration for a package tape. The registration 

summary report will display all new product authorizations added to the system. See 

the file SOLAR*DIAGNOSTIC. 

Note: When SOLAR 4R7 or above is first used and any key is registered (software 

product key or Exec key), the SYS$*DATA$ KEYTABLE$ format is extended to 

version 8 and is not recognized by previous levels of SOLAR or Exec levels that do 

not have PLE 18756811 applied. The ability to use SOLAR 4R7A on previous Exec 

levels is required for crossbooting. 

Use of a SOLAR 4R7 or above KEYGEN created Exec key can only be used on an 

Exec which recognizes the new SOLAR keytable version 8 expanded definitions. 


First install the Windows component of URU-OS2200. This installation converts the 

URU database to the new format. When the Windows installation is complete, install 

the OS 2200 component of URU-OS2200 (CP05). 




6. Prepare the ClearPath OS 2200 Release 13.2 versions of these library files: 






Notes: 



• The MCODE$ file is empty; however, this file is still needed. 



to upgrade 47-level local code. The file name EXEC48-PCF47*PCF$. 



CP-SPF tape. Refer Appendix C for a listing of the Exec features on the CP-SPF tape. 

Caution 







7831 0349–043 7–19



generation, all SGS configuration labels in the CO$CONFIG element are compared to 

a list of valid configuration SGSs. See 4.2 for a listing of any obsolete SGS 

configuration labels that should be removed. 


stops: 





See 4.2.1 for more information about generating boot tapes for the correct system 

type. 


corresponds to the target Exec level using the CP-TRN tape. 

Notes: 

• TIPUTIL generations require the RLIB$ file which corresponds to the target Exec 

level. If you generate your TIPUTIL on the target Exec level, it will include the 

correct RLIB$ file. To prebuild your TIPUTIL system on your current system 

before migration to the target Exec level, use the RLIB$ SGS to specify the 

location of the target Exec’s RLIB$ file. For details on using the RLIB$ SGS, see 

Configuring TIP in the Exec System Software Installation and Configuration 

Guide. 

• TIPUTIL requires ASCII FORTRAN Compiler (FTN) and C Compiler (UC) to build. 

ASCII FORTRAN Compiler is delivered with the CSW20-BLD style. See 3.9 for 

more information. C Compiler is part of the IOE. 

10. Boot the Exec. When you boot the system, you are loading the Exec into the system 

from the boot tape and then initializing the system. 

Unisys recommends that all sites use jump key 4 to reload libraries. 



11. Install DAP from tape CP02, FLIT from tape CP07, and DMPLIB from the tape CP05. 

Note: EXEC dumps taken on any level should always be processed with the levels 

of DAP and DMPLIB corresponding to that release. Older levels of DAP and DMPLIB 

may not recognize changes made in newer EXEC levels. 

7–20 7831 0349–043

Installation 


Name 

Security- 

Admin 

12. To administer security, install the following set of products. 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

4R3 CP05 A 

SIMAN 6R6 CP18 SEC 

CIFS 7R3 CPO4 NORMAL 

Installation 


Name 


Notes 

13. Use the INSTALLPKG runstream to install the default modes of URTS, LINK, 

I18NLIB, and ELMS. 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

URTS 13R3A CP02 AFCB 

LINK 12R2B CP03 A 

I18NLIB 2R2 CPO2 A 

Notes 

ELMS 3R1B CP03 A You must install I18NLIB (CP02) before you execute 

ELMS. 

Notes: 

• It is important that you deactivate all active subsystems that require ongoing 

LINK services whenever LINK is replaced. To do this, you can either explicitly 

deactivate the subsystems, or you can do an autorecovery through a $! keyin 

after installing the new level of LINK. See Linking System considerations in 5.27 

for more information. 



14. Install TIPUTIL. If you have created a customized TIPUTIL tape in step 9, install that 

TIPUTIL. 

Note: You must install the TIPUTIL level that corresponds with the target Exec 



The following steps describe the installation of product sets. Use either of the 

following methods to install these products. 






7831 0349–043 7–21


Installation 


Name 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

MAP 33R1M CP02 AFCB-FREE 

ED 16R1F CP02 A 

ELT 8R3C CP02 A 

FAS 10R5A CP02 A 

SSG 24R2A CP02 A 

MASM 6R3J CP02 A 

SLIB 1R5I CP02 A 

PDP 13R2D CP02 AFCB 

LST 4R1J CP02 A 

CML 1R1J CP02 A 

UCSRTS 1R1M CP02 A 

Notes 

RSS 3R2N CP02 A After installing RSS, attach transfer files to RSS. They 

cannot be transferred until DDP-PPC (CP10) is 

installed. 

CMR 2R6 CP04 A 

COMAPI 7R3A CP-OE1B A CP-OE1B or CP-COMMSUITE. 

PMD 32R2F CP04 A 

MSCP 3R8D CP04 A See 4.1.3 for additional considerations. 

CKRS 7R8A CP05 Common bank 


TUTIL 1R1B CP05 A If you currently have SAUTILITIES installed and want to 

install TUTIL, remove SAUTILITIES using the PRODRV 

utility or install TUTIL in mode TEST. For more TUTIL 

information, refer to “Tape Labeling Utility for 

ClearPath OS 2200 (TUTIL)” in Section 5. 

DPREP1100 10R7E CP04 A 

PADS 13R3C CP05 AFCB 

16. Install, configure, and boot OPE. 

7–22 7831 0349–043

Installation 


Name 


Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 


Notes 

LSS 14R3A CP06 A LSS and the UCS Compilers must be at the same 

ClearPath OS 2200 Release level. 

PLUS 8R2O CP07 AFCB 

UC 10R3A CP07 A 

UPLS 8R1D CP08 DEFAULT 



PCIOS 7R1B CP09 A 

SORT 22R2D CP09 A 



Installation 


Name 

18. If you did not install MCB or CITA when you installed TIPUTIL from the CP-TRN tape, 

install MCB and CITA now. MCB installs into APPL3. 

19. Install the following set of products. Before you install these products, the 

associated background runs should be terminated. After successful installation and 

adjustments, the associated background runs can be restarted. 




Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

Notes 

IPF 7R1D CP10 A Check the IPF 1100 Administration Guide for 

configuration considerations when installing IPFcompatible 

products (for example, DDP-FJT or TAS). 

DDP-PPC 7R3A CP10 A • DDP-PPC must be properly conditioned for the 

system security environment. See 5.14. 


• If you are migrating a Dorado 400 system and 

run CPCommOS 2R2, you can either run 

DDP-PPC level 7R2E or make the following 

configuration changes to DDP-PPC 7R3A: 

The CPMODE keyword in the OSITSU and 

TASTSU records of the DDP-PPC 

configuration file must be set to CMSA 

(CPMODE=CMSA). 

7831 0349–043 7–23


Installation 


Name 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 


GSA 6R2D CP11 A 

Notes 

TAS 6R2I CP11 B TAS may require a post-installation procedure before 

it functions correctly. See the TCP/IP Application 

Services (TAS) Implementation and Administration 

Guide. 

DPS 6R5A CP11 A 

NTSI 7R3A CP11 A 

JVM 5R1 CP12 A The CIFS background run must be active when you 

install JVM. 

Installation 


Name 


Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

Notes 

IRU 20R2 CP13 IRU Install the additional MODE FSAH if required. 


RDMSKEY 17R2 CP15 A 









Overview and the Universal Data System 

Configuration Guide. 

UREP 13R2 CP16 A The installation user-id must be the same as the 

UREP security officer. 






7–24 7831 0349–043

Installation 


Name 


Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

CIPHER-API 2R2 CP17 A 

OLTP- 

TM2200 

12R1C CP17 A 

OSI-TP 9R1H CP17 A 

WEBTS 5R9 CP17 A 


Support Name 


Notes 




exclusive. 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 




Notes 




information, see 5.47. 









TQ-PMLOG 7R4B CP18 A 

TQ-PROBES 7R4D CP18 A 


7831 0349–043 7–25

Initializing an Existing System (I-Boot) 

23. Install your remaining products. 

Notes: 

• Use the SOLAR PKGREG Key Package Summary Report produced when the key 


• See Appendix C for the tape names of these products. 

7.8. Initializing an Existing System (I-Boot) 

System initialization is initiated when there are no files on fixed mass storage to be 

saved. It is typically used in test scenarios, and with mass storage specifically reserved 

for test purposes, or for setting up a new and previously unused environment. In very 

infrequent cases, system initialization might be initiated to boot a system to an initialized 

or clear state in preparation for reloading data that was lost due to a catastrophic event. 

This subsection provides a procedure for installing your ClearPath OS 2200 Release 13.2 

suite of products with an initial boot. With this sequence, you boot the system with the 

supplied boot tape. You can use this environment for further system enhancements, 

such as tailoring the OS 2200 operating system, TIP, and MCB. 

In this procedure, you use fast-load and package tapes to install your products. Because 

of the many product and feature interdependencies, do not randomly install ClearPath 

OS 2200 Release 13.2 software. Although some flexibility is allowed, this recommended 

installation order should be observed as closely as possible. 

In this sequence, the following fast-load tapes are used: CP-FLD, CP-FLD400, CP-OE1A, 

CP-OE1B, and CP-OE2 (see descriptions in 7.4). 

Notes: 





• Once IOE products have been installed from the fast-load tape, they need not be 

reinstalled from a package tape unless the site wishes to customize the installation. 

• If you encounter any difficulties when following this installation sequence, contact 

your Unisys Support Center. 

Installation Sequence 

Caution 

Failure to read and apply the installation considerations described in 7.2 might 

cause the following installation sequence to fail. 

7–26 7831 0349–043


Note: This installation sequence uses the logical package name. See C.1 for more 

information. 

The recommended steps are as follows: 

1. For metering based systems, prior to performing the I-Boot, ensure all existing COD 

Log entries have been harvested from the OS 2200 system by URU-OS2200. COD 

Log entries are created every minute. Stop the system within a minute after a 

harvest completes. Harvests occur every 15 minutes or can be forced by stopping 

and then starting the URU Windows Service. A harvest is performed immediately 

after the URU-OS2200 Service is started. 

2. Boot the Exec using the supplied boot tape. Set jump keys 4, 7, and 13. When you 

boot the system, you are loading the Exec into the system from the boot tape and 

then initializing the system. 

Note: Enter N in response to the TIP INITIALIZATION message. 















products. 

Note: If you use the full-screen interface for installing CP-FLD, CP-FLD400 or CP01 

products, sign off from your demand terminal and wait until the batch install 

runstream finishes. Then, reenter the full-screen interface and continue with your 

installation. 

7831 0349–043 7–27


Installation 


Name 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

Notes 

COMUS 6R9A CP-FLD A COMUS is needed to generate the Exec. 

CPComm 

Note: 

CPComm is 

used only 

with Dorado 

300, 700, and 


systems. 


Note: 


2R2 is used 

only with 

Dorado 400 


systems. 


Note: 


4R2A is used 

only with 

Dorado 

4000/4100 

and 4200 


systems. 

CryptoLib 

Note: 

CPComm 6R2 

does not build 

or run unless 

CryptoLib is 

installed. 

6R2 CP-FLD A 

AFCB 

CMSA-CPCA 

2R2 CP- 

FLD400 

4R2A CP-FLD A 

AFCB 

CMSA-CPCA 

XNIOP 

A 

If you use CPComm and installation modes other than A, 

AFCB, and CMSA-CPCA delivered on fast-load tape CP- 

FLD, install CPComm for the other installation modes 

from package tape CP-COMMSUITE after the product key 

tape has been registered (step 5). 

The ClearPath OS 2200 13.2 level of CPCommOS 4R2A is 

incompatible with the Plateau that is available on the 

Dorado 400 systems. Those systems must continue to 

use the CPCommOS 2R2 level. The CPCommOS 2R2 

product is included on the CP-FLD400 fast-load tape for 

installation. See section “7.10 Migration for Existing 

Dorado 400 Customers” for additional Dorado 400 

specific migration considerations. 








If you use CPCommOS and installation modes other than 

A, AFCB, CMSA-CPCA and XNIOP delivered on fast-load 

tape CP-FLD, install CPCommOS for the other installation 



1R1 CP-FLD LIB The CryptoLib product is required by CPComm 6R2 and 

Cipher-API 2R2 for installation. If CryptoLib is not 

installed on your CP 13.2 system, CPComm and Cipher- 

API terminate in error at initialization. 




ROLRUNS 4R3 CP-FLD A ROLRUNS is needed to ensure the Exec can be placed on 

the DRS device. 

SILAS 3R2B CP-FLD A SILAS is needed to run a demand session. SILAS requires 

CPComm (including mode AFCB) to access the network. 



7–28 7831 0349–043


4. Start the REGISTERPKG runstream to register the supplied Exec key tape (labeled 

“Software Controlled Performance Key Tape”) to establish the contracted 

performance level for the system. For more information about Software Controlled 

Performance (SCP), see 4.8. 


product key tape. A key tape is registered using the same steps as registration for a 

package tape. The registration summary report will display all new product 

authorizations added to the system. See the file SOLAR*DIAGNOSTIC. 


First install the client component of URU-OS2200. This installation converts the URU 

database to the new format. When the client installation is complete, install the 

ClearPath OS 2200 component of URU-OS2200 level 5.1 from package tape CP05. 




7. Install the products on fast-load tape CP-OE1A using the INSTALLPKG runstream 

and CP-OE1B using the INSTALLIOE runstream. See Appendix C for the contents of 

those tapes. 

You can selectively install products (in default mode) from either tape using SOLAR. 

If you choose to do so, you should follow the order of installation as described in 7.7. 

Notes: 

• Do not install LINK until URTS, SLIB, and SYSLIB have been installed. If you are 

installing the products from the CP-OE1B tape, the INSTALLIOE runstream does 

this for you. 

• The CP-OE1B tape includes LINK. It is important that you deactivate all active 

subsystems that require ongoing LINK services whenever LINK is replaced. To 

do this, you can either explicitly deactivate the subsystems, or you can do an 

autorecovery through a $! keyin after installing the new level of LINK. See 5.27 

for more information. 



• The INSTALLPKG runstream for CP-OE1A and the INSTALLIOE runstream for 

CP-OE1B will present warning messages because ELMS has not been installed 

on the system. These warnings can be ignored, as they will be resolved when 

ELMS is installed during the installation of the CP-OE1B Fast Load tape. 

**WARNING* PRODLD 23015: 

The location of ELMSs processor, MDBREG, could not be ascertained 

because ELMS was not installed. The Extended Language Message 

System’s search chain could not be updated. 

• Check the IPF 1100 Administration Guide for configuration considerations when 

installing IPF-compatible products (for example, DDP-FJT or TAS). 

• DDP-PPC must be properly conditioned for the system security environment. 

See 5.14. 

7831 0349–043 7–29


• If you are migrating a Dorado 400 system, DDP PPC 7R3A requires the following 

configuration changes to run on a Dorado 400 system with CPCommOS2R2: 



• For ClearPath OS 2200 Release 13.2 platform installation, the products on tapes 

CP13, CP14, or CP16 are usually customized prior to installation. The products 

on these package tapes can be installed after the platform is established. 

8. Install, configure, and boot OPE. Then take one of the following steps: 

• If you plan to customize the Exec, TIPUTIL, DPS, and MCB, continue with step 9 

of this installation sequence. 

• If you do not plan to customize the Exec, TIPUTIL, DPS, and MCB, go to step 14. 

You can use the CP-OE2 tape to install DPS, TIPUTIL, and MCB in default mode. 

9. Prepare the ClearPath OS 2200 Release 13.2 versions of these library files: 






Notes: 



• The MCODE$ file is empty. This file is still needed, however. 



to upgrade 47-level local code. The file name EXEC48 PCF47*PCF$. 



CP-SPF tape. See Appendix C for a listing of the Exec features on the CP-SPF tape. 


generation, all SGS configuration labels found in the CO$CONFIG element are 

compared to a list of valid configuration SGSs. See 4.2 for a listing of any obsolete 

SGS configuration labels that should be removed. 


stops: 





7–30 7831 0349–043


Caution 







12. Before building TIPUTIL, you must install the products delivered with the 

IXS 4000-BLD or CSW20-BLD style first. These products are ACOB, FTN, UC, 

UCOB, and UFTN. See 3.9 for more information. 


corresponds to the target Exec level using the CP-TRN tape. Likewise, if your site 

needs to build MCB, build MCB using the CP-TRN tape. 

Note: You must build using the TIPUTIL level that corresponds with your target 

Exec level. 

14. Perform a jump key 4,7 boot to tape recover your system using the newly created 

Exec boot tape from step 11. 

Note: Enter Y in response to the TIP INITIALIZATION message. 

15. Install TIPUTIL and MCB by using either 

• The TIPUTIL and MCB you built in step 13. 

• The APP3 default TIPUTIL and MCB on the CP-OE2 or CP-TRN tapes. 

Note: You should install the TIPUTIL level that corresponds with the target Exec 



The following steps describe the installation of product sets. You can select either of 

two methods to install these products. 






Notes: 

• If you have previously installed the products delivered with the IXS 4000-BLD or 

CSW20-BLD style, you do not need to install ACOB, FTN, UCOB, and UFTN as 

indicated in the following table. 

• If you have previously installed IRU from the CP-OE1B tape, you do not need to 

install it as indicated in the following table. 

7831 0349–043 7–31


Installation 


Name 

Level 

Logical 

Tape 

Name 

Default 

Installation Mode 

IRU 20R2 CP13 IRU 

CKRS 7R8A CP05 COMMONBANK 


Notes 

TUTIL 1R1B CP05 A If you currently have SAUTILITIES installed and 

you want to install TUTIL, you must remove 

SAUTILITIES using the PRODRV utility or install 

TUTIL in mode TEST. For more TUTIL 

information, refer to “Tape Labeling Utility for 

ClearPath OS 2200 (TUTIL)” in Section 5. 

FLIT 14R2 CP07 A 





Installation 


Name 





Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 



Notes 

TAS 6R2I CP11 B TAS may require a post installation procedure before 

it functions correctly. See the TCP/IP Application 

Services (TAS) Implementation and Administration 

Guide. 

DPS 6R5A CP11 A If you already installed the CP-OE2 tape, you do not 

need to reinstall DPS. 

7–32 7831 0349–043

Installation 


Name 


Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 


Notes 





Overview and the Universal Data System Configuration 

Guide. 

RDMSKEY 17R2 CP15 A If you already installed the CP-OE1B tape, you do not 

need to reinstall RDMSKEY. 






UREP 13R2 CP16 A The installation user-id must be the same as the UREP 

security officer. See Section 4 of the Installation Guide 

for installation requirements. 






7831 0349–043 7–33



Support Name 




exclusive. 

Level 

Logical 

Tape 

Name 

Default 

Installation 

Mode 

Notes 

SIMAN 6R6 CP18 SEC If you already installed the CP-OE1A tape, you do not 

need to reinstall SIMAN . 







information, see 5.47. 










20. You can now tailor the ClearPath OS 2200 Release 13.2 initial system platform for 

the following: 

• Other software installation (including nonkeyed media/products). Refer to the 

Software Products Installation Guide. 

• The SOLAR PKGREG Key Package Summary Report produced when the key 


• OS 2200 Exec. Refer to the Exec System Software Installation and Configuration 

Guide. 

• Transaction Processing (TIP). Refer to the Transaction Processing Administration 

and Operations Reference Manual. 

• Message Control Bank (MCB). Refer to the MCB Installation Guide. 

7–34 7831 0349–043

Migration for Existing Dorado 4000 Customers 

• IRU. Refer to the Integrated Recovery Utility Administration Guide, Universal 

Data System Configuration Guide, and Universal Data System Planning and 

Installation Overview. 

• Security. Refer to the Security Administration for ClearPath OS 2200 Help. 

21. Reestablish the system profile. To do this, you must restore the file that contains the 

system profile information and then perform a system recovery. This causes the 

EXEC to read the system profile information from this file to reestablish the system 

profile. 

7.9. Migration for Existing Dorado 4000 Customers 

For Dorado 4000 systems, ClearPath OS 2200 Release 13.2 is tightly paired with Plateau 

2.3 and the ClearPath 13.1 Dorado 4000 Compatibility Package which contains the 

2.3-CP13.1-4000-COMPATIBILITY.sup file. If your system is not currently on these 

levels, you must install these components as part of your migration. 

If you are currently running the ClearPath OS 2200 12.0 release or the ClearPath 

OS 2200 12.1 release and have not migrated to the new method of configuring your 

CPCommOS network interfaces, then follow the instructions in Section 5.8 for migrating 

to the new method of configuring your CPCommOS network interfaces. Section 5.8 

provides step-by-step instructions for installing the ClearPath 13.1 Dorado 4000 

Compatibility Package and updating your CPCommOS 4R2A configuration to the new 

format. 

After the ClearPath 13.1 Dorado 4000 Compatibility Package is installed, it is no longer 

possible to use levels of CPCommOS prior to 3R1A. 

Dorado 4000 Plateau and ClearPath Release Interdependencies 

Table 7–3 details the interdependencies that exist between the Exec and CPCommOS 

products and the plateau level. These dependencies are tightly coupled for the Dorado 

4000 systems. Use Table 7–3 to verify if the product levels that you plan to install are 

supported. 

7831 0349–043 7–35


Dorado 4000 

Plateau 2.3 

(without additional sup files) 

Plateau 2.3 and additionally* 

2.3-CP12.1COMPATIBILITY. 

sup 

This allows you to continue 

to configure the network 

using SAILCC-NET. 

Plateau 2.3 and additionally* 

2.3- 

CP12.1COMPATIBILITY.sup 

2.3-CP12.1SAILCC-NET.sup 

This allows you to configure 

the network using the new 

CPCommOS configuration 

statements. 

Plateau 2.3 and additionally 

2.3- 

CP13.0COMPATIBILITY.sup 

This requires you configure 



statements and ensures you 

have all of the plateau 

updates to execute with 


Plateau 2.3 and additionally 

2.3-CP13.1-4000-COMPATI 

BILITY.sup 

This requires you configure 



statements and ensures you 

have all of the plateau 

updates to execute with 

ClearPath 13.2 

Table 7–3. Dorado 4000 Plateau and ClearPath Release Interdependencies 

ClearPath 




2R2 


3R1A is 

required 


3R1A is 

required 


3R1A or higher 

is required 


3R1A or higher 

is required 




Plus 


2R2A 


3R1A is 

required 


3R1A is 

required 


3R1A or 

higher is 

required 


3R1A or 

higher is 

required 





3R1A is not 

supported 


3R1A is 

required 


3R1A is the 

supported 

level 


3R1A or 

higher is 

required 


3R1A or 

higher is 

required 





4R1 is not 

supported 


4R1 is not 

supported 


4R1 is not 

supported 


4R1 is the 

supported 

level 


4R1 is the 

supported 

level 





4R2 is not 

supported 


4R2 is not 

supported 


4R2 is not 

supported 


4R2 is not 

supported 


4R2 is the 

supported 

level 

7–36 7831 0349–043 



Release 13.2 


4R2A is not 

supported 


4R2A is not 

supported 


4R2A is not 

supported 


4R2A is not 

supported 


4R2A is the 

supported 

level

Notes: 


• For Dorado 4000 systems, ClearPath OS 2200 Release 13.2 is tightly paired with 

Plateau 2.3 and the ClearPath 13.1 Dorado 4000 Compatibility Package which 

contains the 2.3-CP13.1-4000-COMPATIBILITY.sup file. 

• Plateau 2.3 and the Compatibility Package are available on the ClearPath Support site 

for Dorado 4000 series systems at: 

http://www.support.unisys.com/common/search/Downloads.aspx?pla=D4K&nav=D4K 

This link gives you access to the ClearPath Dorado 4000 Series product downloads. 

To acquire the media, click on the Media Tab, then click on the Plateau 2.3 link and 

download all the software products listed in the release. 

7.10. Migration for Existing Dorado 400 Customers 

When migrating to the ClearPath OS 2200 13.2 on a Dorado 400 system, you must be 

aware that the CPCommOS 4R2A product delivered in this release is restricted on the 

Dorado 400 systems. Due to interdependencies with the plateau level, the CPCommOS 

4R2A product will not function on a Dorado 400 system. To resolve this situation, Unisys 

supplies CP-FLD400 fast-load tape for use on the Dorado 400 systems only. This tape 

includes the ClearPath OS 2200 13.2 product levels and CPCommOS 2R2. Use the ST 

INSTALLPKG runstream to install this Dorado 400-specific fast-load tape. 

The CPCommOS 2R2 product was delivered in the ClearPath OS 2200 12.0 release. If 

you need to build the CPCommOS 2R2 product, use the product that was delivered on 

the CPCOMMSUITE logical package tape in the ClearPath OS 2200 12.0 release. If you 

did not take delivery of the ClearPath OS 2200 12.0 release and require a copy of the 

CPCommOS 2R2 product, contact the Unisys support Center and request a copy of this 

product be made available to you. 

Table 7–4. CP-FLD400 Logical 

Package Tape Contents for 

Dorado 400 

Installation and Support 

Name Level 

COMUS 6R9A 

CPCommOS 2R2 

FURPUR 32R5B 

PCFP 3R3A 

ROLRUNS 4R3 

SILAS 3R2B 

SOLAR 4R7A 

SYSLIB 76R4 

7831 0349–043 7–37


DDP-PPC Considerations 

The DDP-PPC 7R3A product delivered in the ClearPath OS 2200 Release 13.2 will not 

function on a Dorado 400 system that is running CPCommOS level 2R2. To avoid this 

issue, you can either run DDP-PPC level 7R2E or make configuration changes to 

DDP-PPC level 7R3A. 

The migration scenarios documented in Section 7 of this document install DDP PPC 

7R3A from either the CP-OE1B fast-load tape or the CP10 package tape. Once the 

DDP-PPC 7R3A product is installed, the following configuration changes must be 

applied: 



Dorado 400 Plateau and ClearPath Release Interdependencies 

Table 7–5 details the interdependencies that exist between the Exec and CPCommOS 

products and the plateau level. Use this table to verify that the product levels you plan to 

install are supported. 

Table 7–5. Dorado 400 Plateau and ClearPath Release 

Interdependencies 

Dorado 400 

Plateau 1.1 

SAIL-1.1.9 or 

higher 




EXEC 48R4 is 

supported. 


2R2 is 

supported. 




EXEC 48R6 is 

supported. 


2R2 is 

supported. 


3R1A is not 

supported. 




EXEC 48R7 is 

supported. 


2R2 is 

supported. 


4R1 is not 

supported. 

7.11. Migration for Existing Dorado 4100 

Customers 




EXEC 48R8 is 

supported. 


2R2 is 

supported. 


4R2 is not 

supported. 

The Dorado 4100 was introduced with the ClearPath OS 2200 12.1 release. 



Release 13.2 


2R2 is 

supported. 


4R2A is not 

supported. 

For Dorado 4100 systems, ClearPath OS 2200 Release 13.2 is tightly paired with Plateau 

1.2. If your system is not currently on Plateau 1.2 you must install this level before 

migrating your software to the ClearPath OS 2200 13.2 Release. 

7–38 7831 0349–043

Section 8 

Operations Sentinel (Formerly Single 

Point Operations) 

Note: Operations Sentinel was formerly called Single Point Operations. Throughout this 

document, however, the former product name, Single Point Operations, is used in some 

cases when referring to lower levels of the product. 

ClearPath OS 2200 Release 13.2 supports Operations Sentinel Basic Edition level 12.1. 

This version supports all Dorado models for OS 2200 systems. To run this version, you 

need a server such as one from the ES3000 series running Microsoft Windows Server 

2003 or 2008. When installing Operations Sentinel 11.1 on a server that has Operations 

Sentinel 11.0 installed, the installer has the option of copying the 11.0 configuration and 

merging 11.1 corrections into the 11.1 configuration. This avoids the need to manually 

recreate the configuration as was required with Operations Sentinel 11.0. 

For ClearPath Plus Dorado Server Model 110 users, Basic Edition is also supported on 

Windows XP Professional, but only when running on the Service Processor. 

When migrating to Operations Sentinel 11.0 or higher, users of any previous level of 

Single Point Operations must manually recreate their monitoring configurations. No 

conversion utility is provided with Operations Sentinel 11.x to migrate 10.x and earlier 

configurations to 11.x. 

7831 0349–043 8–1

Operations Sentinel (Formerly Single Point Operations) 

8–2 7831 0349–043

Appendix A 

Media Contents 

This appendix provides an overview of the ClearPath software media available with this 

release and lists the contents for the following system types: 

• Dorado Models 800, 700, and 300 Workload IOE Package (A.2) 

• Dorado Models 800, 700, and 300 Workload UOE Package (A.3) 

• ClearPath Dorado Model 400, 4000, 4100, and 4200 Workload Image IOE Basic 

Package (A.4) 

• ClearPath Dorado Model 400, 4000, 4100, and 4200 UOE Basic Package (A.5) 

Products in the Integrated Operating Environment (IOE) are used with nonmetered 

systems. Products in the Unisys Operating Environment (UOE) are used with metered 

systems. 

A.1. Software Packaging 

Unisys delivers the Exec and related software to each site on the following media, which 

includes a standard set of IOE products or UOE products, Exec features, Exec master 

and boot tapes, and optional product tapes: 

• Preconfigured boot tape 

You use the preconfigured boot tape to initialize and run your system. Symbolic 

mode customers use the preconfigured tape to get their system running the first 

time. The tape is configured with the following mandatory features: CARTIS, FBCIS, 

SCSITIS, TAVR, CARTLIB, and CARTTAPELIB. DMPLIB is also included on the boot 

tape. 

Two preconfigured boot tapes are delivered, but they are not interchangeable 

between the architectures. The architectures are 

• SAIL-based systems – ClearPath Dorado 400, 4000, 4100, and 4200 Server 

systems (nonmetered 420, 4080, 4180, 4280 and metered 430, 4090, 4190, 

4250, 4270, 4290). 

• CMOS systems – All other OS 2200 systems (Dorado systems) 

Note: The boot tape delivered with ClearPath Dorado 400, 4000, 4100, and 4200 

Server systems will not boot on Dorado 800, 700, or 300 Server systems and the 

boot tape delivered with Dorado 800, 700, or 300 Server systems will not boot on 

Dorado 400, 4000, 4100, and 4200 Server systems. 

7831 0349–043 A–1

Software Packaging 

• Java Boot tape 

SECOPT1 is required by Java and is included on the Java boot tape. Most users 

running stand-alone Java partitions will not have to generate the Exec in the partition, 

and can initialize the system after loading the Java boot tape. This is different from 

the standard OS 2200 boot tape. 

• Exec base symbolics tape 

This tape contains the source code for the current base level of the Exec, which is 

level 48. You use the base symbolics during system generation, which creates the 

Exec boot tape. 

• Exec release master tape 

This tape contains other software that you need to generate and boot the Exec. The 

system generation merges the base symbolics with the permanent correction file 

(PCF) code from the release master tape to create the Exec boot tape. 

• Fast-load tapes 

Fast-load tapes have been created to speed up installation of the products. A 

fast-load tape is a PRODLD tape that is created using the SOLAR/E PRODSV utility. 

• IOE software (ClearPath and ClearPath Plus nonmetered systems) 

Mandatory Integrated Operating Environment (IOE) products are delivered on 

package tapes in a keyed, buildable format. 

• UOE software (ClearPath Plus metered systems) 

Mandatory Unisys Operating Environment (UOE) products are delivered on package 

tapes in a keyed, buildable format. 

• Optional products 

Optional products are delivered on the remainder of the package tapes. 

• Optional product media 

This media contains optional nonhost products you order for your system packaged 

on the appropriate media (for example, CD-ROM). 

Section 7 describes the procedures for installing the products in this release. This 

includes migration and installation considerations and provides procedures for installing 

from both fast-load tapes and package tapes. Appendix C lists the contents of both 

fast-load tapes and package tapes. 

A–2 7831 0349–043

Dorado Models 800, 700, and 300 Workload IOE Package 

A.2. Dorado Models 800, 700, and 300 Workload 

IOE Package 

This package includes the following ClearPath software: 

• General-Purpose-Workload IOE 

The standard production IOE for 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, plus 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, plus the BIS software. It also 

includes one (1) Developer license and ten (10) User licenses. Additional BIS seat 

licenses are optional. 

BIS metering is available only on a prepaid basis. 

• OS 2200 Enterprise Application Environment (EAE) IOE Package 

The EAE (formerly LINC) package includes the standard IOE products, plus the 

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

in the package, it is required to be licensed separately. 

The specialized IOE packages can be used on a ClearPath system dedicated to the 

environment for that package or they could be used in a dedicated partition on a 

system with multiple partitions. 

• OS 2200 Java IOE (Dorado 300 only) 

This package includes the products in the Java Operating Environment. 

Table A–1 lists the contents of the software package. Most of the products in the table 

execute on the OS 2200 node of ClearPath systems. Products with an X in a column are 

included in the designated package. 

7831 0349–043 A–3


Table A–1. Dorado Models 800, 700, and 300 Workload IOE Software 


Support Name 

880/860/ 

840/ 

780/740/ 

380 

General Purpose SDK BIS EAE Java 

340 320 880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340 

320 

ACOB X X 

BIS IOE identifier 

(paper doc) 

380/340/ 

320 

CARTIS X X X X X X 

CARTLIB X X X X X X X 

CIFS X X X X X X X 

CIPHER-API X X X X X X X 

CITA X X X X X 

CKRS X 

CML X X X X X X X 

CMR X X X X X X X 

COMAPI X X X X X X X 

Common Core 

Media Package 

X X X X X X X 

COMUS X X X X X X X 

CPComm X X X X X X X 

CryptoLib X X X X X X X 

DAP X X X X X X X 

DDP-FJT X 

DDP-PPC X X X X X X X 

DFP X 

DMPLIB X X X X X X X 

DMS-RA X 

DPREP1100 X X X X X X X 

DPS 2200 X X X X X X 

DTI X X X X X X 

EAE IOE identifier 

(paper doc) 

ED X X X X X X X 

A–4 7831 0349–043 

X 

X




Support Name 

880/860/ 

840/ 

780/740/ 

380 


340 320 880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340 

320 

380/340/ 

320 

ELMS X X X X X X X 

ELT X X X X X X X 

EOM Departmental X X X X X X 

EOM/2200 File 

Print Manager 

X X X X X X X 

Exec X X X X X X X 

FAS X X X X X X X 

FBCIS X X X X X X X 

FLEX X X X X X X 

FLIT X 

FTN X 

FURPUR X X X X X X X 

GSA X X X X X X 

I18NLIB X X X X X X X 

InfoAccess 

CONNECT LIC 

InfoAccess QUERY X 

IPF X X X X X X 

IRU X X X X X X 

Java Boot X 

Java IOE identifier 

(paper doc) 

J2EE-CON- 

OPENDTP 

X X X X X X 

J2EE-CON-OS2200 X X X X X X 

JVM X X X X X X X 

LINK X X X X X X X 

LIST X X X X X X X 

LSS X X X X X X 

MAP X X X X X X X 

7831 0349–043 A–5 

X 

X




Support Name 

MAPPER 

OPEN/OLTP 

MAPPER System 

for 2200 

880/860/ 

840/ 

780/740/ 

380 


340 320 880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340 

320 

380/340/ 

320 

MASM X X X X X X X 

MCB X X X X X X 

MRI X 

MSCP X X X X X X X 

MSMQI X 

NTSI X X X X X X 

Open OLTP HTP/ic 

(HTP/ic-2200) 

Open/OLTP 2200 

Transaction 

Manager 

X X X X X 

X X X X X 

PADS X X X X X X 

PCFP X X X X X X X 

PCIOS X X X X X X X 

PDP X X X X X X X 

PLUS X X X X X X X 

PMD X X X X X X X 

QLP X 

QLP/PCIOS X 

RDMS-JDBC X X X 

ROLRUNS X X X X X X X 

RSS X X X X X X X 

SCSITIS X X X X X X X 

SDK IOE identifier 

(paper doc) 

SECOPT1 X X X X X X X 

A–6 7831 0349–043 

X 

X 

X




Support Name 

880/860/ 

840/ 

780/740/ 

380 


340 320 880/860/ 

840/ 

780/740/ 

380/340/ 

320 

SECOPT2 X 

880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340 

320 

380/340/ 

320 

SECURITY-ADMIN X X X X X X X 

SFS X X X X X X 

SILAS X X X X X X X 

SLIB X X X X X X X 

SOLAR X X X X X X X 

SOLAR/E X 

SORT X X X X X X 

SP-OPERATION/ 

Basic Edition 

X X X X X X 

SSG X X X X X X X 

SYSLIB X X X X X X X 

TAS X 

TAVR X X X X X X X 

TIPUTIL X X X X X X 

TRAM X 

Turbo MAPPER Included 

in the 

MAPPER 

system 


TUTIL X 

UCOB X X 

UCS C X X X X X 

UCSRTS X X X X X X X 

UDS DMS 

1100KEY 

Note: This product 

delivers the full 

functionality of 

DMS. 

7831 0349–043 A–7 

X




Support Name 

UDS RDMSKEY 




RDMS. 

880/860/ 

840/ 

780/740/ 

380 


340 320 880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340/ 

320 

880/860/ 

840/ 

780/740/ 

380/340 

320 

X X X 

UDSC X X X X X X 

Notes: 

• UDSC includes DMS, RDMS, and UREP for Unisys internal use. 

• UREP in UDSC can be used to create and maintain all definitions for RDMS. 

380/340/ 

320 

• UREP in UDSC can be used to create and maintain storage-area definitions for 

DMS. 

UFTN X 

UNIACCESS-ODBC 

(2 concurrent 

threads key) 

X 

Unit Duplexing X 

UPLS X X X X X X X 

UREPKEY 




UREPKEY. 

A–8 7831 0349–043 

X 

X X 

URTS X X X X X X X 

Virtual Tape 

Handler 

Web Transaction 

Server (standard 

encryption) 

Includes Java DPS 

25 licenses 


Server 

Includes Java DPS 

25 licenses 

X 

X 

X 

X 

X 

X 

X 

X 

X 

X 

X

Dorado Models 800, 700, and 300 Workload UOE Package 

A.3. Dorado Models 800, 700, and 300 Workload 

UOE Package 

This software package includes the following ClearPath software: 

• General-Purpose Workload UOE 

The standard production UOE software for ClearPath systems includes the 

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


This package includes the standard UOE products, plus compilers, database 



This package includes the standard UOE products, plus the BIS software. It also 




• OS 2200 Enterprise Application Environment (EAE) UOE Package 

The EAE (formerly LINC) package includes the standard UOE products, plus the 

additional products required for use with Enterprise Application Environment. 

Although Enterprise Application Environment software is not included in the 

package, it is required to be licensed separately. 

• OS 2200 Java UOE (Dorado 300 only) 

This package includes the products in the Java Operating Environment. 




7831 0349–043 A–9


Table A–2. Dorado Models 800, 700, and 300 Workload UOE Software 


Support Name 


890/ 

870/ 

850/ 

790/ 

750/ 

390 350 330 

890/ 

870/ 

850/ 

790/ 

750/ 

390/ 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

A–10 7831 0349–043 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

ACOB X X X X X X X 

BIS IOE identifier X X 

CARTIS X X X X X X X X X 

CARTLIB X X X X X X X X X 

CIFS X X X X X X X X X 

CIPHER-API X X X X X X X X X 

CITA X X X X X X X X 

CKRS X X X X 

CML X X X X X X X X X 

CMR X X X X X X X X X 

COMAPI X X X X X X X X X 

Common Core 

Media Package 

350/ 

330 

X X X X X X X X X 

COMUS X X X X X X X X X 

CPComm X X X X X X X X X 

CryptoLib X X X X X X X X X 

DAP X X X X X X X X X 

DDP-FJT X X 

DDP-PPC X X X X X X X X X 

DFP X X X X 

DMPLIB X X X X X X X X X 

DMS-RA X X 

DPREP1100 X X X X X X X X X 

DPS 2200 X X X X X X X X 

DTI X X X X X X X X 

390/ 

350/ 

330




Support Name 


890/ 

870/ 

850/ 

790/ 

750/ 

390 350 330 

890/ 

870/ 

850/ 

790/ 

750/ 

390/ 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

7831 0349–043 A–11 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

EAE IOE identifier X X 

ED X X X X X X X X X 

ELMS X X X X X X X X X 

ELT X X X X X X X X X 

EOM Departmental X X X X X X X X 

EOM/2200 File 

Print Manager 

350/ 

330 

X X X X X X X X X 

Exec X X X X X X X X X 

FAS X X X X X X X X X 

FBCIS X X X X X X X X X 

FLEX X X X X X X X X 

FLIT X X X X 

FTN X X X X 

FURPUR X X X X X X X X X 

GSA X X X X X X X X 

I18NLIB X X X X X X X X X 

InfoAccess 

CONNECT LIC 

X X 

InfoAccess QUERY X X 

IPF X X X X X X X X 

IRU X X X X X X X X 

Java Boot X 

Java IOE identifier 

(paper doc) 

J2EE-CON- 

OPENDTP 

X X X X X X X X 

J2EE-CON-OS2200 X X X X X X X X 

JVM X X X X X X X X X 

390/ 

350/ 

330 

X




Support Name 


890/ 

870/ 

850/ 

790/ 

750/ 

390 350 330 

890/ 

870/ 

850/ 

790/ 

750/ 

390/ 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

A–12 7831 0349–043 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

LINK X X X X X X X X X 

LIST X X X X X X X X X 

LSS X X X X X X X X 

MAP X X X X X X X X X 

MAPPER 

OPEN/OLTP 

MAPPER System 


X X 

X X 

MASM X X X X X X X X X 

MCB X X X X X X X X 

MRI X X 

MSCP X X X X X X X X X 

MSMQI X X X X 

NTSI X X X X X X X X 



Open Distributed 

Transaction 

Processing 

(OLTP-TM2200) 



PADS X X X X X X X X 

PCFP X X X X X X X X X 

PCIOS X X X X X X X X X 

PDP X X X X X X X X X 

PLUS X X X X X X X X X 

PMD X X X X X X X X X 

QLP X X X X 

QLP/PCIOS X X X X 

350/ 

330 

390/ 

350/ 

330




Support Name 


890/ 

870/ 

850/ 

790/ 

750/ 

390 350 330 

890/ 

870/ 

850/ 

790/ 

750/ 

390/ 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

7831 0349–043 A–13 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

RDMS-JDBC X X X X 

ROLRUNS X X X X X X X X X 

RSS X X X X X X X X X 

SCSITIS X X X X X X X X X 

SDK IOE identifier X 

SECOPT1 X X X X X X X X X 

SECOPT2 X X X X X X 

SECURITY-ADMIN X X X X X X X X X 

SFS X X X X X X X X 

SILAS X X X X X X X X X 

SLIB X X X X X X X X X 

SOLAR X X X X X X X X X 

SOLAR/E X X X X 

SORT X X X X X X X X 

SP-OPERATION/ 

Basic Edition 


SSG X X X X X X X X X 

SYSLIB X X X X X X X X X 

TAS X X X X X X 

TAVR X X X X X X X X X 

TIPUTIL X X X X X X X X 

TRAM X X 

Turbo MAPPER Included 

in the 

MAPPER 

system 


TUTIL X X X X 

Included 

in the 

MAPPER 

system 


350/ 

330 

390/ 

350/ 

330




Support Name 


890/ 

870/ 

850/ 

790/ 

750/ 

390 350 330 

890/ 

870/ 

850/ 

790/ 

750/ 

390/ 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

A–14 7831 0349–043 

350/ 

330 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

UCOB X X X X X X X 

UCS C X X X X X X X X 

UCSRTS X X X X X X X X X 

UDS DMS 

1100KEY 




DMS. 

UDS RDMSKEY 




RDMS. 

X X 

X X X X 

UDSC X X X X X X X X 

Notes: 


350/ 

330 

• UREP in UDSC can be used to create and maintain all definitions for RDMS. 

390/ 

350/ 

330 

• UREP UDSC can be used to create and maintain storage-area definitions for DMS. 

UFTN X X X X 


(2 concurrent 

threads key) 

X 

Unit Duplexing X X X X 

X 

UPLS X X X X X X X X X 

UREPKEY 




UREPKEY. 

X X X X X X 

URTS X X X X X X X X X 

URU-OS2200 X X X X X X X X X




Support Name 

Virtual Tape 

Handler 



encryption): Java 

DPS 25 licenses 


Server: Java DPS 

25 licenses 


890/ 

870/ 

850/ 

790/ 

750/ 

390 350 330 

890/ 

870/ 

850/ 

790/ 

750/ 

390/ 

350/ 

330 

X X X X 

X 

X 

X 

X 

X 

X 

X 

X 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

7831 0349–043 A–15 

X 

X 

350/ 

330 

X 

X 

890/ 

870/ 

850/ 

790/ 

750/ 

390 

X 

X 

350/ 

330 

X 

X 

390/ 

350/ 

330

ClearPath Dorado Model 400, 4000, 4100, and 4200 Workload Image IOE Basic 

Package 

A.4. ClearPath Dorado Model 400, 4000, 4100, and 

4200 Workload Image IOE Basic Package 

This software package includes the following software: 

• General-Purpose Workload IOE 

The standard production IOE software for ClearPath systems includes the mandatory 

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


This package includes the standard IOE products, plus compilers, database 



This package includes the standard IOE products, plus the BIS software. It also 




• OS 2200 Enterprise Application Environment (EAE) IOE Package 

The EAE (formerly LINC) package includes the standard IOE products, plus the 







Table A–3. ClearPath Dorado Model 400, 4000, 4100, and 4200 IOE 

Software 


Name 

General 

Purpose SDK BIS EAE 

4280/4180/4080/420 

ACOB X X 


(paper doc) 

CARTIS X X X X 

CARTLIB X X X X 

CIFS X X X X 

CIPHER-API X X X X 

CITA X X X X 

CKRS X 

A–16 7831 0349–043 

X

ClearPath Dorado Model 400, 4000, 4100, and 4200 Workload Image IOE Basic Package 




Name 

General 


4280/4180/4080/420 

CML X X X X 

CMR X X X X 

COMAPI X X X X 

Common Core Media 

Package 

X X X X 

COMUS X X X X 

CPCommOS X X X X 

CryptoLib X X X X 

DAP X X X X 

DDP-FJT X 

DDP-PPC X X X X 

DFP X 

DMPLIB X X X X 

DMS-RA X 

DPREP1100 X X X X 

DPS 2200 X X X X 

DTI X X X X 

EAE IOE identifier (paper 

doc) 

ED X X X X 

ELMS X X X X 

ELT X X X X 

EOM Departmental X X X X 

EOM/2200 File Print 

Manager 

X X X X 

Exec X X X X 

FAS X X X X 

FBCIS X X X X 

FLEX X X X X 

FLIT X 

7831 0349–043 A–17 

X


Package 




Name 

FTN X 

General 


4280/4180/4080/420 

FURPUR X X X X 

GSA X X X X 

I18NLIB X X X X 

InfoAccess CONNECT LIC X 

InfoAccess QUERY X 

IPF X X X X 

IRU X X X X 

J2EE-CON-OPENDTP X X X X 

J2EE-CON-OS2200 X X X X 

JVM X X X X 

LINK X X X X 

LIST X X X X 

LSS X X X X 

MAP X X X X 

MAPPER OPEN/OLTP X 

MAPPER System 


MASM X X X X 

MCB X X X X 

MRI X 

MSCP X X X X 

MSMQI X 

NTSI X X X X 




Transaction Manager 

X X X X 

X X X X 

PADS X X X X 

PCFP X X X X 

A–18 7831 0349–043 

X





Name 

General 


4280/4180/4080/420 

PCIOS X X X X 

PDP X X X X 

PLUS X X X X 

PMD X X X X 

QLP X 

QLP/PCIOS X 

RDMS-JDBC X X 

ROLRUNS X X X X 

RSS X X X X 

SCSITIS X X X X 


(paper doc) 

SECOPT1 X X X X 

SECOPT2 X 

SECURITY-ADMIN X X X X 

SFS X X X X 

SILAS X X X X 

SLIB X X X X 

SOLAR X X X X 

SOLAR/E X 

SORT X X X X 

SP-OPERATION/ 

Basic Edition 

7831 0349–043 A–19 

X 

X X X X 

SSG X X X X 

SYSLIB X X X X 

TAS X 

TAVR X X X X 

TIPUTIL X X X X 

TRAM X


Package 




Name 

General 


4280/4180/4080/420 

Turbo MAPPER Included in the 

MAPPER system 


TUTIL X 

UCOB X X 

UCS C X X X X 

UCSRTS X X X X 

UDS DMS 1100KEY 

Note: This product delivers 

the full functionality of DMS. 

UDS RDMSKEY 


the full functionality of 

RDMS. 

UDSC X X X X 

Notes: 

UFTN X 

UNIACCESS-ODBC (2 

simultaneous connections 

key) 

Unit Duplexing X 

A–20 7831 0349–043 

X 

X 

• UDSC includes DMS, RDMS, and UREP for Unisys internal 

use. 

• UREP in UDSC can be used to create and maintain all 

definitions for RDMS. 

• UREP in UDSC can be used to create and maintain 

storage-area definitions for DMS. 

UPLS X X X X 

UREPKEY 


the full functionality of 

UREPKEY. 

X 

X X 

URTS X X X X 

Virtual Tape Handler X 

X





Name 

Web Transaction Server 

(standard encryption) 

Includes Java DPS 25 

licenses 

Web Transaction Server 


licenses 

General 


4280/4180/4080/420 

X X X X 

X X X X 

7831 0349–043 A–21

ClearPath Dorado Model 400, 4000, 4100, and 4200 UOE Basic Package Software 

A.5. ClearPath Dorado Model 400, 4000, 4100, and 

4200 UOE Basic Package Software 

• General-Purpose Workload UOE 

The standard production UOE software for ClearPath systems includes the 

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


This package includes the standard UOE products, plus compilers, database 



This package includes the standard UOE products, plus the BIS software. It also 




• OS 2200 Enterprise Application Environment (EAE) UOE Package 

The EAE (formerly LINC) package includes the standard UOE products, plus the 







Table A–4. ClearPath Dorado Model 400, 4000, 4100, and 4200 UOE Basic 

Package Software 


Support Name 

430/ 

4050 

General Purpose SDK BIS EAE 

4290/4270 

4250/4190 

4170/4150 

4090 

4290/4270 

4190/4170 

4090 

4290/4270 

4250/4190 

4170/4150 

4090/4050 

4290/4190 

4090 

ACOB X X X X 


(paper doc) 

CARTIS X X X X X 

CARTLIB X X X X X 

CIFS X X X X X 

CIPHER-API X X X X X 

A–22 7831 0349–043 

X





Support Name 

430/ 

4050 


4290/4270 

4250/4190 

4170/4150 

4090 

4290/4270 

4190/4170 

4090 

4290/4270 

4250/4190 

4170/4150 

4090/4050 

4290/4190 

4090 

CITA X X X X X 

CKRS X X X 

CML X X X X X 

CMR X X X X X 

COMAPI X X X X X 

Common Core Media 

Package 

X X X X X 

COMUS X X X X X 

CPCommOS X X X X X 

CryptoLib X X X X X 

DAP X X X X X 

DDP-FJT X 

DDP-PPC X X X X X 

DFP X X X 

DMPLIB X X X X X 

DMS-RA X X 

DPREP1100 X X X X X 

DPS 2200 X X X X X 

DTI X X X X X 

EAE IOE identifier 

(paper doc) 

ED X X X X X 

ELMS X X X X X 

ELT X X X X X 

EOM Departmental X X X X X 

EOM/2200 File Print 

Manager 

X X X X X 

Exec X X X X X 

7831 0349–043 A–23 

X





Support Name 

430/ 

4050 


4290/4270 

4250/4190 

4170/4150 

4090 

4290/4270 

4190/4170 

4090 

4290/4270 

4250/4190 

4170/4150 

4090/4050 

4290/4190 

4090 

FAS X X X X X 

FBCIS X X X X X 

FLEX X X X X X 

FLIT X X X 

FTN X X X 

FURPUR X X X X X 

GSA X X X X X 

I18NLIB X X X X X 

InfoAccess CONNECT 

LIC 

X X 

InfoAccess QUERY X X 

IPF X X X X X 

IRU X X X X X 

J2EE-CON-OPENDTP X X X X X 

J2EE-CON-OS2200 X X X X X 

JVM X X X X X 

LINK X X X X X 

LIST X X X X X 

LSS X X X X X 

MAP X X X X X 

MAPPER 

OPEN/OLTP 

MAPPER System 


MASM X X X X X 

MCB X X X X X 

MRI X 

MSCP X X X X X 

A–24 7831 0349–043 

X 

X





Support Name 

430/ 

4050 


4290/4270 

4250/4190 

4170/4150 

4090 

4290/4270 

4190/4170 

4090 

MSMQI X X X 

4290/4270 

4250/4190 

4170/4150 

4090/4050 

4290/4190 

4090 

NTSI X X X X X 




Transaction Manager 

X X X X X 

X X X X X 

PADS X X X X X 

PCFP X X X X X 

PCIOS X X X X X 

PDP X X X X X 

PLUS X X X X X 

PMD X X X X X 

QLP X X X 

QLP/PCIOS X X X 

RDMS-JDBC X X 

ROLRUNS X X X X X 

RSS X X X X X 

SCSITIS X X X X X 


(paper doc) 

SECOPT1 X X X X X 

SECOPT2 X X X 

SECURITY-ADMIN X X X X X 

SFS X X X X X 

SILAS X X X X X 

SLIB X X X X X 

SOLAR X X X X X 

SOLAR/E X X X 

7831 0349–043 A–25 

X





Support Name 

430/ 

4050 


4290/4270 

4250/4190 

4170/4150 

4090 

4290/4270 

4190/4170 

4090 

4290/4270 

4250/4190 

4170/4150 

4090/4050 

4290/4190 

4090 

SORT X X X X X 

SP-OPERATION/ 

Basic Edition 

X X X X X 

SSG X X X X X 

SYSLIB X X X X X 

TAS X X X 

TAVR X X X X X 

TIPUTIL X X X X X 

TRAM X 

Turbo MAPPER Included in 

the MAPPER 

system for 

2200 

TUTIL X X X 

UCOB X X X X 

UCS C X X X X X 

UCSRTS X X X X X 

UDS DMS 1100KEY 



functionality of DMS. 

UDS RDMSKEY 



functionality of RDMS. 

X X 

X X 

UDSC X X X X X 

A–26 7831 0349–043





Support Name 

430/ 

4050 

Notes: 


4290/4270 

4250/4190 

4170/4150 

4090 

4290/4270 

4190/4170 

4090 

4290/4270 

4250/4190 

4170/4150 

4090/4050 


4290/4190 

4090 

• UREP in UDSC can be used to create and maintain all definitions for 

RDMS. 

• UREP in UDSC can be used to create and maintain storage-area definitions 

for DMS. 

UFTN X X X 


(2 simultaneous 

connections key) 

Unit Duplexing X X X 

UPLS X X X X X 

UREPKEY 




UREPKEY. 

7831 0349–043 A–27 

X 

X X X X 

URTS X X X X X 

URU-OS2200 X X X X X 

Virtual Tape Handler X X X 



encryption) Includes 

Java DPS 25 licenses 


Server 


licenses 

X X X X X 

X X X X X


A–28 7831 0349–043

Appendix B 

Product Interdependencies 

This appendix contains an interdependency matrix for the software products in this 

release. Table B–1 identifies specific ClearPath OS 2200 Release 13.2 products that are 

required by other Release 13.2 products. 

• The first column lists the installation and support name of each product. 

• The second, third, and fourth columns (Required to Install, Required to Build, and 

Required to Execute) identify the products required before you can install, build, or 

execute the product in the first column. 

• The fifth column (Optional Products) identifies products you can order separately to 

expand the capabilities of the product listed in the first column. These products are 

considered optional because they are not required for functional operation. See 

Table B–2 for more detailed information about the interdependencies associated 

with these products. In this column, notes refer to information in Table B–2. 

Products marked with an asterisk (*) in Table B–1 are included in the General Purpose 

Operating Environment (IOE) package for one or more system types and typically are 

installed when you install your IOE products. See Appendix A for the list of IOE products 

by system. 

Separately packaged features of the Exec are not listed because you need only the IOE 

to build, install, or execute them. 

Note: The Required to Build column does not apply to absolute (nonsymbolic) versions 

of these products. 

7831 0349–043 B–1



Support Name 

Table B–1. Products Interdependency Matrix 

Required to 

Install Required to Build 

ACOB MAP*, MASM*, 

PCIOS, PDP*, SORT, 

SSG*, SYSLIB*, 

UCSRTS* 

Required to 

Execute 

CA-TNG-INTF Not buildable CA Unicenter TNG 

CIFS CPComm* or 

CPCommOS*, 

COMAPI*, ELMS*, 

FURPUR*, LINK*, 

SSG*, URTS* 

CITA COMUS*, ELT*, LINK*, 

MASM*, SSG*, 

RDMS*, URTS*, UC* 

CKRS 

CML MAP*, MASM* 

CMR COMUS*, ELT*, MAP*, 

MASM*, PLUS*, SSG* 

COMAPI COMUS*, ELT*, LINK*, 

MASM*, PDP*, SSG*, 

UC* 

COMUS ACOB, GSA*, PCIOS*, 

SORT 

CPComm COMUS*, ELT*, LINK*, 

LSS*, MAP* MASM*, 

PDP*, SSG*, UC*, 

UPLS*, URTS*, 

CryptoLib* 

CPCommOS COMUS*, ELT*, LINK*, 

LSS*, MAP* MASM*, 

PDP*, SSG*, UC*, 

UPLS*, URTS* 

Optional Products 

(see Table B–2) 

PCIOS, UCSRTS* CKRS, DFP, DMS, 

FTN, PADS*, PCIOS, 

SFS, SORT 

COMAPI*, MCB* 

MSCP* 

LINK*, URTS*, 

CryptoLib* 

LINK*, URTS* 

cpFTP UC* 

CULL SORT SORT (See 3.8 for 

TeamQuest key 

information.) 

ACOB, PCIOS, SORT 

DAP Not buildable DPS*, LINK*, PCFP* See note about LINK. 

B–2 7831 0349–043


Support Name 


Required to 


DDP-FJT SOLAR* COMUS*, DAP*, 

DDP-PPC*, ELMS*, 

ELT*, FURPUR*, GSA*, 

IRU*, LINK*, LSS*, 

MAP*, MASM*, PDP*, 

PLUS*, SSG*, SYSLIB* 

DDP-PPC SOLAR* COMUS*, ELMS*, 


LINK*, LSS*, MAP*, 

MASM*, PDP*, PLUS*, 

SSG*, SYSLIB*, UC*, 

UPLS *, URTS* 

DEPCON-2200 Not buildable 


Required to 

Execute 

DAP*, DDP-PPC*, 

ELMS*, FURPUR*, 

GSA*, I18NLIB*, IRU*, 

SSG*, SYSLIB* 

DAP*, ELMS*, 

FURPUR*, GSA*, 

I18NLIB*, LINK*, 

LSS*, SSG*, SYSLIB*, 

URTS* 



ACOB, DPS*, IPF*, 

UCOB 

ACOB, CPComm*, 

DPS*, MCB*, OSITS, 

TCP-IP, Telcon, UC*, 

UCOB, UFTN 

DFP PCIOS, SFS 

DMS ACOB, I18NLIB*, 

SORT*, SYSLIB* 

ACOB, FTN, QLP, 

UCOB, UFTN 

DMS-RA Not buildable CPComm* or 


COMAPI*, DMS, 

UREP, URTS* 

DPREP1100 Not buildable 

DPS ACOB, ED*, ELT*, 



PLUS*, SSG* 

Security-Admin, 

SIMAN, SORT*, UREP 

OLTP-TM2200* 


ACOB, CULL, 

COMUS*, FTN, 

I18NLIB*, LINK*, 

Telcon, UCOB, UFTN 

DTI Windows 2000 CITA*, 

OLTP-TM2200* 

ELMS GSA*, UC* GSA* 

ELT 

EXEC 

EXPIPE PCIOS* ACOB, SORT*, UCOB 

FAS ELT*, FURPUR*, GSA*, 


PLUS*, SORT*, SSG*, 

SYSLIB* 

SORT* 

FDP-ADP SORT* QLP 

FLEX ELMS*, LINK* 

FLIT DPS*, LINK*, PCFP* 

7831 0349–043 B–3



Support Name 


Required to 


FTN CML*, MAP*, MASM*, 

PCIOS*, PDP*, PLUS*, 

SYSLIB*, UCSRTS 

FURPUR ELT*, MAP*, MASM*, 

PDP*, PLUS*, SORT*, 

SSG*, SYSLIB* 

GSA 

HTPIC-2200 SOLAR* COMUS*, ELMS*, 


LSS*, MAP*, SSG*, 

SYSLIB*, URTS* 

Required to 

Execute 

CML*, PCIOS*, 

UCSRTS 



CKRS, DFP, SFS*, 

SORT* 

LINK* ELMS*, PCFP*, 

SORT*, 


FURPUR*, LSS*, 

OLTP-TM2200*, SSG*, 


CPComm*, DTI*, 

I18NLIB Not buildable ELMS*, MAP*, SLIB*, 


UREP, URTS* 

INFOACCESS Not buildable CPComm*, DMS, 

Windows NT 

INTERCONNECT DDP-PPC*, CIFS*, 

URTS* 

Not buildable CIFS*, COMAPI*, 

CPComm* or 


DDP-PPC* 

INTERIX SP-Operation 

IPF GSA* RDMS* 

IRU GSA*, SORT*, UPLS, 

UC, URTS 

JBOSS-2200 CIFS*, JVM Not buildable CIFS*, COMAPI*, 

CPComm* or 


JPJVM* 

JPJVM CIFS*, 

Interconnect 

URTS MCB*, SORT*, TIP, 

UDSC* 

Not buildable CIFS*, 

I18NLIB*,LINK*, LSS*, 

UC*, URTS*, 

Interconnect 

J2EE-CON- 

OPENDTP*, J2EE- 

CON-OS2200*, OLTP- 

TM2200*, RDMS*, 

RDMS-JDBC*, DMS, 

DMS-RA* 

OLTP-TM2200*, 

DMS-RA*,BIS-RA, 

RDMS-JDBC, 

J2EE-CON-OS2200*, 

J2EE-CON-OPENDTP* 

, 

JBOSS-2200, MCB* 

B–4 7831 0349–043


Support Name 


Required to 



Required to 

Execute 

JVM CIFS* Not buildable CIFS*, I18NLIB*, 

LINK*, LSS*, URTS*, 

COMAPI*, 

CPComm*or 

CPCommOS* 

J2EE-CON-OS2200 CITA, CPComm* or 


COMAPI*, MCB* 

LA COMUS*, ELT*, MAP*, 

MASM*, PLUS*, GSA*, 

PCIOS, SORT*, 

SYSLIB* 

LINK GSA*, LINK*, LSS*, 

MAP*, MASM*, 

PLUS*, SLIB*, UC*, 

UPLS*, URTS* 

LIST 

LSS ELMS*, GSA*, LINK*, 

MAP*, MASM* PDP*, 

SLIB*, SYSLIB*, 

UPLS*, URTS* 

MAP GSA* 

MASM 

MCB COMUS*, DAP*, ELT*, 


PLUS*, SSG*, 

MQS2200 SOLAR* COMAPI*, COMUS*, 

ED*, FURPUR*, LINK*, 

MASM*, MCB*, 


MSAR SOLAR* COMUS*, MAP*, 

MASM*, PCIOS, 

SORT*, SYSLIB* 

PCIOS, SORT* 

(See 3.8 for 

TeamQuest key 

information.) 

LSS*, LINK*, SLIB*, 


ELMS*, LINK*, SLIB*, 

SYSLIB*, UC*, UCOB, 

UFTN, URTS* 

DAP*, PMD* 

PCIOS, SORT* 

(See 3.8 for 

TeamQuest key 

information.) 

MSMANAGER PCIOS, SORT* 

(See 3.8 for 

TeamQuest key 

information.) 




PADS*, DMS-RA*, 

BIS-RA, RDMS-JDBC, 

J2EE-CON-OS2200*, 

J2EE-CON- 

OPENDTP*, JBOSS- 

2200, MCB*, UC* 


7831 0349–043 B–5 

CIFS* 

SFS 

COMAPI*, COMUS*, 

ED*, FURPUR*, 

LINK*, MASM*, 

MCB*, OLTP-TM2200, 

BIS 

DPS*



Support Name 


Required to 


Required to 

Execute 

MSMQI NTSI*, Windows 

Message Queuing 

(MSMQ) 

NTSI Not buildable COMAPI*, Windows 

2000 Server SP2 or 

later 

OLTP-TM2200 SOLAR* ACOB, UC*, UCOB, 

ELMS*, ELT*, 


LSS*, MAP*, MASM*, 

PDP*, SSG*, SYSLIB*, 

URTS* 

OPE LINK*, MASM*, 

SOLAR*, SSG* 

OSAM SOLAR* UC*, ED*, ELT*, 


LSS*, MASM*, UPLS*, 

SSG*, URTS*. 

OSI-TP SOLAR* ELMS*, ELT*, 



PDP*, SSG*, SYSLIB*, 

UC*, URTS* 

PADS FTN, GSA*, LINK*, 


PLUS*, SYSLIB*, UC*, 

UFTN, URTS* 

PAR SOLAR* COMUS*, ELT*, FTN, 

MAP*, MASM*, 

SYSLIB*, 

CPComm* ELMS*, 



URTS* 



See notes. 

FLEX 

See notes. 

FURPUR*, URTS* RDMS, UC*, UCOB 

URTS* (See 3.8 for 

TeamQuest key 

information.) 

CPComm*, 



OLTP-TM2200*, SSG*, 


ACOB, UC*, UCOB, 

UFTN, LINK*, LSS*, 

SORT*, SYSLIB*, 

URTS* 

(See 3.8 for 

TeamQuest key 

information.) 

PCFP Not buildable LINK*, SYSLIB* ELMS* 

PCIOS ELT*, MAP*, MASM*, 

PDP* 

PDP 

ACOB, FTN, QLP, 

SORT*, UC*, UCOB, 

UFTN 

PLUS Not buildable PADS*, PCIOS, 

SYSLIB* 

PMD MAP*, MASM*, 

SYSLIB* 

QLP DMS, GSA*, PCIOS, 

SORT* 

DMS, PCIOS, RDMS, 

SORT* 

B–6 7831 0349–043 

DTI* 

FTN 

DFP 

UREP


Support Name 


Required to 


RDMS CIFS*, GSA*, I18NLIB*, 

SORT*, URTS* 


Required to 

Execute 

RDMS-JDBC Not buildable CPComm*or 


COMAPI*, I18NLIB*, 

RDMS, URTS* 

ROLRUNS Not buildable FAS 

RSS COMUS*, DAP*, ED*, 



PLUS*, SSG*, 



CIFS*, SORT* ACOB, FTN, DMS, 

IPF*, LINC II, MRI, 

QLP, SFS*, UC*, 

UCOB, UFTN, UREP 

DDP-PPC* 

SAUTILITIES SOLAR* Not buildable (See 3.8 for 

TeamQuest key 

information.) 

Security-Admin cpFTP, TAS FLEX* 

SFS ACOB, FTN, IMS1100, 

UCOB, UFTN 

SILAS COMUS*, DAP*, ELT*, 

MAP*, MASM*, 

PCFP*, PDP*, PLUS*, 

SSG*, SYSLIB* 

SIMAN SOLAR* GSA*, SORT*, 

COMUS*, ELT*, MAP*, 

MASM*, PLUS* 

SLIB Not buildable 



DFP, UREP 

CPComm*, SORT* DAP*, PCFP*, PMD* 

(See 3.8 for 

TeamQuest key 

information.) 

SOLAR Not buildable CPComm*, SILAS*, 

ED*, ELT*, FURPUR*, 

LINK*, SSG* 

SOLAR/E Not buildable CPComm*, SILAS*, 

ED*, ELT*, FURPUR*, 

LINK*, SSG* 

SORT I18NLIB*, MAP*, 

MASM*, PDP*, 

PCIOS*, SSG*, 


SP-OPERATION Not buildable 

SP-OPERATION CP Not buildable 

I18NLIB*, PCIOS*, 


FAS, SLIB* 

(See note about 

FURPUR.) 

FAS, SLIB* 

(See note about 

FURPUR.) 

7831 0349–043 B–7 

CKRS



Support Name 


Required to 


SSG ELT*, MASM*, MAP*, 

PMD*, SSG*, SYSLIB* 

SYSLIB 

TAS SOLAR* COMUS*, DAP*, 

DDP-PPC*, ELT*, 

FURPUR*, GSA*, IRU*, 

LINK*, LSS*, MAP*, 

MASM*, PDP*, PLUS*, 

SSG*, SYSLIB* 

TIP-LA LINK*, LSS*, 

SOLAR*, URTS* 

TIPUTIL FTN, UC* 

Required to 

Execute 

DAP*, DDP-PPC*, 


IRU*, SSG*, SYSLIB* 

Not buildable URTS* (See 3.8 for 

TeamQuest key 

information.) 

TQ-BASELINE Not buildable (See 3.8 for 

TeamQuest key 

information.) 

TQ-MODEL Not buildable TQ-BASELINE (See 3.8 

for TeamQuest key 

information.) 

TQ-ONLINE Not buildable TQ-VIEW (See 3.8 for 

TeamQuest key 

information.) 

TQ-PMLOG TQ-BASELINE Not buildable TQ-BASELINE (See 3.8 


information.) 

TQ-PROBES TQ-BASELINE Not buildable TQ-BASELINE (See 3.8 


information.) 

TQD-FRAGGER SOLAR* Not buildable URTS* (See 3.8 for 

TeamQuest key 

information.) 

TQRDFRAGGER SOLAR* Not buildable URTS* (See 3.8 for 

TeamQuest key 

information.) 

TUTIL 

UC ELMS*, GSA*, LINK*, 


UPLS* 

PCIOS*, LINK*, LSS*, 

PDP*, URTS* 



ACOB, DPS*, IPF*, 

UCOB, UDSC*, UFTN 

COMAPI*, 

TQ-MODEL, Cipher- 

API 

Cipher-API 

See note about 

TQ-VIEW. 

CKRS, DFP, DPS*, 

18NLIB*, MCB*, 

PADS*, PCFP*, PDP*, 

RDMS, SFS*, SORT*, 

UREP, CIFS* 

B–8 7831 0349–043


Support Name 


Required to 


UCOB GSA*, LINK*, LSS*, 

MAP*, MASM*, UPLS* 

UCSRTS MASM*, SSG* 


Required to 

Execute 

ELMS*, LINK*, LSS*, 

PCIOS*, URTS* 

UDSC GSA*, SORT*, UC* DMS, RDMS, SFS*, 

SORT* 

UFTN GSA*, LINK*, LSS*, 

MAP*, MASM*, UPLS* 

UNIACCESS-ODBC Not buildable RDMS 

ELMS*, LINK*, LSS*, 

PCIOS*, URTS* 

UPLS Not buildable ELMS*, LINK*, LSS*, 

URTS* 



CIFS*, DMS, JVM*, 

PADS*, RDMS, SFS*, 

SORT*, UREP 

ACOB, DMS 

CKRS, DFP, DMS, 

DPS*, MCB*, PADS*, 

PCFP*, RDMS, SFS*, 

SORT*, UREP 

PADS*, PCIOS* 

UREP GSA*, UC* I18NLIB*, SORT* DMS, DPS*, RDMS, 

IPF*, UC*, UCOB, 

UFTN 

URTS GSA*, LSS*, MAP*, 

MASM*, PCIOS*, 

PDP*, PLUS*, 

SYSLIB*, UC*, UFTN, 

UPLS* 

SYSLIB* PCIOS*, SORT* 

URU-OS2200 Not buildable CPComm* IRU 

WEBTS Not buildable CPComm* TAS, cpFTP, FLEX 

WMQ2200 INTERCONNECT, 

SOLAR* 

COMAPI*, COMUS*, 

ED*, MCB*, 


XRLOAD SORT* 

INTERCONNECT, 

COMAPI*, DDP-PPC* 

OLTP-TM2200, BIS 

7831 0349–043 B–9



Support Name 

Table B–2. Optional Product Interdependency Notes 

Interdependency Notes 

ACOB CKRS, DFP, DMS, PADS, and SFS are required only if you want to use their 

respective capabilities with ACOB. 

FTN is required if you want to access FORTRAN from a COBOL program. 

PCIOS is an optional execution dependency. 

SORT is required only if you want to use the X3.23-1974 standard SORT module 

features in ACOB. 

COMUS ACOB, PCIOS, and SORT are required to use the common-banked version. 

cpFTP UC is required to build cpFTP to apply CHGs, or to make a new mode of cpFTP. 

DAP LINK is required for simulation and dump analysis of ZOOMs, UCS-compiled 

object modules, and subsystems. 

DDP-FJT ACOB or UCOB is required if you write a program-callable COBOL application. 

DPS is required for generation and execution if the DPS interface is used. 

IPF is required if the IPF interface is used. 

Note: The Print Driver and Print Manager components of DDP-FJT are no longer 

supported because PERCON has been decommitted. 

DDP-PPC ACOB, UCOB, or UFTN is required if you are writing a program-to-program 

application. 

CPComm is required for execution. 

DPS is required if you use the DPS interface for UTILITY processor. 

MCB is required if you use the Single Message Transfer (SMT) interface or 

DDP-PPC to start TIP transactions. 

OSITS is required if DDP-PPC OSI connections use the DCP transport layer 

services as a gateway, or for OSI routing. 

Telcon software is required if DDP-PPC connections are routed through a DCP. 

DDP-PPC does not require Telcon if connections are routed through CPComm. 

TCP-IP is required if the DCP is used as a TCP-IP router for DDP-PPC TCP-IP 

network connections. 

UC is required to write a C program-to-program application. 

DFP DFP can be used to specify characteristics of files that are accessed by SFS or 

PCIOS. 

DMS ACOB, FTN, UCOB, UFTN, or QLP is required to create and access DMS 

databases. 

SORT is required if the DRU or DMU components of DMS are used. 

UREP can be used with DMS operations. 

DMS-RA OLTP-TM2200 is required for XA transaction support. 

DPS COMUS, CULL, and LINK are optional generation dependencies. 

FTN, I18NLIB, LSS, UCOB, UFTN are optional execution dependencies. 

B–10 7831 0349–043


Support Name 




DTI CITA and COMAPI are used to connect to the 2200. You do not need to use this 

connection if you are using OLTP. 

OLTP-TM2200 is optional because OpenTI can go to TUXEDO or OLTP and 

Transaction Integrator can get to the OS 2200 via COMAPI. 

ELMS The GSA processor MCON is required for processing the application’s message 

modules (also known as Message Data Bases or MDBs) if you are planning to 

use ELMS in your applications. 

EXPIPE ACOB, SORT, and UCOB are optional execution dependencies. 

FLIT DPS is required in order to use FLIT full-screen mode during interactive 

debugging. 

FTN DFP is required only if you want to use the Define File capabilities with 

FORTRAN. 

SFS is required only if you want to use the Shared File capabilities of SFS with 

FTN. 

SORT is required only if you want to do a sort in a FORTRAN program. 

FURPUR PCFP is an optional generation dependency. 

HTPIC-2200 CPComm is required. 

ELMS, PCFP, and SORT are optional execution dependencies. 

DTI is required if you want transactions to communicate with Microsoft 

Transaction Services. 

I18NLIB ELMS, MAP, SLIB, SSG, SYSLIB, UREP, and URTS are optional execution 

dependencies. 

IPF RDMS is required if IPF SQL capabilities are required. 

IRU SORT is required only for IRU COLLECT command execution. 

MCB is required only for applications that use MCB. 

TIP is required only for applications that use TIP. 

UDSC is required only for applications that use UDSC. 

7831 0349–043 B–11



Support Name 



JBOSS-2200 J2EE-CON-OPENDTP is required to integrate Open Distributed Transaction 

Processing applications with JBoss Java EE technology through a Java EE 

connector. 

J2EE-CON-OS2200 and CITA are required to connect JBoss applications to 

OS 2200 TIP and HVTIP programs. 

OLTP-TM2200 is required to integrate Open Distributed Transaction Processing 

applications with JBoss Java EE technology or to ensure that your JBoss 

transactions are recoverable. 

RDMS and RDMS-JDBC are required to access Relational Database Server data 

from JBoss applications through RDMS-JDBC. 

DMS and DMS-RA are required to access Network Database Server data from 

JBoss applications through DMS-RA. 

Business Information Server and BIS-RA are required to access BIS data from 

JBoss applications through BIS-RA. 

JPJVM OLTP-TM2200 is required to use the JPJVM in an OLTP environment. 

J2EE-CON-OPENDTP is required to integrate Open Distributed Transaction 

Processing applications with JBoss J2EE technology through a J2EE connector. 


from JBoss applications through RDMS-JDBC. DMS and DMS-RA are required 

to access Network Database Server data from JBoss applications through DMS 

RA. J2EE-CON-OS2200 and CITA are required to connect JBoss applications to 

OS 2200 TIP and HVTIP programs. 

JVM PADS is required if PADS debugging of native methods is desired, or if the 

debugging version of the Java launcher, javag, is used. 

OLTP-TM2200 is required to use the JVM in an OLTP environment. 

J2EE-CON-OPENDTP is required to integrate Open Distributed Transaction 

Processing applications with JBoss J2EE technology through a J2EE connector. 


from JBoss applications through RDMS-JDBC. DMS and DMS-RA are required 

to access Network Database Server data from JBoss applications through 

DMS-RA. J2EE-CON-OS2200 and CITA are required to connect JBoss 

applications to OS 2200 TIP and HVTIP programs. 

LINK LSS is required if an object module is produced by a UCS compiler. 

CIFS is required to build or execute CIFSLD. If CIFS is not installed, CIFSLD will 

not be rebuilt. 

LSS Requires SFS if you want to have shared access to data files with locking and 

recovery features. 

MQS2200 COMAPI is required to use the MQSeries channels. 

OLTP-TM2200 is required for participation in global transactions. 

BIS is required to use the basic mode interface (BMI). The basic mode interface 

enables BIS to access the Message Queuing Interface (MQI). 

MSMANAGER DPS is required to use the full screen interface. 

B–12 7831 0349–043


Support Name 




MSMQI MSMQI is installed as part of Messaging Integration Services (NTSI) on an 

OS 2200. 

Message Queuing (MSMQ 2.0 or higher) is required on the Windows server on 

which the NTSI service is installed. 

NTSI MAPI compliant client on a Windows server is required for Mail Service 

Integration. 

OADE-WIN (installs as 

Programmer's 

Workbench) 

User Authentication (FLEX) on the OS 2200 and an OS 2200 Uniscope Emulator 

on the workstation are required for network authentication. 

Windows 2000 Server SP2, Windows 2003 Server, or Windows 2008 Server is 

required for network authentication and for OS 2200 SSPI support. 

ACOB, LINK, MAP, PDP, UCOB, UFTN, and UC are optional execution 

dependencies. 

Interactive debugging requires COMAPI. 

OPE RDMS is required if embedded SQL is used in either C or COBOL programs. 

UC is required if the ncc or cob utilities are used. 

UCOB is required if the cob utility is used. 

OSI-TP DTI is required if you want transactions to communicate with Microsoft 

Transaction Services. 

PADS ACOB, UC, UCOB, and UFTN programs can use PADS for debugging. 

ASCII Fortran Compiler (FTN) runtime is used by the EDIT, LIST, and PROFILE 

MONITOR LINE capabilities of PADS. 

SORT is required if you use the NPEER capability. 

PCIOS DFP is required if you need to change the file description without recompiling 

the program. 

PCFP ELMS is an optional execution dependency. 

PLUS PADS, PCIOS, and SYSLIB are optional execution dependencies. 

QLP UREP is required only if DMS or RDMS is selected. 

RDMS ACOB, FTN, UC, UCOB, or UFTN are required when accessing RDMS from an 

ASCII COBOL, ASCII FORTRAN, C Compiler, COBOL Compiler, or Fortran 

Compiler program. COBOL Compiler programs access RDMS with the 

embedded SQL interface (ESQL) or the ENTER MASM interface. 

DMS and SFS are required for applications that use them. 

IPF is required only to access RDMS interactively through the IPF SQL Interface. 

EAE is required when EAE is used on OS 2200 machines. 

MRI is required to access RDMS databases from Business Information Server 

(BIS). 

QLP is required to produce QLP query reports on data in an RDMS database. 

The full UREP product (UDS UREP KEY) is required to use data-entity modeling 

in conjunction with a relational database. 

7831 0349–043 B–13



Support Name 



RDMS-JDBC I18NLIB is required by RDMS-JDBC to handle character set translations on the 

JDBC Server side. OLTP-TM2200 is required for XA transaction support. 

Security-Admin If FLEX is installed, the Security-Admin Agent will call ASIS to perform user 

authentication. On Security level 1 and higher systems, user-ids and ACRs need 

to be set up for the installed FLEX/ASIS subsystem. 

SFS DFP is required to specify the file as shared without recompiling the accessing 

program. 

UREP is an optional execution dependency. 

SILAS DAP, PCFP, and PMD are optional execution dependencies. 

SOLAR FAS is required to execute the LIBSAVE/FAS and LIBLOAD/FAS runstreams. 

FURPUR—SOLAR does not use FURPUR to read or write the system key table 

(SYS$*DATA$.KEYTABLE$). However, a loose dependency exists between 

SOLAR and FURPUR in that a compatible level of FURPUR is required to read 

the system key table version written by SOLAR in order to perform product 

generation, COMUS installation, and general copying of files from package 

tapes. 

SLIB is required to execute the FKEY utility. 

SOLAR/E FAS is required to execute the LIBSAVE/FAS and LIBLOAD/FAS runstreams. 

FURPUR—SOLAR/E does not use FURPUR to read or write the system key 

table (SYS$*DATA$.KEYTABLE$). However, a loose dependency exists 

between SOLAR/E and FURPUR in that a compatible level of FURPUR is 

required to read the system key table version written by SOLA/E in order to 

perform product generation, COMUS installation, and general copying of files 

from package tapes. 

SLIB is required to execute the FKEY utility. 

SORT CKRS is an optional execution dependency. 

SYSLIB Required by FURPUR and PCFP. 

TAS ACOB is required to write program-callable COBOL applications. 

IPF is required if the IPF interface is used. 

UC is required to write program-callable C applications. 

UCOB is required to write program-callable UCOB applications. 

UDSC is required if you use the mail interface. 

UFTN is required to write program-callable UCS FORTRAN applications. 

TQ-BASELINE COMAPI is required for execution only if using a socket connection. 

TQ-MODEL is an optional execution dependency. 

CIPHER-API is required if you use FIPS 140-2 compliant encrypted user-id and 

password in the TQTCP configuration element for socket connections. 

TQ-ONLINE CIPHER-API is required if you use FIPS 140-2 compliant encrypted user-id and 

password in the TQTCP configuration element for socket connections. 

B–14 7831 0349–043


Support Name 



TQ-VIEW TeamQuest View (TQ-VIEW) requires Microsoft Windows. 


UC CKRS, DFP, DPS, I18NLIB, MCB, PCFP, SFS, SORT, and UREP are optional 

execution dependencies. 

PADS is required to do interactive debugging with PADS. 

RDMS is required to execute a program containing calls to rsa. 

CIFS is required to build or execute CIFSCC. If CIFS is not installed, CIFSCC is 

not rebuilt. 

UCOB CIFS and JVM are required to use the ZIP/UNZIP routines. 

CKRS, DFP, DPS, 18NLIB, MCB, PCFP, PDP, SFS, and UREP are optional 

execution dependencies. 

DMS is required to use DMS features with UCOB. 

PADS is required to use the debugging capabilities of PADS with UCOB. 

RDMS is required to use the Relational Database features with UCOB. 

UDSC ACOB is used for DMS subproduct generation. 

SORT is used by RDMS, DMS, and UREP subproducts during execution. 

UC is used for UREP subproduct generation. 

UFTN CKRS, DFP, DPS, MCB, PCFP, SFS, SORT, and UREP are optional execution 

dependencies. 

DMS is required to use the DMS features with UFTN. 

PADS is required to use the debugging capabilities of PADS with UFTN. 

RDMS is required to use the Relational Database features with UFTN. 

UPLS PADS is required to use the debugging capabilities of PADS with UPLS. 

PCIOS is required to do SEQUENTIAL or DIRECT I/O. 

UREP DMS, DPS, and RDMS are optional execution dependencies. 

IPF is required for the UREP editing feature. 

UC, UCOB, or UFTN are required only when the repository is used for storing or 

retrieving compile-time information. DPS is required only in similar 

circumstances. 

UREP must be installed in the default application group to use the features of 

UCS products that are integrated with RDMS or UREP on an alternate 

application group. 

URTS PCIOS is required if you do 

• SEQUENTIAL, RELATIVE, or INDEXED I/O in a UCOB program 

• SEQUENTIAL or DIRECT I/O in a UFTN program 

• TEXT or BINARY I/O in a UC program 

PCIOS is also required for some UPLS I/O. 

SORT is an optional execution dependency. 

7831 0349–043 B–15



Support Name 




IRU FSAH is required to execute a URU-OS2200 installed with Mode B 

installation. Mode B installation is required for nonstandard configurations of the 

COD audit trail or system log trail. It is also required to use the IRU 19R1or 

earlier IRU Move history file formats. URU Mode A uses the new Move history 

file formats. 

WEBTS Requires Windows XP, Windows 2000, or Windows 2003 for installation and 

execution of its Web Transaction Server Administration (WebTSA) utility. 

Requires a Java development environment (such as Sun Java Development Kit 

from Sun) if the JavaClient for DPS is used for Web-enabling DPS transactions. 

Requires the Flexible User Authentication (FLEX) facility of the OS 2200 

operating system to use the WEBTS Kerberos/NTLM feature. 

WMQ2200 OLTP-TM2200 is required for participation in global transactions. 

BIS is required to use the basic mode interface (BMI). The basic mode interface 

enables BIS to access the WebSphere MQ MQI. 

B–16 7831 0349–043

Appendix C 

Fast Load and Package Tape Contents 

This appendix identifies the products that are contained on fast-load tapes as well as 

package tapes. 

You can access the utility file (PRODSAVE$*UTILITY$) located at the beginning of each 

package tape to determine the location of each product on that tape. The element, TFD, 

contained in this file lists the products, product files, and their positions on the tape. 

For information on keyed-tape deliveries, including a listing of products that are not 

keyed, see 3.7. For information about the IXS 4000-BLD style, see 3.9. For ordering 

information, including style IDs, see the ClearPath Enterprise Servers Software Product 

Catalog. 

C.1. Logical Package Tape Definition 

Unisys software for the Dorado 300, 400, 700, 800, 4000, 4100, and 4200 systems is 

available on DVD media. This software packaging strategy allows the entire OS 2200 

software release to be packaged on a set of five DVDs. This strategy uses the following 

packaging definitions: 

• Physical Package – A media piece on which a software package resides. A physical 

package consists of one or more logical packages. 

• Logical Package – A grouping of products and extra files on a physical package. 

The logical package structure is based on current product package groupings. Each DVD 

media piece is a physical package consisting of multiple logical packages. 

If there are no installation dependencies or conflicts, you can select products in different 

logical packages on the same physical package for installation from the same 

runstream. Refer to the SOLAR User Reference Manual for detailed information about 

using the F12 function key from the Product selection screen. 

7831 0349–043 C–1

Products on Fast-Load Tapes 

Logical Package Tape Example Physical Package Tape Example 

The CP01 logical package tape contains 

the following set of products: 

CP01 

COMUS 

FURPUR 

PCFP 

ROLRUNS 

SOLAR 

The CPHD-03 DVD physical package tape contains a 

set of logical packages. Each logical package consists 

of the group of products: 

CPHD-03 

CP01 

CP02 

CP03 

CP04 

CP05 

CP06 

CP07 

C.2. Products on Fast-Load Tapes 

To support faster installation of the ClearPath Integrated Operating Environment (IOE) 

products, Unisys has created the following fast-load tapes: CP-FLD, CP-FLD400, 

CP-OE1A, CP-OE1B, and CP-OE2. The products on fast-load tape CP-FLD are nonkeyed, 

nonbuildable, and are installed in their default mode. Tape CP-OE1A and CP-OE1B are 

installed in their default mode and are keyed. You must install keys first before products 

can be installed. 

The following subsections describe the contents of the fast-load tapes. For information 

on installing products using fast-load tapes, see 7.6. 

Note: Once IOE products have been installed from fast-load tape, they need not be 

reinstalled from a package tape unless your site wishes to customize the installation for 

some reason. 

C.2.1. Fast-Load Tapes CP-FLD/CP-FLD400 

The fast-load tape CP-FLD or CP-FLD400 is the first tape that you should load. The 

CP-FLD tape is to be used for all systems except the Dorado 400. The CP-FLD400 tape 

is for Dorado 400 systems only. The CP-FLD and CP-FLD400 tapes contain products that 

must be installed on your current system before migrating to the new Exec. Table C–1 

lists the contents of tape CP-FLD. 


Support Name 

Table C–1. Tape CP-FLD Fast-Load Tape Contents 

COMUS COMUS 

CPComm Communications Platform 

Product Name 

CPCommOS Communications Platform for Open Systems 

CryptoLib Cryptographic Library 

FURPUR File Utility Routines/Program Utility Routines 

C–2 7831 0349–043


Support Name 


Table C–1. Tape CP-FLD Fast-Load Tape Contents 

PCFP Program-Callable FURPUR 

ROLRUNS Roll-Out/Roll-Back Runstream 

Product Name 

SILAS System Interface for Legacy Application Systems 

SOLAR Software Library Administrator 

SYSLIB System Service Routines Library 

C.2.2. Fast-Load Tape CP-OE1A 

Either Security-Admin or TeamQuest SIMAN is required to administer security. 

Table C–2 lists the contents of tape CP-OE1A. 


Support Name 

Table C–2. Tape CP-OE1A Fast-Load Tape Contents 

DAP Dump Analysis Procedures 

DMPLIB DMPLIB 

Product Name 

OLTP-TM2200 Open Distributed Transaction Processing 

Security-Admin Security-Admin 

SIMAN TeamQuest SIMAN 

C.2.3. Fast-Load Tape CP-OE1B 

Fast-load tape CP-OE1B contains IOE products that are typically installed in default mode 

and without any configuration changes (see Table C–3). Table C–3 lists the contents of 

tape CP-OE1B in alphabetical order, not in the order they are stacked on the tape. 


Support Name 

Table C–3. Tape CP-OE1B Fast-Load Tape Contents 

CML Common Mathematical Library 

CMR Console Message Redisplay 

COMAPI 

Product Name 

Communications Application Program Interface 

DDP-PPC Distributed Data Processing Program-to-Program 

Communications 

7831 0349–043 C–3



Support Name 


DPREP1100 DPREP1100 

ED ED 

Product Name 

ELMS Extended Language Message System 

ELT OS 2200 Element Processor 

FAS File Administration System 

GSA General Syntax Analyzer 

I18NLIB I18N Service Library 

IPF Interactive Processing Facility 

IRU Integrated Recovery Utility 

LINK Linking System 

LIST LIST Processor 

LSS Language Support System 

MAP Collector 

MASM Meta-Assembler 

MSCP Monitor Services Control Program 

NTSI Messaging Integration Services 

OUTPUT-MGR Enterprise Output Manager (EOM) for ClearPath OS 2200 

PADS Programmer’s Advanced Debugging System 

PCIOS Processor Common Input/Output System 

PDP Procedure Definition Processor 

PLUS PLUS 

PMD Postmortem Dump processor 

RDMSKEY Enterprise Relational Database Server for ClearPath OS 2200 

product key 

RSS Remote System Support 

SLIB Service Library 

SORT Sort/Merge Utility 

SSG Symbolic Stream Generator 

SYSLIB SYSLIB 

UC C Compiler 

UCSRTS Runtime System for Basic Mode Compilers 

C–4 7831 0349–043


Support Name 

Products on Package Tapes 


Product Name 

UPLS Universal Compiling System (UCS) PLUS 

URTS Runtime System for Extended Mode Compilers 

C.2.4. Fast-Load Tape CP-OE2 

Fast-load tape CP-OE2, like tapes CP-OE1A and CP-OE1B, was created to speed up 

installation. 

The CP-OE2 tape contains products (TIPUTIL, MCB, and Display Processing System) that 

might or might not need to be configured to your particular needs. If you do not need to 

reconfigure them, use the INSTALLPKG runstream to install those products in default 

mode. Table C–4 lists the contents of tape CP-OE2. 


Support Name 

Table C–4. Tape CP-OE2 Fast-Load Tape Contents 

DPS Display Processing System 

MCB Message Control Bank 

TIPUTIL Transaction Processing Utilities 

C.3. Products on Package Tapes 

Product Name 

Table C–5 lists the products available on keyed package tapes. The last column identifies 

the availability of the product on a fast-load tape. 

Note: For your convenience, we have listed the products in order by their installation 

and support names in the following table. The full names of the products are provided as 

well. 

Tape Name Installation and 

Support name 

Table C–5. DVD Package Tape Contents 

Product name DVD Package 

Tape 

CP01 COMUS COMUS CPHD-03 CP-FLD 

FURPUR File Utility 

Routines/Program 

Utility Routines 

PCFP Program-Callable 

FURPUR 

CPHD-03 CP-FLD 


Fast-Load Tape 

7831 0349–043 C–5



Support name 


ROLRUNS Roll-out/Roll-back 

Runstream 

SOLAR Software Library 

Administrator 

CP02 CML Common 

Mathematical Library 

DAP Dump Analysis 

Procedures 


Tape 



CPHD-03 CP-OE1B 

CPHD-03 CP-OE1A 

ED OS 2200 Text Editor CPHD-03 CP-OE1B 

ELT OS 2200 Element 

Processor 

FAS File Administration 

System 



I18NLIB I18N Service Library CPHD-03 CP-OE1B 

LIST LIST Processor CPHD-03 CP-OE1B 

MAP Collector CPHD-03 CP-OE1B 

MASM Meta-Assembler CPHD-03 CP-OE1B 

PDP Procedure Definition 

Processor 

RSS Remote System 

Support 



SLIB Service Library CPHD-03 CP-OE1B 

SSG Symbolic Stream 

Generator 

SYSLIB System Service 

Routines Library 

UCSRTS Runtime System for 

Basic Mode 

Compilers 

URTS Runtime System for 

Extended Mode 

Compilers 

CP03 ELMS Extended Language 

Message System 

CP04 




CP-OE1B 




LINK Linking System CPHD-03 CP-OE1B 

CIFS CIFS for ClearPath 


CPHD-03 

C–6 7831 0349–043


Support name 


CMR Console Message 

Redisplay 


Tape 



DPREP1100 DPREP1100 CPHD-03 CP-OE1B 

MSCP Monitor Services 

Control Program 

PMD Postmortem Dump 

processor 

CP05 CKRS Checkpoint/Restart CPHD-03 



DMPLIB DMPLIB CPHD-03 CP-OE1A 

FLEX User Authentication CPHD-03 

PADS Programmer’s 

Advanced 

Debugging System 

SEC-ADMIN Security 

Administration for 


TUTIL Tape Labeling Utility 

for ClearPath 


URU-OS2200 Utilization Report 

Utility for OS 2200 

CP06 LSS Language Support 

System 

CP07 FLIT Fault Location by 

Interpretive Testing 



CPHD-03 

CPHD-03 


CPHD-03 

PLUS PLUS CPHD-03 CP-OE1B 

UC C Compiler CPHD-03 CP-OE1B 

CP08 UCOB COBOL Compiler CPHD-04 

UFTN FORTRAN Compiler CPHD-04 

UPLS Universal Compiling 

System (UCS) PLUS 

CP09 ACOB ASCII COBOL 

Compiler 

EXPIPE Multiple Batch Run 

Optimizer 

FTN ASCII FORTRAN 

Compiler 


CPHD-04 

CPHD-04 

CPHD-04 


7831 0349–043 C–7



Support name 



Tape 

MMGR Media Manager CPHD-04 

PCIOS Processor Common 

Input/Output System 


SORT Sort/Merge Utility CPHD-04 CP-OE1B 

CP10 DDP-FJT Distributed Data 

Processing File and 

Job Transfer 

DDP-PPC Distributed Data 

Processing 

Program-to-Program 


IPF Interactive 

Processing Facility 

CP11 cpFTP FTP Services for 


DFP Define File 

Processor 

DPS Display Processing 

System 

GSA General Syntax 

Analyzer 

HTPIC-2200 OS 2200 High 

Performance 

Transaction 

Processing 

Interconnect 

NTSI Messaging 

Integration Services 

SOLAR/E Software Library 

Administrator 

Extended 

TAS Transmission Control 

Protocol/Internet 

Protocol (TCP/IP) 

Application Services 

CP12 IC2200 Interconnect for 

JProcessor and 

QProcessor 

JVM Virtual Machine for 

Java Platform 

CPHD-04 



CPHD-04 

CPHD-04 

CPHD-04 CP-OE2 


CPHD-04 


CPHD-04 

CPHD-04 

CPHD-04 

CPHD-04 


C–8 7831 0349–043


Support name 


CP13 IRU Integrated Recovery 

Utility 

UDSC Universal Database 

Control 

CP14 DMS Enterprise Network 


DMS-RA Network Database 

Server Resource 

Adapter for the Java 

Platform 

DMSKEY Enterprise Network 


product key 

CP15 RDMS Enterprise Relational 

Database Server for 


RDMS-JDBC Relational JDBC 

Driver for OS 2200 

RDMSKEY Enterprise Relational 

Database Server for 


product key 

CP16 FDP/ADP File Definition 

Processor/Applicatio 

n Processor 

INFOAccess ODBC Data Access - 

Corporate Edition 

QLP Query Language 

Processor 


Tape 



CPHD-05 

CPHD-05 

CPHD-05 

CPHD-05 

CPHD-05 

CPHD-05 


CPHD-05 

CPHD-05 

CPHD-05 

SFS Shared File System CPHD-05 

UNIACCESS UniAccess-ODBC CPHD-05 

UREP Repository for 


UREPKEY Repository for 


product key 

XRLOAD Relational Database 

Fast Load 

CPHD-05 

CPHD-05 

CPHD-05 

CP17 CIPHER-API CPHD-05 


7831 0349–043 C–9



Support name 


OLTP-TM2200 Open Distributed 

Transaction 

Processing 

OSI-TP Open Systems 

Interconnection 

Transaction 

Processing 

WEBTS Web Transaction 

Server 


Tape 


CPHD-05 

CPHD-05 

CP18 CULL TeamQuest CULL CPHD-05 

IACULL TeamQuest IACULL CPHD-05 

LA TeamQuest LA CPHD-05 

MSAR TeamQuest MSAR CPHD-05 

MSMANAGER TeamQuest 

MSManager 

CPHD-05 

OSAM TeamQuest OSAM CPHD-05 

PAR TeamQuest PAR CPHD-05 

SAUTILITIES TeamQuest 

SAUtilities 

CPHD-05 

SIMAN TeamQuest SIMAN CPHD-05 CP-OE1A 

TIP-LA TeamQuest TIP-LA CPHD-05 

TQ-BASELINE TeamQuest Baseline CPHD-05 

TQD-FRAGGER TeamQuest 

D-Fragger 

CPHD-05 

TQ-ONLINE TeamQuest Online CPHD-05 

TQ-PMLOG TeamQuest PMLog CPHD-05 

TQ-PROBES TeamQuest Probes CPHD-05 

TQRDFRAGGER TeamQuest 

RemD-Fragger 

CP-OPE OPE Open Programming 

Environment 

CP-SPF ARC Automatic Recovery 

of Components 

CARTIS Cartridge Tape 

Interface Software 

CARTLIB Cartridge Library 


CPHD-05 

CPHD-02 

CPHD-01 

CPHD-01 

CPHD-01 


C–10 7831 0349–043


Support name 


FBCIS Fixed Block 

Compatible Interface 


MHFS Multi-Host File 

Sharing 

PAEXEC Partitioned 

Applications 

executive portion 

SCSITIS Small Computer 

System Interface 

(SCSI) Software 


Tape 


CPHD-01 

CPHD-01 

CPHD-01 

CPHD-01 

SECOPT1 Security Level 1 CPHD-01 



SINCH Unisys Interconnect 

Channel Handler 

SIPIPM Software 

Instrumentation 

Package Internal 

Performance 

Monitor 

TAVR Tape Automatic 

Volume Recognition 

CPHD-01 

CPHD-01 

CPHD-01 

UDUPLEX Unit Duplexing CPHD-01 

VTH Virtual Tape Handler CPHD-01 

XPCEXEC Extended Processing 

Complex – Locking 

(XPC-L) software 

XTCEXEC Extended 

Transaction Capacity 

(XTC) software 

CP-TRN CITA Communications 

Interface for 

Transaction 

Applications 

MCB Message Control 

Bank 

TIPUTIL Transaction 

Processing Utilities 

CPHD-01 

CPHD-01 

CPHD-01 




7831 0349–043 C–11



Support name 


CP-COMM SUITE COMAPI Communications 

Application Program 

Interface 

CPComm 

Note: CPComm 

is used only with 

Dorado 300, 700, 

and 800 Server 

systems. 


Notes: 

• The CP-FLD is 

for use on 

Dorado 4000, 

4100, and 

4200 systems. 

• The 

CP-FLD400 is 

for use on 

Dorado 400 

systems. 

• Dorado 400 

systems must 

use 


level 2R2 . 


Tape 


Platform 


Platform for Open 

Systems 




CPHD-02 CP-FLD (Dorado 

4000, 4100, and 

4200 systems) 

CP-FLD400 

(Dorado 400 

systems) 

CryptoLib Cryptographic Library CPHD-02 CP-FLD 

SILAS System Interface for 

Legacy Application 

Systems 


C–12 7831 0349–043

Appendix D 

BDI Allocation 

A bank descriptor index (BDI) is the hardware name for a bank within the OS 2200 

addressing architecture. It is a numerical index that points to a specific bank. 

BDI allocation is a concern only at the application level of the OS 2200 address tree. 

Banks at the application level are also known as application level banks, common banks, 

or shared banks. These terms are all synonymous for code and data that is potentially 

accessible from all runs, programs, and activities running within the system. 

D.1. BDI Types 

There are two types of BDIs: fixed and dynamic. 

D.1.1. Fixed BDI 

Fixed BDIs are permanently allocated to particular banks and products. This allocation is 

globally defined and applies to all OS 2200 systems worldwide. In this way, programs 

that need access to services provided by these common banks can be created with the 

assurance that the targeted bank has the same index or name on any system. 

D.1.2. Dynamic BDI 

Dynamic BDIs are allocated to banks of object module subsystems (also known as 

extended mode subsystems). These banks are loaded when a subsystem is activated, or 

they are dynamically created during execution. Object module subsystems employ a 

single fixed BDI, which points to a fixed gate bank. A gate bank contains one gate per 

entry point into the subsystem. Gates are dynamically created and contain the acquired 

BDIs for the other banks of the subsystem. The gate bank is built at the time the 

subsystem is loaded, and it is updated when a bank is dynamically acquired. In this way, 

all of the banks of the object module subsystem can be dynamically assigned BDIs, 

rather than depend on fixed assignments. When the subsystem is deactivated, the BDIs 

can be reused. 

7831 0349–043 D–1

BDI System Generation Parameters 

D.2. BDI System Generation Parameters 

There are two system generation parameters that indicate the number of fixed or 

dynamic BDIs allowed. They are MAXBDI and APLDYNBDS, respectively. This 

subsection also identifies the highest-numbered BDI that might be referenced by basic 

mode programs. 

D.2.1. MAXBDI 

MAXBDI is an Exec system generation parameter that indicates the maximum number 

of fixed BDIs permitted. Its default, and recommended value, is 3121 (06061). If a value 

other than the default is selected, the allocation of BDIs (as described in this appendix) 

must be adjusted accordingly. In addition, application level products which have been 

given a fixed BDI greater than the selected MAXBDI will not function properly on the 

system. 

D.2.2. Basic Mode BDIs 

BDI number 4095 (07777) has special significance. This is the highest-numbered BDI 

that might be referenced by basic mode programs. Thus, 4095 becomes a line of 

demarcation separating basic mode banks, as well as those extended mode banks which 

must be accessed by basic mode programs, from banks which are exclusively extended 

mode. 

D–2 7831 0349–043

D.3. BDI Groups 

BDI Groups 

At present, the BDIs at the application level of the address tree are allocated into three 

groups: 

• Group 1: Fixed (between 1 and MAXBDI) 

• Group 2: Dynamic Code and Data (between MAXBDI+1 and 4095) 

• Group 3: Dynamic Code (between 4096 and 32766) 

GROUP 3 -----------------4096 through 32766-------------------------- 

Application Level Dynamic BDIs 

Used for Extended Mode Code & Data banks. This is 

the default for EM Code banks: 

Exec: GAP/SAP=Execute 

Linking System: BANK_TYPE=CODE 

GROUP 2--------------------------4095------------------------------ 

Application Level Dynamic BDIs (974 total BDIs) 

Used for Extended Mode Code & Data banks. This is 

the default for EM Data banks: 

Exec: GAP/SAP=Execute 

Linking System: BANK_TYPE=CODE 

Used when there are no banks > 4095 available. 

Used for Linking System control banks (2 per subsystem). 

GROUP 1---------------------MAXBDI (3121 default)------------------ 

FIXED BDIs (3121 total, 866 customer, 2255 'Unisys') 

Used for Basic Mode Common banks. 

Used for Object Module Subsystem Fixed Gate banks. 

------------------------------------------------------------------- 

Note: Group 3 banks cannot be referenced from basic mode. Also, any Executive 

Requests (ER) that reference BDIs in E,BDI (basic mode) format cannot be used with 

banks that have BDIs larger than 4095. 

7831 0349–043 D–3

Customer BDIs 

D.4. Customer BDIs 

Basic mode programs use 12 bits to specify a BDI, for a maximum of 4095 BDIs, while 

extended mode programs use 15 bits, for a maximum of 32767. Thus, the first 4095 

BDIs might be used by basic or extended mode programs, but the rest are only available 

to extended mode. 

Within the 3121 fixed BDIs defined by MAXBDI, 2255 are reserved for specific Unisys 

products and 866 are reserved for customer use. All 3121 fixed BDIs fall within the first 

4095 BDIs. 

The set of customer BDIs is defined as the following: 

0300 - 0323 

0400 - 0411 

0500 - 0511 

... 

then the first 10 (12 octal) from each 

100 octal through 03100 

03100 - 03111 

03200 - 03777 

05500 - 05777 

06000 - 06061 

... 

In addition, the following BDIs are reserved for customers: 

04600 - 04607 

04700 - 04707 

05100 - 05107 

05200 - 05207 

05300 - 05307 

05400 - 05407 

Note: BDIs are always denoted by octal numbers. BDIs are also often concatenated 

with the address tree level indicator and displayed as 18-bit numbers. For example, 

application level BDI 0300 might be referred to as 0400300 in basic mode and 0200300 

in extended mode. 

Caution 

When creating local common banks and subsystems, it is important to use 

only the customer set of BDIs. Local common banks include additional copies 

of standard Unisys products, such as UDS, MCB, and so forth, which might 

be installed in the same system, as would be the case with multiple 

application groups. Doing otherwise is highly discouraged as it creates the 

potential for conflicts with future standard Unisys products. 

D–4 7831 0349–043

BDI Allocation Listing 

Dynamic BDIs are allocated on an as needed basis. Therefore, there is no way to allocate 

BDIs to customer use versus Unisys product use, nor is there a way to enforce such a 

division. The mix of subsystems that can be active is limited by the local site setting of 

MAXBDI and the number of BDIs available between MAXBDI and 4095 (07777). 

D.5. BDI Allocation Listing 

Table D–1 lists all BDI allocations. It includes the bank name and the product for each 

BDI. This table reflects the BDI allocation information available at the time of publication. 

If any changes occur, they will be indicated in PLE 17662627. 

The value in the Bank Name column is not used for the BDIs associated with fixed gate 

subsystems. 

Note: The BDI Allocation listing is not specific to this release. 

BDI Bank Name Product 

1 RMATH$ CML 

2 DMATH$ CML 

3 CMATH$ CML 

4 NIOCB$ FOR 

5 ASM$ ASM 

6 NWBCB$ FOR 

7 ED$ ED 

10 LINK$FAULT EXEC 

11 FURPR$ FURPUR 

12 SPICB$ no-product 

13 T$SCRN EXEC 

14 ISICB$ SIMAN 

15 CTS$I CTS 

16 BSCAN$ CTS 

17 BFOR$I CTS 

20 C2A$ PCIOS 

21 C2S$ PCIOS 

22 C2D$ PCIOS 

23 C2E$ PCIOS 

24 C2I$ PCIOS 

25 C2F$LOCAL FTN 

Table D–1. BDI Allocation 


26 C2M$ PCIOS 

27 FTN$B1 FTN 

30 FTN$B2 FTN 

31 FTN$B3 FTN 

32 FTN$B4 FTN 

33 FTN$BU FTN 

34 FTN$BX FTN 

35 FTN$BE FTN 

36 CDMATH$ CML 

37 BFTN$I CTS 

40 PALS$ PALS (SYSTEM 11) 

40 SCPAR$ QLP 

41 TASK$ QLP 

42 NUALG$I12 NUALG 



45 C$DIAG ACOB 

46 C$SISAM ACOB 

47 C$SIIOB ACOB 

50 C$ANS ACOB 

51 C$MASS ACOB 

7831 0349–043 D–5



52 C$TAPE ACOB 

53 C$SDF ACOB 

54 C$CFH ACOB 

55 RPG$1 RPG 

56 RPG$2 RPG 

57 RPG$3 RPG 

60 QEDIT$ QLP 

61 C$SORT ACOB 

62 APL$MIXD APL 

63 BCOB$I CTS 

64 APL$QFMT APL 

65 APL$SCMD APL 

66 ACTCDB$ ACTS 

67 RESERVED UNISYS 


71 UDS$DMRICR DMS 

72 STAT$ CTS 

73 C$IBM ACOB 

74 C$LION ACOB 

75 C$FORM ACOB 

76 C$LABEL ACOB 

77 C$RPW ACOB 

100 C$ACS ACOB 

101 C$STRING ACOB 

102 C$CONV ACOB 

103 C$INITIAL ACOB 

104 C$MCS ACOB 

105 C$SYMBIONT ACOB 

106 C$DML ACOB 

107 PLS$U PLUS 

110 PLS$1 PLUS 

111 HVTS$CB HVTS 




114 PLS$R PLUS 


116 PLS$E PLUS 

117 HVTS$AC1 HVTS 

120 MDC$ MACRO 

121 MDP$ MACRO 


123 FTN$4YI FTN 

124 FTN$4XI FTN 

125 FTN$UTILITY FTN 

126 CPBBNK$ UCAD 

127 SCHBNK$ UCAD 

130 MASM$I MASM 


132 DMR2$ DMS 

133 DMR3$ DMS 

134 DMR4$ DMS 

135 DMR5$ DMS 

136 DMR6$ DMS 

137 BANK1S$$$ ACOB 




143 BANK5AS$$$ ACOB 

144 BANK5AL$$$ ACOB 


146 RFOR$I RFOR 

147 ROFR$I RFOR 

150 SCANNER$ UBASIC 

151 COMPEX$ UBASIC 

152 UTILITY$ UBASIC 

153 PL1$2A PL1 

D–6 7831 0349–043


154 PL1$E PL1 

155 PL1$1 PL1 

156 PL1$2B PL1 

157 PL1$3 PL1 

160 PL1$R PL1 

161 PL1$4 PL1 

162 PL1$5 PL1 

163 PIRCB$ SYSLIB 

164 TFC$IO EXEC 

165 RPG$RTL RPG 

166 SFILE$ QLP 

167 QPIM$ QLP 

170 CKPAR$ CKRS 

171 RSPAR$ CKRS 

172 CKFUL$ CKRS 

173 RSFUL$ CKRS 

174 C2PP$ PLUS 

175 CTS$ALT CTS 

176 CTS$ED CTS 

177 CTS$MDS CTS 

200 HVTS$AC2 HVTS 

201 HVTS$BCOM HVTS 

202 HVTS$BRUN HVTS 

203 HVTS$BSCN HVTS 

204 HVTS$CRE HVTS 

205 HVTS$DAT HVTS 

206 HVTS$EXP HVTS 

207 HVTS$FIN HVTS 

210 HVTS$HEL HVTS 

211 HVTS$HELP HVTS 

212 HVTS$II HVTS 

213 HVTS$LIS HVTS 

215 HVTS$MAS HVTS 



216 HVTS$MSG HVTS 

217 HVTS$OLD HVTS 

220 HVTS$SAV HVTS 

221 HVTS$SNP HVTS 

222 HVTS$STA HVTS 

223 HVTS$PUN HVTS 

224 APL$ APL 

225 APL$D APL 

226 APL$T APL 

227 APL$B APL 

230 APL$U APL 

231 APL$D4 APL 

232 BDI8$ ETP 

233 BDI7$ ETP 

234 BDI6$ ETP 

235 BDI5$ ETP 

236 BDI1$ ETP 

237 BDI2$ ETP 

240 BDI3$ ETP 

241 BDI4$ ETP 

242 FMS8BDI$ FMS8 

243 ERRMSGBDI$ FMS8 

244 BDI9$ ETP 

245 BDI10$ ETP 


247 CONTB$ QLP 

250 DIAG$ QLP 

251 QPRBK$ QLP 

252 QPABK$ QLP 


254 PADS$K PADS 

255 FTN$HELP FTN 

256 LOG$BK RPS 

7831 0349–043 D–7



257 DPY$BK RPS 

260 MSG$BK RPS 

261 OPN$BK RPS 

262 BLD$BK RPS 

263 USR$BK RPS 

264 FFL$BK RPS 

265 SRC$BK RPS 

266 DST$BK RPS 

267 TFR$BK RPS 

270 SRT$BK RPS 

271 PRT$BK RPS 

272 LUT$BK RPS 

273 MCH$BK RPS 

274 CMP$BK RPS 

275 IDX$BK RPS 

276 TUT$BK RPS 

277 FRM$BK RPS 

300 – 

323 RESERVED CUSTOMER 

324 HLP$BK RPS 

325 MAR$BK RPS 

326 PL1$2C PL1 

327 HVTS$FCOM HVTS 

330 HVTS$FRUN HVTS 

331 HVTS$FSCN HVTS 

332 HVTS$APL HVTS 

333 TASKS$ QLP 

334 DBP$IB1 DMS 





341 DBP$DB11 DMS 


























372 DPS$BK DPS 

373 C$BK1 EXEC 

374 C$BK2 EXEC 

375 FI$HBK EXEC 

376 MCSNCB$BDI PCCS 

377 MCSUCB$BDI PCCS 

400 – 


412 BANKES$$$ ACOB 

413 UTS4CB$ CMS 

414 C$DML8 ACOB 

D–8 7831 0349–043


415 IP$SSCB DDP-PPC 

416 IP$U000 IPF 

417 SM$INIT SORT 

420 SM$SORT SORT 

421 SM$MERGE SORT 

422 SM$EST SORT 

423 SM$ERR SORT 

424 DRU$DB1 DMS 










436 UNX-SSDEF$ MQSERIES-2200 


440 VOD$FGSS VoD 

441 NTSISS NTSI 

442 ADOISS ADOI 

443 PADS$RW PADS 

444 PADS$I PADS 

445 PADS$H PADS 

446 PADS$J PADS 

447 MINT$ QLP 

450 MDEF$ QLP 

451 HVTS$FTNB1 HVTS 



454 HVTS$FTNHELP HVTS 

455 HVTS$FTNBE HVTS 



456 HVTS$FTN4YI HVTS 

457 HVTS$FTNL HVTS 

460 HVTS$FTNLR HVTS 

461 HVTS$CON HVTS 

462 HVTS$BFTN HVTS 

463 PL1$IO PL1 

464 PL1$TSK PL1 

465 PL1$MEM PL1 

466 PL1$GEN PL1 

467 PL1$CHR PL1 

470 PL1$BIT PL1 

471 PL1$CNV PL1 

472 PL1$DESC PL1 

473 PL1$UTL PL1 

474 PL1$PIC PL1 

475 PL1$RET PL1 

476 IP$U002 IPF 

477 IP$U003 IPF 

500 – 


512 IP$U004 IPF 

513 IP$U005 IPF 

514 IP$U006 IPF 

515 IP$U007 IPF 

516 IP$U008 IPF 

517 IP$U009 IPF 

520 IP$U010 IPF 

521 IP$U011 IPF 

522 IP$U012 IPF 

523 IP$U013 IPF 

524 IP$U014 IPF 

525 IP$U015 IPF 

526 IP$U016 IPF 

527 IP$U017 IPF 

7831 0349–043 D–9



530 IP$U018 IPF 

531 IP$U019 IPF 

532 IP$U020 IPF 

533 IP$U021 IPF 

534 IP$U022 IPF 

535 IP$U023 IPF 

536 IP$U024 IPF 

537 IP$U025 IPF 

540 IP$U026 IPF 

541 IP$U027 IPF 

542 IP$U028 IPF 

543 IP$U029 IPF 

544 IP$CD00 DDP-PPC 










556 IP$QB00 IPF 

557 FJT$CB DDP-FJT 

560 IP$NETD DDP-PPC 

561 IP$MASCOM IPF 

562 IP$EXT IPF 


564 IP$U001 IPF 

565 URTS$PM1 URTS 

566 URTS$CH1 URTS 

567 URTS$DM1 URTS 

570 URTS$DM2 URTS 


571 URTS$OC1 URTS 

572 URTS$SP1 URTS 

573 URTS$SG1 URTS 

574 URTS$RC1 URTS 

575 URTS$UD1 URTS 

576 CTL$BNK1 MCB 

577 CTL$BNK2 MCB 

600 – 


612 MCBBNK$ MCB 

613 RNE$BNK1 MCB 

614 UPAS$RTSMSG UPAS 

615 PL1$SIO PL1 

616 PADS$L PADS 

617 PADS$M PADS 

620 MSB MSCP 

621 PADS$N PADS 

622 PADS$O PADS 

623 AFCBBANK1$ ETP 

624 AFCBB13$ ETP 

625 AFCBGBNK$ ETP 

626 AFCBRL$ ETP 

627 RPGII$01$ RPGII 












D–10 7831 0349–043








651 PADS$MSG PADS 

652 – 

657 RESERVED UDSC 

660 UDS$TCLCD001 UDSC 

661 – 


665 UDS$ADTCDB UDSC 

666 – 


700 – 


712 – 


723 UDS$DMRCKSUM DMS 


725 UDS$DMRLDM01 DMS 





732 UDS$DMRLINKR DMS 

733 RESERVED RDMS 


735 UDS$RDMICR RDMS 

736 – 


746 C2LDM$ SFS 

747 C2P$ SFS 

750 C2PICR$ SFS 

751 C2SRHD$ SFS 



752 C2SRHM$ SFS 

753 UDS$TCLCDICR UDSC 

754 DMR$LEV8 DMS 

755 VNXBNK MCB 

756 SES$I1 MASTERSHEET 

757 LINK$$I LINK 




763 RDPCDB$ RDP 

764 PERCONCDB$ PERCON 

765 ICOMOUTMSG$ CMR 

766 KANJI$CONV URTS 

767 RS$SSCB RSS 

770 RS$CD00 RSS 

771 RS$CD01 RSS 

772 RS$NETD RSS 

773 RS$NETI RSS 

774 RC$SSCB RSC 

775 RC$CD00 RSC 

776 RC$CD01 RSC 

777 RC$NETD RSC 

1000 – 


1012 RC$NETI RSC 

1013 CGOACB4 USAS CGO 

1014 MATP$Q USAS SYS 


1016 MESSAGEBNK UREP 

1017 REPORTBNK UREP 

1020 DDSBNK UREP 

1021 DSDBNK UREP 

1022 DDFBNK UREP 

1023 DDFUTIL UREP 

7831 0349–043 D–11



1024 DSRMAIN UREP 

1025 DSRBLD UREP 

1026 DSRUTL UREP 

1027 DDSEMBNK UREP 

1030 DDS$DDFUTIL2 UREP 

1031 PCIBNK1 UREP 








1041 UDS$EM$RICR RDMS 

1042 RSA$CFGSBDI RDMS 

1043 DDSICRBNK UREP 

1044 DBNK UREP 

1045 EPIPBNK UREP 


1047 URTS$$CH1 URTS 

1050 URTS$$DB1 URTS 

1051 URTS$$DM1 URTS 


1053 URTS$$OC1 URTS 

1054 URTS$$PM1 URTS 

1055 URTS$$RC1 URTS 


1057 URTS$$SG1 URTS 

1060 URTS$$SM1 URTS 






1065 URTS$$SP1 URTS 

1066 URTS$$UD1 URTS 


1070 DPS$CFBK DPS 




1074 C$RDMRPLB4 RDMS 

1075 IMSI$ IMS1100 

1076 IMSD$ IMS1100 

1077 IMSDREC$ IMS1100 

1100 – 


1112 – 

1131 RESERVED IMS1100 

1132 CS$$RETR DDP-PPC 

1133 FTAM$PROV1 OSI-FTAM 

1134 FTAM$MENU OSI-FTAM 

1135 FTAM$CD1 OSI-FTAM 

1136 FTAM$MSG1 OSI-FTAM 

1137 IPM$IBNK1 OSI-MHS 


1141 IPM$CDBNK OSI-MHS 

1142 MTA$MSGS OSI-MHS 


1144 MTA$IBNK2 OSI-MHS 

1145 DIR$IBNK1 OSI-MHS 

1146 IPM$PCIBNK1 OSI-MHS 



1151 BL$OPT2 LSS 


1153 BL$LOP2 LSS 


D–12 7831 0349–043


1155 KEY$BANK LSS 

1156 UCS$CDEBUG LSS 

1157 COBIBM LSS 

1160 FTNRDM LSS 

1161 CRDM LSS 

1162 COBDMS LSS 

1163 FTNDMS LSS 

1164 UCS$CMNI LSS 

1165 B$C LSS 

1166 JAVAVM JVM 

1167 B$PASERROR LSS 

1170 B$PASTOKEN LSS 

1171 B$PASMOST LSS 

1172 B$PLSMAIN UPLS 

1173 B$PLSMSG UPLS 

1174 B$PLSLS UPLS 

1175 B$PLSDS1DS2 UPLS 

1176 B$PLSDS3 UPLS 

1177 B$PLSDS4 UPLS 

1200 – 


1212 B$SKS LSS 

1213 B$REG LSS 

1214 B$SKI1 LSS 

1215 B$SRCALOC LSS 

1216 OM$$LIST LINK 

1217 LSC$$LIST LINK 

1220 B$CBERROR UCOB 

1221 B$COBMAIN UCOB 

1222 B$COBTEXT UCOB 

1223 B$COBTA UCOB 

1224 B$COBTB UCOB 

1225 B$COBTC UCOB 

1226 B$COBERROR UCOB 



1227 B$COBTOKEN UCOB 

1230 B$COBIDEXP UCOB 

1231 B$COBIDRES UCOB 

1232 B$COBEXPRES UCOB 

1233 B$COBDBASE UCOB 

1234 B$COBENV UCOB 

1235 B$COBDATR UCOB 

1236 B$COBDATA UCOB 

1237 B$COBRD UCOB 

1240 B$COBRDGRP UCOB 

1241 LINK$$I LINK 

1242 LINK$$I2 LINK 


1244 LINK$$D LINK 

1245 LINK$$E LINK 

1246 LINK$$OMOR LINK 

1247 LINK$$OMOR2 LINK 

1250 SLINK$I1 LINK 




1254 OM$$LIST LINK 

1255 LSC$$LINK LINK 

1256 LINKINGSYSTEM LINK 

1257 NPEAFCB1 LINK 

1260 NPEAFCB2 LINK 

1261 LINK$DEBUG LINK 

1262 SSDEFG JVM 

1263 BL$PASERROR UPAS 

1264 BL$PASTOKEN UPAS 

1265 BL$PASMOST UPAS 

1266 BL$EMCODE LSS 

1267 RESERVED LSS 

7831 0349–043 D–13



1270 CIFSHI CIFS 

1271 BL$DCM LSS 

1272 BL$TEX LSS 


1274 BL$SKS LSS 

1275 BL$REG LSS 

1276 BL$SKI1 LSS 

1277 BL$SRCALOC LSS 

1300 – 


1312 BL$SDDCROS LSS 


1314 BL$CBERROR LSS 

1315 BL$COBMAIN UCOB 

1316 BL$COBTD UCOB 

1317 BL$COBTA UCOB 

1320 BL$COBTB UCOB 

1321 BL$COBTC UCOB 

1322 BL$COBERROR UCOB 

1323 BL$COBTOKEN UCOB 

1324 BL$COBTE UCOB 

1325 BL$COBIDRES UCOB 

1326 BL$COBEXPRES UCOB 

1327 BL$COBTF UCOB 

1330 BL$COBENV UCOB 

1331 BL$COBDATR UCOB 

1332 BL$COBDATA UCOB 

1333 BL$COBRD UCOB 

1334 BL$COBRDGRP UCOB 


1336 BL$CBEINT LSS 

1337 BL$RDMBE LSS 

1340 BL$INI LSS 

1341 IP$$IA02 IPF 


1342 IP$$IA03 IPF 

1343 IP$$IA04 IPF 

1344 IP$$IA05 IPF 

1345 IP$$IA06 TAS 

1346 IP$$IA07 IPF 

1347 IP$$IA08 IPF 

1350 IP$$IB06 IPF 

1351 IP$$IB07 IPF 

1352 IP$$IB09 IPF 

1353 IP$$IH00 IPF 

1354 AD$$COMFAC IPF 

1355 AD$$PCICODE1 IPF 






1363 AD$$DDFCODE IPF 

1364 AD$$JUMPBANK IPF 

1365 AD$$EDITCMDS IPF 

1366 AD$$DEFNCMDS IPF 

1367 AD$$MISC IPF 

1370 AD$$FSAPPL IPF 

1371 IP$$IK01 IPF 

1372 IP$$IK03 IPF 

1373 IP$$IK04 IPF 

1374 IP$$IK05 IPF 

1375 IP$$IK06 IPF 

1376 IP$$IK08 IPF 

1377 IP$$IK11 IPF 

1400 – 


1412 IP$$IK12 IPF 

1413 IP$$IK13 IPF 

D–14 7831 0349–043


1414 IP$$IK14 IPF 

1415 IP$$IK17 IPF 

1416 IP$$IM00 DDP-PPC 

1417 SSD DDP-PPC 

1420 IP$$IM05 IPF 

1421 IP$$IM11 IPF 

1422 FJT$RCAS DDP-FJT 

1423 FJT$IPF DDP-FJT 

1424 FJT$WORK01 DDP-FJT 

1425 IP$$H000 IPF 

1426 IP$$H001 IPF 

1427 IP$$H002 IPF 

1430 IP$$H003 IPF 

1431 IP$$H004 IPF 

1432 IP$$H005 IPF 

1433 IP$$H006 IPF 

1434 IP$$H007 IPF 

1435 IP$$H008 IPF 

1436 IP$$H009 IPF 

1437 IP$$H010 IPF 

1440 IP$$H011 IPF 

1441 IP$$H012 IPF 

1442 IP$$H013 IPF 

1443 IP$$H014 IPF 

1444 IP$$H015 IPF 

1445 IP$$H016 TAS 

1446 FJT$MSG DDP-FJT 

1447 IP$$H018 IPF 

1450 IP$$H019 IPF 

1451 IP$$H020 IPF 

1452 IP$$H021 IPF 

1453 IP$$H022 TAS 

1454 IP$$H023 DIS1100 



1455 IP$$H024 IPF 


1457 IP$$CNTNG IPF 

1460 ROS$CBX ROSIE 

1461 LINK$$D LINK 

1462 IP$$DDPMSTEK IPF 

1463 IP$$IM07 IPF 

1464 MSGBNK MCB 

1465 MSGLNGBNK MCB 

1466 SM$SUB SORT 

1467 IP$$IM02 DDP-PPC 

1470 FJT$LCAS DDP-FJT 

1471 DPS$BK1 DPS 






1477 STATI$ TPAS 

1500 – 








1520 EPS$I$UTIL SUFICS 

1521 EPS$I$MAIN SUFICS 

1522 EPS$I$CALC SUFICS 

1523 EPS$I$CAL1 SUFICS 

1524 EPS$I$CAL2 SUFICS 

1525 EPS$I$DATA SUFICS 

1526 EPS$I$DISP SUFICS 

7831 0349–043 D–15



1527 EPS$I$FILE SUFICS 

1530 EPS$I$LOGN SUFICS 

1531 EPS$I$SENS SUFICS 

1532 EPS$I$FORE SUFICS 

1533 EPS$I$FORT SUFICS 

1534 EPS$I$HIER SUFICS 

1535 EPS$I$REGR SUFICS 

1536 EPS$I$STAT SUFICS 

1537 EPS440I$USCR SUFICS 

1540 – 

1551 RESERVED SUFICS 

1552 CONTB$ QLP 

1553 DIAG$ QLP 

1554 MDEF$ QLP 

1555 MINT$ QLP 

1556 QEDIT$ QLP 

1557 QPABK$ QLP 

1560 QPIM$ QLP 

1561 QPRBK$ QLP 

1562 SCPAR$ QLP 

1563 SFILE$ QLP 

1564 TASKS$ QLP 

1565 TASK$ QLP 

1566 PAD$MH PADS 

1567 IP$$IA00 TAS 

1570 IP$$IA01 TAS 

1571 RO$IBNK1 OSI-MHS 

1572 MTA$IBNK1 OSI-MHS 

1573 MTA$CDBNK OSI-MHS 


1575 IP$$IK07 TAS 

1576 DDN$IBNKM TAS 

1577 DDN$IBNKF TAS 

1600 – 

RESERVED CUSTOMER 


D–16 7831 0349–043 

1611 

1612 IP$$IK11 TAS 

1613 IP$$IN04 TAS 

1614 IP$$IN05 TAS 


1616 IP$IK15 COBEDT 




1622 UCS$PRIM no-product 

1623 PDP$I PDP 

1624 UCS$$COBRDML LSS 

1625 UCS$COBDEBUG URTS 

1626 UCS$PASDEBUG URTS 

1627 F$164I FPS-164 

1630 F$164D FPS-164 

1631 PUR$CSB PURCHASE1100 

1632 PUR$CDB PURCHASE1100 

1633 PUR$CNT PURCHASE1100 

1634 CSBUDT$ UNIDIS*TRANS 

1635 CDBUDT$ UNIDIS*TRANS 

1636 CNTUDT$ UNIDIS*TRANS 

1637 UCOB$RTSMSG UCOB 

1640 TTS$DRV1 TTS 

1641 LINC$DG1 LINCRT 



1644 ASETNCCB$ ASET 

1645 ASETCB$ ASET 

1646 ASETIPCB$ ASET 

1647 DPS$TSAM USAS 

1650 RES$ACB USAS 

1651 CKI$ACB USAS


1652 CGO$ACB USAS 

1653 FQT$ACB USAS 

1654 FDC$ACB USAS 

1655 SYS$ACB USAS 

1656 UCPDUW$ USAS 

1657 DPS$SUPR SUPREMA 

1660 ICES$CI ICES 

1661 ICES$DISK ICES 

1662 ICES$DYNARR ICES 

1663 ICES$ERRBNK ICES 

1664 ICES$FUNENT ICES 

1665 ICES$GRAPHS ICES 

1666 ICES$INITLS ICES 

1667 ICES$INTCOM ICES 

1670 ICES$LOADER ICES 

1671 ICES$PMM ICES 

1672 ICES$SAVRES ICES 

1673 ICES$SYSCOM ICES 

1674 ICES$UTILITY ICES 

1675 GRAPH$ADM TEMPLATE 

1676 GRAPH$AED TEMPLATE 

1677 GRAPH$ALP TEMPLATE 

1700 – 


1712 GRAPH$CAL TEMPLATE 

1713 GRAPH$DGG TEMPLATE 

1714 GRAPH$DMP TEMPLATE 

1715 GRAPH$ENV TEMPLATE 

1716 GRAPH$FCG TEMPLATE 

1717 GRAPH$GDM TEMPLATE 

1720 GRAPH$GEN TEMPLATE 

1721 GRAPH$HEW TEMPLATE 

1722 GRAPH$HOU TEMPLATE 

1723 GRAPH$HP2 TEMPLATE 



1724 GRAPH$H21 TEMPLATE 

1725 GRAPH$IDT TEMPLATE 

1726 GRAPH$JUP TEMPLATE 

1727 GRAPH$LA3 TEMPLATE 

1730 GRAPH$LEX TEMPLATE 

1731 GRAPH$MEG TEMPLATE 

1732 GRAPH$MGM TEMPLATE 

1733 GRAPH$MGP TEMPLATE 

1734 GRAPH$PDF TEMPLATE 

1735 GRAPH$PS3 TEMPLATE 

1736 GRAPH$PTR TEMPLATE 

1737 GRAPH$RM1 TEMPLATE 

1740 GRAPH$RM6 TEMPLATE 

1741 GRAPH$TEK TEMPLATE 

1742 GRAPH$TK1 TEMPLATE 



1745 GRAPH$SKO TEMPLATE 

1746 GRAPH$SPC TEMPLATE 

1747 GRAPH$U30 TEMPLATE 

1750 GRAPH$U60 TEMPLATE 

1751 GRAPH$VTK TEMPLATE 

1752 GRAPH$VIS TEMPLATE 

1753 GRAPH$VT6 TEMPLATE 

1754 GRAPH$ZET TEMPLATE 

1755 GRAPH$SUC TEMPLATE 

1756 GRAPH$DG1 TEMPLATE 







7831 0349–043 D–17






1770 CTLBNK USAS 

1771 ALT$ACB1 USAS 







2001 – 





2015 ARCBY$ ARC 

2016 ARCBY$DB ARC 



2021 URTS$$CM1 URTS 

2022 LINK$$OMOR LINK 

2023 SKMAPCDB$ PERCON 

2024 PERCON$CDB PERCON 

2025 XPERCON$CDB PERCON 

2026 UPLS$RTSMSG PLUS 

2027 MGASI$ MAPPER 

2030 MGASD$ MAPPER 

2031 IP$DI01 DIS1100 

2032 IP$DI02 DIS1100 

2033 IP$DI03 DIS1100 

2034 IP$DI04 DIS1100 

2035 IP$DI05 DIS1100 

2036 IP$DI06 DIS1100 


2037 IP$DI07 DIS1100 

2040 IP$DI08 DIS1100 

2041 IP$DI09 DIS1100 

2042 DS$DPS OSI-DIR 

2043 IP$IB06 TAS 

2044 BM$$CDB DDP-PPC 

2045 IP$DI13 DIS1100 

2046 IP$DI14 DIS1100 

2047 IP$DI15 DIS1100 

2050 IP$DI16 DIS1100 

2051 IP$DI17 DIS1100 

2052 IP$DI18 DIS1100 

2053 IP$DI19 DIS1100 

2054 IP$DI20 DIS1100 

2055 BL$GAP LSS 

2056 PROGEN$SUB PROGEN 

2057 PROGEN$FTN PROGEN 

2060 PROGEN$DPS PROGEN 

2061 MGASU$ MAPPER 

2062 B$COBRDML URTS 

2063 BL$RDML LSS 

2064 ITF$1 ITF 

2065 DDN$BANK DDP-PPC 

2066 PROGEN$CML PROGEN 

2067 FP$COMDATA FLEXPRINT 

2070 UCS$BASIC UBASIC 

2071 – 

2077 RESERVED DBSI 

2100 – 


2112 – 

2115 RESERVED DBSI 

2116 IFC$I OFISLINK 

2117 IFC$D OFISLINK 

D–18 7831 0349–043


2120 RDMS$EMICRBNK RDMS 

2121 RSA$CFGSBDI RDMS 

2122 IP$$IB05 TAS 

2123 IP$$IK09 TAS 

2124 IP$$IK10 TAS 

2125 BL$FTNMAIN UFTN 

2126 BL$FTNTP UFTN 

2127 BL$FTNIDRP UFTN 

2130 BL$FTNEPP UFTN 

2131 BL$FTNPSP UFTN 

2132 BL$FTNPEP UFTN 

2133 BL$FTNECP UFTN 

2134 BL$FTNCCP UFTN 

2135 BL$FTNXCP UFTN 

2136 BL$FTNCP UFTN 

2137 BL$FTNRP UFTN 

2140 BL$FTNMSG UFTN 

2141 UFTN$RTSMSG UFTN 

2142 TNASERM$ TNAS 

2143 TNASQRM$ TNAS 

2144 TNASBNK1$ TNAS 

2145 TNASBNK2$ TNAS 

2146 DDN$CB TAS 

2147 BL$COBTG UCOB 

2150 URTS$$BM1 URTS 





















2173 MHSQ$CDBNK OSI-MHS 

2174 MS$CDBNK OSI-MHS 


2176 RJEI$CDB SNARJE 


2200 – 


2212 PLS$BU$ PLUS 

2213 PLS$BE$ PLUS 

2214 PLS$BD$ PLUS 

2215 PLS$1A$ PLUS 

2216 PLS$DB$ PLUS 

2217 PLS$D1$ PLUS 

2220 PLS$DS$ PLUS 

2221 PLS$1B$ PLUS 

2222 PLS$B2$ PLUS 


2224 PLS$BR$ PLUS 


2226 PLS$4B$ PLUS 

2227 PLS$B4OMBAS$ PLUS 

2230 PLS$4BOMBAS$ PLUS 

2231 PLS$B4OMEXT$ PLUS 

2232 PLS$4BOMEXT$ PLUS 

7831 0349–043 D–19



2233 LINK$$E LINK 

2234 LU62INIT DDP-PPC 

2235 LU62MAIN DDP-PPC 

2236 LU62STAK SNAPPC 

2237 IP$STAK DDP-PPC 

2240 BLOCK$ UNIDAS 1100 

2241 UCB$1 UNIDAS 1100 

2242 UCB$2 UNIDAS 1100 

2243 UCB$3 UNIDAS 1100 

2244 UCB$4 UNIDAS 1100 

2245 UCB$5 UNIDAS 1100 

2246 UCB$6 UNIDAS 1100 

2247 UCB$7 UNIDAS 1100 

2250 UCB$8 UNIDAS 1100 

2251 UCB$9 UNIDAS 1100 

2252 UCB$10 UNIDAS 1100 

2253 GRRMI$ MAPPER 

2254 GRRUI$ MAPPER 

2255 PADS$EX PADS 

2256 PADS$P PADS 


2260 UCS$FTNDEBUG PADS 

2261 BL$DCM4 LSS 

2262 BL$DCM2 LSS 

2263 APEP$EM APEP 

2264 APEP$BM APEP 

2265 C2F$SC MASTERSHEET 

2266 DM$SC MASTERSHEET 

2267 RM$SC MASTERSHEET 

2270 C2S$SC MASTERSHEET 

2271 SU$DBT SUBAS 

2272 SU$PAP SUBAS 

2273 SU$FCT SUBAS 


2274 SU$PRT SUBAS 

2275 SU$MUT SUBAS 

2276 SU$SUB SUBAS 

2277 SU$DBI SUBAS 

2300 – 


2312 SU$DBL SUBAS 

2313 SU$DCL SUBAS 

2314 SU$CIL SUBAS 

2315 SU$SEP SUBAS 

2316 SU$CFB SUBAS 

2317 SU$CFL SUBAS 

2320 SU$LDS SUBAS 

2321 SU$LDL SUBAS 

2322 SU$MSG SUBAS 

2323 SU$VAR SUBAS 

2324 SU$DU1 SUBAS 

2325 SU$DU2 SUBAS 

2326 SU$XFC SUBAS 

2327 BLIH$D RS1000 

2330 BLIH$I RS1000 

2331 BL$PHRED RS1000 

2332 BL$$PHRED2 RS1000 

2333 FTP$$CB TAS 

2334 CIPHERBM1 CIPHER 

2335 CIPHEREM1 CIPHER 

2336 RESERVED RMRUN 

2337 RMRUN$UTIL RMRUN 

2340 RESERVED RMRUN 

2341 RM$BKALOC RMRUN 

2342 RM$PIMCB RMRUN 

2343 RM$CONTIN RMRUN 

2344 RM$BANK01 RMRUN 


D–20 7831 0349–043






















2372 LINK$$OMOR2 LINK 

2373 BL$ALI LSS 

2374 IP$IM06 IPF 

2375 C2D$SC MASTERSHEET 

2376 C2E$SC MASTERSHEET 

2377 C2A$SC MASTERSHEET 

2400 – 







2417 LLMS$ ELMS 



2420 OSI$SERVICES DDP-PPC 

2421 BL$$PHRED3 RS1000 

2422 BL$$PHRED4 RS1000 

2423 DTM$I MAPPER 

2424 DTM$D MAPPER 

2425 DTM$U MAPPER 

2426 DTM$T MAPPER 

2427 MTRRUN$ ARC 

2430 MRI$MI MAPPER 

2431 MRI$MU MAPPER 

2432 MRI$UI MAPPER 

2433 MRI$UD MAPPER 

2434 HCADS$DMR1 HCADS 




2440 UDS$ADTGATE UDSC 



2443 C2SFSE$ SFS 

2444 C2SFSM$ SFS 

2445 C2SFSD$ SFS 

2446 C2LDM2$ SFS 

2447 – 



2453 UDS$TCLCDICR UDSC 

2454 – 


2500 – 


2512 – 


2527 UDS$DMRLINKR DMS 


7831 0349–043 D–21








2536 UDS$DMRCKSUM DMS 

2537 MESSAGEBNK UREP 

2540 REPORTBNK UREP 

2541 DSDBNK UREP 

2542 DDFBNK UREP 

2543 DDFUTIL UREP 

2544 DSRMAIN UREP 

2545 DSRBLD UREP 


2547 DDSEMBNK UREP 

2550 DDS$DDFUTIL2 UREP 

2551- 










2564 DDSICRBNK UREP 

2565 DBNK UREP 

2566 EPIPBNK UREP 




2572 UDS$RDMICR RDMS 

2573 – 

RESERVED RDMS 


D–22 7831 0349–043 

2577 

2600 – 












2624 C2SFSE$ SFS 

2625 C2SFSM$ SFS 

2626 C2SFSD$ SFS 

2627 C2SRHD$ SFS 

2630 C2SRHM$ SFS 

2631 C2P$ SFS 

2632 C2PICR$ SFS 

2633 C2LDM$ SFS 

2634 C2LDM2$ SFS 

2635 UNADS$MASTER UNADS 

2636 LINE$COMP UNADS 

2637 PAGE$COMP UNADS 

2640 COMMANDS$1 UNADS 

2641 UNA$GRAPHIC UNADS 

2642 HANDLR$INPUT UNADS 

2643 UNA$INDEXING UNADS 


2645 UNADS$COMMON UNADS 

2646 HSPA$HNDLR UNADS 

2647 COMP80$HNDLR UNADS 

2650 LIN202$HNDLR UNADS


2651 APS5$HNDLR UNADS 

2652 HPLJ3$HNDLR UNADS 

2653 SP37$HNDLR UNADS 

2654 XX9700$HNDLR UNADS 

2655 DGDUMP EXEC 

2656 DGSUBS EXEC 

2657 MCBTARGET$EQ MCB 

2660 MSGTARGET$EQ MCB 

2661 LNGTARGET$EQ MCB 

2662 EMMCBBNK MCB 

2663 FSAH Product IRU 

2664 ALTFSAH IRU 

2665 – 


2671 PDS$0SM PDS 

2672 LINC$CB01 LINCII 






2700 – 


2712 PCFP$1 PCFP 






2720 – 








2732 AP7$DMRSHELL DMS 




2736 USR$SC MASTERSHEET 

2737 USAS$Q USAS 

2740 UCS$ACB URTS 

2741 FJT$CHKPT DDP-FJT 

2742 FJT$WORK02 DDP-FJT 

2743 FJT$INTF DDP-FJT 

2744 GATE-BDI DDP-PPC 

2745 FJT$DPS DDP-FJT 

2746 IP$$LTR DDP-PPC 


2750 IP$$MCP DDP-PPC 

2751 IP$$CSU DDP-PPC 

2752 SU$SUPT SUPER 

2753 SU$SUP1 SUPER 

2754 SU$SUP2 SUPER 

2755 SIMAN$GATE SIMAN 

2756 TIPUTIL$EM TIPUTIL 

2757 TIPUTIL$BM TIPUTIL 

2760 UOF$SYNC UOSS 

2761 – 


2771 OSMI$04 OSM MAIL 





2776 IPM$DPSCFG OSI-MHS 


7831 0349–043 D–23 

3000 

RESERVED CUSTOMER



– 

3011 

3012 RUA$CDBNK OSI-MHS 



3015 UN92$HNDLR UNADS 

3016 HPLJ2$HNDLR UNADS 

3017 DPS$BK1A DPS 

3020 DPS$BK4A DPS 

3021 DPS$BK4B DPS 

3022 DPS$BK4C DPS 

3023 UREPTEST1 UREP 



3026 SJE$I SJE1100 

3027 SJE$D SJE1100 

3030 COLLECTOR$01 MAP 








3040 MASM$R MASM 







3047 DDS$DPSCFG UREP 

3050 DDS$DPSCFG UREP 

3051 DDS3R1$A3 UREP 


3052 DDS3R1$B1 UREP 



3055 RITELINK$E LINK 

3056 FTP$$DMP TAS 

3057 FTP$$DMP1 TAS 

3060 FTP$$DMP2 TAS 

3061 MAIL$$DMP TAS 

3062 MAIL$$DMP1 TAS 

3063 MAIL$$DMP2 TAS 

3064 IP$IB07 TAS 

3065 MAIL$$PRT1 TAS 

3066 OIAP$CONFIG OIAP 

3067 RESERVED RMCOB 

3070 RMCOB$UTIL RMCOB 


3072 RM$CBL120 RMCOB 






3100 – 



3113 SYSLIB$1 SYSLIB 




3117 TRN$ACB USAS 

3120 ASR$ACB USAS 

3121 LDP$ACB USAS 

3122 MSG$ACB USAS 

3123 TKT$ACB USAS 

D–24 7831 0349–043


3124 HTL$ACB USAS 

3125 ISW$ACB USAS 

3126 PALS$PALS PALS 

3127 CKRSEMFCTN$ CKRS 

3130 FLP$ACB USAS 

3131 UCS$EXTENDED LSS 

3132 UCS$EAGLE URTS 

3133 SCHDMI$ MAPPER 

3134 SCHDBI$ MAPPER 

3135 SCHDP1$ MAPPER 







3144 BL$REG2 LSS 

3145 BL$COBRDGRP1 UCOB 

3146 UDS$DMRSHELL DMS 

3147 HCADS$$1 HCADS 





3154 REGBANK$ PEER 

3155 B$$CFEMAIN UC 

3156 B$$CFELS1 UC 

3157 B$$CFELS2 UC 

3160 B$$CFEDCL1 UC 



3163 B$$CFESTMT1 UC 





3166 B$$CFEDBG UC 

3167 B$$CFEMSG UC 


3171 EXECEP$BANK$ EXEC 

3172 BL$ORD LSS 

3173 $LUIBASE SNARJE 

3174 LUT1$INIT DDP-PPC 

3175 LUT1$MAIN DDP-PPC 

3176 LUT1$STAK DDP-PPC 


3200 – 


4000 – 

4043 RESERVED OPE 

4044 – 

4477 RESERVED SX1100 

4500 UREPTEST2 UREP 

4501 DDS$IRDS0001 UREP 

4502 DDSBNK UREP 

4503 – 


4514 EMSLIB$1 SLIB 

4515 DPS$TERMINDX DPS 

4516 DPS$FORMINDX DPS 

4517 LLMS$IB ELMS 

7831 0349–043 D–25 

4520 

CMS$UCIFS- 

AA/AB/AC/AD CPComm 

4520 CMS1100$TSAM CMS1100 

4521 CMS$BMIF-A CPComm 

4521 CMS1100$BMIF CMS1100 

4522 CMS$EMIF-A CPComm 

4522 CMS1100$EMIF CMS1100 

4523 SQL$PLS SQL-PLUS 

4524 SQL$CON SQL-CONNECT



4525 SQL$NET SQL-NET 

4526 SQL$COM SQL-NET 

4527 OL$PRINT OLPRINT 

4530 IB$$H026 SPW 

4531 IP$$ISPWF SPW 

4532 IP$$IK09 SPW 

4533 CMF$0SM CMF-SNAPSHOT 

4534 IP$$IK18 SPW 

4535 FTAM$BP OSI-FTAM 


4537 FJT$BP DDP-FJT 

4540 DSS$SUB DDP-PPC 

4541 DDP$MCB DDP-PPC 


4543 GIS$ACB USAS 



4545 ROS$RCB ROSIE 

4546 CTLH$CODE CTL 

4547 CTLH$QUE CTL 

4550 

CMS$UCIFS- 

TA/TB/TC/TD CPComm 

4550 CM$1100TSAM2 CMS1100 

4551 CMS$BMIF-T CPComm 

4551 CM$1100BMIF2 CMS1100 

4552 CMS$EMIF-T CPComm 

4552 CM$1100EMIF2 CMS1100 

4553 OSTP$EXTRACT ODS-HOST 

4554 OSTP$EXTEST ODS-HOST 




















4577 LINC7$ LINCII 

4600 – 










4620 SXNFS$ NFS-2200 

4621 DMSKEY$ DMS 

4622 RDMSKEY$ RDMS 

4623 UREPKEY$ UREP 

4624 PEERBANK$ PADS 

4625 – 


4635 OSI$$OUT DDP-PPC 

4636 OSI$$IN DDP-PPC 

4637 NFS$BK1 NFS-2200 

D–26 7831 0349–043


4640 LINC$MON1 LINCII 



4643 LINC$LAN1 LINCII 



4646 RAS$SLOG$ RASSLOG 

4647 2200$POSIX$ POSIX 

4650 2200-POSIX$ POSIX 

4651 MMPAR$ EXEC 

4652 HPXL3$HNDLR UNADS 


4654 IC2200 IC2200 



4657- 


4670 BATAP$ USAS 

4671 ROBOHST2$ ROBOHST2 

4672 INSP$GATE EXEC 

4673 BISAPI BIS 2200 

4674 BISAP2 BIS 2200 

4675 CPCIFR CIPHER 

4676 BISJVS BIS 2200 

4677 BISJV2 BIS 2200 

4700 – 


4710 PDBLP2 USAS 

4711 SYSACBLP2 USAS 

4712 RESACBLP2 USAS 

4713 CKIACBLP2 USAS 

4714 FDCACBLP2 USAS 

4715 CGOACBLP2 USAS 

4716 FQTACBLP2 USAS 



4717 CARACBLP2 USAS 

4720 TURACBLP2 USAS 

4721 MSGACBLP2 USAS 

4722 TKTACBLP2 USAS 

4723 PRFACBLP2 USAS 

4724 ISWACBLP2 USAS 

4725 ACRACBLP2 USAS 

4726 UCSACBLP2 USAS 

4727 GISACBLP2 USAS 

4730 LNCACBLP2 USAS 

4731 USAS$QLP2 USAS 

4732 BATA$PLP2 USAS 

4733 SCHDLRLP2 USAS 

4734 HTHUIBLP2 USAS 

4735 ALTACB1LP2 USAS 










4747 CMS1100$UOC CMS1100 

4750 SYSLNC USAS 

4751 SM$EMSUB SORT 

4752 SX1100EXTMD$ LSS 

4753 CBEP$TM/O HUBWARE DTP 

4754 TPE2NPE$BDI RASSLOG 


4756 TQ$BASELINE 

4757 TQ$STATI$EM TPAS 

BASELINE & 

ONLINE 

7831 0349–043 D–27



4760 ORA-CLIENT ORACLE Client 

4761 ORA-CLIENT2 ORACLE Client 

4762 SQLPLUS ORACLE Client 

4763 SQLPLUS2 ORACLE Client 

4764 PROCOB ORACLE Client 

4765 PROCOB2 ORACLE Client 

4766 PROC ORACLE Client 

4767 PROC2 ORACLE Client 

4770 CIPHER CIPHER 

4771 DB$XFER SAUtilities 

4772 DB$XFERGB SAUtilities 

4773 CPCOMMFGSS$E CPComm 

4774 CPCOMMFGSS$F CPComm 

4775 CPCOMMFGSS$G CPComm 

4776 CPCOMMFGSS$H CPComm 

4777 BM$MQSSSDEF$ MQSERIES-2200 

5000 PID$BNK1 MCB 


































5041 COR$BNK1 MCB 








5051 SIT$BNK1 MCB 









D–28 7831 0349–043






5066 TQ$BLCONTROL 

5067 TQ$BLPROBLEM 

BASELINE & 

ONLINE 

BASELINE & 

ONLINE 

5070 SSD OSI-TP 

5071– 


5075 ISO$RDA ISO-RDA 

5076 LINKINGSYSTEM LINK 

5077 MSB2NDCOPY EXEC 

5100 – 


5110 LINC$R01 LINCII 



5113 CARACBBDI USAS 

5114 TURACBBDI USAS 

5115 GATE_BDI UREP 

5116 DDSENTRY UREP 

5117 DDSSECD UREP 

5120 SECBNK UREP 

5121 GATE_BDI UREP 

5122 DDSENTRY UREP 

5123 DDSSECD UREP 

5124 SECBNK UREP 

5125 UCSEMX LSS 

5126 ATOMSBDI CNMS/2200 

5127 ATOMSBMIFBDI CNMS/2200 

5130 ATOMSEMIFBDI CNMS/2200 

5162 SSD OSI-DIR 

5163 APEP$SYST APEP 



5164 APEP$APPL APEP 

5165 MS$OSAM OSAM 

5166 LC$OSAM OSAM 

5167 RDMS$CFGSBDI RDMS 

5170 UDSC$PFGSBDI UDSC 

5171 UDSC$CFGSBDI UDSC 

5172 UDSC$TCLCD0003 UDSC 

5173 UOF$SYNCA UOSS 

5174 UTILITY$A CMR 

5175 CPCOMM$AFCB2 CPComm 

5176 COMAPI$C COMAPI 

5177 COMAPI$D COMAPI 

5200 – 


5210 RDMS$CFGSBDI RDMS 

5211 UDSC$PFGSBDI UDSC 

5212 UDSC$CFGSBDI UDSC 

5213 UDSC$TCLCD0003 UDSC 

5214 TM$BMAFCB OLTP-TM2200 

5215 TM$EMAFCB OLTP-TM2200 

5216 MS$OSAM$GATE OSAM 

5217 LC$OSAM$GATE OSAM 

5220 UACS UniAccess 

5221 CFRONT$GATE CFRONT 

5222 CPCOMMFGSS$A CPComm 

5223 CPCOMMFGSS$B CPComm 

5224 CPCOMMFGSS$C CPComm 

5225 CPCOMMFGSS$D CPComm 

5226 ORATG$GTW ORA-TG 

5227 ORATG$CM ORA-TG 

5230 Reserved UNISYS 

5231 Reserved UNISYS 

5232 I18NLIB$FGSS$ I18NLIB 

5233 I18NLIB$AFCB$ I18NLIB 

7831 0349–043 D–29



5234 I18NLIB$RTT$A$ I18NLIB 

5235 EBRSCB EBRS 

5236 EBRSCBGB EBRS 

5237 ASIS$BANK FLEX 

5240 EXPIPE$CMN EXPIPE 

5241 EXPIPE$CMNGB EXPIPE 

5242 XLT$SS InfoOFIS 

5243 FKEYFOUND$CB SOLAR Utility 

5244 FKEYFOUND$SS SOLAR Utility 

5245 MAPSEC MAPPER2200 

5246 WEBTS$SS WEBTS 

5247 WEBTS$ST WEBTS 

5250 IASSUB ODBC Access 

5251 IASOCK ODBC Access 

5252 CPFTPSS cpFTP 

5253 MSBDB MSCP 








5263 EBRADMSS EBRS 

5264 DB$EVENT DBEVENT 

5265 DB$EVENTGB DBEVENT 

5266 HPTPX OSI-TP 

5267 URST$EMDB2 URTS 

5270 URST$EMDB2 URTS 

5271 PPC$DPS DDP-PPC 

5272 APIX25 X25TIP 

5273 SILAS$UOC SILAS 

5274 CPCOMM$AFCB CPComm 


5275 CTCACB USAS*CTC 

5276 CPFTPSSB cpFTP 

5277 COMAPI$A COMAPI 

5300 – 


5310 DEPCON$I1 DEPCON 

5311 – 

5377 CAPPED SAVE 

5400 – 


5410 – 

5463 CAPPED SAVE 

5464 LINCRSS$1 LINCIIRT 



5467 LINC$RTS LINCIIRT 



5472 MSISS NTSI 



5475 COMAPI$B COMAPI 


5477 MQS-SSDEF$ MQSERIES-2200 

5500 – 


D–30 7831 0349–043

Appendix E 

Acronyms and Abbreviations 

This appendix defines the acronyms and abbreviations used in this overview and related 

Unisys documentation. 

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 Auto Answer 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 

AT audit trail 

ATM asynchronous transfer mode 

ATMCA Asynchronous Transfer Mode Channel Adapter 

BDI bank descriptor index 

BIF Built-in function 

BIS Business Information Server 

BMC block multiplexer channel 

7831 0349–043 E–1 

A 

B


CA channel adapter 

CADIS Cache/Disk Interface Software 

CAM channel adapter microcode 

CARTIS Cartridge Tape Interface Software 

CARTLIB Cartridge Library 

CARTTAPELIB Cartridge Tape Library 

CBD common bank descriptor 

CCS coded character set 

CD Communications Delivery 

CEC central electronics complex 

CER Customer Engineering Request 

CIFS Common Internet File System 

CIOP Communications I/O processor for Ethernet connections 

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 

CMS 1100 Communications Management System 

CMSR Customized Media Summary Report 

COMAPI Communications Application Program Interface 

COMPOOL communications message-buffer pool 

CPComm Communications Platform 

CPCommOS Communications Platform for Open Systems 

cpFTP FTP Services for ClearPath OS 2200 

CPM central processing module 

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 

E–2 7831 0349–043 

C

DAD Device Area Descriptor 

DAP Dump Analysis Procedures 

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 

DFP Define File Processor 

DML data manipulation language 

DMPLIB Dump Library 

DMS Enterprise Network Database Server 

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 

EBRS Enterprise Backup and Restore 

ECL Executive Control Language 

ED OS 2200 Text Editor 

EDRC Enhanced Data Recording Capability 

ELF Executive Link Function 

ELMS Extended Language Message System 

ELT Element Processor 

EM Extended Mode 

EOM Enterprise Output Manager (formerly DEPCON) 

7831 0349–043 E–3 

D 

E


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 

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 

FTP File Transfer Protocol 

FURPUR File Utility Routines/Program Utility Routines 

GRS general register set 

GSA General Syntax Analyzer 

E–4 7831 0349–043 

F 

G

HLC Host LAN Controller 

HMP Heterogeneous multiprocessing 

HVTIP High-Volume Transaction Processing 

I18NLIB Internationalization service routine library 


I18NLIB Assistant Online help for internationalization service routine library 

IACULL TeamQuest Interactive Cross Reference Generator 

ICP Initial Control Program 

ILES Independent Linked Exec Subsystem 

INFOACCESS ODBC Data Access 

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 

J2EE Java 2 Platform, Enterprise Edition 

J2SE Java 2 Platform, Standard Edition 

JBOSS-2200 JBoss Application Server 

JDBC Java DataBase Connectivity 

JNI Java Native Interface 

JPJVM Virtual Machine for the Javaî Platform on ClearPath OS 2200 JProcessor 

JVM Virtual Machine for the Javaî Platform on ClearPath OS 2200 

7831 0349–043 E–5 

H 

I 

J


LA TeamQuest Log Analyzer 

LAN local area network 

LDAT Logical Device Address Table 

LEPF Large element program file 

LFI Log File Interface 

LINC Logic and Information Network Compiler 

LINK Linking System 

LLMS Local Language Message System 

LPF large program file 

LSS Language Support System 

LTO Linear Tape Open 

MAP Collector 

MASM Meta-Assembler 

MCB Message Control Bank 

MCN Manufacturing Control Number 

MFD master file directory 

MHFS Multi-Host File Sharing 

MMGR Media Manager 

MPE Modular Processor EISA-Bus 

MQS2200 MQSeries for ClearPath OS 2200 

MSAR TeamQuest Mass Storage Analysis and Relocation processor 

MSB Monitor Services Bank 

MSCP Monitor Services Control Program 

MSMANAGER TeamQuest Mass Storage Manager 

NIC network interface card 

NIOP network I/O processor 

NTLM Windows NT LAN Manager 

NTSI Messaging Integration Services 

E–6 7831 0349–043 

L 

M 

N

Open DTP Open Distributed Transaction Processing 

OLE-DB-OS2200 Network Database OLE DB Data Provider 

OLTP online transaction processing 

OPE 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 

PADS Programmers Advanced Debugging System 

PAEXEC Partitioned Applications Exec 

PAR TeamQuest Performance Analysis Routines 

PBD page bank descriptor 

PCF permanent correction file 

PCFP Program-Callable FURPUR 

PCIOP peripheral component interconnect I/O processor 

PCIOS Processor Common Input/Output System 

PCT program control table 

PDP Procedure Definition Processor 

PFP Program File Package 

PLE problem list entry 

PLUS Programming Language for Unisys Systems 

PMD PostMortem Dump 

PPC Program-to-Program Communications 

QBR Queue Bank Repository 

QLP Query Language Processor 


7831 0349–043 E–7 

O 

P 

Q


RDMS Unisys Enterprise Relational Database Server 

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 

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) 

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 

E–8 7831 0349–043 

R 

S

SLAR System Log Analyzer and Reports 

SLI schema length information 

SLIB Service Library 

SLRR System Log Read Routines 

SNA Systems Network Architecture 

SNMP simple network management protocol 

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 

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 

TAS TCP/IP Application Services 

TAVR Tape Automatic Volume Recognition 

TCDBF TIP Common Data Bank File 

TCP/IP transmission control protocol/Internet protocol 

TIP Transaction Processing 

TMI table mapping information 

TPAS TeamQuest Transaction Performance Auditing System 

TPM TIP Performance Monitor 

TQ-BASELINE TeamQuest Baseline 

TQ-MODEL TeamQuest Model 

TQ-ONLINE TeamQuest Online 

TQ-PMLOG TeamQuest PMLog 

TQ-PROBES TeamQuest Probes 

TSAM Transport Service Access Method 

TS/TN termination system/transport network 


7831 0349–043 E–9 

T


TSU transport service user 

TUTIL Tape Labeling Utility 

UC C Compiler 

UCF User Communication Form 

UCOB COBOL Compiler 

UCPP C++ Compiler 

UCS Universal Compiling System 

UCSRTS Runtime System for Basic Mode Compilers 

UDI user-defined information 

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 

UOSS Unattended Operations Support 

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 

VALTAB validation table 

WAD Word addressable file 

WEBTS Unisys Web Transaction Server for ClearPath OS 2200 

WMQ2200 WebSphere® MQ Version 7 for ClearPath OS 2200 

E–10 7831 0349–043 

U 

V 

W

XIOP eXtended I/O Processor for connection to the XPC-L 

XML Extensible Markup Language 

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 

ZOOM zero overhead object module 


7831 0349–043 E–11 

X 

Z


E–12 7831 0349–043

Glossary 

A 

absolute element 

An executable basic mode program produced by the Collector after being compiled by an 

ASCII compiler. 

ACI 

See audit control interface. 

application group 

The designation for an application (database, programs, and audit trail) that is defined 

through Exec step control in OS 2200. A site can define up to nine application groups, 

numbered 1 through 9. An application group can be local (accessible to only one host), 

switchable (accessible to both hosts in a Partitioned Applications environment), or 

concurrent (accessible to all hosts in an XTC environment). TIP system files that must be 

accessed by all application groups are stored in the null application group. The null 

application group is automatically configured when the TIP system is generated, and is 

assigned to application group 0. 

application program 

A program that is designed to run in a transaction processing system. 

application user 

A person who enters a transaction code at a TIP terminal in order to execute a program 

belonging to a TIP application. 

ARF 

See audit recovery file. 

ASCII COBOL 

A programming language used to create transaction application programs. ASCII COBOL 

conforms to the ANSI standard for COBOL compilers. 

ASCII FORTRAN 

A programming language used to create transaction application programs. ASCII 

FORTRAN conforms to the ANSI standard for FORTRAN compilers. 

audit control 

The Exec feature that keeps track of recoverable events on the audit trail for an 

application group. The audit trail can be used to roll back or apply database updates after 

a program or system failure. 

7831 0349–043 Glossary–1

Glossary 

audit control interface (ACI) 

A mass storage file created and updated by the system that is used by step control and 

the IRU. This file contains data about audit trail media, such as the current tape reel. 

audit recovery file (ARF) 

An Exec file that defines the structure and state of the audit trail for an application group. 

Audit control uses the ARF to recover the state of the application group’s audit trail. 

B 

basic mode 

A type of program that is the result of compilation by the ASCII COBOL or ASCII 

FORTRAN compiler and collection by the Collector. The program is an absolute element. 

batch program 

A user-initiated program that runs in background mode. A batch program uses ECL 

statements to start execution, and by default it uses a READ$ and PRINT$ file for input 

and output. 

C 

CMS 1100 

See Communications Management System. 

Collector 

The Exec feature used to gather all executable elements needed to execute a basic 

mode program. 

Communications Management System (CMS 1100) 

The communications interface between the message control bank (MCB) and the enduser 

terminals. 

compiler 

A mechanism used to convert a high-level program into machine-readable form. 

COMPOOL 

A part of CMS 1100 that provides message-handling services for basic mode TIP 

application programs. 

CONECT primitive 

A TIP primitive that allows a batch or demand program to access TIP files. The program 

that connects to TIP is not registered with TIP, so execution options must be specified 

on the @XQT statement. 

Data Management System (DMS 2200) 

The component of the Universal Data System that application programmers use to 

create a network database model. 

Glossary–2 7831 0349–043

Glossary 

database 

A set of permanent files that belong to an application group and that organize data and 

access to the data in a particular way. The possible types of databases in a TIP 

applications environment are those handled by UDS data managers (DMS 2200, RDMS 

2200, or SFS 2200) and FCSS or Freespace databases, handled by TIP file control. 

Display Processing System (DPS 2200) 

The product that handles screen development and display. It can also handle messages 

for TIP programs that use either MCB or COMPOOL. 

duplex TIP file 

See TIP file. 

E 

ECL 

See Executive Control Language. 

Executive Control Language (ECL) 

The interface between users and the operating system. ECL provides a set of 

statements that allow users to start and control runs; generate and execute programs; 

create, delete, erase, copy, and otherwise manipulate files; and send messages to the 

console and to other terminals (if allowed). 

extended mode 

A type of program that is the result of compilation by the UCS COBOL, UCS FORTRAN, 

or UCS C compiler and linking by the UCS Linking System. The program is an object 

module; if it is a TIP or HVTIP program, it is a ZOOM. Object modules are linked 

dynamically; ZOOMs are the result of static linking, so they can be executed more 

quickly than object modules. 

Extended Transaction Capacity (XTC) 

A grouping of software features that supports both TIP and UDS environments. XTC 

provides increased processing capacity by using multiple hosts. 

Extended Transaction Processing Architecture (XTPA) 

Multiple-host systems that extend the availability and capacity of OS 2200 transaction 

processing environments. The XTPA systems available for OS 2200 are Extended 

Transaction Capacity (XTC) and Partitioned Applications. 

F 

FCSS 

Abbreviation for file control superstructure. See also TIP file control. 

FCSS file 

See TIP file. 

file control superstructure See TIP file control. 

7831 0349–043 Glossary–3

Glossary 

fixed mass storage 

Disks used for storing data that are logically defined as fixed (always present). Fixed 

mass storage is viewed by the Exec as one continuous pool of storage that consists of 

one or more disks. See also mass storage, removable mass storage. 

Freespace file 

See TIP file. 

Freespace Integrated Processing System (FREIPS) utility 

The TIP file control utility that the administrator uses to create and maintain FCSS or 

Freespace files. FREIPS is intended as a replacement for the TREG and TFUR TIP file 

control utilities. 

H 

High-Volume Transaction Processing (HVTIP) 

A group of performance options applied to TIP. HVTIP programs consist of brief modules 

that are compiled and linked independently as program banks and then executed in 

sequence. 

HVTIP program library 

A TIP file created by the system to hold HVTIP program banks, which the administrator 

copies into the library by means of the TPUR utility. There can be up to 64 HVTIP libraries 

on a system, numbered 0 through 63. A library can contain extended mode HVTIP 

ZOOMs or basic mode absolute programs. 

I 

ICP 

INITAL 

See initial control program. 

A TIP primitive that basic mode transaction programs can call to request input. See also 

multiple initialization. 

initial control program (ICP) 

The program used in HVTIP applications to initiate a transaction sequence. All modules 

defined for the transaction are called from within the initial control program. 

input message 

The transaction code and data that an application user enters at a TIP terminal in order to 

execute an application program. 

integrated recovery 

OS 2200 features that ensure database integrity and recoverability and, optionally, 

message recovery for TIP applications. 


The utility used in OS 2200 environments to recover programs, databases, and 

messages after a system or application failure. 

IRU 

See Integrated Recovery Utility. 

Glossary–4 7831 0349–043

L 

Glossary 

Linking System 

The feature used to link the executable elements needed to execute an extended mode 

program. 

local mass storage 

The set of disk devices that are accessible only to one host in a multihost environment. 

For single-host environments, the only option is to use local mass storage. 

M 

mass storage 

The disk or tape devices used to store information. Disks are the most common type of 

mass storage device. See also fixed mass storage, removable mass storage. 

master file directory (MFD) 

A directory maintained by the Exec to control cataloged files. The MFD contains the 

security attributes, look-up entries, and directory items needed to maintain cataloged 

files. Files listed in the master file directory are cataloged and retained after a run ends. 

MCB 

See Message Control Bank (MCB). 

Message Control Bank (MCB) 

The message handler for extended mode TIP programs and, optionally, for basic mode 

TIP programs. MCB provides message recovery and is intended as the replacement for 

COMPOOL. 

MFD 

MHFS 

MRF 

See master file directory. 

See Multi-Host File Sharing. 

Abbreviation for message retention file. 

Multi-Host File Sharing (MHFS) 

A separately packaged feature of the OS 2200 Exec that allows multiple hosts in a 

system to access shared mass storage devices. The MHFS feature associates Exec files 

with a local MFD or a shared MFD and handles the interhost communications necessary 

to deal with Exec file sharing across multiple hosts. This feature is needed in multiple 

host systems. See also Extended Transaction Capacity, Partitioned Applications. 

multiple initialization 

A type of program logic that allows the current copy of a TIP program to be kept ready 

for new scheduling requests. This type of program logic is often called multiple INITAL. 

O 

offline 

The state of a transaction program when it is not accessible to end users. The TIP file 

containing the transaction program must be brought online before users can access it. 

7831 0349–043 Glossary–5

Glossary 

online 

The state of a transaction program when it is accessible to end users for execution. 

online batch program 

A program that is registered with TIP through the validation table. It is scheduled by TIP, 

and has access to all TIP features and capabilities. A user executes an online batch 

program by entering the associated transaction code at a TIP terminal. 

output message 

The message that is displayed to the application user at a TIP terminal as a result of the 

execution of an application program. 

P 

Partitioned Applications 

A grouping of software features that increases system availability. In a Partitioned 

Applications environment, each host acts as a backup for the other host to achieve 

continuous processing. 

pass-off message 

A message with which one TIP program calls another and passes data for the other 

program to process. 

permanent TIP file 

See TIP file. 

position identifier (PID) 

An identifier by which CMS 1100 recognizes a TIP terminal that application users can 

use. The PID is the source of the input message for a TIP program and the destination of 

the output message. 

primitive 

A subroutine that allows a TIP program to request file-access or message-handling 

services from the Exec in a high-level language. TIP primitives are installed in a TIP 

system file when TIPUTIL is installed on the system. TIP file control primitives provide 

access to TIP databases. TIP message-handling primitives use the COMPOOL interface 

to provide services to basic mode TIP programs; the MCB primitive interface also uses 

COMPOOL. 

R 

record lock processor (RLP) 

A hardware device connected to all hosts in an XTC or Partitioned Applications 

environment. It is used by the hosts to coordinate and retain all database locks pertaining 

to the XTC shared TIP database. 

Record Lock Processor Configuration utility (RLPCON) 

The software feature used to configure the record lock processor on a system. This 

feature is part of the XTPA feature grouping. 

recovery 

The process of reconstructing files or data to a consistent state. 

Glossary–6 7831 0349–043

Relational Data Management System (RDMS 2200) 


create a relational database model. 

Glossary 

removable mass storage 

Disks used for storing data that are logically defined as removable (not fixed). See also 

fixed mass storage; mass storage. 

RLP 

See record lock processor. 

RLPCON 

See Record Lock Processor Configuration utility. 

RTPS 

S 

Abbreviation for resident transaction program system. 

scratch TIP file 

See TIP file. 

security level 

The security level defines the mandatory attributes of a subject or object. Specifically, 

the security level is the executing clearance level and compartment set for a subject, and 

the clearance level and compartment set for an object. 

Security Option 1 

Security Option 1 enhances the Fundamental Security package in the OS 2200 with all 

the features ownership enables, plus other features as well. Users have security records 

in addition to user-ids and passwords. The TIP file security feature is available with 

Security Option 1. This TIP feature extends the Exec file security protection to TIP files. 

See also TIP file security feature. 


Security Option 2 builds on the Fundamental Security and Security Option 1 packages for 

the OS 2200. The TIP message security feature is available with Security Option 2. The 

TIP message security feature controls message transmissions by comparing the security 

attributes of the sending and receiving TIP sessions. See also TIP message security. 


Security Option 3 provides the maximum OS 2200 security protection available. This 

option includes all the features available in the other security packages, and some 

additional features. 

Security Option 3 Controlled Access Protection Environment 

A special case of Security Option 3. This environment contains all of the discretionary 

access control features available with Security Option 3. This environment satisfies the 

Class C2 security requirements documented in the Department of Defense Trusted 

Computer System Evaluation Criteria. 

7831 0349–043 Glossary–7

Glossary 

Security Option 3 Trusted Environment 

A special case of Security Option 3. This environment is a specific hardware and 

software configuration evaluated by the National Computer Security Center to satisfy the 

Class B1 security requirements documented in the Department of Defense Trusted 

Computer System Evaluation Criteria. It includes all of the Security Option 3 features, 

plus the mandatory hardware security, physical security, and mandatory security 

procedures described in the Security Planning and Administration Reference Manual. 

Shared File System (SFS 2200) 


create shared data files. 

shared mass storage 

The set of disk devices that are accessible by one or more hosts in a multihost 

environment. Shared mass storage is used in XTC and Partitioned Applications systems 

to allow programs to access shared databases. 

simplex TIP file 

See TIP file. 

standard TIP program 

A transaction program that is registered with TIP but is not an HVTIP program. Standard 

TIP programs reside in TIP program files created and maintained by means of the SUPUR 

utility. 

step control 

The Exec feature that keeps track of program steps, the recoverable unit of processing in 

a TIP application, and handles the sequencing of database updates and recovery 

procedures. 

SUDS 

Abbreviation for UDS Control Supervisor utility program. 

SUPUR utility 

A TIP utility that an administrator uses to create a standard TIP program file from an 

FCSS file. The administrator copies extended mode ZOOMs or basic mode absolute 

elements into the file, from which the system loads them for execution. SUPUR allows 

TIP programs meeting certain requirements to use a fast-load option. 

symbolic element 

The source code for a program, before it has been compiled. 

T 

temporary TIP file 

See TIP file. 

TFUR utility 

A TIP utility that the administrator can use to reserve a TIP file in an Exec file registered 

with TIP. However, FREIPS is the preferred TIP file control utility. 

Glossary–8 7831 0349–043

TIP 

Glossary 

The OS 2200 environment in which transaction processing applications are created and 

maintained. The TIP system is integrated with the Exec. 

TIP common data bank file (TCDBF) 

An FCSS file that the administrator can set up to hold tables of static data. When the file 

is registered as a TCDBF, a copy of it is moved into main storage as a common bank, and 

any application program can reference it. 

TIP file 

A file reserved for TIP within a TIP/Exec file using the TFUR or FREIPS utility. Users can 

create a TIP file as a permanent, temporary, or scratch file. A permanent file can be a 

simplex or duplex file. At creation time, the user must define a TIP file as a TIP (FCSS) 

file, UDS/TIP file, or Freespace file. 

• UDS/TIP file: A permanent TIP user file that users access and maintain through UDS. 

The FREIPS utility is used to set up TIP user files as UDS/TIP files, with DMS 2200 

area numbers. The DMS 2200 areas are numbered downward from the upper end of 

the range of TIP file numbers. 

• duplex TIP file: A permanent TIP file with two identical legs (copies) that reside in 

two separate TIP/Exec files on separate (but identical) devices. At creation time, you 

define a file as either a simplex file or a duplex file. Updates to one leg of the file are 

automatically made to both legs of the duplex file. 

• Freespace file: A TIP user file in which the user application programs have record 

space allocated and released as needed by Freespace functions when calling FCSS. 

• permanent TIP file: A TIP file set up inside an Exec file for the application database. 

This type of file is assigned permanently to TIP, so any transaction program accesses 

it quickly, without having to assign it or release it. A permanent TIP file may be a TIP 

(FCSS) file, UDS/TIP file, or Freespace file. In the XTC environment, permanent TIP 

files can be defined by the site administrator in either the local or the shared TIP 

FCSS directory. 

• temporary TIP file: A fixed-length TIP (FCSS) file that can be assigned by a 

transaction or batch-connect program by means of the FCSS AS function. It remains 

in the system until specifically released. Shared TIP files cannot be used for 

temporary files. 

• scratch TIP file: A fixed-length TIP (FCSS) file that can be assigned by a transaction or 

batch-connect program by means of the FCSS AS function. This type of file exists 

only for the duration of the execution or connect period, and is released 

automatically by TIP. It may be released by a TIP file control call before termination 

of the execution or connect period. Shared TIP files cannot be used for scratch files. 

• simplex TIP file: A permanent TIP file that exists as a single copy in a TIP/Exec file. 

• TIP (FCSS) file: A TIP user file with a fixed record structure that is accessed and 

maintained through TIP file control. The TFUR or FREIPS utility is used to set up a 

TIP (FCSS) file. 

TIP file control 

An Exec component that handles the creation and maintenance of FCSS and Freespace 

files and access to the files. It is also called TIP file control superstructure (FCSS). 

7831 0349–043 Glossary–9

Glossary 

TIP file duplexing 

A method for establishing duplicate copies of TIP files. Duplexed TIP files are maintained 

by TIP file control. Duplexing TIP files ensures data integrity and availability in the event 

of a disk or file failure. See also duplex files; Unit Duplexing. 

TIP file security 

A security feature that allows the access control specified for Exec files to be extended 

to the TIP files that they contain. See also TIP message security; TIP session control. 

TIP message security 

A security feature that allows the tracking of each message in the TIP system and of the 

user involved in each message. 

TIP program file 

A TIP file in which TIP programs reside and from which they are loaded for execution. 

SUPUR program files are containers for standard TIP programs; HVTIP program libraries 

are containers for HVTIP program banks. Standard online program files can also be used 

for standard TIP programs, but SUPUR program files are intended as replacements for 

the online files. 

TIP scheduling 

The TIP feature that locates a TIP program after an application user has entered the 

transaction code, loads the program, and schedules it for execution. 

TIP session control 

A security feature that requires all TIP users to sign on to the TIP system before they can 

execute any TIP programs. 

TIPUTIL 

The TIP product release files, which contain the TIP utilities and primitives. 

TPUR utility 

A TIP utility that the administrator uses to copy HVTIP program banks into an HVTIP 

program library and maintain the library. 

transaction code 

A unique code that an application user enters at a TIP terminal to execute a TIP program. 

The transaction code is associated with the program and its attributes through its 

validation table entry. 

transaction processing 

A method used to perform small, well-defined activities in a small amount of time. 

Transaction processing methods are used in airline reservations, payroll, inventory, and 

other applications for which fast data access and processing speed are required. 

transaction program 

A short program that typically requires a single input, processes the input, and produces 

a single output. In a TIP applications environment, this program is registered with TIP so 

that it can be executed at a high priority. 

Glossary–10 7831 0349–043

Glossary 

TREG utility 

A TIP utility that the administrator can use to register an Exec file with TIP. However, 

FREIPS is the preferred TIP file control utility. 

U 

UCS 

UCS C 

See Universal Compiling System (UCS). 

The compiler used on OS 2200 systems to compile extended mode programs written in 

the C programming language. 

UCS COBOL 


the COBOL programming language. 

UCS FORTRAN 


the FORTRAN programming language. 

UDS 

See Universal Data System. 

UDS Control 

The component of the Universal Data System that controls locking, cache management, 

recovery, system table control, and thread control for all UDS data management facilities. 

UDS/TIP file 

See TIP file. 

Unisys Repository Manager (UREP) 

A container for data objects and other database information used by components of 

UDS. Programmers can use UREP to define runstreams and programs that use the data 

contained in UREP. 

Unit Duplexing 

An Exec feature that maintains two disk devices with identical information. This disk 

redundance method ensures data integrity and availability in the event that a disk, disk 

device, or file failure occurs. See also duplex files; TIP file duplexing. 

Universal Compiling System (UCS) 

A feature grouping that includes the UCS COBOL, UCS FORTRAN, and UCS C compilers 

and the Linking System. UCS produces extended mode programs. 

Universal Data System (UDS) 

A system for complete database creation and management that includes UDS Control 

and its three data managers, DMS 2200, RDMS 2200, and SFS 2200. UDS provides 

access to any of the databases. 

UREP 

See Unisys Repository Manager. 

7831 0349–043 Glossary–11

Glossary 

utility 

V 

A program that provides a simple interface for the administrator to Exec and TIP file 

control services. TIP utilities are installed in a TIP system file when TIPUTIL is installed 

on the system. 

validation table (VALTAB) 

A structure that TIP uses for locating and executing TIP programs. The system creates 

the VALTAB in a TIP system file. For each TIP program, the administrator uses the 

VTBUTL utility to create a VALTAB entry that identifies a unique transaction code and 

program number for the program and its loading and execution attributes. 

VALTAB index (VINDEX) 

A separate area in the VALTAB file to help TIP locate TIP programs registered in the 

VALTAB. 

VTBUTL utility 

The TIP utility that the administrator uses to create VALTAB entries for TIP programs, in 

order to register them with TIP. The administrator also uses the utility to change or 

delete entries in the VALTAB. 

X 

XTC 

See Extended Transaction Capacity. 

XTCEXEC 

A feature used in XTC environments that allows application programs running on multiple 

hosts to access shared TIP files. 

XTPA 

Z 

See Extended Transaction Processing Architecture. 

zero overhead object module (ZOOM) 

An extended mode TIP or HVTIP program produced by static linking. 

Glossary–12 7831 0349–043

Index 

A 

ACOB 

package tape location, C-7 

release level, 1-5 

acronyms and abbreviations, E-1 

ARC 

current level, 1-10 


ASCII COBOL Compiler (ACOB) 


ASCII FORTRAN Compiler (FTN) release 

level, 1-6 

auditing software before migrating, 7-2 

B 

bank descriptor index (BDI) 

listing of, D-5 

reserved for customers, D-4 

system generation parameters, D-2 

types, D-1 

Business Information Server 

considerations, 5-1 

C 

C Compiler (UC) 


CARTIS 



CARTLIB 



checklist, migration planning, 7-2 

CIFS 




CIPHER API 


CITA 



CKRS 












ClearPath Plus 

IOE content 

Business Information Server (BIS), A-3, 

A-9, A-16 

Enterprise Application Environment 

(EAE), A-3, A-9, A-16 

general-purpose workload, A-3, A-9, 

A-16 

Software Development Kit (SDK), A-3, 

A-9, A-16 

CML 

fast-load tape location, C-3 



CMR 




COBOL Compiler (UCOB) 



Collector (MAP) release level, 1-7 

COMAPI 




Communications Application Program 

Interface (COMAPI) release level, 1-5 

7831 0349–043 Index–1

Index 

Communications Interface for Transaction 

Applications (CITA) release level, 1-5 

Communications Platform 


Communications Platform for Open Systems 


compliance 

Image Enabler Key, 3-23 

software product key, 3-23 

COMUS 




security privileges, 5-47 

considerations 

Business Information Server 

(MAPPER), 5-1 

CIFS, 5-2 

CKRS, 5-4 

ClearPath OS 2200 Release 12.1, 3-6 



ClearPath OS 2200 Release 13.2, 3-1 

COMUS, 5-13 

CPComm, 5-6 

CPCommOS, 5-9 

cpFTP, 5-15 

DDP-FJT, 5-17 

DDP-PPC, 5-18 

DMS, 5-22 

DMS-RA, 5-16 

ECLIPSE-2200, 5-19 

ELMS, 5-20 

Enterprise Output Manager (EOM), 5-21 

FORTRAN Compiler (UFTN), 5-15 

I18NLIB, 5-30 

IPF, 5-30 

IRU, 5-26 

J2JEE-CON-2200, 5-30 

JPJVM, 5-60 

JVM, 5-59 

LINK, 5-31 

LSS, 5-31 

MCB, 5-32 

NTSI, 5-33 

ODBC Data Access, 5-34 

OLTP-TM2200, 5-35 

OSI-TP, 5-41 

RDMS, 5-23 

RDMS-JDBC, 5-41, 5-42 

RSS, 5-42 

SOLAR, 5-46 

SORT, 5-49 

SSG, 5-49 

SYSLIB, 5-51 

TAS, 5-52 

TUTIL, 5-52 

UDSC, 5-56 

UniAccess-ODBC, 5-56 

UREP, 5-43 

URTS, 5-45 

URU-OS2200, 5-57 

WEBTS, 5-61 

console 

OS 2200 Server Management 

Control, 3-39 

System Architecture Interface Layer 

control center, 3-39 

CPComm 


fast-load tape installation, 7-9, 7-18 



package-tape installation, 7-28 




fast-load tape installation, 7-9, 7-18, 7-37 




CP-FLD 

fast-load tape, 7-5 

tape contents, C-2 

cpFTP (FTP Services) 




CP-OE1A and CP-OE1B 



CP-OE2 



Cryptographic Library 


CryptoLib 



CTS5136 tape subsystem 




microcode, 3-48 



Index–2 7831 0349–043

microcode, 3-48 

CTS9840C tape subsystem 


CTS9940B tape subsystem 


CULL 


D 

DAP 




DDP-FJT 




DDP-PPC 

considerations, 5-18, 7-3 




Define File Processor (DFP) 


DEPCON (Enterprise Output Manager) 

workstation requirements, 6-1 

DFP (Define File Processor) 



diagnostic file 

noncompliance message, SOLAR, 3-18 

discontinued products, 3-14 

Distributed Transaction Integration (DTI) 


DLT 7000 and DLT 8000 tape 


DMPLIB 



DMPLIB fast-load tape location, C-3 

DMS (Enterprise Network Database Server) 


DMSKEY package tape location, C-9 



DMS-RA 



DPREP1100 




DPS 




DTI (Distributed Transaction Integration) 


DVD software media, 1-4, 4-36, C-1 

Index 

7831 0349–043 Index–3 

E 

ECLIPSE-2200 



ED 


ELMS 





ELT 




Enterprise Network Database Server (DMS) 




Enterprise Output Manager (DEPCON) 


Enterprise Output Manager (EOM) 




workstation requirements, 6-1 

Enterprise Relational Database Server 

(RDMS) 



EPORTAL-2200 


Exec 

log entry changes, 4-9 


separately packaged features 

ARC, 1-10 

CARTIS, 1-10 

CARTLIB, 1-10 

DMPLIB, 1-10

Index 

FBCIS, 1-10 

MHFS, 1-10 

MMGR, 1-10 

MSCP, 1-10 

PAEXEC, 1-10 

SCSITIS, 1-10 

SECOPT1, 1-10 

SECOPT2, 1-10 

SECOPT3, 1-10 

SINCH, 1-10 

SIPIPM, 1-10 

TAVR, 1-10 

TIPUTIL, 1-10 

UDUPLEX, 1-10 

VTH, 1-10 

XPCEXEC, 1-10 

XTCEXEC, 1-10 

SGS and configuration parameters 


tape and DVD considerations, 4-10 

EXPIPE 



F 

FAS 




fast-load tapes 

CP-FLD, C-2 

CP-OE1A and CP-OE1B, C-3 

CP-OE2, C-5 

descriptions, 7-5 

migration requirements, 7-6 

FBCIS 



FDP/ADP package tape location, C-9 

FLEX 



FLIT 




FORTRAN Compiler (UFTN) 



FTN 



FTP Services (cpFTP) release level, 1-5 

FURPUR 



Index–4 7831 0349–043 

G 

GSA 




H 

HTPIC 2200 



I 

I18NLIB 


I18NLIB 


I18NLIB 


I18NLIB 


Image Enabler Key 

compliance, 3-23 

description, 4-40 

MIPS-based, Dorado 150, 240, and 

340, 4-41 

MIPS-metered, 4-41 

new format, 3-20 

old format, 3-20 

removal warning, 3-25 

software performance, 3-16 

INFOAccess 


INFOAccess (ODBC Data Access) 


initializing Cipher API, 5-2 

installation sequences 


initializing an existing system, 7-26 

installing products from fast-load tapes, 7-6

installing products from package 

tapes, 7-15 

installation verification procedures (IVP), 5-47 

INTERCONNECT 


IOCQ, 4-6 

IOE content 

ClearPath Plus 

Business Information Server (BIS), A-3, 

A-9, A-16 

Enterprise Application Environment 

(EAE), A-3, A-9, A-16 

general-purpose workload, A-3, A-9, 

A-16 

Software Development Kit (SDK), A-3, 

A-9, A-16 

IPF (Interactive Processing Facility) 





IRU 





J 

J2JEE-CON-2200 



interdependency, B-12 


JPJVM 



JVM 




K 

key 

Image Enabler key 

new format, 3-20 

old format, 3-20 

tape delivery 

introduction, 3-29 

Index 

7831 0349–043 Index–5 

L 

levels for Separately Packaged Exec Features 

(SPEF), 1-10 

LINK (Linking System) 





LIST 




local code, auditing when migrating, 7-2 

LSS (Language Support System) 





M 

maintenance LAN, 3-39 

MAP 




MAPPER considerations, 5-1 

MASM 




master SCN, 3-17 

MCB 





MCN (manufacturing control number), 3-16 

Media Manager 


media, software 

DVD, 1-4, 4-36, C-1 

tape, 4-14, 4-23, 4-26, 4-33, 7-3, A-1 

Messaging Integration Services (NTSI) 



metered systems, 1-1 

MHFS 


package tape location, C-11

Index 

migration 

fast-load tapes, 7-6 

package tapes, 7-15 

planning checklist, 7-2 

MIPS-based Image Enabler Key, Dorado 150, 

240, and 340, 4-41 

MMGR current level, 1-10 

MQS2200 (MQSeries for ClearPath OS 2200) 


MSAR 


MSCP 




MSMANAGER 


MSMQI 


Multiple Batch Run Optimizer (EXPIPE) 


N 

new format Image Enabler Key, 3-20 

NTSI (Messaging Integration Services) 





O 

ODBC Data Access (INFOAccess) 



old format Image Enabler Key, 3-20 








Operations Sentinel (SP-OPERATION), 1-7, 

5-40 

Operations Sentinel, runs on, 3-39 

Operations Server, 3-39 

OS 2200 Server Management Control 

runs on, 3-39 

OSAM 






OST4890 tape subsystem 


Index–6 7831 0349–043 

P 

package tapes 

migration requirements, 7-15 

packaging, software 

Exec base symbolic tape, A-1 

Exec release master information tape, A-1 

Exec release master tape, A-1 

preconfigured boot tape, A-1 

PADS 




PAEXEC 



PAR 


PCFP 



PCIOS 




PDP 




PLUS 




PMD 




PRODSV utility, 3-29 

product key 

DMS (Enterprise Network Database 

Server), C-9

RDMS (Enterprise Relational Database 

Server), C-9 

TeamQuest, 3-32 

UREP, C-9 

profile, SCN, 3-19 

Q 

QLP 



R 

RDMS (Enterprise Relational Database 

Server) 



RDMSKEY 




RDMS-JDBC 



Relational JDBC Driver 



release level 

ACOB, 1-5 

CIFS, 1-5 

CIPHER-API, 1-5 

CITA, 1-5 

CKRS, 1-5 

CML, 1-5 

CMR, 1-5 

COMAPI, 1-5 

COMUS, 1-5 

CPComm, 1-5 

CPCommOS, 1-5 

cpFTP, 1-5 

CryptoLib, 1-5 

CULL, 1-5 

DAP, 1-5 

DDP-FJT, 1-5 

DDP-PPC, 1-5 

DEPCON-2200, 1-5 

DFP, 1-5 

DMS, 1-5 

DMS-RA, 1-5 

Index 

DPREP1100, 1-5 

DPS, 1-5 

DTI, 1-5 

ECLIPSE-2200, 1-5 

ELMS, 1-6 

ELT, 1-6 

Enterprise Output Manager (DEPCON), 1-5 

EPORTAL-2200, 1-6 

EXEC, 1-6 

EXPIPE, 1-6 

FAS, 1-6 

FLEX, 1-6 

FLIT, 1-6 

FTN, 1-6 

FURPUR, 1-6 

GSA, 1-6 

HTPIC-2200, 1-6 

I18NLIB, 1-6 

INFOACCESS, 1-6 

INTERCONNECT, 1-6 

IPF, 1-6 

IRU, 1-6 

J2EE-CON-OPENDTP, 1-6 

J2EE-CON-OS2200, 1-6 

JBOSS-2200, 1-6 

JPJVM, 1-6 

JVM, 1-6 

LA, 1-6 

LINK, 1-7 

LSS, 1-7 

LST, 1-7 

MAP, 1-7 

MASM, 1-7 

MCB, 1-7 

MQS2200, 1-7 

MSAR, 1-7 

MSMANAGER, 1-7 

MSMQI, 1-7 

NTSI, 1-7 

OLTP-TM2200, 1-7 

OPE, 1-7 

OSAM, 1-7 

OSI-TP, 1-7 

PADS, 1-7 

PAR, 1-7 

PCFP, 1-7 

PCIOS, 1-7 

PDP, 1-7 

PLUS, 1-8 

PMD, 1-8 

QLP, 1-8 

RDMS, 1-8 

RDMS-JDBC, 1-8 

7831 0349–043 Index–7

Index 

ROLRUNS, 1-8 

RSS, 1-8 

SAUTILITIES, 1-8 

Security-Admin, 1-8 

SFS, 1-8 

SILAS, 1-8 

SIMAN, 1-8 

SLIB, 1-8 

SOLAR, 1-8 

SOLAR/E, 1-8 

SORT, 1-8 

SSG, 1-8 

SYSLIB, 1-8 

TAS, 1-8 

TIP-LA, 1-9 

TQ-BASELINE, 1-8 

TQD-FRAGGER, 1-8 

TQ-MODEL, 1-8 

TQ-ONLINE, 1-8 

TQ-PMLOG, 1-8, 7-15 

TQ-PROBES, 1-8 

TQRDFRAGGER, 1-9 

TUTIL, 1-9 

UC, 1-9 

UCOB, 1-9 

UCSRTS, 1-9 

UDSC, 1-9 

UFTN, 1-9 

UNIACCESS-ODBC, 1-9 

UPLS, 1-9 

UREP, 1-9 

URTS, 1-9 

URU-OS2200, 1-9 

WEBTS, 1-9 

WMQ2200, 1-9 

XRLOAD, 1-9 

removal warning, Image Enable Key, 3-25 



ROLRUNS 



RSS 





Runtime System for Basic Mode Compilers 

(UCSRTS) release level, 1-9 

Runtime System for Extended Mode 

Compilers (URTS) 



Index–8 7831 0349–043 

S 

SAIL, See System Architecture Interface 

Layer 

SAUtilities release level, 1-8 

SCN 

master, 3-17 

profile, 3-19 

software control number, 3-16 

workload, 3-21 

SCP 


SCSITIS 



SECMGR command line utility, Security- 

Admin, 5-46 

SECOPT1 



SECOPT2 



SECOPT3 


security management product 

Security Administration for ClearPath 

OS 2200, 1-11 

Security-Admin 




Security-Admin client, Security-Admin, 5-46 

Separately Packaged Exec Features (SPEF) 

ARC, 1-10 

CARTIS, 1-10 

CARTLIB, 1-10 

DMPLIB, 1-10 

FBCIS, 1-10 

MHFS, 1-10 

MMGR, 1-10 

MSCP, 1-10 

PAEXEC, 1-10 

SCSITIS, 1-10 

SECOPT1, 1-10 

SECOPT2, 1-10 

SECOPT3, 1-10 

SINCH, 1-10 

SIPIPM, 1-10 

TAVR, 1-10 

TIPUTIL, 1-10 

UDUPLEX, 1-10

VTH, 1-10 

XPCEXEC, 1-10 

XTCEXEC, 1-10 

Server Management Control, See OS 2200 

Server Management Control 

Server Sentinel, 3-38 

service processor, 3-38 

SFS 



Shared File System (SFS) release level, 1-8 

SILAS 




SIMAN 


SINCH 



SIPIPM 



SLIB 




SMC, See OS 2200 Server Management 

Control 

software 

control number (SCN), 3-16 

media 

DVD, 1-4, 4-36, C-1 

tape, 4-14, 4-18, 4-23, 4-26, 4-33, 7-3, 

A-1 

packaging 

Exec base symbolic tape, A-1 

Exec release master information 

tape, A-1 

Exec release master tape, A-1 

fast-load tape, A-1 

IOE software, A-1 

optional products, A-1 

preconfigured boot tape, A-1 

UOE software, A-1 

performance level, Image Enabler 

Key, 3-16 

product key 

compliance, 3-23 

master SCN, 3-17 

update, 3-21 

upgrade, 3-21 

Index 



SOLAR 




PRODSV utility, 3-29 


security privileges, 5-47 

using as an installation tool, 5-46 

SOLAR/E 



SORT 





SP-OPERATION (Operations Sentinel), 5-40 

SSG 





support policy, 1-11 

SYSLIB 


fast-load tape location, C-3, C-4 



system 

metered, 1-1 

System Architecture Interface Layer 

console traffic, 3-39 

purpose, 3-38, 3-39 

7831 0349–043 Index–9 

T 

tape considerations 

36-track tape subsystems 

CTS5136, 4-16 

CTS5236, 4-16 

general considerations, 4-14 

OST4890, 4-17 

CTS5236 microcode, 3-48 

CTS9840, 4-23 

CTS9840 microcode, 3-48 

CTS9840C, 4-26 

CTS9940B, 4-33 

DLT 7000 and DLT 8000, 4-18 

tapes

Index 

CP-FLD contents, C-2 

CP-OE1 A and CP-OE1B content, C-3 

CP-OE2 contents, C-5 

fast-load content, C-2 

TAS 




TAVR 



TeamQuest 

Baseline 


CULL 



D-Fragger 



IACULL 


LA 



Model 


MSAR 



MSManager 


MSMANAGER 


Online 


OSAM 



PAR 



PMLog 


Probes 


products considerations, 7-4 

RemD-Fragger 



SAUtilities 



SIMAN 



TIP Log Analyzer 


TIP-LA 


TQ-BASELINE 


TQ-ONLINE 


TQ-PMLOG 


TQ-PROBES 


View considerations, 6-1 

TeamQuest SIMAN 


TIPUTIL 




TQ-ONLINE 


TQ-PMLOG 


TQ-PROBES 


TQ-TIP-LA release level, 1-9 

TQ-VIEW considerations, 6-1 

TUTIL 




Index–10 7831 0349–043 

U 

UC 



UCOB 



UCSRTS 




UDS application group 3, installing, C-5 

UDSC 



elease level, 1-9 

UDUPLEX 



UFTN (FORTRAN Compiler) 



UniAccess-ODBC 




update, software, 3-21 

upgrade, software, 3-21 

UPLS 




UREP 




UREPKEY package tape location, C-9 

URTS 









Index 

7831 0349–043 Index–11 

V 

Virtual Machine for the Javaî Platform on 

ClearPath OS 2200. 


VTH 



W 

WEBTS 




workload, SCN, 3-21 

wrong system, product key tape, 3-21 

X 

XPCEXEC 


XRLOAD 



XTCEXEC 



Index 

Index–12 7831 0349–043

© 2012 Unisys Corporation. 

All rights reserved. 

*78310349-043* 

7831 0349–043

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

Create successful ePaper yourself

Delete template?

Save as template?