CA Console Management for OpenVMS r3.1 Readme

3.0 System Requirements
3.1 TCP/IP Stack Requirements
3.2 Console Manager
3.3 CA Common Services Integration

4.0 Installation Considerations
4.1 Natively Mount CD on OpenVMS
4.2 Access ISO Disk Image with OpenVMS Logical Disk Facility
4.2.1 Launch the Installation
4.2.2 Activate Integration
4.3 Upgrade Considerations
4.4 Windows Considerations

5.0 General Considerations
5.1 Version Number
5.2 Motif Interface
5.3 Affect of Uninstallation of CA Common Services on Tomcat and JRE
5.4 IPv6
5.5 Test the SSH configuration from DCL
5.6 Secure Communication Best Practice
5.7 Obsolete Commands Removed
5.8 Reconfiguring SSH Connections
5.9 Console System State

6.0 Known Issues

7.0 Published Fixes

8.0 Documentation
8.1 HTML Bookshelf
8.2 Release Numbers on Documentation

9.0 Contact Technical Support

1.0 Welcome

Welcome to CA Console Management for OpenVMS r3.1. This file contains product installation considerations, general considerations, known issues, published fixes, and information about contacting CA Technical Support.

2.0 Operating System Support

CA Console Management for OpenVMS r3.1 supports the following operating systems:

HP OpenVMS Industry Standard 64 v8.2-1, v8.3 and v8.3-1H1

HP OpenVMS Alpha v7.3-2, v8.2 and v8.3

This release does not support the following operating systems:

OpenVMS Alpha v6.2, v7.1, v7.2, v7.3, v7.3-1

OpenVMS VAX

We recommend that you install any HP OpenVMS ECOs with an installation rating of 1.

3.0 System Requirements

The following requirements must be met or exceeded for CA Console Management for OpenVMS r3.1 to install and run correctly:

TCP/IP Stack Requirements

Console Manager

CA Common Services (CCS) Integration

3.1 TCP/IP Stack Requirements

The following list contains the OpenVMS versions and the corresponding TCP/IP stack versions:

HP TCP/IP Services for OpenVMS Industry Standard 64 V5.5 and V5.6

HP TCP/IP Services for OpenVMS Alpha V5.4, V5.5 and V5.6
For systems running HP TCP/IP Services, at a minimum the following HP ECO level is recommended:
- HP TCP/IP Services I64 V5.6, ECO 2
- HP TCP/IP Services I64 V5.5, ECO 3
- HP TCP/IP Services Alpha V5.6, ECO 2
- HP TCP/IP Services Alpha V5.5, ECO 2
- HP TCP/IP Services Alpha V5.4, ECO 7

Process Software TCPware 5.7-2 ,5.8, and 5.9
For systems running TCPware 5.7-2 or 5.8, the following Process Software ECO is required:
- DRIVERS_V582P050 or later
- SSH_V582P020 or later
For systems running TCPware 5.9, the following Process Software ECO is required:
- DRIVERS_V592P010 or later

Process Software MultiNet v5.1, v5.2, and v5.3
For systems running MultiNet v5.1, the following Process Software ECOs are required:
- UCX_LIBRARY_EMULATION-110_A052 or later
- UCXDRIVER-061_A051 or later
- KERNEL-UPDATE-260_A051 or later
- SSH-090_A051 or later
For systems running MultiNet v5.2, the following Process Software ECOs are required:
- UCX_LIBRARY_EMULATION-011_A053 or later
- UCXDRIVER-050_A052 or later
- SSH-050_A052 or later
For systems running MultiNet v5.3, the following Process Software ECOs are required:
- KERNEL-UPDATE-030_A053 or later
- UCX_LIBRARY_EMULATION-011_A053 or later

3.2 Console Manager

The OpenVMS requirements are as follows:

Alpha:

To install Console Manager, a minimum of 365,000 blocks of free disk space is required.

To run Console Manager, a minimum of 110,000 blocks of free disk space is required.

I64:

To install Console Manager, a minimum of 485,000 blocks of free disk space is required.

To run Console Manager, a minimum of 130,000 blocks of free disk space is required.

Disk space refers to space required for the product base files and does not take into account the requirements for log and archive data collected by CA Console Management.

