universal stationx system administration manual universal stationx system administration manual ix...

L

Universal StationXSystem Administration

Manual

UX11-400

L

Universal StationX

Universal StationXSystem Administration

ManualUX11-400

5/94

ii Universal StationX System Administration Manual 5/94

Copyright, Notices, and Trademarks

Printed in U.S.A. – © Copyright 1993 by Honeywell Inc.

Revision 02 – May 11, 1994

While this information is presented in good faith and believed to be accurate,Honeywell disclaims the implied warranties of merchantability and fitness for aparticular purpose and makes no express warranties except as may be stated in itswritten agreement with and for its customer.

In no event is Honeywell liable to anyone for any indirect, special or consequentialdamages. The information and specifications in this document are subject tochange without notice.

This document was prepared using Information Mapping® methodologies andformatting principles.

TDC 3000X is a trademark of Honeywell Inc.

Information Mapping is a trademark of Information Mapping Inc.

OSF, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc.

Universal StationX is trademark of Honeywell Inc.

UNIX is a trademark of AT&T Technologies Inc.

Macintosh is a trademark of Apple Computer, Inc.

TotalPlant is a trademark of Honeywell Inc.

Windows is a trademark of Microsoft Corporation.

HoneywellIndustrial Automation and Control

Automation College2820 West Kelton Lane

Phoenix, AZ 85023

(602) 789-5669

5/94 Universal StationX System Administration Manual iii

About This Publication

This publication is provided to aid configuration/operation of Universal StationX hardware/software.

Use this publication to install, configure, and operate the Universal StationX. If you are unfamiliarwith general LAN (Local Area Network) configuration techniques, or details of the specific LANconfiguration to which the station is attached, your Local Area Network Administrator will beneeded to assist in configuration/troubleshooting.

iv Universal StationX System Administration Manual 5/94

5/94 Universal StationX System Administration Manual v

Table of Contents

SECTION 1 – UNIVERSAL STATIONX SYSTEM ADMINISTRATION DOCUMENTATION 1

1.1 Overview.............................................................................................. 1

SECTION 2 – UNIVERSAL STATIONX CONCEPTS..................................................... 3

2.1 What is Universal StationX...................................................................... 32.2 Universal StationX Hardware .................................................................. 5

SECTION 3 – WINDOW OPERATIONS........................................................................ 7

3.1 Window Manager .................................................................................. 73.2 Cursor Usage........................................................................................ 83.3 Altering Window Size ............................................................................ 93.4 Minimizing/Maximizing Windows........................................................... 103.5 Using the Window Menu...................................................................... 113.6 Repositioning Windows....................................................................... 123.7 Workspace Menu Access .................................................................... 133.8 Operator Workspace Menu.................................................................. 143.9 Supervisor Workspace Menu............................................................... 153.10 Engineer Workspace Menu ................................................................. 163.11 View-Only Workspace Menu................................................................ 183.12 Using the Touchscreen....................................................................... 19

SECTION 4 – UNIVERSAL STATIONX OPERATIONS................................................ 21

4.1 Power-On........................................................................................... 214.2 Accessing Universal StationX Coprocessor Functions........................... 224.3 Loading a Personality to the LCN Processor ......................................... 234.4 Printing from the Universal StationX...................................................... 254.5 Failsafe Operation............................................................................... 264.6 Universal StationX Display Changes ..................................................... 274.7 X Window Operation............................................................................ 284.8 System Security.................................................................................. 294.9 Shut Down the Universal StationX........................................................ 314.10 Universal StationX Restrictions............................................................. 324.11 Problem Reporting.............................................................................. 33

SECTION 5 – COPROCESSOR CONFIGURATION TASKS........................................ 35

5.1 Configuration Overview....................................................................... 355.2 Initial Power-On................................................................................... 415.3 Initial Login ......................................................................................... 425.4 Configure Coprocessor Time and Timezone......................................... 435.5 Configure Coprocessor LAN Information .............................................. 445.6 Configure LAN Routing....................................................................... 465.7 Configure Coprocessor Printer (Local).................................................. 485.8 Configure Coprocessor Printer (Remote).............................................. 505.9 Industrial Workspace Manager.............................................................. 525.10 Change Coprocessor Password........................................................... 55

SECTION 6 – COPROCESSOR USER ENVIRONMENT CONFIGURATION................. 57

6.1 User Configuration Overview ............................................................... 576.2 X Host Authorization............................................................................ 586.3 Configure Native Window Behavior ...................................................... 616.4 Configure Keyboard Focus Policy........................................................ 626.5 Change User Password....................................................................... 63

vi Universal StationX System Administration Manual 5/94

Table of Contents

SECTION 7 – ALTERNATIVE COPROCESSOR CONFIGURATION METHODS........... 65

7.1 Alternative Method Overview............................................................... 657.2 Backup/Restore Alternative (Local DAT Procedure) .............................. 677.3 Backup/Restore Alternative (Remote DAT Procedure) .......................... 697.4 FTP (File Transfer Protocol) Alternative................................................. 717.5 FTP (File Transfer Protocol) Procedure................................................. 757.6 Modifying the /etc/hosts File Manually .................................................. 767.7 Network Backup/Restore Configuration................................................ 77

SECTION 8 – CUSTOM CONFIGURATION ................................................................ 79

8.1 Customizing the Workspace Menu....................................................... 798.2 Customizing the User’s Shell Variables................................................. 84

SECTION 9 – COPROCESSOR ADMINISTRATION TASKS ....................................... 85

9.1 Create New Coprocessor Users ........................................................... 859.2 Delete Coprocessor Users................................................................... 879.3 Modify Coprocessor User Information................................................... 889.4 Backup the Coprocessor Hard Drive..................................................... 899.5 Restore Coprocessor Hard Drive Data................................................... 919.6 Coprocessor Software Update (Local DAT)........................................... 939.7 Coprocessor Software Update (Remote DAT)....................................... 969.8 Preparing Software Update Server ....................................................... 999.9 Checking Tracking Files..................................................................... 1029.10 Creating Recovery Tapes .................................................................. 103

SECTION 10 – OPTIONAL APPLICATION SOFTWARE........................................... 105

10.1 Application Software Supported ........................................................ 10510.2 Loading Kinet Software from a Local DAT Drive................................... 10610.3 Loading Kinet Software from a Remote DAT Drive............................... 108

5/94 Universal StationX System Administration Manual vii

Acronyms

AIA.......................................................................... Application Integration ArchitectureCIM ........................................................................ Computer Integrated ManufacturingIWSM ............................................................................. Industrial Work Space ManagerLAN ................................................................................................ Local Area NetworkLCN ............................................................................................ Local Control NetworkOSF.................................................................................... Open Systems FoundationOSI ............................................................................... Open Systems InterconnectionTDC ........................................................................................ Total Distributed ControlTPDG...................................................................... Turbo Peripheral Display GeneratorUCN...................................................................................... Universal Control NetworkUNPX......................................................................................... Universal Personality XUXS ........................................................................... Universal Station with ExtensionsWSI.............................................................................................. Workstation Interface

viii Universal StationX System Administration Manual 5/94

References

PublicationTitle

PublicationNumber

BinderTitle

BinderNumber

UXS User Guide UX09-400 Universal StationX TDC 2093

Universal StationX SystemAdministration Manual

UX11-400 Universal StationX TDC 2093

Universal StationXService UX13-410 Universal StationX TDC 2093

Five/Ten Slot Module Service LC09-400 LCN Service - 1 TDC 2060-1

Hardware Verification Test SystemHVTS-Universal StationX

SW13-211 LCN Service - 2 TDC 2060-2

UXS Specification and Technical Data UX03-400 Universal StationX TDC 2093

LCN Site Planning SW02-450 System Site Planning TDC 2020

LCN Guidelines LC09-410 LCN Installation TDC 2025

LCN System Installation SW20-410 LCN Installation TDC 2025

LCN System Checkout SW20-400 LCN Installation TDC 2025

HP-UX System AdministrationConcepts

98594-90062

HP-UX System Administration Tasks 98594-90061

A Beginners Guide to the X WindowSystem

98594-90002

Using the X11 Window System 98794-90001

Installing and Configuring the X WindowSystem

98794-90004

HP-UX System Security 92453-90029

Introducing UNIX System V 98597-90620

A Beginners Guide to HP-UX 98594-90006

HP-UX Concepts and Tutorials: TextEditors and Processors

97089-90022

A Beginner’s Guide to Text Editing 98594-90010

Quick Reference Card for vi Editor 98597-90000

HP-UX Concepts and Tutorials: Shellsand Miscellaneous Tools

97089-90062

5/94 Universal StationX System Administration Manual ix

References

A Beginner’s Guide to Using Shells 98594-90008

Finding HP-UX Information HP9000Series 300

98594-90081

HP-UX Installation Manual 98594-90013

HP-UX Reference 09000-90013

Installing and Maintaining NS-ARPAServices

B1014-90007

LAN Node Managers Handbook

Using ARPA Services B1014-90000

Installing and Administering ARPAServices

B1014-90001

ARPA/Berkeley Reference Pages B1014-90002

Berkeley IPC Programmer’s Guide 98194-60525

Using NFS Services B1013-90000

Installing and Administering NFSServices

B1013-90001

NFS Services Reference Pages B1013-90003

Programming and Protocols for NFSServices

B1013-90002

Using Network Services B1012-90000

Installing and Administering NetworkServices

B1012-90001

Network Services Reference Pages B1012-90002

NetIPC Programmer’s Guide 98194-60527

NS Cross-System NFT ReferenceManual

Installing and Administering OSITransport Services

Installing and Administering X.400Administrators Guide

32034-90005

LAN/X.25 Reference Pages 98194-90014

X.25 Programmer’s Guide

X.25: The PSN Connection

Networking Overview B1012-90003

x Universal StationX System Administration Manual 5/94

References

Installing Peripherals HP 9000Series 300

97005-90002

Troubleshooting HP-UX Systems ErrorDiagnosis and Recovery

92453-90026

HP 35470A SCSI DAT (Digital AudioTape) Drive

Model 382 and R/382 Owners Guide

HP A2258A 210 Mb Disk DriveUpgrade Manual

HP A2259A 423 Mb Disk DriveUpgrade Manual

Quantum 210 Mb Disk Drive Manual

Quantum 423 Mb Disk Drive Manual

Patriot Monitor (Aydin) Operation andMaintenance Manual

Laserjet III Printer User’s Manual

LaserJet 4 and 4M Printers User Manual C2001-90912

Guide to Setting Up the HP LaserJet 4Printer

C2001-90901

LaserJet 4 and 4M Printer QuickReference Guide

R-1E-296-VID

5/94 Universal StationX System Administration Manual 1

Section 1 – Universal StationX System AdministrationDocumentation

1.1 Overview

Availabledocumentation

The system administration documentation for the Universal StationX

product is comprised of the following manuals published by Honeywell andHewlett Packard:• Universal StationX User Guide, UX09-100

• Universal StationX System Administration Manual, UX11-100

• Universal StationX Service

• 5-Slot Module Service

• HVTS-Universal StationX

• Universal StationX Specification and Technical Data

• System Site Planning

• LCN Guidelines

• LCN Planning

• LCN Installation

• LCN System Checkout-Universal StationX

• A Beginners Guide to the X Window System

• Using the X11 Window System

• HP-UX Concepts and Tutorials: Text Editors and Processors

• A Beginner’s Guide to Text Editing

• Quick Reference Card for vi Editor

• HP-UX System Administration Concepts

• HP-UX System Administration Tasks

• HP-UX System Security

• HP 35470A SCSI DAT (Digital Audio Tape) Drive

• Model 382 and R/382 Owners Guide

• HP A2258A 210 Mb Disk Drive Upgrade Manual

• HP A2259A 423 Mb Disk Drive Upgrade Manual

• Quantum 210 Mb Disk Drive Manual

• Quantum 423 Mb Disk Drive Manual

ProceduresThis publication covers specific procedures to perform many tasks whichinclude:

• Set the coprocessor Time, Date, and Timezone

• Configuration of coprocessor LAN connectivity

• Laser printer (coprocessor printer) configuration

• Configuration of LCN window display behavior

Continued on next page

2 Universal StationX System Administration Manual 5/94

1.1 Overview, Continued

• Adding/Deleting/Modifying users

• Adding/Deleting user authorization to shut down the coprocessor

• Adding/Deleting user authorization to Enter Native Mode

• Adding/Deleting X Host authorization

• Performing routine backup/restore

• Performing software updates (Local, Remote, and Server install)

• Adding/deleting/modifying users

• Changing user passwords

• Changing the coprocessor password.

Additionaldocumentation

Additional information to assist in customizing the coprocessorconfiguration is available in the following Hewlett Packard documents:

• HP-UX Installation Manual

• HP-UX Reference

• Installing and Maintaining NS-ARPA Services

• LAN Node Managers Handbook

• Using ARPA Services

• Installing and Administering ARPA Services

• ARPA/Berkeley Reference Pages

• Berkeley IPC Programmer’s Guide

• Using NFS Services

• Installing and Administering NFS Services

• NFS Services Reference Pages

• Programming and Protocols for NFS Services

• Using Network Services

• Installing and Administering Network Services

• Network Services Reference Pages

• NetIPC Programmer’s Guide

• NS Cross-System NFT Reference Manual

• Installing and Administering OSI Transport Services

• Installing and Administering X.400 Administrators Guide

• LAN/X.25 Reference Pages

• X.25 Programmer’s Guide

• X.25: The PSN Connection

• Networking Overview

• Installing Peripherals HP 9000 Series 300

• Troubleshooting HP-UX Systems Error Diagnosis and Recovery


Section 2 – Universal StationX Concepts

2.1 What is Universal StationX

