…Details…

Icon

Thoughts that's escape, only details.

OpenVMS – SCSSYSTEMID

SCSSYSTEMID (G)
Specifies a number that identifies the computer. This parameter is not dynamic. SCSSYSTEMID is the low-order 32 bits of the 48-bit system identification number.

If the computer is in an OpenVMS Cluster, specify a value that is unique within the cluster. Do not use zero as the value.

If the computer is running DECnet for OpenVMS, calculate the value from the DECnet address using the following formula:

SCSSYSTEMID = ((DECnet area number) * 1024) + (DECnet node number)

Example: If the DECnet address is 2.211, calculate the value as follows:

SCSSYSTEMID = (2 * 1024) + 211 = 2259

OpenVMS – IPv6

Memo about configure ipv6 on OpenVMS system as host mode:

First of all invoke the TCPIP$IP6_SETUP command procedure by entering the following command:

TARDIS::LEO$ @SYS$MANAGER:TCPIP$IP6_SETUP

Leaving default option to all question, in this mode the dcl create default configuration script.

Then edit the inet6 script:

TARDIS::LEO$ EDIT SYS$SYSTEM:TCPIP$INET6_CONFIG.DAT

After the “up” command

$ ifconfig "IE0" ipv6 up

Append the following line with ip and default gateway:

$ ifconfig "IE0" inet6 ip6prefix 2001:1418:0193:0001::40/64
$ route add -inet6 default 2001:1418:0193:0001::250 -"I" "IE0"

Save, exit and run the dcl:

TARDIS::LEO$ @SYS$SYSROOT:[SYSEXE]TCPIP$INET6_CONFIG.DAT

OpenVMS – Set Time

The command to reset the system time to 18-APR-2010 09:47 is:

$ SET TIME=18-APR-2010:09:47

Note the colon between the date and the time specification. (This
extra colon is a requirement resulting from the DCL parsing rules.
Normally, there is a space between the date and time.)

On OpenVMS VAX, once a year between January 1st and circa April 11th,
or whenever a different SYS.EXE system image is bootstrapped, issue the
command:

$ SET TIME

to resynchronize the VAX time-of-year (TOY) clock and the contents of
the OpenVMS VAX system image. (This SET TIME command is automatically
performed during a normal system shutdown.) The TOY clock stores (only)
the time since January 1 00:00:00.00 of the current year, and has a
maximum resolution of roughly 466 days. The system image is used as the
storage location for the current year. Between these two values, the
current time and date is “constructed” during the OpenVMS VAX system
bootstrap. (And this is the reason the saved time value in the system
image must be reset every year between January and April.)

The SYSGEN parameter SETTIME can be used to enable prompting for the
system time during the system bootstrap.

OpenVMS – Command line editing

DCL implements command line editing and recall, so that users can more easily correct typing errors and reuse previous command lines.

Recall buffer: access to recently issued commands

$ RECALL string Bring up last command beginning with string.
$ RECALL/ALL Displays all commands and their numbers.
$ RECALL number Use a number found in RECALL/ALL.

Command line editing (if it isn’t on, do: $ SET TERM/LINE):

$ {up-arrow} Previous command in recall buffer.
$ {down-arrow} Next command in recall buffer.
$ {Ctrl A} Toggle insert/overstrike editing.
$ {Ctrl D} Move one character left.
$ {Ctrl E} Move to the end of the line.
$ {Ctrl F} Move one character right.
$ {Ctrl H} Move to the beginning of the line.
$ {Ctrl J} Delete word left of cursor.
$ {Ctrl R} Rewrite the command line.
$ {Ctrl U} Delete line left of cursor.
$ {Ctrl X} Cancel the current command line.

Miscellaneous:

$ {Ctrl 3} ASCII code for {Esc}.
$ {Ctrl I} ASCII code for {Tab}.
$ {Ctrl Z} Tell DCL "end of file". Used in some programs
to indicate more general sorts of "end" commands.

