Configuration de OpenVMS VAX sous l’émulateur simh – partie 2/2

Configuration de OpenVMS VAX sous l’émulateur simh – partie 2/2.

1) Lancement du l’émulateur :


pi@raspberrypi ~ $ cd /usr/local/vax/bin
pi@raspberrypi /usr/local/vax/bin $ sudo ./vax

VAX simulator V3.9-0
NVR: creating new file
NVR: buffering file in memory
RQ: creating new file
RQ: creating new file
RQ: creating new file
RQ: unit is read only
Eth: opened OS device eth0

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.
>>>

2) Boot sur le lecteur de cd-rom :


>>>boot dua3
(BOOT/R5:0 DUA3

2..
-DUA3
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 X7G7 Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 06-OCT-2013 14:08

Configuring 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 RA92
Available device DUA1: device type RA92
Available device DUA2: device type RA92
Available device DUA3: device type RRD40
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: y
%BACKUP-I-IDENT, Stand-alone BACKUP T7.2; the date is 6-OCT-2013 14:10:56.12
$

3) Sauvegarde :


$ backup dua3:vms073.b/save_set dua0:
If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.

If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue: [Ctrl]+[e]
Simulation stopped, PC: 839ABF8D (BBC #3,26C(R3),839ABFE1)
sim>

4) Boot sur le cpu :


sim> boot cpu

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.
>>>

5) Boot sur le premier disque :


(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 BI73-7G7 Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.

OpenVMS VAX V7.3 Installation Procedure

Model: VAXserver 3900 Series
System device: RA92 - _DUA0:
Free Blocks: 2854566
CPU type: 10-01

* Please enter the date and time (DD-MMM-YYYY HH:MM) 06-OCT-2013 14:18
*********************************************************
%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 6-OCT-2013 14:18:17.86 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM

%%%%%%%%%%% OPCOM 6-OCT-2013 14:18:17.88 %%%%%%%%%%%
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 6-OCT-2013 14:18:18.08 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%% OPCOM 6-OCT-2013 14:18:18.10 %%%%%%%%%%%
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 6-OCT-2013 14:18:23.23 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%% OPCOM 6-OCT-2013 14:18:23.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 6-OCT-2013 14:18:29.53 %%%%%%%%%%%
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...

%SET-I-INTSET, login interactive limit = 1, current interactive value = 0
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0

6) Configuration du disque de système :


If this system disk is to be used in an OpenVMS 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 OVMSVAXSYS, press RETURN in response
to the next question.

* Enter the volume label for this system disk [OVMSVAXSYS]: [Entrée]

* Enter name of drive holding the OpenVMS distribution media: DUA3
* Is the OpenVMS media ready to be mounted? [N] y
%MOUNT-I-MOUNTED, VAXVMS073 mounted on _DUA3:

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
o DECnet Phase IV networking - 800 blocks

Space remaining on system disk: 2854377 blocks

* Do you want to install the OpenVMS library files? (Y/N) y

Space remaining on system disk: 2802177 blocks

* Do you want to install the OpenVMS optional files? (Y/N) y

Space remaining on system disk: 2783177 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? [Entrée]
[SYS$COMMON:[SYSHLP]]

Space remaining on system disk: 2772777 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 install the PC client software.
If you want to use the OpenVMS Management Station, you must install
these optional files on at least one OpenVMS system and then use one or
both of them to install the PC client on one or more PCs. There are two
files: TNT030_I.EXE for Intel systems (Windows 95 and Windows NT), and
TNT030_A.EXE for Alpha Windows NT systems.

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: 2752777 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.3.

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
* an OpenVMS Cluster 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) n

Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. Compaq strongly recommends that
DECnet users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.

DECnet Phase IV is also provided as an option. Support for DECnet
Phase IV is available through a Prior Version Support Contract.

If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see the OpenVMS
Management Guide for information on running DECnet over TCI/IP.