Long term plan In today’s competitive environment, maintaining control of costs andquality is paramount. Many process industry companies are formulatinglong-range plans to meet these objectives. The broad direction is to achievelow cost operations through the integration of process control andinformation system technologies. Honeywell’s TDC (Total DistributedControl) system will be the foundation of the future CIM (ComputerIntegrated Manufacturing) system. This Honeywell system is calledTotalPlant.

To meet these challenges, it is important to provide an evolutionary path ofproducts, that preserve customer investments in hardware and training. TheUniversal StationX platform is the first step in implementing this long termstrategy.

Definition of UniversalStationX

An embedded open system environment provides support fordisplay/import of data generated on non-LCN platforms. ThisTDC 3000X/X Windows integrated platform enables software connectionsbetween the PIN (Plant Information Network) and the LCN (Local ControlNetwork). Universal StationX is the linking of open systems, X-Windows,and Motif to produce a visually integrated display of TotalPlant information.

The initial introduction/release of the Universal StationX product providesvisual integration of plant information. Visual Integration provides thefollowing features/benefits:

Features Benefits

Dual Operating System Support Power of TDC - flexibility of open systems

Window Management Management of multiple displays

Single LCN window - MotifEnvironment

Ability to resize or move LCN window

Client/Server X Windows Communication with non-TDC computersystems

Multiple PIN windows Simultaneous access to multiple non-TDCcomputer systems

Fail Safe Fall Back Ensures the “view to the valve”

System Security Limits access to authorized users

TDC system isolated from open system



2.1 What is Universal StationX, Continued

Universal StationXexample

The support for the open system, allows connection to a wide variety ofhardware platforms.

TDC SYSTEM LOCAL AREA NETWORK

PROCESSDATA

LAB ANALYSISSOFTWARE

U S CONNECTED TO LCN AND LAN

12583

X

Currently, information on the LAN (Local Area Network) can be displayedor updated at the Universal StationX. This allows operators to view labanalysis data on the same screen as the process data. By integrating thisdata, the operator has less distractions and requires less training (only onecomputer system). A typical control room operator may have two or threecomputers to monitor (each holding some essential process data). Thepotential for process upset increases when the operator’s attention isdiverted from the TDC display.


2.2 Universal StationX Hardware

US - Universal StationXmigration

The Universal StationX is available in two basic forms: upgrade kits (for astandard Universal Station), or as a complete station (with furniture). Theupgrades are available in several versions to match your specific hardwareconfiguration.

Initial hardware The initial Universal StationX deliveries are in a standard/current TDC3000X Universal Station furniture.

Components The Universal StationX consists of a tightly integrated TDC 3000X

Universal Station and an open system processor environment in acoprocessor architecture. The Universal StationX contains the followingcomponents:

• Standard US furniture cabinet

• Standard 5-slot module

• New electronics package

• New monitor

• Hard drive and DAT (Digital Audio Tape) drive

New electronicspackage

The electronics package consists of:

• Standard K2LCN-8 board

• Workstation Interface board (WSI board)

• Turbo Peripheral Display Generator (TPDG board)

• I/O boards for each of the boards above

• 8 ampere power supply

New monitor A 1280 x 1024 monitor provides high resolution display.

New coprocessor media A hard drive and a DAT (Digital Audio Tape) drive have been added tocontain these Universal StationX files:• Open system filesystem

• X Window files

• TPDG download code

• Universal StationX (UNPX) personality download code

This media is connected to the Open system coprocessor and is notaccessible by the LCN filesystem.

Specific details For more specific hardware information, refer to Section 8 UniversalStationX Service.


Section 3 – Window Operations

3.1 Window Manager

X window system The X Window system provides standards by which computers ofdissimilar types can exchange window displays. This allows computersystems to execute an application and send the display of that application toother computer systems which support the X window graphical standard.This standard integrated the concept of a window manager. The windowmanager allows manipulation of the X window displays.

Consistent look The Universal StationX utilizes Motif Window Manager to provide aconsistent look to all applications displayed on the Universal StationX. Thissoftware provides functions for opening, closing, moving, resizing, andindicating the active window. If you have used Microsoft Windows youwill immediately recognize the similarities.

The Window Manager attributes are preset, and cannot be changed. Laterversions will allow custom configuration of window attributes.

Functions provided The Motif Window Manager applies the window interface attributesindependent of the application running within a window. The windowinterface effects only the manner in which that window is displayed. It willprovide such elements as: title bars, scroll bars, resizing, control ofoverlapping windows, and the ability to iconify a window. These elementsallow manipulation of multiple windows, independent of their application orthe underlying computer platform/operating system executing theapplication. This allows one window interface to display all windowsappearing on the Universal StationX screen.


3.2 Cursor Usage

Cursor types The Window Manager uses various cursor types to depict the type ofoperation being performed. The types are:

• pointing or or

• working

• moving

• resizing or or or or or or or


3.3 Altering Window Size

Changing window size Where you grab the window’s frame determines how the window will beresized. The dimensions (width x height) of the window being resized isdisplayed in the center of the screen. The measurement is in characters(across) and lines (down) for terminal windows; other types are measuredin pixels (dots on the screen).

NOTE: When resizing the LCN Native Window, it is necessary to clickthe bottom right corner of the window border to cause the LCNdisplay to resize. The LCN processing continues withoutproblem, but the display may be only partially visible.

Use the following to change the window size:

If you want to stretch or shrink thewindow . . .

Point to . . .

vertically from the . . .

top top of the frame, above the title bar

bottom bottom of the frame

horizontally from the . . .

right right side of the frame

left left side of the frame

diagonally from the . . .

bottom left corner frame’s lower left corner

top left frame’s upper left corner

top right frame’s upper right corner

bottom right frame’s lower right corner


3.4 Minimizing/Maximizing Windows

Minimize a window To reduce workspace clutter, you may change a window to an icon. Anicon is a graphical representation of the application executing in thatwindow. This reduction to an icon is called “minimizing” a window.Applications executing in a minimized window continue to execute until thetask is completed, or until they require user input.

There are several methods to minimize a window:

• Use the Minimize button on the windows title bar

• Use the Minimize selection from the Window Menu

A window which has been minimized (iconified) may be returned to thewindow form using several methods.

• Double-Click (click twice in rapid succession) the icon.

• Use the Maximize selection from the Window Menu

Telnet%

MINIMIZEBUTTON

Telnet

12584

Maximize a window Clicking on the Maximize button will enlarge the window to cover the entiremonitor. Clicking on the button a second time will return the window sizeto the original dimensions.

NOTE: When resizing the LCN Native Window, it is necessary to clickon the bottom right corner of the window border to cause the LCNdisplay to resize. The LCN processing continues withoutproblem, but the display may be only partially visible.

Telnet%

MAXIMIZEBUTTON

12585


3.5 Using the Window Menu

Window menu Each window has a window menu containing functions for controlling thewindow. To access the window menu, point to the menu target and thenpress and hold the select button. The menu is displayed as long as the selectbutton is held down. To select a menu item, drag the cursor down the listand release the select button when the appropriate item is highlighted.

Telnet%

MENUBUTTON

12586

To perform the following, select the appropriate menu item:

To do this . . . Select . . .

Restore a window from an icon or aftermaximizing.

Restore

Change the location of a window. Move

Change the size of a window. Size

Shrink the window to its iconrepresentation.

Minimize

Enlarge the window to cover the entireroot window.

Maximize

Send a window to the back or bottomof the window stack, the positionclosest to the root window.

Lower

Immediately close the window andmake it disappear.

Close


3.6 Repositioning Windows

Moving windows Windows can be positioned anywhere on the screen, with one exception.The Native LCN window is configured (for all users except engineer groupmembers) to inhibit its ability to be partially obscured or overlapped byother windows. This attribute can be configured and is covered insubsection 6.3, Configure Native Window Behavior.

To move a window, click and drag on the window’s title bar. Whilemoving, an outline of the window is shown for positioning purposes. Thewindow will move to this new location if the select button is released at thecurrent position.

Telnet%

TITLE BAR

12587


3.7 Workspace Menu Access

Workspace menu To reduce the user interaction with the open system environment, aworkspace menu (sometimes called the root menu) is included. This menuis accessed by holding down the select button within the workspace(outside all windows). You can select a menu item by dragging the pointerdown the menu list and releasing the select button when that item ishighlighted.

Operator Menu

X Menu >

Application Menu >

Engineer Menu

X Menu >

Application >

System Menu >12588

Hierarchical menus The menu uses hierarchical (nested) menu items indicated by an arrow tothe right of the item which has another level of menu. To access thesenested menus, hold the select button and scroll to the appropriate menu; thenested menu item will appear. Moving the cursor onto this new menu willallow selections to be made from this newly visible list of items.

Applications

Calculator

Datebook

Telnet

DECnet

Change Password

Operator Menu

X Menu >

Application Menu >

12589

Access levels The menu is preconfigured according to the access level, which is assignedby the system administrator. When a user is added to the coprocessor, theiruser login name is associated to a group of users. This association providessecurity restrictions by displaying menus specific to that group’s accessauthorization.

The access levels are:

• Operator

• Supervisor

• Engineer

• View Only


3.8 Operator Workspace Menu

Operator Menu items The Operator Menu contains the following:

• X Menu - a nested menu

• Application - a nested menu

Operator Menu

X Menu >

Application Menu >

12590

X Menu items The operator’s X Menu contains the following:

• Shuffle - Shuffles the position (Up/Down) of the active window.

• Native Window - Changes the Native LCN Window attribute to(Allow/Disallow) the window to be Partially Obscured by otherwindows.

• Keyboard Focus Policy - Configures the X Windows attribute(Explicit/Pointer) to identify the active window. Either a mouseclick (Explicit) or cursor within the window (Pointer) is required toidentify the active window.

• X Host Authorization - Authorizes remote computing resourcesto display X applications on this station. Configured for each individualuser.

• Window Print - Prints the contents of the selected window.

• Refresh - Performs a redraw of the X application windows.

• Restart - Restarts the Motif Window Manager; used to force a reset ofMotif Window Manager.

• Logout - Sends a kill message to all X hosts to close open applications,logs the user out, and idles the coprocessor.

Application Menu The operator’s Application Menu contains the following:

• Calculator - a full function calculator application

• Datebook - a calendar/datebook application

• Telnet - accesses the TELNET TCP/IP protocol

• Decnet - accesses the DECnet protocol

• Change Password - allows the user to change their login password


3.9 Supervisor Workspace Menu

Supervisor Menu items The Supervisor Menu contains the following:



Supervisor Menu

X Menu >

Application Menu >

12591

X Menu items The supervisor’s X Menu contains the following:









Application Menu items The supervisor’s Application Menu contains the following:







3.10 Engineer Workspace Menu

Engineer Menu items The Engineer Menu contains the following:



• System Menu - a nested menu

Engineer Menu

X Menu >

Application >

System Menu >12592

X Menu items The engineer’s X Menu contains the following:









Application Menu items The engineer’s Application Menu contains the following:

• UNIX Load - a bar chart display of UNIX processor loading





3.10 Engineer Workspace Menu, Continued

Application Menu items,continued




System Menu items The engineer’s System Commands menu contains the following:

• Configuration - a nested menu of configuration items

• Update Software - used to update coprocessor software

• Add/Remove Users - a coprocessor user registration application

• Backup/Restore - used to backup/restore the coprocessor software

Configuration Menuitems

The engineer’s Configuration Menu contains the following:

• IWSM Configuration - Shutdown WSI and Native Mode access

• System Configuration - used to configure the coprocessor LANenvironment

• Set Time/Timezone - sets the coprocessor time, date, and timezone

• Gated Daemon - Turns ON/OFF dynamic LAN routing


3.11 View-Only Workspace Menu

X Menu items The View-Only X Menu contains the following:










3.12 Using the Touchscreen

Display resolution The high resolution display required a change to touchscreen operation.Software is provided to zoom the screen display at 2 times original size.This zoom touchscreen aids in the selection of small targets.

Zoom feature availability The zoom feature is only available when a user is logged into thecoprocessor environment. The software action is performed as part of the Xwindow environment and does not effect operation of the application withinthe window.

Zoom touchscreen The touchscreen on the Universal StationX is supplemented by software toaid in selecting small targets in high resolution display. On the initial touch aboundary is created approximately 3 inches around the target area. This willshow a zoomed-in view of the screen around your finger. As you moveyour finger, the image moves one half the distance.

The proper method of using the zoom touchscreen is to place your finger on(or as close to) the desired target as possible. This is to reduce the amountof finger movement necessary allowing selection of targets close to thescreen border. It is important to watch the zoomed view, as the 2:1 ratio offinger to image movement is confusing at first.


Section 4 – Universal StationX Operations

4.1 Power-On (Procedure)

Apply power Apply power using the following steps:

Step Action

1 Open front access door to gain access to the circuit breaker.

2 Place the circuit breaker in the ON position.

3 Open the rear access door to gain access to the 5-slot module.

4 Apply power to the station, using the power switch on the 5-slotmodule face plate.

5 Observe the K2LCN board LEDs during the power on self-test. If noerrors are detected, the appropriate LCN node address is displayed.

6 If the appropriate LCN node address is displayed:Proceed with Step 7.

If another number is displayed:Record the error number for maintenance personnel to assist incorrecting the fault. Proceed with Step 9.

7 The Login banner should appear within 5 minutes.

8 If the Login banner does appear:Proceed to subsection 4.2, Accessing Co-Processor Functions.

If the Login banner has not appeared:Proceed with Step 14.

9 The Login banner should appear within 5 minutes.

10 If the banner does appear:Proceed to Step 11 to shut down the coprocessor.


11 Position the cursor in the Login box and typeusername <RETURN>

Note: The user must be authorized to shutdown the WSI.

12 Position the cursor in the Password box and typepassword <RETURN>

Note: Replace password with your password.

13 Click the Shutdown WSI target.

14 Using the power switch located on the 5-slot module faceplate,remove power from the 5-slot module. Set the station circuit breakerto the OFF position. Contact maintenance to correct the error.


