Advant Advant Station 500 Series

Transcription

Advant® OCS
with MOD 300™ Software
Advant Station 500 Series
with AdvaCommand 1.7/1 /
AdvaBuild 2.7/3
User’s Guide
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, AdvaCommand, AdvaInform, and AdvaBuild are registered trademarks of ABB Asea Brown Boveri Ltd, Switzerland.
NOTICE
The information in this document is subject to change without notice and should not be construed as a commitment by ABB
Industrial Systems Inc. ABB Industrial Systems Inc. assumes no responsibility for any errors that may appear in this document.
In no event shall ABB Industrial Systems 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 Industrial Systems 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 ABB Industrial Systems Inc.’s written permission,
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.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low Voltage Directive 72/23/EEC.
Copyright © ABB Industrial Systems Inc. 2000
3BUR001 835R0001 REV C
3BSE001264/D
Template: 3BSE001286/E
Advant Station 500 Series with AdvaCommand 1.7/1 / AdvaBuild 2.7/3 User’s Guide
Table of Contents
TABLE OF CONTENTS
Chapter 1 - Introduction
1.1
Before You Begin..................................................................................................... 1-1
1.1.1
1.2
PROMs.................................................................................................... 1-1
1.1.1.1
D/F PROMs...................................................................... 1-1
1.1.1.2
Other PROMs................................................................... 1-1
1.1.2
DCN Node Upgrade Sequence for Alarm Burst Handling..................... 1-1
1.1.3
General.................................................................................................... 1-2
Equipment Requirements......................................................................................... 1-3
1.2.1
Workstation Requirements...................................................................... 1-4
1.2.2
Operator Station without Environment Builder ...................................... 1-5
1.2.3
X-Terminal Server Workstation .............................................................. 1-5
1.2.3.1
1 MByte Memory Cache.................................................. 1-6
1.2.4
Additional Workstation Requirements.................................................... 1-6
1.2.5
X-Terminal Requirements....................................................................... 1-7
1.3
How to Use This Book............................................................................................. 1-8
1.4
Conventions ............................................................................................................. 1-8
1.5
Related Documentation............................................................................................ 1-9
1.6
Release History ...................................................................................................... 1-11
1.6.1
AdvaCommand ..................................................................................... 1-11
1.6.2
Universal Serial Bus (USB) Support .................................................... 1-12
Chapter 2 - Installation
2.1
Site Planning Environment ...................................................................................... 2-1
2.2
Installation Procedures............................................................................................. 2-1
2.2.1
AdvaBuild 2.7/3 General Information .................................................... 2-1
2.2.2
Quick Reference for Installation Procedures .......................................... 2-2
2.2.3
3BUR001 835R0001 REV C
2.2.2.1
Installation with Data Backup and Restore
Quick Reference............................................................... 2-3
2.2.2.2
Clean Installation Quick Reference ................................. 2-4
General Installation Preparations............................................................ 2-4
2.2.3.1
DAT Tape Drive Connection ............................................ 2-4
2.2.3.2
Customized Memory Pool ............................................... 2-5
2.2.3.3
Considerations for AdvaBuild Basic Software ................ 2-5
2.2.4
AdvaCommand Data Backup Information ............................................. 2-5
2.2.5
AdvaBuild Data Backup Information ..................................................... 2-6
2.2.5.1
Upgrade Customer Database............................................ 2-6
2.2.5.2
Save TCL Source Code Files ........................................... 2-6
2.2.5.3
Save Additional User-specific Data ................................. 2-6
i
Table of Contents
CONTENTS (continued)
2.2.5.4
Record Project Information .............................................. 2-7
2.2.5.5
Export Project Data and Store it to Tape .......................... 2-7
2.2.5.6
Backup FMS-specific files ............................................... 2-8
2.2.6
AdvaInform Data Backup Information ................................................... 2-8
2.2.7
Installation Procedures ............................................................................ 2-8
2.2.8
2.2.9
2.2.7.1
Shutdown the Station........................................................ 2-8
2.2.7.2
Installing HP-UX 10.20, AdvaCommand and
Options from CDROM Media.......................................... 2-9
2.2.7.3
Installing HP-UX 10.20, AdvaCommand and
Options from an Ignite Server ........................................ 2-14
2.2.7.4
Loading HP Netstation Software.................................... 2-22
2.2.7.5
Log File Update.............................................................. 2-22
Post Installation Work ........................................................................... 2-23
2.2.8.1
Pre-Conditions................................................................ 2-23
2.2.8.2
Setting Initial HP-UX Passwords ................................... 2-24
2.2.8.3
Considerations for Printer Support................................. 2-24
2.2.8.4
Additional Post Installation Work .................................. 2-24
2.2.8.5
Customized Memory Pool Restoration .......................... 2-24
AdvaInform Post Installation Work ...................................................... 2-24
2.2.9.1
2.2.10
AdvaCommand Data Restore Information............................................ 2-25
2.2.11
AdvaBuild Restore Data Information ................................................... 2-25
2.2.11.1
Create Project Body........................................................ 2-25
2.2.11.2
How to Create Additional User(s) for a Project ............. 2-27
2.2.11.3
Restore Project Data ....................................................... 2-29
2.2.11.4
Post Project Data Restore Procedure.............................. 2-30
2.2.11.5
Restore FMS-specific Files ............................................ 2-30
2.2.12
Loading Software to MOD 300 Subsystems......................................... 2-30
2.2.13
AdvaInform History Data Restore and Upgrade Information............... 2-35
2.2.14
Installing the Serial Expansion Unit (SEU) .......................................... 2-35
2.2.12.1
2.2.15
ii
Operator Station with AdvaInform Options
OMF config.cfg File Update........................................... 2-25
Controllers ...................................................................... 2-31
2.2.14.1
Before You Install the Device Driver ............................. 2-35
2.2.14.2
Installation Prerequisites ................................................ 2-35
2.2.14.3
Installation Instructions .................................................. 2-35
2.2.14.4
Booting from a Backup Kernel....................................... 2-39
Installing the Touchscreen..................................................................... 2-40
2.2.15.1
Hardware Setup .............................................................. 2-40
2.2.15.2
SONY Monitor with Elo Touch SAW Touchscreen....... 2-40
3BUR001 835R0001 REV C
Table of Contents
2.2.16
2.3
2.4
2.2.15.3
SONY Monitor with Elo Touch SAW Touchscreen
and SEU ......................................................................... 2-42
2.2.15.4
Carroll Touch ................................................................. 2-43
2.2.15.5
Carroll Touch with SEU................................................. 2-43
2.2.15.6
Xtouch Software Installation.......................................... 2-43
Final Note ............................................................................................. 2-45
Shut-down Procedures ........................................................................................... 2-45
2.3.1
AdvaCommand Software Shutdown..................................................... 2-45
2.3.2
Power Down the Advant Station........................................................... 2-46
2.3.2.1
Power Down by a Non-Root User.................................. 2-46
2.3.2.2
Power Down by the Root User....................................... 2-47
Start-up Procedures................................................................................................ 2-47
2.4.1
Host Power Up and Verification ........................................................... 2-47
2.4.1.1
2.4.2
AdvaCommand Auto Startup ......................................... 2-48
X-Terminal Power Up and Verification ................................................ 2-50
2.4.2.1
X-Terminal Startup......................................................... 2-50
2.4.2.2
Automatic X-Terminal Connection................................ 2-50
2.4.2.3
AdvaCommand X-Terminal Auto Startup Interface ...... 2-51
Chapter 3 - Configuration/Application Building
3.1
Capacity and Performance ....................................................................................... 3-1
3.2
Database Configuration ........................................................................................... 3-1
3.2.1
3.2.2
3.2.3
3.2.4
3.3
Representing the Operator Station in the MOD 300 Database............... 3-1
3.2.1.1
GENERICD Object.......................................................... 3-3
3.2.1.2
MODUSERS Object ........................................................ 3-5
How to Configure Database Objects to Support Alarm/Event Logging. 3-6
3.2.2.1
AREA Object ................................................................... 3-6
3.2.2.2
LOG_DETL Object.......................................................... 3-9
Database Objects for History................................................................ 3-13
3.2.3.1
AREA Object ................................................................. 3-14
3.2.3.2
MSG_ROUT Object....................................................... 3-16
Database Objects for Reports and PDL ................................................ 3-17
Setup for Interface with MOD 300 System via a Serial Gateway ......................... 3-18
3.3.1
How to Configure the MOD 300 Database to Support
a Serial Gateway ................................................................................... 3-19
3.3.1.1
3BUR001 835R0001 REV C
GenericD Object ............................................................ 3-19
3.3.1.2
Computer Interface Object............................................. 3-19
3.3.1.3
Computer Interface Definition Object............................ 3-19
3.3.1.4
Serial Port Setup Object ................................................. 3-20
iii
Table of Contents
3.3.2
3.4
How to Configure the Serial Port on the Engineering Station .............. 3-21
3.3.2.1
Serial Port Configuration Dialog.................................... 3-21
3.3.2.2
Creating Device Special File on an Advant Station ....... 3-22
3.3.3
How to Configure the Jumpers on the MOD 300 Serial I/O Module ... 3-23
3.3.4
Serial Cable Requirements .................................................................... 3-23
How to Transfer Taylor Ladder Logic (TLL) Segment Files................................. 3-24
3.4.1
Prerequisites .......................................................................................... 3-24
3.4.2
File Transfer Procedure ......................................................................... 3-24
3.5
Application Start-up ............................................................................................... 3-25
3.6
Station Configuration ............................................................................................. 3-26
3.6.1
3.6.2
3.6.3
3.6.4
Setting the DCN Address ...................................................................... 3-26
3.6.1.1
Initial DCN Address ....................................................... 3-26
3.6.1.2
Changing the DCN Address ........................................... 3-26
3.6.1.3
Configuring a DCN Stand-alone System ....................... 3-26
3.6.1.4
Converting a DCN Stand-alone System to a
System on the DCN ........................................................ 3-26
Environments ........................................................................................ 3-26
3.6.2.1
AdvaCommand Default Environment ............................ 3-26
3.6.2.2
AdvaBuild Default Environment.................................... 3-27
3.6.2.3
Automatic Environment Install ...................................... 3-27
Changing TCP/IP Network Parameters and Time Zone with set_parms3-27
3.6.3.1
How to Change the System Name (Hostname) .............. 3-27
3.6.3.2
How to Change the TCP/IP Address .............................. 3-28
3.6.3.3
How to Change Additional TCP/IP Network Parameters3-28
3.6.3.4
How to Change the Time Zone....................................... 3-28
Conversion to Two-screen Operation .................................................... 3-29
3.6.4.1
iv
Vertical Two-screen Orientation..................................... 3-29
3.6.5
Native Language Support (NLS)........................................................... 3-29
3.6.6
Traditional and Simplified Chinese Character Set ................................ 3-30
3.6.7
Adding a Page Selector Alarm Panel (PSAP) to the Operator Station . 3-32
3.6.8
Configurable Function Keys ................................................................. 3-32
3.6.8.1
Text File Configuration .................................................. 3-33
3.6.8.2
Supported Keywords ...................................................... 3-34
3.6.8.3
The default.Function_Keys File Information ................. 3-35
3.6.8.4
Errors .............................................................................. 3-35
3.6.9
Operator Station Peripheral Devices General Information ................... 3-36
3.6.10
AdvaBuild Device Special File ............................................................. 3-37
3.6.11
Printer Setup.......................................................................................... 3-38
3BUR001 835R0001 REV C
Table of Contents
3.6.11.1
Hardware Connection..................................................... 3-38
3.6.11.2
HP-UX Printer Configuration ........................................ 3-38
3.6.11.3
Make Printer Available to Advant Applications ............ 3-40
3.6.12
How to Configure Alarm/Event Loggers.............................................. 3-41
3.6.13
External Alarm Annunciation Configuration ....................................... 3-43
3.6.13.1
Enabling External Annunciation in an Environment ..... 3-44
3.6.13.2
External Alarm CCF Loop Configuration...................... 3-44
3.6.14
SCSI Device Information...................................................................... 3-46
3.6.15
Security Key.......................................................................................... 3-46
3.6.15.1
3.6.16
Configuring the Serial Expansion Unit................................................. 3-49
3.6.16.1
Making Serial and Parallel Device Nodes...................... 3-49
3.6.16.2
Connecting Terminals to the SEU.................................. 3-50
3.6.16.3
Connecting Modems to the SEU.................................... 3-50
3.6.17
Configuring External Display Access for Xtouch ................................ 3-51
3.6.18
X-Terminal Installation......................................................................... 3-51
3.6.19
3.6.18.1
AdvaCommand osXConfig for HP and
PC X-Terminals.............................................................. 3-51
3.6.18.2
HP X-Terminal Configuration Procedures..................... 3-52
3.6.18.3
PC X-Terminal Configuration Procedures ..................... 3-57
3.6.18.4
PC with Reflection X X-Terminal
Software Configuration ................................................. 3-60
3.6.18.5
X-Terminal Startup......................................................... 3-63
3.6.18.6
Headless Server Configuration....................................... 3-63
3.6.18.7
Removing All X-Terminals............................................ 3-63
Optimizing User Graphic Performance ................................................ 3-64
3.6.19.1
3.6.20
Memory Resident Graphics ........................................... 3-65
Optimizing AdvaCommand Memory Usage ........................................ 3-66
3.6.21
Optimizing OMF Shared RAM Usage ................................................. 3-67
3.6.22
Adding File System Swap Space .......................................................... 3-68
3.6.23
Memory Pool Utility (mputil)............................................................... 3-69
3.6.24
Changing Tag Highlight Colors and Group Trend Attributes............... 3-71
3.6.25
Alarm Options....................................................................................... 3-73
3.6.26
Configuring Mouse Button 2 for Alarm Acknowledgement ................ 3-73
3.6.27
Advant Authority and Security Enhancements (ASE).......................... 3-74
3.6.27.1
3BUR001 835R0001 REV C
Security Key Configuration Programs ........................... 3-47
ASE User Configuration Tool ........................................ 3-75
3.6.27.2
ASE Configuration Options ........................................... 3-82
3.6.27.3
TCL Runtime User Identification .................................. 3-83
3.6.27.4
Automatic User Logoff .................................................. 3-84
v
Table of Contents
3.6.28
3.6.29
3.6.27.5
Read-Only AdvaCommand Station ................................ 3-85
3.6.27.6
ASE Log Files ................................................................ 3-85
Central Graphics and Environment Administration.............................. 3-86
3.6.28.1
Server Configuration ...................................................... 3-87
3.6.28.2
Client Configuration ....................................................... 3-87
3.6.28.3
Environment Server Selection Menu.............................. 3-88
3.6.28.4
Graphics Server Selection Menu .................................... 3-89
AdvaBuild On-line Documentation Configuration ............................... 3-90
3.6.29.1
Mounting the On-line Documentation CD ..................... 3-90
3.6.29.2
Auto-Mount the On-line Documentation CD................. 3-90
3.6.29.3
Copying the On-line Documentation CD
to the Hard Disk ............................................................. 3-91
3.6.29.4
Accessing the On-line Documentation CD
on Other Systems via NFS ............................................. 3-91
Chapter 4 - Runtime Operation
4.1
Operating Overview ................................................................................................. 4-1
4.2
Operating Instructions.............................................................................................. 4-1
4.2.1
Keyboard Mappings ................................................................................ 4-1
4.2.2
Using Xtouch .......................................................................................... 4-3
4.2.2.1
Default Xtouch Options.................................................... 4-3
4.2.2.2
Calibrating Xtouch ........................................................... 4-3
4.2.2.3
Starting Xtouch................................................................. 4-5
4.2.2.4
Terminating Xtouch.......................................................... 4-6
Chapter 5 - Maintenance
5.1
Error Messages......................................................................................................... 5-1
5.1.1
5.1.2
5.1.3
AdvaCommand Error Messages.............................................................. 5-1
5.1.1.1
Swap Space Improperly Configured................................. 5-1
5.1.1.2
OMF Shared RAM Exceeded........................................... 5-2
Error Messages for Xtouch (Touchscreen) Software .............................. 5-3
5.1.2.1
Calibration Diagnostic Messages ..................................... 5-3
5.1.2.2
Xtouch Diagnostic Messages ........................................... 5-4
5.1.2.3
“Problem with X...” .......................................................... 5-5
5.1.2.4
Performance Problems...................................................... 5-6
5.1.2.5
Hardware Problems .......................................................... 5-7
Error Messages for Serial Expansion Unit (SEU)................................... 5-8
5.1.3.1
vi
If You Have SEU Problems .............................................. 5-8
3BUR001 835R0001 REV C
Table of Contents
5.2
5.3
5.4
Full Station Backup/Recovery for AdvaCommand Stations 1.6/1 or Later ............ 5-8
5.2.1
Backing Up a Station .............................................................................. 5-8
5.2.2
Restoring a Station................................................................................ 5-10
AdvaCommand Partial Backup and Recovery....................................................... 5-11
5.3.1
fbackup.................................................................................................. 5-11
5.3.2
frecover ................................................................................................. 5-12
AdvaCommand 1.6/0 and Later Application Backup/Restore .............................. 5-13
5.4.1
Saving Existing Configuration Information.......................................... 5-13
5.4.2
Environments ........................................................................................ 5-13
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.5
5.6
Saving Your Environments............................................. 5-13
5.4.2.2
Restoring Your Environments ........................................ 5-13
Graphics ................................................................................................ 5-14
5.4.3.1
Saving Graphics ............................................................. 5-14
5.4.3.2
Restoring Your Graphics ................................................ 5-14
Personal Menu Files.............................................................................. 5-14
5.4.4.1
Saving Personal Menu Files........................................... 5-14
5.4.4.2
Restoring Personal Menu Files ...................................... 5-14
TCL and Batch 300 Files ...................................................................... 5-15
5.4.5.1
Saving TCL and Batch 300 FMS Files .......................... 5-15
5.4.5.2
Restoring TCL and Batch 300 FMS Files...................... 5-15
5.4.5.3
Saving TCL and Batch 300 Source Code Files.............. 5-15
5.4.5.4
Restoring TCL and Batch 300 Source Code Files ......... 5-16
Shared Memory Sizes ........................................................................... 5-16
5.4.6.1
Saving Shared Memory Sizes ........................................ 5-16
5.4.6.2
Restoring Shared Memory Sizes.................................... 5-16
NLS Definition Files............................................................................. 5-16
5.4.7.1
Saving NLS Definition Files .......................................... 5-16
5.4.7.2
Restoring NLS Definition Files ..................................... 5-17
AdvaCommand Backup/Restore Utility (HP OmniBack II) ................................. 5-18
5.5.1
Backup Considerations ......................................................................... 5-18
5.5.2
Restore Considerations ......................................................................... 5-22
AdvaBuild Application Backup/Restore................................................................ 5-23
5.6.1
3BUR001 835R0001 REV C
5.4.2.1
Project Backup...................................................................................... 5-23
5.6.1.1
Saving Project Data to DAT Tape .................................. 5-23
5.6.1.2
Saving a Project Release and Placing it into the
Same Station .................................................................. 5-24
5.6.1.3
Restoring Saved Project Data from DAT Tape............... 5-27
5.6.1.4
Restoring a Saved Project Release within a Station....... 5-31
vii
Table of Contents
5.6.2
FMS Backup and Restore...................................................................... 5-35
5.6.2.1
5.7
5.8
5.9
Full FMS Backup and Full FMS Restore ....................... 5-36
5.6.2.2
User FMS Backup and User FMS Restore..................... 5-37
5.6.2.3
TCL Data Backup and TCL Data Restore...................... 5-39
5.6.2.4
FMS and TCL Backup Procedure .................................. 5-39
5.6.2.5
FMS and TCL Restore ................................................... 5-41
AdvaBuild Copying Projects.................................................................................. 5-41
5.7.1
Copying a Project within a Station........................................................ 5-41
5.7.2
Copying a Project to another AdvaBuild Station in the Network ......... 5-45
5.7.3
Copying a Project to another Disconnected AdvaBuild Station ........... 5-47
5.7.4
Copying Project Subtree to another Project in same
AdvaBuild Station ................................................................................. 5-48
5.7.5
Copying Project Subtree to Project in different AdvaBuild Station ..... 5-50
5.7.6
Copying a Project Subtree to another Disconnected
AdvaBuild Station ................................................................................. 5-52
AdvaBuild Save and Restore of Private Data......................................................... 5-54
5.8.1
Saving Private Data on Tape ................................................................. 5-54
5.8.2
Restoring Private Data from Tape ......................................................... 5-54
AdvaInform Application Backup/Restore.............................................................. 5-55
5.9.1
5.9.2
History Data .......................................................................................... 5-55
5.9.1.1
Saving History Data ....................................................... 5-55
5.9.1.2
Restoring History Data ................................................... 5-55
Reports Data.......................................................................................... 5-55
5.9.2.1
Saving Reports Data ....................................................... 5-55
5.9.2.2
Restoring Reports Data .................................................. 5-56
Appendix A - X-Windowing
A.1
X-Windowing into an Information Management Station........................................ A-1
A.1.1
A.2
Closing the IMS Menu Session.............................................................. A-2
X-Windowing into an Engineering Station ............................................................. A-2
Appendix B - Function Key Configuration
B.1
viii
Function Key Configuration.................................................................................... B-1
B.1.1
Display Types......................................................................................... B-1
B.1.2
The default.Function_Keys File Listing................................................. B-2
3BUR001 835R0001 REV C
Table of Contents
Appendix C - HP-UX 10.20 Impact
C.1
General.....................................................................................................................C-1
C.2
New Layout of the File System ...............................................................................C-1
C.3
I/O Convergence ......................................................................................................C-7
C.4
Logical Volume Support ..........................................................................................C-9
Appendix D - Naming Scheme For Patches
Appendix E - Native Language Support (NLS) Readme File
Appendix F - PROM Checksums
F.1
Version 10.0/n and 14.n Multibus Node PROM Checksums - (4 June 1999) ......... F-1
INDEX
3BUR001 835R0001 REV C
ix
Table of Contents
x
3BUR001 835R0001 REV C
Section 1.1 Before You Begin
Chapter 1 Introduction
1.1 Before You Begin
1.1.1 PROMs
1.1.1.1 D/F PROMs
New D/F PROMs were required for SC Controller applications before upgrading to
AdvaCommand 1.6/0 / AdvaBuild 2.7/0 software. If AdvaCommand 1.6/0 was not installed,
D/F PROMs must be installed at this time. The D/F PROMs are also recommended for Model B
Controller D/F boards, especially for systems with high communication loads.
The D/F PROM kit (part number 155S1026) is available from the Columbus factory.
1.1.1.2 Other PROMs
The latest released PROMs are listed in Appendix F, PROM Checksums. Some of the latest
PROM releases are summarized below:
•
The D/M PROMs were new in July, 1997. The 512K version of the D/M PROMs are
needed for new model boards only.
•
New Model A and B Controller PROMs were recommended, but not required with
AdvaBuild Version 2.5/0 - Update 14.3-023, or AdvaBuild Revision 2.1/6- Patch 14.2
(3109).
•
Multibus PROMs were new in September, 1995. Serial I/O PROMs were new in May,
1994, and were required for Version 8.2.R2 and above.
1.1.2 DCN Node Upgrade Sequence for Alarm Burst Handling
AdvaCommand 1.6/0 software update provided a new alarm/event handling capability that
required a change to existing alarm/event message formats (as they exist on the MOD system).
If AdvaCommand 1.6/0 was not installed, and a site is upgrading to this software on-line, it is
necessary to upgrade the nodes on the DCN in a certain sequence. If the upgrade is not done in
this sequence, process alarms may be lost by MOD Consoles, CDP's, Advant Operator Stations,
Advant Engineering Stations, and Advant IMS nodes during the time of the upgrade.
The correct node upgrade sequence must be as follows:
3BUR001 835R0001 REV C
1.
Upgrade and restart all nodes that can be the receivers of Alarm/Event Messages first. This
means all MOD Consoles, CDP's, and Advant stations.
2.
Upgrade and restart any multibus nodes which have both Console and CCF functionality.
This would include turbo nodes functioning as Bulk I/O or PLC Gateways. This represents
a special class of node which is both a receiver and a sender.
1-1
3.
Upgrade ALL nodes that can be the originator of Alarm/Event Messages last. This means
Model A/B, SC, and Advant Controllers. On-line upgrade capability can be used to
upgrade controller software.
For further information, you can contact Technical Services:
SupportLine USA: +1-800-HELP 365
Worldwide: +1-614-224 5888
1.1.3 General
This book covers the installation and set-up of an Operator Station and Operator Station with
AdvaBuild® or AdvaInform® options. It covers both a clean installation, and an installation
with data backup and restore. The book should be used by station support personnel who are
responsible for station configuration.
If you are doing an upgrade to AdvaCommand 1.7/1, AdvaBuild 2.7/3, or the AdvaInform
Options 2.3, refer to the AdvaCommand 1.7/1 / AdvaBuild 2.7/3 Release Notes for upgrade
instructions.
The term “Operator Station” refers to an Advant 500 Series Station with AdvaCommand® Basic
Functions software. The Operator Station can also have AdvaBuild or AdvaInform options
software. An Operator Station with AdvaBuild options is referred to as an OS/ES.
The term “Engineering Station” refers to an Advant 500 Series Station with AdvaBuild Basic
Functions software. The Engineering Station can also have AdvaBuild options software.
AdvaCommand Stations with AdvaBuild options use the AdvaCommand Basic Functions
software as their base, but are not necessarily licensed to use it.
X-terminals can be used as lower cost remote displays to run the AdvaCommand or AdvaBuild
software. When X-terminals are used to run AdvaCommand software, they share the same
environment with the host worksation.
The hardware platform for the Advant Station Operator Station is the Advant Station 500 Series
(Advant Stations 510, 515, 520, 520i, 530/C110, 520/B132L, 520i/B132L, 520/B180L, or
530/B180L). It runs the AdvaCommand Basic Functions 1.7/1 software with any purchased
AdvaBuild 2.7/3 or AdvaInform 2.3 options.
The AdvaCommand Basic Functions software is the base software for all station configurations
in this book.
Operator stations can have one of the following software options:
1-2
•
Batch 300
•
AdvaBuild
•
AdvaInform
3BUR001 835R0001 REV C
Section 1.2 Equipment Requirements
The components of each of these options are listed below:
•
Batch 300
–
•
•
Batch 300 Software (requires AdvaBuild TCL Builder)
AdvaBuild
–
AdvaBuild Basic Functions (Structure Builder, Template Builder, and Function Chart
Builder, Typical Solutions, On-line Builder, and Oracle Report Writer)
–
AdvaBuild TCL Builder
–
AdvaBuild Environment Builder
–
AdvaBuild Display Builder
–
Taylor Ladder Logic (TLL)
–
Programmable Controller (PLC)
AdvaInform
–
AdvaInform Reports
–
AdvaInform History
–
AdvaInform SPC
–
AdvaInform PDL
–
AdvaInform SQL*Access
Instructions for hardware setup and installation, and for using the Operator Station software, are
provided in the applicable user’s guides as described in Section 1.5, Related Documentation.
NOTE
This book is not intended to be the sole source of instruction for the Advant
Station software. Those people involved in Operator Station support should
attend the applicable courses offered by ABB.
1.2 Equipment Requirements
There are specific requirements for worksations, and workstations that serve X-terminals. There
are also specific X-terminal requirements. Read the following sections carefully to determine
the equipment requirements for your configuration.
3BUR001 835R0001 REV C
1-3
1.2.1 Workstation Requirements
The RAM and Disk Space requirements for stations that do not serve X-terminals are as
follows:
For the AS520/B132L workstation:
Table 1-1. AS520/B132L RAM and Disk Requirements
Minimum RAM(1)
(MBytes)
Minimum Disk
Space(2)
(GBytes)
Operator Station(3)
96
3
128
4
OS with AdvaBuild option
96
3
128
4
OS with AdvaInform options
96
4
128
4
OS without Environment
Builder
96
2(4)
128
3
Station
Recommended Recommended Disk
RAM (MBytes)
Space (GBytes)
(see Section 1.2.2, Operator
Station without Environment
Builder)
(1)
(2)
(3)
(4)
Additional RAM is available in sets of 32 MB, 64 MB, and 128 MB.
If using more than 96 MB of RAM, you must use the larger Recommended Disk Space.
If Traditional Chinese is being installed, see Section 2.2.7, Installation Procedures.
Using minimum LVM option during install in Section 2.2.7.2, Installing HP-UX 10.20, AdvaCommand and Options from CDROM
Media. Note: Traditional Chinese cannot be installed on systems with a 2 Gbyte disk.
For the AS515, AS520i and AS530 workstations:
Table 1-2. AS515, AS520i and AS530 RAM and Disk Requirements
Minimum
RAM(1) (MBytes)
Minimum Disk
Space(2)
(GBytes)
Operator Station
80
3
128
4
OS with AdvaBuild option
96
3
128
4
OS with AdvaInform options
96
4
128
4
OS without Environment
Builder
80
2(3)
128
3
Station
Recommended Recommended Disk
RAM (MBytes)
Space (GBytes)
(see Section 1.2.2, Operator
Station without Environment
Builder)
(1) Additional RAM is available in sets of 16 MB, 32 MB, 64 MB, and 128 MB (AS530).
(2) If using more than the Minimum RAM, you must use the larger Recommended Disk Space.
(3) Using minimum LVM option during install in Section 2.2.7.2, Installing HP-UX 10.20, AdvaCommand and Options from CDROM
Media.
1-4
3BUR001 835R0001 REV C
Section 1.2.2 Operator Station without Environment Builder
1.2.2 Operator Station without Environment Builder
The Operator Station without Environment Builder is a new option in AdvaCommand 1.7/1.
This option allows you to designate one or more Operator Stations as Environment/Graphics
servers and designate other Operator Stations as Environment/Graphics clients. On the client
stations, the Environment Builder and Oracle are not loaded saving over 240 MBytes of disk
space and 20 Mbytes of memory. These client stations can operate with lower disk requirements
and increased performance due to reduced memory usage.
On an Operator Station with 96 Mbytes of RAM, a 2 Gbyte disk has over 400 MBytes available
for graphic usage. Systems with 128 MBytes or more, will require at least a 3 Gbyte disk due to
increased swap size requirements. These stations will still benefit from the reduced memory
usage and easier graphics maintenance. If you are upgrading from a previous version, calculate
the amount of space used by your converted graphic files and check to see if it is less than 360
MBytes. This allows you to determine if you can avoid adding additional disk space to a
2 GByte system.
You can not upgrade, but must fully reinstall AdvaCommand to take advantage of this option.
1.2.3 X-Terminal Server Workstation
X-terminals are supported with AdvaCommand and AdvaBuild software, but are not supported
with AdvaInform or Batch 300 software.
You can have a maximum of 4 X-terminals. The local monitor counts as one X-terminal.
Two local heads are supported, but they count as one X-terminal in calculating system load and
hardware requirements.
The following are the minimum requirements for Advant Stations that serve X-terminals:
•
AS520/B132L workstation or higher
•
RTAB board with 16 MBytes or RAM
•
96 MBytes of workstation RAM, see Table 1-3 below
•
HP Netstation version 8 or 9 X-terminal software.
You must purchase the HP Netstation software as an option to use X-terminals on
your station. Instruction for loading the HP Netstation X-terminal software are
supplied with the media when the option is purchased.
3BUR001 835R0001 REV C
1-5
Table 1-3. Workstation RAM Requirements for X-Terminals
Number of X-Terminals
Amount of RAM (MBytes)(1)
1
96
2
128
3
192
4
256
(1) These are the minimum requirements and may need to be raised for larger
environments, a large number of graphics, or increased performance.
•
3 GBytes of disk space. If you have more than 300 graphics, additional disk space may be
required.
•
Common ethernet sub-network for the Workstations, X-terminals and printers
1.2.3.1 1 MByte Memory Cache
An optional 1 MByte memory cache chipset is available. It improves the performance of the
B132 workstation about 5-10%. It is not available for the other workstations.
1.2.4 Additional Workstation Requirements
Additional requirements that apply to all workstations include:
•
Swap space is set to the values in Table 1-4
Table 1-4. Workstation Swap Space Settings
1-6
RAM Memory
(MBytes)
Swap Space Size
(MBytes)
< 96
200
96 - 128
320
128 - 192
480
192 - 256
640
> 256
960
•
Universal keyboard with mouse or trackball or
•
Universal Serial Bus (USB) keyboard with trackball (requires PS/2 keyboard and mouse)
•
4mm, 1.2 GB DAT tape drive
•
CD-ROM drive (as fast as possible)
3BUR001 835R0001 REV C
Section 1.2.5 X-Terminal Requirements
1.2.5 X-Terminal Requirements
You can have up to four X-terminals running AdvaCommand software. If you run
AdvaCommand at the local graphics monitor, a maximum of three X-terminals can be used.
You can have up to four X-terminals running AdvaBuild software.
The X-terminal can be either an HP Envizex II with 20 MBytes of RAM, or a PC. The X-station
monitor should be color and have a resolution of 1280 x 1024.
The minimum requirements for a PC are:
•
100MHz Pentium CPU
•
32 MBytes of RAM
•
Microsoft Windows 95 with service pack 1, or NT 4.0 with service pack 3 operating
system
•
WRQ Reflection X X-terminal server software version 7.0.
NOTE
On a PC X-terminal, configure your PC operating system to use only 256 colors.
Figure 1-1 shows the layout of an Advant Station with X-terminals on a plant network.
up to four X-terminals running AdvaCommand
up to four X-terminals running AdvaBuild
TCP/IP Plant Network
Advant Station
DCN
Figure 1-1. Advant Station with X-terminals
X-terminals do not support touchscreens, datakeys, ABB keyboards, or PSAPs.
There are keyboard mappings that X-terminals can use to emulate the ABB keyboard functions,
see Section 4.2.1, Keyboard Mappings.
3BUR001 835R0001 REV C
1-7
There is a total of 4 simultaneous RDP displays allowed per server.
The X-terminals must be on a common TCP/IP sub-network. The sub-network can be part of the
plant network, or a dedicated network.
1.3 How to Use This Book
This book is organized into chapters and sections as shown in Table 1-5.
Table 1-5. Manual Organization
Introduction
Installation
Configuration
Runtime
Operation
Maintenance
Appendices
Before You
Begin
Site Planning
Capacity &
Performance
Operating
Overview
Error Messages
X-Windowing
Equipment
Requirements
Installation
Procedures
Database
Configuration
Operating
Instructions
Backup/Restore
Procedures
Function Key
Configuration
How to Use This Shut-down
Book
Procedures
Application
Start-up
HP-UX 10.20
Impact
Conventions
Station
Configuration
Naming Scheme
For Patches
Start-up
Procedures
Related
Documentation
Release History
1.4 Conventions
The following conventions are used throughout this manual for the presentation of material:
1-8
•
The words in proper names of screen elements (for example, the title in the title bar of a
window, the label for a field of a dialog box) are initially capitalized.
•
The names of keyboard keys are boldfaced.
–
Initial capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, the Return key or <Return>.
–
Lowercase letters are used for the name of a keyboard key that is not labeled on the
keyboard. For example, the space bar, comma key, and so on.
–
In descriptions, the word “key” is used in conjunction with its name. For example,
pressing the Return key initiates the process.
–
In tables and procedures, angle brackets replace the word “key.” For example, press
<Return>.
–
A dash is used to indicate that you must simultaneously press several keys. For
example, <Ctrl-C> indicates that you must hold down the Control key while
pressing the C key.
3BUR001 835R0001 REV C
Section 1.5 Related Documentation
–
•
•
•
The phrase “press and release” is used to indicate that you sequentially press several
keys. For example, to close a window, press and release <Alt>, and then <F4>. This
indicates that you press and release the Alt key, and then you press and release the F4
function key.
The names of push and toggle buttons are boldfaced.
–
Initial capital letters are used for the name of a push or toggle button labeled on the
display. For example, the OK button.
–
In descriptions, tables and procedures, the word “button” is used in conjunction with
its name. For example, pressing the OK button initiates the process.
The names of menus and menu items are boldfaced.
–
Initial capital letters are used for the name of menus listed in the menu bar. For
example, the File menu.
–
Initial capital letters are used for the name of menu items. For example, to open a
new window, choose New from the File menu.
System prompts/messages are shown in the Courier font, and user responses/input are in
the boldfaced Courier font. For example, if you enter a value out of range, the following
message is displayed:
Entered value is not valid. The value must be 0-30.
In a tutorial, you may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
1.5 Related Documentation
Below are lists of related books providing information on upgrading AdvaCommand, the
Operator Station, and options.
The books below describe the hardware platform for the Operator Station. Consult these books
for instructions regarding hardware setup and installation.
3BUR001 835R0001 REV C
•
Advant Station 510 Hardware User’s Guide
•
•
•
Advant Station 520i Hardware User’s Guide
•
Advant Station 530/C110 Hardware User’s Guide
•
Advant Station 520/B132L Hardware User’s Guide
•
Advant Station 520i/B132L Hardware User’s Guide
•
Advant Station 530/B180L Hardware User’s Guide
•
Advant Station 520/B180L Hardware User’s Guide (Supports USB)
1-9
The following books provide instructions on upgrading and/or using the AdvaCommand and
options software.
•
AdvaCommand 1.7/1 / AdvaBuild 2.7/3 Release Notes
•
AdvaCommand 1.6/1 / AdvaBuild 2.7/0 Release Notes
•
•
AdvaCommand Basic Functions Version 1.7/1 User’s Guide
•
AdvaBuild Display Builder User’s Guide
•
AdvaBuild Environment Builder User’s Guide
The following books provide information related to the Advant Station Operator Station with
the Batch 300 Option:
•
Batch 300 User’s Guide
•
Batch 300 Engineering Guidelines
The following books provide information relevant for the Advant Station Operator Station with
AdvaBuild Options:
•
AdvaBuild Basic Functions User’s Guide
•
AdvaBuild TCL Builder User’s Guide
•
Taylor™ Ladder Logic (TLL)
•
Taylor™ Programmable Controller Interface User’s Guide
The following books provide information relevant for the Advant Station Operator Station with
AdvaInform Options:
•
AdvaInform History User’s Guide
•
AdvaInform Reports User’s Guide
•
AdvaInform PDL User’s Guide
•
AdvaInform SPC User’s Guide
•
AdvaInform SQL*Access User’s Guide
The following books provide installation and usage instructions for the Hewlett Packard HP-UX
10.20 software:
1-10
•
Readme before Installing or upgrading to HP-UX 10.20
•
Quick Guide to Updating HP-UX
•
Installing HP-UX 10.20 and Updating from HP-UX 10.0x to 10.20
•
Support Media User´s Manual
3BUR001 835R0001 REV C
Section 1.6 Release History
1.6 Release History
1.6.1 AdvaCommand
Version 1.3
•
Adding a Page Selector Alarm Panel (PSAP) to the Operator Station
•
Xtouch (touch screen) software
•
Serial Expansion Unit (SEU) software
Version 1.4
•
osAddDisk Utility
•
Power_down by a non-root user
•
Backup Logger now functional
•
New program, asb_tar, to do full backup and restore
Version 1.6
•
SONY Touch Screen support
•
Native Language Support (NLS)
•
New Keyboard Mappings
•
Memory Resident Graphics
•
Security (Data) Key
•
Single X-terminal configuration
•
Configurable Function Keys
•
AdvaCommand on-line diagnostics error messages
Version 1.6/1
3BUR001 835R0001 REV C
•
New station lock
•
New external alarm annunciation
•
Now supports up to 4 AdvaCommand X-terminals (with B132 Workstations)
•
New X-terminal login window
•
New X-terminal Auto Start-up Interface Window
•
New <Crtl-D> display line command “stopsession” to terminate an X-terminal session
•
New AdvaCommand display memory optimization procedure
•
New OMF shared memory optimization procedure
•
New alarm options
•
Full station backup and recovery for AdvaCommand 1.6/1 with options
1-11
Version 1.6/2 and 1.6/3
•
Simplified Chinese Character Set
•
TLL Segment Display modified to provide better user interface
•
Button 2 on 3-button mouse is configurable for Acknowledge function
Version 1.6/4
•
No new functionality, just patches
Version 1.7/1
•
MPUTIL support for PCI RTAB
•
Authority and Security Enhancements (ASE)
–
Password encryption
–
User authority groups
–
Password aging
–
Can enable/disable user accounts
–
Can configure users to enter an ID in addition to a password
–
Users can maintain their own passwords
–
Secure User Configuration Tool
–
Extended log files for user activities
–
Automatic logoff configuration
–
Read-only AdvaCommand station configuration
–
TCL user identification
•
Central Administration for environments and graphics
•
Traditional and Simplified Chinese Character sets
•
Button 2 on 3-button mouse can be configured for Ack function
1.6.2 Universal Serial Bus (USB) Support
USB Universal keyboards are used on an Operator Station (OS) with the addition of the
AS520/180L workstation. Refer to the Advant Station 520/B180L Hardware User’s Guide for
specific information concerning USB devices. This configuration also requires a PS/2 keyboard
and mouse be connected. Without the PS/2 keyboard and mouse the station will not boot or
shutdown correctly.
1-12
3BUR001 835R0001 REV C
Section 2.1 Site Planning Environment
Chapter 2 Installation
2.1 Site Planning Environment
For information regarding site planning and environmental considerations for your Operator or
Engineering Station, refer to the applicable Advant Station Hardware User’s Guide, as indicated
in Section 1.5, Related Documentation.
2.2 Installation Procedures
These instructions guide you through the new installation of the following:
•
Operator Station
•
Operator Station with AdvaBuild options
•
Operator Station with AdvaInform options
All the different station configurations are delivered with the applicable software installed;
therefore, software installation is not required upon delivery. Software installation is required
under the following conditions:
•
Total hard disk failure: this requires a complete installation of HP-UX 10.20 and Advant
software. This procedure clears all existing software and data on the hard disk(s).
•
If you want to install this software on an existing Advant Station, YOU MUST back up all
your application programs/data files. When you are finished with the installation, you must
restore the application data.
There are two types of installation: one with data backup and restore, and one without. Section
2.2.2, Quick Reference for Installation Procedures, provides a quick overview of the steps
required for these two types of installation.
2.2.1 AdvaBuild 2.7/3 General Information
The instructions in this chapter apply to installing AdvaBuild 2.7/3. During installations, the
existing station software is overwritten. AdvaBuild 2.7/x data can be backed up before, and
restored after installation according to these instructions.
If you are doing an upgrade of your AdvaBuild software, the instructions are in the
AdvaCommand 1.7/1 / AdvaBuild 2.7/3 Release Notes.
If you are installing on an existing Engineering Station version 2.1/7 or 2.5/2, you should
upgrade to version 2.7/0 first. Refer to the AdvaCommand 1.6/1 /AdvaBuild 2.7/0 User’s Guide
for more information.
3BUR001 835R0001 REV C
2-1
WARNINGS
•
If saving AdvaBuild data, you must use the same DAT drive to backup and
restore data.
•
For on-line installations, the controllers must be running the version 2.7/0, or
subsequent versions MOD 300 software.
Please review all instructions and your ABB support terms and conditions for
precautions, scope of license, restrictions, and, limitation of liability and
warranties, before installing any new software. Any problems or questions with
this installation should be directed to the Technical Support Group via
SUPPORTLINE: in the U.S. - (1-800-HELP-365); international (1-614-224-5888).
Full station backups done after you install AdvaBuild software version 2.7/3 are
handled by the Operator Station software, but backup of projects, MOD-specific
data, and user-specific data is still done with the AdvaBuild software utilities.
2.2.2 Quick Reference for Installation Procedures
If you want to do an installation on a station where the contents of your station will be cleared,
but data will be saved and restored, follow the steps outlined in Section 2.2.2.1, Installation with
Data Backup and Restore Quick Reference.
If you want to do an installation that completely clears the contents of your station, and does not
save or restore any data, follow the steps outlined in Section 2.2.2.2, Clean Installation Quick
Reference.
2-2
3BUR001 835R0001 REV C
Section 2.2.2 Quick Reference for Installation Procedures
2.2.2.1 Installation with Data Backup and Restore Quick Reference
The steps for installing on a station where there is data that needs to be backed up and restored
are summarized in Table 2-1.
Table 2-1. Installation with Data Backup and Restore
Installation with Data Backup and Restore
AdvaCommand
AdvaCommand
w/AdvaBuild Options
AdvaCommand
w/AdvaInform Options
Section 2.2.3, General
Installation Preparations
Section 2.2.4,
AdvaCommand Data
Backup Information
Section 2.2.4,
AdvaCommand Data
Backup Information
Section 2.2.4,
AdvaCommand Data
Backup Information
Section 2.2.7, Installation
Procedures
Section 2.2.5, AdvaBuild
Data Backup Information
Section 2.2.6, AdvaInform
Data Backup Information
Section 2.2.8, Post
Installation Work
Procedures
Procedures
Section 2.2.10,
AdvaCommand Data
Restore Information
Section 2.2.8, Post
Installation Work
Section 2.2.8, Post
Installation Work
Section 2.2.10,
AdvaCommand Data
Restore Information
Post Installation Work
Section 2.2.11, AdvaBuild
Restore Data Information
Section 2.2.10,
AdvaCommand Data
Restore Information
Section 2.2.12, Loading
Software to MOD 300
Subsystems
History Data Restore and
Upgrade Information
3BUR001 835R0001 REV C
2-3
2.2.2.2 Clean Installation Quick Reference
The steps for performing a clean installation (no data to backup) are summarized in Table 2-2.
Table 2-2. Clean Installation Path
Clean Installation
AdvaCommand
AdvaCommand
w/AdvaBuild Options
OS w/AdvaInform Opts.
Procedures
Procedures
Procedures
Section 2.2.8, Post
Installation Work
Section 2.2.8, Post
Installation Work
Section 2.2.8, Post
Installation Work
Post Installation Work
2.2.3 General Installation Preparations
To prepare for the installation, you will need:
•
a CD reader.
•
a DAT device. If saving AdvaBuild data, you must use the same DAT drive to backup and
restore data.
•
the AdvaCommand Ver. 1.7/1 AdvaBuild Ver. 2.7/3 AdvaInform Options Ver 2.3 CD-ROM
(Article Number 3BUR 001 700R1)
2.2.3.1 DAT Tape Drive Connection
Before installing your Operator Station, make sure you have a DAT device properly connected.
See Section 3.6.14, SCSI Device Information for instructions on how to connect it.
CAUTION
Shut down the station and turn power off before connecting a DAT device.
2-4
3BUR001 835R0001 REV C
Section 2.2.4 AdvaCommand Data Backup Information
2.2.3.2 Customized Memory Pool
If you have customized RTAB memory pools for your station, run the memory pool utility (see
Section 3.6.23, Memory Pool Utility (mputil)). Note both the custom pool percentages and their
absolute sizes. This information may be used during post installation. Quit the utility without
making any changes.
2.2.3.3 Considerations for AdvaBuild Basic Software
Check For Proper Network Terminators If Using Stand-alone Workstations
The following network terminators are required for the workstation to run properly:
•
AS520:
The TCP/IP BNC output is terminated with the supplied T-cross connector with two 50
Ohm terminator resistors.
•
AS515 and AS520i:
The TCP/IP AUI output is terminated with the supplied transceiver-cable, transceiver and
the T-cross connector with two 50 Ohm terminator resistors.
Network Name and Network Address
Your workstation is prepared to be integrated into a computer network based on TCP/IP.
If your workstation is already connected to a network, check for a possible mismatch/duplicate
Network name and/or Network address. Contact your Network administrator.
2.2.4 AdvaCommand Data Backup Information
If you are installing AdvaCommand 1.7/1 on an existing Advant Station with AdvaCommand
1.6/0 or later, and you want to save your AdvaCommand data, you must back it up as described
in Section 5.4, AdvaCommand 1.6/0 and Later Application Backup/Restore. When you are
done, go to Section 2.2.5, AdvaBuild Data Backup Information.
A full backup of your AdvaCommand 1.6/1 or later station can be performed as described in
Section 5.2, Full Station Backup/Recovery for AdvaCommand Stations 1.6/1 or Later. There is
no full backup procedure for AdvaCommand 1.6/0 stations. You will have to backup your files
as described in Section 5.3, AdvaCommand Partial Backup and Recovery.
If you are installing on an existing Advant Station with AdvaCommand version 1.4/1 through
1.4/5 you should upgrade to AdvaCommand 1.6/0 first. Refer to the AdvaCommand 1.6/1
/AdvaBuild 2.7/0 User’s Guide for more information.
If you are doing a new installation, go directly to Section 2.2.7, Installation Procedures.
3BUR001 835R0001 REV C
2-5
2.2.5 AdvaBuild Data Backup Information
This section only applies to installations of AdvaBuild software at 2.7/0 and above, where you
want to save the AdvaBuild data on the station.
If you are installing on an existing Engineering Station version 2.1/7 or 2.5/2, you should
upgrade to version 2.7/0 first. Refer to the AdvaCommand 1.6/1 /AdvaBuild 2.7/0 User’s Guide
for more information.
If you are doing a clean installation, go directly to Section 2.2.7, Installation Procedures.
NOTE
You must use the same DAT drive to backup and restore data.
2.2.5.1 Upgrade Customer Database
This section describes how to upgrade a customer database from release 2.7/x to release 2.7/3.
When you upgrade the customer database, you merge new data; data structures, and files from
the delivery version, with the customer project data, so the upgraded database and project
structures have the same contents as the old ones.
CAUTION
Make sure no other user is connected to the database during the upgrade.
The Example Project (MOD_EXP) may be changed without notice. If you have
made any changes to it that should be copied to the new database, create a new
project, with a name other than mod_exp, as a copy of your example project.
2.2.5.2 Save TCL Source Code Files
Make sure all TCL source code files for each project reside in a directory beneath the respective
project directory ($C_CAPE/<project>).
To save TCL source code files:
1.
Log in as the ocsmgr user, by entering: su - ocsmgr
and then entering the password (default password is ocsmgr).
2.
If not already created, make a new directory TCL beneath the project directory (of the
particular project).
3.
Copy all TCL sources for this project to this path.
Make sure this is done for all projects.
2.2.5.3 Save Additional User-specific Data
Any user-specific files (script or data) that exist within the file structure, but are not beneath a
project directory ($C_CAPE/<project>) must also be backed up. To do so:
1.
2-6
3BUR001 835R0001 REV C
Section 2.2.5 AdvaBuild Data Backup Information
2.
Create a new directory (for example, USER_DATA) beneath a project directory you plan
to backup. If the data is related to a particular project, create the new directory beneath that
project directory.
3.
Copy all user-specific files to this path.
2.2.5.4 Record Project Information
Record project information (name, size, and number) for each project to avoid losing data
during the installation. To check project data:
1.
Log in as the ocsmgr user, by entering: su - oscmgr
2.
Enter stb to start the Structure Builder.
3.
Open project administration using the admin username and password. Ensure the
password for the admin user is set to admin.
4.
Check and record the following information for each project using the AdvaBuild
Structure Builder (Administer/Projects or Administer/Users):
–
The project name, size and number
NOTE
This project number has to be used in order to successfully restore the project.
–
all usernames and group numbers of the project as indicated in the User window of
the administration function.
NOTE
If the default user password has been changed (from <project>_cfg), you must reset it
prior to installing an upgrade or patch. Failure to do so prior to installing an upgrade or
patch prevents the upgrade from successfully creating any new tables and/or performing
modifications on existing tables. This can be done from the ADMINISTRATION form,
select the Administer/Users menu option. Then from the USERS form, navigate to the
user you wish to reset. Next, select the Edit/Password menu item. This will bring up the
form used to change the password.
2.2.5.5 Export Project Data and Store it to Tape
For EACH PROJECT you are going to upgrade to AdvaBuild version 2.7/3, do the following:
1.
Log in as user ocsmgr by entering: su - ocsmgr
2.
Change the directory as follows: cd /home/ocsmgr
3.
Insert a blank tape into the tape drive (set the tape slide to the "READ/WRITE" position).
4.
To backup the project to tape, enter:
backup_project.sh -p <project> 2>&1 | tee $C_BIN_CAPE_LOG/backup_<project>.log
3BUR001 835R0001 REV C
2-7
where project = project short name
5.
When you see the message "Do you want to continue [y]", press <Return>.
6.
After project backup to tape is finished, remove the tape and label it with project name,
date, used project database size, and set the tape slide to the "READ ONLY" position.
After this procedure is completed, project data can be installed on an Advant Station with
AdvaBuild version 2.7/3 software.
2.2.5.6 Backup FMS-specific files
Use the utility USER_FMS_BACKUP to save FMS application files including Batch 300,
Taylor Ladder Logic, Taylor Control Language (generated via Multibus-based TCL editor),
diagnostic message archive, and installed MOD 300 database, to DDS tape. Refer to Section
5.6.2.2, User FMS Backup and User FMS Restore for more information.
WARNING
Make sure there are no active users when backing up FMS-specific files.
2.2.6 AdvaInform Data Backup Information
If you are installing AdvaCommand 1.7/1 with History options 2.3 over an Advant Station with
AdvaCommand 1.6/1 or later with AdvaInform History options 2.2 or later, you can backup
your AdvaInform data as described in Section 5.9, AdvaInform Application Backup/Restore
and then restore and upgrade your data as described in Section 2.2.13, AdvaInform History Data
Restore and Upgrade Information. If you have AdvaInform History 2.1/1, you must upgrade to
AdvaCommand 1.6/1 or later with AdvaInform History options 2.2 first.
2.2.7 Installation Procedures
This section applies to clean installations and existing installations where user data is being
saved and restored.
Overview
Ignite-UX is a tool supplied with HP-UX to do initial configuration of HP-UX systems. It
replaced the existing HP-UX Install program (also known as Cold Install) as well as the
CHAMP program (which was used by manufacturers to create HP-UX systems). Ignite-UX
supports all HP-UX releases starting with version 10.01. It is provided as a free bundled
product. In this release, Ignite is used to cold boot machines and network boot machines. It is
also used to backup and restore stations, refer to Section 5.2, Full Station Backup/Recovery for
AdvaCommand Stations 1.6/1 or Later.
2.2.7.1 Shutdown the Station
Before you begin the installation, shut down the station as follows:
2-8
3BUR001 835R0001 REV C
Section 2.2.7 Installation Procedures
NOTE
A USB device configuration requires a PS/2 keyboard and mouse be connected.
or the station will not shutdown correctly.
a.
Log in as root user by entering: su root (Password root)
b.
Enter: /etc/shutdown -h 0.
c.
After the message “system halted” is displayed, turn off the power.
NOTE
The alarm annunciator within the universal keyboard or the PSAP keyboard may
sound if the system unit is powered down. The annunciator may also go off if the
USB device is physically disconnected from the OS station. The RESET button
on the IH532/542 keyboard can be used to silence the annunciator. The PSAP
must be powered down to silence the annunciator.
2.2.7.2 Installing HP-UX 10.20, AdvaCommand and Options from CDROM Media
Everything needed for installation is contained on the CD. You will control the install session
via a terminal user interface running on the station’s console.
The name of the CD media for this installation is:
AdvaCommand 1.7/1 AdvaBuild 2.7/3 AdvaInform Options 2.3
The CD contains AdvaCommand 1.7/1, AdvaBuild 2.7/3 options, and AdvaInform 2.3 options
software.
NOTE
Device drivers for DAT drives, CD-ROM drives, or any other peripherals are not
created unless they are connected to the station during installation. If you want to
automatically configure a DAT drive or other peripheral on your station, connect
it to your station before starting the installation. If you don’t have the DAT drive
or other peripheral connected during installation, you can configure it later using
SAM.
To load AdvaCommand and/or the options:
1.
Do the following to boot your station from CD-ROM. The CD-ROM SCSI port must be
configured as address 2.
a.
Reboot your station and stop the boot process when prompted to do so. You do this
by continually pressing <ESC>. On some stations there is a very short window of
time to complete this operation.
NOTE
If you see a prompt to select a monitor, please ignore it. The local monitor is
selected by default.
b.
3BUR001 835R0001 REV C
Insert the CD into the CD-ROM drive.
2-9
2.
c.
Enter the command to search for boot devices (sea).
d.
Enter the command to boot using the CD-ROM as the device. If you see a prompt to
interact with IPL, respond by entering n (no). The station will begin to boot.
In a few minutes you will be prompted to configure the system.
a.
Enter the number for the keyboard language you want and confirm.
NOTE
Some older model machines may not prompt you for a keyboard language.
b.
Select Install HP-UX from the menu on the Hardware Summary display.
NOTE
The Ignite-UX Terminal user interface is started now. The following keys can be
used to navigate:
<Return> and <Space> select an item
<Tab> moves to the next item on the screen.
<Right> arrow and <Down> arrow cycle to the next item in the “Tab Group”
A Tab Group is defined as all of the selectable options within an area of the screen
defined by dotted lines. To move to the next Tab Group, <Tab> must be used.
<Left> arrow and <Up> arrow cycle to the previous item in the Tab Group. To move
to the next Tab Group, <Tab> must be used.
Additionally, any key with an underlined character, can be chosen by typing that
underlined character.
3.
Some older machines may prompt you for the Source Location Option. Leave the Media
Only Installation option selected.
4.
Select Advanced Installation from the User Interface Options, then select OK.
5.
Using the Basic tab, choose which Environment you will load. Your choices are:
6.
–
AdvaCommand Station
–
AdvaCommand Station with AdvaBuild option
–
AdvaCommand Station with AdvaInform option
You MUST select the Standard LVM file system unless you have a 2 Gbyte system and
you do not plan to install the Environment Builder with Oracle runtime product, in which
case you must select the Minimum LVM file system. If this is not done properly, your
disks will NOT be sized correctly and the load will fail.
For all stations except AdvaCommand without Environment Builder options select the
Standard LVM by double-clicking on the text. You will see the cursor change to an hour
glass cursor momentarily. If you don’t see the cursor change, double-click on the text
again. If you are not using the X-window GUI, you can reselect the “Standard LVM” file
system by pressing <Tab> until the Standard LVM text is highlighted, and press
2-10
3BUR001 835R0001 REV C
<Return> twice. For 2 Gbyte systems running AdvaCommand without Environment
Builders select the Minimum LVM text.
NOTE
Once the necessary disk space is allocated for the selected software, the install
utility allocates the remaining disk space to the /home logical volume, up to a
maximum of 2.5 Gbytes. Any additional drive space is not used. If you need
additional disk space at a later time, the unused disk space can be allocated to a
logical volume using Sam.
7.
Using the Software tab, select ALL from the Category frame and choose the products, if
any, that you wish to load.
The choices and descriptions are:
–
Envir. Builder with Oracle runtime
Select this option if you plan to build environments and graphics for other systems
and install them using the Central Administration features.
–
B4474EA_APZ - HP Netstation 8.0/7.1
HP Netstation should be selected if X-terminals are used as part of AdvaCommand.
This option only sizes disk partitions, the Netstation software needs to be purchased
and separately installed (see Section 2.2.7.4, Loading HP Netstation Software) to
operate X-terminals.
–
B3691AA_APZ_TRY - Trial HP GlancePlus/UX for s700 10.20
GlancePlus is a system performance monitor. This is a trial product only.
–
Ignite-UX-10-20 - HP-UX Installation Utilities for
Installing 10.20 Systems
This is the HP ignite server software. This option should be selected if you plan to
use this station as an Ignite server to load software onto client stations over the
network, or if you plan to do full station backups for client machines over the
network (see Section 5.2, Full Station Backup/Recovery for AdvaCommand Stations
1.6/1 or Later).
–
J2559C - Hewlett-Packard JetAdmin for Unix Utility
This is the HP patch for network printers. Load this option if you plan on using HP
network printers from this station.
3BUR001 835R0001 REV C
–
ABB-AB-MODEXP - Select this product if you want the AdvaBuild starter project.
–
HW-Enablement - Hardware enablement patches (ACE). This is selected for you
depending on your workstation hardware.
–
ABB-AI-SQLCONN - AdvaInform SQL*Connect option. Select this product if you
purchased the AdvaInform SQL option.
–
ABB-AI-SPC - (MOD) AdvaInform SPC option. Select this product if you
purchased the AdvaInform SPC option.
–
ABB-AI-REPORTS - (Advant) AdvaInform Reports option. Select this product if
2-11
you purchased the AdvaInform Reports option.
–
ABB-AI-PDL - (MOD300) AdvaInform PDL option. Select this product if you
purchased the AdvaInform PDL option.
–
ABB-AI-HISTORY - (Advant) AdvaInform History option. Select this product if
you purchased the AdvaInform History option.
NOTE
If you are installing AdvaCommand with AdvaBuild or AdvaInform options, you
might see WARNINGs that say: software selections can not be
selected due to an exrequisite of the selected item.
Please ignore these messages.
8.
Using the System tab, enter the machine specific system parameters. The information
entered is:
–
Hostname
–
IP Address
–
Subnet mask
–
Time and Date information
–
Time Zone
–
Root Password
–
Network Services - Under the Static Routes tab (ask network administrator for
values, or use the values below):
Destination: default
Gateway IP Address: Check with your network administrator for the address (Central
Administration functions require this)
Destination Hop Count:1
Select ADD followed by <Enter>. Once you see the gateway address in the window,
select OK.
9.
Using the File System tab, you can check to make sure your disk(s) are large enough to
accommodate software selections. If the Avail: megabytes field is a negative number, the
disk(s) are too small for all the software that you are loading.
The projected sizes of each logical volume can be viewed. You may change the sizes of
logical volumes, but it is not recommended, unless you are installing the Traditional
Chinese filesets. If you are installing the Traditional Chinese filesets, you will need to
increase the size of the /usr LVM by at least 150 Mbytes. To do this, perform the
following steps:
2-12
a.
Select the File System tab.
b.
Scroll down to the /usr LVM and increase its size by at least 150 Mbytes.
c.
Select modify.
3BUR001 835R0001 REV C
d.
View the sizes of the other LVMs to ensure that your disk(s) are large enough to
accommodate your software selections.
e.
Select OK.
WARNING
The volumes are sized for selected software, future software, maintenance, and
debugging. If LVM sizes are changed for reasons other than installing the
Traditional Chinese filesets, the software load may fail, Advant applications may
fail, and the system may have a reduced troubleshooting capability.
Any changes in LVM sizes are automatically rounded to even 4 megabyte increments.
For DVD:
If you are using a DVD drive to load your station, you must remove the DVD drive from
vg00. To do so from within the File System tab,
a.
Select the Add/Remove Disks option.
b.
Select the DVD drive in the scroll list.
c.
The Usage pulldown menu will show LVM. Change the pulldown to None.
d.
Click on the Modify button.
e.
Click OK in the Volume Resize Information window that pops up.
f.
Click OK in the Add/Remove Disks window.
WARNING
If you fail to remove the DVD drive from vg00, the load will fail.
10. Select GO! to start the installation.
There is another screen that will give WARNING and/or ERROR messages. Pay careful
attention to all the messages before you select the next GO! operation.
All software is now loaded and the AdvaCommand Start-up Interface will be displayed,
refer to Section 2.4.1.1, AdvaCommand Auto Startup. The amount of time varies based on
your station type and CD-ROM drive.
11. Load the following minor kernal fix to the System Administration Manager (SAM) tool.
NOTE
If you are using Ignite, you will have to copy the file kernel_fix to a temp
directory on the newly loaded station and then execute it at the station.
a.
Open an HP Term window, login as ROOT and enter:
/SD_CDROM/fixes/kernel_fix
the following message is displayed:
** WARNING ** : This script modifies the system kernel
and then reboots the machine.
3BUR001 835R0001 REV C
2-13
Do you wish to continue? (y for yes)
b.
enter y for yes.
12. If your station has the AdvaBuild options, reboot your station by opening an HP terminal
window from the AdvaCommand Startup Interface, login as root, and enter:
shutdown -r -y 0
If your station does not have the AdvaBuild options, reboot the station using the Operator
Station Startup Interface window.
13. Check the file named /var/adm/sw/swagent.log for any error messages.
NOTES
•
Error messages for the PHCO_14734 fileset can be ignored.
•
ORA-00942 errors in /var/adm/sw/swagent.log for importing
MOD_STD and MOD_EXP projects can be ignored. The errors occur
because USERS, PROJECT_SAVES and PROJECT_STATUS tables have a
constraint that references the PRO_NO column of the PROJECTS table.
When importing the PROJECTS table, the import tries to create the
constraints on the USERS, PROJECT_SAVES and PROJECT_STATUS
tables that have not been imported yet and generates the errors as a result. The
constraints are later created during the import of the USERS,
PROJECT_SAVES and PROJECT_STATUS tables.
2.2.7.3 Installing HP-UX 10.20, AdvaCommand and Options from an Ignite Server
Remote installations can be performed and monitored from a central server. You can also
perform multiple installations simultaneously.
Information about each installation is kept on the server in a per-target directory identified by
the address of the target machine. This data allows you to re-install the same target with the
same configuration at a later time if necessary.
Using the ignite server, you can use the graphical user interface instead of the terminal user
interface to perform the installation.
You can also choose to run a non-interactive installation. You can define the configuration you
want applied ahead of time and set an option to not run the user interface. In this case, the target
system will start the installation process as soon as it contacts the server. You are able to monitor
the process from the server, if you choose.
WARNING
The status bars representing the station load progress will indicate that the
installation is complete before the installation is actually completed. The load
progress status shown, only refers to the HPUX 10.20 load status, not the Advant
software load status. DO NOT begin the post installation procedures until the
target station displays the AdvaCommand Startup interface.
2-14
3BUR001 835R0001 REV C
Ignite-UX Server System Requirements:
•
NFS Server: The Ignite-UX server requires NFS to be configured and working, The
Ignite-UX installation will add lines to the /etc/exports file, and run exportfs.
•
tftp: Ignite-UX will transfer some of its files using tftp. The minimum directories needed
by tftp are set up in the /etc/inetd.conf file. Others may need to be added if you
place configuration scripts in non-standard locations.
NOTE
A separate Ignite-UX server is required for each subnet that you plan to install on.
Ignite installations across different subnets or domains is not recommended
because the results can be unpredictable.
Installation of Ignite-UX Server Software
1.
If you did not choose the Ignite-UX-10-20 product from the Software tab when you
installed your machine then you must load the software and the AdvaInstall software from
the AdvaCommand 1.7/1 AdvaBuild 2.7/3 AdvaInform Options 2.3 CD by entering the
commands (as root user):
swinstall -s /SD_CDROM/HPUX-Apps Ignite-UX-10-20
swinstall -s /SD_CDROM/Advant-OCS AdvaInstall
2.
In your login scripts add /opt/ignite/bin to your default search path by entering the
command:
export PATH=${PATH}:/opt/ignite/bin
3.
Start Ignite-UX with the command:
/opt/ignite/bin/startIgnite
NOTE
You will get a warning dialog stating no clients exist. This is normal since you
really do not have any clients waiting.
Ignite-UX Server Configuration
1.
As the root user (su root), start Ignite-UX by entering the command:
/opt/ignite/bin/startIgnite
For these instructions, Ignite must run in GUI mode, not in terminal text mode. If you are
running in GUI mode, you will see Ignite in a separate window with a blue background. In
this case, you can go to step 2.
If Ignite is started in terminal text mode (it will be running in the same window that you
issued the ignite command from), exit Ignite by typing <Ctrl-C>. Enter: su - operator and
then the password when prompted. Next, log on as root by entering su and the root
password when prompted. Once you are logged on as root, enter
/opt/ignite/bin/startIgnite. Ignite will now start in GUI mode.
3BUR001 835R0001 REV C
2-15
NOTE
You may see a “no clients” message. Ignore and choose OK to close the message
dialog.
2.
Select Server Configuration from the Options pulldown menu.
This will show the Server Configuration Menu with two tabs: Server Options and Session
Options. Under the Server Options tab do the following:
Modify (if needed) the Server Options to match the following:
3.
–
Default Configuration: Advant OCS English HPUX B.10.20 ACE CDE
–
Default Printer: <select a default printer to be used by IUX>
–
Client Timeouts: 40 (this is the number of minutes delay due to network, or client
failures before the IUX server will inform the administrator of a problem)
–
Run client installation UI on: server
(most administration of the install process to be performed only on the IUX server)
Select Configure booting IP Addresses
During installation, a client must boot over the network from the Ignite-UX server, using a
temporary IP address. One temporary IP address is needed for each simultaneous network
installation. This temporary IP address is only used when booting over the network during
the initial transfer of the kernel client. It cannot be the IP address of an existing machine
within your network, or you will get network errors. Temporary IP addresses can be
provided by your network administrator.
Under Booting Clients, provide an initial range of temporary boot IP addresses that are
part of your domain.
You can add booting IP addresses one at a time, or if you have a contiguous range of IP
addresses you can add the entire range. To add individual addresses, type the address in the
IP: field and click on the Add button. To add a range, type the first address of the range in
the IP Range: field, type the ending address in the To field, and then click on the Add
Range button. In either case, after clicking on the Add or Add Range button, the new IP
addresses appear in the Booting IP addresses scroll list. When finished, click on the OK
button.
In the following example, the temporary IP address range will allow the Ignite-UX to
perform 20 simultaneous installations.
15.2.73.1
15.2.73.20
If you need to change these addresses later, you will need to edit the
/etc/opt/ignite/instl_boottab file directly.
NOTE
Do not change the DHCP services settings.
2-16
3BUR001 835R0001 REV C
4.
Select Session Options tab, and ensure that only these items are checked:
–
Confirm new clients
–
Show the welcome screen for the install server
You may wish to de-select the “Ask for customer information”, because this installation
information is more geared to HP and HP distributor-partner manufacturing.
5.
Press the OK button to save the Ignite-UX configuration.
6.
From an HPterm window, as root user, export the Ignite-UX client directory to enable
network installations by entering the command:
exportfs -a
Starting the Installation Process
There is nothing that needs to be done to the target machine to allow it to use Ignite-UX.
The target system can either be remotely controlled by the Ignite-UX server, or from the
consoles display on the target machine.
Rebooting a Target Machine as a Client of the Ignite-UX Server
The Ignite-UX bootsys command is used to perform a target machine system shutdown, and
allow the target machine to be installed from the Ignite-UX server machine.
Select Actions->Boot New Client… from the Actions pulldown menu.
Enter the hostname of the machine you wish to install and press the OK button.
You will then see a dialog window stating that the Ignite-UX server is going to reboot the target
machine.
If you get the message “The target system “hostname”, is not allowing
root remsh access by you root@”hostname"”, answer y to the question “Would
you like bootsys to set the .rhosts file on that system at this
time? ([y]/n)” and then enter the root password for the target machine at the Password
prompt.
NOTE
If you get an error message stating that the Ignite-UX server can not lookup the IP
address of the target machine, you will need to edit the /etc/hosts file and
add a line for the target machine.
Within a few minutes you will see the target machine appear as a client in the Ignite-UX
window.
3BUR001 835R0001 REV C
2-17
Manually Rebooting a Target Machine as a Client of the Ignite-UX Server
If the target machine is not responding to the Ignite-UX Server, you may need to manually
reboot the target machine.
1.
Reboot your target station and stop the boot process when prompted to do so. Do this by
continually pressing <ESC>. On some architectures there is a very short window of time
to complete this operation.
NOTE
If you see a prompt to select a monitor, ignore it. The local monitor is selected by
default.
2-18
2.
Enter the command to search for LAN boot devices. Specify the LAN address of the Ignite
Server as the boot device. If you see a prompt to interact with IPL, respond by entering n
(no). The station will begin to boot.
3.
In a few minutes you will be prompted to configure the system as follows:
a.
Select a keyboard language
b.
Select Install HP-UX from the menu
c.
Select Remote graphical interface running on the Ignite-UX server
4.
In a few moments the install process will search for a DHCP server for networking
information, interrupt this process by pressing <CTRL-C>.
5.
At the next screen fill in the target machine’s specific information. The information
entered is:
–
Hostname
–
IP Address
–
Default gateway routing internet protocol address
–
The subnet mask
–
IP address of Ignite-UX Server
6.
Answer N to the question if this information is only temporary.
7.
Select OK and in a few minutes the target machine will appear as a client in the Ignite-UX
GUI running on the Ignite-UX Server machine.
3BUR001 835R0001 REV C
Selecting a Client to Load the HP-UX 10.20, AdvaCommand, and Options
Select the client you wish to install, and then select Actions->Install Client->New Install from
the Actions pulldown menu.
1.
2.
Using the Basic tab, choose which Environment you will load. Your choices are:
–
AdvaCommand Station
–
AdvaCommand Station with AdvaBuild option
–
AdvaCommand Station with AdvaInform option
You MUST select the Standard LVM file system unless you have a 2 Gbyte system and
you do not plan to install the Environment Builder with Oracle runtime product, in which
case you must select the Minimum LVM file system. If this in not done properly, your
disks will NOT be sized correctly and the load will fail.
For all stations except AdvaCommand without Environment Builder options select the
Standard LVM by double-clicking on the text. You will see the cursor change to an hour
glass cursor momentarily. If you don’t see the cursor change, double-click on the text
again. If you are not using the X-window GUI, you can reselect the “Standard LVM” file
system by pressing <Tab> until the Standard LVM text is highlighted, and press
<Return> twice. For 2 Gbyte systems running AdvaCommand without Environment
Builders select the Minimum LVM text.
NOTE
Once the necessary disk space is allocated for the selected software, the install
utility allocates the remaining disk space to the /home logical volume, up to a
maximum of 2.5 Gbytes. Any additional drive space is not used. If you need
additional disk space at a later time, the unused disk space can be allocated to a
logical volume using Sam.
3.
Using the Software tab, select ALL from the Category frame and choose the products, if
any, that you wish to load.
The choices and descriptions are:
–
Envir. Builder with Oracle runtime
Select this option if you plan to build environments and graphics at other systems and
install them using the Central Administration features.
–
B4474EA_APZ - HP Netstation 8.0/7.1
HP Netstation should be selected if X-terminals are used as part of AdvaCommand.
This option only sizes disk partitions, the Netstation software needs to be purchased
and separately installed (see Section 2.2.7.4, Loading HP Netstation Software) to
operate X-terminals.
–
B3691AA_APZ_TRY - Trial HP GlancePlus/UX for s700 10.20
GlancePlus is a system performance monitor. This is a trial product only.
–
3BUR001 835R0001 REV C
Ignite-UX-10-20 - HP-UX Installation Utilities for
Installing 10.20 Systems
2-19
This is the HP ignite server software. This option should be selected if you plan to
use this station as an Ignite server to load software onto client stations over the
network, or if you plan to do full station backups for client machines over the
network (see Section 5.2, Full Station Backup/Recovery for AdvaCommand Stations
1.6/1 or Later).
–
J2559C - Hewlett-Packard JetAdmin for Unix Utility
This is the HP patch for network printers. Load this option if you plan on using HP
network printers from this station.
4.
–
ABB-AB-MODEXP - Select this product if you want the AdvaBuild starter project.
–
HW-Enablement - Hardware enablement patches (ACE). This is selected for you
depending on your workstation hardware.
–
ABB-AI-SQLCONN - AdvaInform SQL*Connect option. Select this product if you
purchased the AdvaInform SQL option.
–
ABB-AI-SPC - (MOD) AdvaInform SPC option. Select this product if you
purchased the AdvaInform SPC option.
–
ABB-AI-REPORTS - (Advant) AdvaInform Reports option. Select this product if
you purchased the AdvaInform Reports option.
–
ABB-AI-PDL - (MOD300) AdvaInform PDL option. Select this product if you
purchased the AdvaInform PDL option.
–
ABB-AI-HISTORY - (Advant) AdvaInform History option. Select this product if
you purchased the AdvaInform History option.
Using the System tab, enter the machine specific system parameters. The information
entered is:
–
Hostname
–
IP Address
–
Subnet mask
–
Time and Date information
–
Time Zone
–
Root Password
–
Network Services - Under the Static Routes tab (ask network administrator for
values, or use the values below):
Destination: default
Gateway IP Address: Check with your network administrator for the address (Central
Administration functions require this)
Destination Hop Count:1
Select ADD followed by <Enter>. Once you see the gateway address in the window,
select OK.
2-20
3BUR001 835R0001 REV C
5.
Using the File System tab, you can check to make sure your disk(s) are large enough to
accommodate software selections. If the Avail: megabytes field is a negative number, the
disk(s) are too small for all the software that you are loading.
The projected sizes of each logical volume can be viewed. You may change the sizes of
logical volumes, but it is not recommended, unless you are installing the Traditional
Chinese filesets. If you are installing the Traditional Chinese filesets, you will need to
increase the size of the /usr LVM by at least 150 Mbytes. To do this, perform the
following steps:
a.
Select the File System tab.
b.
Scroll down to the /usr LVM and increase its size by at least 150 Mbytes.
c.
Select modify.
d.
View the sizes of the other LVMs to ensure that your disk(s) are large enough to
accommodate your software selections.
e.
Select OK.
WARNING
The volumes are sized for selected software, future software, maintenance, and
debugging. If LVM sizes are changed for reasons other than installing the
Traditional Chinese filesets, the software load may fail, Advant applications may
fail, and the system may have a reduced troubleshooting capability.
Any changes in LVM sizes are automatically rounded to even 4 megabyte increments.
6.
Select GO! to start the installation.
There is another screen that will give WARNING and/or ERROR messages. Pay careful
attention to all the messages before you select the next GO! operation.
NOTE
Remember the previous warning at the beginning of this section.
7.
If your station has the AdvaBuild options, reboot your station by opening an HP terminal
window, and entering:
shutdown -r -y 0
All software is now loaded and the AdvaCommand Startup Interface will be displayed
(refer to Section 2.4.1.1, AdvaCommand Auto Startup) on the target machine. The amount
of time varies based on your station type and CD-ROM drive.
8.
Check the file named /var/adm/sw/swagent.log for any error messages.
NOTE
Error messages for the PHCO_14734 fileset can be ignored.
3BUR001 835R0001 REV C
2-21
WARNING
The Advant Station programs are protected by copyright law and international
treaties. Before you install any of the options on your station, you must verify that
you have acquired the right to use that particular option on your station and have
received the Software Certificate authorizing such use.
2.2.7.4 Loading HP Netstation Software
If you plan on having X-terminals connected to this station, you must install Netstation
software. There are currently two supported versions of Netstation, versions 8.01 and 9.01. The
loading instructions are included with your Netstation software.
For version 8.01, follow the Netstation loading instructions supplied with the media. In this case
you can ignore the rest of this section.
For version 9.01, you must load only 4 of the 8 subproducts/filesets provided on the Netstation
media. You can follow the Netstation instructions that are included with the media, but before
you load the software, make sure to follow the instructions below:
1.
Insert the Netstation 9.01 media into the drive.
2.
In the swinstall program, double-click on B4474FA Netstation 9.01
3.
Double-click on netstation. You will see 8 subproducts/filesets.
4.
Mark only the 4 subproducts/filesets listed below for loading:
HPXT2-ADM
HPXT2-BASE
HPXT2-FONTS
HPXT2-UNSUPP
To mark a subproduct/fileset for loading, click on it with mouse button 1, then click on it
with mouse button 3, and then select the mark for loading option.
5.
After loading the software, you can verify how much disk space Netstation has used on
your station, by typing the following commands:
cd /opt/hpxt/enware2
du -s
This command reports the number of blocks. You can divide this number by 2000 to get
the number of Mbytes.
For Netstation 8.01 (all filesets) there should be 188,076 blocks or approximately 95
Mbytes.
For Netstation 9.01 (4 filesets) there should be 52,926 blocks or approximately 26 Mbytes.
2.2.7.5 Log File Update
Whenever a revision or patch is installed on a system, you should edit the text file
user_update.log found in the /var/adm/sw directory. At the end of the file, add the
2-22
3BUR001 835R0001 REV C
Section 2.2.8 Post Installation Work
revision or patch 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.7-1.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.
2.2.8 Post Installation Work
This section applies to all clean installations and existing installations where data is being saved
and restored.
2.2.8.1 Pre-Conditions
To begin the post installation work, the station must be running, and be on the Login Display.
AdvaCommand Default Environment
Each Station running AdvaCommand Basic Functions software has a default Environment
named “ADVANT.” Its user is ADVANT, and the password is MOD.
Load the ADVANT Environment and login.
AdvaBuild Default Environment
Each Station with the AdvaBuild options software has a default Environment named “ES.” The
ES environment is an AdvaCommand environment which controls access privileges to
AdvaCommand functions. The environment prohibits you from using the AdvaCommand
runtime displays, but permits you to use RDP displays and external applications in
AdvaCommand.
NOTE
If the DCN address for the node has not been set before installation of the
AdvaBuild Version 2.7/3 software, the ES default environment will be created
with the default address of 0100 for RDP functions. If you want this environment
to use your node address, delete that environment (via the AdvaBuild
Environment Builder) and run the create program again.
/opt/advant/ES/bin/create_es_default_env
HP Terminal
In the following post installation procedures, you need an HP terminal to perform much of the
work.
You can access an HP terminal by selecting HPTerm from the External Applications area of the
Display Menu.
3BUR001 835R0001 REV C
2-23
2.2.8.2 Setting Initial HP-UX Passwords
The root password is set during HP-UX installation.
You should set the passwords for the three other HP-UX user accounts: ocsmgr, poweroff and
operator. To set the passwords, log on as root from an HP terminal, and enter the following
command for each user account:
passwd ocsmgr <Return>
passwd poweroff <Return>
passwd operator <Return>
You will be prompted for the password, and password confirmation
AdvaBuild Unix IDs
Unix user IDs have changed. Users mod and cape have been replaced by operator and
ocsmgr, respectively.
2.2.8.3 Considerations for Printer Support
If you want to configure a printer, use the SAM utility. The system default printer will be used
as the primary print destination by the Structure Builder, Report Writer, and Function Chart
Builder functions.
2.2.8.4 Additional Post Installation Work
You may have to do additional post installation work after the software is loaded. Only some of
the following sections may be applicable, depending on your configuration:
•
Section 2.2.14, Installing the Serial Expansion Unit (SEU)
•
Section 2.2.15, Installing the Touchscreen
•
Chapter 3, Configuration/Application Building
2.2.8.5 Customized Memory Pool Restoration
If you have customized RTAB memory pools for your station, you should have made note of
their sizes as directed in Section 2.2.3.2, Customized Memory Pool. The memory pool utility
should be run as described in Section 3.6.23, Memory Pool Utility (mputil) to restore the
customized sizes. This may not be necessary if additional memory was added to the RTAB as
part of the upgrade. In that case, standard memory pools may be sufficient and no customizing
may be needed. If the amount of RTAB memory is still the same, the utility should be used to set
the pool sizes as close as possible to their pre-upgrade values.
2.2.9 AdvaInform Post Installation Work
This section applies to AdvaInform clean installations and existing installations where data is
being saved and restored.
2-24
3BUR001 835R0001 REV C
Section 2.2.10 AdvaCommand Data Restore Information
2.2.9.1 Operator Station with AdvaInform Options OMF config.cfg File Update
This section applies only to a clean installation of an Operator Station with AdvaInform options.
If you are installing over and existing Operator Station with AdvaInform options, and are saving
your AdvaInform data, skip this section and remember to do Section 5.4.6.2, Restoring Shared
Memory Sizes, when you do your post upgrade work.
If you are doing a clean installation of an Operator Station with AdvaInform options, you need
to increase your OMF shared memory allocation value to14336 Kbytes.
1.
To define the OMF memory size, bring up the AdvaCommand Auto Startup window and
enter 14336 into the OMF Shared Memory field. Refer to Section 2.4.1.1, AdvaCommand
Auto Startup for more information.
2.
Restart the station
2.2.10 AdvaCommand Data Restore Information
If you are installing over an Advant Station with AdvaCommand 1.6/0, with/without AdvaBuild
or AdvaInform options, you must restore your AdvaCommand data as described in Section 5.4,
AdvaCommand 1.6/0 and Later Application Backup/Restore. If you are doing a new
installation, skip this section.
2.2.11 AdvaBuild Restore Data Information
The following procedures need be performed for each project:
NOTE
You must use the same DAT drive to restore data as was used to backup data.
2.2.11.1 Create Project Body
To create the project body (or bodies):
1.
Open an HPterm window, and log in as user ocsmgr by entering: su - ocsmgr
2.
3.
Log in to the Administration application as user admin (default password is admin).
4.
When the Administration window is opened, select the Menu function (or press <f5>) to
access the menu bar.
5.
Choose Projects from the Administer menu.
This opens the Projects window.
6.
3BUR001 835R0001 REV C
Select the Menu function to access the Projects window menu bar.
2-25
7.
Choose Insert from the Edit menu.
This displays the Insert Project dialog box with the cursor located in the Project Name
field.
8.
Enter the Project Name recorded at the time the project was saved to tape in step 4 of
Section 2.2.5.4, Record Project Information, and then press <Return> or <Tab> to move
the cursor to the Project No (Number) field.
9.
Enter the Project Number recorded at the time the project was saved to tape in step 4 of
Section 2.2.5.4, Record Project Information, and then press <Return> or <Tab> to move
the cursor to the Project Size field.
NOTE
You must use the old project number that was previously recorded.
10. Enter the project size recorded at the time the project was saved to tape in step 4 of Section
2.2.5.4, Record Project Information, and then press <Return>.
The default size is 50 M. To use the default, simply press <Return> or <Tab> to move the
cursor to the Comment field. If the size you enter is smaller than the source project, the
size is adapted automatically after the name of the source project is entered.
11. Enter a project comment if desired.
The comment is displayed in the top-most object in the Structure Builder tree presentation.
This field is optional. If you do not want a comment, simply press <Return> or <Tab> to
move to the next field.
12. Enter a project description (up to three lines) if desired.
The project description is optional. If you do not want a description, simply press
<Return> or <Tab> to move to the next field. You may have to press <Return> or <Tab>
three times (once for each line in the Project Description field). This moves the cursor to
the CFG-Password field.
13. Define passwords for the project’s two default users.
For each new project, two default users are created: a user <project>_CFG and a user
<project>_RDR. The CFG and RDR user names cannot be changed. Only the passwords
can be modified.
The name and default password for the CFG user is <project_name>_CFG. This user
(group 2 = CFG) owns all project tables and can configure Oracle Reports 2.5. The name
and default password for RDR user is <project_name>_RDR. This user has read-only
access to the project.
a.
Enter a new CFG password or accept the default by pressing <Return>.
This moves the cursor to the RDR-Password field.
b.
Enter a new RDR password or accept the default by pressing <Return>.
This moves the cursor to the Copy from Project: field.
2-26
3BUR001 835R0001 REV C
Section 2.2.11 AdvaBuild Restore Data Information
14. Enter the name of the source project that you want to use as the basis for the new project,
and then press <Return>.
You can display a list of valid project names to be used as source project by pressing List.
When the source project has been entered, the size is checked. If the size entered is too
small for the source project, the size is adapted to be at least as big.
15. Press <Return>, to move the cursor to the Protect Project Y/N field.
16. Protect the project against read-access from other projects if necessary.
The default entry for the Protect Project field is N = No. This means the project is not
protected against read access from other projects.
If you want to prevent users of other projects from copying parts of your project to their
own, choose Y = Yes. You can toggle the protection mode via the Edit-Modify menu item
as described in the AdvaBuild Basic Functions User’s Guide.
17. Press <Return> to move the cursor over the OK target at the bottom of the dialog box.
18. Select Accept/Save.
This starts the insert project function and displays a message box. The message asks you to
wait (minimum 15 minutes depending on the amount of data to be copied and the load and
performance of the machine).
When the function is finished, this message box is removed and another box is displayed.
This message indicates whether or not the function was successful. This message must be
acknowledged by clicking OK.
In either case, the logfile provides a detailed description of the function. The logfile
inspro_<project>.log resides in the directory pointed to by the environment variable
$C_CAPE_ALL_ADM_LOG.
If the project has been successfully inserted (created), close the Projects window and create any
additional users that had existed for each project at the time the project was saved to tape. The
project restore will not recreate them. See Section 2.2.11.2, How to Create Additional User(s)
for a Project.
After the project is created, configure the PROJECT object attributes (CUSTOMER,
PRO_LEADER, RESP_DEPT, REVISION…) via the Template Builder. This is required
because the PROJECT object in release 2.7/3 will not be modified by restoration of data from
the previous release.
2.2.11.2 How to Create Additional User(s) for a Project
When you create a project, two default users are assigned automatically: a configuration user
<project>_CFG of user group 2 = CONFIG with special access rights, and a reader user
<project>_RDR of user group 4 = READER with read-only access to the project.
The configuration user has unrestricted access to all project data and can configure Oracle
Reports.
In addition to the default users, you can assign writer users (user group 3 = WRITER) to do
most of the actual database configuration work.
3BUR001 835R0001 REV C
2-27
NOTE
Directories that contain data associated with the original users will be restored
with the project data. These directories are found in the $C_CAPE/my_proj/usr/
path. If a user (that existed when the project was saved) does not exist at the time
of the project restore, the directory associated with that user will be renamed. If at
a later time the user is recreated, the data in the renamed directory can be moved
back into the new user directory.
To create additional user(s) for a project:
1.
Log in to the Administration function if you are not already logged in.
2.
Choose User from the Administer menu in the Administration window.
This opens the Users window.
3.
Select the Menu function to access the Users window menu bar.
4.
This displays the Insert User dialog box.
5.
Enter the user name recorded at the time the project was saved to tape in step 4 of Section
2.2.5.4, Record Project Information, and press <Return>.
The logfile name is filled in automatically, using the user name.
6.
Enter the password recorded at the time the project was saved to tape in step 4 of Section
2.2.5.4, Record Project Information, and press <Return>.
NOTE
User name and password should start with a letter and continue with letters, digits
or ‘_’ (underscore). Do not use any special characters like @, # or +.
7.
Enter the appropriate group number recorded at the time the project was saved to tape in
step 4 of Section 2.2.5.4, Record Project Information, to establish the access level for the
user.
Usually, group 3 = WRITER is chosen for a normal project user, but you can also select 4
= READER to create a user with read-only access or 2 = CONFIG for a user with special
configuration privileges. The corresponding group name is entered automatically.
8.
Assign the user to a specific project.
a.
Press <Return> to move to the next field.
b.
Enter the project number recorded at the time the project was saved to tape in step 4
of Section 2.2.5.4, Record Project Information (as shown in the Pro No column in the
Projects window).
c.
Press <Return>.
The corresponding project name is entered automatically, and the cursor is moved to
the OK target on the bottom of the dialog box.
2-28
3BUR001 835R0001 REV C
Section 2.2.11 AdvaBuild Restore Data Information
9.
Select Accept/Save.
This starts the insert user function and displays a message box. The message asks you to
wait for the function to complete. When the function is finished, this box is removed and
another box is displayed. The new box indicates whether or not the function was
successful. This message must be acknowledged by clicking OK.
In either case the log file provides a detailed description of the insertion process. The log
file insusr_<user>.log resides in the directory pointed to by the environment variable
10. Repeat this procedure for as many users as required.
2.2.11.3 Restore Project Data
To restore/upgrade the project data for each project previously saved to tape:
Insert the tape containing the backed up project data and start the restore/upgrade project script
“upgrade_project.sh” for each project separately as follows:
1.
Log in as user ocsmgr, if not already logged in, by entering: su - ocsmgr
2.
Make sure you are in the /home/ocsmgr directory.
3.
Insert the tape that holds the project data.
4.
To restore/upgrade a project, enter:
restore_project.sh -p <project> 2>&1 | tee $C_BIN_CAPE_LOG/rest_<project>.log
5.
After restoration of the project is complete, remove the tape.
6.
Check the log file $C_BIN_CAPE_LOG/rest_my_proj.log for errors.
7.
Repeat step 3 through step 6 until all your projects are restored/upgraded.
Oracle warnings (imp-00033) could appear in the restore_project.sh log file for
tables that are new in the AdvaBuild 2.7/3 release. These can be ignored.
NOTE
This process will also restore the TCL and user-specific data that was stored
beneath each project directory.
3BUR001 835R0001 REV C
2-29
2.2.11.4 Post Project Data Restore Procedure
1.
2.
Invoke the following command for each project restored (project name needs to be all
uppercase):
ABB-PESU_273000.sh -P <PROJECT_NAME>
NOTE
If you see the following command error message, it can be ignored:
rm: /home/opt/advant/es/proj/proj_adm/fcb/mod/PC_LIB/* not existent
2.2.11.5 Restore FMS-specific Files
Use the utility USER_FMS_RESTORE to restore FMS application files including Batch 300,
Taylor Ladder Logic, Taylor Control Language (generated via Multibus-based TCL editor),
diagnostic message archive, and installed MOD 300 database, from DDS tape. Refer to Section
5.6.2.2, User FMS Backup and User FMS Restore for more information.
2.2.12 Loading Software to MOD 300 Subsystems
NOTE
Prior to loading software to MOD 300 Subsystems, make sure the Advant Station
has been rebooted (that is, shutdown and restarted). Refer to Section 2.3,
Shut-down Procedures and Section 2.4, Start-up Procedures for information on
how to reboot the Advant Station.
During the following steps you load software into the MOD 300 subsystems.
The software installation procedure must be performed for each Configurator Data Processor
(CDP) node and Remote Data Processor separately, one domain at a time. Note that a Batch
node is a remote Data Processor.
It is not necessary to do a Database compile from the top. If a top down compile is ever done in
the Database Configurator, use the COMPILE WITH SAVING LREFS option (this option is
under the “SERVICE” SOFTKEY). If a COMPILE WITHOUT SAVING LREFS (default) is
done and there are multiple CDPs, the System ID changes and the other databases are rendered
incompatible. The databases must then be recompiled, exported, installed, and rebooted.
Multibus Subsystems
Reboot all Multibus Subsystems (for example, Consoles, Gateways, D-to-D nodes) within the
current CDP’s domain.
2-30
3BUR001 835R0001 REV C
Section 2.2.12 Loading Software to MOD 300 Subsystems
2.2.12.1 Controllers
The procedure depends on whether the controllers can be taken off-line and rebooted.
•
If all the Controllers can be rebooted, reboot them now, and no further steps are required.
•
If any Controllers cannot be rebooted, use the instructions below to upgrade the controllers
on-line.
On-line Upgrade of Model A/B and SC Controllers
The Engineering Station should already be upgraded with On-line Builder software prior to
upgrading Controller software.
1.
Terminate redundancy in Controller #n; verify that the Redundancy Status is
“TERMINATED” and P-Bus Status is “DOWN”.
2.
Re-establish redundancy and verify that the Redundancy Status goes “ACTIVE”.
3.
Reboot the Backup Controller, and wait until its Node Status goes to “READY”.
4.
For any Model A/B or SC Controllers that CAN be rebooted, terminate redundancy, and
do a hard reset on the controller.
NOTE
For the remaining controllers that CANNOT be rebooted, the following steps
must be performed.
5.
The Redundancy Status of Controller #n should be “ACTIVE”. If it is not, manually
establish Redundancy.
6.
Failover Controller #n from the Console.
7.
Verify that the Redundancy Status of the Backup Controller is “EMULATING”.
8.
After Controller #n reboots and its Redundancy Status goes to “READY”, wait 20
seconds.
9.
Switch back to Controller #n.
10. Wait until the Backup Controller reboots and its Redundancy Status goes to “READY”.
11. Wait 20 seconds, then go to step #3, and repeat for the next controller.
On-line Upgrade of AC-460 CPUs
The AC 460s can be upgraded on a per subsystem basis and can be done without shutting down
the entire system. All modules of the same type, within a subsystem, must be at the same
revision level.
The reason to perform an on-line software upgrade is to upgrade an AC 460 controller(s) with a
new revision of software without taking the controller “off-process”. This procedure is intended
to support software upgrades within a major release level (for example, all V14 releases).
The only display involved is the AC 460 Subsystem Status Display. The dialog boxes allow the
“resets” and “switchovers” of selected controllers. An overview of the steps are:
3BUR001 835R0001 REV C
2-31
1.
Install “new” AC 460 controller software onto an Engineering Station.
2.
The backup controller Processor Module is put into the “UPGRADE” mode through the
AC 460 Subsystem Status Display.
3.
Wait for it to re-boot with new controller software (by watching status on the AC 460
Subsystem Display).
4.
Issue a “SWITCHOVER” to newly-booted controller Processor Module via the AC 460
Subsystem Display.
5.
Repeat step 2 through step 4 for other controller Processor Modules as needed.
NOTE
This functionality is NOT INTENDED to be used as an alternative redundancy
scheme.
Only AC 460 controllers support on-line software upgrades.
The procedure can only be performed through Advant Operator Stations.
The switchover portion of the upgrade procedure can only be performed on one (1) AC 460
controller in a subsystem at a time. The reason for this is to keep the switchover time as small as
possible.
There is a brief period in time during the “switchover” that process inputs are not scanned, and
process outputs are not updated and are held at their current values. That period is estimated to
be no greater than 4 seconds.
During the backup controller “switchover” any MVIs (CI532 or CI537) attached to that
controller will reset and restart. Any device connected to these MVIs will temporarily loose
communications for up to 30 seconds before re-establishing normal communications. Make sure
all devices connected to MVIs are in a safe state and can tolerate the temporary loss of
communications.
The detailed procedure for performing an on-line AC 460 software upgrade is described in the
following steps. It assumes that there is a redundant pair of AC 460 controller Processor
Modules available, where one is acting as the primary, and the other is the backup.
2-32
1.
Install the new version of MOD300 software for the AC 460 controllers in the applicable
Advant Engineering Station. It is necessary to do this prior to performing the upgrade
procedure.
2.
Invoke the AC 460 Subsystem Status Display and select a backup controller that is to be
rebooted in the “upgrade” mode. This in turn brings up a dialog box with a set of
push-buttons. Select the RESET for UPGRADE push-button to indicate that the backup
is to be rebooted into the “upgrade” mode. The command requires confirmation before it is
actually sent to the backup controller. To do so, select the EXECUTE push-button.
3.
The backup controller is then rebooted. At this time, it receives a program download of the
new AC 460 software. The fact that the backup controller was rebooted using the RESET
for UPGRADE command signifies that on reboot the controller will come up in a state
where it can become the primary controller by simply transferring the primary controller’s
database to itself.
3BUR001 835R0001 REV C
Section 2.2.12 Loading Software to MOD 300 Subsystems
4.
A controller in this state is said to be in the “ready for upgrade” mode or state. The state of
the backup controller will be “UPGRDE” on the AC460 Subsystem Status Display at this
time. The 7 segment LED display on the backup controller will contain the value “UP”
when it is in the “ready to upgrade” state.
NOTE
If a primary controller fails, a backup controller in the “UPGRDE” state
will NOT takeover as the primary controller.
5.
The operator can then request a “switchover” of the primary controller to the backup
controller in the “ready for upgrade” state. This is done by selecting the backup controller
that is to be “switched over”. This brings up a dialog box with a set of push-buttons. Select
the SWITCHOVER push-button to indicate that the primary is to be switched over to the
backup. The command requires confirmation before it is actually sent to the primary
controller. To do so, select the EXECUTE push-button.
NOTE
Prior to doing the “switchover” during an on-line upgrade, make sure all devices
connected to MVIs are in a safe state and can tolerate the temporary loss of
communications.
6.
The primary controller receives the “switchover” request from the operator, ensures that its
database is in a consistent state, and issues a request to the backup controller to switchover.
The backup controller then transfers the primary controller’s database into its own
memory via the FB+. During this time:
–
The database is NOT accessible to external nodes. This means that external database
accesses to the controller may momentarily fail while it is going through the database
transfer process.
–
Any process I/O outputs are held at their current output values until the upgrade
process is complete.
–
Any I/O watchdog timers are refreshed by the upgrade software to ensure that the
outputs do not go to their default values (S100, S800 and TRIO I/O) during the
switchover period.
When the transfer process is complete, the applications are restarted in the backup controller
(now using the primary controller’s database). The backup controller resets the “old” primary
controller, and the upgrading process is now complete.
Push-buttons on AC460 Subsystem Status Display
A set of controller command push-buttons are available in a dialog box below the AC 460
Subsystem Status Display. There are three (3) command push-buttons and two (2) confirmation
push-buttons within the box. All push-buttons are dimmed until a primary or backup controller
is selected. At this point, the controller selected is highlighted, and the command push-buttons
become accessible. They allow the operator to issue various commands to the controller in order
to perform the desired software upgrade. When a command push-button is selected, the
confirmation push-buttons become accessible. The descriptions for the push-buttons follows:
3BUR001 835R0001 REV C
2-33
The RESET for UPGRADE push-button is used to reset a backup controller and reboot into
the “UPGRDE” state. The following restrictions apply for this command:
•
If the dialog box was invoked from a primary controller, the RESET for UPGRADE
push-button cannot be selected. This prevents primary controllers from being reset by an
operator.
•
The command is not actually sent until the EXECUTE push-button is selected.
•
The CANCEL push-button can be used to clear the SWITCHOVER
The SWITCHOVER push-button is used to force the switchover of a primary controller to a
backup controller (that is loaded with a different version of software). The following restrictions
apply for this command:
•
If the backup controller is not in the “UPGRDE” state, the SWITCHOVER push-button
cannot be selected in the dialog box. This prevents switchover from being attempted for
backup controllers that are not in the correct state.
•
A five (5) second delay after selection of this push-button occurs before other push-buttons
can be selected. This prevents switchover of different controllers in the same AC 460
subsystems from overlapping.
•
•
The CANCEL push-button can be used to clear the fact that this push-button was selected.
The HARD RESET push-button can be used to reset any controller on the AC 460 subsystem
display. Resetting a controller through this push-button has the same effect as depressing the
“Enter” button on the controller’s front panel.
CAUTION
This bottom must not be used during the on-line upgrade procedure.
The following restrictions apply for this command:
•
•
The CANCEL push-button can be used to clear the fact that this push-button was selected.
Because there is a need to prevent inadvertent selection of a push-button from causing
unintended controller resets and switchovers, the EXECUTE push-button is used to provide a
confirmation process for the “RESET for UPGRADE”, “HARD RESET”, and
“SWITCHOVER” functions. The actual reset or switch request is not sent until the EXECUTE
push-button is selected. The following restriction applies for this command:
•
This push-button is dimmed until one (and only one) of the SWITCHOVER,
HARD RESET, or RESET for UPGRADE buttons has been selected.
The CANCEL push-button is used to clear the fact that any other push-button was selected. It is
also used to de-select the controller for which the push-buttons applied.
2-34
3BUR001 835R0001 REV C
Section 2.2.13 AdvaInform History Data Restore and Upgrade Information
2.2.13 AdvaInform History Data Restore and Upgrade Information
If you backed up AdvaInform History data because you installed AdvaCommand 1.7/1 with
History options 2.3 over an Advant Station with AdvaCommand 1.6/1 or later with AdvaInform
History 2.2 or later, you can restore and upgrade your History data as follows (to restore only,
see Section 5.9.1.2, Restoring History Data):
1.
Shutdown the AdvaCommand software by typing <Ctrl-D> and entering quit in the
dialog.
2.
Select the Suspend button on the AdvaCommand Auto Startup Sequence window.
3.
Select Yes next to Would you like to start a HPterm window and login as operator.
4.
Insert the tape with the saved History files into tape drive.
5.
Run the conversion routine to bring the History data and configuration to the proper format
for the new version.
/opt/advant/History/bin/UpgradeHistory
2.2.14 Installing the Serial Expansion Unit (SEU)
2.2.14.1 Before You Install the Device Driver
You should wait to install the scsiTerminal Server (STS) hardware until after you have
completed the Operator Station software installation. The supplied software includes utilities
that are helpful in identifying SCSI devices already present on your system, and in selecting the
proper SCSI ID for the new STS unit(s).
The HP-9000 Series 700 device drivers and all associated files are contained on the DAT tape.
You must be able to log in as root (superuser) to perform the installation. If you do not have root
permissions, talk to your system administrator.
2.2.14.2 Installation Prerequisites
Required:
•
Operator Station
•
Serial Expansion Unit (SEU)
•
HP DAT Drive
•
High-density to high-density SCSI cable
•
Low-density to high-density SCSI cable
•
Low-density SCSI terminator
2.2.14.3 Installation Instructions
The following procedure describes how to install the software from the release media.
3BUR001 835R0001 REV C
2-35
1.
Suspend the Auto Start Interface. Select a HPterm window from the Auto Start Interface.
Log in as a superuser.
2.
From the home directory, make a directory to contain the SEU software, then change to
this directory. For instance, if you are in your home directory you would type:
mkdir /usr/sts
cd /usr/sts
3.
Insert the release DAT tape into the DAT drive. Wait for the lights on the DAT drive to stop
blinking.
4.
Extract the SEU installation software by typing the command:
tar xvf /dev/rmt/0m
The following file will be unloaded into the subdirectory: hp4012.shar of the directory
created in step 2 (for example, /usr/sts)
Remove the release DAT tape from the DAT drive.
5.
Execute the command:
sh hp4012.shar
6.
In response to the following question shown in the HPterm window:
Have you previously read and agreed to the terms of Central
Data’s Data License Agreement?
Yes/No/Display license? (y/n/D):
Enter: y
7.
Press the space bar several times while scrolling through the packing list. This list
contains files and pathnames about to be loaded on the Operator Station.
8.
In response to the following question shown in the HPterm window:
Begin extracting files from this SIS file? (y/N):
Enter: y
9.
In response to the following question shown in the HPTerm window:
Begin the installation procedure? (y/N):
Enter: y
10. In response to the following question shown in the HPterm window:
Desired base directory (default is /usr/local/STS):
Press: <Enter>
Desired bin directory (default is /usr/local/bin):
Press: <Enter>
Desired man directory default is /usr/local/man):
Press: <Enter>
The SEU software will now load, and the kernel will be rebuilt.
Do you wish to shutdown the system?
Enter: y
2-36
3BUR001 835R0001 REV C
Section 2.2.14 Installing the Serial Expansion Unit (SEU)
14. Switch the Operator Station OFF after the following message is displayed:
Halted, you may now cycle power
15. Connect the high-density to high-density SCSI cable from the Operator Station to the
SEU. Connect the low-density to low-density SCSI cable from the SEU to the HP DAT
drive. Connect the low-density SCSI terminator to the HP DAT drive.
CAUTION
Always shut down the Operator Station before adding or removing any SCSI
cables. Login as a superuser and execute the following command to shut down the
Operator Station:
/etc/shutdown –y –h 0
Switch the Operator Station OFF after the “Halted, you may now cycle power”
message. Then change any SCSI cables and switch the Operator Station ON as
described in Section 2.4, Start-up Procedures.
16. Switch the Operator Station ON.
17. If all goes well, messages such as the following are scrolled on the screen during bootup:
Central Data scsiTerminal driver (R*.00*) configured
CenData ST-1008 (Rev. v*.*) at bus/target = 0/x)
NOTE
For a default SEU, x is set to 4.
18. If the system does not boot, take one or more of the following measures to try to isolate the
problem:
–
Recheck the SCSI cabling and/or swap out SCSI cables.
–
Recheck the SCSI IDs (the SEU is preset to 4).
–
Power cycle the SEU unit(s) (they only read their SCSI ID at power up).
–
Remove the SEU(s) and try booting to make sure the kernel itself is functional.
–
Boot from the backup kernel with the SEU(s) still on the SCSI bus.
–
Remove the SEU(s) AND boot from the backup kernel to make sure the hard drive is
OK.
See Section 2.2.14.4, Booting from a Backup Kernel, for instructions on how to boot from
a backup kernel.
If you are not successful in locating the problem, contact the Technical Support Group via
SUPPORTLINE: in the U.S., 1-800-HELP-365; international, 614-224-5888.
19. If you have successfully booted from the new kernel and have noted the boot time
messages as described above, continue.
Suspend the Auto Start Interface. Select a HPterm window from the Auto Start Interface.
Log in as a superuser.
3BUR001 835R0001 REV C
2-37
20. From the home directory, execute the cdscanbus function to see if the SEU is present on
the SCSI bus. For instance, if you are in your home directory you would type:
cd /usr/local/bin
./cdscanbus
The hpterm window should read:
Target 3: tape
Target 4: comm
Target 5: Disk (optional)
Target 6: Disk
21. If the SEU is not present on the SCSI bus, take one or more of the following measures to
try to isolate the problem:
–
Recheck the SCSI cabling and/or swap out SCSI cables.
–
Recheck the SCSI IDs (the SEU is preset to 4).
–
Power cycle the SEU unit(s) (they only read their SCSI ID at power up).
–
Reboot the Operator Station using the steps as described in Section 2.2.14.2,
Installation Prerequisites.
22. Install the SEU device ports on the Operator Station by typing the commands:
cd /usr/sts
./Install
Do you have a Central Data Etherlite® unit to install? (N/y):
Enter: n
Do you wish to automatically make device nodes? (Y/N):
Enter: y
Do you wish to replace any old nodes? (Y/n):
Enter: y
Central Data scsiTerminal Etherlite® driver installation
complete.
For a default SEU (SCSI ID of 4), the serial device ports listed in Table 2-3 have been
created. Table 2-3 also shows how the serial ports on the back of the SEU correspond to
the Operator Station device drivers.
Table 2-3. SEU Serial Ports Corresponding to OS Device Drivers
SEU port
2-38
OS dialup device
driver
OS local
device driver
X3
/dev/ttyc40
/dev/ttyC40
X4
/dev/ttyc41
/dev/ttyC41
3BUR001 835R0001 REV C
Section 2.2.14 Installing the Serial Expansion Unit (SEU)
Table 2-3. SEU Serial Ports Corresponding to OS Device Drivers (Continued)
X5
/dev/ttyc42
/dev/ttyC42
X6
/dev/ttyc43
/dev/ttyC43
X7
/dev/ttyc44
/dev/ttyC44
X8
/dev/ttyc45
/dev/ttyC45
X9
/dev/ttyc46
/dev/ttyC46
X10
/dev/ttyc47
/dev/ttyC47
The parallel port “X11” on the back of the SEU corresponds to the Operator Station device
driver “/dev/lpC48”.
Use the ‘c’ ports for modem lines. Use the ‘C’ ports for local devices such as terminals and
serial devices.
2.2.14.4 Booting from a Backup Kernel
If you must boot from an old copy of the kernel, do the following. When the Selecting a
system to boot... message is displayed, press and hold the ESC key. It indicates that the
selection process has been interrupted. The message searching for potential boot
devices... is displayed. Again, press and hold the ESC key to interrupt this process.
A short menu is displayed at this point. Select option a to enter boot administration mode. Then
type the command:
boot scsi.X /hp-ux.no_sts
where X is the target ID of the SCSI disk to boot from and hp-ux.no_sts is the name of the
backup kernel.
After a short delay, the following prompt is displayed:
ISL>
At this prompt, type the command:
hpux /hp-ux.no_sts
This loads and runs the backup kernel.
3BUR001 835R0001 REV C
2-39
2.2.15 Installing the Touchscreen
2.2.15.1 Hardware Setup
CAUTION
Always shut down the Operator Station before adding or removing any SCSI
cables. To shut down the Operator Station, log in as a superuser and execute the
command:
/etc/shutdown -y -h 0
Switch the Operator Station OFF after the “Halted, you may now cycle power”
message. Then change any SCSI cables. Do not switch the Operator Station ON
until instructed to do so.
2.2.15.2 SONY Monitor with Elo Touch SAW Touchscreen
Required:
•
SONY monitor IM535, with integrated Elo Touch SAW touchscreen and serial cable
•
Operator Station with AdvaCommand version 1.7/1 software
To prepare the Elo Touch touchscreen for operation:
1.
Connect the video cable of the monitor to the video port on the back of the Operator
Station.
2.
Connect the touchscreen serial cable from the serial port on the back of the monitor to the
serial port on the back of the Operator Station.
3.
Verify that the SONY monitor is plugged in and turned on before attempting to use the
touchscreen.
Configure the Serial Port
The touchscreen serial port must be configured as a direct connect terminal with hardware flow
control enabled. To verify the port is configured correctly, open an HP terminal window, log on
as root, and enter:
ls -l /dev/tty0p0 /dev/tty1p0 <Return>
You should see the following:
crw-rw-rw- 1 bin bin 1 0x000010 <date> /dev/tty0p0
crw-rw-rw- 1 bin bin 1 0x010010 <date> /dev/tty1p0
If the devices files do not exist or are not configured properly, remove the existing files, and use
the mknod command to create a touchscreen device file as follows:
mknod /dev/tty0p0 c 1 0x000010 (for port 0)
or
mknod /dev/tty1p0 c 1 0x010010 (for port 1)
2-40
3BUR001 835R0001 REV C
Section 2.2.15 Installing the Touchscreen
NOTE
Because some touchscreen controllers use modem hardware handshake signals,
the serial port that the touchscreen is to be connected to must also be configured
for a Modem port.
Configure the station to recognize the touchscreen using the on-line System Administration
Manager (SAM) tool. The port you plugged the Touchscreen cable into is the port you will need
to configure in the Station.
SAM Procedure for Configuring Your System to Work With a SONY IM535
Touchscreen
1.
Start an HP terminal window.
2.
Log in to the station as a superuser (root).
3.
Enter: sam <Return>
4.
In the SAM main window, select or highlight the Peripheral Devices-> list item and
activate the Open control button. (The Peripheral Devices window appears, displaying a
list of types of peripheral devices.)
5.
In the Peripheral Devices window, highlight the Terminals and Modems list item and
activate the Open control button. (The Terminals and Modems window appears,
displaying a list of the currently configured terminals and modems.)
6.
To add a modem, pull down the Action menu and choose Add Modem.... The Add
Modem screen appears. Enter the appropriate data in each field.
a.
Select either the first entry for serial port 0, or the second entry for serial port 1.
NOTE
Do not change the Port Number field. It should always be 0.
3BUR001 835R0001 REV C
b.
For Speed (Baud Rate), enter 9600
c.
Select Use Device for Calling Out.
d.
Select Receive In-coming Calls (start getty process).
e.
If you need help completing the screen entries, activate the Help control button. To
get help on a particular data field, put the location cursor on that field and press the
F1 key.
7.
After completing the Add Modem screen, you should be ready for SAM to add the modem
to your system. SAM does this by creating the appropriate device files, and by making a
getty entry in the /etc/inittab file.
8.
When you are ready for SAM to add the modem, activate the OK control button. A
message follows that the device drivers are being added.
9.
Exit SAM.
2-41
Verify that Device Drivers are Loaded and Running
1.
To verify that SAM has created the device drivers, enter:
ls -l /dev/ttyd* /dev/cu*
You should see the following for Serial Port 0:
0x000001
/dev/cua0p0
0x000001
/dev/cu10p0
0x000002
/dev/ttyd0p0
You should see the following for Serial Port 1:
2.
0x010001
/dev/cua1p0
0x010001
/dev/cu11p0
0x010002
/dev/ttyd1p0
To verify that getty is running on port 0 and it is in a pending state, enter:
ps -ef|grep ttyd0p0
3.
You should see something similar to the following:
root 272 1 0 08:23:42 ? 0:00 /usr/lbin/uucp/uugetty -r -t 60 -h ttyd0p0 9600
There should be a “?” in the tty field to show it is pending. If getty is not in a pending
state, the hardware should be checked.
2.2.15.3 SONY Monitor with Elo Touch SAW Touchscreen and SEU
Required:
•
SONY Monitor IM535, with integrated Elo Touch SAW touchscreen and serial cable
•
Operator Station with version 1.7/1 software
•
Serial expansion unit
To prepare the Elo Touch touchscreen for operation:
2-42
1.
Station.
2.
Connect the touchscreen serial cable from the serial port on the back of the monitor to the
serial expansion unit.
3.
Verify that the SONY monitor is plugged in and turned on before attempting to use the
touchscreen.
3BUR001 835R0001 REV C
Section 2.2.15 Installing the Touchscreen
2.2.15.4 Carroll Touch
Required:
•
Touchscreen Monitor
•
Monitor power supply
•
To prepare the Carroll Touch touchscreen for operation:
1.
Station.
2.
Connect the touchscreen serial cable from the serial port of the touchscreen to the serial
port on the Operator Station.
3.
Verify that both the touchscreen and the HP monitor are plugged in and turned on before
attempting to use the touchscreen.
2.2.15.5 Carroll Touch with SEU
Required:
•
Touchscreen Monitor
•
Monitor power supply
•
•
Serial expansion unit
To prepare the Carroll Touch touchscreen for operation:
1.
Station.
2.
Connect the touchscreen serial cable from the serial port of the touchscreen to the Serial
expansion unit.
3.
Verify that both the touchscreen and the HP monitor are plugged in and turned on before
attempting to use the touchscreen.
2.2.15.6 Xtouch Software Installation
Xtouch Software is now delivered on CD or DVD. Use teh appropriate instructions below for
Tape drive or CD/DVD installation.
Starting Instructions for Station with Tape Drive Attached
1.
Log on as root (or use the su command to become superuser).
2.
Insert the proper touchscreen tape into drive 0m and be sure to load SONY touchscreen for
SONY and Carol Touch for other types.
3.
Extract the software from the tape into the /usr/lib/tsi directory by entering
tar -xvf /dev/rmt/0m
3BUR001 835R0001 REV C
2-43
4.
Verify that the files are now under the /usr/lib/tsi and /usr/lib.tsi1
directories by entering ll /usr/lib/tsi*
For Carroll Touch, this should display the following:
./
./xtouch
./setup
For SONY IM535 Integrated Touchscreens, the following should be displayed:
./
./xtouch
./setup
./LICENSE.TSI
5.
Remove the tape from tape drive 0m.
Starting Instructions for Station with CD-ROM or DVD-ROM Reader Attached
These instructions must be performed to prepare the CD-ROM or DVD-ROM reader to load the
Touchscreen software to the local station.
Adding /SD_CDROM with sam
The /SD_CDROM directory must exist before adding this software 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 proceed to Preparing the CD-ROM or DVD-ROM
for Installation.
These instructions must be performed to add the /SD_CDROM directory.
1.
In an HP terminal window, log on as the root user.
2.
Enter sam
3.
Within the SAM Areas window, select Disks and File Systems.
4.
Within the SAM Areas: Disks and File Systems window, select Disk Devices.
5.
Within the Disk Devices window, select CD from SCSI list of devices.
6.
Under the Actions menu item, select ‘Add’ -> Not Using the Logical Volume Manager.
7.
Within the ‘Add CD_ROM Disk’ window, enter /SD_CDROM as the Mount Directory.
8.
In the ‘When to mount’ area, deselect ‘Now’. Leave ‘At every system boot’ selected.
9.
Click OK.
10. Select File -> Exit.
11. Select File -> Exit SAM.
Preparing the CD-ROM or DVD-ROM for Installation
1.
2-44
In an HP terminal window, log on as the root user.
3BUR001 835R0001 REV C
Section 2.2.16 Final Note
2.
Insert the SONY Touchscreen Software CD-ROM into the CD_ROM drive.
3.
Enter: mount /SD_CDROM
4.
Enter: cd /SD_CDROM
5.
Extract the software from the CD onto the workstation by entering:
cp -r -p /SD_CDROM/* /
6.
Verify that the files are now under the /usr/lib/tsi and /usr/lib/tsi1
directories by entering
ll /usr/lib/tsi*
For SONY IM535 Integrated Touchscreens, the following files should be displayed under
both the /usr/lib/tsi and /usr/lib/tsi1 directories:
LICENSE.TSI
setup
xtouch
7.
Enter: umount /SD_CDROM
8.
Enter: chmod 777 /usr/lib/tsi
9.
Enter: chmod 777 /usr/lib/tsi1
10. Remove the CD from the CD_ROM drive.
2.2.16 Final Note
NOTE
You should backup you station immediately after performing an installation. For
instructions, refer to Chapter 5, Maintenance.
If you have any problems or questions with this installation, contact the SUPPORTLINE at
1 (800) 435-7365, or, worldwide at 1 (614) 224-5888.
2.3 Shut-down Procedures
2.3.1 AdvaCommand Software Shutdown
To exit the AdvaCommand software while it is still running:
3BUR001 835R0001 REV C
1.
Press <Ctrl-D> to bring up the command line dialog.
2.
Enter either quit or stopsession in the field, then press <Return>. Below is the
description of the ‘quit’ and ‘stopsession’ commands:
quit
Terminates the AdvaCommand session on the host and all
X-terminal sessions
stopsession
Terminates the AdvaCommand session only on the host or
X-terminal that ‘stopsession’ was executed on.
2-45
This returns you either to the operator login session (if manually started) or to the
Autostart process.
NOTE
You need to have Engineer authority to execute the quit command, and
Operator authority to execute the stopsession command.
2.3.2 Power Down the Advant Station
The workstation can be powered down by two user accounts. One is for the poweroff user
and the other is for the root user.
The concept of the poweroff user is to allow someone to automatically shutdown the
workstation by knowing the poweroff password, but not necessarily knowing the root
password.
If you know the root password, you can issue a shutdown command as illustrated below in
Section 2.3.2.2, Power Down by the Root User.
NOTE
A USB device configuration requires a PS/2 keyboard and mouse be connected.
or the station will not shutdown correctly.
2.3.2.1 Power Down by a Non-Root User
A special user account named poweroff has been created to automatically shutdown the
workstation for all non-root users.
To power down the Operator Station as a non-root user:
1.
Press <Ctrl-D> to bring up the command line dialog. Enter poweroff and then press
<Return> in the command line dialog. An HP terminal window will open and a password
request will be displayed.
-orFrom the Unix command line, enter login -l poweroff <Return>.
2.
Enter the password and press <Return> in the HP Term window.
If the correct password is entered, the station will shutdown.
Some messages will be displayed, ending with the following:
Halted - you may now cycle power
NOTE
The unix passwd command can be used to change the password for the
poweroff account. In an HP Term window, as root user, type passwd
poweroff <Return> and type the new password.
2-46
3BUR001 835R0001 REV C
Section 2.4 Start-up Procedures
3.
When you see the above message, turn power off at the Operator Station and attached
peripherals in the reverse order that power was turned on. That is, turn off the System Unit,
then printers, then the external mass memory system, then the Uninterruptible Power
Supply (UPS), and, finally, the monitor.
WARNING
Do not assume that all power to the computer is off just because the Power
On/Standby switch has been turned off. To completely remove power from your
computer, unplug the power cable from the power outlet, or disconnect that cable
from the power supply.
2.3.2.2 Power Down by the Root User
To power down the Operator Station as the root user:
1.
From an HP Term window, enter su - root and then press <Return>.
2.
At the password prompt, enter the password and then press <Return>.
3.
Enter /etc/shutdown -h 0 and then press <Return>.
Some messages will be displayed, ending with the following:
Halted - you may now cycle power
4.
When you see the above message, turn power off at the Operator Station and attached
peripherals in the reverse order that power was turned on. That is, turn off the System Unit,
then printers, then the external mass memory system, then the Uninterruptible Power
Supply (UPS), and finally the monitor.
WARNING
Do not assume that all power to the computer is off just because the Power
On/Standby switch has been turned off. To completely remove power from your
computer, unplug the power cable from the power outlet, or disconnect that cable
from the power supply.
2.4 Start-up Procedures
2.4.1 Host Power Up and Verification
To power up the Operator Station, turn on the power to the Operator Station as described in the
applicable Advant Station Hardware User’s Guide.
NOTE
All USB devices must be connected and powered up prior to the OS station
being powered up. If power is lost to a USB device or if a USB connector
becomes disconnected, that USB device and devices connected to or downstream
from that device become not usable. The only way to regain functionality is to do
a total shutdown of the OS station. This configuration also requires a PS/2
3BUR001 835R0001 REV C
2-47
keyboard and mouse be connected. Without the PS/2 keyboard and mouse the
station will not boot or shutdown correctly.
2.4.1.1 AdvaCommand Auto Startup
The Operator Station containing AdvaCommand Basic Functions software will start-up
automatically when rebooted or powered up.
When the Operator Station starts up, you will see the Auto Startup Window, Figure 2-1.
Figure 2-1. AdvaCommand Auto Startup Sequence Window
From the Auto Startup window, you have the following options:
Would you like to start You can launch an HP terminal window to do pre-startup work, or
a HPterm window?
post-installation work, by selecting Yes
Note: You must exit all hpterm windows before the
AdvaCommand station will start.
Start the
AdvaCommand
Station in a window?
2-48
No is the default. To view the Auto Startup Status window, click
on Yes.
3BUR001 835R0001 REV C
Section 2.4.1 Host Power Up and Verification
Start the individual
tasks in separate
windows?
To see the individual tasks in separate windows for
trouble-shooting purposes, select Yes.
Start OMF Socket
Communication?
When enabled, AdvaCommand can access Advant Enterprise
Historian nodes on other control networks (Yes indicates
enabled). Refer to the Advant Enterprise Historian for Unix
User’s Guide for information on OMF socket communication.
Multicast TTL Value:
This is the time-to-live value which indicates the number of router
hops to do before a message is discarded (not sent any more). This
prevents endless messages loops that may occur as a result of
unexpected or unusual network partitioning.
0 = multicast messages are not sent at all
1 = multicast messages are sent only on the local subnet
>1 = multicast messages are forwarded to one or more hops
OMF Multicast
Address:
This is the Multicast address used by OMF (omfNetworkExt and
omfNameProc). A valid multicast group address that enables
routing of multicast messages must be in the range:
224.0.0.2 to 239.225.225.225
Enter OMF
SharedMemory Size:
Enter OMF shared memory size in this field. See the Advant
Enterprise Historian for Unix User’s Guide for guidelines on
calculating OFM shared memory requirements.
DCN Address (in hex,
or S for standalone):
If the DCN address is not correct, type it in the field provided and
press <Enter>. The address is verified once <Enter> is pressed.
E-DCN Network
Address1 (in hex):
This address is used only if you have an Ethernet DCN system.
Please refer to the Ethernet DCN User’s Guide for configuration
information.
E-DCN Network
Address2 (in hex):
See above.
Time before auto
startup:
You can enter the time (in seconds) to wait for startup once the
Start button is pressed. If you want the station to start
immediately, press OK.
If you press Suspend, the countdown will stop, and the Suspend
button will change to Start.
If you press Start, the timer will start counting down and you will
see the Start button change to Suspend.
3BUR001 835R0001 REV C
2-49
2.4.2 X-Terminal Power Up and Verification
To power up the Operator Station, turn on the power to the Operator Station as described in the
applicable Advant Station Hardware User’s Guide.
2.4.2.1 X-Terminal Startup
NOTE
The X-terminal must be first be configured (refer to Section 3.6.18, X-Terminal
Installation) before it will startup as explained.
The HP X-terminal will start-up automatically when rebooted or powered up.
When the X-terminal is started, you will see a login window, Figure 2-2.
Figure 2-2. X-Terminal Login Window
To use the AdvaCommand software, login as operator and enter the password. Once you are
logged-in, the X-terminal Auto Startup Interface will appear. Refer to Section 2.4.2.3,
AdvaCommand X-Terminal Auto Startup Interface for information about this window.
To use the AdvaBuild software, login as ocsmgr and enter the password. To run the AdvaBuild
software, enter the appropriate commands in the x-term window that appears.
2.4.2.2 Automatic X-Terminal Connection
You can configure the workstation to log you on automatically to bypass the X-terminal login
window. To do this:
1.
Open the file /opt/hpxt/enware2/xdm/Xaccess for editing.
2.
Go to the end of the file and add a line for each X-terminal that you want to automatically
logon. The syntax of the line is:
hostname BYPASS_LOGIN login
2-50
3BUR001 835R0001 REV C
Section 2.4.2 X-Terminal Power Up and Verification
where hostname is the hostname or IP address of the X-terminal, and login is either
“operator” to start AdvaCommand, or “ocsmgr” to start AdvaBuild.
This configuration process is also explained in the Xaccess file.
2.4.2.3 AdvaCommand X-Terminal Auto Startup Interface
When you log on to the X-terminal as ‘operator’, the X-Terminal Auto Startup interface
Window appears, Figure 2-3.
Figure 2-3. AdvaCommand X-Terminal Auto Startup Interface Window
From the X-Terminal Auto Startup Interface window, you have the following options:
3BUR001 835R0001 REV C
Which application
would you like to
start?
Select OS Client to start an AdvaCommand session. Select
Window Manager to run programs other than AdvaCommand.
Start the
AdvaCommand
Station in a window?
No is the default. To view the Auto Startup status window, click
on Yes.
2-51
Start the individual
tasks in separate
windows?
see the individual tasks in separate windows for trouble-shooting
purposes, select Yes.
Start OMF Socket
Communication?
When enabled, AdvaCommand can access Advant Enterprise
Historian nodes on other control networks (Yes indicates
enabled). Refer to the Advant Enterprise Historian for Unix
User’s Guide for information on OMF socket communication.
Multicast TTL Value:
This is the time-to-live value which indicates the number of router
hops to do before a message is discarded (not sent any more). This
prevents endless messages loops that may occur as a result of
unexpected or unusual network partitioning.
0 = multicast messages are not sent at all
1 = multicast messages are sent only on the local subnet
>1 = multicast messages are forwarded to one or more hops
OMF Multicast
Address:
This is the Multicast address used by OMF (omfNetworkExt and
omfNameProc). A valid multicast group address that enables
routing of multicast messages must be in the range:
224.0.0.2 to 239.225.225.225
Enter OMF
SharedMemory Size:
Enter OMF shared memory size in this field. See the Advant
Enterprise Historian for Unix User’s Guide for guidelines on
calculating OFM shared memory requirements.
DCN Address (in hex,
or S for standalone):
If the DCN address is not correct, type it in the field provided and
press <Enter>. The address is verified once <Enter> is pressed.
E-DCN Network
Address1 (in hex):
This address is used only if you have an Ethernet DCN system.
Please refer to the Ethernet DCN User’s Guide for configuration
information.
E-DCN Network
Address2 (in hex):
See above.
Time before auto
startup:
You can enter the time (in seconds) to wait for startup once the
Start button is pressed. If you want the station to start
immediately, press OK.
If you press Suspend, the countdown will stop, and the Suspend
button will revert to Start.
If you press Start, the timer will start counting down and you will
see the Start button change to Suspend.
2-52
3BUR001 835R0001 REV C
Section 3.1 Capacity and Performance
Chapter 3 Configuration/Application Building
3.1 Capacity and Performance
Custom Graphics Disk Sizes
Typical disk usage for graphics with dynamic display elements is 24 Kb + (10 Kb * Number of
dynamic elements). Information on disk usage for other types of elements, such as static display
elements or trend elements, will be available at a later time.
3.2 Database Configuration
3.2.1 Representing the Operator Station in the MOD 300 Database
An Advant Station Operator Station must be represented in the MOD 300 database by a
GENERICD object. This object is a child of the AREA object and represents a subsystem in the
area. The database object hierarchy related to the GENERICD object is shown in Figure 3-1.
MOD_DB represents MOD 300 database
AREA_1 represents one configuration
area
OP_STA_1
OP_STA_1 represents an Advant
Station Operator Station node in
AREA_1
These objects represent additional nodes
in AREA_1
AREA_2 represents a second configuration
area
Figure 3-1. MOD 300 Database Hierarchy Related to GENERICD Object
3BUR001 835R0001 REV C
3-1
The GENERICD database object is inserted into the MOD 300 database hierarchy, and its
object attributes are defined via the AdvaBuild Structure Builder and Template Builder,
respectively (as described in AdvaBuild Basic Functions User’s Guide). The GENERICD object
can have various children objects that define the specific functionality for the Operator Station,
as denoted in Table 3-1.
Table 3-1. GENERICD and Related Objects for the Advant Station Operator Station
OBJECT TYPE
PURPOSE
REFERENCE
GENERICD
Child of AREA object. Establishes an Advant Station node in
the configuration area. Children of the GENERICD object
determine the functional characteristics of the subsystem.
Section 3.2.1.1,
GENERICD Object
MODUSERS(1)
Child of GENERICD object. One required for any
Section 3.2.1.2,
configurator/data processor (CDP) subsystem, if that CDP is
MODUSERS Object
used to configure Multibus-based consoles. This object defines
names, passwords, and access privileges for console users.
LOG_DETL
Child of GENERICD object. One required for any subsystem
that supports an Alarm/Event Logger.
Section 3.2.2, How to
Configure Database
Objects to Support
Alarm/Event Logging
TCL_DEV(1)
Child of GENERICD object. Required for any subsystem that
supports Taylor Control Language development. Additional
objects related to TCL can be assigned as children to the
TCL_DEV object.
TCL User’s Guide
LL_DEV(1)
Child of GENERICD object. Required for subsystems that run TLL User’s Guide
Taylor Ladder Logic software. Additional objects related to TLL
can be assigned as children to the TLL_DEV object.
(1) Only applicable for Operator Stations with AdvaBuild Options
3-2
3BUR001 835R0001 REV C
Section 3.2.1 Representing the Operator Station in the MOD 300 Database
3.2.1.1 GENERICD Object
The Template Builder view of the GENERICD object is shown in Figure 3-2. The GENERICD
object attributes are described below.
Figure 3-2. GENERICD Object, Template Builder View
PHYSICAL DEVICE
This is the DCN node address. This must be the same DCN address as was defined for the
Operator Station during software loading. Be sure to enter the address in the Physical Address
field as a decimal number. The Operator Station node must be at a physical address with a lower
order hex digit of 1 as given in Table 3-2. Non-configurator nodes can be at any physical address
from 1 to 255 decimal.
Table 3-2. DCN Addresses for Nodes with Configurator Software
Address (Hex)
3BUR001 835R0001 REV C
Decimal Equivalent
01
1
11
17
21
33
31
49
41
65
3-3
Table 3-2. DCN Addresses for Nodes with Configurator Software (Continued)
Address (Hex)
Decimal Equivalent
51
81
61
97
71
113
81
129
91
145
A1
161
B1
177
C12
193
D1
209
E1
225
F1
241
AUTO START
This field determines whether or not the node starts automatically when the software is
downloaded. The only valid choice for a GENERICD node is YES.
SOFTWARE NAME
This field is not applicable. Leave it at the default.
DO RATE
This attribute is not applicable. Leave it at the default.
SECONDARY DP, BACKUP ENABLE, and BACKUP OVERRIDE
These fields have not been implemented. Leave them at their default values.
DEFAULT ENVIRONMENT
This attribute is not applicable.
NODE TYPE
This field specifies the hardware platform for the GENERICD node. The choices are:
3-4
MOD300_NODE
This option is for a Multibus-based node.
ADVANT_STATN
This option is for an Advant Station.
3BUR001 835R0001 REV C
Section 3.2.1 Representing the Operator Station in the MOD 300 Database
3.2.1.2 MODUSERS Object
The MODUSERS object is required for configurator/data processor subsystems (such as the
Operator Station with AdvaBuild Options) that are being used to configure Multibus-based
Console Subsystems (or Turbo Nodes that support console functionality in addition to other
functions). This object establishes the access class for users on this console. An edit window is
provided for entering user IDs and associated passwords, access classes, security devices, and
log in methods, Figure 3-3. Each line in this window represents one user.
Figure 3-3. MODUSERS Object (Page 1), Template Builder View
The columns in this window are:
USER ID
21 characters maximum.
PASSWORD
12 characters maximum.
3BUR001 835R0001 REV C
3-5
ACCESS CLASS
This field determines the access class for the user. The choices are:
OP
Operator (view and control process through console displays)
SU
Supervisor (operator functions plus tuning)
EN
Engineer (supervisor functions plus configuration and application building)
SEC DEV
This field determines if a security key is required for this user. The valid choices are:
DATA KEY
This option enables the data key function. This means the system checks for
the datakey device when you log in. If the key is found, the login is allowed. If
the key is not found, an error message is generated.
NONE
This option disables the datakey function.
AUTO LOG
This field determines how the user logs in and out when the security key function is
implemented. The choices are:
ON
You are logged in once the key is inserted into the reader and turned. You
remain logged in even after the key has been removed from the reader. Log
out is via the ENVIRONLOGON display.
OFF
To log in, you must insert the key into the reader, turn the key, and log in via
the ENVIRONLOGON display. Log out is automatic when the key is
removed from the reader.
NONE
To log in, you must insert the key into the reader, turn the key, and log in via
the ENVIRONLOGON display. Log out is via the ENVIRONLOGON
display.
BOTH
Log in is automatic when you insert the key into the reader and turn the key.
Log out is automatic when you remove the key.
EXPORT TO DEVICES
This field is only applicable when the system has multiple configurators.
3.2.2 How to Configure Database Objects to Support Alarm/Event Logging
3.2.2.1 AREA Object
This section describes the database attributes of the AREA object that are applicable for
configuring an Alarm/Event Logger. Instructions for configuring the AREA object in general
are provided in the AdvaBuild Engineering Methods for Systems with MOD 300 Software
User’s Guide.
To support an Alarm/Event Logger, you must configure the Message Center of the AREA where
the Operator Station node resides. This configuration is described below.
3-6
3BUR001 835R0001 REV C
Section 3.2.2 How to Configure Database Objects to Support Alarm/Event Logging
The MESSAGE CENTER edit window, Figure 3-4, is used to specify the destinations of
messages originating in this configuration area. This window starts on page 4 of the AREA
object template view (use <tab> to get to page 4). During runtime, the following types of
messages can be generated by the system: CCF event, CCF alarm, TCL event, TCL billboard
and system error. The edit window has one line for each type of message.
Figure 3-4. AREA Object, Template Builder View, Page 4 with MESSAGE CTR Window
The line format is:
MESSAGE CTR
This is the object ID for the device (Console, History, Logger, Generic DPSS or LCP) receiving
the messages. The ID must be the same as the one assigned when the object was inserted in the
MOD 300 database.
3BUR001 835R0001 REV C
3-7
MESSAGE TYPE
Is the type of message. Valid entries for type are:
CCF_ALARM
CCF_EVENT
CCF_BOTH
Both CCF alarm and event messages
TCL_EVENT
TCL_BILLBOARD
used to designate TCL unit messages that are generated by TCL MESG
and REPLY statements and programmable unit alarms generated by
TCL UNIT_ALARM statements
TCL_BOTH
Both TCL event and billboard messages
SYSTEM
REMOTE TYPE
This field is only applicable for systems using multiple configurators, and when the message
destination is in another configurator domain. The entry specifies the object type and must be
one of the following: CONSOLE, LOGGER, GENERIC_DPSS, LCP, or HISTORY.
Message Center Entries for Alarm/Event Loggers
Alarm/Event Loggers are software devices that log messages to printers and/or disks. You must
make an entry in the MESSAGE CTR window for each type of message that you want to send
to a specific logger. The example below contains entries that send all the messages to a Logger
named LOGGER1:
LOGGER1
CCF_BOTH
LOGGER1
TCL_BOTH
LOGGER1
SYSTEM
In this example, LOGGER1 is the object ID assigned to the object representing this logger.
It is not mandatory for all five message types to be sent to the logger. Any combination of
message types is valid. If a system has more than one Configuration Area, entries must be made
in the MESSAGE CTR edit windows of each AREA object.
3-8
3BUR001 835R0001 REV C
3.2.2.2 LOG_DETL Object
A LOG_DETL object, Figure 3-5, is required for subsystems that support an Alarm/Event
Logger. This object, in combination with the AREA object, determines which messages are
logged.
Figure 3-5. LOG_DETL Object, Template Builder View
The LOG_DETL object has the following attributes:
Templet Name
This field is used to assign a name to the logger. This name appears on each page the logger
prints. It must also be entered into the MESSAGE CTR edit window of the AREA object for the
configuration area where the logger resides. Valid entry is a character string of up to 8
characters.
Logger Description
This field allows you to specify a descriptor for the logger. The descriptor appears on each page
the logger prints. Valid entry is a character string of up to 24 characters.
Backup Logger Name
The field allows you to designate another logger as the backup for the logger being configured.
If the primary logger cannot print the message, it sends it to the backup logger. The backup
logger must be on another subsystem. Valid entry is the name assigned to the backup logger via
its TEMPLET NAME field.
3BUR001 835R0001 REV C
3-9
Printer Name
This field is used to specify the printer where the logger prints its messages. The printer must be
part of the subsystem containing the logger.
If the logger resides on a Multibus-based node, it must have a serial channel configured for it
via the Serial Ports object. Valid entry is the printer name which was assigned to the printer via
the PORT NAME field of the Serial Ports object.
If the logger resides on an Advant Station-based node, the Printer Name has to exactly match
(UNIX is case-sensitive) the HP-UX printer name.
Backup Printer Name
This field is used to specify which printer the logger sends messages to, if the primary printer is
not functioning. Valid entry is the printer name that was assigned to the printer via the PORT
NAME field of the Serial Ports object.
NOTE
This field is not applicable for loggers that reside on an Advant Station-based
node.
Max # Msgs on Disk
This field is applicable only for loggers defined for Data Processor Subsystems. This field sets
up a buffer, on the disk, that is used to store messages until the printer is free to print them. Valid
entry is an integer n where n = the number of messages. The default is 0.
Max # Msgs In Memory
This field sets up a buffer in memory, that is used to store messages until the printer is free to
print them. Valid entry is an integer n where n = the number of messages. The default is 50.
STD Alarm Color
This field is applicable only when a color printer is assigned to the logger. The field specifies
the color used to print messages for standard priority (priority 3) CCF alarms.
There are two color ribbons: the primary ribbon (red, blue, green and black) and the process
ribbon (magenta, cyan, and yellow). If you have a color printer, you need to know which ribbon
your printer has in order to configure the alarm/event colors. Valid entries are: RED, BLUE,
GREEN, BLACK, MAGENTA, CYAN, YELLOW. The default is BLUE. Use BLUE for
primary ribbons, or CYAN for process ribbons.
3-10
3BUR001 835R0001 REV C
STD Alarms Printed
This field enables the logging of standard priority CCF alarm messages. These messages are not
logged unless entries are also made to the MESSAGE CTR edit windows of the Configuration
Area Templets where the messages originate. Valid entries are:
YES
Log standard priority CCF alarm messages
NO
Do not log standard priority CCF messages
Default is: NO
STD Print Type
This field specifies the type face used to print the standard priority CCF alarm messages. Valid
entries are:
BOLD
print messages in a bold type face
UNDERLN
print messages in the normal type face, underlined
NORMAL
print messages in the normal type face
Default is: UNDERLN
Trip Limit High
This field specifies the trip point that, when exceeded, causes a message to be printed warning
that the logger buffer is almost full. The trip point is expressed as a percentage of the message
buffering capacity, which is the sum of the messages that can be stored in the memory buffer
(Max # Msgs in Memory field) and the disk buffer (Max # Msgs on Disk field). Valid entry is an
integer nn which represents a percentage of the capacity of the memory buffer. The default is
70.
Example:
If the entry to this field is 70, and the logger can buffer 50 messages in memory and 40
messages on disk, the warning message is printed when the buffers contain 63 messages
(70% of 90).
Trip Limit High High
This field specifies a more critical trip point that, when exceeded, causes a second (and more
urgent) message to be printed warning that the logger buffer is on the verge of being full. Like
TRIP LIMIT HIGH, this value is expressed as a percentage of the message buffering capacity.
This value should be higher than the entry for the TRIP LIMIT HIGH field. Valid entry is an
integer nn which represents a percentage of the capacity of the memory buffer. The default is
90.
Event Color
This field is applicable only when a color printer is assigned to the logger. This field specifies
the color used to print event messages. These messages consist of CCF parameter change
messages, all TCL messages, and the subset of the system diagnostic messages the logger prints.
3BUR001 835R0001 REV C
3-11
GREEN, BLACK, MAGENTA, CYAN, YELLOW. The default is GREEN. Use GREEN
for both primary and process ribbons.
Events Printed
This field enables the logging of event messages. These messages consist of CCF parameter
change messages, all TCL messages, and the subset of the system diagnostic messages the
logger prints. These messages are not logged unless entries are also made to the
MESSAGE CTR edit windows of the Configuration Area Templets where the messages
originate.
Valid entries are:
YES
Log event messages.
NO
Do not log event messages.
Default is: NO
Event Print Type
This field specifies the type face used to print the event messages. Valid entries are:
BOLD
print the messages in a bold type face
UNDERLN
print the messages in the normal type face, underlined
NORMAL
print the messages in the normal type face
Default is: NORMAL
HP Alarm Color
the color used to print messages for high priority (priority 1) CCF alarms.
GREEN, BLACK, MAGENTA, CYAN, YELLOW. The default is RED. Use RED for
primary ribbons, or MAGENTA for process ribbons.
HP Alarms Printed
This field enables the logging of high priority CCF alarm messages. These messages are not
Area Templets where the messages originate.
Valid entries are:
YES
Log high priority CCF alarm messages.
NO
Do not log high priority CCF alarm messages.
Default is: YES
3-12
3BUR001 835R0001 REV C
Section 3.2.3 Database Objects for History
HP Print Type
This field specifies the type face used to print the high priority CCF alarm messages. Valid
entries are:
BOLD
print the message in a bold type face
UNDERLN
print the message in the normal type face, underlined
NORMAL
print the message in the normal type face
Default is: BOLD
MED Alarm Color
the color used to print messages for medium priority (priority 2) CCF alarms.
GREEN, BLACK, MAGENTA, CYAN, YELLOW. The default is BLACK. Use BLACK
for both primary and process ribbons.
MED Alarms Printed
This field enables the logging of medium priority CCF alarm messages. These messages are not
Area Templets where the messages originate. Valid entries are:
YES
Log medium priority CCF alarms.
NO
Do not print medium priority CCF alarms.
Default is: YES
MED Print Type
This field specifies the type face used to print medium priority CCF alarm messages. Valid
entries are:
BOLD
print the message in a bold type face
UNDERLN
print the message in the normal type face, underlined
NORMAL
print the message in the normal type face
Default is: NORMAL
3.2.3 Database Objects for History
A HISTORY object must be inserted as a child of the GENERICD object that represents the OS
where the History software runs. Then a RECORDER object must be inserted as a child of the
HISTORY object. These objects do not have any attributes that need to be configured to support
AdvaInform History. However, they must exist in the database so messages can be routed to the
node. They also support the ability to present AdvaInform History data on Multibus-based trend
displays.
3BUR001 835R0001 REV C
3-13
If you need to route messages to history in the OS, the following database objects related to
message routing must be configured:
•
The AREA object for any configuration area whose nodes route CCF alarm, CCF event,
TCL event, and TCL billboard messages to History.
•
The MSG_ROUT (message routing) object for any Multibus-based console that routes log
on and alarm acknowledge messages to History.
3.2.3.1 AREA Object
You must configure the Message Center edit window in any AREA object whose children nodes
route messages to History. The Message Center edit window, Figure 3-6, is used to specify the
destinations of messages originating in this configuration area. This window starts on page 4 of
the AREA object template view.
During runtime, CCF event, CCF alarm, TCL event, TCL billboard and system error messages
can be generated by the system. The edit window has one line for each type of message.
Figure 3-6. AREA Object, Template Builder View, Page 4 w/MESSAGE CTR Window
The line format is:
MESSAGE CTR
3-14
This is the object ID for the device or History/Logger package
(Console, OS, History, Logger, Generic DPSS or LCP) to receive
the messages. The ID must be the same as the one assigned when
the object was inserted in the MOD 300 database.
3BUR001 835R0001 REV C
Section 3.2.3 Database Objects for History
MESSAGE TYPE
Is the type of message. Valid entries for type are:
CCF_ALARM
CCF_EVENT
CCF_BOTH (both CCF alarm and event messages)
TCL_EVENT
TCL_BILLBOARD (used to designate TCL unit messages that are generated by
TCL MESG and REPLY statements and programmable unit alarms generated by
TCL UNIT_ALARM statements
TCL_BOTH (both TCL event and billboard messages)
SYSTEM Not routed to a History package
REMOTE TYPE
This field is only applicable for systems using multiple
configurators, and when the message destination is in another
configurator domain. The entry specifies the object type and must
be one of the following: CONSOLE,LOGGER,
GENERIC_DPSS, LCP, or HISTORY.
Message Center Entries for Historical Services
You can route CCF alarm, CCF event, TCL event, and TCL billboard messages from the area to
AdvaInform history. The example below shows how to configure the Area object to route all
types of messages to HISTORY1. HISTORY1 is the object ID for the History object.
3BUR001 835R0001 REV C
HISTORY1
CCF_BOTH
HISTORY1
TCL_BOTH
3-15
3.2.3.2 MSG_ROUT Object
This object must be inserted as a child of the CONSLIB object of any MOD300 console or
Advant OS nodes. It provides the means for you to configure how console log on and/or alarm
acknowledgment messages are routed to AdvaInform History nodes and loggers, Figure 3-7.
Figure 3-7. MSG_ROUT Object, Template Builder window
This object has the following attributes:
MESSAGE CTR
To route messages, enter the message destinations and the types of messages to be routed to
these destinations in the MESSAGE CTR edit window.
Indicate the message destination by entering the object ID of the destination package. For
message type enter any one of the following:
CONS_LOG_ONS
Console log on
CONS_ACKS
Console alarm acknowledgment
CONS_BOTH
Both console log on and console alarm acknowledgment
There is a limit of 256 destinations for messages. Messages of a specific type from a
configuration area can be sent to no more than 40 destinations.
REMOTE TYPE
This field is only applicable for systems using multiple configurators, and when the message
destination is in another configurator domain. The entry specifies the object type and must be
one of the following: CONSOLE,LOGGER, GENERIC_DPSS, LCP, or HISTORY.
3-16
3BUR001 835R0001 REV C
Section 3.2.4 Database Objects for Reports and PDL
3.2.4 Database Objects for Reports and PDL
A REP_BLDR object must be inserted as a child of the GENERICD object that represents the
Advant Station where the History and Reports software runs. This object does not have any
attributes that need to be configured to support the station. However, it must exist in the
database to support PDL functionality.
In addition you must configure the REPORT ID and REPORT ID 2 fields on the
UNIT_MASTER object of any unit that will send batch data to Production Data Logs (PDLs)
on the IMS, Figure 3-8.
Figure 3-8. UNIT_MAST Object
To establish the station as the destination for recorded data (TCL RECORD statements),
configure the REPORT ID and REPORT ID 2 fields on the Unit Master object (template). These
fields are used to specify the Reports software package(s) (up to two) that will process batch
data for the unit corresponding to the Unit Master object you are configuring.
There are two Reports packages that can run in the Advant OCS with MOD 300 software:
Multibus-based Reports Services or AdvaInform Reports. The Report ID must be entered
exactly as it is defined in the TEMPLET NAME field on the REP_BLDR object for the node
where the Reports package runs.
Batch recording and tracing information can be stored redundantly by configuring two Report
IDs.
3BUR001 835R0001 REV C
3-17
3.3 Setup for Interface with MOD 300 System via a Serial Gateway
You can set up a serial interface between an Engineering Station and the MOD 300 System to:
•
upload existing MOD 300 database and TCL source files from the MOD 300 System to the
Engineering Station
•
download database and TCL source files from the off-line Engineering Station to the
MOD 300 System to compile, install (or link), and download to a MOD 300 Subsystem.
If your Engineering Station is equipped with a Real-time Accelerator (RTA) Board which
supports On-line Builder functions, you can perform uploads and downloads without the serial
interface. Refer to the AdvaBuild Basic Functions User’s Guide for details on how to use
On-line Builder functions.
In the MOD 300 System, the serial gateway for the Engineering Station is supported by a
Multibus-based subsystem. This subsystem can be dedicated to just the gateway functionality,
or it can be configured to support a combination of functions such as console/gateway or data
processor/gateway, and so on. The MOD 300 serial gateway can support up to four Engineering
Stations, depending upon other CPU and memory load requirements.
The computer interface function in the Multibus-based subsystem is limited to one type of
computer. Therefore, the subsystem cannot support an interface with both an Advant Station
Engineering Station and an IBM PC at the same time.
To establish a serial interface between the Engineering Station and MOD 300 Serial Gateway:
•
3-18
Configure the following objects to support the gateway node in the MOD 300 database:
–
GenericD object that represents the MOD 300 serial gateway node
–
serial port setup object that establishes the serial interface parameters
–
computer interface object
–
computer interface definition object
•
Set up a serial port on the Engineering Station
•
Configure the serial interface parameters via jumpers on the MOD 300 Serial I/O module
•
Build the serial cable to connect the gateway node port to the Engineering Station
3BUR001 835R0001 REV C
Section 3.3.1 How to Configure the MOD 300 Database to Support a Serial Gateway
3.3.1 How to Configure the MOD 300 Database to Support a Serial Gateway
The database objects required to support a serial gateway in the MOD 300 System are shown in
Figure 3-9. This section describes how to configure the database attributes for these objects that
are specific to supporting the serial gateway for the Engineering Station. General instructions
for configuring these database objects are provided in the following books:
•
For a Multibus-based configurator, see MOD 300 System Configurator User’s Guide.
•
For an Advant Station Engineering Station, see AdvaBuild Engineering Methods for the
MOD 300 System and AdvaBuild Basic Functions User’s Guide.
GENERICD
SERIAL_PORT_SETUP
COMPUTER_INTERFACE
COMP_INT_DEFINITION
Figure 3-9. MOD 300 Database Objects for Serial Gateway Function
3.3.1.1 GenericD Object
The GenericD object represents a subsystem that may support multiple functions. The specific
functionality for a subsystem is defined by the SOFTWARE NAME attribute. For serial
gateway functionality, define the Software Name attribute as one of the following:
•
GATEWAY to configure node as a dedicated gateway
•
TURBO to configure node to support all turbo node functions
•
TURBOGW to configure node to support data processor, history, and gateway functions
Configure all other attributes per the instructions in the applicable book.
3.3.1.2 Computer Interface Object
This object defines passwords and access classes for interface users. There are no specific
entries required for the Engineering Station. Configure this object per the applicable book.
3.3.1.3 Computer Interface Definition Object
This object defines the communication protocol and data compatibility for the interface. In the
COMMUNICATION PROTOCOL field, enter SERIAL. In the DATA COMPATIBILITY field,
enter HEWLETT-PACK. Configure all other attributes per the applicable book.
3BUR001 835R0001 REV C
3-19
3.3.1.4 Serial Port Setup Object
The Serial Port Setup object establishes the serial communication parameters (baud rate, parity,
data bits, stop bits, and so on) for the serial port that supports the gateway. The entries for this
object must match the corresponding entries in the Serial Port Configuration dialog as described
in Section 3.3.2, How to Configure the Serial Port on the Engineering Station.
The fields on this object that require specific values for the Engineering Station interface are
described below. Configure all other fields per instructions in the applicable book.
PORT NAME
A unique 12-character name. The first three characters must be CIF.
TYPE
The required entry is TERMCHAR
SPEED
Standard speed is 9600 baud. Other valid baud rates for the Engineering
Station are 1200, 2400, 4800, and 19,200. The value you enter here must
match the value that you enter on the Serial Port Configuration dialog for the
Engineering Station.
WORD
The required value is 8. This value must also be entered on the Serial Port
Configuration dialog for the Engineering Station.
PARITY
Standard parity is NONE. Other valid entries for the Engineering Station are
ODD, EVEN, SPACE, and MARK. The value you enter here must match the
value that you enter on the Serial Port Configuration dialog for the
Engineering Station.
STOP
The required value is 1. This value must also be entered on the Serial Port
Configuration dialog for the Engineering Station.
OTO
The required value is 1.
TERM CHAR
The required value is 2E 3F 2A. You must enter this information exactly as
shown. Include a space after the E and the F.
NOTES
If you do not use all the ports on the serial module, you may want to configure
one unused port as a spare keyboard port. Beyond that it is best not to configure
any other spare ports. This saves memory space which is particularly important
when the module contains one or more Engineering Station ports.
If you plan to connect more than one Engineering Station to a given module, it is
recommended that you use the higher port numbers for the Engineering Stations.
3-20
3BUR001 835R0001 REV C
Section 3.3.2 How to Configure the Serial Port on the Engineering Station
3.3.2 How to Configure the Serial Port on the Engineering Station
You configure the serial port on the Engineering Station via the Serial Port Configuration
dialog. This procedure is described in Section 3.3.2.1, Serial Port Configuration Dialog.
A device special file is created in HP-UX on the Advant Station during installation of the
Engineering Station. This file is required to support serial communication between the
Engineering Station and the serial device being connected to it. Since the file is created
automatically as part of installation, you generally need not be concerned with it. The procedure
for creating a device special file is provided in Section 3.3.2.2, Creating Device Special File on
an Advant Station, in the event that your file gets deleted and you must create a new one.
3.3.2.1 Serial Port Configuration Dialog
The serial interface parameters for the HP-UX port (baud rate, parity, data bits, and stop bits)
must be configured to match the characteristics of the corresponding serial port on the remote
platform. In the case of the Multibus Configurator/Data Processor (CDP), these parameters are
defined on the Serial Port Setup Template.
The means for configuring the serial port on the Advant Station are provided via the Special
Commands menu item from the Object menu on the Structure Builder menu bar. To Configure
the Serial Port on the Advant Station:
1.
Click on the Project object in the tree presentation.
2.
Choose Special Commands from the Object menu.
3.
Select the CI_CONFIG option in the Special Commands box and then click on OK.
This displays the Serial Port Configuration dialog box, Figure 3-10.
/dev/tty0p0
Figure 3-10. Serial Port Configuration Dialog Box
3BUR001 835R0001 REV C
3-21
4.
Define the serial interface parameters in this dialog box as described below.
DEVICE PATH is the Device Special File Name portion of the MKNOD command. This field
defaults to /dev/tty0p0. The value must match the value in the mknod command (Section
3.3.2.2, Creating Device Special File on an Advant Station). Unless a value other than
/dev/tty0p0 was used, the default does not have to be changed.
BAUD RATE, PARITY, STOP BITS, and DATA BITS (WORD LENGTH) must match the
values for the corresponding serial port on the remote platform. For a Multibus CDP, these
parameters are defined on the Serial Port Setup templet. Selecting one of these parameters,
displays a pop-up menu with a listing of valid choices. Figure 3-10 shows typical values for
communication with a Multibus CDP. A complete list of valid choices for these fields is
provided below.
BAUD RATE
1200, 2400, 4800, 9600, 19200 (19200 cannot currently be used for remote
IBM PC platforms.)
PARITY
NONE, ODD, EVEN, SPACE, MARK
STOP BITS
1
DATA BITS
8
TIMEOUT is the time (in seconds) that the Advant Station waits for a response from the remote
platform before timing out. The Advant Station retransmits a message five times during the
specified period. An error message is generated if no response is received after the fifth try. The
choices for TIMEOUT are: 0, 10, 20, 30, 40, 50, and 60. 0 (zero) is not recommended since this
causes the Advant Station to wait indefinitely in the event that the other CDP failed to respond.
3.3.2.2 Creating Device Special File on an Advant Station
A device special file must be created on the Advant Station to support data transfer. This is done
via the HP-UX mknod command. Refer to Section 3.6.10, AdvaBuild Device Special File for
more information.
3-22
3BUR001 835R0001 REV C
Section 3.3.3 How to Configure the Jumpers on the MOD 300 Serial I/O Module
3.3.3 How to Configure the Jumpers on the MOD 300 Serial I/O Module
For the MOD 300 side of the serial interface, the serial ports are located on the 6007B Serial I/O
Modules in the Multibus cardfile. Up to two serial I/O modules can be installed in one cardfile,
and each module has eight ports. You can connect up to four Engineering Stations to a Multibus
subsystem via these ports. To support communication with an Engineering Station, the serial
port must be configured for the correct serial communications parameters as described in
Table 3-3. These parameters are configured by setting jumpers on the serial I/O module. Refer
to the Multibus Principle Modules for detailed instructions on how to set the jumpers on the
serial I/O module.
Table 3-3. Serial Port Parameters for Interface with Engineering Station
Parameter
Entry
Type
RS232
Device CTS (Clear to Send)
Enabled
Device DSR (Data Set Ready)
Disabled
NOTE
If you plan to connect more than one Engineering Station to a given module, it is
recommended that you use the higher port numbers for the Engineering Stations.
3.3.4 Serial Cable Requirements
The serial cable from the Engineering Station is connected to a 6052B or 6060B Serial Interface
Module as shown in Figure 3-11. The serial interface module is connected to the serial I/O
module via a pre-fabricated internal ribbon cable.
Serial Interface Cable
Internal Ribbon Cable
p/o interface module chassis 6151N
6007B Serial
I/O Module
6052B or 6060B Serial
Interface Module
Advant Station
Engineering Station
J1 P1
P2
Serial Connector A or B
Figure 3-11. Serial Cable Connection Between Engineering Station and MOD 300 Serial Gateway
3BUR001 835R0001 REV C
3-23
3.4 How to Transfer Taylor Ladder Logic (TLL) Segment Files
This section describes how to transfer TLL segment files between the Multibus-based and
Advant Station-based CDPs. This functionality is supported by two commands which are
invoked via the command line in an HP-UX terminal window:
•
tllupld transfers existing TLL segment files from a Multibus-based CDP node to an
Advant Station Engineering Station.
•
tlldnld transfers TLL segment files from an Advant Station Engineering Station to a
Multibus node.
3.4.1 Prerequisites
The following must be done before you transfer TLL segment files between CDP platforms:
•
serial communications between the Advant Station Engineering Station and the Multibus
node must be established as described in Section 3.3, Setup for Interface with MOD 300
System via a Serial Gateway.
•
the appropriate ladder logic devices and ladder logic segments must be created at the
destination CDP, if they do not already exist. This procedure is described in the Taylor
Ladder Logic User’s Guide.
3.4.2 File Transfer Procedure
Before you attempt to use either of these procedures, you should be aware that:
•
runtime diagnostic output is controlled by the environment variables DEBUG_TLLUPLD
(for tllupld) and DEBUG_TLLDNLD (for tlldnld). This output can be enabled by
exporting the appropriate environment variable, and disabled by unsetting the appropriate
environment variable.
•
these two functions can be used only for ladder logic segments.
To transfer TLL segment files from one CDP platform to another CDP platform:
1.
Log in to the Multibus CDP from the Engineering Station using the CI_LOGON
command.
This command is available via the Special Commands menu item in the Object menu.
Click on the Project object, choose Special Commands from the Object menu, and then
select CI_LOGIN.
As an alternative, you can enter the CI_LOGIN command via an HP-UX terminal
command line.
2.
3-24
Open a terminal window on the Engineering Station.
3BUR001 835R0001 REV C
Section 3.5 Application Start-up
3.
Enter the tllupld command to transfer TLL segment files from the Multibus-based CDP to
the Engineering Station:
tllupld [-r] <MOD300_src_file spec> [<HP-FMS_dest_file_spec>]
or enter the tlldnld command to transfer TLL segment files from the Engineering Station
to the Multibus-based CDP:
tllnpld [-r] [<HP-FMS_src_file_spec>] <MOD300_dest_file spec>
NOTE
The square brackets denote optional parameters.
The -r option indicates that if the specified destination file exists, it is to be replaced.
Since the files have been created (see Section 3.4.1, Prerequisites), the -r option, in this
case, is always required.
The source and destination file specifications have the following format:
<MOD300_src_file spec> :== <node>::<dev>:[<user>.<cat>]<filename>.<ext>
<HP-FMS_dest_file_spec> :== <dev>:[<user>.<cat>]<filename>.<ext>
The <HP-FMS_dest_file_spec> is optional. It defaults to the Advant Station with the same
FMS file name and location as the <MOD300_dest_file spec>.
NOTE
If you are transferring many files, it may be advantageous to create a script to
perform the transfers in a batch-like fashion.
The following is an example of the tllupld command that copies a file from the DPSS
to the Advant Station with same name and location ( <HP-FMS_dest_file_spec> is
omitted):
tllupld -r dpss::wc00:[20566.plantcon]12.sr
The following is an example of the tllupld command that copies a file from the DPSS
to the Advant Station in a different location, with the same name:
tllupld -r dpss::wc00:[20566.plantcon]12.sr wc00:[20566.newplant]12.sr
4.
When the transfer is complete, log out of the Multibus CDP using the CI_LOGOFF
command (via Special Commands menu item in Object menu as described in step 1).
5.
Save the segment files from the segment editor as described in the Taylor Ladder Logic
User’s Guide.
This compiles the segments and makes them ready for use.
3.5 Application Start-up
When the Operator Station starts up, the AdvaCommand Main Window is displayed. Refer to
the AdvaCommand Basic Functions User’s Guide for information on using AdvaCommand.
3BUR001 835R0001 REV C
3-25
3.6 Station Configuration
3.6.1 Setting the DCN Address
3.6.1.1 Initial DCN Address
When the OS starts up for the first time after installing the software, the Auto Startup dialog
prompts you for the DCN address of your workstation. Enter the DCN device address in
hexadecimal, or enter S for stand-alone. This address is for the device only, so C100 is entered
as C1.
3.6.1.2 Changing the DCN Address
If you wish to change the DCN address of the Operator Station, you must restart the Operator
Station (see Section 2.3, Shut-down Procedures) and modify the DCN address when the Auto
Startup window appears.
3.6.1.3 Configuring a DCN Stand-alone System
If you wish to define your Operator Station as a stand-alone node on the DCN (the only node on
the DCN), simply enter an S when the Auto Startup window appears. This entry will cause Auto
Startup to set the device address to 0100, and install the STARTER-X database in this node.
This system configuration allows you to boot the node, and to create graphics and environments
via the Display Builder and Environment Builder, without interacting with other nodes on the
Plant Control Network.
NOTE
The DCN cables should not be connected to a stand-alone node. Connecting the
cables may cause a situation in which two or more devices are using the device
address 0100, and unexpected results will occur.
3.6.1.4 Converting a DCN Stand-alone System to a System on the DCN
To convert a DCN stand-alone system to a system on the DCN, simply restart the system and
enter the device address as it is configured in the database when the Auto Startup window
appears.
3.6.2 Environments
3.6.2.1 AdvaCommand Default Environment
Each Operator Station running AdvaCommand Basic Functions software has a default
environment named “ADVANT.” Its user is ADVANT and the password is “MOD.” This allows
Operator Station users to get into the Environment Builder and create new environments. For
additional security, users can change the user ID and password in the default environment.
3-26
3BUR001 835R0001 REV C
Section 3.6.3 Changing TCP/IP Network Parameters and Time Zone with set_parms
3.6.2.2 AdvaBuild Default Environment
When you purchase the AdvaBuild software, you now also receive the AdvaCommand
software. However, if you have not purchased a license for the AdvaCommand software, you
can utilize the AdvaCommand RDP functionality but not the runtime displays.
When you install the AdvaBuild ABB-AB-BASEFUN software, a default AdvaBuild
environment named ES is created. The ES environment is an AdvaCommand environment that
controls access privileges to AdvaCommand functions. The environment prohibits you from
using the AdvaCommand runtime displays, but permits you to use RDP displays and external
applications in AdvaCommand.
NOTE
If the DCN address for the node has not been set before installation of the
AdvaBuild Version 2.7/0 software, the ES default environment will be created
with the default address of 0100 for RDP functions. If you want this environment
to use your node address, delete that environment (via the AdvaBuild
Environment Builder) and run the create program again.
/opt/advant/ES/bin/create_es_default_env
3.6.2.3 Automatic Environment Install
You can set the OS up to automatically install an Environment during the startup sequence. To
configure an Environment for automatic installation do the following:
1.
Log on as root.
2.
Open the file $OS_CONFIG/customerSystemVariables with a text editor.
3.
Search for the line in the file that starts with “Uis.SystemVariable.defaultEnvironment:”
4.
Change the value of ‘none’ to an existing environment contained on the node.
Example: Uis.SystemVariable.defaultEnvironment: ADVANT
5.
Save the file.
6.
The automatic environment installation feature will take effect after you reboot the station.
3.6.3 Changing TCP/IP Network Parameters and Time Zone with set_parms
You can change the TCP/IP networking parameters and the time zone by running a program
called set_parms. The sections below explain how to change each of the individual options
3.6.3.1 How to Change the System Name (Hostname)
This section discusses how to change the system name (called the hostname) on the workstation.
Each of the nodes must have a unique hostname. You will want to get the hostname from your
plant network manager before continuing. If you are not on the plant network, you will have to
pick a unique hostname.
3BUR001 835R0001 REV C
3-27
To change the hostname, you must log on as root and do the following:
1.
Enter: set_parms hostname
2.
Follow the dialog provided to enter the hostname.
3.
If you see the prompt: reboot station (y/n)?, enter y unless you are changing
other network parameters. You can change other parameters, and reboot when you are
done.
3.6.3.2 How to Change the TCP/IP Address
This section discusses how to change the TCP/IP address on the workstation (not the DCN
address). Each of the nodes must have a unique TCP/IP address. You will want to get the IP
address from your plant network manager before continuing. If you are not on the plant
network, you will have to pick a unique IP address.
To change the IP address, you must log on as root and do the following:
1.
Enter: set_parms ip_address
2.
Follow the dialog provided to enter the IP address.
3.
done.
3.6.3.3 How to Change Additional TCP/IP Network Parameters
This section discusses how to change additional TCP/IP network parameters on the workstation,
such as the subnet mask, network gateway, network gateway IP address, local domain name,
Domain Name System (DNS) server host name, DNS server IP address and Network
Information Service domain name. You will want to get this information from your plant
network manager before continuing. If you are not on the plant network, you most likely will
not need to do this section.
To change the additional network parameters, you must log on as root and do the following:
1.
Enter: set_parms addl_netwrk
2.
Follow the dialog provided to enter the network parameters.
3.
If you see the prompt: reboot station (y/n)?, enter y.
3.6.3.4 How to Change the Time Zone
This section discusses how to change the time zone on the workstation.
To change the time zone, you must log on as root and do the following:
3-28
1.
Enter: set_parms timezone
2.
Follow the dialog provided to enter the hostname.
3BUR001 835R0001 REV C
Section 3.6.4 Conversion to Two-screen Operation
3.
done.
3.6.4 Conversion to Two-screen Operation
To convert to two-screen operation, you must have a workstation with two-screen hardware.
You must know which version of the Operator Station you are using in order to set OS_HOME
correctly.
To convert to two-screen operation, do the following:
1.
Log on as root.
2.
Enter cp -p /usr/lib/X11/X0screens /usr/lib/X11/X0screens.orig
This saves the original.
3.
Enter: cp -p /opt/advant/MOD-OS/etc/X0screens.2head
/usr/lib/X11/X0screens
4.
To use the two heads, you must now restart the workstation.
3.6.4.1 Vertical Two-screen Orientation
If you are converting to a vertical two-screen orientation, with one screen above the other, you
must do the following steps to make the cursor track vertically between the screens:
1.
Log in as root.
2.
Use a text editor to open the file:/usr/lib/X11/X0pointerkeys
3.
Find the line: # screen_orientation
4.
Remove the # sign at the beginning of the line to un-comment the line
5.
Save the file.
vertical
NOTE
In the /usr/lib/X11/X0screens file, Screen 0 (the bottom screen) is the
first screen named, and Screen 1 (the top screen) is the second screen named.
3.6.5 Native Language Support (NLS)
Changing the AdvaCommand Language
The Operator Station can be configured to call up all dialogs and operational displays (except
for RDP displays) in the following languages: English, French, German, and Russian.
Configuration of NLS is done by running the osLangSetup script as the ‘root’ user. The
syntax for the osLangSetup script is:
/opt/advant/MOD-OS/bin/osLangSetup language
where language is the desired language for the OS.
3BUR001 835R0001 REV C
3-29
If you run the osLangSetup script with no language argument, or the language argument
is ‘C’, then the OS will be restored to the default language (the default language is English).
Examples:
To configure the OS to German, log on as root and type:
/opt/advant/MOD-OS/bin/osLangSetup german
To configure the OS to English, log on as root and type:
/opt/advant/MOD-OS/bin/osLangSetup english
or
/opt/advant/MOD-OS/bin/osLangSetup C
or
/opt/advant/MOD-OS/bin/osLangSetup
The station must be rebooted for the changes to take effect.
For more information on NLS, refer to Appendix E, Native Language Support (NLS) Readme
File.
3.6.6 Traditional and Simplified Chinese Character Set
NOTE
If traditional Chinese is being installed, the size of the /usr LVM must be
increased by 150 Mbytes. Refer to the installation instructions in Chapter 1,
Introduction and Chapter 2, Installation of this book.
Simplified and traditional Chinese characters in user-built graphics are now supported. These
instructions outline the procedures to load and configure the font sets.
1.
Install either the simplified or traditional Chinese version of CDE from the CD. This
installs the message files, fonts, character maps, and so on that you will need, as well as
nlio and the input method server. The CD is not distributed by ABB and must be
purchased from Hewlett-Packard.
The station needs a PS2_DIN keyboard.
2.
3-30
To set the language to simplified or traditional Chinese and allow for character input:
a.
Login as root.
b.
Uncomment the appropriate lines in the files: $OS_CONFIG/mod.x11start and
$OS_HOME/etc/environment. In the case of X-terminals, uncomment the
appropriate lines in the /home/operator/.xsession file. More explicit
instructions are found in the comment sections of these files.
c.
For simplified Chinese, copy the file $OS_HOME/etc/kbdlang_S_Chinese to
the file /etc/kbdlang
d.
For traditional Chinese, copy the file $OS_HOME/etc/kbdlang_T_Chinese to
the file /etc/kbdlang
3BUR001 835R0001 REV C
Section 3.6.6 Traditional and Simplified Chinese Character Set
e.
Reboot the station.
To switch back to English, do the following:
3.
–
Add the comment metacharacter to the appropriate lines in the files:
$OS_CONFIG/mod.x11start and $OS_HOME/etc/environment. In the
case of X-terminals recomment appropriate lines in the
/home/operator/.xsession file.
–
Copy the file $OS_HOME/etc/kbdlang_US_English to the file
/etc/kbdlang
–
Reboot the station.
To use the Chinese character set in the Display Builder:
a.
Add exactly one of the following sets of lines to the end of the file:
$MODDB/lib/config/fontdef.dat
For simplified Chinese, size 18 font, add the line:
default raster 13
-hp--medium-r-normal--18-*-*-*-*-*-hp-schinese15
/* SChinese-med-r 18:18 FO */
For size 24 font, add the line:
default raster 13
-hp--medium-r-normal--24-*-*-*-*-*-hp-schinese15
/* SChinese-med-r 24:24 FO */
For traditional Chinese, size 18 font, add the line:
default raster 13
-hp--medium-r-normal--18-*-*-*-*-*-hp-tchinese15
/* TChinese-med-r 18:18 FO */
For size 24 font, add the line:
default raster 13
-hp--medium-r-normal--24-*-*-*-*-*-hp-tchinese15
/* TChinese-med-r 24:24 FO */
NOTE
The dynamic function keys can use either of these fonts. However, static text
elements and the display elements listed below only use the size 18 font.
3BUR001 835R0001 REV C
3-31
b.
Using the Display Builder, Chinese characters can be added as labels on dynamic
function keys, and to the following display elements:
CondDLink
CondPValue
CTarget
DLink
DynamicText
Pvalue
To start the Chinese input, press the right ALT Key. To stop the Chinese input, press the left
ALT key.
3.6.7 Adding a Page Selector Alarm Panel (PSAP) to the Operator Station
NOTES
•
You can currently have only one PSAP per Operator Station due to power
requirements on the system.
•
A PSAP needs an external power supply.
To add a Page Selector Alarm Panel (PSAP) to your Operator Station:
1.
Before plugging in the PSAP, power down the Operator Station.
2.
Daisy-chain the universal keyboard, the PSAP, and the mouse:
3.
a.
Unplug the mouse from the universal keyboard.
b.
Plug the PSAP into the output of the universal keyboard (where the mouse used to be
plugged in).
c.
Plug the mouse into the output of the PSAP.
Set the hexadecimal dial underneath the PSAP to a non-zero number code from 2 to 15
(a PSAP with a number code of 0 will not get installed, and the number 1 is generally
reserved for the universal keyboard).
NOTE
The dial underneath the PSAP must be set to the same number code that is entered
in the PSAP Definition dialog box in the Environment Builder. Refer to the
AdvaBuild Environment Builder User’s Guide for details.
4.
Restart the Operator Station.
3.6.8 Configurable Function Keys
Configurable Function Keys allows you to configure the function key definitions for the
Operator Station displays listed in Section B.1.1, Display Types. This feature allows you to
callup displays from the function keys.
3-32
3BUR001 835R0001 REV C
Section 3.6.8 Configurable Function Keys
You must modify a text file for each Environment defining the displays to be accessed by the
<F1> -< F10> keys. These definitions will take effect by installing the Environment.
This feature does not support External Applications, Set TCL Sequence State, Control Dialog,
Put Value Dialog, or Immediate Put Value from a function key. RDP display callup is limited to
the RDP displays which are listed in Section B.1.1, Display Types.
3.6.8.1 Text File Configuration
There is a default function key definition for all new Environments. You must modify the
Function Key configuration file for each Environment that will not use the default key
definitions.
The syntax for the lines of the configuration file is:
DISPLAY_TYPE;KEY_NAME;VISIBLE;KEY DESCRIPTION;TYPE;SCREEN;DISPLAY_NAME;parameters
Table 3-4 explains the definitions for each parameter.
Table 3-4. Syntax Descriptions
Syntax
3BUR001 835R0001 REV C
Description
DISPLAY_TYPE
The name of the display on which the function key definition
will appear. See Section B.1.1, Display Types for a list of all
available display types.
KEY_NAME
F1, F2, F3, F4, F5, F6, F7, F8, F9, F10
VISIBLE
Should KEY_NAME be displayed?
V - Visible or I - Invisible.
KEY DESCRIPTION
Text label to be displayed on the function key. To insert
multiple lines use the newline character (\n). Entering a
single space will cause the DISPLAY_NAME to be
displayed. The semicolon (;) character is not allowed within
this or any other field.
TYPE:
Defines if display is a base display or overlap display. (BASE
or OLAP).
SCREEN
Defines which screen display will appear on. (0 - current
display, 1, or 2).
3-33
Table 3-4. Syntax Descriptions (Continued)
Syntax
Description
DISPLAY_NAME
Any valid display name (that is, AREASTATUS,
GROUPTREND, UNITDETAIL, boiler1_graphic,…). If the
DISPLAY_NAME is not a member of DISPLAY_TYPE, then
it is assumed that it requires no parameters.
parameters
Semicolon-separated list of up to two parameters.
Parameters can be the actual values or keywords. For
example, AREASTATUS;SC5_1 or
AREASTATUS;CURR_AREA. See Section 3.6.8.2,
Supported Keywords for a complete list of supported
keywords.
Comment lines can be inserted into the definition file by starting the line with a ‘#’ character.
Any line beginning with the ‘#’ character will be ignored.
The function key configuration files are located in the directory:
/home/operator/persMenuUsers/
The configuration file names are of the format:
Environment.Function_Keys
where Environment is the name of the Environment that the configuration file applies.
3.6.8.2 Supported Keywords
Table 3-5, lists the keywords that can be used in the configuration file for the display
parameters.
Table 3-5. Keywords for the Display Parameters
Keyword
Meaning
Valid Scope
(Display Type)
PREV_AREA
Get previous area name from area list
HIERARCHY
NEXT_AREA
Get next area name from area list
HIERARCHY
CURR_AREA
Get current area name
HIERARCHY
PREV_GROUP
Get previous group name from group list
HIERARCHY
NEXT_GROUP
Get next group name from group list
HIERARCHY
CURR_GROUP
Get current group name
HIERARCHY
TOP_GROUP
Get top group name from current area
HIERARCHY
MID_GROUP
Get middle group name from current area
HIERARCHY
3-34
3BUR001 835R0001 REV C
Section 3.6.8 Configurable Function Keys
Table 3-5. Keywords for the Display Parameters (Continued)
Keyword
Meaning
Valid Scope
(Display Type)
BOT_GROUP
Get bottom group name from current area
HIERARCHY
CURR_LOOP
Get current loop name
HIERARCHY
PREV_OVER
Get previous overview name from overview list
OVERVIEW
NEXT_OVER
Get next overview name from overview list
OVERVIEW
CURR_OVER
Get current overview name
OVERVIEW
PREV_UNIT
Get previous unit name from unit list
TCL/BATCH
NEXT_UNIT
Get next unit name from unit list
TCL/BATCH
CURR_UNIT
Get current unit name
TCL/BATCH
CURR_SEQ
Get current sequence name
TCL/BATCH
CURR_LL_DEV
Get current LadderLogic device name
LADDERLOGIC
3.6.8.3 The default.Function_Keys File Information
Every new Environment will have a configuration file named:
/home/operator/persMenuUsers/Environment.Function_Keys
that will be a copy of the default function key definitions file named:
/home/operator/persMenuUsers/default.Function_Keys
The default function key definition file is listed in Section B.1.2, The default.Function_Keys
File Listing.
This file may be changed to contain more default definitions.
3.6.8.4 Errors
The syntax of the text files is checked when you install the Environment, and a log file is
generated containing information on any function key definition that contains an error. The log
file’s full path name is:
$OSLOGDIR/Environment.Function_Keys_Log
where Environment is the name of the Environment that the log file applies to. When a
display is called up, function keys which contained an error in the definition file will be marked
with the ‘*’ character.
In cases where the syntax is correct, but the display cannot be located at run-time, the function
key will be grayed-out.
The function keys for graphics (AREA, GROUP, and UNIT) will be grayed-out if there is no
graphic defined in the Environment.
3BUR001 835R0001 REV C
3-35
3.6.9 Operator Station Peripheral Devices General Information
The Operator Station supports various peripheral devices. Table 3-6 lists these devices and
provides references to installation and configuration information.
Table 3-6. Operator Station Peripheral Devices with References
Peripheral Device
Installation Information
Configuration Information
Printers
None required
Section 3.6.11, Printer Setup
Alarm/Event
Loggers
None required
Section 3.6.12, How to Configure
Alarm/Event Loggers
SCSI Disk and DAT None required
drives
Section 3.6.14, SCSI Device
Information
Security Key
None required
Section 3.6.15, Security Key
Serial Expansion
Unit (SEU)
Section 2.2.14, Installing the Section 3.6.16, Configuring the
Serial Expansion Unit (SEU) Serial Expansion Unit
Touchscreen
Section 2.2.15, Installing the Section 3.6.17, Configuring
Touchscreen
External Display Access for Xtouch
Instructions for making cable connections between the Operator Station and the various
peripherals are provided in the applicable Advant Station Hardware User’s Guide, refer to
Section 1.5, Related Documentation.
In addition to hardware considerations, there are certain procedures that you must perform in
HP-UX to make the devices operational. These procedures are described in HP-UX Installing
Peripherals. In addition, you can use the HP-UX on-line documentation utility man pages to
get detailed instructions on any of the HP-UX commands.
This section provides a brief overview of these functions and describes device-specific
parameters required for peripherals connected to the Operator Station.
Device Files
The HP-UX operating system uses special files called device files to perform I/O to peripheral
devices. Each peripheral in your system requires an associated device file. Pre-defined device
files already exist on the HP-UX system. Device files are located in the /dev directory, or in
one of its subdirectories. If a device file that is appropriate for your application already exists,
you can use it; otherwise, you must create a new one.
If you choose not to use an existing device file, there are two ways to create a new device file. If
you use SAM (System Administration Manager) to add an HP peripheral, you can choose to
have SAM automatically create the device file. (To access SAM in HP-UX, you must know the
root password.)
3-36
3BUR001 835R0001 REV C
Section 3.6.10 AdvaBuild Device Special File
If you are not using SAM, or if you choose not to have SAM create the device file, you must use
the mknod function to create the device file. You invoke mknod via a command line in a
terminal window. You can open a terminal window via the Terminal Window menu item in the
Station menu. You must be a superuser to use the mknod function.
3.6.10 AdvaBuild Device Special File
The syntax for the mknod command is:
mknod /dev/ttyap0 c 1 0x0b00c0
where:
mknod
is the Command.
/dev/ttyap0
is the Device Special File Name.
a - port number (0 for port A or 1 from port B)
The name shown here is typical. Other names can be substituted. Refer to the applicable HP documentation for details regarding syntax for Device Special File Name. This
name must be entered on the Serial Port Configuration
display.
c
is the Character Special File
1
is the Major Number
0x0b00c0
is the Minor Number
b - port number (1 for port A or 2 for port B)
c - flow control (1 for most systems, 0 for B132L machine
ports not using flow control; for devices such as the
datakey and touchscreen)
The following is an example of the command used to create a device file for port A on a
non-B132L system:
mknod /dev/tty0p0 c 1 0x010010
After you create a device file, you should change the protection on it so that everyone has
read/write permission by entering the command:
chmod 666 <device file name>
NOTE
You must be a Superuser on the Advant Station to use the mknod command.
3BUR001 835R0001 REV C
3-37
3.6.11 Printer Setup
Printers can be connected to an Operator Station node to support Loggers and application
printing. Loggers and RDP applications require line printers to support the dot-matrix format. If
a printer is configured to be used by a logger, it can also be used by other applications. Laser
printers should be capable of printing both ASCII and PostScript text. (TCL files require
PostScript. Other applications require ASCII.)
There are three steps to setup a printer on the Advant Station:
1.
Connect the hardware.
2.
Configure the printer into the HP-UX operating system
3.
Make the HP-UX printer available to the Advant applications.
3.6.11.1 Hardware Connection
The printer connection can be made via either a serial or parallel interface. The logger and line
printer cannot share the same printer if the printer is using parallel communications. Attempting
this will cause unexpected results. If the logger and line printer share the same printer, then the
printer should be set up for serial communications, which allows concurrent access between the
logger and line printer. Otherwise, the logger should be dedicated to the printer with parallel
communications.
3.6.11.2 HP-UX Printer Configuration
You can use either the SAM, utility or HP-UX printer administration commands to create a
printer in the HP-UX operating system on the Advant Station.
The SAM utility has help menus to aid you in setting up a printer. To run SAM, log on as root
and type sam.
To configure a printer using the HP-UX printer administration commands, do the following:
1.
Log in as root.
2.
Turn off the print spooler:
ps -ef | grep lp
[UNIX will return a process id, <pid>]
kill -9 <pid>
3-38
3BUR001 835R0001 REV C
Section 3.6.11 Printer Setup
3.
Add a printer to the spooler:
/usr/lib/lpadmin -p<printer_name> -m<printer_type> -v/dev/<ttynn>
where:
<printer_name> is the name you assigned to the printer in the Logger Template. You must
use the same name.
<printer_type> is alGenicom for Mannesmann and Genicom printers.
<ttynn> is the device file specification for the serial port to which you will connect the
printer. Verify that the communication ports are configured correctly by entering ll
/dev/tty0* for serial ports, and /dev/*_lp for the parallel port, and comparing the
results with Table 3-7 below.
Table 3-7. Advant Station Communication Ports Information
Port
Parallel Port
Device File Name
/dev/c1t0d0_lp or
Major Number
Minor Number
216
0x010002 or
0x020002
/dev/c2t0d0_lp
Serial Port 1
/dev/tty0p0
1
0x000000
Serial Port 2
/dev/tty1p0
1
0x010000
The major and minor numbers are shown in the two columns to the left of the date, in the
output of the ll command.
4.
Enable the printer by entering:
enable <printer_name>
5.
Accept the printer by entering:
/usr/lib/accept <printer_name>
6.
Restart the spooler by entering:
/usr/lib/lpsched -a
7.
Check the printer status by entering:
lpstat -t
8.
Test the printer by entering:
lp -d<printer_name> <test_file_name>
where <test_file_name> is any small text file. You can use: /etc/hosts.
NOTE
Although UNIX allows multiple printers to be configured on a single port, it is
recommended that you configure only one printer per port. Proper operation of
the logger cannot be ensured if multiple printers share a single port.
3BUR001 835R0001 REV C
3-39
3.6.11.3 Make Printer Available to Advant Applications
RDP Applications
Configure a printer in the Serial Port Setup templet for the node where the printer is attached.
See the System Configurator User's Guide if you are not familiar with this templet.
You must configure the PORTS object templet of the node where the printer resides. The PORT
NAME is the same as the HP-UX printer name configured in Section 3.6.11.2, HP-UX Printer
Configuration. The PORTS templet is a child of the GENERICD templet in the Template
Builder. For more information on the PORTS object, refer to the AdvaBuild Engineering
Methods for Systems with MOD 300 Software instruction book.
Other Advant Applications
Many Advant applications, such as the Structure Builder, Function Chart Builder, and the
Template Builder, use the HP-UX default printer as their application printer. To change an
HP-UX printer as the default, you can use SAM, or use the lpadmin command.
To make a printer the default printer using the lpadmin command, enter:
lpadmin -d<printer_name>
where <printer_name> is the name you assigned to the printer when you created it. You must
use the same name.
Display Builder Application
Display Builder displays can be printed by selecting a printer from the Display Builder Printer
dialog box. In order for printers to be listed in the Printer dialog box, you must first create an
ASCII file named dbPrinters.dat in the $MODDB/lib/config directory. In this file,
list the available printers followed by their logical names. That is, enter the name of the printer,
a space, and the logical name of the printer, which is what will be displayed in the Printer dialog
box. For example, if you enter
ps1 colorPSPrinter
the colorPSPrinter will be included in the Printers list in the Printer dialog box.
NOTE
Include the default printer in the dbPrinters.dat file. This allows you to
print display objects from the AdvaBuild Structure Builder.
3-40
3BUR001 835R0001 REV C
Section 3.6.12 How to Configure Alarm/Event Loggers
3.6.12 How to Configure Alarm/Event Loggers
Alarm/Event Detection and Notification
The system detects the occurrence of an event through the interaction of several software
packages. The process starts with the Data Base Manager Service (DBMS), which resides in the
memory of every node (subsystem and control module) in the system. When the DBMS detects
a parameter change, it determines if an event has taken place by checking the parameter change
against two event tables. One table is static and contains a list of the standard events. The other
table contains a list of the events defined specifically for an individual system.
When the DBMS determines an event has taken place, it relays the information to the
Alarm/Event Handler. The Alarm/Event Handler, in turn, notifies the appropriate applications
and devices in the system. Some applications/devices, such as TCL runtime modules, are
automatically notified. Other devices, such as Loggers and Historical Recorders, must be
targeted for notification by configuring the Message Center attribute for the AREA object.
During runtime, Configurable Control Functions (CCF) checks the status of alarms. When an
alarm becomes active, CCF passes that information to the Alarm/Event Handler.
Refer to the AdvaCommand Basic Functions User’s Guide for a detailed discussion of the
following Alarm/Event Handling features:
•
Alarm and event display and acknowledgment
•
Suppression of alarm and event messages
•
Alarm display setup
Alarm/Event Logging
The Alarm and Event Logger software generates a printed log of alarm, event, TCL Billboard,
and system error messages on printers. To implement alarm/event logging functionality in your
system, you must configure loggers in the database. A logger is a software device that reports
and records messages addressed to it from elsewhere in the system. Loggers can be configured
for Multibus-based consoles and data processors, and Advant Station-based Operator Stations,
Engineering Stations, and Information Management Stations. Each subsystem is limited to a
maximum of one logger.
Refer to the AdvaCommand Basic Functions User’s Guide for a detailed discussion of the
following Alarm/Event logging features:
•
Logger control
•
How to read the Alarm/Event log
•
Alarm/Event message formats
Alarm/Event Logger Considerations
If you are connecting an Alarm/Event Logger:
•
3BUR001 835R0001 REV C
The PRINTER_NAME you assign to the printer must be the printer name used on the
LOG_DETL object (Logger Template) in the MOD 300 database.
3-41
•
The PRINTER_TYPE must be either alEpson or alGenicom.
Also, you must configure the following objects in the MOD 300 database:
•
On the AREA object (parent of the subsystem object), make entries for the Logger in the
MESSAGE CTR edit window.
•
Assign and configure a LOG_DETL object (Logger Template) as a child of the
GENERICD object for the subsystem. The LOG_DETL object defines the operating
parameters of the logger.
Refer to Section 3.2.2, How to Configure Database Objects to Support Alarm/Event Logging,
for information about configuring the AREA and LOG_DETL objects.
Refer to Section 3.6.11.2, HP-UX Printer Configuration, for information about configuring the
Logger printer in HP-UX. You should place the logger into the OFF or HOLD state when you
are creating a printer in HP-UX.
Helpful Hints
•
When configuring the Logger Template in the MOD 300 database, you still need to enter a
printer name. For the sake of consistency, you may want to use the same name for the
Logger template (the logger name) and the Printer Name field in the Logger Template.
This will make your logger name and your printer name the same.
•
The AS500 baud rate to the printer is 9600, but the Multibus to printer baud rate is 4800.
Therefore, there is a configuration change required for the Genicom printer. If garbage
comes out when you print the test file, you probably have a baud rate problem.
Printer Straps A should be as follows (changes are underlined):
12345678901234567890123456789012
11000000101100000000000000000000
3-42
3BUR001 835R0001 REV C
Section 3.6.13 External Alarm Annunciation Configuration
•
The complete Genicom printer configuration is reproduced below:
Figure 3-12. Genicom Printer Configuration
3.6.13 External Alarm Annunciation Configuration
The external annunciator feature of the AdvaCommand software allows you to connect an
external horn or similar alarm device to a digital output FCM, that can be triggered by alarm
messages, TCL messages, diagnostic messages, and operator acknowledgments.
External alarm annunciation uses a CCF continuous loop containing a digital output FCM. The
digital output FCM supports a 16 bit output. The alarm loop triggers digital outputs based on
events processed by AdvaCommand. There is one predetermined loop name for each
workstation based on the DCN address.
3BUR001 835R0001 REV C
3-43
Once an event is detected by AdvaCommand, the value of the digital output FCM is changed on
the external alarm loop. The digital output FCM can be used to drive external annunciators, and
CCF loops or TCL Sequences. Multiple loops can be processed to provide redundant
annunciation.
3.6.13.1 Enabling External Annunciation in an Environment
External annunciation is configured as part of the environment from the Operator Station Setup
Display of the Environment Builder. There is a column of push buttons labeled External Alarm
Enabled on the right hand side of the scrollable window. External annunciation is enabled by
selecting these buttons.
There is one button for each of ten possible types of events. These events are:
•
CCF HIGH PRIORITY
•
CCF MED PRIORITY
•
CCF STD PRIORITY
•
RINGBACK TIME
•
TCL HIGH PRIORITY
•
TCL MED PRIORITY
•
TCL STD PRIORITY
•
DIAG FATAL
•
DIAG NON-FATAL
•
SPC TIME (STD, MED, HIGH)
For more information on the Environment Builder, refer to the AdvaBuild Environment Builder
User’s Guide.
3.6.13.2 External Alarm CCF Loop Configuration
The external alarm CCF loop name is EXTALM##, where ## is the Operator Station’s zero
padded hexadecimal node address. For example: If an Operator Station has a DCN address of
3D00, the external alarm loop name is “EXTALM3D.” If the DCN node Address is 1, the loop
name is “EXTALM01.”
The external alarm loop must be a continuous loop that contains a digital output FCM named
“DOT”. Each time an event is detected, the DOT FCM output is set. The output FCM must
always be in manual mode. Each bit in the DOT FCM is associated to a particular event.
The output of the DOT FCM can be mapped to a series of contiguous output channels ranging
from 1 to 16. The external alarm functionality uses the first 11 channels. Refer to the
Configurable Control Functions User’s Guide for more information on the digital output FCM.
As the value of the DOT FCM is changed by the external alarm function, the changes are
updated. Each change represents one bit of a 16 bit variable. Refer to Table 3-8 for the output
channel and message type correlation.
3-44
3BUR001 835R0001 REV C
Section 3.6.13 External Alarm Annunciation Configuration
.
Table 3-8. DOT FCM Message Types / Bit Definitions
Message Type
Bit Position
(Output Channel)
All Unacknowledged Messages
01
Unacked CCF High Priority
02
Unacked CCF Med Priority
03
Unacked CCF Std Priority
04
CCF Ringback
05
Unacked TCL High Priority
06
Unacked TCL Med Priority
07
Unacked TCL Std Priority
08
Unacked Fatal Diagnostic
09
Unacked Non-Fatal Diagnostic
10
Unacked Statistical Process Control (SPC)
11
The first bit in the DOT FCM represents all unacknowledged messages. When an event is
detected, the first bit is set as well as the bit for the specific message type.
The DOT FCM can drive different I/O types such as direct I/O, TRIO, S100, and S800. The
DOT FCM can be an input for CCF loops or TCL Sequences. External annunciators can be
wired to the I/O devices of other loops. The loops from several Operator Stations can be
connected with logic to provide a redundant annunciator that can be silenced from any Operator
Station keyboard or screen.
Acknowledgment Considerations
When an active message type is acknowledged, the bit associated with that message type will be
cleared even though there are other unacknowledged active messages for the same type. This
also applies to the bit representing all unacknowledged messages. If any active message type is
acknowledged, the bit representing all unacknowledged messages is cleared even though other
active messages exist.
When the “Silence Key” is selected, all the bits are cleared and ‘0’ is written to the DOT FCM.
3BUR001 835R0001 REV C
3-45
3.6.14 SCSI Device Information
The DAT drive should be installed at SCSI port 3.
CAUTION
Do not connect or disconnect any SCSI device while the system is running or turn
power on or off to any SCSI device while it is connected to a powered-up system.
Do not add or remove SCSI devices while the system is powered on. Doing so
could result in data corruption or a system panic, which in turn could lead to
corruption of the file system.
If you need to change the bus address for a SCSI device, be sure to perform the task in the
following sequence:
1.
Shut down your system.
2.
Turn off the SCSI device.
3.
Change the SCSI device bus address.
4.
Turn on the SCSI device. Turn on power to all SCSI peripherals and make sure they have
time to complete their self-test before powering on the Advant Station System Unit.
5.
Reconnect the power cord to the Advant Station System Unit.
6.
Turn on the power to the Advant Station System Unit.
NOTE
The SAM function is not applicable for DAT devices.
3.6.15 Security Key
The Security Key, also known as the DataKey, is a plastic, key-like device designed to enhance
password security. The key can be read from or written to with a Security Key interface unit.
The key itself contains EEPROM read/write memory.
Once written to, the Security Key is easy to operate. When the key is inserted and turned in the
interface unit, the Operator Station verifies the user information and either autologs the user on,
or continues a security check by requiring a password. The log on and log off information can
be routed to the history package and/or a logger. The message sent contains the time and the
individual's name.
3-46
3BUR001 835R0001 REV C
Section 3.6.15 Security Key
Keys previously programmed for use in MOD300 console subsystems will not be usable
without reprogramming.
Figure 3-13. An Example of a Security Key
3.6.15.1 Security Key Configuration Programs
There are two programs (datakey and datakeyRead) that support the security key. These
programs can only be executed by the root user. The programs must be run before starting up
the AdvaCommand software. Before you run these programs, you must set your environment
variables, and configure a datakey serial port.
To set the environment variables enter:
. /home/ocsmgr/etc/ocsEnvironment
To configure a datakey serial port, do the following:
1.
Enter: ln -s /dev/tty0p0 $IPA_DEV/datakey1
NOTE
/dev/tty0p0 is serial port 1, and /dev/tty1p0 is serial port 2 on most
stations. Replace this with the appropriate serial port.
2.
If a second datakey port is needed, repeat the previous command, changing datakey1 to
datakey2, and select a new serial port to replace /dev/tty0p0.
If the datakey is no longer needed, and you want to disable it, remove the link file that was
created in the steps above by entering:
rm $IPA_DEV/datakey1
or
rm $IPA_DEV/datakey2
depending on which serial port the datakey is on.
3BUR001 835R0001 REV C
3-47
The datakey Program
The datakey program will program a key with a user’s name, password, and logon/logoff
options. If a key is not in the reader, the program will request that one be inserted. The usage for
the datakey program is as follows:
datakey <port> <name> <password> [-a] [-l]
where:
port is the datakey port (1 or 2)
name is the username
password is either a password or one of the following
-a specifies to auto logon when the key is inserted and turned
-l specifies to auto logoff when the key is removed
Example 1-- card for user “ed,” password “eddie,” on port 1
datakey 1 ed eddie
Example 2-- card for user “joe,” password “schmoe,” autologoff, on port 1, key not in reader
datakey 1 joe schmoe -l
Please insert a key to continue
Example 3-- card for user “burns,” autologon, autologoff, on port 1
datakey 1 burns -a -l
Security Key Reader Program
The datakeyRead program will read the contents of a key and display the username,
password, and the auto logon or auto logoff modes that are enabled on the key. If a key is not in
the reader, it will request that one be inserted. The usage for the datakeyRead program is as
follows:
datakeyRead <port>
port is the datakey port (1 or 2)
Example 1 -- card for user “ed,” on port 1
datakeyRead 1
This key is assigned to ed(eddie)
Example 2 -- card for user “joe,” on port 1
datakeyRead 1
This key is assigned to joe(schmoe)
This key is configured to log OFF automatically
3-48
3BUR001 835R0001 REV C
Section 3.6.16 Configuring the Serial Expansion Unit
Example 3 -- card for user “burns,” on port 1, key not in reader
datakeyRead 1
Please insert a key to continue
This key is assigned to burns(master)
This key is configured to log ON automatically
This key is configured to log OFF automatically
3.6.16 Configuring the Serial Expansion Unit
Serial device nodes and parallel device nodes should have already been made when the SEU
was installed according to Section 2.2.14, Installing the Serial Expansion Unit (SEU).
3.6.16.1 Making Serial and Parallel Device Nodes
A Central Data utility named cdmknods has been provided that greatly simplifies the process
of making nodes for SEU devices, if necessary. For more information, type the command:
man cdmknods
For example, if you wish to make default nodes for a SEU at SCSI ID 4, simply type the
command:
/usr/local/bin/cdmknods –product ST-1008 –target 4
Table 3-9 shows how the serial ports on the back of the SEU correspond to the Operator Station
device drivers.
Table 3-9. SEU Serial Ports Corresponding to OS Device Drivers
SEU port
OS dialup device
driver
OS local
device driver
X3
/dev/ttyc40
/dev/ttyC40
X4
/dev/ttyc41
/dev/ttyC41
X5
/dev/ttyc42
/dev/ttyC42
X6
/dev/ttyc43
/dev/ttyC43
X7
/dev/ttyc44
/dev/ttyC44
X8
/dev/ttyc45
/dev/ttyC45
X9
/dev/ttyc46
/dev/ttyC46
X10
/dev/ttyc47
/dev/ttyC47
The parallel port “X11” on the back of the SEU corresponds to the Operator Station device
driver “/dev/lpC48”.
3BUR001 835R0001 REV C
3-49
3.6.16.2 Connecting Terminals to the SEU
To begin using terminals with SEU, you will need to cable the terminal(s) to the SEU properly
and set up the terminal characteristics.
1.
Power up the terminal. Initially set the terminal parameters to the following defaults:
Baud Rate
9600
Bits per character
8
Parity
none
Stop bits
1
Flow control
XON/XOFF
You may need to refer to the manual for the specific terminal to learn how to do this.
2.
Run a cable between the terminal and any serial port of the SEU. Since the SEU ports use
the DTE RS-232 device pinout, you will need either a null modem cable or a standard
RS-232 cable and a separate null modem adapter.
Null modem cables and adapters are widely available commercially.
3.6.16.3 Connecting Modems to the SEU
The SEU supports Carrier Detect (CD), Ready To Send (RTS), Clear To Send (CTS), Data Set
Ready (DSR), and Data Terminal Ready (DTR). Below are a few helpful hints for the successful
use of modem control signals.
HP-UX enforces a tty device node standard which specifies the meaning of the 4 least
significant bits of the minor device number. As previously defined, to enable the use of
hardware flow control, bit 3 of the serial port’s minor device number must be set (0x8 must be
“ORed” into it). In addition to this, a part of the HP-UX operating system called the line
discipline must be informed of your intent to use hardware flow control. This is specified by
using the “crts” termio configuration. For a login terminal this is specified in /etc/gettydefs. For
a manually configured line, this is specified as an argument to the stty command. Often when
hardware flow control is used, XON/XOFF flow control needs to be turned off so that the XON
and XOFF characters are not interpreted by the line discipline. These can be disabled with
“-ixon” and “-ixoff” arguments. Note that the minus sign (“-”) in front of these arguments
means they are turned off, whereas the absence of the minus sign means they are turned on.
Alternatively, if XON/XOFF flow control is to be used, bit 3 of the minor device number must
be reset, and “ixon” and “ixoff” set. “ixany” can be set instead of “ixon” to specify the restarting
of output upon the receipt of any character. “-ixany” specifies the restarting of output only upon
the receipt of the XON character.
3-50
3BUR001 835R0001 REV C
Section 3.6.17 Configuring External Display Access for Xtouch
3.6.17 Configuring External Display Access for Xtouch
If you have installed the Xtouch™ (touchscreen) software, you can use External Display Access
to place Xtouch on the Display Menu of the Operator Station main window.
To configure External Display Access, do the following:
1.
Under the Display Menu, select EXTERNAL APPLICATIONS….
This displays the External Applications submenu of the Display Menu.
2.
Under the External Applications Display Menu, select EnvirBuilder.
3.
Create a new environment (or select a previously existing environment).
This calls up the Environment Top Level Display.
4.
Click on the External Display Access button on the Environment Top Level Display.
This displays the External Display Access dialog box.
5.
Choose New from the File menu in the External Display Access dialog box. This displays
the External Display Access Add dialog box.
6.
Define the External Display Access information for Xtouch:
a.
Select the External Display Name field and enter TouchScreen
b.
Select the Class field and choose an access class operator for TouchScreen.
c.
Select the Display Type field and choose ExternalApp.
d.
Select the Definition field and enter the following lines:
$OS_HOME/bin/startXtouch
e.
Click on OK, then select Quit from the File menu to exit the External Display
Access Add dialog box.
7.
Select Close from the File menu to exit the External Display Access dialog box.
8.
Click on the Environment Top Level Display’s Exit button, then return to the
LOGINPAGE and install the environment.
Xtouch now appears under the External Applications submenu of the Display Menu.
3.6.18 X-Terminal Installation
3.6.18.1 AdvaCommand osXConfig for HP and PC X-Terminals
The osXConfig program modifies the X-terminal configuration and is used only when
configuring the AdvaCommand X-terminal.
If you are configuring X-terminals for AdvaBuild only, do not use this program.
3BUR001 835R0001 REV C
3-51
1.
Log on as user root
2.
Enter:
/opt/advant/MOD-OS/bin/osXConfig
You will see one of the following messages:
–
A font server daemon has been started. You can now enable
client systems to use this font server. This can be done
interactively by configuring the systems as font clients
during their initial system startup or by running
‘/sbin/set_parms font_c-s’ on each one.
You can also run the script command
‘/usr/sbin/mk_fnt_clnt’ on a system to configure it as a
font client.
–
3.
A font server is already setup to run.
You will see the following prompt:
Enter the maximum number of AdvaCommand clients to configure
[1-4]:
Enter the number of OS client (this should include the host station if it is running
AdvaCommand).
4.
Depending on which X-terminals you have, proceed to Section 3.6.18.2, HP X-Terminal
Configuration Procedures and/or Section 3.6.18.3, PC X-Terminal Configuration
Procedures.
3.6.18.2 HP X-Terminal Configuration Procedures
X-Terminal Administration Program (xtadm)
1.
3-52
Login as root.
3BUR001 835R0001 REV C
Section 3.6.18 X-Terminal Installation
2.
Enter: /opt/hpxt/enware2/lbin/xtadm. You will see the following message and
menu:
Initializing...
_________________________________________________
HP NETSTATION ADMINISTRATIVE TASKS
MAIN MENU
1) Add a netstation
2) Remove a netstation
3) Printers, plotters
4) Installation testing
5) XDM Administration
6) Manage software versions
?) Help
x) exit
Please enter selection (default=1): 1
_________________________________________________
3.
Enter 1 to add a netstation. You will see the following message:
ADD A NETSTATION
To add a netstation to this computer you will need to obtain
the following information from your local network
administrator:
* The name you want to call the netstation (network
hostname).
* The internet protocol (IP) address of the netstation.
* The LAN hardware (link level) address of the netstation.
(From the boot screen or shipping carton of the
netstation)
If the network you are adding the netstation to is connected
to other networks you will also need to know:
* The subnet mask of the netstation.
* The internet protocol (IP) address of the default gateway.
Continue adding a netstation [y|n] (y): <Return>
3BUR001 835R0001 REV C
3-53
4.
Press the <Return> key to continue. You will see the following message:
ADD A NETSTATION
Enter name of netstation to add [q|?] :
5.
Enter the host name of the X-terminal. You will see the following message:
Got IP address of xxx.xxx.xxx.xxx for <hostname> from NIS.
The LAN hardware address of an HP netstation is shown on
its boot screen and its shipping carton label.
Enter LAN hardware address of netstation [q|?] :
6.
Enter the LAN hardware address of the X-terminal. This is a the 12 character address of
the X-terminal’s ethernet hardware. You will see the following message:
Enter subnet mask in dot notation [q|?] (none):
7.
Get the subnet mask from your network administrator and enter it now. You will see the
following message:
Enter gateway IP address in dot notation [q|?] (none):
8.
Get the gateway address, if any, and enter it now. You will see the following message:
You have entered the following network parameters for this
netstation:
Name:
hostname
IP address:
xxx.xxx.xxx.xxx
LAN hardware address:xxxxxxxxxxxx
Subnet mask:
xxx.xxx.xxx.xxx
Default gateway IP address:xxx.xxx.xxx.xxx
Are these correct? [y|n|?] (y):
9.
Press <Return> if the information is correct. You will see the following message:
<X-terminal hostname> added to /etc/bootptab.
NFS is running on this computer …
Use <OS hostname> as NFS server for this netstation? [y|n|?]
(y): <Return>
3-54
3BUR001 835R0001 REV C
10. Press <Return>. You will see the following message
Configuration file /opt/hpxt/enware2/config/
<X-terminal hostname>.cfg created.
Most HP netstations will automatically attempt to boot using
NFS.
Some older models may need to be manually configured to do
this.
Please make sure that terminal is set to boot using NFS, e.g.
On HP X term terminal: <press and hold F12> <click Network>
<click tftp -> NFS> <click Save/OK>
enter <return> to continue: <Return>
11. Follow the instruction for configuring the X-terminal to use NFS for booting and press
<Return>. You will see the following message
xdm is not running. Do you want to start xdm? [y|n|?] (y)
<Return>
12. Press <Return>. You will see the following message:
This selection will:
1) Check if xdm is being started up from /etc/inittab. If
this is not the case, /etc/inittab will be edited in
order to start up xdm automatically whenever your host
computer boots.
and
2) After prompting you, xdm will be started up
immediately.
copied existing /etc/inittab to /etc/inittab.orig.8482
Add xdm start-up code to /etc/inittab ? [y|n] (y):
<Return>
13. Press <Return>. You will see the following message:
xd:234:respawn:/usr/bin/X11/xdm -config
/usr/lib/X11/xdm/xdm-config -nodaemon < /dev/null >
/dev/null 2>&1
Above entry appended to /etc/inittab.
Start xdm running now? [y|n|?] (y): y
3BUR001 835R0001 REV C
3-55
14. Enter y. You will see the following message:
xdm has been started.
xdm is already running
This netstation will start using xdm after powerup if factory
defaults
in the Startup config screen have not been changed.
Copy .xsession script to a user home directory? [y|n|?]
(def=y): n
15. Enter n. You will see the following message:
Add another netstation? [y|n] (y):
Enter y to add additional netstations. Once you are done adding netstations, enter n.
16. You will see the following menu:
_________________________________________________
MAIN MENU
1) Add a netstation
?) Help
x) exit
Please enter selection (default=1): x<Return>
17. Enter x and press <Return>.
18. Enter: chmod 666 /opt/hpxt/enware2/config/*.cfg
Additional Configuration for HP X-Terminals (Envizex II)
3-56
1.
Power-up the HP X-terminal.
2.
Stop (Abort) the boot process by clicking on the stop button.
3.
Click on the Setup button.
4.
Click on the Network button.
5.
Click on the File Server button.
6.
Enter the IP address of the Advant server station (file server).
7.
Click on the Ethernet button.
3BUR001 835R0001 REV C
8.
Enter the IP address of the X-terminal in the address field.
9.
Enter 255.255.255.0 in the Subnet Mask field.
10. Enter the terminal name (host name) of the X-terminal in the Terminal Name field.
11. Set Parameters From to Download From Host (BOOTP/DHCP).
12. Enter the IP address of the Advant server station in the DHCP Client ID field.
13. Click on the Exit button.
14. Click on the Save and Quit button.
15. Turn the power off on the X-terminal. It is now configured.
NOTE
After configuring, to access the HP Netstation Configuration Utility while the
X-terminal is running, press and release < ALT-F12>. The X-terminal would
normally use <F12> for this function, but this key is used for the AdvaCommand
ramp-up function.
3.6.18.3 PC X-Terminal Configuration Procedures
This section, step 1 - step 9, does not need to be done if the xtadm program was already run as
part of Section 3.6.18.2, HP X-Terminal Configuration Procedures. The xtadm program only
needs to be run once.
X-Terminal Administration Program (xtadm)
1.
3BUR001 835R0001 REV C
log in as user root.
3-57
2.
Enter: /opt/hpxt/enware2/lbin/xtadm
You will see the following message and menu:
Initializing...
_________________________________________________
MAIN MENU
1) Add a netstation
?) Help
x) exit
_________________________________________________
3.
Enter 5 to enter XDM administration. You will see the following menu:
_________________________________________________
XDM ADMINISTRATION MENU
1) Check operation of xdm
2) Start xdm
3) Create .xsession script in user’s home directory
4) Stop xdm
5) Enable/disable xdm password aging
6) Enable/disable xdm root login
7) Trim xdm logfile
?) Help
p) previous menu
3-58
3BUR001 835R0001 REV C
4.
Enter 2. You will see the following message:
This selection will :
1) Check if xdm is being started up from /etc/inittab.If
this is not the case, /etc/inittab will be edited in
order to start up xdm automatically whenever your host
computer boots.
and
2) After prompting you, xdm will be started up
immediately.
copied existing /etc/inittab to /etc/inittab.orig.3836
Add xdm start-up code to /etc/inittab ? [y|n] (y): y
5.
Enter y.
xd:234:respawn:/usr/bin/X11/xdm -config
/usr/lib/X11/xdm/xdm-config -nodaemon <
/dev/null > /dev/null 2>&1
Above entry appended to /etc/inittab.
Start xdm running now? [y|n|?] (y):y
6.
Enter y. You will see the following message:
xdm has been started.
Please type <Enter> to continue
3BUR001 835R0001 REV C
3-59
7.
Press <Return>. You will see the following menu:
_________________________________________________
XDM ADMINISTRATION MENU
1) Check operation of xdm
2) Start xdm
3) Create .xsession script in user’s home directory
4) Stop xdm
5) Enable/disable xdm password aging
6) Enable/disable xdm root login
7) Trim xdm logfile
?) Help
p) previous menu
Please enter selection (default=1): p
8.
Enter p. You will see the following menu:
_________________________________________________
MAIN MENU
1) Add a netstation
?) Help
x) exit
Please enter selection (default=1): x<Return>
9.
Enter x and press <Return>.
3.6.18.4 PC with Reflection X X-Terminal Software Configuration
You must use WRQ Reflection X X-terminal server software version 6.2. On a PC X-terminal,
configure your PC operating system to use only 256 colors.
Following are the instructions for configuring the Reflection X X-terminal software:
3-60
1.
Start the Reflection X program. If a window titled “Select XDMCP Host” appears, select
Cancel.
2.
Select New XDMCP Connection from the Connection menu in the menu bar.
3BUR001 835R0001 REV C
3.
In the Connection Settings box, select Direct from the Method pull-down menu.
4.
In the Connection Settings box, enter the hostname or IP address of the Advant
workstation you are connecting to.
5.
Select Window Manager from the Settings menu in the menu bar. The window titled
“Reflection X Settings” appears.
6.
In the Window Mode box, under Window Manager Settings, click on the X Terminal
Desktop radio button.
7.
From the Category window, select the Fonts icon.
8.
Add the text tcp/<Hostname/IP>:7000 to the beginning of the contents of the Font
Path field where <Hostname/IP> is the hostname or IP address of the Advant workstation
you are connecting to. The Font Path field should read:
tcp/<Hostname/IP>:7000 sun ibm hp dec 100dpi misc
9.
In the Options box, enable Retain Font Server Fonts by clicking on it.
10. From the Category window, scroll down and select the Color icon.
11. In the Options box, enable Animate Palette in Background and Realize Palette in
Background by clicking on them.
12. From the Category window, scroll down and select the Keyboard icon.
13. In the Options box, disable Backspace Key Sends Delete by clicking on it.
14. In the Host Keyboard box, select HP.
15. In the Keyboard Map box, select Customize. The window titled “Keyboard Remapping”
appears.
16. Select the Key Attributes radio button on the right side of the window.
17. Select the F11 (11) key in the PC Keyboard box.
18. Disable AutoRepeat by clicking on the box in the Set column.
19. Repeat step 17 and step 18 for the F12 (12) key.
20. Select the Legend radio button in the right side of the window.
21. You need to re-define six PC keyboard keys according to Table 3-10 below. To re-define
each key:
3BUR001 835R0001 REV C
a.
select it in the PC Keyboard box
b.
click on the Characters button in the middle of the window
c.
select Keyboard from the pull-down menu below the Function Keys radio button
d.
select the desired definition (Table 3-10) from the scroll window
e.
click on the Map button
3-61
Table 3-10. PC Keyboard Remapping Definitions
PC Key (Keyboard Label)
Definition
Print Screen (PS)
Print
Scroll Lock (SL)
Scroll_Lock
Pause (PA)
Pause
Insert (IN)
Insert
Delete (DE)
Delete
End (EN)
End
22. Select the Save As button, enter custom.kmp in the File Name field, and select Save to
save the keyboard mapping file.
23. Select OK in the Keyboard Remapping window.
24. Select OK in the Reflection X Settings window.
25. Select Save As from the File menu in the menu bar of the Reflection X window.
26. Enter the hostname of the Advant workstation you are connecting to and click on the Save
button.
27. Select Run... from the Start menu in your Windows Operating System Task Bar.
28. Enter regedit in the Open field of the RUN window, and click on OK to start the
Registry Editor.
29. Expand the registry hierarchy by clicking on the ‘+’ boxes of:
HKEY_CURRENT_USER
Software
Reflection
Rx 6.2
config
until the Server folder appears. Select the Server folder by clicking on it.
30. Under the Edit menu, select New Binary Value from the New pull-down menu.
31. Type in FullScreen in the highlighted field next to the binary icon under the Name
column.
32. From the Edit menu, select Modify. The Edit Binary Value window appears.
33. Enter 01 in the Value data area, and click on the OK button.
34. Select Exit from the Registry menu to close the Registry Editor.
35. To start the session, click on the Connect button.
3-62
3BUR001 835R0001 REV C
3.6.18.5 X-Terminal Startup
Now that you are done configuring the Advant station for X-terminals, it should be rebooted by
entering the command:
/etc/shutdown -r 0
AdvaCommand X-terminal Startup
When the X-terminal boots, you are prompted for a login and a password. You should login as
operator and enter the password. Wait for the Auto Startup Sequence window to appear and
select any applicable options. For more information on the Auto Startup Sequence window,
refer to Section 2.4.1.1, AdvaCommand Auto Startup. Click on the OK button to start the
AdvaCommand session.
AdvaBuild X-terminal Startup
When the X-terminal boots, you are prompted for a login and a password. You should login as
ocsmgr and enter the password.
3.6.18.6 Headless Server Configuration
A headless server will not run AdvaCommand at the local monitor. To create a headless server,
do the following:
1.
log in as user root.
2.
Enter: cd /etc/rc.config.d
3.
Edit the file named advacommand and change the line:
OS_START=1
to
OS_START=0
3.6.18.7 Removing All X-Terminals
1.
From an HP Term window on the X-terminal, enter su - root and then press
<Return>.
2.
At the password prompt, enter the password and then press <Return>.
3.
Enter cd /etc and press <Return>.
4.
Rename the inittab.orig.#### file to inittab by entering:
mv inittab.orig.#### inittab
where #### is the four digit number created during the xtadm procedure. This step
simply restores the original inittab file.
3BUR001 835R0001 REV C
5.
Enter /usr/bin/X11/700X/admin/xtadm
6.
From the xtadm menu, select 2 and press <Return> to remove an X-terminal.
3-63
7.
Enter /opt/advant/MOD-OS/bin/osXConfig -remove
8.
Power down your X-terminal.
9.
Reboot your OS.
3.6.19 Optimizing User Graphic Performance
There is a configurable tuning parameter that the Operator Station uses for optimizing user
graphic call-up time. The parameter values refer to the length of a cache. This holds a copy of
the most recently invoked graphic’s data files in memory. When leaving a user graphic display,
this file’s data is copied into the cache, and the oldest display currently in the cache is removed.
Every site has a number of user graphics that are invoked repeatedly during the course of
normal operation. Ideally, the cache value should be set greater than or equal to this number,
ensuring the best results under normal operations. However, there is a trade-off when choosing
the cache value: size vs. speed. If the value is set too high, then all of RAM will fill and the
surplus will go into swap space, causing memory fragmentation and gradual performance
degradation (sometimes called an OS slow down). If the value is set too low, then un-cached
graphics could exist whose call-up times will be longer than necessary.
The best choice of cache value would be one that best matches the available RAM. The cache
value calculation is based on the amount of RAM and the size of the installed graphics. When
the OS boots, it checks the amount of RAM and performs an initial calculation. The OS then
evaluates the total size of the graphics that were installed during the previous OS session. This
size can cause the cache value to be adjusted down. However, the installed graphic base in the
current OS session may be very different than the previous OS session (as in an initial startup
when there was no previous session). In this case, the script that performs the cache value
calculation may be run manually (after graphics have been installed) to determine whether the
OS session should be restarted with a better cache value.
To run the cache tuning script, enter:
/opt/advant/MOD-OS/bin/Mbytes
If the text output from the script is:
Default is sufficient for previously installed graphics
then the cache value used at start-up time is optimum. If the text output from the script is:
Lowering cache size to: x graphics
where ‘x’ is the number of graphics, then the cache value used at start-up time is too large. A
new value has been calculated and will be used when the OS is restarted. You should restart the
OS in this case.
3-64
3BUR001 835R0001 REV C
Section 3.6.19 Optimizing User Graphic Performance
WARNINGS
•
Failure to perform this step and restart the OS when recommended may result
in performance degradation and possible failure of the OS. This should be
performed at first installation, whenever graphics are modified, and when new
graphics are installed.
•
The Mbytes script calculates the number of displays based on the average
graphic size. If you want to size cache value based on large graphics, you can
manually set it to a new value by copying the file OS.CacheValues to the
directory:
/var/opt/advant/MOD-OS/data/customer/config/
After the file is copied, edit the file to lower values using the same original
format of the file.
NOTE
If the number of different graphics that the site uses in a normal day exceeds the
default value (or the new value, if the default was modified), then that site may
want to increase RAM to run more effectively. When RAM is added, additional
device swap or file swap must be added to maintain the swap space at 2.5 times
the installed RAM. Device swap has better performance than file swap. Device
swap is automatically configured by reinstalling the software. File system swap is
added according to the instructions in Section 3.6.22, Adding File System Swap
Space.
3.6.19.1 Memory Resident Graphics
Another method of optimizing user graphic call-up time is the concept of Memory Resident
Graphics (MRG). The MRG software deals with two of the larger files, .fo and .m2, that
make up a user graphic. The MRG software enables you to specify which graphics the MRG
optimization will be applied to.
In order to use MRG, the following file must be created:
/var/opt/advant/MOD-OS/data/customer/config/OS.MemResGraphics.
This will be a simple text file. Each line of this file will contain a graphic name. If this file
exists, then any time a graphic is installed, a check will be done to see if the graphic is in the
file. If so, it will be marked MRG and the graphic’s .m2 and .fo files will be pulled in at install
time, speeding up the initial call-up and any subsequent call-ups when the graphic is not in
cache. (It should be noted that there is no expected performance difference if the graphic is
already in the normal cache.)
HOWEVER, the system memory usage must be considered. MRG is independent of the
OS.CacheValues cache. This implies that for each line in the MRG text file, the memory that
this graphic will take up must be accounted for. This is done in the MBytes script file. After
calculating “normal” cache values in Mbytes, the script subtracts 2 from each of the cache
values for each entry in the MRG text file. In other words, if Mbytes had previously calculated
cache values of 10 and 9, and an OS.memResGraphics file with 2 entries has been created,
then when the Mbytes script is re-run, it will create new cache values of 6 and 5, in order to
avoid the memory problems described in the previous section. Therefore, it is recommended
that MRG only be applied to a small number of time-critical graphics.
3BUR001 835R0001 REV C
3-65
3.6.20 Optimizing AdvaCommand Memory Usage
AdvaCommand is a large application requiring a lot of memory. AdvaCommand version 1.7/1
contains memory optimizations in many areas. The optimizations are meant to partially offset
increased memory usage in HP-UX version 10.20, and additional AdvaCommand features.
Display call-up and miscellaneous functions operate faster due to reduced memory usage. Your
system automatically has these optimizations after AdvaCommand 1.7/1 installation.
In addition, AdvaCommand allows you to tune memory usage by deleting unnecessary displays
or reducing memory buffers. Carefully read and follow these instructions to determine if your
system can benefit from these optimizations.
The file:
$OS_CONFIG/customerSystemVariables
allows you to remove sets of displays from the system. The default values are set to have all
displays are present. If you do not modify the file, your system operates the same as in
AdvaCommand versions 1.4 and 1.6/0.
NOTE
AdvaCommand allows up to four X-terminal clients with certain hardware
configurations. Changing this file effects all clients.
To optimize the AdvaCommand Display memory usage, edit the file:
according to the instructions that follow:
All Display Elements Option
There are approximately 100 display elements. In previous AdvaCommand versions, each
element was loaded into memory during the AdvaCommand start-up. However, most systems
use only a subset of display elements which wastes the memory used by the unused elements.
The variable UIS.SystemVariable.installAllDisplayElements has a default
value of TRUE. Changing it to FALSE forces the system to load elements when they are needed
on user graphics. After an element is loaded once, it remains in memory until AdvaCommand
restarts. Therefore, you save the memory that would have been used by any elements not
present on your graphics. The only drawback is the display takes slightly longer to display the
first time if it uses new elements. Testing indicates that this time difference is not perceptible. It
is highly recommended to change the option to FALSE.
TCL and Batch Displays Option
The variable UIS.SystemVariable.installTCLBATCHDisplays has a default value
of TRUE. If you do not use TCL/Batch options, or do not need those displays on a particular
Operator Station, change the option to FALSE and you will save approximately 1.4 MBytes of
system memory.
NOTE
Unit Graphic and Unit Message displays are always available. These options use
very little memory and most systems require them.
3-66
3BUR001 835R0001 REV C
Section 3.6.21 Optimizing OMF Shared RAM Usage
TLL Displays Option
The variable UIS.SystemVariable.installTLLDisplays has a default value of
TRUE. If you do not use the Ladder Logic options, or do not need those displays on a particular
Operator Station, change the option to FALSE and you will save approximately 700 KBytes of
system memory.
S100 Displays Option
The variable UIS.SystemVariable.installS100Displays has a default value of
TRUE. If you do not use S100 I/O, or do not need those displays on a particular Operator
Station, change the option to FALSE and save you will save approximately 100 KBytes of
system memory.
S800 Displays Option
The variable UIS.SystemVariable.installS800Displays has a default value of
TRUE. If you do not use S800 I/O, or do not need those displays on a particular Operator
Station, change the option to FALSE and save you will save approximately 1.5 MBytes of
system memory.
3.6.21 Optimizing OMF Shared RAM Usage
Object Management Facility (OMF) is the Advant station’s mechanism for retrieving virtually
all data. OMF uses HP-UX shared RAM. To improve performance, OMF allocates one large
section of RAM at system start-up and manages it separately from the operating system. The
station will stop operating if this allocated RAM is exceeded.
In AdvaCommand versions 1.4 and 1.6, the OMF shared RAM size is set at 10 MBytes. In
version 1.4, some systems exceeded the limit and the configuration was changed to increase the
amount. Other systems, mostly small and one-headed, used well below the 10 MByte limit. In
version 1.6, OMF optimized its memory usage so that less RAM is used.
You can reduce the amount of OMF Shared RAM by modifying a configuration file.
WARNING
Be very careful when changing this value because the system will crash if it is set
too low.
NOTE
Only Operator Stations not running History options and those not using
X-terminals should be considered for this change. The change is intended to
improve performance on small (80-96 MByte) systems where a reduction in OMF
RAM usage represents a significant reduction in total usage.
To determine the amount of RAM used, run the shared memory tool by entering the following
UNIX command:
/opt/advant/OMF/bin/omfShMemTool
3BUR001 835R0001 REV C
3-67
The shared memory tool shows the current OMF memory usage and will monitor usage as long
as it is active. It only shows information gathered while it is active, so you need to start the tool
and let it run during high usage periods to determine peak OMF usage. You will see peaks when
the following events occur simultaneously:
•
large displays are used
•
overlaps displays are used
•
dialogs are used
•
alarm conditions occur
You should always configure the amount of RAM to be 20% greater than the measured peak and
never lower than 6 MBytes.
To change the amount of OMF shared RAM:
1.
Multiply the number of megabytes desired by 1024 to get the number of kilobytes. The
default is 10240, and the minimum 6 Mbytes is 6144.
2.
Bring up the AdvaCommand Auto Startup window and enter the number of kilobytes into
the OMF Shared Memory field. Refer to Section 2.4.1.1, AdvaCommand Auto Startup for
more information.
The system must be re-started for changes to take effect.
3.6.22 Adding File System Swap Space
To add file system swap space to your system, enter the following commands in the system
administration manager (SAM) utility:
NOTE
File system swap is less efficient than device swap and should only be used
temporarily.
1.
From an HP terminal window, enter su and type in the password for the root user.
2.
Enter: sam
3.
Within the SAM utility, select the menu item Disks and File Systems and click on Open.
4.
Select Swap and click on Open.
5.
Select Add File System Swap … from the Actions menu.
6.
Select the disk or file system to hold the swap space. Select the file system that has enough
free space and has the least activity.
7.
Enter a value in the Minimum Swap field. This should be the value of the additional swap
space you are adding.
8.
Enter a value in the Maximum Swap field. (This can be the value of the additional swap
space you are adding, plus one. Pick a value that your disk will support.)
9.
Select Priority 1.
10. Select Enable: NOW.
3-68
3BUR001 835R0001 REV C
Section 3.6.23 Memory Pool Utility (mputil)
11. Select Enable: At Every System Boot.
12. Select OK.
13. Select OK in the informational popup dialog.
14. Select Exit from the File menu.
15. Select Exit Sam.
You have now added file system swap space to your system.
3.6.23 Memory Pool Utility (mputil)
CAUTION
The mputil utility is intended to be used by knowledgeable ABB personnel or
customers. The utility has no specific knowledge of how pools should be
configured to allow a functioning system. The utility makes it possible to change
memory pool allocations so that the RTAB/Advant node will not start. If you need
assistance, contact your field support representative.
The mputil utility, is used to display and change the allocation of memory to the MTOS
memory pools on the Run Time Accelerator Board (RTAB). Changes take effect the next time
the RTAB or workstation is restarted. It works by modifying the MTOS memory pools table
overlay files pu510_pools.x and pu511_pools.x. The file pu510_pools.x is used
for an EISA RTAB, and the file pu511_pools.x is used for a PCI RTAB. One of these files,
depending on which RTAB you have, is loaded into the RTAB during its start-up sequence. The
most common use of mputil is to enlarge the BACKMEM pool for large customer
applications. CCF, TCL and DBMS are examples of system applications that use BACKMEM.
The program is menu-driven. It is invoked from the shell command line in either an hpterm or X
terminal window, but displays best in an X terminal window. You must include the home
directory, $MODBASE_HOME/etc/Tools/ss, in the $PATH environment variable, or use
the absolute path of the program to run it. If you change the path variable, enter: mputil to run
it.
If the you want to change allocations, you must have write permission for the
pu510_pools.x and pu511_pools.x files in the $RTALOAD directory. Also, you must
know how much RAM is on the RTAB because the utility will prompt you for it. The System
Status page on the OS is one source of this information.
When you run mputil, you are presented with the following menu of options:
Memory Pool Allocation Utility Ver 1.2
C: RTA (PU51n) Memory Configuration
Q: Quit
Select one :
3BUR001 835R0001 REV C
3-69
Select C for default. Enter the amount of RTAB memory at the next prompt. The current/custom
memory configuration, and the original default configuration, are displayed. Below is a screen
shot of the main mputil display where memory allocation is done.
Node Type: ADVANT/Standard
X-file directory: /opt/advant/MODPU510/load/
Custom Pool: pu51n_pools.x
Default Pool: pu51n_pools.default
End of Memory: $7FFFFF
Pool Memory: 5159 Kb
Bit map start: $3a5300
Size: 34K
Pool #
Pool Name
Custom Pools
Default Pools
------------------------------------------------------------------------0
FASTMEM
16%
708 K
16%
708 K
1
LONGMEM
15%
664 K
15%
664 K
2
DPLMEM
45%
1991 K
45%
1991 K
3
BACKMEM
FIXED
700 K
FIXED
700 K
4
HISTMEM
0%
0 K
0%
0 K
5
CONSMEM
0%
0 K
0%
0 K
6
OMFMEM
24%
1062 K
24%
1062 K
------------------------------TOTAL
100%
5125 K
100%
5125 K
------------------------------------------------------------------------P : Enter POOL number and new percent
R : RESET custom pool sizes to default sizes
M : Change end of MEMORY address
S : SAVE custom pool sizes
Q : QUIT
Pools file is not affected until changes are saved.
Select one :
You can modify the custom configurations. The first time the utility is run, the default
configuration is saved to the file:
pu51n_pools.default
where n=0 for an EISA RTAB, and n=1 for a PCI RTAB.
Changes to the custom file will not be made until you save them. Therefore, you are allowed to
experiment until the right configuration is achieved.
To save the custom pool values, select S. You will be given the opportunity to save the old pools
overlay file to any filename. You must have write permission in the $RTALOAD directory. The
new changes are saved back to the pu51n_pools.x file, which is the file loaded onto the
RTAB.
CAUTION
There are other files in the $RTALOAD directory. Do not use any files that you
have not created.
To change the amount of memory to configure on the RTAB, select M, then select either 1 or 2
for 8 or 16 Mbytes.
NOTE
EISA RTABs can have either 8 or 16 Mbytes of memory. PCI RTABS have 16
Mbytes of memory.
3-70
3BUR001 835R0001 REV C
Section 3.6.24 Changing Tag Highlight Colors and Group Trend Attributes
3.6.24 Changing Tag Highlight Colors and Group Trend Attributes
The “loop under control”, “tag focus highlighting” and Group Trend attributes are all
configurable by editing a text file.
“Tag focus highlighting” occurs when your cursor is focused over a control element on
AdvaCommand runtime displays. When you are focused over a tag, corner brackets highlight
the element. “Loop under control highlighting” occurs when you select a display element to take
control on AdvaCommand runtime displays. When you select the element, a set of corner
brackets highlight the element. For more information on these highlighting features, refer to the
AdvaCommand Basic Functions User’s Guide.
The Group Trend trace width, background color, grid color, and the 4 trend trace colors, are all
configurable in the same text file.
To change the tag highlight colors and Group Trend attributes, you must edit the text file:
You can use any text editor to change the values of the variables.
The Group Trend trace width variable, Uis.SystemVariable.gptTraceWidth, has a
default value or 1. For the best appearance, values ranging from1 to 5 are suggested.
The Group Trend background, grid color and 4 trace color variables are:
Uis.SystemVariable.gptBackgroundColor
Uis.SystemVariable.gptGridColor
Uis.SystemVariable.gptTraceColor0
The tag highlight color variables, Uis.SystemVariable.underControlColor and
Uis.SystemVariable.highlightColor, can be set to “OFF” (default).
NOTE
The variable Uis.SystemVariable.useSingleColumnStatusBlocks should not
be changed from the default value of FALSE.
3BUR001 835R0001 REV C
3-71
The color codes used by the color variables in this file are the same as those used by the
AdvaBuild Display Builder and the Environment Builder. To see the color codes in the Display
Builder, click on Colors from the Tools menu for any display. To display the Color Palette,
Figure 3-14, in the Environment Builder, go to the Operator Station Setup Display from the
Environment Top Level Display and click on any Alarm Type.
Figure 3-14. Environment Builder Color Palette
3-72
3BUR001 835R0001 REV C
Section 3.6.25 Alarm Options
3.6.25 Alarm Options
Alarm options allow you to add dates to alarm and TCL message formats, and add milliseconds
to alarm time formats. You can also turn alarms off for PSAPs and overview displays.
You can change the alarm options by changing variables in the text file:
You can use any text editor to change the values of the variables.
Changes will not take effect until you re-install the environment.
All of the options are listed below:
Show Alarm Milliseconds
Changing the variable Uis.SystemVariable.ShowAlarmMilliSeconds to TRUE
forces the Fetch Alarm window and Alarm Message display to show the three digit millisecond
count of the alarm generation time.
Show the Message Date
Changing the variable Uis.SystemVariable.ShowMessageDate to TRUE forces the
Fetch Alarm window, Alarm Message display, and TCL Unit Message display to show the date
before the message time. The date shows the day of month and the three letter month
abbreviation. The year is not displayed.
Show Alarm Acknowledge Date
Changing the variable Uis.SystemVariable.ShowAlarmAckDate to TRUE forces the
Alarm Message display to show the date of alarm acknowledgment immediately before the
time. The date shows the day of month and the three letter month abbreviation. The year is not
displayed.
Show Alarms on PSAPs and Overviews
Changing the variable Uis.SystemVariable.showAlarmOnOverviewPSAP to
FALSE (default is TRUE) forces PSAPS and Overview displays to stop displaying alarms.
3.6.26 Configuring Mouse Button 2 for Alarm Acknowledgement
On a 3-button mouse, mouse button 2 (the middle mouse button) can be configured to perform
the acknowledge function. To do this, the variable, Uis.SystemVariable.Button2Ack,
in the $OS_CONFIG/customerSystemVariables file must be modified. The default
value is “OFF”. With a text editor, set Uis.SystemVariable.Button2Ack to “ON” to
enable mouse button 2 to perform the acknowledge function.
3BUR001 835R0001 REV C
3-73
3.6.27 Advant Authority and Security Enhancements (ASE)
Overview
Configuration and maintenance of users is easier using the ASE features. Typically, plant
operations have many users with identical tag authority levels. In order to trace operator
changes, a separate environment user is maintained, but that proves to be time consuming in
large and dynamic facilities. The ASE features allow user names and passwords to be
maintained separately from the environment and “linked” to a set of environment authorities.
When users are added/deleted, no environment changes are necessary. When tag names change,
only a small number of environment users, relative to the number of operators, need
modification.
There are several advanced authority and security features in the AdvaCommand software
including:
•
Password encryption
•
User authority groups
•
Password aging
•
Enable/disable user accounts
•
Users must enter an ID in addition to password
•
Users maintain their own passwords
•
Secure User Configuration Tool
•
Extended log files for user activities
•
Automatic logoff configuration
•
Read-only AdvaCommand station configuration
•
LoopFCM is accessible to all users, but is read-only if they do not have write authority for
the tag.
•
TCL can verify the current user ID through billboard statements. The user ID may also be
sent to PDL to improve batch records.
•
AdvaCommand stations can be configured as “read only” to prevent changes to tags or
TCL from all users. An application for this feature is resident or modem-connected PCs
monitoring plant operating conditions.
How to Configure ASE Users and Groups
Users defined in the environment are used as ASE user authority groups instead of individual
users. ASE users are added to the authority user groups with the ASE User Configuration Tool,
see Section 3.6.27.1, ASE User Configuration Tool.
When ASE users log into the environment, they inherit all access and authority from their
authority group as defined in the Environment Builder.
3-74
3BUR001 835R0001 REV C
Section 3.6.27 Advant Authority and Security Enhancements (ASE)
Environment Builder Requirements
You can configure user authority groups for environments that contain many users with the
same authority. ASE user groups are configured in the Environment Builder just as users are
configured in the Environment Builder. The difference is that the ASE User Configurator Tool
is used to add ASE users to environment user authority groups.
The environment defined users will not login at runtime, because they are the environment
authority groups.
3.6.27.1 ASE User Configuration Tool
The ASE User Configuration Tool is used to add ASE users to the ASE user authority groups
previously defined in the Environment Builder.
Starting the ASE User Configuration Tool
To start the User Configuration Tool, you must be logged on as the user operator, and enter:
$OS_HOME/bin/startosUserTool. You are required to enter the root password before
the User Configuration Tool opens, Figure 3-15. You can also make the User Configuration
Tool an external application in the environment, making it readily available from the
AdvaCommand Display Menu.
3BUR001 835R0001 REV C
3-75
Figure 3-15. ASE User Configuration Tool Start Screen
Creating a New User File
The host machine must have the full version of Oracle installed to create new ASE User files. If
not, when you try to create a new user file, an error message is displayed. If you wish to install
the full version of Oracle on a station that doesn’t already have it, you must reinstall the station
according the instructions in Chapter 1, Introduction and Chapter 2, Installation of this book.
To create a new ASE user file, select File > New from the menu bar. A list of environments is
displayed, Figure 3-16.
3-76
3BUR001 835R0001 REV C
Figure 3-16. Environment List
Select the environment for which you wish to create the new user file, and select OK. The User
Configuration Tool work area is then displayed, Figure 3-17.
Figure 3-17. User Configuration Tool Work Area
3BUR001 835R0001 REV C
3-77
If a user file already exists for the environment, and you try to create a new one, you are asked if
you want to overwrite the file, or to cancel. If you select Cancel, the list closes.
Adding New Users
To add new users, click on Add. The User Configuration Tool then enters add mode,
Figure 3-18.
Figure 3-18. User Configuration Tool Work Area (Add Mode)
Fill out all the information, and click on OK to complete adding the user.
A description of all the items on the work area is given below:
Users
Alphabetical scroll list of users configured for the environment.
Information about a user appears in the work area and is
accessible for editing when the user’s name is selected from the
list..
User Name
The User Name must be between 1 and 12 characters, and be
composed of letters, numbers, the underscore ‘_’ character, and
the
hyphen ‘-’ character. Duplicate names are not allowed.
Once configured, user names cannot be changed without first
deleting the user and creating a new one.
Disable
3-78
This button only appears when an existing user account is being
edited. To disable the user account, click on the Disable button.
3BUR001 835R0001 REV C
User Group
A pull-down list of previously configured user authority groups
from the selected environment.
If for some reason this application cannot connect to Oracle, the
pull-down list turns into a text input field where you can add a
user authority group.
The User Group must be between 1 and 15 characters, and be
the hyphen ‘-’ character.
Pass Expires Every
Number of days from 1 to 999 until the password expires. New
users are requested to change their password the first time they try
to log on. The password will expire at the rate of the configured
interval.
If Never is selected, the password will not expire.
Initial Password
The Password must be between 9 and 16 characters, and be
the
hyphen ‘-’ character. The password must also contain at least one
alphabetic character and one non-alphabetic character.
Verify Password
Type in the same password as above for confirmation.
Add
Selecting the Add button clears the work area of any previous
information to prepare for the addition of a new user. All fields
must be completed before a new user can be added.
OK
Pressing OK submits the user information for processing and the
user is added if no errors are detected. If errors are found, you are
prompted to correct them.
Delete
Deletes the user displayed in the work area from the user file. To
display a user in the work area, select the name from the User
List.
Change Password
Changes a user’s previously configured password. A change
password window appears allowing you to change the password.
Editing a User
To edit an existing user, select the name from the User List. The User Configuration Tool enters
edit mode, Figure 3-19.
3BUR001 835R0001 REV C
3-79
Figure 3-19. User Configuration Tool Work Area (Edit Mode)
To change the user’s password, click on Change Password.
You can disable a user by clicking on the Disable button next to the User Name field.
After editing the user information, select OK to complete your changes.
Deleting a User
To delete a user, select the name from the User List and click on the Delete button.
Saving the User File
To save additions to the user file, you must select File > Save from the menu bar. If you try to
close the user file, or quit the User Configuration Tool with unsaved changes, you will be given
the option to save them before exiting.
NOTE
Saved changes are not written to the user file until the user file is closed or the
tool is exited.
Closing the User File
To close the user file, select File > Close from the menu bar. If you have unsaved changes, you
will be given the option to save them before closing. When the work area disappears, the User
Configuration Tool Start Screen appears.
3-80
3BUR001 835R0001 REV C
Quitting the User Configuration Tool
You can quit from either the work area, or the start screen, of the User Configuration Tool by
selecting File > Quit from the menu bar.
Opening Existing User Files
To open an existing ASE user file, select File > Open from the menu bar. A list of users files is
displayed, Figure 3-20. If you select Cancel, the list closes.
Figure 3-20. List of User Files
Deleting User Files
To delete a user file, select File > Delete from the menu bar of the User Configuration Tool. A
Delete Files dialog appears with a list of all the user files on the host station. Select the user file
you wish to delete, and select OK. This deletes the file and closes the window. To exit the
window without deleting a file, select Cancel to close the window without deleting any files.
ASE User Tool Online Help
Online help is available for the ASE User Configuration Tool, and provides a tutorial for using
the application. To access online help, select Help > Open from the menu bar, Figure 3-21. To
close the help window, select the Close button on either the help menu, or the help dialog.
3BUR001 835R0001 REV C
3-81
Figure 3-21. User Configuration Tool Online Help
3.6.27.2 ASE Configuration Options
Additional ASE parameters can be configured as needed. They are:
•
maximum number of unsuccessful logins required to generate a diagnostic message
•
communications maximum number of retries
•
minimum wait period for ASE password changes
These variables are all defined in the $CUSTOMERDIR/customerSystemVariables file.
Maximum Number of Unsuccessful Logins
To configure the maximum number of unsuccessful logins required to generate a diagnostic
message, modify the variable:
Uis.SystemVariable.unsuccessfulLoginThreshold
This parameter enables the system to check how many times a user unsuccessfully attempts to
logon. If the maximum is reached, a diagnostic warning message is generated containing the
user’s name, timestamp, and the number of consecutive failed attempts. The range for this
variable is 3 to 10. The default is 3.
3-82
3BUR001 835R0001 REV C
Communications Maximum Number of Retries
To configure the communication maximum number of retries, modify the variable:
Uis.SystemVariable.communicationRetryMax
The default value is 12, which is equal to approximately 6 seconds. This variable controls the
number of times (about 1/2 second each) the ASE login request tries to start the change
password dialog. If the maximum number of retries is reached, a dialog message appears telling
the user the OS password dialog can not be started and to login with your old password. The
range of values is 12 to 10,000. The default value of 12 should work for most sites; it can be
adjusted up for sites with high TCP/IP traffic.
Minimum Wait Period for ASE Password Changes
To configure the minimum wait period for ASE password changes, modify the variable:
Uis.SystemVariable.passChangeMinimumWait
If this variable is set to 0, which is the default, users don’t have to wait any period between
password changes. If the value is greater than 0, the user must wait the defined number of
minutes between password changes. The minimum value is 20 minutes.
3.6.27.3 TCL Runtime User Identification
You can configure your TCL programs to prompt the user at runtime for their username and
password. This allows the TCL program to determine the authority level of the user. When
enabled, a configurable prompt (Figure 3-22) requests the user’s username and password to
verify their identity.
Figure 3-22. TCL User Verification Window
Enabling TCL Runtime User Identification
To configure this TCL runtime user identification, the variable:
Uis.SystemVariable.TCLIdentificationMessage
in the $CUSTOMERDIR/customerSystemVariables file must be set to a text string to
display as the runtime prompt for user verification.
NOTE
The maximum number of characters in the string is 39.
3BUR001 835R0001 REV C
3-83
The station must be rebooted for this change to take effect.
A TCL unit message must have the reply type set to integer or string, and contain text that
matches the variable in the customerSystemVariables file. If the text in both match, a
runtime message dialog appears with the matching text, prompting the user to logon with their
username and password.
If the reply type is set to integer, and the username and password match that of the currently
logged on user, an integer value between 1 an 4 representing the user’s authority level is
returned to the TCL program as shown below:
1 = OPERATOR
2 = SUPERVISOR
3 = ENGINEER
4 = ENVIRONMENT
If the reply type is set to integer, and the username and password do not match that of the
currently logged on user, a value of 0 is returned to the TCL sequence.
If the reply type is set to string, and the username and password match that of the currently
logged on user, a string is returned containing the authority level and username. For example:
3John
which is the user John with the engineer (3) authority level. If the username and password do
not match that of the currently logged on user, a string is returned containing 0.
Disabling TCL Runtime User Identification
To disable this feature, you only need to change the variable:
Uis.SystemVariable.TCLIdentificationMessage
in the $CUSTOMERDIR/customerSystemVariables file so it no longer matches the text
in the TCL unit message. When the text does not match, the normal unit message appears at
runtime. The station must be rebooted for this change to take effect.
3.6.27.4 Automatic User Logoff
The AdvaCommand software can automatically logoff all users after a configurable time of
inactivity. Activity is defined as moving the mouse or hitting a key on the keyboard. A message
is displayed at runtime when automatic logoff occurs. The time range is 20 minutes to 24 hours.
Enabling Automatic User Logoff
To enable automatic user logoff, you must set the variable:
Uis.SystemVariable.autoLogoffPeriod
in the $CUSTOMERDIR/customerSystemVariables file to a value between 20 minutes
and 1440 minutes (24 hours). This defines the number of minutes of inactivity before the system
logs off all users. If the variable is set to a value greater than 0, automatic user logoff is enabled.
If you enter a value between 0 and 20 minutes, a warning message is displayed, and the
3-84
3BUR001 835R0001 REV C
minimum time of 20 minutes is used. If the variable is set to a value higher than 1440 minutes, a
warning message is displayed, and the maximum value of 1440 minutes is used. The station
must be rebooted for this change to take effect.
Disabling Automatic User Logoff
To disable automatic user logoff, you must set the variable:
Uis.SystemVariable.autoLogoffPeriod
in the $CUSTOMERDIR/customerSystemVariables file to 0. The station must be
rebooted for this change to take effect.
3.6.27.5 Read-Only AdvaCommand Station
Individual Advant Stations with AdvaCommand software can be configured to be read-only.
Once enabled, users can only view, not change, process information on the station regardless of
their user authority.
Enabling Read-Only Access on an AdvaCommand Station
To enable read-only access, you must add the IP address of the read-only station(s) to the
variable:
Uis.SystemVariable.readOnlyNodes
in the $CUSTOMERDIR/customerSystemVariables file. You can have up to four
stations defined (host and 3 X-terminals) as read-only. The IP address(es) must be bound by
double quotes. Multiple addresses must be separated by a space. As an example:
Uis.SystemVariable.readOnlyNodes “129.12.1.14 129.12.1.15”
The station must be rebooted for this change to take effect.
When an AdvaCommand station starts, it checks this list to see if its IP address is defined. If the
station’s IP address matches one in the list, read-only access is enabled for the station.
Disabling Read-Only Access on an AdvaCommand Station
To disable read-only access, you must remove the IP address of the station(s), from the variable:
Uis.SystemVariable.readOnlyNodes
in the $CUSTOMERDIR/customerSystemVariables file. The station must be rebooted
for this change to take effect.
3.6.27.6 ASE Log Files
ASE creates history log files containing text information about logons, logoffs, and password
changes. You must be logged on as root to view these files and the directories in which they
are stored.
3BUR001 835R0001 REV C
3-85
There are two types of history log files produced:
logon/logoff history file name:
<environment name>-history.<hostname>
password history file name:
<environment name>-password-history.<hostname>
where <environment name> is the name of the environment the log file is generated for and
<hostname> is the name of the host the environment is running on. The format of these files is:
logon/logoff history file format:
<timestamp> <user> <action>
password history file format:
<timestamp> <user> <password change result>
The logon/logoff history file contains information about logons, logoffs, unsuccessful attempts,
and unknown user attempts.
The password history file contains information about successful and unsuccessful password
changes.
These files can hold a maximum of 2000 entries on a first-in-first-out basis.
The log files are located on both the local node (node the environment is running on) and the
remote node (node the environment was downloaded from). On both the local and remote
nodes, the log files are located in the directory $OSLOGDIR/ase. In this directory, there are
two subdirectories: local and remote.
If your environment was installed from the local node, you will have a logon/logoff and a
password log file located in the local directory. If your environment was installed from a
remote node, the logon/logoff log file is located in the local node’s remote directory and the
password log file is located in the remote node’s remote directory.
3.6.28 Central Graphics and Environment Administration
Overview
The AdvaCommand Central Administration feature allows you to set up a server/client scheme
for environments and graphics. Environments and graphics are maintained on a central server
station, thus freeing resources on the client stations. The client stations install environments and
graphics directly from the server without having to store them locally. This scheme eliminates
the need to distribute changed environments and graphics to each destination station prior to
installing them.
Client stations use less disk and memory resources because the Environment Builder, Display
Builder, Display Converter, and Oracle Server are not required. If you want a station to be a
client only, and the Oracle server is already installed, you can either leave it on, or reload your
station without it to optimize performance.
3-86
3BUR001 835R0001 REV C
Section 3.6.28 Central Graphics and Environment Administration
3.6.28.1 Server Configuration
The server requirements for environments and graphics differ slightly. In both cases, the Advant
Station designated as the server must either be accessible on the TCP/IP network, or be the local
station. Additional requirements for environments and graphics servers are described below.
Environment Servers
In order for an AdvaCommand station to be an environment server, it needs to have the Oracle
server software installed when the station is loaded. If the station does not already have the
Oracle server software installed, and you want it to be a server, you will have to reload your
station software according to the instructions in Chapter 1, Introduction and Chapter 2,
Installation of this book.
Stations can be servers and client, meaning they will serve environments to themselves, as well
as to other clients.
Graphic Servers
Any AdvaCommand station can be configured as a graphics server; however, this increases the
disk requirements of the station. The disk requirements depend on the number and size of the
graphics.
Graphics server stations must be designated as such by executing the
osCreateGraphicsServerNode function.
NOTE
The local station is always considered a valid graphics server; therefore, you are
NOT required to run the osCreateGraphicsServerNode function on it.
To configure an Advant Station as a graphics server:
1.
Log in as the ocsmgr user.
2.
Enter: $OS_HOME/bin/osCreateGraphicsServerNode.
3.6.28.2 Client Configuration
The client connects to an Oracle server when the AdvaCommand software is started on the
client. Which server the client installs its environment and/or graphics from is specified by
defining two system variables in the $CUSTOMERDIR/customerSystemVariables file.
The variables are:
Uis.SystemVariable.envPrimaryServerNode
Uis.SystemVariable.envBackupServerNode
The default value for both variables is LOCAL. This means the client will install from its own
local Oracle server and graphics server.
3BUR001 835R0001 REV C
3-87
You can modify these variables to specify a primary server node and back-up server node. To do
this, replace LOCAL with either the TCP/IP address of the server node, or the corresponding
alias as defined in the /etc/hosts file. For example:
Uis.SystemVariable.envPrimaryServerNode: "100.100.100.10"
Uis.SystemVariable.envBackupServerNode: "OS-ES2"
When the AdvaCommand software starts on the client, the client node is connected to the
primary server node. If the primary server is not available, the client is connected to the backup
server. If the backup server is also unavailable, the client is connected to its own local Oracle
server, if it is installed and running.
Graphics associated with environments (group, area and unit), are installed with the
environment if the Oracle server node is also a valid graphics server node (see Section 3.6.28.1,
Server Configuration).
The Uis.SystemVariable.envPrimaryServerNode and
Uis.SystemVariable.envBackupServerNode variables are read when the host
AdvaCommand software is started. If you modify these variables, you must re-start the host
AdvaCommand software using the quit command, not the stopsession command, to
make the changes take affect.
3.6.28.3 Environment Server Selection Menu
You can configure the system to display a server menu on the Login Page for environment
installation. This menu lets the operator override the configured servers (as described in Section
3.6.28.2, Client Configuration) from the Login Page.
To display a server menu on the Login Page, set the value of the
Uis.SystemVariable.envServerMenu variable in the
$CUSTOMERDIR/customerSystemVariables file to TRUE or FALSE. The default
setting for this variable is FALSE. In this case, the menu is not displayed, and operators cannot
manually override the server selection.
If the variable is set to TRUE, a pull down menu is associated with the “From” field on the
Login Page, Figure 3-23.
Figure 3-23. Pop-up Server Menu on Login Page
3-88
3BUR001 835R0001 REV C
Section 3.6.28 Central Graphics and Environment Administration
The Uis.SystemVariable.envServerMenu variable is read when the environment is
downloaded. If the value is changed, the change takes effect following the next environment
download.
The default menu choices are the alias names for the primary server, backup server, and local
server. Additional servers may be added by modifying the $HOST_FILE
($CUSTOMERDIR/CAhosts) file. This file is formatted in the same way as the
/etc/hosts file, except that it can be modified by the operator user.
Users must have environment install authority to change the server on the pull down menu.
When a new server is selected from the menu, it is validated. If the node is invalid, an error
message is displayed and the menu reverts to the previous server.
If a default environment is defined in the
Uis.SystemVariable.defaultEnvironment, that environment is downloaded from
the server to which the client is initially connected.
3.6.28.4 Graphics Server Selection Menu
You can configure the system to display a server menu on the Installer display for graphics
installation. This menu allows the operator to override the configured servers (as described in
Section 3.6.28.2, Client Configuration), from the Installer display.
To display a server menu on the Installer display, set the value of the
Uis.SystemVariable.graphicsServerMenu variable in the
$CUSTOMERDIR/customerSystemVariables file to TRUE or FALSE. The default
setting for this variable is FALSE. In this case, the menu is not available, and operators cannot
manually override the server selection.
If the variable is set to TRUE, a pull down menu is associated with the “Available On” field on
the Installer display, Figure 3-24.
Figure 3-24. Pop-up Server Menu on Installer Display
The Uis.SystemVariable.graphicsServerMenu variable is read when the
environment is downloaded. If the value is changed, the change takes effect following the next
environment download.
The default menu choices are the alias names for the primary server, backup server, and local
server. Additional servers may be added by modifying the $HOST_FILE
($CUSTOMERDIR/CAhosts file. This file is formatted in the same way as the
/etc/hosts file, except that it can be modified by the operator user.
3BUR001 835R0001 REV C
3-89
All the graphics servers listed (primary, backup, and CAhosts file entries) are validated when
the Installer is started. Only validated stations are available for selection from the menu.
3.6.29 AdvaBuild On-line Documentation Configuration
The on-line documentation option is available in the AdvaBuild Structure Builder from the
Help menu. However, the system must be configured to access the On-line documentation CD
via a CD-ROM drive installed on the system.
3.6.29.1 Mounting the On-line Documentation CD
To install a CD-ROM drive on the system, the following steps must be taken:
1.
As root user, create a mount directory to mount the CD drive to by entering:
mkdir /cdrom
2.
Execute the mount command to allow the CD-ROM drive to be accessible by the system
by entering:
mount -e -F cdfs -o cdcase,ro,nosuid /dev/dsk/c0t2d0 /cdrom
NOTE
The file /dev/dsk/c0t2d0 is the device associated with the CD drive. This
could also be /dev/dsk/c1t2d0. If you are unsure, execute the command:
ll /dev/dsk and match the correct device file
3.
Create a softlink so the Structure Builder knows where to find the CD drive. Enter:
ln -s /cdrom /opt/advant/AcroRead/doc
3.6.29.2 Auto-Mount the On-line Documentation CD
If the system will have the CD drive available most of the time for the on-line documentation
CD, it is suggested to add a line to the /etc/fstab file to automatically mount the CD drive
when you restart your station. To auto-mount the CD, follow the instructions below:
1.
As root user, create a backup of the /etc/fstab file.
2.
Add the following line to the bottom of the /etc/fstab file:
/dev/dsk/c0t2d0 /cdrom cdfs cdcase,ro,nosuid 0 1
NOTE
The /dev/dsk/c0t2d0 parameter may be different as described in the note in
Section 3.6.29.1, Mounting the On-line Documentation CD.
3-90
3BUR001 835R0001 REV C
Section 3.6.29 AdvaBuild On-line Documentation Configuration
3.6.29.3 Copying the On-line Documentation CD to the Hard Disk
If the system will not have the CD drive available for the on-line documentation most of the
time, you may consider copying the information to disk. This requires approximately 300
MBytes of available disk space. To copy the CD to disk:
1.
Create a directory to store the contents of the CD. As an example you can create a
directory called “doc” off of the root directory by entering the command:
mkdir /doc
2.
Copy the contents of the CD to that directory (indicated below by /doc) by entering:
cp -R /cdrom /doc
This command also copies the subdirectories from the CD.
3.
Create the soft link for the Structure Builder (you need to be root user):
ln -s /doc/cdrom /opt/advant/AcroRead/doc
3.6.29.4 Accessing the On-line Documentation CD on Other Systems via NFS
The on-line documentation can be served to other stations (clients) by setting your station up as
an NFS server. This is true whether the on-line documentation is being access from the CD
drive, or if you have copied the files to the hard disk. For information on setting up NFS servers
and clients, refer to the administration manuals for your operating system.
Below is an example of setting up the NFS client on an Advant Station:
1.
On the client station, a directory must be created to mount to by entering:
mkdir /cdrom
2.
The following command should be added to the /etc/fstab file, and the client station
rebooted for the change to take place:
“IP NETWORK ADDRESS”:/cdrom /cdrom nfs ro,bg 0 0
where “IP NETWORK ADDRESS” is the IP address of the NFS server.
NOTE
The steps above can be changed to access the documentation from a server where
the online documentation has been installed on the disk. Instead of accessing the
/cdrom directory, change the access to the full path of the directory where the
on-line documentation was copied.
3.
Create the necessary soft link on the client station to allow the Structure Builder to access
the documentation:
ln -s /cdrom /opt/advant/AcroRead/doc
3BUR001 835R0001 REV C
3-91
3-92
3BUR001 835R0001 REV C
Section 4.1 Operating Overview
Chapter 4 Runtime Operation
4.1 Operating Overview
For information on how to use the Operator Station during runtime, refer to Section 1.5, Related
Documentation.
4.2 Operating Instructions
4.2.1 Keyboard Mappings
The keys on the HP workstation and X-terminal keyboards have been mapped to emulate the
functionality of the ABB keyboard. Listed in Table 4-1, are the keyboard mappings for the
different keyboards on the Operator Station.
Table 4-1. Operator Station Keyboard Mappings
ABB Keyboard
HP HIL Keyboard
HP PS/2 Keyboard
PC Keyboard
F1 -- F10 and Shft-F1 -- Shft-F10 are the same on all Keyboards
Help
DownArrow
DownArrow
DownArrow
DownArrow
LeftArrow
LeftArrow
LeftArrow
LeftArrow
RightArrow
RightArrow
RightArrow
RightArrow
Find
(1)
NP. *
NP. *
Nextchoice
NP. -
NP. -
NP. -
Nextfield
NP. /
NP. /
NP. /
UN-DEL
ClearLine
Pause/Break
Pause/Break
INS LINE
Clear
Insert
Insert
DEL LINE
Shft-Clear
Shft-Insert
Shft-Insert
DEL CHAR
Insert Line
NP. Del
NP. Del
EOL DEL
Shft-Insert Line
Shft-NP. Del
Shft-NP. Del
WORD ADV
Delete line
Delete
Delete
Enter
NP. +
Select
3BUR001 835R0001 REV C
4-1
Table 4-1. Operator Station Keyboard Mappings (Continued)
ABB Keyboard
HP HIL Keyboard
HP PS/2 Keyboard
PC Keyboard
DEL WORD
Shft-Delete Line
Shft-Delete
Shft-Delete
BOT
Insert Char
Home
Home
TOP
Shft-Insert Char
Shft-Home
Shft-HOME
EOL
Delete Char
End
End
BOL
Shft-Delete Char
Shft-End
Shft-End
PAGE UP(Prev)
Page Up (Prev)
Page Up
Page Up
LEFT UP
Shft-Page Up (Prev)
Shft-Page Up
Shft-Page Up
PAGE DOWN(Next)
Page Down (Next)
Page Down
Page Down
RIGHT DOWN
Shft-Page Down
(Next)
Shft-Page Down
Shft- Page Down
Ovw1
Ctrl-F1
Ctrl-F1
Ctrl-F1
Ovw1Lap
Shft-Ctrl-F1
Shft-Ctrl-F1
Shft-Ctrl-F1
Ovw2
Ctrl-F2
Ctrl-F2
Ctrl-F2
Ovw2Lap
Shft-Ctrl-F2
Shft-Ctrl-F2
Shft-Ctrl-F2
Ovw3
Ctrl-F3
Ctrl-F3
Ctrl-F3
Ovw3Lap
Shft-Ctrl-F3
Shft-Ctrl-F3
Shft-Ctrl-F3
Ovw4
Ctrl-F4
Ctrl-F4
Ctrl-F4
Ovw4Lap
Shft-Ctrl-F4
Shft-Ctrl-F4
Shft-Ctrl-F4
SystemStatus
Ctrl-ClearDsply
ScrollLock
ScrollLock
SystemStatusLap
Shft-Ctrl-ClearDsply
Shft-ScrollLock
Shft-ScrollLock
Display Request
Ctrl-D
Ctrl-D
Ctrl-D
RampDown
F11
F11
F11
RampDownFast
Shft-F11
Shft-F11
Shft-F11
RampBottom
Ctrl-Shft-F11
Ctrl-Shft-F11
Ctrl-L-F11
RampUp
F12
F12
F12
RampUpFast
Shft-F12
Shft-F12
Shft-F12
RampTop
Ctrl-Shft-F12
Ctrl-Shft-F12
Ctrl-L-F12
RampStop
F11
F11
F11
Enter
4-2
3BUR001 835R0001 REV C
Section 4.2.2 Using Xtouch
Table 4-1. Operator Station Keyboard Mappings (Continued)
ABB Keyboard
RampStop
HP HIL Keyboard
HP PS/2 Keyboard
PC Keyboard
F12
F12
F12
Print
Print Screen
Print Screen
Ack
NP.Tab
Enter
Enter
Silence
Ctrl-NP.Tab
Ctrl-NP.Enter
Ctrl-NP.Enter
StatetreeUp
Ctrl-C
Ctrl-C
Ctrl-C
ScreenCopy
*
(1) NP. is used to represent the Number Pad.
4.2.2 Using Xtouch
This section provides instructions for using the Xtouch software, which supports the Operator
Station touchscreen. To start Xtouch, select Xtouch from the External Applications submenu of
the Display Menu. A terminal window is displayed with the Xtouch main menu options. (To add
Xtouch to the Display Menu, refer to Section 3.6.17, Configuring External Display Access for
Xtouch.)
4.2.2.1 Default Xtouch Options
To change the current device or display for which Xtouch is configured, select D from the
Xtouch main menu. This calls up the Default Options menu.
Specifying the Device Port
The change device option (C) is used to specify the device name of the touchscreen serial port.
NOTE
/dev/tty0p0 is serial port 1, and /dev/tty1p0 is serial port 2 on most
stations. Replace this with the appropriate serial port.
Specifying the X Display
The modify display option (D) is used to select the X Windows System display to receive the
touch events. By default, Xtouch sends touch events to the X display on the computer on which
the software is running. For example, setting the display option to hamlet:0 will cause Xtouch to
run on the X display named hamlet:0.
4.2.2.2 Calibrating Xtouch
Before starting Xtouch, you must calibrate your touchscreen so that the Xtouch software can
translate the touchscreen data into appropriate pointer actions. A utility program is provided to
calibrate your touchscreen system. The calibration program is used to specify the
correspondence between the image displayed on your monitor and the touchscreen coordinate
system so that the touch data can be accurately translated into pixel locations.
3BUR001 835R0001 REV C
4-3
NOTE
The calibration session must be run at least once on every port for which you
intend to use a touchscreen. A separate calibration data file will be made for each
port.
To configure Xtouch, do the following:
1.
Select C from the Xtouch main menu. This starts the calibration process, assuming a
default installation of the scsiTerminal Server software. To change the default device, refer
to Section 4.2.2.1, Default Xtouch Options. Select y if the device is correct.
2.
Now, adjust your monitor settings as if you were about to begin a work session. Position
yourself in front of the monitor in your usual working posture and position. For best
calibration results, when prompted to touch the screen you should use the same finger and
hand position at all times.
If you experience problems while running the calibration session, refer to Section 5.1.2.1,
Calibration Diagnostic Messages.
3.
This step is used to calibrate the Carroll Touch touchscreen only. If you have a SONY
touchscreen, go to step 4.
The program will prompt you to touch the bottom-left corner of the screen image.
Carefully touch your finger to the touchscreen at the lower-left corner of the image, press
firmly, and then lift your finger from the touchscreen. Do NOT touch the physical corner
of the screen; instead, touch the location on the CRT which is displaying the lower-left
corner of your screen picture.
Proceed to step 5.
4.
This step is used to calibrate the SONY touchscreen only. If you have a Carroll Touch
touchscreen, go to step 5.
The SONY Touch Screen Setup display, Figure 4-1 below, is used for the SONY
calibration instructions.
From the SONY Touch Screen Setup display, the following instructions, must be
performed:
a.
Select the Software Calibration button The program will then prompt you to touch
the lower left and upper-right corners of your screen picture. Again, touch the corner
of the displayed screen image and NOT the physical corner of the screen.
If you cannot touch the edge of the screen image because the image is filling the
entire CRT display, adjust the monitor controls so it is possible to touch the edge of
the image and then recalibrate the screen.
b.
Press the Save Settings button.
c.
Press Exit to exit the Touch Screen Setup display.
The following instructions are optional:
4-4
a.
Click and drag to the desired Jitter Control value (default 0).
b.
Click and drag to the desired Press Threshold value (default 6).
c.
Click and drag to the desired Release Threshold value (default 2).
3BUR001 835R0001 REV C
Section 4.2.2 Using Xtouch
d.
For MouseButton Emulation, Click on Left.
e.
The Serial Device Name should match the configured device name.
f.
The Display Name should match the display that is running the touchscreen.
g.
Leave the default values for the Display Width Range and the Display Height
Range.
Figure 4-1. SONY Touch Screen Setup
The program will notify you of the creation of a calibration data file.
It may become necessary to recalibrate your touchscreen. If your monitor is moved or tilted, if
the monitor controls are adjusted, or if a user views the screen from a different angle than usual,
parallax error may cause the cursor to appear to be offset from the user’s finger. In this case,
stop all processes that are reading from the touchscreen data port, and then follow the
instructions in this section to run the calibration session again.
4.2.2.3 Starting Xtouch
To start the Xtouch program, select S from the main menu section. This will start Xtouch with
the device and display options configured at the Default Options menu. If the device and display
options are correct, select y; the Xtouch session will start. To change either the device or the
display, refer to Section 4.2.2.1, Default Xtouch Options.
3BUR001 835R0001 REV C
4-5
NOTE
Xtouch must be started every time the Xserver is started. This includes each time
the Operator Station is started from AutoStart.
4.2.2.4 Terminating Xtouch
To terminate an Xtouch session, select T from the main menu section. This option will search
the process list for an Xtouch process attached to the display option configured at the Default
Options menu. If this option does not terminate the Xtouch session, then you will need to kill
the Xtouch process manually.
To kill Xtouch manually, open a terminal window on the screen that is running Xtouch. Enter
the following command to determine the process id:
ps -ef | grep xtouch
This command will produce a listing of all the Xtouch processes. Next, you will need to
determine the name of your X display. To do this, enter the following command:
echo $DISPLAY
This command will tell you the name of your X display. Now you must search the process list
for the Xtouch command that refers to the name of your display. If the process ID for the Xtouch
process was 1234, the command
kill -9 1234
will stop the Xtouch process. If you need further assistance, contact your system administrator
or call the Technical Support Organization via SUPPORTLINE: in the U.S., 1-800-HELP-365;
international, 614-224-5888.
4-6
3BUR001 835R0001 REV C
Section 5.1 Error Messages
Chapter 5 Maintenance
5.1 Error Messages
5.1.1 AdvaCommand Error Messages
The AdvaCommand software has on-line diagnostics to detect and warn users of error
conditions.
5.1.1.1 Swap Space Improperly Configured
When the AdvaCommand software is started, the swap space configuration is checked. The
system swap space must be at least 2.5 times the installed RAM. If the swap space is too low
when AdvaCommand starts, the background of the start-up X-window screen will be red, and
the error dialog will be displayed, Figure 5-1. When there is a swap space error, the
AdvaCommand software will not start.
Figure 5-1. Swap Space Error Dialog
Problem Resolution
When the station software is initially installed, the swap space size is automatically configured.
If additional RAM is added, the swap space is no longer configured properly. To correct this
problem, add either filesystem swap space or device swap space.
To add device swap space, you must re-install the system. This provides the best runtime
performance.
To add file system swap space, refer to Section 3.6.22, Adding File System Swap Space.
Filesystem swap space does not offer as good of performance as device swap space.
3BUR001 835R0001 REV C
5-1
5.1.1.2 OMF Shared RAM Exceeded
The AdvaCommand software checks the OMF shared RAM utilization every time you change a
display. If the OMF usage is greater than 90 percent of the maximum, a shared memory warning
is displayed, Figure 5-2.
Figure 5-2. OMF Shared Memory Warning
If you click on the VIEW LOG button, the Shared Memory Help Dialog appears, Figure 5-3.
This window displays the log of OMF memory information. You can scroll forward and
backward by using the scroll bar on the left side of the log window.
Figure 5-3. OMF Shared Memory View Log Dialog
Problem Resolution
The OMF shared RAM is used for data access. The default value is 10 Mbytes. If the OMF
Shared RAM is exceeded, the AdvaCommand software stops, and additional RAM must be
allocated. If the dialog appears, you should increase the OMF allocated RAM and restart the
AdvaCommand software. Increasing the OMF shared RAM cannot be performed while
AdvaCommand is running. You should increase the OMF shared memory in 2 Mbytes
increments until the dialog no longer appears. Greatly increasing the OMF allocated RAM will
eliminate the warning dialog, but may cause excess memory usage and decreased system
performance.
To modify the OMF shared RAM follow these steps:
5-2
1.
Stop the AdvaCommand software.
2.
In an HP terminal window, logon as root.
3BUR001 835R0001 REV C
Section 5.1.2 Error Messages for Xtouch (Touchscreen) Software
3.
Enter: cd /etc/opt/advant/OMF
4.
Change the access rights for the configuration file:
chmod 644 /etc/opt/advant/OMF/config.cfg
5.
Modify the content of the configuration file config.cfg
Find the section [SharedMemory], and change the memory size. The default size is 10240
Kbytes. To add 2 Mbytes, increment the number by 2048. 12 Mbytes would be 12288
# Size is in Kbytes
Size
= 12288
6.
Restore the access rights for the configuration file:
chmod 444 /etc/opt/advant/OMF/config.cfg
7.
Restart AdvaCommand
For more information on optimizing OMF shared RAM, refer to Section 3.6.21, Optimizing
OMF Shared RAM Usage.
5.1.2 Error Messages for Xtouch (Touchscreen) Software
5.1.2.1 Calibration Diagnostic Messages
Below is a list of error messages and warnings that may be generated by the calibration
program. Each is followed by a brief explanation of the message or condition, as well as
suggestions on how to remedy the problem.
•
“Usage: ccalib device_name”
You must specify which RS-232 communications device port is attached to the
touchscreen controller, so that the software knows where to look for touchscreen data.
From the Default Options menu, specify the -device option for a known device (for
example, /dev/tty00).
•
“open: <error text>”
•
“Invalid device <device_name>”
The device file <device_name> you specified as the command line argument to the
calibration program could not be opened for reading. The error text may provide a clue to
the nature of the problem. Be sure that the file you specified actually exists on your
system. Check for typing errors in your command line. Make sure you specify the full
pathname of the device file (for example, “/dev/tty00” and not “dev/tty00” or “tty00”).
Verify that you have read permission on the device file.
3BUR001 835R0001 REV C
•
“ioctl [TCGETA]: <error text>”
•
“ioctl [TCSETA]: <error text>”
5-3
•
“Could not get/set/port attributes.”
An error occurred while reading or setting the communication parameters for the device
port you specified as the command line argument to the calibration program. Verify that
this device name corresponds to an RS-232 communications port and that you have
permission to change the port settings.
•
“Touch bottom left corner of screen. …no response when screen is touched”
Make sure that:
–
The controller is connected to the correct RS-232 port.
–
The controller has power.
–
The touchscreen has power.
–
The touchscreen is connected to the controller unit.
–
All cabling connections are tight and secure.
–
You press firmly and then release completely.
If the problem persists, see Section 5.1.2.5, Hardware Problems.
•
“Error creating ccalibfile, create: <error text>”
The software was unable to create the calibration data file. The error text may provide a
clue to the problem. Some likely causes include:
•
–
/usr/lib/tsi directory does not exist
–
You lack write permission to the /usr/lib/tsi directory
“write: <error text>”
An error occurred while writing data to the calibration file. The error text may provide a
clue to the nature of the problem. Run the calibration program again.
•
“Created filename <filename> in <directory>”
A calibration file has been created in the directory specified. If no error messages were
displayed during the procedure, you should be able to run the Xtouch software using this
calibration file. If any error messages were displayed while running the calibration
program, you should remedy the cause of the error(s) and run the calibration program
again before running Xtouch.
5.1.2.2 Xtouch Diagnostic Messages
Below is a list of error messages and warnings that may be generated by the Xtouch program.
Each is followed by a brief explanation of the message or condition, as well as suggestions for
how to remedy the problem.
•
“xtouch <version>”
This line indicates the version number of the Xtouch software.
•
5-4
“open: <error text>”
3BUR001 835R0001 REV C
•
“Invalid device <device_name>”
The device file <device_name> you specified as the command line argument to the
calibration program could not be opened for reading. The error text may provide a clue to
the nature of the problem. Be sure that the file you specified actually exists on your
system. Check for typing errors in your command line. Make sure you specify the full
pathname of the device file (for example, “/dev/tty01” and not “dev/tty01” or “tty01”).
Verify that you have read permission on the device file.
•
“ioctl [TCGETA]: <error text>”
•
“ioctl [TCSETA]: <error text>”
•
“Could not get/set/port attributes.”
An error occurred while reading or setting the communication parameters for the device
port you specified to the calibration program. Verify that this device name corresponds to
an RS-232 communications port and that you have permission to change the port settings.
•
“Could not find calibration file, Using default calibration data”
The calibration data file could not be opened. Check the /usr/lib/tsi directory for the
calibration file with a “.IR” extension. Make sure you have read permission for the
calibration file. If the file does not exist or if the problem persists, run the calibration
program again.
•
“Calibration file data is corrupted, Using default calibration data”
The calibration data was not in the format expected by the Xtouch software. Run the
calibration program again to recreate the calibration file.
•
“Not able to create atom.”
An error occurred while attempting to create the “X_TOUCH_EVENT” atom for sending
client messages. For more information, call the Technical Support Group via
SUPPORTLINE: in the U.S., 1-800-HELP-365; international, 614-224-5888.
•
“Touchscreen data is unreadable.”
An error occurred while reading data from the touchscreen controller. Verify that all cable
connections are secure, and run the Xtouch program again.
5.1.2.3 “Problem with X...”
•
The Xtouch software was unable to open a connection to the X server. If you specified a
“-display” option on the command line, verify that the display is a valid X display. Try
running a program such as xclock to that display. For example, enter the command:
xclock -display <display_name>
Make sure that the X server is accepting connections from your network node. If not, use
the xhost command from the target node. Check your environmental DISPLAY variable
with the env command to be sure it is correct.
3BUR001 835R0001 REV C
5-5
5.1.2.4 Performance Problems
This section lists several common problems that are experienced after the Xtouch software is
running. Following the description of each problem are some suggestions for correcting the
difficulty.
•
Inverted pointer response (for example, moving your finger from left to right results in the
pointer moving from right to left).
Rerun the calibration program. If this does not solve the problem, try running the
calibration program again, touching the upper-right corner first (when prompted to touch
the lower-left) and the lower-left corner last. If the problem still persists, contact the
Technical Support Group via SUPPORTLINE for assistance.
•
Pointer consistently offset from touch location.
Rerun the calibration program. To guard against parallax errors, be sure that you calibrate
the screen from the same position you will use when running the Xtouch software. Note
that adjusting monitor positional controls or physically moving the monitor can affect the
apparent calibration of the touchscreen.
•
Calibration good at center of screen, worse towards edges.
You must recalibrate your touchscreen. This problem can be caused by touching areas
outside the touch-sensitive area of the screen during calibration, or by touching inside the
corners of the display image. Adjust the monitor display area so that there is a large blank
area between the edges of the displayed image and the physical limits of the screen. Rerun
the calibration program, touching the corners of the displayed image, not the physical
corners of the screen. Check the calibration. If the problem persists, contact the Technical
Support Group via SUPPORTLINE for assistance.
•
Pointer tracks finger, but applications do not respond as though mouse button had been
pressed.
Xtouch’s mouse emulation does not extend to window managers, since these applications
ignore events generated by the Xtouch software. Window manager functions such as
moving, resizing, and iconifying windows cannot be performed with the touchscreen.
Some development toolkits, such as the OpenLook toolkit, ignore the events generated by
Xtouch as well. Applications developed using these toolkits may not respond reliably to
the touchscreen.
•
Touchscreen response is intermittent.
Check that all cabling connections are secure. If possible, substitute other cables. If the
problems persist, contact the Technical Support Group via SUPPORTLINE for assistance.
•
Pointer wanders erratically.
If your touchscreen controller unit is installed inside your monitor, electromagnetic
interference or overheating may be responsible. Contact the Technical Support Group via
SUPPORTLINE for assistance.
5-6
3BUR001 835R0001 REV C
5.1.2.5 Hardware Problems
•
Verify that the touchscreen controller is attached to the same device port you specify in the
calibration or Xtouch programs.
•
Make sure that no other process is attempting to read from the touchscreen device port.
Only one process can access the touchscreen data port at a time. If conflicting processes
are attempting to read the data port, kill all processes accessing the data port and try the
calibration program again.
•
Make sure that the touchscreen is connected to the controller unit, that the controller unit is
connected to the RS-232 port, and that the controller has power. Verify that all connections
are secure.
•
Try a null-modem cable between the controller unit and the data port (a null-modem cable
swaps pin 2 and pin 3), since your serial port may expect null-modem input.
•
For SEU IC510 and IC511 only: verify that the DIP switch settings on the touchscreen
controller board inside the SEU are correct. The touchscreen controller is the board with
the 8-pin telephone jack connector.
W3-1 OFF
W3-2 OFF
W3-3 OFF
W3-4 OFF
W3-5 OFF
W4 1-2 OFF
W4 3-4 ON
•
If you have another serial port available, try connecting the touchscreen controller to that
device port instead.
If you experience a problem not addressed above, or if the above information is not sufficient to
solve your problem, call the Technical Support Group for assistance via SUPPORTLINE: in the
U.S., 1-800-HELP-365; international, 614-224-5888. Please have as much information
available as possible when you call, including:
3BUR001 835R0001 REV C
•
Your computer hardware.
•
Your Operating System version.
•
The type of touchscreen you have.
•
The version number of the Xtouch software.
•
Your touchscreen vendor.
•
A complete description of your problem.
5-7
5.1.3 Error Messages for Serial Expansion Unit (SEU)
Serial port errors due to overruns, parity errors, framing errors, or multiple errors are posted to
the console. See the man page on termio(7) for information about controlling parity error
reporting.
Parallel port errors due to “printer busy”, “printer out of paper”, or “printer not selected” are
also posted to the console.
NOTE
Some printers erroneously report printer errors. The scsiTerminal Server driver
will display these error conditions on the console.
5.1.3.1 If You Have SEU Problems
The most common SEU problems are caused by improper hardware installation and/or cabling
and improper device nodes.
•
Check your SCSI cable(s) carefully. SCSI cable(s) may look as if they are connected, but
they may not be making a connection.
•
Make sure the SEU is receiving power. The LED on the face of the SEU should be
illuminated. Also, the LED on the scsiTerminal Server inside of the SEU should be
illuminated and not blinking. (If it is blinking, there has been a self-test error in the
scsiTerminal Server unit.)
•
Check your cabling to the terminal or printer. Try swapping cables. Use only known
cables, if possible. If you have an RS-232 breakout box, you might want to use it to help
track down problems with a terminal or modem interface.
5.2 Full Station Backup/Recovery for AdvaCommand Stations 1.6/1 or Later
Ignite-UX client-server software is used to perform full backups and restores of AdvaCommand
Stations 1.6/1 or later with options. It can create a system image which can be restored at a later
time.
All stations are installed with Ignite-UX client software. This allows them to be backed up by an
Ignite-UX server station.
One or more stations must be installed with the Ignite-UX server software. This allows these
stations to backup client stations. Server stations must have enough free disk space to store an
image of a single client station (approximately 500Mb). To install the Ignite-UX server
software, refer to the instructions: Installation of Ignite-UX Server Software in Section 2.2.7.3,
Installing HP-UX 10.20, AdvaCommand and Options from an Ignite Server.
5.2.1 Backing Up a Station
To create an image, perform the following instructions on the Ignite-UX client station:
1.
5-8
As root user, enter: cd /
3BUR001 835R0001 REV C
Section 5.2.1 Backing Up a Station
2.
To create a system image, the client station must have a minimum number or processes
running. To do this, enter: shutdown 0
This command shuts down the station to single user mode. You may be asked if you want
to send a message. Press Return to accept the default.
3.
Enter:
/usr/sbin/os_make_sys_image <hostname> <ignite_server_ip>
where:
<hostname> is the client’s hostname
<ignite_server_ip> is the IP address of the ignite server
This will create a system image of hostname (client) on ignite_server_ip (server), and a
system configuration file for hostname on ignite_server_ip. The client will reboot itself
when the operation is complete.
4.
If you wish to minimize disk usage, or make a backup copy of an image, you can “tar”
the client image and configuration file to a DDS tape on the server.
NOTES
•
It is recommended that you backup your images either by backing up the
ignite server, or making a tape copy of the image(s) with the tar command.
•
If you want to make a tape copy of the image(s), it must be done before doing
step 5.
An example of the tar command to save the image and configuration files to tape is:
tar cvf /dev/rmt/0m /home/opt/ignite/images/<hostname>.*
The files to “tar” to tape are named using the client’s hostname with a ‘.gz' or ‘.config’
suffix:
/home/opt/ignite/images/<hostname>.gz
/home/opt/ignite/images/<hostname>.config
where:
For example: /home/opt/ignite/images/os1.gz
/home/opt/ignite/images/os1.config
5.
After the client system image has been created, you must follow these steps on the IgniteUX server station to allow Ignite to perform the restore operation.
a.
As root user, enter: cd /
b.
Enter: /usr/sbin/os_add_image <hostname>
where:
3BUR001 835R0001 REV C
5-9
This command adds the client’s configuration information to the Ignite-UX
configuration files and changes the suffix of the configuration file name from .config
to .impacts.
5.2.2 Restoring a Station
To restore your station:
1.
If the ignite server that you are using to perform the restore is not the server that was used
to perform the backup of the client image, the following instructions must be done on the
new ignite server.
a.
Copy the client image from tape using the tar command. An example of the tar
command to restore the image and configuration files from tape is:
tar xvf /dev/rmt/0m
b.
Enter /usr/sbin/os_add_image <hostname>
where <hostname> is the clients hostname.
2.
Logon as root to the Ignite-UX server. Run the Ignite-UX interface by entering the
command: /opt/ignite/bin/startIgnite
3.
If the client is not displayed in the Ignite-UX window, perform step 4; otherwise, skip to
step 5.
4.
Select Actions->Boot New Client… from the Actions pulldown menu.
a.
Enter the hostname of the machine you wish to restore and press the OK button.
You will then see a dialog window stating that the Ignite-UX server is going to reboot the target
machine.
If you get the message “The target system “hostname”, is not allowing
root remsh access by you root@”hostname"”, answer y to the question “Would
you like bootsys to set the .rhosts file on that system at this
time? ([y]/n)” and then enter the root password for the target machine at the Password
prompt.
NOTE
If you get an error message stating that the Ignite-UX server can not lookup the IP
address of the target machine, you will need to edit the /etc/hosts file and
add a line for the target machine.
b.
Within a few minutes you will see the target machine appear as a client in the IgniteUX window.
5.
Select the client you wish to restore from the Ignite-UX window.
6.
Select Actions->Install Client->New Install from the Actions pull-down menu.
If you used the Ignite Server to install the machine, you will be asked if you want to
reinstall the machine. Answer Yes to this question. You will then be asked if you wish to
retain the settings from the current session. Answer No to this question.
5-10
3BUR001 835R0001 REV C
Section 5.3 AdvaCommand Partial Backup and Recovery
7.
Using the Basic tab, choose which core archive you wish to restore from the
Configurations selection.
8.
Using the System tab, enter the Time Zone and Root Password and verify the other
machine specific system parameters (Hostname, IP Address, Subnet mask, Time and Date
information, Network Services).
9.
Press GO!, and read the warnings. Do not worry about anything pertaining to loss of data
on the disks, the root password, or system’s time zone. This data is stored in the archive
image.
5.3 AdvaCommand Partial Backup and Recovery
This section describes how to back up and restore specific files on your Advant Station Operator
Station. This functionality is provided by the fbackup and frecover commands in HP-UX.
With these commands, if you know the path specifications and contents of individual files, you
can specify explicitly which files to back up and recover.
The fbackup and frecover commands have many options that meet specific
backup/restore requirements. This section provides instructions for using these commands with
a limited number of options for the most basic backup/restore applications. If the options
described in this section do not meet your requirements, refer to the HP-UX manual pages for
these commands for further information.
•
For fbackup enter: man fbackup
•
For frecover enter: man frecover
5.3.1 fbackup
For Advant Station Operator Station applications, fbackup transfers files from the hard
disk(s) to the DAT tape. For each file that is transferred, the contents of the file and all relevant
information necessary to restore it to an equivalent state are copied to the DAT tape.
The fbackup command lets you periodically back up application software such as database
configurations, TCL programs, and reports. This involves backing up the specific files where
the application software resides.
NOTES
3BUR001 835R0001 REV C
•
fbackup allocates resources that are not returned to the system if it is killed
in an ungraceful manner. If it is necessary to kill fbackup, send it a
sigterm, NOT a sigkill, with the kill command.
•
fbackup does not require special privileges; however, if you do not have
access to a given file, the file is not backed up. To back up all files, you must
have access at the root level.
5-11
The -g, -i, and -e options provide the means to specifically include or exclude certain files
in the fbackup command. To use these options, you must know the path specifications and
contents of the files. If you do, refer to the manual pages for fbackup for details on how to use
these options.
Another method for backing up a specific subset of files is via incremental backups. This
method allows you to back up only those files that have changed since a previous backup. Refer
to the manual pages for fbackup for details on how to do incremental backups.
5.3.2 frecover
For Advant Station Operator Station applications, frecover reads files from the DAT tape
where they were backed up and restores them on the hard drive. As with fbackup, you can
either restore all the files on the DAT tape or just a subset of the files.
CAUTION
•
By default, frecover does not overwrite any files on the hard disk(s) that
are more current than the corresponding files on the DAT tape. For instance, if
file1 on the hard disk is dated 6/8/93 12:00:00 and file1 on the DAT tape is
dated 6/1/93 12:00:00, the file on the DAT tape WILL NOT be used to
overwrite the file on the hard disk. Thus, when you do a full restore, you may
not restore all the original files.
If you want to restore all the original files regardless of their age, use the -o
option with the frecover command, as described in the manual pages.
•
To allow frecover to restore files to an external hard disk (any disk other
than the root disk), the mount point for that disk must be defined. For
example, an Operator Station with two disks will be defined to have a mount
point on the second disk. For frecover to successfully restore files to the
second disk, the mount point has to be defined on the second disk before the
command is invoked.
To invoke the frecover command to restore all files from the DAT tape back to the hard
disk(s):
1.
Open a terminal window.
2.
Log in as superuser (root).
3.
At the prompt (#), enter: /etc/frecover -rf /dev/rmt/0m
where
-r is the option for specifying a complete restore of all files
4.
Press <Return>.
NOTE
If the restore is interrupted for some reason, you can restart the command from
the point where it was interrupted by entering:
/etc/frecover -Rf /dev/rmt/0m
5-12
3BUR001 835R0001 REV C
Section 5.4 AdvaCommand 1.6/0 and Later Application Backup/Restore
The -g, -i, and -e options provide the means to specifically include or exclude certain files
in the frecover command. To use these options you must know the path specifications and
contents of the files. If you do, refer to the manual pages for frecover for details on how to
use these options.
If you use the incremental backup method to back up files, refer to the manual pages for
frecover for details on how to restore these files.
5.4 AdvaCommand 1.6/0 and Later Application Backup/Restore
5.4.1 Saving Existing Configuration Information
To save your configuration files, do the following steps:
1.
Document the configuration file /etc/hosts by printing it, writing down its content,
or by copying it to another directory. If you have NFS mounted disks, do the same with
/etc/mnttab and /etc/exports.
2.
Document your printer configurations. They have to be re-configured after the upgrade.
5.4.2 Environments
5.4.2.1 Saving Your Environments
If you wish save your environments, you must save them onto a blank tape by opening the
Environment Builder and using the Distributor ‘Tape Copy’ function. Refer to the AdvaBuild
Environment Builder User’s Guide, for information on using the Distributor.
NOTE
The Environment Builder Distributor ‘Tape Copy’ function provides you with the
option of saving any graphics associated with the environment. It is
recommended that you not save graphics with Environments because it takes a
very long time. Instructions for saving all your graphics are in Section 5.4.3.1,
Saving Graphics. If you save graphics with the Environment, you will only have
to explicitly save any graphics that are not associated with the Environments.
5.4.2.2 Restoring Your Environments
After the AdvaCommand 1.6/1 software is loaded, you should restore the environments from
tape by opening the Environment Builder and using the Distributor “Restore from Tape”
function. Refer to the AdvaBuild Environment Builder User’s Guide for information on using
the Distributor.
3BUR001 835R0001 REV C
5-13
5.4.3 Graphics
5.4.3.1 Saving Graphics
If you wish to save your current graphics, you must save them onto tape. To backup your
graphics onto tape, do the following:
1.
Insert a labeled blank tape into the tape drive.
2.
To save your graphics, perform the following commands from a HP terminal window:
cd /home/operator/osgraphics/lib/source
tar cv *
5.4.3.2 Restoring Your Graphics
To restore your OS graphics, perform the following from a HP terminal window:
1.
Enter su root and then enter the password.
2.
Insert the tape containing your saved graphics into the tape drive.
3.
Enter:
cd /home/operator/osgraphics/lib/source
4.
Enter: tar xv
5.
To change file ownership, enter:
chown -R operator:ocs /home/operator/
5.4.4 Personal Menu Files
5.4.4.1 Saving Personal Menu Files
If want to save Personal Menu files, they must be saved on tape. To backup your Personal Menu
files onto tape, do the following:
1.
Insert a labeled blank tape into the tape drive.
2.
Open an HP Terminal window and log on as operator.
3.
Enter: cd /home/operator/persMenuUsers
4.
Enter: tar cv *
5.4.4.2 Restoring Personal Menu Files
To restore your Personal Menu Files, do the following:
5-14
1.
Open an HP Terminal window and log on as operator.
2.
Insert the tape containing your Personal Menu Files into the tape drive.
3.
Enter: cd /home/operator/persMenuUsers
3BUR001 835R0001 REV C
Section 5.4.5 TCL and Batch 300 Files
4.
Enter: tar xv
5.4.5 TCL and Batch 300 Files
5.4.5.1 Saving TCL and Batch 300 FMS Files
If you wish to save your TCL and Batch 300 FMS files, you must save them on tape. To save
them, you must run the osSaveTCL script.
NOTE
If the Advant Station has AdvaBuild software, saving the TCL FMS files using
the osSaveTCL script is not required because the files are backed up within the
AdvaBuild upgrade preparation procedures in Section 5.6, AdvaBuild
Application Backup/Restore.
To save your TCL and Batch 300 FMS files using the osSaveTCL script:
1.
Open an HP terminal window.
2.
Insert a blank tape into the tape drive.
3.
Enter osSaveTCL
5.4.5.2 Restoring TCL and Batch 300 FMS Files
The script, osRestoreTCL, will restore any TCL or Batch 300 FMS files that were saved.
NOTE
If the Advant Station has AdvaBuild software, restoring the TCL and Batch 300
FMS files using the osRestoreTCL script is not required because the files are
restored within the AdvaBuild post upgrade procedures in Section 2.2.11,
AdvaBuild Restore Data Information.
To restore your TCL and Batch 300 FMS files from tape using the osRestoreTCL script:
1.
Insert the tape with the saved files into tape drive.
2.
As operator, enter osRestoreTCL
5.4.5.3 Saving TCL and Batch 300 Source Code Files
If you wish to keep your current OS1.3 or 1.4 TCL and Batch 300 source code files, you must
save them on tape and restore them after you have installed and started the AdvaCommand 1.6/1
software. To save your TCL and Batch 300 source code files, you must change the directory to
the directory where they are located, and make a tape archive of them onto tape.
For example:
3BUR001 835R0001 REV C
1.
Login as root.
2.
Insert a tape into the DAT drive.
5-15
3.
To change the directory enter: cd /products/user/operator/TCL
4.
To make the tape archive enter: tar cv *
5.
When complete, remove the tape.
5.4.5.4 Restoring TCL and Batch 300 Source Code Files
To restore TCL and Batch 300 source code files:
1.
Insert the tape with files saved form Section 5.4.5.3, Saving TCL and Batch 300 Source
Code Files into the tape drive.
2.
Change the directory (cd) to the desired directory to restore the files to.
3.
Enter: tar xv *
4.
When complete, remove the tape.
5.4.6 Shared Memory Sizes
5.4.6.1 Saving Shared Memory Sizes
You should note the size of your OMF and env shared memory sizes so they can be restored if
needed.
To get the OMF and env shared memory sizes, note the contents of the two files:
/var/opt/advant/MOD-OS/ipc/shm.dat (This file is only one line long).
/etc/opt/advant/OMF/config.cfg (In this file, only the Size parameter of the
[SharedMemory] section is important.)
You will manually restore this information if you reload your software.
5.4.6.2 Restoring Shared Memory Sizes
To restore the OMF memory and env shared memory sizes, the values that were noted in
Section 5.4.6.1, Saving Shared Memory Sizes, should be changed in the files:
/var/opt/advant/MOD-OS/ipc/shm.dat (This file is only one line long.)
/etc/opt/advant/OMF/config.cfg (In this file, only the Size parameter of the
[SharedMemory] section is important.)
The numbers should be updated accordingly.
5.4.7 NLS Definition Files
5.4.7.1 Saving NLS Definition Files
To backup the NLS definition files:
1.
5-16
Log on as any user.
3BUR001 835R0001 REV C
Section 5.4.7 NLS Definition Files
2.
Insert a new tape into the tape drive.
3.
Enter: cd /etc/opt/advant/MOD-OS/lib/nls/
4.
Enter:
tar cv en_US.iso88591
tar rv your_language/*.def
5.
Remove the tape.
5.4.7.2 Restoring NLS Definition Files
To restore the NLS definition files:
1.
As the root user, change to the MOD-OS etc directory, create the american directory, and
restore the archived definition files by entering:
cd /etc/opt/advant/MOD-OS
mkdir -p lib/nls
cd lib/nls
tar xv
mv american en_US.iso88591
chown -R ocsmgr:ocs lib
find lib -type d |xargs chmod 775
find lib -type f |xargs chmod 444
2.
If you have a fonts.alias file, leave it here until after you load the ABB-AC-NLS
fileset.
3.
Read the /lib/nls/README.nls.10.01 file to familiarize yourself with how the
NLS functionality differs from a Unix 9.x machine. In this file you will also find the new
name for the language you desire to use.
4.
Now, move your language definition files to the new language format as follows:
mv your_language new_language_format.iso88591
5.
You must load the ABB-AC-NLS fileset. Insert the tape with the ABB-AC-NLS fileset on
it. As the root user, entering the command:
swinstall -S /dev/rmt/0m ABB-AC-NLS
6.
If you have a fonts.alias file, compare it to the new version and add the changes to
the new version by entering:
diff /opt/advant/MOD-NLS/etc/fonts.alias /opt/advant/MOD-OS/lib/X11
If there are any differences, as the root user, edit the file:
/opt/advant/MOD-OS/lib/X11/fonts.alias
3BUR001 835R0001 REV C
5-17
5.5 AdvaCommand Backup/Restore Utility (HP OmniBack II)
NOTES
•
This procedure can be used on Advant Stations with AdvaCommand software
only. It should not be used on Advant Stations with the AdvaBuild or
AdvaInform options.
•
When the OmniBack utility is running, you will not be able to install an
environment or run the Environment Builder.
OmniBack II is a backup/restore utility that can be used as an alternative means to back up and
restore system data files. This utility is an option that can be purchased directly from Hewlett
Packard.
Some of the advantages to using OmniBack II in place of the standard Advant Station
backup/restore utilities are as follows:
•
You can back up and restore data files for all applications related to AdvaCommand basic
functions, AdvaBuild Display Builder, and AdvaBuild Environment Builder in one basic
step rather than having to use several different utilities.
•
One Advant Station can be designated as the central backup/restore machine and be used
to back up and restore data files on multiple Advant Stations.
NOTE
OmniBack II is intended as a backup/restore tool for data files only, and should
not be used as a means to do a full recovery from a system crash.
OmniBack II includes comprehensive on-line help information with detailed instructions for
back up and restore procedures. This section provides guidelines that are specific to using
OmniBack II to back up and restore data files on an Advant Station with AdvaCommand
software.
5.5.1 Backup Considerations
Editing the Data List
This is the procedure where you specify which data files to back up. You begin editing the data
list by choosing Generate Datalist from the Edit menu in the OmniBack Backup window.
5-18
3BUR001 835R0001 REV C
Section 5.5.1 Backup Considerations
Since your intention is to back up just data files, you must exclude any executable files from the
data list. To do this:
1.
Delete all mount points, except for /home in the Backup Editor window, Figure 5-4.
Delete all
mount points
except /home
Figure 5-4. Deleting All Mount Points Except /home
2.
Exclude the following files that reside in /home:
–
*.PK.*
–
*.DP.*
–
POOLS.PL.*
–
*.x
This is done via the Filesystem Backup dialog. First double-click on the /home mount
point in the Backup Editor window to display the FileSystem Backup dialog, and then
click on the Exclude button to display the Exclude Files/Directories dialog. See
Figure 5-5.
3BUR001 835R0001 REV C
5-19
Click Exclude button.
Specify files to exclude here, then click
Add.
Figure 5-5. Excluding Executable Files in /home
5-20
3BUR001 835R0001 REV C
Section 5.5.1 Backup Considerations
Specify Pre-Execution and Post-Execution Scripts for Backup
When you perform a back up with OmniBack, Oracle processes and the environment installer
process must be shut down before the backup, and then be re-started after the back up. This is
handled by two scripts - a Pre-exec script that runs before the back up, and a Post-exec script
that runs after.
These scripts are specified in the Filesystem Options dialog which is displayed by clicking the
Filesystem Backup Options button in the Filesystem Backup dialog, Figure 5-6.
Figure 5-6. Pre-exec and Post-exec Scripts for Backup
The scripts are:
3BUR001 835R0001 REV C
•
Pre-exec: /opt/advant/MOD-OS/bin/os_omni_pre.com
•
Post-exec: /opt/advant/MOD-OS/bin/os_omni_post.com
5-21
5.5.2 Restore Considerations
Specify Pre-Execution and Post-Execution Scripts for Restore
When you perform a restore with OmniBack, Oracle processes and the environment installer
process must be shut down before the restore, and then be re-started after the restore. This is
handled by the same two scripts used in the back up procedure.
For restore, these scripts are specified in the Filesystem Options dialog which is displayed by
clicking the Options button in the FileSystem Restore dialog, Figure 5-7.
Figure 5-7. PreExec and PostExec Scripts for Restore
5-22
3BUR001 835R0001 REV C
Section 5.6 AdvaBuild Application Backup/Restore
5.6 AdvaBuild Application Backup/Restore
5.6.1 Project Backup
A project backup is used to save project data to disk or tape for freezing a project status,
archiving a project or moving project data from workstation to workstation. It is also possible to
restore a project after a failure, to continue work with a known good project.
The saved file set can include data derived from ORACLE database and UNIX file system. In
case of archiving data, keep documentation and tape together, similar to full backup.
5.6.1.1 Saving Project Data to DAT Tape
This procedure backs up project, TCL, and related data to DAT tape.
Save TCL Source Code Files
Make sure all TCL source code files for each project reside in a directory beneath the respective
project directory ($C_CAPE/<project>).
To save TCL source code files:
1.
2.
If not already created, make a new directory TCL beneath the project directory (of the
particular project).
3.
Copy all TCL sources for this project to this path.
Make sure this is done for all projects.
Save Additional User-specific Data
Any user-specific files (script or data) that exist within the file structure, but are not beneath a
project directory ($C_CAPE/<project>) must also be backed up. To do so:
1.
2.
Create a new directory (for example, USER_DATA) beneath a project directory you plan
to backup. If the data is related to a particular project, create the new directory beneath that
project directory.
3.
Copy all user-specific files to this path.
Record Project Information
Record project information (name, size, and number) for each project to avoid losing data
during the upgrade. To check project data:
1.
3BUR001 835R0001 REV C
Log in as the ocsmgr user, by entering: su - oscmgr
5-23
2.
3.
Open project administration using the admin username and password. Ensure the
password for the admin user is set to admin.
4.
Check and record the following information for each project using the AdvaBuild
Structure Builder (Administer/Projects or Administer/Users):
–
The project name, size and number
NOTE
This project number must be used in order to successfully restore the project.
–
all usernames and group numbers of the project as indicated in the User window of
the administration function.
NOTE
If the default user password has been changed (from <project>_cfg), you must reset it
prior to installing an upgrade or patch. Failure to do so prior to installing an upgrade or
patch prevents the upgrade (or patch) from successfully creating any new tables and/or
performing modifications on existing tables. This can be done from the
ADMINISTRATION form by selecting the Administer/Users menu option. Then, from
the USERS form, navigate to the user you wish to reset. Next, select the Edit/Password
menu item. This will bring up the form used to change the password.
Export Project Data and Store it to Tape
For EACH project you are going to backup, do the following:
1.
Log in as user ocsmgr by entering: su - ocsmgr
2.
Change the directory as follows: cd /home/ocsmgr
3.
Insert a blank tape into the tape drive (set the tape slide to the "READ/WRITE" position).
4.
To backup the project to tape, enter:
backup_project.sh -p <project> 2>&1 | tee $C_BIN_CAPE_LOG/backup_<project>.log
5.
When you see the message "Do you want to continue [y]", press <Return>.
6.
After project backup to tape is finished, remove the tape and label it with project name,
date, used project database size, and set the tape slide to the "READ ONLY" position.
5.6.1.2 Saving a Project Release and Placing it into the Same Station
A project release can be frozen by storing it as data files in a separate directory, Figure 5-8. A
project release refers to the project data in the AdvaBuild database and to the operating system
objects, for example, text and drawing files. By saving a project release, the complete project
subtree is copied under a user chosen directory (default directory: …/proj/proj_adm/savedirs).
5-24
3BUR001 835R0001 REV C
Section 5.6.1 Project Backup
Do not copy or restore the database files by operating system commands, especially not before
you dismount the database. Simply replacing database files results in an inconsistent database.
If you do so before you dismount the database, a database crash occurs.
Overview
The database contents are exported into a single file placed in the project directory sav using the
Oracle Export utility.
All project directories except dat (which contains the database files) are copied underneath the
user chosen directory (default directory: …/proj/proj_adm/savedirs) and the original export
file in the project directory sav is removed.
Workstation A
Project 1
Instance
Data
(DB,Files)
Library
Data
(DB,Files)
SAVE
Project 1
Backup Area
...proj/proj_adm/savedirs/
project_release.
Figure 5-8. Saving a project Release in the Same Station
Procedure
To save a project release and place it in the same station:
1.
Log in as user oscmgr, enter: su - ocsmgr
2.
Start the Structure Builder by entering: stb
3.
Open project administration using the admin username and password. This opens the
Administration window.
4.
This opens the Administration Projects window.
3BUR001 835R0001 REV C
5.
Click on Menu to access the menu bar of the Projects Administration window.
6.
Choose Save from the File menu.
5-25
This displays the Save Project dialog box, Figure 5-9.
Figure 5-9. Save Project Dialog Box
7.
Enter the number of the project to be saved (the number can be chosen from a list).
After entering the number, the project name is entered automatically.
8.
Press <Return> or <Tab> to move to Release No field.
9.
Enter a unique release ID consisting of characters or numbers.
10. Press <Return> or <Tab> to move to the field containing the name of the directory under
which the project directory structure will be saved (default: …/savedirs).
11. Enter the directory.
To accept the default directory go to the next step.
To choose a directory, give the complete pathname, for example:
/home/opt/advant/ES/proj/savedirs
12. Press <Return> to move the cursor to the Ok button.
NOTE
Make sure that write access is granted to the target directory (to the directory path
above) in case the target directory must be created first.
5-26
3BUR001 835R0001 REV C
13. Click on Accept/Save in the Projects Administration window.
This starts the save project function and displays a message box. The message asks you to
wait for the function to complete. When the function is finished, this message box is
removed and another box is displayed. This box indicates whether or not the function was
In either case the logfile provides a detailed description of the saving process. The logfile
named savpro_project_release.log resides in the directory pointed to by the environment
variable $C_CAPE_ALL_ADM_LOG.
NOTES
•
You should check the logfile savpro_project_release.txt as well, especially in
case of program error. This logfile provides more detailed information.
•
Deleting a project also deletes the saved project under the project directory.
You can not restore a project release via the File Restore menu item until it
has been saved.
5.6.1.3 Restoring Saved Project Data from DAT Tape
This procedure restores project, TCL, and related data from DAT tape.
Create Project Body
To create the project body (or bodies):
1.
Open an HPterm window, and log in as user ocsmgr by entering: su - ocsmgr
2.
3.
Log in to the Administration application as user admin (default password is admin).
4.
When the Administration window is opened, select the Menu function (or press <f5>) to
access the menu bar.
5.
This opens the Projects window.
6.
Select the Menu function to access the Projects window menu bar.
7.
field.
8.
3BUR001 835R0001 REV C
Enter the Project Name recorded at the time the project was saved to tape in Section
5.6.1.1, Saving Project Data to DAT Tape, and then press <Return> or <Tab> to move the
cursor to the Project No (Number) field.
5-27
9.
Enter the Project Number recorded at the time the project was saved to tape in Section
5.6.1.1, Saving Project Data to DAT Tape, and then press <Return> or <Tab> to move the
cursor to the Project Size field.
NOTE
You must use the old project number that was previously recorded.
10. Enter the project size recorded at the time the project was saved to tape in Section 5.6.1.1,
Saving Project Data to DAT Tape, and then press <Return>.
The comment is displayed in the top-most object in the Structure Builder tree presentation.
This field is optional. If you do not want a comment, simply press <Return> or <Tab> to
The project description is optional. If you do not want a description, simply press
<Return> or <Tab> to move to the next field. You may have to press <Return> or <Tab>
three times (once for each line in the Project Description field). This moves the cursor to
the CFG-Password field.
13. Define passwords for the project’s two default users.
For each new project, two default users are created: a user <project>_CFG and a user
<project>_RDR. The CFG and RDR user names cannot be changed. Only the passwords
can be modified.
The name and default password for the CFG user is <project_name>_CFG. This user
(group 2 = CFG) owns all project tables and can configure Oracle Reports 2.5. The name
and default password for RDR user is <project_name>_RDR. This user has read-only
access to the project.
a.
b.
14. Enter the name of the source project that you want to use as the basis for the new project,
and then press <Return>.
small for the source project, the size is adapted to be at least as big.
5-28
3BUR001 835R0001 REV C
own, choose Y = Yes. You can toggle the protection mode via the Edit-Modify menu item
as described in the AdvaBuild Basic Functions User’s Guide.
17. Press <Return> to move the cursor over the OK target at the bottom of the dialog box.
This message indicates whether or not the function was successful. This message must be
In either case, the logfile provides a detailed description of the function. The logfile
inspro_<project>.log resides in the directory pointed to by the environment variable
If the project has been successfully inserted (created), close the Projects window and create any
additional users that had existed for each project at the time the project was saved to tape. The
project restore will not recreate them. See the section below: How to Create Additional User(s)
for a Project.
After the project is created, configure the PROJECT object attributes (CUSTOMER,
PRO_LEADER, RESP_DEPT, REVISION…) via the Template Builder. This is required
because the PROJECT object in release 2.7/3 will not be modified by restoration of data from
the previous release.
How to Create Additional User(s) for a Project
When you create a project, two default users are assigned automatically: a configuration user
<project>_CFG of user group 2 = CONFIG with special access rights, and a reader user
<project>_RDR of user group 4 = READER with read-only access to the project.
The configuration user has unrestricted access to all project data and can configure Oracle
Reports.
In addition to the default users, you can assign writer users (user group 3 = WRITER) to do
most of the actual database configuration work.
NOTE
Directories that contain data associated with the original users will be restored
with the project data. These directories are found in the $C_CAPE/my_proj/usr/
path. If a user (that existed when the project was saved) does not exist at the time
of the project restore, the directory associated with that user will be renamed. If at
a later time the user is recreated, the data in the renamed directory can be moved
back into the new user directory.
3BUR001 835R0001 REV C
5-29
To create additional user(s) for a project:
1.
Log in to the Administration function if you are not already logged in.
2.
Choose User from the Administer menu in the Administration window.
This opens the Users window.
3.
Select the Menu function to access the Users window menu bar.
4.
This displays the Insert User dialog box.
5.
Enter the user name recorded at the time the project was saved to tape in Section 5.6.1.1,
Saving Project Data to DAT Tape, and press <Return>.
The logfile name is filled in automatically, using the user name.
6.
Enter the password recorded at the time the project was saved to tape in Section 5.6.1.1,
Saving Project Data to DAT Tape, and press <Return>.
NOTE
User name and password should start with a letter and continue with letters, digits
or ‘_’ (underscore). Do not use any special characters like @, # or +.
7.
Enter the appropriate group number recorded at the time the project was saved to tape in
Section 5.6.1.1, Saving Project Data to DAT Tape, to establish the access level for the user.
Usually, group 3 = WRITER is chosen for a normal project user, but you can also select 4
= READER to create a user with read-only access or 2 = CONFIG for a user with special
configuration privileges. The corresponding group name is entered automatically.
8.
Assign the user to a specific project.
a.
Press <Return> to move to the next field.
b.
Enter the project number recorded at the time the project was saved to tape in Section
5.6.1.1, Saving Project Data to DAT Tape (as shown in the Pro No column in the
Projects window).
c.
Press <Return>.
The corresponding project name is entered automatically, and the cursor is moved to
the OK target on the bottom of the dialog box.
9.
Select Accept/Save.
This starts the insert user function and displays a message box. The message asks you to
wait for the function to complete. When the function is finished, this box is removed and
In either case the log file provides a detailed description of the insertion process. The log
file insusr_<user>.log resides in the directory pointed to by the environment variable
10. Repeat this procedure for as many users as required.
5-30
3BUR001 835R0001 REV C
Restore Project Data
To restore/upgrade the project data for each project previously saved to tape:
Insert the tape containing the backed up project data and start the restore/upgrade project script
“restore_project.sh” for each project separately as follows:
1.
2.
Make sure you are in the /home/ocsmgr directory.
3.
Insert the tape that holds the project data.
4.
To restore/upgrade a project, enter:
restore_project.sh -p <project> 2>&1 | tee $C_BIN_CAPE_LOG/rest_<project>.log
5.
After restoration of the project is complete, remove the tape.
6.
Check the log file $C_BIN_CAPE_LOG/rest_my_proj.log for errors.
7.
Repeat step 3 through step 6 until all your projects are restored.
Oracle warnings (imp-00033) will appear in the upgrade_project.sh log file for
tables that are new in the AdvaBuild 2.7/3 release. These can be ignored.
NOTE
This process will also restore the TCL and user-specific data that was stored
beneath each project directory.
5.6.1.4 Restoring a Saved Project Release within a Station
A project release can only be restored to the project in the current database it has been saved
from, Figure 5-10. After restoring a project release, all modifications done to the project since
the release was saved are lost. If you want to keep these modifications, save a new release
before restoring an old one.
The File Restore menu item is used to restore a project release that was saved via File Save.
Overview
The contents of all project directories except dat (containing the database files) and usr
(containing the user directories) are overwritten by the contents of the saved project directories.
3BUR001 835R0001 REV C
5-31
The contents of the project are overwritten by the contents of the database as it existed during
project save. This is done by filling the project tables with the data imported from the export file
which was created with the Oracle export utility during File Save.
Workstation A
Project 1
Instance
Data
(DB,Files)
Library
Data
(DB,Files)
RESTORE
Project 1
Backup Area
......proj/proj_adm/
savedirs
Figure 5-10. Restore a Saved Project Release
Procedure
1.
Log in as user ocsmgr.
2.
Start the Structure Builder by entering: stb
3.
Open project administration using the admin username and password. This opens the
Administration window.
4.
Choose Projects from the Administer menu to open the Projects window.
5.
Click on Menu to access the menu bar of the Projects Administration window.
6.
Choose Restore from the File menu.
This displays the Restore Project dialog box, Figure 5-11.
5-32
3BUR001 835R0001 REV C
Figure 5-11. Restore Project Dialog Box
7.
Enter the number of the project to be restored (the number can be chosen from a list).
After entering the number, the project name is entered automatically.
8.
Press <Return> or <Tab> to move to Release No field.
9.
In Release No field, choose the identifier of the release you want to restore (can be chosen
from a list).
After you enter the release number, the Save Date and Logfile fields are filled in
automatically.
10. Press <Return> or <Tab> to move to the CFG-Password field.
11. Enter the configuration user password for the project.
The configuration user is one of the two users that were created when the project was
inserted. The name is project_CFG. If you have not changed the default password, the
password is project_CFG as well.
12. Press <Return> to move the cursor to the Ok button and click on Ok.
This removes the dialog box.
3BUR001 835R0001 REV C
5-33
13. Click on Accept/Save in the Projects Administration window.
This starts the project restore function and displays a message box. The message asks you
to wait for the function to complete. When the function is finished, this box is removed and
successful and has to be acknowledged by clicking OK.
In either case the logfile provides a detailed description of the restoration process. The log
file named rstpro_project_release.log resides in the directory pointed to by the
environment variable $C_CAPE_ALL_ADM_LOG.
NOTES
5-34
•
It is recommended that you check the logfile rstpro_project_release.txt as
well, especially in case of program error. This logfile provides more detailed
data import information. Search for string ‘IMP-’ to find possible import
errors.
•
If an error occurs when you import project data, the program aborts and the
database state is inconsistent. In this case, start the restoration program again.
3BUR001 835R0001 REV C
Section 5.6.2 FMS Backup and Restore
5.6.2 FMS Backup and Restore
These backup and restore functions are invoked via FREE objects. These FREE objects are
children of the BACKUP/RESTORE FUNCTIONS object which, in turn, is a child of the
PROJECT object, Figure 5-12. This structure is defined under the MOD_STD project and is
included in any project that you create by copying the MOD_STD project.
Figure 5-12. FREE Object Structure for Backup and Restore
General Constraints
Read the following constraints before you attempt to backup or restore FMS files.
•
The HP-UX fbackup and frecover facilities allow only a single fileset per tape.
•
The Structure Builder continues to run while backup and restore operations are in
progress. For this reason only one backup/restore operation is allowed to run at any given
time. It is your responsibility to insure the integrity of the data.
•
There is no provision for determining what is on a tape prior to performing a restore
activity except by manual invocation of the frecover command:
/etc/frecover -f /dev/rmt/0m -I
•
3BUR001 835R0001 REV C
There is no provision for selectively restoring files from a backed up fileset. All files will
be restored regardless of permissions or file dates of existing files. Also, existing files
which are not part of a restored fileset will be left unharmed.
5-35
•
There will be no provision for excluding files from the backup fileset. This means that
installed database files within the HP-FMS area could inadvertently be overwritten by a
subsequent restore operation. Care must be taken to understand the possible implications
when performing any restore operation.
•
There is no provision for including additional files to any backup fileset. The backup
fileset definitions are fixed and the data must reside within the predetermined area. The
HP-FMS area will be defined by the FMSPATH environment variable and the TCL area
will be defined by the path specified by ‘$C_PROJ/TCL’ which, when evaluated, will
point to
/proj/<project_name>/TCL.
•
Before you begin a backup procedure, you must determine if the tape is inserted and not
write protected. The procedure for doing this will overwrite the header placed on the tape
by any previous backup. This means that the underlying HP-UX fbackup facility will
always report that the tape is being used for the first time as opposed to supplying
information about any previous use.
•
The backup and restore procedures will perform there respective operations ‘relative’ to
the specified subdirectory to be accessed. This means that the path from the root to the
specified directory must exist. The backup procedure will change to the specified
subdirectory before invoking fbackup. The restore procedure will also change to the
specified subdirectory before invoking frecover.
5.6.2.1 Full FMS Backup and Full FMS Restore
Full FMS Backup transfers FMS application files including Batch 300, Taylor Ladder Logic,
Taylor Control Language (generated via Multibus-based TCL editor), diagnostic message
archive, and installed MOD 300 database to DDS tape. Full FMS Restore restores these files to
the FMS partition on your hard drive.
CAUTION
FMS Backup also backs up executable FMS files. Be aware that if you upgrade
your engineering station to a newer version of software, and then restore backed
up executable files via FMS Restore, the older executable files on the backup tape
will overwrite the newer (upgrade) executable files.
You are not required to shut down the database when you perform a full FMS backup or restore.
Refer to Section 5.6.2.4, FMS and TCL Backup Procedure and Section 5.6.2.5, FMS and TCL
Restore for details.
5-36
3BUR001 835R0001 REV C
5.6.2.2 User FMS Backup and User FMS Restore
User FMS Backup transfers files under $FMSPATH/WC00 excluding any files listed in
$C_PROJ/util/free/userfiles.dat to DDS tape. User FMS Restore restores these files to
$FMSPATH/WC00/… on your hard drive. The files which get backed up are listed in Table 5-1.
Table 5-1. Files Included in User FMS Backup
Application
File Specification
Description
$FMSPATH/WC00/210/CLASS_/*
Batch equipment class files
$FMSPATH/WC00/210/CONTRL/*
Batch master recipes
$FMSPATH/WC00/210/CUSTOM/*
Batch customization files
$FMSPATH/WC00/210/EQUIP_/*
Batch equipment files
$FMSPATH/WC00/210/MASTER/*
Batch site recipes
$FMSPATH/WC00/210/MATERL/*
Batch material handling files
$FMSPATH/WC00/210/PHASE_/*
Batch phase files
$FMSPATH/WC00/210/WORKIN/*
Batch control recipe files
$FMSPATH/WC00/50/DPOOLS/*
Customized pools for DPSS nodes
$FMSPATH/WC00/50/GPOOLS/*
Customized pools for GATEWAY nodes
$FMSPATH/WC00/50/TPOOLS/*
Customized pools for TURBO nodes
$FMSPATH/WC00/170/PAGEDATA
User-defined graphic symbol files
$FMSPATH/WC00/170/UDPSDATA
User-defined process symbol files
$FMSPATH/WC00/170/LIBDATA
User-defined library symbol files
$FMSPATH/WC00/170/ENV*
user environment source code
$FMSPATH/WC00/170/LINK
Linked/compiled user environment code
BATCH
SYSTEM
PAGEBUILD
CONSCONFIG
$FMSPATH/WC00/50/CFDISPLY/SPALGDSC* Special algorithm data files
$FMSPATH/WC00/50/DB*/*
Compiled user databases
$FMSPATH/WC00/50/INDEX/*/
Installed user database
$FMSPATH/WC00/50/INRECOVR/*
Recoverable user database
$FMSPATH/WC00/1/PLC/*
TLL device files
$FMSPATH/WC00/20556/*
TLL segment files
$FMSPATH/WC00/260/CONFIG/*
PLC user data files
CONFIGURATOR
LADDERLOGIC
PLC
3BUR001 835R0001 REV C
5-37
Table 5-1. Files Included in User FMS Backup (Continued)
Application
File Specification
Description
$FMSPATH/WC00/210/RECIPE/*
TCL recipe files
$FMSPATH/WC00/210/RECIPESR/*
TCL recipe source
$FMSPATH/WC00/210/TCL/*
TCL sequences
$FMSPATH/WC00/210/TCLDB/*
TCL sequence database references
$FMSPATH/WC00/210/TCLDF/*
TCL sequence discrete descriptor tables
$FMSPATH/WC00/210/TCLDS/*
TCL sequence display steps
$FMSPATH/WC00/210/TCLID/*
TCL sequence symbol tables
$FMSPATH/WC00/210/TCLLF/*
TCL sequence link files
$FMSPATH/WC00/210/TCLPC/*
TCL sequence p-codes
$FMSPATH/WC00/210/TCLS/*
TCL sequence string tables
$FMSPATH/WC00/210/TCLTF/*
TCL sequence database scanner tags
$FMSPATH/WC00/220/*
TCL user directories
TCL
NOTES
•
Backing up and restoring these files should in no way be construed as a means
for upgrading files from version to version.There is no guarantee that files
created and backed up within one version of an application will be compatible
with a subsequent version without applying the appropriate upgrade
procedures.
•
You should not save a subset of an application fileset. The user data files for a
particular application should be saved as a whole.
•
The batch application is a superset of the TCL application. If user data files
for batch are being backed up, then the TCL user data files should also be
included.
You can add files to or delete files from this file as required to customize your backup scheme.
You are not required to shut down the database when you perform a user FMS backup or
restore. Refer to Section 5.6.2.4, FMS and TCL Backup Procedure and Section 5.6.2.5, FMS
and TCL Restore for details.
5-38
3BUR001 835R0001 REV C
5.6.2.3 TCL Data Backup and TCL Data Restore
TCL Data Backup transfers TCL application files generated via the TCL Builder (stored in
$C_PROJ/TCL) to DDS tape. TCL Data Restore restores these files to $C_PROJ/TCL on your
hard drive.
You are not required to shut down the database when you use TCL Data Backup or TCL Data
Restore. However, you must insure that TCL files are not being updated. Refer to Section
5.6.2.4, FMS and TCL Backup Procedure and Section 5.6.2.5, FMS and TCL Restore for
details.
5.6.2.4 FMS and TCL Backup Procedure
The procedures for Full FMS Backup, User FMS Backup and TCL Data Backup are essentially
the same. The only difference is the FREE object that you invoke to start the procedure. Follow
the common procedure below. In step 2, open the applicable FREE object depending on the type
of backup you are performing (Full, User, or TCL).
To backup FMS applications on your Engineering Station:
1.
Place a blank tape in the DAT tape drive.
Be sure that the write protect tab is NOT on.
2.
From a HPterm window, start the Structure Builder by entering: stb. Then, login to your
project with the project name and password.
3.
Open the applicable FREE object under BACKUP/RESTORE FUNCTIONS:
–
For a full FMS backup, open FULL FMS BACKUP.
CAUTION
Full FMS Backup also backs up executable FMS files. Be aware that if you
upgrade your Engineering Station to a newer version of software, and then restore
backed up executable files via Full FMS Restore to the older executable files on
the backup tape will overwrite the newer (upgrade) executable files.
3BUR001 835R0001 REV C
–
To backup just the FMS user files, open USER FMS BACKUP.
–
To backup just the TCL files, open TCL DATA BACKUP.
5-39
These objects have a TEMPLATE view and a FREE view, Figure 5-13.
Figure 5-13. Open Object Dialog Box
The TEMPLATE view lets you define the script that the FREE object invokes and well as
various parameters. Generally, you should not have to modify the script or parameters.
The FREE view invokes the script associated with the FREE object.
4.
Select FREE and then click on OK.
This starts the appropriate backup script.
One or more messages are displayed as the process runs, depending upon the success or
failure of the process.
5.
Respond to any messages generated by the backup script as follows:
If the backup fails for some reason, a message box indicating the cause of the failure is
displayed. Click OK in the message box to clear the message, take the appropriate
corrective action according to the message, and then try again.
If the backup is successful, a BACKUP initiated message is displayed, followed by a
BACKUP completed message. Click OK in these message boxes to clear the messages.
The backup process creates a log file in the /tmp directory where you can check the status
of the most recent FMS backup operation.
5-40
3BUR001 835R0001 REV C
Section 5.7 AdvaBuild Copying Projects
5.6.2.5 FMS and TCL Restore
To restore previously backed up FMS applications on your Engineering Station, place the tape
with the backed up files in the DAT tape drive, and then follow steps 2 through 4 from the
procedure above. In step 2, open the appropriate FREE object FULL FMS RESTORE, USER
FMS RESTORE, or TCL DATA RESTORE as required.
CAUTION
When you perform an FMS restore, if there is a file that does not exist on the
restore tape, but does exist in the destination directory, the file will remain intact
in the destination directory after the restore. The restore procedure does not wipe
out the file.
5.7 AdvaBuild Copying Projects
5.7.1 Copying a Project within a Station
A project with its file and database objects can be copied to a new created project, Figure 5-14.
Overview
A new project is created. A directory subtree for the project is established. Space is reserved for
the project in the database. Two users are inserted for the new project by default. All database
and file objects of the source project are copied.
Workstation A
Project 1
Instance
Data
(DB,Files)
Project 2
Library
Data
(DB,Files)
Instance
Data
(DB,Files)
Library
Data
(DB,Files)
COPY
Figure 5-14. Copying a Project within the Station
Procedure
3BUR001 835R0001 REV C
1.
Log in as user oscmgr.
2.
Call the Structure Builder.
3.
Fill in user/password = admin/admin.
5-41
4.
This opens the Projects window, Figure 5-15.
Figure 5-15. Projects Window
5.
5-42
Click on Menu to access the Projects window menu bar.
3BUR001 835R0001 REV C
Section 5.7.1 Copying a Project within a Station
6.
field, Figure 5-16.
Figure 5-16. Insert Project Dialog Box
7.
Enter a unique project name.
8.
Press <Return> or <Tab> to move the cursor to the Project Size field.
The CFG- and RDR-Username, the CFG- and RDR-Password, and Logfile fields are filled
in automatically, using the project name.
9.
Enter the project size and then press <Return>.
The comment is displayed in the topmost object in the Structure Builder tree presentation.
This field is optional, if you do not want a comment, simply press <Return> or <Tab> to
3BUR001 835R0001 REV C
5-43
The project description is optional. The project description (if used) is displayed in the
footers of document packages generated via Oracle Reports 2.5.
You may have to press <Return> or <Tab> three times (once for each line in the Project
Description field). This moves the cursor to the CFG-password field.
12. Define passwords for the project.
For each new project, two default users are created: a user project_CFG and a user
project_RDR. The CFG- and RDR- usernames cannot be changed. Only the passwords
can be modified.
The name and default password for the CFG user is project_CFG. This user (group 2 =
CFG) owns all project tables and can configure Oracle Reports 2.5. The name and default
password for RDR user is project_RDR. This user has read-only access to the project.
a.
b.
13. Enter the name of the source project that you want to copy to the new project, and then
press <Return>.
small for the source project, the size is adapted to be at least as big as the source.
own, choose Y = Yes. You can toggle the protection mode via menu item Edit Modify.
16. Press Return to move the cursor over the OK target at the bottom of the dialog box.
This message indicates whether or not the function was successful. This message has to be
In either case the logfile provides a detailed description of the function. The logfile
inspro_project.log resides in the directory pointed to by the environment variable
5-44
3BUR001 835R0001 REV C
Section 5.7.2 Copying a Project to another AdvaBuild Station in the Network
18. Close the Projects window if the project has been successfully inserted.
5.7.2 Copying a Project to another AdvaBuild Station in the Network
A project can be copied to another workstation by creating a new project and copying the source
project to the new project, Figure 5-17. The new project is saved and transferred via ftp to the
workstation that shall be the destination for the project copy. The saved project copy is restored
at the destination workstation.
Overview
The source project is copied to a new created project on the workstation of the source project.
The project copy is saved and the saved files are packed. The packed files are transferred via ftp
to directory..../proj/proj_adm/savedirs in the destination workstation.
A new project is created in the destination workstation with the same name, release number and
size as the project copy on the source workstation. The new created project at the destination
workstation is saved to the default save directory $C_CAPE/proj_adm/savedirs.
The save path of the saved project in the save directory /savedirs is deleted. The packed file of
the project release is unpacked and stored in /savedirs/project_release on the destination
workstation.
The copied project release is restored on the destination workstation by File Restore (see
Section 5.6.1.4, Restoring a Saved Project Release within a Station).
3BUR001 835R0001 REV C
5-45
Workstation A (project source)
Project X (copy of Proj.1)
Project 1
Instance
Data
(DB,Files)
Library
Data
(DB,Files)
Instance
Data
(DB,Files)
COPY
Project X
Backup Area
packed project files
in user defined file
tar
Library
Data
(DB,Files)
SAVE
Project X
Backup Area
savedirs
ftp
Workstation B (destination of project copy)
Project X (copy of Proj.1)
Instance
Data
(DB,Files)
Library
Data
(DB,Files)
RESTORE
Project X
Backup Area
Project X
tar
Backup Area
savedirs
Figure 5-17. Copying a project to another AdvaBuild Station on the Network
Procedure
5-46
1.
Log in as user ocsmgr, call the Structure Builder, fill in User/Password=admin/admin.
2.
Copy project on workstation of the project source according to Section 5.7.1, Copying a
Project within a Station.
3.
Save the copy to the save directory below the new project directory according to Section
5.6.1.2, Saving a Project Release and Placing it into the Same Station.
3BUR001 835R0001 REV C
Section 5.7.3 Copying a Project to another Disconnected AdvaBuild Station
4.
Change to the new project subdirectory where the saved project copy is located
–
5.
cd $C_CAPE/proj/proj_admin/savedirs
Pack the saved files of the project copy into a separate file by tar command.
–
tar -cvf file project_release
6.
Create new project on the destination workstation by copying an existing one (for
example, the standard project) according to Section 5.7.1, Copying a Project within a
Station.
7.
Save the new created project on the destination workstation to the save directory
…/proj/proj_admin/savedirs according to Section 5.6.1.2, Saving a Project Release and
Placing it into the Same Station.
8.
Change to the save directory on destination workstation and delete the whole save-path.
Enter:
9.
–
cd $C_CAPE/project_adm/savedirs
–
rm -rf project_release
The information about the backed up project and save-paths are stored in the Oracledatabase.
Transfer content of the packed file in directory …/proj/proj_admin/savedirs of the
source workstation to the directory …/proj/proj_admin/savedirs on the destination
workstation. The following activities are started from the destination workstation B.
ftp> open node_A
ftp> get
(remote file)
/home/opt/advant/ES/proj/project_adm/savedirs/file
(local file)
/home/opt/advant/ES/proj/project_adm/savedirs/file
ftp> close
10. Unpack the packed files of the project copy in the destination workstation. Give the project
subdirectory project_release the name of the project that has been created and saved on the
destination workstation.
–
tar -xvf file project_release
11. Restore the project copy on the destination workstation with the user activities as
described in Section 5.6.1.4, Restoring a Saved Project Release within a Station.
5.7.3 Copying a Project to another Disconnected AdvaBuild Station
A project can be copied to another workstation by transferring the project data via a tape to this
workstation. The two main steps are
3BUR001 835R0001 REV C
•
Save project data to tape
•
Restore project data from tape
5-47
5.7.4 Copying Project Subtree to another Project in same AdvaBuild Station
A subtree of a project is copied to another project by using the Import Function of the STB,
Figure 5-18.
Workstation 1
Project 1
Instance
Data
(DB,Files)
Project 2
Library
Data
(DB,Files)
Instance
Data
(DB,Files)
Library
Data
(DB,Files)
COPY SUBTREE
Figure 5-18. Copying a Project Subtree to another project within the AdvaBuild Station
Procedure
1.
Log in to project to which subtree shall be copied as config user.
2.
Choose Import from the File menu.
This displays the Import Dialog Box, Figure 5-19.
5-48
3.
Select the project from which a subtree shall be copied.
4.
Select the top object of the subtree to be copied.
5.
Fill in the object to which the subtree shall be assigned.
6.
Modify object id’s either in substitute or mask mode.
7.
Click on Apply or OK.
3BUR001 835R0001 REV C
Section 5.7.4 Copying Project Subtree to another Project in same AdvaBuild Station
Figure 5-19. Import Dialog Box
3BUR001 835R0001 REV C
5-49
5.7.5 Copying Project Subtree to Project in different AdvaBuild Station
A project subtree can be copied to another workstation by creating a new project and copying
the subtree to the new project. This project is used as transfer project and is saved and
transferred via ftp to the workstation that shall be the destination for the copied subtree. The
saved transfer project with the subtree copy is restored at the destination workstation. The
subtree can be copied at the destination workstation from the transfer project to the final
destination project.
Overview
The subtree is copied to a new created project on the workstation of the source project. The new
project (transfer project) with the subtree-copy is saved. The saved files are packed and the
packed files are transferred to the destination workstation via ftp.
A new project is created at the destination workstation, with the same name, release number and
size as the transfer project with the subtree copy. The new created project at the destination
The save path of the saved project in the save directory /savedirs is deleted. The packed files of
the transfer project are saved on the save directory of the new created project in the destination
workstation.
The transfer project with the subtree copy is restored at the destination workstation. The subtree
is copied from the restored transfer project to the destination project.
5-50
3BUR001 835R0001 REV C
Section 5.7.5 Copying Project Subtree to Project in different AdvaBuild Station
Workstation A
Project 1
Instance
Data
(DB,Files)
Project X
Library
Data
(DB,Files)
Instance
Data
(DB,Files)
Library
Data
(DB,Files)
COPY SUBTREE
Project X
Backup Area
tar
SAVE
Project X
Backup Area
savedirs
ftp
Workstation B
Project 2
Instance
Data
(DB,Files)
Project X
Library
Data
(DB,Files)
Instance
Data
(DB,Files)
COPY SUBTREE
Project X
Backup Area
Library
Data
(DB,Files)
RESTORE
Project X
tar
Backup Area
savedirs
Figure 5-20. Copying a Project Subtree to a Project in another AdvaBuild Station on the Network
Procedure
Refer to the applicable procedures in Section 5.7.4, Copying Project Subtree to another Project
in same AdvaBuild Station and Section 5.7.2, Copying a Project to another AdvaBuild Station
in the Network.
3BUR001 835R0001 REV C
5-51
5.7.6 Copying a Project Subtree to another Disconnected AdvaBuild Station
A project subtree can be copied to another workstation by creating a new project and copying
the subtree to the new project. This project is used as transfer project and is saved and
transferred via a tape to the workstation that shall be the destination for the copied subtree. The
saved transfer project with the subtree copy is restored at the destination workstation. The
subtree can be copied at the destination workstation from the transfer project to the final
destination project.
Overview
The subtree is copied to a new created project on the workstation of the source project. The new
project (transfer project) with the subtree-copy is saved and the saved files of the transfer
project are transferred to a tape.
A new project is created at the destination workstation, with the same name, release number and
size as the transfer project with the subtree copy. The new created project at the destination
The save path of the saved project in the save directory /savedirs is deleted. The content of the
tape is stored to the save directory of the new created project in the destination workstation.
The transfer project with the subtree copy is restored at the destination workstation. The subtree
is copied from the restored transfer project to the destination project.
5-52
3BUR001 835R0001 REV C
Section 5.7.6 Copying a Project Subtree to another Disconnected AdvaBuild Station
Workstation A
Project 1
Instance
Data
(DB,Files)
Project X
Library
Data
(DB,Files)
Instance
Data
(DB,Files)
COPY SUBTREE
Library
Data
(DB,Files)
SAVE
Project X
Backup Area
savedirs
DAT Unit
Workstation B
Project 2
Instance
Data
(DB,Files)
Project X
Library
Data
(DB,Files)
Instance
Data
(DB,Files)
COPY SUBTREE
Library
Data
(DB,Files)
RESTORE
Project X
Backup Area
savedirs
Figure 5-21. Copying a project Subtree to another AdvaBuild Station Not on the Network
Procedure
Refer to the applicable procedures in Section 5.7.4, Copying Project Subtree to another Project
in same AdvaBuild Station and Section 5.7.3, Copying a Project to another Disconnected
AdvaBuild Station.
3BUR001 835R0001 REV C
5-53
5.8 AdvaBuild Save and Restore of Private Data
5.8.1 Saving Private Data on Tape
Private data are stored in directory /home/user. The following describes how to save these data
on a tape.
1.
Log in as the user who is owner of the files in directory /home/user.
(user = username)
2.
Change to the directory where the private data are stored.
cd /home
3.
Insert a tape that is new or can be overwritten. Check that the tape is not write protected
and rewind the tape with the command:
mt rew
4.
Save the private data on tape by entering the command:
tar -cvf /dev/rmt/0mn user
5.
If you want to create a table of contents file use the commands:
mt rew
tar tvf /dev/rmt/0mn > user/content_user
6.
If you want to append the table of contents file to the tape use the commands:
mt rew
tar rvf /dev/rmt/0mn user/content_user
5.8.2 Restoring Private Data from Tape
The following describes how to restore private data that have been saved on a tape.
1.
Log in as the user whose private data shall be restored in the directory /home/user.
(user = username)
2.
Change to the directory where the private data shall be restored.
cd /home
3.
Load the data from the tape (standing in the path /home)
mt rew
tar xvf /dev/rmt/0mn user
4.
If you want to create a table of contents file use the commands:
mt rew
tar tvf /dev/rmt/0mn > user/content_user
5-54
3BUR001 835R0001 REV C
Section 5.9 AdvaInform Application Backup/Restore
5.9 AdvaInform Application Backup/Restore
5.9.1 History Data
5.9.1.1 Saving History Data
To backup your History data, insert a blank tape into the tape drive and run hsBAR by entering
the following command:
$HS_HOME/bin/hsBAR -m b -s
For more information on using hsBAR, refer to the AdvaInform History User’s Guide.
5.9.1.2 Restoring History Data
To restore your History data, do the following:
1.
Shutdown the AdvaCommand software by typing <Ctrl-D> and entering quit in the
dialog.
2.
Select the Suspend button on the AdvaCommand Auto Startup Sequence window.
3.
Select Yes next to Would you like to start a HPterm window and login as operator.
4.
Insert the tape with the saved History files into tape drive.
5.
Enter: $HS_HOME/bin/hsBAR -m r
5.9.2 Reports Data
5.9.2.1 Saving Reports Data
To save your Reports data, do the following:
1.
Make sure that all application files you want to move to the upgraded machine are placed
under the directory tree /home/opt/advant/Reports, including Report output files.
2.
To export the Reports Oracle Data and the ABB Connect location table, and archive the
results to tape:
a.
Label a new DAT tape “Report Backup Tape”
b.
Insert the tape into the drive:
c.
As root, run the following commands from a terminal window:
/opt/advant/Reports/bin/repBU
tar cv /var/opt/advant/tmp/reportsBackup.tar
3BUR001 835R0001 REV C
5-55
d.
As operator, enter:
cd /var/opt/advant/tmp
exp userid=gtw_system/manager tables=$LOC\$$ file=gtwloc.exp log=gtwexp.out
Information about the exports will scroll on the screen. When the export is complete
you should see the line:
Export terminated without warnings
tar rv gtwloc.exp
5.9.2.2 Restoring Reports Data
Restore the Report Template Files and Report Output Files by doing the following:
1.
Insert the DAT tape labeled “Report Backup Tape” into the drive
2.
As operator, run the following commands from a terminal window:
tar xv
3.
When the tar command is complete, remove the tape.
4.
As root, enter:
/opt/advant/Reports/bin/repRest
Information will scroll by as this restore script runs.
5.
As operator, run the following command from a terminal window to import the
location table:
imp gtw_system/manager ignore=y tables=* file=/var/opt/advant/tmp/gtwloc.exp
Information about the import will scroll on the screen. When the import is complete you
should see the message:
Import terminated without or without warnings
5-56
3BUR001 835R0001 REV C
Section A.1 X-Windowing into an Information Management Station
Appendix A X-Windowing
A.1 X-Windowing into an Information Management Station
If an IMS has the X server running and is connected to the Plant Network, you can access the
IMS from an Operator Station:
1.
From an HPTerm window prompt on the Operator Station, enter cd /usr/bin/Xll
2.
Issue an xhost command. The xhost program is used to add and delete hostnames or
user names to the list of those allowed to make connections to the X server. Enter:
xhost +<IMS system name or IMS IP address>
IMS hostname example:
xhost +roc100
IMS IP address example:
xhost +130.110.67.100
NOTE
If you enter a hostname, this hostname must have been previously entered in the
/etc/hosts file, which converts the hostname to an IP address.
3.
Log on to the remote system by using telnet. Telnet is used to communicate with another
host using the TELNET protocol.
a.
Enter:
telnet <IMS system name or IP address>
IMS hostname example:
telnet roc100
IMS IP address example:
telnet 130.110.67.100
b.
Log on to the IMS by entering the user name and password.
NOTE
The default IMS user name and password is imsegr. Contact your IMS
administrator if you need to find out the current user name and password.
c.
Enter hp or hpterm, or press <Return> if hp is displayed as the default.
You should now be on the IMS host station.
3BUR001 835R0001 REV C
A-1
Appendix A X-Windowing
4.
Set the DISPLAY variable by entering a command in the following format:
DISPLAY=<local system name or local IP address>:0.0
Local hostname example:
DISPLAY=roc105:0.0
Local IP address example:
DISPLAY=130.110.67.105:0.0
NOTE
The local hostname or IP address is for the station that you are currently on.
5.
Export the DISPLAY variable to all shells. Enter:
export DISPLAY
6.
Enter the IMS menu program with the following command:
IMSmenu
A new IMS Menu window will be displayed. The HP terminal window in which you have
been working, can be minimized, but do not close it or your session with the IMS host will
be broken.
NOTE
The IMS Menu window can also be minimized. If it is minimized, it will still use
resources on both the host and local systems.
A.1.1 Closing the IMS Menu Session
To close the IMS Menu window:
1.
Choose Exit from the File menu on the IMS menu bar.
2.
To end your telnet session with the IMS host, enter exit in the HPTerm window that
was used to telnet to the IMS host. This action will disconnect you from the IMS host.
3.
Close the HPTerm window by clicking on the box in the upper left corner of the HPTerm
window and then choosing Close from the window menu.
A.2 X-Windowing into an Engineering Station
If an Engineering Station has the X server running and is connected to the Plant Network,
you can access the Engineering Station from an Operator Station. To X-window into the
Structure Builder from an Operator Station, follow the procedures described above in Section
A.1, X-Windowing into an Information Management Station with the following variations:
A-2
•
In steps 2 and 3a, enter the system name or IP address for the Engineering Station rather
than the IMS.
•
In step 3b, log in to the Engineering Station using the appropriate user name and password.
•
In step 6, enter stb& to enter the Structure Builder program.
3BUR001 835R0001 REV C
Section B.1 Function Key Configuration
Appendix B Function Key Configuration
B.1 Function Key Configuration
B.1.1 Display Types
There are four groups of standard Operator Station displays. They are:
•
MAIN MENU
•
HIERARCHY
•
TCL/BATCH
•
LADDERLOGIC
Table B-1 is a list of the display types listed by group that are supported by the configurable
function keys feature.
Table B-1. Display Types Supported by Configurable Function Keys Feature
MAIN MENU
HIERARCHY
TCL/BATCH
LADDERLOGIC
DISPLAYREMOVER
AREAALARM
BATCHDETAIL
COUNTERDISPLAY
ENVIRONMENTALARM
AREAGRAPHIC
BATCH_CUSTOM
FILEDISPLAY
INSTALLER
AREASTATUS
CONTROLRECIPEDETAIL IOPOINTDISPLAY
LOGGERCONTROL
GROUPALARM
EDITB_EQUIP
REGISTERDISPLAY
LOGINPAGE
GROUPGRAPHIC
EDITB_RECIPE
SEGMENTDISPLAY
LOOPDETAIL
GROUPSTATUS
EDITB_SCHED
SEQUENCERDISPLAY
LOOPFCM
GROUPTREND
EQUIPOVERVIEW
TIMERDISPLAY
OSPREFORMANCE
RECIPEDETAIL
OVERVIEW
SEQUENCEDEBUG
SYSTEMSTATUS
SEQUENCEDETAIL
XCONFIG
SFC
TCLCATALOG
TCLRECIPE
UNITDETAIL
UNITGRAPHIC
3BUR001 835R0001 REV C
B-1
Table B-1. Display Types Supported by Configurable Function Keys Feature (Continued)
MAIN MENU
HIERARCHY
TCL/BATCH
LADDERLOGIC
UNITMESSAGE
UNITOVERVIEW
UNITSUPERVISOR
B.1.2 The default.Function_Keys File Listing
The default.Function_Keys file is listed below:
#
#
Area displays
#
AREASTATUS;F1;V; ;BASE;0;AREAALARM;CURR_AREA
AREASTATUS;F2;V; ;BASE;0;AREASTATUS;CURR_AREA
AREASTATUS;F3;V; ;BASE;0;AREAGRAPHIC;CURR_AREA
AREASTATUS;F5;V; ;BASE;0;AREASTATUS;PREV_AREA
AREASTATUS;F6;V; ;BASE;0;GROUPSTATUS;CURR_AREA;TOP_GROUP
AREASTATUS;F7;V; ;BASE;0;GROUPSTATUS;CURR_AREA;MID_GROUP
AREASTATUS;F8;V; ;BASE;0;GROUPSTATUS;CURR_AREA;BOT_GROUP
AREASTATUS;F10;V; ;BASE;0;AREASTATUS;NEXT_AREA
AREAALARM;F1;V; ;BASE;0;AREAALARM;CURR_AREA
AREAALARM;F2;V; ;BASE;0;AREASTATUS;CURR_AREA
AREAALARM;F3;V; ;BASE;0;AREAGRAPHIC;CURR_AREA
AREAALARM;F5;V; ;BASE;0;AREAALARM;PREV_AREA
AREAALARM;F6;V; ;BASE;0;GROUPALARM;CURR_AREA;TOP_GROUP
AREAALARM;F7;V; ;BASE;0;GROUPALARM;CURR_AREA;MID_GROUP
AREAALARM;F8;V; ;BASE;0;GROUPALARM;CURR_AREA;BOT_GROUP
AREAALARM;F10;V; ;BASE;0;AREAALARM;NEXT_AREA
AREAGRAPHIC;F1;V; ;BASE;0;AREAALARM;CURR_AREA
AREAGRAPHIC;F2;V; ;BASE;0;AREASTATUS;CURR_AREA
AREAGRAPHIC;F3;V; ;BASE;0;AREAGRAPHIC;CURR_AREA
AREAGRAPHIC;F5;V; ;BASE;0;AREAGRAPHIC;PREV_AREA
AREAGRAPHIC;F6;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;TOP_GROUP
AREAGRAPHIC;F7;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;MID_GROUP
AREAGRAPHIC;F8;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;BOT_GROUP
AREAGRAPHIC;F10;V; ;BASE;0;AREAGRAPHIC;NEXT_AREA
#
#
Group displays
#
GROUPSTATUS;F1;V; ;BASE;0;GROUPALARM;CURR_AREA;CURR_GROUP
GROUPSTATUS;F2;V; ;BASE;0;GROUPSTATUS;CURR_AREA;CURR_GROUP
GROUPSTATUS;F3;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;CURR_GROUP
GROUPSTATUS;F4;V; ;BASE;0;GROUPTREND;CURR_AREA;CURR_GROUP
GROUPSTATUS;F5;V; ;BASE;0;GROUPSTATUS;CURR_AREA;PREV_GROUP
B-2
3BUR001 835R0001 REV C
Section B.1.2 The default.Function_Keys File Listing
GROUPSTATUS;F6;V; ;BASE;0;AREAALARM;CURR_AREA
GROUPSTATUS;F7;V; ;BASE;0;AREASTATUS;CURR_AREA
GROUPSTATUS;F8;V; ;BASE;0;AREAGRAPHIC;CURR_AREA
GROUPSTATUS;F10;V; ;BASE;0;GROUPSTATUS;CURR_AREA;NEXT_GROUP
GROUPALARM;F1;V; ;BASE;0;GROUPALARM;CURR_AREA;CURR_GROUP
GROUPALARM;F2;V; ;BASE;0;GROUPSTATUS;CURR_AREA;CURR_GROUP
GROUPALARM;F3;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;CURR_GROUP
GROUPALARM;F4;V; ;BASE;0;GROUPTREND;CURR_AREA;CURR_GROUP
GROUPALARM;F5;V; ;BASE;0;GROUPALARM;CURR_AREA;PREV_GROUP
GROUPALARM;F6;V; ;BASE;0;AREAALARM;CURR_AREA
GROUPALARM;F7;V; ;BASE;0;AREASTATUS;CURR_AREA
GROUPALARM;F8;V; ;BASE;0;AREAGRAPHIC;CURR_AREA
GROUPALARM;F10;V; ;BASE;0;GROUPALARM;CURR_AREA;NEXT_GROUP
GROUPGRAPHIC;F1;V; ;BASE;0;GROUPALARM;CURR_AREA;CURR_GROUP
GROUPGRAPHIC;F2;V; ;BASE;0;GROUPSTATUS;CURR_AREA;CURR_GROUP
GROUPGRAPHIC;F3;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;CURR_GROUP
GROUPGRAPHIC;F4;V; ;BASE;0;GROUPTREND;CURR_AREA;CURR_GROUP
GROUPGRAPHIC;F5;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;PREV_GROUP
GROUPGRAPHIC;F6;V; ;BASE;0;AREAALARM;CURR_AREA
GROUPGRAPHIC;F7;V; ;BASE;0;AREASTATUS;CURR_AREA
GROUPGRAPHIC;F8;V; ;BASE;0;AREAGRAPHIC;CURR_AREA
GROUPGRAPHIC;F10;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;NEXT_GROUP
GROUPTREND;F1;V; ;BASE;0;GROUPALARM;CURR_AREA;CURR_GROUP
GROUPTREND;F2;V; ;BASE;0;GROUPSTATUS;CURR_AREA;CURR_GROUP
GROUPTREND;F3;V; ;BASE;0;GROUPGRAPHIC;CURR_AREA;CURR_GROUP
GROUPTREND;F4;V; ;BASE;0;GROUPTREND;CURR_AREA;CURR_GROUP
GROUPTREND;F5;V; ;BASE;0;GROUPTREND;CURR_AREA;PREV_GROUP
GROUPTREND;F6;V; ;BASE;0;AREAALARM;CURR_AREA
GROUPTREND;F7;V; ;BASE;0;AREASTATUS;CURR_AREA
GROUPTREND;F8;V; ;BASE;0;AREAGRAPHIC;CURR_AREA
GROUPTREND;F10;V; ;BASE;0;GROUPTREND;CURR_AREA;NEXT_GROUP
#
#
Loop displays
#
LOOPDETAIL;F9;V; ;BASE;0;LOOPFCM;CURR_LOOP
LOOPFCM;F9;V; ;BASE;0;LOOPDETAIL;CURR_LOOP
#
#
Overview displays
#
OVERVIEW;F5;V; ;BASE;0;OVERVIEW;PREV_OVER
OVERVIEW;F10;V; ;BASE;0;OVERVIEW;NEXT_OVER
#
#
TCL displays
#
Unit displays
#
UNITMESSAGE;F1;V; ;BASE;0;UNITMESSAGE;CURR_UNIT
UNITMESSAGE;F2;V; ;BASE;0;UNITDETAIL;CURR_UNIT
UNITMESSAGE;F3;V; ;BASE;0;UNITGRAPHIC;CURR_UNIT
UNITMESSAGE;F4;V; ;BASE;0;RECIPEDETAIL;CURR_UNIT
3BUR001 835R0001 REV C
B-3
UNITMESSAGE;F5;V; ;BASE;0;UNITMESSAGE;PREV_UNIT
UNITMESSAGE;F9;V; ;BASE;0;UNITOVERVIEW
UNITMESSAGE;F10;V; ;BASE;0;UNITMESSAGE;NEXT_UNIT
UNITDETAIL;F1;V; ;BASE;0;UNITMESSAGE;CURR_UNIT
UNITDETAIL;F2;V; ;BASE;0;UNITDETAIL;CURR_UNIT
UNITDETAIL;F3;V; ;BASE;0;UNITGRAPHIC;CURR_UNIT
UNITDETAIL;F4;V; ;BASE;0;RECIPEDETAIL;CURR_UNIT
UNITDETAIL;F5;V; ;BASE;0;UNITDETAIL;PREV_UNIT
UNITDETAIL;F9;V; ;BASE;0;UNITOVERVIEW
UNITDETAIL;F10;V; ;BASE;0;UNITDETAIL;NEXT_UNIT
UNITGRAPHIC;F1;V; ;BASE;0;UNITMESSAGE;CURR_UNIT
UNITGRAPHIC;F2;V; ;BASE;0;UNITDETAIL;CURR_UNIT
UNITGRAPHIC;F3;V; ;BASE;0;UNITGRAPHIC;CURR_UNIT
UNITGRAPHIC;F4;V; ;BASE;0;RECIPEDETAIL;CURR_UNIT
UNITGRAPHIC;F5;V; ;BASE;0;UNITGRAPHIC;PREV_UNIT
UNITGRAPHIC;F9;V; ;BASE;0;UNITOVERVIEW
UNITGRAPHIC;F10;V; ;BASE;0;UNITGRAPHIC;NEXT_UNIT
RECIPEDETAIL;F1;V; ;BASE;0;UNITMESSAGE;CURR_UNIT
RECIPEDETAIL;F2;V; ;BASE;0;UNITDETAIL;CURR_UNIT
RECIPEDETAIL;F3;V; ;BASE;0;UNITGRAPHIC;CURR_UNIT
RECIPEDETAIL;F4;V; ;BASE;0;RECIPEDETAIL;CURR_UNIT
RECIPEDETAIL;F5;V; ;BASE;0;RECIPEDETAIL;PREV_UNIT
RECIPEDETAIL;F9;V; ;BASE;0;UNITOVERVIEW
RECIPEDETAIL;F10;V; ;BASE;0;RECIPEDETAIL;NEXT_UNIT
#
#
Sequence displays
#
SEQUENCEDEBUG;F1;V; ;BASE;0;UNITMESSAGE;CURR_UNIT
SEQUENCEDEBUG;F2;V; ;BASE;0;UNITDETAIL;CURR_UNIT
SEQUENCEDEBUG;F3;V; ;BASE;0;UNITGRAPHIC;CURR_UNIT
SEQUENCEDEBUG;F4;V; ;BASE;0;RECIPEDETAIL;CURR_UNIT
SEQUENCEDEBUG;F6;V; ;BASE;0;SEQUENCEDEBUG;CURR_UNIT;CURR_SEQ
SEQUENCEDEBUG;F7;V; ;BASE;0;SEQUENCEDETAIL;CURR_UNIT;CURR_SEQ
SEQUENCEDEBUG;F8;V; ;BASE;0;SFC;CURR_UNIT;CURR_SEQ
SEQUENCEDEBUG;F9;V; ;BASE;0;UNITOVERVIEW
SEQUENCEDETAIL;F1;V; ;BASE;0;UNITMESSAGE;CURR_UNIT
SEQUENCEDETAIL;F2;V; ;BASE;0;UNITDETAIL;CURR_UNIT
SEQUENCEDETAIL;F3;V; ;BASE;0;UNITGRAPHIC;CURR_UNIT
SEQUENCEDETAIL;F4;V; ;BASE;0;RECIPEDETAIL;CURR_UNIT
SEQUENCEDETAIL;F6;V; ;BASE;0;SEQUENCEDEBUG;CURR_UNIT;CURR_SEQ
SEQUENCEDETAIL;F7;V; ;BASE;0;SEQUENCEDETAIL;CURR_UNIT;CURR_SEQ
SEQUENCEDETAIL;F8;V; ;BASE;0;SFC;CURR_UNIT;CURR_SEQ
SEQUENCEDETAIL;F9;V; ;BASE;0;UNITOVERVIEW
SFC;F1;V; ;BASE;0;UNITMESSAGE;CURR_UNIT
SFC;F2;V; ;BASE;0;UNITDETAIL;CURR_UNIT
SFC;F3;V; ;BASE;0;UNITGRAPHIC;CURR_UNIT
SFC;F4;V; ;BASE;0;RECIPEDETAIL;CURR_UNIT
SFC;F6;V; ;BASE;0;SEQUENCEDEBUG;CURR_UNIT;CURR_SEQ
SFC;F7;V; ;BASE;0;SEQUENCEDETAIL;CURR_UNIT;CURR_SEQ
B-4
3BUR001 835R0001 REV C
Section B.1.2 The default.Function_Keys File Listing
SFC;F8;V; ;BASE;0;SFC;CURR_UNIT;CURR_SEQ
SFC;F9;V; ;BASE;0;UNITOVERVIEW
#
#
Batch displays
#
BATCHDETAIL;F1;V; ;BASE;0;BATCHDETAIL;CURR_UNIT
BATCHDETAIL;F2;V; ;BASE;0;UNITSUPERVISOR;CURR_UNIT
BATCHDETAIL;F3;V; ;BASE;0;UNITDETAIL;CURR_UNIT
BATCHDETAIL;F4;V; ;BASE;0;CONTRECIPEDETAIL;CURR_UNIT
BATCHDETAIL;F5;V; ;BASE;0;BATCHDETAIL;PREV_UNIT
BATCHDETAIL;F9;V; ;BASE;0;EQUIPOVERVIEW
BATCHDETAIL;F10;V; ;BASE;0;BATCHDETAIL;NEXT_UNIT
UNITSUPERVISOR;F1;V; ;BASE;0;BATCHDETAIL;CURR_UNIT
UNITSUPERVISOR;F2;V; ;BASE;0;UNITSUPERVISOR;CURR_UNIT
UNITSUPERVISOR;F3;V; ;BASE;0;UNITDETAIL;CURR_UNIT
UNITSUPERVISOR;F4;V; ;BASE;0;CONTRECIPEDETAIL;CURR_UNIT
UNITSUPERVISOR;F5;V; ;BASE;0;UNITSUPERVISOR;PREV_UNIT
UNITSUPERVISOR;F9;V; ;BASE;0;EQUIPOVERVIEW
UNITSUPERVISOR;F10;V; ;BASE;0;UNITSUPERVISOR;NEXT_UNIT
CONTROLRECIPEDETAIL;F1;V; ;BASE;0;BATCHDETAIL;CURR_UNIT
CONTROLRECIPEDETAIL;F2;V; ;BASE;0;UNITSUPERVISOR;CURR_UNIT
CONTROLRECIPEDETAIL;F3;V; ;BASE;0;UNITDETAIL;CURR_UNIT
CONTROLRECIPEDETAIL;F4;V; ;BASE;0;CONTRECIPEDETAIL;CURR_UNIT
CONTROLRECIPEDETAIL;F5;V; ;BASE;0;CONTRECIPEDETAIL;PREV_UNIT
CONTROLRECIPEDETAIL;F9;V; ;BASE;0;EQUIPOVERVIEW
CONTROLRECIPEDETAIL;F10;V; ;BASE;0;CONTRECIPEDETAIL;NEXT_UNIT
#
#
LadderLogic displays
#
COUNTERDISPLAY;F1;V; ;BASE;0;COUNTERDISPLAY;CURR_LL_DEV
COUNTERDISPLAY;F2;V; ;BASE;0;IOPOINTDISPLAY;CURR_LL_DEV
COUNTERDISPLAY;F3;V; ;BASE;0;REGISTERDISPLAY;CURR_LL_DEV
COUNTERDISPLAY;F4;V; ;BASE;0;SEGMENTDISPLAY;CURR_LL_DEV
COUNTERDISPLAY;F6;V; ;BASE;0;TIMERDISPLAY;CURR_LL_DEV
IOPOINTDISPLAY;F1;V; ;BASE;0;COUNTERDISPLAY;CURR_LL_DEV
IOPOINTDISPLAY;F2;V; ;BASE;0;IOPOINTDISPLAY;CURR_LL_DEV
IOPOINTDISPLAY;F3;V; ;BASE;0;REGISTERDISPLAY;CURR_LL_DEV
IOPOINTDISPLAY;F4;V; ;BASE;0;SEGMENTDISPLAY;CURR_LL_DEV
IOPOINTDISPLAY;F6;V; ;BASE;0;TIMERDISPLAY;CURR_LL_DEV
REGISTERDISPLAY;F1;V; ;BASE;0;COUNTERDISPLAY;CURR_LL_DEV
REGISTERDISPLAY;F2;V; ;BASE;0;IOPOINTDISPLAY;CURR_LL_DEV
REGISTERDISPLAY;F3;V; ;BASE;0;REGISTERDISPLAY;CURR_LL_DEV
REGISTERDISPLAY;F4;V; ;BASE;0;SEGMENTDISPLAY;CURR_LL_DEV
REGISTERDISPLAY;F6;V; ;BASE;0;TIMERDISPLAY;CURR_LL_DEV
SEGMENTDISPLAY;F1;V; ;BASE;0;COUNTERDISPLAY;CURR_LL_DEV
SEGMENTDISPLAY;F2;V; ;BASE;0;IOPOINTDISPLAY;CURR_LL_DEV
SEGMENTDISPLAY;F3;V; ;BASE;0;REGISTERDISPLAY;CURR_LL_DEV
SEGMENTDISPLAY;F4;V; ;BASE;0;SEGMENTDISPLAY;CURR_LL_DEV
SEGMENTDISPLAY;F6;V; ;BASE;0;TIMERDISPLAY;CURR_LL_DEV
3BUR001 835R0001 REV C
B-5
TIMERDISPLAY;F1;V;
TIMERDISPLAY;F2;V;
TIMERDISPLAY;F3;V;
TIMERDISPLAY;F4;V;
TIMERDISPLAY;F6;V;
B-6
;BASE;0;COUNTERDISPLAY;CURR_LL_DEV
;BASE;0;IOPOINTDISPLAY;CURR_LL_DEV
;BASE;0;REGISTERDISPLAY;CURR_LL_DEV
;BASE;0;SEGMENTDISPLAY;CURR_LL_DEV
;BASE;0;TIMERDISPLAY;CURR_LL_DEV
3BUR001 835R0001 REV C
Section C.1 General
Appendix C HP-UX 10.20 Impact
C.1 General
The Advant Station employs the HP-UX version 10.20 operating system and makes use of the
following features:
•
new layout of file system
•
I/O convergence
•
logical volume support
These features are described in the sections that follow.
C.2 New Layout of the File System
Previous versions of the HP-UX operating system contained file system layouts which did not
conform to standards. The new file system conforms to SVR4 and OSF/1 standards. As such,
nearly every file is located in a new path.
Advant software complies with the new file system layout. As such, directory names and file
locations have changed.
The following are general rules for the new layout:
3BUR001 835R0001 REV C
•
The shareable portion of the OS resides beneath /usr and /sbin. Only the operating system
may install files into these hierarchies.
•
Applications reside in subdirectories beneath /opt. This is the recommended install point
for applications.
•
Directories /usr, /sbin, and the application subdirectories of /opt are shareable among
networked hosts. These hierarchies must not contain host-specific information. All
host-specific configuration data, temporary files, log files, and other files inappropriate for
sharing among hosts must reside in private directories on the file system. The private
directories include /etc, /var, /tmp, /stand, and /home.
•
The /etc directory is used exclusively for host-specific configuration data essential to the
correct operation of the system. This directory no longer holds executable commands.
•
The /var hierarchy contains host-specific files created during execution of the system that
are not essential configuration information. Examples of files that reside here are log files,
temporary files, and printer spool files.
•
The /home directory is the root for all users’ home directories.
•
The /export directory is the root for sharable, networked file systems, such as NFS
exported directories.
C-1
/dev
/dev is used for device files. The contents and meaning of /dev has not changed. Nothing should
be installed in /dev. Instead, configuration files should create node-specific device files.
/etc
The /etc hierarchy contains host-specific system and application configuration files important to
the correct operation of the system. Files located here are usually a fixed size and do not grow.
By contrast, the /var hierarchy holds files that are dynamic in length or are less critical to system
execution, such as log files. In general, /etc holds essential information that must be preserved in
order for the system to function correctly, while /var holds information generated by the system
that may be disposed of when it is no longer of interest. Some customer sites may choose to
make automatic backups of the /etc hierarchy, but not of /var.
There will be subdirectories under /etc for some systems; for example /etc/mail and /etc/uucp
for the mail system and uucp respectively.
The /etc directory itself is used ONLY for system configuration files. /etc no longer contains
commands, rc scripts, log files (with the exception of a few critical log files), or other files not
related to system configuration. Most commands have moved to /usr/sbin. rc scripts now reside
in /sbin/init.d and follow the new system startup and shutdown paradigm. Log files and other
miscellaneous files not related to system configuration are now in /var.
/etc/opt
Applications will store application-specific, host-specific configuration data under
/etc/opt/<application>.
/etc/rc.config.d
This directory contains configuration data files for startup and shutdown scripts.
/export
The directory is used to support diskless file sharing. Servers export root directory hierarchies
for networked clients.
/home
User directories will be created and managed under /home instead of /users. Nothing should be
installed in /home. This is a portion of the file system that is allowed to grow.
/lost+found
/lost+found contains files located by fsck(1m).
C-2
3BUR001 835R0001 REV C
Section C.2 New Layout of the File System
/mnt
Reserved name for mount points for local file systems. This is not an install location (that is,
nothing should be directly installed here from HP update media). /mnt can be used as a mount
point directory, or a directory containing multiple mount points.
/net
Reserved name for mount points for remote file systems.
/opt
The root directory for optional applications. /opt is not a sharing point, but rather, its
subdirectories are sharing points. This allows one to mount only those applications that make
sense for a given machine or release, rather than mounting all applications available on a server.
No files should be delivered into /opt, but rather into subdirectories of /opt, as described below.
/opt/<application>
The shareable portion of each optional application resides in a hierarchy beneath a single
subdirectory of /opt. A uniform application structure is recommended, which consists of the
following standard set of directories under /opt/<application>: bin, lib, man, help, lbin and
newconfig for default configuration info.
/sbin
/sbin contains the commands and scripts essential to boot and shutdown of a system. /sbin
contains the commands required to bring the system into a state in which the /usr file system can
be mounted and the boot process continued. /sbin also contains commands needed to fix
filesystem mounting problems.
Commands in /sbin must not depend on any file systems that may not be mounted at the time the
command must execute, including the /usr, /var, and /opt file systems. Since shared libraries
reside beneath /usr, commands in /sbin are statically linked (that is, built with archived
libraries). Commands in /sbin must not execute any commands from the /usr filesystem; only
other /sbin executables may be referenced. If a command referenced by an /sbin command is
replicated between /sbin and either /usr/bin or /usr/sbin, then the path to the command must
refer to the /sbin version.
Some commands in /sbin are duplicates of, or the target of symbolic links from, other
commands in /usr/bin and /usr/sbin. For example, the ls command exists in both /sbin and
/usr/bin. If a command in /sbin is duplicated in either /usr/bin or /usr/sbin, the duplicate exists to
take advantage of shared libraries for most executions of that command, or to provide full
functionality if the /sbin version does not.
Some commands in /sbin do not offer the full functionality provided by their /usr/bin or
/usr/sbin counterparts. For example, some NLS functionality that requires shared libraries is not
present in the /sbin versions of certain commands. For this reason, use of the /usr/bin or
/usr/sbin versions of replicated commands is preferred, when possible. When constructing shell
PATH variables that contain a /sbin component, /sbin should appear after /usr/bin and/or
/usr/sbin in the path.
3BUR001 835R0001 REV C
C-3
/sbin/init.d and /sbin/rc#.d
/sbin/init.d contains all rc scripts used to startup and shutdown various subsystems.
/sbin/rc#.d contains ordered symbolic links to rc scripts in /sbin/init.d that are executed when
changing run levels.
/stand
/stand is for system-specific kernel configuration and binary files. The files are typically needed
at boot time to bring up a system. This directory is not an install point.
/tmp
/tmp is for system-generated temporary files. The contents of /tmp are usually NOT preserved
across a system reboot. The choice of whether or not /tmp is cleaned up at boot time is left to the
customer.
The /tmp directory is private. Since many sites will delete files from /tmp at boot time, files that
must be preserved should not be placed in the /tmp directory. Application working files should
go in /var/tmp or /var/opt/<application>. Files generated by the OS that must be preserved
across reboots should go into the /var/tmp directory.
/usr
/usr contains the bulk of the operating system, including commands, libraries and
documentation. The /usr file system contains only shareable operating system files, such as
executables and ASCII documentation. Multiple systems of compatible architectures should be
able to access the same /usr directories. /usr may be mounted as read-only by diskless clients,
and thus may not be writable by clients.
The allowed subdirectories in /usr are defined below; no additional subdirectories should be
created. Any 9.X applications that resided in other subdirectories in /usr have moved beneath the
/opt hierarchy.
/usr/bin
/usr/bin is used for common utilities and applications.
/usr/ccs
The minimal C compiler is located here. The functionality is sufficient to build a kernel. The
fully-functional C compiler resides below /opt.
/usr/conf
/usr/conf is a static directory containing the sharable kernel build environment.
/usr/contrib
This directory contains contributed software. The 10.0 layout has no changes to this directory.
C-4
3BUR001 835R0001 REV C
Section C.2 New Layout of the File System
/usr/include
/usr/include contains header files. The 10.0 layout has no changes to this directory.
/usr/lbin
The /usr/lbin directory is intended for backends to commands in the /usr hierarchy. Commands
such as /usr/lib/divpage and /usr/ lib/diff3prog are placed in /usr/lbin. There are some
subdirectories for special systems, such as /usr/lbin/spell and /usr/lbin/uucp.
/usr/lib
/usr/lib holds libraries and machine dependent databases. In 10.0, most files that once resided in
/lib now reside in /usr/lib. There is no /lib directory; code referencing /lib should be changed to
reference the correct path.
/usr/local
/usr/local is for site local files, including binaries, libraries, sources, and documentation. HP will
deliver this directory empty and not install software here.
/usr/newconfig
This directory contains default operating system configuration data files.
Files that once resided in /etc/newconfig now either reside in /usr/newconfig or
/opt/<application>/newconfig. The structure of /usr/newconfig is different than that of
/etc/newconfig; /usr/newconfig contains a directory hierarchy somewhat mirroring that of /.
/usr/old
During an operating system update, this directory is used for host customization. System files
being replaced by files in /usr/newconfig, will be moved here. It is also used to hold old versions
of software for compatibility with a previous release. /usr/old contains a directory hierarchy
somewhat mirroring that of /.
/usr/sbin
The directory /usr/sbin is for system administration related commands. Many of the commands
previously in /etc have moved to this directory.
/usr/share
This hierarchy contains architecture-independent sharable files that can be shared among
various architectures (for example, terminfo files).
/usr/share/dict
This directory contains spell and ispell dictionaries.
3BUR001 835R0001 REV C
C-5
/usr/share/doc
This directory contains HP-UX operating system documentation on various topics that is not
delivered with other parts of the system.
/usr/share/lib
This directory is for miscellaneous sharable files. For example, terminfo files will appear
beneath this directory.
/usr/share/man
This directory is for man pages. Processed man pages (for example, /usr/share/man/cat1.Z/*)
will also be held here.
/usr/tmp
A temporary directory symbolically linked to /var/tmp for backward compatibility. This
directory is not shared with other systems in a diskless cluster.
/var
This directory is for multipurpose log, temporary, transient, variable-sized, and spool files. The
/var directory is extremely “variable” in size, hence the name. In general, any files that an
application or command creates at runtime, and that are not critical to the operation of the
system, should be placed in a directory that resides under /var. For example, /var/adm will
contain log files and other runtime-created files related to system administration. /var will also
contain variable size files like crontabs, and print and mail spooling areas. In general, files
beneath /var are somewhat temporary. System administrators that wish to free up disk space are
likely to search the /var hierarchy for files that can be purged. Some sites may choose not to
make automatic backups of the /var directories. If a product locates important configuration files
here that do not fit under /etc, it is recommended that documentation explicitly reference /var
files to back-up.
/var should not be placed on a small, fixed-size partition. Also, /var is not an install point.
/var/adm
This directory hierarchy is used for common administrative files, logs, and databases. For
example, files generated by syslog, files used by cron, and kernel crash dumps will be kept here
and in subdirectories. Host-specific administration information will also be kept here. /usr/adm
has become /var/adm.
/var/adm/crash
Kernel crash dumps will be located in this directory.
/var/adm/cron
Used for log files maintained by cron, and cron fifos.
C-6
3BUR001 835R0001 REV C
Section C.3 I/O Convergence
/var/adm/sw
Used by SD, the HP OpenView Software Distributor.
/var/adm/syslog
System log files generated by syslog (see syslogd(1M) and syslog(3C)) will go into this
directory.
/var/mail
Directory where incoming mail messages are kept.
/var/news
Electronic bulletin board files used by news(1) will be kept here. Formerly /usr/news.
/var/opt
Application runtime files (for example, logs, status, temporary files) for applications mounted in
/opt will be stored in /var/opt/<application> for each application.
/var/preserve
Files preserved by vi(1) will be stored here. Formerly /usr/preserve.
/var/run
PID files for daemon programs will be stored in /var/run, NOT in /etc.
/var/spool
Host-specific spool files are located here. In general, /usr/spool becomes /var/spool.
/var/tmp
/var/tmp is for user temporary files generated by commands in the /usr hierarchy. Files located
here are preserved between system reboots. Temporary files generated by applications installed
under /opt/<application> will use /var/opt/<application> for temporary files.
/var/uucp
UUCP administration files will reside here.
C.3 I/O Convergence
All device files now follow a single naming convention. All device files follow the SVR4
convention.
3BUR001 835R0001 REV C
C-7
Disk Device Files
The syntax for disk device files is the following:
dev/dsk/c#t#d#
or
dev/rdsk/c#t#d#
where
represents the card instance number for the class of interface card to which the
device is connected. Classes of interface cards include ext_bus, graphics, tty,
lan, and others. The card instance of an interface card is unique for its specific
class. There is no relationship between the instance number and the slot
number of the interface card in the card cage.
c#
The class and instance number can be seen in the first two columns of
/usr/sbin/ioscan -f output. When interpreting a device special file, the only
significant instance number is the card instance (that is, the instance number
for the class of interface to which a device is attached). Thus, in a sample disk
device file /dev/rdsk/c1t4d0, the c1 refers to the card instance, not to an LU
number (as in previous releases).
t#
represents the target address of the device on the interface bus, and can range
from 0 to 7 maximum. Typically t# is the address set with jumpers or dip
switches on the device itself.
d#
represents the device number, and can range from 0 to 7 maximum. On SCSI
devices, d# is the SCSI LUN; on HP-FL and HP-IB, it is the unit number.
Except for multi-function devices, d# is typically d0.
Terminal Device Files
The syntax for terminal device files is the following:
dev/tty#p#
where
tty#
represents the card instance number. The card instance of an interface card is
unique for its specific class. There is no relationship between the instance
number and the slot number of the interface card in the card cage.
The class and instance number can be seen in the first two columns of
/usr/sbin/ioscan -f output. When interpreting a device special file, the only
significant instance number is the card instance (that is, the instance number
for the class of interface to which a device is attached). Thus, in a sample
terminal device file /dev/tty1p0, the tty1 refers to the card instance, not to an
LU number (as in previous releases).
p#
C-8
represents the port number on the card. Single port cards default to port 0.
3BUR001 835R0001 REV C
Section C.4 Logical Volume Support
C.4 Logical Volume Support
Logical volumes are collections of disk space from one or more physical disks. Each collection
(logical volume) appears like a single disk. A logical volume need not utilize all the space
available on a given physical disk. For example, a user may have two physical disks and create
eight logical volumes from those two disks.
Logical volumes automatically manage the partitioning of the physical disks.
Unlike physical disks, the size of a logical volume can be expanded. A user can add a physical
disk to the system and expand the size of one or more logical volumes. The benefit is that
existing data in the logical volume need not be moved or restored.
3BUR001 835R0001 REV C
C-9
C-10
3BUR001 835R0001 REV C
Appendix D Naming Scheme For Patches
Patches use the following naming scheme:
ABB-PXXX_iii(i)jjj
where
P…
Patch
XXX …
Product/Package/Option shortname (see below)
iii(i) …
Release (e.g. 210 or 1443)
jjj …
Serial number of the patch per ABB-PXXX_iii(I)
Product Shortnames
AEH
ES
IMS
OS
Advant Enterprise Historian
Engineering Station
Information Management Station
Operator Station
Package/Option Shortnames
BAS
DIB
DOB
DYB
EDI
FCB
FMS
HSU
MD
MDE
MDO
MDS
MDX
MM
MML
MR
MRE
MRO
MRS
MRX
PDB
TCB
UXB
UPG
TSH
Example:
3BUR001 835R0001 REV C
SYSTEM
Diagram Builder
Document Builder
Display Builder
Electrical Diagram Builder
MOD Function Chart Builder
File Management System
History Unix
MOD (basic shortcut)
MOD executables
MOD On-line Builder
MOD Standard Project
MOD Example Project
MASTER/MOD (basic shortcut)
MASTER/MOD Shared Libraries
MASTER (basic shortcut)
MASTER executables
MASTER On-line Builder
MASTER Standard Project
MASTER Example Project
Plant Documentation Builder
MOD TCL Builder
UXBase
UPGRADE
Typical Solution Handling
ABB-PHSU_230008
P
Patch
HSU
History Unix
D-1
Appendix D Naming Scheme For Patches
230
008
Release Version 2.3/0
Patch Number 008
MOD300 Hawkridge Boot Files, DPL Tasks, or FMSFiles Shortnames
AE
AR
CC
CF
CI
CO
CS
DBMS
DG
HR
OMF
OS
PB
PL or LL
PLC
RG
SSE
TL
Example:
D-2
Alarm Event
AccuRay
Configurable Control Functions (CCF)
Configurator
Computer Interface
Console
Communication Services
Database Management System
Diagnostics
History
OMF Translator
Operating System
Page Builder
Ladder Logic
Programmable Logic Controller
Report Generator
System State Executive
Taylor Control Language
ABB-PTLU_1443123
P
Patch
TLU
Taylor Control Language Unix
144
MOD Release Version 14.4
3123
Patch Number 3123 (i.e., indicates Patch Number 123 tested
against Revision 14.4/3)
3BUR001 835R0001 REV C
Appendix E Native Language Support (NLS) Readme File
#-----------------------------------------------------------------------------#
# $Id: README,v 1.5 1997/11/21 18:50:42 moore Exp $
#
#------------------------------------------------------------------------------
NLS - Native Language Support
-----------------------------
Overview:
All text whether 'static' (Titles, Column Headers, Labels, Prompts,
Error Messages, etc.) or 'dynamic' (States, Modes, Conditions, etc.)
should be displayed in the language environment variable LANG, which
is configured in the file:
/opt/advant/MOD-OS/etc/environment
Currently, we provide Computer (LANG = C, default language),
American (LANG = en_US.iso88591), and German (LANG = de_DE.iso88591).
The Display and Environment Builders do not contain Native Language
Support.
These text strings are stored in message files. At run-time, the
application retrieves the appropriate text strings depending on the
language specified by the LANG variable.
Message Files:
Whenever 'static' or 'dynamic' text is added to a display, the text
string is placed in the appropriate message files. Message files
can be found for English text in:
/etc/opt/advant/MOD-OS/lib/nls/en_US.iso88591
for the German text in:
/etc/opt/advant/MOD-OS/lib/nls/de_DE.iso88591
Mostly, there is a one-to-one correspondence between the message
file and its OS display.
Within the message file, the first column is the message constant,
the second column is the message number and the third is the actual
message text.
3BUR001 835R0001 REV C
E-1
If the message includes data from the code, there are three parameters
that can be specified within the actual message text: %D1 (numeric data),
%D2 (numeric data), and/or %T (text data).
Compiling Message Files:
In order for the Operator Station display routines to pick up the
message files (*.def), they must be in a different file format called
a catalog file (*.cat). The Makefile in the appropriate nls directory
will compile the message files and create a corresponding catalog file
for each message file. You must set the NLS_LANG language variable
for the Makefile to compile your changes correctly.
Example: If you have altered the Russian version of the message file
LoginPage_bsUSOS.def in:
/etc/opt/advant/MOD-OS/lib/nls/ru_RU.iso88595
Set the NLS_LANG language variable to Russian
export NLS_LANG=ru_RU.iso88595
Compile the message file in
/etc/opt/advant/MOD-OS/lib/nls:
make -e
This will create the catalog file LoginPage_bsUSOS.cat in
/etc/opt/advant/MOD-OS/lib/nls/ru_RU.iso88595
Non-English Keyboards:
There are a vast number of language character sets, however we currently
only support the German keyboard and provide limited support for a
Russian keyboard.
Non-English Character sets:
Utilising a non-english character is accomplished by choosing a font
that supports your character set. The German character set is supported
with the fonts used by the Operator Station. The Russian character
set is supported with the following fonts:
cyr8x16
cyr8x19
cyr9x17
cyr6x16
cyr7x17
E-2
cyr14x26
cyr11x19
cyr12x23
3BUR001 835R0001 REV C
Section
To utilize the cyrillic fonts in an Operator Station, you simply alias
the cyrillic fonts to fonts used by the Operator Station. This has been
done within the 'fonts.alias' file found in:
/opt/advant/MOD-NLS/etc/fonts.alias
In order to use this alias file, you must copy it into the directory
'/opt/advant/MOD-OS/lib/X11/fonts' as follows:
cp -f /opt/advant/MOD-NLS/etc/fonts.alias
/opt/advant/MOD-OS/lib/X11/fonts
To utilize the cyrillic fonts in an HPterm window you can either start
a HPterm window with a cyrillic font:
hpterm -fn "--user-medium-r-normal--17-128-72-72-m-90-iso8859-5"
Or you can alias a font, say 9x15b which we use for all HPterm windows,
in the fonts.alias file as so:
9x15b
--user-medium-r-normal--17-128-72-72-m-90-iso8859-5
Backup/Restore American definition files on a pre Unix 10.x machine
---------------------------------------------------------------------
If the NLS customize kit has been installed on a system whose Unix version is
pre-10.x, the following steps should be performed before updating to the new
version of Unix:
On the pre-10.x machine, as any user:
Move to the alarm nls directory:
cd /products/components/USOS/alarm/lib/nls/
Backup the English and your language definition files to the tape
archive:
tar cv american/*.def
Move to the runtime nls directory:
cd /products/components/USOS/runtime/lib/nls
Backup the English and your language definition files to the tape
archive:
tar rv american/*.def
3BUR001 835R0001 REV C
E-3
If you have added aliases to your fonts.alias file, move to the fonts
directory:
cd /products/components/USOS/runtime/lib/X11/fonts
tar rv fonts.alias
On the 10.x machine, BEFORE you load the ABB-AC-NLS fileset, as the 'root' user:
Move to the MOD-OS etc directory, create the american directory, and
restore the archived definition files:
mkdir -p lib/nls
cd lib/nls
tar xv
mv american en_US.iso88591
chown -R ocsmgr:ocs lib
find lib -type d |xargs chmod 775
find lib -type f |xargs chmod 444
If you have a fonts.alias file, leave it here until after you load the
ABB-AC-NLS fileset.
Read the /lib/nls/README.nls.10.01 file to familiarize yourself with how
the NLS functionality differs from a Unix 9.x machine. In this file you
will also find the new name for the language you desire to use.
Now, move your language definition files to the new language format:
mv your_language new_language_format.iso88591
On the 10.x machine, AFTER you load the ABB-AC-NLS fileset:
If you have a fonts.alias file, compare it to the new version and add
the changes to the new version:
diff /etc/opt/advant/MOD-OS/lib/nls/fonts.alias
/opt/advant/MOD-OS/lib/X11
As the 'root' user:
vi /opt/advant/MOD-OS/lib/X11/fonts.alias
Once the archived definition files have been loaded onto the Unix 10.x system,
the user should follow the steps outlined in the section below, entitled
"Updating language files to a new version."
E-4
3BUR001 835R0001 REV C
Section
Updating language files to a new version
------------------------------------------
Updating existing language files to a new version is similar to adding a new
language, and involves some of the same steps. When the swinstall program
loads the MOD-AMERICAN fileset onto an Operator Station, it puts the new
message definition files (*.def) into a temporary directory:
'/opt/advant/MOD-NLS/newconfig/en_US.iso88591'
After loading the new definition files to this directory, the configure script
looks for any existing definition files in the '/etc/opt/advant/MOD-OS/lib/nls/
en_US.iso88591' directory. If the script finds existing definition files, it
will move those files into a backup directory named "version.orig". Where
'version' is the version of the NLS files presently installed on your machine.
This backup directory will exist in '/opt/advant/MOD-NLS'.
Once the existing definition files have been copied, and the new definition
files have been moved, the configure script will perform a 'diff' on the
definition files. Any differences that are found will be stored in a file
called 'file_changes' in the '/etc/opt/advant/MOD-OS/lib/nls' directory.
If there are no differences, the 'file_changes' file will not be created.
Note: If the American definition files have not previously been installed or
loaded, the configure script will simply copy the definition files from the new
directory to the appropriate directory. The orig directory will be created the
next time an NLS install is performed.
Now the 'root' user should perform the following:
If the NLS customize kit has not been previously installed, the
steps listed above under "Addition of a New Language" should
be followed.
If the NLS customize kit has been previously installed, or if the user
has loaded a pre-1.6 version of the English definition files onto a new
Unix 10.x system (as part of the upgrade steps outlined in the preceding
section), the user should now:
View the '/var/adm/sw/swagent.log' file. If the configure script has
found any differences between the old and new language definition files,
the creation of the diff output file(s), 'file_changes', will be noted
in this log. If no differences were found, this will also be noted.
If a 'file_changes' file was created for the, move to the MOD-OS nls
directory:
cd /etc/opt/advant/MOD-OS/lib/nls
3BUR001 835R0001 REV C
E-5
Examine the 'file_changes' file. Please note that this file is produced
by the Unix 'diff' command, using the -l option. As a result,
differences are indicated as follows:
Lines that have been deleted from the old definition file are marked
with a '-' in the old file. Lines that have been added to the new
definition file are marked with a + in the new file. Lines that
have changed from the old definition file to the new definition file
are marked with '!' in both files.
Move to the $NLS_LANG directory:
cd $NLS_LANG
For each change in the body of the american definition files, as
indicated in 'file_changes', make the appropriate change, and
translation (if necessary), in the $NLS_LANG *.def files. These changes
should be made as the 'ocsmgr' user.
Try to keep the translated message text the same length as the
English version and obey all length restrictions stated in a few of
the message files.
Make sure there are no extraneous spaces at the end of the message
text, since such spaces can lead to alignment problems.
Do not alter the message constants or the message numbers.
If any of the 'en_US.iso88591/*.def' files are new, and do not exist in
the $NLS_LANG directory, follow steps 4 through 6 of the section,
"Addition of a New Language."
Compile the new language message files using the nls Makefile in the
'/etc/opt/advant/MOD-OS/lib/nls' directory:
make -e
Now create a link from the MOD-OS nls directory to the $NLS_LANG
directory, as the 'ocsmgr' user:
umask 222
cd /opt/advant/MOD-OS/lib/nls
chmod u+w .
ln -s /etc/opt/advant/MOD-OS/lib/nls/$NEW_LANG $NEW_LANG
chmod u-w .
E-6
3BUR001 835R0001 REV C
Section
Addition of a New Language
-----------------------------
The addition of a new language is just a matter of setting your working shell
environment to the new language, translating the message text files from
English to the new language, and then creating the new language catalog files.
Setting your working shell environment to a new language can be accomplished by
running the osLangSetup script with the new language as the first parameter:
Example: Say you wish to setup the Operator Station for the German
language. As the 'root' user you would run:
osLangSetup German
This would alter all the configuration files necessary for a German
Operator Station.
To return the Operator Station to the default language either of the
following would work:
osLangSetupor
osLangSetup C
Translating the message text files from English to the new language:
Set the nls language variable for compiling the new language message
files.
export NLS_LANG="new_lang"
Where "new_lang" can be ru_RU.iso88591 (Russian) for example (do not
enter the quotes).
Move to the NLS directory:
Create a new message file directory as the 'ocsmgr' user:
mkdir $NLS_LANG
chmod 775 $NLS_LANG
chown ocsmgr:ocs $NLS_LANG
Copy the message files from the English (en_US.iso88591) directory into
the new language directory and change the permissions on the new
language message files.
cp en_US.iso88591/*.def $NLS_LANG/
chmod 664 $NLS_LANG/*.def
3BUR001 835R0001 REV C
E-7
For each of the message definition files (*.def) in the new language
directory, translate the message texts into the new language.
Try to keep the translated message text the same length as the English
version and obey all length restrictions stated in a few of the message
files.
Make sure there are no extraneous spaces at the end of the message text,
this can lead to alignment problems.
Do not alter the message constants or the message numbers.
Creating the new language catalog files:
Compile the new language message files using the nls Makefile in the
'/etc/opt/advant/MOD-OS/lib/nls' directory
make -e
Now create a link from the MOD-OS nls directory to the $NLS_LANG directory:
umask 222
cd /opt/advant/MOD-OS/lib/nls
chmod u+w .
ln -s /etc/opt/advant/MOD-OS/lib/nls/$NEW_LANG $NEW_LANG
chmod u-w .
E-8
3BUR001 835R0001 REV C
Section F.1 Version 10.0/n and 14.n Multibus Node PROM Checksums - (4 June 1999)
Appendix F PROM Checksums
F.1 Version 10.0/n and 14.n Multibus Node PROM Checksums - (4 June 1999)
MULTIBUS, D/D
Cat #6006PZ00032B
Change 9/6/95 #P195606
Location
Pacific
68000
Pacific
68020
Synergy
68020
PROM ID
Bitsum
U110
U122
U111
90H
$790E
U113
U153
U115
90L
$2803
U310
U207
U311
98H
$DCCF
U313
U170
U315
98L
$8BF6
SERIAL I/O
Cat #6007PZ000010A
Change 5/20/94 #P194604
Location
Bitsum
U19
$BA11
D/M
128K PROM -
Cat #6009PZ00023A
512K PROM -
Change 7/15/97 #P197605
Cat #6009PZ00023B
Change 7/15/97 #P197605
Location
Bitsum for 128K
PROM
Bitsum for 512K
PROM
U44
$1AA0
$1AA0
NOTE
512K PROM is used on 125S2206-10 for 6009B - Model L; 6005B - Model S;
6205B - Model J.
3BUR001 835R0001 REV C
F-1
D/F1
(512-2)
Cat #6005PZ00033B
(68000 microprocessor only!) Change 1/15/98 #P197048
TO USE 512K PROMS:
Model E Requires Daughter Board. - 125S2800-1 and 256K RAM; NDA 1698E3;
PAL U101 - $1730 - 129S1078-22
Model G,J -Contains no Daughter Board; Includes PAL U101 - $1748 - 129S1078-26
1.
F-2
Location
PROM ID
Bitsum
U75, U751, SCU78
20H
$4885
U76, U761, SCU79
20L
$0AB7
U77, U771, SCU80
0H
$9E10
U78, U781, SCU81
0L
$A386
Same D/F PROMs for SC and Models A/B/C Controller Subsystems. Remove W2 Memory jumper, when going to
Version 8 or 10 Software. Model E board with Daughter Board, and PAL becomes Model F (important if board is
ever serviced).
3BUR001 835R0001 REV C
MULTIBUS
(2M)
Cat #6026PZ00004A
(33MHz only) Change 9/6/95 #P195606
Location
Taylor
68020
PROM ID
Bitsum
U5
0H
$0CBC
U6
0L
$2820
SCSI DISK CONTROLLER
(2M)
Cat #6027PZ00003A
Change 6/5/99 #P199031
Location
Bitsum
D1
$A1BF
VIDEO MODULE
(256-2)
Cat #6008P_00_06A
Model C and above Boards only!
Change 4/24/91 #1900331
Location
U3
U9
3BUR001 835R0001 REV C
Bitsum
(Z - English)
$54AC
(A - Russian)
$5BA5
(B - Serbo-Croatian)
$5AA6
(006A Standard Color)
$F982
(106A Option #1)
$C228
(206A Option #2; On Mod D Video
Module only, on which PAL U7 is
129S1190-4)
$2E0F
F-3
MODEL A CONTROLLER1
(256-2)
Cat #6004PZ00031A
Change 3/96 #P196600
Location
PROM ID
Bitsum
U99
30H
$828C
U100
30L
$E863
U101
20H
$2EBB
U102
20L
$2E7E
U103
10H
$95C1
U104
10L
$7114
U105
0H
$E634
U106
0L
$7431
Location
PROM ID
Bitsum
U128, U112
20H
$B147
U129, U113
20L
$16E1
U130, U114
0H
$7BF5
U131, U115
0L
$E545
Location
PROM ID
Bitsum
U14
P3
$7F05
U15
P2
$A352
U16
P1
$368A
U17
P0
$DE46
MODEL B,C,D CONTROLLER1
(512-2)
Cat #6004PZ00031B
Change 3/96 #P196600
SC_CONTROLLER
(512-2)
Cat #6204PZ00030A
Change 5/1/91 #P191032
1.
F-4
Watchdog Timer Jumper must be off.
3BUR001 835R0001 REV C
BMC1
(512-2)
Cat #6014PZ00027B
Change 7/1/93 #P193608
TO USE 512K PROMS:
Model A,B Requires Daughter Board- 125S2794-1; PAL U124 - $14A6 - 129S1078-23
Model C and above - No Daughter Board; Requires PAL U176 - $14BE - 129S1078-24
Location
PROM ID
Bitsum
U95, U201, U148, U101
20H
$60BE
U96, U202, U149, U102
20L
$8537
U97, U203, U150, U103
0H
$F28C
U98, U204, U151, U104
0L
$0554
SC_BMC
(512-2)
Cat #6214PZ00005A
Change 7/1/93 #P192615
1.
3BUR001 835R0001 REV C
Location
PROM ID
Bitsum
U6
P3
$62B5
U7
P2
$E14C
U8
P1
$4F58
U9
P0
$6637
Watchdog Timer Jumper must be off. Model C and D boards with PAL become Model E (important if board is ever
serviced).
F-5
F-6
3BUR001 835R0001 REV C
Index
INDEX
A
ACCESS CLASS 3-6
ADVANT Environment 2-23, 3-26
Alarm/Event logging 3-41
AREA object 3-1, 3-6, 3-14
AUTO LOG 3-6
AUTO START field 3-4
Autostart 2-48, 2-50
External Alarm 3-43
External Display Access 3-51
F
fbackup 5-11
frecover 5-12
Full Station Backup and Recovery 5-8
Function Key Configuration 3-33
B
G
Backing up environments 5-13
Backing up TCL and Batch 300 5-15
Backup and Restore 5-11
BACKUP LOGGER NAME 3-9
BACKUP PRINTER NAME 3-10
GENERICD object 3-1, 3-3
Graphics restore 5-14
C
CFG-Password 2-26, 5-28, 5-44
CI_CONFIG 3-21
Communication Ports 3-39
D
DCN address 3-26
Changing the DCN address 3-26
Initial DCN address 3-26
DCN Stand-alone system 3-26
Device files 3-36
Device Special File 3-22
Disk Failure 2-1
DO RATE 3-4
E
Environment
ADVANT 2-23, 3-26
Automatic Installation 3-27
ES 2-23, 3-27
Environment backup 5-13
Environment Variable
$C_CAPE_ALL_ADM_LOG 2-27, 2-29
DEBUG_TLLDNLD 3-24
DEBUG_TLLUPLD 3-24
ES Environment 2-23, 3-27
EVENT COLOR 3-11
EVENT PRINT TYPE 3-12
EVENTS PRINTED 3-12
EXPORT TO DEVICES 3-6
3BUR001 835R0001 REV C
H
HISTORY object 3-13
HP ALARMS PRINTED 3-12
HP PRINT TYPE 3-13
I
Insert Project 2-26, 5-27
Insert User 2-28, 5-30
installation of the IMS software 2-1
Installation Types 2-1
L
LL_DEV 3-2
LOG_DETL object 3-2, 3-9
LOGGER DESCRIPTION 3-9
M
MAX # MSGS IN MEMORY 3-10
MAX # MSGS ON DISK 3-10
MED ALARM COLOR 3-13
MED ALARMS PRINTED 3-13
MED PRINT TYPE 3-13
Memory
OMF Shared 2-25, 2-49, 2-52
RTAB 2-5, 2-24
Message Center Edit Window 3-7
MESSAGE CTR 3-16
mknod 3-22
MOD 300 database object hierarchy 3-1
MODUSERS object 3-2, 3-5
MSG_ROUT Object 3-16
i
Index
N
envPrimaryServerNode 3-87 to 3-88
envServerMenu 3-88
gptBackgroundColor 3-71
gptGridColor 3-71
gptTraceColor0 3-71
gptTraceWidth 3-71
graphicsServerMenu 3-89
highlightColor 3-71
installAllDisplayElements 3-66
installS100Displays 3-67
installS800Displays 3-67
installTCLBATCHDisplays 3-66
installTLLDisplays 3-67
passChangeMinimumWait 3-83
readOnlyNodes 3-85
ShowAlarmAckDate 3-73
ShowAlarmMilliSeconds 3-73
showAlarmOnOverviewPSAP 3-73
ShowMessageDate 3-73
TCLIdentificationMessage 3-83 to 3-84
underControlColor 3-71
unsuccessfulLoginThreshold 3-82
useSingleColumnStatusBlocks 3-71
NODE TYPE 3-4
O
OMF Shared Memory 2-25, 2-49, 2-52
P
Page Selector Alarm Panel (PSAP), Adding a 3-32
PASSWORD 3-5
Peripheral devices 3-36
PHYSICAL DEVICE 3-3
PRINTER NAME 3-10
Printer setup 3-38
Project
comment 2-26, 5-28, 5-43
description 2-26, 5-28, 5-44
Name 2-26, 5-27, 5-43
restore 5-31
Size 2-26, 5-27 to 5-28, 5-43
source 2-27, 5-28, 5-44
project number 2-28, 5-30
project user 2-28, 5-30
Projects window 2-25, 5-27, 5-42
Protect Project 2-27, 5-28, 5-44
R
RDR-Password 2-26, 5-28
reader user 2-27, 5-29
REMOTE TYPE 3-16
Restoring graphics 5-14
S
Save Project dialog box 5-26
SEC DEV 3-6
Serial Expansion Unit 3-49
serial port 3-21
Shut-down procedures 2-45
SOFTWARE NAME 3-4
Start-up procedures 2-1
STD ALARM COLOR 3-10
STD ALARMS PRINTED 3-11
STD PRINT TYPE 3-11
System Variable
autoLogoffPeriod 3-84 to 3-85
Button2Ack 3-73
communicationRetryMax 3-83
defaultEnvironment 3-27, 3-89
envBackupServerNode 3-87 to 3-88
ii
T
TCL and Batch 300 backup 5-15
TCL_DEV 3-2
Touch screen, see Xtouch
TRIP LIMIT HIGH 3-11
TRIP LIMIT HIGH HIGH 3-11
Two-screen operation, converting to 3-29
U
User
CFG 2-26, 5-28, 5-44
configuration 2-27, 5-29
group 2-26, 5-28, 5-44
RDR 2-26, 5-28, 5-44
writer 2-27, 5-29
USER ID 3-5
Users window 2-28, 5-30
W
writer 2-27, 5-29
X
Xtouch 4-3
Error messages 5-3
External Display Access 3-51
3BUR001 835R0001 REV C
3BUR001 835R0001 REV C
October 2000

Advant Advant Station 500 Series

Transcription

Similar documents

welcome praise message giving communion

Cycle tour for the retention of religion in schools kicks off

A SHORT HISTORY of BAINSFORD CHURCH

Disk to Disk Backup for IBM Midrange Servers

ampx user manual - Klundert Muziek

Plan to Restore America

RS Series Brochure

Diapositiva 1

By Richard Osei Ref. Chuck Missler

REWARDS PROGRAM - TCL Chinese Theatres