Sysadmin Linux

®
DISPATCH
System Administration
Class
Modular Mining Systems

3289 E Hemisphere Loop
Tucson, Arizona (USA) 85706-5028
Telephone: (520) 746-9127
URL: http://www.mmsi.com
January 2003
RESTRICTIVE COVENANT
AND
DISCLAIMER
Copyright © 2003 by Modular Mining Systems, Inc.

Tucson, Arizona, U.S.A.
All rights reserved.
Modular Mining Systems, Inc., makes no representation regarding the fitness, quality, design, condition,
capacity, suitability, or performance of the equipment or of the material or workmanship thereof and/or compliance
of the system with the requirements of any law or regulations, and disclaims all warranties, either express or implied,
including but not limited to any implied warranty of merchantability or fitness for any particular purpose. Modular
Mining Systems, Inc., shall not be responsible for any loss or damage to property or injury or death to persons caused
by any defect or failure in the system hardware and/or software regardless of the form of action, whether in contract
or in tort, including negligence, strict liability, or otherwise. Modular Mining Systems, Inc., is not responsible for
any losses, financial or otherwise, that the customer, purchaser, or end user (hereafter, collectively, user) incurs nor
shall it be liable for any damages whatsoever (including, without limitation, damages for loss of business or
investment profits, business interruption, loss of business information or the like) arising out of the use, interruption
in the use of, or performance of the system hardware and/or software. User expressly agrees to indemnify and hold
harmless Modular Mining Systems, Inc., from and against all claims, damages, losses, and expenses, including but
not limited to: (i) any loss resulting from general or particular requirements of needs of user as defined in user’s
originating purchase order; (ii) any damages from loss of use, loss of data, loss of profits, or loss of business arising
out of or in connection with the performance of system hardware and/or software; (iii) any loss or damage to
property or injury or death to persons proximately resulting from system hardware and/or software, even if entirely
due in whole or in part to negligent acts or omissions of Modular Mining Systems, Inc.; and (iv) attorney’s fees and
costs.
The information described in this document is furnished as proprietary information and may not be copied or sold
without the written permission of Modular Mining Systems, Inc.
Trademarks
The Modular distinctive font, MasterLink, PowerView, ProVision, and WebReports are trademarks of
Modular Mining Systems, Inc.
The Modular logo, DISPATCH, and IntelliMine are registered U.S. trademarks of Modular Mining Systems, Inc.
All other brand names and product names used in this book are trademarks, registered trademarks, or
trade names of their respective holders.
Contents
Introduction to the DISPATCH System Administration Class .............................................................. -1
Introduction ....................................................................................................................................... -1
System Administration Class Outline ............................................................................................... -1
1 Overview of a System and Network ..................................................................................................... 1-1
Goals for this Chapter ..................................................................................................................... 1-1

Differences Between a System and a Network ............................................................................... 1-1
Two Common Views of a System .................................................................................................. 1-1
Component View of a System .................................................................................................. 1-1
Functional View of a System .................................................................................................... 1-3
.................................................................................................................................................. 1-5
Communications Protocol - TCP/IP ......................................................................................... 1-5
SCSI ................................................................................................................................................ 1-6
Kernel ........................................................................................................................................ 1-7
Shells ......................................................................................................................................... 1-7
2 System Administrator Duties ................................................................................................................ 2-1

The System Administrator .............................................................................................................. 2-1
System Administrator Responsibilities ..................................................................................... 2-1
3 System Structure .................................................................................................................................... 3-1

Files ................................................................................................................................................. 3-1
Three Common Files Types ...................................................................................................... 3-1
Plain Files ........................................................................................................................... 3-1
Directory Files .................................................................................................................... 3-2
Link Files ............................................................................................................................ 3-2
Four Uncommon File Types ..................................................................................................... 3-2
Device Files ........................................................................................................................ 3-2
Socket and Named Pipe Files ............................................................................................. 3-3
Directories ....................................................................................................................................... 3-3
TOC - 1
TOC - 2 System Administration Class
Some Comments About Pathname ........................................................................................... 3-3

Understanding File Information ................................................................................................ 3-3
Permissions ..................................................................................................................................... 3-5
Symbolic Links ......................................................................................................................... 3-6
Partitions ......................................................................................................................................... 3-8
Mount Points ............................................................................................................................. 3-8
Disks ............................................................................................................................................... 3-9
4 Fundamental Linux Commands ........................................................................................................... 4-1

The ls Command ............................................................................................................................. 4-1
cd (change directory) ................................................................................................................ 4-2
pwd ............................................................................................................................................ 4-3
history ....................................................................................................................................... 4-3
man ............................................................................................................................................ 4-3
clear ........................................................................................................................................... 4-3
cp (copy file) ............................................................................................................................. 4-3
grep ........................................................................................................................................... 4-4
mkdir ......................................................................................................................................... 4-4
mv ............................................................................................................................................. 4-4
rm .............................................................................................................................................. 4-4
rmdir .......................................................................................................................................... 4-5
Wildcards .................................................................................................................................. 4-5
Special Characters ..................................................................................................................... 4-5
5 The vi Editor ........................................................................................................................................... 5-1

vi Modes .......................................................................................................................................... 5-1
Opening a File ................................................................................................................................. 5-1
Navigating within a vi File ............................................................................................................. 5-2
Saving and Quitting a File .............................................................................................................. 5-2
Common vi Commands .................................................................................................................. 5-3
Copying Text ............................................................................................................................ 5-3
Deleting Text ............................................................................................................................ 5-3
Moving Text .............................................................................................................................. 5-4
Undo .......................................................................................................................................... 5-4
Contents - Continued January 2003

System Administration Class TOC - 3
6 External and Internal System Hardware Components ...................................................................... 6-1

External Components / Peripherals ................................................................................................. 6-1
Internal Components ....................................................................................................................... 6-1
7 Basic System Maintenance .................................................................................................................... 7-1

root (super-user) .............................................................................................................................. 7-1
8 DISPATCH Directory Structure and Related Processes & Peripherals .......................................... 8-1

DISPATCH Directory Structure ..................................................................................................... 8-2
mms (Modular Mining Systems) .................................................................................................... 8-4
To View the DISPATCH Environment Variables .......................................................................... 8-4
To Modify DISPATCH Environment Variables ............................................................................ 8-4
To Bring up a New Keypad in Color .............................................................................................. 8-5
To Output the Generic FORMS Symbols ....................................................................................... 8-5
To Determine Which FORM the DISPATCH System is Accessing .............................................. 8-5
To Read Online Modular man Pages for FORMS .......................................................................... 8-6
OMS ................................................................................................................................................ 8-6
OMS command line utilities and their usages ................................................................................ 8-6
OMSns - OMS name services. ........................................................................................................ 8-6
Usage: ............................................................................................................................................. 8-7
Examples: ........................................................................................................................................ 8-7
Starting OMSns: ............................................................................................................................. 8-8
OMSrouter – OMS router ............................................................................................................... 8-8
Usage: ............................................................................................................................................. 8-8
Notes: .............................................................................................................................................. 8-9
OMSnfs – OMS network file server ............................................................................................... 8-9
Usage: ............................................................................................................................................. 8-9
Notes: .............................................................................................................................................. 8-9
OMSdebug – OMS debug ............................................................................................................... 8-9
OMStip – OMS terminal emulation .............................................................................................. 8-10
OMSRUN ..................................................................................................................................... 8-10
Environment variables: ................................................................................................................. 8-10
OMSDOMAIN ............................................................................................................................. 8-10
January 2003 Contents - Continued

TOC - 4 System Administration Class
PSWD ........................................................................................................................................... 8-10

OMSRETRIES .............................................................................................................................. 8-10
OMSTIMEOUT ............................................................................................................................ 8-10
OMSDEBUG ................................................................................................................................ 8-11
pswd (Packet Switcher Daemon) Start-up (for sites not running the new OMS system) .......... 8-11
dbmsd (Database Management System Daemon) Start-up .......................................................... 8-12
................................................................................................................................................. 8-13
GPS (Global Positioning System) ................................................................................................. 8-13
To Initiate Changes to the config File ........................................................................................ 8-14
To Limit User Access to DISPATCH Accounts ........................................................................... 8-15
To Check Error Messages ............................................................................................................. 8-16
tk.err ........................................................................................................................................ 8-16
utility.err.................................................................................................................................. 8-17
lpd.errs .................................................................................................................................... 8-17
messages ................................................................................................................................. 8-18
To Check Memory Usage ............................................................................................................. 8-18
dmesg ...................................................................................................................................... 8-18
To Check Disk Usage ................................................................................................................... 8-19
df ............................................................................................................................................. 8-19
du and df ................................................................................................................................. 8-19
find .......................................................................................................................................... 8-20
ls -lagR .................................................................................................................................... 8-21
To Modify the Length of Time Transaction and Exception Files are Kept on the Machine ........ 8-21
To Copy Modified Files to Other Machines ................................................................................. 8-21
To Exclude Certain Files from Being Copied to Other Machines .......................................... 8-22
To Automatically Print Reports .................................................................................................... 8-22
To Keep Machines Synchronized ................................................................................................. 8-23
Endshift Scripts ............................................................................................................................. 8-23
Generic endshift script ............................................................................................................ 8-23
Client-specific endshift scripts ................................................................................................ 8-23
To Run PIT and SHIFT Database Backups .................................................................................. 8-25
Switching to the Backup Machine from the Main CPU (for older systems running packet switcher dae-
mon) ........................................................................................................................................ 8-26
Switching to the Main CPU from the Backup Machine ............................................................... 8-29
Creating and Adding Another DISPATCH User .......................................................................... 8-34
Backing-up System Files .............................................................................................................. 8-35
Contents - Continued January 2003
System Administration Class TOC - 5
To Retrieve DISPATCH files from Tape Backup ........................................................................ 8-36

The Diagnostic Laptop .................................................................................................................. 8-37
The Masterlink Tracking System (MTS) ...................................................................................... 8-38
Appendix A Computer Basics ................................................................................................................. A-1
Bits and Bytes ................................................................................................................................ A-1

Pages .............................................................................................................................................. A-1
Memory .......................................................................................................................................... A-1
Drive Format .................................................................................................................................. A-3
Drive Partitions .............................................................................................................................. A-3
Appendix B The dbclean Utility ..............................................................................................................B-1
The DBCLEAN Utility ...................................................................................................................B-1

The SUMMARIZE Utility ..............................................................................................................B-4
Summarize Switches .................................................................................................................B-4
Appendix C List of Generic config Variables ........................................................................................ C-1
Appendix D Output from mms keypad Symbols .................................................................................. D-1
Appendix E RF Coverage..........................................................................................................................E-1
January 2003 Contents - Continued

Introduction to the DISPATCH System
Administration Class
Notes
Introduction
Welcome to the Modular Mining Systems DISPATCH system administration
class.
The purpose of this system administration class is to show you how to

successfully perform certain routine system functions, diagnostics, and
repairs on the DISPATCH system.
System Administration Class Outline

To cover all the material that needs to be presented, the course has been
broken into eight major topics. We will cover the major topics in the
following order:
1. Overview of a System and Network
2. System Administrator Duties
3. System Directory Structure
4. Fundamental Linux Commands
5. The vi text Editor
6. Internal and External Hardware Components
7. Basic System Maintenance
8. DISPATCH Directory Structure and Related DISPATCH

Processes & Peripherals
Generally, following each topic, you will be given lab time or a practice
exercise to complete.
i-1
i-2
1
Overview of a System and Network
Notes
Goals for this Chapter
• Identify the two common views of a system
• Recognize the three major components of a system
• State the three major and minor sub-systems of a system
• Identify the host address in an Internet Protocol address
• State the importance of individual SCSI device IDs
• State the importance of the GNU/Linux kernel
• Describe the function of the kernel and shell
• State the importance of a desktop manager
Differences Between a System and a Network

The objective of this class is to help you understand the basics of system
administration. First, we must lay out the differences between a system and
a network.
A system is normally thought of as a self-contained unit that is usually

located in a single room. Typically a CPU, monitor, disk drive, printer, and
modem comprises a system.
A network, although similar to a system, entails the use of additional

equipment and is set up in a different manner. Typically many computers
(located throughout a mine site or office complex) connected to a hub via
physical interfaces comprise a network.
Two Common Views of a System

DISPATCH is an integrated software and hardware system for large-scale
mine management. As the system administrator for the mine it is necessary
for you to have an understanding of the system from different perspectives.
One perspective is to see the system as an integration of three major
components: the hardware, software, and an interface. Another view is to
understand the system from a functional perspective, that is, an integration
of various major and minor sub-systems.
Component View of a System
1-1
1-2 System Administration Class
Notes
Each system is a combination of three components: the hardware or physical
components, the software or programs, and an interface that connects the
first two components.
Typically, the hardware can include the following:
• central processing unit (cpu)

• monitor
• mouse
• keyboard
• other peripherals
- printer
- CD-ROM
- tape drive
- external drives
The software includes
• the operating system (OS)

• applications
The interface includes
• the Linux kernel
The DISPATCH system is also a networked system of computers and

components. Figure 1.1 illustrates this concept.
Overview of a System and Network January 2003

System Administration Class 1-3
Notes
Monitor
Tape Drive External Disk
Console CPU
3.5” Drive
CD-ROM
Keyboard
Mouse
Modem
Printer
Figure 1.1 Generic Hardware Components
The DISPATCH system was originally designed to run on Sun workstations

running the Solaris operating system. With the introduction of MasterLink,
DISPATCH now runs on a variety of platforms (Sun and PC) using the linux
operating system.
Functional View of a System
The functional view of a system is an integration of major and minor sub-

systems. The System Administrator is responsible for ensuring that these
systems run smoothly.
Major sub-systems include:
• System hardware - physical components
January 2003 Overview of a System and Network

Notes
• Disk systems - moves data to and from disks
• Operating system - coordinates other systems - facilitates
inter-process communication
Minor sub-systems include:
• Backup system - moves data from disk to tape for permanent storage
or emergency recovery
• Mail system - composition, delivery, and retrieval of electronic mail
messages
• uucp system - allows sites to exchange electronic mail with other
sites and to exchange files
• Printer system - allows data to be printed
• Security system - prevents unauthorized access and restricts
authorized access to data
• Internet System - enables the local network to connect with the
Internet
The advantage of this is that administrative tasks can be easily distributed

among experts in their respective subsystems if desired.
Networking
Networking is a large topic in it’s own right and cannot be completely covered
in this course. However, a brief description of the most common network
functionality is in order.
The most common form of networking in corporations today is the LAN (Local
Area Network) and the WAN (Wide Area Network). A LAN can be as simple
as two computers connected to each other via a basic hub, or a massive
infrastructure consisting of hundreds of computers connected via switches,
routers, hubs and miles of network cable. A WAN is a connection of networks
over large distances. There are, however, some basic components and
protocols that the simplest and most complex networks have in common.
Networking hardware
Each computer (or any network device) must have a NIC (network interface
card). To connect varies devices to the network, CAT5 (category 5) network
cable is used to connect to hubs, routers or switches. A hub can be thought of
as a junction box. Once connected to a hub, and with the proper network
configuration, the device will be able to communicate with other, similarly
configured network units.

Notes
Corporate LAN
4 port hub
Dispatch Computer
Networked Printer
Dispatch Computer
Dispatch Computer
Networked PC
Figure 1.2 Generic Small Network
Communications Protocol - TCP/IP
TCP/IP is the networking protocol suite most commonly used with UNIX,
MacOS, Windows, Linux, and most other operating systems. It is also the
native language of the Internet. TCP stands for Transmission Control
Protocol and IP stand for Internet Protocol.
TCP/IP defines a uniform programming interface to different types of

network hardware, guaranteeing that systems can exchange data
("interoperate") despite their many differences. IP, the suite’s underlying
delivery protocol, is the workhorse of the Internet. TCP and UDP (the User
Datagram Protocol) are transport protocols that are built on top of IP to
deliver packets to specific applications.
The system administrator assigns a name to each host on the local area
network. Smaller companies and networks use Class C Internet address. An
Internet address consists of four numeric fields separated by periods.
Example of Class C IP address
[192-223] [0-255] [0-255] [0-255]
IP= 201 . 23 . 178 . 18
Network Number: 201.23.178

Notes
Host Address: 18
The file /etc/hosts contains a registry of IP addresses and associated host

names. The System Administrator edits this file directly or from a GUI
(Graphical User Interface) networking utility. For users of Suse Linux for
Sparc, the gui is the yast2 configuration utility. For users of RedHat linux, the
gui resides in /usr/sbin and the executable is called "redhat-config-network".
SCSI
PC and Sun workstations use hard drives that are connected to the system
board or motherboard by a Small Computer System Interface (SCSI-
pronounced "scuzzy") connection. The SCSI standard allows different types
of devices to be connected together with one common interface. The SCSI
adapter card is located in one of the expansion slots inside the computer.
When the computer boots, each SCSI adapter interrogates all devices
connected to it and then enables them to function. Each SCSI device must be
on during this interrogation to operate during the session. SCSI devices
remain available as long as they remain connected and the computer is
operating.
SCSI allows multiple devices to be connected in a daisy chain with each

device having a unique target ID. On Sun computers, the adapter card is
usually ID 7. If two devices have the same ID, one device will not be
recognized during the interrogation and will not function during the session.
This is a common system set-up problem.
On the newer PC servers, the scsi devices are connected to an internal raid
controller card, which provides data protection via redundancy. This raid
configuration is done for you prior to recieving the computer. More SCSI
devices can be added by connecting them to the additional SCSI PCI card.
The GNU/Linux Operating System.

A computer requires an operating system and application to do work. The
workstations used in the DISPATCH system use a version of the GNU/Linux
operating system. Depending on the computer hardware, the system will
either be running Suse Sparc Linux, RedHat Linux or Mandrake Linux. The
underlying functionality of these distributions of GNU/Linux all work very
much alike.
The Linux kernel was developed in 1991 by Linus Torvalds, a Finnish student
at the University of Helsinki. The GNU "operating system" (GNU’s not Unix),
started in 1984, utilizes the linux kernel. Together, GNU and the linux kernel
comprise what most of us call "Linux". Since the Linux kernel is licensed
under the GNU project, all the source code is available for free. When a Linux
distribution is purchased, GNU/Linux is not being purchased, it’s the

compilation of programs and packaging that is being purchased. All versions

Notes
of GNU/Linux can be downloaded free off the Internet.
The operating system is made up of several layers with each layer

communicating with adjacent layers.
Kernel
The hardware in a computer is at the core of all computers. The kernel is the
part of the software in the operating system that manages the hardware.
Hardware
Kernel
Shell
User Applications
Figure 1.3 Operating System Hierarchy

Shells
Although gui’s are becoming more and more popular, the shell is still where
the system administrator spends most of his/her time. A shell window is the
input medium the administrator uses to talk to the operating system. The
kernel takes the text that we type into a shell window and converts it into
instructions that the hardware can understand. It is also the layer between
applications and the kernel.
There are a number of shells available to the Linux/Unix user: csh, ksh, bash,
tsch, zsh to name a few. The DISPATCH system you received from Modular
is configured to use the bash (bourne again shell).
Some of the features of the bash shell are:
• Aliases
• Command line editing
• History List
• Job Control
The Desktop Manager

:

Notes
A desktop manager is what controls the desktop environment. How the
menus look, how the borders on the windows and different applications
look...all are controlled by the desktop manager. In the Linux world, there
are a number of different desktop managers; KDE, Gnome, Enlightenment,
Afterstep, icewm, fvwm2, to name the more popular ones. The chosen
desktop manager for the DISPATCH system is icewm. Icewm is a fully
functional desktop/windowing environment with popup and drag right
menus and toolbar. It gives linux a more "windows" feel. Many DISPATCH
utilities can be found in menus as well as the standard DISPATCH control
panel.

2
System Administrator Duties
Notes
• Understand the primary responsibility of the System Administrator
• Identify the primary responsibilities of the System Administrator for
the customer installation
The System Administrator

This portion of the System Administration class introduces you to the concepts,
techniques and procedures that you need to know in order to accomplish your job as
System Administrator. Some clients operate very large mines while other mines are
relatively small. For this reason the duties and responsibilities of the System
Administrator vary. However, the primary responsibility of the System Administrator is
the proper functioning of the DISPATCH Mine Management System.
System Administrator Responsibilities
The following list contains some of the tasks assigned to a System Administrator. Each
System Administrator assigns different priorities to these tasks depending upon the
individual system installation and staffing. The general areas of responsibility include:
•Administer devices
Format disks
Clone disks
Partition and repartition disks
•Administer operating system
Understand system commands
Understand and use bash and csh shells
Use the vi editor
Use man pages
•Administer file systems
Understand the power of root ( / ) (Chapter 7)
Become super user
Understand path
Understand and set mount points
Understand system directory structure
2-1
Notes
Understand file types and file system types
Mount and unmount file systems
Understand symbolic links
Locate files
Gain full access to all file systems and resources
•Navigate the DISPATCH directory system
•Administer network services
Perform boot, shutdown and reboot
Perform periodic backups
Restore files from a backup
Understand network utilities
Automate certain system administration activities
•Administer printing
Install and maintain system printers
Use print commands
•Administer user accounts
Understand user groups
Create and delete user accounts
•Recognize and correct file access problems
Recognize and correct problems with search paths
Recognize and correct problems with permission and ownership
Troubleshoot and correct network and file access problems
•Install software
Install operating system software
Install bundled software
Install unbundled software
•Administer system security
Assign and maintain passwords
Read, assign and change permissions
Identify and change file ownership
•Monitor system performance
Understand and monitor disk usage and space
Verify and modify swap space
•Administer electronic mail
Setup mail (uucp) system
System Administrator Duties January 2003

Communicate with users Notes

•Install and remove system hardware
Set up modems
Install and remove tape drives
Install and remove CD-ROM
Install and remove other peripherals
•Maintain local documentation
•Train users
January 2003 System Administrator Duties

3
System Structure
Notes
• Understand the basic system structure elements: files, directories,
partitions, and disks
• Identify the three common file types
• Identify four less common file types
• State the directory location for the Device files
• Explain the purpose of Socket and Named Pipe files
• Explain the difference between a symbolic link and a hard link
• Identify the root directory
• Understand user groups
• Understand file types and permissions
• Identify the components of a pathname
• Understand symbolic links
• Explain mount points
Files
A file is a collection of data occupying space on a hard drive or other storage
medium in the system. It is a stream of data that is digitally recorded and
stored. Linux treats (almost) everything in the system as a file. This
includes all files, devices, directories and commands. Commands to control a
device or maintain the system begin as a file. Linux recognizes seven file
types, three common and four less common.
Note: Linux treats everything as a file regardless of the fact that they could be a
device, directory, or command. When you think you’re writing data to a file, you
could really be writing to a device, such as a printer, terminal, or monitor.
Three Common Files Types
The three common file types are plain, directory and link.
Plain Files
There are two flavors of plain files: ASCII and binary.
ASCII files use a subset of the 256 binary values. These values represent
text symbols such as letters, numerals, and punctuation. Examples of ASCII
3-1
Notes
files are simple text files, data files and script files. Data files are organized
tables of data used by specific commands. A script or shell script is a
structured list of shell commands organized to perform a particular task.
ASCII files are easily viewed and edited.
Binary files use all of the 256 binary values. Binary files are executable
programs and data files which use some type of formatting such as forms,
spreadsheet and word processor files. Binary files usually require special
tools to view or edit.
Directory Files
A directory is a container that contains other files, directories, and links. A