4.2 Accessing Universal StationX Coprocessor Functions(Procedure)

Coprocessor accessbanner

After power ON (3 to 5 minutes) the Universal StationX will display abanner on the lower portion of the screen.

This banner allows access to:

• X windows environment

• Shutdown of the coprocessor

• Universal StationX Native Mode operation.

These items are user and password restricted to maintain security andrestrict access to the coprocessor or LAN environment.

Using the accessbanner

Using the touchscreen:

Step Action

1 Touch the Login field.

2 Type your username <RETURN>

3 Type your password

4 To Login:Press <RETURN>

To Shutdown the Coprocessor:Touch the Shutdown WSI target and select it with the space bar.

To revert to Standard Universal Station Operation:Touch the Native Mode target and select it with the space bar.

Using the mouse or trackball:

Step Action

1 Select the Login field by placing the cursor over the field.

2 Type your username <RETURN>

3 Type your password

4 To Login:Press <RETURN>

To Shutdown the Coprocessor:Select the Shutdown WSI target.

To revert to Standard Universal Station Operation:Select the Native Mode target.


4.3 Loading a Personality to the LCN Processor

Capabilities The Universal Personality has been encapsulated in a “Windowsenvironment” to form the UNPX Personality stored on the coprocessorhard drive. This integration enables the Universal StationX to function aseither a Universal StationX or a standard TDC 3000X Universal Station.

The X-window capabilities are available only when functioning as aUniversal StationX. As a Universal StationX, the presentation of all displayswill be controlled by the X windows/Motif Window Manager to provide theaddition of such items as: title bar, zoom box, and scroll bars.

Hardware tests A fully operational Universal StationX system can use the UNPXpersonality. When power is applied, the system performs a series ofinternal self-tests. These tests check the presence and condition of both theTDC and coprocessor hardware. The results determine the loading actionavailable, when <Load> is pressed.

If test result is ... then loading action available is ...

TDC and coprocessor hardware OK UNPX personality from hard drive orUNP, ENG, or OPR from HistoryModule

TDC hardware OK/coprocessor testfailure

UNP, ENG, or OPR from HistoryModule or Removable Media

TDC and coprocessor hardware failure No loading performed

Loading the personality The Universal StationX may be loaded from several sources:

• History Module• Removable Media (cartridge or floppy)• Internal coprocessor hard drive

The Universal StationX may be loaded from other consoles (UniversalStationX or US) on the LCN. However, the hardware tests will control theappropriate prompt. For example, failure of the coprocessor will inhibit theload prompt from displaying the appropriate choice (W).

The actual loading is achieved through the standard TDC loadingprocedures. However, when loading from the coprocessor (W), only theUniversal Personality is available. NOTE: For Universal StationX

functionality the LCN processor must be loaded from the coprocessor. Thefollowing personality types are available from the History Module orRemovable Media:

• OPR• ENG• UNP



4.3 Loading a Personality to the LCN Processor, Continued

Load the LCNprocessor

Using the following, load the LCN processor:

Step Action

1 If the access banner is on the screen:Press <Load> on the operator keyboard.

If you are already logged in:Select the Native LCN Window, press <Load> on the operatorkeyboard.

2 At the prompt W, N, 1, 2, 3, 4, X type W <RETURN>

3 The load modules will be displayed as the LCN processor is loaded.

4 At the prompt NCF? type N <RETURN>

5 The station will complete the load process in 1 to 2 minutes.


4.4 Printing from the Universal StationX

Two printers The Universal StationX has two printer connections.

The standard LCN printer connection provided to print LCN displays andreports is configured as a standard Universal Station printer. This printer isfunctional whenever the station is in operation. The LCN printer can beconnected directly to a Universal StationX or assigned from another stationin the console (US or Universal StationX). Standard UniversalStationX operating procedures apply to the printing of reports, alarmsummaries, configuration data, print displays, etc.

The coprocessor has a printer connection provided to print window dumpsof X Window applications. This printer is available only when the user islogged into the coprocessor, however printing will still continue afterlogging out. This printer will not print the various Universal Station Printerfunctions of alarm summaries, reports, etc. The coprocessor printer can bedirectly attached to this Universal StationX or shared across the LAN fromanother Universal StationX.

Printing the LCNwindow

The LCN processor must be active to print. The user can be logged into thecoprocessor but it is not required to print LCN data.

To print the LCN window on the LCN printer, use the following:

Step Action

1 If logged into the coprocessor:Select the LCN window.

2 Press the Print Display key.

Printing X Windows When the user is logged into the coprocessor, the coprocessor printer canbe used to print any window contents. To print to a shared printer, thecoprocessor of the Universal StationX sharing the printer must be active(login banner displayed or a user logged in).

To print any X Window on the coprocessor printer, use the following:

Step Action

1 Select Window Print from the workspace menu.

Note: The cursor will change to a cross-hair pointer.

2 Position the cursor in the appropriate window to print.

3 Click the select button.

4 The printing of the display can take 5 to 10 minutes.


4.5 Failsafe Operation

Failsafe fall back The Universal StationX is designed to be failsafe. Should an error occur inthe coprocessor, the Universal StationX reverts to a standard TDCUniversal StationX hardware/software configuration. If this should occur,the LCN display will revert to full screen and the messageCoprocessor has failed to start, Call maintenancewill be displayed in place of the Login banner.

When functioning as a standard Universal Station, you will be unable toaccess LAN (Local Area Network) resident applications.

Native mode The Universal StationX can be configured as a standard Universal StationX

by selecting Native Mode from the Login banner. To enter Native Mode,the user must be authorized using the procedures covered in IWSMConfiguration, Universal StationX System Administration Manual.

Manual shutdown The coprocessor can be shut down after power-on using theShutdown WSI target located on the login prompt. This action can also beperformed by logging out of the open system session and waiting for thelogin prompt to appear.

To invoke the failsafe condition:

• At the login prompt, enter your login name/password and select theShutdown WSI target.

Shutdown restriction To shutdown the WSI, the user must be authorized using the procedurescovered in IWSM Configuration, Universal StationX SystemAdministration Manual.

Restarting aftershutdown

After the coprocessor has been shutdown, a status message will appear inthe Login banner area. The message is:The coprocessor is idle, select the box to reset.

There is a red box to the right of the status message. Using the mouse, clickon the box to reset the coprocessor.


4.6 Universal StationX Display Changes

TDC display changes Several changes are apparent when operating from the Universal StationX.Some changes are due to TDC software Release 410, and are not UniversalStationX inherent.

• Console and Node Status DisplaysA field for the personality type has been added. The node status is notoverwritten by personality type when status is OK.

• Console Status DisplayAbility to choose the personality which is loaded to a UniversalStationX has been added. The autoload_net target determines thedefault personality to load by testing the hardware.

• Real Time Journal ChangesThe System Maintenance Journal is updated with additional messagesto support the new TPDG hardware. The System Status ChangeJournal will be updated with a new message—State ChangeNotification (SCN) to establish the personality subtype in a node.


4.7 X Window Operation

Background The Universal StationX is configured to launch the X window environmentupon login. Once the system has initialized, the primary LCN displaywindow appears. At this time you can start an X window session withLAN resident computing resources.

Pre-requisites The LAN computing resources must be configured to allow access from theUniversal StationX. In general terms, the following information is requiredby the LAN hardware and/or application software:

• Universal StationX internet address

• System name

• User name/password for its login

LAN access protocols To access LAN resident applications you will use one of thesecommunication protocols:

Protocol Accessed by . . . Access Level Required

DECnet DECnet from root menu Operator, Supervisor, Engineer

TELNET TCP/IP TELNET from root menu Operator, Supervisor, Engineer

Procedure LAN resident applications may not be Honeywell supplied; therefore, theseaccess procedures are general in nature.

Step Action

1 Login with the appropriate access capabilities.

2 Select the appropriate communication protocol from the X Menu.

NOTE: If you cannot determine the appropriate protocol, consultyour LAN administrator.

3 Place the cursor in the new communication window.

4 Type the commands provided by your LAN administrator.

5 The application is launched in this window.

NOTE: Follow the LAN administrators instructions on closing the application.

Keyboard mapping The operator and engineer keyboards are both active and can be used fortext entry.

When using xterm, the engineer's keyboard mapping is altered to utilize thePF1 through PF17 keys. This alteration occurs only when the pointer is in axterm window and enhances DECnet emulation.


4.8 System Security

TDC isolated The TDC operating system is isolated and inaccessible to the coprocessor.This eliminates the possibility of misuse/tampering with the process controlsystem by unauthorized personnel who may gain access to the Local AreaNetwork.

The full implementation of HP-UX version 8.0 security features areprovided. System security is controlled through the configuration and loginutilities.

Configuration Configuration parameters ensure only designated computer systems will beable to login to the Universal StationX. This allows multiple computersystems to exchange data transparently while ensuring data integritythrough limited authorized access.

The coprocessor password should be changed and recorded during initialconfiguration. This password is the highest level of system access, andsystem security must be enforced by good password discipline.

Login A password controlled login utility protects against unauthorized UniversalStationX coprocessor usage. This utility configures access dependent on theuser login identification. The system customizes the workspace menu asappropriate to the access level of the user. Access to additional items can beprovided to individual users by modifying the .mwmrc file in the usershome directory.

Access keylock versuscoprocessor login

This login utility performs a function similar to the Access Level Keylockon the standard Universal Station; however, the coprocessor login isentirely independent from the keylock mechanism. System security may becompromised if the user leaves the immediate area without logging out ofthe coprocessor environment.

It is suggested to remove the key and logout to ensure security. This willeliminate unauthorized access to the LCN system and the coprocessor.

Security emphasis Users should be advised of the potential for security problems. A periodicreview of the system security, security procedures, and system users willhelp to raise awareness. Remind users that the password is their computersignature. Emphasize the importance of periodically changing thispassword.



4.8 System Security, Continued

Coprocessor access bygroup

The restrictions placed upon access levels are:

• Operator—able to configure their own environment, use telnet, and theoptional VT340 DECnet communications

• Supervisor—able to configure their own environment, use telnet, and theoptional VT340 DECnet communications

• Engineer—able to configure their own environment, use telnet, theoptional VT340 S/W, coprocessor configuration (requires coprocessorpassword), and perform periodic backups of the coprocessor file system

• View Only—able to configure their own environment.

Note: User-configurable items are: X Hosts, allowPartiallyObscured NativeWindow, and Keyboard Focus Policy.

Configuration To configure the coprocessor security features, review the procedures,gather the required information, and perform all tasks in Section 7,Universal StationX Configuration.


4.9 Shut Down the Universal StationX

Background To prevent damage to the UNIX filesystem, the station must be shut downusing a special sequence. The shutdown procedure must be followed beforepower is removed from the station.

Failure to perform the proper shutdown procedure could result in damage tothe coprocessor filesystem. The next time the station is powered up, it maytake up to 5 minutes to perform automatic repairs of the coprocessorfilesystem. Use caution in cycling power on and off. If this is done while arepair is being made, the filesystem may be left in an unrepairable state.This would require reloading the filesystem backup from tape and possiblyrequire reformatting or replacement of the hard drive.

Procedure If you are currently logged into the Universal StationX, use the followingprocedure:

Step Action

1 Select Logout from the workspace menu.

2 At the prompt Quit Mwm?, select the OK target.

3 When login menu appears, enter your username and password.

4 Select SHUTDOWN WSI target.

5 Press the CONSOLE STATUS key.

6 Select the node number of the appropriate Universal StationX.

7 Select the SHUTDOWN target.

8 Press ENTER to confirm the shutdown request.

Note: The message Coprocessor is idle, select box to reset.will appear. Reset the coprocessor by selecting the box.

If no user is logged into the Universal StationX, use the followingprocedure:

Step Action

1 When login menu appears, enter your username and password.

2 Select the SHUTDOWN WSI target from the login menu.

3 Press the CONSOLE STATUS key.

4 Select the node number of the appropriate Universal StationX.

5 Select the SHUTDOWN target.

6 Press ENTER to confirm the shutdown request.

Note: The message Coprocessor is idle, select box to reset.will appear. Reset the coprocessor by selecting the box.


4.10 Universal StationX Restrictions

Shutdown procedure Because the coprocessor operating system is incorporated into the UniversalStationX, the station must be turned off using a special sequence. Theshutdown procedure must be followed any time power is to be removedfrom the station.

Failure to perform the proper shutdown procedure could result in damage tothe coprocessor filesystem. The next time the station is powered up it maytake 5 minutes to perform automatic repairs to the coprocessor filesystem.Use caution in cycling power on and off. If this is done while a repair isbeing made, the filesystem may be left in a unrepairable state. This wouldrequire reloading the filesystem backup from tape, and possibly requirereformatting or replacement of the hard drive.


4.11 Problem Reporting

Service contacts If you encounter any problems please contact:

Honeywell IAC - Technical Assistance Center16404 North Black Canyon HighwayPhoenix, AZ 85023Phone (602) 863-5558Phone (800) 822-7672


Section 5 – Coprocessor Configuration Tasks

5.1 Configuration Overview

LCN requirements The Universal StationX requires TDC 3000X software Release 410. TheUniversal StationX does not place any new requirements on LCN softwareor hardware. Approach the Universal StationX planning and implementationtasks as a standard Universal Station. All the LCN conventions forUniversal Station implementation apply to the Universal StationX such as:node addressing, HM volume allotments, and NCF changes.

The Universal StationX uses all LCN schematics/overlays without any dataconversion. The Universal Station and Universal StationX are equivalentsas TDC 3000X Process Control Computers. The Universal StationX canload the standard personalities (UNP, ENG, and OPR) from the HistoryModule or Removable Media, and also can load the UNPX personalityfrom the coprocessor hard drive.

