VMS 7.1 Installation
This section shows how the original VMS 7.1 was installed on SIMH running on an iBook G3 laptop. I was never able toget the VAX network adapter to work on this G3 laptop but had better success when SIMH was moved and a new VAX executable was created on the PowerBook G4.
Cluster ConfigurationThe first step is to log into the SIMH39 directory and sart up the emulator. In this configuration DUA0 is an RA90
disk drive which will receive the VMS installation. The DUA1 device is an RRD40 CD-ROM drive which contains the CD image of the VMS 7.1 instllation save set.
The goal is to boot from the CD-ROM VMS 7.1 save set and install VMS on DUA0 disk.
These disks are configured as follows in the VAX.ini file:
- DUA0 - vaxvmssys.iso - VMS boot disk.
- DUA1 - vaxvmscd.iso - standalone boot disk with product save sets.
| Part 1: Start the emulator |
|---|
Last login: Wed Dec 31 19:00:47 on console Welcome to Darwin! manuel-duartes-ibook:~ manuelduarte$ ls Desktop Pictures simh.ini Documents Public simh.ini.rtf Library SIMH simh39 Movies Send Registration Music Sites manuel-duartes-ibook:~ manuelduarte$ cd sim39h -bash: cd: sim39h: No such file or directory manuel-duartes-ibook:~ manuelduarte$ cd simh39 manuel-duartes-ibook:~/simh39 manuelduarte$ ls 0readme_39.txt PDP10 sim_ether.c 0readme_ethernet.txt PDP11 sim_ether.h ALTAIR PDP18B sim_fio.c AltairZ80 PDP8 sim_fio.h BIN S3 sim_rev.h GRI SDS sim_sock.c H316 VAX sim_sock.h HP2100 build_mingw.bat sim_tape.c I1401 build_mingw_ether.bat sim_tape.h I1620 descrip.mms sim_timer.c I7094 makefile sim_timer.h Ibm1130 scp.c sim_tmxr.c Interdata scp.h sim_tmxr.h LGP sim_console.c swtp6800 NOVA sim_console.h PDP1 sim_defs.h manuel-duartes-ibook:~/simh39 manuelduarte$ cd bin manuel-duartes-ibook:~/simh39/bin manuelduarte$ ls VAX.ini nvram.bin vaxvmscd.iso ka655x.bin vax vaxvmssys.iso manuel-duartes-ibook:~/simh39/bin manuelduarte$ sudo ./vax Password: VAX simulator V3.9-0 NVR: buffering file in memory Listening on port 12000 (socket 7) KA655-B V5.3, VMB 2.7 Performing normal system tests. 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25.. 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09.. 08..07..06..05..04..03.. Tests completed. >>>sho dev UQSSP Disk Controller 0 (772150) -DUA0 (RA90) -DUA1 (RRD40) -DUA2 (RD54) -DUA3 (RX50) UQSSP Tape Controller 0 (774500) -MUA0 (TK50) -MUA1 (TK50) -MUA2 (TK50) -MUA3 (TK50) RLV12 Controller 0 (774400) -DLA0 (RL01) -DLA1 (RL01) -DLA2 (RL01) -DLA3 (RL01) Ethernet Adapter 0 (774440) -XQA0 (08-00-2B-C0-A7-78) >>>b dua1: |
The second part is to boot off the standalone backup on DUA1 that contains the VMS image so that it can be unpacked to DUA0.
| Part 2: Install the VMS save set on DUA0: |
|---|
-DUA1 1..0.. %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk %SYSBOOT-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk OpenVMS (TM) VAX Version X6NO Major version id = 1 Minor version id = 0 PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 17-JUN-2013 11:11 Configuring devices . . . Now configuring HSC, RF, and MSCP-served devices . . . Please check the names of the devices which have been configured, to make sure that ALL remote devices which you intend to use have been configured. If any device does not show up, please take action now to make it available. Available device DUA0: device type RA90 Available device DUA1: device type RRD40 Available device DUA2: device type RD54 Available device DUA3: device type RX50 Available device DLA0: device type RL01 Available device DLA1: device type RL01 Available device DLA2: device type RL01 Available device DLA3: device type RL01 Available device MSA0: device type MW_TSV05 Available device DYA0: device type RX02 Available device DYA1: device type RX02 Available device MUA0: device type TK50 Available device MUA1: device type TK50 Available device MUA2: device type TK50 Available device MUA3: device type TK50 Enter "YES" when all needed devices are available: Enter "YES" when all needed devices are available: yes %BACKUP-I-IDENT, Stand-alone BACKUP V7.1; the date is 17-JUN-2013 11:13:23.03 $ backup/image/verify dua1:vms071.b/save_set dua0: %BACKUP-I-STARTVERIFY, starting verification pass %BACKUP-I-PROCDONE, operation completed. Processing finished at 17-JUN-2013 11:15:14.98 If you do want to perform another standalone BACKUP operation, ensure the standalone application volume is online and ready. Enter "YES" to continue: If you do not want to perform another standalone BACKUP operation, use the console to halt the system. Simulation stopped, PC: 839ECB47 (BBC #3,26C(R3),839ECB9B) Note: CTRL-E to stop SIMH sim> quit Goodbye NVR: writing buffer to file |
Re-start the emulator and boot from DUA0 which now contains the VMS installation.
| Part 3: Install and configure VMS |
|---|
manuel-duartes-ibook:~/simh39/bin manuelduarte$ sudo ./vax
Password:
VAX simulator V3.9-0
NVR: buffering file in memory
Listening on port 12000 (socket 7)
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>b dua0:
(BOOT/R5:0 DUA0
2..
-DUA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version BI71-6NO Major version id = 1 Minor version id = 0
OpenVMS VAX V7.1 Installation Procedure
Model: VAXserver 3900 Series
System device: RA90 - _DUA0:
Free Blocks: 2312772
CPU type: 10-01
* Please enter the date and time (DD-MMM-YYYY HH:MM) 17-JUN-2013 23:16
*********************************************************
%SYSTEM-W-TZGMT, your local timezone has defaulted to GMT
%SYSTEM-I-SETTZ, to set your local timezone use:
$ @SYS$MANAGER:UTC$TIME_SETUP.COM
*********************************************************
On MIN or UPGRADE system startup - CLUE is not run.
%%%%%%%%%%% OPCOM 17-JUN-2013 23:16:12.25 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 17-JUN-2013 23:16:12.27 %%%%%%%%%%%
Operator status for operator _OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 17-JUN-2013 23:16:12.46 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 17-JUN-2013 23:16:12.47 %%%%%%%%%%%
Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%SYSTEM-I-BOOTUPGRADE, security auditing disabled
%%%%%%%%%%% OPCOM 17-JUN-2013 23:16:16.23 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 17-JUN-2013 23:16:16.25 %%%%%%%%%%%
Message from user JOB_CONTROL
-RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%SYSTEM-I-BOOTUPGRADE, security server not started
%%%%%%%%%%% OPCOM 17-JUN-2013 23:16:24.04 %%%%%%%%%%%
Message from user SYSTEM
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
If this system disk is to be used in a cluster with multiple system
disks, then each system disk must have a unique volume label. Any
nodes having system disks with duplicate volume labels will fail to
boot into the cluster.
You can indicate a volume label of 1 to 12 characters in length. If you
want to use the default name of OpenVMS071, press RETURN in response
to the next question.
* Enter the volume label for this system disk [OpenVMS071]:
* Enter name of drive holding the OpenVMS distribution media: DUA1:
* Is the OpenVMS media ready to be mounted? [N] y\y\
* Is the OpenVMS media ready to be mounted? [N] n
* Is the OpenVMS media ready to be mounted? [N] y
%MOUNT-I-MOUNTED, VAXVMS071 mounted on _DUA1:
Select optional software you want to install. You can install one
or more of the following OpenVMS or DECwindows components:
o OpenVMS library - 52200 blocks
o OpenVMS optional - 19000 blocks
o OpenVMS Help Message - 10400 blocks
o OpenVMS Management Station - 20000 blocks
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts - 6200 blocks
o DECnet-Plus networking - 80000 blocks
Space remaining on system disk: 2312592 blocks
* Do you want to install the OpenVMS library files? (Y/N) y
Space remaining on system disk: 2260392 blocks
* Do you want to install the OpenVMS optional files? (Y/N) y
Space remaining on system disk: 2241392 blocks
The Help Message utility (MSGHLP) provides online explanations
and user actions for OpenVMS messages in place of the hardcopy
OpenVMS System Messages and Recovery Procedures Reference Manual,
which is now separately orderable.
The MSGHLP database file, MSGHLP$LIBRARY.MSGHLP$DATA,
consumes approximately 10400 blocks and will be
placed by default on your system disk in SYS$COMMON:[SYSHLP]
unless you specify an alternate device when prompted.
* Do you want to install the MSGHLP database? (Y/N) y
You can install this database on your system disk in SYS$COMMON:[SYSHLP]
or on an alternate device. If you specify an alternate device, but no
directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When
prompted, take the default of the system disk or specify an alternate
device using this format:
device:[directory]
* Where do you want to install the MSGHLP database?[SYS$COMMON:[SYSHLP]]
Space remaining on system disk: 2230992 blocks
The OpenVMS Management Station is a client-server application
that provides OpenVMS system management capabilities through a
client application on a personal computer (PC) running Microsoft
Windows. The server application runs on OpenVMS systems and is
automatically installed as part of the OpenVMS operating system.
This option provides the files used to create the installation media
for the PC client software. If you want to use the OpenVMS Management
Station, you must install these files on at least one OpenVMS system to
create the installation media, which can then be used to install the
PC client on one or more PCs.
Note: To use the OpenVMS Management Station on your PC, you must be
running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1)
software.
The OpenVMS Management Station optional files consume approximately 20000
blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].
* Do you want to install the optional OpenVMS Management Station files? (Y/N) y
Space remaining on system disk: 2210992 blocks
You can select DECwindows now, or you can use the DECW$TAILOR utility
to provide or remove DECwindows support after the installation.
Some media, TK50s in particular, can be very slow when tailoring on files.
You might want to select DECwindows now and tailor off unwanted files later.
NOTE: This kit does NOT contain full DECwindows.
To obtain full DECwindows, you must also install the separate
layered product, DECwindows Motif for OpenVMS VAX.
V1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX
that can be used with OpenVMS VAX V7.1.
The DECwindows components provided in this kit requires approximately
34400 blocks, broken down as follows:
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts (optional) - 6200 blocks
You must select the DECwindows base support option if
- you plan to run DECwindows software, or
- you are installing this kit on
* a workstation or
* a VAXcluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows base support, then you will have to use
the DECW$TAILOR utility to provide font files.
* Do you want the DECwindows base support? (Y/N) y
Space remaining: 2206592 blocks
You must select the DECwindows workstation support option if
- you are installing this kit on
* a workstation or
* a VAXcluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows workstation support, then you will have
to use the DECW$TAILOR utility to provide font files.
* Do you want to install DECwindows workstation support? (Y/N) y
Space remaining: 2182792 blocks
DECwindows workstation support includes the 75 dots per inch video fonts.
All DECwindows applications run with 75 dots per inch video fonts.
By default, most systems startup with 75 dots per inch video fonts.
Certain applications can take advantage of 100 dots per inch video fonts.
For the VAXstation 4000 series machines, 100 dots per inch video fonts
are used by default. If you decide not to install 100 dots per inch
video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
to force 75 dots per inch video fonts to be the default. Otherwise,
certain applications may not space text properly.
For instructions on how to configure your system with both 75 and 100
dots per inch video fonts, see the installation guide or look at the
template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE.
* Do you want 100 dots per inch video fonts installed? (Y/N) y
Space remaining: 2176592 blocks
Beginning with OpenVMS V7.1 DECnet-Plus is provided with the
OpenVMS operating system. Digital strongly recommends that DECnet
users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is available for separate installation. Please see the
"OpenVMS V7.1 Release Notes" for important information regarding
DECnet Phase IV support.
If you plan to install DECnet Phase IV do NOT select DECnet-Plus.
* Do you want to install DECnet-Plus? (Y/N) y
Space remaining on system disk: 2096592 blocks
The following options will be provided:
OpenVMS library
OpenVMS optional
OpenVMS Help Message
OpenVMS Management Station Software -- PC files
DECwindows base support
DECwindows workstation support with:
- 75 dots per inch video fonts
- 100 dots per inch video fonts
DECnet-Plus
Space remaining on system disk: 2096592 blocks
* Is this correct? (Y/N) y
Restoring OpenVMS library save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS optional save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS Help Message save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS Management Station Software -- PC files
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows base support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows workstation support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 75 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 100 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
You can now remove the distribution kit from DUA1:.
Creating [VMS$COMMON] directory tree ...
In a cluster, you can run multiple systems sharing all files except
PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR.
Cluster configuration cannot be done at this time because no network
is present. In order to configure a cluster you must FIRST do one
or both of the following:
o Install DECnet-Plus (or DECnet Phase IV), or
o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the
comment delimiter ("!") from the line
$! @SYS$STARTUP:LAN$STARTUP
in SYS$MANAGER:SYSTARTUP_VMS.COM.
Then configure the cluster by executing the following command:
@ @SYS$MANAGER:CLUSTER_CONFIG
See the OpenVMS System Manager's Manual: Essentials for more information.
* Do you want DECwindows Motif as the default windowing system? (Y/N) y
Now we will ask you for new passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
Passwords must be a minimum of 8 characters in length. All passwords
will be checked and verified. Any passwords that can be guessed easily
will not be accepted.
* Enter password for SYSTEM:
Password must be at least 8 characters in length.
* Enter password for SYSTEM:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified
* Enter password for SYSTEST:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEST verified
The SYSTEST_CLIG account will be disabled. You must re-enable
it before running UETP but do not assign a password.
%UAF-I-PWDLESSMIN, new password is shorter than minimum password length
%UAF-I-MDFYMSG, user record(s) updated
* Enter password for FIELD:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for FIELD verified
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors.
%UAF-I-RDBCREMSG, rights database created
%UAF-I-RDBADDMSGU, identifier DEFAULT value [000200,000200] added to rights database
%UAF-I-RDBADDMSGU, identifier FIELD value [000001,000010] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEM value [000001,000004] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEST value [000001,000007] added to rights database
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value [000001,000007] to rights database
-SYSTEM-F-DUPIDENT, duplicate identifier
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-RDBDONEMSG, rights database modified
Creating MODPARAMS.DAT database file, SYS$SYSTEM:MODPARAMS.DAT
* Please enter the SCSNODE name: apple\elppa\apple
* Please enter the SCSSYSTEMID: help
HELP is not a legal SCSSYSTEMID
Legal range is 1025 - 65535
* Please enter the SCSSYSTEMID: 1055
After the installation finishes, you might want to do one or more of the
following tasks:
o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system
libraries are shipped in a data-compressed format. If you have
enough disk space, you can decompress the libraries for faster access.
To data expand the libraries, type:
$ @SYS$UPDATE:LIBDECOMP.COM
If you do not decompress these libraries, you will experience slower
response to the HELP and LINK commands.
o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
using the procedure described in the upgrade and installation supplement"
supplied for your VAX computer.
o TAILOR THE SYSTEM DISK - You might want to review the files provided or
not provided during this installation. If you find there are files
you want to remove from the system disk (TAILOR OFF) or files you want
to add (TAILOR ON), use the following utilities to perform the
desired tailoring.
OpenVMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR
DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR
NOTE: The tailor procedure cannot be used to TAILOR ON or TAILOR OFF
files located on an alternate disk.
=================================================================
Continuing with OpenVMS VAX V7.1 Installation Procedure.
Configuring all devices on the system ...
If you have Product Authorization Keys (PAKs) to register, you can
register them now.
* Do you want to register any Product Authorization Keys? (Y/N): y
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:1
Do you have your Product Authorization Key? [YES]:
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to the main menu.
Issuer [DEC]:
Authorization Number [XXXXXXXXXXXXXX]
Product Name [VAX-VMS]:
Producer [DEC]:
Number of Units [1600]:
Version []:
Product Release Date []:
Key Termination Date []:
Availability Table Code []:
Activity Table Code [C]:
Key Options [NO_SHARE]:
Include Node []:
Product Token []:
Hardware-Id []:
Checksum [XXXXXXXXXXXX]:
Here is a list of the license information just entered:
Issuer: DEC
Authorization: XXXXXXXXXXX
Product Name: VAX-VMS
Producer: DEC
Units: 1600
Release Date:
Version:
Termination Date:
Availability:
Activity: C
Options: NO_SHARE
Token:
Hardware ID:
Checksum: XXXXXXXXXXXX
Is that correct? [YES]:
Registering VAX-VMS license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:
%LICENSE-I-LOADED, DEC VAX-VMS was successfully loaded with 1600 units
Press RETURN to return to the main menu
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:
Do you have your Product Authorization Key? [YES]:
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to the main menu.
Issuer [DEC]:
Authorization Number []:XXXXXXXXXXXX
Product Name []:vaxcluster
Producer [DEC]:
Number of Units []:230
Version []:
Product Release Date []:
Key Termination Date []:
Availability Table Code []:e
Activity Table Code []:
Key Options []:mod_units
Product Token []:
Hardware-Id []:
Checksum []:XXXXXXXXXXXX
Here is a list of the license information just entered:
Issuer: DEC
Authorization: XXXXXXXXXXXX
Product Name: VAXCLUSTER
Producer: DEC
Units: 230
Release Date:
Version:
Termination Date:
Availability: E
Activity:
Options: MOD_UNITS
Token:
Hardware ID:
Checksum: XXXXXXXXXXXX
Is that correct? [YES]:
Registering VAXCLUSTER license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:
%LICENSE-I-LOADED, DEC VAXCLUSTER was successfully loaded with 230 units
Press RETURN to return to the main menu
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:
Do you have your Product Authorization Key? [YES]:
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to the main menu.
Issuer [DEC]:
Authorization Number []:XXXXXXXXXXXX
Product Name []:dvnetend
Producer [DEC]:
Number of Units []:230
Version []:
Product Release Date []:
Key Termination Date []:
Availability Table Code []:E
Activity Table Code []:
Key Options []:mod_units
Product Token []:
Hardware-Id []:
Checksum []:XXXXXXXXXXXX
Here is a list of the license information just entered:
Issuer: DEC
Authorization: XXXXXXXXXXXX
Product Name: DVNETEND
Producer: DEC
Units: 230
Release Date:
Version:
Termination Date:
Availability: E
Activity:
Options: MOD_UNITS
Token:
Hardware ID:
Checksum: XXXXXXXXXXXX
Is that correct? [YES]:
Registering DVNETEND license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:
%LICENSE-I-LOADED, DEC DVNETEND was successfully loaded with 230 units
Press RETURN to return to the main menu
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:
Do you have your Product Authorization Key? [YES]:
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to the main menu.
Issuer [DEC]:
Authorization Number []:XXXXXXXXXXXX
Product Name []:net-app-sup-250
Producer [DEC]:
Number of Units []:10
Version []:
Product Release Date []:
Key Termination Date []:
Availability Table Code []:f
Activity Table Code []:
Key Options []:mod_units
Product Token []:
Hardware-Id []:
Checksum []:XXXXXXXXXXXX
Here is a list of the license information just entered:
Issuer: DEC
Authorization: XXXXXXXXXXXX
Product Name: NET-APP-SUP-250
Producer: DEC
Units: 10
Release Date:
Version:
Termination Date:
Availability: F
Activity:
Options: MOD_UNITS
Token:
Hardware ID:
Checksum: XXXXXXXXXXXX
Is that correct? [YES]:
Registering NET-APP-SUP-250 license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:
%LICENSE-I-LOADED, DEC NET-APP-SUP-250 was successfully loaded with 10 units
Press RETURN to return to the main menu
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:
Do you have your Product Authorization Key? [YES]:
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to the main menu.
Issuer [DEC]:
Authorization Number []:XXXXXXXXXXXX
Product Name []:c
Producer [DEC]:
Number of Units []:20
Version []:
Product Release Date []:
Key Termination Date []:
Availability Table Code []:f
Activity Table Code []:
Key Options []:mod_units
Product Token []:
Hardware-Id []:
Checksum []:XXXXXXXXXXXX
Here is a list of the license information just entered:
Issuer: DEC
Authorization: XXXXXXXXXXXX
Product Name: C
Producer: DEC
Units: 20
Release Date:
Version:
Termination Date:
Availability: F
Activity:
Options: MOD_UNITS
Token:
Hardware ID:
Checksum: XXXXXXXXXXXX
Is that correct? [YES]:
Registering C license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:
%LICENSE-I-LOADED, DEC C was successfully loaded with 20 units
Press RETURN to return to the main menu
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:
Do you have your Product Authorization Key? [YES]:
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to the main menu.
Issuer [DEC]:
Authorization Number []:XXXXXXXXXXXX
Product Name []:fortran
Producer [DEC]:
Number of Units []:20
Version []:
Product Release Date []:
Key Termination Date []:
Availability Table Code []:f
Activity Table Code []:
Key Options []:mod_units
Product Token []:
Hardware-Id []:
Checksum []:XXXXXXXXXXXX
Here is a list of the license information just entered:
Issuer: DEC
Authorization: XXXXXXXXXXXX
Product Name: FORTRAN
Producer: DEC
Units: 20
Release Date:
Version:
Termination Date:
Availability: F
Activity:
Options: MOD_UNITS
Token:
Hardware ID:
Checksum: XXXXXXXXXXXX
Is that correct? [YES]:
Registering FORTRAN license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:
%LICENSE-I-LOADED, DEC FORTRAN was successfully loaded with 20 units
Press RETURN to return to the main menu
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:
Do you have your Product Authorization Key? [YES]:
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to the main menu.
Issuer [DEC]:
Authorization Number []:XXXXXXXXXXXX
Product Name []:cdd-plus
Producer [DEC]:
Number of Units []:400
Version []:
Product Release Date []:
Key Termination Date []:
Availability Table Code []:f
Activity Table Code []:
Key Options []:mod_units
Product Token []:
Hardware-Id []:
Checksum []:XXXXXXXXXXXX
Here is a list of the license information just entered:
Issuer: DEC
Authorization: XXXXXXXXXXXX
Product Name: CDD-PLUS
Producer: DEC
Units: 400
Release Date:
Version:
Termination Date:
Availability: F
Activity:
Options: MOD_UNITS
Token:
Hardware ID:
Checksum: XXXXXXXXXXXX
Is that correct? [YES]:
Registering CDD-PLUS license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:
%LICENSE-I-LOADED, DEC CDD-PLUS was successfully loaded with 400 units
Press RETURN to return to the main menu
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to return to this menu.
Enter one of the above choices [1]:99
********************************************************************************
After the system has rebooted you should register any additional
Product Authorization Keys (PAKs) you have, or receive in the
future, by executing the following procedure:
$ @SYS$UPDATE:VMSLICENSE
See the OpenVMS License Management Utility Manual for any additional
information you need.
********************************************************************************
Now registering the OpenVMS operating system in the
POLYCENTER Software Installation product database
The following product will be registered:
DEC VAXVMS VMS V7.1 Transition (registration)
The following product has been registered:
DEC VAXVMS VMS V7.1 Transition (registration)
%UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE]
Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- Main Time Zone Menu
1) Australia 11) GMT 21) Mexico 31) Turkey
2) Brazil 12) Greenwich 22) NZ 32) UCT
3) CET 13) Hong Kong 23) NZ-CHAT 33) US
4) Canada 14) Iceland 24) Navajo 34) UTC
5) Chile 15) Iran 25) PRC 35) Universal
6) Cuba 16) Israel 26) Poland 36) W-SU
7) EET 17) Jamaica 27) ROC 37) WET
8) Egypt 18) Japan 28) ROK 38) Zulu
9) Factory 19) Libya 29) Singapore
10) GB-Eire 20) MET 30) SystemV
0) None of the above
Select the number above that best describes your location: 4
You selected Canada as your time zone.
Is this correct? (Yes/No) [YES]:
Canada Time Zone Menu
1) Atlantic 3) East-Saskatchewan 5) Mountain 7) Pacific
2) Central 4) Eastern 6) Newfoundland 8) Yukon
0) None of the above
Select the number above that best describes your location: 1\1\4
You selected Canada/Eastern as your time zone.
Is this correct? (Yes/No) [YES]:
Default Time Differential Factor for standard time is -5:00.
Default Time Differential Factor for daylight saving time is -4:00.
The Time Differential Factor (TDF) is the difference between your
system time and Coordinated Universal Time (UTC). UTC is similar
in most repects to Greenwich Mean Time (GMT).
The TDF is expressed as hours and minutes, and should be entered
in the hh:mm format. TDFs for the Americas will be negative
(-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
will be positive (1:00, 2:00, etc.).
Is Daylight Savings time in effect? (Yes/No): y
Enter the Time Differential Factor [-4:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00.
Is this correct? [Y]:
DECnet-Plus will now be installed.
Media containing the DECnet-Plus kit must be available.
If you are installing OpenVMS from an Infoserver (DAD1)
or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM.
If you are installing from a cartridge tape (TK50) or
from an open reel tape, you should have a DECnet-Plus kit
on cartidge tape or open reel tape.
An appropriate DECnet-Plus kit may also be available on
the Consolidated Distribution CD-ROM, or you may have a
separate DECnet-Plus kit.
NOTE: You may choose any available media for the
DECnet-Plus kit. It is NOT NECESSARY to use the same
type of media that contained the OpenVMS kit.
If you do not have a DECnet-Plus kit available, or if you
have decided NOT to install/upgrade DECnet-Plus, you can
bypass the DECnet-Plus installation by entering "EXIT"
for the "name of drive holding the DECnet-Plus kit".
* Enter name of drive holding the DECnet-Plus kit: dua1:
* Is DUA1: ready to be mounted? [N] y
The following product has been selected:
DEC VAXVMS DECNET_OSI V7.1 Layered Product
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX
Copyright ? Digital Equipment Corporation 1994. All rights reserved.
Digital Equipment Corporation
This product requires one of two PAKs: DVNETEND or DVNETRTG.
Do you want the defaults for all options? [YES]
Do you want to review the options? [NO]
Execution phase starting ...
The following product will be installed:
DEC VAXVMS DECNET_OSI V7.1 Layered Product
Portion done: 0%...10%...20%...30%...40%...80%...90%...100%
The following product has been installed:
DEC VAXVMS DECNET_OSI V7.1 Layered Product
********************************************************************************
Running AUTOGEN to compute the new SYSTEM parameters ...
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, SYS$SPECIFIC:[SYSEXE]SYSDUMP.DMP;1 created
%SYSGEN-I-CREATED, DUA0:[SYS0.SYSEXE]ERRORLOG.DMP;1 created
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
installation will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;
-RMS-E-FNF, file not found
SHUTDOWN message from user SYSTEM at Batch 03:19:54
The system will shut down in 0 minutes; back up SOON. Please log off.
Reboot system with AUTOGENerated parameters
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
?06 HLT INST
PC = 8443BD09
Loading system software.
No default boot device has been specified.
Available devices.
-DUA0 (RA90)
-DUA1 (RRD40)
-DUA2 (RD54)
-DUA3 (RX50)
-MUA0 (TK50)
-MUA1 (TK50)
-MUA2 (TK50)
-MUA3 (TK50)
-DLA0 (RL01)
-DLA1 (RL01)
-DLA2 (RL01)
-DLA3 (RL01)
-XQA0 (08-00-2B-C0-A7-78)
Device? [XQA0]: dua0
(BOOT/R5:0 DUA0
2..
-DUA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
OpenVMS (TM) VAX Version V7.1 Major version id = 1 Minor version id = 0
%DECnet-I-LOADED, network base image loaded, version = 05.0C.00
%DECnet-W-NOOPEN, could not open SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
*****************************************************************
OpenVMS VAX V7.1
You have SUCCESSFULLY installed the OpenVMS VAX Operating System.
The system is now executing the STARTUP procedure. Please
wait for the completion of STARTUP before logging in to the
system.
*****************************************************************
%STDRV-I-STARTUP, OpenVMS startup begun at 18-JUN-2013 22:06:10.77
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:02.71 %%%%%%%%%%%
Operator _APPLE$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:02.86 %%%%%%%%%%%
Operator status for operator _APPLE$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:03.73 %%%%%%%%%%%
Logfile has been initialized by operator _APPLE$OPA0:
Logfile is APPLE::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:03.93 %%%%%%%%%%%
Operator status for operator APPLE::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:13.29 %%%%%%%%%%%
Message from user AUDIT$SERVER on APPLE
%AUDSRV-I-NEWSERVERDB, new audit server database created
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:16.12 %%%%%%%%%%%
Message from user AUDIT$SERVER on APPLE
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:16.43 %%%%%%%%%%%
Message from user AUDIT$SERVER on APPLE
%AUDSRV-I-NEWOBJECTDB, new object database created
%SET-I-NEWAUDSRV, identification of new audit server process is 0000020A
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:22.59 %%%%%%%%%%%
Message from user JOB_CONTROL on APPLE
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:22.70 %%%%%%%%%%%
Message from user JOB_CONTROL on APPLE
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:36.46 %%%%%%%%%%%
Message from user SYSTEM on APPLE
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:37.84 %%%%%%%%%%%
Message from user SYSTEM on APPLE
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:37.89 %%%%%%%%%%%
Message from user SYSTEM on APPLE
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 18-JUN-2013 22:08:37.92 %%%%%%%%%%%
Message from user SYSTEM on APPLE
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up
Copyright (c) Digital Equipment Corporation 1996. All rights reserved.
%NET$STARTUP-W-NONETCONFIG, this node has not been configured to run DECnet-Plus for OpenVMS
use SYS$MANAGER:NET$CONFIGURE.COM if you wish to configure DECnet
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is OFF
%%%%%%%%%%% OPCOM 18-JUN-2013 22:09:17.52 %%%%%%%%%%%
Message from user SYSTEM on APPLE
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
%DECdtm-F-NODECnet, the TP_SERVER process was not started because either:
o DECnet-Plus is not started or is not configured, or
o The SYS$NODE_FULLNAME logical name is not defined
This could be because when you installed DECnet-Plus and were prompted
for the system's full name, you specified a local name instead of a
DECdns or Domain name.
If you want to use DECdtm services, make sure that DECnet-Plus is started and
configured and that SYS$NODE_FULLNAME is defined, then use the following
command to start the TP_SERVER process:
$ @SYS$STARTUP:DECDTM$STARTUP.COM
%%%%%%%%%%% OPCOM 18-JUN-2013 22:09:27.93 %%%%%%%%%%%
Message from user AUDIT$SERVER on APPLE
Security alarm (SECURITY) and security audit (SECURITY) on APPLE, system id: 1055
Auditable event: Audit server starting up
Event time: 18-JUN-2013 22:09:27.28
PID: 00000203
Username: SYSTEM
%UAF-I-RDBADDMSG, identifier SYS$NODE_APPLE value %X80010000 added to rights database
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 18-JUN-2013 22:09:46.17
Accounting information:
Buffered I/O count: 1393 Peak working set size: 1015
Direct I/O count: 596 Peak page file size: 5069
Page faults: 5692 Mounted volumes: 0
Charged CPU time: 0 00:03:24.18 Elapsed time: 0 00:03:59.24
|