3.3 CA Common Services Integration

To run CA Common Services (CCS )Integration on Windows, the version requirements are as follows:

CA Network and System Management (NSM), or CA CCS r11.1 or r11.2. See the Readme files for these products for other prerequisites.

Note: This release does not support NSM or CCS 3.x or r11.

4.0 Installation Considerations

Installation and upgrade procedures for this release of CA Console Management for OpenVMS r3.1 are in the CA Console Management for OpenVMS Installation guide.

Before installing CA Console Management for OpenVMS r3.1 (or any of its components) or migrating from a previous product release, be sure to review the following sections carefully to determine if there are additional installation or configuration steps, or both, that you need to follow for this release.

4.1 Natively Mount CD on OpenVMS

Natively mount the CD-ROM (Alpha) or DVD-ROM (I64) on OpenVMS. Use the following command to mount the CD or DVD after replacing the device with your own drive information:

Mount/over=id device:

Note: Device is the CD-ROM or DVD-ROM drive.

4.2 Access ISO Disk Image with OpenVMS Logical Disk Facility

OpenVMS provides a mechanism to mount an ISO image of a CA OpenVMS product CD/DVD directly. These steps are valid for OpenVMS Alpha 7.3-2 and newer, and OpenVMS I64 8.2-1 and newer.

Notes:

OpenVMS Alpha users should start at step 1; OpenVMS I64 users should start at step 4.

Steps 1 and 2 only need to be performed once on systems running OpenVMS Alpha 7.3-2, but are unnecessary for systems running OpenVMS Alpha 8.2 and newer.

To access the ISO disk Image

Edit the file SYS$STARTUP:CDRECORD.COM using any suitable text editor.
Search for the text "load_ldcld:". The line immediately following the occurrence of this text should be "$ set command sys$input". Starting with the line immediately after the line that reads "$ set command sys$input", cut all lines of text up to but not including the line that reads "$ RETURN 1" into a file named LD.CLD; this will be approximately 245 lines of text.

The first few and last few lines of the selected text should look as follows:
```
  !+++ 
  ! 
  ! Facility: 
  ! 
  ! Command Definition File for the LD Utility. 
  ! 
  ! Abstract: 
  ! 
  ! This file defines the following commands; 
  . 
  . 
  . 
  DEFINE SYNTAX PARAM_ALL 
  PARAMETER P1,LABEL=COMMAND,PROMPT="Command",
  VALUE(REQUIRED,TYPE=LD_OPTIONS) 
  PARAMETER P2,LABEL=DEVICE,VALUE(TYPE=$DEVICE)
!<end-of-file> 
```

Edit the file SYS$STARTUP:LD$STARTUP.COM and search for a line of text that reads:

$ if f$file_attributes("sys$system:ld$utility.exe","known")

Insert the following lines of DCL immediately before that line:

$ if f$file_attributes("sys$message:ld$msg.exe","known")
$ then
$   install replace sys$message:ld$msg.exe
$ else
$   install create sys$message:ld$msg.exe
$ endif

Close the file and terminate your editing session.

Add the LD command to your command tables. For OpenVMS Alpha 7.3-2, you will use the LD.CLD file that you created in step 1 as follows:
```
$ SET COMMAND LD
```
For OpenVMS Alpha 8.2 and newer, execute the following:
```
$ SET COMMAND SYS$UPDATE:LD.CLD
```
The above commands should be executed whenever you login.

Start the logical disk facility by executing the new version of LD$STARTUP.COM created in STEP 3. This only needs to be executed once after each system boot:
```
$ @SYS$STARTUP:LD$STARTUP.COM
```

Download the .ISO image of the products that you wish to install and record the location where you have placed them on your OpenVMS system. These files must be transferred using a transfer type of "binary".

Connect the .ISO image to a logical disk device using the command:
```
$ LD CONNECT disk:[dir-path]filename.ISO
```
The system responds with the device name of the logical disk device that the .ISO file was connected to. You will need this device name for the following step.

Mount the logical disk device using the command:

$ MOUNT/MEDIA=CD/OVER=ID logical-disk-device-from-step-6