When loading the UNPX from the coprocessor hard drive, the buttonoverlays, abstracts, schematics, and NCF are all read from the HM. Thecoprocessor hard drive stores only the QLTs and UNPX files for theK2LCN processor. The additional files cannot be stored on the coprocessorhard drive and must be loaded from the HM or Removable Media.

Currently, the UNPX personality is the functional equivalent of the UNPstored on the History Module; however, pending UNPX enhancements,provide functionality to the Universal StationX that will not be available atthe US.

NCF changes Several fields were added to the NCF (Network Configuration File) tosupport Release 410. The NCF must be modified to reflect the UniversalStationX installation. This is done by following the standard NCFmodification instructions available in the R410 Release Guide.

The changes to the NCF reflect the Universal StationX LCN node address,LCN node configuration, and console assignment must be completed priorto applying power to the station.

The NCF has the following changes: new personality type—UniversalStationX, new board type—TPDG, new board type—WSI.

The SMCC (System Maintenance Control Center) has the following change:new board type—TPDG.



5.1 Configuration Overview, Continued

Coprocessorconfiguration

The major difference when compared to a Universal Station is the UniversalStationX's ability to display non-TDC 3000X applications, generated byLAN (Local Area Network - Ethernet) computing resources. The TPDGboard works in tandem with the coprocessor, providing the TDC display asan X client, which then is displayed through the X-window/Motifenvironment.

There are several attributes new to the TDC display, which are necessitatedby viewing in the X-window environment.

Installation complete? This procedure assumes the Universal StationX equipment to be properlyinstalled and ready to apply power.

The following items must be completed, prior to the initial power on/login:

• Uncrating/positioning of the Universal StationX equipment.

• Ground connections (power, cabinet, and Master Reference Ground)

• LCN node address pinning

• LCN cable connections

• LAN interface cable and transceiver attached to the Ethernet network

• Universal StationX keyboard connection

• Universal StationX mouse/trackball connection

• LCN printer connection (optional equipment)

• Laser printer connection (optional equipment)

• Visual inspection of all boards/cables to ensure proper seating

• Power Connection




Make a copy You will find it convenient to make a copy of the following lists forreference when performing the configuration procedures.

Required information The information required to complete this process is listed below.

Desired hostname for the Universal StationX Desired IP address Time/Date/Timezone Multiple network routers (Yes/No)(Single router only) IP address of router

Remote computer system information can be input in one of two ways:1) Hostname and IP address for each when entered manually.

hostname ###.###.###.###

2) Source of existing /etc/hosts file when using FTP.IP address of source Login account at source Password for account

Coprocessor laser printer? (Local/Remote/Unused)If Remote - Network information needed

Hostname of print server IP address of print server Printer name




Required information,continued

Coprocessor user informationUsername/Access Group johndoe/Engineer

Shutdown WSI access username

Native mode access username

X hosts to be accessed hostnames




Required information,continued

Desired coprocessor password

Note: This password is extremely important. It is the key to yourcoprocessor security. Secure this document and control its accessafter completing the initial configuration.

Configuration checklist Use this checklist to plan and record the various configuration tasks.

Step Initials Step performed Section Approx. time

1 Ensure installation complete?

Uncrating/positioning of theUniversal StationXequipment.

Ground connections (power,cabinet, and MasterReference Ground)

LCN node address pinning

LCN cable connections

LAN interface cable andtransceiver attached to theEthernet network

Universal StationX keyboardconnection

Universal StationXmouse/trackball connection

LCN printer connection(optional equipment)

Laser printer connection(optional equipment)

Visual inspection of allboards/cables to ensureproper seating

Power connection

Information prepared

N/A 1 hour

2 Initial power on completed? 5.2 3-5 minutes

3 Initial login completed? 5.3 2-3 minutes

4 Time/date/timezone entered? 5.4 15 minutes

5 Hostname and IP address of thisstation entered?

5.5 2-3 minutes




Configuration checklist,continued

Step Initials Step performed Section Approx. time

6 Remote hostnames and addressesentered?

Optional MethodSee subsection 7.1, AlternativeMethods

5.5

7.4 or 7.6

3-20 minutes

2 minutes

7 Network routing configured? 5.6 1-15 minutes

8 Laser printer configured? 5.7 or 5.8 7-10 minutes

9 Optional Custom ConfigurationsSee subsection 7, AlternativeMethods

7 1-8 hoursestimated

10 Coprocessor users configured? 5.9 - 5.11 0-30 minutes

11 Shutdown WSI access configured? 5.12 2-30 minutes

12 Native mode access configured? 5.12 2-30 minutes

13 Coprocessor password changed? 5.16 2-3 m minutes

14 Optional software loaded/configured? 5-45 minutes

15 Coprocessor filesystem backed up? 5.17 15-90minutes

16 Recovery tapes created and stored? 9.11 2-3 hours


5.2 Initial Power-On

Apply power Apply power using the following steps:

Step Action

1 Open front access door to gain access to the circuit breaker.

2 Place the circuit breaker in the ON position.

3 Open the rear access door to gain access to the 5-slot module.

4 Apply power to the station, using the power switch on the 5-slotmodule face plate.

5 Observe the K2LCN board LEDs during the power on self-test. If noerrors are detected, the appropriate LCN node address is displayed.

6 If the appropriate LCN node address is displayed:Proceed with Step 7.

If another number is displayed:Record the error number and contact maintenance personnel tocorrect the fault. Proceed with Step 9.

7 Wait 5 minutes for the Login banner to appear.

8 If the Login banner does appear:Proceed with subsection 5.3, Initial Login.


9 Wait 5 minutes for the login banner to appear.

10 If the banner does appear:Proceed with Step 11 to shut down the coprocessor.


11 Position the cursor in the Login box and type root <RETURN>

12 Click on the Shutdown WSI target.

13 Using the power switch located on the 5-slot module faceplate,remove power from the 5-slot module.

14 Set the station circuit breaker to the OFF position. Contactmaintenance to correct the fault.


5.3 Initial Login

Preconfigured users The Universal StationX coprocessor environment is preconfigured with oneuser in each of the four groups. The initial login passwords of thepreconfigured users should be changed to ensure security.

The steps for changing the preconfigured user passwords are presentedfollowing the initial configuration procedures covered in this section.

Coprocessor password The coprocessor itself must be password protected; however, to easeinstallation it is shipped without a password. During initial installationprocedures, the coprocessor has no password. When asked to type thepassword, press <RETURN>.

Only users with Engineer Access rights have configuration access to thecoprocessor environment. Prior to obtaining access, however, the usermust provide the coprocessor password.

The steps for changing the coprocessor password is presented following theinitial configuration procedures.

Initial login passwords The preconfigured user names and passwords are as shown:

User Name Password Coprocessor Access

engineer engineer Engineer Access

operator operator Operator Access

supervisor supervisor Supervisor Access

viewOnly viewOnly View-Only Access

Coprocessorconfiguration password

No Password EnteredBLANK

CoprocessorConfiguration Access

Login Login as the user “engineer,” using the steps below:

Step Action

1 Position the cursor in the Login box and type engineer <RETURN>

NOTE: After pressing <RETURN>, the password box will be selected.Do not move the mouse/trackball. If the cursor is moved, it will benecessary to reposition the cursor over the password box.

2 Type the password engineer <RETURN>.


5.4 Configure Coprocessor Time and Timezone

Required access level The procedures must be performed while logged in as “engineer.” Thecoprocessor password is required.

Menu appearance

Configuration

IWSM Configuration

LAN Configuration

Set Time/Timezone

Gated Daemon >

System Commands

Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

Engineer Menu

X Menu >

Application >

System Menu >

12593

Set time/timezone Set the time, date, and timezone using the following procedure.

Step Action

1 Select Set time/timezone from the System Configuration menu.

2 Type the coprocessor password and <RETURN> at the prompt.

NOTE: This will not be necessary on a new station.

3 Respond to the prompts using the appropriate keyboard entry and<RETURN> to enter values.

4 When you have completed entering the information, you will beasked if you want to reboot the system.Type Y and press <RETURN>.

NOTE: After completing this step, a few seconds will pass before thesystem reboots. When the system shuts down, DO NOT SELECTTHE RED TARGET. THE COPROCESSOR SHOULDAUTOMATICALLY REBOOT.

It is a good idea to reboot the system after entering date and time.This will ensure that the system uses the correct time and date fortime dependant functions such as cron, and file time stamps.


5.5 Configure Coprocessor LAN Information


Menu appearance

Configuration

IWSM Configuration

System Configuration

Set Time/Timezone

Gated Daemon >

Engineer Menu

X Menu >

Application >

System Menu >System Commands

Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

12594

Enter LAN information The coprocessor hostname,TCP/IP address, TCP/IP subnet mask, remotehostnames, and their TCP/IP addresses are set using the followingprocedure:

Step Action

1 Select System Configuration from the workspace menu.



3 Use the arrow keys and <RETURN> to make selections.

Select Networks/Communications <RETURN>.

4 Select LAN Hardware and Software <RETURN>.

5 Select View/Modify a LAN Card’s Configuration<RETURN>.

6 Enter up to eight characters for your station name.

NOTE: This will be necessary only on a new station.

7 Using the arrow keys to move the cursor, type the TCP/IP addressinto the IP address field.

8 If alias names are desired for this station, type them into the aliasesfield.

NOTE: Hostnames can consist of a maximum of 64 alphanumeric,underscore, and period characters.



5.5 Configure Coprocessor LAN Information, Continued

Enter LAN information,continued

Step Action

9 If this station is to be placed on a subnet, enter Y, and the appropriatesubnet mask.

10 Select Perform Task.

11 Press the space bar.

12 Select NFS (Network File System) Configuration<RETURN>.

13 Select Add/Modify Connectivity Info about a RemoteSystem <RETURN>.

14 Type the hostname into the hostname field.

15 Type the IP address for the remote system into the IP address field.

16 If you wish to use an alias to the full hostname, type it into thehostname aliases field.



19 Repeat Steps 14 through 18 for each additional system.

20 Select Exit Task.

21 Select Main Menu.

22 Select Exit SAM and the window will close.


5.6 Configure LAN Routing Information

Routing choices The Universal StationX coprocessor may be configured for either static ordynamic routing of LAN information.

If the LAN uses multiple routers and stations that are configured withsubnet masks, it will be necessary to configure the gated daemon ON. Thecoprocessor will interrogate the routers and use the routers dynamic routingtable information.

If the LAN has no routers or only one router, the gated daemon should beconfigured OFF; the hostname and TCP/IP address for the default gatewayshould be configured.


Menu appearanceEngineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

Configuration

IWSM Configuration


Set Time/Timezone

Gated Daemon > On

Off

12595



5.6 Configure LAN Routing Information, Continued

Setup of static LANrouting

The Universal StationX is configured for static routing. The default gatewaycan be set using the following procedure:

Step Action





Select Networks/Communications <RETURN>.

4 Select LAN Hardware and Software <RETURN>.

5 Select NFS (Network File System) Configuration<RETURN>.

6 Select Specify the Default Gateway <RETURN>.

7 Using the arrow keys to move the cursor, type the hostname for thedefault gateway into the Default Gateway Hostname field.

8 Type the TCP/IP address into the Default Gateway IP address field.





The coprocessor is now setup to use this default router.

Setup of dynamic LANrouting

If multiple gateways are used, use the following procedure to invokedynamic routing.

Step Action

1 Select On for the Gated Daemon from the workspace menu.


NOTE: No password is required for a new station - just press<RETURN>

After completing this step, the system will reboot. When the systemshuts down, DO NOT SELECT THE RED TARGET. THECOPROCESSOR SHOULD AUTOMATICALLY REBOOT.


5.7 Configure Coprocessor Printer (Local)

Local printer install This procedure will configure a local coprocessor printer. This printer willbe available to other Universal StationX stations, which are configuredusing the procedure in subsection 5.8, Configure Coprocessor Printer(Remote).


Menu appearance

Configuration

IWSM Configuration


Set Time/Timezone

Gated Daemon >

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

12594

Configure laser printer Configure the coprocessor laser printer using the following procedure:

Step Action





Select Peripheral Devices <RETURN>.

4 Select Printers and Plotters <RETURN>.

5 Select Add a local printer <RETURN>.

6 Using the arrow keys to move the cursor, type the information into thecorresponding fields.

7 Printer name laserjet

8 Printer model/interface laserjet

9 Printer device file name /dev/lp0

10 Printer priority 0



5.7 Configure Coprocessor Printer (Local), Continued

Configure laser printer,continued

Step Action

11 Make this the system default printer y



14 Do you wish to test the printer? y


Wait for the test to complete.


17 Type n.




Printer Server? If the laser printer will be shared among Universal StationX stations, locatethe following line (using vi) in the /etc/rc file:

# /usr/bin/slp -i0 > /dev/lp

Add the following lines after the previous line:

# ADDED TO START THE PRINT SPOOLER DAEMON/usr/lib/rlpdaemon


5.8 Configure Coprocessor Printer (Remote)

Remote printer install This procedure will configure the coprocessor to use a printer attached to aremote Universal StationX station. This printer must have been configuredat the local station, using the procedure in subsection 5.7, ConfigureCoprocessor Printer (Local).


Menu appearance

Configuration

IWSM Configuration


Set Time/Timezone

Gated Daemon >

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

12594

Configure laser printer Configure the coprocessor laser printer, using the following procedure:

Step Action




Select Peripheral Devices <RETURN>.

4 Select Printers and Plotters <RETURN>.

5 Select Add a Remote Printer <RETURN>.

6 Using the arrow keys to move the cursor, type the information into thecorresponding fields.

7 Printer name laserjet

8 Remote system name hostname

9 Remote printer name laserjet

11 Make this the system default printer y



5.8 Configure Coprocessor Printer (Remote), Continued

Configure laser printer,continued

Step Action

12 Select Perform Task


14 Do you wish to test the printer? y


Wait for the test to complete.


17 Type n.





5.9 Industrial Workspace Manager (IWSM) Configuration



X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