Of these, only {Ctrl I} will insert a character into the command line,
rather than just move the cursor around. No new characters may be
inserted before a tab ({Ctrl I}) in a command line, but existing characters
may be changed in overstrike mode, or deleted. This behavior is documented in the “I/O User’s Guide” and has existed since VMS 4.0.

OpenVMS – SYS$BATCH Queue

Little memo about sys$batch queue:

If no queue manger set:

$ DEFINE/SYSTEM/EXECUTIVE_MODE QMAN$MASTER DKA100:[QUEMAN]
$ START/QUEUE/MANAGER DKA100:[SYSQUE]

Problem:

$ SHOW QUEUE SYS$BATCH
%JBC-E-NOSUCHQUE, no such queue

Resolution:

$ INIT/QUE/BATCH SYS$BATCH

Problem:

$ SHOW QUEUE SYS$BATCH
%JBC-E-JOBQUEDIS, system job queue manager is not running

Resolution:

$ START/QUE SYS$BATCH

Full Reset:

$ STOP/QUE SYS$BATCH
$ DELETE/QUE SYS$BATCH
$ INIT/QUE/BATCH SYS$BATCH

More info:
OpenVMS System Manager’s Manual
Chapter 13
Managing the Queue Manager and Queue Database

DEC 3000 Alpha – Firmware Upgrade

>>> boot esa0
INIT-S-CPU...
INIT-S-ASIC...
INIT-S-MEM...
INIT-S-NVR...
INIT-S-CXT...
INIT-S-SCC...
INIT-S-NI...
INIT-S-SCSI...
INIT-S-ISDN...
AUDIT_BOOT_STARTS ...
AUDIT_BOOT_REQ
AUDIT_BOOT_RETRY
AUDIT_BOOT_RETRY
AUDIT_BOOT_RETRY
AUDIT_BOOT_RETRY
AUDIT_BSERVER_FOUND
AUDIT_LOAD_BEGINS
AUDIT_LOAD_DONE
*** FIRMWARE UPDATE UTILITY V2.6a ***
*** SYSTEM TYPE: M300 ***
UPDATE
VERIFY
LIST
SHOW
?
UPD-> update
Read IO ROM Device ID
UPD-I VERIFY LOADED ROM IMAGE
...........................
UPD-I VERIFY LOADED ROM IMAGE DONE
MANUFACTURER = INTEL (0x89)
DEVICE CODE = 28F020 (0xbd) 256K x 8
Read System ROM Device ID
UPD-I VERIFY LOADED ROM IMAGE
...........................
UPD-I VERIFY LOADED ROM IMAGE DONE
MANUFACTURER = INTEL (0x89)
DEVICE CODE = 28F020 (0xbd) 256K x 8
UPDATE SYSTEM ROM DEVICE
UPD-I VERIFY LOADED ROM IMAGE
...........................
UPD-I VERIFY LOADED ROM IMAGE DONE
FIRMWARE REVISION: V7.0 LENGTH: 0x352e4 -> 217828 BYTES CHECKSUM: 0x1c
MANUFACTURER = INTEL (0x89)
DEVICE CODE = 28F020 (0xbd) 256K x 8
UPD-I *** ROM CONTENTS WILL BE DESTROYED ***
UPD-I ARE YOU READY TO PROGRAM DEVICE ? (Y/N ) y
UPD-I PRECHARGING DEVICE
................................................................
UPD-I ERASING ROM DEVICE
................................................................
UPD-I PROGRAMMING DEVICE
.....................................................
UPD-I PROGRAMMING COMPLETED
...........................
SYSTEM ROM UPDATE SUCCESSFUL
UPDATE IO ROM DEVICE
UPD-I VERIFY LOADED ROM IMAGE
...........................
UPD-I VERIFY LOADED ROM IMAGE DONE
FIRMWARE REVISION: V7.0 LENGTH: 0x34da8 -> 216488 BYTES CHECKSUM: 0x59
MANUFACTURER = INTEL (0x89)
DEVICE CODE = 28F020 (0xbd) 256K x 8
UPD-I PRECHARGING DEVICE
................................................................
UPD-I ERASING ROM DEVICE
................................................................
UPD-I PROGRAMMING DEVICE
....................................................
UPD-I PROGRAMMING COMPLETED
...........................
IO ROM UPDATE SUCCESSFUL
UPD->
UPD-> ?
UPDATE:
Update the ROMs. Jumpers MUST be installed on both roms.
For example
UPD->update

VERIFY [DEVICE]:
Verify the ROM[s]. If no qualifiers then all ROMS verified
The Checksum of file image is compared with rom image
For example
UPD->verify
UPD->verify system
UPD->verify io

SHOW [DEVICE]:
Show the current ROM Revision
For example
UPD->show
UPD->show system
UPD->show io

LIST :
List the supported ROM Devices
For example
UPD->list
*** ROM Devices Supported ***
SYSTEM: KN15-AA CPU Module 28F020 256Kx8 FLASH MEMORY
IO: IO-XXX I/O Module 28F020 256Kx8 FLASH MEMORY

*** FIRMWARE UPDATE UTILITY V2.6a ***
*** SYSTEM TYPE: M300 ***
UPDATE
VERIFY
LIST
SHOW
?
UPD->

VAX – MMJ DEC423 Pinout

Setting up serial connection to VAXstation 4000/60:

First made a serial cable, attention Vax use a DEC423 serial port designed for long distant terminal line:

--------------- 1 - DTR (Data terminal ready)
I             I 2 - TxD (Transmit data)
I 1 2 3 4 5 6 I 3 - GND (Signal ground)
I             I 4 - RxC (Receive common)
I             I 5 - RxD (Receive data)
---------I____I 6 - DSR (Data set ready)

Pin 2 of the phone connector goes to Rx pin of the serial (3 of DB25 or 2 of DB9), pins 3 & 4 go to ground (7 of DB25 or 5 of DB9), and pin 5 goes to Tx pin (2 of DB25 or 3 of DB9).

Then, make sure that the S3 switch (on the front of the 4000/60) is set to
the up position so that the VAX uses the serial console instead of the
graphics console.

Then, load up your favourite terminal application, set the speed to 9600
baud, make sure hardware handshaking is off, and see if you can talk to
the VAX.

My first VAX and VMS system

3 days ago I find a nice VAX Station 4000/60 on ebay for only 41 Euro (about 60 Dollars), obviously I bought it, and today delivery boy knock my door!

I paste the command/console output of the recovery procedure:

KA46-A V1.4-38E-V4.2
08-00-2B-92-4E-C7
24MB

?? 001 9 NI 0172

>>> sh config

KA46-A V1.4-38E-V4.2
08-00-2B-92-4E-C7
24MB

DEVNBR DEVNAM INFO
------ -------- --------------------------
1 NVR OK
2 LCG OK
HR - 8 PLN FB - V1.2
3 DZ OK
4 CACHE OK
5 MEM OK
24MB = SY=8MB, S0/1=8MB, S2/3=8MB, S4/5=0MB
6 FPU OK
7 IT OK
8 SYS OK
9 NI ?? 001 0172
10 SCSI OK
3-L0-RZ26B 6-INITR
11 AUD OK

>>> ?

