ClearPath OS 2200 - Unisys€¦ · unisys ClearPath OS 2200 Software Planning and Migration Overview for Release 16.0 ClearPath OS 2200 Release 16.0 February 2015 7831 0349–046

unisys

ClearPath OS 2200

Software Planning and Migration Overview

for Release 16.0

ClearPath OS 2200 Release 16.0

February 2015 7831 0349–046

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.

7831 0349–046 iii

Contents

Section 1. Introducing ClearPath OS 2200 Release 16.0

1.1. Highlights for ClearPath OS 2200 Release 16.0........................... 1–3 1.1.1. New Major Capabilities ........................................................... 1–3

1.1.2. OS 2200 Master Glossary and Hypertext Links to Glossary Terms ............................................................... 1–5

1.2. Software Delivery on CD/DVD Media ...........................................1–6 1.3. Product Status Summary .................................................................. 1–7 1.4. Separately Packaged Exec Features (SPEF) ............................... 1–13 1.5. Support ................................................................................................ 1–14 1.6. Locating Terms Using CDLib Manager Search ......................... 1–15 1.6.1. Installing and Opening CDLib Manager ............................. 1–15

1.6.2. Performing a Search .............................................................. 1–16

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

1.6.4. For More Information ............................................................ 1–17

Section 2. New Products and Updated Features

2.1. APEX Level 2.0 ..................................................................................... 2–1 2.2. CIFS Level 8R3 .................................................................................... 2–3 2.3. CPCOMM Level 6R5 ......................................................................... 2–4 2.4. CPCOMMOS Level 4R5 .................................................................... 2–5 2.5. CPFTP Level 4R3 ................................................................................ 2–8 2.6. DAP Level 15R2 .................................................................................. 2–9 2.7. DEPCON Level 12.0 .......................................................................... 2–10 2.8. DMS Level 22R1 ............................................................................... 2–13 2.9. DPS Level 6R6 .................................................................................. 2–13 2.10. ECLIPSE-2200 Level 4.3.2............................................................... 2–13 2.11. EPORTAL-2200 Level 2.2 ............................................................... 2–21 2.12. EXEC Level 49R2 .............................................................................. 2–24 2.13. FLIT Level 15R2 ................................................................................. 2–29 2.14. IRU Level 22R2 ................................................................................. 2–30 2.15. JBOSS-2200 Level 6.2..................................................................... 2–31 2.16. JPJVM Level 8.0 ............................................................................... 2–33 2.17. LSS Level 14R4 ................................................................................. 2–33 2.18. MAP Level 33R2 ............................................................................... 2–34 2.19. MASM Level 6R3L ........................................................................... 2–34 2.20. RDMS Level 20R1 ............................................................................ 2–35 2.21. RDMS-JDBC Level 2.10 .................................................................. 2–37 2.22. SECURITY-ADMIN Level 4R4A ..................................................... 2–38 2.23. SLIB Level 2R1 .................................................................................. 2–38 2.24. SORT Level 22R3 ............................................................................. 2–39 2.25. SP-OPERATION Level 15.0 ............................................................. 2–39

Contents

iv 7831 0349–046

2.26. SP-OPERATION Level 15.0CP ....................................................... 2–42 2.27. SYSLIB Level 77R1 ........................................................................... 2–45 2.28. TeamQuest Products ...................................................................... 2–47 2.28.1. TeamQuest BASELINE® Level 7R5A................................ 2–47

2.28.2. TeamQuest® D-Fragger Level 4R2 .................................. 2–48

2.28.3. TeamQuest® LA Level 8R2 ................................................ 2–48

2.28.4. TeamQuest Online® Level 7R5A ...................................... 2–48

2.28.5. TeamQuest® PAR Level 9R3 ............................................. 2–49

2.28.6. TeamQuest® Probes Level 7R5A ..................................... 2–49

2.28.7. TeamQuest® RemD-Fragger Level 4R2 .......................... 2–49

2.28.8. TeamQuest® SAUTILITIES Level 8R1A ............................ 2–49

2.28.9. TeamQuest® SIMAN Level 7R2 ........................................ 2–50

2.29. UC Level 10R5 ................................................................................... 2–50 2.30. UCOB Level 12R2 ............................................................................. 2–50 2.31. UREP Level 16R1............................................................................... 2–51 2.32. URTS Level 13R4 .............................................................................. 2–52 2.33. URU-OS2200 Level 8.0 ................................................................... 2–52 2.34. WEBTS Level 6R1............................................................................. 2–53 2.35. XRLOAD Level 6R1E ........................................................................ 2–55

Section 3. Software Considerations, Management, and

Delivery

3.1. Considerations ..................................................................................... 3–1 3.2. Discontinued Products ..................................................................... 3–9 3.3. Future Considerations .................................................................... 3–10 3.3.1. MCB Rewritten in Extended Mode ................................... 3–10

3.3.2. TDATE$ Timestamp Format ................................................ 3–10

3.3.3. Master File Directory (MFD) ................................................. 3–11

3.3.4. Summary Accounting File ..................................................... 3–11

3.3.5. Freespace ................................................................................. 3–11

3.3.6. Program File Element Table ................................................ 3–12

3.3.7. Notice of Intent to Remove Software ............................. 3–12

3.3.8. Notice of Intent to Remove Hardware ............................ 3–13

3.4. Software License Management .................................................. 3–13 3.4.1. Definitions ................................................................................ 3–14

3.4.2. Software License Management ........................................ 3–16

3.4.3. Ordering ClearPath OS 2200 Software ............................ 3–17 3.4.4. System Upgrade Information ............................................. 3–17

3.4.5. Registering Your Software Product Keys ....................... 3–18

3.4.6. Frequently Asked Questions .............................................. 3–19

3.5. Software License Management and

LIBSAVE/LIBLOAD ...................................................................... 3–21 3.5.1. LIBSAVE/LIBLOAD Examples .............................................. 3–21

3.5.2. Example 1: Performing a LIBLOAD onto

System B ............................................................................. 3–22 3.5.3. Example 2: Performing a LIBLOAD onto

System C ............................................................................. 3–25 3.6. Keyed Tape Delivery ....................................................................... 3–27 3.6.1. Nonkeyed Products ............................................................... 3–29

3.6.2. Key Package Registration .................................................... 3–30

Contents

7831 0349–046 v

3.7. License Keys for TeamQuest Products ..................................... 3–30 3.7.1. Updating Keys ........................................................................ 3–31

3.7.2. Product License Registration for Your OS 2200 Host ...................................................................................... 3–33

3.7.3. Product License Registration for your PC

(TeamQuest Model® Only) ............................................ 3–33

3.7.4. Obtaining a Registered Product License Key .................3–34

3.8. Build Option .......................................................................................3–34 3.9. ClearPath and Plateau Interdependencies ................................ 3–35 3.10. ClearPath Specialty Partitions Interdependencies .................. 3–38 3.10.1. OS 2200 JProcessor ..............................................................3–40 3.10.2. OS 2200 QProcessor ............................................................ 3–41 3.10.3. ePortal for OS 2200 ............................................................... 3–42 3.11. Microcode Requirements for CTS5236 and T9840

Tape Drives .................................................................................. 3–42 3.12. Supported Peripheral Products ....................................................3–43

Section 4. Exec Software Compatibility and Migration

Considerations

4.1. General Exec Considerations .......................................................... 4–2 4.1.1. ClearPath OS 2200 Release 16.0 .......................................... 4–2 4.1.1.1. Secure by Default – Optionally disallow

@@PASSWD ............................................................... 4–2

4.1.1.2. Secure by Default – Configure Delayed

Sign On Solicitation to meet PCI DSS

guidelines .................................................................... 4–2

4.1.1.3. CARTLIB Change ............................................................ 4–3

4.1.2. ClearPath OS 2200 Release 15.0 .......................................... 4–3 4.1.2.1. Daylight Saving Time Adapt ........................................ 4–3

4.1.2.2. DMPLIB 9R1 ..................................................................... 4–8

4.1.2.3. Exec Migration Issues for MHFS

environments ............................................................. 4–8

4.1.2.4. I/O Legacy Removal ...................................................... 4–8

4.1.2.5. Secure by Default ......................................................... 4–11

4.1.2.6. TCFUPGRADE Routine for Updating Exec

Level 48 to 49 .......................................................... 4–13

4.1.3. ClearPath OS 2200 Release 14.0 ........................................ 4–14 4.1.4. LIBSAVE/LIBLOAD Scenario ................................................ 4–14

4.1.5. I/O COMMAND QUEUING (IOCQ) ..................................... 4–15

4.1.6. Processing Exec Dump Files (DUMPLIBS) ...................... 4–16

4.2. SGS and Configuration Parameters ............................................ 4–17 4.2.1. New Configuration Parameters ......................................... 4–17

4.2.2. MODEL_TYPE Statement ..................................................... 4–18

4.3. Migrating from a Nonmetered System to a Metered

System ........................................................................................... 4–18 4.4. Log Entry Changes .......................................................................... 4–19 4.5. XPC-L ................................................................................................... 4–21 4.6. Tape and DVD ................................................................................... 4–21 4.6.1. Tape ........................................................................................... 4–22

4.6.2. Tape Drive Encryption ..........................................................4–24

Contents

vi 7831 0349–046

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

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

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

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

4.6.7. T9840A Tape Subsystem .................................................... 4–35

4.6.8. T9840C Tape Subsystem .................................................... 4–37

4.6.9. T9840D Tape Subsystem ................................................... 4–39

4.6.10. T10000A Tape Subsystem ...................................................4–42

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

4.6.12. T9940B Tape Subsystem ................................................... 4–44

4.6.13. CSC and ACSLS ..................................................................... 4–46

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

4.6.15. Virtual Tapes ...........................................................................4–47

4.7. TIP ....................................................................................................... 4–48 4.7.1. General .................................................................................... 4–48

4.7.2. ClearPath OS 2200 Release 16.0 ....................................... 4–48 4.7.3. ClearPath OS 2200 Release 15.0 ....................................... 4–49 4.7.4. ClearPath OS 2200 Release 14.0 ........................................4–50 4.8. Software Controlled Performance (SCP) ...................................4–50 4.8.1. Manufacturing Control Number Expansion .................... 4–51

4.8.2. PDB_MFG_CONTROL_NUMBER ER CONFIG$

Changes ............................................................................... 4–51

4.9. POSTOEXMSTR ................................................................................ 4–51

Section 5. OS 2200 Software Compatibility and Migration

Considerations

5.1. Summary of Considerations ........................................................... 5–2 5.2. APEX ...................................................................................................... 5–4 5.3. Business Information Server (BIS or MAPPER) ......................... 5–4 5.4. CIFS ........................................................................................................ 5–4 5.5. Cipher API ............................................................................................ 5–5 5.6. CITA ....................................................................................................... 5–6 5.7. Checkpoint/Restart (CKRS) ............................................................. 5–7 5.8. CMR ....................................................................................................... 5–7 5.9. COMAPI ................................................................................................ 5–8 5.10. Communications Platform (CPComm) .......................................... 5–9 5.11. Communications Platform for Open Systems

(CPCommOS) ............................................................................... 5–10 5.12. COMUS ............................................................................................... 5–12 5.13. cpFTP .................................................................................................. 5–13 5.14. CryptoLib ............................................................................................ 5–14 5.15. DMS-RA .............................................................................................. 5–14 5.16. DPS ...................................................................................................... 5–15 5.17. Distributed Data Processing File and Job Transfer

(DDP-FJT) ...................................................................................... 5–16 5.18. Distributed Data Processing Program-to-Program

Communications (DDP-PPC) .................................................... 5–16 5.19. ELMS ................................................................................................... 5–17 5.20. Enterprise Output Manager (EOM) ............................................. 5–17 5.21. Enterprise Relational Database Server (RDMS) ....................... 5–18

Contents

7831 0349–046 vii

5.22. FAS....................................................................................................... 5–19 5.23. FLEX ..................................................................................................... 5–20 5.24. HTPIC-2200 ........................................................................................ 5–20 5.25. Integrated Recovery Utility (IRU) ................................................. 5–21 5.26. Interactive Processing Facility (IPF) ............................................. 5–24 5.27. Interconnect ...................................................................................... 5–24 5.28. JPJVM ................................................................................................. 5–25 5.29. OS 2200 Transaction Resource Adapter for the

Java™ Platform (J2EE-CON-OS2200) .................................... 5–26 5.30. Language Support System (LSS) ................................................. 5–26 5.31. Linking System (LINK) ..................................................................... 5–27 5.32. MAP ..................................................................................................... 5–28 5.33. Message Control Bank (MCB) ...................................................... 5–28 5.34. MSMQI ............................................................................................... 5–28 5.35. NTSI ..................................................................................................... 5–29 5.36. ODBC Data Access (INFOAccess) ............................................... 5–29 5.37. Open Distributed Transaction Processing (Open DTP)

(OLTP-TM2200) ............................................................................ 5–30 5.38. Open Programming Environment (OPE) .................................... 5–31 5.39. OSI-TP ................................................................................................. 5–33 5.40. RDMS .................................................................................................. 5–33 5.41. RDMS-JDBC ...................................................................................... 5–33 5.42. Remote System Support (RSS) .................................................... 5–34 5.42.1. Configuration Requirements ............................................... 5–34

5.42.2. RSS Operations Considerations ......................................... 5–35

5.43. Runtime System for Extended Mode Compilers

(URTS) ............................................................................................ 5–35 5.44. Security-Admin ................................................................................. 5–35 5.45. SILAS ................................................................................................... 5–36 5.46. SOLAR and SOLAR/E ...................................................................... 5–37 5.47. SP-OPERATION (Operations Sentinel)........................................ 5–38 5.48. SSG ......................................................................................................5–40 5.49. SYSLIB ................................................................................................ 5–41 5.50. Tape Labeling Utility for ClearPath OS 2200 (TUTIL) ............... 5–43 5.51. TCP/IP Application Services (TAS) .............................................. 5–44 5.52. TeamQuest Products ..................................................................... 5–44 5.52.1. TeamQuest Baseline® ........................................................ 5–44

5.52.2. TeamQuest® LA .................................................................... 5–45

5.52.3. TeamQuest Online® ............................................................. 5–45

5.52.4. TeamQuest® OSAM ............................................................. 5–45

5.52.5. TeamQuest® PAR ................................................................. 5–45

5.52.6. TeamQuest® PMLog ............................................................ 5–45

5.52.7. TeamQuest® SAUTILITIES ..................................................5–46

5.52.8. TeamQuest® TIP-LA .............................................................5–46

5.53. UCOB .................................................................................................. 5–47 5.54. UniAccess-ODBC ............................................................................. 5–47 5.55. Universal Database Control (UDSC) ............................................ 5–47 5.56. UREP ................................................................................................... 5–48 5.57. Utilization Report Utility for OS 2200 (URU-OS2200) ............. 5–51 5.58. Web Transaction Server (WEBTS) .............................................. 5–53 5.59. WebSphere® MQ Version 7 for ClearPath OS 2200

(WMQ2200) .................................................................................. 5–53

Contents

viii 7831 0349–046

Section 6. Workstation-Based Software Considerations

6.1. ClearPath OS 2200 Release 16.0 .....................................................6–1 6.1.1. Apex .............................................................................................6–1

6.1.2. Enterprise Output Manager Workstation

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

6.1.3. TeamQuest Model® (TQ-MODEL) ...................................... 6–2

6.1.4. TeamQuest View® (TQ-VIEW) ............................................. 6–2

6.1.5. Utilization Report Utility (URU) ............................................. 6–2

6.1.6. Web Transaction Server ........................................................ 6–2

6.1.7. Operations Sentinel (SPO) ..................................................... 6–3

Section 7. Installing ClearPath OS 2200 Release 16.0 Software

7.1. Installation Considerations .............................................................. 7–3 7.2. ClearPath OS 2200 Release 16.0 Migration

Considerations ............................................................................... 7–3 7.3. Fall Back Considerations From ClearPath OS 2200

Release 16.0 to Prior Releases .................................................. 7–7 7.4. Other Considerations ...................................................................... 7–10 7.5. Description of Fast-Load Tapes .................................................... 7–11 7.6. Migration Sequences ....................................................................... 7–11 7.7. Initial Migration Steps ..................................................................... 7–12 7.7.1. Initial Migration Steps for Moving from Release

14.0 to Release 16.0 ......................................................... 7–13

7.7.2. Initial Migration Steps for Moving from Release

15.0 to Release 16.0 ......................................................... 7–22

7.8. Installing from Fast Load Tapes ................................................... 7–26 7.9. Installing from Package Tapes ..................................................... 7–30 7.10. Initializing an Existing System (I-Boot) ....................................... 7–36 7.11. Migration for Dorado 4000 Customers...................................... 7–45 7.12. Migration for Dorado 4100 Customers ...................................... 7–45 7.13. Migration for Dorado 4200 Customers ...................................... 7–45 7.14. Migration for Dorado 4300 and Dorado 6300

Customers .................................................................................... 7–46

Section 8. Operations Sentinel (Formerly Single Point

Operations)

Appendix A. Media Contents

A.1. Software Packaging .......................................................................... A–1 A.2. Dorado Models Workload IOE....................................................... A–3 A.3. Dorado Models Workload UOE ..................................................... A–9

Appendix B. Product Interdependencies

Contents

7831 0349–046 ix

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 ........................................................ C–2

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

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

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

Contents

x 7831 0349–046

7831 0349–046 xi

Tables

1–1. Product Status Summary ................................................................................................ 1–7

3–1. Software Products and Features Not Supported in

ClearPath OS 2200 Release 16.0 ............................................................................. 3–9 3–2. ClearPath Dorado Plateau Interdependencies Without XPC-L Support .......... 3–35

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

3–4. CPCommOS Plateau Component Requirements .................................................. 3–37

4–1. Tape Assign Mnemonics ............................................................................................. 4–22

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

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

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

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

4–6. DVD Assign Mnemonics ..............................................................................................4–47

5–1. Summary of Release 16.0 Considerations ................................................................ 5–2

5–2. Summary of Release 15.0 Considerations ................................................................ 5–3

7–1. SYSLIB and SLIB Installation ....................................................................................... 7–14

7–2. Package Tape Products ................................................................................................ 7–15

7–3. DVD, CDROM, and Download Media ....................................................................... 7–16

7–4. Dorado 4000 Plateau and ClearPath Release Interdependencies .................... 7–45

A–1. Products in all IOEs......................................................................................................... A–3

A–2. Additional IOE products based on System and Workload ....................................A–7

A–3. Products in all UOEs ...................................................................................................... A–10

A–4. Additional UOE products based on System, General Purpose and

SDK Workload ........................................................................................................... A–13

A–5. Additional UOE products based on System, BIS and EAE Workload ............... A–15

B–1. Required System Products ........................................................................................... B–2

B–2. Products Interdependency Matrix .............................................................................. B–3

B–3. Optional Product Interdependency Notes ................................................................B–9

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

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

Tables

xii 7831 0349–046

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

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

7831 0349–046 1–1

Section 1 Introducing ClearPath OS 2200 Release 16.0

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

contains support for the following ClearPath Dorado servers.

Note: Beginning with the ClearPath OS 2200 release 15.0, the Dorado 300 Series

systems are no longer supported.

Nonmetered Systems Metered Systems

Dorado 740 Dorado 750









Dorado 880E Dorado 4290


Dorado 4370

Dorado 4390

Dorado 6390

Dorado 850

Dorado 870

Dorado 890E

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.

Highlights for ClearPath OS 2200 Release 16.0

1–2 7831 0349–046

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.

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 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 4000/4100/4200/4300/6300 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) 19027589. To obtain a copy of the PLE, contact your Unisys service

representative or access the current PLE from the Unisys Product Support website:

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

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)

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

access the current PLE from the Unisys Product Support website:

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


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.


7831 0349–046 1–3

1.1. Highlights for ClearPath OS 2200 Release 16.0

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 16.0 release.

1.1.1. New Major Capabilities

ClearPath OS 2200 is a complete operating environment for ClearPath Dorado Servers

that includes all of the software needed to operate a mission-critical Dorado server.

The OS 2200 16.0 integrated software stack includes 110 fully integrated and qualified

software components to ensure the seamless operations required for critical core

business applications and databases.

Application Modernization

With this release, customers can more effectively utilize readily available developer

skills and at the same time execute application modernization initiatives that better

align IT investments with business objectives.

ClearPath ePortal for OS 2200 is a point-and-click Service-Oriented Architecture (SOA)

enabler that can rapidly extend ClearPath applications to reach new partners, channels,

and markets through Web, Mobile or Web Services technologies.

ClearPath ePortal enables application developers to automatically deploy, manage, and

secure ClearPath applications for Web, mobile device, and Web services solutions.

ClearPath ePortal automates a solution at every point: from development to

deployment. With the enhancements in ePortal developer for this release, customers

can reduce application complexity and develop web service applications faster with

support for the latest version of Microsoft® Visual Studio® 2013. In addition,

developers can easily build hybrid mobile applications while minimizing the need to

master each platform’s proprietary language, SDK, and tool set with access to the

Unisys Hybrid App Build Service, a new Cloud-based, mobile application build service

from Unisys.

ClearPath OS 2200 IDE for Eclipse addresses the needs of today’s ClearPath

developers by integrating the well-known industry standard development environment

from Eclipse.org with the OS 2200 environment. Customers can rapidly develop and

update their OS 2200 applications, and develop new Java-based composite

applications that interface with OS 2200 applications and data. This release of

ClearPath OS 2200 IDE for Eclipse supports Eclipse version 4.3.2. Developer

productivity enhancements include improved performance when working with large

projects, the ability to record macros using keystroke recording of frequently used

tasks, and content assist for DMS and RDMS and ECL commands.

Java has also been updated in this release, and now customers can benefit from

speed and performance of the latest versions of this popular application environment

through features for productivity, ease of use, security, and improved performance.


1–4 7831 0349–046

Data Center Transformation

In OS 2200 release 16.0 there are several updates that improve the way customers

interact with and process data.

First, there are several performance improvements to our popular RDMS database

that allow customers to more quickly access their data. Also included in this release

are improvements to query syntax that supports more complex SQL queries and that

allows customer applications more efficient access to data as well as enabling

customers to better support their business requirements particularly those that

involve data warehousing and online analytical processing (OLAP).

Customers using cpFTP will benefit from the file transfer performance improvements

that leverage the Dorado 4300/6300 “fabric” as well as 10 Gb Ethernet NICs.

Simplifying operation complexity of enterprise-wide IT-infrastructure, Operations

Sentinel makes migrating from one OS 2200 release to the next easier with the

Autoaction Database Scanner which detects changed message patterns within the

CP-AMS databases.

As a comprehensive output-management solution for mixed-platform networks,

Enterprise Output Manager now provides the capability to personalize e-mail

messages through text style (font, color), as well as the ability to insert file content,

images, and logos. Enterprise Output Manager now supports large file transfer from

OS 2200 systems (greater than 262,143 tracks).

Security

In OS 2200 release 15.0, we introduced two major security related capabilities and in

this release we are adding additional features to increase the capabilities of these

features.

Apex is a new product introduced in OS 2200 release 15.0 that provides an

easy-to-use, intuitive Web-based interface for managing the OS 2200 operating

system. In the initial release, Apex provided capabilities to manage OS 2200 users and

accounts. In OS 2200 release 16.0, Apex provides additional security configuration and

reporting capabilities. Apex enables customers to better manage their security

settings using less experienced staff, freeing more knowledgeable staff for more

complex tasks.

“Secure by Default” is a set of capabilities first introduced in OS 2200 release 15.0 that

aligns OS 2200 default system values with the best security practices that have

evolved in the industry. In release 16.0, Secure by Default offers additional features

allowing customers to reduce and simplify the task of configuring security settings on

ClearPath OS 2200 while staying more secure from the start.


7831 0349–046 1–5

Other security-related enhancements in 16.0 include:

• Encryption updates for CIFS ZIPUT, Enterprise Output Manager, and Web

Transaction Server for ClearPath OS 2200 (WebTS)

• Security and standards compliance: CPCOMMOS support for TLS protocol

versions 1.1 and 1.2 and FIPS 140-2-Validated SSL/TLS

• SIMAN support for User Authentication Module 19 (Configured Password Profiles)

• Signed applets with WebTS JavaClient for Web-enabled DPS transactions

System Recovery

The file recovery portion of the recovery boot time is reduced by 15-80%, depending

on configuration (number and type of disks and number of files).

1.1.2. OS 2200 Master Glossary and Hypertext Links to Glossary Terms

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

the ClearPath OS 2200 products. Since the Master Glossary contains all the terms and

definitions that were in the individual glossaries, the individual glossaries have been

removed from the OS 2200 documents.

Beginning with ClearPath OS 2200 release 14.0 each of the document PDF files

contains hypertext links that show up as blue underline. The hypertext links open the

Master Glossary to the page the term is on.

Accessing the Master Glossary

You can access the OS 2200 Master Glossary from either the

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

website.

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

• 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.

• If you open the document PDF files from the Product Support website, the

hypertext links will open the Master Glossary to the page the term is on. If you

download a PDF file from the Product Support website you need to also download

the Master Glossary (3850 6523-003) and put it in the same folder as the

document (s) you downloaded in order for the hypertext links to work.

Software Delivery on CD/DVD Media

1–6 7831 0349–046

1.2. Software Delivery on CD/DVD Media

The ClearPath OS 2200 release software is distributed on a set of DVDs and

CD-ROMs. 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. The CD-ROMs are

installed on servers and workstations connected to the OS 2200 system, typically for

use in Windows or Java environments.

Dorado 700, 800, 4000, 4100, 4200, 4300, and 6300 Server systems are each delivered

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

systems a cell is one partition. Larger systems 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,<DVD>

@ASG,TF TAPE.,MNEMONIC,<REEL>

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

@COPY,M DVDFILE.,TAPE.,999999

Note: Roxio Creator DE Level 9 by Sonic Solutions is the product used to create

DVD media.

Product Status Summary

7831 0349–046 1–7

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.

Table 1–1. Product Status Summary

Installation and

Support Name

Product Name

Level

Operating

System

Status

ACOB ASCII COBOL Compiler 7R3M OS 2200 Stability Update

APEX Apex 2.0 OS 2200 and

Windows

Server

Feature Update

CIFS CIFS 8R3 OS 2200 Feature Update

CIPHER-API CIPHER API 2R4A OS 2200 Stability Update

CITA Communications Interface

for Transaction Applications

2R4A OS 2200 Stability Update

CKRS CKRS 7R8B OS 2200 No Change

CML CML 1R1J OS 2200 No Change

CMR CMR 3R1 OS 2200 No Change

COMAPI Communications

Application Program

Interface

8R1B OS 2200 Stability Update

COMUS COMUS 6R9C OS 2200 No Change

CPComm Communications Platform 6R5 OS 2200 Feature Update

CPCommOS Communications Platform

for Open Systems

4R5 OS 2200 Feature Update


1–8 7831 0349–046


Installation and

Support Name

Product Name

Level

Operating

System

Status

cpFTP FTP Services for ClearPath

OS 2200


CryptoLib Cryptographic Library 1R3 OS 2200 No Change

CULL TeamQuest® CULL 5R1C OS 2200 No Change

DAP DAP 15R2 OS 2200 Feature Update

DDP-FJT DDP-FJT 5R5L OS 2200 Stability Update

DDP-PPC DDP-PPC 7R4B OS 2200 Stability Update

DEPCON-SERVER Enterprise Output Manager 12.0 Windows Feature Update

DEPCON-2200 Enterprise Output Manager

for ClearPath OS 2200

12.0 OS 2200 Feature Update

DFP Define File Processor 2R2C OS 2200 No Change

DMS Enterprise Network

Database Server


DMS-RA DMS-RA 4.1 OS 2200 No Change

DPREP1100 DPREP1100 10R7G OS 2200 No Change

DPS Display Processing System 6R6 OS 2200 Feature Update

DTI Distributed Transaction

Integration

11.3A Windows No Change

ECLIPSE-2200 ECLIPSE 2200 4.3.2 OS 2200 Feature Update

ELMS ELMS 3R1B OS 2200 No Change

ELT ELT 8R3C OS 2200 No Change

EPORTAL-2200 2.2 Feature Update

EXEC Exec 49R2 OS 2200 Feature Update

EXPIPE Multiple Batch Run

Optimizer

2R2B OS 2200 No Change

FAS FAS 11R1A OS 2200 Stability Update

FLEX User Authentication 4R4A OS 2200 Stability Update

FLIT FLIT 15R2 OS 2200 Feature Update

FTN ASCII FORTRAN Compiler 11R3 OS 2200 No Change

FURPUR FURPUR 32R5D OS 2200 No Change

GSA GSA 6R2E OS 2200 No Change

OS-2200-SBR 16.0


7831 0349–046 1–9


Installation and

Support Name

Product Name

Level

Operating

System

Status

HTPIC-2200 HTPIC-2200 9R1K OS 2200 Stability Update

I18NLIB I18NLIB 2R2A OS 2200 No Change

INFOACCESS ODBC Data Access 9R3B OS 2200 Stability Update

INTERCONNECT INTERCONNECT 1R4B OS 2200 Stability Update

IPF Interactive Processing

Facility

7R1D OS 2200 No Change

IRU Integrated Recovery Utility 22R2 OS 2200 Feature Update

J2EE-CON-

OPENDTP

Open Distributed

Transaction Processing

Resource Adapter for the

Java™ Platform

15.0 OS 2200 No Change

J2EE-CON-OS2200 OS 2200 Transaction

Resource Adapter for the

Java™ Platform

14.1 OS 2200 No Change

JBOSS-2200 JBoss Enterprise

Application Platform for

ClearPath OS 2200

(formerly known as JBoss

Application Server for

ClearPath OS 2200)


JPJVM Virtual Machine for the

Javaî Platform on

ClearPath OS 2200

JProcessor


LA TeamQuest® LA 8R2 OS 2200 Feature Update

LINK Linking System 12R2D OS 2200 Stability Update

LIST LIST 4R1J OS 2200 No Change

LSS Language Support System 14R4 OS 2200 Feature Update

MAP Collector 33R2 OS 2200 Feature Update

MASM MASM 6R3L OS 2200 Stability Update

MCB MCB 9R1A OS 2200 Stability Update

MSAR TeamQuest® MSAR 7R7D OS 2200 No Change

MSMANAGER TeamQuest® MSManager 5R7G OS 2200 No Change

MSMQI MSMQ Interface 2R1C OS 2200 or

Windows

No Change


1–10 7831 0349–046


Installation and

Support Name

Product Name

Level

Operating

System

Status

NTSI Messaging Integration

Services

7R3B OS 2200 (other

components of

NTSI are

installed on the

ClearPath

Windows node

and Windows

workstations)

No Change

OLTP-TM2200 Open Distributed

Transaction Processing

(Open DTP)

12R1F OS 2200 Stability Update

OPE Open Programming

Environment

4R1S OS 2200 No Change

Operations

Sentinel (See

SP-OPERATION)

OSAM TeamQuest® OSAM 7R6A OS 2200 Stability Update

OSI-TP OSI-TP 9R1K OS 2200 Stability Update

PADS Programmer’s Advanced

Debugging System

13R4A OS 2200 Stability Update

PAR TeamQuest® PAR 9R3 OS 2200 Feature Update

PCFP PCFP 3R3C OS 2200 No Change

PCIOS PCIOS 7R1C OS 2200 Stability Update

PDP PDP 13R2D OS 2200 No Change

PLUS PLUS 8R2O OS 2200 No Change

PMD PMD 32R2G OS 2200 No Change

QLP QLP 7R3C OS 2200 No Change

RDMS Enterprise Relational

Database Server


RDMS-JDBC Relational JDBC Driver 2.10 OS 2200 Feature Update

ROLRUNS ROLRUNS 4R3 OS 2200 No Change

RSS Remote System Support 3R2N OS 2200 No Change

SAUTILITIES TeamQuest® SAUtilities 8R1A OS 2200 Stability Update

Security-Admin Security-Admin 4R4A OS 2200 Stability Update

SFS Shared File System 4R1 OS 2200 No Change

SILAS SILAS 3R3B OS 2200 Stability Update


7831 0349–046 1–11


Installation and

Support Name

Product Name

Level

Operating

System

Status

SIMAN TeamQuest® SIMAN 7R2 OS 2200 Feature Update

SLIB SLIB 2R1 OS 2200 Feature Update

SOLAR SOLAR 4R8 OS 2200 No Change

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

SORT Sort/Merge 22R3 OS 2200 Feature Update

SP-OPERATION Operations Sentinel 15.0 Windows Feature Update

SP-OPERATION Operations Sentinel

Basic Edition

15.0CP

Windows Feature Update

SSG SSG 24R3 OS 2200 No Change

SYSLIB SYSLIB 77R1 OS 2200 Feature Update

TAS TAS 6R2L OS 2200 Stability Update

TQ-BASELINE TeamQuest Baseline® 7R5A OS 2200 Stability Update

TQ-D-FRAGGER TeamQuest® D-Fragger 4R2 OS 2200 Feature Update

TQ-MODEL TeamQuest Model® CP16.0 Windows

workstation

Feature Update

TQ-ONLINE TeamQuest Online® 7R5A OS 2200 Stability Update

TQ-PMLOG TeamQuest® PMLog 7R5 OS 2200 No Change

TQ-PROBES TeamQuest® Probes 7R5A OS 2200 Feature Update

TQ-REMD-

FRAGGER

TeamQuest®

RemD-Fragger


TQ-TIP-LA TeamQuest® TIP-LA 1R6 OS 2200 No Change

TUTIL Tape Labeling Utility 1R1B OS 2200 No Change

UC C Compiler 10R5 OS 2200 Feature Update

UCOB COBOL Compiler 12R2 OS 2200 Feature Update

UCSRTS Runtime System for Basic

Mode Compilers

1R1M OS 2200 No Change

UDSC Universal Database Control 20R1 OS 2200 Feature Update

UFTN FORTRAN Compiler 11R2 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

OS 2200



1–12 7831 0349–046


Installation and

Support Name

Product Name

Level

Operating

System

Status

URTS Runtime System for

Extended Mode Compilers


URU-OS2200 Utilization Report Utility for

OS 2200

8.0 OS 2200 and

Windows

Feature Update

WEBTS Web Transaction Server 6R1 OS 2200 Feature Update

WMQ2200 WebSphere MQ version 7

for ClearPath Dorado

Servers

7R0C OS 2200 Stability Update

XRLOAD Relational Database Fast

Load

6R1E OS 2200 Stability Update

Separately Packaged Exec Features (SPEF)

7831 0349–046 1–13

1.4. Separately Packaged Exec Features (SPEF)

The following list shows ClearPath OS 2200 release 16.0 levels for separately

packaged Exec features.

Feature Level

ARC 5R8

DMPLIB 9R2

MHFS 49R1

MMGR 49R2

MSCP 3R8E

SECOPT1 49R2

SECOPT2 49R1

SECOPT3 49R1

Feature Level

SIPIPM 49R1

TAVR 49R1

TIPUTIL 49R2

UDUPLEX 49R1

VTH 49R1

XPCEXEC 49R1

XTCEXEC 49R1

• 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.

Support

1–14 7831 0349–046

1.5. 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 16.0 will be supported until 08/31/2018.

Contact your Unisys Support Center for information about resolving problems and

submitting User Communication Forms (UCF).

The Unisys Product Support website contains support plans for ClearPath servers. It is

updated regularly, and you can access this website 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)

Locating Terms Using CDLib Manager Search

7831 0349–046 1–15

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

website (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 website 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–16 7831 0349–046

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–046 1–17

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–18 7831 0349–046

7831 0349–046 2–1

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. APEX Level 2.0

Support for ACRs and Groups

Customer Solution/Benefit:

ACRs provide a powerful tool for sites using Security Level 1 or higher to protect files

and other system objects. Groups provide streamlined ways of populating ACRs.

Defining and updating them in Apex provides a level of ease of use that will make it

much easier for inexperienced administrators to use them effectively.

Detailed Description:

The Apex interface lets the user create, update, and delete Access Control Records

(ACRs) and User Groups, providing functionality equivalent to or better than Security

Client, within the Apex framework.

Additional and Enhanced Reports


These new reports and enhancements to existing Apex reports help the administrator

monitor compliance with enterprise security policies.


New reports are added for ACRs and Groups. The Security Environment page displays

the symbolic names of Clearance Levels along with their integer values. The user’s

authentication type is now included in the exported and printed Passwords report.

Printed and exported reports now identify the system on which they were created.

APEX Level 2.0

2–2 7831 0349–046

Support for New Exec Configuration Parameters


Starting with release 15.0, Apex has provided the ability for the administrator to view

and update Exec dynamic configuration parameters. With each release that introduces

new parameters or changes existing ones, an update to Apex will continue to let the

administrator manage those parameters through Apex.


For release 16.0 the Exec configuration screen in Apex has a new Time tab. It includes

these new configuration parameters:

• accounting_modified_swtime

• freespace_modified_swtime

• shared_mfd_modified_swtime

• std_mfd_modified_swtime

Apex’s Exec configuration Security tab includes the new configuration parameter

enable_passwd_control_statement.

Report Installed Software


The administrator can see which products are installed on the OS 2200 system, along

with their version, without having to log into a demand session on the host. He or she

can then compare this with information from the Unisys support site to determine if

the installed levels are current.


The Apex display of installed software includes the product name, level, date installed,

and other details.

Print and Export Account, User, Group, and ACR Pages


The user who would like a printed or CSV-format copy of information for a single

account, user, group, or ACR can easily get it.


New Print and Export options are available for Account, User, Group and ACR pages.

The outputs include information from all of the tabs of the selected object.

CIFS Level 8R3

7831 0349–046 2–3

Print and Export the Security Environment


The user who would like a printed or CSV-format copy of information for the security

environment can easily get it.


The OS 2200 security environment includes numerous attributes that are not part of

the Exec configuration but are included in the Apex Security Environment page. New

Print and Export options for that page let the use get a copy that combines

information from all of the tabs.

Update Message of the Day


The Message of the Day is a multiline message displayed when a user logs on; it

provides a way for an administrator to inform or remind users of events, policies, etc.

It has been part of the OS 2200 Exec for decades, and now the administrator can

display and update the OS 2200 system message of the day from a web browser by

using Apex.


The Apex user can display and update the system message that is displayed when a

user logs on.

2.2. CIFS Level 8R3

ZIPUT encryption


Increased security.


ZIPUT can now encrypt and decrypt data using modern algorithms that are compatible

with widely available tools such as WinZip.

CPCOMM Level 6R5

2–4 7831 0349–046

2.3. CPCOMM Level 6R5

SSL GET CERTIFICATE Command


The SSL GET CERTIFICATE command allows an administrator to save a certificate,

presented by a remote system during an SSL/TLS handshake, to a file. The

Communications Platform administrator can perform this action without requiring the

administrator of the peer system to manually provide the certificate.


Communications Platform does not allow an SSL/TLS connection where the

peer-presented certificate is not trusted. The SSL GET CERTIFICATE command allows

the administrator to extend trust to the certificate. If a peer system presents an

untrusted certificate, this command allows the administrator to save a copy of the

certificate so that it can be added to a trusted certificates file. The administrator can

then use the SSL UPDATE TRUST command to establish the certificate as a trusted

certificate.

SSL Version 3.0 Protocol Unsupported by Default


Security experts have determined that the SSL version 3.0 security protocol is

vulnerable to security breaches. Therefore, Communications Platform level 6R5

improves security by disallowing the use of the SSL version 3.0 protocol unless the

administrator specifically enables the protocol.


Levels of Communications Platform prior to 6R5 made available and, by default, used

all versions of the SSL/TLS protocols supported by Communications Platform.

However, the SSL version 3.0 protocol contains serious vulnerabilities that allow for

bypassing its protections. Therefore, Unisys recommends that sites use the SSL

version 3.0 protocol only in circumstances that make use of the protocol necessary,

such as when a peer system does not support any newer protocol versions. Starting

with level 6R5, Communications Platform does not allow or use by default the SSL

version 3.0 protocol unless the site administrator specifically names the protocol on

an SSL/TLS-SECURITY configuration statement.

DNR Uses a Random Port by Default


In previous Communications Platform releases, the DNR component used port 8210 by

default to listen for responses to Domain Name System queries. While

Communications Platform has historically allowed the administrator to specify other

options for the DNR listen port, this feature changes the default DNR behavior. With

this change, the default DNR behavior is to listen on a different randomly selected port

for each query. This feature makes Communications Platform adhere more closely to

the overall security tenet "secure by default."

CPCOMMOS Level 4R5

7831 0349–046 2–5


Communications Platform continues to allow administrators to choose the precise

DNR port-selection behavior; it merely changes the default behavior in the absence of

any administrative selection.

User Command Enhancements


This feature adds the connection or listen establishment time to the output of the

following commands, thus improving the Communications Platform administrator

interface:

STATUS SSL,LISTENS

STATUS TCP,PASSIVE

STATUS UDP,LISTENS

TCP DISPLAY

TCP GET-ITEM

TCP GET-NEXT


The additional output specifies the establishment time of a TCP active or passive

connection, a UDP listen, or an SSL listen. The additional information allows the

administrator to better monitor connections and listens.

2.4. CPCOMMOS Level 4R5

SSL/TLS Improvements


The Secure Sockets Layer (SSL)/Transport Layer Security (TLS) protocol protects

network messages from unauthorized access and tampering while in transit. In

response to discovered weaknesses and to continually improve message security, the

Internet Engineering Task Force periodically updates the protocol. This release of

Communications Platform for Open Systems takes advantage of increased protections

provided by SSL/TLS in the form of newer, more secure protocol versions and

stronger cipher suites.


Communications Platform for Open Systems level 4R5 makes the following

enhancements to improve network security:

• Adds support for TLS protocol versions 1.1 and 1.2

CPCOMMOS Level 4R5

2–6 7831 0349–046

• Adds support for the following newer, more secure cipher suites:

RSA_WITH_NULL_SHA256

RSA_WITH_AES_128_CBC_SHA256

RSA_WITH_AES_128_GCM_SHA256

DHE_RSA_WITH_AES_128_CBC_SHA256

DHE_RSA_WITH_AES_128_GCM_SHA256

DHE_DSS_WITH_AES_128_CBC_SHA256

DHE_DSS_WITH_AES_128_GCM_SHA256

RSA_WITH_AES_256_CBC_SHA256

RSA_WITH_AES_256_GCM_SHA384

DHE_RSA_WITH_AES_256_CBC_SHA256

DHE_RSA_WITH_AES_256_GCM_SHA384

DHE_DSS_WITH_AES_256_CBC_SHA256

DHE_DSS_WITH_AES_256_GCM_SHA384

Note: These new cipher suites are not available for use with SSL/TLS protocols

earlier than TLS protocol version 1.2.

Communications Platform for Open Systems employs these improvements by default,

although an administrator can also specify them within the Communications Platform

for Open Systems configuration.

To enable these SSL/TLS improvements, you must have both of the following:

• Communications Platform for Open Systems version 4R5

• A Dorado Server Firmware version from this list, or a newer version:

− Dorado 4300 or 6300 Server Firmware

− Dorado 4200 Server Firmware 2.0 Interim Correction 3



SSL GET CERTIFICATE Command


The SSL GET CERTIFICATE command allows an administrator to save a certificate,

presented by a remote system during an SSL/TLS handshake, to a file. The

Communications Platform for Open Systems administrator can perform this action

without requiring the administrator of the peer system to manually provide the

certificate.


Communications Platform for Open Systems does not allow an SSL/TLS connection

where the peer-presented certificate is not trusted. The SSL GET CERTIFICATE

command allows the administrator to extend trust to the certificate. If a peer system

presents an untrusted certificate, this command allows the administrator to save a

copy of the certificate. The administrator can then use the SSL UPDATE TRUST

command to establish the certificate as a trusted certificate.

CPCOMMOS Level 4R5

7831 0349–046 2–7

FIPS 140-2-Validated SSL/TLS


Communications Platform for Open Systems and XNIOP provide support for the

SSL/TLS protocol via OpenSSL software. This release of Communications Platform for

Open Systems and its paired XNIOP provide a FIPS 140-2-validated version of

OpenSSL. FIPS 140-2 is a governmental program that sets standards for cryptography.

This feature allows customers to meet the FIPS 140-2 standards and increase

cryptographic security.


Users can use a new field on the Communications Platform for Open Systems ADMIN

configuration statement to select whether or not to run in FIPS-approved mode.

Running Communications Platform for Open Systems in FIPS-approved mode limits

the available SSL/TLS protocol versions and cipher suites to only those which are

FIPS-approved, thus making Communications Platform for Open Systems adhere to

the FIPS 140-2 cryptographic standards.

To enable the FIPS 140-2-Validated SSL/TLS feature, you must have all of the following:


• A Dorado 4300 or 6300 Server or newer system

• The Dorado 4300 or 6300 Server Firmware 1.1, or a newer version

SSL Version 3.0 Protocol Unsupported by Default


Security experts have determined that the SSL version 3.0 security protocol is

vulnerable to security breaches. Therefore, Communications Platform for Open

Systems level 4R5 improves security by disallowing the use of the SSL version 3.0

protocol unless the administrator specifically enables the protocol.


Levels of Communications Platform for Open Systems prior to 4R5 made available

and, by default, used all versions of the SSL/TLS protocols supported by

Communications Platform for Open Systems. However, the SSL version 3.0 protocol

contains serious vulnerabilities that allow for bypassing its protections. Therefore,

Unisys recommends that sites use the SSL version 3.0 protocol only in circumstances

that make use of the protocol necessary, such as when a peer system does not

support any newer protocol versions. Starting with level 4R5, Communications

Platform for Open Systems does not allow or use by default the SSL version 3.0

protocol unless the site administrator specifically names the protocol on an

SSL/TLS-SECURITY configuration statement.

CPFTP Level 4R3

2–8 7831 0349–046

User Command Enhancements


This feature adds the connection or listen establishment time to the output of several

commands, thus improving the Communications Platform for Open Systems

administrator interface. The additional information allows the administrator to better

monitor connections and listens.


The following commands produce additional output that specifies the establishment

time of a TCP active or passive connection, a UDP listen, or an SSL listen:

STATUS SSL,LISTENS

STATUS TCP,PASSIVE

STATUS UDP,LISTENS

TCP DISPLAY

TCP GET-ITEM

TCP GET-NEXT

Increased IPv4 Router Address Configuration Limit


Some specialized environments require more than four IPv4 router addresses

configured on an IPV4-ROUTER configuration statement. This feature allows for

configuring a larger number of IPv4 router addresses to support those specialized

environments.


This feature allows an administrator to configure up to 32 IPv4 router addresses on an

IPV4-ROUTER configuration statement. Previously, Communications Platform for Open

Systems allowed only four IPv4 router addresses on such a statement.

2.5. CPFTP Level 4R3

Performance improvement


This feature improves the performance of file transfer to better take advantage of

10 Gb Ethernet NICs.

The feature leverages the Dorado 4300 / 6300 "fabric" as well as 10 Gb Ethernet NICs.


The main change is as follows:

One file transfer processing is performed by one activity and the activity uses IOW$

instead of IO$ to perform I/O to a file.

DAP Level 15R2

7831 0349–046 2–9

This feature provides some new configuration parameters to meet for your

environment.

Unisys suggests that the client uses the default configuration parameters to take

advantage of the new parameters.

The main parameters are as follows:

MAX_TRANSFER send[,receive]

Specify the number of concurrent file transfer for both

sending and receiving. The default is 20 for both send and

receive (= 20 concurrent transfer).

NUM_OF_ACW num_of_acw

Specify the number of ACWs (1 ACW = 9 TRKs) used when

reading/writing data from/to a file.

num_of_acw is allowed to have the range of 3 to 16 and

the default is 8 (72 TRKs).

REL_ALL_GRANULE ON | OFF

Specify whether cpFTP releases an initial reserve area of

a file in the first processing of file reception, if a

file has catalogued with an initial reserve.

ON: cpFTP once releases an initial reserve area of a file

and cpFTP re-assigns a file with initial reserve

after that.

This set reduces the erasing time of an initial

reserve area

OFF: cpFTP erases an initial reserve area.

The default is OFF.

Provide a capability to work local command in an inactive mode


The previous level provided new commands !LS/!DIR/!NLIS. These commands will not

work until the FTP Services client is connected to the FTP server. This feature is able

to use a local command when an FTP connection has not been established.

2.6. DAP Level 15R2

DAP level 15R2 contains the following enhancements:

• The system mode panic dump supports the Dorado-4300 and Dorado-6300

systems.

• Program mode Post-Mortem Dump (PMD) supports the Dorado-4300 and

Dorado-6300 systems.

• The GET$SWTIME function returns the current date/time in single-word time

format.

• The GET$MSWTIME function returns the current date/time in Modified-SWTIME

format.

DEPCON Level 12.0

2–10 7831 0349–046

• The EQUF mechanism ([]) supports the Modified-SWTIME formats.

• The EQUF mechanism ([]) TDATE format displays either the TDATE format or the

Modified-SWTIME format depending on the value.

• The EQUF mechanism ([]) supports banks with 24-bit addressing.

2.7. DEPCON Level 12.0

The Enterprise Output Manager 12.0 product is a feature release and includes fixes to

reported problems.

Support large file transfer from OS 2200


This feature supports transfer of large files from the Output Manager 2200

component to other servers thus, enabling users to send or receive large files without

any restrictions.


Prior releases of Enterprise Output Manager had restrictions for file transfers by

imposing the file size limit of 262143 tracks. Files that exceeded this limit were moved

into an error queue during the transfer process.

Personalize e-mail message body


This feature allows personalizing the e-mail message body with a static or dynamic

text, by changing the text style (font, color), inserting file content, and inserting images

or logos.


Prior to Release 12.0, the e-mail message body could either be part of a specific static

file or be part of a processing file. The Email Attribute is now enhanced to

1. Specify static text or dynamic text by using keyword substitution.

2. Specify static image path or dynamically using keyword substitution Set text style

(font and color) and specify the file name to insert file content in the message

body.

Hiding the URL of files in File Finder Search Results page


This feature prevents a user from unauthorized access to files that are posted using

Web Assistant, by hiding the actual URL of these files.

DEPCON Level 12.0

7831 0349–046 2–11


Prior to Release 12.0, when a user opened a file from the File Finder search result

page, the actual URL of the file appeared in the address bar. As a result, the user could

use the actual URL of the file and browse to other files posted using Web Assistant.

The encryption feature now masks or hides the URL when a user browses or

downloads a file.

DDA conditional command ("If", "Else If", and "Else") enhancements


This feature reduces the number of steps required to create a command under the "If",

"Else If", or "Else" DDA commands. The commands created based on the ‘If’ or ‘Else If’

or ‘Else’ DDA commands are now automatically positioned under the conditional

statement DDA command.

The feature also allows users to configure more than one conditional statement in the

"If" and "Else If" DDA commands by using the "AND" or "OR" conditional operator. This

reduces the number of conditional statement DDA commands and provides more

flexibility in DDA.


Prior to Release 12.0, to create a command under the "If", "Else If", or "Else" DDA

commands, a user had to drag and drop the new command under the conditional

statement DDA command. Additionally, users had to configure many or nested

conditional statement DDA commands to validate statements in a complex scenario.

This feature allows user to create commands under the "If" or "Else If" or "Else" DDA

commands by eliminating the need to drag and drop. The "If" and "Else If" DDA

commands are enhanced to specify multiple conditional statements combined with

the "AND" or "OR" conditional operator.

DDA Set Variable enhancement - Load mixed text and keywords


This feature allows users to define a new Setting type called "Dynamic string", which

essentially behaves as a "Setting type" of "String" and allows keyword substitution.

This feature is useful especially when users want to compose by setting a variable

made up of strings and keyword values. Prior to Release 12.0, the users had to use a

combination of variables and several Concatenate Variable commands to achieve the

desired result.


A new "Setting type" called "Dynamic string" is added that allows keyword substitution

as a variable value is set.

DEPCON Level 12.0

2–12 7831 0349–046

DDA Convert Variable enhancement - Get data type


This feature allows users to determine the character mix in a variable. Based on the

numeric value returned, the users can perform further computations in different

scenarios, such as validating data for a barcode.


A new "Conversion Type" called "Get data type" is added to the Convert Variable

command. This allows in determining the content type of a variable or partial contents

of a variable as indicated in the To/From fields of the DDA Convert Variable and returns

a numeric value. Based on the contents of a variable, the following numeric values will

be returned.

Value Contents of Variable

0 Tab characters or spaces or both

1 Numeric characters

2 Alphabetic characters

3 Alphabetic and numeric characters

4 Special characters

5 Special and numeric characters

6 Special and alphabetic characters

7 Special, numeric, and alphabetic

characters

Find and replace in Configuration Explorer


This feature allows a user to quickly find an attribute or a particular text in the

Configuration Explorer, saving the time when the user wants to debug or modify that

particular attribute or text. The replace functionality eases changing multiple attributes

or text instances.


Prior to Release 12.0, there was no direct way to search for an attribute or text in the

Configuration Explorer and replace it. The Find and Replace option in the Configuration

explorer now makes it easy to search for any configuration attribute or text and

replace it with a desired value. Users can also restrict the search operation to a

specific attribute or attribute type. All the search results appear in a grid that provides

an option for the users to navigate to an attribute or its property.

DMS Level 22R1

7831 0349–046 2–13

Adobe Distiller discontinuance


Unlike EOM 11.0 and earlier versions, EOM 12.0 no longer supports the use of Adobe

distiller for creating PDF files. Users can now use the Enterprise Output Manager

Integrated PDF writer feature that was introduced in EOM 10.0.

Users can contact the Unisys representative to order this no-charge feature. They may

also use a standalone PDF generator.

2.8. DMS Level 22R1

This release contains infrastructure changes in support of future feature development.

2.9. DPS Level 6R6

Supporting use of signed applets with WebTS JavaClient for Web-enabled DPS transactions


This feature allows WebTS JavaClient to conform to the latest Java security

restrictions by using signed applets for Web-enabled DPS transactions. However, to

adhere to the security restrictions related to this feature, customers must follow

additional procedures when web-enabling DPS transactions.


Signed applets allow users to ensure secure Web-enabled DPS transactions. Some

recent JRE levels display warning messages when users attempt to use unsigned

applets. Earlier Java Runtime Environment (JRE) levels allow users to hide these

warning messages. However, starting with JRE7u40, users cannot hide the warning

messages and must consent to using the unsigned applet each time before

proceeding. Starting with JRE7u51, the recommended Java security settings require

users to use signed applets and blocks all use of unsigned applets.

DPS level 6R6 contains the necessary code to allow for WebTS JavaClient signed

applets. If you use WebTS JavaClient and install DPS level 6R6, you must also

incorporate WebTS procedural changes to enable the use of signed applets. Refer to

the Web Enabler for Display Processing System User’s Guide for more information.

2.10. ECLIPSE-2200 Level 4.3.2

Eclipse-2200 IDE Ver 4.3.2 is based on the Eclipse 4.3.2 (Kepler) from the Eclipse

Foundation. For more information on what Kepler added to the Eclipse IDE, refer to the

Eclipse Web site at:

http://www.eclipse.org.

ECLIPSE-2200 Level 4.3.2

2–14 7831 0349–046

Eclipse-2200 Contents for ClearPath OS 2200 Release 16.0

Porting Unisys plug-ins to Eclipse 4.3


Qualify with the one of the most current versions of Eclipse available for the general

public consumption.


Eclipse 4.3 is the most current version of Eclipse available. Eclipse OS 2200 IDE plug-in

will be qualified against the latest version of Eclipse IDE and also the corresponding

version of the C/C++ Development Tooling (CDT).

Support for 64 bit Java Runtime Environment (JRE) and runtime environment in Eclipse


Eclipse now supports working in a 64-bit environment that provides large Random

Access Memory (RAM) space. This feature therefore facilitates handling of large

in-memory data, allowing customers to experience improvement in performance and

stability of the application.


Most of the latest versions of Windows Operating System (OS) are now of 64 bit,

providing ability to handle large amount of RAM compared to 32-bit OS.

A 64-bit OS

• Improves performance of working with large projects because the contents in the

RAM need not be swapped between the hard disk and RAM more frequently

compared to 32-bit OS.

• Provides additional RAM space compared to the maximum RAM size limit of 4 GB

in 32-bit OS.

This means, by running Eclipse within a 64-bit JRE, customers can take advantage of

improved performance due to large RAM space that can be allocated to the Eclipse

process. For example, allocating 2 GB of RAM (which is the JRE's maximum heap

space) is impossible on a 32-bit JRE. Whereas, on a 64-bit JRE, customers can easily

allocate more than 4 GB of RAM to improve performance of Eclipse.

As a result, customers can

• Open large files in multiple editors

• Easily navigate between different Eclipse components

• Avoid Eclipse from running out of memory


7831 0349–046 2–15

Telnet macros


Telnet macros help in improving customer productivity by storing frequently used ECL

statements as macros. This feature allows customers to execute the stored macros at

a different time from a Telnet session.


Storing some of the commonly used ECL commands as macros allows customers to

reuse them when required. To further improve productivity, those commands are

associated with a shortcut key. Additionally, customers can manage the configured

macros by editing or deleting them.

Eclipse C/C++ Development Tooling (CDT) project refresh


This feature provides the latest Eclipse C/C++ Development Tooling (CDT) project for

the ClearPath OS 2200 IDE for Eclipse Release for 16.0.


As part of Eclipse 4.3.2, the C/C++ Development Tooling (CDT) project has been

refreshed as well. In addition to OS 2200 UCS C support, CDT will support other

C environments.

Recording feature for keystrokes


This plug-in from Eclipse Market allows customers to record the keystrokes for cut,

copy, paste, find, replace, and type text operations so that they can playback the

sequence of operations multiple times automatically.


This feature allows customers to record a set of keystrokes (events) and play them

back at a later stage when needed. This means, customers can now record and replay

events such as

• Entering keystrokes

• Cut, copy, and paste

• Find and replace

The plug-in also allows customers to edit a recorded macro or delete a macro.


2–16 7831 0349–046

Option to run Proc Definition Processor (PDP) on an element of type COBOL Copy Proc


Customers can optionally run Proc Definition Processor (PDP) over a COBOL Copy

Proc element when the element is saved back to an OS 2200 system. This improves

productivity because customers can automatically generate the Copy Proc without

leaving the Eclipse Environment.


Customers can run PDP on a COBOL Copy Proc element to generate the definitions

for COBOL Copy Proc. Integrating this functionality within Eclipse will improve

customer productivity because they can generate the definitions without leaving the

Eclipse environment.

Highlight unreferenced working storage variables


Customers can easily identify unreferenced working storage variables, which are

defined in the working storage section in bold. This contributes toward productivity

because identifying the unreferenced variables is now lot simple and easier.


While developing a code, sometimes developers leave unreferenced working storage

variables within the code. Performing a cleanup operation of such variables is very

time consuming; however, leaving them within the code is also not recommended

because it consumes memory when the program is loaded. The current functionality

will highlight such unreferenced variables so that customers can take a remediation

action. This improves

• Customer productivity because customers do not have to spend time searching

for such unreferenced variables

• Efficiency of memory footprint of the program

E-mail files from the Eclipse environment


This feature allows customers to easily send files as an e-mail attachment without

leaving the Eclipse environment, thereby enhancing customer productivity.


This feature allows customers to attach multiple files (limit of 10 files and up to 10 MB

size limit) that are in the Eclipse environment. The files may be the opened editors, or

files within the OS 2200 Explorer or OS 2200 File Explorer. E-mailing files from the

Eclipse environment is a simple way of sharing the files with multiple recipients when

required.


7831 0349–046 2–17

Cobol Syntax Error Checking feature


This feature highlights errors within a COBOL program without performing a real

compilation. As a result, customers will find it easy to identify any errors and rectify

them, thereby improving productivity.


While developing COBOL programs, it is common to introduce syntax errors. This

feature will parse the COBOL programs and highlight the most common syntax errors,

such as duplicate variable names, duplicate paragraph names, and so on.

Provide content assist to DMS and RDMS keywords


Content assist functionality and highlighting of DMS and RDMS keywords is

implemented to improve customer development productivity.


The earlier Eclipse COBOL editor highlighted the source in different colors for verbs,

reserved words, variables, and literals; but this was not applicable for the DMS and

RDMS keywords. The content assist feature now supports syntax highlighting,

thereby allowing customers to improve productivity.

Datafile elements cacher


This feature improves performance of project creation and customer productivity

when the element list within a file is cached during project creation. At a later time,

the customer can include a new element to the project by selecting it from the cached

list instead of fetching the content from an OS 2200 system.


Customers work with elements that are added to an Eclipse project. When the project

is created for the first time, customers use a workfile and then add the elements

within the workfile. At this time, caching the element list significantly improves the

performance and productivity when more elements are included into the project at a

later time. That means, the element list is populated from a cached list; therefore,

there is no need for Eclipse to reach the OS 2200 system to fetch the new element

list. In the meantime, if a new element is added to the workfile, then customers may

choose to include the newly created element by refreshing the cache.

Conformance to OS 2200 element name standards while dragging a file into the Eclipse project


Eclipse assists customer to conform to the OS 2200 element naming standards when

a file is directly dragged from its local file system into an Eclipse project.


2–18 7831 0349–046


According to the standard naming convention of an OS 2200 element and version, a

file:

• Can be up to 12 characters long

• Can contain alphanumeric characters, - (hyphen), and a $ (dollar) sign

When a file from the local file system is directly dragged into the Eclipse project, the

filename is validated for conformance to the OS 2200 naming convention.

Non-conformance of the filename makes the element unusable for customers.

Element Date/Time changes on copy into Eclipse


Customers can rely on the last modified timestamp when an element is dragged into

Eclipse project.


When an element is copied from an Eclipse project by using the Project Explorer or

drag and drop operation, the element's last modified timestamp retains the original

timestamp. Based on the date/time displayed on the element, customers can verify

which code they have changed.

Customizable file attribute options while saving a new file on OS 2200 system


This feature provides an ability to set file attributes, such as entering the file catalog;

access (for example, public or private), addressable type (for example, sector or

word), file size (min/max and granule), while creating a new file/element on OS 2200

host.


When customers create files on the OS 2200 system, they can also set different file

attributes for the files. Allowing customers to set these parameters will improve their

ability to customize file attributes while creating a file.

Dynamic update of OS 2200 Log View


This feature provides customers the dynamic trace so that they can monitor the

activities in real time when needed. If the customers observe any error, they can

pause the logs to investigate the error further.


7831 0349–046 2–19


The OS 2200 Log View displays the log traces. These traces contain information about

the activities that have been performed using Eclipse. Since the operations performed

are dynamic, it is easy for customers to dynamically monitor the logs while they are

happening. As a result, in the event of an error, they can pause the logs to investigate

the issue further.

Wildcard assistance with a list of supported wildcards for OS 2200 File Explorer


This feature improves customer productivity by allowing customers to leverage the

information on wildcard usage when using OS 2200 File Explorer or including elements

into a project.


With the help of supporting wildcards, customers can easily filter the file or element

list when using OS 2200 File Explorer or including elements into a project. This intuitive

filter functionality assists customers to use the wildcard feature more appropriately.

Display timestamp when the OS 2200 File Explorer cache is cleared


This feature indicates when the customer has last cleared the cache information.


This feature provides an indication when the cache was last cleared so that the

customer can decide to perform a refresh of the cache if it is a stale cache.

OS 2200 Compare Tool Manager


This feature manages configuration and maintenance of the compare tool in OS 2200.


OS 2200 Compare Tool Manager allows customers to easily configure and maintain a

compare tool.

OS 2200 comparison tool to work independent of workspace


This feature provides an ability to use the configured comparison tool across different

workspaces.


2–20 7831 0349–046


Generally, customers configure the comparison tool once and use the same tool

across different workspaces. Customers can now make global settings for the

configuration tool to make the tool function more effectively across different

workspaces.

Field Size for COBOL variable-structures.


COBOL programs may contain very large variable-structures. Calculating the size of

such structures can be time-consuming and error-prone. This feature provides an

ability to calculate the size of such structure efficiently and correctly, thereby

improving productivity.


Customers generally want to calculate the size of COBOL variable-structures in order

to match the value with its redefinition or its equivalent Schema-definition. This

feature allows the customers to know the offset (Start Bit and Size) of each variable in

the structure accurately and in considerably no time.

Content Assist for ECL statements


This feature provides an ability to insert the ECL statement in the Text-editor in

Eclipse-2200 from the list of ECL statements displayed in the content assistant. The

users can tab through the ECL parameters and change them as required, thereby

improving productivity.


This feature allows the customer to insert the ECL statements to a buildstream with

ease. The content assistant provides a list of the most commonly used ECL

statements to choose from. The user can tab through the default parameters, such as

track-size, granularity, filename, and so on, and change them as required.

Error messages are not properly localized on the Japanese Windows operating system


This feature enhancement allows customers to view the messages in the specific

locale they are in.


For a non-English speaking customer, displaying error messages in English is of no

use. The Java internationalization mechanism will allow customers to view error

messages that are specific to their locale.

EPORTAL-2200 Level 2.2

7831 0349–046 2–21

2.11. EPORTAL-2200 Level 2.2

Support for Microsoft Visual Studio 2013 and .NET 4.5 / 4.5.1


Support for Microsoft support for the latest web standards, updated code and design

editors for HTML5, CSS3 and JavaScript, integrated multi-browser testing, improved

IntelliSense, deployment options, and more.

Expose any ClearPath Data Source as .Net Annotated Models for easy integration with

the widest range of Microsoft application development technologies. Exposing

ClearPath ePortal Data Sources as standard annotated models automates presentation

generation, model binding, and validation between models and their presentations

across a variety of Unisys and Microsoft project types.

Support for Microsoft dependency-checked ClearPath ePortal feature updates. Add

only the capabilities you need to your projects for improved flexibility.

Support for Visual Studio Multi-Targeting for the .Net Framework. Work with the latest

versions of the .Net Framework, or optionally target earlier versions from within the

same version of Visual Studio. Easily import earlier versions of ClearPath ePortal

projects without risking upgrade changes.

Support for the new Visual Studio One ASP.Net unified web project template. Gain

access to all the web development features in ASP.Net from within a single web

project, avoiding hard-to-change initial project choices.

Experience improved development cycles and build performance when working with

large Agile Business Suite, Enterprise Application Environment(EAE), and other

projects that typically contain large numbers of transactions and messages.

Support for Microsoft’s Model-View-Controller 5 (MVC 5)


Model-View-Controller is a popular design pattern that helps cope with application

complexity by separating major functionality into customizable and flexible

components. ClearPath ePortal now supports Microsoft’s ASP.NET

Model-View-Controller 5 (MVC 5) Framework as an alternative to ASP.Net Web Forms

for web, mobile, and web service presentation generation. MVC brings unique

advantages, including:

• Superior architecture that promotes separation-of-concerns, test-driven

development, pluggable and extensible components, and flexible request

routing policies that accommodates Web designers who value a high degree of

control and choice of client-side presentation technologies and frameworks.

• Supports all ClearPath MCP and OS 2200 application Data Sources, including Agile

Business Suite, Enterprise Application Environment, 3GL COBOL and UTS/T27

terminal screen applications, Open OLTP, and forms presentation libraries

(DPS/SDF).


2–22 7831 0349–046

• Presentation Generation based on Microsoft’s Templating Engine, making it

possible to change the type of presentation generated by modifying simple,

text-based templates.

• Easily leverage popular, open-source, client-side frameworks such as jQuery,

Knockout, AngularJS, Backbone.js, and others for complete application control and

rich client-side scripting.

• Target desktop and mobile applications with a single project and common code by

using the Bootstrap responsive client-framework. Responsive client frameworks,

using standard HTML,CSS, and JavaScript, adapt the presentation based on screen

dimensions and device capabilities to provide the best user experience across

mobile and desktop devices with a single code base.

• Automatic two-way binding and input validation between a model and its

presentation with automatic generation of form validation controls and error

messages.

• Automatic generation of the MVC Models (Views and Controllers) based on new

or existing ClearPath ePortal Data Sources. Models support automatic binding and

validation and error handling for popular data types such as e-mail addresses,

URLs, currency, and phone numbers as well as for ClearPath-specific data types.

• Easily leverage tools such as LESS for CSS design, automatic minification, and

bundling of client scripts for efficiency and easy modification.

• Unisys provided MVC Helpers and Templates tailored to ClearPath application

modernization.

• Integrate multiple ClearPath Data Sources from within a single MVC project.

Support for Web API RESTful Service Applications


ClearPath ePortal supports Service Oriented Architectures (SOA) by automatically

exposing your ClearPath applications as Microsoft WCF (SOAP) and RESTful web

services. New for ClearPath ePortal is the ability to expose your ClearPath application

by using the ASP.NET Web API, MVC-based framework.

Microsoft Web API is a RESTful web service that is built upon the MVC framework.

Web APIs can be accessed by a variety of HTTP clients, including browsers and mobile

devices.

Enhancement for Unisys Mobile ASP.NET Web Form Projects


New Unisys Mobile ASP.Net Web Form Themes for iOS 7, Android, and Windows

Phone 8. Mobile applications now receive the latest, adaptively rendered mobile user

interfaces (UIs).

Integration with the NuGet Package Manager for incremental updates to mobile

themes.


7831 0349–046 2–23

New Unisys Hybrid App Build Service


With ClearPath ePortal, developers will also gain access to the Unisys Hybrid App

Build Service, a new Cloud-based, mobile application build service from Unisys. With

point-and-click simplicity, the Unisys Hybrid App Build Service allows you to submit

your HTML, CSS, and JavaScript project assets to the Unisys-hosted build service and

receive installable applications for your targeted devices, all from within Microsoft

Visual Studio. Using the Hybrid App Build Service, developers can now easily build

hybrid mobile applications that

• Leverage the native capabilities of mobile devices that were previously

inaccessible to cross-platform, web applications

• Write applications once using familiar web application development technologies,

including HTML5, CSS3, and JavaScript. Build the application without having to

master each platform's proprietary language, software development kit (SDK), and

tool set.

• Use common JavaScript APIs to access native functions like the GPS and

Geolocation, Camera Image and Video Capture, Barcode Scanning,

Push-Notifications, local app data such as Contact List information,

Accelerometers, Compass, In-App-Browsing, Local Storage and more across

multiple platforms with the convenience of never leaving Visual Studio or installing

and learning platform specific SDKs and development environmental tools and

languages.

• Because the app is written for the web, locally test your application in a browser

before packaging it for native platforms.

• Install as native applications on Android, Apple iOS, and Microsoft Windows Phone

8 devices.

• Publish applications to Apple’s App Store, Google Play, Windows Phone Store or

local enterprise app repositories.

Support for Agile Business Suite on Windows


ClearPath ePortal is now available for the Agile Business Suite Windows Runtime

Server. An Agile Business Suite application running in the Windows environment can

now take advantage of ClearPath ePortal modernization capabilities.

EXEC Level 49R2

2–24 7831 0349–046

New modern look and feel


An improved management interface that supports the latest desktop and tablet

browsers.

New terminology that is consistent with the latest processing technologies from Intel

and Unisys.

New Terminology Old Terminology

ePortal Manager

Partition

Controller

ePortal Web

Partition

Web Personality

Module

ePortal Web Cluster Virtual Server

Platform Chassis

Support for separately managed administrator credentials


Provides enhanced compatibility with industry-standard security requirements.

An expanded web service-based automation capability


Allows automation of many management tasks through a web services interface.

2.12. EXEC Level 49R2

Exec Support Product Level Summary:

ARC 5R8 5.15

DMPLIB 9R2 9.24

E$ORMSG 6.14

MILES 1R4 1.17

MMGR 49R2 43.64

MSCP 3R8E 3.19

PASSGEN 2R2 2.4

RLIB$ 1.87

TIPUTIL 49R2 49.7

VIPR 1R3C 1.8

This release of the Exec supports ClearPath OS 2200 16.0 with increased stability,

performance, and new functionality. The file recovery portion of the recovery boot

time is reduced by 15-80%, depending on configuration (number and type of disks and

number of files).

EXEC Level 49R2

7831 0349–046 2–25

ARC Inclusion of APPREC


Consolidates all ARC utilities and runstreams in the ARC product.


The sample runstreams for ARC and the APPREC processor called by these

runstreams were previously packaged with the IRU product. While these runstreams

are setup primarily to automate IR application group recovery, they are only used

along with the ARC product. Therefore, the sample runstreams and the APPREC

processor are now included with the ARC product.

Freespace Depletion Option


Allows a customer to optionally avoid the read and reply system console message

which is issued when a TIP Freespace file is depleted of all records of a defined

Freespace file record type. This ability can be used to give an application the ability to

resolve the situation and avoid potential down time.


A new Freespace file attribute (RDQ - Record Depletion Query) is defined which, if

specified, will prevent the read and reply system console message from being

generated when a request is made for a Freespace record type for which no records

are available. The request will instead immediately receive an FCSS error status 046

indicating that no records are available for the requested record type. The TIP utility

FREIPS is updated to allow the setting/clearing and displaying of the RDQ Freespace

file attribute. In an XTC environment, updates of the RDQ Freespace file attribute are

broadcast to all hosts in the XTC environment.

Freespace TDATE$ Remediation


Provides infrastructure for the forthcoming feature to change the format for all new

timestamps in the TIP Freespace complex. Modified-SWTIME is the replacement

timestamp format for TDATE$ for new timestamps in the TIP Freespace complex. This

feature makes OS 2200 compatible with both the TDATE$ and Modified-SWTIME

timestamp formats in the TIP Freespace complex.

EXEC Level 49R2

2–26 7831 0349–046


TDATE$ use is being phased out of the OS 2200 products as the TDATE$ timestamp

format will wrap the year portion after 2027-12-31 23:59:59. Control of

Modified-SWTIME timestamp generation in the TIP Freespace complex is provided

globally by a new dynamic EXEC configuration parameter

(freespace_modified_swtime) and at a TIP application group level via a new dynamic

Freespace parameter (MSWTIM). Both of these dynamic configuration parameters

initially default to FALSE (TDATE$ timestamps continue to be generated in the TIP

Freespace complex). Both of these configuration parameters must be enabled before

Modified-SWTIME timestamps are generated in a TIP Freespace application group.

These configuration parameters affect only new timestamps in the TIP Freespace

complex. Existing timestamps in the TIP Freespace complex are not changed with this

feature. The TIP utility FREIPS is updated to define and display the new Freespace

application configuration parameter MSWTIM. Modification of the MSWTIM parameter

is not allowed in this release (its value will be FALSE/NO). When able to be set to

TRUE/YES in a future release, all new timestamps in the corresponding TIP Freespace

application group will be generated in Modified-SWTIME format (this assumes the

EXEC global freespace_modified_swtime configuration parameter has also been

enabled on the system).

ER TERMRUN$ using a USERID


This feature permits a privileged user to terminate all runs or transactions associated

with a specified userid.


ER TERMRUN$ can be used by a privileged user to terminate a specific run or to

terminate multiple runs that meet the criteria in passed in the input packet. The criteria

passed on input can, for example, include all transactions in an Application Group.

This feature permits a privileged user to terminate all runs or transactions associated

with the userid specified in the input packet. The userid specified on input must not be

the userid associated with the run that issues the ER TERMRUN$.

When a userid is specified on input, the ER TERMRUN$ searches all runs and

transactions in the system. If a batch run or a transaction is found to be associated

with the specified userid, an E,N keyin is issued for that run or transaction. The batch

run or transaction is terminated but the N-option on the E-keyin does not allow

diagnostics. If a demand run is found to be associated with the specified userid, a "SM

siteid T" keyin is issued. The demand run is terminated and the site is disabled.

This feature is intended for use by intrusion detection mechanisms.

SMOQUE and SDF Timestamp


This feature introduces UTC-based timestamps in Modified-SWTIME format to

SMOQUE entries and SDF type 050 label records.

EXEC Level 49R2

7831 0349–046 2–27


This feature:

• Adds a new timestamp in Modified-SWTIME format to the SMOQUE entries

maintained in the SYS$*GENF$ file.

• Adds a new timestamp in Modified-SWTIME format to the SMOQUE entry

information returned by ER SMOQUE$ and the SMOQ$HNDLR interface -- the

existing TDATE$ format timestamp continues to be returned.

• Permits SMOQ$HNDLR callers to specify input timestamps in either TDATE$

format or the new binary format (Word 1 YYYYYYMMMDDD, Word 2

HHHMMMSSS000).

For the SMOQUE entry maintained in the SYS$*GENF$ file, the new Modified-SWTIME

format timestamp is placed in a word that was previously reserved. The existing

TDATE$ format timestamp is retained which allows existing utilities continue to

execute as before. This feature does not require a Jump Key 9 boot and a recovery

boot will add the Modified-SWTIME format timestamp to a SMOQUE entry if one does

not exit.

Master File Directory (MFD) TDATE$ Remediation


Provides infrastructure for the forthcoming feature to change the format for all new

timestamps in the Master File Directory (MFD). Modified-SWTIME is the replacement

timestamp format for TDATE$ for new timestamps in the MFD. This feature makes

OS 2200 compatible with both the TDATE$ and Modified-SWTIME timestamp formats

in the MFD.


TDATE$ use is being phased out of the OS 2200 products because the TDATE$

timestamp format will wrap the year portion after 2027-12-31 23:59:59. New dynamic

configuration parameters mfd_modified_swtime and shared_mfd_modified_swtime

are added. These parameters initially default to false and can only be set to false.

When set to false, all new timestamps in the specified MFD are in TDATE$ format.

When able to be set true in a future release, all new timestamps in the specified MFD

will be in the format Modified-SWTIME. These parameters affect only new

timestamps in the MFD. Existing timestamps in the MFD are not changed with this

feature.

Summary Accounting File TDATE$ Remediation


Provides infrastructure for the forthcoming feature to change the timestamp format

for all new timestamps in the Summary Accounting File. Modified-SWTIME is the

replacement timestamp format for TDATE$ for new timestamps in the Summary

Accounting File. This feature makes OS 2200 compatible with both the TDATE$ and

Modified-SWTIME timestamp formats in the Accounting file.

EXEC Level 49R2

2–28 7831 0349–046


TDATE$ use is being phased out of the OS 2200 products as the TDATE$ timestamp

format will wrap the year portion after 2027-12-31 23:59:59. A new dynamic

configuration parameter accounting_modified_swtime is added. This parameter initially

defaults to false and can only be set to false. When set to false, all new timestamps in

the Accounting file are in TDATE$ format. When able to be set true in a future release,

all new timestamps in the Accounting file will be in the format Modified-SWTIME. The

parameter affects only new timestamps in the Accounting file. Existing timestamps in

the Accounting file are not changed with this feature.

Secure by Default - Optionally disallow @@PASSWD


This feature lets the site configure the Exec to either allow or disallow @@PASSWD

transparent commands in Fundamental Security and Security Levels 1 and 2. This has

two benefits:

First, the Exec does not have a way to blank the password when the user types

@@PASSWD commands, and this feature addresses the threat of someone looking

over the shoulder of the terminal user and seeing his new password as he enters it.

Second, @@PASSWD bypasses authentication modules. This means that the user of

Configured Password Profiles (CPP, AM 19), introduced in release 15.0, might think he

is changing his password with @@PASSWD, only to later find that the CPP password

area was not updated by @@PASSWD. If @@PASSWD is not allowed, all other ways a

user can change a password are effective ways of changing the CPP password.


In previous Exec levels, @@PASSWD is disallowed when Security Level 3 is configured

but allowed in all lower security levels.

A new Exec dynamic configuration parameter, enable_passwd_control_statement,

allows the use of @@PASSWD if the parameter value is TRUE and disallows it if the

parameter value is FALSE. This applies to Fundamental Security and Security Levels 1

and 2. The default value for these security levels is FALSE, which is a change from

previous releases. If a user enters the @@PASSWD command when it is disallowed,

the Exec responds with the following message, is the same message displayed at

Security Level 3 in previous releases:

'System configuration disallows password changes by @@PASSWD'

Secure by Default - Configure Delayed Sign On Solicitation to meet PCI DSS guidelines


The hacker frustration method Delayed Sign-on Solicitation quadruples the wait time

between sign-on prompts, thus slowing down a hacker (human or automated) trying

to guess a valid user-id/password combination. After 8 attempts, the Exec disables

the terminal. However, to comply with customer security policies, configuring it for a

lower number is required.

FLIT Level 15R2

7831 0349–046 2–29

The PCI DSS 3.0 requirement 8.1.6 says to lock out the user after no more than 6

attempts, and this feature lets a site limit attempts to 6 or any other number up to 8,

thus making Delayed Sign-on Solicitation a viable choice for sites who might have

previously avoided it because it could not meet the PCI DSS requirement.


The existing Exec configuration parameter max_sign_on_attempts controls the

maximum number of sign-on attempts a user has to successfully sign on to a terminal.

In previous releases, it only applied when the hacker frustration method was to ignore

excessive logins after the limit was reached or exceeded. The default value for

max_sign_on_attempts changed from 63 to 5 in release 15.0.

With this Exec level, max_sign_on_attempts applies to delayed sign-on solicitation. If

the configuration parameter delayed_sign_on_solicitation is TRUE, the Exec will

continue to quadruple the wait time between sign-on prompts, as before, and it will

disable the terminal after max_sign_on_attempts or 8 incorrect login attempts,

whichever is smaller. As in previous releases, the terminal remains disabled until the

operator enables it with a TS command or until the system is rebooted.

Because max_sign_on_attempts now applies to delayed sign-on solicitation, it is no

longer accurate to say that the two methods of hacker frustration are Max Sign On

Attempts and Delayed Sign-on Solicitation. Instead, the terminology changes with this

release to say that the two methods of hacker frustration are Ignore Excessive Logins

and Delayed Sign-onSolicitation. This change of terminology is fully compatible with

the previous use of max_sign_on_attempts, which is now described as follows:

Configuring a value for max_sign_on_attempts sets the maximum number of invalid

sign-on attempts to a number in the range 1 through 63 (with a default of 5). After the

specified number of attempts has been reached or exceeded,

• If delayed_sign_on_solicitation is FALSE, the system uses the Ignore Excessive

Logins method of hacker frustration and ignores further entries but keeps

soliciting entries from the user.

• If delayed_sign_on_solicitation is TRUE, the system disables the terminal; note that

if max_sign_on_attempts is more than 8, the system will disable the terminal at

the 8th incorrect login attempt, before reaching max_sign_on_attempts.

2.13. FLIT Level 15R2

FLIT level 15R2 contains the following enhancements:

• System mode supports the Dorado-4300 and Dorado-6300 systems.

• The system mode MEM$STATUS function displays the SAIL-based memory

status.

• The system mode APBOOT processor NOPREP command supports a disk name.

• Program mode supports the S2200$8070 (Dorado-4300 and Dorado-6300)

machine type. MACH:=S2200$8070.

IRU Level 22R2

2–30 7831 0349–046

• Program mode emulates the ER-MODSWTIME$ and ER-TIMECONFIG$ executive

requests.

• Program mode emualtes the CALL-MOD$SWTIME and CALL-TIME$CONFIG

executive calls.

• The GET$SWTIME function returns the current date/time in single-word time

format.

• The GET$MSWTIME function returns the current date/time in Modified-SWTIME

format.

• The EQUF mechanism ([]) supports the Modified-SWTIME format.

• The EQUF mechanism ([]) TDATE format displays either the TDATE format or the

Modified-SWTIME format depending on the value.

• The EQUF mechanism ([]) supports banks with 24-bit addressing.

2.14. IRU Level 22R2

REPLICATE MOVE restart


This feature provides a mechanism to restart replication in a move set.


Prior to IRU level 22R2, if something happened with the original move history or tapes

or some other error was encountered, there was no way to continue replication for a

set; you had to delete the set and start over.

Sites might want to retain the existing information in a set while starting over after an

issue. This feature provides syntax to mark a hole and restart the replication process

from a new start point.

LIST APPL


Provide the ability to display application and audit trail status.


Some IRU commands require knowing the application group status before execution.

While this information is readily available in the AP and AT keyins for local application

groups, it is not easily accessible for multiple hosts in a concurrent application group

environment.

The LIST command is enhanced to display application group state, audit trail state, and

DR flag for any or all AG/hosts.

JBOSS-2200 Level 6.2

7831 0349–046 2–31

REPLICATE use of TAPE-TYPE-OVERRIDE


Enhances tape type override capabilities within REPLICATE commands.


The configuration parameter TAPE-TYPE-OVERRIDE replaces the specified presumed

tape type with another compatible type. This parameter works well for most

commands, but can cause problems for commands that use multiple reels at the same

time: REPLICATE and B-option DUMP, DUMP CHANGES, or MOVE commands.

In REPLICATE, this parameter is currently applied to both the source and destination,

which may not be the desired effect. To make replication work well, we need a way to

determine if the override should be applied to the source or the destination or both.

There may be cases where the users want a different override applied to each, which

would require two override values.

This feature introduces two new configuration parameters:

TAPE-TYPE-OVERRIDE-R for read tape assignments and

TAPE-TYPE-OVERRIDE-W for write tape assignments

TAPE-TYPE-OVERRIDE is retained, with changes to its value applied to both new

parameters.

2.15. JBOSS-2200 Level 6.2

JBOSS-2200 level 6.2 is a feature release of the Red Hat JBoss Enterprise Application

Platform for the OS 2200 platform.

JBOSS-2200 is provided as a SOLAR installable tape for installation to an OS 2200

system. The JBoss level 6.2 for ClearPath OS 2200 Developer Kit and Documentation

DVD media is available that contains the JBoss source code and the JBoss binaries

that can be used to install JBoss-2200 to a workstation for development and testing.

Upgrade to Red Hat JBoss Enterprise Application Platform (EAP) 6.2


Provide the most current level of the JBoss Enterprise Application Platform (EAP),

which is 6.2.


JBoss EAP 6.2 includes many improvements and fixes.

JBOSS-2200 Level 6.2

2–32 7831 0349–046

Key Features of JBoss EAP 6.2 include:

• Role-based access control (RBAC) for management operations

Role-based access control (RBAC) has been implemented, improving granularity of

access control for management operations through all management interfaces.

Users and groups can be associated with one of several roles that determine the

level of access to the management operations.

• Syslog Handler Configuration

JBoss EAP 6 now provides a handler and configuration for the syslog protocol.

• External JNDI Federation

A Naming subsystem configuration has been added to the JBoss EAP 6

configuration that enables an administrator to connect an external naming system

to the JBoss EAP 6 JNDI. This capability replaces the ExternalContextMBean from

JBoss EAP 5.

Other new features include:

• Generic JMS Resource Adapter

A generic JMS resource adapter is now available with EAP 6.2. This resource

adapter is provided to support integration with external JMS systems that do not

provide their own resource adapter and supports both XA and non-XA use cases.

• Management Operations for Patching

Management operations to install patches, roll-back patches, and report patch

state have been implemented. These operations enable users to install CVE,

single, and cumulative patches in JBoss EAP 6.2 releases and beyond. The

operations are exposed in the CLI, Native, and HTTP management interfaces. The

operations will be exposed in the console in a later release.

• Administrative Audit Logging

New configuration options for logging of administrative actions. Management

access to the audit log configuration can be scope to Auditor role defined in RBAC

configuration.

• Integration with WebSphere MQ via WebSphere MQ resource adapter has been

tested and certified

Integration with WebSphere MQ via the WebSphere MQ resource adapter has

been tested and certified.

• JDBC Transaction Store

JBoss transactions can be configured to store transaction state in any of the

RDBMS systems tested with JBoss EAP 6.2. This enhancement eliminates the

need for a shared file system for transaction recovery.

• WSI-Basic Profile 1.2 and 2.0

JBoss Web Services has been tested to assure compliance with the WSI-Basic

Profile 1.2.

JPJVM Level 8.0

7831 0349–046 2–33

• HornetQ discovery via JGroups

HornetQ now offers dynamic discovery of server connection settings via UDP and

JGroups.

• JBoss CLI Silent Mode

A 'Silent Mode' has been added to the CommandContext API for processes

embedding the CLI.

• Support of customer transports in Mail subsystem

The mail subsystem has been enhanced to enable an administrator to provide a

custom transport protocol.

• New Hibernate Batch loading Algorithms

Hibernate has added two batch loading algorithms to the existing Legacy

algorithm: Dynamic and Padded.

• Hibernate improved second level caching of objects referenced for Non-Mutable

Data

The Oracle 12c database has been tested and added to the list of supported

configurations.

JBoss EAP 6.2 (JBoss 2200)is qualified and is supported on JPJVM 7 (JDK 1.7)

For more information on the features of JBoss EAP 6.2, please refer to

http://www.jboss.com/products/platforms/application/features.

2.16. JPJVM Level 8.0

• Remove support of Oracle JDK 6.

• Update to the latest version of Oracle JDK 7 and JDK 8 Java levels.

• JDK level 7 remains the default level.

2.17. LSS Level 14R4

Support for the UCOB 12R2 Features


See section 2.30 for information on the UCOB 12R2 features.

MAP Level 33R2

2–34 7831 0349–046

2.18. MAP Level 33R2

Provide New Collector-defined Symbols as TDATE$ Alternatives


The two Collector-defined symbols D$ATE and T$IME can be used together to create

a TDATE$ format timestamp indicating when an absolute element was created by the

Collector (MAP). Since TDATE$ format overflows on 2028-01-01, additional timestamp

formats that remove the date overflow restriction are provided.


There are six new Collector-defined symbols that indicate when an absolute element

was created:

• The symbols SYSTIME1$, SYSTIME2$, SYSTIME3$, and SYSTIME4$ can be used

together to create a four-word SYS$TIME (TIMEB) format timestamp. A TIMEB

format timestamp is in UTC time and contains the seasonal and time zone offsets

necessary to convert it to local time. A TIMEB format timestamp also contains the

time zone mnemonic.

• The symbols SYSTIME1$ and SYSTIME2$ can be used together to create a

two-word DWTIME$ format timestamp in UTC time.

• The symbols DWTIME1$ and DWTIME2$ can be used together to create a

two-word DWTIME$ format timestamp in local time.

SYSLIB 77R1 provides the new procedures S$YSTIME, D$WTIMEUTC, and D$WTIME

that use the new Collector-defined symbols to generate the three timestamp formats

described above.

2.19. MASM Level 6R3L

2200/9010 Adapt


Allows you to select the MASM instruction set for systems with the 2200/9010

system type designation.


The M$9010 definition is added to the MASM definition element MACH$DEF. You can

specify this definition on a $MACH directive to select the instruction set for the

2200/9010 system. This instruction set is architecturally identical in MASM to the one

selected by the M$8020, M$8030, M$8040, M$8050, M$8060, and M$8070 definitions

for the 2200/8020, 2200/8030, 2200/8040, 2200/8050, 2200/8060, and 2200/8070

systems. The M$M_SERIES definition selects the instruction set for all M Series

architectures, including the 2200/9010 system.

RDMS Level 20R1

7831 0349–046 2–35

The following illustrates the use of the new definition:

$INCLUDE 'MACH$DEF' . Include machine definitions

. ...

$MACH M$9010 . Select 2200/9010 instructions set

2.20. RDMS Level 20R1

Derived Tables


Using derived tables, you can write more complex SQL queries. The SQL explain and

get description commands provide information related to the derived table.


A derived table is a query expression with a correlation name which, when evaluated,

populates a table. The description of the derived table appears in the explain text at

the end of the section for the access macro that the derived table is defined in.

Common Table Expression (CTE)


This feature is used as a shortcut for writing a derived table and replace the multiple

usages of a query-expression within an SQL statement. The SQL explain and get

description commands provide information related to the CTE.


The WITH clause is used to create a CTE. When a CTE is referenced multiple times,

the description of the CTE appears at the beginning of the explain text.

Performance improvement in arithmetic expression evaluation


SQL statements containing arithmetic expressions, such as price+1, are executed

using less CPU.


• The RDMS optimizer now converts constants, such as the "1" in the expression

price+1, to the data type in which the expression is evaluated. This eliminates the

need for data type conversion during runtime.

• Expressions consisting of only constants, such as dateadd ('dd', -70 '1998-12-01'),

are now evaluated only once.

• The RDMS arithmetic expression evaluation code is streamlined to improve

performance.

RDMS Level 20R1

2–36 7831 0349–046

Comparison operator augmentation


Adding two "synonyms" for the inequality operator (<>) eases the conversion from

other implementations and provides the C programmer more similarity between SQL

and C.


Testing for inequality in an SQL statement is performed by the operator ^= or != in

addition to the existing <>.

Performance improvement in Boolean expression evaluation


SQL statements containing Boolean expressions, such as WHERE price BETWEEN 3

AND 7, now execute using less CPU. SQL statements including IN, OR, ANY may

execute using less CPU.


A Boolean expression may be evaluated by the Relational Storage Manager (RSM) or

less efficiently by the RDMS Abstract Machine (AB). The RDMS optimizer has

implemented several new optimizations which move the evaluation from AB to RSM.

One optimization relates to expanding the other entation of IN, and ANY to be

transformed into EXISTS even when there are other predicates in the WHERE

condition. Earlier releases evaluated the IN predicate as an RDM Boolean when a Built

In Function (BIF) was involved; such IN predicates are now evaluated as RSM

Booleans. If a Boolean factor involves multiple tables, earlier levels of RDMS evaluate

those predicates as an RDM Booleans. RDMS may now duplicate some of the

predicates as RSM Booleans to allow for earlier evaluation of those predicates. With

these optimizations, EXPLAIN shows more RSM Booleans and, may or may not, show

fewer RDM Booleans. The addition of the RSM Booleans means that the more

expensive RDM Booleans are executed less often.

The RDMS code which evaluates Boolean expressions is streamlined to improve

performance.

RDMS Catalog improvements


The performance of the RDMS Catalog views is optimized.


This feature improves the performance of the RDMS Catalog views by updating the

view syntax and updating the RDMS code to recognize the views. New RDMS Catalog

views are created which are variations of existing views, but with improved

performance.

RDMS-JDBC Level 2.10

7831 0349–046 2–37

Expanded Timestamp Format


This feature allows additional variations of timestamp literals to appear in SQL

commands. Some customers will find these timestamp formats more in line with local

timestamp conventions.


RDMS accepts timestamp literal strings in the following format:

yyyy-mm-dd-hh.mm.ss(.ffffff)

Note the dash between the date and time portions and the dots between hours,

minutes, and seconds

2.21. RDMS-JDBC Level 2.10

Simplified Installation


Installation of the RDMS-JDBC metadata catalog is now part of the UREP install

process.


Prior to RDMS-JDBC level 2.10, the installation of the RDMS-JDBC metadata catalog

(JDBC$CATALOG2) was a post-SOLAR install process step. Now (in ClearPath OS 2200

release 16.0) this catalog is automatically installed as part of UREP install, either as

migration or initial install.

Environment Verification


JDBC Server performs a quick check of the RDMS environment each time the server

is started. This feature also helps detect metadata access problems early and logs any

issues.


Performs a six-step verification process each time the JDBC Server is started. Proper

access to the JDBC and RDMS metadata catalogs is verified. Any issues are logged

and the JDBC Server is shut down if critical issues are detected. The verification steps

can be bypassed with a runtime execution option.

JDBC Database Metadata Performance Enhancements


Execution times for many of the JDBC DatabaseMetadata API methods are improved.

This provides faster response times for many tools that read the metadata associated

with the RDMS database.

SECURITY-ADMIN Level 4R4A

2–38 7831 0349–046


The execution times for many of the JDBC DatabaseMetadata API methods,which

return ResultSets, are reduced. For example, getColumns() and getIndexInfo().

2.22. SECURITY-ADMIN Level 4R4A

In this release, the SECAGX and SECMGR OS 2200 components support

Modified-SWTIME use in the Summary Accounting file. To support Crossboot

backward, this release also runs on release 15.0. This release also contains stability

fixes for the SECMGR OS 2200 component. No changes were made in the Windows

client application. Because of changes in the Exec handling of the security file in

release 16.0, Security-Admin now shows a user-id as disabled (timed out) when the

days of inactivity exceeds the maximum allowed. Updated Security Client

documentation in .chm and PDF format is available on the release 16.0 Product

Information DVD and the Unisys support website. It includes the release 16.0 Exec

Secure by Default features.

2.23. SLIB Level 2R1

Support Modified-SWTIME Format as a TDATE$ Replacement


The UTC-based, one-word Modified-SWTIME format timestamp was added in

ClearPath OS 2200 release 15.0 to provide a potential replacement for the one-word

TDATE$ format timestamp, which overflows on 2028-01-01. The SLIB Time Format

Convert service and the UPLS SLIB shell interface to SYSLIB routines SFDT$ and

TIMECONV$ now support Modified-SWTIME. This allows you to replace TDATE$

timestamps in your own applications and to adapt to the ongoing replacement of

TDATE$ formatted timestamps with Modified-SWTIME timestamps in externally

visible Unisys data structures at your own pace without impacting your existing

program base.


The SLIB Time Format Convert service and the UPLS SLIB shell interface to SYSLIB

routines SFDT$ and TIMECONV$ accept the Modified-SWTIME format as a valid

timestamp.

To allow you to replace TDATE$ timestamps with one-word Modified-SWTIME

timestamps at your own pace, the affected SLIB service and SLIB shell interfaces

automatically recognize and process both TDATE$ and Modified-SWTIME timestamps

when the input timestamp type is specified as TDATE$. This allows migration from

TDATE$ timestamps to Modified-SWTIME timestamps with no required code change

nor impact to your existing calls to Time Format Convert or the SLIB shell interface

routines SFDT and TIMECONV$. If desired, you can inhibit this part of the feature by

setting an option in the calling packet.

In addition to this automatic detection of Modified-SWTIME timestamps passed as a

TDATE$, you can explicitly specify an input timestamp format of Modified-SWTIME.

SORT Level 22R3

7831 0349–046 2–39

The updated SLIB service and shell interface routines support timestamps in TDATE$,

DWTIME$, SYS$TIME (TIMEB), Modified-SWTIME, and three-word binary formats.

Conversions from UTC-based Modified-SWTIME to local time require additional time

configuration information. The default action is to retrieve the running system's time

configuration using ER TIMECONFIG$. To avoid repeated time configuration retrieval,

or to accommodate translation to other time zones than the currently running system,

you can set an option to provide an alternative time configuration as input to use in

the conversion.

In the SLIB Time Format Convert service, Modified-SWTIME timestamps can be

converted to all supported date and time formats. However, local timestamps cannot

be converted to UTC-based formats (Modified-SWTIME and SYS$TIME).

2.24. SORT Level 22R3

Support for the TDATE$ Remediation adapt.

2.25. SP-OPERATION Level 15.0

The Operations Sentinel level 15.0 product is a feature release. This feature set applies

to Operations Sentinel Basic Edition, Department Edition, and Enterprise Edition.

Feature Content:

The following is an overview of each feature:

ADBM Editor enhancement

Provides enhanced editing capabilities into the Autoaction Database Manager.


This feature provides more powerful visual editing features to ADBM editor in

Operations Sentinel, such as

• Keyword/Syntax coloring

• Ability to insert Event Report templates, such as AC, CO, and so on

• Ability to split the editor into two separate panes for the same source file


The earlier version of ADBM editor is a simple text editor that does not support any

advanced editing capabilities. The new feature adds more advanced editing capabilities

to provide a richer GUI experience to a user. Visual editing features, such as color

differences between keywords, comments, and message patterns, aid in easier and

more productive database development. Predefined Event Report templates are

provided for auto-insertion, which reduces AMS scripting time and manual errors.

SP-OPERATION Level 15.0

2–40 7831 0349–046

Save and Cancel options for Topology window

Provides extension of Save and Cancel capabilities to Custom Topology window.


Users get refined user interface with convenience because the Custom Topology

window now has control over the save or discard changes.


With this enhancement, users have an option to save or discard any changes in the

Topology window itself without the need to navigate to the parent window.

Time scheduler for Alert Policy

Provides flexible time scheduling capabilities during which execution of the Alert

Policy action can be disabled.


The scheduling feature is provided in the Alert Policy for the administrator to skip the

action execution for the specified alert types during a specified time frame.


The existing functionality supports enabling the Alert Policy and triggering the

specified actions, such as sending e-mails. With the new scheduling feature, the

administrator can skip the action execution for the specified alert type during a given

time frame.

Silent installation of WRM and ULRM agents

Provides remote installation of WRM and ULRM agents on multiple systems.


This feature empowers administrators to install the WRM and ULRM agent software

from server to multiple remote systems in one pace.


The existing functionality in Operation Sentinel supports manual copy and installation

of WRM and ULRM agents. This manual procedure is overcome by the automated

installation provided in this feature. This new wizard enhancement is provided to avert

the manual operation and allow the administrator to trigger the silent installation

process of WRM and ULRM agents.

Autoaction Database Scanner

Aims to detect the changed message patterns with in the CP-AMS databases.


This feature aims to detect message pattern changes in the databases. It currently

serves the purpose of catering to the changes pertaining to the DSTA feature.

SP-OPERATION Level 15.0

7831 0349–046 2–41


The CP-AMS databases of Operations Sentinel are impacted by changes in the

timestamps and other changes in key-in outputs by EXEC and other products that

generate console messages. The Daylight Saving Time Adapt (DSTA) feature released

in ClearPath OS 2200 15.0 release included many such changes. The Autoaction

Database Scanner is implemented for the user to easily identify the non-DSTA

message patterns and provide recommendations for the DSTA-compatible patterns.

This feature can compare a customer's CP-AMS database with a list of the changed

DSTA messages, flag potential conflicts, and display recommended changes.

SNMP V2 support

Provides extended support to SNMP v2.


With this feature, Operations Sentinel server can receive the SNMP v2 trap as alert

event reports.


Earlier versions of Operations Sentinel support SNMP v1 only, which limits the usage

of trap service. The extended support to SNMP v2 increases use of Operations

Sentinel Trap services to interact with devices that support both versions of the

protocol.

Qualification of ULRM agent on RedHat v5 and v6.

RedHat v4 is going end of life soon hence the ULRM agent for RedHat systems (32 bit

version) has been upgraded to support the next levels of RedHat versions.

Support extension for SAIL-Based System configuration.

Provides enhancements to the "New SAIL-based System wizard" for supporting

Dorado 4200 and Dorado 4300/6300 system configurations.


This enhancement provides extension for Operations Sentinel's support for auto

configuration for Dorado 4200 and Dorado 4300/6300 system configurations through

the New SAIL-based System wizard.


Currently the "New SAIL-based System" wizard can be used for auto-configuring of the

objects in Operations Sentinel for Dorado 4100 system configuration only. For any

other Dorado configurations like for Dorado 4200 or Dorado 4300/6300 the

Administrator is required to manually edit the values in this wizard and also has to

follow a lengthy manual procedure for creation of the objects in Operations Sentinel.

SP-OPERATION Level 15.0CP

2–42 7831 0349–046

This enhancement concentrates on extending Operations Sentinel's support for auto


the New SAIL-based System wizard. Thus it eliminates the overhead incurred with the

manual intervention to create the particular Dorado system configuration. It enables

the administrator to choose the type of Dorado system which needs to be configured

and based on the choice made the respective wizard will open up which will be

prefilled with the values. Administrator can make further choices to complete the

required setup and the respective objects will be automatically created in Operations

Sentinel.

2.26. SP-OPERATION Level 15.0CP

The Operations Sentinel level 15.0 product is a feature release. This feature set applies

to Operations Sentinel Basic Edition, Department Edition, and Enterprise Edition.

Feature Content:

The following is an overview of each feature:

ADBM Editor enhancement

Provides enhanced editing capabilities into the Autoaction Database Manager.


This feature provides more powerful visual editing features to ADBM editor in

Operations Sentinel, such as

• Keyword/Syntax coloring

• Ability to insert Event Report templates, such as AC, CO, and so on

• Ability to split the editor into two separate panes for the same source file


The earlier version of ADBM editor is a simple text editor that does not support any

advanced editing capabilities. The new feature adds more advanced editing capabilities

to provide a richer GUI experience to a user. Visual editing features, such as color

differences between keywords, comments, and message patterns, aid in easier and

more productive database development. Predefined Event Report templates are

provided for auto-insertion, which reduces AMS scripting time and manual errors.

Save and Cancel options for Topology window

Provides extension of Save and Cancel capabilities to Custom Topology window.


Users get refined user interface with convenience because the Custom Topology

window now has control over the save or discard changes.


7831 0349–046 2–43


With this enhancement, users have an option to save or discard any changes in the

Topology window itself without the need to navigate to the parent window.

Time scheduler for Alert Policy

Provides flexible time scheduling capabilities during which execution of the Alert

Policy action can be disabled.


The scheduling feature is provided in the Alert Policy for the administrator to skip the

action execution for the specified alert types during a specified time frame.


The existing functionality supports enabling the Alert Policy and triggering the

specified actions, such as sending e-mails. With the new scheduling feature, the

administrator can skip the action execution for the specified alert type during a given

time frame.

Silent installation of WRM and ULRM agents

Provides remote installation of WRM and ULRM agents on multiple systems.


This feature empowers administrators to install the WRM and ULRM agent software

from server to multiple remote systems in one pace.


The existing functionality in Operation Sentinel supports manual copy and installation

of WRM and ULRM agents. This manual procedure is overcome by the automated

installation provided in this feature. This new wizard enhancement is provided to avert

the manual operation and allow the administrator to trigger the silent installation

process of WRM and ULRM agents.

Autoaction Database Scanner

Aims to detect the changed message patterns with in the CP-AMS databases.


This feature aims to detect message pattern changes in the databases. It currently

serves the purpose of catering to the changes pertaining to the DSTA feature.


2–44 7831 0349–046


The CP-AMS databases of Operations Sentinel are impacted by changes in the

timestamps and other changes in key-in outputs by EXEC and other products that

generate console messages. The Daylight Saving Time Adapt (DSTA) feature released

in ClearPath OS 2200 15.0 release included many such changes. The Autoaction

Database Scanner is implemented for the user to easily identify the non-DSTA

message patterns and provide recommendations for the DSTA-compatible patterns.

This feature can compare a customer's CP-AMS database with a list of the changed

DSTA messages, flag potential conflicts, and display recommended changes.

SNMP V2 support

Provides extended support to SNMP v2.


With this feature, Operations Sentinel can receive the SNMP v2 trap as alert event

reports.


Earlier versions of Operations Sentinel support SNMP v1 only, which limits the usage

of trap service. The extended support to SNMP v2 increases use of Operations

Sentinel Trap services to interact with devices that support both versions of the

protocol.

Qualification of ULRM agent on RedHat v5 and v6.

RedHat v4 is going end of life soon hence the ULRM agent for RedHat systems (32 bit

version) has been upgraded to support the next levels of RedHat versions.

Support extension for SAIL-Based System configuration.

Provides enhancements to the "New SAIL-based System wizard" for supporting

Dorado 4200 and Dorado 4300/6300 system configurations.


This enhancement provides extension for Operations Sentinel's support for auto


the New SAIL-based System wizard.


Currently the "New SAIL-based System" wizard can be used for auto-configuring of the

objects in Operations Sentinel for Dorado 4100 system configuration only. For any

other Dorado configurations like for Dorado 4200 or Dorado 4300/6300 the

Administrator is required to manually edit the values in this wizard and also has to

follow a lengthy manual procedure for creation of the objects in Operations Sentinel.

SYSLIB Level 77R1

7831 0349–046 2–45

This enhancement concentrates on extending Operations Sentinel's support for auto


the New SAIL-based System wizard. Thus it eliminates the overhead incurred with the

manual intervention to create the particular Dorado system configuration. It enables

the administrator to choose the type of Dorado system which needs to be configured

and based on the choice made the respective wizard will open up which will be

prefilled with the values. Administrator can make further choices to complete the

required setup and the respective objects will be automatically created in Operations

Sentinel.

2.27. SYSLIB Level 77R1

Support Modified-SWTIME Format as a TDATE$ Replacement


The UTC-based, one-word Modified-SWTIME format timestamp was added in

ClearPath OS 2200 release 15.0 to provide a potential replacement for the one-word

TDATE$ format timestamp, which overflows on 2028-01-01. The SYSLIB AEDIT$,

EDIT$, SFDT$, and TIMECONV$ routines are enhanced to support Modified-SWTIME

timestamps with little or no impact to users that call these routines to perform date

and time processing.


The following new features are available in the AEDIT$, EDIT$, SFDT$, and

TIMECONV$ routines:

• When the routines expect a TDATE$ format timestamp, a Modified-SWTIME

format can be substituted and is correctly processed with no code changes. A

recollection (@MAP) with SYSLIB 77R1 is required for callers that access the

SYSLIB relocatable elements. No change of any kind is required for callers that

access the SYSLIB common banks. There are exceptions to this automatic

conversion capability, described below. If desired, you can inhibit the automatic

conversion by setting an option flag in the packet used by the routine you are

calling.

• Conversion of the UTC-based Modified-SWTIME timestamp to local time requires

additional time configuration information. The routines' default action is to retrieve

this information with ER TIMECONFIG$. As an alternative, you can provide

alternate time configuration information for the routines to use. This improves

performance, allows conversions to the local time for any desired locality, and

allows time to be expressed in UTC time.

• In addition to automatic conversion of Modified-SWTIME timestamps, you can

explicitly specify in routine packets that a Modified-SWTIME format timestamp is

to be processed. The routines support timestamps in TDATE$, DWTIME$,

SYS$TIME (TIMEB), Modified-SWTIME, and three-word binary formats.

• In the TIMECONV$ routine, Modified-SWTIME timestamps can be converted to all

supported date and time formats. Only the UTC-based SYS$TIME and

Modified-SWTIME timestamp formats can be converted to Modified-SWTIME

format.

SYSLIB Level 77R1

2–46 7831 0349–046

• When using the AESFDT$ and SFDT$ routines to convert a TDATE$ timestamp to

time format 3 (hhmm:ss.fff) or time format 4 (hh:mm:ss[.fffffffff]) a separate TIME$

value was previously required. This value replaced the time portion of the TDATE$

timestamp. This often made using these time formats inconvenient. You can now

provide a TIME$ value of -2 (negative 2) to specify that the TDATE$ time portion

should be used with time formats 3 and 4 and that the fractional seconds should

be zeroes.

Note that the SYSLIB ID$ routine does not support Modified-SWTIME timestamps. ID$

continues to support only TDATE$ timestamps.

Automatic Conversion Exceptions

The following are exceptions to the automatic conversion of Modified-SWTIME values

described in the first bullet item under Detailed Description:

• The AEDIT$ AESFDT$ routine cannot automatically convert Modified-SWTIME

timestamps when the obsolete A$EPKTSFDT packet is used and when a version 1

A$EDITPKT is used.

• The SFDT$ routine cannot automatically convert Modified-SWTIME timestamps

when a version 1 S$FDTPKT is used.

In these cases, an attempt to convert a Modified-SWTIME value results in the retrieval

and formatting of the current date and time. If you want to use automatic conversion,

you must update your programs to generate the current packets (for AESFDT$, the

version 2 A$EDITPKT packet; for SFDT$, the version 2 S$FDTPKT packet).

Provide New Procedures That Use the New Collector-defined Symbols


There are three new procedures that provide a convenient method for generating

complete timestamps based on the six new Collector-defined symbols. These

symbols indicate when an absolute element was created by Collector (MAP) level

33R2.


The following new procedures can be used to generate standard format timestamps

that indicate when an absolute element was created:

• The S$YSTIME procedure generates a four-word SYS$TIME (TIMEB) format

timestamp, based on the new Collector-defined symbols SYSTIME1$, SYSTIME2$,

SYSTIME3$, and SYSTIME4$. A TIMEB format timestamp is in UTC time and

contains the seasonal and time zone offsets necessary to convert it to local time.

A TIMEB format timestamp also contains the time zone mnemonic.

• The D$WTIMEUTC procedure generates a two-word DWTIME$ format timestamp

in UTC time, based on the new Collector-defined symbols SYSTIME1$ and

SYSTIME2$.

• The D$WTIME procedure generates a two-word DWTIME$ format timestamp in

local time, based on the new Collector-defined symbols DWTIME1$ and

DWTIME2$.

TeamQuest Products

7831 0349–046 2–47

2.28. TeamQuest Products

2.28.1. TeamQuest BASELINE® Level 7R5A

TQSYS enhanced log entry count summary


The TeamQuest Baseline TQSYS probe reports the number of log entry records read

and log entry records processed for each system logfile processed, as well as the

total number of records read and processed for all system logfiles. These counts are

summarized in the file "tqsys$prt " and are written when the TQSYS probe is done

executing. Providing the additional reporting on an individual logfile basis is informative

and can be useful for debugging purposes.


The TeamQuest Baseline TQSYS probe currently counts and reports the total number

of log entries read and number of log entries processed and writes that information to

the summary file "tqsys$prt" when the TQSYS probe finishes. The count of log entries

read and log entries processed are now reported for each system logfile processed

by the TQSYS probe, as well as the total log entries read and processed for all system

logfiles.

Route @@CONS Keyin Response back to Demand User


TeamQuest Baseline sends a response back to a demand user’s run-id when a keyin is

entered via @@CONS to terminate a probe or check a status. The keyin

acknowledgement back to the user’s run-id provides an indication to the user that the

keyin was requested. This is in addition to the keyin request being displayed on the

system console and recorded in the system logfile.

Specify COMAPI Mode During TQINIT


During the TQINIT process that is used to setup and configure TeamQuest Baseline,

the user is queried for the COMAPI mode that is installed on the system so the TQTCP

run will communicate correctly with the installed COMAPI. The COMAPI default is

mode A, however, modes B through Z may be selected.


During the TQINIT process that is used to setup and configure TeamQuest Baseline,

the user is queried for the COMAPI mode (A through Z) that is installed on the system

so the TQTCP run will communicate correctly with the installed COMAPI. When the

LINK of TQTCP is performed, the correct COMAPI library is used that matches the

mode of COMAPI in use. A TQTCP ZOOM that is linked with the incorrect COMAPI

library will not function correctly.

TeamQuest Products

2–48 7831 0349–046

2.28.2. TeamQuest® D-Fragger Level 4R2

Support for the TDATE$ Remediation adapt for the Master File Directory

2.28.3. TeamQuest® LA Level 8R2

TDATE$ Remediation


There is a need to identify which programs are executing ER TDATE$ and ER DATE$,

so that they can be updated. LA is updated to display an easy to read report with this

information.


A new section, SPECIAL_COUNTERS, is being added to the Program Report that

displays the programs that have executed an ER TDATE$ or ER DATE$.

This section will display the:

• Program name

• Runid

• Program start and end times

• Number of ER TDATE$ executed

• Number of ER DATE$ executed

• Number of RMD emulations

• Number of BMTC emulations

Support of updated log entries

For all log entries modified or added to this release, LA will be updated to process the

detail as necessary.

2.28.4. TeamQuest Online® Level 7R5A



TeamQuest Online sends a response back to a demand user’s run-id when a keyin is





TeamQuest Products

7831 0349–046 2–49

Specify COMAPI Mode During TQINIT


During the TQINIT process that is used to setup and configure TeamQuest Online, the

user is queried for the COMAPI mode that is installed on the system so the TQTCP run

will communicate correctly with the installed COMAPI. The COMAPI default is mode A,

however, modes B through Z may be selected.


During the TQINIT process that is used to setup and configure TeamQuest Online, the

user is queried for the COMAPI mode (A thru Z) that is installed on the system so the

TQTCP run will communicate correctly with the installed COMAPI. When the LINK of

TQTCP is performed, the correct COMAPI library is used that matches the mode of

COMAPI in use. A TQTCP ZOOM that is linked with the incorrect COMAPI library will

not function correctly.

2.28.5. TeamQuest® PAR Level 9R3

PAR-L processor is directly callable


The alternate, large system configuration, PAR-L processor is installed to be directly

callable (@PAR-L). There will no longer be the requirement to execute this processor

from the install file (@SYS$LIB$*PAR.PAR/L).

2.28.6. TeamQuest® Probes Level 7R5A



TeamQuest Probes sends a response back to a demand user’s run-id when keyin is





2.28.7. TeamQuest® RemD-Fragger Level 4R2


2.28.8. TeamQuest® SAUTILITIES Level 8R1A


UC Level 10R5

2–50 7831 0349–046

2.28.9. TeamQuest® SIMAN Level 7R2

Support for User Authentication Module 19


TeamQuest Site Management Complex (SIMAN) supports restricting user-id login

constraints based on time of day. This was introduced in User Authentication Level

4R4 as part of Configured Password Profiles and Authentication Module 19.


User-ids can be updated with TeamQuest SIMAN to restrict login to a specific time of

day, such as 8:00 - 5:00 Monday through Friday.

Support for the TDATE$ Remediation adapt for the ACCOUNT file

2.29. UC Level 10R5

This release contains code supporting the RDMS feature "Comparison operator

augmentation."

Comparison operator augmentation (RDMS)


Adding two "synonyms" for the inequality operator (<>) eases the conversion from

other implementations and provides the C programmer more similarity between SQL

and C.


Testing for inequality in an SQL statement is performed by the operator ^= or != in

addition to the existing <>.

2.30. UCOB Level 12R2

Insert non-standard features to allow for easier migration of IBM MVS COBOL applications to OS 2200.


These features reduce the amount of modifications required to transfer from IBM

COBOL applications to OS2200 UCOB. Programs utilizing IBM extensions benefit from

increased compatibility.


The following new capabilities are added:

• Allow COMP-3/ COMPUTATIONAL-3

An enhancement to the COMP-BIN keyword option allows data-items to be

declared as USAGE COMPUTATIONAL-3 or COMP-3. Internally, the numeric data

items are allocated as PACKED-DECIMAL.

UREP Level 16R1

7831 0349–046 2–51

• Allow COMP-4/ COMPUTATIONAL-4

New data USAGE COMP-4 and COMPUTATIONAL-4 are now allowed. Numeric

data-items declared as USAGE COMPUTATIONAL-4 or COMP-4 are treated as

USAGE BINARY.

• POINTER Handling

This feature provides a two word byte addressable pointer with enhancements to

the SET statement and LINKAGE SECTION to accommodate IBM OS/360

compatibility. This feature provides Based and dynamic storage capabilities to the

COBOL user.

• Additional Keywords

NULL and NULLS are included into the UCOB syntax as unreserved keywords.

They are treated as a two words of binary zeroes for the VALUE clause, sending

field of a SET statement, and conditional expressions.

ADDRESS is also an unreserved keyword. It can be used to obtain a two word

pointer address of a data-item within a SET statement.

• GOBACK Statement

This feature implements a new COBOL statement. The GOBACK statement

functions like the EXIT PROGRAM statement when it is coded as part of a called

program. It functions like the STOP RUN statement when it is coded in a main

program.

• Nested COPY PROCs

A nested COPY procedure is a PROC that contains one or more COPY statements.

Nested COPY PROCs allow for templating common structures and import

additional source code into a program.

• Allow Alternate Host Variable Name (:A.B)

UCOB now allows embedded SQL statements to contain a host variable group

name followed by a period and a data-name. The new name (A.B) is equivalent to

B of A.

2.31. UREP Level 16R1

RDMS-JDBC Simplified Installation


The UREP install creates the RDMS-JDBC metadata catalog. The RDMS-JDBC

customer no longer has to manually create it.


This feature updates the UREP Mode A (migration) and Mode B (initialization) installs to

support the RDMS-JDBC Simplified Installation feature. The installs create the

RDMS-JDBC metadata catalog (JDBC$CATALOG2).

URTS Level 13R4

2–52 7831 0349–046

RDMS Catalog improvements


The performance of the RDMS Catalog views is optimized.


This feature improves the performance of the RDMS Catalog views by updating the

view syntax and updating the RDMS code to recognize the views. New RDMS

Catalog views are created which are variations of existing views with improved

performance.

2.32. URTS Level 13R4

Support for the TDATE$ Remediation adapt.

2.33. URU-OS2200 Level 8.0

This release contains stability updates and new functionality.

The new functionality is described as follows:

Automatic Periodic Interim Usage Reports


Provide an improved means for customers to track metered system usage. This

feature enhances URU-OS2200 by implementing customer-configured automatic

periodic MIPs usage reports. Through the new feature suggestion (NFS) process, the

functionality to allow for the automatic creation of interim reports based on a

user-specified schedule (daily, weekly, or monthly) has been added. (See NFS UCFs

94344943 and 80886535.)

These user-specified periodic interim reports could be used for several purposes

including long-term usage tracking and charting, as well as the monitoring of

day-to-day MIPs usage.


This feature adds a URU-wide selection (Yes/No) for Periodic Interim Usage Reports,

and includes the capability of scheduling these reports for a selected number of

contracts. This feature also includes the capability of sending the automatically

generated interim reports through email. The email settings for the feature are also

URU-wide. This feature adds new tabs to both the Configuration and the Service

Management windows of URU for configuring and controlling this new feature.

WEBTS Level 6R1

7831 0349–046 2–53

The stability updates are as follows:

Read errors on COD and system log crossing from release 14.0 to release 15.0

This release resolves problems when reading audit trails across a transition from

pre-release 15.0 to release 15.0. The following error may be encountered if the

pre-release 15.0 audit trail terminates without a close record:

*ERROR* 7009 AT <num> Buffer changed after record <rec> of TBSN <tbsn>

IRU's FSAH, which included in the URU, is updated to handle the transition between

the pre-release 15.0 audit trail format and the release 15.0 audit trail format.

Automatic missing data harvests generated after a database split when there is no missing data.

The URU service is updated to look at all databases in order to determine missing

data, instead of just the primary database.

Contractual reports not generated after four day waiting period in the presence of missing data if the URU service is restarted within the time period.

The URU service is updated to maintain missing data information between URU

service restarts.

Missing data detection can produces a false positive in the presence of alternate databases.

The URU service is updated to consider all databases when confirming possible

missing data holes.

2.34. WEBTS Level 6R1

Web Transaction Server 6R1 product is a feature release and includes fixes to

reported problems.

Feature Content:

Supporting SSL/TLS communication between WebTS and WebTSA


This feature facilitates customers to use encrypted WebTS-WebTSA connection with

the SSL/TLS security protocol.

WEBTS Level 6R1

2–54 7831 0349–046


Prior to WebTS level 6R1, the WebTS-WEBTSA connection was CIPHER encrypted,

based on its availability on the OS 2200 system, where WebTS runs. If CIPHER was not

available, the communication took place in plain text that often contained confidential

information, such as user ID, password, and so on, which was susceptible to attacks.

Additionally, the key used in CIPHER encryption was equally susceptible to such

attacks as it was communicated over the network before the actual encryption took

place. Now, customers can opt for the SSL/TLS security protocol through the initial

host connection form that appears when launching WebTSA. This in turn will enable

them to have the encrypted WebTS-WebTSA connection available at all times for

communication without any security risks. However, the customers may continue to

use the existing security protocol without SSL/TLS.

Supporting use of signed applets with WebTS JavaClient for Web-enabled DPS transactions


This feature allows customers to use JavaClient conforming to the latest Java security

restrictions by using signed applets for Web-enabled DPS transactions. However, to

adhere to the security restrictions related to this feature, the customers must follow

additional procedures involved in the web-enabling process.


Signed applets allow customers to ensure secure Web-enabled DPS transactions.

With WebTS levels prior to 6R1, warning messages were displayed to the customers

for unsigned applets. Starting with JRE7u40, these warning messages could not be

hidden and appeared every time for consent before proceeding. With this new

feature, such warning messages are not displayed as the applets would be signed.

Customers have the choice of continuing with the existing procedure of Web enabling

a DPS transaction even without the use of signed applets but with the existing

security risk. However, with JRE7u51, customers must use signed applets as the

unsigned applets are blocked with the recommended Java security settings of

JRE7u51.

DPS level 6R6 is enhanced to support this feature. Therefore, customers must install

the latest version of DPS level 6R6 to avail the benefits of this feature. Customers will

be able to use both the signed applets (with procedural changes) and unsigned applets

(with existing procedures) even with the older levels of WebTS and new DPS level

6R6, without any problem. To facilitate such customers, who are still using older

WebTS levels but have upgraded the DPS level to 6R6 for using signed applets, a PLE

would be added for the document for older WebTS levels specifying the procedural

changes or requirements. Refer to Web Enabler for Display Processing System

User's Guide (7851 5509) for more information.

XRLOAD Level 6R1E

7831 0349–046 2–55

2.35. XRLOAD Level 6R1E

Note: XRLOAD 6R1E does not support the two new Expanded Timestamp formats

introduced in RDMS 20R1.

• The TIME format hh.mm.ss(.ffffff) (not supported)

• The TIMESTAMP format yyyy-mm-dd-hh.mm.ss(.ffffff) (not supported)

XRLOAD Level 6R1E

2–56 7831 0349–046

7831 0349–046 3–1

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.


• Unisys supports crossbooting between the currently supported releases.

Supported Crossboot Scenarios

Migrating from ClearPath

OS 2200 Release

Migrating to ClearPath

OS 2200 Release

14.0 15.0

14.0 16.0

15.0 16.0

Note: Unisys does not provide code to support crossbooting between 13.x

and the supported releases.

• Migrating to Release 16.0

Unisys supports migration to ClearPath OS 2200 release 16.0 from both release

14.0 and release 15.0. Sites already running release 15.0 have already completed all

of the migration steps that were required as part of the Daylight Saving Time

Adapt. Sites moving directly from release 14.0 to release 16.0 will have more

migration considerations than sites already running release 15.0.

If you plan to migrate directly to ClearPath OS 2200 release 16.0 from release 14.0,

bypassing release 15.0, beginning with a complete base of release 14.0 is critical.

Starting from a stable 14.0 base will reduce the risk of unexpected problems

during the migration to release 16.0 and DSTA.

Considerations

3–2 7831 0349–046

If you have not already done it, you will need to upgrade your OS 2200 systems to

release 14.0 before starting the upgrade to the ClearPath OS 2200 16.0 release.

Release 14.0 includes many products that are enhanced to support the Daylight

Saving Time Adapt features aiding the migration process. If you move directly

from release 14.0 to release 16.0, release 16.0 will represent your first exposure to

the Daylight Saving Time Adapt.

Unisys is providing code to support crossbooting between release 14.0 and 16.0

and is thoroughly testing the crossboot scenarios between the two releases.

Starting from a stable 14.0 base will reduce the risk of unexpected problems

during the migration to release 16.0 and DSTA.

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

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

OS-2200-SBR level 16.0.

• Migration Planning Documentation

The migration steps to move to the ClearPath OS 2200 16.0 release vary

depending on the release that you are migrating from. If you are migrating from

the release 15.0, you have already completed the migration tasks required by the

changes introduced with the release 15.0 DSTA feature. If you are migrating from

release 14.0, you will need to address the DSTA changes, when moving to release

16.0. A new Time document Time Considerations for ClearPath OS 2200 Systems

is introduced in release 16.0. This new document details time concepts and details

the changes that Unisys is planning as we work toward the TDATE$ Remediation

2028.

− ClearPath OS 2200 Release 15.0 and Daylight Saving Time Adapt

Frequently Asked Questions (8222 3959)

− Mandatory Migration Actions for ClearPath OS 2200 Release 15.0 and

Higher (8222 3777)

− Time Considerations for ClearPath OS 2200 Systems (8230 6671)

• CARTLIB Change

Beginning with the ClearPath OS 2200 16.0 release the Exec CARTLIB feature is no

longer delivered as a separate SPEF. CARTLIB is now incorporated in the standard

Exec.

• CryptoLib

Starting with ClearPath OS 2200 release 16.0, only the NOTFIPS mode is installed

when using the CP-FLD tape. Previous ClearPath OS 2200 releases have installed

mode FIPS from the CP-FLD tape. If FIPS certification is required, you must install

mode FIPS on your system using the CryptoLib release tape.

Considerations

7831 0349–046 3–3

• Secure by Default – Optionally disallow @@PASSWD

The default for the new Exec configuration parameter

enable_passwd_control_statement is FALSE, which disallows the use of

@@PASSWD on Fundamental Security and Security Level 1 and 2 systems. To

change passwords on a system with this parameter FALSE, either change the

password at login time, use the @PASSWD$ processor supplied with User

Authentication, or use system administration software (Security Client, Apex, or

TeamQuest SIMAN) to change the password.

• Secure by Default – Configure Delayed Sign On Solicitation to meet PCI DSS

guidelines

If you use the Delayed Sign-on Solicitation method of hacker frustration, the

terminal will be disabled after 8 unsuccessful login attempt or

max_sign_on_attempts unsuccessful login attempts, whichever is smaller. Since

the default for max_sign_on_attempts is 5, leaving the default at 5 will result in

hackers or users having the terminal disabled sooner than in past releases.

If you had previously considered using Delayed Sign-on Solicitation but avoided it

because it could not meet the PCI DSS requirement of shutting out hackers after

no more than 6 unsuccessful login attempts, Delayed Sign-on Solicitation is now a

viable choice when combined with a value of max_sign_on_attempts that is 6 or

lower.

• SYSLIB and SLIB

In the ClearPath OS 2200 16.0 release, both SYSLIB 77R1 and SLIB 2R1 introduce

the new Support Modified-SWTIME Format as a TDATE$ Replacement feature.

Several release 16.0 products are using this new feature to perform date and time

processing. The migration sequences in Section 7 are updated to install these two

products in the initial migration steps, addressing this compatibility requirement.

• TDATE$ Remediation

Several new features are introduced in the release 16.0 to further Unisys plans to

remove the TDATE$ timestamps. The features in release 16.0 concern the MFD,

the Summary Accounting file and Freespace. These features implement the use of

Modified-SWTIME in these areas. They provide configuration parameters to

specify use of Modified-SWTIME format timestamps in place of TDATE$ for new

timestamps. Only TDATE$ use is allowed in this release. A future release will

allow use of Modified-SWTIME. The values of these configuration parameters may

be retrieved and used by programs that need this information when adapting to

the new timestamp format.

Unisys is encouraging our customers to look at their tools, programs and

applications, and to start adapting to the new timestamp format as well as

replacing TDATE$ format timestamp generation wherever practical.

• Software Logical Package Consideration

The product packaging has changed. SLIB is added to the CP-FLD First Load tape.

Considerations

3–4 7831 0349–046

• New EXEC configuration parameters are introduced in this release. See section

4.2.1 for additional details.


• Migration Planning Documentation

To help you prepare for your upgrade, Unisys is providing two planning

documents in the documentation library of the ClearPath OS 2200 15.0 release. The

ClearPath OS 2200 Release 15.0 and Daylight Saving Time Adapt Frequently

Asked Questions (8222 3959) document provides answers to frequently asked

questions about the 15.0 release and DSTA. The Mandatory Migration Actions for

ClearPath OS 2200 Release 15.0 and Higher (8222 3777), explains the adapt at a

high level, provides detailed information about changes that may be required in

your application code, and provides information on reference documentation for

the DSTA feature.

• CIFS

The security requirements for the User-Id that owns the CIFS subsystem file have

changed. Beginning with the ClearPath OS 2200 release 15.0, that User-Id should

be given the SSLOGER privilege.

The SMB Message Signing capability is not functional for clients using Windows

network credentials to log into OS 2200 through ASIS/NTSI. To work around the

issue, either clients must present native OS 2200 credentials, or SMB signing must

be inhibited by setting the CIFS background run’s CIFS$SIGNSMB environment

variable to DISABLED.

• EXEC I/O Legacy Removal

ClearPath OS 2200 release 15.0 has removed Exec I/O Legacy code, elements,

features and Executive Requests (ERs) which are obsolete and will no longer

function with the new SCIOP and IOM I/O architectures. Only Dorado-700/800 and

Dorado-4000/4100/4200/4300/6300 systems are supported with these newer I/O

architectures.

Four Exec features, three Executive Requests (ERs) and two Exec Boot files have

been removed along with the affected obsolete equipment types including

Channel Modules, Control Units and device types. See section 4.1, “General Exec

Considerations” for more details on this I/O Legacy removal and the migration

issues and considerations.

Considerations

7831 0349–046 3–5

• EXEC Multi-Host File Sharing (MHFS) environment changes

The ClearPath OS 2200 15.0 release increases the number of hosts that can

participate in a Multi-Host File Sharing (MHFS) environment from four to six. While

this release supports a maximum of a six host environment, the implementation of

this change created an infrastructure that can support up to 12 hosts. Thus, in

some console messages, ERs (Executive requests), and data structure

descriptions, references to 12 hosts will be seen.

• Exec Secure by Default Security Configuration parameter changes

The default values for several security-related Exec configuration parameters have

changed with the Secure by Default feature. If you currently use the default values

for these parameters and continue to use the new default values, your users will

be affected by the changes. The previous default forced passwords to expire after

7300 days. The new default is 90 days. This change may force many of your users

to change their passwords when the Exec 49R1 is initially installed. The need for

more frequent password changes could also affect certain batch background runs

if they rely on the use of a user-ID/password combination. The default values for

minimum and maximum password character length have also changed and this

may be new for your users. The default number of maximum sign on attempts is

now set to 5. If you choose to use the new default configuration parameters, you

may want to warn your users of the changes and prepare them for the actions

they may be required to take. If you need to continue using your old security

parameter settings, you must ensure that your Exec configuration specifically

includes these parameters and their desired value. If these parameters are not

specified in your EXEC configuration, the new default values will now be used.

See section 4.1 for additional information.

The following Exec configuration parameter default values are updated:

Static Name Dynamic Name Previous

Default

Release

15.0 Default

TSS TSS_CONTROL FALSE TRUE

MAXPASSDAY DEFAULT_MAX_DAYS_PASSWORD 7300 90

MINPASSDAY DEFAULT_MIN_DAYS_PASSWORD 0 1

MINPASSLEN MIN_PASSWORD_LENGTH 1 8

MAXPASSLEN MAX_PASSWORD_LENGTH 6 18

MAXATMP MAX_SIGN_ON_ATTEMPTS 63 5

Considerations

3–6 7831 0349–046

• FLEX

For sites using Apex and Configured Password Profiles, the ASIS subsystem

owner User-Id (-ASIS-) requires the SSREADEXEC privilege. Beginning with the

ClearPath OS 2200 release 15.0, that User-Id should be given the SSREADEXEC

privilege.

• Discontinued Products

Beginning with the ClearPath OS 2200 15.0 release the following products and

Exec features are no longer included in the ClearPath OS 2200 release.

− JVM

− CARTIS

− FBCIS

− PAEXEC (PAEXEC is no longer orderable or delivered)

− SCSITIS

− SINCH


The product packaging has changed.

− Apex 1.0 is new in the release and included on package CP05.

− JPJVM and WMQ2200 were previously delivered as stand-alone unkeyed

products. The JPJVM 7.2 and WMQ2200 7R0B products are now keyed,

and included on package CP12.

− Eportal-2200 2.1 was delivered as a stand-alone keyed product. It is now

also included on package CP12.

New CP12 package format:

CP12

EPORTAL-2200 2.1

IC2200 1R4A

JPJVM 7.2

WMQ2200 7R0B

See Appendix C for the complete packaging information.

Considerations

7831 0349–046 3–7


• The ClearPath OS 2200 14.0 release is a critical stepping stone to future releases

that will contain the Daylight Saving Time Adapt (DSTA). You will need to upgrade

your OS 2200 systems to release 14.0, including the release 14.0 versions of IRU

and UDS, before starting the upgrade to DSTA in the ClearPath OS 2200 15.0

release.

Unisys is providing code to support crossbooting between 14.0 and 15.0, and is

thoroughly testing the crossboot scenarios between 14.0 and 15.0. Starting from a

stable 14.0 base will reduce the risk of unexpected problems during the migration

to 15.0 and DSTA.

Unisys does not plan to provide code to support crossbooting between 13.x and

15.0 releases.

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

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

OS-2200-SBR level 14.0.

• Discontinued Products

Beginning with ClearPath OS 2200 14.0 release the following products are no

longer included in the ClearPath OS 2200 release

− MQS2200

− JBOSS-2200 4.3A (JBOSS-2200 6.0 with the JProcessor is supported)

− JVM (JVM will continue to be shipped with ClearPath OS 2200 release 14.0,

although it is discontinued).


The Dorado 400 is not supported with the ClearPath OS 2200 14.0 release. The

logical package CP-FLD400 fast-load tape is no longer included in the release

packaging.

Considerations

3–8 7831 0349–046

Following is the new DVD packaging structure:

CPHD-01 14.0 CPHD-04 14.0

CP-EXEC-MSTR CP08

CP-EXEC-SYM CP09

CP-FLD CP10

CP-OE1A CP11

CP-OE1B CP12

CP-OE2 CPHD-05 14.0

CP-SPF CP13

CP-TRN CP14

CPHD-02 14.0 CP15

CP-COMMSUITE CP16

CP-OPE CP17

CPHD-03 14.0 CP18

CP01

CP02

CP03

CP04

CP05

CP06

CP07

Discontinued Products

7831 0349–046 3–9

3.2. Discontinued Products

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

additional information describing support for OS 2200 systems.

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

be ordered as part of ClearPath OS 2200 release 16.0. The Support Discontinued In

column identifies the software release in which the product or feature was

discontinued.

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


Product or Feature Support Discontinued In Replaced By

JVM ClearPath OS 2200 release 14.0 JPJVM with JProcessor

JBOSS-2200 4.3A ClearPath OS 2200 release 14.0 JBOSS-2200 6.0 with JProcessor

MQS2200 ClearPath OS 2200 release 14.0 WMQ2200 with QProcessor

CARTIS ClearPath OS 2200 release 15.0

FBCIS ClearPath OS 2200 release 15.0

PAEXEC ClearPath OS 2200 release 15.0 Note: PAEXEC is no longer

orderable or delivered with the

ClearPath OS 2200 15.0 release.

SCSITIS ClearPath OS 2200 release 15.0 DVD, OST5136, CTS5236,

T9840C and T9940B tape

equipment no longer require the

SCSITIS feature.

SINCH ClearPath OS 2200 release 15.0

PHP-CLEARPATH ClearPath OS 2200 release 16.0 PHP-CLEARPATH is no longer

available with OS 2200 release

16.0.

CARTLIB ClearPath OS 2200 release 16.0 Beginning with ClearPath

OS 2200 16.0 CARTLIB is incorporated in the standard

Exec.

Future Considerations

3–10 7831 0349–046

3.3. Future Considerations

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

customers.

3.3.1. MCB Rewritten in Extended Mode

In a future release, the MCB will be totally rewritten in Extended Mode (EM) where

MCB is re-implemented as a protected fixed-gate shared subsystem (FGSS) with

source code written mostly in UC. This new level of MCB will greatly expand the

capacity of MCB’s resources for transaction access and message creation. It will relax

the Traditional Programming Environment (TPE) Basic Mode application program

addressing constraints imposed by previous levels of MCB. Most memory needed by

MCB will be acquired/expanded/contracted at runtime. This new level of MCB will use

queue banks in place of the traditional chains of core buffers, and MCB will not write

non-recoverable messages to mass storage. TPE transactions will gain access to the

MCB subsystem by calling through a pair of AFCBs that make the TPE-to-NPE

transition.

Application Program Interfaces (API) for Transaction Programs remain unchanged,

except that the data returned by the STATS$$ and PIDSTAT$$ functions are changed

due to changes to MCB’s internal data structures. Also, sites using Tailored Message

Analysis or Tailored Session Analysis (TMA/TSA) local code must adapt their code due

to changes to MCB’s internal data structures.

3.3.2. TDATE$ Timestamp Format

Over the next several years, Unisys plans to eliminate the generation of TDATE$

format timestamps and formats based on TDATE$ in all of its products.

The TDATE$ timestamp format will overflow its allotted 36 bits of storage after

December 31, 2027, 23:59:59. At this time, the year portion of the format will wrap,

resulting in TDATE$ timestamps which are ambiguous and are considered to be

invalid. The valid range for the TDATE$ timestamp format is from January 1, 1964,

00:00:00 to December 31, 2027, 23:59:59. Timestamps outside this range will be

processed as if they are within this range. This situation may result in incorrect time

display or invalid program logic.

Unisys strongly recommends that you eliminate the generation of new TDATE$ and

TDATE$-based timestamps from your applications, local code, runstreams, databases,

and external interfaces. Existing TDATE$ timestamps do not need to be changed. They

are within the valid TDATE$ range and will continue to be valid historically.

• If you desire to continue to use local time, switch from interfaces that return

TDATE$ format (for example, ER TDATE$) to interfaces that return other

timestamp formats (for example, ER DWTIME$).


7831 0349–046 3–11

• If possible, Unisys recommends that you switch to UTC time, using interfaces that

return UTC time. ER SYS$TIME or CALL SYSTEM$TIME return UTC time in the

recommended four word TIMEB timestamp format. ER MODSWTIME$ and

CALL MOD$SWTIME return UTC time in a one word, second granular timestamp

format called Modified-SWTIME.

3.3.3. Master File Directory (MFD)

With the ClearPath 16.0 release, two new configuration parameters are introduced to

specify the timestamp format used for the MFD. The configuration parameters

indicate whether TDATE$ or Modified-SWTIME format times are used when creating

new timestamps in the standard or shared MFD.

This release only allows the TDATE$ setting for these parameters. A future release

will allow the parameters to be set to use the Modified-SWTIME format. However, the

value of these parameters may now be retrieved and used by programs that create

timestamps to determine the correct timestamp format to use.

In a release following the one that allows the use of Modified-SWTIME, the use of

TDATE$ timestamp format in the MFD for new timestamps will be eliminated.

3.3.4. Summary Accounting File

With the ClearPath 16.0 release, a new configuration parameter is introduced to

specify the timestamp format used for the Summary accounting file. The configuration

parameter indicates whether TDATE$ or Modified-SWTIME format times are used

when creating new timestamps in the Accounting file.

This release only allows the TDATE$ setting for this parameter. A future release will

allow the parameter to be set to use the Modified-SWTIME format.


TDATE$ timestamp format in the Summary Accounting file for new timestamps will

be eliminated.

3.3.5. Freespace

With the ClearPath 16.0 release, a new system configuration parameter is introduced

and a new Freespace application configuration parameter is introduced to specify the

timestamp format generated for timestamps in the Freespace complex. The

configuration parameters indicate whether TDATE$ or Modified-SWTIME format times

are used when creating new timestamps in the Freespace complex. This includes all

internal Freespace structures and the timestamp included in Freespace file records if

the Freespace application file type keyword ‘TS’ (Time Stamp) is set to

Permitted/Enabled (Permitted/Enabled is the default setting).

This release only allows the TDATE$ setting for the Freespace application

configuration parameter (generation of Modified-SWTIME timestamps in the

Freespace complex cannot be specified). A future release will allow modification of

the Freespace application configuration parameter to cause Modified-SWTIME

timestamps to be generated in the specified Freespace application group.


3–12 7831 0349–046


TDATE$ timestamp format in the Freespace complex for new timestamps will be

eliminated.

3.3.6. Program File Element Table

In a future release, the Program File Element Tables will be converted to use

UTC-based timestamps for all new timestamps. Existing TDATE$ format timestamps

will continue to be valid historically.

To help prepare for this change, in a release prior to the future release mentioned

above, a new configuration parameter for Program File Element Tables will be made

available. This configuration parameter, when turned on, will cause the new

timestamps in the Element Table to be generated using a UTC-based timestamp.

3.3.7. Notice of Intent to Remove Software

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

in a future release.

• Apex was first released in release 15.0 as an OS 2200 administration tool. Its first

release provided a subset of the functions of Security Administration along with

other administrative capabilities. The feature set of Apex is enhanced with release

16.0 and will continue to be enhanced in future releases with security and other

administrative capabilities. With some future system delivery, Security

Administration will no longer be provided, because Apex will serve as its

replacement, including supporting the command line utility SECMGR.

• The following features will be removed from DTI:

− Heritage Application Programs

− AutoUpdate Gateway

− CORBA Client

− Enterprise JavaBeans Client Development

− Java RMI client

• SMOQUE TDATE$ Use

In a future release, the TDATE$ format timestamp in the SMOQUE entries will be

removed. With this release, an additional UTC-based timestamp (in

Modified-SWTIME format) was added to the SMOQUE entries. The TDATE$ format

timestamp in the SMOQUE entries was retained. Please convert programs to use

the Modified-SWTIME format to avoid future issues.

In a future release, the input format of TDATE$ for CALL SMOQ$HNDLR will be

removed. With this release, an additional format for the input timestamp was

added to the CALL SMOQ$HNDLR. The input timestamp format of TDATE$ was

retained. Please convert programs to use the new input format to avoid future

issues.

Software License Management

7831 0349–046 3–13

• MCT and PCT TDATE$ Use

In release 15.0, the TDATE$ format timestamps in the MCT Date/Time section, the

shared MCT and the PCT were replicated in TIMEB timestamp format elsewhere in

these structures. In a future release, the use of the TDATE$ timestamp format in

these structures will be changed or removed. Please consider converting to use

the TIMEB format timestamps in these structures.

• Initial Register R2 and UCSINITREG$ TDATE$ Use

In a future release, the TDATE$ value returned in R2 on program initialization or

through UCSINITREG$ will be changed or removed.

• ER DMCG$ TDATE$ Use

In a future release, the TDATE$ value returned in the ER DMGC$ packet will be

changed or removed. Please consider converting to the use of CALL UCS$GC.

• TPMHVS and SUHVSR - HVSTAT Utilities

The TPMHVS utility, which transfers TPM data into HVSTAT files, will be

decommitted in a future release. The SUHVSR utility, which produces reports from

HVSTAT data, will also be decommitted in a future release.

• CALL CARTTAPELIB$ Ready Packet Versions 0-1

The CALL CARTTAPELIB$ ready packet, versions 0 and 1, contain use of TDATE$.

These packet versions will be removed in a future release.

• OPE

OPE will no longer be provided in a future OS 2200 release.

3.3.8. Notice of Intent to Remove Hardware

For latest information, refer to Hardware Support Plan on the Unisys Product Support

website using the following link:

http://www.support.unisys.com/common/ShowWebPage.aspx?id=1329&pla=D8X&nav=D8X


so.

3.4. 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–14 7831 0349–046

3.4.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 or UOE products

• Optional products

• Software performance levels (Image Enabler Key)

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

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.

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 General Purpose IOE/UOE

• ClearPath OS 2200 Software Development Kit (SDK) IOE/UOE

• ClearPath OS 2200 Business Information Server (BIS) IOE/UOE


7831 0349–046 3–15

• ClearPath OS 2200 Enterprise Application Environment (EAE) IOE/UOE

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

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 its corresponding key SCN that matches the Exec image enabler key SCN is

registered.


3–16 7831 0349–046

3.4.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.


7831 0349–046 3–17

3.4.3. Ordering ClearPath OS 2200 Software

To take delivery of the ClearPath OS 2200 release software, you must place an update

order 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 tape received

with the ClearPath OS 2200 software release. The software product key DVD is

delivered in an orange clam shell holder to easily distinguish it from the rest of the

release media. The following figure shows an example of a software product key tape

label.

3.4.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.


3–18 7831 0349–046

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.4.5). The software products do not need to be reinstalled.

3.4.5. Registering Your Software Product Keys

Use SOLAR to register the 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.


7831 0349–046 3–19

3.4.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 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 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.


3–20 7831 0349–046

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.

How does this feature affect package tapes created with SOLAR/E?

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.

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.

Software License Management and LIBSAVE/LIBLOAD

7831 0349–046 3–21

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.5. 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.5.1. LIBSAVE/LIBLOAD Examples

Examples in 3.5.2 and 3.5.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.

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.


3–22 7831 0349–046

• 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.5.2. Otherwise, see 3.5.3.

3.5.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.


7831 0349–046 3–23

Perform the following steps:

1. Perform LIBSAVE from System A to save DATA$ information from System A.

System A System B

Image Enabler

Keys

Product

Key

Image Enabler

Keys

Product

Key

In Compliance

MCN1 SCN1 SCN1 MCN2 SCN2 SCN2 Yes.

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.

System A System B

Image Enabler

Keys

Product

Key

Image Enabler

Keys

Product

Key

In Compliance

MCN1 SCN1 SCN1 MCN1 SCN1 SCN1 No.

Image Enabler key MCN does

not match hardware MCN.

WARNING

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–24 7831 0349–046

3. Register System B Image Enabler key tape values MCN2 and SCN2 onto System B.

System A 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.

System A System B

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.


7831 0349–046 3–25

3.5.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.

System A System C

Image Enabler

Keys

Product

Key

Image Enabler

Keys

Product

Key

In Compliance

MCN1 SCN1 SCN1 MCN3 None None Yes.

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.

System A System C

Image Enabler

Keys

Product

Key

Image Enabler

Keys

Product

Key

In Compliance


Image Enabler key MCN does

not match hardware MCN.

WARNING

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.

System A System C

Image Enabler

Keys

Product

Key

Image Enabler

Keys

Product

Key

In Compliance

MCN1 SCN1 SCN1 - SCN1 No.

Image Enabler key is no longer

registered.


3–26 7831 0349–046

4. Register the System C Image Enabler key tape value of MCN3 onto System C.

There is no SCN value.

System A System C

Image Enabler

Keys

Product

Key

Image Enabler

Keys

Product

Key

In Compliance

MCN1 SCN1 SCN1 MCN3 None SCN1 No.

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.

System A 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.

Keyed Tape Delivery

7831 0349–046 3–27

3.6. 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 system and

particular software group. 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 * 2014-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 - - 20140224 - - MIXED 0123456 15.0

- 19:32:01

- - - - -

-

SOLAR 4R7A 9894-25 - - 20140224 - - ABSOLUTE 0123456 15.0

- 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 system is authorized for the product or the file.

Keyed Tape Delivery

3–28 7831 0349–046

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.

Keyed Tape Delivery

7831 0349–046 3–29

• 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.6.1. Nonkeyed Products

The following packages and products are delivered without SOLAR keys:

• CP-FLD

• CP-OE2

• Exec boot tape

• Exec release master / Symbolics

• Enterprise Output Manager (EOM) for ClearPath OS 2200 (DEPCON)

• Software Controlled Performance (SCP) key tape or file

• SOLAR

License Keys for TeamQuest Products

3–30 7831 0349–046

3.6.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.7. 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)

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.


7831 0349–046 3–31

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.

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.

3.7.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 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 system’s product license keys are kept

in this master file, each product is immediately ready for use as soon as the

installation completes.


3–32 7831 0349–046

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

is the site-id for the system or the keyword DEMO_KEY (for product license keys

used before products are registered).

key

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/2015

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.


7831 0349–046 3–33

3.7.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/14 13:21:56

>

> 12345678901234567890

> Exec Level : 49R1

> Siteid : CL01

> System Type : 2200/8030

> MCN : 00112233

> SCN : 1234567

> Expiration : 2016/12/15

3.7.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.

Build Option

3–34 7831 0349–046

3.7.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.8. Build Option

Unisys provides a build option package that contains absolute keys for the set of

products listed below. These products are used for customized builds before

installation. The style of the build option package is CSW20-BLD. To order this build

option package, contact your Unisys representative.

Note: TIPUTIL requires C Compiler (UC) and ASCII FORTRAN Compiler (FTN) to

build. C Compiler is supplied to ClearPath systems as part of their IOE/UOE. 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)

ClearPath and Plateau Interdependencies

7831 0349–046 3–35

3.9. ClearPath and Plateau Interdependencies

Plateau media must be ordered and installed by your Unisys service representative.

ClearPath OS 2200 release 16.0 was tested as an integrated package on ClearPath.

Table 3–2 and Table 3–3 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–2. ClearPath Dorado Plateau Interdependencies Without XPC-L

Support

Dorado System

(without XPC-L

support)

System Plateau Release

Level

Release 16.0 Dependency

Initial Current

Dorado 4050, 4080,

4090

1.0 2.4 Requires Dorado 4000 Plateau

2.4 (no additional compatibility

package is required).

Dorado 4150, 4170,

4180, 4190

1.0 1.2 Requires Dorado 4100 Plateau 1.2

Dorado 4250, 4270,

4280, 4290

1.0 2.0 No specific dependency

Dorado 4350, 4370,

4380, 4390


Dorado 6380, 6390 1.0 2.0 No specific dependency



Dorado 840, 850, 860,

870, 880, 890



3–36 7831 0349–046

Table 3–3. ClearPath Dorado Plateau Interdependencies with XPC-L

Support

Dorado System (with XPC-L

support)

System and XPC-L Plateau

Release Level


Initial Current

XPC-L Support on Dorado

4080, 4090

Dorado Plateau Requires Dorado 4000

Plateau 2.4 (no additional

compatibility package is

required).

2.0 2.4

XPC-L Plateau

XPC-L-2 2.2 2.2

XPC-L-3 3.0 3.4


4180, 4190

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.4


4280, 4290

Dorado Plateau

2.0 2.0

XPC-L Plateau

XPC-L-3 3.2 3.4


4380, 4390

Dorado Plateau No specific dependency

2.0 2.0

XPC-L Plateau

XPC-L-3 3.4 3.4


6380, 6390


2.0 2.0

XPC-L Plateau

XPC-L-3 3.4 3.4

XPC-L support on Dorado

780, 790


2.0 3.5

XPC-L Plateau

XPC-L-2 2.1 2.2

XPC-L-3 3.0 3.4


7831 0349–046 3–37

Table 3–3. ClearPath Dorado Plateau Interdependencies with XPC-L

Support

Dorado System (with XPC-L

support)

System and XPC-L Plateau

Release Level


Initial Current

XPC-L support on Dorado

860, 870, 880, 890


3.1 3.5

XPC-L Plateau

XPC-L-3 3.0 3.4

Note: 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–4 details the requirements by product level.

Table 3–4. CPCommOS Plateau Component Requirements

Product/Level

Release Dorado 4000

Dependency

Dorado 4100

Dependency

Dorado 4200

Dependency

Dorado

4300/6300

Dependency

CPCommOS

4R3

ClearPath

OS 2200 14.0

Requires either

Dorado 4000

Plateau 2.4 (no

compatibility

package is

required) or

Dorado 4000

Plateau 2.3 and

ClearPath 13.1

Dorado 4000

Compatibility

Package

Plateau 1.2 Plateau 1.0 No specific

dependency

CPCommOS

4R4

ClearPath

OS 2200 15.0

Requires either

Dorado 4000

Plateau 2.4 (no

compatibility

package is

required) or

Dorado 4000

Plateau 2.3 and

ClearPath 13.1

Dorado 4000

Compatibility

Package


dependency

ClearPath Specialty Partitions Interdependencies

3–38 7831 0349–046

Table 3–4. CPCommOS Plateau Component Requirements

Product/Level

Release Dorado 4000

Dependency

Dorado 4100

Dependency

Dorado 4200

Dependency

Dorado

4300/6300

Dependency

CPCommOS

4R5

ClearPath

OS 2200 16.0

Requires

Dorado 4000

Plateau 2.4 (no

additional

compatibility

package is

required)


dependency

3.10. ClearPath Specialty Partitions Interdependencies

ClearPath OS 2200 release 16.0 supports the following three specialty partitions:

• OS 2200 JProcessor

• OS 2200 QProcessor

• ePortal for OS 2200

The specialty partitions execute on a single purpose dedicated engine, a

multi-partitioned Consolidated Specialty engine, a Bundled Specialty module, or an

Enterprise Partition Platform for the Dorado 4300 or 6300 Series. JProcessor and

QProcessor Specialty Partitions 2.2 for Consolidated Specialty engines may execute

with release 14.0 and above. JProcessor and QProcessor Specialty Partitions 3.0 for

the Enterprise Partition Platform may execute with release 15.0 and above.

Server Specialty Partition SRP

Dorado 700 Single purpose dedicated engine

JProcessor JPROCESSOR-2.2

QProcessor QPROCESSOR-2.2

ePortal EPORTAL-2200-2.1 (PRP)





Multi-partitioned Consolidated Specialty engine

JProcessor & ePortal CSE-2200-J-E-2.2

JProcessor & QProcessor CSE-2200-J-Q-2.2


7831 0349–046 3–39

Server Specialty Partition SRP









Dorado 4200 Bundled Specialty module

JProcessor & ePortal CSE-2200-BSM-2.2

Multi-partitioned Consolidated Specialty engine

JProcessor & QProcessor CSE-2200-J-Q-2.2

Dorado 4300 Enterprise Partition Platform

JProcessor JProcessor-3.0

QProcessor QProcessor-3.0

Dorado 6300 Enterprise Partition Platform

JProcessor JProcessor-3.0

QProcessor QProcessor-3.0

ClearPath OS 2200 release 16.0 is paired with JProcessor release 2.2 or 3.0 and

QProcessor release 2.2 or 3.0. The following table shows the Specialty Partition

software product dependencies.

Specialty Partition

ClearPath OS 2200 16.0 Specialty

Partition Product Levels

JProcessor 2.2/3.0 JPJVM 8.0

INTERCONNECT 1R4B

QProcessor 2.2/3.0 WMQ2200 7R0C

INTERCONNECT 1R4B

Sections 3.10.1 and 3.10.2 of this document include the supported software

configurations on JProcessor and QProcessor releases including JPJVM, WMQ2200,

and INTERCONNECT that are included in the ClearPath OS 2200 releases.


3–40 7831 0349–046

3.10.1. OS 2200 JProcessor

Release Contents

ClearPath OS 2200 release 16.0 includes JPJVM 8.0 and INTERCONNECT 1R4B.

Refer to the JProcessor-3.0 System Release Profile (SRP) on the Unisys Product

Support website. The JProcessor-3.0 SRP highlights the new features for JProcessor

3.0 and the additional products that support JProcessor. The SRP lists download

information for each of the products in the OS 2200 JProcessor 3.0 release.

For JProcessor 3.0 the following table identifies the recommended software levels

that have been tested and verified for compatibility with each other. Applicable

updates and other important information are available in the product release profile

(PRP) for each product.

Product Level Support Name Product Level Support Name

Interconnect (IC2200) 1R4B INTERCONNECT

Virtual Machine for the Java™ Platform on ClearPath

OS 2200 JProcessor

8.0 JPJVM

The following configurations are supported.

Product-Level

Combination JProcessor 2.2 JProcessor 3.0

JPJVM 7.1/ IC2200 1R4 Supported Not Supported

JPJVM 7.2/ IC2200 1R4A Supported Supported

JPJVM 8.0/IC2200 1R4B Supported Supported

Going Forward!

This section highlights important JProcessor environmental differences between the

Forward! Enterprise Platform Partition or EPP and its predecessor processors, the

multi-partition Consolidated Specialty Engine (CSE) and single-purpose Specialty

Engine.

In the Forward! environment, the CSE or single-purpose Specialty Engine application

and maintenance AM LAN becomes two separate LANs, the IP LAN (Inter-Partition

LAN) and the FM LAN (Forward! Management LAN). These LAN addresses are fixed

and preset at commissioning. The EPP JProcessor LAN addressing is based on

platform number and partition number. The default FM LAN format is

172.29.<platform#>.<partition#>. The default IP LAN format is

172.31.<platform#>.<partition#>.

JProcessor designators still exist but are unused in the Forward! environment.


7831 0349–046 3–41

3.10.2. OS 2200 QProcessor

ClearPath OS 2200 release 16.0 includes WebSphere MQ 7R0C and INTERCONNECT

1R4B.

The following configurations are supported.

Product-Level

Combination QProcessor 2.2 QProcessor 3.0

WMQ2200 7R0A/

IC2200 1R4

Supported Not Supported

WMQ2200 7R0B/

IC2200 1R4A

Supported Supported

WMQ2200 7R0C/

IC2200 1R4B

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

website.

Going Forward!

This section highlights important QProcessor environmental differences between the

Forward! Enterprise Platform Partition or EPP and its predecessor processors, the

Consolidated Specialty Engine (CSE) and Specialty Engine.

In the Forward! environment, the CSE or Specialty Engine (SR1500) application and

maintenance AM LAN becomes two separate LANs, the IP LAN (Inter-Partition LAN)

and the FM LAN (Forward! Management LAN). These LAN addresses are fixed and

preset at commissioning. The EPP QProcessor LAN addressing is based on platform

number and partition number. The default FM LAN format is

172.29.<platform#>.<partition#>. The default IP LAN format is

172.31.<platform#>.<partition#>.

QProcessor designators still exist to aid in the installation of the WMQ2200 product

components to the OS 2200 QProcessor through the ICADMIN configuration.

However, QProcessor IP addressing in the Forward! environment no longer uses

these installation designator numbers.

CSE and Specialty Engine QProcessor local storage and external storage queue

manager backup file sets can be used to restore or move queue managers to a

Forward! EPP QProcessor. However, a Filesystem Backup file set cannot be used to

restore any part of the CSE or Specialty Engine file system or networking environment

to an EPP.

Microcode Requirements for CTS5236 and T9840 Tape Drives

3–42 7831 0349–046

When you set up a Resource Group for HA monitoring using the CSE or Specialty

Engine, you specified an OS 2200 Application Access Point – IP Address. This is the IP

address that moves between HA nodes in a failover situation. It is also the address

used as the mqseries/config LinuxIP configuration parameter. For the Forward! EPP,

these addresses are pre-defined and provided for you. The Application Access

Point – IP address uses a modified form of the preset IP LAN address. Six resource

groups can be configured in a Forward! EPP HA configuration using this new

addressing scheme.

The maximum number of QProcessor partitions allowed in the Dorado 4300/6300 is

four (4). Also, a maximum of one QProcessor partition is allowed per EPP platform.

This implies the configuration profile for the maximum of four QProcessor partitions in

the Forward! environment is one QProcessor partition on each of four EPP platforms.

HA is only supported for two QProcessor partitions residing on separate EPP

platforms.

3.10.3. ePortal for OS 2200

The OS 2200 ePortal release includes software support for .NET Framework 4.0. For

detailed information on whether you need to perform any additional steps to enable

the .NET Framework 4.0 support, see the ClearPath ePortal .NET Framework 4.0

Package link on the ePortal Support website. Use the following steps to navigate to

the ePortal-2200 Support Site:

1. Go to http://www.support.unisys.com.

2. Expand the ClearPath OS 2200 Servers and Software list, and click the

desired OS 2200 Mainframe series.

3. Under Support Options, click Software, and then click Search Product

Downloads.

4. Under Specialty Partitions, expand ClearPath ePortal, and then click

ClearPath ePortal Unisys.

The ClearPath ePortal web page contains information for ePortal MCP and e-Portal

OS 2200.

5. Expand Level Information, and under Level/Downloads click the link to the

latest download level.

The ClearPath ePortal-2200 Support website opens.

6. In Additional Links, click the ClearPath ePortal .NET Framework 4.0

Package link to enable the .NET Framework version 4.0 support.

3.11. Microcode Requirements for CTS5236 and T9840 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

Supported Peripheral Products

7831 0349–046 3–43

• 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.12. Supported Peripheral Products

See Section 9, “Peripheral Migration,” in the ClearPath Dorado

700/800/4000/4100/4200/4300/6300 Server I/O Planning Guide (3839 6586). This

appendix identifies the supported tape and disk products, discontinued products

previously supported, and miscellaneous products.

Supported Peripheral Products

3–44 7831 0349–046

7831 0349–046 4–1

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 16.0.

• 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.

General Exec Considerations

4–2 7831 0349–046

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 16.0 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 16.0

4.1.1.1. Secure by Default – Optionally disallow @@PASSWD

The default for the new Exec configuration parameter

enable_passwd_control_statement is FALSE, which disallows the use of @@PASSWD

on Fundamental Security and Security Level 1 and 2 systems. To change passwords on

a system with this parameter FALSE, either change the password at login time, use

the @PASSWD$ processor supplied with User Authentication, or use system

administration software (Security Client, Apex, or TeamQuest SIMAN) to change the

password.

4.1.1.2. Secure by Default – Configure Delayed Sign On Solicitation to meet PCI DSS guidelines

If you use the Delayed Sign-on Solicitation method of hacker frustration, the terminal

will be disabled after 8 unsuccessful login attempt or max_sign_on_attempts

unsuccessful login attempts, whichever is smaller. Since the default for

max_sign_on_attempts is 5, leaving the default at 5 will result in hackers or users

having the terminal disabled sooner than in past releases.

If you had previously considered using Delayed Sign-on Solicitation but avoided it

because it could not meet the PCI DSS requirement of shutting out hackers after no

more than 6 unsuccessful login attempts, Delayed Sign-on Solicitation is now a viable

choice when combined with a value of max_sign_on_attempts that is 6 or lower.


7831 0349–046 4–3

4.1.1.3. CARTLIB Change

The obsolete Exec feature CARTLIB must be removed from the Exec build generation.

If an obsolete feature is installed, the Exec build GEN will display the following error

messages:

Example: An attempt to INSTALL the CARTLIB obsolete FEATURE will error the build

GEN as follows:

SSG*MESSAGE,IL NOTE: AN INSTALL OF CARTLIB FEATURE WAS DONE.

SSG*MESSAGE,ILE ERROR - INSTALL CARTLIB - INVALID FEATURE NAME.

runid*MSG: 1 FEATURE/SKEL ERROR(S) DETECTED!

Note: Beginning with ClearPath OS 2200 release 16.0, CARTLIB is now

incorporated in the standard Exec.


This subsection describes the Exec migration and compatibility considerations that

apply to Exec level 49R1.

4.1.2.1. Daylight Saving Time Adapt

This feature enables the Exec to support a dynamic change of the seasonal time

offset. This feature replaces the use of local time with the use of UTC time in many

places in the Exec. See Mandatory Migration Actions for ClearPath OS 2200 Release

15.0 and Higher (8222 3777) for more details.

DSTA migration issues

• Exec Configuration Parameters and Defaults

− The dynamic configuration parameter TIME_DATE_FORMAT (TIMEDATEFRMT)

has been removed. This parameter displayed the Run Start and Run Fin

messages and the continuous console display in Japan Industrial Standard (JIS)

date and time format (yyyy-mm-dd-hh:mm:ss) instead of the ISO format

standard used by the standard Exec (yyyy-mm-dd hh:mm:ss zone).

− Audit Control - The audit block header has increased in size from 8 words to 10

words. If you specify any Audit Control TRANSFER MAXIMUM SGS, you might

need to adjust the maximum transfer size to allow for the two additional

words of the audit block header. With the two additional words in the audit

block header, the block envelope words have increased from 22 to 24 words

for XTC concurrent Step Control applications and from 17 to 19 words for all

other audit trails.

− Audit Control - The ACI file configuration statement is changed. Instead of

specifying the file size in terms of the number of tracks, you specify the

number of records in the ACI file. The ACI file configuration statement, if used,

must match the Exec level. If an ACI file configuration statement is not

specified, the system default is used.


4–4 7831 0349–046

The default ACI statement for a Step Control ACI is:

ACI TRAIL at-num PARAMETERS ARE: MEDIA,FIX TYPE,F MCR,73000 PSL,525000

The default ACI statement for a non-Step Control ACI is:

ACI TRAIL at-num PARAMETERS ARE: MEDIA,FIX TYPE,F MCR,73000

− Audit Control - The default COD audit trail configuration file size has been

increased so that 32 cycles of the COD audit trail contain approximately one

year of COD data.

− Step Control - The Step Control QNBR statement and ABQNBR defaults have

changed. The QNBR default changed from 250 to 1000. The ABQNBR default

changed from 15 to 100. If you specify only QNBR or only ABQNBR, you might

need to specify both QNBR and ABQNBR to avoid errors and produce the

same configuration. For example, if you currently specify QNBR IS 50 and use

the default for ABQNBR (default of 15), you must now specify ABQNBR IS 15

to produce the same output. If you currently specify the maximum number for

QNBR and use the default for ABQNBR, you must now specify ABQNBR IS 15

to produce the same results. Alternatively, you could adjust the QNBR down

so that the total of QNBR plus the default ABQNBR is not greater than the

maximum number of queue items allowed.

• Audit Control

− Audit trail formats are changed. The ATD version is incremented which closes

the audit trails and initializes the audit trail configuration from the MCT. Audit

block header format is changed and audit trail control records are reformatted.

User programs that read audit trails and do not use IRU's Free Standing Audit

Handler (FSAH) must be modified to recognize the new control record

formats. User programs that use IRU's FSAH need to use the release 15.0 IRU

FSAH. User programs that use FSAH have the option of converting to the

FSAH interface format - version 5 or 6 - that uses UTC time.

User programs that previously used IRU's FSAH will work with no

modification. However, special considerations exist if they use the version 4

FSAH interface and specify start or end points in local time. Since the local

time is converted to UTC before searching the audit trail, the start and end

points may be off by the seasonal shift amount if a seasonal shift occurred

within the range of audit trail times being read.

− Many audit records have changed.

Step Control audit records are reformatted to use UTC time. FCSS audit

records are changed to use UTC time.

TPM audit records are changed to use UTC instead of local time with additional

time configuration information appended to type 15 subtype 6.

COD audit records type 1 and 2 have additional time configuration information

appended to them.

Many system log records have additional time data appended to them, and

one system log record is replaced – see 4.4 for a list of affected log records.


7831 0349–046 4–5

User programs that read audit trails might need modification, depending on

which audit trails and audit trail records they reference.

− The ACI file format has changed, which results in an increase in ACI file size.

The ACI file entries have increased in size to use UTC time. The default

number of ACI entries has increased. For Step Control audit trails, a new ACI

section for periodic save locations is added.

• Step Control

− An application initialization is required when crossbooting between release

14.0 and release 15.0 or higher. Both the Step Control QCA version and the

step-id format have changed. Recoverable messages and recovered ready

steps cannot be preserved across crossboots between release 14.0 and

release 15.0. IRU short recovery and queue item recovery are not supported

across the crossboots. IRU medium and long recovery are supported across

the crossboot from release 14.0 to release 15.0. The IRU for release 15.0 or

higher must be installed on the release 14.0 Exec to support recovery for a

crossboot back. An orderly application shutdown is recommended before

crossbooting. See Section 7 for more information.

− The Step Control step-id format has changed in format but not in size.

Programs that interpret the step-id as a time will need to be adapted.

− The TIP Session Control session file record size has been expanded from 112

to 224 words. PSFUTIL is automatically started when moving from release 14.0

to release 15.0 or when dropping back from release 15.0 to release 14.0 to

resize the TSC session file for the appropriate Exec level if an invalid record

size is detected.

In addition, PSFUTIL is automatically started to resize the TSC session file if the

number of records in the TIP file does not match the number of sessions in

the TSC Exec configuration.

• Extended Transaction Capacity (XTC)

XTC systems may be migrated to release 15.0 one host at a time. This is referred

to as 'mixed mode' and requires all hosts to run the same local time offset and

seasonal offset. All hosts must be running with the release 15.0 IRU version - IRU

22R1.

This mode is not recommended as a long term environment. All hosts must be

running release 15.0 before the next seasonal time shift (dynamic or not) or the

integrity of the recovery operation is not guaranteed.

• ERs and CALLs

− The following ERs have changed:

o ER CONFIG$ - STEP_CONTROL_BASIC_CONFIG has a new TSC area.

o ER ERCVS$ - changed to UTC times and the new step-id format. Only the new version of ERCVS$ is supported.

o ER MCT$ - MCT Date/Time section has additional UTC time information.

o ER PCT$ - a PCT extension contains additional UTC time information.

o FCSS CT - TCDBF checkpoint time is now UTC-based.


4–6 7831 0349–046

o FCSS ET - this function is no longer supported (see FCSS TS).

o FCSS TS - this function replaces FCSS ET with oldest deferred update time in UTC.

− The following Step Control ERs are unchanged in format but return the new

step-id format:

o ER CO$MIT

o ER RL$BAK

o ER TIP$Q

o ER TIP$ID

o ER QI$NIT

o ER QI$CON

o ER TIP$XMIT

o ER SC$QR

o ER MQF$

− The following CALLs have changed:

o CALL INSP$RUNS - has additional UTC time information.

o CALL INSP$RUNID - has additional UTC time information.

o CALL UNIQUE$ID - the restriction for seasonal setback (seasonal shift) is removed.

o CALL CARTTAPELIB$ - a new version with UTC time is available.

o CALL MEDIA$MGR - a new buffer version contains UTC time.

− The following Step Control CALLs return the new step-id format:

o CALL OLTP$STEP

o CALL READY$STEPS

o CALL REMOTE$STEP

o CALL UDS$STEP - also updated to return start-of-step time in UTC

• Console Keyins and Console Messages

− Console keyin output has changed the time display for the following keyins:

o BL

o LC TPM

o PAUSEIO

o RC

o SS

o T


7831 0349–046 4–7

o TP RC

o Continuous display

See Mandatory Migration Actions for ClearPath OS 2200 Release 15.0 and

Higher for more details.

− Various console messages are changed to include new time information (see

Mandatory Migration Actions for ClearPath OS 2200 Release 15.0 and Higher

for examples).

• Tailsheet

The tailsheet format has changed to add a time zone to the START and FIN times.

• DIAG$

The DIAG$ file format has changed - the DAP/FLIT and PADS from release 14.0 or

higher are required.

• TIP Error History

The TIP Error History file format has changed.

• Dynamic Time Shift Considerations

Some areas of the Exec remain in local time. Because of this, various warning

messages will be displayed when doing a local time shift. Details of these are in

the Exec ARM Time section and in the Mandatory Migration Actions for

ClearPath OS 2200 Release 15.0 or higher:

− MFD - This is the possibility of loss of removable file allocation that occurs

within the two hour local time overlap window on a dynamic time shift back.

− MFD - After a dynamic time shift, it is possible for a file's 'File Creation' time to

be displayed as later than its 'Last Update' time. This is a display anomaly only.

− FAS - FAS commands BACKUP and COPY_VOLUME may be affected by a

dynamic time shift back.

− SIP and IOTRACE - SIP and IOTRACE must be stopped across a dynamic time

shift.

− KONS and TIMER - Possible anomalies may occur for TIMER scheduling and

KONS across a dynamic time shift.

− Start/deadline runs - Possible anomalies may occur for delayed start and

deadline runs across a dynamic time shift.

− Application considerations - Do not use dynamic shift if your applications

cannot support it.

• TDATE$ time format replacement - Modified-SWTIME

A new time format is added - Modified-SWTIME. This is a 36-bit, second-granular,

UTC-based time that may be used to replace the TDATE$ format in situations

where the recommended TIMEB format cannot be used.

ER MODSWTIME$ and CALL MOD$SWTIME have been added to return the

current time in Modified-SWTIME format.


4–8 7831 0349–046

Two other interfaces - ER TIMECONFIG$ and CALL TIME$CONFIG - have been

added to return the Partition Data Bank (PDB) time configuration. This

configuration data is needed when working with Modified-SWTIME; for example,

when converting Modified-SWTIME into TIMEB. For additional information on

Modified-SWTIME, see section “Time Management” in the Exec System Software

Administration Reference Manual and the section “Obtaining Timestamps” in the

ClearPath OS 2200 System Services Programming Reference Manual.

4.1.2.2. DMPLIB 9R1

Exec 49R1 requires DMPLIB 9R1 to process the 49R1 level Exec dumps. Install DMPLIB

9R1 in advance of installing the Exec 49R1.

4.1.2.3. Exec Migration Issues for MHFS environments

If you have a MHFS environment you must build and boot crossboot change PLE

18950154 on all hosts before the first host moves from release 14.0 to release 15.0.

4.1.2.4. I/O Legacy Removal

The I/O Legacy Removal removed the following obsolete components:

• Four Exec Features:

− Cartridge Tape Interface Software, CARTIS

− Fixed Block Compatible Interface Software, FBCIS

− SCSI Tape Interface Software, SCSITIS

− HYPERchannel Interconnect Handler, SINCH

• Three Executive Requests (ERs):

− ER HOST$ (0311): Retrieve information from Port_ID_Table in the Shared MCT.

− ER IOAID$ (0267): Arbitrary Device Handler (Replaced by SCIO$ADI Call

Interface).

− ER MCODE$ (0266): Microcode Load Handler, Exec boot file SYS$*MCODE$ is

removed.

• Two Exec Library files removed from the system and the Exec boot tape:

− SYS$*MCODE$.

− SYS$*PRINTER$.

• Removed ER INFO$ Function 25, MAC$, (FEP Media Access Control)

• Four Channel Module Types:

− CHBMX: Block Multiplexor(Mux) Channel (BMC)

− WORDCM: Word Channel

− IOP900: Legacy CSIOP Channel

− SCSI: Small Computer System Interface [SCSI2W (2-wide) is still supported}]

• MDISK Family of disks not supported, Disk mnemonic MDISK removed.


7831 0349–046 4–9

• Fifteen Control Unit Types:

CU5042, CU5055, CU5061, CU5073, CU5074, CURLP, HYPRCU, DCPBCU, IPCCU,

HLCCU, HLDCU, HTRCU, HFDCU, FDICU, HLICU

• Thirty-one Equipment Device Types:

HPRDEV, DCPBDV, IPCDEV, HLCDEV, HTRDEV, FDIDEV, ARBBYTE, ARBWORD,

CTLIPC, CTLHLC, CTLHLD, CTLHTR, CTLHFD, CTLFDI, CTLHLI, U22D, U24D, U30D,

U26N, U28N, U32N, U34N, U36N, U47, U47L, CT0899, AC40, DRLP, DRMRLP,

DMGRLP, DORLP

• Twenty-two Tape Equipment Mnemonics:

36N, 34N, 32N, 28N, 26N, 30D, 24D, 22D, U36N, U34N, U32N, U28N, U26N, U30D,

U24D, U22D, U47, U47L, HIC40, U47NL, LCART, NLCART

I/O Legacy migration issues:

• Obsolete equipment must be removed from the PDB. If obsolete equipment is

detected in the PDB during the Exec boot an Exec IAR 0133 Halt will occur

indicating an obsolete equipment was found during the boot process.

Example: A State Save or EZDUMP will contain the following:

130:ER8-ER11 000000000000 000000166351 050004000133 000014716060 NOEQPCFG=014

134:ER12-ER15 132016231631 162425716060 000000000170 000000000001

FKINIT IOP900

− Register ER10 contains the IAR Code 050004000133, IAR Halt 0133.

− Register ER11,H1 contains the error subcode 000014, NOEQPCGF, Unknown

Equipment mnemonic.

− Register ER12 contains the Fieldata name of the Exec element FKINIT which

detected the error.

− Register ER13 contains the Fieldata name of the obsolete equipment

mnemonic, IOP900.

• Obsolete Exec features CARTIS, FBCIS, SCSITIS or SINCH, must be removed from

the Exec build generation. If an obsolete feature is installed, the Exec build GEN

will display the following error messages:

Example: An attempt to INSTALL the SCSITIS obsolete FEATURE will error the

build GEN as follows:

SSG*MESSAGE,IL NOTE: AN INSTALL OF SCSITIS FEATURE WAS DONE.

SSG*MESSAGE,ILE ERROR - INSTALL SCSITIS - INVALID FEATURE NAME.

runid*MSG: 1 FEATURE/SKEL ERROR(S) DETECTED!

Notes:

• DVD equipment type no longer requires the SCSITIS feature.

• OST5136 tape equipment no longer requires the SCSITIS feature.

• CTS5236 tape equipment no longer requires the SCSITIS feature.

• T9840C tape equipment no longer requires the SCSITIS feature.


4–10 7831 0349–046

• T9940B tape equipment no longer requires the SCSITIS feature.

• The BOOTELT 9R1 delivered with the Exec 49R1 has been updated to remove the

SYS$*MCODE$ and SYS$*PRINTER$ library files that are no longer used or needed

with release 15.0 Exec 49R1. Be sure that your SYS$*RUN$ file is using the

updated BOOTELT.

The two library files SYS$*MCODE$ and SYS$*PRINTER$ can be removed from

the system at the site’s convenience.

• If you have any products, utilities or programs that use any of the obsolete Exec

ERs: HOST$, IOAID$ or MCODE$, the program will abort with the following error:

Example:

ER TYPE 04 CODE 03 CONT 12 REENT ADR: 001143 BDI: 000004 L,BDI: 400004

AUX INFO: 000000000267

'ER' INDEX WITHIN RANGE, BUT NOT IN USE.

The AUX INFO value is the obsolete ER index, in this case the old IOAID$ value of

0267.

Note: The ER IOAID$ is replaced by the SCIO$ADI interface and those

programs would have to be modified to continue to use the new arbitrary device

handler.

• Several Exec system log entry Types are no longer generated on release 15.0 Exec

49R1 and beyond:

Type 613: HYPERchannel Device Error

Type 625: HLC Error

Type 1251: Channel program error

Type 1252: Tape Channel Program Error

Type 1253: Mass Storage Channel Program Error

Type 1257: HYPERchannel Device or FEP Error

Type 1352: Log Only Subsystem Information

Type 1354: Channel Clear Failure

• The following obsolete tape equipment mnemonics should be removed from

programs.

36N, 34N, 32N, 28N, 26N, 30D, 24D, 22D, U36N, U34N, U32N, U28N, U26N, U30D,

U24D, U22D, U47, U47L, HIC40, U47NL, LCART, NLCART

If any of the obsolete tape equipment mnemonics are attempted to be used the

following error will occur:

>@asg,tj tap.,u47,scrtch

>E:201033 U47 is not a configured assign mnemonic.

Any programs using these obsolete tape equipment mnemonics will need to be

modified to use supported tape equipment mnemonics.

Note: Using the pool name “NONCTL” with the mnemonic U47M will force the

assignment to a freestanding U47M drive.


7831 0349–046 4–11

4.1.2.5. Secure by Default

The default values for a number of security settings are modified by the Exec Secure

by Default feature. These changes are delivered on both the EXEC boot tape and EXEC

master tape. The new default Exec configuration might now contain parameter

settings which differ from the values that were built into your Exec 48R9 system. If

your Exec sysgen uses the system defaults for these security settings, it will use the

new release 15.0 values. Each of the parameters in the table below can be changed

dynamically except TSS_CONTROL, which requires a reboot to change. Here is the

effect of each of the parameters on systems that used the previous defaults.

Static Name Dynamic Name Previous

Default

Release

15.0

Default

Effect of changing from previous

to new value

TSS TSS_CONTROL FALSE TRUE Only affects Fundamental Security

systems with TSS_CONTROL

FALSE. See note 1.

MAXPASSDAY DEFAULT_MAX_D

AYS_PASSWORD

7300 90 Requires users to change

passwords every 90 days unless

overridden in the user-id’s security

record. See note 2.

MINPASSDAY DEFAULT_MIN_D

AYS_PASSWORD

0 1 Requires a password to remain

without change for 1 day unless

overridden in the user-id’s security

record. See note 2.

MINPASSLEN MIN_PASSWORD

_LENGTH

1 8 Requires changed passwords to

be at least 8 characters long. See

note 3.

MAXPASSLEN MAX_PASSWORD

_LENGTH

6 18 Only affects Security Level 1 or

higher systems with

machine-generated passwords

enabled. See note 4.

MAXATMP MAX_SIGN_ON_A

TTEMPTS

63 5 The Exec ignores further sign-on

attempts after 5 failures if

DELAYED_SIGN_ON_SOLICITATIO

N is not configured. See note 5.

Each of the parameters can be modified dynamically except TSS_CONTROL, which

requires a reboot to change.


4–12 7831 0349–046

Notes:

1. When TSS_CONTROL is FALSE, user terminal security is not enabled and only

the security officer has user-id/password sign-on protection. When

TSS_CONTROL is TRUE, terminal security is on and all users have security

records with authentication information. Moving from a system with

TSS_CONTROL FALSE to one with TSS_CONTROL TRUE requires creating

security records for the system’s users. All systems with Security Level 1 or

higher already have TSS_CONTROL TRUE. The other five parameters in this

table only apply when TSS_CONTROL is TRUE.

2. Within each user-id security record, you can specify values that override the

system defaults for MAXPASSDAY and MINPASSDAY. For example, you could

set up the system default to be that everyone has to change their password

every 90 days but you could update that value to be 7300 days (20 years) in the

user-id record for user-ids associated with your batch background runs (since

you probably do not want to have to be updating those passwords all the time).

The Apex Passwords report will show you which user-ids are not using the

system default values.

3. Users using traditional authentication can continue to use their current

passwords of any length until they are required to change passwords. When

they change, the new password must be 8 or more characters long. The

password length restriction does not apply to the initial password supplied by

the administrator who creates the user-id security record. In addition, the

password length restriction does not affect logins that use network user-ids,

including users of Authentication Modules 2 (Kerberos), 3 (NTLM), 7 (local with

network ID), and 12 (LDAP). Similarly, it does not affect users of Authentication

Module 19 (Configured Password Profiles) and 59 (Enhanced Security Profiles).

4. When the Exec generates a machine-generated password choice for a user, it

creates a string whose length is between the minimum and maximum password

lengths. For systems that do not have machine-generated passwords

configured, the maximum password length is unchanged from previous levels,

which support up to 18 character passwords. Similarly, even if

machine-generated passwords are enabled, an individual user-id can be

configured to not use a machine-generated password, and for those users, this

new value of MAX_PASSWORD_LENGTH makes no difference from previous

levels.

5. The Exec supports two methods of hacker frustration, and a system uses one or

the other but not both. The default method is MAX_SIGN_ON_ATTEMPTS, but

if DELAYED_SIGN_ON_SOLICITATION is TRUE, it overrides

MAX_SIGN_ON_ATTEMPTS. If DELAYED_SIGN_ON_SOLICITATION is FALSE,

the Exec ignores the user’s logon credentials after the 5th failure to supply a

correct user-id/password combination, but it keeps on prompting for new

user-id/password combinations, to keep a hacker or automated logon attack

from realizing when it stumbled upon a valid combination. (Note that only the

default limit has changed, not the mechanism.)


7831 0349–046 4–13

4.1.2.6. TCFUPGRADE Routine for Updating Exec Level 48 to 49

ClearPath OS 2200 release 15.0 introduces a symbolic update for EXEC level 49R1.

Unisys is delivering the TCFUPGRADE software tool to assist you when you migrate

your local code from EXEC level 48 to EXEC level 49. The TCFUPGRADE routine is

found in the utility file of the Exec release master tape and the Exec Symbolic tape.

To use this tool, you need the following files:

• TCFUPGRADE routine and TCFUPGRADE/SKEL skeleton

These elements are in the first file of the EXEC level 49R1 master tape or the EXEC

SYM49 release tape. You must copy them into a file of your choice (Q*F) or

ESD*UTIL. on your system. If you use your file choice (Q*F), then edit the

elements to use your file, instead of ESD*UTIL in elements TCFUPGRADE and

TCFUPGRADE/SKEL.

• The last level 48 mainline PCF used to create the level 49.0 symbolics is supplied

by Unisys.

This file is the third file on the CP-EXEC-SYM (EXEC level 49.0 symbolics) package

tape. You must copy this file to a cataloged file named 48*LASTPCF.

The TCFUPGRADE tool converts an existing TCF that fits against the last level 48

mainline PCF (SYSNUM 48.563) into a new TCF that can be built on top of the level 49

symbolic. The following information is required to build the revised TCF:

• An input TCF source (your existing level 48 code) to convert across the symbolic

update

• The PCF supplied by Unisys from file 48*LASTPCF

• A cataloged output file (SDF format) where the revised TCF (RTCF) will be written

The TCF to be converted may be either an SDF file or element. The first line of the TCF

must be a * card that specifies the name of an EXEC element where your local

changes are applied. Following this line are the correction images for that element,

and, optionally, more * cards and more correction images. Multiple EXEC elements

may be updated within a single TCF. The TCFs being converted must contain only the

code portion of a COMUS change. The TCF cannot contain any COMUS header lines,

and must not include an @EOF after the final line of code.

Note that the BRKPT print file used with the TCFUPGRADE tool is named RTCFPRT.

If the input TCF contains line correction images that change line correction images in

the PCF (for example, -1,2/0,0/2,3), the RTCF result may be incorrect. It is also

impossible to restore lines deleted by the original PCF. Examine the RTCF before

applying it to the new base symbolics. In order to ease this examination, SSG places

the following message above RTCF line correction images that may be in error:

*.*WARNING* UPDATE PERFORMED RESULTS ARE UNPREDICTABLE ******

This will appear above all RTCF line corrections where the original TCF line numbers

contained a slash, even though most or all of the RTCF line corrections are correct.


4–14 7831 0349–046

After completion, examine the RTCF and then remove * WARNING * line(s) from the

RTCF.

In the following example, the items entered by a user are bolded.

@ADD ESD*UTIL.TCFUPGRADE

Enter TCF input source (Q*F or Q*F.E):MY*FILE.MYLOCALCODE

Enter file name of the Unisys-supplied last mainline PCF <48*LASTPCF.>:

(transmit to use the default name) Enter Output SDF Data File for new revised TCF (Q*F.) <RTCF.>: (transmit to use the default name) Note: Revised TCF in SDF data file RTCF.! -- TCFUPGRADE output BRKPTed to file RTCFPRT. -- WARNING! Check BRKPTd file for WARNINGS/ERRORS! Sequence errors

are flagged & associated correction images discarded!! -- @ED,R RTCFPRT.

FURPUR 32R5C (120912 1328:28) 2013 Aug 01 Thu 2233:14

DROP FLAG SET ON ALL CYCLES

I:002333 CAT complete.

W:120433 filename not known to this run.

ELT 8R3C (020110 1432:43) 2013 Aug 01 Thu 2233:14

Copyright(c) 1995-1997 Unisys Corporation.

All rights reserved.

UNISYS PROPRIETARY

@ADD,DP MY*FILE.MYLOCALCODE

END ELT. ERRORS: NONE. TIME: 1.796 SEC. IMAGE COUNT: 38

I:002333 FREE complete.


Stepcontrol Rollback Counter

The Stepcontrol Rollback Counter feature limits the number of rollbacks (without a

commit) allowed per step to 4000. A new error code (054) is returned to any user who

attempts to do more than 4000 rollbacks “with step resume” without an intermediate

successful commit. Prior to this feature, the number of rollbacks “with step resume”

was unlimited.

4.1.4. LIBSAVE/LIBLOAD Scenario

Communications Platform for Open Systems (CPCommOS) is the communications

product for the ClearPath Dorado 4000, 4100, 4200, 4300, or 6300 Server systems.

Dorado 700 or 800 Server systems continue to use the CPComm product.

To perform a LIBLOAD between a Dorado 700 or 800 Server system and a ClearPath

Dorado 4000, 4100, 4200, 4300, or 6300 Server system, the correct communications

product must be installed after the LIBLOAD is completed.


7831 0349–046 4–15

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 700 and 800 systems is on package tape

CP-COMMSUITE.

• CPCommOS for Dorado 4000, 4100, 4200, 4300, or 6300 Server systems is on

package tape CP-COMMSUITE.

Note: The communications configuration file is not included in the LIBSAV.

4.1.5. 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.

With IOCQ, OS 2200 does not queue I/Os that are for the same disk unless the number

of concurrent requests to the disk exceeds the number of (configuration-dependent) I/O

channel paths to that disk. OS 2200 supports up to 16 I/O channel paths to any individual

disk. Therefore, a site may choose to increase the concurrency of I/O requests to a disk

by simply configuring additional I/O channel paths (up to a maximum of 16) to the 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 IOCQ allows the subsequent I/O to proceed ahead of the cache

miss on a different I/O channel path, significantly improving disk performance.

IOCQ is available on all Dorado platforms.


4–16 7831 0349–046

For a disk subsystem to qualify for IOCQ, all of the following conditions must be met:

• The subsystem must be a member of the EMC Symmetrix product family. See

3.12.

Note: The EMC CLARiiON product family does not support IOCQ.

• The EMC functional microcode level must be 56.68.xx.yy or higher. All supported

Symmetrix 5.0, 5.5, DMX, and VMAX models meet this condition, but Symmetrix

4.8 and earlier models are excluded.

• 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.

4.1.6. Processing Exec Dump Files (DUMPLIBS)

Updating the DUMPLIB product from level 8Rx to 9Rx introduces a migration issue.

With DUMPLIB level 8R9A and earlier levels, the EXEC*DUMPLIBS file is used to

process dumps from Exec level 48Rx and earlier systems. With DUMPLIB level 9R1

and later levels, the EXEC*DUMPLIBS file is used to process dumps only from Exec

level 49Rx and later systems.

If you want to process a dump from an Exec level 48Rx or earlier system, you must

save your old EXEC*DUMPLIBS file to an alternate file named EXEC48*DUMPLIBS for

processing before installing the new level of DUMPLIB. You must manually create the

file with the EXEC48 qualifier on each system.

Note: Be sure to save your existing EXEC*DUMPLIBS file to an alternate file

before installing the new level of DUMPLIB. To do this, see the following procedure.

If you want to process Exec dumps from both Exec level 48Rx and level 49Rx

systems, you must perform the following manual procedure:

1. Manually catalog a file named EXEC48*DUMPLIBS.

2. Copy (@COPY) your existing EXEC*DUMPLIBS file (level 8Rx) into the EXEC48*DUMPLIBS file to save the older file.

3. Install the new level 9R1 DUMPLIB file. This overwrites the contents of the EXEC*DUMPLIBS file.

SGS and Configuration Parameters

7831 0349–046 4–17

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. New Configuration Parameters

This release introduces the following new configuration parameters:

• enable_passwd_control_statement (ATATPASSENA)

If TRUE, it allows the use of @@PASSWD on systems with Fundamental Security

or Security Level 1 or 2. The default is FALSE. It can be changed dynamically.

• std_mfd_modified_swtime (MFDMSWTIME) and shared_mfd_modified_swtime

(MFDSHMSWTIME)

Specifies the timestamp format for the MFD. The configuration parameters

indicate whether TDATE$ or Modified-SWTIME format times are used when

creating new timestamps in the standard or shared MFD. This release only allows

the TDATE$ setting for these parameters. A future release will allow the

parameters to be set to use the Modified-SWTIME format. However, the value of

these parameters may now be retrieved and used by programs that create

timestamps to determine the correct timestamp format to use.

• accounting_modified_swtime (ACCTMSWTIME)

Specifies the timestamp format used for the Summary Accounting file. The

configuration parameter indicates whether TDATE$ or Modified-SWTIME format

times are used when creating new timestamps in the Accounting file. This release

only allows the TDATE$ setting for this parameter. A future release will allow the

parameter to be set to use the Modified-SWTIME format.

Migrating from a Nonmetered System to a Metered System

4–18 7831 0349–046

• freespace_modified_swtime (FSMSWTIME)

Specifies the timestamp format used for the TIP Freespace complex. The

configuration parameter indicates whether TDATE$ or Modified-SWTIME format

times are used when creating new timestamps in the TIP Freespace complex. In

addition to this system level configuration parameter, the TIP Freespace

application level parameter MSWTIM must also be enabled before

Modified-SWTIME timestamps are generated in a Freespace application group.

This release only allows the TDATE$ setting for the MSWTIM parameter. A future

release will allow the MSWTIM parameter to be set to use the Modified-SWTIME

format.

4.2.2. 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!

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.

Log Entry Changes

7831 0349–046 4–19

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, 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 49R2

• Log entry 101 "Program" is incremented to version 8 and appended with counts of

ER TDATE$ and ER DATE$ use.

• Log entry 107 "Run Termination" is incremented to version 8 and appended with

counts of ER TDATE$ and ER DATE$ use.

• Log entry 401 "Arbitrary Device/File" is incremented to version 4 and changes the

file assign and catalogue times into DWTIME$ format with a UTC base.

• Log entry 403 "Fixed Mass Storage File" is incremented to version 6 and changes

the file assign, catalogue and first write/unload times into DWTIME$ format with a

UTC base.

• Log entry 405 "Tape File" is incremented to version 7 and changes the file assign

and catalogue times into DWTIME$ format with a UTC base.

• Log entry 407 "Removable Mass Storage File" is incremented to version 5 and

changes the file assign, catalogue and first write/unload times into DWTIME$

format with a UTC base.

• Log entry 499 “FREESPACE Application Configuration” is incremented to version 3

and the Freespace application configuration parameter MSWTIM update flags and

before/after values are added.

• Log entry 602 "SW-detected Error Log Entries” is incremented to version 2 and

changes all pack and MFD, last reference and catalogue times to DWTIME$ format

with a UTC base.

Log Entry Changes

4–20 7831 0349–046


Exec Level 49R1

The common log header has changed. The log header version is incremented to 2. The

log timestamp is changed to a UTC base. The thread identifier and caller identifier are

now based on UTC time.

Log entry 205 replaces log entry 203 for logging of console messages.

The following log entries have changed:

• Log entry 71 "System Date and Time" is incremented to version 3 and appended

with UTC time and the PDB time configuration data.

• Log entry 101 "Program" is incremented to version 7 and appended with UTC time.

• Log entry 103 "TIP Program Termination" is incremented to version 15 and changed

to use UTC time.

• Log entry 106 "Run Identification" is incremented to version 6 and appended with

UTC time.

• Log entry 107 "Run Termination" is incremented to version 7 and appended with

UTC time.

• Log entry 110 "TIP Session Control" is incremented to version 4 and appended with

UTC time.

• Log entry 203 "Console Message" has been deleted and replaced with log entry

205.

• Log entry 401 "Arbitrary Device/File" is incremented to version 3 and appended

with UTC time.

• Log entry 403 "Fixed Mass Storage File" is incremented to version 5 and appended

with UTC time.

• Log entry 405 "Tape File" is incremented to version 6 and appended with UTC time.

• Log entry 407 "Removable Mass Storage File" is incremented to version 4 and

appended with UTC time.

• Log entry 461 "Unauthorized Media Manager Function" is incremented to version 2

and changed to UTC time.

• Log entry 612 "Fatal System Error" is incremented to version 2 and appended with

UTC time.

• Log entry 801 "Security Message" has a change in one of the messages to include

a time zone at the end of the message.

• Log entry 1007 "Dayclock Control" is incremented to version 4 and changed to

contain all UTC times.

• Log entry 1008 "Dayclock Syncronization" is incremented to version 3 and changed

to contain all UTC times.

• Log entry 1271 "SCIOP/SIOP Error" is incremented to version 2 and changed to use

UTC time.

XPC-L

7831 0349–046 4–21

• Log entry 1351 "IOP Fault" is incremented to version 4 and changed to use UTC

time.

• Log entry 1353 "NIOP Hardware Error" is incremented to version 3 and changed to

use UTC time.

• Log entries 1361, 1362, 1363, 1364 "SCIOP/SIOP Fault" are incremented to version 2

and changed to use UTC time.

• Log entry 1411 "UPI Timeout" is incremented to version 2 and changed to use UTC

time.

• Log entry 1601 "XPC Execution" is incremented to version 2 and changed to use

UTC time.

• Log entry 1602 "XPC UPI Message Block" is incremented to version 3 and changed

to use UTC time.

• Log entry 1603 "XPC UPI Status Block" is incremented to version 2 and changed to

use UTC time.


Exec Level 48R9

Log entry type 16006 is defined to allow the logging of commands processed by the

TIP utility TPUR.

4.5. XPC-L

The XPC-L (Extended Processing Complex-Locking) is the current 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

This subsection provides information about the following:

• Tape (see 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)

Tape and DVD

4–22 7831 0349–046

• T10000A tape subsystem (see 4.6.10)

• T9840D and T10000A applicable (see 4.6.11)

• T9940B tape subsystem (see 4.6.12)

• CSC and ACSLS (see 4.6.13)

• DVD (see 4.6.14)

• Virtual Tapes (see 4.6.15)

4.6.1. Tape

This subsection provides information on enhancements to the assign mnemonics,

coexistence with other cartridge tape subsystems, and fast tape access.

Tape Mnemonics

Table 4–1 describes the assign mnemonics.

Note: The U47M and U47LM assign mnemonics have not changed with this

release. All assign mnemonics are described in the Executive Control Language (ECL)

and FURPUR Reference Manual.

Table 4–1. Tape Assign Mnemonics

Assign Mnemonic

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

Any available 18-track or 36-track

drive (for example 5073, CTS5236)

HICL All 18-track 1/2-inch

cartridge tapes

Any available 18-track drive (for

example, 5073)

HICM All 36-track 1/2-inch

cartridge tapes

Any available 36-track drive (for

example, CTS5136, CTS5236,

OST4890)

DLT70 All DLT 7000 cartridge

tapes

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

Tape and DVD

7831 0349–046 4–23

Table 4–1. Tape Assign Mnemonics

Assign Mnemonic

CONV EQUATE

Drive Allocated

HIS99B All HIS99B cartridge tapes Any available HIS99B tape drive

T10KA All T10000A cartridge

tapes

UT10KA

Any available T10000A cartridge

tapes

LTO

LTO3

LTO4

ULTO3, ULTO4

ULTO3

ULTO4

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 U47M will force the

assignment to a freestanding U47M drive.

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, an 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.

Tape and DVD

4–24 7831 0349–046

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.

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.

Tape and DVD

7831 0349–046 4–25

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 website.

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

Tape and DVD

4–26 7831 0349–046

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.

• 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.

Tape and DVD

7831 0349–046 4–27

• 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

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).

Tape and DVD

4–28 7831 0349–046

Considerations for the OST5136 tape subsystem are as follows:

• Due to device equipment mnemonics and file assignment mnemonics introduced


• 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.

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


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.

Tape and DVD

7831 0349–046 4–29

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.

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.

Tape and DVD

4–30 7831 0349–046

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.

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).

Tape and DVD

7831 0349–046 4–31

• 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.

• 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.

• 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.

Tape and DVD

4–32 7831 0349–046

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

Tape and DVD

7831 0349–046 4–33

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.

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.

Tape and DVD

4–34 7831 0349–046

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.

Restrictions Restrictions Restrictions 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.

Tape and DVD

7831 0349–046 4–35

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 when the T9840A attaches to the

host through SBCON channels.

Note: Throughout this subsection, wherever SCSI T9840A is mentioned, FCSCSI

T9840A also applies.

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.

Tape and DVD

4–36 7831 0349–046



• T9840A tapes are not compatible with any other ClearPath IX system tape device.

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

Device Types

IBM

9840/SBCON

“3590 Mode”

(32-bit capable)

Unisys

9840/SBCON

(with feature)

(32-bit capable)

Unisys

9840/SBCON

(without feature)

(22-bit capable)

Unisys

9840/SCSI or

FCSCSI

(32-bit capable)

Tape

Format

Read

Append

Read

Append

Read

Append

Read

Append

IBM 9840

(32-bit

Block ID)

OK OK OK OK Error1 Error

2 OK OK

Unisys

9840

(22-bit

Block ID)

OK up

to 22

bit

Error OK OK OK OK OK OK

Unisys

9840

(32-bit

Block ID)

OK up

to 22

bit

Error OK OK OK up

to 22

bit3

OK up

to 22

bit3

OK OK

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.

Tape and DVD

7831 0349–046 4–37

• 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.

− 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





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).

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 cartridges used with 18-track, 36-track, DLT, or CTS9940B tape drives.

Tape and DVD

4–38 7831 0349–046

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

1/2-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.

Tape and DVD

7831 0349–046 4–39

• 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.


is 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.

− 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






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.

Tape and DVD

4–40 7831 0349–046

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)Mixed Media Management (from Sun/StorageTek 95739, Rev YA)Mixed Media Management (from Sun/StorageTek 95739, Rev YA)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

Tape and DVD

7831 0349–046 4–41

Table 4–4. Cartridge Read/Write Capability

Compatibility Drive Model

T9840A T9840B T9840C T9840D

Read a cartridge

formatted by

T9840A and

T9840B

T9840A and

T9840B

T9840A,

T9840B, and

T9840C

T9840A,

T9840B,

T9840C, and

T9840D

Write or append

data to a cartridge

formatted by

T9840A and

T9840B

T9840A and

T9840B

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).

Tape and DVD

4–42 7831 0349–046

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.

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.

Tape and DVD

7831 0349–046 4–43

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

Tape Mark Buffering Phase II (BUFTAP) y y

Operator clean message y y

Media manager support y y

CKRS support y y

1Tape Alert Log Sense page is saved in the ESI log entry.

Tape and DVD

4–44 7831 0349–046

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).

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.


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.

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.

Tape and DVD

7831 0349–046 4–45

• 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




is 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.

• 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.

− 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



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

Tape and DVD

4–46 7831 0349–046

• 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.

4.6.13. CSC and ACSLS

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.

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.

Tape and DVD

7831 0349–046 4–47

4.6.14. Software Delivery on DVD Media

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 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

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.

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.

Table 4–6. DVD Assign Mnemonics

Assign Mnemonic CONV EQUATE Drive Allocated

DVDTP None DVD

4.6.15. Virtual Tapes

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.

TIP

4–48 7831 0349–046

4.7. TIP

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.

• 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.


• A new Freespace file attribute (RDQ - Record Depletion Query) is defined which, if

specified, will prevent the read and reply system console message from being

generated when a request is made for a Freespace record type for which no

records are available. The request will instead immediately receive an FCSS error

status 046 indicating that no records are available for the requested record type.

The TIP utility FREIPS is updated to allow the setting/clearing and displaying of the

RDQ Freespace file attribute. In an XTC environment, updates of the RDQ

Freespace file attribute are broadcast to all hosts in the XTC environment.

For more information, see Section 6.4, “FREIPS Parameters for Freespace Files” in

the Transaction Processing Administration and Operations Reference Manual

(7830 7881).

• A new Freespace application group dynamic configuration parameter is defined

(MSWTIM) along with a new dynamic EXEC configuration parameter

(freespace_modified_swtime). Both of these dynamic configuration parameters

initially default to FALSE. The TIP utility FREIPS is updated to define and display the

new Freespace application configuration parameter MSWTIM. Modification of the

MSWTIM parameter is not allowed in this release (its value will be FALSE/NO).

When able to be set to TRUE/YES in a future release, all new timestamps in the

corresponding TIP Freespace application group will be generated in

Modified-SWTIME format (this assumes the EXEC global

freespace_modified_swtime configuration parameter has also been enabled on

the system).

For more information, see Section 6.4, “FREIPS Parameters for Freespace Files” in


(7830 7881).

TIP

7831 0349–046 4–49


• For release 15.0, the TIP Session Control (TSC) session file and the TSC session file

entries are expanded. When the application is initialized for release 15.0, the

release 14.0 or higher PSFUTIL automatically expands the TSC session file. If a

crossboot back is done to release 14.0, the PSFUTIL automatically reduces the size

of the TSC session file when the application is initialized.

• A new TIP VALTAB indicator option (IND,T) is defined. If specified, the TIP

transaction’s wall clock time starts accumulating when its associated input

message is queued (instead of when the TIP transaction copy becomes active on

the system). If the “T” VALTAB indicator option is set for a transaction, a queued

TIP input message (scheduling request) for the transaction receives a newly

defined TIP scheduling error (011) when de-queued and if the following conditions

are also met:

− The TIP FLAGBOX bit MAXTIMENQ is set (enabled) on the system.

− The input message’s queue time exceeds the TIP transaction’s specified

maximum wall clock time (indicated by the VALTAB keyword “TIM”).

For more information, see Section 11.3.21, “VALTAB Indicator Field – IND Keyword”

and Section 11.3.37, “Time (wall clock) Field – TIM keyword,” in the Transaction

Processing Administration and Operations Reference Manual (7830 7881).

• A new dynamic EXEC configuration parameter called “tip_view_print” (static name

“TIPVIEWPRINT”) is defined. If this EXEC configuration parameter is set to “TRUE”,

all TIP print files that are generated on the system will be generated with standard

file names (this allows TIP print file contents to be viewed with standard file

editors).

For more information, see Section 10.1, “Basic TIP Configuration Parameters,” in

the Exec System Software Installation and Configuration Guide (7830 7915).

• A new system console “TP” keyin (TP XL) is defined which allows the display of

information about shared (XPC-L) FCSS locks which have runs or TIP transactions

queued to them. The information displayed about shared locks includes the host

identifier and RUNID of lock owners.

For more information, see Section 11.84.7, “TP XL Keyin,” in the Exec System

Software Operations Reference Manual (7831 0281).

• A new FREESPACE application configuration parameter called “NODSC” (no

discard) is defined. If this configuration parameter is set to “YES” for the

FREESPACE application, deferred release FREESPACE items will not be discarded.

For more information, see Section 6.4, “FREIPS Parameters for Freespace Files,” in


(7830 7881).

Software Controlled Performance (SCP)

4–50 7831 0349–046

• A new dynamic EXEC configuration parameter called “tip_fs_message_limit” (static

name “TIPFSMSGLMT”) is defined. This EXEC configuration parameter can be used

to control the maximum number of FREESPACE messages that will be displayed

on the system console over a six second interval.

For more information, see Section 10.1, “Basic TIP Configuration Parameters,” in

the Exec System Software Installation and Configuration Guide (7830 7915).

• A new TPM (TIP Performance Monitor) optional area called “L$MISC” is defined

for the TIP transaction TPM termination summary record. Enabling the collection of

this TPM area causes additional information to be collected for and logged as part

of TIP transaction termination summary record.

For more information, see Section 18.5.3, “TPM System Records – Type 015

Records,” in the Transaction Processing Administration and Operations

Reference Manual (7830 7881). The content related to L$MISC area is documented

under the heading “Miscellaneous Data Area”.


A new TIP FLAGBOX bit named “TPURLOG” is defined which, if enabled, will result in

commands processed by the TIP utility TPUR being logged to the system log trail (log

entry type 16006). The new log entries will identify the run (userid) that performed the

TPUR command, the TPUR command performed and HVTIP library(s) and bank(s)

involved, and the completion status and any status text generated.

For more information about TPUR command logging system log entries, see the

System Log Operations and Support Reference Manual Volume 2 (3839 6347).

A new TIP file attribute “TPM” is defined which can be dynamically enabled or disabled

for a TIP file via the TIP utility FREIPS change (CHA) command. If the TPM attribute is

specified on a TIP file and the L$FCSS selection bit is enabled (non-mandatory mode),

TPM L$FCSS log entries will be generated for all FCSS functions performed on the TIP

file by demand/batch programs or TIP transactions. The FREIPS list file directory (LFD)

function can also be used to list TIP files which have the TPM attribute enabled.

For more information about the TIP file TPM attribute see the Transaction Processing

Administration and Operations Reference Manual (7830 7881).

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 System Software

Administration Reference Manual.

POSTOEXMSTR

7831 0349–046 4–51

An Image Enabler is an SCP Exec key tape or file used for activating a performance

image on a ClearPath server.

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 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, 4200, 4300, and 6300 Series systems, the MCN is the

seven-character OEM Cell Service Tag.

• For Dorado 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.

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.

POSTOEXMSTR

4–52 7831 0349–046

To use the utility, place the name of a preassigned tape containing the Exec release

master files on the utility call line, for example:

@ASG,TJ tape-file.,type,reel-num

@SYS$LIB$*SOLAR.POSTOEXMSTR tape-file.

or

@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.

7831 0349–046 5–1

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.

Unisys supports crossbooting between currently supported levels, 14.0, 15.0 and 16.0.

Unisys does not provide code to support crossbooting between 13.x and the

supported releases.

If you are migrating from release 14.0, you must migrate your system to all release

14.0 products before migrating to release 16.0. Starting from a stable 14.0 base

reduces the risk of unexpected problems during the migration to 16.0 and DSTA.

Refer to Table 5–1 for a summary of products in the release 16.0 that introduce

compatibility or migration issues.

Refer to Table 5–2 for a summary of products in the release 15.0 that introduce

compatibility or migration issues.

Summary of Considerations

5–2 7831 0349–046

5.1. Summary of Considerations

This section includes two tables that detail compatibility and migration considerations

for the changes in release 16.0 and also the changes that were introduced in release

15.0. If you are migrating from release 15.0, you have already addressed the

considerations noted in Table 5–2. If you are migrating from release 14.0, you will need

to carefully review the information listed in both the Table 5–1 and Table 5–2 to

address compatibility and migration issues that might affect you.

Table 5–1 summarizes the compatibility and migration consideration for all sites

migrating to the ClearPath OS 2200 release 16.0 and references the subsection that

contains more information.

Table 5–1. Summary of Release 16.0 Considerations

Installation and Support Name Type of Consideration Subsection

APEX Compatibility and Migration 5.2

CIPHER-API Compatibility and Migration 5.5

CITA Compatibility 5.6

CPComm Migration 5.10

CPCommOS Compatibility and Migration 5.11

CryptoLib Migration 5.14

DPS Compatibility 5.16

INFOAccess Compatibility and Migration 5.36

Interconnect Compatibility and Migration 5.27

IRU Compatibility and Migration 5.25

MAP Compatibility 5.32

PAR Compatibility 5.52.5

RDMS Compatibility 5.40

Security-Admin Compatibility 5.44

SP-OPERATION Compatibility and Migration 5.47

SYSLIB Compatibility and Migration 5.49

UCOB Compatibility 5.53

UREP Migration 5.56

URU-OS2200 Compatibility 5.57

WMQ2200 Compatibility and Migration 5.59

Summary of Considerations

7831 0349–046 5–3

Table 5–2 summarizes the additional compatibility and migration consideration for

sites migrating from the ClearPath OS 2200 release 14.0 and references the

subsection that contains more information.

Table 5–2. Summary of Release 15.0 Considerations

Installation and Support Name Type of Consideration Subsection

CIFS Compatibility 5.4

Cipher Compatibility and Migration 5.5

CMR Migration 5.8

CPCommOS Compatibility 5.11

CryptoLib Compatibility 5.14

EOM Migration 5.20

FLEX Compatibility 5.23

IRU Compatibility and Migration 5.25

Interconnect Compatibility and Migration 5.27

JPJVM Migration 5.28

J2EE-CON-OS2200 Compatibility 5.29

MCB Compatibility 5.33

MSMQI Compatibility and Migration 5.34

NTSI Compatibility 5.35

INFOAccess Compatibility and Migration 5.36

RDMS-JDBC Compatibility 5.41

URTS Compatibility 5.43

SP-OPERATION Compatibility and Migration 5.47

SSG Compatibility 5.48

TeamQuest Baseline® Migration 5.52.1

TeamQuest® LA Migration 5.52.2

TeamQuest Online® Migration 5.52.3

TeamQuest® OSAM Migration 5.52.4

TeamQuest® PMLog Migration 5.52.6

TeamQuest® SAUTILITIES Compatibility and Migration 5.52.7

TeamQuest® TIP-LA Compatibility and Migration 5.52.8

URU-OS2200 Compatibility 5.57

WMQ2200 Compatibility and Migration 5.59

APEX

5–4 7831 0349–046

5.2. APEX


APEX Level 2.0

Compatibility

Apex requires the SLIB 2R1 and SYSLIB 77R1 products that are delivered with this

ClearPath release. Apex requires the FLEX product from Release 15.0 or later.

Migration

The OS 2200 Apex agents should be upgraded before the IIS web applications to allow

for new functionality.

5.3. 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 website:

http://www.support.unisys.com/common/welcome.aspx?pla=MAP&nav=MAP

5.4. CIFS


Business Backward migration to a previous CIFS level is not recommended.


CIFS Level 8R1

Compatibility

The security requirements for the User-Id that owns the CIFS subsystem file have

changed. Beginning with the ClearPath OS 2200 release 15.0, that User-Id should be

given the SSLOGER privilege.

The SMB Message Signing capability is not functional for clients using Windows

network credentials to log into OS 2200 through ASIS/NTSI. To work around the issue,

either clients must present native OS 2200 credentials, or SMB signing must be

inhibited by setting the CIFS background run’s CIFS$SIGNSMB environment variable to

DISABLED.

Cipher API

7831 0349–046 5–5

5.5. 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).


Cipher API Level 2R4A

Compatibility

• Cipher API level 2R4A is fully compatible with previous levels.

• Cipher API 2R4 and 2R4A command line no longer support parameters supplied in

a program file element. All parameters must be on the command line.

Migration

The OS 2200 Cryptographic Library (CryptoLib) must be installed for Cipher API to run.

Levels of Cipher API earlier than 2R1 did not require CryptoLib.


Cipher API Level 2R4

Compatibility

• Cipher API level 2R4 is fully compatible with previous levels.

• Cipher API 2R4 command line no longer supports parameters supplied in a

program file element. All parameters must be on the command line.

Migration


Levels of Cipher API earlier than 2R1 did not require CryptoLib.

CITA

5–6 7831 0349–046


Cipher API Level 2R3

Compatibility

Cipher API 2R3 is fully compatible with previous levels.

Migration


Levels of Cipher API prior to 2R1 did not require CryptoLib.

Installing level 2R3 replaces the default configuration tables. If a customer has made

site-unique changes to the configuration tables in level 2R2 and wishes to keep those

changes, he or she must make those changes again after installing level 2R3. Because

each configuration file is very small, the manual update is simple.

5.6. CITA


CITA Level 2R4A

Compatibility

CITA level 2R4A should be used with systems beginning with release 15.0, or apply

the CHG attached to PLE 19024733. This ensures a successful analysis of any CITA

dump that is taken, due to the DIAG$ format change introduced in release 15.0.


CITA Level 2R4

Migration

The CITA COMUS build has some changes.

The following queries no longer appear in the CITA COMUS BUILD routine:

• BUILD printout: tape or printer - <T>/P ?

• LIST - reel/file./NONE/<> ?

− No longer needed because the build printout is always saved to the

NEWMASTER tape unless ‘NONE’ is specified when queried for the

NEWMASTER tape.

• Should the symbolics be saved - <Y>/N ?

− No longer needed because the symbolic output is always saved to the


NEWMASTER tape.

Checkpoint/Restart (CKRS)

7831 0349–046 5–7

If you want to retain the previous handling of the SO file and print file, you can use the

COMUS CO$ADDSTATEMENTS SGS, entered as a permanent or additional SGS in the

CITA COMUS build.

Example:

CO$ADDSTATEMENTS BEFORE-SAVE,ADDTHIS

ADDTHIS ‘ ‘@COPY SO.,<your-file.>’ ‘


ADDTHIS ‘ ‘@SYM,U CITA$PRT$.,,<print-queue>’ ‘

Note: You must register the CITA 2R4 release tape with your COMUS database

to pick up this feature.

5.7. 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.8. CMR


CMR Level 3R1

Migration

This version of CMR is necessary due to the new Type-205 log entry.

Migration to CMR level 3R1 must be concurrent with migration to Exec for ClearPath

OS 2200 release 15.0. CMR level 3R1 does not work with Exec levels earlier than

release 15.0, nor do CMR levels earlier than 3R1 work with the Exec in ClearPath

OS 2200 release 15.0.

COMAPI

5–8 7831 0349–046

5.9. 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.


COMAPI Level 8R1

Migration

The COMAPI build process has some changes.

The following queries no longer appear in the COMAPI COMUS BUILD routine:





NEWMASTER tape.




NEWMASTER tape.



COMAPI COMUS build.

Communications Platform (CPComm)

7831 0349–046 5–9

Example:




ADDTHIS ‘ ‘@SYM,U COMAPI$PRT$.,,<print-queue>’ ‘

Note: You must register the COMAPI 8R1 release tape with your COMUS database

to pick up this feature.

5.10. 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.

When installing a new level of Communications Platform into any of the modes A - H,

you must also install the Communications Platform mode AFCB. New entry points are

sometimes introduced in new levels of Communications Platform. Following this

install sequence prevents undefined references from occurring.


CPComm Level 6R5

Migration

Levels of Communications Platform prior to 6R5 made available and, by default, used

all versions of the SSL/TLS protocols supported by Communications Platform. Security

experts have determined that the SSL version 3.0 protocol contains serious

vulnerabilities that allow for bypassing its protections. Therefore, Unisys recommends

that sites use the SSL version 3.0 protocol only in circumstances that make use of the

protocol necessary, such as when a peer system does not support any newer

protocol versions. Starting with level 6R5, Communications Platform does not allow or

use by default the SSL version 3.0 protocol unless the site administrator specifically

names SSLV3.0 on an SSL/TLS-SECURITY configuration statement.

Communications Platform for Open Systems (CPCommOS)

5–10 7831 0349–046


CPComm Level 6R3

Migration

The CPComm build process has some changes

The following queries no longer appear in the Communications Platform COMUS

BUILD routine:





NEWMASTER tape.




NEWMASTER tape.



Communications Platform COMUS build.

Example:




ADDTHIS ‘ ‘@SYM,U CPCOMM$PRT$.,,<print-queue>’ ‘

Note: You must register the Communications Platform 6R3 release tape with your

COMUS database to pick up this feature.

5.11. Communications Platform for Open Systems

(CPCommOS)


CPCommOS Level 4R5

Compatibility

To enable the SSL/TLS improvements feature, you must have both of the following:


• The version of XNIOP that is released with the Dorado 4300 or 6300 Servers, or a

newer level of XNIOP

Communications Platform for Open Systems (CPCommOS)

7831 0349–046 5–11

To enable the FIPS 140-2-Validated SSL/TLS feature, you must have all of the following:


• The version of XNIOP that is released with the Dorado 4300 or 6300 Server

Firmware 1.1, or a newer level of XNIOP

• A Dorado 4300 or 6300 Server or newer system

Migration

Levels of Communications Platform for Open Systems prior to 4R5 made available

and, by default, used all versions of the SSL/TLS protocols supported by

Communications Platform for Open Systems. Security experts have determined that

the SSL version 3.0 protocol contains serious vulnerabilities that allow for bypassing

its protections. Therefore, Unisys recommends that sites use the SSL version 3.0

protocol only in circumstances that make use of the protocol necessary, such as when

a peer system does not support any newer protocol versions. Starting with level 4R5,

Communications Platform for Open Systems does not allow or use by default the SSL

version 3.0 protocol unless the site administrator specifically names SSLV3.0 on an

SSL/TLS-SECURITY configuration statement.


CPCommOS Level 4R4

Compatibility

To enable the insecure connection prohibition feature and the TRACEROUTE user

command feature, you must have

• Communications Platform for Open Systems version 4R4.

• The version of XNIOP that is released with the Communications Platform for Open

Systems 4R4 media, or a newer level of XNIOP.

The STATUS BOND and STATUS NIC-INTERFACE user commands are not supported

on Dorado 4000 systems.


CPCommOS Level 4R3

Compatibility

• The Network Packet Capture feature is only available on Dorado 4100 and Dorado

4200. This feature is not available on Dorado 4000.

Migration

• Refer to Table 3-4 for plateau dependency considerations.

• The CPCommOS Network Packet Capture feature requires XNIOP level 5.27 or

higher.

COMUS

5–12 7831 0349–046

• The CPCommOS build process has some changes.

The following queries no longer appear in the Communications Platform for Open

Systems COMUS BUILD routine:





NEWMASTER tape.




NEWMASTER tape.

If you want to retain the previous handling of the SO file and print file, you can use

the COMUS CO$ADDSTATEMENTS SGS, entered as a permanent or additional SGS

in the Communications Platform for Open Systems COMUS build.

Example:




ADDTHIS ‘ ‘@SYM,U CPCOMOS$PRT$.,,<print-queue>’ ‘

Note: You must register the Communications Platform for Open Systems 4R3

release tape with your COMUS database to pick up this feature.

5.12. 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.

cpFTP

7831 0349–046 5–13

• 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.

5.13. 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 4R1

Compatibility

This release changes behavior of PASV_PORT configuration parameter. The

PASV_PORT configuration parameter change to be effective in both Secure and

NonSecure CryptoLib.

CryptoLib

5–14 7831 0349–046

5.14. CryptoLib


CryptoLib Level 1R3 (rollover)

Migration

Starting with ClearPath OS 2200 release 16.0, only the NOTFIPS mode is installed when

using the CP-FLD tape. Previous ClearPath OS 2200 releases have installed mode FIPS

from the CP-FLD tape. If FIPS certification is required, you must install mode FIPS on

your system using the CryptoLib release tape.


CryptoLib Level 1R3

Compatibility

If FIPS certification is required, you must use install modes FIPS or FIPSTEST.


CryptoLib Level 1R2

Compatibility

Additional installation modes of CryptoLib are now available so a user can choose to

install the latest uncertified version of CryptoLib, if desired. The FIPS certified version

remains the default install mode. If FIPS certification is not required, using the

uncertified version provides the latest CryptoLib features and fixes, and ensures

improved performance. If FIPS certification is required, DO NOT install modes NOTFIPS

or NOTFIPSTEST on your system.

5.15. DMS-RA


DMS-RA Level 4.1

Compatibility

DMS-RA 4.1 requires use of Java SE 7 or higher Runtime Environment. In addition, to

use the ANT scripts provided with the DMS-RA, Apache ANT 1.8.4 or higher must be

used.

A subschema that is used to provide Java access to DMS data must be processed with

the ClearPath 14.0 version of the SDDL processor, DMS 21R3, or above, to be

compatible with DMS Resource Adapter 4.1.

DPS

7831 0349–046 5–15

5.16. DPS


DPS Level 6R6

Compatibility

If you use WebTS 6R1 JavaClient and install DPS level 6R6, you must also incorporate

WebTS procedural changes to enable the use of signed applets. Refer to the Web

Enabler for Display Processing System User’s Guide for more information.


DPS Level 6R5B

Migration

Beginning with DPS 6R5B, ePortal developers must generate new CONNECTOR

working storage/message format for every DPS screen that was previously generated

and used with DPS 6R5 or 6R5A. In addition, the resulting COBOL structures must be

imported into the ePortal Developer projects using the import wizard. Not doing so can

cause a mismatch with the message/record format in the DPS run-time system,

generating errors on transaction input, or ePortal receiving unrecognizable data on

transaction output. It is highly recommended that ePortal users upgrade to ePortal 5.0

for use with DPS 6R5B.

CONNECTOR working storage/message format for DPS 6R5B now contains data fields

for DPS check number and DPS special fields.

The DPS 6R5B common I-bank DPS$BK2 has expanded. The new address limits of this

bank are 01000 - 040777. Previously, the upper limit was less than 040000. The larger

size of DPS$BK2 increases the chance that programs that call DPS can have address

overlap conflicts between their own banks and DPS$BK2. The conflict is most likely to

occur with D-banks, as the collector uses 040000 as the default lower address limit for

D-banks. The bank overlap most likely causes program guard modes, but there may be

other unpredictable errors or program behavior.

To resolve the address overlap conflicts, the affected programs are recommended to be

re-collected or re-linked with conflicting bank addresses starting at 044000 or above.

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

5–16 7831 0349–046

5.17. 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.

• DDP-FJT 5R5K requires IRU 22R1 to be installed with mode FSAH.

Refer to the SYS$LIB$*DDP-FJT-3.README element for additional release

documentation.

5.18. 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.

ELMS

7831 0349–046 5–17

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

• 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.

5.19. ELMS

The consideration for ELMS is that you must install I18NLIB before you attempt to use

ELMS.

5.20. Enterprise Output Manager (EOM)


EOM Level 11.0

Migration

A continuation of Enterprise Output Manager 10.0. All prior levels, that are currently

supported, can be migrated to Output Manager 11.0.

EOM 11.0 requires IRU 22R1 to be installed with mode FSAH.

Enterprise Relational Database Server (RDMS)

5–18 7831 0349–046


EOM Level 10.0

Migration

A continuation of Enterprise Output Manager 9.1. All prior levels of Output Manager

can be migrated to Output Manager 10.0.

5.21. Enterprise Relational Database Server (RDMS)


RDMS Level 18R1

Compatibility

RDMS 18R1 expands support of double bounded search keys from supporting only

predicates of the form: COLUMN <op> CONSTANT . RDMS now supports:

Table1.COLUMN <op> Table2.COLUMN, COLUMN <op> ARITHMETIC/BIF. This change

is performed by the optimizer. If you are using ESQL, you will need to recompile the

program to take advantage of this access path optimization. If you are using dynamic

or interactive SQL, you may see a different access path.

Migration

SYSDATE and SYSTIMESTAMP are now reserved words. Objects (for example, table

names, column names, and so on) by these names must be renamed. To rename a

column, use the ALTER TABLE RENAME COLUMN statement.

COBOL and C programs containing either STATIC or DYNAMIC ESQL which are

compiled using RDMS 18R1, and triggers, stored procedures, and functions created

using RDMS 18R1, may not be executed using an earlier level of RDMS.

FAS

7831 0349–046 5–19

5.22. FAS


FAS Level 10R6

Compatibility

The following consideration was introduced by FAS CHG 1881. FAS 10R6 is the first

level of FAS released with this CHG.

The MFD file selection CRITERIA processing and the BACKUP CRITERIA=DIRECTORY

command have been modified from using internal FAS routines to using calls to the

SYSLIB MFDSP$ routines. This may introduce some minor compatibility differences.

This is mainly because the internal FAS routines examined the files in the MFD in Main

Item order, while the calls to the MFDSP$ routines examine the files in the MFD in

Lead Item order. In most cases the differences would only be apparent if FAS listings

without and with this correction were compared side-by-side. The following

summarizes the possible differences:

• Even though the selected files are sorted before they are processed by a FAS

command, the difference in the original order may result in a difference in the

sorted order. This depends on the files and the FAS command being processed.

For instance, the BACKUP command may back up loaded mass storage files in a

different order to output volumes.

• MFD error and warning messages that are displayed on file validation errors when

the M option is not specified may appear in a different order.

• Identical MFD error and warning messages are not guaranteed because some of

the validation occurs in the MFDSP$ routines instead of in the FAS routines. The

code changes attempt to minimize these differences by mapping MFDSP$ error

codes to existing MFD error messages.

• Errors in either the MFD structure or the retrieval of MFD items result in new error

messages. The possible new error messages are:

*ERROR* - MFD size exceeds the available buffer space.

*ERROR* - MFDSP$ error. A2: <a> A3: <b>

A4: <c> A5: <d>

*WARNING* - MFDSP$ detected <a> error(s) with error code(s)

0[, ...] for [ Lead Item(s), ][ Main Item(s), ]

[ DAD Item(s), ][ SFE Item(s)].

FLEX

5–20 7831 0349–046

5.23. FLEX


FLEX Level 4R4

Compatibility

To use Apex and Configured Password Profiles, the ASIS subsystem owner User-Id

(-ASIS-) requires the SSREADEXEC privilege in order to read the name of the Security

Officer from the Exec configuration. Beginning with the ClearPath OS 2200 release

15.0, that User-Id should be given the SSREADEXEC privilege.

5.24. 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.

HTPIC-2200

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.

Integrated Recovery Utility (IRU)

7831 0349–046 5–21

5.25. Integrated Recovery Utility (IRU)


IRU Level 22R2

Compatibility

VERIFY Command Output Changes:

VERIFY command output changed in this release.

The label "MESSAGE BLOCKS" is no longer displayed. This label reflected the

combination of MCB subtype 1 and 2 audit records. Instead,

• Subtype 1 MCB audit records are now displayed next to the label "MESSAGES"

• Subtype 2 MCB audit records are now displayed next to the label

"CONTINUATION/OVERFLOW"

MCB Idle Point and User subtypes continue to be displayed as they have in the past.

The heading "DATA REPLICATION RECORDS" replaces "DATA CAPTURE RECORDS". In

addition, the line item tags have been updated to reflect work being done for Data

Exchange and other possible applications for the records formerly used in Data

Capture.

Configuration Parameter Changes:

ABSOLUTE-DEVICE is no longer allowed for ASSUME or REPORT CONFIG.

REPORT CONFIG ALL output changed to report the two new parameters and remove

reporting TAPE-TYPE-OVERRIDE and ABSOLUTE-DEVICE.

REPORT CONFIG TAPE-TYPE-OVERRIDE now displays both new parameters. REPORT

CONFIG MAX-GROUP or NORING-CONFIGURED now displays OBSOLETE.

Setting TAPE-TYPE-OVERRIDE to an absolute device or control unit when the B-option

is specified now results in a warning.

Removing the APPREC Component:

The removal of APPREC as an IRU component prompted a change to the build

questions beginning in this release. IRU build sequence no longer asks about basic

mode PLUS compilers, as these were used only for APPREC which is no longer part of

IRU. The following prompts have been removed:

BM PLUS compiler filename – Q*F/<SYSLIB$*PLS> ?

BM PLUS library filename – Q*F/<SYSLIB$*PLS> ?

Migration

APPREC is no longer located in the IRU product or copied to the IRU system file during

IRU installation. Sites that require APPREC need to change the installation procedures

for this component; it is now a part of the Exec ARC component.


5–22 7831 0349–046


IRU Level 22R1

Compatibility

The IRU release tape contains a generic FSAH utility called IAP (IRU Audit Print). You

can use IAP to read the audit trail, or as an example for building your own audit

reading utility. The IAP utility in this level only supports new format audit trails. The

display fields have been adjusted for new record formats and time values. If you want

to read pre-DSTA audit trails you must use a previous version of IAP.

The IAP released with this version of IRU does not support audit trails generated by

release 14.0 or earlier Exec levels.

Information for generating and installing IRU has moved from the UDS documents to

the IRU Administration Guide.

Configuration parameters MAX-GROUP and NORING-CONFIGURED are renamed to

reflect their actual use. MAX-QUAL replaces MAX-GROUP, as this parameter controls

the number of qualifiers or UDS/TIP numbers you can have in a single IRU command.

TAPE-WRITEPROTECT replaces NORING-CONFIGURED as a clearer name for the

function it performs. The build routine location of these parameters did not change,

and ASSUME and REPORT CONFIG commands accept both old and new names. The

full config report has the new names in alphabetic order, so some of the other

parameters shifted to accommodate this change.

Migration

This is a list of migration changes due to the Daylight Saving Time Adapt (DSTA). See

the Mandatory Migration Actions for ClearPath OS 2200 Release 15.0 and Higher

(8222 3777) for a complete list of dynamic time shift and DSTA issues.

While you can migrate XTC systems to the Exec 49R1 one host at a time, you must

complete migration of all hosts participating in a concurrent application group before

performing a seasonal time shift. IRU uses the current zone and seasonal offsets to

adjust times for comparison between different format timestamps in the old and new

Exec levels.

Be aware that the MOVE tape format reflects the format of the audit trail being

archived. Since the audit trail format changes when you migrate to the DSTA level of

Exec, the move tape format will also change at that time.

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 FSAH 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.


7831 0349–046 5–23

If you have a utility that alters IAP code (i.e. applies a local change to the IRU IAP code

base), be aware that major structural revisions were made to the IAP code in this

release.

If you move up to release 15.0 Exec and create any audit trails or move tapes that you

want to continue being able to use, you must remain on IRU 22R1 or higher if you drop

back Exec levels.

Release 15.0 IAP can only interpret release15.0 audit trail records. You should execute

the version of IAP that matches the trails you are reading.


IRU Level 21R1

Compatibility

FSAH Enhancements

There is a new set of FSAH packets - version 6. FSAH still supports packet versions 4

and 5. New fields and features are available only when the version is set to 6.

Setup and read packets have new fields for enhanced return codes. Existing return

status codes are unaltered, new codes are provided in addition to the existing status

values.

While the codes are unaltered, the size of the setup and read return status fields was

reduced, with the sub-status added to the upper half of the original field. Programs

that do not use the FSAH packet definitions provided on the release tape must change

to use the proper field size before moving up to version 6 packets.

An auto-answer flag was added to the setup packet. If you set this flag, batch

programs no longer issue messages to the console; all messages will go only to the

print file.

FSAH interprets values in the setup packet trail-id field as a valid request for alternate

ALAT or COD trail numbers. These values are ignored in previous versions.

Setup packets now allow specification of the string $DEFAULT in place of a mass

storage filename. This value is interpreted as a request to use the default mass

storage file name (as opposed to using $DEFAULT as the name of the file).

The filter packet is updated to accommodate filtering by ALAT type. Existing filename

filters (overlaid by the new ALAT-type filter) can continue to be used unaltered.

Interactive Processing Facility (IPF)

5–24 7831 0349–046

Daylight Saving Time Adapt (DSTA)

The IRU release tape contains a generic FSAH utility called IAP. You can use IAP to

read the audit trail or as an example for building your own audit reading utility. The IAP

utility in this level does not support DSTA format audit trails. The utility reads only the

pre-DSTA format audit trails.

Be aware that the MOVE tape format reflects the format of the audit trail being

archived. Because the audit trail format changes when you migrate to the DSTA level

of Exec, the move tape format also changes at that time.

Migration

This is a list of IRU compatibility/migration issues. See section 3.4 for resources

containing detailed information about dynamic time shift and DSTA issues.

Although you can migrate XTC systems to the DSTA level of Exec one host at a time,

you must complete migration of all hosts participating in a concurrent application

group before performing a seasonal time shift. IRU uses the current zone and

seasonal offsets to adjust times for comparison between different format timestamps

in the earlier and current Exec levels.

FSAH applications must be able to handle new formats for records they expect to

encounter. FSAH converts packet fields to their appropriate to format but returns

audit records to the caller in whatever format exists on the audit trail being read. Note

that TDATE values in FSAH 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.

5.26. 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.27. Interconnect


Interconnect Level 1R4B

Compatibility

The 2200 component of Interconnect 1R4B is fully compatible with the 2200

component of 1R4.

Migration

You can migrate from Interconnect 1R4/1R4A to 1R4B on the 2200. No upgrade or

migration is required on the JProcessor or QProcessor.

JPJVM

7831 0349–046 5–25


Interconnect Level 1R4A

Compatibility

The 2200 component of Interconnect 1R4A is fully compatible with the 2200

component of 1R4.

Migration

You can migrate from Interconnect 1R4 to 1R4A on the 2200. No upgrade or migration

is required on the JProcessor or QProcessor.


Interconnect Level 1R4

Compatibility

The 2200 Interconnect product level 1R4 is upward compatible with levels 1R2 & 1R3.

It can be installed onto the 2200 independent of the products that utilize it. Application

programs will not require a recompile. If the Specialty Partitions have an image with

an Interconnect level lower than 1R4 then the new features are not available but

existing applications will continue to run. To take advantage of any new Interconnect

1R4 features, you will need to migrate WMQ2200 and JPJVM on both the 2200 and the

Specialty Partition to levels that pair with Interconnect 1R4.

Migration

WMQ2200 and JPJVM should be made inactive or shutdown before the Interconnect

installation to avoid having them abort during the install.

5.28. JPJVM


JPJVM Level 7.2

Migration

JPJVM-7.2 requires Interconnect 1R4A.

OS 2200 Transaction Resource Adapter for the Java™ Platform (J2EE-CON-

OS2200)

5–26 7831 0349–046

5.29. OS 2200 Transaction Resource Adapter for the

Java™ Platform (J2EE-CON-OS2200)


J2EE-CON-OS2200 Level 14.1

Compatibility

Fully compatible with J2EE-CON-OS2200 Level 14.0.


J2EE-CON-OS2200 Level 14.0

Compatibility

The OS2200Header class has changed to take advantage of the retain connection

feature and to allow variable bean name lengths. The new header Version "3" format is

defined in the OS2200Header class API. Two new subclasses have been created,

OS2200HeaderRev2 and OS2200HeaderRev3, for versions "2" and "3", respectively.

OS 2200 programs which invoke EJBs with inbound communications are

recommended to precede the EJB data with the Version "3" 72-byte header. COBOL

(SLHEADER.COBP) and C (SLHEADER.H) definitions for the Version "3" header can also

be found in the ExampleInbound\Client directory. The Version "2" header is deprecated

and will not be supported in a future release.

The OS2200Ejb3RemoteObject interface has changed: the os2200EjbService() method

no longer throws java.rmi.RemoteException. Your inbound EJB 3.0 beans must be

recoded to no longer throw java.rmi.RemoteException, and recompiled and

redeployed. See the API documentation for OS2200Ejb3RemoteObject interface and

the OS 2200 TIP Connector inbound EJB 3.0 samples for JBoss Enterprise Application

Platform (including JBOSS-2200), WebLogic Server, and WebSphere Application

Server.

5.30. 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.

Linking System (LINK)

7831 0349–046 5–27

5.31. 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.

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.

MAP

5–28 7831 0349–046

5.32. MAP


MAP Level 33R2

Compatibility

The "Provide New Collector-defined Symbols as TDATE$ Alternatives" feature

introduces six new Collector-defined symbols. If user definitions conflict with the new

Collector-defined symbols, then the user definitions always take precedence. Note

that Unisys recommends that users should not define names that end with a dollar

sign ($).

5.33. 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.


MCB Level 9R1

Compatibility

Migration to MCB level 9R1 must be concurrent with migration to Exec 49R1 for

ClearPath OS 2200 release 15.0. MCB level 9R1 does not work with Exec levels earlier

than release 15.0, nor do MCB levels earlier than 9R1 work with the Exec 49R1 in

ClearPath OS 2200 release 15.0.

Starting with MCB 9R1, the MCB RESILIENT configuration statement is ignored when

processing the MCB configuration. The RESILIENT configuration statement was used

in conjunction with PAEXEC, which is no longer orderable or delivered.

5.34. MSMQI


MSMQI Level 2R1C

Compatibility

Fully compatible with MSMQI 2R1B.

NTSI

7831 0349–046 5–29

Migration

Requires NTSI 7R3B.

5.35. NTSI


NTSI Level 7R3B

Compatibility

Fully compatible with NTSI 7R3A

5.36.ODBC Data Access (INFOAccess)


INFOAccess Level 9R3B

Compatibility

The Administrator, SQL Server and Modeller components can be installed on the same

system as 9R3 or any 9R3x or 9R2x version.

Beginning with version 9R3, the OLE DB component is no longer available on the

release media. Support for OLE DB was discontinued in version 9R2D.

Multiple versions of the ODBC Driver or ISQL can coexist on the same system. All

supported versions are cross compatible with any operating system components,

provided that the 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 9R3A

Compatibility


system as 9R3 or any 9R2x version.

Beginning with version 9R3, the OLE DB component is no longer available on the



supported versions are cross compatible with any operating system components,

provided that the TCP/IP port numbers are adjusted.

Open Distributed Transaction Processing (Open DTP) (OLTP-TM2200)

5–30 7831 0349–046

Migration

If a prior version of the ODBC Driver is to be updated, the DSNs created should be

deleted prior to uninstall.


INFOAccess Level 9R3

Compatibility


system as any earlier 9R2x version.

Beginning with this version, the OLE DB component is no longer available on the



supported versions are cross compatible with any OS components, provided that the

default TCP/IP port numbers are adjusted.

Migration

If an earlier version of the ODBC Driver is to be updated, the DSNs created should be

deleted before uninstalling it.

5.37. 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.

Refer to the Open Distributed Transaction Processing Administration Guide Volume

1 for installation instructions.

Open Programming Environment (OPE)

7831 0349–046 5–31

5.38. Open Programming Environment (OPE)

The OPE component IXS5000-OPE is removed from all IOE (Standard) and UOE

packages (Metered).

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.


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

these local addresses**

ip-address,127.0.0.3,sxtsab ;

ip-address,127.0.0.4,sxtsac .

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 Saving 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 saving 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.


5–32 7831 0349–046

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

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 saving 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









OSI-TP

7831 0349–046 5–33

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.

5.39. OSI-TP

Refer to the SYS$LIB$*XTP$$UTIL.README element for additional release

documentation, including information about how to use new features.

5.40. RDMS


RDMS Level 20R1

Compatibility

Application and/or test programs that currently fail with certain RDMS errors may

either process properly or fail with different errors because RDMS processes further.

Static ESQL statements, stored procedures, and triggers must be recompiled to get

the benefit of the optimizer conversion of constants.

The UREP migration install drops and recreates the RDMS Catalog views. You have to

recreate any stored procedures or triggers that use the RDMS Catalog views. You

should also recompile any COBOL or C programs with embedded SQL that reference

the RDMS Catalog views.

Current timestamp formats are still valid.

5.41. RDMS-JDBC


RDMS-JDBC Level 2.9

Compatibility

RDMS-JDBC 2.9 requires use of a Java 1.7 (Java 7) or higher Runtime Environment.

Both the RDMS JDBC client and server components must be updated and used

together.

Remote System Support (RSS)

5–34 7831 0349–046


RDMS-JDBC Level 2.8

Compatibility

RDMS-JDBC 2.8 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.

5.42. 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.42.1. Configuration Requirements

Use the following guidelines to configure DDP-PPC and CPComm.

DDP-PPC

HOST NAME=<local-ddp-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=<process-name>

PASSWORD=<password>

CPMODE=<CPCOMMx> ;

where x is the mode. See SYS$LIB$*DDP-PPC-2.README for additional details.

CPComm

PROCESS,<process-name> PASSWORD,<password> ;

T-SELECTORS,X,'DDP$$<local-ddp-name>'

CA,<device-name>

LINK,<link-name> CA,<device-name>

[IP-INFO ...]

IP,<ip-name> LINK,<link-name> ;

IP-ADDRESS,<ip-address>[,<process-name>]

Runtime System for Extended Mode Compilers (URTS)

7831 0349–046 5–35

Note: If <process-name> 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.42.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.43. 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 or CPCommOS they will

be affected by the reinstallation of URTS. Refer Table B-2 for products that use

CPComm or CPCommOS.

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.


URTS Level 13R3C

Compatibility

The Interface to Zip Utilities code has been converted from Java to C. The same entry

points of ZIP$NBRENTRIES, ZIP$NAMEENTRIES, ZIP$READENTRY, ZIP$WRITEENTRY,

ZIP$CLOSEENTRY, ZIP$PRINTEXCEPTION, and ZIP$SETCOMPRESSION still exist. For

more information, see Section 20, in the C Compiler PRM Volume 2 (7831 0430) and

Section 10.26, in the Cobol Compiler PRM Volume 2 (7831 0455).

5.44. Security-Admin


The Security-Admin product includes the following:

• Security-Admin client 4R4

• Security-Admin agent 4R4A

• SECMGR command line utility 4R4A

SILAS

5–36 7831 0349–046


Security-Admin Level 4R4A

Compatibility

Security-Admin requires the SLIB 2R1 and SYSLIB 77R1 products that are delivered

with this ClearPath release.


Security-Admin Level 4R4

Compatibility

• The compatibility issues of the client software with Windows 7/VISTA are fixed in

this release.

• The Security Administration level 4R4 client requires SNMP version 3 and no

longer supports connections using SNMP version 1. Communications Platform

supports connections using SNMP version 3.

5.45.SILAS


SILAS Level 3R3

Migration

The SILAS build process has some changes.

The following queries no longer appear in the SILAS COMUS BUILD routine:





NEWMASTER tape.




NEWMASTER tape.



SILAS COMUS build.

SOLAR and SOLAR/E

7831 0349–046 5–37

Example:




ADDTHIS ‘ ‘@SYM,U SILAS$PRT$.,,<print-queue>’ ‘

Note: You must register the SILAS 3R3 release tape with your COMUS database to

pick up this feature.

5.46. 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, UOE, 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.

• 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.

SP-OPERATION (Operations Sentinel)

5–38 7831 0349–046

• 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.

5.47. SP-OPERATION (Operations Sentinel)

For detailed considerations, see Section 8.


SP-OPERATION Level 15.0, 15.0CP

Compatibility

Operations Sentinel level 10.x and previous releases are not compatible with

Operations Sentinel level 15.0. Therefore, configurations developed under level 10.x

and previous releases must be manually recreated for use with the new Operations

Sentinel level 15.0 data model structures.

Installation of Operations Sentinel 15.0 allows to carry forward and convert the 11.x

and above level configuration to the 15.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 of the Operations Sentinel level 15.0 data model.

SP-OPERATION (Operations Sentinel)

7831 0349–046 5–39



Compatibility


Operations Sentinel level 14.0. Therefore, configurations developed under level 10.x

and previous releases must be manually recreated for use with the new Operations

Sentinel level 14.0 data model structures.

Installation of Operations Sentinel 14.0 allows to carry forward and convert the 11.x

and above level configuration to the 14.0 structure. This is available at the installer's

choice.

Migration


recreation of the configuration of the Operations Sentinel level 14.0 data model.

DSTA Migration issues for Operations Sentinel 14.0:

Migration to the ClearPath OS 2200 15.0 environment requires installing or upgrading

to the Operations Sentinel 14.0 level, prior to installing the Exec 49R1.

Operations Sentinel 14.0 is backwards compatible and will function in the ClearPath

OS 2200 14.0 environment.

Note: The format of numerous console messages, including the continuous display

format, has changed in EXEC 49R1. If you install EXEC 49R1 without updating

Operations Sentinel 14.0, the Operations Sentinel Log file will be flooded with

Continuous Display Messages.

Migration to Windows 8 operating system and Windows 2012 Server platform would

require manual disabling of UAC by modifying the registry entry. Customers have to

edit the registry entry in the following registry location and set the value to 0 (zero):

HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA

SSG

5–40 7831 0349–046



Compatibility


Operations Sentinel level 13.0. Configurations developed under level 10.x and previous

releases must be manually recreated to be used with the new Operations Sentinel

level 13.0 data model structures. Backward compatibility is not supported, in that

Operations Sentinel level 10.x and previous levels cannot use Operations Sentinel level

13.0 configurations.

The installation of Operations Sentinel 13.0 provides an opportunity to carry forward

and convert the 11.x configuration to the 13.0 structure. This is available at the

installer's choice.

Migration


recreation of the configuration to the Operations Sentinel level 13.0 data model.

5.48. SSG


SSG Level 24R3

Compatibility

• On the @SSG call line, beginning at param-7, SGS input streams can be specified in

the format "SGS/n,name-1,...,name-n". Prior to this feature the SGS identifier could

be specified in the illegal format "SGSxxxxxxxxx", where the "x" are non-blank,

non-separator characters. This is corrected so that SSG reports the following

error:

*ERROR* - SPEC nn --> INVALID FORM SGSxx

• Prior to this feature the option characters specified on the File Identification OPT

statement were not validated in any way. There was no validation that the

specified option characters were alphabetic and no validation that the characters

were legal additional SSG options, as documented in the SSG Programming

Reference Manual (7831 1784), Table 2-4. With this feature the specified options

are now validated. As a result of this, illegal option characters that were previously

ignored now cause the following warning message to be output:

*WARNING* - ILLEGAL OPTION CHARACTER(S) IGNORED: illegal-option-chars

SYSLIB

7831 0349–046 5–41

• In the extremely unlikely event that you have a user-defined global variable with

the name FEATURE_LEVEL$ your skeleton will no longer operate correctly and will

produce warning messages whenever you attempt to modify the variable.

FEATURE_LEVEL$ is the name given to the new reserved global read-only variable

by the 'Determine currently supported SSG features' feature above.

• In the extremely unlikely event that you have a user-defined global or local variable

with the names UTC$ the date and time values contained in the automatically

defined DATE$ and TIME$ SGS may change when UTC$ has a nonzero value. See

the 'New date/time information available on DATIME$, DATE$, and TIME$ SGSs'

feature above.

Note that Unisys recommends that you do not define global or local variable names

that end with a dollar sign ($).


SSG Level 24R2B

Compatibility

After Symbolic Stream Generator (SSG) level 24R2B is installed, the SSG *RESTORE

directive can still process *SAVE directive elements and files created by all levels of

SSG, including SSG levels that are no longer supported.

However, *SAVE directive elements and files created by SSG level 24R2B are not

backward compatible to unsupported SSG levels or to supported SSG levels that do

not have SSG CHG 1288 integrated. An attempt to use the *RESTORE directive with

the new format *SAVE element or file results in a guard mode (IGDM) contingency,

most likely in element SSGSAR routine SGS_FROM_BUFF.

Therefore, if you routinely move *SAVE directive elements and files between systems,

you need to be sure that either SSG level 24R2B is installed or SSG CHG 1288 is

integrated on all systems.

5.49. SYSLIB


SYSLIB Level 77R1

Compatibility

The "Support Modified-SWTIME Format as a TDATE$ Replacement" feature increases

the size of several SYSLIB relocatable elements and the PIRCB$ and SYSLIB$1

common banks. MAP errors can occur for user program collections that were

error-free for SYSLIB 76R4B. This can occur if the increased SYSLIB element sizes

cause banks to exceed the Basic Mode addressing window size limits.

SYSLIB

5–42 7831 0349–046

The following relocatable elements have significant element size increases in SYSLIB

76R4 and 77R1. Their sizes are shown in octal words:

76R3E 76R4 77R1

AEDIT$SFDT 0273 01004 * 01154 *

AEDIT$T 0240 0772 * 01122 *

EDIT$T 0207 0760 * 01105 *

ID$ 0512 ** 0461 ** 0461 **

SFDT$ 0425 01213 * 01370 *

TIMECONV$ n/a 0635 * 01040 *

TIMESUBR$ n/a 0207 0226

* Causes inclusion of element TIMESUBR$

** Causes inclusion of SFDT$

The common bank address ranges are shown in octal:

76R3E 76R4 77R1

PIRCB$ 01000 - 023764 01000 - 024732 01000 - 025126

SYSLIB$1 01000 - 011662 01000 - 014253 01000 - 015037

Several of the SYSLIB MASM procedures generate additional code. If you call these

procedures this increases the size of your basic mode relocatable elements or your

extended mode object module elements. MASM, MAP, or execution errors can occur

for user programs that operated error-free with SYSLIB 76R4B. This can occur when

increased sizes cause elements or banks to exceed addressing size limits.

The following procedures have generated code size increases in SYSLIB 76R4 and

77R1. The generated code sizes are shown in decimal words:

76R3E 76R4 77R1

A$EDITPKT 17 18 18

S$FDTPKT 5 8 8

EM$EDIT * 30 35 37

EM$EDITPKT ** 21 22 22

* Assumes parameters "func,param1,param2" are specified

** Does not include variable size of buffer generated

Tape Labeling Utility for ClearPath OS 2200 (TUTIL)

7831 0349–046 5–43

The "Provide New Procedures That Use the New Collector-defined Symbols" feature

introduces three new procedures. If user procedure names conflict with the new

SYSLIB procedure names, then the user definitions take precedence, as long as the

user definitions are found before the file SYS$LIB$*SYSLIB is searched. The SYSLIB

PROC$ element is near the end of the standard MASM procedure search chain.

However, the MASM procedure search order can be modified by user-supplied @USE

statements. The MASM Programming Reference Manual (7830 8269) describes

library searching in Section 3.4. Note that Unisys recommends that users should not

define procedure names that have a dollar sign ($) as the second character.

Migration

With the "Support Modified-SWTIME Format as a TDATE$ Replacement" feature the

AEDIT$, EDIT$, SFDT$, and TIMECONV$ routines will provide automatic conversion of

Modified-SWTIME timestamps when TDATE$ date/time format type is specified or

implied. This will not require user code changes and will not impact the SYSLIB routine

callers.

However, illegal TDATE$ values with bit 0 set that previously resulted in validation

errors or in the formatting of an illegal month will now be assumed to be a

Modified-SWTIME date/time and will be automatically converted based on the

assumption that bits 2 to 35 contain the seconds since 1899-12-31 00:00:00 and bit 1

indicates if the seasonal shift was in use at the specified date and time. This may

result in creating output date/time formats the are before 1964-01-01 or after

2027-12-31, the range of TDATE$ date/time values.

5.50. 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.

TCP/IP Application Services (TAS)

5–44 7831 0349–046

5.51. TCP/IP Application Services (TAS)


• After TAS is installed, the background runs error on a system running Fundamental

Security (SENTRY=0). See 5.18 (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.

• TAS 6R2K requires IRU 22R1 to be installed with mode FSAH.

Refer to the SYS$LIB$*TAS-2.README element for additional release documentation.

5.52. TeamQuest Products

Note: See 3.7 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.52.1. TeamQuest Baseline®


TeamQuest Baseline® Level 7R5

Migration

TeamQuest Baseline® level 7R5 is required with Exec level 49R1. TeamQuest

Baseline® level 7R5 also works with previous Exec levels.

TeamQuest Products

7831 0349–046 5–45

5.52.2. TeamQuest® LA


TeamQuest® LA Level 8R1

Migration

TeamQuest® LA level 8R1 is required with Exec level 49R1. TeamQuest® LA level 8R1

also works with previous Exec levels.

5.52.3. TeamQuest Online®


TeamQuest Online® Level 7R5

Migration

TeamQuest Online® level 7R5 is required with Exec level 49R1. TeamQuest Online®

level 7R5 also works with previous Exec levels.

5.52.4. TeamQuest® OSAM


TeamQuest® OSAM Level 7R6

Migration

TeamQuest® OSAM level 7R6 is required with Exec level 49R1. TeamQuest® OSAM


5.52.5. TeamQuest® PAR


PAR Level 9R3

Compatibility

In the prior release, the large configuration processor was available as an absolute:

@SYS$LIB$*PAR.PAR/L.

With this release, the large configuration processor is installed, and callable, as

@PAR-L.

5.52.6. TeamQuest® PMLog


TeamQuest® PMLog Level 7R5

TeamQuest Products

5–46 7831 0349–046

Migration

TeamQuest® PMLog 7R5 is required with Exec 49R1. TeamQuest® PMLog 7R5

PMLog level 7R5 also works with previous Exec levels.

5.52.7. TeamQuest® SAUTILITIES


TeamQuest® SAUTILITIES Level 8R1

Compatibility

• New versions of the LFI setup and read packets have been added to allow for the

processing of audit trails using the Daylight Saving Time Adapt format.

• The LFI setup and read packets have been modified to allow the caller to specify if

times should be interpreted as LOCAL or UTC. Additional fields contain the time

conversion information required by the calling program to convert times between

UTC and LOCAL.

• There are two new error status values that can be returned by the LFI setup and

read routines. These will need to be processed within the calling program.

Migration

TeamQuest® SAUtilities level 8R1 is required with Exec level 49R1. TeamQuest®

SAUtilities level 8R1 also works with previous Exec levels.

5.52.8. TeamQuest® TIP-LA


TeamQuest® TIP-LA Level 1R6

Compatibility

• Step-id values are displayed as two word octal values when the audit trail file is a

DSTA version file. When the program processes a pre-DSTA audit trail file, the

location of the step-id information is changed within the report.

• When using DUMP_REPORT FORMAT=TEXT, the value for MISC Offset has been

added for the Termination Summary record (13/3). The positions of the other offset

values displayed have been modified in order to include this new value.

Migration

TeamQuest® TIP-LA level 1R6 is required with Exec level 49R1. TeamQuest® TIP-LA


UCOB

7831 0349–046 5–47

5.53. UCOB


UCOB Level 12R2

Compatibility

GOBACK is now a new COBOL verb. Any use of the word GOBACK, either as a data

name or a procedure name, will no longer be allowed in a UCS COBOL program. Any

use of a data name or procedure name of GOBACK will need to be changed.

ADDRESS, NULL, and NULLS are now unreserved words. An incompatibility was

introduced if a user had a data-name declared as ADDRESS and used that data name

as a sender or receiver in a SET statement. A similar incompatibility was also

introduced for data-names NULL or NULLS used as a sending item in a SET statement

or in a conditional statement (I.E. an IF statement). In those situations, NULL and

NULLS are now treated as a two word value of binary zeroes. Any use of the data

names ADDRESS, NULL or NULLS within SET or relational statements will need to be

changed.

5.54.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.55. 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.

UREP

5–48 7831 0349–046

5.56. UREP


UREP Level 16R1

Migration

There are two UREP install changes.

1. The UREP install creates any new or missing RDMS Catalog views for the

application group.

The UREP migration install (Mode A) cannot create a new or missing RDMS

Catalog view if the UREP installer's user ID does not have privileges to reference

all the UREP and RDMS system tables and RDMS Catalog views referenced by the

view. In this case the SOLAR PRODLD issues an error.

An informational, warning, or fatal error has been detected during

PRODLD. Consult the PRODLD diagnostic element for detailed

information.

END PRODLD Errors: 0 Warnings: 1 Info: 0

The PRODLD breakpoint element contains the error

THE INSTALL FAILED TO CREATE ONE OR MORE OF THE MISSING RDMS CATALOG

OR UREP SQL VIEWS FOR THE APPLICATION GROUP. CHECK THE INSTALL

OUTPUT FILE TO DETERMINE THE EXACT CAUSE OF THE ERROR. TO CREATE

THE VIEW(S), YOU MUST FIX THE ERROR AND RERUN THE INSTALL. THIS

ERROR DID NOT AFFECT THE REST OF THE UREP INSTALL. IF YOU DON'T PLAN

TO USE THE VIEW(S) THAT COULD NOT BE CREATED, YOU DON'T NEED TO

CREATE THEM.

The PRODLD breakpoint element also contains the specific RDMS CREATE VIEW

error.

CREATE VIEW RDMS_CATALOG.RDMS_STATS

(SCHEMA_NAME, TABLE_NAME, TABLE_VERSION, INDEX_NAME,

COLUMN_NAME, NUM_RECORDS, NUM_UNIQUE_VALUES, DEPTH,

NUM_LEAF_PAGES, PCT_PAGE_FULL, AVG_REC_SIZE,

HIGH2KEY_NCHAR, HIGH2KEY_CHAR, HIGH2KEY_DP_REAL,

LOW2KEY_NCHAR, LOW2KEY_CHAR, LOW2KEY_DP_REAL) AS

SELECT * FROM RDMS.STATS

WITH ACCESS CONTROL;

Last command returned the following error status: 6002

APP 3 RDM EX 25560 CREATE VIEW command rejected.

User would lack select-access on newly created

view. Privileges held due to membership in a role

do not apply to CREATE VIEW. In addition to role

security, the table owner must explicitly grant

to the view creators userid.

UREP

7831 0349–046 5–49

You can ignore the error if you do not use the view(s) that could not be created and

you do not use RDMS-JDBC on the application group. The error does not affect the

rest of the UREP install. To correct the error

a. Determine the owner user ID of all the RDMS and UREP system tables and

RDMS Catalog views in the FROM clause of the CREATE VIEW commands

that failed.

To determine the owner user ID of a table

@use dds.,sys$lib$*urep. (default application group)

or @use dds.,uds$$xxx*urep$abs. (alternate application group)

@dds.dd

process table stats for schema rdms report.

*** Report for Table STATS for Schema RDMS

Logical Filename: STATS$FILE for Schema

Owner Userid : 5AAA

exit.

To determine the owner user ID of a view


or @use dds.,uds$$xxx*urep$abs. (alternate application group)

@dds.dd

rpt x-ref view relations for schema rdms_catalog to userid.

**CROSS-REFERENCE REPORT**

VIEW RELATIONS

SCHEMA RDMS_CATALOG

References :

1. Via : VIEW-TO-USERID

USERID 5AAA

Is referenced by :

No entity references this entity

b. Sign on with the owner user ID of the RDMS or UREP system table or

RDMS Catalog view.

UREP

5–50 7831 0349–046

c. Grant the UREP installer's user ID access to the RDMS or UREP system

table or RDMS Catalog view.

@use rsa.,sys$lib$*rsa. (default application group)

or @use rsa.,uds$$xxx*rsa. (alternate application group)

@xqt,e rsa.rsac-coivp

begin thread for appname update;

grant select on table rdms.stats to "5INS" with grant option;

end thread

exit;

d. Sign on with the UREP installer's user ID.

e. Rerun the UREP install.

2. The UREP install creates the JDBC Catalog for the application group. The

RDMS-JDBC product requires the JDBC Catalog.

If a UREP migration install (Mode A) cannot migrate the JDBC catalog, then SOLAR

PRODLD issues an error.

An informational, warning, or fatal error has been during

PRODLD. Consult the PRODLD diagnostic element for detailed

information.

END PRODLD Errors: 0 Warnings: 1 Info: 0

The PRODLD breakpoint element contains the error

THE INSTALL WAS NOT ABLE TO MIGRATE THE JDBC CATALOG. TO GET THE

CURRENT VERSION OF THE JDBC CATALOG YOU HAVE TO MANUALLY DELETE

IT FROM THE APPLICATION GROUP AND RERUN THE INSTALL. TO MANUALLY

DELETE THE JDBC CATALOG:

1. SIGN ON WITH THE USERID THAT OWNS SCHEMA JDBC$CATALOG2.

2. @USE UREPUTIL.,UREP*UTILITY. (DEFAULT APPLICATION

GROUP)

OR @USE UREPUTIL.,UDS$$XXX*UREP$UTIL. (ALTERNATE

APPLICATION GROUP)

3. @ADD,L UREPUTIL.JDBC-DELETE

>UDS$$XXX

THIS ERROR DID NOT AFFECT THE REST OF THE UREP INSTALL AND THE

OLD JDBC CATALOG STILL EXISTS ON THE APPLICATION GROUP. IF YOU

DON'T PLAN TO USE THE JDBC CATALOG YOU DON'T NEED TO MIGRATE IT.

Utilization Report Utility for OS 2200 (URU-OS2200)

7831 0349–046 5–51

You can ignore the error if you do not use RDMS-JDBC on the application group.

The error does not affect the rest of the UREP install. To correct the error

a. Determine the user ID that owns SCHEMA JDBC$CATALOG2. It is the

value of the schema's AUTHORIZATION-IDENTIFIER attribute.


or @use dds.,uds$$xxx*urep$abs. (alternate application group

@dds.dd

report schema jdbc$catalog2.

**DESCRIPTION REPORT**

SCHEMA JDBC$CATALOG2

AUTHORIZATION-IDENTIFIER

5AAA

exit.

b. Sign on with the user ID that owns SCHEMA JDBC$CATALOG2.

c. Manually delete the JDBC Catalog.

@use ureputil.,urep*utility. (default application group)

or @use ureputil.,uds$$xxx*urep$util. (alternate application group

@add,l ureputil.jdbc-delete

>uds$$xxx

d. Sign on with the UREP installer's user ID.

e. Rerun the UREP install.

5.57. 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.

Utilization Report Utility for OS 2200 (URU-OS2200)

5–52 7831 0349–046

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.

When migrating to a new URU, the URU Windows components should be installed

first and then the URU OS 2200 component.


URU-OS2200 Level 8.0

Compatibility

The URU Windows components are compatible with the URU OS 2200 component

from this release and all earlier supported releases.

The URU OS 2200 component is compatible with the URU Windows components from

the release but might not be compatible with URU Windows components from earlier

releases. If you install URU Mode B, you must have IRU FSAH installed from the

ClearPath OS 2200 release 16.0 - IRU 22R2.


URU-OS2200 Level 7.0

Compatibility

The URU Windows components are compatible with the URU OS 2200 component

from this release and all earlier supported releases.

The URU OS 2200 component is compatible with the URU Windows components from

the release but might not be compatible with URU Windows components from earlier

releases. If you install URU Mode B, you must have IRU FSAH installed from the

ClearPath OS 2200 release 15.0 - IRU 22R1.

Web Transaction Server (WEBTS)

7831 0349–046 5–53

5.58. 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) and Unisys Operating Environment (UOE).

• 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.59.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.

WebSphere® MQ Version 7 for ClearPath OS 2200 (WMQ2200)

5–54 7831 0349–046

Existing MQS2200 applications can use WMQ2200 without relinking, provided you are

using the same MQS subsystem gate bank BDI (Bank Descriptor Index). The default

MQS subsystem BDI for WMQ2200 is the same as the one used for MQS2200. There

are some exceptions to this general relinking rule. Refer to Section 4 of the

WebSphere® MQ Version 7 for ClearPath OS 2200 Installation, Administration, and

Programming Guide Level (3843 3744) for more information on multibyte data.

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.

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.


7831 0349–046 5–55

Installing a new level of the Interconnect does not require relinking WMQ2200.

WMQ2200 uses dynamic linking to resolve references to the Interconnect library. The

Interconnect library OM is loaded at subsystem load time and at UNX shell invocation.

Before installing a new level of the Interconnect, all WMQ2200 components must be

terminated. This includes exiting all UNX shell sessions, terminating the WMQ2200

background daemon, and deactivating the WMQ2200 MQS subsystem. When

WMQ2200 is restarted, the new Interconnect library will be loaded.


WMQ2200 Level 7R0C

Compatibility

WMQ2200 is based on IBM® WebSphere MQ Version 7.0 and is a compatible follow-

on to IBM MQSeries Version 5.2 (MQS2200). Differences exist and are documented in

the WebSphere® MQ Version 7 for ClearPath OS 2200 Installation, Administration,

and Programming Guide.

WMQ2200 level 7.0 is also compatible with its previous version, WMQ2200 level 6.0.

The ClearPath OS 2200 release 16.0 levels of WMQ2200 7R0C and INTERCONNECT

1R4B are fully compatible with QProcessor levels 2.2 and higher. Using WMQ2200

7R0C on any QProcessor version earlier than 2.2, or using QProcessor level 2.2 with

any WMQ2200 version earlier than 7R0A is not supported.

WMQ2200 7R0C requires Interconnect 1R4 or higher.

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 7R0C is also

supported. To do this it is required that you install the QProcessor level 2.2 image or

higher on your QProcessor Specialty Partition before installing WMQ2200 level 7R0C.

Consult the QProcessor PVP for product release pairings.

Consult the WebSphere MQ Version 7 for ClearPath OS 2200 Installation,

Administration, and Programming Guide for more information on these migration

scenarios.


5–56 7831 0349–046


WMQ2200 Level 7R0B

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. Consult the WebSphere

MQ Version 7 for ClearPath OS 2200 Installation, Administration, and Programming

Guide for more information. WMQ2200 level 7.0 is also compatible with its previous

version, WMQ2200 level 6.0.

WMQ2200 level 7R0B is compatible with QProcessor levels 2.2 and 3.0. Using

WMQ2200 7R0B on any QProcessor version earlier than 2.2, or using QProcessor level

2.2 with any WMQ2200 version earlier than 7R0A is not supported.

The ClearPath OS 2200 release 15.0 levels of WMQ2200 and INTERCONNECT are fully

compatible with QProcessor 2.2 software levels.

WMQ2200 7R0B requires Interconnect 1R4 or higher.

Migration



Upgrading from a previous level of WMQ2200 to WMQ2200 Version 7R0B is also

supported. To do this it is required that you install the QProcessor level 2.2 or

QProcessor level 3.0 image on your QProcessor Specialty Partition before installing

WMQ2200 level 7R0B. Consult the QProcessor PVP for product release pairings.



scenarios.


WMQ2200 Level 7R0A

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. Consult the WebSphere

MQ Version 7 for ClearPath OS 2200 Installation, Administration, and Programming

Guide for more information. WMQ2200 level 7.0 is also compatible with its previous

version, WMQ2200 level 6.0.

WMQ2200 level 7R0A is paired with QProcessor level 2.2. Using WMQ2200 7R0A on

any QProcessor version earlier than 2.2, or using QProcessor level 2.2 with any

WMQ2200 version earlier than 7R0A is not supported.


7831 0349–046 5–57

Migration



Upgrading from a previous level of WMQ2200 to WMQ2200 Version 7R0A is also

supported. To do this it is required that you install the QProcessor level 2.2 image on

your QProcessor Specialty Partition before installing WMQ2200 level 7R0A.



scenarios.


5–58 7831 0349–046

7831 0349–046 6–1

Section 6 Workstation-Based Software

Considerations

This section covers the migration and compatibility considerations for the

workstation-based software products.

6.1. ClearPath OS 2200 Release 16.0

Products are listed in alphabetical order.

6.1.1. Apex

The presentation tier of Apex architecture is your workstation or mobile device

running a compatible web browser and displaying Apex web pages. Apex is fully

supported with Internet Explorer 9, 10, and 11. Other browsers might also work

successfully with Apex, although the page formatting may differ somewhat from its

appearance on Internet Explorer.

The application tier is a Windows server running Internet Information Server (IIS). This

tier, typically a Dorado Operations Server, runs the Apex Web application and serves

the Apex Web-based help when you request it from your web browser.

• The server OS must be Windows 2008 or later.

• .NET Framework v4 or later full version must be installed and registered with IIS.

• IIS must be installed with the ASP.NET role service enabled.

6.1.2. 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 8 (Enterprise, Professional, and Ultimate Editions), Windows 8.1,

Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2,

Windows Server 2008, Windows 7 (Enterprise, Professional, and Ultimate

Editions), or Windows Vista (Business, Enterprise, and Ultimate Editions).

Workstation-Based Software Considerations

6–2 7831 0349–046

Note: The setup determines the bitness of the Operating System (32-bit or

64-bit) and then decides which version of Enterprise Output Manager must be

installed. Going forward, a 32-bit Enterprise Output Manager will not be allowed

to install on 64-bit server machines.

(Bitness refers to the differentiation between 32-bit and 64-bit

processor architecture).

• The Microsoft .NET Framework 4.0. The installation for the English version of the

.NET Framework is included on the Enterprise Output Manager installation CD. For

other languages or to verify that other dependencies are also installed, please

refer to the Microsoft website.

• 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.3. TeamQuest Model® (TQ-MODEL)

See 3.7 for important information about license keys for TeamQuest products.

6.1.4. TeamQuest View® (TQ-VIEW)

The following is the consideration for TeamQuest View® (TQ-VIEW):

TeamQuest View® for Microsoft Windows Vista, 7 and 8 is automatically included

in the TeamQuest Baseline® package.

6.1.5. Utilization Report Utility (URU)

Release 16.0, URU 8.0, is supported on: Windows Vista, Windows Server 2008,

Windows Server 2008 R2 (64 bit), Windows 7 (32 and 64 bit), Windows 8 (32 and 64

bit), Windows 8.1 (32 and 64 bit), Windows Server 2012, and Windows Server 2012 R2.

6.1.6. 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 7, Windows 8, Windows 8.1, Windows Server

2008 R2, Windows Server 2012, and Windows Server 2012 R2.


7831 0349–046 6–3

• Refer to “Hardware and Software Requirements” in the Web Transaction Server

for ClearPath OS 2200 Administration Guide for more dependencies.

6.1.7. Operations Sentinel (SPO)

Operations Sentinel server is supported on Windows Server 2008 (Standard Edition or

higher), Windows 2008/R2, Windows Server 2012, and Windows 2012/R2. Operations

Sentinel workstation is supported on Windows Vista Business Edition, Windows

Server 2008 (Standard Edition), Windows 7 Professional, Windows 8, and Windows

8.1. Operations Sentinel workstation is supported on both 32-bit and 64-bit versions of

the workstation operating systems.


6–4 7831 0349–046

7831 0349–046 7–1

Section 7 Installing ClearPath OS 2200 Release 16.0 Software

This section provides the following information to assist you in installing the ClearPath

OS 2200 release 16.0 products on your system:

• Installation considerations (Section 7.1)

• ClearPath OS 2200 release 16.0 migration considerations (Section 7.2)

• Fall back considerations from ClearPath OS 2200 release 16.0 to either release 14.0

or 15.0 (Section 7.3)

• Other considerations (Section 7.4)

• Description of fast-load tapes (Section 7.5)

• Migration sequences (Section 7.6)

− Initial Migration Steps (Section 7.7)

− Alternative 1: Installing products from fast-load tapes (Section 7.8)

− Alternative 2: Installing products from package tapes (Section 7.9)

• Procedure for initializing an existing system (I-boot) (Section 7.10)

• Migration for existing Dorado 4000 customers (Section 7.11)



• Migration for existing Dorado 4300 and Dorado 6300 customers (Section 7.14)

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: Migration to ClearPath OS 2200 release 16.0 is possible from either release

14.0 or 15.0. The migration sequence described in this section assumes that all of

the products on your system have been updated to the ClearPath OS 2200 14.0

levels at minimum.

Installation Considerations

7–2 7831 0349–046

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 4000, 4100, 4200, 4300, or 6300 system to

this release from a prior release, there may be critical interdependencies involving

CPCommOS, various plateau components, and the installation order for certain

products (including the EXEC). Refer to sections “7.11 Migration for Dorado 4000

Customers”, “7.12 Migration for Dorado 4100 Customers”, “7.13 Migration for

Dorado 4200 Customers”, or “7.14 Migration for Dorado 4300 and Dorado 6300

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. The ClearPath

OS 2200 DVD Media Quick Reference Card (7862 2032) also details the product

packaging information.

• You will receive a product key tape that provides access to the authorized

products for your system. 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).

Installation Considerations

7831 0349–046 7–3

7.1. 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.18 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.2. ClearPath OS 2200 Release 16.0 Migration Considerations

The migration from ClearPath OS 2200 release 14.0 to release 15.0 involved several

more product-related considerations than the migration for previous ClearPath

releases. Most of the migration considerations for release 15.0 were one-time

changes required by the Daylight Saving Time Adapt (DSTA). The migration from

ClearPath OS 2200 release 15.0 to 16.0 requires significantly fewer changes.

Migration to ClearPath OS 2200 release 16.0 is supported from systems currently

running either release 14.0 or release 15.0. Sites already running release 15.0 have

already completed all of the migration steps that were required as part of the Daylight

Saving Time Adapt. Sites moving directly from release 14.0 to release 16.0 will have

more migration considerations than sites already running release 15.0. If you move

directly from release 14.0 to release 16.0, release 16.0 will represent your first

exposure to the Daylight Saving Time Adapt.

Unisys does not support migration to ClearPath OS 2200 release 16.0 from any release

prior to release 14.0. Verify that all products on your system are updated to at least

release 14.0 before beginning your migration to release 16.0.

ClearPath OS 2200 Release 16.0 Migration Considerations

7–4 7831 0349–046

Crossboot Changes for MHFS environments

If you have a MHFS environment you must build and boot crossboot change PLE

18950154 on all hosts before the first host moves from release 14.0 to either release

15.0 or release 16.0. If your MHFS hosts are already running ClearPath OS 2200 release

15.0 then no additional crossboot changes need to be applied before moving from

release 15.0 to release 16.0.

Crossboot Changes for Date and Time Compatibility

If your system is currently running ClearPath OS 2200 release 14.0, you must build and

boot a version of EXEC 48R9 including the changes listed in PLE 19028330 prior to

beginning any of the installation steps for Release 16.0. This PLE provides EXEC

support in the Release 14.0 environment for several new ERs and CALL interfaces that

are now being used by numerous software products in Release 16.0. Failure to install

this PLE may result in problems during the early phases of the recommended

installation sequence for the Release 16.0 products or difficulties if you should choose

to fall back from Release 16.0 to Release 14.0 in the future.

If your system is already running Release 15.0, the code associated with this PLE is

already present in your system and no additional EXEC gen or reboot is required prior

to moving up to Release 16.0.

DSPER Consideration

If you use the SMON or MSLATE hardware diagnostic tools, you must use DSPER

10R5 or later. Older versions of SMON and MSLATE will not run in conjunction with

EXEC 49R2.

DSPER 10R5 or later is available for download on the Unisys support web page.

http://www.Support.Unisys.com

Symbolic Updates for Exec and MCB

Both the Exec and MCB introduced symbolic updates in ClearPath OS 2200 release

15.0. If you are moving up to ClearPath OS 2200 release 16.0 directly from release 14.0

and have local code in these products, update the local code before beginning this

migration process. If you are already running ClearPath OS 2200 release 15.0 there are

no new base symbolic considerations for these two products between releases 15.0

and 16.0.

To assist you in migrating your Exec local code, Unisys is delivering the TCFUPGRADE

software tool. See 4.1.2.6 for more information.


7831 0349–046 7–5

Automated Message System

If you use the Automated Message System (AMS) feature of SP-Operation or other

products that use patterns that look for specific console messages and are moving up

to ClearPath OS 2200 release 16.0 directly from release 14.0, you may need to make

changes as timestamps in the keyin output, messages, and console displays have

changed in both format and location. See the Mandatory Migration Actions for

ClearPath OS 2200 Release 15.0 and Higher (8222 3777), Appendix A for additional

information, including examples of messages that changed as the result of the

Daylight Saving Time Adapt in CleatPath OS 2200 release 15.0.

There is a new feature in the Operations Sentinel product, Autoaction Database

Scanner that assists you in locating message patterns within your AMS databases that

are susceptible to changes in timestamp format. This feature was released as an IC

for level 14.0 of Operations Sentinel and is integrated in level 15.0 of that product. See

PLE 18998165 for further details.

Audit Trail Changes

The audit trail formats were changed by the Daylight Saving Time Adapt in ClearPath

OS 2200 release 15.0. If you are moving up to ClearPath OS 2200 release 16.0 from

release 15.0 then you are already familiar with these changes. If you are moving up to

ClearPath OS 2200 release 16.0 directly from release 14.0, release 16.0 will represent

your first exposure to these changes.

• Audit control records on all trail types have changed

• ACI File structure for all trail types have changed

• ACI File configuration SGS has changed

• Many trail specific records have changed

• The Step-id Format (but not size) has changed

If you have utilities that read any of the audit trails (Step Control, ASCII Log, TPM or

COD) you may need to update your utilities. Unisys recommends that you use the

IRU’s Freestanding Audit Handler (FSAH) as the basis for any utility that reads audit

trails, including the system log. If you use FSAH to retrieve audit records, you only

need to manage changes to the records themselves, not to the audit structures.

Third Party Software

If you have purchased or shareware utilities that read the log file (for example,

TeamQuest, Sightline, or Formula Consultants log products) you will need to acquire

the versions that are compatible with the ClearPath OS 2200 16.0 release.

See the Mandatory Migration Actions for ClearPath OS 2200 Release 15.0 and Higher

(8222 3777-002).


7–6 7831 0349–046

Exec 49R2 Considerations

There are no major EXEC considerations introduced between EXEC 49R1 (ClearPath

OS 2200 release 15.0) and EXEC 49R2 (ClearPath OS 2200 release 16.0). Sites moving

from release 15.0 to release 16.0 can skip over the remainder of this section. There

were numerous changes required between EXEC 48R9 (ClearPath OS 2200 release

14.0) and EXEC 49R1 (release 15.0), however, including a symbolic update. Sites moving

up to ClearPath OS 2200 release 16.0 directly from release 14.0 must take all of the

following changes into account when planning this migration.

Besides being a symbolic update, Exec 49R1 (ClearPath OS 2200 release 15.0)

introduced several configuration changes and the decommitment of several Exec

features. See Section 4.1, “General Exec Considerations” for a detailed description of

changes that will require your action when building Exec 49R2.

� Have you looked at your Exec configuration to plan changes?

Exec 49R1 introduced several configuration changes:

• Default values for security-related configuration parameters have

changed.

• Audit Control Transfer Maximum stream generation statement (SGS)

changes.

• ACI SGS change.

• STEP CONTROL QNBR SGS default change.

• COD default configuration change.

• Removal of configuration parameter TIME_DATE_FORMAT.

� Do you have utilities that look for files on the Exec boot tape?

Exec 49R1 introduced changes to the boot tape.

The SYS$*MCODE$ file and the SYS$*PRINTER$ file have been removed

from the boot tape.

� Have you removed the Exec features that are no longer supported?

Exec feature CARTLIB is no longer included in this release. If you installed this

feature with release 15.0, do not include them in your release 16.0 Exec build.

� Do you have unsupported hardware in your configuration?

The I/O Legacy Removal feature eliminates support for numerous equipment

types. See section 4.1.2.4 for information on the obsolete components that

were removed in ClearPath OS 2200 release 15.0.

� Do you run with a Multi Host File Sharing (MHFS) environment?

Exec 49R1 introduced a crossboot consideration that requires you to build

and boot Exec 48R9 with PLE 18950154 for all MHFS hosts before migrating

any of the systems to the Exec 49R1 or EXEC 49R2 levels.

� Is your system currently running EXEC level 48R9 (Release 14.0)?

If so, you should build PLE 19028330 into your current EXEC level and boot

that boot tape. If you are already running EXEC level 49R1 (Release 15.0), this

step is not necessary.

Fall Back Considerations From ClearPath OS 2200 Release 16.0 to Prior Releases

7831 0349–046 7–7

� Are you prepared to Initialize (INIT) your application groups immediately after

starting the Release 16.0 Exec 49R2?

You must INIT your application groups when moving from release 14.0 to

release 16.0. You will also need to do an orderly shutdown of your application

groups in preparation for the INIT.

Unisys recommends that you use one of the following approaches to backup

the database before you INIT:

• Backup any databases before you boot the Exec 49R2.

• Backup any databases as soon as you have booted the new Exec 49R2.

� Do you use TIP Session Control (TSC)?

The TSC session file record is resized. This is done automatically by PSFUTIL

when the application group is initialized.

Verify that the LIB$ file on your Exec 48R9 and Exec 49R2 boot tapes has the

PSFUTIL absolute from Exec 48R9 or higher.

� The Exec 49R2 supports only labeled dump tapes. Establish a pool of labeled

dump tapes for future use.

7.3. Fall Back Considerations From ClearPath OS 2200 Release 16.0 to Prior Releases

In the event that you must drop back from EXEC 49R2 (ClearPath OS 2200 release 16.0)

to EXEC 49R1 (release 15.0), there are no fallback considerations or product

incompatibilities known at this time. Boot EXEC level 49R1 and then skip the rest of

the information in this section.

In the event that you must drop back from EXEC 49R2 (ClearPath OS 2200 release 16.0)

to 48R9 (release 14.0), your EXEC 48R9 boot tape must include the changes listed in

PLE 19028330. In addition, there is a specific series of migration steps that must be

followed. Those steps are described in the remainder of this section.

Dropping back from release 16.0 to any release prior to 14.0 is not supported.

Note: In a fallback scenario, many of the non-EXEC products associated with

release 16.0 must continue to remain installed on your system. Once EXEC 49R2 has

been booted, it is not possible to revert to an environment (or restore a LIBSAVE

tape) that contains only release 14.0 products. After a fallback occurs, you will be

running EXEC level 48R9 but must use a combination of other products that will be

from both release 14.0 and release 16.0.

Be aware that the MCB and CMR (Console Message Redisplay) products must remain

in lockstep with the EXEC level. When you are running EXEC level 48R9 (from

ClearPath OS 2200 release 14.0), you must also use the release 14.0 levels of MCB and

CMR. When you are running EXEC level 49R2 (from ClearPath OS 2200 release 16.0),

you must also use the release 15.0 or 16.0 levels of MCB and CMR. There is no single

level of either MCB or CMR that can run on both a 48-level EXEC and a 49-level EXEC.

Thus, every time you cross-boot back and forth between EXEC 48R9 and EXEC 49R2,

you must also install the corresponding levels of MCB and CMR.


7–8 7831 0349–046

IRU level 22R2 (from ClearPath OS 2200 release 16.0) was installed on your system

prior to moving up to EXEC 49R2. Even if you drop back from EXEC 49R2 to

EXEC 48R9, you must continue using IRU 22R2. You cannot revert to an earlier IRU

level.

Following are the recommended steps for dropping back:

1. If you decide to drop back from EXEC 49R2 to 48R9, you will again have to INIT all

of your Step Control applications. Thus, if you have any important database

information, you should plan to do an orderly shutdown of your applications and

audit trails prior to dropping back.

When falling back to previous (release 14.0) Exec 48R9 level, the action you must

take to properly recover database work depends on which situation your Step

Control application group fits it. Use the following table to determine which

situation your environment is in, and the appropriate action that you must take.

Situation Action

If you did not restart application

work on release 16.0

You can just go back to release 14.0 without additional

database recovery considerations. You will still need to

INIT the applications when you come up, but if you did

not restart the applications on release 16.0, there are no

recovery requirements associated with this INIT.

For concurrent AGs that have

started database work on release

16.0

Execute an inter-host MEDIUM RECOVER for the failed

host from a surviving host BEFORE rebooting the failed

host on the release 14.0 Exec. You will lose recoverable

messages on the failed host, but the database updates

will be consistent.

For local AGs that have started

database work

After rebooting the release14.0 Exec, you must long

recover the application group to ensure all database

updates are properly applied. You should start the

RECOVER ALL from the initial migration time. This time

is sufficient as a start time; it might be earlier than

necessary but there is no consistent means to

determine proper start time (which is the start-of-step

of anything that was active or CIP at the crash point).

If your application uses

Quick-Look recovery

You must RELOAD and RECOVER database files that

use quick-look recovery method.

2. You may wish to perform a LIBSAVE before dropping back. Although most of the

non-EXEC software products from release 16.0 that are already installed do not

need to be reverted to previous levels, you may have installed certain products

from release 16.0 (such as MCB and CMR) that will need to be reverted to an older

level after you drop back.

3. If you use the MHFS feature, be sure that your boot tape for EXEC 48R9 includes

all of the changes associated with PLE 18950154.


7831 0349–046 7–9

4. Boot EXEC level 48R9. Dropping back from EXEC level 49R2 to any level prior to

48R9 is not supported. During recovery, you will have to INIT all of your

stepcontrol applications. If your system uses TIP Session Control, the EXEC will

automatically decrease the size of your TIP Session files by invoking the PSFUTIL

utility.

5. After doing the INIT of your stepcontrol applications but prior to recovering your

applications with IRU 22R2, you must first restore the ClearPath OS 2200 release

level 14.0 level of MCB (level 8R3G). You cannot continue using the release 16.0

level of MCB (level 9R1) after dropping back to EXEC level 48R9.

Note: If you inadvertently try to run the incorrect level of MCB on either Exec

48R9 or 49R2, MCB displays the following message and goes down.

This MCB level is not compatible with current EXEC

6. Once MCB 8R3G has been restored, you should be able to recover your

stepcontrol applications using IRU 22R2. You must continue using the IRU level

from ClearPath OS 2200 release 16.0 (level 22R2). Once your system has moved up

to EXEC 49R2, even if only briefly, you cannot re-install any earlier IRU level.

Note: You should consider doing a database backup on the restored levels if it

is appropriate for your environment. See Step 12 of Section 7.7.1, “Initial

Migration Steps for Moving from Release 14.0 to Release 16.0” for information

on backing up your database.

7. If you use the CMR product, you should restore the ClearPath OS 2200 release

14.0 level of CMR (level 2R6). You cannot continue using the release 16.0 level of

the CMR product (level 3R2) when running EXEC level 48R9.

8. The release 16.0 products that were initially installed during the migration

sequence before EXEC level 49R2 was booted must remain installed even after

you drop back to EXEC 48R9. These products function with both EXEC 48R9 and

49R2, but earlier versions of these products may encounter problems if they are

used after you have fallen back from EXEC 49R2 to 48R9. Do not revert back to

the release 14.0 versions of any of these products:

• IRU (including FSAH)

• SYSLIB and SLIB

• DDP-FJT and DDP-PPC

• TeamQuest products: LA, OSAM, SAUTILITIES, TQ-Baseline, TQ-Online,

TQ-PMLOG, TQ-PROBES, TQ-TIP-LA

• URU

• EOM (DEPCON)

• Operations Sentinel (SP-Operation)

9. The TIPUTIL and MMGR from release 16.0 (level 49R2) can remain installed after

you drop back to EXEC level 48R9.

10. If you installed the latest version of the DSPER tape, you can also leave that installed. The newer versions of the hardware diagnostic utilities will continue to

work correctly on EXEC level 48R9.

Other Considerations

7–10 7831 0349–046

11. If you have installed additional release 16.0 products other than those listed above, you can either leave them installed or revert them to release 14.0 levels.

7.4. Other Considerations

• Fast-load tapes CP-OE1A and CP-OE1B containing the Integrated Operating

Environment (IOE) and Unisys Operating Environment (UOE) products are keyed.

You must register keys first before products can be installed.

• Software releases are delivered on DVD and CD-ROM media. Refer to the

ClearPath OS 2200 DVD Media Quick Reference Card or C.1 for more information

on logical package tape definition. Refer to the ClearPath OS 2200 CD-ROM and

DVD Media Index Cross Reference Card for more information on CD-ROM media.

• 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.

• You must install and activate CIFS before installing JPJVM. 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.7 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 system initialization, 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.

Description of Fast-Load Tapes

7831 0349–046 7–11

7.5. Description of Fast-Load Tapes

To support faster installation of the ClearPath Integrated Operating Environment (IOE)

and Unisys Operating Environment (UOE) products, Unisys has created the following

fast-load tapes:

• The CP-FLD (“first-load”) tape contains 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 register 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 and UOE 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 or the ClearPath OS 2200 DVD Media Quick Reference Card

(7862 2032) for detailed information about tape packaging of products.

7.6. Migration Sequences

This subsection describes how to migrate your systems to the ClearPath OS 2200

release 16.0 products. To begin the migration, start with Section 7.7, “Initial Migration

Steps.” This section documents the common steps that everyone must follow to

begin the migration process. Once you have completed the installation steps in

Section 7.7, you have the choice to install the remainder of the ClearPath OS 2200 16.0

products from Fast Load tapes (Section 7.8) or from Package tapes (Section 7.9).

Because of the many product and feature interdependencies, do not randomly install

the ClearPath OS 2200 release 16.0 software. Although some flexibility is allowed, the

recommended migration order presented in these sequences should be observed as

closely as possible.

The migration from ClearPath OS 2200 release 14.0 to release 15.0 involved several

more product-related considerations than the migration for previous ClearPath

releases. Most of the migration considerations for release 15.0 were one-time

changes required by the Daylight Saving Time Adapt (DSTA). The migration from

ClearPath OS 2200 release 15.0 to 16.0 requires significantly fewer changes.

Initial Migration Steps

7–12 7831 0349–046

Migration to ClearPath OS 2200 release 16.0 is supported from systems currently

running either release 14.0 or release 15.0. Sites already running ClearPath OS 2200

release 15.0 have already completed all of the migration steps that were required as

part of the Daylight Saving Time Adapt. Sites moving directly from ClearPath OS 2200

release 14.0 to release 16.0 will have more migration considerations than sites already

running release 15.0. If you move directly from release 14.0 to release 16.0, release

16.0 will represent your first exposure to the Daylight Saving Time Adapt.

Begin your migration:

• Initial Migration Steps (7.7)

Complete your migration; choose one of the following installation scenarios:

• Installing products from fast-load tapes (7.8)

• Installing products from package tapes (7.9)

Notes:

• If you are migrating an existing Dorado 4000, 4100, 4200, 4300, or 6300 system

to this release from a prior release, there may be critical interdependencies

involving CPCommOS, various plateau components, and the installation order

for certain products (including the EXEC). Refer to section “7.11 Migration for

Dorado 4000 Customers”, ”7.12 Migration for Dorado 4100 customers", “7.13

Migration for Dorado 4200 customers” or “7.14 Migration for Dorado 4300 and

Dorado 6300 customers" for details.

• If you encounter any difficulties while following these installation sequences,

contact your Unisys Product Support Center.

• Software levels in ClearPath OS 2200 release 16.0 have been tested for stability

and compatibility as part of an integrated system. Products having lower levels

than those in ClearPath OS 2200 release 16.0 might function correctly, but

Unisys recommends that your site develop a migration plan to use only

ClearPath OS 2200 release 16.0 levels.

7.7. Initial Migration Steps

This section contains the migration steps that must be followed to migrate to the

ClearPath OS 2200 16.0 Release. The migration sequence you should follow depends

on whether you are migrating from release 14.0 or release 15.0.

If your system is currently running ClearPath OS 2200 release 14.0, use the information

provided in Section 7.7.1 and skip the information in section 7.7.2.

If your system is currently running ClearPath OS 2200 release 15.0, use the information

provided in Section 7.7.2 and skip the information in section 7.7.1.

Once you have completed the work in the appropriate section (either 7.7.1 or 7.7.2),

you can choose to install the rest of the ClearPath OS 2200 16.0 products from the fast

load tapes (Section 7.8, “Installing from Fast Load Tapes”) or from package tapes

(Section 7.9, “Installing from Package Tapes”).


7831 0349–046 7–13

7.7.1. Initial Migration Steps for Moving from Release 14.0 to

Release 16.0

1. The Exec 48R9 requires several changes before beginning the migration

sequence. The first step in the migration is to build and boot your current Exec

48R9 level.

a. Build your existing Exec 48R9:

1. Apply EXEC PLE 19028330 on your existing EXEC 48R9 (Release 14.0)

system.

2. The RLIB$ level from Exec 49R2 should be installed in conjunction with

this PLE. Prior to building this PLE, assign your Exec 49R2 master tape and

copy the 12th file (RLIB$) from this tape to mass storage. When you create

the EXEC generation runstream to build this PLE into 48R9, ensure that the

RLIB$ clause of the “LIB FILES ARE...” statement within that EXEC

generation runstream points to this new mass storage file. Your Exec

48R9 generation will then copy the 49R2 version of RLIB$ onto the

resulting 48R9 boot tape.

3. In addition, if your system uses Multi Host File Sharing, all of the hosts in

your MHFS environment must build and boot with the changes from EXEC

PLE 18950154 before any of your hosts can move up to any EXEC level

beyond 48R9.

b. Boot the newly built Exec 48R9 with Jump Key 4 set in order to install the

new RLIB$ during the reboot.

Note: If you plan to use release 14.0 FLIT 14R2A to simulate object modules,

ZOOMS, or absolutes that call these interfaces before installing release 16.0

FLIT 15R2, apply FLIT PLE 19030482.

2. Perform a LIBSAVE of your current system. See Section 5.46, “SOLAR and

SOLAR/E” for more information.

3. Start the REGISTERPKG runstream to register the ClearPath OS 2200 release 16.0

product key tape using the SOLAR 4R7B that is installed in your release 14.0

environment. A key tape is registered using the same steps as registration of a

package tape. The registration summary report will display all new product

authorizations added to the system. See the file SOLAR*DIAGNOSTIC.

4. This step installs products that have migration implications/requirements when

moving to release 16.0. The release 16.0 levels of SYSLIB 77R1 and SLIB 2R1 (Table

7–1) are installed first in this step to address compatibility requirements introduced

in the Support Modified-SWTIME format as a TDATE$ Replacement feature. These

two updated products must be installed at the same time. The next set of

products (Table 7–2 and Table 7–3) have migration implications/requirements due

to the changes introduced in the Daylight Saving Time Adapt feature (DSTA). Older

levels of those products will not run in conjunction with EXEC 49R2.

Note: Before you install these products, the associated background runs should

be terminated. After successful installation and adjustments, the associated

background runs can be restarted.


7–14 7831 0349–046

Table 7–1. SYSLIB and SLIB Installation

Installation and

Support Name Level

Logical

Tape

Name

Default

Installation

Mode Notes

SYSLIB 77R1 CP02 A Install release 16.0 versions of SYLIB and SLIB

together.

SLIB 2R1 CP02 A

5. Install the set of products that have migration implications/requirements due to

the changes introduced in the Daylight Saving Time Adapt feature (DSTA). Older

levels of those products will not run in conjunction with EXEC 49R2.

Note: Before you install these products, the associated background runs

should be terminated. After successful installation and adjustments, the

associated background runs can be restarted.


7831 0349–046 7–15

Table 7–2. Package Tape Products

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

DMPLIB 9R2 CP05 INSTALL-ABS

URU-OS2200 8.0 CP05 A Install URU 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).

DDP-FJT 5R5L CP10 A

TAS 6R2L CP11 B TAS may require a post-installation procedure before

it functions correctly. See the TCP/IP Application

Services (TAS) implementation and Administration

Guide.

IRU 22R2 CP13 IRU

FSAH

Install with both modes IRU and FSAH

LA 8R2 CP18 A

OSAM 7R6A CP18 A

SAUTILITIES 8R1A CP18 A If you currently have TUTIL installed and you want to

install SAUTILITIES, you must remove TUTIL 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.

TQ-BASELINE 7R5A CP18 A If you are authorized for TeamQuest Baseline®, do

not use the INSTALLPKG runstream to install CP18.

TeamQuest Baseline® and TeamQuest Online® are

mutually exclusive.

TQ-ONLINE 7R5A CP18 A TeamQuest Baseline® and TeamQuest Online® are

mutually exclusive.

TQ-PMLOG 7R5 CP18 A

TQ-PROBES 7R5A CP18 A

TQ-TIP-LA 1R6 CP18 A


7–16 7831 0349–046

Table 7–3. DVD, CDROM, and Download Media

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installatio

n Mode

Notes

Operations

Sentinel

(SP-Operation)

15.0 or

15.0CP

CDROM The format of numerous console messages,

including the continuous display format, changed

beginning with EXEC level 49R1. If you install EXEC

49R1 or higher without updating to SP-Operation 14.0

or higher the SP-Operation Log file will be flooded

with Continuous Display Messages.

A new feature Autoaction Database Scanner in the

Operations Sentinel product will assist you in locating

message patterns within your AMS databases that

are susceptible to changes in timestamp format. This

feature was released as an IC for level 14.0 of

Operations Sentinel and is integrated in level 15.0.

See PLE 18998165 for further details.

DSPER 10R5 Download Default DSPER 10R5 is available for download on the Unisys

support web page.

http://www.Support.Unisys.com

DSPER 10R5 requires the FSAH subsystem be

installed. Verify that the security attributes for the

FSAH subsystem are set up before installing DSPER.

EOM (DEPCON)

OUTPUT-MGR

12.0 Stand-

alone

DVD

A

Notes:

• Older levels of these products do not function correctly in conjunction

with EXEC 49R2.

• The installation of DDP-FJT and TAS might report PRODLD warnings.

This occurs due to the relation between IPF and DDP-FJT and TAS. A

COMUS CONFIG of IPF is later required. See the Interactive Processing

Facility (IPF 1100) Administration Guide.

• In the event that you need to revert back to Exec 48R9 after you have

booted Exec 49R2, the release 16.0 level of products installed in this

step can continue to run in the Exec 48R9 environment. You should not

revert to the ClearPath OS 2200 14.0 product levels.

6. Install the products contained on the first-load (CP-FLD) fast-load tape (refer to the

following table).

Install these products quickly by using the ST INSTALLFLD command.

The SOLAR full-screen interface can also be used to register and install these

products.


7831 0349–046 7–17

Note: If you use the full-screen interface for installing CP-FLD 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.

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

COMUS 6R9C CP-FLD A COMUS is needed to generate the Exec

CPComm

Note: CPComm

is used only with

Dorado 700 and

800 Series systems.

6R5 CP-FLD A

AFCB

CMSA-CPCA

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.

CPCommOS Note:

CPCommOS is

used only with

Dorado 4000,

4100, 4200, 4300,

and 6300 Series

systems.

4R5 CP-FLD A

AFCB

CMSA-CPCA

XNIOP

There may be migration dependencies for the Dorado

4000, 4100, 4200, 4300, and 6300 systems. Before

beginning migration, refer to the following sections

for migration considerations:

• 3.9 ClearPath and Plateau Interdependencies

• 7.11 Migration for Dorado 4000 Customers



• 7.14 Migration for Dorado 4300 and Dorado 6300

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.

CryptoLib

Note: CPComm

does not build or

run unless

CryptoLib is

installed.

1R3 CP-FLD NOTFIPS The CryptoLib product is required by CPComm 6R5

and Cipher API 2R4A for installation. If CryptoLib is

not installed on your ClearPath 16.0 system, CPComm

and Cipher API terminate in error at initialization.

Note: CPCommOS does not require CryptoLib.

FURPUR 32R5D CP-FLD A

PCFP 3R3C CP-FLD A

ROLRUNS 4R3 CP-FLD A ROLRUNS is needed to ensure the Exec can be

placed on the DRS device.

SILAS 3R3B CP-FLD A CPComm requires SILAS for the demand connection.

SLIB 2R1 CP-FLD A

SOLAR 4R8 CP-FLD A

SYSLIB 77R1 CP-FLD A


7–18 7831 0349–046

7. Prepare the ClearPath OS 2200 release 16.0 versions of the three library files: LIB$,

RUN$ and RLIB$. Beginning with Exec 49R1 (in release 15.0), the MCODE$ and

PRINTER$ library files were removed. The three remaining library files are required

for system generation, regardless of system type. Either copy the files from the

release master tape to another tape or catalog three 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 Exec level 49.0 base symbolic tape has three files: Utility, Base

Symbolics, and the last 48-level PCF file. The PCF file on the base symbolic

tape is needed to upgrade 48-level local code. The file name

EXEC49SYM*48LASTPCF. distinguishes the 49R1 PCF file from the 48-level

PCF file.

• To assist you in migrating your Exec local code, Unisys is delivering the

TCFUPGRADE software tool. See 4.1.2.6 for more information on this tool.

8. Install the Separately packaged Exec features that you have ordered for your

system from the CP-SPF tape. See Appendix C for a listing of the Exec features on

the CP-SPF tape.

Note: The following Exec features; CARTIS, FBCIS, PAEXEC, SCSITIS, and

SINCH have been removed from the ClearPath OS 2200 15.0 release and in

addition CARTLIB has been removed from the ClearPath OS 2200 16.0 release.

Do not include these features in your Exec 49R2 build.

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.

9. Generate Exec level 49R2 (ClearPath OS 2200 release 16.0). Note that Exec 49R1

(in release 15.0) introduced a symbolic update to a 49-level base and that Exec

48R9 (in release 14.0) used a 48-level base. During system generation, all SGS

configuration labels found in the CO$CONFIG element are compared to a list of

valid configuration SGSs. See 4.1.2.4 for a listing of any obsolete SGS configuration

labels that should be removed.


7831 0349–046 7–19

If an invalid SGS is detected, the following error occurs and the 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

THE OBSOLETE SGS(S), OR CORRECT THE IMBEDDED SEMICOLON!

Beginning with ClearPath OS 2200 release 15.0, support for several obsolete

device and control units was removed. See section 4.1.2.4 for additional

information.

See 4.2.2 for more information about generating boot tapes for the correct system

type.

10. 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.8 for more information. C Compiler is part of the IOE and UOE.

11. Generate MCB 9R1 but do not install it yet. MCB 9R1 is a symbolic update.

12. Be aware that the MCB and CMR (Console Message Redisplay) products must remain in lockstep with the EXEC level.

Caution

When you are running EXEC level 48R9 (from ClearPath OS 2200 release

14.0), you must also use the release 14.0 levels of MCB and CMR. When

you are running EXEC level 49R2 (from ClearPath OS 2200 release 16.0), you

must also use the release 16.0 levels of MCB and CMR. There is no single

level of either MCB or CMR that can run on both of these EXEC levels.

Thus, every time you cross-boot back and forth between EXEC 48R9 and

EXEC 49R2, you must also install the corresponding levels of MCB and

CMR.


7–20 7831 0349–046

11. Perform a LIBSAVE of your current system to back up the products that you have just installed. See Section 5.46, “SOLAR and SOLAR/E” for more information.

12. Perform an orderly shutdown of your stepcontrol applications.

Note: Unisys recommends that any database be backed up at this point or after

the INIT on the new level documented in Step 17. Use the following discussion

information to determine which approach (Option A or Option B) works best for

your environment. Either option is correct, neither is required. You must decide

which approach satisfies your site needs and risk tolerance.

Backing up your database during the migration to release 16.0.

Option A

The operations-minded people recommend backing everything up before making a

major change.

Unisys recommends that you consider performing a LIBSAVE to ensure you have a

good backup point for your software, and this would be a good time to also

perform database backups.

This option involves performing a static dump after the application is stopped and

before rebooting on the new Exec 49R2 level, giving you a good copy of the

database before any changes are done.

Option B

The database/recovery-minded people recommend backing everything up after

the move to the new Exec 49R2 level has been completed.

Before moving, you have a good backup from the last dump along with the audit

trails. Should anything happen before or during the switch, you can use those as

you normally would. After coming up on the new level, getting another backup

gives you a good fallback point on the new side of the transition – assuring you

would not need to process over the transition if you needed recovery.

You could do this as dynamic dumps, making it possible to get the application

running sooner with minimized down time.

Note: Short and medium recoveries do not need to cross levels, since you INIT

between levels. Long recovery will cross levels if required (for example,

following a RELOAD from dump tapes before the switch). The reason for a

dump here is for security in knowing you will not need to execute special

recovery processing involving multiple timestamp and step-id formats.


7831 0349–046 7–21

13. Boot the Exec 49R2. 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

Installation and Configuration Guide.

Caution

If you boot EXEC 49R2 but later determine that you need to revert back to

EXEC 48R9, be aware that there is a fallback sequence which needs to be

strictly followed. See Section 7.3 for a detailed discussion of steps that you

must follow during the fallback process.

14. Install MCB 9R1. This new level of MCB is required by Exec 49R2. If you need to revert back to Exec 48R9, you must revert the MCB level to 8R3G (ClearPath

OS 2200 release 14.0).

15. Install CMR 3R1. This new level of CMR is required by Exec 49R2. If you need to revert back to Exec 48R9, you must revert the CMR level to 2R6 (ClearPath

OS 2200 release 14.0).

16. Install TIPUTIL 49R2.

Notes:

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.

The following applies if you use TIP Session Control:

• The TSC paging file record is resized. This is done automatically by PSFUTIL

when the application group is initialized

• Verify that the LIB$ file on your Exec 49R2 boot tape has the PSFUTIL

absolute from Exec 48R9 or higher.

• When dropping back from a Exec 49R2 to Exec 48R9 you must also be sure

that the LIB$ file on your Exec 48R9 contains a PSFUTIL absolute that is

from Exec level 48R9 or higher.

17. Bring up your application groups. You must do an INIT of your applications.

Note: If you did not perform a database backup before the orderly shutdown

of your database documented in Step 12 Option A, do the backup according to

Step 12 Option B now.


7–22 7831 0349–046

18. You may want to perform a LIBSAV now, if you intend to crossboot between the release 14.0 and release 16.0 environments.

Continue the migration, either using the steps described in 7.8 (Installing from Fast

Load Tapes) or 7.9 (Installing from Package Tapes).

7.7.2. Initial Migration Steps for Moving from Release 15.0 to

Release 16.0

1. Perform a LIBSAVE of your current system. See Section 5.46, “SOLAR and

SOLAR/E” for more information.

2. Start the REGISTERPKG runstream to register the ClearPath OS 2200 release 16.0

product key tape using the SOLAR 4R8 that is installed in your release 15.0

environment. A key tape is registered using the same steps as registration of a

package tape. The registration summary report will display all new product



following table).



products.




your installation.

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

COMUS 6R9C CP-FLD A COMUS is needed to generate the Exec

CPComm

Note: CPComm

is used only with

Dorado 700 and

800 Series systems.

6R5 CP-FLD A

AFCB

CMSA-CPCA

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.


7831 0349–046 7–23

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

CPCommOS Note:

CPCommOS is

used only with

Dorado 4000,

4100, 4200, 4300,

and 6300 Series

systems.

4R5 CP-FLD A

AFCB

CMSA-CPCA

XNIOP

There may be migration dependencies for the Dorado

4000, 4100, 4200, 4300, and 6300 systems. Before

beginning migration, refer to the following sections

for migration considerations:






Customers


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.

CryptoLib

Note: CPComm

does not build or

run unless

CryptoLib is

installed.

1R3 CP-FLD NOTFIPS The CryptoLib product is required by CPComm 6R5

and Cipher API 2R4A for installation. If CryptoLib is

not installed on your ClearPath 16.0 system, CPComm

and Cipher API terminate in error at initialization.



PCFP 3R3C CP-FLD A

ROLRUNS 4R3 CP-FLD A ROLRUNS is needed to ensure the Exec can be

placed on the DRS device.

SILAS 3R3B CP-FLD A CPComm requires SILAS for the demand connection.

SLIB 2R1 CP-FLD A

SOLAR 4R8 CP-FLD A


4. Prepare the ClearPath OS 2200 release 16.0 versions of the three library files: LIB$,

RUN$ and RLIB$. Beginning with Exec 49R1 (in release 15.0), the MCODE$ and

PRINTER$ library files were removed. The three remaining library files are

required for system generation, regardless of system type. Either copy the files

from the release master tape to another tape or catalog three 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.


7–24 7831 0349–046

Notes:





tape was needed to upgrade 48-level local code. The file name


PCF file.

5. Install the Separately packaged Exec features that you have ordered for your

system from the CP-SPF tape. See Appendix C for a listing of the Exec features on

the CP-SPF tape.

Note: The Exec CARTLIB feature has been removed from the ClearPath

OS 2200 16.0 release. CARTLIB is now incorporated in the standard Exec. Do not

include it in the features for your Exec 49R2 build.

Caution

Unisys Recommends that you perform an INSPECT generation before a






6. Generate Exec level 49R2 (ClearPath OS 2200 release 16.0). During system

generation, all SGS configuration labels found in the CO$CONFIG element are

compared to a list of valid configuration SGSs. See 4.1.2.4 for a listing of any

obsolete SGS configuration labels that should be removed.


stops:





See 4.2.2 for more information about generating boot tapes for the correct system

type.


7831 0349–046 7–25

7. 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.8 for more information. C Compiler is part of the IOE and UOE.

8. Perform a LIBSAVE of your current system to back up the products that you have

just installed. See Section 5.46, “SOLAR and SOLAR/E” for more information.

9. Boot the Exec 49R2 . 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.



Caution

If you boot EXEC 49R2 but later determine that you need to revert back to

EXEC 49R1, there may be special fallback procedures that need to be

strictly followed. See Section 7.3 for a detailed discussion of any steps that

you must consider during the fallback process.

10. Install TIPUTIL 49R2.

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.

Continue the migration, either using the steps described in 7.8 (Installing from Fast

Load Tapes) or 7.9 (Installing from Package Tapes).

Installing from Fast Load Tapes

7–26 7831 0349–046

7.8. Installing from Fast Load Tapes

Once you have completed the initial migration steps documented in either Section

7.7.1 or Section 7.7.2, use this section to install the remainder of release 16.0 products

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 CP-OE1A and CP-OE1B fast-load tapes are used

(see 7.5).

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.9). 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/UOE 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.





Dorado 4000”, “7.12 Migration for Dorado 4100 Customers”, “7.13 Migration for

Dorado 4200 Customers”, or “ 7.14 Migration for Dorado 4300 and Dorado 6300



7831 0349–046 7–27

1. Install the products contained on the fast-load tape CP-OE1A using the

INSTALLPKG runstream. Products on the tape are DAP, DMPLIB, OLTP-TM2200,

Security-ADMIN, and SIMAN.

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. Deactivate

the Security-Admin background run before installing CP-OE1A.

2. Install the following set of products.

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

CIFS 8R3 CP04 NORMAL

FLIT 15R2 CP07 A

3. Install the products contained on the fast-load tape CP-OE1B using the INSTALLIOE

runstream. See Appendix C for the contents of this tape. Note that the IRU

product should be installed in both mode IRU and mode FSAH.

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.31 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.18.

4. Install, configure, and boot OPE.

5. 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.

• Use the SOLAR full-screen interface to register and install specific products

and modes from each registered package tape. Start SILAS and CPComm or

CPCommOS to activate a demand terminal.


7–28 7831 0349–046

6. Install the following set of products. If you are moving up to ClearPath OS 2200

release 16.0 from release 14.0, you will have already installed URU-OS2200 as part

of step 3 in section 7.7.1 and do not need to re-install it in this step.

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

APEX 2.0 CP05 NORMAL Additionally you must install the Apex IIS web

application on a Windows server. See the ClearPath

OS 2200 Apex Getting Started Guide (8207 4055) for

installation instructions for the Apex IIS web

application.

CKRS 7R8B CP05 COMMON

BANK

FLEX 4R4A CP05 NOAUTO

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.

URU-OS2200 8.0 CP05 A Install URU 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).

UFTN 11R2 CP08 A

UCOB 12R2 CP08 A

ACOB 7R3M CP09 D

FTN 11R3 CP09 AFCB

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

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

cpFTP 4R3 CP11 A

DPS 6R6 CP11 A If you already installed the CP-OE2 tape, you do not

need to reinstall DPS.

CITA 2R4A CP-TRN A


7831 0349–046 7–29


Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

UDSC 20R1 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


DMS 22R1 CP14 NOREGISTER

DMSKEY 22R1 CP14 A

DMS-RA 4.1 CP14 A

RDMS 20R1 CP15 A

RDMSKEY 20R1 CP15 A If you already installed the CP-OE1B tape, you do not

need to reinstall RDMSKEY.

RDMS-JDBC 2.10 CP15 A

QLP 7R3C CP16 AFCB-DMS-P

SFS 4R1 CP16 COLLECTOR

UREP 16R1 CP16 A The installation user-id must be the same as the UREP

security officer.

Application group 3 must be up and recovered before

you install UREP.

UREPKEY 16R1 CP16 A

9. Install the products for which you are authorized from the following set.

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

MSAR 7R7D CP18 A

CULL 5R1C CP18 A

IACULL 5R1C CP18 A

MSMANAGER 5R7G CP18 A

PAR 9R3 CP18 A

TQD-FRAGGER 4R2 CP18 A

TQRDFRAGGER 4R2 CP18 A

Installing from Package Tapes

7–30 7831 0349–046

10. If you are migrating directly from ClearPath OS 2200 release 14.0 to release 16.0, skip this step and proceed to step 11, since you will have already installed these

products during an earlier part of your migration (step 3 in section 7.7.1). If you are

migrating from ClearPath OS 2200 release 15.0 to release 16.0, install any products

from the following set for which you are authorized:

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

LA 8R2 CP18 A

OSAM 7R6A CP18 A




more TUTIL information, refer to “Tape Labeling Utility

for ClearPath OS 2200 (TUTIL)” in Section 5.

TQ-BASELINE 7R5A CP18 A If you are authorized for TeamQuest Baseline®, do

not use the INSTALLPKG runstream to install CP18.


mutually exclusive.


mutually exclusive.

TQ-PMLOG 7R5 CP18 A



11. 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.9. Installing from Package Tapes

Once you have completed the initial migration steps documented in either Section

7.7.1 or Section 7.7.2, use this section to install the remainder of release 16.0 products

from package tapes.

This sequence describes how to migrate to the current release using the package

tapes to install products. If you install the products in the exact order presented here,

you will avoid possible interdependency conflicts.

Notes:

• This installation sequence uses the logical package name. See C.1 for more

information.


7831 0349–046 7–31









Dorado 4000”, “7.12 Migration for Dorado 4100 Customers”, “7.13 Migration for

Dorado 4200 Customers”, or “7.14 Migration for Dorado 4300 and Dorado 6300


1. Install DAP from tape CP02 and FLIT 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.

If you are moving up to ClearPath OS 2200 release 16.0 from release 14.0, skip

ahead to the next step. You will have already installed DMPLIB, URU-OS2200, and

IRU as part of step 3 in section 7.7.1 and do not need to re-install them at this time.

If the ClearPath OS 2200 release 16.0 levels of DMPLIB and URU-OS2200 (both on

tape CP05) and IRU (tape CP13) have not yet been installed, install them now. IRU

should be installed in both mode IRU and mode FSAH.

2. To administer security, install the following set of products.

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

APEX 2.0 CP05 NORMAL Additionally you must install the Apex IIS web application

on a Windows server. See the ClearPath OS 2200 Apex

Getting Started Guide (8207 4055) for installation

instructions for the Apex IIS web application.


Security-

Admin

4R4A CP05 A

SIMAN 7R2 CP18 SEC

CIFS 8R3 CP04 NORMAL

3. Use the INSTALLPKG runstream to install the default modes of URTS, LINK,

I18NLIB, and ELMS.

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

URTS 13R4 CP02 AFCB

LINK 12R2D CP03 A


7–32 7831 0349–046

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

I18NLIB 2R2A CP02 A

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.31 for more information.




The following steps describe the installation of product sets. Use either of the

following methods to install these products.




and modes from each registered package tape. Start SILAS and CPComm to

activate a demand terminal.

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

MAP 33R2 CP02 AFCB-FREE

ED 16R1F CP02 A

ELT 8R3C CP02 A

FAS 11R1A CP02 A

SSG 24R3 CP02 A

MASM 6R3L CP02 A

SLIB 2R1 CP02 A Previously installed from the CP-FLD Fast Load tape.

PDP 13R2D CP02 AFCB

LST 4R1J CP02 A

CML 1R1J CP02 A

UCSRTS 1R1M CP02 A

RSS 3R2N CP02 A After installing RSS, attach transfer files to RSS. They

cannot be transferred until DDP-PPC (CP10) is


7831 0349–046 7–33

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

installed.

COMAPI 8R1B CP-OE1B A CP-OE1B or CP-COMMSUITE.

PMD 32R2G CP04 A

MSCP 3R8E CP04 A

CKRS 7R8B CP05 Common bank

CITA 2R4A CP-TRN

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 10R7G CP04 A

PADS 13R4A CP05 AFCB

5. Install, configure, and boot OPE.


Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

LSS 14R4 CP06 A LSS and the UCS Compilers must be at the

same ClearPath OS 2200 release level.

PLUS 8R2O CP07 AFCB

UC 10R5 CP07 A

UPLS 8R1D CP08 DEFAULT

UFTN 11R2 CP08 A

UCOB 12R2 CP08 A

PCIOS 7R1C CP09 A

SORT 22R3 CP09 A

ACOB 7R3M CP09 D

FTN 11R3 CP09 AFCB

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


7–34 7831 0349–046

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

IPF 7R1D CP10 A Check the IPF 1100 Administration Guide for

configuration considerations when installing

IPF-compatible products (for example, DDP-FJT or

TAS).

DDP-PPC 7R4B CP10 A DDP-PPC must be properly conditioned for the

system security environment. See 5.18.

cpFTP 4R3 CP11 A

GSA 6R2E CP11 A

DPS 6R6 CP11 A

NTSI 7R3B CP11 A


Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

UDSC 20R1 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 20R1 CP15 A

RDMS 20R1 CP15 A

DMSKEY 22R1 CP14 A


DMS-RA 4.1 CP14 A

UREPKEY 16R1 CP16 A

UREP 16R1 CP16 A The installation user-id must be the same as the

UREP security officer.

Application group 3 must be up and recovered

before you install UREP.






7831 0349–046 7–35

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

CIPHER-API 2R4A CP17 A

OLTP-

TM2200

12R1F CP17 A

OSI-TP 9R1K CP17 A

WEBTS 6R1 CP17 A


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.

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

MSAR 7R7D CP18 A

CULL 5R1C CP18 A

IACULL 5R1C CP18 A


PAR 9R3 CP18 A



11. If you are migrating directly from ClearPath OS 2200 release 14.0 to release 16.0, skip this step and proceed to step 12, since you will have already installed these

products during an earlier part of your migration (step 3 in section 7.7.1). If you are

migrating from ClearPath OS 2200 release 15.0 to release 16.0, install any products

from the following set for which you are authorized:

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

LA 8R2 CP18 A

OSAM 7R6A CP18 A




more TUTIL information, refer to “Tape Labeling Utility

for ClearPath OS 2200 (TUTIL)” in Section 5.

Initializing an Existing System (I-Boot)

7–36 7831 0349–046

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

TQ-BASELINE 7R5A CP18 A If you are authorized for TeamQuest Baseline®, do not

use the INSTALLPKG runstream to install CP18.


mutually exclusive.


mutually exclusive.

TQ-PMLOG 7R5 CP18 A



12. 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.10. 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 16.0 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 16.0 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-OE1A, CP-OE1B,

and CP-OE2 (see descriptions in 7.5).


7831 0349–046 7–37

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.1

might cause the following installation sequence to fail.

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.




following table).



products.




your installation.


7–38 7831 0349–046

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

COMUS 6R9C CP-FLD A COMUS is needed to generate the Exec.

CPComm

Note:

CPComm is

used only

with Dorado 700 and 800

Series

systems.

6R5 CP-FLD A

AFCB

CMSA-CPCA

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).

CPCommOS Note:

CPCommOS

is used only

with Dorado

4000, 4100,

4200, 4300,

and 6300

Series

systems.

4R5 CP-FLD A

AFCB

CMSA-CPCA

XNIOP

ClearPath OS 2200 release 16.0 may introduce migration

dependencies for the Dorado 4000, 4100, 4200, 4300,

and 6300 systems. Before beginning migration, refer to

the following sections for migration considerations:






Customers


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 5).

CryptoLib

Note: CPComm

does not

build or run

unless

CryptoLib is

installed.

1R3 CP-FLD NOTFIPS The CryptoLib product is required by CPComm 6R5 and

Cipher API 2R4A for installation. If CryptoLib is not

installed on your release 16.0 system, CPComm and

Cipher API terminate in error at initialization.



PCFP 3R3C CP-FLD A

ROLRUNS 4R3 CP-FLD A ROLRUNS is needed to ensure the Exec can be placed

on the DRS device.

SILAS 3R3B CP-FLD A SILAS is needed to run a demand session. SILAS

requires CPComm (including mode AFCB) to access the

network.

SLIB 2R1 CP-FLD A

SOLAR 4R8 CP-FLD A SOLAR is needed to register the product key tape.



7831 0349–046 7–39

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.

5. Start the REGISTERPKG runstream to register the ClearPath OS 2200 release 16.0 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


6. For metering-based systems

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 8.0 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. Note that IRU (CP-OE1B) should be installed in both mode IRU and

mode FSAH.

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.9.

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.31 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.18.


7–40 7831 0349–046

• For ClearPath OS 2200 release 16.0 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 16.0 versions of these library files: LIB$,

RUN$, and RLIB$. All three of these files are required for system generation,

regardless of system type. Either copy the files from the release master tape to

another tape or catalog three 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:





tape is needed to upgrade 48-level local code. The file name


PCF file.

10. 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.

11. Generate Exec level 49R2 (ClearPath OS 2200 release 16.0). 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.


stops:






7831 0349–046 7–41

Caution

Unisys recommends that you perform an INSPECT generation before a






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.8 for more information.

13. If your site requires a customized TIPUTIL, build the level of TIPUTIL that 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 level. Previous levels of TIPUTIL might not be compatible with the target

Exec level.


The following steps describe the installation of product sets. You can select either

of two methods to install these products.




and modes from each registered package tape. Start SILAS and CPComm to

activate a demand terminal.

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.


7–42 7831 0349–046

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation Mode

Notes

APEX 2.0 CP05 NORMAL Additionally you must install the Apex IIS web

application on a Windows server. See the

ClearPath OS 2200 Apex Getting Started

Guide (8207 4055) for installation instructions

for the Apex IIS web application.

IRU 22R2 CP13 IRU Also install MODE FSAH.

CKRS 7R8B CP05 COMMONBANK


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 15R2 CP07 A

UFTN 11R2 CP08 A

UCOB 12R2 CP08 A

ACOB 7R3M CP09 D

FTN 11R3 CP09 AFCB


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.

Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

DDP-FJT 5R5L CP10 A

cpFTP 4R3 CP11 A

TAS 6R2L 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 6R6 CP11 A If you already installed the CP-OE2 tape, you do not

need to reinstall DPS.


7831 0349–046 7–43


Installation

and Support

Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

UDSC 20R1 CP13 AP3 You must have APP3 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


RDMSKEY 20R1 CP15 A If you already installed the CP-OE1B tape, you do not

need to reinstall RDMSKEY.

RDMS 20R1 CP15 A

DMSKEY 22R1 CP14 A


DMS-RA 4.1 CP14 A

UREPKEY 16R1 CP16 A

UREP 16R1 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.

APP3 must be up and recovered before you install

UREP.





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.


7–44 7831 0349–046

Installation and

Support Name

Level

Logical

Tape

Name

Default

Installation

Mode

Notes

SIMAN 7R2 CP18 SEC If you already installed the CP-OE1A tape, you do not

need to reinstall SIMAN .

MSAR 7R7D CP18 A

CULL 5R1C CP18 A

IACULL 5R1C CP18 A



PRODRV utility. For more TUTIL information, see

section 5.


LA 8R2 CP18 A

OSAM 7R6A CP18 A

PAR 9R3 CP18 A

TQ-BASELINE 7R5A CP18 A TQ-ONLINE and TQ-BASELINE are mutually exclusive.

TQ-ONLINE 7R5A CP18 A TQ-ONLINE and TQ-BASELINE are mutually exclusive.




20. You can now tailor the ClearPath OS 2200 release 16.0 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

tape was registered to determine which products remain.

• OS 2200 Exec. Refer to the Exec System Software Installation and


• Transaction Processing (TIP). Refer to the Transaction Processing

Administration and Operations Reference Manual.

• Message Control Bank (MCB). Refer to the MCB Administration and

Operations Guide.

• IRU. Refer to the Integrated Recovery Utility Administration Guide.

• Security. Refer to the Security Administration for ClearPath OS 2200 Help.

Migration for Dorado 4000 Customers

7831 0349–046 7–45

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 information from this file to reestablish the system profile.

7.11. Migration for Dorado 4000 Customers

Table 7–4 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–4 to verify if the product levels that you plan to install are

supported.

Table 7–4. Dorado 4000 Plateau and ClearPath Release

Interdependencies

Dorado 4000 ClearPath

OS 2200 Release

14.0

ClearPath

OS 2200 Release

15.0

ClearPath

OS 2200 Release

16.0

Plateau 2.3 and additionally

2.3-CP13.1-4000-COMPATIBILI

TY.sup

This requires you configure

the network using the new

CPCommOS configuration

statements and ensures you

have all of the plateau updates

CPCommOS 4R3

is the supported

level

CPCommOS 4R4

is the supported

level

CPCommOS 4R5

is the supported

level

Plateau 2.4 (no additional

compatibility package is

required)

CPCommOS 4R3

is the supported

level

CPCommOS 4R4

is the supported

level

CPCommOS 4R5

is the supported

level

Note: 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.


For Dorado 4100 systems, ClearPath OS 2200 release 16.0 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 16.0 Release.


For Dorado 4200 systems, ClearPath OS 2200 release 16.0 is paired with Plateau 1.0 or

higher.

Migration for Dorado 4300 and Dorado 6300 Customers

7–46 7831 0349–046

7.14. Migration for Dorado 4300 and Dorado 6300 Customers


higher.


higher.

7831 0349–046 8–1

Section 8 Operations Sentinel (Formerly Single Point Operations)

ClearPath OS 2200 release 16.0 supports Operations Sentinel Basic Edition level

15.0. This version supports all Dorado models for OS 2200 systems. To run this

version, you need a server running Microsoft Windows Server 2008 or 2012.

Refer to the migration requirements section of the ClearPath Enterprise Servers

Operations Sentinel Software Release Announcement for considerations while

migrating from older Operations Sentinel levels.

Operations Sentinel (Formerly Single Point Operations)

8–2 7831 0349–046

7831 0349–046 A–1

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 Workload IOE (A.2)

− Products in all IOEs independent of server or workload (Table A–1)

− Additional products in the IOE dependent on server or workload (Table A–2)

• Dorado Models Workload UOE (A.3)

− Products in all UOEs independent of server or workload (Table A–3)

− Additional products in the General Purpose or SDK UOE dependent on server

or workload (Table A–4)

− Additional products in the BIS and EAE UOE dependent on server or workload

(Table 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 mandatory feature TAVR. 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 4000, 4100, 4200, 4300, and 6300

Server systems.

− CMOS systems – ClearPath Dorado 700 and 800 Server systems.

Software Packaging

A–2 7831 0349–046

Note: The boot tape delivered with ClearPath Dorado 4000, 4100, 4200, 4300,

and 6300 Server systems will not boot on Dorado 800 or 700 Server systems

and the boot tape delivered with Dorado 800 or 700 Server systems will not

boot on Dorado 4000, 4100, 4200, 4300, and 6300 Server systems.

• Exec base symbolics tape

This tape contains the source code for the current base level of the Exec, which is

level 49. 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 nonmetered systems)

Mandatory Integrated Operating Environment (IOE) products are delivered on

package tapes in a keyed, buildable format.

• UOE software (ClearPath 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.

Dorado Models Workload IOE

7831 0349–046 A–3

A.2. Dorado Models Workload IOE

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.

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.

Table A–1. Products in all IOEs

Installation and Support

Name

General

Purpose SDK BIS EAE

APEX X X X X

CIFS X X X X

CIPHER API X X X X

CITA X X X X

CML X X X X

CMR X X X X

COMAPI X X X X


A–4 7831 0349–046



Name

General

Purpose SDK BIS EAE

COMUS X X X X

CryptoLib X X X X

DAP X X X X

DDP-PPC X X X X

DMPLIB X X X X

DPREP1100 X X X X

DPS 2200 X X X X

DTI X X X X

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

FLEX X X X X

FURPUR X X X X

GSA X X X X

I18NLIB X X X X

IPF X X X X

IRU X X X X

J2EE-CON-OPENDTP X X X X


7831 0349–046 A–5



Name

General

Purpose SDK BIS EAE

J2EE-CON-OS2200 X X X X

LINK X X X X

LIST X X X X

LSS X X X X

MAP X X X X

MASM X X X X

MCB X X X X

MSCP X X X X

NTSI X X X X

Open OLTP HTP/ic

(HTP/ic-2200) X X X X

Open/OLTP 2200

Transaction Manager X X X X

PADS X X X X

PCFP X X X X

PCIOS X X X X

PDP X X X X

PLUS X X X X

PMD X X X X

ROLRUNS X X X X

RSS X X X X

SECOPT1 X X X X

SECURITY-ADMIN X X X X

SFS X X X X


A–6 7831 0349–046



Name

General

Purpose SDK BIS EAE

SILAS X X X X

SLIB X X X X

SOLAR X X X X

SORT X X X X

SP-OPERATION/

Basic Edition X X X X

SSG X X X X

SYSLIB X X X X

TAVR X X X X

TIPUTIL X X X X

UCS C X X X X

UCSRTS X X X X

UDSC 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.

• UREP in UDSC can be used to create and maintain storage-area

definitions for DMS.

UPLS X X X X

URTS X X X X

Web Transaction Server

Includes Java DPS 25

licenses

X X X X

Web Transaction Server

Includes Java DPS 25

licenses

X

X

X

X


7831 0349–046 A–7




Table A–2. Additional IOE products based on System and Workload

Installation and

Support Name

General Purpose SDK BIS EAE

880E/880

860/840

780/740

6380

4380 4280

4180 4080

880E/880/860/840 780/740

6300 4380

4280 4180 4080

ACOB X X

BIS IOE identifier

(paper doc) X

CKRS X

CPComm X (800/700

ONLY)

X (800/700

ONLY)

X (800/700

ONLY)

X (800/700

ONLY)

CPCOMMOS X (6300 ONLY) X

X (6300/4x00

ONLY)

X (6300/4x00

ONLY)

X (6300/4x00

ONLY)

DDP-FJT X

DFP X

DMS-RA X

EAE IOE identifier

(paper doc) X

FLIT X

FTN X

InfoAccess CONNECT

LIC X

InfoAccess QUERY X

MAPPER OPEN/OLTP X

MAPPER System

for 2200 X

MRI X

MSMQI X

QLP X

QLP/PCIOS X

RDMS-JDBC X X X

SDK IOE identifier

(paper doc) X

SECOPT2 X


A–8 7831 0349–046

Table A–2. Additional IOE products based on System and Workload

Installation and

Support Name


880E/880

860/840

780/740

6380

4380 4280

4180 4080

880E/880/860/840 780/740

6300 4380

4280 4180 4080

SOLAR/E X

TAS X

TRAM X

TUTIL X

UCOB X X

UDS DMSKEY

Note: This product

delivers the full

functionality of DMS.

X

UDS RDMSKEY

Note: This product

delivers the full

functionality of

RDMS.

X X X

UFTN X

UNIACCESS-ODBC (2

concurrent threads

key)

X X

Unit Duplexing X

UDS UREPKEY

Note: This product

delivers the full

functionality of

UREP.

X X

Virtual Tape Handler X

Dorado Models Workload UOE

7831 0349–046 A–9

A.3. Dorado Models Workload UOE

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.

• OS 2200 Software Development Kit (SDK) Package

This package includes the standard UOE 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 UOE 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) 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 Business Continuance (BC) Workload UOE

The Business Continuance offering is designed for clients with metered ClearPath

servers who need protection from planned and unplanned outages. BC workloads

include all of the mandatory products required to backup another production

metered server. Business Continuance is available for General Purpose, SDK, BIS,

and EAE workloads.


A–10 7831 0349–046




Table A–3. Products in all UOEs

Installation and

Support Name


APEX X X X X

CIFS X X X X

CIPHER API X X X X

CITA X X X X

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

CryptoLib X X X X

DAP X X X X

DDP-PPC X X X X

DMPLIB X X X X

DPREP1100 X X X X

DPS 2200 X X X X

DTI X X X X

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

FLEX X X X X

FURPUR X X X X

GSA X X X X

I18NLIB X X X X


7831 0349–046 A–11


Installation and

Support Name


IPF X X X X

IRU X X X X

J2EE-CON-OPENDTP X X X X

J2EE-CON-OS2200 X X X X

LINK X X X X

LIST X X X X

LSS X X X X

MAP X X X X

MASM X X X X

MCB X X X X

MSCP X X X X

NTSI X X X X

Open OLTP HTP/ic

(HTP/ic-2200) X X X X

Open Distributed

Transaction

Processing

(OLTP-TM2200)

X X X X

PADS X X X X

PCFP X X X X

PCIOS X X X X

PDP X X X X

PLUS X X X X

PMD X X X X

ROLRUNS X X X X

RSS X X X X

SECOPT1 X X X 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


A–12 7831 0349–046


Installation and

Support Name


SORT X X X X

SP-OPERATION/

Basic Edition X X X X

SSG X X X X

SYSLIB X X X X

TAVR X X X X

TIPUTIL X X X X

UCS C X X X X

UCSRTS X X X X

UDSC 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.

• UREP UDSC can be used to create and maintain storage-area

definitions for DMS.

UPLS X X X X

URTS X X X X

URU-OS2200 X X X X

Web Transaction

Server Java DPS 25

licenses

X X X X

Web Transaction

Server: Java DPS 25

licenses

X X X X


7831 0349–046 A–13




Table A–4. Additional UOE products based on System, General Purpose and

SDK Workload

Installation and

Support Name

General Purpose SDK

890E/890

850/870

790/750

6390

4390/4370/4350

4290/4270/4250

4190/4170/4150

4090

4050

850/870

890E/890

790/750

6390

4390/4370/4350

4290/4270/4250

4190/4170 4090

ACOB X X X X

CKRS X X X X

CPCOMM X (700/800

ONLY) X (700/800 ONLY)

CPCommOS X (6300 ONLY) X X X (4x00/6300 ONLY)

DDP-FJT X X

DFP X X X X

DMS-RA X X X

FLIT X X X X

FTN X X X X

InfoAccess

CONNECT LIC X X X

InfoAccess QUERY X X X

MSMQI X X X X

QLP X X X X

QLP/PCIOS X X X X

RDMS-JDBC X X

SDK IOE identifier

(paper doc) X

SECOPT2 X X X X

SOLAR/E X X X X

TAS X X X X

TUTIL X X X X

UCOB X X X X


A–14 7831 0349–046

Table A–4. Additional UOE products based on System, General Purpose and

SDK Workload

Installation and

Support Name

General Purpose SDK

890E/890

850/870

790/750

6390

4390/4370/4350

4290/4270/4250

4190/4170/4150

4090

4050

850/870

890E/890

790/750

6390

4390/4370/4350

4290/4270/4250

4190/4170 4090

UDS DMSKEY

Note: This product

delivers the full

functionality of

DMS.

X X X

UDS RDMSKEY

Note: This product

delivers the full

functionality of

RDMS.

X X

UFTN X X X X

UNIACCESS-ODBC

(2 simultaneous

connections key)

X X

Unit Duplexing X X X X

UDS UREPKEY

Note: This product

delivers the full

functionality of

UREP.

X X X X

Virtual Tape Handler X X X X


7831 0349–046 A–15




Table A–5. Additional UOE products based on System, BIS and EAE Workload

Installation and

Support Name

BIS EAE

890E/890

870/850

790/750

6300

4390/4370/4350

4290/4270/4250

4190/4170/4150

4090/4050

890E/890

870/850

790/750

6300

4390 4290

4190 4090

ACOB X X X

BIS IOE identifier

(paper doc) X X

CPCOMM X (800/700 ONLY)

X (800/700

ONLY)

CPCommOS X (6300 ONLY) X X (6300 ONLY) X

EAE IOE identifier

(paper doc) X X

MAPPER

OPEN/OLTP X X

MAPPER System

for 2200 X X

MRI X X

RDMS-JDBC X X

TAS X X

TRAM X X

UCOB X X X

UDS RDMSKEY

Note: This product

delivers the full

functionality of

RDMS.

X X

UDS UREPKEY

Note: This product

delivers the full

functionality of

UREP.

X X


A–16 7831 0349–046

7831 0349–046 B–1

Appendix B Product Interdependencies

This appendix contains an interdependency matrix for the software products in this

release. Table B–2 identifies specific ClearPath OS 2200 release 16.0 products that are

required by other Release 16.0 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. This column assumes that the products

listed in Table B–1 are installed on the system. These products are included in the

IOE and UOE.

Exec separately packaged features are not listed because you need only the

IOE/UOE products to build, install, or execute them.

• 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–3 for more detailed information about the interdependencies

associated with these products. In this column, notes refer to information in

Table B–3.

Note: The Required to Build column does not apply to absolute (nonsymbolic)

versions of these products.

Product Interdependencies

B–2 7831 0349–046

Table B–1. Required System Products

CML FURPUR ROLRUNS

CMR GSA RSS

COMUS I18NLIB SILAS

CPComm LINK SLIB

CPCommOS LIST SOLAR

DAP MAP SSG

DMPLIB MASM SYSLIB

DPREP1100 MSCP UCSRTS

ED PCFP UPLS

ELMS PDP URTS

ELT PLUS

EXEC PMD


7831 0349–046 B–3

Table B–2. Products Interdependency Matrix

Installation and

Support Name

Required to

Install Required to Build

Required to

Execute

Optional Products

(see Table B–3)

ACOB PCIOS, SORT CKRS, DFP, DMS, FTN,

PADS, PCIOS, SFS,

SORT

APEX Not buildable FLEX, COMAPI

CIFS Not buildable COMAPI

Cipher API Not buildable CryptoLib

CITA UC COMAPI, MCB

CKRS

CML

CMR MSCP

COMAPI UC

COMUS ACOB, PCIOS, SORT ACOB, PCIOS, SORT

CPComm LSS, UC, CryptoLib CryptoLib

CPCommOS LSS, UC

cpFTP Not buildable UC

Cryptolib Not buildable

CULL SORT SORT

(See 3.7 for

TeamQuest key

information.)

DAP Not buildable DPS, LINK See note about LINK.

DDP-FJT DDP-PPC, IRU, LSS DDP-PPC ACOB, DPS, IPF,

UCOB

DDP-PPC UC LSS ACOB, DPS, MCB, UC,

UCOB, UFTN

DEPCON-2200 Not buildable

DFP PCIOS, SFS

DMS UDSC, UREP ACOB, SORT ACOB, FTN, QLP,

UCOB, UFTN, UDSC,

UREP

Security-Admin,

SIMAN, SORT, UREP,

DMSKEY

DMS-RA Not buildable COMAPI, DMS, UREP, OLTP-TM2200

JBOSS-2200

DPREP1100 Not buildable

DPS ACOB ACOB, CULL, FTN,

UCOB, UFTN


B–4 7831 0349–046


Installation and

Support Name

Required to


Required to

Execute

Optional Products

(see Table B–3)

DTI Not buildable Windows CITA, OLTP-TM2200

ELMS UC

ELT

EXEC

EXPIPE Not buildable PCIOS ACOB, SORT, UCOB

FAS SORT SORT

FDP-ADP SORT QLP

FLEX Not buildable

FLIT DPS

FTN PCIOS PCIOS CKRS, DFP, SFS, SORT

FURPUR SORT SORT

GSA

HTPIC-2200 LSS DDP-PPC, LSS,

OLTP-TM2200

DTI

I18NLIB Not buildable UREP

INFOACCESS Not buildable DMS, Windows

INTERCONNECT DDP-PPC, CIFS,

URTS

Not buildable CIFS, COMAPI,

DDP-PPC

IPF RDMS

IRU SORT, UC MCB, SORT, UDSC

JBOSS-2200 CIFS Not buildable CIFS, COMAPI, JPJVM J2EE-CON-OPENDTP,

J2EE-CON-OS2200,

OLTP-TM2200, RDMS,

RDMS-JDBC, DMS,

DMS-RA

JPJVM CIFS, Interconnect Not buildable CIFS, LSS, UC,

Interconnect

OLTP-TM2200,

DMS-RA,BIS-RA,

RDMS-JDBC,

J2EE-CON-OS2200,

J2EE-CON-OPENDTP,

JBOSS-2200, MCB

J2EE-CON-OS2200 Not buildable CITA, COMAPI, MCB JBOSS-2200


7831 0349–046 B–5


Installation and

Support Name

Required to


Required to

Execute

Optional Products

(see Table B–3)

LA PCIOS, SORT PCIOS, SORT

(See 3.7 for

TeamQuest key

information.)

LINK UC URTS CIFS, LSS

LIST

LSS UC, UFTN SFS, UC, UCOB, UFTN

MAP

MASM

MCB DAP

MSAR PCIOS, SORT PCIOS, SORT

(See 3.7 for

TeamQuest key

information.)

MSMANAGER Not buildable PCIOS, SORT

(See 3.7 for

TeamQuest key

information.)

DPS

MSMQI Not buildable NTSI, Windows

Message Queuing

(MSMQ)

See notes.

NTSI Not buildable COMAPI, Windows

2008 Server or higher

FLEX

See notes.

OLTP-TM2200 ACOB, UC, UCOB, LSS LSS

OPE RDMS, UC, UCOB

OSAM UC, LSS (See 3.7 for

TeamQuest key

information.)

OSI-TP LSS, UC DDP-PPC, LSS,

OLTP-TM2200

DTI

PADS FTN, LSS, UC, UFTN,

URTS, LINK

LSS, URTS, LINK FTN, ACOB, UC,

UCOB, UFTN, SORT

PAR FTN (See 3.7 for

TeamQuest key

information.)

PCFP Not buildable

PCIOS DFP, ACOB, FTN, QLP,

SORT, UC, UCOB,


B–6 7831 0349–046


Installation and

Support Name

Required to


Required to

Execute

Optional Products

(see Table B–3)

UFTN

PDP

PLUS Not buildable PADS, PCIOS

PMD

QLP DMS, PCIOS, SORT SORT UREP, DMS, PCIOS,

RDMS

RDMS UDSC, UREP CIFS, SORT CIFS, SORT, UDSC,

UREP, I18NLIB

ACOB, FTN, IPF, MRI,

QLP, UC, UCOB,

UFTN, EAE,

RDMSKEY, UREPKEY

RDMS-JDBC RDMS Not buildable COMAPI, RDMS, UREP OLTP-TM2200,

JBOSS-2200, CIFS,

I18NLIB, JPJVM

ROLRUNS Not buildable FAS

RSS DDP-PPC

SAUTILITIES Not buildable (See 3.7 for

TeamQuest key

information.)

Security-Admin Not buildable cpFTP, TAS FLEX

SFS UDSC, UREP DFP, UREP, ACOB,

FTN, UCOB, UFTN

SILAS SORT

SIMAN SORT (See 3.7 for

TeamQuest key

information.)

SLIB Not buildable

SOLAR Not buildable FAS

(See note about

FURPUR.)

SOLAR/E Not buildable FAS

(See note about

FURPUR.)

SORT PCIOS, I18NLIB PCIOS CKRS, I18NLIB

SP-OPERATION Not buildable

SP-OPERATION CP Not buildable

SSG

SYSLIB


7831 0349–046 B–7


Installation and

Support Name

Required to


Required to

Execute

Optional Products

(see Table B–3)

TAS DDP-PPC, IRU, LSS DDP-PPC, IRU ACOB, DPS, IPF,

UCOB, UDSC, UFTN

TIP-LA LSS Not buildable (See 3.7 for

TeamQuest key

information.)

TIPUTIL FTN, UC

TQ-BASELINE Not buildable (See 3.7 for

TeamQuest key

information.)

COMAPI, TQ-MODEL,

Cipher-API

TQ-MODEL Not buildable TQ-BASELINE (See 3.7

for TeamQuest key

information.)

TQ-ONLINE Not buildable TQ-VIEW (See 3.7 for

TeamQuest key

information.)

Cipher-API

See note about

TQ-VIEW.

TQ-PMLOG TQ-BASELINE Not buildable TQ-BASELINE (See 3.7

for TeamQuest key

information.)

TQ-PROBES TQ-BASELINE Not buildable TQ-BASELINE (See 3.7

for TeamQuest key

information.)

TQD-FRAGGER Not buildable URTS

(See 3.7 for

TeamQuest key

information.)

TQRDFRAGGER Not buildable URTS

(See 3.7 for

TeamQuest key

information.)

TUTIL Not buildable

UC LSS PCIOS, LSS CKRS, DFP, DPS,

MCB, PADS, RDMS,

SFS, SORT, UREP,

CIFS, I18NLIB

UCOB LSS LSS, PCIOS CIFS, DMS, PADS,

RDMS, SFS, SORT,

UREP, CKRS, DFP,

DPS, I18NLIB, MCB,

PCFP

UCSRTS


B–8 7831 0349–046


Installation and

Support Name

Required to


Required to

Execute

Optional Products

(see Table B–3)

UDSC SORT RDMS, UREP

UFTN LSS LSS, PCIOS CKRS, DFP, DMS,

DPS, MCB, PADS,

RDMS, SFS, SORT,

UREP, PCFP

UNIACCESS-ODBC Not buildable RDMS

UPLS Not buildable LSS PADS, PCIOS

UREP RDMS,UDSC UC SORT, I18NLIB, RDMS,

UDSC

DMS, DPS, RDMS, IPF,

UC, UCOB, UFTN

URTS LSS, UC, PCIOS, UFTN PCIOS, SORT, CIFS

URU-OS2200 Not buildable IRU

WEBTS CIFS Not buildable TAS, cpFTP, FLEX

WMQ2200 INTERCONNECT,

SOLAR

MCB, OLTP-TM2200 INTERCONNECT,

COMAPI, DDP-PPC

OLTP-TM2200, BIS

XRLOAD Not buildable SORT


7831 0349–046 B–9

Table B–3. Optional Product Interdependency Notes

Installation and

Support Name

Interdependency Notes

ACOB CKRS, DFP, DMS, PADS, PCIOS and/or SFS are required to use their respective

capabilities with ACOB.

FTN is required to access FORTRAN from a COBOL program.

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 populate and access DMS

databases.

SORT is required if the DRU or DMU components of DMS are used.

UREP can be used with DMS operations.

SIMAN or SECURITY-ADMIN is needed to define ACRs if ACRS are used to

control access to the database or to control file security.

DMS-RA OLTP-TM2200 is required for global (XA) transaction support.

JBoss-2200 is required to run Java DMS applications on the 2200 in a JBoss

environment.


B–10 7831 0349–046


Installation and

Support Name


DPS COMUS, CULL, and LINK are optional generation dependencies.

FTN, I18NLIB, LSS, UCOB, UFTN are optional execution dependencies.

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 to use the Define File capabilities with FORTRAN.

SFS is required to use the Shared File capabilities of SFS with FTN.

SORT is required to do a sort in a FORTRAN program.

CKRS is required to use Checkpoint Restart in a FORTRAN program.

FURPUR PCFP is an optional generation dependency.

ELMS, PCFP, and SORT are optional execution dependencies.

HTPIC-2200 CPComm is required.

DTI is required if you want transactions to communicate with Microsoft

Transaction Services.

I18NLIB UREP is required to use ASCII like Coded Character Sets (CCCs).

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.

UDSC is required only for applications that use UDSC.


7831 0349–046 B–11


Installation and

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

The CIFSLD processor requires CIFS.

LSS SFS is required to use shared access to data files with locking and recovery

features.

UC must be installed and executed with LSS to compile C programs.

UCOB must be installed and executed with LSS to compile COBOL programs.

UFTN must be installed and executed with LSS to compile FORTRAN

programs.

MSMANAGER DPS is required to use the full screen interface.

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.


B–12 7831 0349–046


Installation and

Support Name


NTSI MAPI compliant client on a Windows server is required for Mail Service

Integration.

User Authentication (FLEX) on the OS 2200 and an OS 2200 Uniscope Emulator

on the workstation are required for network authentication.

Windows 2008 Server or higher is required for network authentication and for

OS 2200 SSPI support.

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 to change the file description without recompiling the

program.

ACOB, FTN, QLP, SORT, UC, UCOB and/or UFTN can be used to read or write

files with PCIOS.

PCFP ELMS is an optional execution dependency.

PLUS PADS is required to perform interactive debugging.

PCIOS is required for PLUS programs that use file IO.

QLP UREP is required if QLP is used to retrieve data from a DMS or RDMS

database.

QLP can be used to retrieve data from a DMS or RDMS database.

QLP can be used to retrieve data from PCIOS data files.

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.

IPF is required only to access RDMS interactively through the IPF SQL

Interface.

EAE is required when EAE is used on OS 2200 machines.

The BIS Relational Interface (MRI) is required to access RDMS databases from

BIS.

QLP is required to produce QLP query reports on data in an RDMS database.

UREPKEY (UDS UREPKEY) is required to use the UREP REPORT

COBOL/C/FORTRAN command or UREP-XREF feature.

RDMSKEY (UDS RDMSKEY) is required to create tables.


7831 0349–046 B–13


Installation and

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 global (XA) transaction

support.

CIFS is required to install the downloadable version of RDMS-JDBC.

JPJVM is required to run a JAVA component on the J-Processor.

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.

ACOB, FTN, UCOB and/or UFTN are required to reference SFS.

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 required to use the CKPT parameter.

I18NLIB is required dependent on SORT’s usage of the CCSLOCNUM and

CCLOCNUMCHK configuration parameters and the values of the LOCAL and

CODE-TYPE processor parameters.

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.


B–14 7831 0349–046


Installation and

Support Name


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.

TQ-VIEW TeamQuest View® (TQ-VIEW) requires Microsoft Windows.

UC CKRS, DFP, DPS, I18NLIB, MCB, PCFP, SFS, SORT and/or UREP are required to

use their respective capabilities with UC.

PADS is required to perform interactive debugging.

RDMS is required to execute programs containing calls to RSA.

CIFS is required to build or execute CIFSCC. If CIFS is not installed, CIFSCC is

not rebuilt.

UCOB CIFS is required to use the ZIP/UNZIP routines.

CKRS, DFP, DPS, DMS, I18NLIB, MCB, PCFP, RDMS, SFS, SORT and/or UREP

are required to use their respective capabilities with UCOB.

PADS is required to perform interactive debugging.

UFTN CKRS, DFP, DPS, DMS, I18NLIB, MCB, PCFP, RDMS, SFS, SORT and/or UREP

are required to use their respective capabilities with UFTN.

PADS is required to use the debugging capabilities of PADS with UFTN.

UPLS PADS is required to perform interactive debugging.

PCIOS is required to do SEQUENTIAL or DIRECT I/O.

UREP DMS is required to execute the PROCESS SCHEMA. PROCESS SUBSCHEMA,

and ATTACH commands.

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 to use the DPS form definition.

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.

CIFS is required to use the ZIP/UNZIP routines.

SORT is required to use the SORT interfaces defined in UCOB and UFTN.

URU-OS2200

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.


7831 0349–046 B–15


Installation and

Support Name


WEBTS Requires Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2,

Windows Server 2012, or Windows Server 2012 R2 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–046

7831 0349–046 C–1

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.6. For information about the IXS 4000-BLD style, see 3.8.

C.1. Logical Package Tape Definition

Unisys software for the Dorado 700, 800, 4000, 4100, 4200, 4300, and 6300 systems is

delivered on DVD media. This software packaging strategy allows the host-based

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 from

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.

Products on Fast-Load Tapes

C–2 7831 0349–046

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)

and Unisys Operating Environment (UOE) products, Unisys has created the following

fast-load tapes: CP-FLD, 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

register 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.8.

Note: Once IOE/UOE products have been installed from fast-load tape, they need

not be reinstalled from a package tape unless your site requires a customized

installation.

C.2.1. Fast-Load Tapes CP-FLD

The fast-load tape CP-FLD is the first tape that you should load. The CP-FLD tape is to

be used for all systems. The CP-FLD tape contains 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.

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

Installation and

Support Name

Product Name

COMUS COMUS

CPComm Communications Platform (CMOS systems CP-FLD tape)

CPCommOS Communications Platform for Open Systems (SAIL-based

systems CP-FLD tape)

CryptoLib Cryptographic Library

FURPUR File Utility Routines/Program Utility Routines


7831 0349–046 C–3

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

Installation and

Support Name

Product Name

PCFP Program-Callable FURPUR

ROLRUNS Roll-Out/Roll-Back Runstream

SILAS System Interface for Legacy Application Systems

SLIB Service Library

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.

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

Installation and

Support Name

Product Name

DAP Dump Analysis Procedures

DMPLIB DMPLIB

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/UOE 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.

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

Installation and

Support Name

Product Name

CML Common Mathematical Library

CMR Console Message Redisplay

COMAPI Communications Application Program Interface


C–4 7831 0349–046


Installation and

Support Name

Product Name

DDP-PPC Distributed Data Processing Program-to-Program

Communications

DPREP1100 DPREP1100

ED ED

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


SORT Sort/Merge Utility

SSG Symbolic Stream Generator

SYSLIB SYSLIB

UC C Compiler

Products on Package Tapes

7831 0349–046 C–5


Installation and

Support Name

Product Name

UCSRTS Runtime System for Basic Mode Compilers

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.

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

Installation and

Support Name

Product Name

DPS Display Processing System

MCB Message Control Bank

TIPUTIL Transaction Processing Utilities

C.3. Products on Package Tapes

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.

Table C–5. DVD Package Tape Contents

Tape Name Installation and

Support name

Product name DVD Package

Tape

Fast-Load Tape

CP01 COMUS COMUS CPHD-03 CP-FLD

FURPUR File Utility

Routines/Program

Utility Routines

CPHD-03 CP-FLD


C–6 7831 0349–046



Support name


Tape

Fast-Load Tape

PCFP Program-Callable

FURPUR

CPHD-03 CP-FLD

ROLRUNS Roll-out/Roll-back

Runstream

CPHD-03 CP-FLD

SOLAR Software Library

Administrator

CPHD-03 CP-FLD

CP02 CML Common

Mathematical

Library

CPHD-03 CP-OE1B

DAP Dump Analysis

Procedures

CPHD-03 CP-OE1A

ED OS 2200 Text Editor CPHD-03 CP-OE1B

ELT OS 2200 Element

Processor

CPHD-03 CP-OE1B

FAS File Administration

System

CPHD-03 CP-OE1B

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

CPHD-03 CP-OE1B

RSS Remote System

Support

CPHD-03 CP-OE1B

SLIB Service Library CPHD-03 CP-OE1B

SSG Symbolic Stream

Generator

CPHD-03 CP-OE1B

SYSLIB System Service

Routines Library

CPHD-03 CP-FLD

CP-OE1B

UCSRTS Runtime System for

Basic Mode

Compilers

CPHD-03 CP-OE1B

URTS Runtime System for

Extended Mode

Compilers

CPHD-03 CP-OE1B

CP03 ELMS Extended Language

Message System

CPHD-03 CP-OE1B

LINK Linking System CPHD-03 CP-OE1B


7831 0349–046 C–7



Support name


Tape

Fast-Load Tape

CP04

CIFS CIFS for ClearPath

OS 2200

CPHD-03

CMR Console Message

Redisplay

CPHD-03 CP-OE1B

DPREP1100 DPREP1100 CPHD-03 CP-OE1B

MSCP Monitor Services

Control Program

CPHD-03 CP-OE1B

PMD Postmortem Dump

processor

CPHD-03 CP-OE1B

CP05 APEX Apex CPHD-03

CKRS Checkpoint/Restart CPHD-03

DMPLIB DMPLIB CPHD-03 CP-OE1A

FLEX User Authentication CPHD-03

PADS Programmer’s

Advanced

Debugging System

CPHD-03 CP-OE1B

SEC-ADMIN Security

Administration for

ClearPath OS 2200

CPHD-03 CP-OE1A

TUTIL Tape Labeling Utility

for ClearPath

OS 2200

CPHD-03

URU-OS2200 Utilization Report

Utility for OS 2200

CPHD-03

CP06 LSS Language Support

System

CPHD-03 CP-OE1B

CP07 FLIT Fault Location by

Interpretive Testing

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

CPHD-04 CP-OE1B


C–8 7831 0349–046



Support name


Tape

Fast-Load Tape

CP09 ACOB ASCII COBOL

Compiler

CPHD-04

EXPIPE Multiple Batch Run

Optimizer

CPHD-04

FTN ASCII FORTRAN

Compiler

CPHD-04

MMGR Media Manager CPHD-04

PCIOS Processor Common

Input/Output

System

CPHD-04 CP-OE1B

SORT Sort/Merge Utility CPHD-04 CP-OE1B

CP10 DDP-FJT Distributed Data

Processing File and

Job Transfer

CPHD-04

DDP-PPC Distributed Data

Processing

Program-to-Program

Communications

CPHD-04 CP-OE1B

IPF Interactive

Processing Facility

CPHD-04 CP-OE1B

CP11 cpFTP FTP Services for

ClearPath OS 2200

CPHD-04

DFP Define File

Processor

CPHD-04

DPS Display Processing

System

CPHD-04 CP-OE2

GSA General Syntax

Analyzer

CPHD-04 CP-OE1B

HTPIC-2200 OS 2200 High

Performance

Transaction

Processing

Interconnect

CPHD-04

NTSI Messaging

Integration Services

CPHD-04 CP-OE1B

SOLAR/E Software Library

Administrator

Extended

CPHD-04


7831 0349–046 C–9



Support name


Tape

Fast-Load Tape

TAS Transmission

Control

Protocol/Internet

Protocol (TCP/IP)

Application Services

CPHD-04

CP12 EPORTAL-2200 ePortal CPHD-04

IC2200 Interconnect for

JProcessor and

QProcessor

CPHD-04

JPJVM Virtual Machine for

the Javaî Platform

on ClearPath OS

2200 JProcessor

CPHD-04

WMQ2200 WebSphere® MQ

Version 7 for

ClearPath OS 2200

CPHD-04

CP13 IRU Integrated Recovery

Utility

CPHD-05 CP-OE1B

UDSC Universal Database

Control

CPHD-05

CP14 DMS Enterprise Network

Database Server

CPHD-05

DMS-RA Network Database

Server Resource

Adapter for the Java

Platform

CPHD-05

DMSKEY Enterprise Network

Database Server

product key

CPHD-05

CP15 RDMS Enterprise Relational

Database Server for

ClearPath OS 2200

CPHD-05

RDMS-JDBC Relational JDBC

Driver for OS 2200

CPHD-05

RDMSKEY Enterprise Relational

Database Server for

ClearPath OS 2200

product key

CPHD-05 CP-OE1B

CP16

FDP/ADP File Definition

Processor/Applicatio

n Processor

CPHD-05


C–10 7831 0349–046



Support name


Tape

Fast-Load Tape

INFOAccess ODBC Data

Access - Corporate

Edition

CPHD-05

QLP Query Language

Processor

CPHD-05

SFS Shared File System CPHD-05

UNIACCESS UniAccess-ODBC CPHD-05

UREP Repository for

ClearPath OS 2200

CPHD-05

UREPKEY Repository for

ClearPath OS 2200

product key

CPHD-05

XRLOAD Relational Database

Fast Load

CPHD-05

CP17 CIPHER-API CPHD-05

OLTP-TM2200 Open Distributed

Transaction

Processing

CPHD-05 CP-OE1A

OSI-TP Open Systems

Interconnection

Transaction

Processing

CPHD-05

WEBTS Web Transaction

Server

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


7831 0349–046 C–11



Support name


Tape

Fast-Load Tape

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

CPHD-05

CP-OPE OPE Open Programming

Environment

CPHD-02

CP-SPF ARC Automatic Recovery

of Components

CPHD-01

MHFS Multi-Host File

Sharing

CPHD-01

SECOPT1 Security Level 1 CPHD-01



SIPIPM Software

Instrumentation

Package Internal

Performance

Monitor

CPHD-01

TAVR Tape Automatic

Volume Recognition

CPHD-01

UDUPLEX Unit Duplexing CPHD-01

VTH Virtual Tape Handler CPHD-01

XPCEXEC Extended

Processing Complex

– Locking (XPC-L)

software

CPHD-01

XTCEXEC Extended

Transaction Capacity

(XTC) software

CPHD-01


C–12 7831 0349–046



Support name


Tape

Fast-Load Tape

CP-TRN CITA Communications

Interface for

Transaction

Applications

CPHD-01

MCB Message Control

Bank

CPHD-01 CP-OE2

TIPUTIL Transaction

Processing Utilities

CPHD-01 CP-OE2

CP-COMM SUITE COMAPI Communications

Application Program

Interface

CPHD-02 CP-OE1B

CPComm

Note: CPComm

is used only

with Dorado 700

and 800 Server

systems.

Communications

Platform

CPHD-02 CP-FLD

CPCommOS

Note:

CPCommOS is

for use on

Dorado 4000,

4100, 4200,

4300, and 6300

systems.

Communications

Platform for Open

Systems

CPHD-02 CP-FLD

CryptoLib Cryptographic

Library

CPHD-02 CP-FLD

SILAS System Interface for

Legacy Application

Systems

CPHD-02 CP-FLD

7831 0349–046 D–1

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.

BDI System Generation Parameters

D–2 7831 0349–046

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.

BDI Groups

7831 0349–046 D–3

D.3. 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.

Customer BDIs

D–4 7831 0349–046

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.

BDI Allocation Listing

7831 0349–046 D–5

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.

Table D–1. BDI Allocation

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 SIMAN$CB 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

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

43 NUALG$I3 NUALG

44 NUALG$I4 NUALG

45 C$DIAG ACOB

46 C$SISAM ACOB

47 C$SIIOB ACOB

BDI Allocation

D–6 7831 0349–046


50 C$ANS ACOB

51 C$MASS ACOB

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

70 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

112 PLS$2 PLUS

113 PLS$3 PLUS

114 PLS$R PLUS

115 PLS$4 PLUS

116 PLS$E PLUS

117 HVTS$AC1 HVTS

120 MDC$ MACRO

121 MDP$ MACRO

122 RESERVED UNISYS

123 FTN$4YI FTN

124 FTN$4XI FTN

125 FTN$UTILITY FTN

126 CPBBNK$ UCAD

127 SCHBNK$ UCAD

130 MASM$I MASM

131 UDS$DMRICR DMS

132 DMR2$ DMS

133 DMR3$ DMS

134 DMR4$ DMS

135 DMR5$ DMS

136 DMR6$ DMS

137 BANK1S$$$ ACOB

140 BANK2S$$$ ACOB

141 BANK3S$$$ ACOB

142 BANK4S$$$ ACOB

143 BANK5AS$$$ ACOB

144 BANK5AL$$$ ACOB

145 BANK6S$$$ ACOB

146 RFOR$I RFOR

147 ROFR$I RFOR

150 SCANNER$ UBASIC

151 COMPEX$ UBASIC

BDI Allocation

7831 0349–046 D–7


152 UTILITY$ UBASIC

153 PL1$2A PL1

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

246 BDI11$ ETP

247 CONTB$ QLP

250 DIAG$ QLP

251 QPRBK$ QLP

252 QPABK$ QLP

253 BDI12$ ETP

254 PADS$K PADS

BDI Allocation

D–8 7831 0349–046


255 FTN$HELP FTN

256 LOG$BK RPS

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

335 DBP$IB2 DMS

336 DBP$IB3 DMS

337 DBP$IB4 DMS

340 DBP$IB5 DMS


341 DBP$DB11 DMS

342 DBP$DB12 DMS

343 DBP$DB13 DMS

344 DBP$DB14 DMS

345 DBP$DB15 DMS

346 DBP$DB21 DMS

347 DBP$DB22 DMS

350 DBP$DB23 DMS

351 DBP$DB24 DMS

352 DBP$DB25 DMS

353 DBP$DB31 DMS

354 DBP$DB32 DMS

355 DBP$DB33 DMS

356 DBP$DB34 DMS

357 DBP$DB35 DMS

360 DBP$DB41 DMS

361 DBP$DB42 DMS

362 DBP$DB43 DMS

363 DBP$DB44 DMS

364 DBP$DB45 DMS

365 DBP$DB51 DMS

366 DBP$DB52 DMS

367 DBP$DB53 DMS

370 DBP$DB54 DMS

371 DBP$DB55 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

BDI Allocation

7831 0349–046 D–9


413 UTS4CB$ CMS

414 C$DML8 ACOB

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

425 DRU$DB2 DMS

426 DRU$DB3 DMS

427 DRU$DB4 DMS

430 DRU$DB5 DMS

431 DRU$DB6 DMS

432 DRU$DB7 DMS

433 DRU$DB8 DMS

434 DRU$DB9 DMS

435 DRU$DB10 DMS

436 UNX-SSDEF$ MQSERIES-2200

437 RESERVED UNISYS

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

452 HVTS$FTNB2 HVTS

453 HVTS$FTNB4 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

BDI Allocation

D–10 7831 0349–046


526 IP$U016 IPF

527 IP$U017 IPF

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

545 IP$CD01 DDP-PPC

546 IP$CD02 DDP-PPC

547 IP$CD03 DDP-PPC

550 IP$CD04 DDP-PPC

551 IP$CD05 DDP-PPC

552 IP$CD06 DDP-PPC

553 IP$CD07 DDP-PPC

554 IP$CD08 DDP-PPC

555 IP$CD09 DDP-PPC

556 IP$QB00 IPF

557 FJT$CB DDP-FJT

560 IP$NETD DDP-PPC

561 IP$MASCOM IPF

562 IP$EXT IPF

563 RESERVED UNISYS

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

630 RPGII$02$ RPGII

631 RPGII$03$ RPGII

632 RPGII$04$ RPGII

633 RPGII$05$ RPGII

634 RPGII$06$ RPGII

635 RPGII$07$ RPGII

636 RPGII$08$ RPGII

637 RPGII$09$ RPGII

640 RPGII$10$ RPGII

BDI Allocation

7831 0349–046 D–11


641 RPGII$11$ RPGII

642 RPGII$12$ RPGII

643 RPGII$13$ RPGII

644 RPGII$14$ RPGII

645 RPGII$15$ RPGII

646 RPGII$16$ RPGII

647 RPGII$17$ RPGII

650 RPGII$18$ RPGII

651 PADS$MSG PADS

652 –

657 RESERVED UDSC

660 UDS$TCLCD001 UDSC

661 –

664 RESERVED UDSC

665 UDS$ADTCDB UDSC

666 –

677 RESERVED UDSC

700 –


712 –

722 RESERVED UDSC

723 UDS$DMRCKSUM DMS

724 UDS$DMRICR DMS

725 UDS$DMRLDM01 DMS





732 UDS$DMRLINKR DMS

733 RESERVED RDMS

734 RESERVED RDMS

735 UDS$RDMICR RDMS

736 –

745 RESERVED RDMS

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

BDI Allocation

D–12 7831 0349–046


1022 DDFBNK UREP

1023 DDFUTIL UREP

1024 DSRMAIN UREP

1025 DSRBLD UREP

1026 DSRUTL UREP

1027 DDSEMBNK UREP

1030 DDS$DDFUTIL2 UREP

1031 PCIBNK1 UREP

1032 PCIBNK2 UREP

1033 PCIBNK3 UREP

1034 PCIBNK4 UREP

1035 PCIBNK5 UREP

1036 PCIBNK6 UREP

1037 PCIBNK7 UREP

1040 PCIBNK8 UREP

1041 UDS$EM$RICR RDMS

1042 RSA$CFGSBDI RDMS

1043 DDSICRBNK UREP

1044 DBNK UREP

1045 EPIPBNK UREP

1046 PCIBNK9 UREP

1047 URTS$$CH1 URTS

1050 URTS$$DB1 URTS

1051 URTS$$DM1 URTS

1052 URTS$$DM2 URTS

1053 URTS$$OC1 URTS

1054 URTS$$PM1 URTS

1055 URTS$$RC1 URTS

1056 URTS$$RC2 URTS

1057 URTS$$SG1 URTS

1060 URTS$$SM1 URTS

1061 URTS$$SM2 URTS

1062 URTS$$SM3 URTS


1063 URTS$$SM4 URTS

1064 URTS$$SM5 URTS

1065 URTS$$SP1 URTS

1066 URTS$$UD1 URTS

1067 URTS$$UD2 URTS

1070 DPS$CFBK DPS

1071 RESERVED RDMS

1072 RESERVED RDMS

1073 RESERVED RDMS

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

1152 BL$OPT3 LSS

BDI Allocation

7831 0349–046 D–13


1153 BL$LOP2 LSS

1154 BL$LOP3 LSS

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

1243 LINK$$I3 LINK

1244 LINK$$D LINK

1245 LINK$$E LINK

1246 LINK$$OMOR LINK

1247 LINK$$OMOR2 LINK

1250 SLINK$I1 LINK

1251 SLINK$I2 LINK

1252 SLINK$I3 LINK

1253 SLINK$I4 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

BDI Allocation

D–14 7831 0349–046


1266 BL$EMCODE LSS

1267 RESERVED LSS

1270 CIFSHI CIFS

1271 BL$DCM LSS

1272 BL$TEX LSS

1273 BL$OPT1 LSS

1274 BL$SKS LSS

1275 BL$REG LSS

1276 BL$SKI1 LSS

1277 BL$SRCALOC LSS

1300 –


1312 BL$SDDCROS LSS

1313 BL$SKI2 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

1335 BL$SKI4 LSS

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 –


BDI Allocation

7831 0349–046 D–15


1412 IP$$IK12 IPF

1413 IP$$IK13 IPF

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

1456 RESERVED UNISYS

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

1472 DPS$BK2 DPS

1473 DPS$BK3 DPS

1474 DPS$BK4 DPS

1475 DPS$BK5 DPS

1476 DPS$BK6 DPS

1477 STATI$ TPAS

1500 –


1512 LINK$$I2 LINK

1513 RESERVED RDMS

1514 RESERVED RDMS


1516 RESERVED RDMS

1517 RESERVED RDMS

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

BDI Allocation

D–16 7831 0349–046


1525 EPS$I$DATA SUFICS

1526 EPS$I$DISP SUFICS

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 –


1612 IP$$IK11 TAS

1613 IP$$IN04 TAS

1614 IP$$IN05 TAS

1615 SLINK$I3 LINK

1616 IP$IK15 COBEDT

1617 IP$IK16 COBEDT

1620 IP$IK18 COBEDT

1621 IP$IK19 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

BDI Allocation

7831 0349–046 D–17


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






BDI Allocation

D–18 7831 0349–046






1770 CTLBNK USAS

1771 ALT$ACB1 USAS

1772 ALT$ACB2 USAS

1773 ALT$ACB3 USAS

1774 ALT$ACB4 USAS

1775 ALT$ACB5 USAS

1776 ALT$ACB6 USAS

1777 ALT$ACB7 USAS

2001 –


2012 ALT$ACB8 USAS

2013 ALT$ACB9 USAS

2014 ALT$ACB10 USAS

2015 ARCBY$ ARC

2016 ARCBY$DB ARC

2017 SLINK$I1 LINK

2020 SLINK$I2 LINK

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

BDI Allocation

7831 0349–046 D–19


2117 IFC$D OFISLINK

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

2151 URTS$$CH1 URTS

2152 URTS$$DB1 URTS

2153 URTS$$DM1 URTS

2154 URTS$$DM2 URTS

2155 URTS$$OC1 URTS

2156 URTS$$PM1 URTS

2157 URTS$$RC1 URTS


2160 URTS$$RC2 URTS

2161 URTS$$SG1 URTS

2162 URTS$$SM1 URTS

2163 URTS$$SM2 URTS

2164 URTS$$SM3 URTS

2165 URTS$$SM4 URTS

2166 URTS$$SM5 URTS

2167 URTS$$SP1 URTS

2170 URTS$$UD1 URTS

2171 URTS$$CM1 URTS

2172 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

2223 PLS$B3$ PLUS

2224 PLS$BR$ PLUS

2225 PLS$B4$ PLUS

2226 PLS$4B$ PLUS

2227 PLS$B4OMBAS$ PLUS

2230 PLS$4BOMBAS$ PLUS

2231 PLS$B4OMEXT$ PLUS

BDI Allocation

D–20 7831 0349–046


2232 PLS$4BOMEXT$ PLUS

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









2252 UCB$10 UNIDAS 1100

2253 GRRMI$ MAPPER

2254 GRRUI$ MAPPER

2255 PADS$EX PADS

2256 PADS$P PADS

2257 LINK$$I3 LINK

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

BDI Allocation

7831 0349–046 D–21























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 –


2412 DPS$BK8 DPS

2413 DPS$BK9 DPS

2414 DPS$BK10 DPS

2415 DPS$BK11 DPS

2416 DPS$BK12 DPS


2417 LLMS$ ELMS

2420 OSI$SERVICES DDP-PPC



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



2437 RESERVED UDSC

2440 UDS$ADTGATE UDSC

2441 RESERVED UDSC


2443 C2SFSE$ SFS

2444 C2SFSM$ SFS

2445 C2SFSD$ SFS

2446 C2LDM2$ SFS

2447 –

2451 RESERVED UDSC


2453 UDS$TCLCDICR UDSC

2454 –

2477 RESERVED UDSC

2500 –


2512 –


2527 UDS$DMRLINKR DMS

BDI Allocation

D–22 7831 0349–046







2535 UDS$DMRICR DMS

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

2546 PCIBNK9 UREP

2547 DDSEMBNK UREP

2550 DDS$DDFUTIL2 UREP

2551-


2554 PCIBNK1 UREP

2555 PCIBNK2 UREP

2556 PCIBNK3 UREP

2557 PCIBNK4 UREP

2560 PCIBNK5 UREP

2561 PCIBNK6 UREP

2562 PCIBNK7 UREP

2563 PCIBNK8 UREP

2564 DDSICRBNK UREP

2565 DBNK UREP

2566 EPIPBNK UREP

2567 PCIBNK9 UREP

2570 RESERVED RDMS

2571 RESERVED RDMS

2572 UDS$RDMICR RDMS


2573 –

2577 RESERVED RDMS

2600 –


2612 RESERVED RDMS

2613 RESERVED RDMS

2614 RESERVED RDMS

2615 RESERVED RDMS


2617 RESERVED RDMS

2620 RESERVED RDMS


2622 RESERVED RDMS

2623 RESERVED RDMS

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

BDI Allocation

7831 0349–046 D–23


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

2713 PCFP$2 PCFP

2714 PCFP$3 PCFP

2715 PCFP$4 PCFP

2716 PCFP$5 PCFP

2717 PCFP$6 PCFP

2720 –

2725 RESERVED RDMS





2731 SLINK$I4 LINK

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 –

2770 RESERVED RDMS

2771 OSMI$04 OSM MAIL





2776 IPM$DPSCFG OSI-MHS


BDI Allocation

D–24 7831 0349–046


3000

– 3011 RESERVED CUSTOMER

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


3025 DPS$BK7 DPS

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

3053 DDS3R1$B2 UREP

3054 DDS3R1$B3 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

3071 RESERVED RMCOB

3072 RM$CBL120 RMCOB






3100 –


3112 RESERVED RMCOB

3113 SYSLIB$1 SYSLIB




3117 TRN$ACB USAS

3120 ASR$ACB USAS

3121 LDP$ACB USAS

3122 MSG$ACB USAS

3123 TKT$ACB USAS

BDI Allocation

7831 0349–046 D–25


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

3136 SCHDP2$ MAPPER

3137 SCHDP3$ MAPPER

3140 SCHDP4$ MAPPER

3141 SCHDP5$ MAPPER

3142 SCHDP6$ MAPPER

3143 SCHDP7$ MAPPER

3144 BL$REG2 LSS

3145 BL$COBRDGRP1 UCOB

3146 UDS$DMRSHELL DMS

3147 HCADS$$1 HCADS

3150 HCADS$$2 HCADS

3151 HCADS$$3 HCADS

3152 HCADS$$4 HCADS

3153 HCADS$$5 HCADS

3154 REGBANK$ PEER

3155 B$$CFEMAIN UC

3156 B$$CFELS1 UC

3157 B$$CFELS2 UC

3160 B$$CFEDCL1 UC

3161 B$$CFEDCL2 UC

3162 B$$CFEDCL3 UC

3163 B$$CFESTMT1 UC

3164 B$$CFESTMT2 UC


3165 B$$CFESTMT3 UC

3166 B$$CFEDBG UC

3167 B$$CFEMSG UC

3170 BL$LOP1 LSS

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 –


4506 CS$A CS2200

4507 CS$B CS2200

4510 CS$C CS2200

4511 CS$D CS2200

4512-


4514 EMSLIB$1 SLIB

4515 DPS$TERMINDX DPS

4516 DPS$FORMINDX DPS

4517 LLMS$IB ELMS

4520

CMS$UCIFS-

AA/AB/AC/AD CPComm

4521 CMS$BMIF-A CPComm

4522 CMS$EMIF-A CPComm

BDI Allocation

D–26 7831 0349–046


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

4551 CMS$BMIF-T CPComm

4552 CMS$EMIF-T CPComm

4553 OSTP$EXTRACT ODS-HOST

4554 OSTP$EXTEST ODS-HOST

4555 URTS$$CH1 URTS

4556 URTS$$DB1 URTS

4557 URTS$$DM1 URTS

4560 URTS$$DM2 URTS

4561 URTS$$OC1 URTS

4562 URTS$$PM1 URTS


4563 URTS$$RC1 URTS

4564 URTS$$RC2 URTS

4565 URTS$$SG1 URTS

4566 URTS$$BM2 URTS

4567 URTS$$SM2 URTS

4570 URTS$$SM3 URTS

4571 URTS$$SM4 URTS

4572 URTS$$SM5 URTS

4573 URTS$$SP1 URTS

4574 URTS$$UD1 URTS

4575 URTS$$CM1 URTS

4576 URTS$$BM1 URTS

4577 LINC7$ LINCII

4600 –


4610 LINC8$ LINCII

4611 LINC9$ LINCII

4612 LINC10$ LINCII

4613 LINC11$ LINCII

4614 LINC12$ LINCII

4615 LINC13$ LINCII

4616 LINC14$ LINCII

4617 LINC15$ LINCII

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

4640 LINC$MON1 LINCII

BDI Allocation

7831 0349–046 D–27




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

4655 IC2200 IC2200

4656 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










4750 SYSLNC USAS

4751 SM$EMSUB SORT

4752 SX1100EXTMD$ LSS

4753 CBEP$TM/O HUBWARE DTP

4754 TPE2NPE$BDI RASSLOG


4756 TQ$BASELINE

BASELINE &

ONLINE

4757 TQ$STATI$EM TPAS

4760 ORA-CLIENT ORACLE Client

4761 ORA-CLIENT2 ORACLE Client

BDI Allocation

D–28 7831 0349–046


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

5001 PID$BNK2 MCB

5002 PID$BNK3 MCB

5003 PID$BNK4 MCB

5004 PID$BNK5 MCB

5005 PID$BNK6 MCB

5006 PID$BNK7 MCB

5007 PID$BNK8 MCB

5010 PID$BNK9 MCB

5011 PID$BNK10 MCB

5012 PID$BNK11 MCB

5013 PID$BNK12 MCB

5014 PID$BNK13 MCB

5015 PID$BNK14 MCB

5016 PID$BNK15 MCB

5017 PID$BNK16 MCB

5020 PID$BNK17 MCB

5021 PID$BNK18 MCB

5022 PID$BNK19 MCB


5023 PID$BNK20 MCB

5024 PID$BNK21 MCB

5025 PID$BNK22 MCB

5026 PID$BNK23 MCB

5027 PID$BNK24 MCB

5030 PID$BNK25 MCB

5031 PID$BNK26 MCB

5032 PID$BNK27 MCB

5033 PID$BNK28 MCB

5034 PID$BNK29 MCB

5035 PID$BNK30 MCB

5036 PID$BNK31 MCB

5037 PID$BNK32 MCB

5040 PID$BNK33 MCB

5041 COR$BNK1 MCB

5042 COR$BNK2 MCB

5043 COR$BNK3 MCB

5044 COR$BNK4 MCB

5045 COR$BNK5 MCB

5046 COR$BNK6 MCB

5047 COR$BNK7 MCB

5050 COR$BNK8 MCB

5051 SIT$BNK1 MCB

5052 SIT$BNK2 MCB

5053 SIT$BNK3 MCB

5054 SIT$BNK4 MCB

5055 SIT$BNK5 MCB

5056 SIT$BNK6 MCB

5057 SIT$BNK7 MCB

5060 SIT$BNK8 MCB

5061 SIT$BNK9 MCB



BDI Allocation

7831 0349–046 D–29




5066 TQ$BLCONTROL

BASELINE &

ONLINE

5067 TQ$BLPROBLEM

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

5234 I18NLIB$RTT$A$ I18NLIB

5235 EBRSCB EBRS

BDI Allocation

D–30 7831 0349–046


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

5254 MSBDB MSCP

5255 MSBDB MSCP

5256 MSBDB MSCP

5257 MSBDB MSCP

5260 MSBDB MSCP

5261 MSBDB MSCP

5262 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 –


7831 0349–046 E–1

Appendix E Acronyms and Abbreviations

This appendix defines the acronyms and abbreviations used in this overview and

related Unisys documentation.

A

ACI Audit Control Interface (file)

ACOB ASCII COBOL Compiler

ACR access control record

ACS Automatic Cartridge System

ACSLS Automatic Client Server Library Software

ADP Application Definition Processor

ADT application definition table

AFCB alternate file common bank

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

B

BDI bank descriptor index

BIF Built-in function

BIS Business Information Server

BMC block multiplexer channel

Acronyms and Abbreviations

E–2 7831 0349–046

C

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

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


7831 0349–046 E–3

D

DAD Device Area Descriptor

DAP Dump Analysis Procedures

DCA Distributed Communications Architecture

DCP Distributed Communications Processor

DDA Data Dependent Attribute

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

DRS disk resident system

DRU Data Reorganization Utility

DSPER Diagnostic Software Peripheral Equipment Routines

DSS Display System Services

DSTA Daylight Saving Time Adapt

DTI Distributed Transaction Integration

DTP Distributed Transaction Processing

E

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)

ER Executive request

ESQL embedded SQL


E–4 7831 0349–046

ESS Electronic Support Services

EUR encryption user routine

Exec OS 2200 Executive

EXPIPE Multiple Batch Run Optimizer

EXPOOL Exec buffer pool

F

FAS File Administration System

FBCIS Fixed Block Compatible Interface Software

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

G

GRS general register set

GSA General Syntax Analyzer

H

HLC Host LAN Controller

HMP Heterogeneous multiprocessing

HVTIP High-Volume Transaction Processing


7831 0349–046 E–5

I

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

J

J2EE Java 2 Platform, Enterprise Edition

J2SE Java 2 Platform, Standard Edition

JBOSS-2200 JBoss Enterprise Application Platform for ClearPath OS 2200

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

L

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


E–6 7831 0349–046

LPF large program file

LSS Language Support System

LTO Linear Tape Open

M

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

MSAR TeamQuest® Mass Storage Analysis and Relocation processor

MSB Monitor Services Bank

MSCP Monitor Services Control Program

MSMANAGER TeamQuest® Mass Storage Manager

N

NIC network interface card

NIOP network I/O processor

NTLM Windows NT LAN Manager

NTSI Messaging Integration Services

O

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


7831 0349–046 E–7

P

PADS Programmers Advanced Debugging System

PAEXEC Partitioned Applications Exec

PAR TeamQuest® Performance Analysis Routines

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

Q

QBR Queue Bank Repository

QLP Query Language Processor

R

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

S

SAUTILITIES TeamQuest® Site Administrator Utilities

SAS Sentinel Alert Service

SBCON Single-byte command code set connection

SBF system boot file


E–8 7831 0349–046

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

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

SLAR System Log Analyzer and Reports

SLI schema length information


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


7831 0349–046 E–9

SSL/TLS Secure Sockets Layer/Transport Layer Security

SUP standard unit of processing

SYSLIB System Service Routines Library

T

TAS TCP/IP Application Services

TAVR Tape Automatic Volume Recognition

TCDBF TIP Common Data Bank File

TCP/IP transmission control protocol/Internet protocol

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

TSU transport service user

TUTIL Tape Labeling Utility

U

UC C Compiler

UCF User Communication Form

UCOB COBOL Compiler

UCPP C++ Compiler

UCS Universal Compiling System

UCSRTS Runtime System for Basic Mode Compilers

UDI user-defined information

UDLS universal data link control

UDS Universal Data System

UDSC Universal Data System Control

UFTN FORTRAN Compiler


E–10 7831 0349–046

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

V

VALTAB validation table

W

WAD Word addressable file

WEBTS Unisys Web Transaction Server for ClearPath OS 2200

WMQ2200 WebSphere® MQ Version 7 for ClearPath OS 2200

X

XIOP eXtended I/O Processor for connection to the XPC-L

XML Extensible Markup Language

XPC Extended Processing Complex

XPC-L Extended Processing Complex-Locking

XRF XPC resident file

XRLOAD Relational Database Fast Load

XTC Extended Transaction Capacity

XTCEXEC Exec Component of XTC Software

XTP Extended Transaction Processing

XTPA Extended Transaction Processing Architecture

Z

ZOOM zero overhead object module

7831 0349–046 Index–1

Index

A

ACOB

package tape location, C-8 release level, 1-7

acronyms and abbreviations, E-1 Apex

considerations, 5-4 APEX

package tape location, C-7 release level, 1-7 workstation requirements, 6-1

ARC

current level, 1-13 package tape location, C-11

ASCII COBOL Compiler (ACOB)

release level, 1-7 ASCII FORTRAN Compiler (FTN) release

level, 1-8 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-4

C

C Compiler (UC)

release level, 1-11 CARTLIB removal, 3-2 checklist, migration planning, 7-2 CIFS

considerations, 3-4, 5-4 package tape location, C-7 release level, 1-7

CIPHER API

release level, 1-7 CITA

considerations, 5-6 package tape location, C-12 release level, 1-7

CKRS


ClearPath Enterprise Servers

IOE content

Business Information Server (BIS), A-3, A-9

Enterprise Application Environment

(EAE), A-3, A-9 general-purpose workload, A-3, A-9 Software Development Kit (SDK), A-3,

A-9

ClearPath OS 2200 Release 16.0 considerations, 3-1

CML

fast-load tape location, C-3 package tape location, C-6 release level, 1-7

CMR

considerations, 5-7 fast-load tape location, C-3 package tape location, C-7 release level, 1-7

COBOL Compiler (UCOB)


Collector (MAP) release level, 1-9 COMAPI


Communications Application Program

Interface (COMAPI) release level, 1-7 Communications Interface for Transaction

Applications (CITA) release level, 1-7 Communications Platform

release level, 1-7

Index

Index–2 7831 0349–046

Communications Platform for Open

Systems

release level, 1-7 compliance

Image Enabler Key, 3-21 software product key, 3-21

COMUS

considerations, 5-12 fast-load tape location, C-2 release level, 1-7 security privileges, 5-38

considerations

Apex, 5-4 Business Information Server

(MAPPER), 5-4 CIFS, 5-4 Cipher API, 5-5 CITA, 5-6 CKRS, 5-7 ClearPath OS 2200 Release 16.0, 3-1 CMR, 5-7 COMUS, 5-12 CPComm, 5-9, 5-10, 5-11 cpFTP, 5-13 CryptoLib, 5-14 DDP-FJT, 5-16 DDP-PPC, 5-16 DMS-RA, 5-14 DPS, 5-15 ELMS, 5-17 EOM, 5-17 FLEX, 5-20 FORTRAN Compiler (UFTN), 5-13 INFOAccess, 5-29 INTERCONNECT, 5-24 IPF, 5-24 IRU, 5-21 J2EE-CON-2200, 5-26 LINK, 5-27 LSS, 5-26 MAP, 5-28 MCB, 5-28 MSMQI, 5-28 NTSI, 5-29 OLTP-TM2200, 5-30 OSI-TP, 5-33 RDMS, 5-33 RDMS-JDBC, 5-33 RSS, 5-34 Security-Admin, 5-36 SOLAR, 5-37 SP-OPERATION, 5-38 SSG, 5-40

SYSLIB, 5-41 TAS, 5-44 TeamQuest Products, 5-44 TUTIL, 5-43 UCOB, 5-47 UDSC, 5-47 UniAccess-ODBC, 5-47 UREP, 5-48 URTS, 5-35 URU-OS2200, 5-51 WEBTS, 5-53 WMQ2200, 5-53

CPComm

considerations, 5-9, 5-11 fast-load tape installation, 7-17, 7-22, 7-23 fast-load tape location, C-2 package tape location, C-12 package-tape installation, 7-38 release level, 1-7

CPCommOS

fast-load tape installation, 7-17, 7-23 fast-load tape location, C-2 package tape location, C-12 release level, 1-7

CP-FLD

fast-load tape, 7-11 tape contents, C-2

cpFTP (FTP Services)


CP-OE1A and CP-OE1B


CP-OE2


Cryptographic Library

release level, 1-8 CryptoLib

considerations, 5-14 fast-load tape location, C-2 release level, 1-8

CTS5136 tape subsystem

considerations, 4-27 CTS5236 tape subsystem

considerations, 4-28 microcode, 3-42

CTS9840 tape subsystem

considerations, 4-35 microcode, 3-42

CTS9840C tape subsystem

considerations, 4-37

Index

7831 0349–046 Index–3

CTS9940B tape subsystem

considerations, 4-44 CULL

release level, 1-8

D

DAP


DDP-FJT


DDP-PPC

considerations, 5-16, 7-3 fast-load tape location, C-4 package tape location, C-8 release level, 1-8

Define File Processor (DFP)

release level, 1-8 DEPCON (Enterprise Output Manager)

workstation requirements, 6-1 DFP (Define File Processor)


diagnostic file

noncompliance message, SOLAR, 3-16 discontinued products, 3-9 Distributed Transaction Integration (DTI)

release level, 1-8 DLT 7000 and DLT 8000 tape

considerations, 4-29 DMPLIB


DMPLIB fast-load tape location, C-3 DMS (Enterprise Network Database Server)

DMSKEY package tape location, C-9 package tape location, C-9 release level, 1-8

DMS-RA

considerations, 5-14 release level, 1-8

DPREP1100


DPS

fast-load tape location, C-5


DSTA

Considerations, 3-7 DTI (Distributed Transaction Integration)

release level, 1-8 DVD software media, 1-6, 4-47, C-1

E

ECLIPSE-2200

release level, 1-8 ED

fast-load tape location, C-4 ELMS


ELT


Enterprise Network Database Server (DMS)


Enterprise Output Manager (DEPCON)

release level, 1-8 Enterprise Output Manager (EOM)

fast-load tape location, C-4 release level, 1-8 workstation requirements, 6-1

Enterprise Relational Database Server

(RDMS)

release level, 1-10 EOM

considerations, 5-17 EPORTAL-2200


Exec

considerations, 3-4, 3-5 log entry changes, 4-19 release level, 1-8 separately packaged features

DMPLIB, 1-13 SIPIPM, 1-13 TAVR, 1-13 TIPUTIL, 1-13 UDUPLEX, 1-13 VTH, 1-13

Index

Index–4 7831 0349–046

XPCEXEC, 1-13 XTCEXEC, 1-13

SGS and configuration parameters

considerations, 4-17 tape and DVD considerations, 4-21

EXPIPE


F

Fall Back

Considerations, 7-7 FAS


fast-load tapes

CP-FLD, C-2 CP-OE1A and CP-OE1B, C-3 CP-OE2, C-5 descriptions, 7-11

FDP/ADP package tape location, C-9 FLEX


FLIT


FORTRAN Compiler (UFTN)


FTN


FTP Services (cpFTP) release level, 1-8 FURPUR

fast-load tape location, C-2 release level, 1-8

G

GSA


H

HTPIC 2200


I

I18NLIB


IC2200

package tape location, C-9 Image Enabler Key

compliance, 3-21 description, 4-51 MIPS-based, Dorado 150, 240, and

340, 4-51 MIPS-metered, 4-51 new format, 3-18 old format, 3-18 removal warning, 3-23 software performance, 3-14

INFOAccess

considerations, 5-29 package tape location, C-10

INFOAccess (ODBC Data Access)

release level, 1-9 initializing Cipher API, 5-5 installation sequences

considerations, 7-3 initializing an existing system, 7-36

installation verification procedures

(IVP), 5-37 INTERCONNECT


IOCQ, 4-15 IOE content

ClearPath Enterprise Servers

Business Information Server (BIS), A-3, A-9

Enterprise Application Environment

(EAE), A-3, A-9 general-purpose workload, A-3, A-9 Software Development Kit (SDK), A-3,

A-9

IPF (Interactive Processing Facility)

considerations, 5-24 fast-load tape location, C-4

Index

7831 0349–046 Index–5


IRU


J

J2EE-CON-2200

considerations, 5-26 JBOSS-2200

interdependency, B-11 release level, 1-9

JPJVM


K

key

Image Enabler key

new format, 3-18 old format, 3-18

tape delivery

introduction, 3-27

L

levels for Separately Packaged Exec

Features (SPEF), 1-13 LINK (Linking System)


LIST


local code, auditing when migrating, 7-2 LSS (Language Support System)


M

MAP


MAPPER considerations, 5-4 MASM


master SCN, 3-14 MCB


MCN (manufacturing control number), 3-14 Media Manager

package tape location, C-8 media, software

DVD, 1-6, 4-47, C-1 tape, 4-25, 4-35, 4-37, 4-44, 7-10, A-1

Messaging Integration Services (NTSI)

release level, 1-10 MHFS


migration

planning checklist, 7-2 MIPS-based Image Enabler Key, Dorado 150,

240, and 340, 4-51 MMGR current level, 1-13 MSAR

release level, 1-9 MSCP

current level, 1-13 fast-load tape location, C-4 package tape location, C-7

MSMANAGER

release level, 1-9 MSMQI


Multiple Batch Run Optimizer (EXPIPE)

release level, 1-8

N

new format Image Enabler Key, 3-18

Index

Index–6 7831 0349–046

NTSI

considerations, 5-29 NTSI (Messaging Integration Services)


O

ODBC Data Access (INFOAccess)

release level, 1-9 old format Image Enabler Key, 3-18 OLTP-TM2200



release level, 1-10 Operations Sentinel (SP-OPERATION), 1-10,

5-38

OSAM

release level, 1-10 OSI-TP


OST4890 tape subsystem

considerations, 4-28

P

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


PAR

release level, 1-10 PCFP


PCIOS


PDP


PLUS


PMD


PRODSV utility, 3-27 product key

DMS (Enterprise Network Database

Server), C-9 RDMS (Enterprise Relational Database

Server), C-9 TeamQuest, 3-30 UREP, C-10

profile, SCN, 3-17

Q

QLP


R

RDMS

considerations, 5-33 RDMS (Enterprise Relational Database

Server)

package tape location, C-9 RDMSKEY

fast-load tape location, C-4 package tape location, C-9

release level, 1-10 RDMS-JDBC

release level, 1-10 Relational JDBC Driver


release level

ACOB, 1-7 APEX, 1-7 CIFS, 1-7 CIPHER-API, 1-7 CITA, 1-7

Index

7831 0349–046 Index–7

CKRS, 1-7 CML, 1-7 CMR, 1-7 COMAPI, 1-7 COMUS, 1-7 CPComm, 1-7 CPCommOS, 1-7 cpFTP, 1-8 CryptoLib, 1-8 CULL, 1-8 DAP, 1-8 DDP-FJT, 1-8 DDP-PPC, 1-8 DEPCON-2200, 1-8 DFP, 1-8 DMS, 1-8 DMS-RA, 1-8 DPREP1100, 1-8 DPS, 1-8 DTI, 1-8 ECLIPSE-2200, 1-8 ELMS, 1-8 ELT, 1-8 Enterprise Output Manager (DEPCON), 1-8 EPORTAL-2200, 1-8 EXEC, 1-8 EXPIPE, 1-8 FAS, 1-8 FLEX, 1-8 FLIT, 1-8 FTN, 1-8 FURPUR, 1-8 GSA, 1-8 HTPIC-2200, 1-9 I18NLIB, 1-9 INFOACCESS, 1-9 INTERCONNECT, 1-9 IPF, 1-9 IRU, 1-9 J2EE-CON-OPENDTP, 1-9 J2EE-CON-OS2200, 1-9 JBOSS-2200, 1-9 JPJVM, 1-9 LA, 1-9 LINK, 1-9 LIST, 1-9 LSS, 1-9 MAP, 1-9 MASM, 1-9 MCB, 1-9 MSAR, 1-9 MSMANAGER, 1-9 MSMQI, 1-9

NTSI, 1-10 OLTP-TM2200, 1-10 OPE, 1-10 OSAM, 1-10 OSI-TP, 1-10 PADS, 1-10 PAR, 1-10 PCFP, 1-10 PCIOS, 1-10 PDP, 1-10 PLUS, 1-10 PMD, 1-10 QLP, 1-10 RDMS, 1-10 RDMS-JDBC, 1-10 ROLRUNS, 1-10 RSS, 1-10 SAUTILITIES, 1-10 Security-Admin, 1-10 SFS, 1-10 SILAS, 1-10 SIMAN, 1-11 SLIB, 1-11 SOLAR, 1-11 SOLAR/E, 1-11 SORT, 1-11 SSG, 1-11 SYSLIB, 1-11 TAS, 1-11 TIP-LA, 1-11 TQ-BASELINE, 1-11 TQD-FRAGGER, 1-11 TQ-MODEL, 1-11 TQ-ONLINE, 1-11 TQ-PMLOG, 1-11 TQ-PROBES, 1-11 TQRDFRAGGER, 1-11 TUTIL, 1-11 UC, 1-11 UCOB, 1-11 UCSRTS, 1-11 UDSC, 1-11 UFTN, 1-11 UNIACCESS-ODBC, 1-11 UPLS, 1-11 UREP, 1-11 URTS, 1-12 URU-OS2200, 1-12 WEBTS, 1-12 WMQ2200, 1-12 XRLOAD, 1-12

removal warning, Image Enable Key, 3-23 Repository for ClearPath OS 2200 (UREP)

Index

Index–8 7831 0349–046

release level, 1-11 ROLRUNS


RSS


Runtime System for Basic Mode Compilers

(UCSRTS) release level, 1-11 Runtime System for Extended Mode

Compilers (URTS)


S

SAUtilities release level, 1-10 SCN

master, 3-14 profile, 3-17 software control number, 3-14 workload, 3-19

SCP

considerations, 4-50 SECOPT1

package tape location, C-11 SECOPT2

package tape location, C-11 security management product

Security Administration for ClearPath

OS 2200, 1-14 Security-Admin


Separately Packaged Exec Features (SPEF)

ARC, 1-13 SECOPT1, 1-13 SECOPT2, 1-13 SECOPT3, 1-13 SIPIPM, 1-13 TAVR, 1-13 TIPUTIL, 1-13 UDUPLEX, 1-13 VTH, 1-13 XPCEXEC, 1-13 XTCEXEC, 1-13

SFS


Shared File System (SFS) release level, 1-10 SILAS


SIMAN

release level, 1-11 SIPIPM

package tape location, C-11 SLIB


software

control number (SCN), 3-14 media

DVD, 1-6, 4-47, C-1 tape, 4-25, 4-29, 4-35, 4-37, 4-44, 7-10,

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-14 product key

compliance, 3-21 master SCN, 3-14

update, 3-19 upgrade, 3-19

Software Controlled Performance (SCP)

considerations, 4-50, 7-10 SOLAR

considerations, 5-37 fast-load tape location, C-3 package tape location, C-6 PRODSV utility, 3-27 release level, 1-11 security privileges, 5-38 using as an installation tool, 5-37

SOLAR/E


SORT


Index

7831 0349–046 Index–9

release level, 1-11 SP-OPERATION (Operations Sentinel), 5-38 SSG


support policy, 1-14 SYSLIB


T

tape considerations

36-track tape subsystems

CTS5136, 4-27 CTS5236, 4-28 general considerations, 4-26 OST4890, 4-28

CTS5236 microcode, 3-42 CTS9840, 4-35 CTS9840 microcode, 3-42 CTS9840C, 4-37 CTS9940B, 4-44 DLT 7000 and DLT 8000, 4-29

tapes

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

package tape location, C-11 TeamQuest

Baseline

release level, 1-11 CULL


D-Fragger


IACULL

package tape location, C-10 LA


Model

release level, 1-11 MSAR


MSManager

release level, 1-9 MSMANAGER

package tape location, C-10 Online

release level, 1-11 OSAM


PAR


PMLog

release level, 1-11 Probes

release level, 1-11 products considerations, 7-10 RemD-Fragger


SAUtilities


SIMAN


TIP Log Analyzer

release level, 1-11 TIP-LA

package tape location, C-10 TQ-BASELINE

package tape location, C-11 TQ-ONLINE

package tape location, C-11 TQ-PMLOG

package tape location, C-11 TQ-PROBES

package tape location, C-11 View considerations, 6-2

TeamQuest Products

considerations, 5-44 TeamQuest SIMAN

fast-load tape location, C-3 TIPUTIL


Index

Index–10 7831 0349–046

TQ-ONLINE

release level, 1-11 TQ-PMLOG

release level, 1-11 TQ-PROBES

release level, 1-11 TQ-TIP-LA release level, 1-11 TQ-VIEW considerations, 6-2 TUTIL


U

UC


UCOB


UCSRTS


UDS application group 3, installing, C-5 UDSC


UDUPLEX

package tape location, C-11 UFTN (FORTRAN Compiler)


UniAccess-ODBC


update, software, 3-19 upgrade, software, 3-19 UPLS


UREP

considerations, 5-48 package tape location, C-10 release level, 1-11 UREPKEY package tape location, C-10

URTS


URU-OS2200


V

VTH

package tape location, C-11

W

WEBTS

considerations, 5-53, 6-2 package tape location, C-10 release level, 1-12

WMQ2200

considerations, 5-53 package tape location, C-9

workload, SCN, 3-19 wrong system, product key tape, 3-19

X

XRLOAD


XTCEXEC

package tape location, C-11

.

© 2015 Unisys Corporation.

All rights reserved.

*78310349-046* 7831 0349–046