Configuration

IWSM Configuration

LAN Configuration

Set Time/Timezone

Gated Daemon > 12596

IWSM configuration toolIWSM Configuration

Grant users permission to...

Enter Native Mode

Shutdown the WSI

Add Delete Close

TEXT ENTRY AREA

DISPLAY AREALISTS CO-PROCESSOR USERS ALLOWED TOPERFORM THE ACTION SELECTED ABOVE.

*ALL* rootThisHostname rootlocalhost usernameThisHostname username

12597



5.9 IWSM Configuration, Continued

Shutdown WSIauthorization

Use the following procedure to authorize specific users to shutdown thecoprocessor:

Step Action

1 Select IWSM Configuration from the workspace menu.


NOTE: On new systems, leave the password field blank and selectthe OK target.

3 Select the Shutdown the WSI target.

4 Select the text entry area of the IWSM Configuration Tool. (Justabove the ADD, DELETE, and CLOSE targets).

5 Type information using this syntax:

*ALL* usernameusername = users login name

Use a space to separate *ALL* from the user name.

6 Select the Add target to authorize the user to shutdown the WSI.

7 Repeat Steps 4 through 6 for each user requiring shutdownprivileges.

8 Select the Close target.

Remove Shutdown WSIauthorization

Use the following procedure to remove authorization to shutdown thecoprocessor from specific users:

Step Action



NOTE: On new systems, leave the password field blank and selectthe OK target.

3 Select the Shutdown the WSI target.

4 Select the username to be deleted.

5 Select the Delete target.

6 Repeat Steps 4 and 5 for all users to be Deleted.




5.9 IWSM Configuration, Continued

Native modeauthorization

Use the following procedure to authorize specific users to enter nativemode:

Step Action



3 Select the Enter Native Mode target.

4 Click on the text entry area of the IWSM Configuration Tool.


*ALL* usernameusername = users login name

Use spaces to separate hostname from the user name.

6 Click on the Add target to authorize the user to Enter Native Mode.

7 Repeat Steps 4 through 6 for each user requiring Native Modeprivileges.

When all users are entered, proceed to Step 11.

8 To delete native mode authorization privileges, click on the usernameto be deleted.

9 Click on the Delete target.

10 Repeat Steps 8 and 9 for all users to be Deleted.



5.10 Change Coprocessor Password


Menu appearance

Configuration

IWSM Configuration


Set Time/Timezone

Gated Daemon >

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

12594

Change thecoprocessor password

Change the coprocessor environment password to ensure security.

Step Action





Select Users <RETURN>.

4 Select Change a Users Password <RETURN>.

5 Type root into the window that appears <RETURN>.

6 Type a new password into the window provided <RETURN>.

7 Confirm the password choice by retyping the chosen password<RETURN>.


9 Select Exit Window.


11 Select Exit SAM


Section 6 – Coprocessor User Environment Configuration

6.1 User Configuration Overview

Coprocessorconfiguration

The major difference, when compared to a Universal Station, is theUniversal StationX's ability to display non-TDC 3000X applications,generated by LAN (Local Area Network - Ethernet) computing resources.

There are several attributes new to the Universal StationX display, whichare necessitated by viewing in the X Windows environment:

• X Host Authorization—Controls remote access to the Universal StationX

display

• Native Window Behavior—Controls dominance of the LCN display

• Keyboard Focus Policy—Controls keyboard/mouse pointer interaction

Required information The following information is required for configuration:

• The hostnames of any remote computing resources which will open an Xdisplay on this station. This access is granted on a user-by-user basisusing subsection 6.2, X Host Authorization.


6.2 X Host Authorization

What is it? The X host authorization application grants X display permission to remotesystems on an individual-user basis. This allows other computer systems toopen a window on the user's Universal StationX display.

Required access level The procedures can be performed by any authorized user. Thisauthorization is granted/recorded on an individual-user basis.


X Menu >

Application >

System Menu >

X Menu

Shuffle >

Native Window >

Keyboard Focus Policy >

X Host Authorization

Refresh

Restart...

Logout

12598

X Host toolX Host Authorization

Only the listed hosts are allowed access

Any host is allowed access

DISPLAY AREALISTS HOSTNAMES AUTHORIZED TO SENDAN X-WINDOW DISPLAY TO THIS STATION.

hostnamehostnamehostname

Add Delete Close

TEXT ENTRY AREA

12599

X host addresses To authorize remote systems to display X Window applications on theUniversal StationX, the hostname and TCP/IP address must be entered priorto this step, using the LAN information entry procedure.



6.2 X Host Authorization, Continued

X host authorizationscope

The user can choose from two methods of granting access permission:

• Explicit host authorization—user must enter the hostnames of all systemsrequiring access

• Grant access to all hosts—user selects Any host is allowed access

Explicit hostauthorization

Use the following to authorize specific X hosts access:

Step Action

1 Select X Host Authorization from the workspace menu.


3 Select Only the listed hosts are allowed access target.

4 Click on the text entry area of the IWSM Configuration Tool.


hostnamehostnamehostnamehostnamehostname = replace with a valid hostname

Use of spaces is not allowed. The tool does nothing if there areinvalid characters in the text entry field.

6 Click on the Add target to authorize the remote host to display locally.

7 Repeat Steps 4 through 6 for each host requiring X host access.

8 To delete a host’s X display authorization privileges, click on thehostname to be deleted.

9 Click on the Delete target.

10 Repeat Steps 8 and 9 for all hosts to be Deleted.




6.2 X Host Authorization, Continued

Allowing all X-hostsaccess

All LAN computing resources listed in the hosts file can be authorized todisplay X-window applications on this station using the followingprocedure.

Step Action

1 Select X Host Authorization from the workspace menu.


3 Select the Any host is allowed access target.



Only the listed hosts are allowed access

Any host is allowed access

DISPLAY AREALISTS HOSTNAMES AUTHORIZED TO SENDAN X-WINDOW DISPLAY TO THIS STATION.

hostnamehostnamehostname

Add Delete Close

TEXT ENTRY AREA

12600


6.3 Configure Native Window Behavior

Window dominance The dominance of the Native LCN Window is configurable on a user-by-user basis. The attribute allows the Native LCN Window to be partiallyobscured by another window.

The Native LCN Window behavior is initially configured to allow onlyengineering group members to partially obscure the LCN display.However, the individual users (all access levels) can set this attribute at theirdiscretion.

Menu appearanceOperator Menu

X Menu >

Application Menu >

X Menu

Shuffle >

Native Window >



Refresh

Restart...

Logout

Native Window

Partially Obscured > Allow

Disallow

12601

Allow partial obscured Follow these steps to allow the LCN display to be partially obscured:

Step Action

1 Select Native Window - Partially Obscured - Allowfrom the workspace menu.

Note: The change will not take effect until the next login.

Disallow partialobscured

Follow these steps to prevent obscuring the LCN display:

Step Action

1 Select Native Window - Partially Obscured - Disallowfrom the workspace menu.



6.4 Configure Keyboard Focus Policy

Required access level The procedures must be performed while logged in as the user.

Menu appearance

X Menu

Shuffle >

Native Window >



Refresh

Restart...

Logout

Operator Menu

X Menu >

Application Menu >

Explicit

Pointer

12602

Explicit vs. Pointer The keyboard focus policy allows two choices:

• Explicit focus—user must click on a window to make it active

• Pointer focus—user must point at the window to make it active

Note: Even small mouse movements may inactivate the windowwhen using pointer focus. This may cause keyboard entries tobe lost or directed to the wrong window.

Explicit focus Use the following to set the focus policy to explicit:

Step Action

1 Select Keyboard Focus Policy - Explicit from theworkspace menu.


Pointer focus Use the following to set the focus policy to pointer:

Step Action

1 Select Keyboard Focus Policy - Pointer from the workspacemenu.



6.5 Change User Password

Required access level The procedures must be performed while logged in as the user. The currentpassword is required.

Menu appearanceOperator Menu

X Menu >

Application >

System Menu >

Applications

Unix Load

Calculator

Datebook

Telnet

DECnet

Change Password12603

Change theuser password

Change the user password frequently to ensure security.

Step Action

1 Select Change Password from the workspace menu.

2 Type the old password and <RETURN> at the prompt.

Note: The new password must be at least 6 characters, containingat least two alpha characters and one numeric character.

3 Type a new password and <RETURN>.

4 Retype the new password and <RETURN> to confirm the entry.


Section 7 – Alternative Coprocessor Configuration Methods

7.1 Alternative Method Overview

Why alternatives? Custom configurations and multiple Universal StationX installations requirespecial procedures to duplicate the necessary items among all users andsystems. These procedures and their concepts can be used to ensure that allsystem configurations are exactly duplicated.

Custom configuration The Universal StationX coprocessor configuration can be customized toalter the standard user environment. This could include:

• Providing custom workspace menu choices

• Altering shell variables (path, terminal, prompt, etc.)

• Automatically mounting remote filesystems (HP LaserRom)

• Automatically running applications at login

Customizing the files which control the coprocessor environment should bedone prior to registering users. When the customization is completed, theusers can be registered and additional systems loaded with the customconfiguration.

Network backup/restore Configuration is necessary to utilize a DAT drive on another UniversalStationX. This access is provided on a user-by-user basis by modifying theusers .Xdefaults file. Access can be provided to the entire group(Operator, Engineer, and Supervisor) by modifying the .Xdefaults filecontained in the .baseuser directory (before creating users).

See subsection 7.7, Network Backup/Restore Configuration.

Multiple UniversalStationX Installations

Configuration and administration of TDC 3000X Systems with multipleUniversal StationX stations using the procedures in Section 5, CoprocessorConfiguration could result in many hours of duplicated effort. Thisduplication would be costly and increase the possibilities of errors in dataentry.



7.1 Alternative Method Overview, Continued

Multiple UniversalStationX Installations,continued

For multiple Universal StationX installations, the procedures in Section 5,Coprocessor Configuration are followed to configure one UniversalStationX. One of two methods can then be used to duplicate theconfiguration:

• A backup of the configured system is restored to the new system.

Note: Backup and restore is the preferred method when all systemsshould be identically configured. See subsection 7.2 or 7.3,Backup/Restore Alternative.

• The configuration files are transferred using the FTP (File TransferProtocol) utility of Telnet.

Note: File transfer is the preferred method when each system will beuniquely configured. See subsection 7.4, FTP Alternative.

Backup and restore System configuration can be duplicated among systems using the backupand restore method. This will duplicate the system configuration entirely(system name, IP address, hosts file, customized files, users, optionalsoftware, etc.) and reduce the effort necessary to configure new systems.

File transfer Portions of configuration can be duplicated using FTP (File TransferProtocol) to transfer the configuration files between systems. Thisprocedure cannot duplicate the users (home directories) who were added tothe original system and, therefore, should be used only to transfercustomized .baseuser and individual user files.

Transferring files is a convenient approach to administration after thesystem has been in operation. For instance, to alter the engineering group’sworkspace menu, customize the file/users/XUS/engineer/.baseUser/.mwmrc; transfer the file to thedirectory /users/XUS/engineer/.baseUser of all UniversalStationX systems, and also transfer it to the home directories of all users inthe engineering group.


7.2 Backup/Restore Alternative (Local DAT Procedure)

Required configuration This procedure requires a DAT tape unit connected to the first UniversalStationX station to be configured. The station must be operational with fulluser login capabilities and connected to an Ethernet network accessible to allUniversal StationXs to be configured. If the Universal StationX to beconfigured does not have a DAT drive directly attached, perform theRemote DAT procedure in subsection 7.3, Backup/Restore Alternative(Remote Procedure).


Local DAT Procedure Use the following to duplicate system configuration from a local DAT drive:

Step Action

1 Configure one Universal StationX station according to Section 5,Coprocessor Configuration Tasks.

Note: Fully configure/customize this Universal StationX with all userinformation and test operation before continuing to Step 2.

2 Perform a Full Backup using the procedure in subsection 9.4,Backup the Coprocessor Hard Drive.

3 Go to the next Universal StationX to be configured and set theTime/Date using the procedure in subsection 5.4, ConfigureCoprocessor Time and Timezone.

4 Perform a Restore with Overwrite using the procedure in subsection9.5, Restore Coprocessor Hard Drive Data.


Note: This performs a set user to “root.”

6 Select the Shell target from the Configuration application.

7 Change the system name by editing the file (using the vi text editor)/etc/src.sh



7.2 Backup/Restore Alternative (Local), Continued

Local DAT Procedure,continued

Step Action

8 Change the Internet address by editing the file (using the vi texteditor) /etc/netlinkrc

9 If Kinet software (optional Decnet emulation) is installed, enter theKinet authorization number using the procedure found in Section 10.

10 Type exit <RETURN> to exit the shell.

11 Select the Exit SAM target from the Configuration application.

12 Select Logout from the Workspace menu.

13 Shutdown the WSI (Work Station Interface).

14 Restart the Coprocessor.

15 Login using a username which was configured on the original system.

Note: Consult Honeywell TAC if problems are encountered.

16 Repeat Steps 3 through 15 to configure each Universal StationX.


7.3 Backup/Restore Alternative (Remote DAT Procedure)

Required configuration This procedure requires a DAT tape unit connected to the first UniversalStationX station to be configured. The station must be operational with fulluser login capabilities, and connected to an Ethernet network accessible toall Universal StationXs to be configured. If the Universal StationX to beconfigured has a DAT drive directly attached perform the Local DATprocedure in subsection 7.2, Backup/Restore Alternative (Local Procedure).


Remote DATProcedure

Use the following to duplicate configuration from a remote DAT drive:

Step Action

1 Configure one Universal StationX station according to Section 5,Coprocessor Configuration Tasks.

Note: Fully configure/customize this Universal StationX with all userinformation and test operation before continuing to Step 2.

2 Perform a Full Backup using the procedure in subsection 9.4,Backup the Coprocessor Hard Drive.