If you plan to install DECnet Phase IV do NOT select DECnet-Plus.

* Do you want to install DECnet-Plus? (Y/N) n

* Do you want to install DECnet Phase IV? (Y/N) n

The following options will be provided:

OpenVMS library
OpenVMS optional
OpenVMS Help Message
OpenVMS Management Station Software -- PC files

Space remaining on system disk: 2752777 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

Now registering the OpenVMS operating system in the
POLYCENTER Software Installation product database

The following product will be registered:
DEC VAXVMS VMS V7.3 DISK$VAXVMSV73:[VMS$COMMON.]

The following product has been registered:
DEC VAXVMS VMS V7.3 Transition (registration)

You can now remove the distribution kit from DUA3:.

In an OpenVMS 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.

7) Initialiser les mots de passe :


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: mot2passe
* Re-enter for verification: mot2passe
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified

* Enter password for SYSTEST: mot2passe
* Re-enter for verification: mot2passe
%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: mot2passe
* Re-enter for verification: mot2passe
%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

8) Nommage du système :


* Please enter the SCSNODE name: PIVAX

* Please enter the SCSSYSTEMID: 1025

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 "Backup Procedures" chapter of
tye upgrade and installation supplement provided 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.

9) Configuration :


=================================================================
Continuing with OpenVMS VAX V7.3 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]: [Entrée]

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]:DEC
Authorization Number []:HOBBYIST-VA-KEY16668-166603
Product Name []:VAX-VMS
Producer [DEC]:DEC
Number of Units []:0
Version []:Entrée
Product Release Date []:3-NOV-2014
Key Termination Date []:3-NOV-2014
Availability Table Code []:Entrée
Activity Table Code []:a
Key Options []:NO_SHARE

This Product Authorization Key (PAK) has been provided with the
NO_SHARE option. If it is to be used by a node in a cluster, this
PAK must be restricted to a specific node.

If this PAK is to be used by a standalone system, answer NO to the
following question.

Is this PAK restricted to a cluster member node? [YES]: [Entrée]

Note: For the majority of systems, the SCS node name is the
same as the DECnet node name.

Node this PAK is restricted to (SCS Node name) []: [Entrée]
Product Token []: [Entrée]
Hardware-Id []:NONE
Checksum []:2-SAMU-GKHG-GOND-OIKI

Here is a list of the license information just entered:

Issuer: DEC
Authorization: HOBBYIST-VA-KEY16668-166603
Product Name: VAX-VMS
Producer: DEC
Units: 0
Release Date: 3-NOV-2014
Version:
Termination Date: 3-NOV-2014
Availability:
Activity: A
Options: NO_SHARE
Token:
Hardware ID: NONE
Checksum: 2-SAMU-GKHG-GOND-OIKI

Is that correct? [YES]: [Entrée]
Registering VAX-VMS license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
%LICENSE-F-BADCHK, checksum does not validate for VAX-VMS

Please review all entered PAK data, including the checksum.

Do you wish to make corrections? [YES]:NO

VAX-VMS license not registered in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB.
Press RETURN to return to the main menu
[Entrée]
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.

********************************************************************************

10) Configuration de la timezone :


%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: 11

You selected GMT as your time zone.
Is this correct? (Yes/No) [YES]: [Entrée]

GMT Time Zone Menu

1) GMT 12) GMT10 23) GMT-7 34) GMTPLUS5
2) GMT0 13) GMT11 24) GMT-8 35) GMTPLUS6
3) GMT1 14) GMT12 25) GMT-9 36) GMTPLUS7
4) GMT2 15) GMT13 26) GMT-10 37) GMTPLUS8
5) GMT3 16) GMT-0 27) GMT-11 38) GMTPLUS9
6) GMT4 17) GMT-1 28) GMT-12 39) GMTPLUS10
7) GMT5 18) GMT-2 29) GMTPLUS0 40) GMTPLUS11
8) GMT6 19) GMT-3 30) GMTPLUS1 41) GMTPLUS12
9) GMT7 20) GMT-4 31) GMTPLUS2 42) GMTPLUS13
10) GMT8 21) GMT-5 32) GMTPLUS3
11) GMT9 22) GMT-6 33) GMTPLUS4

