LJK/CDROM Reference Manual
Appendix C
Copyright
This appendix describes the copyright restrictions for LJK/CDROM, which differ from typical copyright restrictions.
This appendix does not deal with licensing the use of LJK/CDROM.
For licensing information consult Appendix D, Licensing, within the
LJK/CDROM Reference Manual for this version of the product.
The information on the CDROM containing LJK/CDROM is
copyrighted by:
- LJK Software
1 Broadway, Suite 600
Cambridge, MA 02142-1100
Copying for Use
A licensee under any of the licenses in Appendix D, Licensing, within the
LJK/CDROM Reference Manual for this version of the product, may copy the software
to magnetic disk for installation and use in accordance with that
license. Said licensee may also copy the installed software to backup
media in accordance with normal backup procedures, only for use by the
licensee (individual or organization) that installed it.
Copying for Sharing
This software may be copied for licensed use by another licensee (under
any of the licenses in Appendix D, Licensing, within the LJK/CDROM Reference Manual for
this version of the product) only to a CD-R disc under
the following restrictions:
- in such a fashion that a bit by bit comparison with the VMS command
DIFFERENCES with foreign mounted discs
shows the copy is identical. In the absence of a clean termination to
the DIFFERENCES command, it is sufficient that an error like:
%DIFF-F-READERR, error reading DKA400:[].;
-RMS-F-RER, file read error
-SYSTEM-F-ILLBLKNUM, illegal logical block number
|
occur in both direction of comparison.
- in such a fashion that all wording from the face of the original
disc is reproduced in a legible fashion on the face of the copy.
Transfer for Sharing
An original CDROM disc of this software may also be transferred
(temporarily or permanently) for licensed use by another licensee under
any of the licenses in Appendix D, Licensing, within the LJK/CDROM Reference Manual for
this version of the product.
Overall Restriction
Transfer of the files comprising LJK/CDROM to another individual
or organization via any medium other than CDROM or CD-R is forbidden.
Appendix D
Licensing
This appendix gives the license texts for LJK/CDROM.
There are three kinds of licenses for using LJK/CDROM,
as described in the sections below:
General License Terms
For each of those kinds of license, the following apply:
- Software provided under these licenses may only be used in
accordance with the terms specified here. Variances to these terms may
only be made in writing, and no representative of LJK Software is
empowered to
do otherwise.
- No ownership or interest in the subject software is provided by
these licenses. The license is valid only for use on machines owned by
or leased to the licensee. The license may not be transferred to
another entity.
- All aspects of license compliance are subject to technical
enforcement procedures (e.g., Release Date restrictions), but absence
of such procedures does not relieve the licensee to honor the
limitations of the license.
No other use of LJK/CDROM is permitted.
Limitation of Liability
In case of any dispute, the maximum liability of LJK Software shall be
the price paid by the licensee for the license.
Choice of Law
Governing law for each of these license types shall be the laws of the
Commonwealth of Massachusetts.
D.1 Standard License
The recipient of a Product Authorization Key from issuer LJK for an
LJK/CDROM Standard License may use LJK/CDROM:
- Only to use the standard features of LJK/CDROM described in
this document,
- Only on a single VMS system or VMScluster,
- Only for up to the licensed number of simultaneous users specified
in the Product Authorization Key,
- Only for a version of LJK/CDROM with a Release Date prior to
the Release Date specified in the Product Authorization Key.
Prior to the Release Date specified in the Product Authorization Key,
the licensee has the right:
- to expect responses to bug reports submitted to LJK Software in
accordance with the directions in Appendix B, Bug Reports,
- to contact LJK Software via Internet electronic mail at a unique
address to receive answers to informal questions.
The Release Date specified in the Product Authorization Key for a
Standard License corresponds to the end of the Right-to-Use New
Versions period purchased with that Standard License (a minimum of one
year).
D.2 VMS Hobbyist License
The holder of VMS Hobbyist Product Authorization Key with an expiration
date less than one year in the future for product OPENVMS-HOBBYIST from
issuer DEC who does not have a Standard License for LJK/CDROM may
use LJK/CDROM:
- Only to use the standard features of LJK/CDROM described in
this document,
- Only for home hobbyist purposes having no business (commercial or
non-commercial) purpose,
- Only during the duration of their VMS Hobbyist Product
Authorization Key,
- For the version covered by this manual or any earlier version of
LJK/CDROM.
The hobbyist user has no guarantee of receiving responses to any bug
reports.
D.3 No-charge License
A user who does not have a Standard License for LJK/CDROM
and whose usage is not eligible for the VMS Hobbyist License above may
use LJK/CDROM:
- Only to use the VERIFY command of LJK/CDROM,
- without any requirement for a Product Authorization Key,
- for the version covered by this manual or any earlier version of
LJK/CDROM.
The no-charge user has no guarantee of receiving responses to any bug
reports.
Appendix E
VMS Issues
This appendix discusses VMS version-related ISO-9660 issues.
E.1 Multiple Hierarchies
On VMS V7.3 and at least some earlier versions, ISO9660 MOUNT
works only for the first Hierarchy. That can be a
Primary Hierarchy or a Supplementary Hierarchy,
but Hierarchies after the first cannot be mounted.
As a workaround, make sure the Hierarchy you expect to be used
from VMS is the first Hierarchy for which you issue the CREATE
HIERARCHY command.
E.2 Volume Switching
While VMS V6.2 does a reasonable job of handling "volume switching"
when there are fewer CDROM
drives available than the total number of discs in the Volume Set, VMS
V7.0-VMS V7.3 have problems. Unless you have a VMS ECO from HP to
correct this problem, you should restrict your use of Volume Sets on
those versions to situations where you are able to
mount all members of the Volume Set at the same time. Otherwise, in the
worst cases, VMS may crash.
This problem only affects discs mounted as ISO-9660 Volume Sets.
Mounting /FOREIGN causes no problem.
Appendix F
Messages
This appendix gives an explanation of messages that might be issued during use of LJK/CDROM.
There are four types of LJK/CDROM messages:
F.1 Primary Messages
These are the message codes for LJK/CDROM that might be returned
to DCL (after first displaying them if other than Success severity).
These explanations are also available via the HELP/MESSAGE
command once your system has been set up according to the instructions
in Section A.3, Enabling HELP/MESSAGE After Installation.
Another set of messages that might be returned to DCL are those from
the LICENSE facility. Those are documented and supplied for the
HELP/MESSAGE command by VMS itself.
LJK-F-ALLOSPACE, 'logical-block-count' per-disk allocation space is
less than calculated 'logical-block-count'
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.
User Action: Consider submitting a bug report to
LJK Software as described in Appendix B, Bug Reports.
LJK-W-BADCDFORMAT, format errors were encountered in the ISO-9660 data
Facility: LJK, LJK/CDROM Utility
Severity: Warning
Explanation: As indicated in messages displayed before
this one, the format of this Volume did not properly verify
against the relevant standards.
Those earlier messaged will indicate one or more of the following
causes for this problem:
- Faulty formatting of a Volume created by some other software
- An internal error in LJK/CDROM
- A hardware error preventing the reading of data
Further operations based on the commands(s) given will be skipped.
User Action: Report the problem to the appropriate
software or hardware maintainer.
LJK-F-BADCMDCHAR, bad 'name' character "'character'" in value "'string'"
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: An illegal character was provided in a
command line.
User Action: Review the relevant portion of
Chapter 9, Command Reference within the LJK/CDROM Reference Manual.
LJK-F-BADCMDTEXT, bad 'name' value was "'string'"
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: A bad text value was provided in a
command line.
User Action: Review the relevant portion of
Chapter 9, Command Reference within the LJK/CDROM Reference Manual.
LJK-F-BADCMDVALUE, bad 'name' value was 'nnn' (!-'hex-longword' hex)
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: A bad numeric value was provided in a
command line.
User Action: Review the relevant portion of
Chapter 9, Command Reference within the LJK/CDROM Reference Manual.
LJK-W-BADISO9660, 'string'
Facility: LJK, LJK/CDROM Utility
Severity: Warning
Explanation: Data on the Volume for which
verification was requested violates the ISO-9660 standard.
User Action: If the Volume was formatted by
the latest version of LJK/CDROM consider submitting a bug report
to LJK Software as described in Appendix B, Bug Reports within the
LJK/CDROM Reference Manual. If the Volume was formatted by some other
software, contact the maintainer of that software.
LJK-W-BADJOLIET, 'string'
Facility: LJK, LJK/CDROM Utility
Severity: Warning
Explanation:
Data on the Volume for which verification was requested
violates the Microsoft Joliet standard it claims to honor.
User Action: If the Volume was formatted by
the latest version of LJK/CDROM consider submitting a bug report
to LJK Software as described in Appendix B, Bug Reports within the
LJK/CDROM Reference Manual. If the Volume was formatted by some other
software, contact the maintainer of that software.
LJK-F-BADLOGIC, internal logic error detected
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.
User Action: Consider submitting a bug report to
LJK Software as described in Appendix B, Bug Reports within the LJK/CDROM Reference Manual.
LJK-F-BADLOGICPC, internal logic error detected at PC 'hex-longword'
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.
User Action: Consider submitting a bug report to
LJK Software as described in Appendix B, Bug Reports within the LJK/CDROM Reference Manual.
LJK-W-BADPOSIX, 'string'
Facility: LJK, LJK/CDROM Utility
Severity: Warning
Explanation: Data on the Volume for which
verification was requested violates the Rock Ridge or System Use
Sharing Protocol standard it claims to honor.
User Action: If the Volume was formatted by
the latest version of LJK/CDROM consider submitting a bug report
to LJK Software as described in Appendix B, Bug Reports within the
LJK/CDROM Reference Manual. If the Volume was formatted by some other
software, contact the maintainer of that software.
LJK-W-DIFFERENT, the two volumes were logically different
Facility: LJK, LJK/CDROM Utility
Severity: Warning
Explanation: The two Volumes for which the
LJK/CDROM COMPARE command
was issued are not logically the same.
User Action: Compare the areas of difference with your
expectations.
LJK-I-ENQLMLOW, ENQLM quota for process is lower than recommended value
of 100
Facility: LJK, LJK/CDROM Utility
Severity: Informational
Explanation: The specified quota is low.
User Action: Raise the quota using AUTHORIZE or via
system parameter PQL_MENQLM.
LJK-F-EXISTS, 'file-identifier' already exists
Facility: LJK, LJK/CDROM Utility
Severity: Informational
Explanation:
- You are attempting to specify an ISO-9660 File that
already
exists for a different source file.
- LJK/CDROM got an internal error (when accompanied by BADFIELD
or BADLOGIC).
User Action:
- Revise your commands to avoid a conflict.
- Consider submitting a bug report to LJK Software as described in
Appendix B, Bug Reports within the LJK/CDROM Reference Manual.
LJK-F-FOREIGN, device 'device-name' is mounted /FOREIGN
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: A device currently mounted /FOREIGN was
specified in a context where that is not permitted, such as in a
ddcu:[dire]file.ext file specification.
User Action: Determine whether it is the mount status
or the device name that is wrong and retry with corrections.
LJK-I-INSFVOLIDS, insufficient /VOLUME= values for Volumes
'volume-number' through 'volume-number'!/!_and a single wildcarded
value was not supplied
Facility: LJK, LJK/CDROM Utility
Severity: Informational
Explanation: The Volumes being written as a
Volume Set cannot all have unique Volume Identifiers for at least one
Hierarchy. This is only
an informational message because the result is a legal ISO-9660
Volume Set, but mounting individual Volumes on VMS may be
confusing.
User Action: Decide whether unique Volume Identifiers are
important enough to you that you want to make adjustments.
LJK-S-INTERCHANGE_1, ISO9960 Volume metadata conforms to Interchange
Level 1
Facility: LJK, LJK/CDROM Utility
Severity: Success
Explanation: The Volume was verified as
compatible with ISO-9660 Interchange
Level 1. This means it should be readable on any system that is
specified as being able to read ISO-9660 Volumes.
User Action: Distribute without concern.
LJK-I-INTERCHANGE_2, ISO9960 Volume metadata conforms to Interchange
Level 2
Facility: LJK, LJK/CDROM Utility
Severity: Informational
Explanation: The Volume was verified as
compatible with ISO-9660 Interchange
Level 2. This means it should be readable on systems that are specified
as being able to read ISO-9660 Volumes and can also handle
longer File Identifiers and Directory Identifiers.
User Action: Distribute with a warning that longer
names are included.
LJK-I-INTERCHANGE_3, ISO9960 Volume metadata conforms to Interchange
Level 3
Facility: LJK, LJK/CDROM Utility
Severity: Informational
Explanation: The Volume was verified as
compatible with ISO-9660 Interchange
Level 3. This means it should be readable on systems that are specified
as being able to handle the entire ISO-9660 standard.
User Action: Distribute with a warning that full
ISO-9660 compliance is required.
LJK-F-IOSBERROR, unanticipated status block error from the 'name'
system service
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: An I/O error was returned by VMS.
User Action: Investigate the hardware problem.
LJK-F-ISO9660ALLOCATED, Volume 'volume-number' Block
'logical-block-number' was previously allocated
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.
User Action: Consider submitting a bug report to
LJK Software as described in Appendix B, Bug Reports within the LJK/CDROM Reference Manual.
LJK-F-ISO9660NOFIT, ISO9660 per-Volume overhead leaves no space for
files!/!_within /SPACE='logical-block-count' Logical Blocks of
/BLOCK_SIZE='nnn' bytes each
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The required metadata to support
Hierarchies and Directories
is so large that it leaves no room for data.
User Action: Consider using larger Volumes or
smaller Volume Sets.
LJK-F-ISO9660NOVOL, Providing space of 'count' Logical Blocks!/!_within
the per-Volume available space of 'count' Logical Blocks!/!_would
require Volumes 'volnum' through 'volnum',!/!_exceeding the imposed
limit of /SETSIZE='count' Volumes
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The data specified cannot fit within the
given constraints.
User Action: Consider allowing more Volumes in
the Volume Group.
LJK-F-LINKNOTFIRST, the LINK GROUP 'name' command followed a CREATE
HIERARCHY command
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The command LINK GROUP was given
too late.
User Action: Issue the LINK GROUP command
before the first
CREATE HIERARCHY command.
LJK-F-NOCOMMAND, No command verb was present for parsing
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The command was not present for parsing.
User Action: Look for local modifications that created
a duplicate command tables file before LJK/CDROM was installed.
Make sure the process logged in after LJK/CDROM was installed.
LJK-F-NOFILES, no files selected
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The LJK/CDROM WRITE command
was issued
without specifying any Files and without any Files
specified by prior ADD
commands. LJK/CDROM will not format a Volume without
including at least one File. The product is not aimed at the
coaster fabrication market.
User Action: Try again, specifying at least one file
to write to the Volume.
LJK-F-NOMATCH, Existing and Modified records do not match
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.
User Action: Consider submitting a bug report to
LJK Software as described in Appendix B, Bug Reports within the LJK/CDROM Reference Manual.
LJK-F-NOROOTFILE, file 'file-specification' was not included in the
root directory
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: A file was not provided for the [] root
Directory for some Hierarchy even though it had been
specified by one of the qualifiers /PUBLISHER=, /DATA_PREPARER=,
/APPLICATION=, /COPYRIGHT_FILE=,
/ABSTRACT_FILE= or /BIBLIOGRAPHIC_FILE=.
User Action: Use an appropriate ADD command,
or additional filespec to the WRITE
command, to provide the required file. Otherwise, refrain from
specifying that the particular root file will be provided.
LJK-F-NOTDISK, device 'device-name' is not a disk
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: LJK/CDROM can only deal with optical
discs or magnetic disks, except for the /OUTPUT= qualifier, but some
other device was specified.
User Action: Correct the specification in the command.
LJK-F-NOTFOREIGN, device 'device-name' is not mounted /FOREIGN
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: For all contexts except a full file
specification (ddcu:[dir]file.ext), LJK/CDROM requires that
devices be mounted /FOREIGN.
User Action: Determine whether it is the mount status
or the device name that is wrong and retry with corrections.
LJK-F-NOVOLID, no /VOLUME= value for Volume 'volume-number'
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.
User Action: Consider submitting a bug report to
LJK Software as described in Appendix B, Bug Reports within the LJK/CDROM Reference Manual.
It is possible that modifying your use of the /VOLUME= qualifier might
work around this error in LJK/CDROM.
LJK-F-OPENERR, error opening 'file-specification'
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: LJK/CDROM was unable to open the
specified ISO-9660 CDROM or disc image.
User Action: Analyze the problem using normal VMS
techniques considering any subsidiary chained messages.
LJK-F-OPENIN, error opening 'file-specification' as input
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: LJK/CDROM was unable to open the
file specified by /APPUSE=.
User Action: Analyze the problem using normal VMS
techniques considering any subsidiary chained messages.
LJK-F-OPENOUT, error opening 'file-specification' as output
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: LJK/CDROM was unable to store under
the specified File Identifier
(including a new highest File Name Version because an entry already exists
for the highest possible File Name Version).
User Action: Analyze the problem using normal VMS
techniques considering any subsidiary chained messages.
LJK-F-POSIXTOOBIG, Too much Posix information for Rock Ridge V1.09 is
provided!/!_for file "'file-specification'"
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The information provided for POSIX is
more than will fit in the available space.
User Action: Provide less Posix information, refrain
from specifying /POSIX,
or specify /POSIX=IEEE_P1282 rather than /POSIX=RRIP_1_09.
LJK-F-READERR, error reading 'volume-name'
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: One of the two volumes specified with the
LJK/CDROM COMPARE
command could not be validated. LJK/CDROM is unable to compare
unless the inputs specified are both valid ISO-9660 Volumes.
User Action: Re-create the faulty Volume.
LJK-F-SMALLDISK, only 'vms-block-count' of the specified
'vms-block-count' blocks are available!/!_on target 'device-name'
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The /SPACE= qualifier specified more
space that was available
on the target Volume.
User Action: Specify a smaller amount of space, avoid
specifying /SPACE=, or use a larger target Volume.
LJK-F-SSERROR, unanticipated error from the 'name' system service
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: The error specified on following lines
was returned from a VMS system service.
User Action: Take action according to normal VMS
troubleshooting methods.
LJK-F-THISSPACE, 'count' block!%S for the Extended Attribute Record
plus!/!_!_'count' block!%S for File Section 'number'
of!/!_!_'nnn'!/!_!_is more than the calculated!/!_!_'count' maximum
blocks available on any volume
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.
User Action: Consider submitting a bug report to
LJK Software as described in Appendix B, Bug Reports within the LJK/CDROM Reference Manual.
LJK-W-UNKCDFORMAT, unknown version indicators were encountered in the
ISO-9660 data
Facility: LJK, LJK/CDROM Utility
Severity: Warning
Explanation: As indicated by messages displayed
earlier, the Volume has System Use Areas or Continuation Areas
that cannot be interpreted
by LJK/CDROM.
User Action: For the VERIFY command, decide
whether a Volume
with this status is acceptable. If the Volume was formatted by
the latest version of LJK/CDROM consider submitting a bug report
to LJK Software as described in Appendix B, Bug Reports within the
LJK/CDROM Reference Manual.
LJK-F-VALUENOTMATCH, 'name' value 'nnn' (!-'hex-longword' hex) does not
match 'nnn'
Facility: LJK, LJK/CDROM Utility
Severity: Fatal
Explanation: There was an internal error in
LJK/CDROM.