Order Number: SWRK-IG-35
This document describes the installation activities for SysWorks V3.5.
Revision/Update Information: This manual supercedes the SysWorks V3.4-1 Installation Guide
Operating System and Version:
OpenVMS VAX V7.2 or higher;
OpenVMS Alpha V7.2 or higher;
DECwindows/Motif V1.2-3 or higher
Software Version: SysWorks V3.5
Printed in Australia
The following are trademarks of Compaq Computer Corporation: ACMS, ALL-IN-1, AXP, BASIC, Bookreader, CDA, CI, DATATRIEVE, DBMS, DDIF, DEC, DEC ACCESSWORKS, DEC Ada, DEC C, DEC Fortran, DEC Pascal, DECdecision, DECdesign, DECdirect, DECdns, DECdocument, DECdtm, DECforms, DECimage, DECintact, DECmigrate, DECnet, DECnet/OSI, DECset, DECsupport, DECtp, DECwindows, Digital, DTIF, EDT, HSC, MASSBUS, MicroVAX, MicroVAX II, MSCP, OpenVMS, OpenVMS Cluster, RA, StorageWorks, TA, TMSCP, TURBOchannel, ULTRIX, VAX, VAX C, VAX MACRO, VAX-11/780, VAXcluster, VAXELN, VAXft, VAXstation, VIDA, VMS, VMScluster, VT100, and the DIGITAL logo.
PostScript is a registered trademark of Adobe Systems Inc.
Motif is a registered trademark of Open Software Foundation, Inc.
Oracle is a registered trademark, and Oracle CDD/Repository, Oracle CODASYL DBMS, Oracle Expert, Oracle Rally, Oracle Rdb, Oracle Trace and Rdb7 are trademarks of Oracle Corporation.
OSI is a registered trademark of CA Management, Inc
All other trademarks and registered trademarks are the property of their respective holders.
This document was prepared using DECdocument V3.3.
| Contents |
We welcome your comments on this manual or any SysWorks manual. If you have suggestions for improvements or find any errors, please indicate the chapter, section and page number (if available). Your input is valuable in improving future releases of our documentation.
You can send comments to us in the following ways:
SysWorks Corpita Pty Ltd 15 Bedford Street Collingwood VIC 3066 Australia |
This manual describes the activities required before, during and immediately after the installation of SysWorks.
This manual is intended for use by personnel installing SysWorks.
The following conventions are used in this document:
| Conventions | Description |
|---|---|
| [Ctrl/X] | A sequence such as [Ctrl/X] indicates that you must hold down the key labeled [Ctrl] while you press another key or a pointing device button. |
| [] |
In format descriptions, brackets indicate that whatever is enclosed is
optional; you can select none, one or all of the choices.
In system prompts indicates the default value which will be assumed if the Return key is pressed without first entering a value. |
| {} | In format descriptions, braces surround a required choice of options; you must choose one of the options listed. |
| | | In format descriptions, vertical bars separate the options. If the options are enclosed in brackets (i.e. []) you can select none, one or all of the choices. If the options are enclosed in braces (i.e. {}) you must choose one of the options listed. |
| () | In system prompts, parenthesis indicate the list of values one of which may be entered. The values are separated by a forward slash "/" |
| ... | An elipsis indicates that a value within a range may be chosen or a syntax repeated. A range may be indicated by a pair of end values, or an end value and an end keyword. For example Disk quota (0..unlimited) indicates that the keyword unlimited may be used to represent the highest possible disk quota. |
| italic text | Italicized words and letters indicate that you should substitute a word or value of your choice. |
| UPPERCASE TEXT | Uppercase letters indicate the name of a command or routine. |
| monospace text | Normal monospace text indicates system prompts and output. |
| bold monospace text | Bold monospace text indicates user responses to system prompts. |
| bold monospace italic text | Bold monospace italic text indicates user responses to system prompts which need approriate value substitution. |
| mouse | The term mouse is used to refer to any pointing device such as a mouse, a puck or a stylus. |
| MB1, MB2, MB3 | MB1 indicates the left mouse button, MB2 indicates the middle mouse button, and MB3 indicates the right mouse button. (The buttons can be redefined by the user.) |
Unless otherwise noted, all numeric values are represented in decimal notation.
This chapter provides an overview to the installation concepts for
SysWorks V3.5.
1.1 Licenses
SysWorks is provided as a set of complimentary products. These are:
This runtime product provides a comprehensive runtime library and
supports the various SysWorks extensions to DECwindows. All other
SysWorks products use the SysWorks Base product.
1.1.2 SysWorks Administrator
This product is designed to assist system and network administrators and managers perform their OpenVMS activities. See the SysWorks Administrator Software Product Description (SPD) for more details.
When installed at the turnkey level, this product is designed to
provide a turnkey OpenVMS system base. It provides a model from which
users, developers, and system and network administrators and managers
may perform their activities with minimal direct OpenVMS interaction.
See the SysWorks Administrator Software Product Description (SPD) for
more details.
1.1.3 SysWorks Database Tools
1.1.4 SysWorks Developer
This product is designed to assist in the development of well built
applications. It provides a set of tools and enhancements to Digital
products which help achieve this aim. See the SysWorks Developer
Software Product Description (SPD) for more details. If the SysWorks
Administrator product is not also installed, site specific procedures
are required to bind developers to SysWorks Developer.
1.1.5 SysWorks Documentation
1.1.6 SysWorks Example Application
1.1.7 SysWorks Public Domain Utilities
1.2 Installation Level
SysWorks supports three installation levels. These are:
The SysWorks software is installed in the system common area. The
SWRK_STARTUP.COM procedure is placed in the SYS$STARTUP area, and
should be invoked in the system startup procedures. System wide
logicals are defined, and images are installed as shareable. The only
image installed with privileges is the SWRK_LNT_INTERFACE.EXE image so
that user logical name tables may be created when required at login
time. Each developer still needs to execute the SysWorks SYLOGIN.COM
procedure in their LOGIN.COM procedures. A site login or startup
procedure is also required to supply logical names such as disk roots
which would be supplied by SysWorks if it was installed as a higher
level.
1.2.2 System
The SysWorks software is installed as for the public level.
Additionally, a privileged VMS username is registered to act as a
network server. The SWRK_STARTUP.COM procedure installs more images
with privileges in order to assist the network server. This is the
minimum installation level at which the SysWorks Administrator license
will function. Each user still needs to execute the SysWorks
SYLOGIN.COM in their LOGIN.COM procedure. Alternatively, the system
wide SYLOGIN.COM procedure in the SYS$MANAGER area may invoke the
SysWorks procedure.
1.2.3 Turnkey
The SysWorks software is installed as for the system level.
Additionally the various system startup procedures in the SYS$MANAGER
area such as SYCONFIG.COM, SYLOGIN.COM etc are replaced. This is the
minimum installation level required for the SysWorks Turnkey license.
Esentially SysWorks Turnkey will take over management of the OpenVMS
system.
1.3 Installation Mode
There are two installation modes available with SysWorks Administrator and SysWorks Turnkey. These are local and network. This guide only discusses a local installation, since network installations are automated by SysWorks cluster management functions.
This chapter discusses resources that need to be checked and actions
that need to be taken prior to commencing a SysWorks installation.
2.1 Prerequisites
SysWorks V3.5 requires OpenVMS Alpha or VAX, V7.2 and will not install on a lower version of OpenVMS. The installation requires that DECnet is running.
If SysWorks Administrator or SysWorks Turnkey are being installed, the computer node on which the installation is being performed must be either a standalone computer node or the only computer node in a cluster i.e. all other computer nodes in the cluster must be shutdown. If the computer node is a member of a cluster, the DECnet cluster alias name for the computer nodes executor must be set to the cluster alias name, otherwise SysWorks will consider the computer node to be a standalone computer node. This can be checked with the command:
$ MCR NCP SHOW EXECUTOR |
At this time SysWorks does not use the Digital License Management
Facility. When installing the products, the license type needs to be
nominated.
2.3 Disk Space
SysWorks needs approximately 30,000 blocks on the target during and
after installation. If the SysWorks Administrator or Turnkey products
are being installed and network installations are required in the
future, a further 30,000 blocks are required to store the installation
save sets. If the installation level is system or above, this space
must be on the system disk.
2.4 Identifiers
The installation always creates or uses an R_SWRK_PROD identifier as
the owner of the created directories and files. If the installation
level is turnkey, an R_SWRK_HISTORY identifier is created or used to
own the system history files.
2.5 Directories
The installation creates a root directories on the nominated installation disk. This is named [PROD_2].
If the installation level is public and the target disk chosen is not the system disk, the [SWRK] directory is created in this root directory.
If the installation level is public and the target disk is the system disk or the installation level is system or turnkey, the [PROD_2] directory is created in the root of the system disk and the [SWRK] directory in the SYS$COMMON area. The [SWRK] directory isthen entered as an alias into the [PROD_2] directory so that the directory [PROD_2.SWRK] is valid. Various directories are then created in the [SWRK] root directory.
If the installation level is system or turnkey, a [SWRKSRVR] directory
is created in the SYS$SPECIFIC area to act as a default directory for
the network server OpenVMS username. When other computer nodes are
defined in SysWorks Administrator, this directory is created in their
SYS$SPECIFIC areas.
2.6 Building a New System Disk
This section describes the steps required to sucessfully build a new system disk with SysWorks products installed. The steps indicated will work for a turnkey installation.
The steps required are:
This chapter decsribes the installation procedure in detail. An assumprion is made that the installer has basic familiarity with the VMSINSTAL utility.
The steps are as follows:
$ @SYS$UPDATE:VMSINSTAL SWRK035 save-set-location [OPTIONS ...] |
SWRK035 |
* Enter your SysWorks license type: |
* Enter your SysWorks installation level: |
* Enter your target device name [SYS$SYSDEVICE:]: |
* Enter your site code: |
* Enter your site heading: |
* Enter your default printer: |
* Utility logicals scope: |
| Next | Contents |