0) None of the above

Select the number above that best describes your location: 3

You selected GMT1 as your time zone.
Is this correct? (Yes/No) [YES]: [Entrée]

Default Time Differential Factor is 1: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.).

Enter the Time Differential Factor [1:00]: [Entrée]

NEW SYSTEM TIME DIFFERENTIAL FACTOR = 1:00.

Is this correct? [Y]: [Entrée]

********************************************************************************

Running AUTOGEN to compute the new SYSTEM parameters ...

%AUTOGEN-I-BEGIN, GETDATA phase is beginning.

%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$COMMON:[SYSEXE]QMAN$MASTER.DAT;
-RMS-E-FNF, file not found

SHUTDOWN message from user SYSTEM at Batch 14:53:44
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
HALT instruction, PC: 8443B709 (MOVB 400(R1),R0)
sim>

11) Boot :


sim> boot cpu

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.
>>>boot
(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
%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 V7.3 Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.

*****************************************************************

OpenVMS VAX V7.3

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 6-OCT-2013 15:00:23.14
%RUN-S-PROC_ID, identification of created process is 00000206
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:08.68 %%%%%%%%%%%
Operator _PIVAX$OPA0: has been enabled, username SYSTEM

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:08.71 %%%%%%%%%%%
Operator status for operator _PIVAX$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:08.81 %%%%%%%%%%%
Logfile has been initialized by operator _PIVAX$OPA0:
Logfile is PIVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:08.82 %%%%%%%%%%%
Operator status for operator PIVAX::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 6-OCT-2013 15:01:11.08 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
%AUDSRV-I-NEWSERVERDB, new audit server database created

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:11.94 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:11.96 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
%AUDSRV-I-NEWOBJECTDB, new object database created

%SET-I-NEWAUDSRV, identification of new audit server process is 0000020C
%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:13.87 %%%%%%%%%%%
Message from user JOB_CONTROL on PIVAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:13.89 %%%%%%%%%%%
Message from user JOB_CONTROL on PIVAX
-RMS-E-FNF, file not found

%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:17.91 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:18.48 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:18.50 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:18.52 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-SERVERSTARTINGU, security server starting up

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:18.55 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up

%SMG-W-GBLNOTCRE, global section not created
-SYSTEM-F-GPTFULL, global page table is full
%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:23.37 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%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...

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:25.64 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$PIVAX.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:28.48 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
Security alarm (SECURITY) and security audit (SECURITY) on PIVAX, system id: 1025
Auditable event: Audit server starting up
Event time: 6-OCT-2013 15:01:28.20
PID: 00000203
Username: SYSTEM

%STARTUP-I-AUDITCONTINUE, audit server initialization complete

The OpenVMS VAX system is now executing the site-specific startup commands.

%%%%%%%%%%% OPCOM 6-OCT-2013 15:01:31.09 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
Security alarm (SECURITY) and security audit (SECURITY) on PIVAX, system id: 1025
Auditable event: Identifier added
Event time: 6-OCT-2013 15:01:31.02
PID: 00000203
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: PIVAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: SYS$NODE_PIVAX
Identifier value: %X80010000
Attributes: none

%UAF-I-RDBADDMSG, identifier SYS$NODE_PIVAX value %X80010000 added to rights database
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 6-OCT-2013 15:01:34.99

Accounting information:
Buffered I/O count: 1532 Peak working set size: 1851
Direct I/O count: 568 Peak page file size: 4963
Page faults: 4751 Mounted volumes: 0
Charged CPU time: 0 00:01:13.23 Elapsed time: 0 00:01:24.58
[Entrée]

12) Connection avec l’utilisateur « system » :