BOOT [/[R5:]<bflg>] [<ddau>[:]]
CONTINUE
DEPOSIT [{ /B | /W | /L | /Q | /A }] [{ /P | /V | /I }] [/G] [/U] [/N:<n>]
[{ <addr> | <sym> | + | - | * | @ } [<datum>]]
EXAMINE [{ /B | /W | /L | /Q | /A }] [{ /P | /V | /I }] [/G] [/U] [/N:<n>]
[{ <addr> | <sym> | + | - | * | @ }]
FIND [{ /MEMORY | /RPB }]
HALT
HELP
INITIALIZE
LOGIN
REPEAT <cmd>
SET BOOT <ddau>
SET BFLG <bflg>
SET DIAGENV <1-3>
SET FBOOT <0-1>
SET HALT <1-3>
SET KBD <0-15>
SET MOP <0-1>
SET PSE <0-1>
SET PSWD
SET SCSI <0-7>
SET TRIG <0-1>
SHOW { BOOT | BFLG | CONFIG | DEV | DIAGENV | FBOOT | ETHER | ERROR |
ESTAT | HALT | KBD | MEM | MOP | PSE | SCSI | TRIG }
START <addr>
TEST [/UTIL] <devnam | devnbr>
UNJAM
X <addr> <cnt> ...
?

>>> B/1

-DKA300
SYSBOOT> SET/STARTUP OPA0:

SYSBOOT> SET WINDOWS_SYSTEM 0

%SYSBOOT-E-NOPARAM, no such parameter WINDOWS_SYSTEM
SYSBOOT> SET WRITESYSPARAMS 0

SYSBOOT> CONTINUE

VAX/VMS Version V5.5-2H4 Major version id = 1 Minor version id = 0

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 27-NOV-2009 3:51
$

$ SPAWN
SPAWN
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%DCL-S-ATTACHED, terminal now attached to process SYSTEM_1
$ @SYS$SYSTEM:STARTUP
$! Copyright (c) 1993 Digital Equipment Corporation. All rights reserved.

%STDRV-I-STARTUP, VMS startup begun at 27-NOV-2009 04:00:59.19

The VAX/VMS system is now executing the system startup procedure.

%SET-I-NEWAUDSRV, identification of new audit server process is 00000088

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

%RUN-S-PROC_ID, identification of created process is 0000008C
%NCP-W-FILOPE, File open error , Permanent database

%NML-E-OPENOUT, error opening SYS$SYSROOT:[SYSEXE]NETLOGING.DAT; as output
-RMS-F-PLV, unsupported prolog version
%NCP-W-OPEFAI, Operation failure

%SYSTEM-F-TIMEOUT, device timeout
, timeout
, unit is active
, fatal hardware error
%NCP-W-UNRCMP, Unrecognized component , Circuit
Circuit = SVA-0

%NCP-I-NOINFO, No information in database
%RUN-S-PROC_ID, identification of created process is 0000008D
Job NCPSTART (queue SYS$BATCH, entry 1) started on SYS$BATCH
%RUN-S-PROC_ID, identification of created process is 0000008F
%SET-I-INTSET, login interactive limit = 20, current interactive value = 1
27-NOV-2009 04:03:07
Process SYSTEM_1 logged out at 27-NOV-2009 04:03:08.62

Accounting information:
Buffered I/O count: 3431 Peak working set size: 888
Direct I/O count: 1440 Peak page file size: 3806
Page faults: 16606 Mounted volumes: 0
Charged CPU time: 0 00:00:22.71 Elapsed time: 0 00:02:18.06
%DCL-S-RETURNED, control returned to process STARTUP
$ SET DEFAULT SYS$SYSTEM
SET DEFAULT SYS$SYSTEM
$ RUN SYS$SYSTEM:AUTHORIZE
RUN SYS$SYSTEM:AUTHORIZE
UAF> MODIFY SYSTEM /PASSWORD=system
%UAF-I-MDFYMSG, user record(s) updated
UAF> EXIT
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-RDBNOMODS, no modifications made to rights data base
$ LOGOUT
LOGOUT
SYSTEM job terminated at 27-NOV-2009 04:04:26.81

Accounting information:
Buffered I/O count: 99 Peak working set size: 1056
Direct I/O count: 46 Peak page file size: 3978
Page faults: 471 Mounted volumes: 0
Charged CPU time: 0 00:00:00.41 Elapsed time: 0 00:05:33.58

Welcome to VAX/VMS V5.5-2H4

Username:

Archives