filing cabinet is a good analogy for a directory. The primary directory is the
/ (root) directory. Examples of directory files are /, /local, /local/mms/
dsp.
Link Files
A link file provides an alternate path to a location of another file or directory

on the system. There are symbolic and hard links.
A symbolic (sym) link can point to either a directory or file and that file or
directory can be any place on the system. This can shorten a pathname and/
or exploit available space on other partitions because it is not necessary to
have all files necessary to perform a particular process located in the same
partition as the link. Deleting a sym link does not delete the file that it
refers to.
A hard link can only point to a file. The reference can only be to a file in the
same partition as the link.
Caution: Deleting a hard link may result in loss of data. You should avoid using
hard links until you fully understand them.
Four Uncommon File Types
The four uncommon file types are device (block special and character
special), socket, and named pipe.
Device Files
Device files provide the interface between the operating system and
peripherals on the system. This type of file is usually located in the /dev
directory. The two types of device files are block special files and character
special files.
Block special files refer to a device that can handle data in multi-byte
chunks called blocks, such as disks or tapes. Character special files refer
to devices that can handle data in single bytes, such as terminals and
modems.
System Structure January 2003

Socket and Named Pipe Files Notes
These files generally provide communication between running application

programs, sometimes on different machines. Named pipes are for processes
on the same machines; sockets allow networked-based interprocess
communication.
Directories
Linux views all of the available space on a system in the form of the UNIX
file tree. The UNIX file tree always begins at the root or ( / ) directory and
covers all of the files found in all directories below this directory. The system
administrator controls access to the directory system.
Directory Command
/ (root) The first slash represents the top of the file system, or the
root directory. The boot directory resides in the / partition
and contains the program vmlinuz, which is the kernel.
The kernel is the heart of SunOS; it manages the system’s
hardware and schedules and terminates processes.
/dev This is the device directory, which contains files that
support such devices as the screen (/dev/tty), the mouse
(/dev/mouse), and the window system (/dev/win).
/etc This directory is often used by the system administrator for
system maintenance. There are several system
configurable files in this directory.
/tmp Temporary files are stored in this directory and are either
periodically removed by the system administrator or
deleted when the system reboots.
/usr This is a general purpose directory that contains important
subdirectories for commands. For example, /usr/bin
contains many of the Linux command programs, and
/usr/share/man contains the on-line help manual.
/var This directory holds log files and handles queues for
printing and mail.
Some Comments About Pathname
Pathname is the conventional notation for a location or node in the directory

structure and can designate files as well as directories. It allows the user to
locate a particular file, device or process in the system. The / (root)
directory is the starting point. Directories follow, then subdirectories, and
files. An example is /usr or /usr/local/myfile.
Understanding File Information
When the command ls -al is invoked, the contents of the current directory are printed on
the screen.
January 2003 System Structure

Notes File Type

Permissions
Link Count
Owner or User
-rw-r--r-- 1 root staff 46 Jul 19 19:58 Xservers

lrwxrwxrwx 1 root wheel 10 Jul 15 12:37 adm ->../var/adm
-rw-r--r-- 1 root staff 1024 Oct 14 1996 aliases.pag
drwxr-xr-x 2 root staff 512 Aug 22 13:08 apc_repository
Group it belongs to
Size/Bytes
Modification Date (& Time)
Name of the file
Figure 3.1 Interpretation of the ls Command with Group

Ownership
The first ten positions display the file type and its permissions.
Permissions
- r w x r w x r w x
File User Group All, World, or Other

Type
Figure 3.2 File Types and Permissions
File Types
- Indicates a Plain file.
d Indicates a Directory.
l Indicates a Symbolic Link.
b Indicates a Block Special file.
c Indicates a Character Special file.
s Indicates a Socket file.
p Indicates a Named Pipe file.
Plain files — Common Permission / Mode Indicators:
r Indicates permission to read the file.
w Indicates permission to write, modify, or delete the file.

x Indicates permission to execute the file. Notes
- Indicates that the permission is denied.
s Special s-bit (discussed later).
Directory Files — Common Permission / Mode Indicators:
r Indicates permission to "see" what files are in the directory.
w Indicates permission to create or delete files in the directory.
x Indicates permission for the user to "go to" the directory, to cd

to it, but not necessarily be able to "see" its contents or modify
it. See r and w permissions for directory files above.
- Indicates that the permission is denied.

t Sticky bit (discussed later).
Symbolic Link files — Common Permission / Mode Indicators
Since permissions are relevant only to the file to which the link is pointing and not to
the link itself, the permissions of a link file will usually show rwx in all permission
types.
Permissions
When a file is accessed, the system first checks for a match between the user
and the owner of the file. If there is a match, the user is granted the
indicated permissions in the user field. If the user is not the owner, the
system checks for a match between the user’s groups and the group the file
belongs to. If there is a match, the user is granted access to the file based on
the group permissions. If there is still not a match, the user is granted or
denied access to the file based on the world permissions.
Let’s analyze a few examples:
drwxr-xr-x
The d in the first position indicates that this file is a directory.
The rwx in the next three positions indicate that the list owner can list it
(see what is in the directory), can write to it, create, modify or delete files in
it, and cd to it.
The r-x in the next three positions indicate that members of the group can
list it (see what is in the directory), but cannot create or delete files in it. The
group can cd it.
The r-x in the next three positions indicate that members of the world can
list it (see what is in the directory), but cannot create or delete files in it. The
world can also cd it.

Notes
-rw-r--r--
The - in the first position indicates that this file is a plain file.
The rw- in the next three positions indicate that the owner can read it,
write (modify or delete) it, but cannot execute it.
The r-- in the next three positions indicate that members of the group can
read it, cannot write (modify or delete) it, and cannot execute it.
The r-- in the next three positions indicate that members of the world can
read it, cannot write (modify or delete) it, and cannot execute it.
-rwxr--r--
The - in the first position indicates that this file is a plain file.
The rwx in the next three positions indicate that the owner can read it,
write (modify or delete) it, and can execute it.
The r-- in the next three positions indicate that members of the group can
read it, but cannot write (modify or delete) it, and cannot execute it.
The r-- in the next three positions indicate that members of the world can
read it, but cannot write (modify or delete) it, and cannot execute it.
lrwxrwxrwx
The l in the first position indicates that this file is a symbolic or sym link.
Since permissions are relevant only to the file to which the link is pointing
and not to the link itself, the permissions of a link file will usually show rwx
in all permission groups.
drwx------
The d in the first position indicates that this file is a directory.
The rwx in the next three positions indicate that the user can list it, see
what is in the directory, can create or delete files in it, and can cd to it.
The --- in the next three positions indicate that the members of the group
cannot list it, cannot write to it, and cannot cd to it.
The --- in the next three positions indicate that members of world cannot
list it, cannot write to it, and cannot cd to it.
Symbolic Links
Symbolic links shorten pathnames, can point to a directory or file, and can
exploit available space on other partitions.

ln-s/usr/dsp/run/target/tla Notes
usr
dsp
tla
run
target file
or directory
Figure 3.3 Symbolic Link tla to target
In the diagram above, the conventional pathname to get to target from the
root is
/usr/dsp/run/target
However, with a symbolic link established (tla), the pathname from the
root to the target can be shortened to just
/tla
symbolic links work well to exploit available disk space across partitions.
Suppose target needs 50 MB of space and there is only 40 MB available on
the partition. However, there is 100 MB of space available on another
partition.
larger
partition
/
usr
usr2
dsp ln-s/usr2/target/dsp/run/target
run
target file
target file or directory
or directory
Figure 3.4 Symbolic Link target to usr2

Notes
You can create a symbolic link from the target partition to the larger
partition to exploit the 100 MB of space there.
Partitions
A partition is defined as a region of a disk. The Linux operating system
supports up to 16 partitions: 1 through 15, of which one is a hidden extended
partition. Depending on the version of Linux your site is running, the
partition naming convention, minimum size and comments will be similar to
the following table:
Table 1.1 Disk Partitions

Partition Name Partition Size Description
1 = /boot (primary) 30 MB First piece of Linux
(bootable linux
kernel)
2 = / (primary) 1 Gigabyte Linux system files.
3 = /usr (primary) 1 Gigabyte Linux support (/usr/
share/man...etc) files.
4 = extended no size extended partition
5 = swap (logical) 512 MB Typically RAM is
equal to the amount of
physical memory.
Location where
programs reside that
are idle but awaiting
use. Location where
process swapping is
done
6 = /local (logical) rest of disk DISPATCH software
is here. All user home
directories are here
Mount Points
Mount points enable the user to access data in partitions (a mount point is a
directory). Each partition, except swap, has a mount point.
Partition 1 has a mount point of /boot
Partition 2 has a mount point of /

Partition 3 has a mount point of /usr

Notes
Partition 4 is an extended partition to allow creation of logical partitions
and has no mount point
Partition 5 is swap space which is not mounted
Partition 6 has a mount point of /local
Most mount points are done automatically at boot or start-up time. The /
boot and root ( / ) partitions are automatically mounted by the kernel,
creating the structure or directories users interact with. Additional
partitions are mounted in order to access other important directories and
files. These are usually mounted automatically during the boot-up sequence;
however, they can be added after the fact, after the system boots up.
Disks
The primary data storage device is the hard drive system. Tapes and CD-
ROMs also store data. In order to use the stored data, computers use a
defined system for storing and retrieving the data. The system used is a
hierarchal structure of disks (drives), partitions, directories and file
systems.
The disks and partitions are the physical part of the system. The directories
and file systems are virtual. That means that the directories and file
systems can be located anywhere on the physical drives and partitions.
A disk is a hardware device that contains data storage media. The

DISPATCH software is loaded onto disks which are partitioned. Each
partition is created and identified depending upon its specific purpose.

bin
boot vmunix
dev
*
dsp /mms/dsp
mms
*
home /local/home (if needed for disk space)
lib
lost & adm

found
/
mnt
crash
mnt
log
Legend sbin
file
root net
executable
tmp
preserve
directory
usr
spool
proc
*mms modified
var tmp
symbolic
link
yp
Figure 3.5 The Linux root ( / ) Filesystem

X11R6
X11
5include /usr/X11R6
bin
etc
games
include
lib
local /local/mms/linux_<arch>
/usr man
man
share/man
share
openwin Software Dirs

(Suse only)
sbin
tmp /var/tmp
Legend:
spool /var/spool
directory
symbolic
link
Figure 3.6 The Linux /usr Filesystem (varies dependent on

Linux distribution)


Notes

Notes

4
Fundamental Linux Commands
Notes
• Understand some of the Linux commands and options
• Use wildcards and special characters
During this portion of the system administration class, we discuss some of

the most common Linux commands (and concepts) and their functions.
The ls Command
In order to manipulate the files on the system you must determine which
files are available for use and exactly where they reside. The ls command
by itself returns an alphabetical list of the contents of a directory. Depending
on your requirements, the following command line options (or switches)
provide different results:
Option Name Description

-a all Do not hide entries start with
"." (system files).
-A all Same as -a, except that the
entries for the current
directory and the parent of the
current directory are not listed.
-c creation with -lt: sort by, and show,
ctime (time of last modification
of file status information) with
-l: show ctime and sort by
name, otherwise: sort by ctime
-d directory If the ls argument filename is a
directory, lists only its name
-F classify Marks directories with a
trailing slash (/), executable
files with a trailing asterisk
(*), and links with a trailing at
sign (@).
Table 4.1 ls Options
4-1
Notes Option Name Description

-l long Displays detailed information
about each file and directory,
including permissions, owners,
size, number of links and when
the file was last modified.
-lg group Displays the group ownership
of a file in a long listing.
-p file-type Displays a slash at the end of
each directory name, to
distinguish them from
filename.
-r reverse Displays files in reverse
alphabetical order.
-R recursive Includes the contents of all
subdirectories.
-t time Displays files in order of
modification time.
-u used Lists files by the last access
-x wide List entries by lines instead of
by columns.
Table 4.1 ls Options
Example: ls -altR displays a long listing of all the files in the current directory and
all subdirectories of the current directory, sorted by the time each was last modified.
cd (change directory)
The cd command is used to move from one directory to another. If you do

not designate which directory, Linux assumes that you want to return to
your home directory. For example:
cd /home/jones
If you attempt to move to a directory that does not exist or is incorrectly
typed, Linux will return the following prompt:
hones: no such file or directory

Some options you can use with the cd command.
.. Parent directory of the current directory. You can move back

up one directory level with cd ..
Fundamental Linux Commands January 2003

~ This will return you to your home directory. For example: Notes
you could type cd /home/jones or cd ~jones to return
to your home directory.
pwd
When invoked, the pwd (present working directory) command will return
the directory you are currently in. This is useful if you are moving around in
different directories and momentarily forget where you are at.
history
The history command displays a list of previously entered commands in

the order of oldest to most recent. The shell stores a list of commands in the
order you enter them. Erroneous commands, such as spelling errors, are
stored in the history list as well as correct commands. You can repeat a
command by entering !n (where n is the number of the command in the
history list that you wish to repeat). Entering !! executes the last
command. It is also possible to edit a command from the history list. The
-r argument lists the commands in reverse order. To see a specific number
of commands use history n where n is the number desired. Use ^ to
modify and execute the previous command.
man
The man command displays information about commands from the on-line
reference manuals usually located in the /usr/share/man directory.
For example entering man ls displays information on the ls command.
clear
The clear command clears the screen and returns the cursor to the upper
left corner.
cp (copy file)
You can make exact duplicates of files using the cp command. To

accomplish this you must know the name of the file you desire to copy and
decide what name you want to call the new (copied) file. For example:
cp sample.a sample.b
Option Name Description

-i interactive Asks Yes or No before
copying
-p preserve Preserves the file date and
permission modes
Table 4.2 cp Options
January 2003 Fundamental Linux Commands

Notes Option Name Description

-r recursive When copying a directory,
copies its subdirectories
too, creating new
subdirectories as needed,
including backups if
included
Table 4.2 cp Options
grep
The grep command is used to locate files. This command is useful when
you are searching for a file and you only remember what information it
contained. To use the grep command you need to tell the it what you are
looking for. For example:
grep "trucks on standby" *

mkdir
The mkdir command is used to create a directory.
mv
The mv command moves a file from one location or renames a file to a new
name. When moving a file or directory a copy is made and then the original
is deleted. Moving a file to a new location where the same name file exists
overwrites the existing file. For example:
mv shift.am shift.pm
Option Name SunOS 4.x output Solaris output

-f force Forces the move even if the
file or directory permissions
do not allow it.
moving or renaming a file
Table 4.3 mv Options

rm Notes
The rm command deletes (removes) a file permanently. If there are other

links to the file, the file continues to exist, just not under the name you
removed. The rm command deletes just one name (link) to the file.
Option Name SunOS 4.x output Solaris output

-f force Forces removal even if the
file or directory
permissions do not allow it.
deleting each file
-r recursive Deletes an entire directory
and all the files it contains.
Table 4.4 rm Options
rmdir
The rmdir will permanently delete (or remove) a directory. The directory
must not contain any files.
Wildcards
Wildcards are special characters that are used in conjunction with the ls,
cp, rm, and mv commands. There are two wildcards used in Linux:
* Use * for any series of unknown character(s) or

number(s) in a filename.
? Any single character. Acts the same as *.
Caution: Wildcards also work when deleting and moving files.
January 2003 Fundamental Linux Commands

Notes Special Characters
The special characters allow a user to redirect output or as a sort of

shorthand when working with Linux files. Some examples include:
Character Function
| Pipeline allows filtering of one program by another
|more Causes one page of information to be displayed at a
time. Press any key to move down one page.
> Redirects output from commands into a specified
file rather than to the screen. When used with !,
overwrites the existing file.
>> Appends output to an existing file
< Redirects the contents of a file to a command.
~ Substitute for typing in the entire pathname of your
home directory. For example, typing cd ~/reports
moves you to the reports subdirectory of your home
directory. Also, cd ~otherperson would move you to
the otherperson home directory.
Using ~! returns to the SunOS prompt.
![event number] Executes the event specified by the event number.
For example: !25
!! Executes the previous event.
^ Allows you to modify and execute the previous
event.
Table 4.5 Special Characters and Functions

5
The vi Editor
Notes
• Identify the vi modes
• Open a vi file
• Navigate within a vi file
• Save and quit files
• Use some common vi commands
vi Modes
As system administrator, you must edit many files. This portion of the
system administrator class discusses how to use the vi (visual) editor.
The vi editor uses two modes: the command mode and the insert mode.
When the vi editor is invoked it is in the command mode. The command
mode allow you to move within a file, edit the file and issue commands.
The second mode is the insert mode which is used to insert text on the
screen (much like typing on a keyboard). There are several methods to enter
the insert mode.
a Insert text to the right of the cursor (the cursor will then
move to the right one space).
A Add new text at the end of the current line.
i Inserts text at the cursor.
I Add new text at the beginning of the current line.
o Insert a line under the current line.
O Insert a line above the current line.
Opening a File
vi is the Linux command that will invoke the vi editor allowing you to open
a new or existing file. To open a file you simply type:
vi [filename]
There can only be one unique filename within a directory. The filename can
include any ASCII character except a slash ( / ). If you want a space in the
5-1
Notes
filename, it must be preceded by a backslash ( \ ). When you are done, you
must press Return to tell Linux that you have finished your command.
Note: Linux is case-sensitive. Lowercase letters are distinct from uppercase

letters.
Navigating within a vi File

There are two basic methods of navigating within a vi file. To move around
your document, you must be in the command mode [Esc].
←, ↓, ↑, → Use the arrow keys to move around the file.
h, j, k, l These keys function the same as the arrow keys.
w Moves the cursor forward one word (punctuation and

symbols count as words). A number before w (i.e. 5w)
will move you forward five words.
b Allows you to move backwards one word at a time

(punctuation and symbols count as words). A number
before b (i.e. 5b) will move you backwards five words.
B Allows you to move backwards one word at a time

(punctuation not included). A number before B
(i.e. 5B) will move you backwards five words.
[Shift]-G Moves the cursor to the first letter of the first word of
the last line of text in the file.
1 [Shift]-G Moves the cursor to the first letter of the first word of
the first line of text in the file.
0 (Zero) Moves the cursor to the beginning of the current line.

$ Moves the cursor to the end of the current line.
H Moves the cursor to the top line on the screen.
M Moves the cursor to the middle line on the screen.
L Moves the cursor to the bottom line on the screen.
Saving and Quitting a File

There are several ways that you can save and/or exit a file. To save/quit a file
you should be in the command [Esc] mode.
:w Save the file remain in vi editor.
:w! Save the file, override normal checking.
:wq Save the file, exit from vi editor. Same as ZZ
The vi Editor January 2003

:wq! Save the file, no checking done, exit from vi editor. Notes
ZZ Save the file, exit from vi editor. Same as :wq or :x
:x Save the file, exit from vi editor. Same as :wq or ZZ
:q Exit from vi editor.
:q! Exit vi editor, discard changes.
If you find that you are editing a file and have inadvertently wiped out all of
the edits you have made in the session, you can return to the last saved
version of the file by typing:
:e!
Common vi Commands
In this section we discuss some of the commands available in vi that will
allow you to edit your files.
Copying Text
To copy text you will use the y (yank) command and the p (put)
command. The yank command places the copied text into a special buffer for
recall at the desired location in your file.
y[option] Yank (y) needs an object such as a word in order to copy

text. For example: yw will copy a word and y$ will
copy the line.
yy This will allow you to copy a line. To copy more than one
line place a number before the yy. For example: 5yy
Y This function the same as yy.
p The p command will put back (or paste) the last yank
(or deletion). Place the cursor where you want the text to
be and type p. The buffer contents are put on the line
below the cursor.
P The P command works much like p. Place the cursor

where you want the text to be and type P. The buffer
contents are put on the line above the cursor.
Deleting Text
In order to delete text you should be in the command mode [Esc]. There are
several commands that you can use.
x Deletes the character the cursor is currently on. This can be

used with a number. For example: 5x will delete five
characters.
January 2003 The vi Editor

Notes
X Deletes the character to the left of the cursor (like a backspace
key). This can be used with a number. For example: 5X will
delete five characters to the left of the cursor.
d You can delete text with the de command. d must be used

with a text object (such as dw for word).
db Deletes backwards.
dd Deletes the entire line. This can be used with a number. For
example: 5dd will delete five lines from the cursor down.
dE Deletes to the end of a word, including the punctuation. This

command will retain the space between the words.
dw Deletes a word beginning where the cursor is positioned. The

space following the word is also deleted.
d0 Deletes to the beginning of a line.
d$ Deletes to the end of the line. Same as D.
D Deletes to the end of the line. Same as d$.
Moving Text
In vi you can move text by deleting it, then pasting it where you desire. To do
this you could, for example, delete an entire line (dd) then put it (p) where
you want it to appear.
You could also use the yank (y) command in conjunction with the put (p)
command (see copying text).
Undo
If you make a mistake you can use the undo command in vi. There are two
undo commands:
u Undoes the last change you did to the file. A second u will
redo the undo.
U Undoes the changes in the current line. If you moved the

cursor from the line it will not work. You can still use u to
undo the last change.
These are just a few of the commands you can use to navigate through, input
data or edit your file. For other commands you can refer to the SSC Pocket
Tutorial, vi Reference Guide, or any other vi reference manual you have
available.
The vi Editor January 2003

6
External and Internal System
Hardware Components
Notes
• Identify external and internal hardware components.
External Components / Peripherals

This section discusses the various external system hardware components.
The following hardware components are located and discussed:
Console
Monitor
Keyboard
CPU Enclosure
3.5 inch Floppy Drive
Serial Devices
Modem
Printer
Packet Switcher
SCSI devices
Disk Drives
Tape Drives
CD ROM
Ports
SCSI Port
Serial Port
Power Cord
Ethernet Port
10baseT
Thin Net
Thick Net
Internal Components
This section discusses the various internal system hardware components.
After the system is shut down, some internal hardware components are
taken apart so their location can be pointed out.
Inside CPU Enclosure

Disk Drives
6-1
Notes
SIMMS
Power Supply
Fan
Mother Board
Inside SCSI Enclosure

SCSI ID
SCSI Jumpers
After the external and internal system hardware components are located
and discussed, reassemble the system and boot it up.
Monitor
Tape Drive External Disk
Console CPU
3.5” Drive
CD-ROM
Keyboard
Mouse
Modem
Printer
Figure 6.1 System Hardware - Generic Components
External and Internal System Hardware Components January 2003

7
Basic System Maintenance
Notes
• Understand the special privileges and responsibilities of root (super-
user)
• Basic routine maintenance
• Basic system maintenance commands
This portion of the class discusses basic system administrator activities and
certain commands associated with those activities necessary to maintain a
DISPATCH system.
root (super-user)
In order for the System Administrator to accomplish many of the assigned
tasks, it is necessary to have special privileges and access to the system.
These special privileges are held by a special user id (uid) called su (special
or super user id) in an account named root or ( / ). Note that the terms
root and super-user have the same meaning and are used interchangeably.
You must be root to perform many system administration tasks, such as
mounting and unmounting file systems, changing ownership or permissions
for a file or directory you do not own, backing up and restoring file systems,
creating device files, and shutting down the system.
When you have super user privileges, the shell provides a special # (pound
sign) prompt to remind you that you have extra access to the system.
Because unauthorized access to root can be a serious security breach,