Welcome to OpenVMS (TM) VAX Operating System, Version V7.3

Username: system
Password: mot2passe
%LICENSE-I-NOLICENSE, no license is active for this software product
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3
$

13) Initialisation des disques durs :


$ initialize dua1: DATA1
$ initialize dua2: DATA2
$ mount/system dua1 data1
%MOUNT-I-MOUNTED, DATA1 mounted on _PIVAX$DUA1:
$ mount/system dua2 data2
%MOUNT-I-MOUNTED, DATA2 mounted on _PIVAX$DUA2:
$

14) Modification du fichier de démarrage :


$ set term/vt100
$ edit sys$manager:systartup_vms.com

Aller à la fin du fichier avec la touche [Flèche][Bas]

Avant :


$ EXIT

Ajouter :


$! Locally added stuff
$ mount/system dua1 data1
$ mount/system dua2 data2

Quitter et sauvegarder : [Contrôle]+[z]

15) Ajouter un utilisateur :


$ set def sys$system
$ r authorize
UAF> add pi/password=pi/owner="Raspberry Pi"/dev=dua1/dir=[pi]/uic=[200,201]/flag=nodisuser/priv=all
%UAF-I-PWDLESSMIN, new password is shorter than minimum password length
%UAF-I-ADDMSG, user record successfully added
%%%%%%%%%%% OPCOM 6-OCT-2013 15:13:16.77 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
Security alarm (SECURITY) and security audit (SECURITY) on PIVAX, system id: 102
5
Auditable event: System UAF record addition
Event time: 6-OCT-2013 15:13:16.70
PID: 00000211
Process name: SYSTEM
Username: SYSTEM
Process owner: [SYSTEM]
Terminal name: OPA0:
Image name: PIVAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Object class name: FILE
Object name: SYS$COMMON:[SYSEXE]SYSUAF.DAT;1
User record: PI
Default Device: New: DUA1:
Original: SYS$SYSDEVICE:
Default Directory: New: [PI]
Original: [USER]
Flags: New: (none)
Original: DISUSER
Owner: New: Raspberry Pi
Original:
Privileges: New: CMKRNL,CMEXEC,SYSNAM,GRPNAM,ALLSPOOL,IMPERSO
NATE,DIAGNOSE,LOG_IO,GROUP,NOACNT,PRMCEB,PRMMBX,PSWAPM,SETPRI,SETPRV,TMPMBX,WORL
D,MOUNT,OPER,EXQUOTA,NETMBX,VOLPRO,PHY_IO,BUGCHK,PRMGBL,SYSGBL,PFNMAP,SHMEM,SYSP
RV,BYPASS,SYSLCK,SHARE,UPGRADE,DOWNGRADE,GRPPRV,READALL,IMPORT,AUDIT,SECURITY
Original: TMPMBX,NETMBX
UIC: New: [200,201]
Original: [200,200]
Password Date: New: (pre-expired)
Original: (pre-expired)

%UAF-I-RDBADDMSGU, identifier PI value [000200,000201] added to rights database
%%%%%%%%%%% OPCOM 6-OCT-2013 15:13:16.94 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
Security alarm (SECURITY) and security audit (SECURITY) on PIVAX, system id: 102
5
Auditable event: Identifier added
Event time: 6-OCT-2013 15:13:16.90
PID: 00000211
Process name: SYSTEM
Username: SYSTEM
Process owner: [SYSTEM]
Terminal name: OPA0:
Image name: PIVAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: PI
Identifier value: %X00800081
Attributes: none

UAF> exit
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-RDBDONEMSG, rights database modified

16) Création du répertoire de l’utilisateur :


$ create/dir dua1:[pi]
$ set directory/owner=pi dua1:[pi]

17) Déconnection :


$ lo
SYSTEM logged out at 6-OCT-2013 15:16:05.33

Welcome to OpenVMS (TM) VAX Operating System, Version V7.3

