A number of error messages can be returned by the LD utility.
1 – ACCURATE
%LD-I-ACCURATE, Accurate timing is active An LD SHOW/TRACE/STATUS command was given while accurate trace timing is active. This status is only returned on Alpha.
2 – ALLOCLASS
%LD-F-ALLOCLASS, Allocation class mismatch An LD CONNECT/SHARE command was given where the current allocation class of the specified LD device was different on the current node then on another cluster node where the file is connected.
3 – ALREADYCONN
%LD-F-ALRDYCONN, Device already connected An LD CONNECT command is given while the logical disk device was already connected.
4 – ANALYZEERR
%LM-F-ANALYZEERR, Container file structure error at logical block 213 An LM ANALYZE command is given where the tape container file has a structural error at logical block 213.
5 – ANALYZEOK
%LM-I-ANALYZEOK, Container file structure successfully verified An LM ANALYZE command is given where the tape container file has no errors.
6 – BADALLOCLASS
%LD-F-BADALLOCLASS, Bad allocation class specified An LD CONNECT/ALLOCLASS command was given with an allocation class bigger than the limit of 255.
7 – BADDEVSYNTAX
%LD-F-BADDEVSYNTAX, Bad device syntax (LDAZ:) A unit to use as a logical disk was specified with a bad syntax.
8 – BADENTPARAM
%LD-F-BADENTPARAM, Bad /ENTRIES parameter(s) An LD SHOW/TRACE/ENTRIES command was given where either the second parameter was less than the first, or one of the parameters was less than 0.
9 – BADUNIT
%LD-F-BADUNIT, Bad unit number LDAnnnnn An LD command was given where the unit number is out of range. A valid unit numer ranges from 1 to 9999.
10 – BLANKTAPE
%LM-I-BLANKTAPE, Blank tape detected An LM ANALYZE command is given where the tape container file has not been used before.
11 – BLKOUTOFRANGE
%LD-F-BLKOUTOFRANGE, Blocks out of range An LD CONNECT/LBN=(START=x,END=y) command was given where the starting end ending blocks are outside the LBN's of the source device. This error can also occur on an LD CONNECT/LBN=(START=x,COUNT=y) command where y would cause LD to go past the end of the disk.
12 – CANTREADOLDFMT
%LD-F-CANTREADOLDFMT, Can't read old format datafile (Version 2) An attempt was made to read a datafile which was created with an old version of LD. Use the old version of LD to read the file.
13 – CLONENOTMOUNTED
%LD-F-CLONENOTMOUNTED, Clone device must be mounted A CREATE/CLONE=dev or CONNECT/CLONE=dev command was given where 'dev' was not mounted.
14 – CLOSERR
%LD-F-CLOSERR, Unable to close file $1$DUA0:[DATA]LD_TRACE.LOG;1
An LD SHOW/TRACE/{IN,OUT}PUT command was given, and the close of
the in- or output file had a problem.
15 – CONFQUAL
%LD-F-CONFQUAL, Conflicting qualifiers Conflicting qualifiers were given for the specified command. Check the documentation.
16 – CONNECTED
%LD-I-CONNECTED, Device _THEBUG$LDA1: is connected to
$1$DUA1:[DIR]DISKFILE.DSK;1
An LD CONNECT/LOG command is given, or an LD SHOW command.
%LD-I-CONNECTED, Device _THEBUG$LDA1: is connected to $1$DUA1: (Replaced)
An LD CONNECT/LOG/REPLACE command is given, or an LD SHOW command.
The complete device was replaced.
17 – CONTTOOSMALL
%LD-F-CONTTOOSMALL, Container file too small (5000 blocks minimum) An LM CONNECT command was given where the containerfile is smaller than 5000 blocks. Due to buffering in the driver a minimum size of the containerfile is needed, unless /EXTEND was specified.
18 – CONTTRACEACT
%LD-F-CONTTRACEACT, Continuous tracing is already active for
device _THEBUG$LDA1:
An LD SHOW/TRACE/CONTINUOUS command was given while such command
for the same device was already in progress.
19 – CONTTRACENOTACT
%LD-F-CONTTRACENOTACT, Continuous tracing is not active for
device _THEBUG$LDA1:
An LD TRACE/STOP command was given for a specified device
while there was no continuous trace active for that device.
20 – CREATED
%LD-I-CREATED, File $1$DUA1:[DIR]DISKFILE.DSK;1 created An LD CREATE/LOG command is given.
21 – CREATERR
%LD-F-CREATERR, Unable to create file $1$DUA0:[TMP]DATA.DSK;1 An LD CREATE command was given, but the command was unable to complete. The accompanying message shows more info.
22 – CYLINDERS
%LD-F-CYLINDERS, Cylinders mismatch An LD CONNECT/SHARE command was given where the number of cylinders did not match the number of cylinders for the containerfile on another node.
23 – DETECTEDERR
%LD-F-DETECTEDERR, Detected fatal error A general fatal error was detected. Look at the accompanying errormessage.
24 – DEVASSIGN
%LD-F-DEVASSIGN, Device has channels assigned An LD DISCONNECT command was given on a device with active channels. Most probably an LD SHOW/TRACE/CONTINUOUS command is still active.
25 – DEVCONNECTED
%LD-F-DEVCONNECTED, Cannot set allocation class with active LD devices An LD CONNECT/ALLOCLASS command was given while there were already LD devices connected. All devices have to be disconnected before an allocation class can be set.
26 – DEVICEINUSE
%LD-F-DEVICEINUSE, Device incompatible connected to other LD disk in cluster An LD CONNECT command is given where the device to be replaced was already in use by another logical disk or by VMS, either on this system or on another system in a cluster.
27 – DEVICENAME
%LD-F-DEVICENAME, Devicename mismatch An LD CONNECT command is given where the devicename of a shared device or file was not the same as the one on a remote node.
28 – DISCONNECTED
%LD-I-DISCONNECTED, Disconnected $1$DUA1:[DIR]DISKFILE.DSK;1 from $1$LDA1: An LD DISCONNECT/LOG command is given, and the unit plus containerfile disconnected are displayed.
29 – DUPUNIT
%LD-F-DUPUNIT, Duplicate unitnumber An LD CONNECT file LDAxx command was given while the device LDAxx already exists.
30 – EXTENDED
%LD-I-EXTENDED, File $1$DUA1:[DIR]DISKFILE.DSK;1 extended to 10000 blocks An LD CREATE/EXTEND/SIZE=10000/LOG command is given.
31 – FDTACTIVE
%LD-I-FDTACTIVE, FDT Tracing is active An LD SHOW/TRACE/STATUS command was given while FDT tracing is active. This status is only returned on Alpha.
32 – FILEIDINUSE
%LD-F-FILEIDINUSE, File ID in use An LD CONNECT command is given where the specified file is already in use, possibly on a remote node.
33 – FILEINUSE
%LD-F-FILEINUSE, File incompatible connected to other LD disk in cluster An LD CONNECT command is given where the logical disk file was already in use by another logical disk, either on this system or on another system in a cluster. The connect specified on the other system was done in a way which is not compatible with the current connect parameters. This can happen if another node specified for example /MAXBLOCKS, or /TRACKS which were not or incompatible specified on the local node. The complete geometry must be the same on all nodes.
34 – FILEONOTHER
%LD-F-FILEONOTHER, File not allowed to be on other device An LD WATCH/FILE=filespec command was given where the specified file did not reside on the specified LD device.
35 – FILEONVOLSET
%LD-F-FILEONVOLSET, File watchpoint on volumeset not allowed An LD WATCH/FILE=filespec command was given where the specified file resides on a volume set. This is not supported.
36 – FILREADERR
%LD-F-FILREADERR, Unable to read input file $1$DUA0:[TMP]FILE.DAT;1 An LD SHOW/TRACE/INPUT command was given where the requested inputfile could not be read.
37 – FILWRTERR
%LD-F-FILWRTERR, Unable to write output file $1$DUA0:[TMP]FILE.DAT;1 An LD SHOW/TRACE/OUTPUT command was given where the requested outputfile could not be written.
38 – HIGHWATER
%LD-W-HIGHWATER, Highwater marking is enabled on device, be patient An LD CREATE command was given, and the disk where the container file is created has highwater marking enabled, and the specified containersize is more than 100000 blocks. This is just a warning that creation of the container file may take a long time as the contents will be erased.
39 – INCMPDEVTYPE
%LD-F-INCMPDEVTYPE, Incompatible device type An LD command is given which is only applicable to tapes. An LM command is given which is only applicable to disks.
40 – INCMPPROT
%LD-F-INCMPPROT, Incompatible locking protocol in use An LD CONNECT/SHARE command was given while an incompatible version of LDDRIVER was connected to the same resource on another node in a cluster. Make sure that all systems in a cluster sharing an LD connected resource have the same version of LD installed.
41 – INFILERR
%LD-F-INFILERR, Unable to open input file $1$DUA0:[TMP]FILE.DAT;1 An LD SHOW/TRACE/INPUT command was given where the requested inputfile could not be opened.
42 – INVGEOMETRY
%LD-F-INVGEOMETRY, Invalid geometry specified An LD CONNECT command is given where the geometry specified with /TRACKS, /SECTORS or /CYLINDERS is invalid. TRACKS and SECTORS are limited to 255, CYLINDERS is limited to 65535. This error can also be returned if TRACKS * SECTORS * CYLINDERS is less than the maximum logical blocknumber of the container file.
43 – INVOKESTARTUP
%LD-F-INVOKESTARTUP, LD has not been setup correctly, invoke
@SYS$STARTUP:LD$STARTUP.COM
%LM-F-INVOKESTARTUP, LM has not been setup correctly, invoke
@SYS$STARTUP:LM$STARTUP.COM
Any LD or LM command that needs the driver will check if the driver
is loaded, and that the control utility has been installed. If this
is not the case the startup procedure must be executed.
44 – INVVERSIONFMT
%LD-F-INVVERSIONFMT, Invalid driver version format An LD VERSION command was given where the version information returned by the driver is incompatible with the LD utility command program used to get this info.
45 – LOGICALNAMEERR
%LD-F-LOGICALNAMEERR, Error defining locical name An LD CONNECT/LOGICAL command was given where the creation of the logical name returned an error.
46 – MAXBLOCK
%LD-F-MAXBLOCK, Maximum blocknumber mismatch An LD CONNECT/SHARE command was given where the maximum number of blocks did not match the maximum number of blocks for the containerfile on another node.
47 – METADATA
%LD-I-METADATA, Metadata available An LM SHOW/FULL or CONNECT/FULL command was given where the containerfile has valid metadata available.
48 – NEEDDEVICE
%LD-F-NEEDDEVICE, Device name needed An LM LOAD command is given to connect a containerfile to an existing device, and that device is not speficied.
49 – NOCLUSTER
%LD-F-NOCLUSTER, No cluster code loaded An LD CONNECT/SHARE command is given when the system is not running VMSCluster software.
50 – NOGROUPPRIV
%LD-F-NOGROUPPRIV, No privilege to stop trace of device _THEBUG$LDA1: An attempt was made to stop the continuous trace of device THEBUG$LDA1 while the trace was started by a process in the same UIC group. This operation need GROUP privilege.
51 – NOLBNMAP
%LD-F-NOLBNMAP, No lbn mapping specified An LD CONNECT/SHARE command was given when the shared device was created with LBN mapping.
52 – NOMETADATA
%LD-I-NOMETADATA, No metadata available An LM ANALYZE command was given where the containerfile contains no valid metadata.
53 – NOREADWRITE
%LD-F-NOREADWRITE, No read or write function specified for file mode An LD WATCH/FILE=filespec command was given where the function was not one of the following: READPBLK, WRITEPBLK, WRITECHECK or DSE. Such watchpoint may only be specified in combination with a data- transfer function.
54 – NOSHARE
%LD-F-NOSHARE, No sharing specified for file on this node An LD CONNECT command was given while the specified containerfile was connected with /SHARE on another node.
55 – NOSYSNAM
%LD-F-NOSYSNAM, SYSNAM privilege needed to define an EXEC logical name An LD CONNECT/LOGICAL=MODE=EXEC command was given while the process issuing the command lacks SYSNAM privilege.
56 – NOTADISK
%LD-F-NOTADISK, Clone device must be a disk An LD CONNECT/CLONE=dev or CREATE/CLONE=dev was given where 'dev' was not a disk.
57 – NOTCONN
%LD-F-NOTCONN, Device not connected An LM UNLOAD command was given on a tapeunit without a connected container file.
58 – NOTCONNECTED
%LD-W-NOTCONNECTED, Device _THEBUG$LDA1: is not connected An LD SHOW command is given, and the disk was not connected to a file. An LD DISCONNECT command is given while the logical disk device was not connected. This errormessage can only occur if the driver has been assembled without cloned device support.
59 – NOTRCDATA
%LD-F-NOTRCDATA, No trace data available An LD SHOW/TRACE command was given while the tracebuffer did not contain any data.
60 – NOTREPLACED
%LD-F-NOTREPLACED, Device was not connected as replaced on other node An LD CONNECT/REPLACE command was given where the specified device was connected on another node, but not as /REPLACED.
61 – NOTSAVED
%LD-W-NOTSAVED, Container file metadata has not been saved An LD CONNECT/SAVE or LD [NO]PROTECT/PERMANENT command was given where the fileheader of the container file does not have enough space to store the metadata. This can happen if the containerfile was created with an old version of the LD utility. Notice that this is a warning only, to fix this a new container file must be created.
62 – NOTSHARED
%LD-F-NOTSHARED, File is not shared on other node An LD CONNECT/SHARE command was given while the specified containerfile was not connected with /SHARE on another node.
63 – NOTVISIBLE
%LD-F-NOTVISIBLE, Device is not visible on other nodes An LD CONNECT/SHARE command is given when the device to be replaced or the device on which the container file resides is not visible by other cluster nodes.
64 – NOUNITSFOUND
%LD-F-NOUNITSFOUND, No usable logical disk units found An LD SHOW/ALL or TRACE/STOP/ALL command was given while no connected units were found.
65 – NOWATCHDATA
%LD-F-NOWATCHDATA, No watchpoint data available An LD SHOW/WATCH command was given while no watchpoints were set.
66 – NOWDISCONN
%LD-I-NOWDISCONN, Device $8$LDA1: is now disconnected from file
$8$DIA2:[LD]DEVICE1.DSK;1
An LD DISCONNECT/LOG command is given.
67 – NOWORLDPRIV
%LD-F-NOWORLDPRIV, No privilege to stop trace of device _THEBUG$LDA1: An attempt was made to stop the continuous trace of device THEBUG$LDA1 while the trace was started by a process in another UIC group. This operation needs WORLD privilege.
68 – OPENERR
%LD-F-OPENERR, Unable to open file NOFILE An LD CONNECT command was given where the container file could not be opened.
69 – OUTFILERR
%LD-F-OUTFILERR, Unable to open output file $1$DUA0:[TMP]FILE.DAT;1 An LD SHOW/TRACE/OUTPUT command was given where the requested outputfile could not be opened.
70 – PASTDATA
%LD-F-PASTDATA, Requested entry(s) past end of data An LD SHOW/TRACE/ENTRIES command was given where the requested entries were beyond the available data.
71 – RANGEINUSE
%LD-W-RANGEINUSE, LBN range already in use An LD CONNECT/LBN command was given where the requested range of logical blocknumbers was already in use elsewhere in the cluster. This can also happen if there's an overlap with an existing range.
72 – REMOTEALLOC
%LD-W-REMOTEALLOC, Device _$1$LDA1: is allocated on a remote node An LD SHOW or an LD DISCONNECT command was given while the specified LD device was mounted private on a remote node. This can only happen on an LD device which was connected with /SHARE.
73 – SECTORS
%LD-F-SECTORS, Sectors mismatch An LD CONNECT/SHARE command was given where the number of sectors did not match the number of sectors for the containerfile on another node.
74 – STARTLBN
%LD-F-STARTLBN, Starting lbn mismatch An LD CONNECT/LBN=START=x/SHARE command was given where the starting LBN did not match the starting LBN on another node.
75 – STATUS
%LD-I-STATUS, Device _THEBUG$LDA1: has a tracebuffer of 512
entries (139 valid records)
An LD SHOW/TRACE/STATUS command is given. The specified device
has 512 tracebuffer entries allocated, of which 139 are currently
in use.
76 – TRACESTOPPED
%LD-I-TRACESTOPPED, Trace stopped by process 0C20025E (HOSTbuster) An LD TRACE/STOP command was given for a device to force a SHOW/TRACE/CONTINUOUS command which was in progress by another process to exit. The process issuing the command is indicated by the process id and process name.
77 – TRACKS
%LD-F-TRACKS, Tracks mismatch An LD CONNECT/SHARE command was given where the number of tracks did not match the number of tracks for the containerfile on another node.
78 – TRCDISABL
%LD-F-TRCDISABL, Tracing is disabled An LD SHOW/TRACE command was given while tracing was not enabled for the specified device.
79 – TRCENABL
%LD-F-TRCENABL, Tracing is already enabled An LD TRACE command was given while tracing was already enabled.
80 – UNIT
%LD-I-UNIT, Allocated device is _THEBUG$LDA4: An LD CONNECT command was given without /LOG and without a device specification. This informational message shows which device was assigned to the specified file.
81 – UNITNUMBER
%LD-F-UNITNUMBER, Unitnumber mismatch An LD CONNECT/SHARE command was given when the specified unit number was different than the unitnumber for the same containerfile used on another node.
82 – UNSUPPORTEDFS
%LD-F-UNSUPPORTEDFS, Unsupported filesystem An LD CONNECT command was given while the specified containerfile was located on an unrecognized filesystem.
83 – VBNERROR
%LD-F-VBNERROR, Illegal virtual block number specified An LD WATCH/FILE=filespec command was given where the VBN to watch was either zero or beyond the end of file.
84 – VERSION
%LD-I-VERSION, LD version V9.0, module X-9 built on Oct 28 2006 15:19:29
-LD-I-DRIVERVERSION, Driver version: 28-OCT-2006 15:19:59.26 (MON version)
-LD-I-SYSINFO, Node: THEBAT, Hardware: hp AlphaServer DS20L 833 MHz, VMS version: V8.3
An LD VERSION command was given, and the resulting information
is displayed.
85 – WPTNOTFOUND
%LD-F-WPTNOTFOUND, Watchpoint not found An LD SHOW/WATCH command was given where the specified watchpoint does not exist.
86 – Other
The VAX/VMS System Messages and Recovery Procedures Reference Man- ual lists other possible messages and provides explanations and suggested user actions. Note that when errormessages are returned, and you cannot trace them back to the Logical Disk, perform the same checks again for the Physical Disk on which the Logical File resides.