Follow the installation guide for the product that you are installing by substituting the name of the logical disk device for the name of the CDROM or DVD device where indicated in the product installation guide.

Repeat steps 6 and 7 for each ISO image for the products that you want to install.

When you have completed the installations, dismount and disconnect each logical disk using the following commands.
```
$ DISMOUNT LD-device-name
$ LD DISCONNECT LD-device-name
```
You can do this after you complete each installation and before repeating steps 6 and 7 for other ISO product disk images, or after you have completed all installations. If you do this after all installations, repeat these commands once for each ISO product disk image that was connected and mounted.

Sample log file

This log shows the connection, mounting, and start of the installation for the CA Console Management r3.1 for OpenVMS Alpha on a system running OpenVMS Alpha 8.3.

Steps 1 through 5 have already been performed.

$ LD CONNECT $1$DKA100:[000000]CACM_31_VMSAXP.ISO
%LD-I-UNIT, Allocated device is $1$LDA6:
$ MOUNT/OVER=ID/MEDIA=CD/NOASSIST $1$LDA6:
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-CDROM_ISO, CACM_31_VMSAXP: (1 of 1) , mounted on  _$1$LDA6: (USXXXX)

$ RUN $1$LDA6:[000000]SETUP_ALPHA.EXE
UnZipSFX 5.20 of 30 April 1996, by Info-ZIP (Zip-Bugs@wkuvx1.wku.edu).
  inflating: ca$setup.com
  inflating: installhelp.hlp
  inflating: cacm$readme.txt
  inflating: cacm_product.key
  inflating: unzip_alpha.exe
  inflating: unzip_ia64.exe
Setup location: $1$LDA6:[000000]

	CA Console Management for OpenVMS

	Copyright (c) 2004,2010 CA.  All rights reserved.

	---------------------------------

		PRODUCT

	1      Console Manager Install

	I      CA NSM/CCS Integration Help
	P      Product Readme
	H      Install Help
	E      Exit


	Please Enter the Number of the Product you wish to
	install >>>>

4.2.1 Launch the Installation

Using the SYSTEM account, run the installation procedure on the OpenVMS system by typing the following command:

For Alpha:
```
$ run device:[000000]setup_alpha.exe
```

For Integrity:
```
$ run device:[000000]setup_ia64.exe
```

These commands launch an installation menu where you can install the components

4.2.2 Activate Integration

If you answer No to the following question and you want to activate CCS Integration at a later date, you need to import the file CONSOLE$TEMPLATES:CONSOLE$CONFIG_LINK.PORT. Refer to the Installation Guide for detailed instructions.

Do you want to activate the CA Common Services Integration Components [YES]?

And you want to activate CCS Integration at a later date, you need to import the file CONSOLE$TEMPLATES:CONSOLE$CONFIG_LINK.PORT. Refer to the Installation Guide for detailed instructions.

4.3 Upgrade Considerations

Before you upgrade Console Manager on Alpha, you must have installed PTF RO07037, or its successor.

If you are using a private Console setup file, you should follow the following steps before upgrading Console Manager:

Shut down Console Manager

Delete the Console Manager logical name table:

$ DEASSIGN /TABLE=LNM$SYSTEM_DIRECTORY /EXEC  CONSOLE$LOGICAL_NAMES

Rebuild the Console Manager logical name table:
```
$@sys$startup:console$startup logicals
```

4.4 Windows Considerations

The CA NSM Integration component name was changed from "Unicenter for OpenVMS" to "CA Common Services Integration for OpenVMS" (CCS Integration for OpenVMS)

If you are using CA NSM on Windows, you need to be aware of the following situations:

When installing CA OpenVMS Integration for CA NSM on a Windows system running NSM or CCS, you might need to reboot the Windows system after the CCS Integration installation is complete. The installation detects the conditions that require a reboot.

Users installing CCS for OpenVMS r3.2 on OpenVMS will have to install CCS for OpenVMS r3.2 on Windows, the version included in this release. Older versions of CCS for OpenVMS on Windows will not be able to communicate with CCS for OpenVMS r3.2 on OpenVMS.

5.0 General Considerations

This section contains general information you should know before using CA Console Management for OpenVMS r3.1:

Version Number

Motif Interface

Integration

IPv6