always add a password to the root account. For enhanced security, change
the root password frequently.
su command ( super-user, root login, root user )
powers of root ( / )
view, modify, or delete any file
kill any process
execute any command
log in as super user
password
password file: /etc/passwd
7-1
login name
encrypted password
user identification number
group identification number
melvin:ab.F372L.Q:1225:170:happyknife:/home/melvin:/bin/csh
real name
home directory
The colon ( : ) is the field separator in /etc/passwd. shell
Figure 7.1 Interpreting the /etc/passwd file
create user accounts

groups and other users
groups file: /etc/group
delete user accounts

remove entry from /etc/passwd
recover disk space
chmod command (change file permissions)

binary
octal
symbolic
Binary Octal Symbolic

111 7 rwx
110 6 rw-
101 5 r-x
100 4 r--
011 3 -wx
010 2 -w-
001 1 --x
000 0 ---
Figure 7.2 Using the chmod command
chown command (change file owner)
Ex: # chown mms <filename>
chgrp command (change file group)
Ex: #chgrp modular <filename>
Basic System Maintenance January 2003

date command (sets system clock) Notes
Ex: # date 12171635 (mm/dd/hh/mm)
df (disk free space report) command
Ex: #df -h
will report back the filesystem in human readable format
reports the amount of occupied disk space, the amount of used and
available space, and how much of the file system’s storage space
has been used.
Option Name SunOS 4.x output

-h human--readable Report fileysystem size in
human readable format (1k,
243M)
-k type kilobytes Reports on file systems of
the block-size=1024
find command
Ex: $find ~/ -name testfile -print -

locates files with certain characteristics such as name, size,
and so on.
cron command
allows computer to automatically execute certain commands
at prescribed times
automates certain periodic sysadmin tasks such as backups
process management
Ex: #ps -ef will list all of the processes currently running
discussion of processes
ps command (process status)
kill command (terminate process)
mount command
/etc/vfstab
please read the man page on mount
mkswap command (add swap space without need to repartition

disk)
Ex: #dd if=/dev/zero of=/tmp/swapfile bs=1024 count=65536
January 2003 Basic System Maintenance

Notes
#mkswap /tmp/swapfile
#swapon /tmp/swfile
This will create a temporary 65M addition to your swap (virtual memory).
To make this permanent, create the swapfile to a permanent location, for
example /local. So, in the dd command above, replace /tmp with /local.
Then, add an entry into the /etc/fstab as follows:
/local/swapfile swap swap defaults 0 0 (format like rest of file).
certain important network commands
ssh, sftp and scp

rlogin (only applicable at older sites)
telnet (only applicable at older sites)
ping
system / network backup and restoral

discussion of incremental backup vs. full backup
tar command (tape archive storage)
mt command (magnetic tape storage)
backup scripts
backup files
restore files from backup
system security
user logins & passwords
good passwords and BAD passwords
intermachine ssh authentication (user)
monitoring and maintaining disk space

find command
df command (shows used and available space on a file partition)
du command (shows used space in a directory)
rm -r command (removes entire directory and contents)
system shutdown and reboot

shutdown commands
#shutdown now : puts the machine into single user mode
#shutdown -h now : halts the system for poweroff
#reboot : reboots the computer

January 2003 Basic System Maintenance

Notes

8
DISPATCH Directory Structure and
Related Processes & Peripherals
Notes
• Learn about the DISPATCH directory structure.
• Learn about variables.
• Learn the mms applications that are available.
• Use the man pages.
• Learn OMS, pswd and dbmsd start-up.
• Learn the GPS database system.
• Change the config file.
• Control access to DISPATCH accounts.
• Check memory and disk usage.
• Change file formats.
• Conduct backups.
• Switch from the main to the backup machine.
• Retrieve data from backup files.
• Create/add users to DISPATCH.
• Use the restore command.
• Install a modem.
• Install a printer.
• Familiarity with Diagnostic Laptop
• Familiarity with MTS (Masterlink Tracking System)
8-1
DISPATCH Directory Structure

The following information refers to key directories and files contained in the
DISPATCH directory structure as represented on the next page:
bin files are executables
cli contains client-specific directories
form contains directories of generic forms
sh contains shell scripts
the engl, span, common and deprecated files contain the generic
FORMS in the respective language
xyz file contains client-specific c code
etc contains the compiled config.prv file in cfg and cmt

formats
form contains MMS-created form files for specific client
hack contains client-created form files
psw contains packet switcher files
com contains config, privilege, and cron files
linux_v8 contains object files generated by client specific c code
sim contains simulated databases for mine modeling and testing
opns contains operational databases including shyymmdds.ddb,

shyymmdds.transact, shyymmdds.except, sumyymm.ddb,
gpsyymmdds.ddb, and all graphics, tire, plan, and drill
databases.
DISPATCH Directory Structure and Related Processes & Peripherals January 2003
Structure of DISPATCH Directory

(Client Acronym = xyz)
executables
mms
OMS bin
dbmsd
boot
sun4-x
sun5-x etc
sol2-x
classes
form
cfg
disp
tcl
hack
/local
usr2 mms dsp cli xyz psw
lib com
*
language
form common (Spanish,
French, etc.)
sh
linux_v8
sh
sim
shell scripts opns
symbolic links in root directory: symbolic links in dsp directory:

/dsp -> /mms/dsp client -> /dsp/cli/xyz
/mms -> /local/mms tcl -> /mms/tcl
*All languages will reside in subdirectories under common. The specific

"language" is set by defining the DSP_LANGUAGE environment variable.
Figure 8.1 DISPATCH Directory Structure
January 2003 DISPATCH Directory Structure and Related Processes & Peripherals
Notes mms (Modular Mining Systems)

Use the DISPATCH mms executable to bring up all utilities and
applications associated with the DISPATCH process.
The mms script resides in /dsp/bin/mms and allows the user to run these
applications: dbclean, env, keypad, reconcile, simulator,
summarize and which. Also included in the mms executable is the online
man pages (mmsman).
To View the DISPATCH Environment Variables

To view the DISPATCH environment variables, enter mms env at the
prompt.
tower:mms$ mms env

CLIENT=/dsp/cli/xyz/sun4-5.1/client
DSP_CLIENT=/dsp/cli/xyz
DSP_COM=/dsp/cli/xyz/com
DSP_CONFIG=/dsp/cli/xyz/etc/config.cfg
DSP_DDB=HOME
DSP_ETC=/dsp/cli/xyz/etc
DSP_FORM=/dsp/cli/xyz/hack:/dsp/cli/xyz/form:/mms/dsp/form/engl
DSP_FORMCLOBBER=yes
DSP_GFXCONFIG=DSP_OPNS/graphics
DSP_HELP=/dsp/cli/xyz/help:/mms/dsp/form/engl/help
DSP_OPNS=tower!/dsp/cli/xyz/opns:/dsp/cli/xyz/opns
DSP_PRIV=/mms/dsp/sh/allpriv.prv
DSP_STDFORM=/mms/dsp/form/engl
DSP_TKBITMAPS=/dsp/tcl/mms/bitmaps
DSP_TKIMAGES=/dsp/tcl/mms/images
FORMINI=DSP_FORM/formgui
KEYPAD=DSP_FORM/key220
PITDAT=SIM_OPNS/pitdat
RUN_EXCEPT=/mms/dsp/sh/exceptsun crttool
SIM_OPNS=/dsp/cli/xyz/sim
To Modify DISPATCH Environment Variables

file: /dsp/cli/xyz/com/dspenv
To change an environment variable, select the one that needs to be changed

and modify it. For instance, in the script below, the DSP_OPNS variable is
being modified.
#! /bin/sh Notes
# DISPATCH Utility System Module
# Copyright (c) Modular Mining Systems, 1982-1994
# All Rights Reserved
# $RCSfile: mms,v $
# $Revision: 50.23 $
# $Author: boynton $
# $Date: 1996/01/05 18:26:28 $
# $State: Exp $
# Purpose: Shell initialization file for environment variables needed by
the DISPATCH system processes.
#
# This script defines the environment in which the mms executable is run.
# The following environment variables are set:
#
#
# Set DSP_OPNS = /dsp/cli/???/opns:/dsp/mnt/opns
# At client sites the MACHINE file is used to specify the machine to
# use for database access.
#
if [ -f $DSP_CLIENT/opns/MACHINE ]; then
DSP_OPNS=`cat $DSP_CLIENT/opns/MACHINE`!$DSP_CLIENT/opns
else
DSP_OPNS=$DSP_CLIENT/opns
fi
DSP_OPNS=$DSP_OPNS:/dsp/mnt/95shfiles:/dsp/mnt/94shfiles:/dsp/mnt/93shfiles:
/dsp/mnt/92shfiles:/dsp/mnt/91shfiles:/dsp/mnt/90shfiles:/dsp/mnt/89shfiles
export DSP_OPNS
Once modified using the dspenv script above, the environment variable
DSP_OPNS changes to:
DSP_OPNS=tower!/dsp/cli/xyz/opns:/dsp/mnt/95shfiles:/dsp/94shfiles:
/dsp/mnt/93shfiles:/dsp/mnt/92shfiles:/dsp/mnt/91shfiles:/dsp/mnt/90shfiles:
/dsp/mnt/89shfiles:/dsp/cli/xyz/opns
To Bring up a New Keypad in Color

To bring up a new keypad in color, enter mms keypad color at the mms
prompt.
tower:mms$ mms keypad color
To Output the Generic FORMS Symbols

To output the current, generic FORMS symbols, enter:
mms keypad symbols
The output from this command is included in an appendix.
To Determine Which FORM the DISPATCH System is

Accessing
From any directory, you can determine which FORM the system is
accessing. At the prompt enter:
Notes
tower:mms$ mms which formini
The formini.frm file is at /mms/dsp/form/engl/formini.frm
To Read Online Modular man Pages for FORMS

To access man pages for FORMS, you need to know the FORM symbol.
Then, at the prompt, enter mmsman followed by the FORM symbol in
lowercase.
Since UNIX recognizes the $ character, you need to precede the $ with a
backslash ( \ ) or replace it with an underscore ( _ ).
For example, to access the man page for the FORM symbol T$ID, enter
mmsman t\$id or mmsman t_id
OMS
The processes OMSns, OMSnfs and OMSrouter necessary for the proper
communications are started automatically when the dispatcher logs in and
starts dispatch. What follows is a description of the processes.
OMS (Object Messaging System) is what allows us to communicate to all of

our DISPATCH field equipment. The hardware used to communicate at
your site can vary quite a bit. If yours is a new Masterlink site, then you’ll
be using the latest 802.11 wireless access points throughout your pit and
Masterlink hubs and radios on your mining equipment.
However, if you’re site is an upgrade site, you may be running OMS to your
bit regenerators and then still communicating via UHF to your field
equipment. We call this type of site a “hybrid” site.
There are three primary processes that must be running to communicate via
OMS: OMSns, OMSnfs, and OMSrouter. There are also some environment
variables which also must be set. These processes and variables are
described below.
OMS command line utilities and their usages
OMSns - OMS name services.
OMSns is a very important daemon that provides name translation services

for a variety of purposes. One example is to map IP addresses to symbolic
names for use in dispatch. For instance, _16043 might be a name of a truck,
but 167.96.31.43 might be the address of the truck. OMSns also maps RPC Notes
numbers to names, such as mapping the RPC called RESET to 0x020d.
Usage:
-d device-name : Lookup Device by either IP address or name.
-n network-name : Lookup network and its netmask.
-e env-name : Lookup the value for an environment variable
-p port-name : Lookup a port
-t type-name : Lookup a type name or number. This can be a RPC name, or

id.
-s : Display the status of the already running OMSns service.
-kill : Kill off an already running OMSns service.
ENV=VALUE : Set an environment variable to the specified value.
Examples:
> OMSns –s
OMSns: process 23701 on host 172.16.100.1
This will display the process id of the already running OMSns daemon, and
ip address of the machine running it.
> OMSns –d mpr0
192.168.192.0 mpr0 network
This will return the address (192.168.192.0) of the device you query for
(mpr0), as well as the type of device (network) it is listed as in the hosts file.
> OMSns –d _16043
167.96.31.43 _16043 truck
This is just another example of querying for a device, in this case it is a

truck.
> OMSns –d 167.96.31.43
167.96.31.43 _16043 truck
Notes
Here the address was passed as an argument instead of the name. The same
information is returned whether you specify the name or address.
Starting OMSns:
Several internal variables are important for OMS, and should be passed to
OMSns on startup. Most of the time the script /mms/OMS/OMSrun should
be used to start the daemons, but if you want to start it manually, make sure
the following environment variables are set:
BOOTDIR=/mms/boot :This directory tells OMS where to find boot files used
to load embedded devices.
OMSROOT=/mms/OMS :This is the directory of where the system rpc and

hosts files can be found.
DIR=/mms/dsp/client/psw :This is the directory to look for client specific

files.
To start OMSns, you would give the following options:
OMSns BOOTDIR=/mms/boot OMSROOT=/mms/OMS DIR=/mms/dsp/

client/psw
Note, if you start OMSns while another process is already running on the
same OMSDOMAIN, the new one will send the old one a message to shut
down, and the new one will take over, even if the old process was running on
another machine.
OMSrouter – OMS router

OMSrouter is used to communicate with the serial port, and also used when
OMSDOMAIN is set to localhost, so applications can talk to each other
without using multicast messages. It works by setting up routes between
serial ports and ip addresses (or symbolic names that represent ip
addresses). Usually mpr0 is setup to connect to the first serial port and mpr1
is connected to the second port.
Usage:
-s : Display the status of the already running OMSrouter service.
-kill : Kill off an already running OMSrouter service.
-pwrup 0 : make device stay in BOOT ROM
-pwrup 1 : make device run application
-speed bps : set serial port speed in bits/sec
-debug file : print all SLIP frames to debug-file
-proto udp|rpc : define transport protocol Notes
-gw gateway : define gateway route for previous port
port ipaddr : serial ports and IP address
Examples:
OMSrouter –pwrup 0 /dev/ttyS0 mpr0 /dev/ttyS1 mpr1
This will tell OMSrouter to instruct a hub that is connected to the first or
second serial port to stay in the BOOT ROM after it powers up. It will also
setup a route between mpr0 and the first serial port, and mpr1 and the
second port.
OMSrouter –pwrup 0 com1 mpr0 com2 mpr1

This is the same as above, only ports as they would be used in win-
dows.
Notes:
If OMSrun is used to start the OMS daemons, the contents of /mms/OMS/
ports.<architecture> or /mms/OMS/ports.<hostname> file is passed to the
OMSrouter process. You can modify the /mms/OMS/ports.<hostname> to
have any machine specific options you want to have passed to OMSrouter
every time it starts.
OMSnfs – OMS network file server

OMSnfs provides a network file system for embedded devices. This is used
for loading embedded code into the flash memory on hubs and GCs. OMSnfs
uses the DIR and BOOTDIR variables from OMSns to determine what files
are exportable on the network.
Usage:
-s : Display the status of the already running OMSnfs service.
-kill : Kill off an already running OMSnfs service.
Notes:
OMSnfs depends heavily on scripts, which in turn rely on some common
Unix applications, including sed and awk. The standard scripts that are
used for loading hubs and GCs also require the C preprocessor, which must
be located at /usr/local/bin/cpp. It is acceptable for this to be a symbolic link
under Linux.
OMSdebug – OMS debug
Notes Usage:
-v Verbose mode. Will attempt to decode contents of vectors.
-d device Only show packets to or from the device specified.
OMStip – OMS terminal emulation

OMStip allows you to remotely connect to a Modular Mining Systems hub or
GC, and run an interactive object shell on that device. The device can be
connected via the serial port, ethernet, wireless (such as 802.11), or UHF.
-d device Connect to the device specified (Note: if the –d option is miss-

ing, the last argument used is assumed to be the device you
want to connect to.)
-log file Overwrite and log the OMStip session to the file specified
OMSRUN
OMSrun is located in /mms/OMS and is used to start all of the OMS
daemons on a system.
Environment variables:
OMSDOMAIN
OMSDOMAIN is represented as an IP address, but should not be confused
with an actual IP address. The address used for the OMSDOMAIN can be
thought of as a group address that ties multiple OMS and/or dispatch
applications together in a virtual network. At the lowest level, OMS domain
is used to generate a multicast address that each application can listen to.
The address used for OMSDOMAIN can be the address of one of the
computers on the network, or the address of an ethernet connected device, or
even an address that isn’t used elsewhere on the network.
PSWD
PSWD should be set to the exact same value as OMSDOMAIN for
DISPATCH operation.
OMSRETRIES
OMSRETRIES specifies how many retries will be sent for an
unacknowledged message. If OMSRETRIES is set to four, a message will be
tried 4 times before returning a no-talk error message.
OMSTIMEOUT
OMSTIMEOUT specifies how long to wait for an acknowledgment before
sending a retry.
OMSDEBUG Notes
If OMSDEBUG is set with a nonzero value, the applications will generate

diagnostic messages for each message sent or received on the network.
pswd (Packet Switcher Daemon) Start-up (for sites not

running the new OMS system)
The packet switcher daemon (pswd) is the software that converts and routes
radio traffic from the field to the DISPATCH process and vice versa. Without
the pswd, communication to any field equipment would be impossible.
The pswd executable is located at /dsp/psw/bin/pswd and can be

invoked by itself or with the following arguments: -p, -r, -R, and -s. The
argument kill can be used with pswd, but only after the pswd is
invoked.
pswd Invokes the packet switcher daemon.
pswd -p Ping the packet switcher daemon.
pswd -r Reload the packet switcher code into

the packet switcher.
pswd -R Display the current template for a

given rpc (remote procedure call).
pswd -s [machine_ name] Status display of pswd on

machine_name. If name is omitted,
pswd -s returns the status of the
current machine.
pswd -kill [machine_name] Stops the pswd on designated

machine.
Some examples of invoking pswd and the responses:
Notes tower:mms$ pswd -p

pswd on host tower is alive
tower:mms$ pswd -kill tower
tower:mms$ pswd -R ARRIVE