3 Go to the next Universal StationX to be configured and set theTime/Date using the procedure in subsection 5.4, ConfigureCoprocessor Time and Timezone.




6 Change the System name by editing the file (using the vi text editor)/etc/src.sh






12 Restart the coprocessor.

13 Perform a Restore with Overwrite using the procedure in subsection9.5, Restore Coprocessor Hard Drive Data.





7.3 Backup/Restore Alternative (Remote DAT), Continued

Remote DATProcedure,continued

Step Action


17 Change the System name by editing the file (using the vi text editor)/etc/src.sh


19 If Kinet software (optional Decnet emulation) is installed, enter theKinet authorization number using the procedure found in Section 10.





24 Restart the coprocessor.

25 Login using a username which was configured on the original system.

Note: Consult Honeywell TAC if problems are encountered.

26 Repeat Steps 3 through 25 to configure each Universal StationX.


7.4 FTP (File Transfer Protocol) Alternative

Required configuration This procedure requires each Universal StationX station to be configured.The station must be operational with full user login capabilities andconnected to an Ethernet network accessible to all Universal StationXs towhich files are to be transferred.


Applicable files The files applicable to being transferred among systems can be divided intoseveral classifications:

• System configuration files

• Generic user-configuration files

• Specific user-configuration files

System files The following file may be transferred to assist system configuration:

• /etc/hosts

Generic user files Generic user files reside in a directory named .baseUser. When a newuser is created, these files are automatically copied to the users homedirectory. Altering a file in this directory will only affect subsequentlycreated users. Previously registered user’s home directories must beupdated manually using FTP.

There are four directories of generic files corresponding to the four groupsof access restriction level:

• Operator

• Engineer

• Supervisor

• View Only

Generic operator files The following files may be transferred to duplicate customized .baseUserconfiguration among systems.

• /users/XUS/operator/.baseUser/.Autost

• /users/XUS/operator/.baseUser/.Xdefaults

• /users/XUS/operator/.baseUser/.cshrc

• /users/XUS/operator/.baseUser/.environ

• /users/XUS/operator/.baseUser/.exrc

• /users/XUS/operator/.baseUser/.login

• /users/XUS/operator/.baseUser/.mwmrc



7.4 FTP (File Transfer Protocol) Alternative, Continued

Generic operator files,continued

• /users/XUS/operator/.baseUser/.profile

Generic engineer files The following files may be transferred to duplicate customized .baseUserconfiguration among systems.

• /users/XUS/engineer/.baseUser/.Autost

• /users/XUS/engineer/.baseUser/.Xdefaults

• /users/XUS/engineer/.baseUser/.cshrc

• /users/XUS/engineer/.baseUser/.environ

• /users/XUS/engineer/.baseUser/.exrc

• /users/XUS/engineer/.baseUser/.login

• /users/XUS/engineer/.baseUser/.mwmrc

• /users/XUS/engineer/.baseUser/.profile

Generic supervisor files The following files may be transferred to duplicate customized .baseUserconfiguration among systems.

• /users/XUS/supervisor/.baseUser/.Autost

• /users/XUS/supervisor/.baseUser/.Xdefaults

• /users/XUS/supervisor/.baseUser/.cshrc

• /users/XUS/supervisor/.baseUser/.environ

• /users/XUS/supervisor/.baseUser/.exrc

• /users/XUS/supervisor/.baseUser/.login

• /users/XUS/supervisor/.baseUser/.mwmrc

• /users/XUS/supervisor/.baseUser/.profile

Generic view only files The following files may be transferred to duplicate customized .baseUserconfiguration among systems.

• /users/XUS/viewOnly/.baseUser/.Autost

• /users/XUS/viewOnly/.baseUser/.Xdefaults

• /users/XUS/viewOnly/.baseUser/.cshrc

• /users/XUS/viewOnly/.baseUser/.environ

• /users/XUS/viewOnly/.baseUser/.exrc

• /users/XUS/viewOnly/.baseUser/.login

• /users/XUS/viewOnly/.baseUser/.mwmrc

• /users/XUS/viewOnly/.baseUser/.profile




Specific user files Specific user files reside in the user’s home directory. When a new user iscreated, the generic files (from .baseUser directory) are automaticallycopied to the users home directory. A customized file can be transferred tothe user’s home directories on all machines on which the user is registered.

Specific operator files Customized files may be transferred to each user’s home directory toprovide a custom configuration. Substitute the user’s login name forusername in the examples below.

• /users/XUS/operator/username/.Autost

• /users/XUS/operator/username/.Xdefaults

• /users/XUS/operator/username/.cshrc

• /users/XUS/operator/username/.environ

• /users/XUS/operator/username/.exrc

• /users/XUS/operator/username/.login

• /users/XUS/operator/username/.mwmrc

• /users/XUS/operator/username/.profile

Specific engineer files Customized files may be transferred to each user’s home directory toprovide a custom configuration. Substitute the user’s login name forusername in the examples below.

• /users/XUS/engineer/username/.Autost

• /users/XUS/engineer/username/.Xdefaults

• /users/XUS/engineer/username/.cshrc

• /users/XUS/engineer/username/.environ

• /users/XUS/engineer/username/.exrc

• /users/XUS/engineer/username/.login

• /users/XUS/engineer/username/.mwmrc

• /users/XUS/engineer/username/.profile

Specific supervisor files Customized files may be transferred to each user’s home directory toprovide a custom configuration. Substitute the user’s login name forusername in the examples below.

• /users/XUS/supervisor/username/.Autost

• /users/XUS/supervisor/username/.Xdefaults

• /users/XUS/supervisor/username/.cshrc

• /users/XUS/supervisor/username/.environ

• /users/XUS/supervisor/username/.exrc




Specific supervisorfiles, continued

• /users/XUS/supervisor/username/.login

• /users/XUS/supervisor/username/.mwmrc

• /users/XUS/supervisor/username/.profile

Specific view only files Customized files may be transferred to each user’s home directory toprovide a custom configuration. Substitute the user’s login name forusername in the examples below.

• /users/XUS/viewOnly/username/.Autost

• /users/XUS/viewOnly/username/.Xdefaults

• /users/XUS/viewOnly/username/.cshrc

• /users/XUS/viewOnly/username/.environ

• /users/XUS/viewOnly/username/.exrc

• /users/XUS/viewOnly/username/.login

• /users/XUS/viewOnly/username/.mwmrc

• /users/XUS/viewOnly/username/.profile


7.5 FTP (File Transfer Protocol) Procedure


X Menu >

Application >

System Menu >

Applications

Unix Load

Calculator

Datebook

Telnet

DECnet

Change Password12604

Requirements To transfer files using this procedure requires each Universal StationX

station to be configured (Hostname, IP address, and Time/Date minimum).The station must be operational with full user login capabilities andconnected to an Ethernet network accessible to all Universal StationXs towhich files are to be transferred.

FTP procedures Use this procedure to transfer a file between Universal StationXs usingFTP.

Step Action

1 Login as a user with engineering access privileges.

2 Select Telnet from the workspace menu.

3 Enter the FTP utility.

Type ftp hostname <RETURN> where hostname is that of theremote system.

4 To retrieve a file from the remote system:Type get filepathname1 filepathname2 <RETURN>

To send a file to the remote system:Type put filepathname1 filepathname2 <RETURN>

Note: filepathname1 is the source pathname andfilepathname2 is the destination pathname.

5 Repeat Step 4 for each file to be transferred.

6 Exit the FTP utility.

Type quit <RETURN>

7 Close the Telnet window using the window menu.


7.6 Modifying the /etc/hosts File Manually

Modify Procedures If any errors are made, exit this procedure without modifying the file bypressing <ESC> :q! <RETURN>

Step Action




3 Edit the text file /etc/hosts by typing

vi /etc/hosts <RETURN>

4 Position the cursor below the comments at the top of the file.

It may be necessary to delete any lines which are inappropriate.

Use these four keys to move the text cursor:

k = UP

j = DOWN

h = RIGHT

l = LEFT

5 Enter the vi INSERT mode.

Press i

6 Type the TCP/IP address <TAB> hostname <RETURN> for eachsystem to which the Universal StationX requires access.

The file will resemble this:

# The # character is used to add comments# anywhere in the file.129.30.114.100 XUS_01129.30.114.200 XUS_02129.30.114.204 VAX01

7 Exit the INSERT mode.

Press <ESC>

8 It may be necessary to delete any lines which are inappropriate.

Position the cursor on the line to be deleted.

Press dd

9 a To EXIT AND SAVE changes, press :wq! <RETURN>

9 b To EXIT WITHOUT SAVING, press :q! <RETURN>




7.7 Network Backup/Restore Configuration

Configurationrequirements

In order to accomplish a remote backup or restore, the user must have anaccount on the remote machine and there must be an entry for the localmachine (by hostname) in the /etc/host.equiv on the remotemachine. The user must also set a resource(s) for the remote machine(s) intheir local .Xdefaults file. There can be up to three remote machineslisted. When properly configured, the backup and restore application wouldhave buttons for each of the machines listed.

.Xdefaults example For example, suppose that the hostname of the local machine is localNodeand there are 3 remote machines named remNode1, remNode2, andremNode3. If the user’s login name is JohnEngr, then in JohnEngr’s.Xdefaults file the following entries would need to appear:

*XSam*remoteHost1.labelString:remNode1*XSam*remoteHost2.labelString:remNode2*XSam*remoteHost3.labelString:remNode3

/etc/hosts.equiv example

On each of the remote machines the /etc/hosts.equiv file would needthe following entry:

localNode

Testing theconfiguration

If the above is true, then whenever JohnEngr opens the backup/restoreapplication there will be toggle buttons for each of the remote machines.

The easiest way to test this setup is to have the user type this at the shellprompt:

remsh remNode1 ll -a <RETURN>

If the remote node is set up properly, the user’s home directory should belisted. If the test returns:

remsh: Login incorrect

it means one, or possibly both of two things. Either there is no entry in the/etc/hosts.equiv file for the local node, or the user does not have anaccount on the remote machine.


Section 8 – Custom Configuration

8.1 Customizing the Workspace Menu

Why customize? The workspace menu can contain items which connect to and runapplication software on remote systems and cause them to display locally.This reduces the steps and knowledge required to perform an operationaltask.

Modify all users By modifying the file in the appropriate .baseUser directory, thecustomization can be for all subsequently registered users of a specificgroup. Remember to transfer this file to the .baseuser directory on allmachines.

To use the new custom menu, prior users must have the new file transferredto their home directory.

Modify a single user By modifying the .mwmrc file in the user’s home directory, only that userwill have the altered workspace menu. Remember to transfer this file to theuser’s home directory on all machines where he is registered.

Appropriate files A customized command string can be appended to the workspace menu byplacing the command string into the appropriate .mwmrc file.

• /users/XUS/operator/.baseUser/.mwmrc

• /users/XUS/operator/username/.mwmrc

• /users/XUS/supervisor/.baseUser/.mwmrc

• /users/XUS/supervisor/username/.mwmrc

• /users/XUS/engineer/.baseUser/.mwmrc

• /users/XUS/engineer/username/.mwmrc

• /users/XUS/viewOnly/.baseUser/.mwmrc

• /users/XUS/viewOnly/username/.mwmrc

Parts of a commandstring

There are several components of a workspace menu command string to beplaced into the .mwmrc file. The elements of the string are the same for allremote computing systems (even those of dissimilar operating systems).However, the commands and syntax of the remote system are used in oneelement of the command string. This requires knowledge of the remoteoperating systems commands and operation. This knowledge will not becovered in this manual and can be located in the documentation of theappropriate system.



8.1 Customizing the Workspace Menu, Continued

Parts of a commandstring, continued

The elements of the workspace menu command strings:

Menu RootMenu{"Engineer Menu" f.title"X Menu" f.menu XMenu"Application Menu" f.menu ApplicationMenu"System Menu" f.menu SystemMenu}Menu XMenu{"X Menu" f.title"Shuffle" f.menu ShuffleMenu"Logout" f.quit_mwm}Menu ApplicationMenu{"Applications" f.title "Unix Load" f.exec "xload-geom -4+4 &""Calculator" f.exec "xcalc -geom -160+4 &""Datebook" f.exec "datebook -geom +724+4 &""Telnet" f.exec "xterm -geom +291+400 -e telnet &""DecNet" f.exec "xteemx340 -geom +291+400 &"}

MENU ITEM NAMES WINDOW MANAGER COMMANDS

SYSTEM COMMANDS

12605

Creating a command To create the command line use the vi text editor to modify the appropriate.mwmrc file. Here are the steps to creating a command string to be includedin the workspace menu.

Step Action

1 Choose a menu label.

2 Choose the appropriate window manager command.

3 Determine if a remote shell is necessary. It is required to executeapplications on remote computers.

4 Choose the system command including any additional parameters asappropriate to the software application.




Choosing a label Choose a label name that represents the action as close as possible. Timespent planning will provide a menu system that is intuitive and requires little(if any) additional documentation.

Choose a windowmanager command

Several window manager commands are used to customize the workspacemenu and are listed here for your convenience. For additional information,see Hewlett Packard publication, Using the X Window System.

Category Command Description

ProgramExecution

f.exec “cmd &” Executes cmd using /bin/sh

f.restart Restarts the Motif Window Manager

f.kill Kills the client that started the window

MenuOperations

f.menu MenuName Associates a menu with a selection

f.post_wmenu Posts a window menu

f.separator Draws a line between selections

f.title Inserts a title into menu at specifiedposition

Local commands To execute commands on the local system, only the window managercommand and system command are necessary.

Required syntax for executing local applications:“MenuItemName” f.exec “ApplicationName &”“MenuItemName” f.exec “ScriptFileName &”

An example of the command string to execute a local application.“Datebook” f.exec “datebook &”




Remote commands To execute commands in a remote computer system, a remote shell sessionis needed. Add the following to the window manager command to build thecommand string.

Required syntax for executing remote applications:“MenuItemName” f.exec “remsh hostname ApplicationName &”“MenuItemName” f.exec “remsh hostname ScriptFileName &”

An example of the command string to execute the application Framemakeron the host system named hp7ØØ_Ø1.“Word Processor” f.exec “remsh hp7ØØ_Ø1 maker &”

Sample customization The following is an example of the existing Application Menu customized toprovide an automatic connection to remote computers running varioussoftware. It is an excerpt of the standard .mwmrc file with additional lines(shown in bold print) to produce the workspace menu changes.

Menu ApplicationMenu{"Applications" f.title"Unix Load" f.exec "xload -geom -4+4 &""Calculator" f.exec "xcalc -geom -160+4 &""Datebook" f.exec "datebook -geom +724+4 &""Telnet" f.exec "xterm -geom +291+400 -e telnet &""DecNet" f.exec "xteemx340 -geom +291+400 &""Lab Analysis" f.menu LabMenu}Menu LabMenu{"Lab Analysis" f.title"Inlet PH" f.exec "remsh hp700_01 -l Inlet_PH raw1 &""Inlet Temp" f.exec "remsh hp700_02 -l Inlet_Temp raw2 &""Inlet PPM" f.exec "remsh vax01 -l Inlet_Clarity raw3 &""Discharge PH" f.exec "remsh hp700_2 -l Waste_PH out1 &"Discharge Temp" f.exec "remsh hp700_2 -l Waste_Temp out2 &"Discharge PPM" f.exec "remsh vax01 -l Waste_Clarity out3 &"Reports" f.menu ReportMenu}Menu ReportMenu"Reports" f.title"Shift Summary" f.exec "RunShiftSum &""Daily Summary" f.exec "RunDailySum &""Weekly Summary" f.exec "RunWeekSum &"}




Sample customization,continuation

Produces the following Applications Menu with two new sub menus:

Reports Menu

Shift Summary

Daily Summary

Weekly Summary

Applications

Unix Load

Calculator

Datebook

Telnet

DecNet

Lab Analysis >Lab Analysis

Inlet PH

Inlet Temp

Inlet PPM

Discharge PH

Discharge Temp

Discharge PPM

Reports >

12607


8.2 Customizing the User’s Shell Variables

What is the shell? The shell is the mechanism used to issue commands to the UNIXprocessor. This shell acts as a command interpreter and controls the UNIXsystem resources to carry out the requested task. The shell provides apowerful and flexible programming language to allow creation of script filescontaining many commands.

Available shells There are several shells used:

• /bin/sh — Bourne shell used for members of the group Engineer

• /bin/rsh — restricted Bourne shell used for members of the groups:Operator, Supervisor, and View Only

• /bin/csh — C shell used for the root user

Shell variables The shell tracks items called variables that it uses to control systemresources.

The most often used variables are:

• SHELL - Pathname of your shell

• TERM - Defines your terminal type for screen oriented commands

• PATH - List of directories the shell searches for commands

Controlling files The shell variables are set at login and each time a shell is created. Thesystem executes various initialization files depending on the users shelltype. These files are located in the users home directory.

Shell type Controlling files

Bourne shell — /bin/sh .profile — executed at login

Restricted Bourne shell — /bin/rsh .profile — executed at login

C shell — /bin/csh .cshrc — executed at initialization

.login — executed at login

For more information For more information, see the following Hewlett Packard publications:

• A Beginners Guide To Using Shells

• HP-UX Concepts and Tutorials: Shells and Miscellaneous Tools

• HP-UX System Security

5/94 Universal StationXSystem Administration Manual 85

Section 9 – Coprocessor Administration Tasks

9.1 Create New Coprocessor Users

Required access level The procedures must be performed while logged in as “engineer.” Thecoprocessor password is not required.

Guidelines Use the following criteria when adding a user to the coprocessorenvironment:• Assign a separate login name for each user

• Do not assign a login name beginning with a number

• Determine the user’s group access level by providing the “leastprivileges” necessary to perform the required tasks

• Do keep a record of all users assigned access, it should contain:

– User name, contact information (phone number, address, etc.)

– User login name

– User access level

– List all systems the user has accounts on

– List all software where the user has accounts (E-mail, Telex, etc.)

Note: This listing should be maintained by the system administrator.

• Remind the user to change their password during their first session.

Initial use When new users are created, the password is set equal to the login name.For example: the user account “guest,” will use the password “guest.”

To maintain system security, it is important that the password be changed assoon as practical. To do this, login as the new user and select changepassword from the workspace menu. Enter a password and record thisinformation for the new user.


X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore... 12608



9.1 Create New Coprocessor Users, Continued

Add users Use the following procedure to configure user access to the coprocessor:NOTE: If, at any point in the following instructions, you have made an

error, selecting the Close target without selecting Apply willexit without saving changes.

Step Action

1 Select Add/Remove Users... from the workspace menu, it isfound nested as System Menu > Add/Remove Users.

2 Select the User target.

3 Select the Add target.

4 Type the user login name in the Login Name field.

5 Type full user name, office location, work and home phone numberinto the field provided.

6 Select the appropriate group target from the menu.

7 Select the APPLY target to save changes.

8 Repeat Steps 4 through 7 for each user.

9 Select the CLOSE target and the window will close.


11 Select the OK target.


13 Select the Exit Xsam target.



9.2 Delete Coprocessor Users



X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...


Delete users To deny authorized users access to the coprocessor, use the following:NOTE: If at any point in the following instructions you have made an

error, selecting the Close target without selecting Apply willexit without saving changes.

Step Action

1 Select Add/Remove Users... from the workspace menu.


3 Select each user to be removed by selecting the icon to left of theuser login name.

NOTE: The icon is highlighted to show selection.

4 Select the Remove target.


NOTE: This step is required only if multiple users have beenselected to be removed.







9.3 Modify Coprocessor User Information



X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...


Modify user information To modify a user’s coprocessor access information, use the following:NOTE: If, at any point in the following instructions, you have made an

error, selecting the Close target without selecting Apply willexit, without saving changes.

Step Action

1 Select Add/Remove Users... from the workspace menu.


3 Select the OPEN target.

4 Select the user (to modify) by clicking on the icon to the left of theuser login name. Note: icon is highlighted to show selection.

5 If applicable, type changes into the Login ID field.

6 If applicable, type changes into the full name field.

7 To change the access level, select a group target.

8 Repeat Steps 4 through 7 for each user to be modified.

9 Select the Apply target to save changes.


11 Select the Exit Xsam target and the window will close.


9.4 Backup the Coprocessor Hard Drive



X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...


Backup coprocessor Use the following procedure to backup the coprocessor hard drive.NOTE: This procedure currently performs only full backups. The

contents of the DAT tape will be overwritten.

Step Action

1 Remove the appropriate tape from its protective case and gentlyinsert it into the tape drive. Press gently on the edge of the tapecartridge while inserting it into the unit until you feel the unit pull onthe tape. The unit will then load and position the tape. Whilepositioning is being performed, both indicator lamps on the front ofthe unit will flash. When the right lamp shows a solid green,positioning is complete and the tape unit is ready to use.

If you are unable to successfully insert the tape, gently remove thecartridge and reinsert it again. If you are still unsuccessful, contactyour Honeywell service representative for assistance.

1 Select Backup/Restore... from the workspace menu.

2 Select the BACKUP target.

3 To perform a backup of the entire Universal StationX filesystem:

Select the System Backup: target.

To perform a backup of Universal StationX user files only:

Select the User Backup: target.



9.4 Backup the Coprocessor Hard Drive, Continued

Backup coprocessor,continued

Step Action

4 To perform a FULL backup of all files within the scope:

Select the FULL BACKUP target.

To perform an INCREMENTAL backup of all files within the scope:

This feature is not available at this time.

5 Select the appropriate host target. This indicates which device willhave the tape drive.

6 Select the START BACKUP target.

Note: The backup operation will take 3 to 20 minutes to complete. Ifany errors occur, your response to the prompts must betyped into the Input Commands field.

7 Upon completion, the following message is displayed:

fbackup: runtime: 38 SecondsEnd of Execution



Click on OK at the message Do you really want to exit?


9.5 Restore Coprocessor Hard Drive Data



X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...


Coprocessor restoremenu

This menu provides the mechanism necessary to restore the coprocessorfilesystem from a prior backup tape. It allows the user to specify theprocess by which files are restored.

Restore types The restore procedure allows two types of file restoration:

• Overwrite — restores tape contents to the Universal StationX regardlessof time stamp.

• Update — writes files with dates later than those present in the UniversalStationX.

Perform a restore To perform a restore, follow this procedure:NOTE: If, at any point in the following instructions, you have made an

error, select the EXIT RESTORE target to exit.

Step Action

1 Remove the appropriate tape from its protective case and gentlyinsert it into the tape drive. Press gently on the edge of the tapecartridge while inserting it into the unit until you feel the unit pull onthe tape. The unit will then load and position the tape. Whilepositioning is being performed, both indicator lamps on the front ofthe unit will flash. When the right lamp shows a solid green,positioning is complete and the tape unit is ready to use.


2 Select Backup/Restore... from the workspace menu.

3 Select the RESTORE target.



9.5 Restore Coprocessor Hard Drive Data, Continued

Perform a restore,continued

Step Action

4 To perform an overwrite with all files on the tape:

Select the OVERWRITE target.

To perform an update with files from the tape:

Select the UPDATE target.

5 Select the START RESTORE target.



Click on OK at the message Do you really want to exit?


9.6 Coprocessor Software Update (Local DAT)

Introduction This procedure is used to install software updates from DDS tape media todisk storage media on a Universal StationX station.


Required configuration This procedure requires a DAT tape unit connected to the UniversalStationX station. The station must be operational with full user logincapabilities.

Menu appearance

Update Type

Local...

Network...

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...


Detailed installationinstructions

The following steps will complete the installation of this update from thetape media. Execute each step in sequence. Warning: Do not continue if anystep cannot be completed successfully.

Step Action

1 Remove the tape labeled “Universal StationX#.# Update” from itsprotective case and gently insert it into the tape drive. Press gentlyon the edge of the tape cartridge while inserting it into the unit untilyou feel the unit pull on the tape. The unit will then load and positionthe tape. While positioning is being performed, both indicator lampson the front of the unit will flash. When the right lamp shows a solidgreen, positioning is complete and the tape unit is ready to use.


2 Select Update Software - Local from the workspace menu.


4 In the update window, use the arrow keys on the keyboard tohighlight.

Change Source or Destination ->

then press the <RETURN> key on the keyboard.

This will cause a new window to appear within the update window.



9.6 Coprocessor Software Update (Local DAT), Continued

Detailed installationinstructions, continued

Step Action

5 In the window that just popped up, use the arrow keys to highlight

From Tape Device to Local System->



6 In the window that just popped up, there will be a question.

Create or change the address of/dev/update.src->

Position the cursor in the window over the “n” after this questionusing the arrow keys on the keyboard and type “y”


7 In the window that just popped up, verify the following settings andcorrect if wrong:

major number: 54select code: 14bus address: 1unit number: 0volume number: 2

8 Using the mouse, position the cursor over the “Done” button at thebottom of the update window and depress the left button on themouse.

This will cause the top window to close.


This will cause the top window to close and the light on the tape drivewill begin blinking for a few seconds.

10 Once the light on the tape drive has stopped blinking, use the arrowkeys on the keyboard to highlight.

Select All Filesets on the Source Media->





9.6 Coprocessor Software Update (Local DAT), Continued


Step Action

11 In the new window, use the arrow keys on the keyboard to highlight

Start loading now?


12 After a few seconds, a window will pop up and the final sentence inthe window will ask.

Start loading filesets now?

When this window appears, depress the “y” key on the keyboard.

This will start the update and will take approximately 20 minutes.

13 If any errors or warnings occurred, they will be displayed uponcompletion of the update process.

Please record each message and press the Search target to displaythe next message. When all messages have been displayed, thesystem will beep. Select the Exit target.

14 If any errors occurred during the update, this message is displayed:

Update Failed!!!Call the Technical Assistance Center for help

The process will not continue. You must contact TAC to resolve theerrors.

15 The coprocessor will reboot automatically.

16 Remove the update tape from the tape unit by pressing the ejectbutton. The green light will flash while the unit positions the tape to itsbeginning. When the tape is ejected from the unit, remove it andreturn it to its protective case.

17 Reset the Universal StationX node.

If your Universal StationX node is packaged in a standardHoneywell TDC 3000X console, the reset button is located underthe folding top edge of the operator's keyboard.

If your Universal StationX node is packaged in a Honeywell Micro-TDC tower cabinet, the reset button can be accessed only byremoving the front cabinet cover and pressing the button locatedon the front edge of the module power supply.

18 Your Universal StationX node software will automatically reload fromthe local disk storage media. This reload process should takeapproximately 5 minutes. After that time, you will observe the loginbar appear at the bottom portion of the display screen, indicating theUniversal StationX station is now ready to use.


9.7 Coprocessor Software Update (Remote DAT)

Introduction This procedure installs the software update from another Universal StationX

station on the Ethernet network.

Required configuration This procedure requires that an additional Universal StationX station beconnected to the LAN, which contains the update software for UniversalStationX, and is running the “netdist” daemon. This master system must beprepared following subsection 9.8, Preparing Software Update Server(Network Only).


Menu appearance

Update Type

Local...

Network...

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...



The following steps will complete the installation of this update from thetape media. Execute each step in sequence. Warning: Do not continue if anystep cannot be completed successfully.

Step Action

1 Select Update Software - Local from the workspace menu.


3 In the update window, use the arrow keys on the keyboard tohighlight.

Change Source or Destination ->




From Netdist Server to Local System->





9.7 Coprocessor S/W Update (Remote DAT), Continued


Step Action

5 In the window that just popped up, this message is displayed:

Netdist Server (Source):

Enter the name of the node which contains the update files, thenpress the <RETURN> key on the keyboard.








Start loading now?








11 If any Errors occurred during the update, this message is displayed:


The process will not continue. You must contact TAC to resolve theErrors.



9.7 Coprocessor S/W Update (Remote DAT), Continued


Step Action

12 The coprocessor will reboot automatically.

13 Reset the Universal StationX node.

If your Universal StationX node is packaged in a standardHoneywell TDC 3000X console, the rest button is located underthe folding top edge of the operator's keyboard.

If your Universal StationX node is packaged in a Honeywell Micro-TDC tower cabinet, the reset button can be accessed only byremoving the front cabinet cover and pressing the button locatedon the front edge of the module power supply.

14 Your Universal StationX node software will automatically reload fromthe local disk storage media. This reload process should takeapproximately 5 minutes. After that time, you will observe the loginbar appear at the bottom portion of the display screen, indicating theUniversal StationX station is now ready to use.


9.8 Preparing Software Update Server (Server Only)

Introduction This procedure is used to prepare a Universal StationX system to distributesoftware updates from a local DDS tape media to other Universal StationX

stations via Ethernet.

Required configuration This procedure requires a DAT tape unit and a 400 megabyte hard driveconnected to the Universal StationX station. The station must be operationalwith full user login capabilities and connected to an Ethernet networkaccessible to all Universal StationXs to be updated.

Restart after reboot If the coprocessor is rebooted/shutdown before all machines are updated,the network distribution daemon will need to be restarted. This is done bytyping /etc/netdistd & at the unix shell prompt accessed from thesystem configuration menu.


Menu appearance

Update Type

Local...

Network...

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...


Prior networkdistribution server

If a previous network distribution process is running, this procedure willcause a coprocessor reboot. Reinitiate this procedure after the system hasrebooted.



9.8 Preparing S/W Update Server (Server Only), Continued


To install the update, perform each of the following steps in sequence.Warning: Do not continue if any step cannot be completed successfully.

Step Action

1 Remove the tape labeled “Universal StationX#.# Update” from itsprotective case and gently insert it into the tape drive. Press gentlyon the edge of the tape cartridge while inserting it into the unit untilyou feel the unit pull on the tape. The unit will then load and positionthe tape. While positioning is being performed, both indicator lampson the front of the unit will flash. When the right lamp shows a solidgreen, positioning is complete and the tape unit is ready to use.


2 Select Update Software - Remote from the workspace menu.


6 In the window that just popped up, there will be a question.

Create or change the address of/dev/update.src->

Position the cursor in the window over the “n” after this questionusing the arrow keys on the keyboard and type “y”


7 In the window that just popped up, verify the following settings andcorrect if wrong:

major number: 54select code: 14bus address: 1unit number: 0volume number: 2




This will cause the top window to close and the light on the tape drivewill begin blinking for a few seconds.



9.8 Preparing S/W Update Server (Server Only), Continued


Step Action

10 Once the light on the tape drive has stopped blinking, use the arrowkeys on the keyboard to highlight.


then press the <RETURN>key on the keyboard.



Start loading now?








14 If any errors occurred during the update, this message is displayed:


The process will not continue. You must contact TAC to resolve theerrors.

15 Remove the update tape from the tape unit by pressing the ejectbutton. The green light will flash while the unit positions the tape to itsbeginning. When the tape is ejected from the unit, remove it andreturn it to its protective case.

16 The network distribution program (netdistd) will run automaticallyafter the tape install has completed.

This program will start a network process which makes the updateavailable across Ethernet.

17 From each Universal StationX station to be updated, perform thesteps contained in subsection 9.7, Coprocessor Software Update(Remote DAT).


9.9 Checking Tracking Files

Software tracking There are several utilities within UNIX which provide troubleshootinginformation by constantly providing on-line recording of certainevents/messages. This information can often help in locating the troublesource.

Interpreting the file contents is beyond the scope of this publication.However, the location and use of these files will be described here.

Login logs The system logs all login attempts in the /etc directory. You may checkthe logs to determine if there have been any attempts to gain unauthorizedaccess.

Login attempt Recorded in log file

Successful Login /etc/wtmp

Failed Login /etc/btmp

The files are stored in binary format, use the UNIX command last to readthe files. For example last /etc/wtmp <RETURN>

Shutdown log The system logs all shutdowns in the file /usr/adm/shutdownlog.Check this file for any unattended shutdowns (power outage) or anyabnormal conditions incurred during past shutdowns.


9.10 Creating Recovery Tapes


Menu appearance

Configuration

IWSM Configuration


Set Time/Timezone

Gated Daemon >

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

12594

Making recovery tapes Recovery tapes aid in troubleshooting/restoring inoperative systems. It isnot necessary to create a set for every Universal StationX; one set per sitewill provide rapid restoration/recovery. The following procedure will take 2to 3 hours to complete.

Step Action



3 Insert a blank tape in the drive and wait for it to load.

4 Select the Shell target.

5 Typemkrs -v -f /dev/rmt/0m -r /dev/dsk/root <RETURN>

6 When the process completes, remove the tape, label it UniversalStationX BOOT TAPE and store it in a safe and secure place.

7 Insert a tape in the drive and wait for it to load.

8 Type cd / <RETURN>

9 Type tar cv <RETURN>

10 When the process completes, remove the tape, label itRECOVERY TAPE, and store it in a safe and secure place.

11 Type exit<RETURN>.

12 Press the Exit SAM target.


Section 10 – Optional Application Software

10.1 Application Software Supported

Platform Software Software support is provided for the products offered by Honeywell IAC.The software supported on the Universal StationX platform are:

• Hewlett Packard HP-UX UNIX software and associated packages:

– X Windows

– MOTIF

• Communications software packages:

– TCP/IP

– DECnet

– VT 300 Series terminal emulation

These packages reside on the Universal StationX platform and are fullysupported by the Honeywell Technical Assistance Center.

Unsupported software To ensure security and robustness Honeywell IAC does not approve of anyother software (for example, X Window applications) beingloaded/executed on the Universal StationX platform.

Honeywell maintains that the loading and execution of any software on theUniversal StationX platform other than those identified above will not besupported by the Technical Assistance Center. Furthermore, Honeywellretains the right, at its sole discretion, to void the warranty.

External software Honeywell has identified third party software packages that arecommercially available that permit information transfer from either AppleMacintosh or IBM PCs and their compatibles. These commercially availablepackages reside on the users computing devices - not the UniversalStationX.

• DESQview/X - Allows DOS applications to be displayed at the UniversalStationX in an X Window

• XGator - Allows a Macintosh desktop to be displayed at the UniversalStationX in an X Window

The following is Honeywell IACs position regarding these packages:

Demonstration of functionality does not imply Honeywell IAC hasvalidated, certified, nor supported these packages as standard IAC productofferings. Since these and other packages do not reside on the UniversalStationX platform, Technical Assistance Center support will be limited toverifying that the corresponding interfaces (PC, Macintosh, workstation) tothe Universal StationX platform is functioning properly.


10.2 Loading Kinet Software from a Local DAT Drive

Local DAT install This procedure will install and configure the Kinet software on thecoprocessor hard disk drive. This software provides DECnet protocolsupport and VT320/340 terminal emulation.


Menu appearance

Configuration

IWSM Configuration


Set Time/Timezone

Gated Daemon >

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

12594

Load/configure Kinet Load and configure the Kinet software using the following procedure.

Step Action

1 Remove the tape from its protective case and gently insert it into thetape drive. Press gently on the edge of the tape cartridge whileinserting it into the unit until you feel the unit pull on the tape. Theunit will then load and position the tape. While positioning is beingperformed, both indicator lamps on the front of the unit will flash.When the right lamp shows a solid green, positioning is complete andthe tape unit is ready to use.





5 Type cd /usr <RETURN>.

6 Type tar xv <RETURN>.

7 Wait approximately 5 minutes for files to load from tape.



10.2 Loading Kinet from a Local DAT Drive, Continued

Load/configure Kinet,continued

Step Action

8 Type cd kinet and press <RETURN>.

9 Type ./install.ki and press <RETURN>.

10 Using the arrow keys to navigate between fields, enter the following:

1) Software license key provided with the software.NOTE: This must be the correct number for the coprocessor board installed in the station. To view the processor board number, type uname -a <RETURN> at the shell prompt.