Test the SSH configuration from DCL

Secure Communication Best Practice

Obsolete Commands Removed

Reconfiguring SSH Connections

Console System State

5.1 Version Number

CA has changed its product version scheme:

The official version of this release for CA Console Management for OpenVMS is r3.1, which is the same as V3.1-1002.

The version number for CA Common Services for OpenVMS Integration is independent of the product version. The CA Common Services for OpenVMS Integration version used in this release is r3.2.

5.2 Motif Interface

This software was developed on DECwindows Motif and has not been tested with all available X Windows emulators.

5.3 Affect of Uninstallation of CA Common Services on Tomcat and JRE

If you install Tomcat and JRE as part of a CA Common Services installation, you should be aware that uninstalling CA Common Services will also uninstall Tomcat and JRE. This is specifically important if you use CA Common Discovery, because after you uninstall CA Common Services, CA Common Discovery will not work. You must uninstall CA Common Discovery and then reinstall it.

Note: For CA NSM to manage an OpenVMS system, CA Messaging (CAM) must be running on both systems

5.4 IPv6

On MultiNet, IPv6 is supported only on MultiNet 5.2 or later with ECO's listed under System Requirements.

For detailed information on IPv6 for CCS Integration, refer to the Appendix "IPv6" in the CA Common Services for OpenVMS Integration Guide.

5.5 Test the SSH configuration from DCL

Before attempting to connect to a console with Console Manager using SSH, first validate the SSH configuration from DCL.

Be sure the TCP/IP stack commands are initialized. Execute one of the following commands:
TCPIP Services
```
@sys$manager:tcpip$define_commands
```
TCPware
```
$ @TCPware:TCPWARE_COMMANDS
```
MulitNet
```
$ SET COMMAND MULTINET:USER.CLD
```
Note: For best results, run this command in system-wide login procedure SYLOGIN.COM.

Validate the SSH connection to your terminal/console server
```
$ ssh <username>@<terminal/console-server>#<port number>
```

5.6 Secure Communication Best Practice

When it is necessary to change security settings outside of the Console Manager database–the contents of an identity file used by Console Manager for SSH connections, for example–you need to shut down and then restart Console Manager in order to use the new settings for all affected connections.

5.7 Obsolete Commands Removed

As previously announced, this release removes the obsolete commands CONSOLE COORDINATE and CONSOLE RECORD. Use the commands CONSOLE C3 and CONSOLE WATCH, respectively.

5.8 Reconfiguring SSH Connections

The Reconfigure command is a complex database reconfiguration. Some actions are run in the background–these might continue after the Console Manager Reconfigure command returns to the prompt. This pertains mainly to SSH connections, which are highly asynchronous. For SSH connections, allow at least three minutes for the connections to change from unopened state (HYU) to begin opening (HYO state), as shown by the CONSOLE STATUS/ALL command. When the connection succeeds (HYE) or fails (HYF), the connection is complete.

5.9 Console System State

The list of all systems indicates system state, using three columns:

Column 1, Transport
D = Direct

H = SSH

L = LAT

P = Pseudo-terminal

T = TELNET

Column 2, Enabled state
N = Not enabled

Y = Enabled

Column 3: Current state
E = OK

F = Open failed

L = Link lost

O = Opening

U = Unopened

? = Unknown

For Example:

PYE

P (pseudo-terminal) Y (is enabled) E (state is OK).

6.0 Known Issues

The following items are known issues with CA Console Management for OpenVMS r3.1:

If you are running Windows Server 2008 with NSM/CCS r11.2, and you right-click on a VMS object in the MCC or 2D Map, the Telnet command might not work. This occurs because Windows Server 2008 security settings do not allow a program to access \Windows\System32\telnet.exe. To avoid this issue, copy telnet.exe to another folder in the %path%, or change the Windows Server security settings.

During installation, if you choose No to activating integration, you might still be prompted for a NSM/CCS management station. This might occur when the Product Startup Selection menu has at least one product set to start using the command procedure capoly$startup.com. In this case, accept the default management station to continue with the installation. If no other product is using CA Common Services for OpenVMS Integration on this system, you can enter any name to continue with the installation.

