...
The next stage can be either installation of new VAX/VMS system using a distributive provided by HP or transfer of data from some existing VAX system. These possibities will possibilities will be discussed in details in next chapters.
If for some reason CHARON-VAX refuses to start please look for files with .log extention extension (CHARON-VAX log files) located in the directory from which CHARON-VAX starts, open them in some editing tool and analyze their content. In most cases those files contain very helpful information on what may possible went wrong.
Div | ||
---|---|---|
| ||
|
To exit from CHARON-VAX emulator use the following methods:
...
Copy the sample script "/opt/charon/bin/charon" ( "/opt/charon/bin/charon.service" for Fedora Core Linux ) to your home directory (Red Hat Linux) or to "/usr/lib/systemd/system/" directory (Fedora Core), for example:
Red Hat Linux Fedora Core $
cp
/opt/charon/bin/charon
/my_services/mv3k6_service
$
chmod
755
/my_services/mv3k6_service
Fedora Core $
cp
/my_services/opt/charon/bin/charon.service
/usr/lib/systemd/system/mv3k6.service
$
755 /my_serviceschmod
755 /usr/lib/systemd/system/mv3k6.service
Edit the renamed file to replace sample values of the following parameters, for example:
Red Hat Linux Fedora Core exec="/opt/charon/bin/mv3k6"
prog="my_mv3k6"
config="/my_services/mv3k6-service.cfg"
Fedora Core ExecStart=/opt/charon/bin/mv3k6 -d /my_services/mv3k6-service.cfg
WorkingDirectory=/my_services
- Create and edit configuration file ( "/my_services/mv3k6-service.cfg" in the examples above ) the way it was described before and make sure that the following pre-requisites are met:
OPA0 must be configured as virtual port or physical console, not as operator console, for example:
load virtual_serial_line OPA0 port=10003
#load operator_console OPA0Div class pagebreak Use only absolute paths to log, toy clock, nvram files and all the other data such as disk images etc. The names of the references files must be unique too, for example
...
set session log="/my_services/my_mv3k6.log"
set toy container="/my_services/my_mv3k6.dat"
load RQDX3/RQDX3 DUA
set DUA container[0]="/my_services/mv3k6_daemon_boot_disk.vdisk"
...
- Make sure the same physical devices are not used by other CHARON-VAX daemons, same for the OPA0 console port number.
Once configuration file is ready issue the following commands (the specifics belongs to the examples above) to install and start CHARON-VAX as daemon:
Red Hat Linux | Fedora Core |
|
---|---|---|
Fedora Core |
|
Warning | ||
---|---|---|
Note that a certain delay may appear in finding network license by Sentinel Run-time on CHARON-VAX host system startup. So if CHARON-VAX service is starting automatically on host system startup it may report "License not found" error and exit. This problem can be avoided by specifying "license_key_lookup_retry" parameter in the following way:
where:
Example:
In this example if the license key is not found during initial scan, CHARON-VAX will do 5 more attempts waiting 60 seconds between them. See General Settings section for more details. |
...
Div | ||
---|---|---|
| ||
|
Stopping CHARON-VAX service
To stop CHARON-VAX daemon use the following command, for example:
Red Hat Linux | Fedora Core |
|
---|---|---|
Fedora Core |
|
Please note that before stopping CHARON-VAX service, one must shutdown the operating system running by CHARON-VAX.
...
To remove CHARON-VAX daemon use the following commands, for example:
Red Hat LinuxFedora Core |
|
---|---|
Fedora Core |
|
Please note that before removing CHARON-VAX service one must shutdown the operating system running by CHARON-VAX and then stop corresponding CHARON-VAX service.
Please refer to the next chapters for more details concerning CHARON-VAX configuration details