Downloadable - Hewlett-Packard

hp OpenView TeMIP
TeMIP Framework Maintenance Patch Kit
TFR V5.0 Patch 4 for Tru64
Release Notes
for the UNIX Operating Systems
April 2004
© Copyright 2004 Hewlett-Packard Company

Legal Notices
Warranty
Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited
to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be held liable for errors contained herein or direct, indirect, special, incidental or
consequential damages in connection with the furnishing, performance, or use of this material.
A copy of the specific warranty terms applicable to your Hewlett-Packard product can be obtained
from your local Sales and Service Office.
Restricted Rights Legend
Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause in DFARS
252.227-7013.
Hewlett-Packard Company
United States of America
Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-
19(c)(1,2).
Copyright Notices
©Copyright 2000-2004 Hewlett-Packard Company, all rights reserved.
No part of this document may be copied, reproduced, or translated to another language without the
prior written consent of Hewlett-Packard Company. The information contained in this material is
subject to change without notice.
Trademark Notices
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java is a U.S. trademark of Sun Microsystems, Inc.
Microsoft® is a U.S. registered trademark of Microsoft Corporation.
Netscape is a U.S. trademark of Netscape Communications Corporation.
NMOS is a trademark of RiverSoft Technologies Limited.
Oracle® is a registered U.S. trademark of Oracle Corporation, Redwood City, California.
Oracle9 and Oracle9 Server are trademarks of Oracle Corporation, Redwood City, California.
PostScript® is a trademark of Adobe Systems Incorporated.
Riversoft is a trademark of RiverSoft Technologies Limited.
UNIX® is a registered trademark of The Open Group.
Windows® and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
X/Open® is a registered trademark, and the X device is a trademark of X/Open Company Ltd. in the
UK and other countries.
All other product names are the property of their respective trademark or service mark holders and are
hereby acknowledged.
2

Contents
Preface .........................................................................................................................5
Introduction.....................................................................................................7
TeMIP Framework V5.0 Patch 4 for Tru64 Compatibility .............................9
2.1 Unix Compatibility ..............................................................................................9
2.2 TeMIP Framework Compatibility........................................................................9
2.3 Third-Party Products Compatibility ..................................................................10
Installing the Maintenance Patch ................................................................11
3.1 Installation on a non-TruCluster Configuration ................................................11
3.1.1 Installation of a New Director......................................................................11
3.1.2 Installation on Top of a Director Already Configured..................................12
3.2 Installation on a TruCluster Configuration .......................................................13
3.2.1 Installation of a new TeMIP director ...........................................................13
3.2.2 Installation of the Maintenance Patch on top of an already configured
director and no other Maintenance Patch is already installed....................13
3.2.3 Install Maintenance Patch on top of a director already configured and TFR
V5.0 Level 1 Patch 3 is already installed....................................................16
3.3 Installing the TFRV50001-04 Subsets .............................................................17
3.3.1 Prerequisite Subset Installation ..................................................................18
3.3.2 Installation of the Maintenance Patch using TeMIP SystemMate ..............19
3.3.3 Installation of the Maintenance Patch Using seltd...................................20
3.4 Configuration....................................................................................................21
3.5 Manual Operations...........................................................................................22
Fixed Problems in TFRV50001-04................................................................25
Known Problems...........................................................................................28
5.1 Previous Known Problems still applicable on TFR V500 Patch 4 for Tru64....28
5.2 New Known Problems Reported in the TFR V500 Patch 4 for Tru64 .............31
Important Notes ............................................................................................33
6.1 Upgrade to Orbix E2A ASP 6.1 .......................................................................33
6.1.1 Orbix E2A ASP 6.1 and 5.1.2 Configuration...............................................33
6.1.2 Changing IIOP ports of the Orbix processes ..............................................35
6.1.3 Orbix environment variables needed to run Orbix E2A ASP 6.1 tools .......36
6.2 Firewall Support ...............................................................................................37
6.3 Sign-on TeMIP Authentication Support ...........................................................40
6.4 PR#21200 Increase the number of members of a type definition ...................41
6.5 Operations concerning Enhancements/Known problems existing before the
current Maintenance Release V500 Level 1 Patch 4 ......................................41
6.5.1 Upgrade from Tru64 V5.1A to Tru64 V5.1B causes problem at TeMIP
SystemMate server start (JAVA version)....................................................41
3