If you use the Up arrow key to recall a command in the Monitor Interface, do not use the Left arrow key to edit the command. Doing so might cause the terminal screen to not format properly. To avoid this problem use the Backspace/Delete key.

The installation procedure incorrectly directs you to insert the product management command file SYS$STARTUP:CONSOLE$MANAGER$SHUTDOWN.COM into the system shutdown procedure SYS$MANAGER:SYSHUTDWN.COM. The Installation Guide contains the same incorrect instruction.
To shut down Console Manager in a controlled way at system shutdown, the correct commands to use in SYSHUTDWN.COM are:
```
$ @SYS$STARTUP:CAPOLY$SHUTDOWN.COM
```
or
```
$ CONSOLE SHUTDOWN /NOCONFIRM
```

Adobe Acrobat Reader might show invalid mailto: links embedded in code examples when you view the PDF files.
For example:
$ @sys$startup:console$manager$startup.com might show as a link when you mouse over it. If this occurs you can disable Mailto: links in Acrobat Reader. You only need to do this once on each computer used to view the PDF files.
To disable mailto: links in Acrobat Reader
1. Open any PDF in Acrobat Reader.
2. Click Tools, Preferences, General.
3. Deselect the "Create links from URLs" checkbox and then click OK.
  Note: For Acrobat Reader 7, the checkbox is called "Automatically detect URLs from text".

With the release of CA Console Management for OpenVMS r3.1, the packaging for OpenVMS Alpha has changed. The package contains three discs: one disc for CA Console Management for OpenVMS VAX 3.0, and two discs for CA Console Management for OpenVMS Alpha r3.1. Be aware that, while the VAX 3.0 disc also contains the Alpha 3.0 release, you should only install on Alpha using the Alpha r3.1 disc. However, there is one exception: you need to use the VAX 3.0 disc to install on OpenVMS Alpha V6.2.

7.0 Published Fixes

The complete list of published bug fixes for this product can be found at CA Support Online: https://supportconnect.ca.com.

The following fixes and behavioral changes are included in this release. Where applicable, the published PTF number is specified before the description of the fix:

RO07038	When a Console Management station is running in fail-over mode and the connections between a fail-over line controller daemon and terminal servers are lost, the fail-over controller daemon does not attempt to regain the connections. Includes the fixes in R006701.
RO07037	When running under OpenVMS Alpha V8.3 and up, the temporary .COM and .LOG files used by action routine processes may not be deleted after the action routine processes terminate. When a Console Management station is running in fail-over mode and the connections between a fail-over line controller daemon and terminal servers are lost, the fail-over controller daemon does not attempt to regain the connections Includes the fixes in RO00840.
RO06701	When running under OpenVMS I64 V8.3 and up, the temporary .COM and .LOG files used by action routine processes may not be deleted after the action routine processes terminate. Includes the fixes in RO00841.
RO01254	Unicenter Console Management for OpenVMS r3.0 will not install on OpenVMS Alpha 8.x. PTF QO83752 will not install the Unicenter NSM Integration software when Process Software MultiNet is used to supply TCP/IP networking services. Includes the fixes in QO88302.
RO00841	Periodically, a Console Manager user interface command may hang. This includes the CONNECT, MONITOR, SHUTDOWN, and ARCHIVE commands. When using the /BEFORE= , /SINCE=, or both qualifiers with the CONSOLE EXTRACT command, the time-range of the extracted data does not match the time range specified with the qualifiers. The CONSOLE ARCHIVE command may fail when processing the EVENTS file for a managed system. The CONSOLE ARCHIVE command may fail to process all data that was requested to be archived when the /BEFORE= qualifier is used. If the fail-over feature is being used and a CONSOLE RECONFIGURE command is executed, the Console Daemon process may crash with an access violation (ACCVIO) error. When an OpenVMS Mail utility signature file has been setup, the CONSOLE$MAIL action routine may fail. Under certain conditions, a Console Manager line controller daemon process enters a compute loop.
RO00840	Under certain conditions, a Console Manager line controller daemon process enters a compute loop. Includes the fixes in RO00172 and QO83954.
RO00172	The Console Archive command may fail on OpenVMS Alpha 8.3 after completing the first pass of the events file.
RO00171	This kit provides detailed instructions for setting up Console Manager for OpenVMS to work with the LAN-based console of HP Integrity servers along with two command procedures to assist with implementation.
RO00170	This kit provides detailed instructions for setting up Console Manager for OpenVMS to work with the LAN-based console of HP Integrity servers along with two command procedures to assist with implementation.
RI00026	Unicenter Console Management for OpenVMS I64 r3.0 has been certified on OpenVMS I64 V8.3-1H1 and HP BladeSystem Integrity c-Class Blades.
QO99138	WVUniVMS process fails in PPEecifde.dll. Includes the fixes in QO89693.
QO89693	WVUniVMS fail in PPEecifde.dll.
QI89041	The Product Explorer window fails to start on the Japanese version of Windows.
QO88302	Unicenter Console Management for OpenVMS V3.0 will not install on OpenVMS Alpha 8.x. PTF QO83752 will not install the Unicenter NSM Integration software when Process Software MultiNet is used to supply TCP/IP networking services. Includes the fixes in QO83752.
QO86037	The install cannot find TCPWARE:UCX$IPC_SHR when the TCPWARE logical is defined as a search list; the installation fails. VMS-LINK ERROR DURING INSTALLATION.
QO84864	Unicenter for OpenVMS and Enterprise Edition products that are running with a version of CA Licensing older than V1.57 may start displaying out-of-compliance messages after January 3rd, 2007.
QO84695	CA Common Services for OpenVMS (CCSVMS) also knwn as Unicenter for OpenVMS Integration, supplied prior to the release of Unicenter NSM r11, is not fully compatible with version r11. Includes the fixes in QO67674 and QO81583.
QO83954	The OpenVMS Help facility text for the CONSOLE verb contained several incorrect references to the Unicenter TNG Console Manager Users' Guide. The Monitor interface may crash with an ACCVIO if the user has split the terminal screen into multiple sections and either a SHOW SYSTEM or OUTPUT command is entered at the Monitor Interface command prompt. Sometime after a CONSOLE RECONFIGURE command is executed on a fail-over Console Manager host, the Console Daemon process may crash with an access violation (ACCVIO). Includes the fixes in QO61326.
QO83759	Unicenter Console Manager r3 for OpenVMS I64 cannot be installed on OpenVMS 8.3 and up.
QO83752	Unicenter Console Management for OpenVMS V3.0 will not install on OpenVMS Alpha 8.x. Includes the fixes in QO67673.
QO81583	When adding a node for Performance Monitoring (running CubeCfg.exe), the corresponding folder is created in either lowercase or uppercase.
QI77019	A PTF installation may fail with %LINK-W-NOSUCHMOD, module OPENVMS_SHIELD not found in library SYS$COMMON:[SYSLIB]CALIC.OLB.
QO67674	When the CA-Unicenter_OpenVMS_Gateway service requests a heartbeat from a managed OpenVMS node and error 257 is received from that node, the heartbeat fails.
QO67673	Unicenter Console Management for OpenVMS V3.0 will not install on OpenVMS Alpha 8.2.
QO64616	This fix provides new event scan profiles and new system icons.
QO61326	Either the CONSOLE$EVENTLIST or the CONSOLE$EVENTSINGLE action routines may terminate with a DECThreads bugcheck. Periodically, CONSOLE ARCHIVE may terminate when archiving any particular systems log file set with the following message being displayed at the user's terminal: "Archive for system XXXXX has failed." The character-cell configuration editor SHOW GROUP command will output two lines of text to the user's terminal even if the user specified a file-name for which to write the output. When the failover feature is utilized so that one Console Manager host acts as the primary for all managed systems, and another Console Manager host acts as the failover for all managed systems,. In this situation, only the SYSTEM account is able to access the managed systems from any of the user interfaces such as CONNECT/MONITOR, EXTRACT, DIALOG, and so on, when the failover Console Manager host assumes control of the managed systems. If the CONSOLE RECONFIGURE command is executed on a failover Console Manager host when it is in control of any number of managed systems, and there are user disabled systems present in the database, the "User Disabled:" system count as shown by the CONSOLE STATUS command will be set to 0 and the user disabled systems will be counted in the "Active Systems" count. The startup procedure CONSOLE$MANAGER$STARTUP.COM will define several logical names in both the LNM$SYSTEM_TABLE and CONSOLE$LOGICAL_NAMES logical name tables. In some cases the logical names will have different equivalence strings. Includes the fixes in QO50421.
QO50421	System group names longer than 16 characters may prevent the Find function in the C3 interface from locating a system within a group. Includes the fixes in QO32826 and QO38981.
QO38981	If the Console Manager has been shutdown and a user executes a CONSOLE ARCHIVE command, the CONSOLE ARCHIVE command will terminate with an access violation (ACCVIO).
QO30062	After upgrading from an earlier version of Unicenter TNG Console Manager for OpenVMS or CommandIT, the configuration database may contain verification errors that will prevent the product from starting.
QO22714	Console Manager will not load and configure all systems that are enabled in the database if the number of enabled systems exceeds 200. If failover is not being used, no more than 200 systems will be loaded. If failover is enabled, the number will be less and dependent on the configuration. The user may note messages similar to the following appearing on the terminal from which any Console Manager user interface is started: IPC_READ normal con close (endoffile) status: 2160 Connection between line sensor and remote console has been lost IPCWrite: $QIOW WRITEVBLK error 316 IPCClose: $QIOW WRITEOF 316 DECVCS> DECVCS> exit 316 %SYSTEM-F-IVCHAN, invalid I/O channel If system group records are configured in the Console Manager configuration database, and users are granted access to the groups and not the systems within the groups, the users will be denied access to the systems within the groups. Periodically, the command $CONSOLE EXTRACT /EVENT /SINCE=time node-name will ignore the time specified on the /SINCE qualifier and list all events listed in the active log file set for the specified managed system. The DIALOG interface SEND command sends a Carriage Return/New line pair after each string that is sent to a managed system. If the managed system is an OpenVMS system, the trailing new line character can cause undesirable results if the user is using DIALOG to run a command file on the managed systems console. The MONITOR interface FIND TEXT command always issues an error message: "CM Monitor: Cannot allocate monitor->target_timestr" The Monitor interface REVIEW command does not load archived console logs from the archive area. The VERIFY command may report failures when running Test 3. The failures will persist even after re-executing the VERIFY command with the /REPAIR qualifier.