18) Connection avec l’utilisateur pi et création d’un nouveau mot de passe :


Username: pi
Password: pi
%LICENSE-I-NOLICENSE, no license is active for this software product
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3
2 failures since last successful login

Your password has expired; you must set a new password to log in

New password:mot2passe
Verification:mot2passe

%%%%%%%%%%% OPCOM 6-OCT-2013 15:17:48.91 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
Security alarm (SECURITY) and security audit (SECURITY) on PIVAX, system id: 1025
Auditable event: System UAF record modification
Event time: 6-OCT-2013 15:17:48.87
PID: 00000214
Process name: PI
Username: PI
Process owner: [PI]
Terminal name: OPA0:
Image name: PIVAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Object class name: FILE
Object name: SYS$COMMON:[SYSEXE]SYSUAF.DAT;1
User record: PI
Password Date: New: 6-OCT-2013 15:17
Original: (pre-expired)

$

19) Quitter l’émulateur :


$
[Contrôle]+[e]
Simulation stopped, PC: 834D658D (BBC #3,26C(R3),834D65E1)
sim>

Préféré le shutdown en 22)

20) Boot OpenVMS VAX :


>>>boot
(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
%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 V7.3 Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
$! Copyright 2001 Compaq Computer Corporation.

%STDRV-I-STARTUP, OpenVMS startup begun at 6-OCT-2013 15:25:15.61
%RUN-S-PROC_ID, identification of created process is 00000206
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:01.47 %%%%%%%%%%%
Operator _PIVAX$OPA0: has been enabled, username SYSTEM

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:01.49 %%%%%%%%%%%
Operator status for operator _PIVAX$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:01.60 %%%%%%%%%%%
Logfile has been initialized by operator _PIVAX$OPA0:
Logfile is PIVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:01.62 %%%%%%%%%%%
Operator status for operator PIVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%SET-I-NEWAUDSRV, identification of new audit server process is 0000020C
%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:05.61 %%%%%%%%%%%
Message from user JOB_CONTROL on PIVAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:05.63 %%%%%%%%%%%
Message from user JOB_CONTROL on PIVAX
-RMS-E-FNF, file not found

%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:09.40 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:09.48 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:09.66 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:09.95 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-SERVERSTARTINGU, security server starting up

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:09.98 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up

%SMG-W-GBLNOTCRE, global section not created
-SYSTEM-F-GPTFULL, global page table is full
%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:14.79 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%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...

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:17.17 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$PIVAX.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting

%%%%%%%%%%% OPCOM 6-OCT-2013 15:26:19.77 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
Security alarm (SECURITY) and security audit (SECURITY) on PIVAX, system id: 1025
Auditable event: Audit server starting up
Event time: 6-OCT-2013 15:26:19.30
PID: 00000203
Username: SYSTEM

%STARTUP-I-AUDITCONTINUE, audit server initialization complete

The OpenVMS VAX system is now executing the site-specific startup commands.

%DCL-W-NOCOMD, no command on line - reenter with alphabetic first character
%MOUNT-I-MOUNTED, DATA1 mounted on _PIVAX$DUA1:
%MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress
%MOUNT-I-MOUNTED, DATA2 mounted on _PIVAX$DUA2:
%MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 6-OCT-2013 15:26:53.64

Accounting information:
Buffered I/O count: 1207 Peak working set size: 1910
Direct I/O count: 1724 Peak page file size: 4924
Page faults: 4267 Mounted volumes: 2
Charged CPU time: 0 00:01:27.08 Elapsed time: 0 00:01:38.99
[Entrée]

21) Connection avec l’utilisateur « pi » :


Welcome to OpenVMS (TM) VAX Operating System, Version V7.3

Username: pi
Password: mot2passe
%LICENSE-I-NOLICENSE, no license is active for this software product
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3
Last interactive login on Sunday, 6-OCT-2013 15:17
$

22) Shutdown :


$ @sys$system:shutdown