4
6.5.2 Interoperability Tru64 V5.0 versus HP V5.0. ..............................................42
6.5.3 Cascading Corrective filter and callback facility .........................................42
6.5.4 TeMIP dictionary comparison enhancement ..............................................50
6.5.5 Add Environment variable for Assign Target in NOTIF_FM (PR#15382)...51
6.5.6 Mask the Current Problem List during show all attributes (PR#16687)......52
6.5.7 Synonym replica databases not updated (de-synchronized) (PR#16452).52

Preface
These Release Notes describe critical information related to the TeMIP Framework
V5 Patch 4 for Tru64 Maintenance Patch Kit.
Please read this document before installing or using the TeMIP Software.
Software Versions
The term UNIX is used as a generic reference to the operating system, unless
otherwise specified.
The software versions referred to in this document are as follows:
TeMIP UNIX TeMIP Framework
5.0
Tru64 5.1A and
5.1B
TFR V500 Level 1 Patch 4 Revision E
Typographical Conventions
Courier Font:
• Source code and examples of file contents.
• Commands that you enter on the screen.
• Pathnames
• Keyboard key names
Italic Text:
• Filenames, programs and parameters.
• The names of other documents referenced in this manual.
Bold Text:
• To introduce new terms and to emphasize important words.
Support
Please visit our HP OpenView web site at: HP OpenView
There you will find contact information as well as details about OpenView products,
services and support.
The OpenView support area of the OpenView web site includes:
• Downloadable documentation
• Troubleshooting information
• Patches and updates
• Problem reporting
5

• Training information
• Support program information
6

Chapter 1
Introduction
The current Release Notes describe critical information related to the TeMIP
Framework V5 Patch 4 for Tru64 maintenance patch kit. The software kit is
referenced as TFRV50001-04 which stands for TFR V500 Level 1 Patch 4 Revision
E. This Maintenance Patch Kit has to be installed on top of the TeMIP Framework
V5 Manufacturing Release software kit, referenced as TFR V500 Level 1 Revision G.
In addition to problem fixes, the TeMIP Framework V5 Patch 4 for Tru64 brings
following features:
• Support of Tru64 5.1A (Kit 6 BL 24) and Tru64 5.1B (Kit 3 BL 24) (see section
2.1)
• Support of Oracle 9.2.0.4 (see section 2.3)
• Support of firewall between the TAL Orbix Server FM and the TeMIP Client
(see section 6.2)
• Delivery of Orbix E2A ASP V6.1. The TAL Orbix Server FM now uses this
version. (see section 6.1)
• Optimization of Oracle session when using synonyms
These Release Notes contain the following sections:
1.
2.
3.
4.
5.
6.
Introduction: this section
TeMIP Framework V5 Patch 4 for Tru64 compatibility
Installation procedure
List of fixed problems in TeMIP Framework V5 Patch 4 for Tru64
List of known problems in TeMIP Framework V5 Patch 4 for Tru64
Important notes
Please contact TeMIP Support (e-mail to VBETEMIPSUPP@hp.com) for any
problems encountered when installing or running this Maintenance Patch.
7

Chapter 2
TeMIP Framework V5.0 Patch 4 for
Tru64 Compatibility
2.1 Unix Compatibility
The TeMIP Framework V5.0 Patch 4 for Tru64 Maintenance Patch has been qualified
on:
• Tru64 UNIX V5.1A (Kit 6 BL 24)
• Tru64 UNIX V5.1B (Kit 3 BL 24)
2.2 TeMIP Framework Compatibility
The TeMIP Framework V5.0 Patch 4 for Tru64 must be installed over TFR V500
Level 1 Revision G MR software kit.
Any previous TeMIP Framework V5 Maintenance Kit MUST be removed before
installing the TeMIP Framework V5.0 Patch 4 for Tru64.
All TFR V500 Level 1 Revision G MR Extraordinary Patches MUST be
uninstalled before installing the TeMIP Framework V5.0 Patch 4 for Tru64,
otherwise installation will fail.
The TeMIP Extraordinary Patch subsets to be removed are named:
• ‘TFRPATCHXXXXV500’ for TFR V500 Level 1 Revision G MR
or ‘TFRTRU64XXXX’ (new name for TFR patches on Tru64).
The STM patch STMPATCH20449V500 is mandatory. It provides
improvements on the activation of a release tree, so it must be installed on all
your release trees before installation of the TeMIP Framework V5 Patch 4 for
Tru64.
The STM patch STMPATCH18128V500 is also mandatory on the release tree
where the Maintenance Patch will be installed.
The TeMIP Framework Orbix E2A ASP 6.1 Runtime additional subset is
mandatory on the release tree where the Maintenance Patch will be installed.
These STM and Orbix pre-requisite subsets are part of the tar file delivering the
TeMIP Framework V5.0 Patch 4 for Tru64. To install them see section 3.3.1.
9

2.3 Third-Party Products Compatibility
The TeMIP Framework V5.0 Patch 4 for Tru64 has been validated with:
• Version 6.3.2 of DEC C++ (CXX) for Tru64 UNIX
• Oracle 9i version 9.2.0.4
• IONA Orbix E2A ASP V6.1: The TAL Orbix Server FM is now delivered
with this version. See section 6.1 to obtain more details on the upgrade of
this product.
Note: Contact Oracle Support for Patch availability: http://www.oracle.com
10

Chapter 3
Installing the Maintenance Patch
Important Note
All the actions described in this chapter must be performed with root privileges.
3.1 Installation on a non-TruCluster
Configuration
3.1.1 Installation of a New Director
In the context of a new TeMIP director, the following actions must be performed:
1.
2.
Install and configure the TFR V500 Level 1 Revision G Manufacturing Release
using the tool TeMIP_install delivered with the tar file of the TeMIP Framework
V5.0 Patch 4 for Tru64.
For details on the MR kit installation /configuration, refer to the OpenView
TeMIP Installation Guide.
Install the TeMIP Framework V5 Patch 4 for Tru64. Perform the following steps:
• Stop the TeMIP director, the TNS clerk and the TNS server if it is running on
this machine and TeMIP Licenses server if needed:
/usr/opt/temip/bin/temip_stop
/usr/opt/tns/bin/tns_stop or /usr/opt/tns/bin/tns_clerk_stop
/usr/opt/temip/bin/temip_licenses_server stop
• Execute the mandatory pre-installation operations: see section 3.3.3.1.
• Install STM and Orbix pre-requisite subsets and the TeMIP Framework
V5.0 Patch 4 for Tru64 Maintenance Patch (see section 3.3)
• Execute the mandatory post-installation operations: see section 3.3.3.2.
• After manual installation, activate the release tree using:
/usr/opt/TeMIP/temip/bin/temip_activate
/usr/opt/TeMIP is the TeMIP release directory for the Maintenance Patch.
• Restart the TeMIP licenses server and the TNS clerk, restart the TNS server or
check the TNS server is up and running on your platform
/usr/opt/temip/bin/temip_licenses_server start
/usr/opt/tns/bin/tns_start or /usr/opt/tns/bin/tns_clerk_start
• Configure the TAL Orbix Server FM and the TeMIP MAP (if needed). (see
section 3.4)
11

• Restart the TeMIP director (which processed will now be running from the new
release tree):
/usr/opt/temip/bin/temip_start
3.1.2 Installation on Top of a Director Already Configured
In order to install the TeMIP Framework V5.0 Patch 4 for Tru64 on top of a
TeMIP director already configured, you must perform the following steps:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Check that TFR V500 Level 1 Revision G MR kit is installed under the TeMIP
release tree (/usr/opt/TeMIP) associated to the director.
As described in the OpenView TeMIP Installation Guide, you must first clone this
TeMIP release tree.
• Create the TeMIP release directory for the Maintenance Patch:
mkdir /usr/opt/TeMIP
• Clone the release tree using the standard cp Unix command
cp -R -p /usr/opt/TeMIP/* /usr/opt/TeMIP
List the different release trees and the installed subsets and patches using the
following command: /usr/opt/temip/bin/temip_inventory -a
Install the STMPATCH20449V500 on all your release tree directories (see
Section 3.3.1.1)
Under this new release tree:
Un-install all eventual installed TFR patches:
setld -D /usr/opt/TeMIP -d TFRPATCHXXXXV500XXXX
setld -D /usr/opt/TeMIP -d TFRTRU64XXXX (new name for
TFR patches on Tru64)
If a previous Maintenance Patch was already installed, un-install it:
setld -D /usr/opt/TeMIP -d TFRXXXXV50001P00X
Execute the mandatory pre-installation operations: see section 3.3.3.1.
Install the STM and Orbix pre-requisite subsets and the TFRV50001-04
subsets under this new release tree (see Section 3.3)
Execute the mandatory post-installation operations: see section 3.3.3.2.
Stop the TeMIP director, the TNS clerk and the TNS server if it is running on this
machine and TeMIP Licenses server:
/usr/opt/temip/bin/temip_stop
/usr/opt/tns/bin/tns_stop or /usr/opt/tns/bin/tns_clerk_stop
/usr/opt/temip/bin/temip_licenses_server stop
After manual installation, activate the release tree using:
/usr/opt/TeMIP/temip/bin/temip_activate
/usr/opt/TeMIP is the TeMIP release directory for the Maintenance Patch.
Restart the TeMIP licenses server and the TNS clerk, restart the TNS server or
check the TNS server is up and running on your platform
/usr/opt/temip/bin/temip_licenses_server start
/usr/opt/tns/bin/tns_start or /usr/opt/tns/bin/tns_clerk_start
Configure the TAL Orbix Server FM and the TeMIP MAP (if needed). (see
section 3.4)
Restart the TeMIP director (which processed will now be running from the new
release tree):
/usr/opt/temip/bin/temip_start
12

3.2 Installation on a TruCluster Configuration
Three cases can occur:
• No director is configured.
• A TFR V500 Level 1 Revision G MR Director is already configured.
• A TFR V500 Level 1 Revision G MR Director is already configured and TFR
V5.0 Level 1 Patch 3 Maintenance Patch has been previously installed.
3.2.1 Installation of a new TeMIP director
In the context of a new TeMIP director, the following actions must be performed:
1.
2.
3.
4.
5.
6.
7.
8.
Install and configure the TFR V500 Level 1 Revision G MR using the tool
TeMIP_install delivered with the tar file of the TeMIP Framework V5.0 Patch 4
for Tru64.
For details on the MR kit installation /configuration, refer to the OpenView
TeMIP Use in a TruCluster Environment.
Execute the mandatory pre-installation operations: see section 3.3.3.1.
Install the STM and Orbix pre-requisite subsets and the TFRV50001-04
subsets (see section 3.3).
Execute the mandatory post-installation operations: see section 3.3.3.2.
Generate a new CAA action script for the TeMIP director (see Sections 3.2.2.2
and 3.2.2.3).
Activate the release tree (see Section 3.2.2.4)
Configure the TAL Orbix Server FM and the TeMIP MAP (if needed). (see
section 3.4)
Restart the TeMIP director (caa_start )
3.2.2 Installation of the Maintenance Patch on top of an already configured
director and no other Maintenance Patch is already installed.
This section details the way to install and activate the TeMIP Framework V5.0 Patch
4 for Tru64 on top of a director already configured on a TruCluster.
3.2.2.1 TeMIP Framework V5.0 Patch 4 for Tru64 Maintenance Patch
installation
In order to install the TeMIP Framework V5.0 Patch 4 for Tru64 on top of a TeMIP
director configured on a TruCluster, you must perform the following steps:
1. Check that TFR V500 Level 1 Revision G MR kit is installed under the TeMIP
release tree (/usr/opt/TeMIP) associated to the director.
2. As described in the OpenView TeMIP Installation Guide, you must first clone this
TeMIP release tree.
• Create the TeMIP release directory for the Maintenance Patch:
mkdir /usr/opt/TeMIP
• Clone the release tree using the standard cp Unix command
cp -R -p /usr/opt/TeMIP/* /usr/opt/TeMIP
3. Install the STMPATCH20449V500 on all your release tree directories (see
Section 3.3.1.1)
Under this new release tree:
13

4. Un-install all eventual installed TFR patches:
setld -D /usr/opt/TeMIP -f -d TFRPATCHXXXXV500XXXX
setld -D /usr/opt/TeMIP -f -d TFRTRU64XXXX (new name for TFR
patches on Tru64)
The error message:
“ERROR: TeMIP Subsets cannot be installed in
Use the -D option with a path of the form: /usr/opt/TeMIP
where is a string of your choice.
Setld: TFRPATCHXXXXV500XXXX deletion declined by subset control
program,
But subset will be deleted anyway on member1.”
indicates a well-known problem described in TruCluster documentation (see
OpenView TeMIP Use in a TruCluster Environment/Subset Un-installation
section)
5. Execute the mandatory pre-installation operations: see section 3.3.3.1
6. Install the STM and Orbix pre-requisite subsets and the TFRV50001-04
subsets under this new release tree (see Section 3.3).
(The warning message indicates that the temip_activate is not performed, as the
TeMIP Framework V5.0 Patch 4 for Tru64 is not installed on the active release
tree)
7. Execute the mandatory post-installation operations: see section 3.3.3.2.
8. Generate a new CAA action script for the TeMIP director if needed (see Sections
3.2.2.2 and 3.2.2.3).
9. Activate this new release tree (see Section 3.2.2.4).
10. Configure the TAL Orbix Server FM and the TeMIP MAP (if needed). (see
section 3.4)
11. Restart the TeMIP director (caa_start )
3.2.2.2 New TeMIP action script provided with the TFR V500 Level 1
Patch 3 Maintenance Patch
The TFR V500 Level 1 Patch 3 Revision G provided a new template for the
generation of TeMIP director CAA action scripts.
When installing The TFR V500 Level 1 Patch 3 kit, it was therefore necessary to
generate new CAA action scripts for all directors already running on a TruCluster.
If you did not install the TFR V500 Level 1 Patch 3 Maintenance Patch on your
director, it is necessary to update the TeMIP Director CAA action scripts when
installing the TeMIP Framework V5 Patch 4 for Tru64 Maintenance Patch.
For this purpose, after the patch installation, some manual actions must be performed
for each director. The following example describes these actions.
Assume for instance a TeMIP director named director_1 is running on the cluster and
is associated to a cluster alias named rossini. This means the associated action script
is:
/var/opt/TeMIP_directors/director_1/caa/rossini_TeMIP.scr
Furthermore, assume the new TeMIP release tree associated to this director is:
/usr/opt/TeMIPV500L1P4_director_1
And that this director is registered by TNS under END50_NS:.temip
14

Note
If you already applied the following actions, you need only to edit the action
script:
In /var/opt/TeMIP_directors/director_1/caa/rossini_TeMIP.scr file,
TEMIP_RELEASE_TREE variable must be set to:
/usr/opt/TeMIPV500L1P4_director_1/temip
1.
2.
3.
4.
Copy and rename the
/usr/opt/TeMIPV500L1P4_director_1/temip/TruCluster/TeMIP_Action.tmpl
action script template under a temporary directory:
cp /usr/opt/temip/TruCluster/TeMIP_Action.tmpl /tmp/rossini_TeMIP.scr
Edit this /tmp/rossini_TeMIP.scr file.
Four variables in this file must be adapted to your configuration:
• TEMIP_RELEASE_TREE must be set to:
/usr/opt/TeMIPV500L1P4_director_1/temip
• SERVICE_NAME must be set to rossini_TeMIP
• DIRECTOR_NAME must be set to END50:.temip.director_1
• SERVICE_ALIAS must be set to rossini
Save /tmp/rossini_TeMIP.scr.
Backup the /var/opt/TeMIP_directors/director_1/caa/rossini_TeMIP.scr
If you have made some changes in the Action script before installing
TFRV500L01P04, merge the file
/var/opt/TeMIP_directors/director_1/caa/rossini_TeMIP.scr and file
/tmp/rossini_TeMIP.scr to the file /tmp/rossini_TeMIP.scr
In the case a TNS server is running on the cluster and is installed under the new
TeMIP release tree see Section 3.2.2.3.
3.2.2.3 New TNS server action script
It is necessary to update the TNS_RELEASE_TREE variable in the TNS server CAA
action script (located under /var/opt/tns/caa).
For this purpose:
1.
2.
Stop the TNS server (caa_stop )
Update the TNS_RELEASE_TREE variable in the TNS server action script
For instance, TNS_RELEASE_TREE=/usr/opt/TeMIPV500L1P4_director_1/tns
3.2.2.4 Activation of the new release tree
The new TeMIP release tree must be activated on the active TeMIP director
member (that is the member on which the director is running).
Note that if the TeMIP director is not running (normally, at this step, it should still be
running), the active TeMIP director is the latest member on which the director was
running.
In order to find the active TeMIP director member for a director not running, find the
(unique) member on which the link /var/opt/temip ->
/var/opt/TeMIP_directors/ exists.
15

Perform the following actions on the active TeMIP director member:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Stop the TeMIP director if needed:
caa_stop
Stop the TNS clerk if needed:
/usr/opt/tns/bin/tns_clerk_stop
Move the new CAA action script under its correct location if needed:
/var/opt/TeMIP_directors//caa)
(In our previous example: mv /tmp/rossini_TeMIP.scr
/var/opt/TeMIP_directors/director_1/caa/rossini_TeMIP.scr)
If the TNS server is running on the active TeMIP director member, stop it:
caa_stop
After manual installation, activate the new TeMIP release tree:
/usr/opt/TeMIP/temip/bin/temip_activate
/usr/opt/TeMIP is the TeMIP release directory for the Maintenance Patch.
If the TNS server is running on the active TeMIP director member, re-start it:
caa_start < TNS server CAA resource name>
Re-start the TNS clerk:
/usr/opt/tns/bin/tns_clerk_start
Process post-installation mandatory operations (see Section 3.3.3.2)
Cleanup the old TeMIP release tree (if required)
3.2.3 Install Maintenance Patch on top of a director already configured and
TFR V5.0 Level 1 Patch 3 is already installed.
This section details the way to install and activate the TeMIP Framework V5
Patch 4 for Tru64 on top of a director already configured on a TruCluster in
the case the TFR V5.0 Level 1 Patch 3 Maintenance Patch has been
previously installed.
3.2.3.1 TeMIP Framework V5.0 Patch 4 for Tru64 Maintenance Patch
installation
In order to install the TeMIP Framework V5.0 Patch 4 for Tru64 on top of a TeMIP
director configured on a TruCluster, you must perform the following steps:
1. Check that TFR V500 Level 1 Revision G MR kit is installed under the TeMIP
release tree (/usr/opt/TeMIP) associated to the director.
2. As described in the OpenView TeMIP Installation Guide, you must first clone this
TeMIP release tree.
• Create the TeMIP release directory for the Maintenance Patch:
mkdir /usr/opt/TeMIP
• Clone the release tree using the standard cp Unix command
cp -R -p /usr/opt/TeMIP/* /usr/opt/TeMIP
3. Install the STMPATCH20449V500 on all your release tree directories (see
Section 3.3.1.1)
Under this new release tree:
16

4. Un-install all eventual installed TFR patches:
setld -D /usr/opt/TeMIP -f -d TFRPATCHXXXXV500XXXX
setld -D /usr/opt/TeMIP -f -d TFRTRU64XXXX (new name for
TFR patches on Tru64)
The error message:
“ERROR: TeMIP Subsets cannot be installed in
Use the -D option with a path of the form: /usr/opt/TeMIP
where is a string of your choice.
Setld: TFRPATCHXXXXV500XXXX deletion declined by subset
control program,
But subset will be deleted anyway on member1.”
indicates a well-known problem described in TruCluster documentation (see
OpenView TeMIP Use in a TruCluster Environment/Subset Un-installation
section)
5. Un-install TFRXXXXV50001P003 maintenance patch subsets:
setld -D /usr/opt/TeMIP -d TFRXXXXV50001P003
6. Execute the mandatory pre-installation operations: see section 3.3.3.1.
7. Install the STM and Orbix pre-requisite subsets and the TeMIP Framework
V5.0 Patch 4 for Tru64 subsets under this new release tree (see Section 3.3).
(The warning message indicates that the temip_activate is not performed, as the
TeMIP Framework V5.0 Patch 4 for Tru64 is not installed on the active release
tree)
8. Execute the mandatory post-installation operations: see section 3.3.3.2.
9. Generate a new CAA action script for the TeMIP director if needed or reset
correct values in the existing one (see Sections 3.2.2.2 and 3.2.2.3).
10. Activate this new release tree (see Section 3.2.2.4)
11. Configure the TAL Orbix Server FM and the TeMIP MAP (if needed). (see
section 3.4)
12. Restart the TeMIP director (caa_start )
3.3 Installing the TFRV50001-04 Subsets
Be sure to observe all the points listed in the TeMIP Framework V5.0 Patch 4 for
Tru64 Compatibility section (see Chapter 2).
You can only install the TeMIP Framework V5.0 Patch 4 for Tru64 subsets if the
corresponding Manufacturing Release subsets have already been installed on the
system.
You must first install pre-requisite subsets (see Section 3.3.1). Then you can choose
to install the maintenance patch manually using setld command (see Section 3.3.3) or
using TeMIP SystemMate tool (see Section 3.3.2)
The following list shows the subsets delivered with the TFRV50001-04 Maintenance
Patch kit:
Subset
TFRBASEV50001P004
Description
TeMIP Framework Base System Release
V500 level 01 patch 004 Rev E
17

TFRTFCV50001P004
TFRDBV50001P004
TFRITORT123V50001P004
TFRITORT512V50001P004
TFRITORT610V50001P004
TFRTNSCLRV50001P004
TFRTNSSRVV50001P004
TeMIP Framework Visual TeMIP C++
Developer Toolkit Release V500 level 01
patch 004 rev E
TeMIP Framework Database Tools Release
V500 level 01 patch 004 rev E
TeMIP Framework Iona Tech. Orbix 2K
Runtime V1.2.3 Release V500 level 01 patch
004 rev E
TeMIP Framework Iona Tech. Orbix E2A
Runtime V5.1.2 Release V500 level 01 patch
004 rev E
TeMIP Framework Iona Tech. Orbix E2A
Runtime V6.1 Release V500 level 01 patch
004 rev E
TeMIP Framework Name Service Clerk
Release V500 level 01 patch 004 rev E
TeMIP Framework Name Service Server
Release V500 level 01 patch 004 rev E
3.3.1 Prerequisite Subset Installation
In order the TeMIP Framework V5.0 Patch 4 for Tru64 to run properly, it is
mandatory to install the following list of products. These products are part of the tar
file delivering the TeMIP Framework V5.0 Patch 4 for Tru64.
3.3.1.1 STM mandatory patches
Install manually STM patch 18128 and 20449 (if not already installed
previously).
The STM patch 20449 must be installed on all your release trees before
installation of the TeMIP Framework V5 Patch 4 for Tru64. The STM patch
19166 must be un-installed before installing the STM patch 20449 if it was
installed.
For example, on the TeMIP release directory /usr/opt/TeMIP, execute the
following command:
setld –D /usr/opt/TeMIP -d STMPATCH19166V500
setld –D /usr/opt/TeMIP –l /STMPATCH20449V500
setld –D /usr/opt/TeMIP –l /STMPATCH18128V500
3.3.1.2 TFR Orbix E2A ASP 5.1.2 Runtime additional subset
Install manually TeMIP Framework Orbix E2A ASP 5.1.2 Runtime (it is not part of
the TeMIP Framework V5.0 Patch 4 for Tru64), if not already installed. Execute
following command:
setld -D /usr/opt/TeMIP -l /TFRITORT512V500
18

Note
When installing the Maintenance Release TeMIP Framework V5 Patch 4 for Tru64,
Orbix E2A ASP 6.1 becomes the official Orbix version used by the TAL Orbix
Server FM. However, Orbix E2A ASP 5.1.2 is still mandatory and must be
installed before Orbix E2A ASP 6.1.
Orbix E2A ASP 5.1.2 continues to be delivered in order CORBA AMs can continue
running using this Orbix version.
3.3.1.3 TFR Orbix E2A ASP 6.1 Runtime additional subset
TFRITORT512V500 subset must have already been installed.
Install manually TeMIP Framework Orbix E2A ASP 6.1 Runtime (it is not part of
the TeMIP Framework V5.0 Patch 4 for Tru64), if not already installed. Execute
following command:
3.3.1.4 JAVA131 Subset
setld -D /usr/opt/TeMIP -l /TFRITORT610V500
This subset is needed for the Orbix configuration tool.
If it has not yet been installed, install the JAVA131 kit with following commands:
cd /tmp
cp xvf /JAVA131-4.tar .
tar xvf JAVA131-4.tar
setld –l /tmp/131-4
This kit should not be installed under the TeMIP release tree.
If you need to use System Mate tools, this version should not be set as the default
version, the default version must remain java122. See Section 6.5.1.
3.3.2 Installation of the Maintenance Patch using TeMIP
SystemMate
Important Note
Due to problem PR#21680, the TeMIP Framework V5 Patch 4 for Tru64 kit
cannot be installed using TeMIP SystemMate. See PR#21680.
If you need to install this kit using TeMIP SystemMate, please contact the
TeMIP Support (e-mail: VBETEMIPSUPP@hp.com ) to get a patch for this
problem.
Note
If a TFR V5.0 director was already configured, it is highly recommended to import
the new Bundle configurations and services delivered with the TeMIP Framework
V5.0 Patch 4 for Tru64 with the following commands:
# /usr/opt/SystemMate/bin/stm_import /cdrom/TeMIP-V50A-UNIX/INST
# /usr/opt/SystemMate/bin/stm_import /cdrom/TeMIP-V50A-jNIX/INSTALL/*.jar
These commands save the previous version of the .dar and .jar files in a backup
directory (/var/opt/SystemMate/client/backup).
19

1. Start the TeMIP SystemMate deployment tool and load the TeMIP Maintenance
Assistant Configuration.
2. Start the Install Maintenance Release directive.
3. During the installation a copy of tal.dict_cache and scs_fm.dict_cache is
performed, check the TeMIP SystemMate post-installation mandatory operations
chapter (section 3.3.2.1) for more information.
3.3.2.1 TeMIP SystemMate post-installation mandatory operations
If the State Collection Server FM dictionary cache (scs_fm.dict_cache) and TAL
dictionary cache (tal.dict_cache) were customized, a backup of these files exists in
/var/opt/temip/conf/$LANG.
(LANG variable is defined in /var/opt/temip/conf/.temip_config file).
To restore the customized caches, copy the last backup as follow:
# cp /var/opt/temip/conf/$LANG/scs_fm.dict_cache.bck[xx]
/var/opt/temip/conf/$LANG/scs_fm.dict_cache
# cp /var/opt/temip/conf/$LANG/tal.dict_cache.bck[xx]
/var/opt/temip/conf/$LANG/tal.dict_cache
A kernel system parameter of Tru64 UNIX must be updated by executing the
following command on all your machines where TeMIP is running:
# sysconfig -r proc dump_setugid_cores=1
3.3.3 Installation of the Maintenance Patch Using seltd
Install the Maintenance Patch kit using:
setld -D /usr/opt/TeMIP -l ” command.
Note
TFRTFCV50001P004 and TFRTNSSRVV50001P004 subsets are delivered with the
Maintenance Patch TeMIP Framework V5 Patch 4 for Tru64 and are optional. If the
corresponding Manufacturing Release subsets have not been installed on your
machine, an error message will be displayed. It is a normal behavior.
3.3.3.1 Setld pre-installation mandatory operations
As the Maintenance Patch installs the State Collection Server FM dictionary cache
(scs_fm.dict_cache) and TAL dictionary cache (tal.dict_cache), these files must be
saved if they were previously customized and after the installation they must be
copied back (see section 3.3.3.2).
These files are located in /var/opt/temip/conf/$LANG/
(LANG variable is defined in /var/opt/temip/conf/.temip_config file).
3.3.3.2 Setld post-installation mandatory operations
Please perform the additional (Maintenance Patch kit specific) configuration:
Restore the customized caches (see Section 3.3.2.1)
A kernel system parameter of Tru64 UNIX must also be updated by executing the
following command:
# sysconfig -r proc dump_setugid_cores=1
20

3.4 Configuration
• Configure the TAL Orbix Server FM in order to configure TeMIP with Orbix
E2A ASP 6.1 (Mandatory step to be able to run the TAL Orbix Server FM)
• Check TeMIP has been stopped using /usr/opt/temip/bin/temip_show
command.
• Run /usr/opt/temip/bin/orbix_stop_512 in case Orbix E2A ASP 5.1.2
process are still running.
• Run /usr/opt/temip/bin/orbix_stop_123 in case Orbix 2000 1.2.3 process
are still running.
• Check the default Java version is 1.3.1 or 1.4.x. (/usr/opt/java directory).
Else you need to define JAVA_HOME variable to /usr/opt/java131 before
running the script temip_setup -> tal_orbix_server setup.
• Run /usr/opt/temip/bin/temip_setup, choose 4 “Other TeMIP products
setup” and choose “TAL Orbix Server setup”
Note
If Orbix E2A ASP 5.1.2 processes are not stopped before running temip_setup ->
tal_orbix_server_setup for Orbix E2A ASP 6.1, the Orbix configuration fails.
Indeed, before running /usr/opt/temip/bin/temip_orbix_setup_512 script, Orbix E2A
ASP 5.1.2 itlocator process still uses IIOP port 3075. If this process is running when
configuring Orbix E2A ASP 6.1, it uses port 3075 and Orbix E2A ASP 6.1 itlocator
cannot use this port. In that case, the following error occurs:
temip_setup -> TAL Orbix Server setup
...
Starting itconfigure. This setup will take some time. Check the
log file at /var/opt/temip/orbix/610/log to see the progress
Error Saving Deployment Descriptor
com.iona.cfg.tools.common.ConfigurationSettingsException: The
port 3075 on the host moorea.vbe.cpqcorp.net, is required by
the locator service, but is currently being used by another
process.
...
temip_orbix_setup_610 script is not allowed to kill Orbix E2A ASP 5.1.2 processes
because, Orbix E2A ASP 5.1.2 can continue running on the machine even with Orbix
E2A ASP 6.1 installed.
This is the reason why you are asked to stop Orbix E2A ASP 5.1.2 processes by
running /usr/opt/temip/bin/orbix_stop_512 before running temip_setup ->
tal_orbix_server_setup.
• Configure the TeMIP Map. This step is necessary if TeMIP Client applications
connect to this director. Especially it is needed in order the TeMIP Client Entity
Browser can display entities without error.
• Run /usr/opt/temip/bin/temip_setup, choose 4 “Other TeMIP products setup” and
choose “TeMIP Map setup”
• Re-configure Orbix E2A ASP 5.1.2 if needed. For more details, see section
6.1.1.2.
21

3.5 Manual Operations
If you want to enjoy some fixes done into template files located in /usr part of oracle
configuration files delivery, you have to carry the changes forward to your own files
in /var part, or update your own files.
The following changes are relative to fixes already included in TFR V500 Level 1
Patch 3 Maintenance Release, except for PR#21602 that is new (see PR#21602).
Execute the following actions if not yet done with the previous Maintenance Release:
If you create a new database:
• To enjoy the new sizing of system tablespace (required by Oracle 9 release 2)
• Replace:
/var/opt/temip_oracle//conf/temip_database_mandatory_parameters.cfg
by
/usr/opt/temip/oracle//conf/temip_database_mandatory_parameters.cfg
Or report SYS_SIZE parameter value change if you have already modified this
file.
You have a database already created:
• If the Oracle server has been upgraded from Oracle 9 release 1 to Oracle 9
release 2, you need to resize your system tablespace.
• You can do it this way:
Set ORACLE_HOME
Set ORACLE_SID
Launch SQLPLUS
SQL> connect system/
SQL> alter database datafile
'/usr/ORACLE/u02/oradata//SYSTEM/system01.dbf' resize
200M;
• If you want to benefit of the PR#21602 fix delivered in the TeMIP Framework
V5 Patch 4 for Tru64, run the following script on all your existing databases
(master and replica):
/usr/opt/temip/oracle/temipmap/scripts/update_schema
Stop/Start all modified databases.
• In the initialization files of the TeMIP databases: initaharchi.ora, initahrepos.ora,
initpapirep.ora, initsyno.ora, inittmeta.ora
Update:
The value of the parameter “remote_os_authent” to false (PR#11869)
Remove the parameter job_queue_interval (PR#18098)
Stop/Start all modified databases.
• In the initialization file of the TeMIP databases: inittemipmap.ora
22

Update the value of the parameter “remote_os_authent” to false (PR#11869)
Update the value of parameter shared_pool_size to 20000000
Remove the parameter job_queue_interval (PR#18098)
Stop/Start temipmap database.
23

Chapter 4
Fixed Problems in TFRV50001-04
Problems corrected by the Maintenance Patch are listed in the following sections
Table 1 Software Fixed Problems reported in TFR V50001-04
PR# COMPONENT PROBLEM SYNOPSIS
21355 FCL_PM Quotes and brackets in ManagedObject name
21153 KIT new Epatch naming convention
21116 EXEC EXEC: memory leaks when we performing a mcc_call_function
21077 DOMAINS domain map filename does not change after V4 to V5 migration
21041 TOOLS reloaddictionary not working when adding a simple subclass
20933 SCS statemanagement not working when more than 50 subdomains at the same level
20832 EXEC EXEC: Conversion problem for ASN.1 Unsigned 32 to TeMIP Unsigned32
20782 TAL-CS TSyncCall issue on TAL ClientServer
20666 ORACLE Wrong version of Oracle libraries provided with TFR V500L01P03
20420 AH_FM Avoid OC state changes at AHFM shutdown
20255 TAL-CS TAL Client/Server should support single sign-on when connecting from Windows
20149 SYS_LIB mcc_sys_interface_def.h has not been provided with TeMIP V500 P03
25

19991 TFC Avoid parallel OnDoCreate() executions
19738 EF_FM Corrective filter cannot change Event code
19682 ORACLE_ADMI
N_TOOLS
Remove unnecessary errors from the logfiles for the install of the syno temipmap & aharchi databases
19645 EXEC EXEC: Interop. issue : exception ILVTOOBIG raised while decoding a ASN1 real
19563 EXEC TeMIP standalone application crash during temip_stop
19471 ACS customer is getting error while opening client workspace which has got two OC's when central_loggin is enabled
19342 TAL-CS TAL: Incorrect login : behavior regression between V4 and V5
19326 FCL_PM Problem with manage when using all attribute and wildcarding within entity name
19169 NOTIF_FM Common retrying call is not ignored even if listed
19091 EXEC Avoid popen() to calculate checksum
18936 FCL_PM Show all attr on instance-less classes fails
18837 TFC MParameterList (MReply) copy should set correct Parameter reverse link
18750 TAL SunV50 : TAL : Tal crash when invalid string are set in TeMIP Client management view
18737 HDS HDS not working correctly with central logging
18601 TOOLS Errors during restore with temip_backup on tns.group
18560 TOOLS temip_show -a returns arithmetic overflow.
18379 SYN_API TAL syno cache not correctly updated with composite
17970 NOTIF_FM Notif FM systematically produces a core when using duration qualifier and term notif directive
17659 TAL-CS Can/how TAL Orbix server and TeMIP Client work over a network protected by firewall?
17544 NOTIF_FM I18N: Event lost: case sensivity on international characters
17471 TAL alarm are lost if MO not in dictionary (OID_DOES_NOT_EXIST)
17052 EF_FM MEventReport event.GetEventReport() conficts with SetTargetEntity()
16491 FCL_PM Problems if Specific Problem enum data-type is too large
26

16416
16171
15550
14034
8994
1190
EF_FM memory leak on setting the target entity using a MString rather than MFullName
MAPDB temip_map_database_setup cannot export map when Special Characters in string fields
AH_FM Cannot 'archive' an alarm object when its user text field is greater than 40 char.
AH_FM SQL error message is lost during an archive operation
KIT the libtemip_ef_userlibrary.so is overwritted in the one coming with patch 2
AH_FM do not remove cr in additional text during archive
27

Chapter 5
Known Problems
5.1 Previous Known Problems still applicable on TFR V500 Patch 4 for
Tru64
This section sets out the problems discovered during previous testing campaigns on Tru64 or Sun Solaris platforms, which have not been fixed in
this Maintenance Patch.
Table 2
Software Known Problems on Tru64
Ref Component Description Workaround
2442 TAL No exception raised when using SetTime on a call with a bad syntax. When
using a partially correct syntax in a SetTime, like SetTime("at start +2, every
5") ,it take into account the valid part "at start+2" and not the bad part (after the
invalid ","), and didn't return any exception.
Check that SetTime is correctly
encoded in your application.
7050
TNS
In case of disk getting full, the TNS clerk configuration might become corrupted.
Indeed, the Name Space prefixing any TeMIP entity might become not readable.
Example:
Reconfigure the TNS clerk through
the temip_setup utility or used
backups to restore the original
Clearinghouse
manage show op oc1
TeMIP Framework (V5.0.0)
28

Ref Component Description Workaround
Using default ALL IDENTIFIERS
OPERATION_CONTEXT 00-00-00-00-00-00-00-DD-37-00:.oc1
On director: corsica_ns:.temip.corsica_director
AT Thu Dec 13 17:41:57 Identifiers
Name = 00-00-00-00-00-00-00-DD-37-00:.oc1
14450 SCS SCS crash when deleting the top domain collection and stopping the module None
16452 ORACLE Synonym Replica databases not updated (de-synchronized). Apply workaround described in
Section 6.5.7Error! Reference
source not found. Synonym
replica databases not updated (desynchronized)
18777 ORACLE Oracle replication: a Replica creation fails in a specific case: master 9.2/Replica
9.0.1.4
We try to create a replica on Oracle 9.0.1.4, when the
Master is running on Oracle 9.2.0.3.
At creation time, on the statement:
CREATE SNAPSHOT MAP_ITEMS
CLUSTER temipmap.ITEM_CLU (SEQ_ID)
REFRESH FAST WITH PRIMARY KEY
USING DEFAULT LOCAL ROLLBACK SEGMENT
AS SELECT * FROM
temipmap.MAP_ITEMS@master92.nieves.vbe.cpqcorp.net;
The following error is displayed:
creating 'MAP_ITEMS' snapshot
This happens only for the 3
snapshots using CLUSTERS:
MAP_ITEMS,
MATCHED_FILTERS and
GRAPHICAL_REPRESENTATIO
N.
An Oracle case has been created to
track this issue
Note:
The problem exists only in the
following configuration:
29

Ref Component Description Workaround
AS SELECT * FROM
temipmap.MAP_ITEMS@master92.nieves.vbe.cpqcorp.net
*
ERROR at line 5:
ORA-01753: column definition incompatible with clustered column definition
Master 9.2 -> Replica 9.1
But, no problem has been detected
for configurations:
Master 9.2 -> Replica 9.2
Master 9.1 -> Replica 9.1
Master 9.1 -> Replica 9.2
18778 GAT TRU64: Issue with function strptime() in V5.1B PatchKit 2 BL 22.
The AXE10 is disrupted in its alarm decoding, when calling the function:
strptime().
The function is called in the GAT (BinAbsTime.cxx).
(Actually, the AXE10 doesn't crash, and still provide an alarm, but this alarm
doesn't correspond to the alarm provided by the equipment => the severity is set
to INDETERMINATE, the timestamp, is the current one).
The problem is that before the PatchKit 2 BL22, the strptime() function was
accepting white space in the "date" input string.
Since PatchKit 2 BL22, the strptime() returns a null pointer, if the input "date"
contains spaces, and thus doesn't match strictly, the input format.
A case is open to Tru64 concerning
this issue.
30

5.2 New Known Problems Reported in the TFR V500 Patch 4 for Tru64
This section sets out the problems discovered during the current testing campaign, which have not been fixed in this Maintenance Patch.
Table 3
Software Known Problems on Tru64
Ref Component Description Solution
21611 SYS_LIB TeMIP international catalog files installed on
/usr/opt/temip/en_US.ISO8859-1 directory cannot be opened
by TeMIP processes when LANG environment variable is set
to a different value than en_US.ISO8859-1.
21623
TOOLS
Interoperability V4/V5
Using the temip_synchro_mdata tool, the new class
Toggling_Filter (TeMIP V5.0) is not added in the V4.0
TeMIP director. Thus this class can not be managed from a
V4.0 TeMIP director.
21666 TOOLS The following error may occur when running the
temip_setup
->tal_orbix_server_setup at the end of the setup:
Framework initialization failure:
02/04 11:18:15[19414][1] %MCC-F-
DIR_NO_KERNEL_INIT, director: no kernel initialization
This is due to a synchronization problem, but there is no
impact on the TAL configuration, it is successfully
configured.
cd /usr/opt/temip
ls -sf en_US.ISO8859-1 $LANG
Before propagating new V50 classes with temip_synchro_mdata
you have to:
- De-enroll the Event Filter FM from the V40 dispatch table:
temip_enroll -r event_filter_fm
- Propagate the new V50 classes using temip_synchro_mdata from
V50 director
Ignore the error message. The action is successful: TeMIP and the
TAL Orbix Server FM are ready to be started.
31

21679 SYSTEM MATE Incorrect message with System Mate when installing the
TFR V5 Patch 4 Maintenance Patch on Tru64: the log
window displays two messages saying the subsets
TFRITORT512V50001P004 and
TFRITORT610V50001P004 do not need to be installed.
But in fact, these two subsets are installed and no message
informs the customer they have been installed on the host.
Ignore the error message. The action is successful:
21680 SYSTEM MATE Incorrect behavior with System Mate when installing the
TFR V5 Patch 4 Maintenance Patch on Tru64: the procedure
removes all the STM patches installed on the host. This
problem prevents from installing the current Maintenance
Patch using TeMIP System Mate.
If you need to install the TeMIP Framework V5 Patch 4 kit using
TeMIP SystemMate, please contact the TeMIP Support (e-mail:
VBETEMIPSUPP@hp.com ) to get a patch for this problem.
32

Chapter 6
Important Notes
6.1 Upgrade to Orbix E2A ASP 6.1
The TeMIP Framework Patch 4 Maintenance Patch upgrades Orbix product from Orbix E2A
ASP 5.1.2 to Orbix 6.1. This section describes the impact of this upgrade: the changes in the
Orbix configuration and the actions the user may need to apply.
6.1.1 Orbix E2A ASP 6.1 and 5.1.2 Configuration
6.1.1.1 Orbix E2A ASP 6.1 Upgrade
This upgrade is done into 2 steps:
1.
2.
Installation of an additonal mandatory subset TFRITORT610V500.
This subset provides all files necessary to use Orbix E2A ASP 6.1.
It is a temporary step. The installation of this subset has no impact on the different TeMIP
products. TAL Orbix Server FM and CORBA AMs continue using Orbix E2A ASP 5.1.2. It is
still the main Orbix version.
Look at /usr/opt/temip/release.notes/README.TFRITORT610V500 to see how configuring
and using Orbix E2A ASP 6.1 for your CORBA servers, without any impact on TeMIP
products.
Installation of the TeMIP Framework V5 Patch 4 Maintenance Patch and run
/usr/opt/temip/bin/temip_setup -> TAL Orbix Server FM setup
Once the Maintenance Release is installed and temip_setup -> tal_orbix_server_setup script
has been run, Orbix E2A ASP 6.1 becomes the official Orbix version. It means:
• TAL Orbix Server FM now uses the Orbix E2A ASP 6.1
• Orbix E2A ASP 6.1 processes (Locator and naming service) are now used by default:
In /usr/opt/temip/bin directory:
temip_orbix_setup is linked to temip_orbix_setup_610
orbix_start is linked to orbix_start_610
orbix_stop is linked to orbix_stop_610
temip_start calls orbix_start, so Orbix E2A ASP 6.1 is automatically started with
TeMIP.
33

The Orbix E2A ASP 6.1 itlocator process uses IIOP port 3075. It was already the IIOP
port of the itlocator.
• In order to fully support the firewall, the configuration of the Naming Service has been
changed from indirect persistence to direct persistence. See detailed explanations of
this change in 6.2.1.1 section.
Important Note
The fact that Orbix E2A ASP 6.1 has been installed on the director and becomes the official
Orbix version has no impact on CORBA AMs and CORBA Agent development and
runtime. CORBA AMs continue using Orbix E2A ASP 5.1.2 without any changes. The
CORBA Agent continue using Orbix 2000 1.2.3.
There is only an impact if Orbix E2A ASP 5.1.2 processes were used (itnaming and
itlocator), see explanations on this point below.
6.1.1.2 Orbix E2A ASP 5.1.2 Configuration
If some of your applications continue using Orbix E2A ASP 5.1.2 and these applications need
Orbix process to run (itlocator or itnaming), you have two possibilities:
1.
Continue using Orbix E2A ASP 5.1.2 for your processes and communicate with the
Orbix E2A ASP 6.1 services.
It is the recommended solution. The advantage in using Orbix 6.1 Naming Service is
that Orbix 6.1 processes are started automatically on your director when starting TeMIP.
In this case, once temip_orbix_setup_610 has been run, Orbix E2A ASP 6.1 Locator and
Naming Service are ready to be used:
• The Orbix 6.1 itlocator process uses IIOP port 3075 (like before)
• The database of the Orbix 6.1 Naming Service is initially empty, so you need to restart all
your CORBA server applications in order to update the Naming Service database.
Note
For example, in case you are running a trouble ticket server from one of the following TeMIP
Liaisons:
• TeMIP Remedy AR System Liaison V5.0,
• TeMIP Clarify eFrontOffice Liaison V5.0,
You will need to re-start the Trouble Ticket Liaison Server:
To stop then start the TeMIP Trouble Ticket Server run the following commands with root
privilege:
/usr/opt/temip_tttls/Runtime/temip_ttl_stop
/usr/opt/temip_tttls/Runtime/temip_ttl_start
• If you obtained the IOR of the naming service using the
/var/opt/temip/orbix/512/orbix_temip/iona_services.naming..ior file with
Orbix E2A ASP 5.1.2, you will need to update the manner to get this IOR, because this
file is not generated anymore with Orbix E2A ASP 6.1. It can be obtained in
/var/opt/temip/orbix/610/orbix_temip.cfg file searching for
“initial_references:NameService:reference” string.
34

2.
Continue using the Orbix E2A ASP 5.1.2 services.
In that case, you need:
• To re-run the /usr/opt/temip/bin/temip_orbix_setup_512 script in order to set the
correct IIOP ports. Once temip_orbix_setup_512 script has been run, the 5.1.2 itlocator
process uses IIOP port 6075 and can run in parallel with Orbix E2A ASP 6.1
processes.
• Depending on the manner you contact the naming service started on this TeMIP director,
you will need to:
Update the IIOP port of the itlocator process on the host where your CORBA
application runs (for example in /etc/hosts file or directly in the code of your
application). Thus your CORBA application will know the new IIOP port of the
itlocator process.
Re-obtain the IOR of the Naming Service which contains the new IIOP port of the
itlocator.
• Call the /usr/opt/temip/bin/orbix_start_512 and /usr/opt/temip/bin/orbix_stop_512 scripts
to start and stop Orbix E2A ASP 5.1.2 processes
6.1.2 Changing IIOP ports of the Orbix processes
The file /usr/opt/temip/orbix/610/conf/orbix_temip_dd_template.xml is the input file for the
temip_orbix_setup_610 script.
In this file, default values are defined for the IIOP ports used by the Orbix processes:
• Orbix 6.1 itlocator: 3075
• Orbix 6.1 itnaming: 3080
• Orbix 6.1 itnode_daemon: 3079 (process used internally)
These values must not be changed, except if there is a conflict with another application
using the same port.
In that case, the value must also be updated in a second configuration file:
/usr/opt/temip/orbix/610/conf/orbix_ABDriver_template.dtd.
To take the change into account:
- Stop Orbix processes: /usr/opt/temip/bin/orbix_stop as root or temip user and the TAL Orbix
Server FM.
- Re-run /usr/opt/temip/bin/temip_setup ->tal_orbix_server_setup as root user.
- Restart Orbix processes using /usr/opt/temip/bin/orbix_start as temip user and the TAL Orbix
Server FM.
- If the value of the IIOP port of the itlocator has changed, a variable must be defined on all
TeMIP Client hosts to indicate the new value. This variable is:
TAL_ORBIX_LOCATOR_IIOP_PORT.
This file defines also the property “direct persistent” equal to true for the naming service. See
explanations on this notion and why the naming service is now configured with direct
persistence equal to true in 21680
If the direct persistence is not useful in your environment, you can also come back to indirect
persistence by modifying /usr/opt/temip/orbix/610/conf/orbix_temip_dd_template.xml file:
35

Modify:
dd:service name="naming"
dd:activation mode="manual"
dd:run mode="direct_persistent" proxified="false" managed="false" authenticated="false"
perflog="false"
To:
dd:endpoint protocol="iiop" port="3080"
dd:service
dd:service name="naming"
dd:activation mode="manual"
dd:run mode="indirect_persistent" proxified="false" managed="false"
authenticated="false
" perflog="false"
dd:endpoint protocol="iiop" port="0"
dd:service
You need also to modify /usr/opt/temip/orbix/610/conf/orbix_ABDriver_template.dtd file:
Modify:
naming.port = “3080” to “0”
naming.tls.port=“3082” to “0”
naming.direct_persistence=“true” to “false”
In the same way, /usr/opt/temip/orbix/512/conf/ orbix_ABDriver_template.dtd file is the input
file for the temip_orbix_setup_512 script. In this file, default values are defined for the IIOP
ports used by the Orbix processes:
• Orbix 5.1.2 itlocator: 6075
• Orbix 5.1.2 itnode_daemon: 6079
• Orbix 5.1.2 itnaming: dynamic (indirect persistence)
In case of conflict, you can change the IIOP port values. To take the change into account:
- Stop Orbix 5.1.2 processes: /usr/opt/temip/bin/orbix_stop_512 as root or temip user and the
TAL Orbix Server FM.
- Re-run /usr/opt/temip/bin/temip_orbix_setup_512 as root user.
- Restart Orbix 5.1.2 processes using /usr/opt/temip/bin/orbix_start_512 as temip user.
6.1.3 Orbix environment variables needed to run Orbix E2A ASP
6.1 tools
If you want to run tools provided with Orbix E2A ASP 6.1, define the following environment
variables:
IT_LICENSE_FILE /usr/opt/temip/orbix/610/etc/licenses.txt
IT_PRODUCT_DIR /usr/opt/temip/orbix/610
36

IT_CONFIG_DOMAINS_DIR /var/opt/temip/orbix/610
IT_DOMAIN_NAME orbix_temip
LD_LIBRARY_PATH /usr/opt/temip/orbix/610/shlib:/usr/opt/temip/orbix/610/shlib/default
6.2 Firewall Support
Orbix E2A ASP can be configured in order the TAL Orbix Server FM and a TeMIP Client
communicate through a firewall. From Orbix E2A ASP 5.0, a new Orbix variable has been
provided in order to define a range of ports the CORBA server listens on.
It can be used to support a firewall between the TAL Orbix Server FM and the TeMIP Client.
If the TeMIP Director is protected by a firewall, Orbix processes (itlocator, itnaming) and the
TAL Orbix Server FM are protected by this firewall. Potential CORBA AMs are also
protected.
Here are the steps needed to configure Orbix to support a firewall on the TeMIP Director:
6.2.1.1 Check Orbix configuration
Dynamic ports range
In the Orbix configuration file generated by temip_setup -> tal_orbix_server_setup script, a
default range of dynamic ports used by all the CORBA servers (itnaming, itlocator,
itnode_daemon and TAL Orbix Server FM and potential CORBA AMs):
In /var/opt/temip/orbix/610/orbix_temip.cfg:
policies:iiop:server_address_mode_policy:port_range = "6000:6030";
This value is useful to access all the Orbix process through a firewall, by opening the same
range of ports, see details below.
This value can be changed in case of conflict with other applications.
This value can also be redefined for a specific CORBA Application if needed with another
value.
For example, to redefine a specific value for the TAL Orbix Server FM, this value can be
added in /var/opt/temip/orbix/610/orbix_tal_orbix_server.cfg:
temip
{
};
tal_orbix_server
{
...
};
policies:iiop:server_address_mode_policy:port_range = "6031:6033";
37

Important Note
If you re-run the temip_setup -> tal_orbix_server_setup that runs the temip_orbix_setup script,
the orbix_temip.cfg file is regenerated and the default value is redefined. Think about reset
your own values if needed in orbix_temip.cfg file.
Naming Service
With Orbix E2A ASP 5.1.2, all ports used by the Naming Service (itnaming) are correctly in
the range defined by the
policies:iiop:server_address_mode_policy:port_range variable.
With Orbix E2A ASP 6.1, one port used by the itnaming is still dynamic and not in the range.
To fix this problem, the configuration of the itnaming process has been changed:
Previously, the itnaming was "indirect persistent" (See explanations on Indirect persistence /
Direct persistence below). It means that the naming service:
used a dynamic IIOP port
it's IOR published the IIOP port of the itlocator instead of it's own port
Indirect persistence:
You can see if a CORBA server uses Orbix direct or indirect persistence in looking at the IOR
of a CORBA object that it manages.
Run iordump tool to display the content of an IOR with indirect persistence gives:
/usr/opt/temip/orbix/610/asp/6.1/bin/iordump "IOR:… "
Stringified IOR is: ([string/coded data] length: 416 / 206 bytes)
...
Port: 3075
(IANA allocated vendor IIOP port for: IONA Orbix ART
Locator)
...
Object key data:
':>.21.orbix_temip.f7f6438b.IT_NamingContextExt..........'
(looks like an Orbix ART Indirect Persistent key)
The IOR shows that indirect persistence is used and the IIOP port is 3075 (IIOP port of the
itlocator process).
With indirect persistence, when a client wants to connect to the naming service using this IOR,
it contacts first the itlocator that provides the dynamic IIOP port allocated for the itnaming.
Now, with direct persistence the naming service:
• uses a fixed IIOP port that is defined in the Orbix configuration (see below)
• it's IOR publishes it's own fixed port
Direct persistence:
Get IOR naming service in /var/opt/temip/orbix/610/orbix_temip.cfg:
initial_references:NameService:reference = "IOR:… ";
hummer[610] /usr/opt/temip/orbix/610/asp/6.1/bin/iordump "IOR:... "
38

Stringified IOR is: ([string/coded data] length: 400 / 198 bytes)
...
TypeId value: 'IDL:omg.org/CosNaming/NamingContext:1.0.'
...
Port: 3080
...
Object key data: ':>.31.IT_NamingContextExt..........'
(looks like an Orbix ART Direct Persistent key)
The client can contact directly the itnaming without using the itlocator.
However, by administrative actions, it is possible to provide the IOR of the itnaming (with the
fixed port inside) to the itlocator.
These actions are now done in the temip_orbix_setup_610 transparently for the user.
Thus, the client can continue contacting the itlocator that provides the fixed IIOP port
allocated for the itnaming.
Thanks to these changes, the itnaming uses all TCP ports in the range defined with
policies:iiop:server_address_mode_policy:port_range value.
6.2.1.2 Protect your TeMIP director with a firewall
Install and setup a firewall that protects your TeMIP Director. Then, open some ports in order
the TeMIP Client can communicate with the TAL Orbix Server FM:
Example with ipchains, firewall provided with linux (explanations below)
Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
temip1 all ------ anywhere ibiza.lab3g.vbe n/a
Chain output (policy ACCEPT):
Chain temip1 (1 references):
target prot opt source destination
ports
ACCEPT tcp ------ anywhere anywhere any
-> 3075
ACCEPT tcp ------ anywhere anywhere any
-> 3080
ACCEPT tcp ------ anywhere anywhere any
-> 6000:6030
ACCEPT tcp !y---- anywhere anywhere
50000:50300 -> any
ACCEPT icmp ------ anywhere anywhere any
-> any
ACCEPT tcp ------ anywhere anywhere any
-> telnet
REJECT all ----l- anywhere anywhere n/a
Accept connections on port 3075 (port for itlocator)
target prot opt source destination
ports
ACCEPT tcp ------ anywhere anywhere
any -> 3075
Accept connections on port 3080 (port for itnaming)
39

target prot opt source destination
ports
ACCEPT tcp ------ anywhere anywhere
any -> 3080
Accept connections on the range of ports used by our Orbix servers (TAL Orbix Server FM)
defined in the orbix_temip.cfg
target prot opt source destination
ports
ACCEPT tcp ------ anywhere anywhere
any -> 6000:6030
Accept connections that have been initialized by our host.
It is needed because the TAL Orbix Server FM is also client of the TeMIPClient. So, it
initializes a TCP connection.
To be more secure, we can specify the range of ports that we want to contact on the remote
hosts. It can be done if we define also the range of port used by the TeMIPClient on the
TeMIPClient host.
target prot opt source destination
ports
ACCEPT tcp !y---- anywhere anywhere
50000:50300 -> any
6.2.1.3 The TeMIP Client is protected by a firewall
In that case only the TeMIP Client is protected. The same variable must be defined in the
Orbix configuration file used by the TeMIP Client.
In C:\Program Files\TeMIP Client V5.X for Windows\Orbix Run
Time\etc\domains\orbix_temip_client.cfg
Example: policies:iiop:server_address_mode_policy:port_range = "50000:50300";
Protect the TeMIPClient with a firewall and open some ports in order the TAL Orbix Server
FM can communicate with the TeMIPClient.
Important Note
Limitation: if the port_range value is defined on the TeMIP Client host, only one TeMIPClient
can run on this host.
6.3 Sign-on TeMIP Authentication Support
With TeMIP Client V5.1, you can choose single sign-on for the TeMIP authentication policy
(WINDOWS or WINDOWS then UNIX). In that case, a file will be used for authentication
and also to associate an Acloc security profile to the Windows user.
You have to edit the following file on the TeMIP PM Server platform:
/var/opt/temip/acloc/user_profiles/temip_acloc_tal_users
40

If this file does not exist yet, copy it from the template:
/usr/opt/temip/acloc/files/temip_acloc_tal_users
Add one line per user. Syntax and examples are present in the file itself.
User:Profile:Domain:Host
6.4 PR#21200 Increase the number of members of a
type definition
In the case, you need to increase the number of members of a type definition (Number of
Enumerated values for Probable Cause for instance), you may use the following Environment
Variable in the TeMIP Configuration file (/var/opt/temip/conf/.temip_config)
MCC_DICT_TYPE_MAX_MEMBER_ENTRIES=8192
The default value is 4096
Warning: Increasing the number of members may cause huge performance problem.
Try to minimize your Dictionary instead of increasing this value.
6.5 Operations concerning Enhancements/Known
problems existing before the current
Maintenance Release V500 Level 1 Patch 4
The following enhancements have already been announced and documented before the current
Maintenance Release. If you have already taken into account these enhancements, do not
apply the following operations.
6.5.1 Upgrade from Tru64 V5.1A to Tru64 V5.1B causes problem at
TeMIP SystemMate server start (JAVA version)
The TeMIP SystemMate tool needs the JAVA122 as default Java version. If you upgrade your
system to Tru64 V5.1, the JAVA131 becomes the default version. To allow TeMIP
SystemMate working properly, you may process the following commands:
victoria > /usr/opt/java131/bin/unset_java_default.sh
Java 1.3.1 will be set as a non-default version.
Do you wish to continue (y/n)? y
Java 1.3.1 is no longer the default version.
victoria > /usr/opt/java122/bin/set_java_default.sh
This script will set the default java version to Java 1.2.2
provided that there is no system default java currently in place.
41

Do you wish to continue (y/n)? y
Java 1.2.2 is now the default for the system.
Java 1.3.1 is needed to run Orbix configuration setup. If you have set the default java version
to Java 1.2.2, you need to define JAVA_HOME variable to /usr/opt/java131 before running
the script temip_setup -> tal_orbix_server setup.
6.5.2 Interoperability Tru64 V5.0 versus HP V5.0.
Interoperability features allow to build heterogeneous TeMIP solutions with both V5 based
TeMIP systems (Tru64) and new V5 based TeMIP systems (HP-UX). Consequently, it is now
possible to extend a V5 Old TeMIP distributed solution with a V5New Director running on
HP-UX platform.
Therefore, this feature concerning the interoperability capability between Tru64 and HP
platform, provided by an Extraordinary Patch (TFRPATCH13843V500L01P02) upon
TFRV500L1P2 has been included into the TFRV500L1P3 maintenance release.
Note:
If you plan to interoperate the Tru64 TFRV500L01P04 with HP-UX V5 version, after
installation of TFRV500L01P04, you must manually copy the files:
/usr/opt/temip/conf/GetFilesFromTeMIP_V4.0.distfile
/usr/opt/temip/conf/PutFilesToTeMIP_V4.0.distfile
/usr/opt/temip/conf/GetFilesFromTeMIP_V5.0.distfile
/usr/opt/temip/conf/PutFilesToTeMIP_V5.0.distfile
under /var/opt/temip/conf directory.
6.5.3 Cascading Corrective filter and callback facility
6.5.3.1 Product Goals
The enhanced TeMIP V5.0 Low Level Event Filtering capability, running on Tru64 UNIX V5
addresses the need for the following new features:
Cascading corrective filter sub-category
The solution enhances the TeMIP Event Filtering and Correlation software library to provide
an optional alternative cascading policy on a filter basis.
Multiple corrective filter action routine libraries
The solution provides means to load several number of customized user libraries. Each access
module can load a defined set of customized user libraries.
Callback facility in current Low Level Event Filter logic
The solution allows performing arbitrary operations for each discarded event, for example to
record the event.
42

The TeMIP Event Filtering and Correlation software library and the TeMIP Event Filter
Function Module are modified to provide the enhancements listed above. All enhancements
are backward compatible with current implementation.
6.5.3.2 Enhanced Event Filtering Process
The following diagram presents a general view of the enhancements including cascading
corrective filters and callbacks for discarded events.
43

Figure 1 Global View of Low-Level Filter Processing
Alarm
Handling
Event
Logging
TeMIP
OC Event
Filter
Log Event
Filter
High Level Event Filtering
no match
no match
Intelligent Filter
match
Tap Filter
Runtine
error
Non-cascading
Corrective Filter
Filtered Events
match
no match
Intelligent Filter
Processing
match - correction applied
Correction and discriminator construct
are applied to the modified events.
"Intelligent Filter" means a
Transient, Threshold or Heap
Filter.
Discarded Event
Callbacks
Nothing
forwarded
no match(s) match(s) – correction(s) applied
Corrections and discriminator constructs
are applied to the modified events.
Cascading Corrective
Filter(s)
Runtim
e
Incoming events from AM
Low Level Event Filtering
Network Element
6.5.3.3 Configuration
The enhancements to the Low Level Event Filtering have introduced some new
configurations.
44

Environment Variables
Configuration Files
The following new environment variables impact the behavior of the Low Level Event
Filtering:
TEMIP_EF_CALLBACK_ON_FIRST_EVENT
This variable can be set to TRUE or FALSE.
When set to TRUE, the first event matching an intelligent filter (threshold, transient or heap) is
submitted to the discarded events callbacks when discarded, i.e. Forward Alarm And
Clearance or Forward First attributes are set to False.
When set to FALSE, the first event matching an intelligent filter (threshold, transient or heap)
is not submitted to the discarded events callbacks.
The default is FALSE.
TEMIP_EFUL_DIR
This variable defines the location of configuration files.
The default is /var/opt/temip/conf/eful.
TEMIP_EF_USER_LIB
This variable defines the location of the default user library.
The default is /usr/opt/temip/lib/libtemip_ef_user_library.so.
Optional configuration files are added for each module using low-level event filtering. A
configuration lists the custom user libraries that the module should load. Custom user libraries
provide action routines for corrective filters and callbacks for discarded events. This solution
provides means to load several customized user libraries. Each access module can load a
defined set of customized user libraries.
The file is /var/opt/temip/conf/eful/access_module where access_module is the name of the
access module. If this file does not exist, the module loads the default file
/var/opt/temip/conf/eful/all. If the default file does not exist, the default customized user
library /usr/opt/temip/lib/libtemip_ef_user_library.so (or the library specified by the
environment variable TEMIP_EF_USER_LIB) is loaded. The location
/var/opt/temip/conf/eful can be overridden using the environment variable
TEMIP_EFUL_DIR.
Note that the default customized user library libtemip_ef_user_library.so is still loaded if
required, even if not specified in the configuration.
• Syntax
The syntax for this file is as follows:
file ::= { line }
line ::= library | include filename
where
{ x } means 0 to n occurrences of x,
x | y means x or y,
library is the full name of a library (e.g.
/usr/opt/temip/lib/libef.so),
filename is the name of another file listing more libraries. The
filename is not the full name of the file, the location of the file is
as described below.
45

For example:
include all
/opt/lib/libamap.so
/usr/opt/temip/lib/libalog.so
• Examples
The following examples present different cases of configuration.
1. No Configuration File
If the default configuration file all (/var/opt/temip/eful/all) and the access
module configuration file access_module
(/var/opt/temip/conf/eful/access_module) are not present, the default
customized user library libtemip_ef_user_library.so is loaded when the first corrective filter is
executed or when the first event is discarded. This configuration is interesting for directors
including modules that do not contain corrective filters. It prevents them from loading useless
libraries.
2. Only the Default Configuration File
When only the default configuration file all (/var/opt/temip/conf/eful/all) is
present, all modules supporting low level event filtering read this file at initialization and load
the specified libraries. The default customized user library
libtemip_ef_user_library.so is loaded when the first corrective filter is executed or
when the first event is discarded.
3. An Access Module Configuration File
If an access module has a configuration file, the file is read at initialization and the specified
libraries are loaded. The default customized user library
libtemip_ef_user_library.so is loaded when the first corrective filter is executed or
when the first event is discarded.
4. An Empty Access Module Configuration File
If an access module has an empty configuration file, the file is read at initialization and no
libraries are loaded. The default customized user library
libtemip_ef_user_library.so is loaded when the first corrective filter is executed or
when the first event is discarded. This configuration can be used for modules that do not
contain corrective filters. It prevents them from loading useless libraries.
5. A Common Configuration File
A configuration file can include another one. For example:
include common
The file common lists some common libraries. For example:
/usr/opt/temip/lib/libcommon1.so
/usr/opt/temip/lib/libcommon2.so
46

Then an access module can be configured such as it loads the common libraries, plus some
specific ones:
include common
/usr/opt/temip/lib/libdev1.so
In this case, the libraries log, map and dev1 are loaded at initialization, and the default
customized user library libtemip_ef_user_library.so is loaded when the first
corrective filter is executed or when the first event is discarded.
6. Specifying a Different Default Customized User Library
The default customized user library libtemip_ef_user_library.so is by default
found in /usr/opt/temip/lib. It can be overridden using the environment variable
TEMIP_EF_USER_LIB. Its location can also be overridden specifying the library in the
TeMIP configuration file:
/opt/lib/libtemip_ef_user_library.so
In this case the specified library is loaded at initialization, and the default library
/usr/opt/temip/lib/libtemip_ef_user_library.so (or the one specified by
TEMIP_EF_USER_LIB) is not loaded.
Custom Libraries
A custom library can contain action routines for corrective filters, or callbacks for discarded
events.
• Callbacks
The action routines are defined as per the previous versions of the low-level event filtering.
Examples are provided in temip_ef_user_library.cxx.
47

Callbacks are defined as follows:
MCC_T_CVR proc ( FEvent& event, const MEntitySpec& filter )
{
// ….
return MCC_S_NORMAL;
}
The event is passed as a non-constant (modifiable) variable for practical reasons (access to all
methods of the class FEvent). It should however not be modified. Modification to the event
will have no effects other than being passed on to the next callbacks (same object passed to all
callbacks).
Each customized user library defines (optionally) a public function called initialize().It
is mandatory to define the initialize() function in order to use discarding features. The
initialize() function is responsible for advertising any discarded event callback using
the discarded_events_add_callback() function:
void initialize()
{
discarded_events_add_callback(“mylib”,my_callback_1);
discarded_events_add_callback(“mylib”,my_callback_2);
…
}
The callbacks and the initialization function can be defined in the same library than the
corrective filter action routines or in a different library.
Example
Below is an example of custom library with action routines and callbacks:
#include
extern "C"
{
/* action routine */
MCC_T_CVR SetAdditionalText(
FEvent& event,
const MSetOf &values)
{
event.SetAdditionalText(values[1]);
return MCC_S_NORMAL ;
}
/* callback */
MCC_T_CVR log_event(FEvent &event,const MEntitySpec &filter)
{
MTraceStream trace(0x1);
trace

}
/* initialization*/
void initialize()
{
discarded_event_add_callback("log",log_event);
}
}
• Action Routines
Every customized user library defines one or more action routines for the corrective filters.
The action attribute of a corrective filter defines the action routine to execute. With multiple
customized user libraries, the name of the library holding the action routine must also be
defined. This is done by setting the value of the action attribute to library:action where
library is the name of the library (prefix lib and suffix .so are removed)and action is the name
of the action routine:
amap:AMapAction
In this example, the library used is libamap.so and the action called is AMapAction.
If the library is not specified, the routine is found in the default customized user library.
Example specifying a Non-Standard Action Routine
The following FCL command creates a corrective filter using an action routine from the
library libamap.so:
create mcc 0 corrective_filter maloja -
Input Discriminator Construct = { -
( LogicalOp = And ), -
( LogicalOp = Item, -
Item = ( FType = equality, -
relationAssertion = -
( ( (
OSI_SYSTEM, LOG, ALARM_RECORD ) , -
Perceived
Severity ) , Minor ) ) ), -
( LogicalOp = End ) }, -
Target = "alarm_generator_am", -
Action = "amap:action", -
Parameters = { "ApplicationSubsystemFailure" }
Corrective Filters
Corrective filters are split into two categories:
• Cascading corrective filters,
• Non-cascading corrective filters.
49

More then one cascading corrective filter can be applied to an event, while only one noncascading
corrective filter can apply. Cascading corrective filters are executed first and than
the non-cascading corrective filters.
• Cascading Corrective Filters
The optional CASCADE attribute of the CORRECTIVE_FILTER class determines the
cascading policy for the filter. By default this attribute value is FALSE. This reflects the
current behavior of corrective filters. If the value of the CASCADE attribute is TRUE, the
next appropriate filter is executed. This allows the definition of filters using the standard
action routines, and have them cascading to modify multiple attributes of the event. Cascading
filters are executed first and then the non-cascading filters (in each subset the evaluation order
remains unchanged: lexicographic order). The cascading policy of a filter is defined at creation
and cannot be modified.
• Example
Creating a Cascading Corrective Filter
The following FCL command creates a corrective filter with the cascade attribute set to true:
create mcc 0 corrective_filter maloja -
Input Discriminator Construct = { -
( LogicalOp = And ), -
( LogicalOp = Item, -
Item = ( FType = equality, -
relationAssertion = -
( ( (
OSI_SYSTEM, LOG, ALARM_RECORD ) , -
Perceived
Severity ) , Minor ) ) ), -
( LogicalOp = End ) }, -
Target = "alarm_generator_am", -
Action = "SetProbableCause", -
Parameters = { "ApplicationSubsystemFailure" }, -
Cascade = True
6.5.4 TeMIP dictionary comparison enhancement
This feature has been implemented to minimize dictionary comparison time.
6.5.4.1 Generalities
An important performance enhancement has been done on the temip_dict_compare tool that
compares two TeMIP dictionaries.
The mcc_msl tool has been modified in order to add time information internally in the
dictionary, for each dictionary update. This update is fully transparent for the user.
50

Each dictionary branch is now time stamped and the new algorithm for comparison can
operate.
It is possible to get benefit of this enhancement for TeMIP directors using an "old" dictionary,
by migrating a non-time stamped dictionary through the new “–u” mcc_msl option.
In a TeMIP platform containing multiple directors, the good way of migrating and propagating
a dictionary is:
On a TFRV500L01P04 director 1:
• Do "/usr/opt/temip/bin/mcc_msl -u" to migrate an “old” dictionary with the new time
stamped dictionary format.
• Do “/usr/opt/temip/bin/mcc_ptb” to re-build the parse table.
• Reload Dictionary using: “manage reloaddictionary mcc 0”
• Propagate the new dictionary to all the other TeMIP directors via the
/usr/opt/temip/bin/temip_synchro_data tool.
After this operation, all the directors will have an identical time stamped dictionary.
6.5.4.2 Interoperability
A TFRV500L01P04 TeMIP director with a “new” dictionary can operate with a
TFRV500L01P02 TeMIP director with an “old” dictionary.
It is also possible to compare both dictionaries but the performance enhancement of the
dictionary comparison cannot operate.
A “new” dictionary” can be propagated to a TFRV500L01P02 director and used by it. There
will be no real time interoperability issue but the comparison will be possible.
Notes:
• It is impossible to modify a “new” dictionary (via mcc_msl) from a TFRV500L01P02
director due to the fact that the TFRV500L01P02 mcc_msl tool does not support the new
dictionary format.
• If a TeMIP platform contains both TFRV500L01P02 directors and TFRV500L01P04
directors and if updates of the dictionary from the V500L01P02 director are mandatory
on a “new” dictionary, a TFRV500L01P02 Epatch will be necessary to provide the
mcc_msl supporting the new dictionary format. This Epatch could also provide the new
enhanced temip_dict_cmp tool.
The workaround of this issue is to update the dictionary from the TFRV500L01P04
director and propagate it to all the other directors.
6.5.5 Add Environment variable for Assign Target in NOTIF_FM
(PR#15382)
51

The targeting feature is offered to the customer in order to re-affect a new target entity and
severity.
The directive ASSIGN enables defining a re-targeting for the specified Managed Object.
Internally, each client application that performs a call NOTIFY will get event one per one. For
each of them the re-targeting check is applied. This means that an access to the Notification
FM MIR is done systematically to know if there is a re-targeting to do on the entity or not.
This feature was driven by a environment variable
MCC_NOTIF_DISABLE_RUNTIME_TARGETTING.
The main problem was that the default was to make the re-targeting check whereas few
customer/application use it.
Since the TFRV500L1P3 the environment variable has been changed. It is named
MCC_NOTIF_ENABLE_RUNTIME_TARGETTING and the customer has to define it
explicitly if he wants to use the re-targeting feature. By default no re-targeting check is done
which improves clearly the notification performance.
6.5.6 Mask the Current Problem List during show all attributes
(PR#16687)
TeMIP Iconic Map and FCL_PM have been updated to avoid processing call on the following partitions
only in the case of a "Show ... all attributes":
MCC_K_PRT_RESYNCHRONIZATION: /* 24 */
MCC_K_PRT_PROBLEMLISTS: /* 41 */
MCC_K_PRT_CURRENTALARMS: /* 88 */
This impacts FCL_PM and the button "Show all attributes" of the Iconic Map PM.
This ability to hide such partitions is enabled setting the following environment variable to "ON":
TEMIP_PROBLEM_LIST_PARTITION_HIDE
6.5.7 Synonym replica databases not updated (de-synchronized)
(PR#16452)
This functionality is related to PR#16452.
Synonym replica database is not updated in some cases.
When the master synonym database is unavailable (network failures, database shutdown,...),
Oracle performs 16 attempts before considering the Replication job status as broken.
In this case, the replica database will be never updated once the master synonym database is
restarted.
From an Oracle point of view, this is a normal behavior and the way to correct the problem
implies an Oracle administration operation.
This operation consists in executing the following sql commands on the synonym replica
database:
52

_hostname[oracle] sqlplus /nolog
SQL> connect temipsyno/temipsyno;
Connected.
SQL> begin
2 dbms_refresh.refresh('"TEMIPSYNO"."TEMIP_SYNO_ASCII"');
3 dbms_refresh.refresh('"TEMIPSYNO"."TEMIP_SYNO_IP"');
4 dbms_refresh.refresh('"TEMIPSYNO"."TEMIP_SYNO_OSIDN"');
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> alter materialized view temipsyno.temip_syno_ascii
refresh fast
start with SYSDATE
next SYSDATE + 1/4320;
Materialized view altered.
SQL> alter materialized view temipsyno.temip_syno_ip
refresh fast
start with SYSDATE
next SYSDATE + 1/4320;
Materialized view altered.
SQL> alter materialized view temipsyno.temip_syno_OSIDN
refresh fast
start with SYSDATE
next SYSDATE + 1/4320;
Materialized view altered.
SQL> commit;
Commit complete.
SQL> exit;
53