8.0 Documentation

Updated guides for this product are available at: https://support.ca.com

The PDF and HTML guides for this product are as follows:

CA Console Management for OpenVMS Installation Guide

CA Console Management for OpenVMS Administration Guide

CA Console Management for OpenVMS Release Notes

CA Common Services for OpenVMS Integration Guide

8.1 HTML Bookshelf

This release contains the CA HTML Bookshelf, which is an HTML help system that provides access to all deliverables in the product documentation set–regardless of the file format. The HTML Bookshelf features include:

A single help screen that displays all documentation for this release.

An all-in-one search tool that searches the entire documentation set, regardless of file format.

Additional links for using the Bookshelf, downloading Acrobat Reader, and contacting CA.

After installing the product you can find the Bookshelf here:
<WorldView-install-path>\UNIVMS\DOC

For example, on NSM/CCS r11.1:

C:\Program Files\CA\SharedComponents\CCS\WVEM\UNIVMS\DOC

Or on NSM/CCS r11.2:

C:\Program Files\CA\SC\CCS\WVEM\UNIVMS\DOC

Alternatively, on r11.2, the Bookshelf path can be specified like this:

%CA_TND_HOME%UNIVMS\DOC

Note: You can also download and extract the All files with searchable index.ZIP file from CA Support Online. To extract the content of a .ZIP file, use an archive program such as WinZip or StuffIt, and choose to extract the content to a local folder. Once extracted, open the Bookshelf folder and click the Bookshelf.hta file.

8.2 Release Numbers on Documentation

The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, does support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r2.4 can still be valid for r2.4 SP3 or even r3.1. Documentation bookshelves always reflect the current product release number.

Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.

9.0 Contact Technical Support

Contact Technical Support

For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.com/support, you can access the following:

Online and telephone contact information for technical assistance and customer services

Information about user communities and forums

Product and documentation downloads

CA Support policies and guidelines

Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about CA product documentation, you can send a message to techpubs@ca.com.

If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs.