3BUR002051D4 - en AdvaCommand 1.8 2 P1 AdvaBuild 2.9 1 Release Notes

Advant OCS AdvaCommand®1.
8/2 P1 /
with MOD 300™ Software AdvaBuild® 2.9/1
Release Notes
3BUR 002 051D4

Use of DANGER, WARNING, CAUTION, and NOTE
This publication includes, DANGER, WARNING, CAUTION, and NOTE information where appropriate to point out safety
related or other important information.
DANGER Hazards which could result in severe personal injury or death
WARNING Hazards which could result in personal injury
CAUTION Hazards which could result in equipment or property damage
NOTE Alerts user to pertinent facts and conditions
Although DANGER and WARNING hazards are related to personal injury, and CAUTION hazards are associated with
equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational
conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all
DANGER, WARNING, and CAUTION notices.
TRADEMARKS
Advant and AdvaBuild are registered trademarks of ABB Inc
MOD 300 is a trademark of ABB Inc
All other brand or product names are trademarks or registered trademarks or their respective companies or organizations.
NOTICE
The information in this document is subject to change without notice and should not be construed as a commitment by ABB Inc
ABB Inc assumes no responsibility for any errors that may appear in this document.
In no event shall ABB Inc be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising
from the use of this document, nor shall ABB Inc be liable for incidental or consequential damages arising from use of any
software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without the written permission of ABB Inc, and the contents
thereof must not be imparted to a third party nor be used for any unauthorized purpose.
The software described in this document is furnished under a license and may be used, copied, or disclosed only in accordance
with the terms of such license.
Copyright © 2003 ABB Inc

3BSE001264/C
3BUR 002 051D4

AdvaCommand®1.8/2 P1 / AdvaBuild® 2.9/1 Release Notes
Table of Contents
TABLE OF CONTENTS
Chapter 1 - Introduction
1.1 Executive Summary .....................................................................................................1
1.2 Version Designation.....................................................................................................1
1.3 Compatibility ...............................................................................................................2
1.4 Software/Firmware Requirements ...............................................................................2
1.4.1 Firmware for DCN Interface Module .........................................................2
1.4.2 Firmware for Advant Controllers AC 460 ..................................................3
1.5 Related Documentation................................................................................................4
Chapter 2 - Functionality
2.1 Revised Functions........................................................................................................1
2.2 Fixed Problems ............................................................................................................1
2.2.1 AdvaCommand ABB-AC-OSs Fixes..........................................................2
2.2.2 ABB-MODRTA.LOAD Fileset Fixes.........................................................4
2.2.3 AdvaBuild ABB-PESU_291001 Fileset Fixes ...........................................8
2.2.4 ABB-MODRTA.BOOT Fileset Fixes .......................................................10
2.2.5 UXBase Fileset Fixes................................................................................10
2.2.6 ABB-HISTORY Fixes ..............................................................................11
2.3 Known Problems........................................................................................................17
2.3.1 General......................................................................................................17
2.3.2 Advant HSI ...............................................................................................17
2.3.3 AdvaBuild .................................................................................................19
2.3.4 Advant System Software...........................................................................19
Chapter 3 - Installation
3.1 Introduction..................................................................................................................1
3.2 Backup and Restore .....................................................................................................2
3.3 Installation ...................................................................................................................2
3.3.1 Starting Instructions....................................................................................2
3.3.1.1 Adding /SD_CDROM with sam ..........................................2
3.3.1.2 Preparing the CD-ROM or DVD-ROM for Installation.......3
3.3.1.3 Preparing for a Remote Upgrade .........................................3
3.3.2 Instructions for Station(s) to be Updated using CD-ROM .........................3
3.3.3 Finishing Instructions .................................................................................5
3.3.4 Post Installation Work.................................................................................5
3.3.4.1 Update Customer System Variables File..............................5
3.3.4.2 onlineUpgrade File Diagnostic and Removal ......................5
3.3.4.3 Log File Update and Review................................................6
3BUR 002 051D4 1

Table of Contents
3.3.4.4 Loading Software to MOD 300 Subsystems........................7
3BUR 002 051D4 2

Section 1.1 Executive Summary
Chapter 1 Introduction
1.1 Executive Summary

This release provides corrections for AdvaCommand 1.8/1, AdvaBuild 2.9/0 P2, History v2.4/0
P9 and MOD 300 14.5/1 systems. The changes described in this book support the release of
AdvaCommand 1.8/2 P1, including the AdvaBuild 2.9/1 and History 2.4/0 P13 options for an
Advant Station® as well as MOD 300 system software 14.6/3.
Chapter 2, Functionality, includes a summary of new features and fixed problems since the
release of AdvaCommand 1.8/1 / AdvaBuild 2.9/0 P2. Refer to the AdvaCommand 1.8/1 /
AdvaBuild 2.9/0 P2 Release Notes for a summary of new features and fixed problems
documented in that release.
You may be getting the AdvaCommand 1.8/2 P1 release CD-ROM for a new system install or an
upgrade. For a complete install, use the installation instructions found in the Advant Station 500
Series with AdvaCommand 1.8/2 P1 / AdvaBuild 2.9/1 User’s Guide. The complete install is
required for all installations prior to the AdvaCommand 1.8/1 release. Use the current release in
place of any reference to the installation CD-ROM.
Chapter 3, Installation, provides software installation instructions that add the upgrade only (for
AdvaCommand 1.8/1 / AdvaBuild 2.9/0 P2 or for systems already at AdvaCommand 1.8/2 /
AdvaBuild 2.9/1) and for systems with controllers that can be online upgraded.
You can update one or more stations from a single Advant Station. The single station (cannot be
History) must be on your TCP/IP network and have a CD-ROM drive.
1.2 Version Designation

This software is for AdvaCommand 1.8/2 P1 with AdvaBuild 2.9/1 and History 2.4/0 P13
options (during installation you may see History referred to as AdvaInform). It is provided on
CD-ROM as:
Article Number CD-ROM Description
3BUR 002 145R3 AdvaCommand 1.8/2 P1, AdvaBuild 2.9/1,
History 2.4/0 P13
If the following base release functionality is installed, then the 3BUR 002 145R3 CD can also
be used to perform an upgrade:
3BUR 002 145R2 AdvaCommand 1.8/2, AdvaBuild 2.9/1,
History 2.4/0 P13
3BUR 002 145R1 AdvaCommand 1.8/1, AdvaBuild 2.9/0 P2,
History 2.4/0 P9
3BUR 002 051D4 1-1

Section 1.3 Compatibility
1.3 Compatibility
AdvaCommand 1.8/2 P1 and AdvaBuild 2.9/1 software are compatible with each other as well
as with:
• Enterprise Historian Version 2.2 for HP-UX
• Enterprise Historian Version 3.2/1 for Windows
• History 2.4 P13
• Statistical Process Control (SPC) 2.4
• Production Data Log (PDL) 2.4
• Reports 2.3/0 P1
• Based on MOD 300 System Version 14.6/3 software; Remote DP or Batch Nodes must be
at 14.6/3
• MOD 300 System Version 14.6/3 software
• PC Templet Generator 6072SE14108B Source Revision 118 (PC Templet Generator is
only used with MOD 300 System Version 14.5/0 software. It is no longer supported for
AdvaBuild 2.9/0 or later. The same functionality is provided in AdvaBuild 3.0 for NT or
later.)
1.4 Software/Firmware Requirements
1.4.1 Firmware for DCN Interface Module

The following PROMs support 1 second and 100 millisecond time synchronization for the
Process Station DCN Interface Module (3BUR980009, CS512). The new 100 millisecond
PROMs also contain the AC-410 boot code which will now recognize both the DCN and
eDCN configurations.
Table 1-1. CS512 Process Station DCN Interface Module PROM Identification
Time
Article Number Bitsum Location
Synch
4911014-SNM $9FC7 D21 1 sec.
4911014-SVV $8FE8 D21 100 msec
NOTE
1 second PROMs (SNM) are listed for information purposes only. They are no
longer available; however, they can still be used on existing systems. The new
PROMs (SVV) will work with the old 1 second time synchronization PROMs.
3BUR 002 051D4 1-2

Section 1.4.2 Firmware for Advant Controllers AC 460
The following PROMs support 100 msec time synchronization for the Work Station DCN
Interface Module (3BUR980008, CS502):
Table 1-2. CS502 Work Station DCN Interface Module PROM Identification
Time
Article Number Bitsum Location
Synch
4911014-SDM $1F45 D1, D2 1 sec.
4911014-SUD $C591 D1, D2 100 msec
NOTE
1 second PROMs (SDM) are listed for information purposes only. They are no
longer available; however, they can still be used on existing systems. The new
PROMs (SUD) will work with the old 1 second time synchronization PROMs.
System time between nodes can be synchronized to 100ms of the Master