0x0006 ARRIVE dispatch v
tower:mms$ pswd -s
pswd (pid#177) started from inetd at Fri Feb 11 10:20:07 1997
/dev/ttyb Status:ready Bytes in Buffer:0 Errors:0 Retraies:601 RNRs:2
DIR=/dsp/cli/xyz/psw
LOGDIR=/dsp/cli/xyz/psw/log
PSW=/mms/psw
backup.2385 @ backup:2385 port:1573
dispatch @ tower:303 port:1062
rpc GPS-ARRIVE
rpc GPS-CONFIG
rpc sm-danger
devices auxeqmt
devices truck
tower.175 @ tower:175 port:1041
rpc TPC
It is possible to connect to the pswd running on the main machine from any
computer loaded with the DISPATCH executables. Simply set the
environment variable PSWD to the machine running the pswd:
tower:mms$ setenv PSWD demo

tower:mms$ mms keypad form=psw-debug
As already noted, the packet switcher daemon automatically starts when

the packet switcher is accessed.
The following entry in the file /etc/inetd.conf automatically starts the

pswd daemon:
pswd/1 tli rpc/udp wait mms /bin/sh sh /etc/pswd
as well as the following in the /etc/pswd file
exec /mms/psw/bin/pswd /dev/ttya 38400 DIR=/dsp/cli/xyz/psw

LOGDIR=dsp/cli/ xyz/psw/log HOSTFILE=/psw/etc/hosts.pkt-mofrm
Note: The above entry should appear on only one line.
dbmsd (Database Management System Daemon)

Start-up
The database daemon (dbmsd) allows each user and DISPATCH to access all
DISPATCH-related databases. Each connection to a database is in real time
and a change made by any user will affect all other users immediately.
The only valid arguments for dbmsd are -status machine_name and Notes
-kill machine_name.
Some examples:
tower:mms$ dbmsd -status tower

dbmsd:110 (pid#245) started from inetd at Fri Feb 14 10:20:17 1997
Stale :251 NoOpen :2
/dsp/cli/xyz/opns/pitdat.ddb
Handle : 1799/321066
Opens :20 Reads :13352680 ReadMs:497971 Finds:16678 Writes:429068
Updates:4573 Deletes:3380 GetQs :414031 PutQs :456989 Errors:0
Signal1:tower.1261
Signal0:tower.1064
/dsp/cli/xyz/opns/tire9602.ddb
Handle : 1799/322556
Opens :1 Reads :428 ReadMs:30 Finds :0 Writes:0
/dsp/cli/xyz/opns/sh970218a.ddb
Handle : 1799/322251
/dsp/cli/xyz/opns/sum9602.ddb
Handle : 1799/321353
tower:mms$
tower:mms$ dbmsd -kill tower

dbmsd: host tower shutdown
The database management system daemon automatically starts when the

database is accessed. The script resides in /dsp/bin and is initiated by a
remote procedure call (rpc) in inetd.conf
dbmsd_110/1 tli rpc/tcp wait root /dsp/bin/dbmsd rpc.dbmsd.110 user=mms
GPS (Global Positioning System)

For clients who have GPS installed on their system, each piece of equipment
stores its GPS location on board every 30 seconds and transmits an array of
locations to DISPATCH every 8 minutes.
A script (/dsp/sh/gps_data_monitor) is run in the background to

capture the arrays of locations and then stores them in the database file
/dsp/cli/xyz/opns/gpsyymmdds.ddb.
Once the database is created, several GPS tools can be used to analyze the
data. One of these tools is the graphics utility. Another one is the FORM
GPS.
Notes
To invoke the gps_data_monitor script at boot time on a Linux machine,
do the following:
#!/bin/sh
if [ -f /dsp/sh/gps_data_monitor ]; then
su mms -c /dsp/sh/gps_data_monitor & echo ' gps_data_monitor
'
To Initiate Changes to the config File

file: /dsp/cli/xyz/com/config.prv
The config.prv file allows each client to customize DISPATCH code to

suit their mining practices. The appendix includes a complete generic list of
config variables.
Whenever you make changes to the config file, you must enter the
following command at the prompt to initiate the changes:
tower:com$ mms config in=DSP_COM/config.prv
This command creates two files:
/dsp/cli/xyz/etc/config.cfg and
/dsp/cli/xyz/etc/config.cmt
Once the files have been configured, all DISPATCH processes will
automatically read in the changes.
To view the changes to the config file, enter:
tower:mms$ mms config show=lptrucksize

$ CONFIG LPTRUCKSIZE 200.0
Bytes Used: 22645 out of 40000
CONFIG's Used: 810 out of 1000
Longest Hash List: 36
Average Search: 12
Another function of the config.prv file is to override minimum and

maximum values of variables set in C code.
An example of decreasing the minimum shovel size:
$ CONFIG E$SIZE_MIN 1
An example of increasing the fuel tank size of loaders:
$CONFIG E$FUEL_MAX 9999
It is also possible to create configurations for mine-specific purposes:
$ CONFIG BCM_CONVERSION 2.7
In this example, whenever you needed to access this value in a report, you Notes
would use:
.equ BCM_CONVERSION_FACTOR CONFIG( "BCM_CONVERSION" )
To Limit User Access to DISPATCH Accounts

file: /dsp/cli/xyz/com/username.prv
The system administrator can limit user access to DISPATCH utilities

based on entries in the /dsp/cli/xyz/com/username.prv file.
In the following file, the user cannot access the utilities that have the word
NONE in the Access Privilege column.
DISPATCH Privilege File
Protection DB file or Image Access Privilege

$ FORM * EXECUTE
$ FILE * WRITE
$ FORM AUXMOD NONE
$ FORM CUSTOMREP NONE
$ FORM REP_SUMREPORT NONE
$ FORM BREAKS NONE
$ FORM CONFIG NONE
DISPATCH Privilege File
Protection DB file or Image Access Privilege

$ FORM OUT_FUEL NONE
$ FORM FUEL NONE
$ FORM GRADE NONE
$ FORM GRADE _ORE NONE
$ FORM LOADCHNG_MOD NONE
$ FORM LOADCHNG NONE
$ FORM LOCMOD NONE
$ FORM PANELID NONE
$ FORM PSW-DEBUG NONE
$ FORM REASON NONE
$ FORM ROADMOD NONE
$ FORM SHIFTEQMT NONE
$ FORM SHIFTLOC NONE
$ FORM SHIFTROOT NONE
$ FORM SHVLMOD NONE
$ FORM STATCHNG NONE
$ FORM TIRE NONE
$ FORM TRUCKMOD NONE
$ FORM WORKRMOD NONE
When an entry is placed in the username.prv file and the keypad is

invoked, the button remains on the screen but is blank and has no
functionality.
Notes
It is possible to delete or change button functionality on tcl keypads, those
brought up by the control panel, by creating and editing the following file:
/dsp/cli/xyz/tcl/selClientsForms.[username].tcl
The following is an example of this file:
# Purpose - Customize the FORMS selector for a particular user.

# Used to change Functionality and/or appearance of a button
# Usage: selReplaceButton list_name present_button_name
# changed_name changed_form changed_icon changed_fore_color changed_back_color
#
# for upper window
selReplaceButton selUtBtn Dispatch Monitor "dispatch_mon" \"\" White RoyalBlue
#for lower window

selReplaceButton selCoBtn WorkrMod Oper "workrmod_mon" \"\" White RoyalBlue
#
# Used to delete a button.
# Usage: selKillButton list_name button_name
#
selKillButton selCoBtn LocMod
To Check Error Messages

There are four files that contain error messages on the Sun: tk.err,
utility.err, lpd-errs, and a series of messages files.
tk.err
The file /dsp/cli/xyz/opns/tk.err contains errors associated with

window display problems (tk), usually the control panel (crttool-3.0),
and graphics.
The following is an example of a tk.err file:
mms running "crttool-3.0" on tower (Linux 2.4.14) on Thu Notes

Sep 19 08:50:56 MST 1996
crttool input: no shell active
while executing
"$w input "$akey""
invoked from within
"if { $mods != "M" } { # Not Meta key
$w input "$akey"
} elseif { $crtInfo($w,tt_han) != "" } {
# Meta key in tcltalk mode
$w input "$mods ..."
invoked from within
"if {("$akey" != "") && ($nsym <= 255)} {
if { $mods != "M" } { # Not Meta key
$w input "$akey"
} elseif { $crtInfo($w,tt_han) != "" } {
# ..."
(procedure "crtKey" line 7)
invoked from within
"crtKey .crt1.crt i 105 "i" N"
(command bound to event)
utility.err
The file /dsp/cli/xyz/opns/utility.err contains errors associated

with the DISPATCH process.
tower!dispatch@nil at 10-DEC-96:20:51:41 in dispatch: DBREAD: Can't read record

120984 in excav.
tower!dispatch@nil at 10-DEC-96:20:51:46 in dispatch: DBREAD: Can't read record 0 in

path.
tower!dispatch@nil at 16-DEC-96:08:48:48 in dispatch: DBREAD: Can't read record 54924

in shifteqmt.
tower!dispatch@nil at 16-DEC-96:08:54:50 in dispatch: DBREAD: Can't read record 54924

in shifteqmt.
Below are examples of four DBREAD error entries in the utility.err

file. Note that when the record is in shiftxxxx, the shift database must be
cleaned while other errors indicate that the pit database must be cleaned.
lpd.errs
The file /var/adm/lpd-errs contains errors associated with line

printers.
The following are some examples of the error messages:
Nov 25 14:25:18 tower lpd[200]: unable to get hostname for remote machine backup
Dec 15 02:32:22 tower lpd[200]: unable to get hostname for remote machine backup
Dec 15 02:32:25 tower lpd[187]: printer/tcp: unknown service
Dec 16 05:43:37 tower lpd[203]: unable to get hostname for remote machine backup
Dec 16 05:43:40 tower lpd[187]: printer/tcp: unknown service
Notes messages
The directory /var/log contains several messages files. These message

files contain Linux system errors. The most recent message file would be
messages, then messages.0, messages.1, and so on.
The following are examples of the messages file:
Jun 11 14:11:06 linuxinetd[139]: /psw/bin/pswd: Segmentation fault - core dumped

Jun 13 10:35:22 linux su: FAILED SU (to root) mms on /dev/pts/0
Jun 17 17:40:43 linux dhcpd[6274]: broadcasting second DHCP_DISCOVER
Jun 17 17:40:43 linux kernel: Loaded 252 symbols from 4 modules.
To Check Memory Usage

The easiest way to check memory usage in linux is via the "top" utility. Top
reports a number of system statistics.
As seen in the above figure, top reports both physical memory (Mem:) and
Swap memory (Swap:). If, for whatever reason your swap memory is running
low, you can add more swap to the system as outlined in chapter 7.
dmesg
dmesg is a "booting" report from the kernel. As a system boots, the kernel
reports what hardware has been found, and if so, what the system is
referring to it as. We can use this report to see how much physical memory is
installed on our system, check the size of the hard drives and determine
whether the system has found all the hardware we expect it to find. The
syntax to run dmesg is as follows:
# dmesg |more Notes
Piping dmesg to more allows us to look at the output a screen at a time.
To Check Disk Usage

There are four versatile commands to help you check disk usage: df, du,
find, and ls -lagR.
df
This command reports the amount of disk space occupied by currently

mounted file systems, the amount of used and available space, and how
much of the file system’s total capacity has been used.
Without arguments, df displays information on all mounted file systems.

The following is an example:
tower:mms$ df
Filesystem 1k-blocks Used Avail Use Mounted on
/dev/hda1 491884 231296 260588 48% /
/dev/hda2 32207 4238 26306 14% /boot
/dev/hda6 5752980 198776 5554204 4% /local
/dev/hda5 2097576 542768 1554808 26% /usr
shmfs 93352 0 93352 0% /dev/shm
du and df
This command reports the number of kilobytes contained in all files and,
recursively, directories within each specified directory or specified file.
The following are examples, with short explanations, of using the du

command:
a) To list file size of each file and directory in the current directory:
tower:home$ du -s *
67 truckshop
2985 dispmgr
100 dispatch
98 engineering
984 keypad
4427 mms
1214 shop
5984 clerk
b) To sort files from the largest to the smallest:
tower:home$ du -s * | sort -nr |more

5987 clerk
4428 mms
2985 dispmgr
Notes
1214 shop
984 keypad
100 dispatch
98 engineering
67 truckshop
c) To list the size of the current directory:
tower:home$ du -s.
15865
d) To list the files, directories, and all recursive file sizes, sorted by size
from largest to smallest:
tower:home$ du . | sort -nr |more

15865 .
5987 ./clerk
4428 ./mms
3485 ./clerk/live
3461 ./clerk/live/archive
2985 ./dispmgr
1214 ./shop
984 ./keypad
101 ./clerk/new
100 ./dispatch
98 ./engineering
70 ./clerk/dat
67 ./truckshop
38 ./dispmgr/backup_log
28 ./clerk/RCS
18 ./truckshop/limits
15 ./clerk/files
11 ./truckshop/bin
7 ./clerk/files/realtime
7 ./clerk/blablabla
5 ./clerk/transfer
3 ./clerk/live/realtime
etc...
du and df can be used in conjunction with the -h switch.

The -h switch will output the size in "human read-
able" format: 100K, 2M, 3G (kilobytes, Megabytes
and Gigabytes).
find
This command helps locate files quickly. The syntax for this command is:
find [start_position] -name [item_name] [expression]
find recursively descends the directory hierachy from each

start_position, seeking files that match the item_name and, once
found, executes the expression. For example:
tower:mms$ cd home Notes

tower:home$ find . -name core -print
./keypad/core
find is also effective in finding and deleting files that are over x days old.
In the following example, find searches for certain files over 10 days old and
then deletes them:
tower:mms$ cd home
tower:home$ find . -name core -mtime +10 -exec rm -f {} \;
To search for files that do not match the item_name exactly, use wildcards:
tower:mms$ find / -name "*fred*" -print
ls -lagR
This command does a recursive, long file list.
To Modify the Length of Time Transaction and

Exception Files are Kept on the Machine
file: /dsp/cli/xyz/com/environ
To change the length of time, modify the current value. For instance, to
change the PSWD_LOG from its current 5 days to 10 days, change the 5 to
a 10 and then save the file.
#!/bin/sh
#
# xyz-specific environment variable overrides
#
DEL_PSWD_LOG=5 # Pswd log files - 5 days
DEL_TRANSACT=15 # Transaction files - 15 days
DEL_EXCEPT=5 # Exception files - 5 days
DEL_COMM=5 # Comm files - 5 days
DEL_GPS_DDB=10 # GPS Path .ddb files - 15 days
DEL_GPS_DAT=5 # GPS Path .tcl/.dat files - 5 days
export DEL_PSWD_LOG DEL_TRANSACT DEL_EXCEPT DEL_COMM \
DEL_GPS_DDB DEL_GPS_DAT
To Copy Modified Files to Other Machines

file: /dsp/cli/xyz/com/environ
In the following example, "tower" is the name of the master machine

which is set up to copy files from itself to the machines listed in the
DSPTAR_ARGS= line.
#!/bin/sh
#
# Set dsptar options to use version 5.1;
#
Notes
DSPTAR_VERSION=5.1; export DSPTAR_VERSION
DSPTAR_EXCLUDE=/dsp/cli/xyz/com/dsptar.exclude
export DSPTAR_EXCLUDE
host=ùname -n`
if [ "$host" = "tower" ]; then
DSPTAR_ARGS="-src -hack backup -src -hack eng -src -hack keypad"
else
DSPTAR_ARGS="dsptar only from tower!"
fi
To Exclude Certain Files from Being Copied to Other Machines
file: /dsp/cli/xyz/com/dsptar.exclude
In order to exclude certain files from being copied to other machines, add
lines to the dsptar.exclude file identifying the to-be-excluded filename.
In the example below, each line identifies a file that will not be copied to
other machines.
/dsp/cli/xyz/psw/truck.hosts
/dsp/cli/xyz/psw/excav.hosts
/dsp/cli/xyz/psw/pitloc.hosts
/dsp/cli/xyz/psw/auxeqmt.hosts
/dsp/cli/xyz/tcl/cprestart_config.tcl
To Automatically Print Reports

file: /dsp/cli/xyz/com/autoreps
#! /bin/csh
/dsp/bin/mms keypad pit=DSP_OPNS/pitdat batch <<"eof" >/
dev/null
PRINT := "tower"
VERBOSE := 0
MORE := 0
REP$CONTIN := 0
REP$RANGE.0 := "YES"
FORM := "SUM_TRUCK"
FORM := "SUM_EXCAV"
FORM := "SUM_STATUS"
DB$SHIFT := "TOD -3"
FORM := "PIT_TRUCK"
FORM := "PIT_TRUCK"
FORM := "PIT_TRUCK"
exit
"eof"
Edit the crontab file to add the following line:
tower:mms$ crontab -e
10 8 * * * /dsp/cli/xyz/com/autoreps
Note: The 10 8 * * * portion of the above line represents the minutes, Notes
hours, day of month, month, day of week. For more information on crontab
enter "man crontab" from a shell window.
To Keep Machines Synchronized

To keep all the machines synchronized, as super-user add the following line
to the crontab file.
1 0 * * * rdate tower >/dev/null 2>&1
Endshift Scripts
There are two endshift scripts: generic and client-specific.
Generic endshift script
The generic endshift script closes the current data base, closes log files such
as shyymmdds.transact and shyymmdds.except, deletes transaction
and exception files older than ten days, summarizes the just-closed shift file,
copies the just-closed shift files to a backup computer.
The generic endshift script is called from the FORM act_dispatch.frm

at the end of the current shift and resides in /dsp/sh/dspendshift
.expr ACT$ENDSHIFT \
COMM$ENDSHIFT,
ACCESS( "/dsp/sh/dspendshift", "x" ) ?
SPAWN( "endshift",
(str SH$DATE.4)[/bin/sh -x /dsp/sh/dspendshift%z],
"/dev/null",
"/dsp/mnt/opns/endshift.log" )
Client-specific endshift scripts
A client-specific endshift script can be tailored to suit the needs of the client.
The following sample endshift routine re-summarizes the last seven days,
summarizes the entire month, and copies shift files to a third machine. It
calls the dspendshift script in /dsp/cli/xyz/com/ A brief
explanation follows the sample script.
.expr ACT$ENDSHIFT \
COMM$ENDSHIFT,
ACCESS("/dsp/cli/xyz/com/dspendshift", "x" ) ?
SPAWN("endshift",
(str SH$DATE.4, shiftlast)[/bin/sh -x /dsp/cli/xyz/
com/dspendshift %z %z],
"/dev/null",
"/dsp/cli/xyz/opns/endshift.log" )
Following is the file: /dsp/cli/xyz/com/dspendshift
Notes #! /bin/sh
#
/dsp/sh/dspendshift $1
#
mms reconcile sh=/dsp/mnt/opns/sh$2 la=/dsp/mnt/opns/$1
mms summarize update sh=/dsp/mnt/opns/sh$2 la=/dsp/mnt/
opns/$1
#
day=`date +%d`
hour=`date +%H`
month=`date +%m`
year=`date +%y`
sumdb=sum$year$month
shift=$1
#
if [ $# -lt 2 -o "$2" = `hostname` ]; then
if [ "$day" = "01" -a "$hour" = "00" ]; then
mms summarize range=$sumdb
fi
fi
#
if ping xyz2 5 >/dev/null; then
rcp /dsp/mnt/opns/$shift.ddb xyz2:/dsp/cli/xyz/opnsbck/
$shift.ddb
rsh xyz2 /usr/local/bin/gzip /dsp/cli/xyz/opnsbck/
$shift.ddb
fi
The following is a brief explanation of the preceding sample of a client-

specific endscript:
/dsp/sh/dspendshift $1
First runs a generic endshift.
mms reconcile sh=/dsp/mnt/opns/sh$2 la=/dsp/mnt/opns/$1

mms summarize update sh=/dsp/mnt/opns/sh$2 la=/dsp/mnt/opns/$1
Reconciles and summarizes last seven days.
day=`date +%d`
hour=`date +%H`
month=`date +%m`
year=`date +%y`
sumdb=sum$year$month
shift=$1
if [ $# -lt 2 -o "$2" = `hostname` ]; then

if [ "$day" = "01" -a "$hour" = "00" ]; then
mms summarize range=$sumdb
fi
fi
Summarizes the monthly range on the first night shift of every month.
if ping xyz2 5 >/dev/null; then
rcp /dsp/mnt/opns/$shift.ddb xyz2:/dsp/cli/xyz/opnsbck/$shift.ddb
rsh xyz2 /usr/local/bin/gzip /dsp/cli/xyz/opnsbck/$shift.ddb

Notes
fi
Copies the data to xyz2 and compresses it
To Run PIT and SHIFT Database Backups

In case of data corruption or disk failure, it is important to generate backups
of the pit and shift databases. The database backup script is run on the
backup machine and is called from /etc/rc.d/rc5.d/dspbackup. A
copy of the script is shown below.
# start up DISPATCH data base backup procedure

#
if [ -h /dsp/sh/`hostname`.backup ]; then
su mms -c /dsp/sh/`hostname`.backup &
(echo -n ' dspbackup') >/dev/console
fi
In order for the above script to work, make sure there is a link from the
current machine (reporter, for example) to the dspbackup file in the
/dsp/sh directory.
ln -s dspbackup reporter.backup
The backup database is written to the opns directory on the backup

machine:
-rw-rw---- 1 mms staff 638976 Mar 14 12:56 pitdat.00

-rw-rw---- 1 mms staff 122880 Mar 14 12:56 shiftdat.00
In this case, 12 hours of the pit database and 12 hours of the shift database
are saved. DISPATCH automatically overwrites the pitdat.hour and
shiftdat.hour data bases every 10 minutes until the next hour arrives.
Notes
If you ever have to run on the backup machine, the most out of date either of
your databases will be is 10 minutes.
Switching to the Backup Machine from the Main

CPU (for older systems running packet switcher daemon)
If the initial system is configured properly, a redundant DISPATCH system
should be in the control tower. This would include computers, radios, multi-
protocol routers (MPRs - blue boxes, packet modems, or hubs), cables, and
antenna.
Along with the extra hardware, two a/b serial switches are needed to switch
the MPR to the backup system and to the backup computer.
tower backup
ttya ttyb ttya ttyb

Antenna
B
B MPR RADIO
a/b C C a/b
A MPR RADIO
A
When switching to the backup machine, it does not matter what MPR you
are currently using since all the steps are the same. If you do not have a/b
switches installed, then the dispatcher must physically move the packet
modem cable from one machine to the next.
Every DISPATCH hardware configuration is different. Some clients may run

DISPATCH on a dumb terminal, while others use Sun console windows.
When using dumb terminals, there are two ways to accomplish this.
Through the use of a multiplexer (VPX 127 or VPX 128) or a terminal server.
For simplicity we will use the name tower for the real-time machine, and
backup for the backup machine. I will also use the acronym MPR for the
DISPATCH hardware connected to the Sun computer.
1. DISPATCH is running on a dumb terminal.
a) On a multiplexer, switch the a/b switch to connect from the main

machine to the backup machine.
On the terminal server, if there is a menu to connect to the

backup machine use it. If not, type: rlogin backup
b) Connect the MPR to the backup machine by switching the a/b

switch or physically moving the cable.
Note: It is very important that the MPR cable be connected to the correct serial Notes
port on the backup machine (usually the same port).
c) Log into the dumb terminal as dispatch. The following screen

appears:
d) Use the arrow keys and move the cursor down to the option
Set Primary database machine:________
and press PF3 or ? to display the valid machine names to run

DISPATCH. In our example you can either type 1 or backup to
run DISPATCH on the backup machine.
This changes all the DISPATCH machines to look at backup for

real-time information.
After you enter 1, DISPATCH will prompt you to verify that you
want to change the real-time machine name.
To start the DISPATCH process, move the cursor up to either
Restart DISPATCH
or
Notes
Coldstart DISPATCH
The difference between these two options is that Coldstart locks all the
trucks to excavators and disables all cycle buttons except Load. By disabling
all of the other cycle buttons (Arrive and Assign), the truck driver must press
Load when the first bucket of material hits the bed. This allows you to place
the trucks back in their haulage cycles very easily.
2. DISPATCH is running on the Sun Console.
a) The first thing you will have to do is log onto the backup
machine's console.
b) Connect the MPR to the backup machine, either by switching the

a/b switch or physically move the cable.
Note: It is important that the MPR cable be connected to the correct serial port
on the backup machine (usually the same port).
c) Select the DISPATCH Icon on the MMS Control Panel
d) Move the cursor down to the option
Set primary database machine: Database
If the right mouse is clicked on the Database box, all valid

DISPATCH machines will be displayed. Select backup for our
example.
Once selected, another widow pops up asking you to verify the change on Notes
this machine, and all the other DISPATCH machines.
Select YES in all these cases.
e) To start the DISPATCH process, move the mouse up to either
Restart DISPATCH
or
Coldstart DISPATCH
Switching to the Main CPU from the Backup

Machine
Basically the only difference is going back to the real-time machine is that
you want to copy the current pitdat and shift data base files from the backup
machine to the real-time machine.
1. DISPATCH is running on a dumb terminal.
a) Stop DISPATCH by pressing PF4 or Ctrl-z. To copy the current

shift and pit data bases to tower, move the cursor down to the
option
Copy DISPATCH data to another computer: __________
Notes
Either press PF3 or ? for help on the machine names. In our

example we will either enter 0 or tower to copy the data to the
tower machine. Note that the computer will prompt you with
Really copy data files to tower? (Y/N)
Answer YES.
b) Use the arrow keys and move the cursor down to the option
Set Primary database machine:________
and press PF3 or ? to display the valid machine names to run

DISPATCH. In our example you can either type 0 or tower to
run DISPATCH on tower.
This changes all the DISPATCH machines to look at tower for

real-time information.
At the bottom of the screen the computer will ask you to verify
that you want to change to tower.
Answer YES.
c) Log out of the backup machine. Notes
d) On a multiplexer, switch the a/b switch to connect from the

backup machine to the tower machine.
On the terminal server, if there is a menu to connect to the tower

machine use it. If not, type: rlogin tower
e) Connect the MPR to the tower machine, either by switching the

Note: It is very important that the MPR cable be connected to the correct serial
f) Log into the dumb terminal as dispatch.
g) To start the DISPATCH process, move the cursor up to either
Restart DISPATCH
or
Coldstart DISPATCH
2. DISPATCH is running on the Sun Console.
a) Stop DISPATCH by clicking Exit or press Ctrl-z on the

transaction screen. To copy the current shift and pit data bases to
tower, move the cursor down to the option
Copy DISPATCH data to another computer: COPY
Notes
Use the right mouse button to pull down a list of all possible
machines. In our example select tower to copy the data to the
tower machine. Note that the computer will prompt you with
Answer YES.
b) Use the right mouse button on the option
Set Primary database machine: Database
Click the right mouse button on Database to display all valid

DISPATCH machines. In our example select tower. This changes
all the DISPATCH machines to look at tower for real-time
information.
Once selected, the computer will ask you to verify that you want Notes
to copy the files to tower.
Answer YES.
c) Log out of the backup machine.
d) On a multiplexer, switch the a/b switch to connect from the

backup machine to the tower machine. On the terminal server, if
there is a menu to connect to the tower machine use it. If not,
type: rlogin tower
e) Connect the MPR to the tower machine, either by switching the

Note: It is very important that the MPR cable be connected to the correct serial
f) Log into the tower machine as dispatch.
g) Select DISPATCH on the MMS control panel.
h) To start the DISPATCH process, move the cursor up to either
Restart DISPATCH
or
Coldstart DISPATCH
Switching to the Backup Machine from the Main

CPU (OMS sites)
The procedure for switching to the backup machine at an OMS site is much
the same as a packet switcher daemon site with 2 major exceptions.
1. There are no mux’s, radios etc. to switch when going to the backup
machine. Because we set all of our computer hardware to the same
OMSDOMAIN, all we do is logout of the main machine (if possible) and log
into the backup machine as user "dispatch" and restart the dispatch process.
Notes
The only difference you’ll see on the dispatch restart screen at an OMS site
will be the entry "Packet switcher machine:" will be an IP address as
opposed to a host name. In the figure above, "tower" would be replaced with
an IP address and youll never have to change that address.
Creating and Adding Another DISPATCH User
There are a couple of ways to add users to your system: command line entry
and through a gui.
From the command line, as the super user:
#useradd -d /home/dsmith -g 110 -m dsmith
the -d option says to create the directory as stated.
the -g option says to use "group 110", Modular’s group id.
the -m option tells the system to actually create the home direcotry.
The next step would be to copy the system files from another "working"
users’ directory into your new users’ home directory:
tower# cd dsmith
tower# cp ../keypad/.* .
Now get the .ssh directory
tower# tar cf - -C /home/keypad .ssh | tar xvfp -
and finally, change ownership of all files in the new us-

ers’ directory to the new user.
tower# cd /home Notes
tower# chown -R dsmith:modular dsmith
After changing ownership, create a password for the user, dsmith.
tower# passwd dsmith
For users of Suse_sparc_linux, you can use the yast2 GUI to add users:
1. $ xhost + ( to allow root to have a display to run yast2)
2. $su
3. #yast2 ( this brings up the yast2 utility
4. on the lefthand side, select "Security and Users"
5. in the main window, select "Create a new user"
6. fill in the information in the first window (name, id and password)
7. select details and change the "Default group" to "modular".
8. press ok.
You’ll still need to copy the "." files and issue the tar command list above to
make it a working Modular account.
For users of RedHat linux, you can use the Redhat user configuration
utility:
1. $su
2. # /usr/share/redhat-config-users/redhat-config-users
Fill in the information, leaving the "Login Shell" set to /bin/bash. You’ll see
the new user added to the list of users. Highlight that user by left clicking
on it and then go up and select the "Properties" icon. This will open a new
window. Select the "Groups" tab, scroll down and left click in the box next to
the "modular" group.
You’ll still need to copy the "." files and issue the tar command list above to
make it a working Modular account
Backing-up System Files

If your comany IT department does not backup your dispatch system for
you, you should do backups regularly and when necessary.
To perform a system backup, you need a storage device, typically a tape

drive, connected to the machine that has the system files that need to be
Notes
backed up. Put a tape in the tape drive and then log in as super-user to the
machine that has the tape device connected to it.
Before you run a backup, you may want to create a log file of the backup
process, which is highly desirable. To do this, edit the /.bashrc file and
add the following alias:
alias backup="/backup >& /home/mms/backup_log/`date