2) Local Node Name/Address.3) Remote VAX Name/Address provided by the VAX administrator.

11 Navigate to the Option field, press the SPACE BAR to list theselections. Press <RETURN> when Execute is displayed.

12 After several minutes, you will be prompted to “Please use kirebootto reboot your system”

Type kireboot and press <RETURN>.

13 Type y and press <RETURN>.

NOTE: You should NOT logout after performing this step.


10.3 Loading Kinet Software from a Remote DAT Drive

Kinet software install This procedure will install and configure the Kinet software on thecoprocessor hard disk drive from a DAT drive located in another UniversalStationX. This software provides DECnet protocol support and VT320/340terminal emulation.

Requirements The procedures must be performed while logged in as “engineer.” Thecoprocessor password is required. The IP address of the remote stationmust be entered using the procedure in subsection 5.5 or subsection 7.6.

Menu appearance

Configuration

IWSM Configuration


Set Time/Timezone

Gated Daemon >

Engineer Menu

X Menu >

Application >


Configuration >

Update Software >

Add/Remove Users...

Backup/Restore...

12594

Load/configure Kinet NOTE: This procedure requires account level equivalence for root. Securityissues should be considered before allowing root equivalence.

Load and configure the Kinet software using the following procedure.

Step Action

1 Remove the tape from its protective case and gently insert it into thetape drive of the remote system. Press gently on the edge of thetape cartridge while inserting it into the unit until you feel the unit pullon the tape. The unit will then load and position the tape. Whilepositioning is being performed, both indicator lamps on the front ofthe unit will flash. When the right lamp shows a solid green,positioning is complete and the tape unit is ready to use.





5 Type cd /usr <RETURN>.



10.3 Loading Kinet Software from a Remote DAT Drive, Continued

Load/configure Kinet,continued

Step Action

6 Typeremsh host dd if=/dev/rmt/Øm bs=10k | tar xf -<RETURN>

Where host is the hostname of the remote system.

7 Wait approximately 5 minutes for files to load from tape. Whencompleted the prompt will return.

8 Type cd kinet and press <RETURN>.

9 Type ./install.ki and press <RETURN>.

10 Using the arrow keys to navigate between fields, enter the following:

1) Software license key provided with the software.NOTE: This must be the correct number for the coprocessor board installed in the station. To view the processor board number, type uname -a <RETURN> at the shell prompt.

2) Local Node Name/Address.3) Remote VAX Name/Address provided by the VAX administrator.

11 Navigate to the Option field, press the SPACE BAR to list theselections. Press <RETURN> when Execute is displayed.

12 After several minutes, you will be prompted to “Please use kirebootto reboot your system”

Type kireboot and press <RETURN>.

13 Type y and press <RETURN>.

NOTE: You should NOT logout after performing this step.

Index


.mwmrc file 79

A, B

Application Software 105

C, D, E

Coprocessor password 42, 55Coprocessor printer 48Configuration checklist 39Custom configuration 65

F, G

File transfer 66FTP (File Transfer Protocol) 66

H

Hostname 44TCP/IP address 44

I, J, K

Industrial Workspace Manager 52IWSM 52Kinet Software 106

L, M

LAN Routing 46LCN requirements 35Login 42

Initial 42Procedure 22

N

NCF changes 35Network backup/restore 65

O, P, Q

Power On 41Initial 41Procedure 21

R

Recovery Tapes 103

S, T

Set time/timezone 43shell 84

Bourne shell 84C shell 84restricted Bourne shell 84

Software Update 93, 96Software Update Server 99System security 85

U, V

UNPX personality 35

W, X, Y, Z

Window manager commands 81Workspace menu 79Workspace menu command strings 80

READER COMMENTS

Honeywell IAC Automation College welcomes your comments and suggestions toimprove future editions of this and other publications.

You can communicate your thoughts to us by fax, mail, or toll-free telephone call. Wewould like to acknowledge your comments; please include your complet name andaddress

BY FAX: Use this form; and fax to us at (602) 313-4108

BY TELEPHONE: In the U.S.A. use our toll-free number 1*800-822-7673 (available inthe 48 contiguous states except Arizona; in Arizona dial 1-602-313-5558).

BY MAIL: Use this form; detach, fold, tape closed, and mail to us.

Title of Publication: Universal StationX Issue Date: 5/94

System Administration

Publication Number: UX11-400

Writer: R. Evans

COMMENTS: ___________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

RECOMMENDATIONS:___________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

NAME _______________________________________ DATE ____________________

TITLE _________________________________________________________________

COMPANY _____________________________________________________________

ADDRESS ______________________________________________________________

CITY ________________________ STATE ___________ ZIP ____________________

TELEPHONE _____________________ FAX _________________________________

(If returning by mail, please tape closed; Postal regulations prohibit use of staples.)

Automation CollegeIndustrial Automation and Control Honeywell Inc.2820 West Kelton LanePhoenix, Arizona 85023-3028

Communications concerning technical publications should be directed to:

FOLD FOLD

From: NO POSTAGENECESSARY

IF MAILEDIN THE USA

BUSINESS REPLY MAIL

POSTAGE WILL BE PAID BY ....

Industrial Automation and Control 2820 West Kelton LanePhoenix, Arizona 85023-3028

Attention: Manager, Quality

Additional Comments:

Cut

Alo

ng L

ine

FOLD FOLD

FIRST CLASS PERMIT NO. 4332 PHOENIX, ARIZONA

Honeywell

L

Industrial Automation and Control Helping You Control Your WorldHoneywell Inc.16404 North Black Canyon HighwayPhoenix, Arizona 85023-3099

universal stationx system administration manual universal stationx system administration manual ix...

Documents