SHUTDOWN -- Perform an Orderly System Shutdown
on node PIVAX

How many minutes until final shutdown [0]: [Entrée]
Reason for shutdown [Standalone]: [Entrée]
Do you want to spin down the disk volumes [NO]? [Entrée]
Do you want to invoke the site-specific shutdown procedure [YES]? [Entrée]
Should an automatic system reboot be performed [NO]? [Entrée]
When will the system be rebooted [later]: [Entrée]
Shutdown options (enter as a comma-separated list): [Entrée]
REBOOT_CHECK Check existence of basic system files
SAVE_FEEDBACK Save AUTOGEN feedback information from this boot
DISABLE_AUTOSTART Disable autostart queues

Shutdown options [NONE]: [Entrée]

%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%%%%%%%%%%% OPCOM 6-OCT-2013 15:28:49.61 %%%%%%%%%%%
Operator status for operator _PIVAX$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%%%%%%%%%%% OPCOM 6-OCT-2013 15:28:51.49 %%%%%%%%%%%
Message from user JOB_CONTROL on PIVAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%% OPCOM 6-OCT-2013 15:28:51.51 %%%%%%%%%%%
Message from user JOB_CONTROL on PIVAX
-RMS-E-FNF, file not found

SHUTDOWN message on PIVAX from user PI at _PIVAX$OPA0: 15:28:52
PIVAX will shut down in 0 minutes; back up later. Please log off node PIVAX.
Standalone

1 terminal has been notified on PIVAX.

%SHUTDOWN-I-SITESHUT, the site-specific shutdown procedure will now be invoked
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down
%%%%%%%%%%% OPCOM 6-OCT-2013 15:29:02.95 %%%%%%%%%%%
Message from user AUDIT$SERVER on PIVAX
Security alarm (SECURITY) and security audit (SECURITY) on PIVAX, system id: 1025
Auditable event: Audit server shutting down
Event time: 6-OCT-2013 15:29:02.92
PID: 00000210
Username: PI

%SHUTDOWN-I-STOPSECSRV, the security server will now be shut down
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%%%%%%%%%%% OPCOM 6-OCT-2013 15:29:05.41 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-CIASHUTDOWN, breakin detection and evasion processing is shutting down

%%%%%%%%%%% OPCOM 6-OCT-2013 15:29:05.43 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-PROXYSHUTDOWN, proxy processing is shutting down

%%%%%%%%%%% OPCOM 6-OCT-2013 15:29:06.20 %%%%%%%%%%%
Message from user SYSTEM on PIVAX
%SECSRV-I-SERVERSHUTDOWN, security server shutting down

%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
%%%%%%%%%%% OPCOM 6-OCT-2013 15:29:12.92 %%%%%%%%%%%
Message from user PI on PIVAX
_PIVAX$OPA0:, PIVAX shutdown was requested by the operator.

%%%%%%%%%%% OPCOM 6-OCT-2013 15:29:13.09 %%%%%%%%%%%
Logfile was closed by operator _PIVAX$OPA0:
Logfile was PIVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2

%%%%%%%%%%% OPCOM 6-OCT-2013 15:29:13.36 %%%%%%%%%%%
Operator _PIVAX$OPA0: has been disabled, username SYSTEM

SYSTEM SHUTDOWN COMPLETE - use console to halt system
Infinite loop, PC: 833DC2D3 (BRB 833DC2D3)
sim>

23) Quitter l’émulateur :


sim> quit
Goodbye
NVR: writing buffer to file
Eth: closed eth0
pi@raspberrypi /usr/local/vax/bin $

24) Liens :

http://www.wherry.com/gadgets/retrocomputing/vax-simh.html
http://www.blews.co.uk/tony/pi-vax/
http://blog.meadhbh.org/2013/06/installing-vms-on-your-raspberry-pi.html

Laisser un commentaire

Votre adresse de messagerie ne sera pas publiée. Les champs obligatoires sont indiqués avec *