+'%y%m%d'`.backup.log"
NOTE: make sure that the directory "backup_log" exists.
as mms user or root #mkdir /home/mms/backup_log
Now, whenever the backup is run, it will create a log in the mms/
backup_log directory.
At the prompt, enter backup (A typical backup script is included in this

chapter.)
If you want to run the backup process automatically, create another file
called backup_auto with permissions of 744 with the following line:
/backup >& /home/mms/backup_log/`date +'%y%m%d'` .backup.log
Now, set your cronjob to run the backup automatically:
tower:mms$ crontab -e
15 2 * * * /backup_auto > /home/mms/backup_log/backup.log 1>&2
To Retrieve DISPATCH files from Tape Backup

Whenever necessary to retrieve files from a tape backup, follow these steps:
1. On the machine that has the tape device connected to it, log in as su
1. su
1. # mt -f /dev/nst0 rewind ( this brings us to the start of the tape)
By default, we backup / then /usr and finally /local. All mms code resides in /
local/mms. If you wanted to restore files under the mms directory structure,
you would do the following after the rewind process from above.
1. #mt -f /dev/nst0 fsf 2
Now we are at the proper place to retieve our files:
1. /sbin/restore -ivf /dev/nst0
will put you at the restore prompt. You can use the "ls" and "cd" commands
to move to the area where the files reside that you need to restore. For
example, if you’re trying to restore some files from the opns directory, cd to
mms/dsp/cli/xyz/opns. If you do an "ls" now, you should see all the files in the Notes
opns directory. To get files or a directory you can do the following:
1. cd /mms/dsp/cli/xyz
2. add opns
3. extract opns
That will add and then extract the opns directory AND ALL OF IT’S
CONTENTS. If you do this in your home directory, what you’ll get is the
following directory path to the extracted files
/home/dsmith/local/mms/dsp/cli/opns/
The Diagnostic Laptop

There is a manual available on how to use the diagnostic laptop. However,
as the system administrator, you may be expected to install the software
and modify a couple of files.
The new diagnostic laptops run a windows application as opposed to the old
linux laptops. The installation and setup of this new application is relatively
easy. Depending on whether you are a OMS site or an older psw site, you’ll
recieve a client installation disk appropriate for your site. You’ll also recieve
a set of install instructions.
There are 2 files worth mentioning for OMS sites: cppoption and
network.hosts.
The cppoptions file contains the wepkey needed to authenticate to your

wireless network. This file takes the form of:
echo PRISMKEY=xx:xx:xx:xx (you will be supplied a wepkey by Modular)
Following is an example of the network.hosts file. This file MUST be

configured with your network settings.
#
# DISPATCH Utility System Module
# Copyright (c) Modular Mining Systems, 1982-2002
# All Rights Reserved
# $RCSfile: network.hosts,v $
# $Revision: 1.1 $
# $Author: olson $
# $Date: 2002/05/17 18:58:25 $
# $State: Exp $
# Purpose: Default OMS networks and subnets.
#
#
# Default route for upstream network
#
167.96.31.1/24 defaultroute network
#
# Virtual gateway IP for backbone routers. Only define this if
you
# have multiple backbone routers serving a shared wireless sub-

Notes
net.
#
none gateway network
#
# OMS multicast domain for backbone routers. If you don't
define it here,
# you must manually define ÒMS domain' after you load any
Ethernet gateway
# router.
#
167.96.31.4/24 domain network
#
# Default UHF radio network.
#
167.96.31.0/24 radio network
#
# Default 2.4ghz spread spectrum network.
#
167.96.31.0/24 prism network
#
# Wireless broadcast address
#
167.96.31.255 broadcast network
#
# Default network for DISPATCH system LAN
#
167.96.31.0/24 lan network
Your Modular representative can assist you in configuring this file if

necessary.
The Masterlink Tracking System (MTS)

As the Dispatch System Administrator, one of your duties will be to
maintain the Masterlink network. Modular has provided you a very useful
tool to accomplish this.
The MTS comprises an sql database collecting information from all

Masterlink hardware in the field and a java application to view this data.
Once a minute, the Masterlink hardware reports in gps position and access
point association. This allows the user to see real time equipment position
and status of the Masterlink hardware on the equipment.
Probably most important in this application is the ability to see your RF

(radio frequency) Coverage. The user can also see areas of "no coverage".
This is most important in assisting the Dispatch System Administrator in
deciding where to move a mobile access point to provide the necessary radio
coverage. The full manual can be requested from Modular. However, an RF
section has been added to the manual as an appendix for easy reference. The
MTS software is constantly going through improvements, so your software
may be newer than the appendix.
A
Computer Basics
Notes
Bits and Bytes
Computers process bits. Data is stored and used as bits. A bit is a 0 or 1. When
we talk about the size or capacity of things we use the term byte. A byte is 8-
bits. The first microprocessors were 8-bit processors. 16-bit processors were
then built and the concept of word was created. A word is 16-bits or 2 bytes
long. 32-bit and 64-bit processors use double words and quadwords. The fact
that 64-bit processors use 64-bits of data at a time is a part of the reason that
they are so much faster and more capable than earlier processors.
Applications that use 32- or 64-bit data sets are specifically designed to take
full advantage of the greater capacity processors. The early SPARC
processors were 32-bit processors and the later SPARCII and UltraSparc are
64-bit processors.
Other dimensions that we use are kilobytes (kB), megabytes (MB), gigabyte
(GB) and terabyte (TB). A kilobyte is 1024 bytes. A megabyte is
approximately a million bytes, a gigabyte is a billion bytes and a terabyte is
a trillion bytes.
Pages
Data moves into and out of Random Access Memory (RAM) in 4 kB chunks
called pages. At any given moment, an application uses only a small fraction
of the pages it has been assigned. If a computer system starts running out of
RAM to run applications and process data, the operating system copies to the
hard disk all the pages that haven’t been used lately and removes them from
RAM. If an application later needs one of the pages on the hard drive, it
retrieves the page and moves it back into RAM. The application is running in
a virtual mode and using virtual memory (as opposed to physical or real
memory) in this situation because all of the pages are not actually in RAM.
Although the application will run, it will often be slow and non-responsive.
This phenomenon happens most often when running a large program, a large
number of programs or working with a large file. This is an indication that
more RAM is needed.
Memory
There are different types of memory in every computer. We will cover ROM,
RAM and hard drives. ROM is read only memory. ROM is where the basic
boot instructions are stored. RAM is where data is stored just before or just
after it is processed by the CPU. Early microcomputers had 50 kB of RAM.
Early PCs had 1 MB of RAM. PCs today typically have 8 to 32 MB of RAM.
A-1
A-2 System Administration Class
Notes
Workstations and servers have 32 MB to several thousand MB of RAM. This
large amount of RAM is necessary because of the programs and files that run
on workstations and servers.
Hard drives or fixed drives provide the primary data storage for applications
and data that must be used frequently. Hard drive capacity is measured in
MB and GB. Internal hard drives are connected to the system board or
motherboard by a connection to a controller or controller card.
Hard drives are made up of drive platters which are wafers coated with a thin
recording layer of microscopic oxide particles or a mixture of metals.
Recording heads pass over the platter and record data disk by magnetically
changing the electric field of the particles. Hard drive capacity is determined
by the number of platters, the manufacturing techniques used to produce the
platters and the ability of the heads to fly close to the surface and read and
write to very precise locations on the platter.
Figure A.1 Hard Drive Regions

Figure A.1 depicts the hard drive platters. When a new drive is installed into
a computer the parameters for the drive are entered into system memory. The
number of cylinders is the total number of concentric rings on all of the
recordable sides. The number of sectors per cylinder along with the number
of (drive) heads is also recorded. This allows the computer to recognize each
drive and determine how much data can be written to the drive. The
individual hard drive is often called the physical drive. Logical or virtual
drives will be discussed later.
In order for a drive to be used by the computer it must be formatted and a file
system created. When a hard drive is formatted a boot sector is created on the
very first sector of the drive which contains information identifying certain
Computer Basics January 2003

System Administration Class A-3
physical and logical characteristics of the disk, and a block of data that Notes
contains other data about the drive.
Drive Format
Caution: Formatting a hard drive destroys all of the data on the drive!
Modular Mining System customers typically request and receive drives that
are pre-formatted. You learn how to use the operating system to format a
drive later in the System Administration class.
Drive Partitions
In the following discussion the term disk will be used to indicate a hard drive
as opposed to a floppy diskette or CD-ROM. The term drive can be somewhat
confusing since drive refers to both a physical hard drive and to a logical or
virtual drive. There may be several logical drives on one physical drive.
After a successful format, a label is written to the first and last cylinders of
the formatted disk. Then it is necessary to partition the disk prior to use.
Installation of the Sun operating includes partitioning of the disk. However,

if you are adding a disk or repartitioning an existing disk it will be necessary
to partition the disk prior to installing any software. Partitioning also causes
all data on the disk to be lost. Backups allow you to restore the system
software to a newly formatted or partitioned disk.
The Sun operating systems can use eight slices or partition on any given disk.
The DISPATCH system only requires three types partitions. A part of the
operating system uses one partition, swapping of files and data occurs on a
second partition, and the additional partitions are for storage.
Managing swap file space is a major responsibility of the System

Administrator. During initial system software installation, the automatic
process installs minimum default partition sizes. The swap partition size
defaults to twice the amount of RAM installed. Thus on a 32 MB workstation,
64 MB of swap space is set aside.
January 2003 Computer Basics

A-4 System Administration Class
Notes
Figure A.2 DISPATCH Hard Drive Partitions

Figure A.2 shows examples of partitions in a DISPATCH installation. The
root drive shows a minimum size for Solaris. The swap drive size (64 MB) is
the minimum for a workstation with 32 MB of RAM. The swap drive is virtual
memory rather than physical memory (RAM). The System Administrator
adjusts this partition size to accommodate the requirements of each
individual system and the programs running on it.
Computer Basics January 2003

B
The dbclean Utility
Notes
The DBCLEAN Utility
DBCLEAN allows you to clean or restore databases corrupted by system
crashes. However, DBCLEAN is more often used to update old databases
which are not compatible with new releases of DISPATCH software.
DBCLEAN is used to clean the PIT, SHIFT, TIRE, and SUMMARY
Databases.
DBCLEAN is a privileged utility not included on the KEYPAD. Users access

DBCLEAN by typing DBCLEAN.
A sample DBCLEAN Form appears below:
DISPATCH DBCLEAN Utility

Input Database Name:
Size: - Bytes
Allocation: - Bytes
Window Size: NONE Blocks
DDR recovery UNKNOWN
INIT NO
Output Database Name:
The DBCLEAN Form contains prompts for Input Database and Output
Database, and software information occasionally used by Modular. To
DBCLEAN a database, first enter the name of the database to be cleaned in
the Input Database field. The database name should not include the .DDR or
.DDB extension. Next, specify the name of the Output (Cleaned) Database.
At this point, DBCLEAN commences and outputs diagnostic information to
the screen.
The OPERATIONS Databases cannot be DBCLEANed directly while the

system is running. Instead, copy the desired OPERATIONS Database, then
DBCLEAN the copy. After running DBCLEAN, copy the cleaned database
back over to the appropriate OPERATIONS Database.
Users may bypass the DBCLEAN Form by specifying all required

information with the following command:
dbclean from=inputdatabasename to=outputdatabasename
The following sample DBCLEAN Form illustrates how to clean the Input
Database, named PIT, and create an Output Database named CLEANPIT.
B-1
B-2 System Administration Class
Notes DISPATCH DBCLEAN Utility

Input Database Name: DSP_OPNS/pitdat
Output Database Name: ~/pitclean
Clean it? NO
Size: - Bytes
Allocation: - Bytes
Marking all records:
[Creating /home/userid/pitdat.ddb]
Converting truck: Total Records: 000039 -- Total Bytes: 016848
Converting excav: Total Records: 000012 -- Total Bytes: 005184
Converting auxeqmt: Total Records: 000073 -- Total Bytes: 022484
Converting pitloc: Total Records: 000174 -- Total Bytes: 029232
Converting worker: Total Records: 000235 -- Total Bytes: 040420
Converting event: Total Records: 000002 -- Total Bytes: 000176
Converting simul: Total Records: 000001 -- Total Bytes: 000088
Converting travel: Total Records: 000296 -- Total Bytes: 035520
Converting path: Total Records: 000148 -- Total Bytes: 079920
Converting grade: Total Records: 000131 -- Total Bytes: 016244
Converting reasondown: Total Records: 000107 -- Total Bytes: 005992
Converting reasondelay: Total Records: 000081 -- Total Bytes: 004536
Converting action: Total Records: 000000 -- Total Bytes: 000000
Converting error: Total Records: 000010 -- Total Bytes: 000880
Converting pitbreak: Total Records: 000001 -- Total Bytes: 000044
Converting reasonspare: Total Records: 000050 -- Total Bytes: 002800
Converting delroute: Total Records: 000003 -- Total Bytes: 000156
Converting blend: Total Records: 000002 -- Total Bytes: 000920
Converting bar: Total Records: 000077 -- Total Bytes: 006776
Converting bean: Total Records: 000006 -- Total Bytes: 007080
Relocating truck:
Relocating excav:
The dbclean Utility January 2003

System Administration Class B-3
Relocating auxeqmt: Notes

Relocating pitloc:
Relocating worker:
Relocating event:
Relocating simul:
Relocating travel:
Relocating path:
Relocating grade:
Relocating reasondown:
Relocating reasondelay:
Relocating action:
Relocating error:
Relocating pitbreak:
Relocating reasonspare:
Relocating delroute:
Relocating blend:
Relocating bar:
Relocating bean:
Users perform the same DBCLEAN by entering the following command:
dbclean from=~/pit to=~/cleanpit
Note: DISPATCH must be stopped and all mms processes logged out of before
using dbclean on the pit or shift databases.
Whenever records are added to the shift data base, all shift files must be
dbclean'ed. The example below shows an easy method to clean large
numbers of shift files.
(It is always a good practice to test out the script before proceeding with
doing the dbclean. In the examples below, November, 1996 has been
chosen. The date range could easily have been selected for all of 1996
(sh96*ddb) or a date range in a particular month (sh96110[1-9]*.ddb)).
If running csh:
tower<45> cd opns
tower<46> foreach i (sh9611*.ddb)
? echo $i
? end
This prints out all the shift files for November, 1996. If all went well, do the
dbclean:
tower<47> foreach i (sh9611*.ddb)

? echo $i
? mms dbclean from=$i
? end
January 2003 The dbclean Utility

Notes
If running bash:
tower:mms$ cd opns
tower:opns$ for i in sh9611*ddb
> do
> echo $i
> done
Again, if this produces the shift files for November, 1996, then enter:
tower:opns$ for i in sh9611*ddb

> do
> echo $i
> mms dbclean from=$i
> done
The SUMMARIZE Utility

SUMMARIZE allows Users to update the SUMMARY Database after
inputting new information into a SHIFT Database that has already been
summarized.
SUMMARIZE collects the mine information saved in SHIFT Database files

and stores it in a cumulative form in the SUMMARY Database. SUMDAT is
the logical name for the current SUMMARY Database. Users can
SUMMARIZE real-time shift files or, likewise, compile multiple shifts for
simulator generated shift files. DISPATCH accesses the SUMMARY
Database to generate PITSTATS Multiple Shift Reports.
DISPATCH runs SUMMARIZE automatically at the end of each shift to add

the data from the current shift to summary data from previous shifts.
However, mines may wish to update the grades using GRADE, change some
Status records with STATCHNG or add loads with LOADCHNG. After
performing these changes, Users must RESUMMARIZE the affected shift(s)
to revise the information in the SUMMARY Database.
SUMMARIZE is a privileged utility requiring access to command language.

Users may access SUMMARIZE with the Form interface or by entering the
following command:
mms summarize sh = DSP_OPNS/firstshift la = DSP_OPNS/lastshift
Summarize Switches
summary=file-spec The summary switch specifies the name of the

SUMMARY Database used by SUMMARIZE.
SUMDAT is the default.
shift=file-spec The shift switch specifies the name of the shift

file to be appended into the SUMMARY

System Administration Class B-5
Database. If used with the lastshift switch, the Notes

name must be in the SHYYMMDDS format.
SHIFTDAT is the default.
lastshift=file-spec The lastshift switch specifies the last shift file

name in a range of SHIFT Database files to be
summarized. It must have the SHYYMMDDS
format.
list The list switch displays a list of the shift files

already summarized in the summary file. All
other switches except summary are ignored.
close The close switch closes out the selected SHIFT

Databases which have not been properly closed
by DISPATCH.
delete The delete switch deletes the given SHIFT

Databases from the current SUMMARY
Database.
tire The tire switch includes the TIRE Databases

into the SUMMARY Database.
factors The factors switch updates the shift load

factors after summarizing.
updateThe update switch causes DISPATCH to summarize SUMMARY

Databases that have not already been summarized.
If SUMMARIZE is entered without any switches, the following

SUMMARIZE Form appears on the screen:
DISPATCH Summarize Utility

Shift File Date: __________________
or Range of Dates: ____________ thru _____________
Delete Shifts from Database? NO
Close Shifts not Closed by DISPATCH? NO
Use Load Factor from CONFIG.PRV? NO
Summarize Shift not yet Summarized? NO
Summarize the dates? NO
The following sample Form illustrates how to summarize the month of May
1986 for the operations SUMMARY Database.
January 2003 The dbclean Utility

Notes DISPATCH Summarize Utility

Shift File Date: __________________
or Range of Dates: __1-MAY-86__ thru __31-MAY-86__
Delete Shifts from Database? NO
Close Shifts not Closed by DISPATCH? NO
Use Load Factor from CONFIG.PRV? NO
Summarize Shift not yet Summarized? NO
Summarize the dates? NO
Optionally, to SUMMARIZE the same shifts, the user enters the following
command:
mms summarize sh=sh860501n la=sh860631a

C
List of Generic config Variables
@ DSP_FORM/fmt.prv
@ DSP_COM/speed.prv
$ CONFIG ACCELSECS 18
! INT(0,1000) "Number of seconds a truck takes to "\
"accelerate to speed"
$ CONFIG ALTTIEDOWN ""

! STRING("","") "Alternate Shiftchange Area"
$ CONFIG ARRIVECODE 999

! INT(0,1000) "Unexpected location ARRIVE code"
$ CONFIG ASNBYPRIOR YES

! BOOL(YES) "If YES then trucks assignments are made by the "\
"shovel priorities assigned in the SHVPRIOR utility. If NO then "\
"shovel priorities are ignored when making truck assignments, "\
"priorities will then only be used to determine which "\
"shovels become UNUSED if a LP constraint is violated. "
$ CONFIG ASNIDLEBIAS 0.5

! FLOAT(0.0,1.0) "The factor associated with how much DISPATCH "\
"weights Idle time in the lost tons calculation "\
"in the assignment of trucks to shovels. Default"\
"is 1.0"
$ CONFIG AUTOID YES

! BOOL(YES) "Automatically accept the operator payroll number. "\
"If not set then every time a operator logs in the dispatcher "\
"must OK the employee id."
$ CONFIG AUTOLOGIN NO
! BOOL(YES) "If YES then a Ready or Assign is not needed "\
"after the equipment operator logs in."
$ CONFIG BARPCT 50
! INT(0,100) "After a truck is barred from more than"\
"BARPCT of available shovels, DISPATCH"\
"prefers this truck in making shovel"\
"assignments to which the truck is not"\
"barred. "\
$ CONFIG BLENDING NO
! BOOL(YES) ""
$ CONFIG CALCSHIFTTIME 120

! INT(0,10000) "The time between recalculating the stored "\
"shift data if no new shift data base is opened. Used when "\
C-1
C-2 System Administration Class
"the PITSTATS utility is executed. Data for the current "\

"shift is partially summarized and stored. If the user "\
"remains in PITSTATS long enough significant changes to the "\
"pit configuration will take place that will not be "\
"reflected in the reports. CALCSHIFTTIME ensures that current "\
"information is always reported in the PITSTATS reports "\
"without forcing the user to exit the utility."
CONFIG CALLBIAS 1.0

! FLOAT(0.0,1.0) "reassignment dumping factor, factor to make"\
"alternate dumping assignments less attractive"\
"by adding LPTRUCKSIZE TRUCK * CALLBIAS to the"\
"other path. Default is 0.5"
$ CONFIG CRSHDUMPTIME 120

! INT(0,10000) "The normal dumping time in seconds for a "\
"truck to dump it's load at a crusher."
$ CONFIG CRUSHAVG 5
! INT(0,10000) "Moving average crusher rate count."
$ CONFIG CRUSHCALLTIME 0
! INT(0,1000000) "The seconds into the shift when DISPATCH "\
"meets the Crusher Call. DISPATCH compensates for over and "\
"under hourly production at the crusher to meet the Crusher "\
"Call at the CRUSHCALLTIME. Setting the CRUSHCALLTIME to 0 "\
"makes a noncompensating or constant Crusher Call for the shift."
$ CONFIG CRUSHCODE 901

! INT(0,10000) "DISPATCH code used to spare an equipment when "\
"some condition at the crusher prevents the equipment from "\
"operating."
!$ CONFIG *AVG 4
! INT(0,100) "Replace * with any dump name ..and DISPATCH "\
"will calculate the dump avg at that dump"
$ CONFIG DIGAVG 4
! INT(0,100) "The number of most recent loads used "\
"to calculate a shovel's moving average digging rate. "
$ CONFIG DONTSPAREEXCAV YES

! BOOL(YES) "If YES then shovels will not be spared "\
"even if the LP requirments dictate that they should be spared."
$ CONFIG DOWNREASSIGN NO
! BOOL(YES) "YES means reassign even if dispatcher said "\
" NO when answering EXDOWNOPTION."
$ CONFIG DPQUEUE 60
! INT(-1000,1000) "Assignment queue length at each shovel. "
$ CONFIG DUMPAVG 4
! INT(1,100) "The number of most recent dumping time "\
"intervals used to calculate the moving average dump time. "
List of Generic config Variables January 2003

System Administration Class C-3
$ CONFIG DUMPCODE 902

! INT(0,10000) "DISPATCH code used to spare the "\
"equipment due to some condition at the dump which prevents "\
"the equipment from operating."
$ CONFIG EMPTYSIZE 150.0

! FLOAT(0,10000.0) "Average truck size used in the TMPH calculation."
$ CONFIG EQUALFEED YES

! BOOL(YES) "If YES then low priority shovels are "\
"equally assigned trucks without SPARING or UNUSING any of "\
"the shovels due to a dump point restriction. If NO DISPATCH "\
"will SPARE or UNUSE low priority shovels when dictated by "\
"the LP Solution."
$ CONFIG EXCAVCODE 903

! INT(0,10000) "DISPATCH code used to spare a truck when "\
"some condition at the shovel prevents the operation of the truck."
$ CONFIG FACTORAVG 4
! INT(0,10000) "Replaces the weather factor. Updating interval"\
"for truck speed factor."
$ CONFIG FUELCODE 110

! INT(0,999) "DISPATCH code used to delay a truck for fueling"
$ CONFIG FUELPCT 30
! INT(-1,100000) "FUELPCT config represents the fuel"\
"remaining in the tank for fuel assignments to occur; any"\
"truck with less than FUELPCT left in its tank gets a fuel"\
"shop assignment if the queue is OK. A value of -1 disables"\
"the fueling logic."\
$ CONFIG FUELPCT2 20
INT(-1,100000) "FUELPCT2 specifies an amount remaining"\
"in the fuel tank below which a truck is assigned to fuel no"\
"matter how many trucks are currently fueling. This avoids"\
"trucks very low on fuel running out just because the fuel bay"\
"is full."\
$ CONFIG FUELCLOSED 32.0

! FLOAT(0.0,10000.0) "Defines the fuel consumption rate for"\
"trucks when the lubebay is closed"
$ CONFIG FUELTRAINING 32.0

! FLOAT(0.0,10000.0) "Average truck fuel consumption when fuel "\
"consumption variables are not defined."
$ CONFIG GRADEPFX ""

! STRING("","") "Prefix prepended when entering a grade string"
$ CONFIG GRADESTR "GRADE"

! STRING("","") "The client word or phrase which conveys the "\
"meaning of a portion of a blast. GRADESTR might have a value "\
"of 'GRADE', 'SEAM', 'ZONE', or 'STATION'. "
January 2003 List of Generic config Variables

$ CONFIG GRADETMP "9999aaa999-9999"

! STRING("","") "The template used to enter the grade id."
!$ CONFIG *_MAX 9999

! FLOAT(0.0,9999.0) "Increase maximum input field of any DISPATCH"\
"symbol"
!$ CONFIG HOLIDAY ""

! STRING("","") "Used to identify which dates of the "\
"calendar year or days of the week or shifts are non-operating "\
"holidays. Acceptable form is : DD-MMM or day SUN, MON... "
$ CONFIG HOLIDAYWAKEUP 27000

! INT(0,1000000) "Number of seconds into the last shift of "\
"the holiday period that DISPATCH wakes up from it's sleep state."
$ CONFIG LASTREASON 999

! INT(0,10000) "Last reason to show to the dispatcher when "\
"he asks for help to get a list of reason codes. If 999 then "\
"all reasons are shown."
$ CONFIG LATEARRIVE 120

! INT(0,1000000) "Number of seconds after an expected arrival "\
"that a late message is posted on the transaction screen. "
$ CONFIG LATEASSIGN 60
! INT(0,1000000) "Number of seconds after an expected assign "\
"that a late assign message is posted on the transaction screen."
$ CONFIG LATEBREAK 300

! INT(0,1000000) "Number of seconds after an expected ready "\
"after break that a late for ready from break message is "\
"posted on the transaction screen."
$ CONFIG LATEDELAY 300

! INT(0,1000000) "Number of seconds after an expected ready "\
"from delay that a late for ready from delay message is "\
"posted on the transaction screen."
$ CONFIG LATEEXSTART 900

! INT(0,1000000) "Number of seconds after an expected "\
"ready-from-start-of-shift for a shovel that a "\
"late-for-ready-from-shift-change message is posted on the "\
"transaction screen."
$ CONFIG LATEFULL 60
! INT(0,1000000) "Number of seconds after an expected truck "\
"full from a shovel that a late for full message is posted on "\
"the transaction screen."
$ CONFIG LATELOAD 90
"truck load at an shovel that a late for load"\
"message is posted on the transaction screen."

$ CONFIG LATENOTICE 60
! INT(0,1000000) "Number of seconds after late notice that the "\
"late notice is again posted on the transaction screen."
$ CONFIG LATETKSTART 900

"truck start from the begining of the shift that a late "\
"truck start message is posted on the transaction screen."
LOADFACTOR_x
Data Type: Float
Default: 1.0 for all load types
Description: Defines the loading factors for each material type.
The value of 'x' ranges from 1 to N, where N is the number of the last
material type.
$ CONFIG LOADFACTOR_0 1.0

! FLOAT(0.0,1000.0) "Loading factor for material type"
DSPARRIVE.c allows for configs in this form: LOC_XXX where LOC is any valid
location id. XXX is DOWN SPARE or DELAY. The value for the config is the
dispcode for the desired action.
$ CONFIG LOCKEXCEPT NO
! BOOL(YES) "If YES an exception is generated if DISPATCH "\
"needs to overide a Lock to a dump in "\
"order to assign a truck to an alternate location. "\
"The DISPATCHER must answer the exception before the truck gets "\
"it's next dump assignment. If NO then DISPATCH will "\
"automatically overide the Lock and post a message to the "\
"Transaction Screen. "
$ CONFIG LOGOFFCODE ""

! INT(-2,10000) "Pay number code to logoff equipment operator. "\
"A value of -2 disables PAY_NUMBER logoff. Client specific."
$ CONFIG LOOKAHEAD 600

! INT(0,1000000) "The number of seconds in the assignment "\
"look-ahead interval. DISPATCH forecasts the truck arrivals "\
"and assignment requests throughout the lookahead interval "\
"in order to make the best truck assignments at the current "\
"time using a Dynamic Programming algorithm. "\
"When LOOKAHEAD is set to 0 the Dynamic Programming Lookahead "\
"algorithm is disabled and all truck assignments are then based "\
"on the LP solution. "
$ CONFIG LPMATCHTRUCKS -1
! INT(0,1000000) "LP will match the actual trucks to the "\
"required trucks if the absolute difference is greater than "\
"the LPMATCHTRUCKS value. A value of -1 disables this option."
$ CONFIG LPSCALE TIME
! STRING("","") "When defined as TIME the displayed routes "\
"are scaled by truck travel time rather than the default of shovel "\
"tonnage ratemultiplied by the truck travel time."

$ CONFIG LPSHOWAUX NO
! BOOL(TRUE) "If YES then auxiliary equipment are "\
"displayed on the LPROUTE screen. "
$ CONFIG LPSHOWLATE 1
! INT(0,1) "Should be a yes or no. "\
"If greater than 0 the trucks which have not arrived "\
"where they are expected within the specified number of seconds "\
"are displayed on the LPROUTE screen. If 0 this feature is "\
"turned off. "
$ CONFIG LPTIME 1800

! INT(0,1000000) "Time interval in seconds when the LP "\
"solution is updated if no production events force an update. "
$ CONFIG LPTRUCKSIZE 150.0

! FLOAT(0.0,1000000.0 ) ""
$ CONFIG L$ID/TS "TRUCK SHOP"

! STRING "Short string for location, saves typing"
!$ CONFIG MAINTCODE ""
$ CONFIG MAINTDOWN YES

! BOOL(YES) "If YES then the maintenance interval time "\
"includes the equipment's down/spare time."
$ CONFIG MAINTTIME 24
! INT(0,1000000) "Number of hours at which the maintenance "\
"interval takes place. "
$ CONFIG MAINTTIME2 48
! INT(0,1000000) "Number of hours at which the maintenance "\
"interval takes place regardless of the queue"
"at the maintnenance shop. "
$ CONFIG MASSMEAS "Ton"

! STRING("","") "Standard units of mass measure, such as Ton."
$ CONFIG MAXCRUSHTIME 300

! INT(0,1000000) "The maximum acceptable amount of time in "\
"seconds for the dump/crush cycle at a crusher. "
$ CONFIG MAXDIGRATE 5000

! INT(0,1000000) "Maximum standard MASSMEAS units / hour "\
"shovel digging rate."
$ CONFIG MAXDUMPTIME 1000

! INT(0,1000000) "Max for L$TIME and L$SIMDUMP"
$ CONFIG MAXSPEED 35.0

! FLOAT(0,1000.0) "Maximum truck travel speed in short "\
"distance units per second. "

!$ CONFIG MAXSPLIT 2
$ CONFIG MAXSPOTTIME 240

! INT(0,1000000) "Maximum spotting time allowed for a truck "\
"at a shovel."
$ CONFIG MAXWORKERID 999999

! INT(0,999999) "Largest valid worker identification code."
$ CONFIG MAXXLOC 12000

! INT(-1000000,1000000) "Max X location of L$X locmod form variable"
$ CONFIG MAXYLOC 13000

! INT(-1000000,1000000) "Max Y location of L$Y locmod form variable"
$ CONFIG MAXZLOC 3000

! INT(-1000000,1000000) "Max Z location of L$Z locmod form variable"
$ CONFIG MILEFACTOR 5280

! FLOAT(0.0,1000000.0) "Conversion factor multipled by "\
"the long distance measure that yields the short "\
"distance measure (see MILEMEAS and DISTMEAS.) If the long "\
"and short distance measures are miles and feet, respectively, "\
"MILEFACTOR must have the value of 5280.0. "
$ CONFIG MINCRUSHTIME 120

! INT(0,1000000) "The minimum acceptable amount of time in "\
"seconds for the dump/crush cycle at a crusher."
$ CONFIG MINDIGRATE 50
! INT(0,1000000) "Minimium shovel dig rate"
$ CONFIG MINDUMPTIME 0
! INT(0,1000000) "Min for L$TIME and L$SUMDUMP"
$ CONFIG MINPANELID 0
! INT(0,1000000) "Minimium value for panelid"
$ CONFIG MINSPEED 1.0

! FLOAT(0.0,10000.0) "Minimum truck travel speed in short "\
"distance units per second."
$ CONFIG MINSPOTTIME 10
! INT(0,1000000) ""
$ CONFIG MINWORKERID 0
! INT(0,999999) "Smallest valid worker identification code."
$ CONFIG MINXLOC -9000

$ CONFIG MINYLOC -10000
! INT(-1000000,1000000) "Min Y location of L$Y locmod form variable"
$ CONFIG MINZLOC 950
! INT(-1000000,1000000) "Min Z location of L$Z locmod form variable"

$ CONFIG MISROUTE NO
! BOOL(YES) "If YES then trucks are reassigned to an "\
"alternate shovel if DISPATCH detects that the truck is on "\
"an incorrect route. Misroutes are indicated by truck arrivals "\
"at unexpected signposts. If NO then trucks are not reassigned "\
"on a misroute."
$ CONFIG MIXLP YES

! BOOL(YES) "If YES then LP will mix material types."
$ CONFIG NEXTSHIFTLOGIN 27000

! INT(0,1000000) "The default is SHIFTLENGTH. "\
"The number of seconds into the current shift when new logins "\
"are considered to be for the next shift. "
$ CONFIG OTHERCODE -1
! INT(-1,10000) "Down code at "other" shops. "\
"If -1 then auto-down is disabled."
Capacity percentages may be config'd in one of two ways:
1) PCT/<bay1>/<bay2>... [=] Specific percentage for given bays ready

2) PCT/<crushname>/n [=] Specific percentage for n bays open
Otherwise, the current crusher capacity percentage is assumed to

be 100 * ReadyBays / TotalBays
$ CONFIG PCT/bay1/bay2 50
! INT(0,100) "Specific percentage for given bays ready"
$ CONFIG PCT/crusher/n 50
! INT(0,100) "Specific percentage for n bays open"
$ CONFIG REASSIGN ""

! STRING("","") "REASSIGN is used to enter configuration "\
"parameters for the crusher reassignment call point definitions "\
"for DISPATCH installations with "\
"a crusher and ore stockpile, multiple crushers, or multiple "\
"crushers and ore stockpiles. "\
"The format for the specification is "\
"call_point/original_destination/alternate_destination queue_length "\
"Loaded trucks are reassigned at the specified call point "\
"to the alternate destination if the "\
"queue at the original destination exceeds the specified queue "\
"length. For a multiple crusher arrangement the User "\
"defines an allowable queue of zero for each crusher and "\
"DISPATCH reassigns trucks to the open crusher. "\
"For a crusher and stockpile arrangement the User "\
"selects an acceptable queue length and overflow "\
"trucks are diverted to the stockpile. "
Examples:
.$ CONFIG REASSIGN "C10/CR1/D2 3" Reassign trucks at call point 10
to stockpile D2 if more than 3 trucks
are queued at crusher CR1.

.$ CONFIG REASSIGN "C1/CR1/CR2 +0" Reassign trucks at call point 1

to crusher CR2 if the more than 1
or more trucks are queued at crusher
CR1.
$ CONFIG RETORQUE 3
! INT(0,1000) "RETORQUE defines the number of trips "\
"remaining in the multiple retorque sequence when a truck "\
"is reassigned back to a shop for a retorque."
$ CONFIG RETORQUECODE 0
! INT(0,10000) "Retorque, matching code."
$ CONFIG RETORQUETRIPS 0
! INT(0,10000) "Number of retorquetrips"
$ CONFIG SCALETON 0
! INT(-100,100) "Scale factor used for those report columns "\
"which typically can become extremely large, such as total "\
"tonnage figures. The value specified is the power of 10 "\
"divided into the number to get it down to a printable size."
$ CONFIG SHIFTSTART 28800

! INT(-1000000,1000000) "The number of seconds before (a "\
"neagative number) or after (a positive number) midnight that "\
"the first shift of the day starts on."
!$ CONFIG SKIPHOLIDAY YES

! BOOL(YES) ""
$ CONFIG SPARENOOPER 904

! INT(0,10000) "Spare with no operator available code."
$ CONFIG SPAREOPER 905

! INT(0,10000) "Spare with operator available code."
$ CONFIG SPOTAVG 4
! INT(0,100) "The number of most recent spotting/swing "\
"times used to calculate an shovels spotting/swing time "\
"moving average. "
$ CONFIG STRIPQUEUE 3
! INT(0,1000) "Number of trucks required to be at a shovel"
"before DISPATCH will reccommend sending one of those trucks to"
"a nearby shovel which has readied"
$ CONFIG SWINGTIME 10
! INT(0,1000000) "Nominal shovel swing time in seconds for "\
"double backup."
$ CONFIG TIMEAVG 4
! INT(0,10000) "Moving average time count."
$ CONFIG TIRECODE ""

! STRING("","") ""

$ CONFIG TMPHEXCEPT YES

! BOOL(YES) "If YES then a message is sent to the Exception "\
"screen if a truck exceeds a specified TMPH limit."
$ CONFIG TMPHMAX 230.0

! FLOAT(0.0,1000.0) "Maximium tire "
$ CONFIG TMPHMIN 0.0

! FLOAT(0.0,1000.0) "Minimium tire "
$ CONFIG TODAY Today

! STRING("","") "Client word for DISPATCH word TODAY."
$ CONFIG TRUCKCODE 906

! INT(0,10000) "SPARE (Delay) waiting for more trucks code."
Data Type: String

Default: "" (NULL)
Description: Defines the id prefixes for each unit equipment type.
When a prefix is defined the user needs only to enter the numeric
portion of the equipment id. If no prefix is defined type then the
user must enter the complete equipment id according to the
equipment template. The value of 'x' for units from 1 to 9 must
have a leading 0 (i.e. UNITPFX_01).
$ CONFIG UNITPFX_01 "HT"

$ CONFIG UNITPFX_02 "ES"
$ CONFIG UNITPFX_03 ""
$ CONFIG UNITPFX_04 "CR"
$ CONFIG UNITPFX_06 "O"
$ CONFIG UNITPFX_09 "CP"
$ CONFIG UNITPFX_12 "DR"
$ CONFIG UNITPFX_13 "TD"
$ CONFIG UNITPFX_14 "FL"
$ CONFIG UNITPFX_15 "GR"
$ CONFIG UNITPFX_16 "RT"
$ CONFIG UNITPFX_17 "VAN"
$ CONFIG UNITPFX_18 "UT"
$ CONFIG UNITPFX_19 "WT"
$ CONFIG UNITPFX_20 "LP"
$ CONFIG UNITPFX_21 "ACR"
$ CONFIG UNITPFX_22 "BH"
$ CONFIG UNITPFX_23 "BL"
UNITTMP_xx
Data Type: String
Default: "" (NULL)
Description: Defines the id templates for each unit equipment type.

The value of 'x' for units from 1 to 9 must have a leading 0 (i.e.
UNITTMP_01). If no template is defined for an equipment type then
the user may enter any id he wishes.
$ CONFIG UNITTMP_01 "HT999"

$ CONFIG UNITTMP_02 "ES99|FL99"
$ CONFIG UNITTMP_03 "?*?"
$ CONFIG UNITTMP_04 "CR9"
$ CONFIG UNITTMP_05 "O9|9a"
$ CONFIG UNITTMP_06 "9999aaa999"
$ CONFIG UNITTMP_07 "?*?"
$ CONFIG UNITTMP_08 ""
$ CONFIG UNITTMP_09 "CP99"
$ CONFIG UNITTMP_12 "DR9{9}"
$ CONFIG UNITTMP_13 "TD999"
$ CONFIG UNITTMP_14 "FL99"
$ CONFIG UNITTMP_15 "GR999"
$ CONFIG UNITTMP_16 "RT99{9}"
$ CONFIG UNITTMP_17 "VAN999"
$ CONFIG UNITTMP_18 "UT999"
$ CONFIG UNITTMP_19 "WT9{9}"
$ CONFIG UNITTMP_20 "LP999"
$ CONFIG UNITTMP_21 "CRaa"
$ CONFIG UNITTMP_22 "BH999"
$ CONFIG UNITTMP_23 "BL999"
VTCOLOR_xx
Data Type: Integer
Default: none
Description: VTCOLOR is used to assign the terminal escape sequences that
represent the various equipment statuses for the color LPROUTE screens.
xx takes on the values from 00 to 11 where each xx represents the following
status:
xx = 00 forward video ( not really an equipment status )
01 down
02 ready
03 spare
04 delay
05 tiedown
06 loading
07 dumping
08 queueing
09 traveling
10 coldstart
11 reverse video ( not really an equipment status )
VTMONO_xx
Data Type:
Default:
Description: VTMONO is used to assign the terminal escape sequences that
represent the various equipment statuses for the monochrome LPROUTE screens.
xx takes on the same values as VTCOLOR.

$ CONFIG VTCOLOR_00.00 ^[[0;7;40;37;5m Loading

$ CONFIG VTCOLOR_00.01 ^[[0;7;40;32m Traveling
$ CONFIG VTCOLOR_00.02 ^[[0;7;44;37m Dumping
$ CONFIG VTCOLOR_00.03 ^[[0;7;40;32m Queueing
$ CONFIG VTCOLOR_00.04 ^[[0;4;7;43;34m Locked
$ CONFIG VTCOLOR_00.05 ^[[0;7;44;30m Coldstart
$ CONFIG VTCOLOR_00.06 ^[[0;7;44;33;5m Late
$ CONFIG VTCOLOR_01.01 ^[[0;7;47;31m Down
$ CONFIG VTCOLOR_01.02 ^[[0;7;43;34m Ready
$ CONFIG VTCOLOR_01.03 ^[[0;7;44;33m Spare
$ CONFIG VTCOLOR_01.04 ^[[0;7;40;33m Delay
$ CONFIG VTCOLOR_01.05 ^[[0;7;40;36m Tiedown
$ CONFIG VTCOLOR_ERR ^[[0;5m
$ CONFIG VTCOLOR_FWD ^[[0m
$ CONFIG VTCOLOR_REV ^[[0;7m
$ CONFIG VTCOLOR_ULN ^[[0;4m
$ CONFIG VTMONO_FWD "^[[0m" Forward video

$ CONFIG VTMONO_REV "^[[0;7m" Reverse video
$ CONFIG VTMONO_ERR "^[[0;5m" Blink on errors
$ CONFIG VTMONO_ULN "^[[0;4m" Underline
$ CONFIG VTMONO_00.00 "^[[0;5;7m" Loading = reverse blink
$ CONFIG VTMONO_00.01 "^[[0;7m" Traveling = reverse
$ CONFIG VTMONO_00.02 "^[[0;7m" Dumping = reverse
$ CONFIG VTMONO_00.03 "^[[0;7m" Queueing = reverse
$ CONFIG VTMONO_00.04 "^[[0;7;4m" Locked = underlined
$ CONFIG VTMONO_00.05 "^[[0;5m" Coldstart = forward blink
$ CONFIG VTMONO_00.06 "^[[0;5m" Late = forward blink
$ CONFIG VTMONO_01.01 "^[[0;1m" Down = bold
$ CONFIG VTMONO_01.02 "^[[0;7m" Ready = reverse
$ CONFIG VTMONO_01.03 "^[[0;1m" Spare = bold
$ CONFIG VTMONO_01.04 "^[[0m" Delay = forward video
$ CONFIG VTMONO_01.05 "^[[0;1;7m" Tiedown=reverse bold
$ CONFIG WASTEDUMPTIME 90
! INT(0,1000000) "The normal dumping time in seconds for a "\
"truck to dump it's load at a waste dump."
$ CONFIG WEEK "WEEK"
$ CONFIG WEEKBEGDAY 0
! INT(0,6) "The first day of the work week. "\
"The days of the week are numbered from 0 (Sunday) to 6 (Saturday)."
$ CONFIG WEEKBEGSHIFT 1
! INT(0,100) "The shift number considered to be "\
"the first shift of the work week. The shifts are numbered "\
"from 1 (first shift) to the number of shifts per day (the "\
"last shift)."
$ CONFIG WEEKENDDAY 6
! INT(0,6) "The last day of the work week."
$ CONFIG WEEKENDSHIFT
! INT(0,100) "The default is LASTSHIFT. "\
"The shift number of the last shift of the work week."

$ CONFIG WORKASSIGN ""

! STRING("","") "Selects how the LINEUP Utility makes "\
"assignments of workers to equipment. When set to AUTOAUX "\
"workers will be assigned to auxiliarty equipment. "\
"When set to REVERSE workers will be assigned to the "\
"higher numbered equipment first. "\
"When set to SENIORITY workers will be assigned by seniority. "\
"When set to LINEUPSPARE workers will be assigned to Spare, as "\
"well as Ready and Tiedown, equipment."
$ CONFIG WORKERFMT "%5.5..0s"

! STRING("","") "I/O format used for the worker identification "\
"string, see IDSTRING."
$ CONFIG YESTERDAY "Yesterday"

! STRING("","") "Client word for the DISPATCH word Yesterday."

D
Output from mms keypad Symbols
Symbol Type In? Help? Clr? Min/Template Max/Prefix
------ ---- --- ----- ---- ------------ ----------
Ftbl_auxmod Module
A$NEW UNIT Yes No No
A$ID UNIT Yes No No
A$PANEL Integer Yes No No 1 32767
A$UNIT UNIT No No No
A$STATUS STATUS Yes No No
A$LSTAT STATUS Yes No No
A$LREASON Integer Yes Yes No Nil REASONMAX
A$LOC UNIT Yes No No
A$DEL Boolean Yes No No
A$CREW CREW Yes No No
A$OPER Ascii Yes Yes No Nil Nil
A$OPNAME Ascii No No No
A$TYPE QUALIF Yes No No
A$REASON Ascii No No No
A$COMMENT Ascii No No No
A$LOAD LOAD Yes No No
A$ACTION ACTION Yes No No
A$BAY Ascii Yes No No
A$BAYNO Integer No No No
A$VTBL Integer Yes No No 0 255
A$VIRTUAL Boolean Yes No No
A$DIGITAL Boolean Yes No No
A$ANALOG Unsigned Yes No No 0 255
A$PULSE Integer Yes No No 0 2147483647
A$VNAME Ascii No No No
A$VAN Ascii Yes No No
A$LINECMT Ascii Yes No No
A$SENDCOUNT Integer No No No
A$RCVCOUNT Integer No No No
A$PORT Integer No No No
A$LOGIN CREW Yes No No
A$TIMELAST Unsigned No No No
A$TIMENEXT Unsigned No No No
A$TIMELATE Unsigned No No No
A$X Integer Yes No No MINXLOC MAXXLOC
A$Y Integer Yes No No MINYLOC MAXYLOC
A$GPSRADIUS Integer Yes No No MINGPSRADIUS MAXGPSRADIUS
A$REGION Ascii No No No
A$PIT Ascii No No No
A$EXCAV Ascii Yes Yes No UNITTMP_02 UNITPFX_02
Ftbl_beans Module
Ftbl_dumped_beans Module
BD$LAST_LOADS Integer No No No
D-1
D-2 System Administration Class
BD$LAST_TONS Float No No No
BD$LAST_GRADE Float No No No
BD$THIS_LOADS Integer No No No
BD$THIS_TONS Float No No No
BD$THIS_GRADE Float No No No
BD$TOTL_LOADS Integer No No No
BD$TOTL_TONS Float No No No
BD$TOTL_GRADE Float No No No
Ftbl_loaded_beans Module
BL$LAST_LOADS Integer No No No
BL$LAST_TONS Float No No No
BL$LAST_GRADE Float No No No
BL$THIS_LOADS Integer No No No
BL$THIS_TONS Float No No No
BL$THIS_GRADE Float No No No
BL$TOTL_LOADS Integer No No No
BL$TOTL_TONS Float No No No
BL$TOTL_GRADE Float No No No
Ftbl_pit_beans Module
BP$LAST_LOADS Integer No No No
BP$LAST_TONS Float No No No
BP$LAST_GRADE Float No No No
BP$THIS_LOADS Integer No No No
BP$THIS_TONS Float No No No
BP$THIS_GRADE Float No No No
BP$TOTL_LOADS Integer No No No
BP$TOTL_TONS Float No No No
BP$TOTL_GRADE Float No No No
Ftbl_inv_beans Module
INV$ID Ascii Yes No No
INV$NEW Ascii Yes No No
INV$DEL Boolean Yes No No
INV$LOADS Integer Yes No No 0 100000
INV$TONS Float Yes No No 0.00 17000000.00
INV$GRADE Float Yes No No 0.00 100.00
INV$INC Function No No No sd
Ftbl_blendmod Module
BL$NEW Ascii Yes Yes No
BL$ID Ascii Yes Yes No
BL$DEL Boolean Yes No No
BL$MIN Float Yes No No 0.00 100.00
BL$MAX Float Yes No No 0.00 100.00
BL$NOW Float Yes No No 0.00 100.00
BL$AVG Ascii No No No
BL$PCT Integer Yes No No 0 100
BL$PCTNOW Float Yes No No 0.00 100.00
BL$MASS Float Yes No No 0.00 10000.00
BL$DEV Integer Yes No No 0 100
BL$NAME Enum No No No
BL$CAT Enum No No No
BL$BLOCKLPTONS Float Yes No No 0.00 500000.00
Output from mms keypad Symbols January 2003

System Administration Class D-3
BL$BLOCKREMTONS Float Yes No No 0.00 500000.00

BL$CUMTONS Float Yes No No 0.00 1000000.00
BL$OBJTONS Float Yes No No 0.00 1000000.00
BL$GRADE Ascii Yes Yes No GRADETMP Nil
BL$BLOCK Ascii Yes No No
BL$EXCAV Ascii Yes Yes No UNITTMP_02 UNITPFX_02
Ftbl_breaks Module
BRK$NEW Ascii Yes No No
BRK$ID Ascii Yes No No
BRK$START Ascii Yes No No
BRK$END Ascii Yes No No
BRK$LENGTH Ascii Yes No No
BRK$SHIFT SHIFT Yes No No
BRK$TYPE BREAK Yes No No
BRK$CODE Integer Yes Yes No Nil REASONMAX
BRK$DEL Boolean Yes No No
client Remote FORMS Table
Ftbl_dbfunc Module
DATE Ascii Yes No No
DB$PIT Ascii Yes No No
DB$SHIFT Ascii Yes No No
PIT$FD Integer No No No
PIT$OPEN Function No No No s
PIT$COPY Ascii Yes No No
NOHOLIDAY Ascii Yes No No
SH$FD Integer No No No
SH$START Integer No No No
SH$DATE Ascii No No No
SH$INDEX Integer No No No
SH$TIME Integer No No No
SH$CREW CREW Yes No No
SH$FACTOR Float Yes No No 0.50 5.00
ROTATION Function No No No d
DIGFACTOR Function No No No dd
Ftbl_drilldat Module
DR$NEW Ascii Yes No No
DR$ID Ascii Yes No No
DR$EQMT Ascii Yes Yes No
DR$BLAST Ascii Yes Yes No UNITTMP_06 UNITPFX_06
DR$LOAD LOAD Yes No No
DR$DEPTH Integer Yes No No 1 1000
DR$TONS Float Yes No No 1.00 50000.00
DR$DEL Boolean Yes No No
Ftbl_event Module
EV$CREATE Function No No No
EV$TIMEOUT Function No No No ddsd*s
EV$FILE Function No No No ddsd*s
EV$IDLE Function No No No dsd*s
EV$RUN Function No No No
January 2003 Output from mms keypad Symbols

Ftbl_excavmod Module
E$NEW Ascii Yes Yes No UNITTMP_02 UNITPFX_02
E$ID Ascii Yes Yes No UNITTMP_02 UNITPFX_02
E$UNIT UNIT Yes No No
E$PANEL Integer Yes No No 1 32767
E$LOAD Ascii Yes Yes No
E$GRADE Ascii Yes Yes No
E$SIZE Float Yes No No 0.00 200.00
E$STATUS STATUS Yes No No
E$LSTAT STATUS Yes No No
E$LREASON Integer Yes Yes No Nil REASONMAX
E$LOC UNIT Yes No No
E$NEXT UNIT Yes No No
E$LASTLOC Ascii No No No
E$DEL Boolean Yes No No
E$VTBL Integer Yes No No 0 255
E$VIRTUAL Boolean Yes No No
E$DIGITAL Boolean Yes No No
E$ANALOG Unsigned Yes No No 0 255
E$PULSE Integer Yes No No 0 2147483647
E$VNAME Ascii No No No
E$MAINT Float Yes No No 0.00 1000.00
E$CREW CREW Yes No No
E$OPER Ascii Yes Yes No Nil Nil
E$OPNAME Ascii No No No
E$TIEDOWN UNIT Yes No No
E$RATE Integer Yes No No MINDIGRATE MAXDIGRATE
E$MAXRATE Integer Yes No No 100 6000
E$SPOT Integer Yes No No MINSPOTTIME MAXSPOTTIME
E$BACKUP Boolean Yes No No
E$SIGN Integer Yes No No 1 32767
E$AUTO Boolean Yes No No
E$SIGNEXCEPT Boolean Yes No No
E$ACTION ACTION Yes No No
E$OPRIOR PRIOR Yes No No
E$WPRIOR PRIOR Yes No No
E$ALLPRIOR Boolean Yes No No
E$DISABLE Boolean Yes No No
E$TRAM Boolean Yes No No
E$DLOCK UNIT Yes No No
E$DIGLOCK UNIT Yes No No
E$REGLOCK UNIT Yes No No
E$TLOCK Ascii Yes Yes Yes UNITTMP_01 UNITPFX_01
E$TYPE QUALIF Yes No No
E$TONS Float Yes No No 0.00 300.00
E$READY Ascii Yes Yes No UNITTMP_02 UNITPFX_02
E$ASSIGN Ascii Yes Yes No UNITTMP_01 UNITPFX_01
E$ASSIGN2 UNIT Yes No No
E$PICK Boolean Yes No No
E$SPARE Ascii Yes Yes No UNITTMP_02 UNITPFX_02
E$TREADY Boolean Yes No No
E$FEED Float No No No
M$PRIOR MPRIOR Yes No No
E$BAT Boolean Yes No No
E$LOADING Ascii Yes Yes No UNITTMP_01 UNITPFX_01

E$ACTLAST Ascii No No No
E$ACTNEXT Ascii No No No
E$MINS Float No No No
E$CLOCK Ascii No No No
E$REASON Ascii No No No
E$COMMENT Ascii No No No
E$BEANS Integer No No No
E$SHOULD Ascii No No No
E$BLEND Float No No No
E$TRUCKS Integer No No No
E$BREAK Ascii Yes No No
E$VAN Ascii Yes No No
E$FACTOR Float Yes No No 0.00 100.00
E$LOGIN CREW No No No
E$LINECMT Ascii Yes No No
E$SENDCOUNT Integer No No No
E$RCVCOUNT Integer No No No
E$PORT Integer No No No
E$GPSRADIUS Integer Yes No No MINGPSRADIUS MAXGPSRADIUS
E$GPSTYPE GPSTYPE Yes No No
E$X Integer Yes No No MINXLOC MAXXLOC
E$Y Integer Yes No No MINYLOC MAXYLOC
E$LPEQMT LPEXCAV Yes No No
E$TDOWN Boolean Yes No No
E$REGION Ascii No No No
E$PIT Ascii No No No
E$FUEL Integer Yes No No 0 4000
E$TANK Integer Yes No No 100 4000
E$TMPH Float Yes No No 0.00 4000.00
E$ASNTIME Ascii No No No
E$TRAMSCHED Ascii Yes No No
E$TRAMLOAD LOAD Yes No No
E$TRAV Integer No No No
E$PROPFEED Boolean Yes No No
E$NONLPTRKPENALTY Float Yes No No 0.00 400.00
E$CAR Ascii No No No
Ftbl_formfunc Module
SWAP Ascii Yes No No
FORM Ascii Yes No No
FCL Ascii Yes No No
SHELL Ascii Yes No No
HELP Ascii Yes No No
PRINT Ascii Yes No No
PFORM Ascii Yes No No
COPIES Integer Yes No No 1 255
SPLIT Ascii Yes No No
WAIT Integer Yes No No 0 3600
CLOCK Ascii No No No
ASK Function No No No ss*?
VERBOSE Yes No No
CONFIG Ascii No No No
CREATED Ascii No No No
PRINTF Function No No No s*?
FMT Function No No No d

WHICH Function No No No ss*

ELEM Function No No No ds*
STRPOS Function No No No ss
STRLEN Function No No No s
STRNCMP Function No No No ssd
SUBSTR Function No No No sdd
ACCESS Function No No No ss
OPEN Function No No No ss
CLOSE Function No No No d
REWIND Function No No No d
READ Function No No No #dsv*
WRITE Function No No No ds*?
FLUSH Function No No No d
DECODE Function No No No ssv*
ABBREV Function No No No e
ENUM Function No No No et
ENUMSET Function No No No ed
ENUMSIZE Function No No No e
ENUMTYPE Function No No No sd
SPAWN Function No No No ssss
REFRESH Function No No No s*
DIAG Function No No No #s*?
MSG Function No No No s*?
CPU Function No No No s
MOD Function No No No dd
WHERE Function No No No d
EVAL Function No No No s
TOTALAGAIN Function No No No b
MORE Boolean Yes No No
STOP Boolean Yes No No
MOVETO Function No No No dd
HELPSTR Function No No No s*
HELPINT Function No No No d*
HELPFLOAT Function No No No f*
HELPEXPR Function No No No s
PRINTNAME Function No No No s
SECSTOSHIFT Function No No No dvvvv
SHIFTTOSECS Function No No No dddd
SECSTODATE Function No No No dvvvv
DATETOSECS Function No No No dddd
HMSTOSECS Function No No No s
SHIFTLEN Function No No No d
SHIFTLEN2 Function No No No d
SQRT Function No No No f
SIN Function No No No f
COS Function No No No f
TAN Function No No No f
ATAN Function No No No f
ATAN2 Function No No No ff
EXP Function No No No f
LOG Function No No No f
LOG10 Function No No No f
POW Function No No No ff
MOUSE Function No No No vv
TYPO Function No No No s*d

CHCASE Function No No No sd
SETENV Function No No No ss
GETENV Function No No No s*d
FORMOK Function No No No s
DEFINED Function No No No s
EXPRLINE Function No No No
EXPRFILE Function No No No
EXPRSYM Function No No No
ARGV Ascii No No No
BAND Function No No No dd
BOR Function No No No dd
BXOR Function No No No dd
BSHIFTL Function No No No dd
BSHIFTR Function No No No dd
SCROLL Function No No No sd
TEMPLATE Function No No No ss
TEMPLATEPFX Function No No No ssv
MAPCONFIG Function No No No sffffff
GLOBETOMAP Function No No No ffvv
MAPTOGLOBE Function No No No ffvv
BATCHMODE Function No No No
Ftbl_grade Module
G$ID Ascii Yes Yes No Nil Nil
G$NEW Ascii Yes Yes No Nil Nil
G$DUMP UNIT Yes No No
G$LOC UNIT Yes No No
G$LOAD LOAD Yes No No
G$BLEND BLEND Yes No No
G$DBAR UNIT Yes No No
G$DEL Boolean Yes No No
G$SPGR Float Yes No No 0.00 15.00
G$GRADE Float Yes No No 0.00 100.00
G$UPDATE Boolean Yes No No
G$INV Float Yes No No 0.00 200000.00
Ftbl_inventory Module
DB$INV Function No No No ddd
INV$FD Integer No No No
INV$NEW Ascii Yes No No Nil Nil
INV$ID Ascii Yes No No Nil Nil
INV$DEL Boolean Yes No No
INV$ACTIVE Boolean Yes No No
INV$UNIT UNIT Yes No No
INV$DATE Ascii Yes No No
INV$INVDATE Ascii No No No
INV$ORIGTONS Float Yes No No 0.00 9999999.00
INV$TONS Float No No No
INV$GRADE Float No No No
INV$ADDED Float No No No
INV$REMOVED Float No No No
INV$SURVEYNEW Ascii Yes No No
INV$SURVEYDATE Ascii Yes No No
INV$SURVEYTONS Float Yes No No 0.00 9999999.00
INV$SURVEYWORKER Integer Yes No No 0 999
INV$SURVEYGRADE Float Yes No No 0.00 9999999.00

INV$SURVEYDEL Boolean Yes No No

INV$SURVEYLOAD LOAD Yes No No
INV$SURVEYADDED Float No No No
INV$SURVEYREMOVED Float No No No
Ftbl_lineup Module
U$CLR CREW Yes No No
U$CLRVAN Boolean Yes No No
U$AUTO CREW Yes No No
U$VAN Ascii Yes Yes No
U$VANUNIT UNIT Yes No No
U$VANDEL UNIT Yes No No
Ftbl_lpsumry Module
LP$FROM Function No No No #d
LP$TO Function No No No #d
LP$NODE Function No No No #d
LP$LOAD LOAD No No No
LP$PRIOR Integer No No No
LP$TRAVEL Float No No No
LP$SPOT Float No No No
LP$DUMP Float No No No
LP$HAULRATE Float No No No
LP$DIGRATE Float No No No
LP$DUMPRATE Float No No No
LP$GRADE Ascii No No No
LP$BLAST Ascii No No No
LP$EXCAVS Integer No No No
LP$SIZE Float No No No
LP$EPIT Ascii No No No
LP$DPIT Ascii No No No
LP$ACTUAL Float Yes No No 0.00 200.00
LP$THEOR Float No No No
LP$NOW Float No No No
LP$DELAY Float No No No
LP$TOTPATH Float No No No
LP$TOTDIG Float No No No
LP$SWING Float No No No
LP$INTVL Float No No No
LP$PIT Ascii No No No
LP$COMPUTE Boolean Yes No No
LP$DUMPCAPY Float No No No
LP$DUMPFEED Float No No No
LP$MATLFEED Float No No No
LP$TARGET Float No No No
LP$TIME Function No No No d
LP$SHIFT Ascii Yes No No
LP$REFRESH Boolean Yes No No
LP$TRUCKSIZE Float No No No
LP$LPTRUCKTYPE LPTRUCK No No No
LP$LOADTIME Float No No No
LP$DIGFACTOR Float No No No
LP$DIGCAPYPCT Float No No No
LP$DUMPCAPYPCT Float No No No
LP$GLOBPROD Boolean Yes No No

LP$EQUALFEED Boolean Yes No No

LP$MIXLP Boolean Yes No No
LP$TWOWAYDUMPLOCK Boolean Yes No No
LP$EQUALSPLIT Boolean Yes No No
LP$QUEUE Float No No No
LP$PRODVAL Float No No No
LP$FEEDBYMATL Float No No No
LP$LPDIAG Integer No No No
LP$VERSION Integer No No No
Ftbl_locmod Module
L$NEW UNIT Yes No No
L$ID UNIT Yes No No
L$UNIT UNIT No No No
L$X Integer Yes No No MINXLOC MAXXLOC
L$Y Integer Yes No No MINYLOC MAXYLOC
L$Z Integer Yes No No MINZLOC MAXZLOC
L$STATUS STATUS Yes No No
L$DEL Boolean Yes No No
L$SIGN Integer Yes No No 1 32000
L$AUTO Boolean Yes No No
L$BLEND Ascii Yes Yes No
L$SIGNEXCEPT Boolean Yes No No
L$SIGNLOUD Boolean Yes No No
L$TDOWN Boolean Yes No No
L$REGION Ascii Yes Yes No
L$PIT Ascii No No No
L$LOAD LOAD Yes No No
L$TIME Integer Yes No No MINDUMPTIME MAXDUMPTIME
L$CAPY Float Yes No No 0.00 100000.00
L$CALL Float Yes No No 0.00 100000.00
L$FEED Float No No No
L$SHOP SHOP Yes No No
L$QUEUE Integer Yes No No 1 20
L$PCT Integer Yes No No 0 100
L$BAYS Integer Yes No No 1 9
L$BAT Boolean Yes No No
L$GPSRADIUS Integer Yes No No MINGPSRADIUS MAXGPSRADIUS
L$GPSTYPE GPSTYPE Yes No No
L$ACTION ACTION Yes No No
L$REASON Ascii No No No
Ftbl_plot Module
PLOT$INIT Boolean Yes No No
PLOT$PLOT Boolean Yes No No
PLOT$GRID Boolean Yes No No
PLOT$HISTO Boolean Yes No No
PLOT$SOLID Boolean Yes No No
PLOT$XGRID Integer Yes No No 1 100
PLOT$XCHAR Integer Yes No No 1 100
PLOT$YGRID Integer Yes No No 1 100
PLOT$YCHAR Integer Yes No No 1 100
PLOT$CHAR Ascii Yes No No
PLOT$HEADER Ascii Yes No No
PLOT$XAXIS Ascii Yes No No

PLOT$YAXIS Ascii Yes No No

PLOT$LEGEND Ascii Yes No No
PLOT$XY Function No No No dff
Ftbl_psw Module
PSW$OPEN Function No No No ss
PSW$REGISTER Function No No No ss
PSW$NOTALK Function No No No s
PSW$SEND Function No No No s*t
PSW$CALL Function No No No ss*t
PSW$COMMAND Function No No No s
PSW$COMM_LOG Function No No No sds
PSW$INPUT Function No No No s
PSW$BIND Function No No No s
PSW$NAME Function No No No
PSW$NUMBER Function No No No
PSW$RETRY Function No No No
PSW$SEQNO Function No No No
PSW$ISRETRY Function No No No
PSW$ARGC Function No No No
PSW$ARGV Function No No No #d*v
PSW$ID Function No No No #
PSW$PATH Function No No No
PSW$DEVICE Function No No No
PSW$CONSOLE Function No No No *s
PSW$XMIT Function No No No s
PSW$DEBUG Function No No No ss
PSW$LOG Function No No No
PSW$ALIVE Function No No No sd
PSW$NAMETOADDR Function No No No s
PSW$NAMETOID Function No No No s
PSW$ADDRTONAME Function No No No s
PSW$SETADDR Function No No No sss
PSW$RETURN Function No No No *t
Ftbl_reports Module
REP$CREW CREW Yes No No
REP$RANGE Ascii Yes No No
REP$UNIT UNIT Yes No No
REP$ID Ascii No No No
REP$DATE Ascii No No No
REP$PRINT Boolean Yes No No
REP$DISPLAY Boolean Yes No No
REP$REPORT Boolean Yes No No
REP$CUSTOM Boolean Yes No No
REP$FORM Boolean Yes No No
REP$TEXT Boolean Yes No No
REP$TYPE Integer Yes No No 0 100
REP$CHECK Boolean Yes No No
REP$REASON Integer Yes No No Nil REASONMAX
REP$CONTIN Boolean Yes No No
REP$FIRST Integer No No No
REP$LAST Integer No No No
REP$SHIFT Function No No No dd
REP$INIT Boolean Yes No No

REP$NOSUM Integer No No No
REP$MUNCH Function No No No dd
Ftbl_shiftbkt Module
REP$VALID Integer No No No
REP$INVALID Integer No No No
REP$OPER Integer No No No
REP$LOADGRP Boolean Yes No No
REP$TRAM Boolean Yes No No
REP$IBYGRADE Boolean Yes No No
REP$COMPUTE Function No No No sd
REP$HCREW Enum No No No
PLAN$GET Function No No No sdv
PLAN$ADD Function No No No sfd
PLAN$RANGE Function No No No sdd
PLAN$CLEAR Boolean Yes No No
INV$CLEAR Boolean Yes No No
INV$ADD Function No No No sdf*
Ftbl_operbkt Module
OP$ID Ascii Yes No No
OP$UNIT UNIT No No No
OP$NAME Ascii No No No
OP$OPERID Ascii No No No
OP$LOCID Ascii No No No
OP$LT Integer No No No
OP$LOADS Integer No No No
OP$TONS Float No No No
OP$LOADTM Integer No No No
OP$TIME Integer No No No
OP$PIT Ascii No No No
Ftbl_truckbkt Module
EQ$ID Ascii Yes No No
EQ$UNIT UNIT No No No
EQ$EQMTTYPE QUALIF No No No
EQ$TIME Integer No No No
EQ$PIT Ascii No No No
EQ$SHIFT Integer No No No
TK$ID Ascii Yes No No
TK$UNIT UNIT No No No
TK$EQMTTYPE QUALIF No No No
TK$TIME Integer No No No
TK$PIT Ascii No No No
TK$KEY Ascii No No No
TK$LOADS Integer No No No
TK$TONS Float No No No
TK$DISPLOADS Integer No No No
TK$DISPDUMPS Integer No No No
TK$EQMTIDLE Integer No No No
TK$CRUSHIDLE Integer No No No
TK$NOASSIGN Integer No No No
TK$FLATS Integer No No No
TK$LOADSTART Integer No No No
TK$LOADEND Integer No No No

TK$TONSSTART Float No No No
TK$TONSEND Float No No No
TK$FUEL Integer No No No
TK$FULLTIME Integer No No No
TK$EMPTYTIME Integer No No No
TK$DIST Integer No No No
TK$TOTDIST Integer No No No
TK$TMPH Float No No No
TK$FULLCALC Integer No No No
TK$EMPTYCALC Integer No No No
TK$LOADSECS Integer No No No
TK$DUMPSECS Integer No No No
TK$SPOTSECS Integer No No No
TK$IDLEBYEXCAV Integer No No No
TK$LOADBYEXCAV Integer No No No
TK$LOADTMBYEXCAV Integer No No No
TK$SPOTTMBYEXCAV Integer No No No
TK$FULLREADY Integer No No No
TK$EMPREADY Integer No No No
TK$SHIFT Integer No No No
Ftbl_excavbkt Module
EX$ID Ascii Yes No No
EX$UNIT UNIT No No No
EX$EQMTTYPE QUALIF No No No
EX$TIME Integer No No No
EX$PIT Ascii No No No
EX$KEY Ascii No No No
EX$LOADS Integer No No No
EX$TONS Float No No No
EX$DISPLOADS Integer No No No
EX$EQMTIDLE Integer No No No
EX$SPOTSECS Integer No No No
EX$LOADSECS Integer No No No
EX$LOADUNIT UNIT No No No
EX$DUMPUNIT UNIT No No No
EX$LOADID Ascii Yes No No
EX$GRADEID Ascii No No No
EX$DUMPID Ascii No No No
EX$GRADES Float No No No
EX$LOADTIME Integer No No No
EX$LOADELEV Integer No No No
EX$DUMPELEV Integer No No No
EX$SHIFT Integer No No No
EX$LOADTYPE LOADTYPE No No No
EX$DISPDUMPS Integer No No No
EX$EMPTYDIST Integer No No No
EX$FULLDIST Integer No No No
Ftbl_drillbkt Module
DRL$ID Ascii Yes No No
DRL$UNIT UNIT No No No
DRL$EQMTTYPE QUALIF No No No
DRL$TIME Integer No No No
DRL$PIT Ascii No No No

DRL$BLASTUNIT UNIT No No No
DRL$BLASTID Ascii No No No
DRL$DEPTH Integer No No No
DRL$TONS Float No No No
DRL$SHIFT Integer No No No
Ftbl_locbkt Module
LOC$ID Ascii Yes No No
LOC$DUMPID Ascii Yes No No
LOC$INVEN Ascii Yes No No
LOC$INVDATE Ascii No No No
LOC$LOADUNIT UNIT No No No
LOC$DUMPUNIT UNIT No No No
LOC$EXCAVID Ascii No No No
LOC$LOADID Ascii No No No
LOC$GRADEID Ascii No No No
LOC$PIT Ascii No No No
LOC$LOADS Integer No No No
LOC$TONS Float No No No
LOC$GRADES Float No No No
LOC$LOADREGION Integer No No No
LOC$DUMPREGION Integer No No No
LOC$DISPDUMPS Integer No No No
LOC$CRUSHSECS Integer No No No
LOC$CRSHSECS Integer No No No
LOC$DUMPSECS Integer No No No
LOC$CRSHTONS Float No No No
LOC$STARTTONS Float No No No
LOC$STARTGRADE Float No No No
LOC$LOADEDGRADE Float No No No
LOC$DUMPEDGRADE Float No No No
LOC$LOADELEV Integer No No No
LOC$DUMPELEV Integer No No No
LOC$SHIFT Integer No No No
LOC$LOADTYPE LOADTYPE No No No
Ftbl_auxbkt Module
AUX$ID Ascii Yes No No
AUX$UNIT UNIT No No No
AUX$EQMTTYPE QUALIF No No No
AUX$TIME Integer No No No
AUX$PIT Ascii No No No
AUX$KEY Ascii No No No
AUX$SHIFT Integer No No No
Ftbl_roadmod Module
R$BEGIN UNIT Yes No No
R$CLOSE UNIT Yes No No
R$END UNIT Yes Yes No
R$DEL Boolean Yes No No
R$DIST Integer Yes No No 0 50000
R$STREET Ascii Yes No No
R$EMPTY Integer Yes No No 0 18000
R$LOADED Integer Yes No No 0 18000
R$CLOSED Boolean Yes No No

R$SPILL Boolean Yes No No

R$TROLLEY Boolean Yes No No
R$ELEV Integer Yes No No 651248 651240
R$X Integer Yes No No 651224 651216
R$Y Integer Yes No No 651200 651192
R$Z Integer Yes No No 651248 651240
R$XGRAPH Integer Yes No No -2147483647 2147483647
R$YGRAPH Integer Yes No No -2147483647 2147483647
R$FACTOR Integer Yes No No 10 200
R$GRADE Float No No No
R$ID Ascii No No No
R$ESPEED Float No No No
R$LSPEED Float No No No
R$LBEGIN Integer No No No
R$LEND Integer No No No
R$LOC Ascii No No No
R$PATH Function No No No sss
R$TKPATH Function No No No svv
R$POS Function No No No ss
R$COMPUTE Boolean Yes No No
CALCPATH Ascii No No No
RTE$BEGIN UNIT Yes No No
RTE$END UNIT Yes No No
RTE$ONEWAY ONEWAY Yes No No
R$GFXBEGIN Boolean Yes No No
R$GFXEND Boolean Yes No No
R$LINK Integer No No No
ISBARRED Function No No No dd
ISDELROUTE Function No No No dddddddd
ISONTHEWAY Function No No No ddd
Ftbl_shiftdump Module
Ftbl_tm Module
TM$EVENT Function No No No sd*d
TM$INIT Function No No No dd
TM$DURATION Function No No No sd
TM$TIMECAT Function No No No sddd
SD$TIMECAT Function No No No dddd
SD$STATUS Function No No No ddd
SD$LOGIN Function No No No ddd
SD$QUEUE Function No No No sd
SD$LOADGRP Function No No No d
SD$READYTM Function No No No ssdd
SD$DURATION Function No No No dd
SD$NEWSHIFT Boolean Yes No No
Ftbl_simulmod Module
DST$TRAV DSTR Yes No No
SIM$TRAV Integer Yes No No 0 30000
DST$REPLY DSTR Yes No No
SIM$REPLY Integer Yes No No 0 30000
DST$TSTART DSTR Yes No No
SIM$TSTART Integer Yes No No 0 30000
DST$ESTART DSTR Yes No No

SIM$ESTART Integer Yes No No 0 30000

DST$TDELAY DSTR Yes No No
SIM$TDELAY Integer Yes No No 0 30000
DST$EDELAY DSTR Yes No No
SIM$EDELAY Integer Yes No No 0 30000
DST$SIMSPOT DSTR Yes No No
E$SIMSPOT Integer Yes No No MINSPOTTIME MAXSPOTTIME
DST$SIMDIG DSTR Yes No No
E$SIMDIG Integer Yes No No 10 1800
DST$SIMDUMP DSTR Yes No No
L$SIMDUMP Integer Yes No No MINDUMPTIME MAXDUMPTIME
SIM$EQMT Ascii Yes No No
SIM$FORM Ascii Yes No No
SIM$TIME Ascii Yes No No
SIM$CREATE Ascii Yes No No
SIM$REPEAT Ascii Yes No No
SIM$SHIFT SHIFT Yes No No
SIM$ACTION ACTION Yes No No
SIM$CODE Integer Yes No No 0 999999
SIM$DEL Boolean Yes No No
SIM$FACTOR Integer Yes No No 0 100
SIM$COMMENT Ascii Yes No No
SIM$EVENT Function No No No dsddd
DST$SIGMA Function No No No dff
DST$LIMITS Function No No No ddff
DST$EVENT Function No No No dff
DST$URAND Function No No No dd
Ftbl_statchng Module
Ftbl_statchng_eqmt Module
ST$EQMT UNIT Yes No No
ST$EDEL Boolean Yes No No
ST$NOASN Boolean Yes No No
ST$ETYPE QUALIF Yes No No
ST$ESIZE Float Yes No No 0.00 500.00
ST$AUX UNIT Yes No No
ST$ATYPE QUALIF Yes No No
ST$REFRESH Boolean Yes No No
ST$EUNIT UNIT No No No
ST$EID Ascii No No No
ST$AUNIT UNIT No No No
ST$AID Ascii No No No
Ftbl_statchng_state Module
ST$TIME Ascii Yes No No
ST$DEL Boolean Yes No No
ST$STATUS STATUS Yes No No
ST$CODE Integer Yes Yes No Nil REASONMAX
ST$COMMENT Ascii Yes No No
ST$DURATION Integer No No No
ST$CAT TIMECAT No No No
ST$LINK Integer No No No

Ftbl_tclfunc Module
TCL$REGISTER Function No No No ss
TCL$SEND Function No No No s*
TCL$SENDB Function No No No s*
TCL$CALL Function No No No ss*
TCL$RETURN Function No No No #*s
TCL$ERROR Function No No No s
TCL$ARGC Function No No No
TCL$ARGV Function No No No #
TCL$MODE Function No No No *d
TCL$FLUSH Function No No No
Ftbl_truckmod Module
T$NEW Ascii Yes Yes No UNITTMP_01 UNITPFX_01
T$ID Ascii Yes Yes No UNITTMP_01 UNITPFX_01
T$PANEL Integer Yes No No 1 32767
T$LOAD LOAD Yes No No
T$LOADLAST LOAD No No No
T$GRADE Ascii Yes Yes No GRADETMP Nil
T$SIZE Float Yes No No 1.00 300.00
T$STATUS STATUS Yes No No
T$LSTAT STATUS Yes No No
T$LREASON Integer Yes Yes No Nil REASONMAX
T$LOC UNIT Yes No No
T$NEXT UNIT Yes No No
T$LASTLOC Ascii No No No
T$DEL Boolean Yes No No
T$VTBL Integer Yes No No 0 255
T$VIRTUAL Boolean Yes No No
T$DIGITAL Boolean Yes No No
T$ANALOG Unsigned Yes No No 0 255
T$PULSE Integer Yes No No 0 2147483647
T$VNAME Ascii No No No
VSMS$NAME Function No No No dd
VSMS$PRIOR Function No No No dd
T$FUEL Integer Yes No No 0 4000
T$TANK Integer Yes No No 100 4000
T$MAINT Float Yes No No 0.00 1000.00
T$CREW CREW Yes No No
T$OPER Ascii Yes Yes No Nil Nil
T$OPNAME Ascii No No No
T$ACTION ACTION Yes No No
T$ASSIGN UNIT Yes No No
T$ELOCK Ascii Yes Yes No UNITTMP_02 UNITPFX_02
T$LOCKALL Boolean Yes No No
T$BARALL Boolean Yes No No
T$DLOCK UNIT Yes No No
T$RLOCK Ascii Yes No No
T$EUNLOCK Boolean Yes No No
T$DUNLOCK Boolean Yes No No
T$UNBAR Boolean Yes No No
T$TYPE QUALIF Yes No No
T$TMPH Float Yes No No 0.00 4000.00
T$TONS Float Yes No No 0.00 300.00
T$NOASN Boolean Yes No No

T$MINS Float No No No
T$CLOCK Ascii No No No
T$REASON Ascii No No No
T$COMMENT Ascii No No No
T$BEANS Integer No No No
T$SHOULD Ascii No No No
T$EXCAV Ascii Yes Yes No UNITTMP_02 UNITPFX_02
T$EXNEXT Ascii No No No
T$ASNTIME Ascii No No No
T$ACTLAST ACTION Yes No No
T$ACTNEXT ACTION Yes No No
T$TIMELAST Unsigned No No No
T$TIMENEXT Unsigned No No No
T$TIMELATE Unsigned No No No
T$EBAR Ascii Yes Yes No UNITTMP_02 UNITPFX_02
T$DBAR UNIT Yes No No
T$LBAR LOAD Yes No No
T$BAY Ascii Yes No No
T$TIEDOWN Ascii Yes No No
T$RETORQ Integer Yes No No Nil RETORQUETRIPS
T$Q Ascii No No No
T$QREADY Ascii No No No
T$QCOLOR Color No No No
T$REGNEXT Ascii No No No
T$BREAK Ascii Yes No No
T$BREAKTM Ascii Yes No No
T$VAN Ascii Yes No No
T$FACTOR Float Yes No No 0.25 3.00
T$LOGIN CREW Yes No No
T$LINECMT Ascii Yes No No
T$SENDCOUNT Integer No No No
T$RCVCOUNT Integer No No No
T$PORT Integer No No No
DSP$ACT Function No No No dddds
T$X Integer Yes No No MINXLOC MAXXLOC
T$Y Integer Yes No No MINYLOC MAXYLOC
T$LPEQMT LPTRUCK Yes No No
T$NEXTSIGNID Integer No No No
T$REGION Ascii No No No
T$PIT Ascii No No No
T$TRAV Integer No No No
Ftbl_userdb Module
DB$RECORD Function No No No ss*
DB$FILE Function No No No ss*
DB$OPEN Function No No No sssv
DB$CLOSE Function No No No d
DB$NAME Function No No No d
DB$SYMBOL Function No No No tss*
DB$LINK Function No No No sd*
DB$SEEK Function No No No sd*
DB$COPY Function No No No ss
DB$DELETE Boolean Yes No No
DB$ZAP Function No No No s*
DB$CALL Function No No No st#*s

DB$SEND Function No No No dds

DB$RECV Function No No No ddvd
DB$SOCKET Function No No No dd
DB$CLEAN Function No No No s*
DB$SYMTBL Function No No No s*
DB$H Function No No No ss*
DB$MTIME Function No No No s
DB$TYPE Function No No No s
DB$LIST Function No No No #*s
DB$REFRESH Function No No No s*
DB$VAL Function No No No s
DB$LIMIT Function No No No sdtt
DB$WRITES Function No No No s
DB$SWAP Function No No No dd
DB$FLUSH Function No No No d
DB$FILEFMT Function No No No #tv
DB$RECFMT Function No No No #tsvvvvv
DB$DBTYPES Function No No No
DB$RECFLDS Function No No No #svvv
DB$NAMETOSHIFT Function No No No svvvv
DB$DATETOSHIFT Function No No No s
Ftbl_workrmod Module
W$CREW CREW Yes No No
W$LCREW CREW Yes No No
W$NCREW CREW Yes No No
W$ID Ascii Yes Yes No
W$ID2 Ascii Yes Yes No
W$NEW Ascii Yes Yes No
W$NAME Ascii Yes No No
HELLO Function No No No s
W$SHIFT Integer Yes No No 0 999
W$STAT WSTAT Yes No No
W$SEN Ascii Yes No No
W$NUMER Integer Yes No No 1 999
W$QTYPE QTYPE Yes No No
W$DEL Boolean Yes No No
W$SEARCH Function No No No ss
W$ASGN UNIT Yes No No
W$ASID Ascii No No No
W$RIDER LINEUP No No No
W$VAN Ascii No No No
W$SORT Boolean Yes No No
Ftbl_color Module
RD$COLOR Color No No No
UN$COLOR Color No No No
LD$COLOR Color No No No
ST$COLOR Color No No No
T$COLOR Color No No No
E$COLOR Color No No No
L$COLOR Color No No No
A$COLOR Color No No No

Ftbl_system Module
Ftbl_directory Module
OS$CWD Ascii Yes No No
OS$OPENDIR Function No No No s
OS$CLOSEDIR Function No No No d
OS$READDIR Function No No No d
OS$FILENAME Function No No No d
OS$FILEMODE Function No No No d
OS$FILETYPE Function No No No d
Ftbl_stat Module
OS$STAT Function No No No s
OS$ST_DEV Integer No No No
OS$ST_INO Integer No No No
OS$ST_MODE Unsigned No No No
OS$ST_NLINK Integer No No No
OS$ST_UID Integer No No No
OS$ST_GID Integer No No No
OS$ST_RDEV Integer No No No
OS$ST_SIZE Integer No No No
OS$ST_ATIME Integer No No No
OS$ST_MTIME Integer No No No
OS$ST_CTIME Integer No No No
OS$ST_BLKSIZE Integer No No No
OS$ST_BLOCKS Integer No No No
Ftbl_passwd Module
OS$GETPWUID Function No No No d
OS$GETGRGID Function No No No d
Ftbl_regexpr Module
OS$SETREGEXPR Function No No No s
OS$MATCHREGEXPR Function No No No s

E
RF Coverage Selection
An important part of the MasterLink network is the radio coverage in the mining
area. The MTS “RF Coverage” tab allows the user to check this information.
I
n
t
h
e
p
h
o
t
o
a
b
o
v
e
,
t
h
e
Colored dots indicate where a piece of mining equipment (outfitted with Master-
link hardware) reported its current access point association and GPS coordinates.
Each access point has a uniquely colored box around it so that the user can deter-
mine the area an access point covers.
E-1
E-2 System Administration Class
RF Coverage Selection Utility
The photo above shows the RF Coverage Selection utility. To show all repeater
coverage for a specified date range, do the following:
1. Select the “Association Map” button and the “All Nodes” button.
2. Enter the date and time range (longer date ranges take longer to display)
3. Left mouse click on the first repeater under the “Repeaters” list.
4. Hold down the shift key on your keyboard and left click the last repeater in
the “Repeaters” list. (you may need to move the scroll bar down to see the last
repeater in the list).
5. Left click on the “Refresh Display” button to display the results of the search.
To show only one repeater, do the same procedure, selecting only the desired
repeater to view.
January 2003
System Administration Class E-3
RF Coverage “No Association”
In the above photo, the small red dots indicate when a piece of equipment, outfit-
ted with the Masterlink hardware, was unable to report its GPS coordinates and
current access point information. These red dots should be relatively few in
number. However, this information does assist onsite personnel in determining
whether one of the mobile access points needs relocating for better performance.
To run the “No Coverage” report, do the following:
1. In the RF Coverage Selection utility, select the “No Association” button” and
the “All Nodes” button.
1. Enter the desired time and date range.
2. Left click on “Refresh Display”
No Coverage can also be run for an individual piece of equipment as well. To do

so:
1. In the RF Coverage Selection utility, select the “No Association” button” and
the “one node only” button.
1. Enter the desired date and time range.
January 2003
E-4 System Administration Class
2. In the drop down list, select the “node” to view. A node may be a access point
or a piece of equipment.
3. Press the “Refresh Display” button.
January 2003

Sysadmin Linux

Uploaded by

Copyright:

Available Formats

Sysadmin Linux

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sysadmin Linux

Uploaded by

Copyright:

Available Formats

®

Modular Mining Systems

Copyright © 2003 by Modular Mining Systems, Inc.

1 Overview of a System and Network ..................................................................................................... 1-1

Goals for this Chapter ..................................................................................................................... 1-1

2 System Administrator Duties ................................................................................................................ 2-1

Goals for this Chapter ..................................................................................................................... 2-1

3 System Structure .................................................................................................................................... 3-1

Some Comments About Pathname ........................................................................................... 3-3

4 Fundamental Linux Commands ........................................................................................................... 4-1

Goals for this Chapter ..................................................................................................................... 4-1

5 The vi Editor ........................................................................................................................................... 5-1

Goals for this Chapter ..................................................................................................................... 5-1

Contents - Continued January 2003

6 External and Internal System Hardware Components ...................................................................... 6-1

Goals for this Chapter ..................................................................................................................... 6-1

7 Basic System Maintenance .................................................................................................................... 7-1

Goals for this Chapter ..................................................................................................................... 7-1

Goals for this Chapter ..................................................................................................................... 8-1

January 2003 Contents - Continued

PSWD ........................................................................................................................................... 8-10

To Retrieve DISPATCH files from Tape Backup ........................................................................ 8-36

Appendix A Computer Basics ................................................................................................................. A-1

Bits and Bytes ................................................................................................................................ A-1

Appendix B The dbclean Utility ..............................................................................................................B-1

The DBCLEAN Utility ...................................................................................................................B-1

Appendix C List of Generic config Variables ........................................................................................ C-1

Appendix D Output from mms keypad Symbols .................................................................................. D-1

January 2003 Contents - Continued

The purpose of this system administration class is to show you how to

System Administration Class Outline

1. Overview of a System and Network

2. System Administrator Duties

3. System Directory Structure

4. Fundamental Linux Commands

5. The vi text Editor

6. Internal and External Hardware Components

7. Basic System Maintenance

8. DISPATCH Directory Structure and Related DISPATCH

Differences Between a System and a Network

A system is normally thought of as a self-contained unit that is usually

A network, although similar to a system, entails the use of additional

Two Common Views of a System

Component View of a System

Typically, the hardware can include the following:

• central processing unit (cpu)

The software includes

• the operating system (OS)

The interface includes

• the Linux kernel

The DISPATCH system is also a networked system of computers and

Overview of a System and Network January 2003

Figure 1.1 Generic Hardware Components

The DISPATCH system was originally designed to run on Sun workstations

Functional View of a System

The functional view of a system is an integration of major and minor sub-

Major sub-systems include:

• System hardware - physical components

January 2003 Overview of a System and Network