Timekeeper if the 100 ms PROMS are installed and the software is at the
following levels. Otherwise, the node will operate using 1 second time
synchronization.
• AdvaCommand 1.8/2 P1, AdvaBuild 2.9/1, History 2.4/0 P13 for an Advant
Station
• Enterprise Historian 2.2
1.4.2 Firmware for Advant Controllers AC 460

AdvaBuild 2.9/1 software requires:
• PM510 CPU Board 3BSE000270R1 Rev K through S; or PM510V08 3BSE008373R1
Rev A through E; or PM510V16 3BSE008358R1 Rev A through E.
• SC510 Carrier Board 3BSE003832 Rev L through V
• SC540 Carrier Board 3BSE006096 Rev G, H, J or K
The following new PROMs contain the boot code, which will now recognize both the DCN and
eDCN configurations:
Table 1-3. SC540 Carrier Board PROM Identification
Corresponding FMSFile
Article Number PROM ID Bitsum Location
[50.PU520]CSPU520.PK
4911014-SWL P1 (Low Middle) $0FBF D68 15-May-2001
4911014-SWM P0 (Low) $ACCA D69
4911014-SWN P2 (Upper Middle) $8095 D70
4911014-SWP P3 (Upper) $5CD4 D71
3BUR 002 051D4 1-3

Section 1.5 Related Documentation
1.5 Related Documentation

Table 1-4 identifies what documentation to consult, for detailed information about Advant
Stations.
Table 1-4. Related Documentation - Advant Station
Title Description
AdvaCommand 1.8/1 / AdvaBuild 2.9/0 P2 Describes AdvaCommand revision 1.8/1, including the AdvaBuild
Release Notes 2.9/0 P2 and History 2.4/0 options for an Advant Station®. It
includes a summary of new features, fixed problems since the
AdvaCommand 1.8/0, AdvaBuild 2.9/0 release, and known
problems and workarounds for this release.
AdvaCommand 1.8/0 / AdvaBuild 2.9/0 Describes AdvaCommand revision 1.8/0, including the AdvaBuild
Release Notes 2.9/0 and History 2.4/0 options for an Advant Station®. It includes
a summary of new features, fixed problems since previous
releases, and known problems and workarounds for this release.
Advant Station 500 Series with AdvaCommand Provides a general functional overview of the Operator
1.8/2 P1 / AdvaBuild 2.9/1 User’s Guide Station/Engineering Station and instructions for station-level
procedures such as start-up, shutdown, connecting peripherals,
administration functions such as backup/restore, and so on. It
also provides installation instructions for initial installation of the
AdvaCommand 1.8/2 P1 and AdvaBuild 2.9/1 software.
3BUR 002 051D4 1-4

Section 2.1 Revised Functions
Chapter 2 Functionality
2.1 Revised Functions

New or revised functions introduced with AdvaCommand 1.8/2 P1 / AdvaBuild 2.9/1 are:
• HP-UX DVD hardware support included
No new or revised functions are introduced with AdvaCommand 1.8/2 / AdvaBuild 2.9/1.
• Supports MOD 300 14.6/3 System Software
2.2 Fixed Problems

The list of fixed problems described in this section include changes since the release of
AdvaCommand 1.8/1, AdvaBuild 2.9/0 P2, History v2.4/0 P9 and MOD 300 14.5/1 systems.
Only those fixes that support the release of the following product are included:
• AdvaCommand 1.8/2 P1
• AdvaBuild 2.9/1
• History v2.4/0 P13
• MOD 300 14.6/3 System Software
• HPUX base (DXPHRUN_26)
Some of the known problems that were listed in the AdvaCommand 1.8/2 / AdvaBuild 2.9/1
Release Notes have been removed and documented for the way they work. The documented
fixes are:
• Advant HSI #48 - Add note to AdvaCommand Basic Functions book Section 4.4.2.1 Trend
Graphs in the paragraphs for Modifying Trend Traces that custom GROUPTREND Top
and Bottom Of Range settings are not saved.
• Advant HSI #49 - Add note to AdvaCommand Basic Functions book Section 1.8.2.3 User
Authority in the NOTES:
– After installing a graphic with a tag that does not exist in the environment, log off and
then log back on to correct the control authority. This will cause authority to be re
initialized.
• Advant HSI #63 - Fixed Advant Station 500 Series with AdvaCommand 1.8/2 P1 /
AdvaBuild 2.9/1 User’s Guide that, for the SystemVariable numberOfUniquePasswords,
“If a Central Administration server is used, the variable set on the primary and backup is
used.” instead of the local variable.
3BUR 002 051D4 2-1

Section 2.2.1 AdvaCommand ABB-AC-OSs Fixes
2.2.1 AdvaCommand ABB-AC-OSs Fixes

Table 2-1 and Table 2-2 list the fixes provided in the ABB-AC-OSs fileset of the CD-ROM for
upgrading to AdvaCommand 1.8/2 P1.
Table 2-1. ABB-AC-OSs Fixes Introduced with AdvaCommand 1.8/2 P1
ID No. Problem Description

50 Ignite install now works when installing a B2600 machine as the Ignite client.
69 RDP's, LoopFCM did not close on Logon using ASE. If a user was logged on and another user
logged in, the RDP's did not close. If a logoff was done, it worked fine.
137 Output ramping begins at the current output value instead of at zero.
Table 2-2. ABB-AC-OSs Fixes Introduced with AdvaCommand 1.8/2

2 TCL Recipe Detail - updates to string variables are no longer in wrong position.
When the value for a string on Recipe Detail was changed, it was not displayed for the correct Item
Id when Real and Integer item types were also present within the recipe. However, when the
screen was refreshed, the value appeared to be correctly associated with the intended Item Id.
3 S800 LAN Display - this display no longer crashes when more than 40 redundant stations are
configured for the controller. Also, added an error dialog to state that more than 40 redundant
stations are configured.
4 Environment, Area and Group Alarm Displays - Current value did not always update after an alarm
was acknowledged. Acknowledgement also displayed the initial alarm value. Now, the current
value is retained and, if the value changes, it is updated on the screen.
6 TCL Recipe Detail - Dialog no longer sends NULL(0) with return in empty field.
12 XTERM - PC Reflection 8.0 allows changing of cursor colors. Colors that exist within Unix, were
not properly translating into PC colors. The available cursor colors displayed within osXConfig for a
PC client were changed to colors that Reflection 8.0 can properly translate.
14 Basic Functions - PS Status subsystem menu no longer has problems on 2 Head machines.
PSStatus submenus were being erased on two headed machines, when both heads were
displaying the same PSStatus and the display was changed on one of the heads. The submenu
under the Display Menu for the PSStatus of the displaying head was empty.
15 Basic Functions - The size of the PID dialog has been reduced. The PID dialog was increased in
size to allow room for ramp buttons. This caused the dialog to overlap important information on the
display. The dialog was reduced to it's normal size.
16 TLL Displays - Segment Display dialogs for loops now come up correctly. Loop name and value
are no longer 'cut-off'.
3BUR 002 051D4 2-2

Section 2.2.1 AdvaCommand ABB-AC-OSs Fixes
Table 2-2. ABB-AC-OSs Fixes Introduced with AdvaCommand 1.8/2 (Continued)

19 TLL Displays - Segment display was causing controller overloads when an Open All request or
when the display was closed on very large Ladder configurations. Configurable delay parameters
to slow down the open and close were added to the customerSystemVariable file.
The variable UIS.SystemVariable.segmentDisplayOpenSegmentDelay has a default value of 0
(seconds). The variable UIS.SystemVariable.segmentDisplayClosedDisplayDelay has a default
value of 0 (seconds).
23 AdvaCommand - Tags on graphics accessible by an Environment User will now be with control
authority (rather than read only) even if the tag is not included in the environment. This was the
previous method of operation. The logged on ENVIRONMENT user can control tags (including
Unit Relative tags) on graphics even if the tags do not appear elsewhere in the Environment.
27 TCL builder no longer causing a shutdown of AdvaCommand.
When the OS server and clients were (re)started after a TCL builder had been started (seen on an
OS/ES or OS/Batch) and the TCL builder was then exited, the OS could shutdown within a few
minutes of the exit.
37 Alarms - It was possible to acknowledge alarms with no users logged on when using ASE.
40 After upgrading OS station from OS 1.7/2 to OS 1.8/1 it was noticed that the TLL GETDB dialogue
gave the wrong tag information and did not show the resulting value. Fixed in this release.
43 AdvaCommand - All open user dialogs are now closed when a user logs off.
Auto logoff due to ASE timeout was leaving RDP displays, Loopfcm displays, and control dialogs
open. ASE login timeout logs off the user but did not check for above. External applications (e.g.
Display Builder) are left open. This was done for ASE login timeout and normal user logoff.
45 PSAP keyboard was getting out of synch with the alarm tables.
The status indicators on both PSAPs and Overview displays were not updating after certain
activities. Because of the way the Overview display was handled, a linked list identifying new
overview displays was overwriting the lowest access ID in the list.
NOTE: AdvaCommand 1.8/1 added a refresh to the PSAP keyboard in the customer system
variable file called Uis.SystemVariable.refreshPsapKeyboardRate. This should never be set.
3BUR 002 051D4 2-3

Section 2.2.2 ABB-MODRTA.LOAD Fileset Fixes
2.2.2 ABB-MODRTA.LOAD Fileset Fixes

Table 2-3 lists the changes that have been included in the PU510load and PU511load Revision
14.6/3p00xx fixes on the CD-ROM for upgrading to AdvaCommand 1.8/2 P1.
Table 2-3. ABB-MODRTA.PU510LOAD and ABB-MODRTA.PU511LOAD Fileset Revision 14.6/3p00xx Fixes

(Hawkridge and PCI-RTAB Board Boot Files and DPL Tasks
Update AP ID No. Description

14.6/3 20 Initial DataDirect requests - In cases where accessName requests are
made to the hsLogMan process in MOD300 systems AND CCF does not
exist, the first request no longer takes 8 seconds/value seconds for the
initial data request.
14.6/3 59 Corrected memory deallocation diagnostics. These are no longer
generated for S800 I/O device loop configured for 1-in-0-out.
14.6/3 AC460 85 S800 I/O Analog inputs no longer cause demand scan when the input
Controller changes.
14.6/3 FMS 96 The MOD Installer was having problems with the FMS file rename function.
The file would be renamed successfully, but the function would return an
error code and then the installer could no longer perform successful
installs. Now, if you run the installer and the TCL compiler, all sequences
will successfully download.
14.6/3 MOD 300 69 Hardware failure caused corrupt messages to be sent. This PRC adds
Other software protection for this failure.
14.6/3 OMF 92 Writing to the LKP Result though OMF (such as when using the Unix Put
Value or Operate IT B FCM display to any attribute other than the
BP_TABLE attribute) placed random values into the Result.
14.6/3 PLC I/O 77 RS422 MVI cards no longer fails in a state that will not allow a restart even
when the card is reseated. It is no longer necessary to reboot the controller
to clear this MVI failure.
14.6/3 S800 I/O 90 S800 I/O Analog output now provides a bad data quality diagnostic. To
create the diagnostic, the Action On Error attribute must be configured in
the AOT FCM to something other than the default of Nothing.
14.6/2 MOD 300 71 Time synchronization revised so the reverse and non-reverse time
SSE synchronization work identically. This will eliminate the 7 minute update
delay in MTOS.
Time messages sent to host every 10 seconds if current RTA board is
master and RTS is off.
14.6/1 All 66 Added DEV_STATE_COMP to CCF_DEVICE_LOOP. Some clients
needed to be able to get dev_stat rather than result as a composite
attribute combined with dev_alrm, for device loops.
3BUR 002 051D4 2-4


(Hawkridge and PCI-RTAB Board Boot Files and DPL Tasks (Continued)

14.6/1 MOD 300 73 The PHL logs no longer experience a time shift that sometimes occurs
CCF during the time synchronization process.
14.6/0 All 14 TRIO objects (added lan_num to TRIO responses).
14.6/0 CF 25 AC460 controller (slot 6) Bus Errored (0 5.) when a carrier board (C2), with
two Profibus MIBs, was removed (from slot 8) and then reinserted (slot 7).
Bus error protection added to carrier card access statement.
14.6/0 CF 209 If a system had more than 2340 device descriptor states, then during a
node install, the device descriptor update task on the remote CDPs
reported dbms error 17 (duplicate record).
14.6/0 CF 230 If system documentation and the service display were up at the same time,
a lockup would occur in AdvaBuild.
14.6/0 CF 293 Export failed. PU511 only.
14.6/0 CF 322 Install failed after export. PU511 only.
14.6/0 DBMS 9 Bus error occurred when index=0 in dbaemsg.
14.6/0 DBMS 24 Dealloc errors occurred due to second subscription.
14.6/0 DBMS 25 Bus errored on early termination of Multibus MA Profibus objects. This
prevented inclusion of LAN in MODULE_DATA TRIO objects. Fixed
Communication Services access collisions in Channels attribute.
14.6/0 DG 21 Diagnostics not routed to local host. The functions that were written for
routing archive diagnostic to the NT side for support of the MOD
OPCAEServer did not support locally routed diagnostics. Needed because
node down messages are generated as local diagnostics.
14.6/0 DG 23 If a controller was rebooted while a TRIO Block display was left up and
getting data from it, a bus error in dggetrio would occur. This happened
because the pointer to TRIO data was accessed before it was filled in.
14.6/0 DG 52 Model B Controllers were getting error deallocating diagnostic. The
following diagnostic was seen in the B controllers:
ALL MESSAGES - TEXT
ERROR DEALLOCATING $001EC8C4: BAD HEADER
ALL MESSAGES - CODE
$17A15C0 L355 FIX=0004 (00) AP=1682 (001E,C8C4) W
14.6/0 LOOPFCM 213 Enable Rate Alarms item was always NO when using the loop definition
templet from loopfcm. Changing and saving the value to YES, going back
to the loop page and then back to the templet left the value at NO.
3BUR 002 051D4 2-5



14.6/0 OMF 10 When an EXTERNAL_FCM object is accessed, the value of its NAME
attribute is determined from the FCM_ID of the FCM to which it indirectly
refers. In the case of PID, AMC, and UCAL FCMs, this attribute did not
exist and the FCM field of the name was set to "???". This field is used on
the NT version of LoopFCM, and needed to be supported correctly.
14.6/0 OMF 16 OMF was unable to get CCF baserate from RLOCATE. This is required for
LoopFCM NT on the Loop level template. A more generic way to get data
from non-OMF objects is now allowed.
14.6/0 OMF 17 LoopFCM on NT needed to support the breakpoint set table; there was no
way to get this information from OMF.
14.6/0 OMF 18 Input, Output, Device FCMs needed to support chanpath for profibus, like
they do for S800.
14.6/0 OMF 000536 The state of a sequence on the Unit Detail display was not being updated
when it changed from LOADING to INACTIVE shortly after the display
started or refreshed.
Specifically, it was seen in two situations: (1) a sequence is loaded while
the display is running, so that the display automatically refreshes; (2) the
display is called up while the sequence is loading, within about four
seconds of the time it finishes loading. Other state changes besides
LOADING to INACTIVE were also missed, if they happened within the
same time period. Whether this will happen depends on precise timing of
the loading and the display's refresh; it was seen specifically with a unit on
a Model B controller with a large number of sequences. When this occurs,
the state will be correctly updated if either the display is called up again, or
some sequence in the unit is loaded or removed, causing the display to
refresh.
14.6/0 OMF 000872 Excess time to get a response if the subscription is large was eliminated.
When a client makes a call to the User API function bciDoRequest, which
calls the OMF function omfRefresh, it can take excessively long to get a
response if the subscription is large. For example, it took about 18 seconds
to refresh a subscription to 10 attributes in each of 500 objects. The excess
time is approximately proportional to the square of the number of
attributes, so the effect becomes increasingly severe for larger
subscriptions.
14.6/0 OMF 000933 When the TLL Sequencer Display was called up on Windows NT, the OMF
translator in the server could bus error while accessing PT_NAMES.
Similar bus errors could occur in other cases, including some operations
associated with Primary History Log, the new alarm synchronization (for
NT), and, possibly, the array of sequences in a unit.
3BUR 002 051D4 2-6



14.6/0 OMF 000955 A trend display viewing a Primary History Log would drift forward or
backward in time, so that after the display had been up some time, current
data was being displayed either several minutes earlier than the current
time, or several minutes after the current time. The data is correct; only the
time was wrong.
14.6/0 OMF 001022 When an application, such as History, subscribes to more than 100 nodes
in one request, or to more than 100 combinations of node and cycle time,
some nodes were unable to send their data for this subscription
periodically, although there was no other indication of a problem.
14.6/0 OMF 001062 An enhancement was needed to support an efficient set of S800 displays
for use on NT.
14.6/0 OMF 001130 An OMF message (e.g. between OS and History, or from History and
Primary History Logs on an Advant Controller) that exceeds 2K may be
corrupted, losing the last four bytes. This has caused the last of a group of
ten or more Primary Logs accessed by history at one time to return less
data than was requested, because the size of the request was corrupted.
14.6/0 OMF 001253 Due to an error in fixing a fix (which corrected the NAME attribute in the
FCM object), the name was put into the response message without
ensuring that there is room for a terminating null. As a result, if the
returned object name had a multiple of 4 characters, the client would get
the name with extra characters in it.
14.6/0 OMF 001254 The Unit Detail display on NT shows a list of loaded sequences in a unit.
This display did not recognize when one of two TCL servers lost
communication (displayed an empty unit). As a result, it would not allow
the other server, which was still connected, to take over.
14.6/0 OMF 001344 The TLL Sequencer display on NT did not update if a point was deleted
from a step (the point still appeared to be there). If the display was called
up again, or if another change caused it to refresh its data, it would
correctly show that the point was not there.
14.6/0 OMF 001360 The Maestro version of the LOOPFCM display needed to show the source
of S800 I/O, which was not possible using the presently available OMF
objects.
14.6/0 OMF/ 22 Implemented software to handle indirect effects of timeouts, queue
DBMS backups, and other conditions that do not normally occur in the
combinations that cause failure except when under deliberately excessive
load conditions on Advant Controllers.
14.6/0 OMF2MOD 14 Changed PHL to handle daylight savings transitions as an online upgrade.
3BUR 002 051D4 2-7

Section 2.2.3 AdvaBuild ABB-PESU_291001 Fileset Fixes


14.6/0 OMF2MOD 26 RTDS errored when requesting Recipe display which caused the RTAB to
fail and require rebooting.
14.6/0 OMF2MOD 30 Added ability to obtain lists of all units and of all descriptor sets in a system
at start time.
14.6/0 OMF2MOD 56 When requesting "execute|on cycle", a GetByRelInst / CapCommFail error
was received after a node reboot. The error continued after the node came
back up. If the subscription was terminated and restarted the data was
received without error. The following error was printed out in the bugs
window. "* omDbmsPost: terr $23, aerr $64 -> status code $92, flags $0"
14.6/0 OMF2MOD 63 PUT operations for the following attributes in the CCF_DEVICE_LOOP
object type affected the next attribute in the list, rather than the intended
attribute: TIMER_1, TIMER_2, TIME_CNT, TRANOVRD, VEN_TYPE,
REVERT0. Some of these are not supposed to be changed at all, so the
wrong put could affect the operation of the system.
14.6/0 RDP 27 TRIO RDP diagnostic displays were showing no data. The LAN Overview
display for SC controller, and the Block I/O and Block Configuration
displays for both SC and AC controllers, were affected.
14.6/0 TCL 000011 When many STEP_TRANSITION statements were present, the compile
would fail.
14.6/0 TCL 17 Previous fixes (000789 & 000216) needed to be backed out.
000261 was done to fix a bug with 000789. 000789 was checking the
seq_dir files for sequence names (same for recipes) unique to 12
characters, but not 8, and erroneously doing a replace instead of an insert.
This caused other problems. The problem of unique filenames to 12
characters, but not unique to 8, is done by the mechanism creating the files
themselves (i.e. HP-UX or NT TCL Builders).
14.6/0 TCL 000261 No error returned when Dir entry exists.
2.2.3 AdvaBuild ABB-PESU_291001 Fileset Fixes

Table 2-4 lists the new fixes provided in the ABB-PESU_291001 fileset of the CD-ROM:
Table 2-4. ABB-PESU_291001 Fixes
ID No. Description
11* and 336 FCB - Printing using 'print_fcb_27.sh' script now works. FCB’s can now be printed from the
command line. Printing now works for FCB and MOD 300 FCM's.
109 The compiler will no longer crash if Oracle returns an error.
3BUR 002 051D4 2-8

Section 2.2.3 AdvaBuild ABB-PESU_291001 Fileset Fixes
Table 2-4. ABB-PESU_291001 Fixes (Continued)
ID No. Description
207 Error messages are no longer issued when an FMS backup successfully completes.
208 If you had a DEVICE LOOP using a VENDOR TYPE of S100 I/O that does not exist on the
controller, then when the loop was turned on it would cause a bus error.
It is no longer possible to compile, install and download a configuration with S100 IO specified that
does not exist. Also, on an AC460 controller, which does not have S100 IO, a device loop
configured with the vendor type to be S100 and the input and output channels set to zero and
compiled will now have the following error message:
ERROR! - VENDOR TYPE IS S100 I/O
- A S100 I/O TEMPLET HAS NOT BEEN DEFINED !!!
No loadable image will be produced.
213 The enable rate alarming attribute is now correctly displayed on the loop FCM. When you call up a
loop definition templet from the LoopFCM, the Enable Rate Alarms item was always NO.
224 The compiler no longer bus errors on the ll_reg templet if the register name is blank and an initial
value existed.
230 The system no longer locks-up if the system documentation display and the service display are up
at the same time.
262 When new data base points were added onto an existing S800 I/0, the diagnostic message
"DBUPDATER REJECTED MESSAGE FROM 1602\\", AP=1684 and AP=1682" was generated.
This happened when using loopfcm to display a device loops templet which caused a memory
deallocation error when exiting the templet display if the device type was 1-in-0-out or 0-in-1-out
and the loop used S800 I/O. This will no longer happen if either input or output channel path is not
needed.
302 A loop compile on a DEVICE LOOP and LL_I_O template with S100 IO and with the input or output
channel at 0 produced no error. Corrected fix number 208 to solve this problem.
326* The date is now printed on the FCB print outs.
340 An error message now reports 'no references to export' when exporting references if there are no
references to export. Previously a cryptic message was generated. Fixes CCRP APC-0109.
351* The FCB print out will now work for loops that begin with a numeric character.
451 The following message was appearing in the install report:
ALARM GROUP ROUTE ERROR: TOO MANY RECEIVE GROUPS: jRºm J®ÿHfp-@ÿH..ÿ®
ALARM GROUP ROUTING NOT ACTIVE FOR AC6_2
The syntax/error checking is now bypassed if the GRPROUTE.DT file does not exist or the node
being processed is not in the file. As a result, this message is no longer generated.
452 Node level install time has been significantly reduced. Unix file copy functions are used rather than
the slower FMS file copy.
3BUR 002 051D4 2-9

Section 2.2.4 ABB-MODRTA.BOOT Fileset Fixes
Table 2-4. ABB-PESU_291001 Fixes (Continued)
ID No. Description
453 The opt/advant/ES/sh/chsbit was flagged as a security risk and is now removed from the
product.
458 It is now possible to configure an AIN FCM to use the S800 I/O analog output channel as a data
source.
472 TCL RCS files could not be checked out on OS/ES node. When a file was selected, the menu item
"Check Out" (in the Revision menu) was disabled. The only item enabled was "Create Initial
Revision". This problem was caused by the order in which filesets were installed.
476 In certain cases the TCLBuilder could not do check-in on an OS/ES node. This problem was due to
the order in which the file sets were installed. The BASE_FUNC was installed after TCL.
*Originally fixed in AdvaBuild 2.9/0 P3.
2.2.4 ABB-MODRTA.BOOT Fileset Fixes

See Table 2-3 for descriptions to changes that have been included in the ABB-
MODPU510.BOOT fileset (FMS Files) for Revision 14.6/3p00xx fixes on the CD-ROM for
AdvaBuild 2.9/1.
2.2.5 UXBase Fileset Fixes

Fixes for UXBase (DXPHRUN_26) Fileset are listed in Table 2-5.
Table 2-5. ABB-DXPHRUN_26 Fixes
ID No. Description
PHNE-244821 Eliminates possibility for remote user to gain root access in event of buffer overflow in telnetd.
PHNE-17135 HP mail patch.
3BUR 002 051D4 2-10

Section 2.2.6 ABB-HISTORY Fixes
2.2.6 ABB-HISTORY Fixes

Fixes for ABB-HISTORY Fileset Version 2.4/0 P13 are listed in Table 2-7.
Table 2-6. ABB-HISTORY Patch ABB-PHSU_240013 Fixes
ID No. Description
2300 Prevent crash after CAP_PARAMETER is returned from CCF/PHL.
The hsLogMan process would crash because memory was freed from the cache table that was still
referenced by the sorted list of names for the table. This condition occurred when
CAP_PARAMETER was returned from the PRIM_LOG interface and only the timestamp was
cleared for the cached entry. Now, when the CAP_PARAMENTER error is detected, the correct
function is called to expire the cached entry.
2256 Event Log configured for just process section zero collected ALL events for all process sections.
EH 3.2/1 Master OS event collection functioned differently from EH3.2/0. The "not included in a
process section" events could only be collected when ALL events were collected in EH3.2/1. In
EH3.2/0, these events could be collected separately from events included in process sections. The
condition which masks the configured sections for each log (a given section, 0, or all) was
corrected to handle the 18 individual cases and combinations.
2223 Changed hsPDLstorage (the only process responsible for storing PDL data) oracle warnings to
errors. WARNING messages created when the PDL tablespace was filled were changed to
ERROR diagnostics instead of WARNINGS. This addresses the concern where the loss of PDL
data as critical and where the batch data is no less important than the product manufactured.
2071 Changed code to assign the message data length to what was needed. The message length was
not being set correctly when a log was activated or deactivated. Consequently, when activating or
deactivating logs through RTS display, history would sometimes fail to do so on first try.
Subsequent request usually succeeded.
2016 The double link list used for maintaining the TTD/PHL/HDA secondary collection times was being
corrupted because pointer was not cleared correctly when a log was deleted. Now, the next and
previous pointers are cleared right after a secondary log queue entry has been removed.
2015 Corrected Master OS problem on history side.
In Master systems, history uses the ASNode object on each node to query each node for the
presences of a history server. When a remote system has a server that is hung, a response was
never returned to the omf client. This particular problem was with an EH2.2 node communicating
with a Master OS for NT. The history builder and hsLogMan were not finding the other two history
nodes on the system.
History was modified to timeout eventually and move on to the next node. An error message is
generated to track when this happens.
2014 Corrected dates for NT compatibility. A change in WIN2K moved the Minimum time accepted in the
history builder to 02 Jan 1970 12:00. If an object/log was configured with this time, the builder
could not correct it and the configuration would not be maintainable from EH3.2/1. This prevented
viewing HS2.4-0 configurations in EH3.2/1.
3BUR 002 051D4 2-11

Table 2-6. ABB-HISTORY Patch ABB-PHSU_240013 Fixes (Continued)
ID No. Description
2013 Added file to create ops$ocshis user.
Functionality for Information Manager version 3.5 requires that the ops$ochis user exist and have
access to oracle tables in EH2.2. This user will permit consolidation of message and PDL data and
access to numeric data in Information Manager 3.5 data system for viewing and disjoint distributed
collection of data.
2012 When composite logs were deleted, the entries in the log_source table were not deleted. Now,
log_source entries are deleted when composite logs are deleted.
2011 Generic error messages did not match types when forming error string. Tools that use this function
(dbConfig, the history builder, and others) would crash. Corrected sprintf for generic errors.
1685 Prior to this patch, HsBar could not be used to perform an on-line backup. hsBAR aborted the
backup if History was running. This interlock was implemented to prevent inconsistencies that
could occur in a backup image when the backup was done at the same time PDL data was being
collected.
This interlock has been removed so that on-line backups are now permitted; however, the problem
with running the on-line backup while PDL data is being collected has not been fixed. If you are
using PDL, do not run HsBar on-line. In this case you must stop the History process via PAS before
using HsBar.
If you attempted an on-line backup while collecting PDL data, and you have problems restoring the
data, contact the Technical Support Group via SUPPORTLINE - U.S.: (1-800-HELP-365);
International: (1-614-224-5888).
1577 Corrected memory leak in hsLogMan.
When a UserAPI modify of a numeric log was performed, hsLogMan memory grew by about 0.5 K
per putHistdata call. The logManager did not release memory when HSModifyVAlue was used
without an ON_START condition.
1513 After History has been down for some time, made sure all data gets archived after reactivating
History.
The size of an archive group can grow when an archive volume is unavailable and a scheduled
archive occurs. When this happens, the next scheduled archive for the group will be twice as big as
the first. As a result, Archive groups can quickly grow to a size that will not fit on an single archive
volume (but may fit on several archive volumes) causing all the archive volumes to be marked as
full (even though they may be empty).
The solution was to store time when the archive group gets archived in LAST_ARCHIVE column
for the group itself. Then, if History is trying to archive data from a time interval that is greater than
2 scheduled archives the end time for this archive group is reset accordingly. Therefore, data will
never be archived for a time interval greater than twice the scheduled time.
3BUR 002 051D4 2-12

Fixes for ABB-HISTORY Fileset Version 2.4/0 P12 are listed in Table 2-7.
ID No. Description
1457 Corrected section filter conversion for Event Log configuration.
1446 Changed LogSet display to correctly display states.
1432 Corrected collection crash when deactivating a dual log which is failing over.
1428 Corrected parsing issues with dbChanges file.
1409 Corrected restore of PDL modify columns.
1399 Data is stored correctly for Eventlogs messages. This is fixed by a post installation procedure for
Master systems only. See History Services Version 2.4 Patch 12 Release Notes.
378 Previously PDL was corrupted after restore from hsBAR, if History was running while the backup
was being created. hsBAR will not allow History back up with PDL while the system is running.
Patch 13 fix 1685 allows backups on line, even with PDL data (cancels this fix).
1374 Fixed crash that occurred when activating user-supplied log.
1352 Conversion will no longer corrupt numeric data for large logs when conversion is executed twice.
1327 History config can now be migrated to Enterprise Historian 3.2/1.
1313 Retrieval of next entry when countRequest is specified no longer fails.
1312 When restoring a log, verify that corresponding runtime log exists.
Fixes for ABB-HISTORY Fileset Version 2.4/0 p11 are listed in Table 2-8.
ID No. Description
829 In history builder the Archive -> View Report logs option now works correctly, so you can search
for reports in view report log window.
893 Archive volume transition no longer halts if the first archive after it returns a failure.
895 The Update Status command in RTS display no longer waits for History to restart.
905 dbconfig no longer crashes on load when secondary log exists with no primary log.
920 The dbConfig stats output, created when checking dbLoad files, now adjusts the Oracle space
needed for OPC/Audit message logs.
960 Audit Trail Log no longer causes the History Builder to crash with the following error: "hsBuilder.exe
has generated errors and will be closed by Windows. You will need to restart the program. An error
log has been generated."
1002 When restoring any data from any archive, hsArchive will not crash.
3BUR 002 051D4 2-13

ID No. Description
1048 hsArchive process no longer closes STDIN handle.
1176 Running PDL and Reports through TCL statements no longer causes hsModInterface to crash
when a PDL 'end batch' and a Report command are sent very close to each other.
1180 MOD 300 timestamps are now reported correctly (no longer off by 1 hour) when times older than
the last time change are passed from the ModInterface.
1191 Deleting a report log now deletes reports in Oracle and tablespace used by that log is freed up.
1226 Conversion no longer fails for PDL upgrade.
1239 When merging data directories, hsBAR now correctly updates size quotas
1251 hsBAR backup now works correctly for MasterOS.
1253 resource occurrence can be a random number. When recording resource Associations from the
hsModInterface, it is possible that the occurrence number is not zero. This is occurring because the
typeDir treats the values as an output parameter only. Since the value is always zero for this
transaction, the value can be force to zero inside PDLstorage
Fixes for ABB-HISTORY Fileset Version 2.4/0 p10 are listed in Table 2-9.
ID No. Description
216 In cases where only one numeric log exists in a composite log and no CCF or PHL logs are defined
(or the time span for the request is outside the timespan supported by PHL or CCF), the
logManager will not switch to the restored log, if available, when the accessName is the requested
name. (BaseHistory, MOD 300 only).
431 On MOD300 CDP nodes, a timing issue between the start of MTOS and the OMF tasks on the
RTAB can cause the OMF in the host OS (NT or UNIX) to fail to resubscribe on Node UP for the
RTAB. This prevent the logManager from seeing ALL MOD300 nodes (history and controllers) on
the DCN. When this occurs, no trend data can be retrieved from the logManager. (BaseHistory and
History, MOD 300 only)
460 Bulk Data Export fails when getting more than 3200 raw data values.
461 BDX loses parameter default values.
462 BDX cannot get raw data for a single synchronous log, nor can it get interpolated data for a single
asynchronous log. Two or more logs must be specified to have raw data returned.
489 Fixed crash in History Builder when filtering entries in View Archive Media window. Also removed
time field in filter and search dialogs for log entries as that field appears to be completely useless.
495 hsModInterface crash with dead messages. This could occur using PDL when the Start_Batch
message was missed. The END_BATCH would not cause the interim messages to be stored in
PDL, and the hsModInterface process would eventually fail.
3BUR 002 051D4 2-14

ID No. Description
503 Activating a log and then deactivating before it goes from pending to active, causes the log to go to
translating and stay there. Attempting to deactivate again causes a dialog saying that it is already
not active.
604 Auto archiving of Profile PDL data on Batch end has been seen to not work on occasion. The
problem is resolved by restarting History at which point all the PDLs that could not be archived at
their appointed time are archived (MOD 300 and Profiles only).
605 An auto/manual archive of a PDL containing associations to multiple Profile Logs only contains
archive data for the PDL and the first log in the association. The other logs, even though they
contain data, have no data in the archive entry. (MOD 300 and Profiles only).
672 In AdvancedHistoryBuilder, if the user chooses tools > global messages and tries to choose edit
> clear the program will crash. This only happens if there is at least one message in the display.
673 Fix dbConfig crash when like log name matches one of the names of a fully configured log.
704 Remove composite log typical object from history server runtime tables when last log in a typical is
deleted.
If a new log with a typical is created and the typical name is the same as the old one, History
Builder will report an error saying that the name already exists, even though it was deleted.
714 Corrected purge future dates to work properly with files that have super index block. Also added a
utility option to fix the files that have been corrupted with the “hsDBMaint -purge” before this fix was
applied.
715 When asking for data in time range completely after any log data, “hsDBMaint -bdx” has a potential
of crashing or simply not returning what it is supposed to return, which is NoData points for the
entire requested interval.
719 If Directory Maintenance window is opened on a node that has no directories configured in history
or if all directories are deleted from that window, the builder will crash.
729 dbConfig crashed because a compaction ratio had decimals (like 0.0178) in it.
738 When in the composite log view and the user selects File->Open, the dialog shows all the logs but
the Filter Logs, Search Logs, and Refresh List buttons are all grayed out and disabled.
755 BDX incorrect permissions does not allow raw data export to be used for Data Reconciliation client
applications or other client applications.
760 Fixed crash in hsServer when retrieving list of logs in a logs in log sets and second log set is empty.
761 If newly created composite log is the first composite log, it may fail to show up in the Open
Composite Log dialog box after it has been saved.
765 dbConfig changes option does not reset next index when the logCapacity is modified. This can
cause data corruption of the numeric logs when trying to increase the log capacity.
3BUR 002 051D4 2-15

ID No. Description
775 hsLogMan includes CCF/PHL when trying to resolve requests from MOD consoles. This can result
in an 8 second time-out for each trace on a MOD console, delaying data returned for almost 2
minutes (12 traces * 8 =96 seconds). (BaseHistory, MOD 300 only).
779 Modify operations are not accepted by hsServer. Allow debug in hsPDLStorage.
780 Increased surface limit for Jukebox archive to the maximum supported number, 64.
792 Report requests that are issued at the end of Batch 300 batches are preventing PDL data from
being stored and hence archived by the Enterprise Historian.
799 If archive fails to write out an automatically scheduled PDL, history server never reschedules the
PDL to archive again. It will also not schedule any more automatic PDL archives. Once in this
state, the only way to correct the situation is to restart History.
805 Diagnostic errors occur when modifying PDL task variables.
819 The dcHistoryRestore script provided by history for the Master OSHS fails. This occurs because
the -s option for hsBAR should not have been included in the script.
822 During an upgrade of History from 2.2/0 to 2.4/0, the UpgradeHistory220 script failed to convert a
large table (750,000 entries). The temporary tablespace created for the table was not large
enough. The fix is to have the system calculate the size of the temporary table needed before the
conversion task is run, and build the table based on those results.
3BUR 002 051D4 2-16

Section 2.3 Known Problems
2.3 Known Problems
2.3.1 General
Refer to the AdvaCommand 1.8/1 / AdvaBuild 2.9/0 P2 Release Notes for a summary of known
problems documented in that release.
Refer to the AdvaCommand 1.8/0 / AdvaBuild 2.9/0 Release Notes for a summary of known
problems documented in that release.
2.3.2 Advant HSI

Table 2-10 lists Advant HSI known problems.
Table 2-10. Advant HSI Known Problems
ID No. Description
10 Problem: The Display Builder allows users to convert their custom graphics from within the File
pull-down menu. When this Display Converter is used, Central Administration has problems and
the graphic files are not copied to the /home/operator/osgraphics/servergraphics directory.
Work around: The Display Converter (separate external app) conversion of graphics works
properly.
13 Problem: Batch RDP bus errors if checking dependencies for a large recipe while ACTIVE.
Problem was reproduced at an earlier revision (1.7/1).
Work around: None.
21 Problem: Trend Rate accepts bogus values in Loop Detail. Only 0, 6, 12, 60, 120, .... should be
allowed, however, any value could be entered.
Work around: Only use allowed values.
28 Problem: ASE is configured for an environment on a central admin. A client then downloads an
environment from the central admin. After this there is a 3 min timeout period if the central admin
can not be reached leaving the station unusable for 3 mins. This occurs anytime the login window
is brought up.
Work around: None.
55 Problem: All Oracle tasks will not start. The message 'Unable to Find Server' is displayed. Any
attempt to install an environment fails.
Work around: This may happen after the initial installation and on the first load only. Reboot the
oracle node.
59 Problem: Ramp keys (F11&F12) work even if the cursor is not in the dialog (no focus).
Work around: Close the dialog when done.
3BUR 002 051D4 2-17

Section 2.3.2 Advant HSI
Table 2-10. Advant HSI Known Problems (Continued)
ID No. Description
61 Problem: Loop Detail displays generate symbolic error message in certain conditions. If the user
does not have authority to configure the loop detail components and has the area listed in their
user setup ( in the environment builder ) a symbolic error message is generated if they attempt to
violate their authority. The message should read “You do not have authority”.
Work around: None.
62 Problem: If Central Administration and Xterms are being used and the Xterm server cannot
connect to it's primary or backup Central Administration server, the xterm will attempt to download
the environment (configured in the customerSystemVariables file) from the xterm server even if the
xterm server is not listed as a source for environment downloads. If the attempt is successful, there
is no warning message and every consecutive attempt by an xterm to download an environment
from that xterm server will result in the same unexpected environment to be downloaded even if
the network connection to the Central Administration server is restored. If the xterm is unable to get
an environment from either the central admin servers or the xterm server, an error message is
shown; but, any consecutive attempt by an xterm to download an environment from that same
xterm server will result in a failure, even if the network connection to the Central Administration
server(s) have been restored.
Work around: None.
64 Problem: F12 on an xterm is mapped to ramp and xterm configuration. ALT-F12 should be
mapped to the xterm configuration.
Work around: Close the xtrem window if you get it.
66 Problem: The Batch RDP authority configuration from the Environment is copied down to RDP on
the RTAB board every time an RDP display is started. If XTerminals are used it is possible that
different authority arrays are copied to the RTAB. Because there is only one array on the RTAB a
user may gain permission to do an operation which they should not have. The only RDPs known to
use this table are the Batch 300 RDP displays.
Work around: Set up access rights for the XTerminals to be the same as for the Batch RDP.
70 Problem: Installation of OS1.8.2 P1 or greater using search does not work on B180 workstations.
Work around: DO NOT USE the search command. Use the bo scsi.2.0 command.
73 Problem: Central Administration does not "fail" to backup when the node is already running.
When the AdvaCommand software starts on the client, the client node is connected to the primary
server node if available, then the backup server and then to its own local Oracle server. However,
after startup, if the node is running and the primary server goes down the client would not fail to the
backup. Instead, the client looks for a local environment.
Work around: To make sure you have access to another environment server while running, enable
the environment server selection menu on the Login Page for environment installation.
3BUR 002 051D4 2-18

Section 2.3.3 AdvaBuild
2.3.3 AdvaBuild
Table 2-11 lists AdvaBuild known problems.
Table 2-11. AdvaBuild Known Problems
ID No. Description
320 Problem: The COMP MODE RESTRICT field on a PID shows up as updateable (blue) and can be
changed from NO to YES without a loop compile. However, after a controller reset, COMP MODE
RESTRICT shows up as non-updateable and it can not be changed from YES without a compile as
expected.
Work around: None.
488 Problem: Errors show up in logfile when restoring on top of existing project. Lots of Oracle errors
show up in the logfile when a project is restored on top of an existing project.
Work around: Don’t do this. Instead, Remove the project, recreate the project and then restore.
2.3.4 Advant System Software

Table 2-12 lists advant System Software known problems.
Table 2-12. Advant System Software Known Problems
ID No. Description
124 Problem: When upgrading from v14.4 to v14.5 or v14.6, if the Hard reset of the AC460 controller is
used, or if a backup controller is rebooted, when that back up controller comes up it will fail
because the memory for AC460 Redundancy was moved. When the backup and primary
synchronize, the backup controller fails. The primary and other controllers in the subsystem may
also fail.
Work around: If possible, perform an off-line upgrade when upgrading from AdvaCommand 1.6 or
1.7 to 1.8/x or higher. If an off-line upgrade is not possible, once the Engineering Station has been
loaded with the new software, the AC460 controllers should be upgraded as soon as possible
following the correct procedure in the AdvaCommand 1.8/2 P1 / AdvaBuild 2.9/1 User’s Guide.
125 Problem: When using S800 IO DO810 modules with a device loop that has an inverted
momentary output, and is on demand scan, the momentary output may not be set correctly on
controller reboot.
Work around: Either put the device loop on scan, or to give manual commands to initialize the
loop.
3BUR 002 051D4 2-19

Section 3.1 Introduction
Chapter 3 Installation
3.1 Introduction
Please review all instructions before installing this upgrade. Also, review your ABB Support
terms and conditions, for precautions, scope of license, restrictions, and limitation of liability
and warranties, before installing this upgrade.
NOTE
In case of difficulties, please contact the Technical Support Group via
SUPPORTLINE: in the U.S. - (1-800-HELP-365);
International - (1-614-224-5888).
You may be getting this CD-ROM for a new system install or an upgrade. A complete install is
described in the installation instructions of the Advant Station 500 Series with AdvaCommand
1.8/2 P1 / AdvaBuild 2.9/1 User’s Guide and is required for all installations prior to that release.
Even if you are doing a clean install and not an upgrade, the Model B, SC and AC controller
nodes may still be allowed to online upgrade to the current release. Systems with controllers that
can be online upgraded are:
• OS1.6/5, ES2.7/4 (See Caution)
• OS1.7/3, ES2.7/5 (See Caution)
• OS1.8/1, ES2.9/0p2
• OS1.8/2, ES2.9/1
The upgrade instructions in the rest of this section only apply when upgrading from:
AdvaCommand 1.8/1 / AdvaBuild 2.9/0 P2
AdvaCommand 1.8/2 / AdvaBuild 2.9/1
CAUTION
When performing an on-line upgrade of AC460 controllers from AdvaCommand
1.6 or 1.7 to 1.8/x or higher, if the backup controller 'Hard Reset' is selected rather
than 'Reset for Upgrade', the backup controller reboot will fail and may cause
other controllers in that node to fail. This can also happen if the 'Reset for
Upgrade' should fail. If possible, perform an off-line upgrade when upgrading
from AdvaCommand 1.6 or 1.7 to 1.8/x or higher. If an off-line upgrade is not
possible, once the Engineering Station has been loaded with the new software, the
AC460 controllers should be upgraded as soon as possible following the correct
procedure in the AdvaCommand 1.8/2 P1 / AdvaBuild 2.9/1 User’s Guide.
3BUR 002 051D4 3-1

Section 3.2 Backup and Restore
3.2 Backup and Restore

You should backup your Operator Station before upgrading. If necessary, you can use this
backup to restore your data. For information on backing up and restoring your OS, please refer
to the Advant® Station 500 Series with AdvaCommand 1.8/2 P1 / AdvaBuild 2.9/1 User’s
Guide.
3.3 Installation
3.3.1 Starting Instructions

These instructions must be performed to prepare the CD-ROM or DVD-ROM reader to load the
software to the local station or remote stations. These instructions need only be performed one
time before loading one or more stations.
3.3.1.1 Adding /SD_CDROM with sam

The /SD_CDROM directory must exist before adding this update CD-ROM to the system.
Check to see if the /SD_CDROM directory exists by entering ls / and looking for it. If it does
not already exist, follow the instructions below for adding the /SD_CDROM directory with sam.
If it does exist, skip these instructions and continue on to Section 3.3.1.2, Preparing the
CD-ROM or DVD-ROM for Installation.
These instructions are performed to add the /SD_CDROM directory for a CD or DVD drive.
Make sure you have a disk in the drive.
1. In an HP terminal window, log on as the root user.
2. Enter sam
3. Within SAM Areas window, select Disks and File Systems.
4. Within the SAM Areas: Disks and File Systems window, select Disk Devices. This scans
the hardware.
5. Within the Disk Devices window, select CD or DVD from SCSI list of devices.
6. Under the Actions menu item, select ‘Add’ -> Not Using the Logical Volume Manager.
7. For CD devices, use the ‘Add CD_ROM Disk’ window to:
a. enter /SD_CDROM as the Mount Directory
b. in the ‘When to mount’ area, deselect ‘Now’ and leave ‘At every system boot’
selected
c. click OK.
8. For DVD’s, use the ‘Add Disk without LVM’ window to:
a. enter /SD_CDROM as the Mount Directory
b. select Modify Defaults and change Access to Read Only
c. in the ‘When to mount’ area, deselect ‘Now’ and leave ‘At every system boot’
selected
3BUR 002 051D4 3-2

Section 3.3.2 Instructions for Station(s) to be Updated using CD-ROM
d. click OK to ‘Modify Defaults’ window

e. click OK to ‘Add Disk without LVM’ window
f. On the ‘Confirmation’ window leave the ‘Mount the Existing File System’ selected
and click OK.
9. Select File -> Exit.
10. Select File -> Exit SAM.
In addition check/edit the /etc/fstab file to change hfs to cdfs in the /SD_CDROM line so it
reads: /dev/dsk/c0t0d0 /SD_CDROM cdfs ro,suid 0 0.
3.3.1.2 Preparing the CD-ROM or DVD-ROM for Installation

1. In an HP terminal window, log on as the root user.
2. If there is a CD already mounted, be sure to unmount it (umount /SD_CDROM).
3. Insert the AdvaCommand 1.8/2 P1 / Advabuild 2.9/1 CD-ROM into the drive
4. Enter mount /SD_CDROM
5. Enter: /SD_CDROM/upgrade/register_depot
This command only needs to be entered one time before loading the first station. It
registers the directories containing the software to be loaded.
3.3.1.3 Preparing for a Remote Upgrade

These instructions must be performed on each station that is to have the update installed from a
remote host to prevent the local station from trying to use a locally mounted CD-ROM directory.
• Unmount any locally mounted CD-ROM
• Check the etc/fstab file for instructions to mount a CD and comment it out. For example,
be sure to comment out the following (or similar line) as shown:
#/dev/dsk/c0t0d0 /SD_CDROM cdfs ro,suid 0 0
If you fail to do this, the remote upgrade will produce an ERROR in the analysis stage.
3.3.2 Instructions for Station(s) to be Updated using CD-ROM

These instructions must be performed on each station that is to have the update installed.
1. If the station you are updating is an X-terminal host, do step a through step d before you go
to step 2. If the station you are updating is not an X-terminal host, go directly to step 2.
a. You need to stop the AdvaCommand software at every X-terminal connected to the
host. Therefore, at each X-terminal running AdvaCommand remotely from the host,
press <Ctrl-D> and enter stopsession in the command field.
b. On the X-terminal host station press <Ctrl-D> and enter quit in the command field.
c. Suspend the AdvaCommand Auto Startup Interface by clicking on the Suspend
button.
3BUR 002 051D4 3-3

Section 3.3.2 Instructions for Station(s) to be Updated using CD-ROM
d. On the X-terminal host, open an HP terminal window.

2. Stop AdvaCommand.
a. Open an hpterm window, log on as root and run:
/sbin/init.d/advaCommand stop
b. Once the X server is stopped you may have to press the <Enter> key to see the login
prompt.
c. Log on as root (super user).
3. Load the upgrade script by entering:
/opt/advant/Upgrade/UpgradeOCS
4. Enter the TCP/IP address of the host with the CD-ROM (SD_CDROM) if requested
(message only occurs when doing a remote upgrade).
5. Verify your installed software version, the version to be installed and, if correct, enter y at
the prompt to upgrade. For a remote installation, you can ignore the message for the
remote host “ipaddress:/SD_CDROM/Advant-OCS”; Cannot open the
logfile on ... .
6. After the upgrade is complete, the station will either reboot on its own to the MOD OS
configuration page (continue with step 7) or a command prompt will be seen to reboot the
station (enter reboot command).
reboot
NOTE
On the OS or OSES, you may see an error message that the station is unable to
find the server and any attempt to install an environment fails. If this occurs,
perform a second re-boot. With a successful re-boot, the station will find the
server and you can install an environment.
7. At the Operator Station Startup Interface window, open HP terminal windows as required
to complete Section 3.3.4, Post Installation Work and Section 3.3.3, Finishing Instructions.
Exit all HP terminal windows when done.
NOTE
If ES 2.9/0 p3 or p4 was previously installed, the match to target upgrade will
complete, but the project backup to tape will not function unless the softlink
reference to the patch is removed. If you have either of these patches installed,
following the upgrade, remove the extra softlink by performing the following
command(s) as root.
$ rm /opt/advant/ES2.9-0p3 (and/or p4)
8. Follow the start-up procedures as described in Advant Station 500 Series with
AdvaCommand 1.8/2 P1 / AdvaBuild 2.9/1 User’s Guide.
3BUR 002 051D4 3-4

Section 3.3.3 Finishing Instructions
3.3.3 Finishing Instructions

These instructions must be performed to remove the CD-ROM from the reader after loading the
upgrade to the local station or remote stations.
1. In an HP terminal window, log on as the root user
2. Enter umount /SD_CDROM
3. Remove CD-ROM from the reader.
3.3.4 Post Installation Work
3.3.4.1 Update Customer System Variables File

The original file, $OS_CONFIG/customerSystemVariables, may be used to update the
new file, $OS_HOME/newconfig/etc/customerSystemVariables, by doing the
following steps:
1. Use the same HP terminal window and log on as above and do the following steps.
2. Enter:
cp -p customerSystemVariables customerSystemVariables.orig
3. Enter:
cp -p $OS_HOME/newconfig/etc/customerSystemVariables .
4. Merge any changes from the old file to the new file if necessary.
5. Reboot for changes to take effect.
3.3.4.2 onlineUpgrade File Diagnostic and Removal

The file "onlineUpgrade" causes the following system diagnostic warning message to display
for each Advant Station re-booted:
HS:FINISH UPGRD AFTER CTRLS BOOTED AT E14R5 W (text)
E14R5 L632 FIX=0000 (00) AP=822C (0000,0000) W (code)
This message serves as a reminder to finish upgrading each Advant Station, which displays the
message during boot-up, by deleting the "onlineUpgrade" file as follows:
rm /var/opt/advant/tmp/History/onlineUpgrade
or
rm $HS_TMP/onlineUpgrade
After the controllers in a system are upgraded to 14.6/x and the onlineUpgrade file is removed,
reboot the Advant Stations. This allows the OMF object resolution to start working.
If the Advant Station software is ever re-installed from the CD-ROM, the file will be reinstalled
and the diagnostic will occur with a re-boot. Delete the file if your controllers are at the current
software version (14.6/x) and reboot. This file will not be returned to the system if the Advant
Station is upgraded.
3BUR 002 051D4 3-5

Section 3.3.4 Post Installation Work
If an Operator Station with AdvaBuild options is upgraded off-line, do not remove the
"onlineUpgrade" file before it is added to the live ring. This will defeat the purpose of the file
and may cause the controllers (14.4/2 and older) to reset when the ES is added to the "live"
DCN in preparation for the online upgrade.
Enterprise Historian and AdvaCommand with History nodes also require controllers to be at
14.6/x. For MOD 300 systems upgrading from AdvaBuild 2.7/2 (or MOD 300 CDP's at 14.4/2)
or older, the system must be upgraded to MOD 300 system software 14.6/x and the controllers
rebooted before the Enterprise Historian nodes are placed on the system. Failure to follow this
procedure could bus-error all controllers.
3.3.4.3 Log File Update and Review

Whenever an upgrade is installed on a system, you should check for ERROR in the following
text files. Further checks can be reviewed the swinstall.log and swagent.log.
InstallSummary.txt and UpgradeSummary.txt

The system writes pertinent upgrade/installation data to one of the following text files,
depending on whether you are performing a new installation, or an upgrade:
• $IPA_LOG/Upgrade/InstallSummary.txt
• $IPA_LOG/Upgrade/UpgradeSummary.txt.pid
where pid = the process ID of the process that ran the upgrade script. There may be more than
one such file. Look at the file with the most recent date and time.
These text files include:
• a record of before-and-after software versions
• disk usage data
• duration of the upgrade/installation
• any errors recorded in the swagent.log file
It is recommended that you read the applicable summary text file before you check the
swagent.log file. Log is an ocsmgr, then open the applicable text file. If the summary text file
shows errors, then you should also check the swagent.log file. If there are no errors in the
summary txt file, then there is no need to check the swagent.log file.
swinstall.log and swagent.log

Review the swinstall.log and swagent.log in the /var/adm/sw directory.
To review the swagent.log, enter:
tail -270 /var/adm/sw/swagent.log | more
You can use the space bar to page through this file. Search for the correct date and time
heading. Check for any messages that begin with ERROR.
3BUR 002 051D4 3-6

Section 3.3.4 Post Installation Work
NOTE
The following errors can be ignored if seen:
• Could not select the software “PHCO_19845.PHCO_19485”. This software
does not exist in the target. ...
• IC Software object library errors:
IC_SetNumAttribute
IC_GetNumAttribute
• RPC exception: “Connection closed (dce / rpc)”
Optional User Log

At the end of the user_update.log file, add the upgrade names that you have installed, the
date, and description if desired. Any other changes made to the product, such as custom memory
pool changes may also be added.
The file should be created it if it does not exist. You may make the file name more application
specific, such as user_update_os1.8-2P1.log, and rename the file at each software
update step along the way.
The purpose of the text file is to prevent the deletion of certain user critical changes during a
reloading or updating of a machine.
3.3.4.4 Loading Software to MOD 300 Subsystems

Refer to the Advant® Station 500 Series with AdvaCommand 1.8/2 P1 / AdvaBuild 2.9/1 User’s
Guide.
3BUR 002 051D4 3-7

3BUR 002 051D4
April 2003

3BUR002051D4 - en AdvaCommand 1.8 2 P1 AdvaBuild 2.9 1 Release Notes

Uploaded by

Copyright:

Available Formats

3BUR002051D4 - en AdvaCommand 1.8 2 P1 AdvaBuild 2.9 1 Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3BUR002051D4 - en AdvaCommand 1.8 2 P1 AdvaBuild 2.9 1 Release Notes

Uploaded by

Copyright:

Available Formats

Advant OCS AdvaCommand®1.

3BUR 002 051D4

Copyright © 2003 ABB Inc

3BUR 002 051D4

3BUR 002 051D4 1

3.3.4.4 Loading Software to MOD 300 Subsystems........................7

3BUR 002 051D4 2

1.1 Executive Summary

1.2 Version Designation

3BUR 002 051D4 1-1

1.4 Software/Firmware Requirements

1.4.1 Firmware for DCN Interface Module

3BUR 002 051D4 1-2

System time between nodes can be synchronized to 100ms of the Master

1.4.2 Firmware for Advant Controllers AC 460

Table 1-3. SC540 Carrier Board PROM Identification

3BUR 002 051D4 1-3

1.5 Related Documentation

Table 1-4. Related Documentation - Advant Station

3BUR 002 051D4 1-4

2.1 Revised Functions

2.2 Fixed Problems

3BUR 002 051D4 2-1

2.2.1 AdvaCommand ABB-AC-OSs Fixes

Table 2-1. ABB-AC-OSs Fixes Introduced with AdvaCommand 1.8/2 P1

ID No. Problem Description

Table 2-2. ABB-AC-OSs Fixes Introduced with AdvaCommand 1.8/2

ID No. Problem Description

3BUR 002 051D4 2-2

Table 2-2. ABB-AC-OSs Fixes Introduced with AdvaCommand 1.8/2 (Continued)

ID No. Problem Description

3BUR 002 051D4 2-3

2.2.2 ABB-MODRTA.LOAD Fileset Fixes

Table 2-3. ABB-MODRTA.PU510LOAD and ABB-MODRTA.PU511LOAD Fileset Revision 14.6/3p00xx Fixes

Update AP ID No. Description

3BUR 002 051D4 2-4

Table 2-3. ABB-MODRTA.PU510LOAD and ABB-MODRTA.PU511LOAD Fileset Revision 14.6/3p00xx Fixes

Update AP ID No. Description

3BUR 002 051D4 2-5

Table 2-3. ABB-MODRTA.PU510LOAD and ABB-MODRTA.PU511LOAD Fileset Revision 14.6/3p00xx Fixes

Update AP ID No. Description

3BUR 002 051D4 2-6

Table 2-3. ABB-MODRTA.PU510LOAD and ABB-MODRTA.PU511LOAD Fileset Revision 14.6/3p00xx Fixes

Update AP ID No. Description

3BUR 002 051D4 2-7

Table 2-3. ABB-MODRTA.PU510LOAD and ABB-MODRTA.PU511LOAD Fileset Revision 14.6/3p00xx Fixes

Update AP ID No. Description

2.2.3 AdvaBuild ABB-PESU_291001 Fileset Fixes

Table 2-4. ABB-PESU_291001 Fixes

3BUR 002 051D4 2-8

Table 2-4. ABB-PESU_291001 Fixes (Continued)

3BUR 002 051D4 2-9

Table 2-4. ABB-PESU_291001 Fixes (Continued)

*Originally fixed in AdvaBuild 2.9/0 P3.

2.2.4 ABB-MODRTA.BOOT Fileset Fixes

2.2.5 UXBase Fileset Fixes

Table 2-5. ABB-DXPHRUN_26 Fixes

3BUR 002 051D4 2-10

2.2.6 ABB-HISTORY Fixes